Ansicht
Dokumentation

MMPUR_SOA_SESCRT_MXI - BAdI: Customized XML Mapping before SES Creation (SOA Inbound)

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Service Entry Sheet (MM-PUR-SRV-SES) component. You can use this BAdI to replace the standard mapping with your own customized XML mapping. The BAdI is called before the standard mapping, hence before creating a service entry sheet. Be aware that if you set the flag to ABAP_TRUE( CV_SKIP_STANDARD MAPPING) to skip the standard mapping and replace it with your own XML mapping, the BAdI Data Processing before SES Creation will also be skipped. For more information, see section Requirements.

• BAdI method: MAP_XML_DATA_IN (Customize Mapping before SES Creation)

Note: Read the documentation of the BAdI method Customize Mapping before SES Creation (IF_SOA_SES_CRTIN_MAP_XML_IN~MAP_XML) in detail before implementing custom logic. This method provides you with instructions on how to do this without breaking standard application logic.

Note: We recommend taking a look at the implementation example class: CL_EXMP_SESCRTIN_MAP_XML_IN (see section Example).

You must create and activate your own implementation of this BAdI and give the implementation a short text. To do this you will need the following authorizations:

• Administrator Role for Custom Fieldsapp

To implement the BAdI follow these steps: Go to Custom Fieldsapp > Choose Custom Logic tab > Click + to add your implementation > Select Procurement: Service Entry Sheet Header as Business Context > Select the BAdI you want to implement > Enter a short description of your implementation > Click on Create > Choose whether you want to use the example implementation.

Note: To replace the standard mapping with your XML mapping, skip the standard mapping by setting the flag to ABAP_TRUE (Changing Parameter CV_SKIP_STANDARD MAPPING). Otherwise, the standard mapping will be called nevertheless.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

• IS_INBOUND_MESSAGE

This importing parameter contains the SOA Request.

• CV_SKIP_STANDARD_MAPPING

This changing parameter allows you to skip the standard mapping before creating a service entry sheet. To skip insert: ABAP_TRUE. To call the standard mapping, nevertheless, insert: ABAP_FALSE (default setting).

• CS_HEADER

This changing parameter allows you to adjust the service entry sheet header data.

• CT_ITEM

This changing parameter allows you to adjust the service entry sheet item data.

• CT_ACCOUNT_ASSIGNMENT

This changing parameter allows you to adjust the service entry sheet account assignment data.

• CT_HEADER_ATTACHMENT

This changing parameter allows you to adjust the service entry sheet header attachment data.

• CT_ITEM_ATTACHMENT

This changing parameter allows you to adjust the service entry sheet item attachment data.

• CT_HEADER_NOTE

This changing parameter allows you to adjust the service entry sheet header note data.

• CT_ITEM_NOTE

This changing parameter allows you to adjust the service entry sheet item note data.

• CT_MESSAGES

This changing parameter allows you to adjust the messages that were defined in the standard mapping of the service entry sheet.

You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the Implementation Example Classes section.

The following example implementations are available:

• CL_EXMP_SESCRTIN_MAP_XML_IN

You can use this example implementation to implement a simplified version of the standard mapping and to trigger specific use cases depending on the account assignment category in the service entry sheet. In detail, you can append error messages to service entry sheets that contain items with the account assignment category X. As a result, the service entry sheet is not created. Further, the standard mapping will be called if a service entry sheet only contains items with the account assignment category K.

If the account assignment category is neither X nor K, the customized mapping is called. It differs from the standard mapping as it

• converts external currency and UOM codes into internal currency and UOM codes.

• converts currency values into the internal ABAP format.

• fills up numbers with leading zeros to match the correct length of a field (e.g. for Cost Center).

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

For detailed information on the BAdI method see: Customize Mapping before SES Creation

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 7220 Date: 20240523 Time: 205226     sap01-206 ( 173 ms )