Ansicht
Dokumentation
EDI_V_TXTOUT_SUP - Define Mapping for Outbound Texts for Integration with Buyers
rdisp/max_wprun_time - Maximum work process run time BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Define the XML text type mapping for outbound messages that you send to an external buyer system.
For you as a supplier, your system can send long texts that are relevant for the buyer using SOAP service interfaces. For example, a customer invoice that you send to the buyer system through the SOAP Web service Customer Invoice - Send (B2B), message type InvoiceRequest_Out, can contain texts that are intended to be visible on the invoice output, such as a note text for a particular billing item.
In integration scenarios between suppliers and buyers, both communicating systems have different text types with different text IDs. Therefore, a mapping from the Sales side (component SD) to the Sourcing and Procurement side (component MM) side is required. To avoid excessive mapping and customizing effort for each business partner and system, SAP provides independent and predefined XML text types. Both sides (that is, the sending and receiving systems) must map the XML text types that they want to use to text IDs in their respective system.
In the current configuration activity, you define the mapping between the text IDs in your supplier system and the XML text types that are used in the relevant outbound SOAP message type, for example, InvoiceRequest_Out. Outbound text types are then received by the external buyer system and can there be remapped to the local text IDs as required.
Note that texts are always sent out in the language of the bill-to party.
The following table lists the predefined XML text types relevant for billing documents:
| Document Level | | XML Text Type | | Description |
| Header | | BillingInfo | | Billing Info for Customer |
| | BillingInstruction | | Billing Instruction | |
| | BillingInstFromCust | | Billing Instruction from Customer | |
| | BillingNoteFromCust | | Billing Note from Customer | |
| Item | | BillingInfo | | Billing Info for Customer |
| | BillingInstruction | | Billing Instruction | |
| | BillingInstFromCust | | Billing Instruction from Customer | |
| | BillingNoteFromCust | | Billing Note from Customer | |
| | MaterialSalesText | | Material Sales Text | |
| | SalesNote | | Sales Note for Customer | |
| | SalesNoteFromCust | | Sales Note from Customer |
You want to map one of the standard billing document header texts in your system, TX05 ("Billing Instruction for Customer"), to the predefined XML text type BillingInstruction. You make the relevant settings in the configuration activity. When an invoice is sent to the buyer system, the buyer system also receives it as XML type BillingInstruction. In the buyer system, this XML text type can then be mapped to a freely selectable local text ID.
SAP predelivers some standard mappings that you can adapt according to your business requirements.
CL_GUI_FRONTEND_SERVICES - Frontend Services Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 4098 Date: 20240523 Time: 171128 sap01-206 ( 65 ms )
