Ansicht
Dokumentation

Text Transfer (Enhanced) ( RELNSRM_70_TEXT_MAPPING )

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Short text

Text Transfer (Enhanced)

Use

As of SAP Supplier Relationship Management (SAP SRM) 7.0, the transfer of note texts between procurement documents (such as supplier notes, supplier remarks, or approval notes) has been enhanced. The enhancement affects both the transfer of texts between SAP SRM and SAP ERP as well as between SAP SRM procurement documents.

Text Transfer Between SAP SRM and SAP ERP Documents

If you use the classic or the extended classic scenario and SAP ERP 6.0 EHP 04 or higher, you can ensure that all note texts appearing on procurement documents are also displayed on their follow-on documents, independent of whether the documents are created or processed in SAP SRM or SAP ERP. By mapping the texts in Customizing of SAP SRM, you set up the system to transfer the note texts between SAP ERP and SAP SRM, so that they are available throughout the entire procurement process.

For example, if a user creates a purchase requisition in SAP ERP, and sourcing of the requirement is carried out in SAP SRM, follow-on documents such as an RFx or a purchase order are created in SAP SRM. By mapping the texts, you can define which header and item texts in the SAP ERP purchase requisition are also displayed in SAP SRM in the shopping cart, in the RFx, or in the purchase order. When purchasing documents, such as the purchase order, are replicated back to SAP ERP, the texts are also replicated as defined in the mapping.

To ensure the availability of note texts according to your requirements, you can flexibly define mappings of different text types between SAP SRM and SAP ERP. For example, a supplier text created in a shopping cart can be mapped to an internal note in an RFx and become a supplier text in the purchase order.

Text Transfer Between SAP SRM Documents

Up to now, within SAP SRM you could only transfer texts of the same text type from one purchasing document to another, for example from the shopping cart header (text type HTXT) to the header of the purchase order (also text type HTXT). As of SAP SRM 7.0, you can flexibly map texts of different types. For example, you can map a text of the type HTXT from the shopping cart header to a text of the type NOTE on the purchase order header. The same applies to the text types available on item level of the procurement documents.

Note:If items with texts of the same text type must be taken over from several documents, for example SRM shopping carts, to a single SRM procurement document, for example an SRM purchase order, only the text of the first document is copied over to the follow-on document.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

The following Customizing activities are relevant:

• Supplier Relationship Management -→ SRM Server -→ Cross-Application Basic Settings -→ Text Mapping -→ Text Mapping for Inbound and Outbound Texts

• Supplier Relationship Management -→ SRM Server -→ Cross-Application Basic Settings -→ Text Mapping -→ Text Mapping for Internal Texts

Further Information

BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3625 Date: 20240523 Time: 082601     sap01-206 ( 82 ms )