Ansicht
Dokumentation
SIMG_V_TMS_C_PUR - Define Transportation-Relevance of Purchasing Documents
General Material Data Vendor Master (General Section)This documentation is copyright by SAP AG.
Allows you to specify whether purchasing documents are relevant for transportation by assigning a control key to the required document types.
In this Customizing activity, you activate the integration of purchasing documents (including MM scheduling agreements) into TM by assigning a control key to the required document types. The control key determines whether a purchasing document and the corresponding inbound delivery or outbound delivery are to be integrated into TM.
When you create a purchasing document for which the integration has been activated, the system assigns the control key to the purchase order (parameter TM_CONTROL_KEY) and to all relevant documents in the document chain, for example, the inbound delivery. This is a fixed parameter that cannot be changed subsequently in the purchasing document.
You have defined the required control keys in the Customizing activity Define Control Keys for Document Integration.
Define which purchasing documents are relevant for transportation by entering one or more parameters, for example, purchasing organization, purchasing group, and purchase order type, and assigning the required control key to the set of parameters.
If you are working with the internal TM component no additional settings are required.
If you are working with an external SAP TM system, to transfer purchasing documents, you also have to set up the workflow as follows:
- In transactionSWETYPV, you have to create an event type linkage for the events CREATED and CHANGED. Make the following entries for each event:
| Object Category: | ABAP Class | |
| Object Type: | CL_SE_PUR_PO_WF_OUT | |
| Receiver Type: | WS53800008 | |
| Receiver Call: | Function Module | |
| Receiver Function Module: | SWW_WI_CREATE_VIA_EVENT_IBF | |
| Event Delivery: | Using tRFC (Default) | |
| Linkage Activated: | Select this checkbox | |
| Behavior Upon Error Feedback: | System defaults | |
| Receiver Status: | No errors |
- You have to define the service output by adding the following entries to view V_T175SOA in transaction SM30:
| Context | Service ID | |
| Purchase Order Created/Changed | CL_SE_PUR_TRQSUITEREQUEST | |
| Purchase Order Created/Changed | CL_SE_PUR_TRQCANCELREQUES | |
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4171 Date: 20240523 Time: 153948 sap01-206 ( 32 ms )
