Home / Featured Training / External Product Mapping

External Product Mapping

The external product mapping table should be defined when implementing with a 3rd party system where a purchase is made in AA and that purchase is pushed up to the 3rd party vendor. 

Once the necessary provisioning of services has been established for your vendor, AA and the 3rd party vendor are able to be integrated in such a way that when a purchase is made on the AA side for a particular product/service, the vendor’s application can than see that the product/service was purchased and provide access to the product or content on their side.

External Product Mapping Grid in AA: Admin  System  External Product Mapping (stdgrid.show_grid?p_table_name=EC_CFG_EXTERNAL_PRODUCT_MAP)

AA Product Key fields:
External product code: The code of the product in the vendor’s application (please check with your vendor on exactly what should be used as the identifier).  ACGI recommends using a similar naming scheme for product codes and IDs (between AA and the 3rd party) by putting an “E” or “P” in front of the numeric External Product Code value to represent E for Events or P for products. This external product code must match exactly with the vendor’s application.

Product Area: The module of the product being mapped.

Qualifier 1:

  • Product Area: AR
    •  Misc. item code
  • Product Area:EVT
    • Event ID
  • Product Area:EC
    • Product serno
  • Product Area: MEM
    • Subgroup id

Qualifier 2:

  • Product Area: AR
    • Set of books for the misc. item.
  • Product Area: EVT
    • Primary item id (only primary items are supported)
  • Product Area: MEM
    • Class code

Qualifier 3:

  • Product Area: MEM
    • Subclass Code

Maximum Quantity Per Customer: Limits the number of times a customer can purchase the product in a lifetime. If left blank, the customer can purchase the product an unlimited number of times. For an event, this defaults to one because a customer can only be registered for an event once.

Note, the base integration for this does NOT support canceling products/access. Backoffice staff will have to cancel an order on both the AA side and 3rd party side.

Product Key fields required on 3rd party side:

  1. Remote product url: ecssaextprod.add_to_cart?p_vc=ZZZZ&p_context=LMS&p_prod_cd=XXXX (where ZZZZ is the 3rd party vendor code (e.g. COMMPARTNERS) and XXXX is the external product code)
  2. Remote product id: is the External Product Code as configured in the 3rd party system and in the external product mapping table above.

Support for membership was added in 8.6.3