Export Mapping

Prerequisites for Export Mapping

Export Mapping provides a way to associate certain codes and values that are external to OPERA Cloud (such as general ledger codes or back office application codes that are typically determined by the property or the chain) to codes used in OPERA Cloud (such as transaction codes or market codes). When export mapping is configured for an OPERA Cloud code, the export can include the associated information needed for processing externally. For example, when generating an export that contains transaction codes and transaction totals you may require certain codes/values, such as a GL (general ledger) code, to be associated with the transaction code. In this case, each OPERA Cloud transaction code would require an export mapping associated with it. 

Export Mapping configuration involves these steps:

  • Setting up the export mapping types.

    • For each export mapping type, define the property/chain-specific export mapping codes that will be associated with an OPERA Cloud code. For more information, see Managing Export Mapping Types and Codes.

  • Linking the export mapping codes with the OPERA Cloud code and assigning specific values to the export mapping codes. For more information, see Managing Export Mappings.

Note:

 If mappings are configured and are to be included in any export, that export definition must be updated in order to refer to such mappings.