Start of Content Area

Function documentation Maintaining Service Mapping  Locate the document in its SAP Library structure

Use

Service mapping describes the representation of the fields for a container – especially the feature attributes – in the “fixed” interfaces of a service in the form of the service container. No coding (e.g. in a BAdI) needs to be created for this mapping, just metadata entries.

Starting from a service feature, container fields can be represented in the fields of the service container and in this way included in the service. This also makes it possible to copy the results of a service back into the container(s) for the object. (Along with this basic functionality, there are certain special cases that are supported – e.g. the use of additional conditions that cannot, however, be described in detail in this document.)

The procedure for simple mapping of a feature attribute to a service is described using the example of a mapping of the new field ZFELD to the pricing product in pricing. This means that this field is represented in field PRICE_PRODUCT of service container PRC_I_ACS (= “Access structure item”) for feature PRC (= “CRM Pricing”), which is assigned to object BD (= “Billing document”) in application CRMB (= “CRM Billing”).

Procedure

1.       In the navigation tree, open the folder “Object”.

2.       Open the sub-objects for the entry ‘BD’.

3.       Open the folder “Feature”.

4.       Search the list of features for the entry ‘PRC’. Because it is derived from a service feature, it has sub-objects “Function group” and “Business Add-In” for the service wrapping.

5.       Call the context menu for the entry ‘PRC’, and choose the function “Service Mapping -> Display List”.

6.       The detail area displays a list of existing mapping links.

7.       To view the full list of data, you should make the navigation tree as narrow as possible.

8.       In the function bar for the list, choose the function “Display/change data”.

9.       In the function bar for the list, choose the function “Create entry”.

10.   A new line is added to the list.

11.   The ‘Application’ field already has the default value ‘CRMB’, the ‘Object’ field already has the value ‘BD’ and the ‘Service’ field has value ‘PRC’. In the ‘Service container’ field, enter the value ‘PRC_I_ACS’. In the first ‘Field name’ field, enter the value ‘PRICE_PRODUCT’. In the ‘Container’ field, enter the value ‘BDI’. In the second ‘Field name’ field, enter the value ‘ZFELD’ and in the ‘Sort sequence’ field, enter any required value. Use F4 Help to determine whether the ‘Direction’ field plays a role in mapping to a service container, in mapping to container, or both. (In the customer name range, the “specific” values ‘G’, ‘H’ and ‘I’ are relevant here.) Specify a sort sequence in relation to the other fields. You usually leave the fields “Condition” and “Flag target initial” empty.)

12.   Save you data changes using the “Save” function in the BE Navigator.

To ensure that the mapping is available in the generated application, the corresponding service wrapping (in the example: function group “Object layer” of service feature PRC in object BD) must be regenerated.

 

 

End of Content Area