Ansicht
Dokumentation

/AFS/SIMGBC_MAPPING - Interface Mapping

/AFS/SIMGBC_MAPPING - Interface Mapping

Fill RESBD Structure from EBP Component Structure   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you define the customizing for the AFS to SAP Retail Interface. You access this when master data is distributed from the AFS system to the SAP Retail system (material/article and prices).

  • You have logical systems existing to represent the interfacing SAP Retail systems.
  • You have the associated retail customers existing in the customer master.
  • Transfer the merchandise categories and associated data from the SAP Retail systems before defining the Customizing, to minimize mistakes when specifying which Retail data must be associated to AFS data.
  • Make use of the consistency check after changing the SAP AFS to SAP Retail Interface mapping by choosing Logistics - General -> AFS Interface -> AFS Interface to Retail -> Check Consistency of Interface Mapping
  • Maintain Header Entries. One entry must exist for each interfaced SAP Retail system. A retail site, a purchasing organization and a purchasing group must be specified if material prices are to be exchanged to a SAP Retail system.
  • Maintain the following mappings for determination of merchandise category for each SAP Retail Logical system:
  • Assign merchandise category at the material master level. In this case, only the AFS and Retail characteristics need to be mapped. The mapping of the corresponding charactersitic values is required only if they are not same.

  • Maintain a more generic mapping at the grid level. Here the merchandise category is mapped with the grid. Then the mapping of grid characteristics with Retail characteristics is done.

  • Map merchandise category with the material group of the material master, in case of no grid materials.

Note: Only one kind of mapping is required to determine the Merchandise Category. In case all the mappings exist then the priority is given in the order as mapping is mentioned above.

  • Map the Retail charactersitics to AFS characteristics. You can map the merchandise category at the material master level. In case of the AFS characteristics for category fields there are the following possiblities:
  • The category field is mapped to a Retail characteristic.

  • Different articles are to be created for each different possible Value of the Category Field.

  • One article is to be created with multiple EAN/UPC codes. In this last case the main EAN/UPC code will be the one associated to the category field value specified in the CF value for main EAN field.

  • Maintain the mapping of AFS characteristic values to Retail characteristic values. For each mapping of AFS characteristic to Retail characteristic, there must be one entry per possible AFS characteristic value. Display the possible values for the AFS Characteristic field to know which values must be mapped.

Note: If the AFS Characteristic Value is the same as the Retail Characteristic Value (for example size M), the mapping is not necessary.

  • Maintain the mapping of AFS grids to Retail merchandise categories and optionally characteristics profiles for each SAP Retail Logical System. This action must be performed for all grids associated to materials to be distributed to the SAP Retail system. Generally, master grids should be mapped. Sales grids can be mapped to overwrite their master grid mapping.
  • Maintain the mapping of AFS dimensions to Retail characteristics for each grid mapping. There must be one entry for each variant-creating characteristic linked to the merchandise category and characteristics profile. Display the possible values for the Retail Characteristic field to know which Characteristics must be mapped. The following are a list of mapping possibilities:
  • A Retail characteristic can be mapped to an AFS dimension of the grid,

  • A Retail characteristic can always contain a fixed value,

  • A Retail characteristic can be mapped to an AFS category field with EAN relevance (for example, when a category field is used for colors).

  • Maintain the mapping of AFS dimension values to Retail characteristic values for each mapping of AFS dimension to Retail characteristic. There must be one entry per possible dimension value. Display the possible values for the Dimensions field to know which values must be mapped.

Note: If the dimension value is the same as the characteristic value (for example size M), the mapping is not necessary.

  • Maintain the mapping of material groups to Retail merchandise categories and optionally characteristics profiles for each SAP Retail Logical system. This action must be performed for materials without grids to be distributed to the SAP Retail system. One material group cannot be mapped to different merchandise categories. In this case, extra material groups must be created.
  • Define the usage of Category Fields with EAN relevance for each SAP Retail Logical system. The following are a list of the possibilities:
  • The category field is mapped to a Retail characteristic.

  • Different articles are to be created for each different possible value of the category field.

  • One article is to be created with multiple EAN/UPC codes. In this last case, the main EAN/UPC code will be the one associated to the ctegory field value specified in the CF value for main EAN field.

  • Maintain the mapping of AFS category field values to Retail characteristic values for each mapping of AFS category field to retail characteristic . There must be one entry per possible category field value. Display the possible values for the Category Value field to know which values must be mapped.
  • Maintain the mapping of Sales to Purchasing Condition Types for each SAP Retail Logical System. Click the Import Defaults button to get the default SAP condition types mapping (this functionality is only available when the table is empty).






rdisp/max_wprun_time - Maximum work process run time   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 7452 Date: 20240426 Time: 081606     sap01-206 ( 137 ms )