Specify Extension Data Item Mapping
This User Interface allows you to map the extension base service data item and User Defined Screen extension service data item. In this User Interface, first the data item for the user defined screens service context segment fw_Context mapping is done followed by the in-segment that is the flow of data from the base to UDS which is followed by the header segment save and then the details grid save. Out segment that is flow of data from UDS to Base UI is not mandatory.During unmapping also, first the out segment is unmapped followed by the detail segment save unmapping, header segment save unmapping, in segment unmapping and finally fw_context unmapping.The execution sequence of the method is defined in this page
Click the “Extension Data Item Mapping” link from the “Generate Service” tab in the “Specify User Interface” page.
The “Specify Extension Data Item Mapping” page appears.
The following details are displayed in the header:
|
Business Process |
The description of the selected business process is displayed from the ”Specify user interface” user interface . |
|
Component |
The description of the selected component under the specified business process is displayed from the ”Specify user interface” user interface. |
|
Activity |
The description of the activity under the specified component is displayed from the ”Specify user interface” user interface. |
|
User Interface |
The description of the user interface under the specified activity is displayed from the ”Specify user interface” user interface. |
Select the following:
|
UDS Mapped To |
Use the drop-down to select the extension detail for which data item mapping is to be performed. |
The system displays the following in the header:
|
Base User Interface |
The name of the base user interface. |
|
Base Service |
The name of the base service. |
Select the following:
|
Segment Name |
Use the drop-down list box to specify the segment name of the User Define Screen. |
|
Base Process Section |
Use the drop-down list box to specify the base process section name. |
|
Base Method Name |
Use the drop-down list box to specify the base method name. |
|
Execution Sequence |
Use the drop-down list box to specify the execution sequence of EDK and Base Method. When “Call EDK after Base Method Execution” is selected then after executing the base method edk service will be invoked. When “Call EDK before Base Method Execution” is selected then before executing the base method edk service will be invoked. |
|
Base Segment Name |
Use the drop-down list box to specify the base segment name. |
The system displays the following in the multiline:
|
Segment Name |
The segment name of the UDS. |
|
Data Item Name |
The date item name of the UDS. |
|
Base Data Item Flow Direction |
The flow direction of the base data item. |
|
Base Segment Name |
The name of the base segment. |
|
Base Data item Name |
The name of the base data item name. |
|
Base Method Name |
The name of the base method. |
|
Base Process Section Name |
The name of the base process section name. |
Select the following:
|
Mapping Flow Direction |
Use the drop-down list box to specify the data flow mapping direction between Base and UDS. The combo is loaded with options “In”, “Out” and “InOut”. |
|
Base Data Item Name |
The name of the base data item. |
Click “Save”.
The system saves the mapping of the base data item and flow direction to the UDS segment name and data item name.
Business process, components, activities ,user interfaces and controls should have been defined
Extensions having dependent transaction or Logic extensions are required
In Data Transfer UI ,extension should be defined.
Service should be generated in “Generate Service” tab of “Specify User Interface” page.