Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-EPT-SPI (Application Component) Service Provider Infrastructure⤷
/PLMB/BA_FRW (Package) Framework Persistency
IMG Activity
| ID | /PLMB/FRW_MAPDTL | Define Mapping of Data Elements to Parameters |
| Transaction Code | /PLMB/38000094 | (empty) |
| Created on | 20080718 | |
| Customizing Attributes | /PLMB/FRW_MAPDTL | Define Mapping of Data Elements to Parameters |
| Customizing Activity | /PLMB/FRW_MAPDTL | Define Mapping of Data Elements to Parameters |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /PLMB/FRW_MAPDTL |
Use
In this Customizing activity, you can assign data elements to an object type and to a parameter.
Object Type Assignment
An assignment of a data element to an object type is needed:
- For the determination of a context menu
- If some object type dependent conversions should be processed
An object type can be assigned statically by entering the object type directly, or it can be assigned dynamically by entering a data element in the object type reference field that holds the corresponding object type at runtime.
Parameter Assignment
A data element can be assigned directly to a parameter by entering the parameter name. A potential conversion of the parameter value is processed according to the chosen field type.
Grouping of Data Elements
Data elements that belong semantically together should be grouped. This grouping ensures that data elements that belong semantically together are always handled as a bundle. For example, if several data elements of a structure map to parameter "Material", the grouping makes sure that all dependent fields such as unit of measure or the quantity are not mixed up during the mapping.
Note
For the parameter mapping, all mapping relevant data elements must be distinct in the structure to be mapped. If data elements are not distinct, the corresponding data element group(s) will not be considered in the mapping process.
Only complete groups are considered for mapping. If one or more data elements of a group are missing in a structure, the entire group(s) will be ignored in the mapping.
Mapping can be defined based on data elements or based on a structure plus a field. If -for a certain structure component- there is mapping defined based on data elements and based on a structure plus a field, the structure plus field mapping will always be considered before the data element mapping.
For a detailed analysis of the mapping process, activate log point /PLMU/FRW_MAPPING_INFO in transaction SAAB.
Requirements
Standard settings
Activities
Example
Group 1:
Group Data Element
-------------------------------------------------------------------
GRP_01 MATNR
GRP_01 QUANTITY
GRP_01 UOM
Group 2:
Group Data Element
-------------------------------------------------------------------
GRP_02 MATNR_SUCCESSOR
GRP_02 QUANTITY_SUCCESSOR
GRP_02 UOM_SUCCESSOR
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /PLMB/FRW_MAPDTL | 0 | BSD0000065 | Service Provider Infrastructure |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /PLMB/V_MAPDTL | V - View | SM30 |
History
| Last changed by/on | SAP | 20080731 |
| SAP Release Created in | 701 |
