Kontakt

Ansicht
Dokumentation

BBP_TEXT_MAPPING - Text Mapping for Inbound and Outbound Texts

BBP_TEXT_MAPPING - Text Mapping for Inbound and Outbound Texts

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define mappings between SAP SRM text schemas and texts used in SAP ERP procurement documents. You map texts that need to be transferred from SAP ERP to SAP SRM ("inbound texts") and from SAP SRM to SAP ERP ("outbound texts").

By mapping the texts you ensure that long texts belonging to the header or item level of SAP ERP and SAP SRM procurement documents are transferred along the process flow between SAP ERP and SAP SRM. For example, if an SAP SRM shopping cart is created from an SAP ERP purchase requisition, the header and line item texts in the SAP ERP purchase requisition must be mapped to header and line item texts in the SAP SRM shopping cart.

To be able to map texts between SAP ERP and SAP SRM, you must use enterprise services for transferring data between the systems.

In addition, you have made the following Customizing settings:

  • In Customizing for SAP Supplier Relationship Management, you have defined text types and text schemas. You have done this by using the Customizing activities under SRM Server -→ Cross-Application Basic Settings -→ Text Schema.
  • In Customizing for SAP ERP, you have defined text types and copying rules for the desired procurement documents. Note that only texts of the following SAP ERP procurement documents can be transferred to and from SAP SRM:
  • Purchase Requisition

  • Purchase order

  • Contract

You have have defined the text types and copying rules in Customizing for Materials Managementunder Purchasing -→ -→ Texts for .

If you do not define a specific mapping, the system maps the texts as follows:

  • For SAP SRM shopping cart items of type "Material", the supplier text (SAP SRM text ID "ITXT") is mapped from the shopping cart item level to the SAP ERP purchase order item level to the text type "Material Text" (Text ID F03).
  • For SAP SRM shopping cart items of type "Service", the supplier text (also SAP SRM text ID "ITXT") is mapped from the shopping cart item level to the SAP ERP purchase order item level to the text type "External Service Line Item Text" (Text ID LLTX).

  1. To create a new text mapping, choose New Entries.
  2. Specify a logical SAP ERP System.
  3. Specify the SAP ERP business object type with which you want to map the SAP SRM text type. The following entries are possible:
  • EXTREQ (external requirement)

  • BUS2012 (purchase order)

  • BUS2014 (contract)

  • BUS2105 (purchase requisition)

  1. Specify the SAP ERP text ID with which you want to map the SAP SRM text type. For the meaning of the technical keys provided in the input help, note the following conventions:
  • Text IDs of purchase orders start with "F".

  • Text IDs of contracts start with "K".

  • Text IDs of purchase requisitions start with "B".

For the numbers following the letters "F", "K", and "B", see the SAP ERP Customizing activities where the text types were defined. (See the above section "Requirements".)
  1. Specify whether the SAP ERP text type is mapped at header level, at item level, or both at header and at item level.
  2. Specify the SAP SRM text schema with which you want to map the SAP ERP text type.
  3. Specify the SAP SRM text ID with which you want to map the SAP ERP text type.
  4. Specify whether the SAP SRM text type is mapped at header level, at item level, or both at header and at item level.

Note that you can only map texts that exist at the same level of a procurement document. This means that you can map texts from header level to header level, for example. Ensure that you make the same entries under External Header/Item and under SRM Header/Item.






CPI1466 during Backup   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 5042 Date: 20240524 Time: 012904     sap01-206 ( 131 ms )