User Interface
Purpose
The front-end Structure Mapper has been developed so that a new set of mappings can be added, modified or deleted and also to check that the data in the map table is consistent and to perform various validations before it gets stored. This ultimately results in generating mapping information code which reduces time as all DDIC checking is done in this process.
Transaction information about Structure Mapper
Transaction information |
Name |
Transaction name in CRM system |
SMAP |
Program name |
SAPMS_MAPTABLES |
Report name |
SAPSERRREP |
Development class |
SM09 |
Description of the frontend
The screen consists of a tabstrip control with four tabsheets and an error report. Movement from one tabsheet to any of the tab sheets is possible.
Tabsheet-1: Contains information about distinct map names represented as list of mappings.
Tabsheet-2: Contains information for a particular map name, the list of source structures, destination structures, input_type, maporder and active as represented by mapping details .
Tabsheet-3: Contains information in general fields i.e., which source field is mapped to destination field and upon certain criteria and represented as map fields details.
Tabsheet-4: Contains information in general fields i.e. which source field is mapped to destination field. This tabsheet 4 is different from tabsheet 3 since it does source structure to destination structure fields mapping based on data elements. (In short named as container-to-container mapping).
Error report: This error report is called within the dialog program itself. The report is called after code generation for the mapnames and if there are errors for that particular date and time.