To find a source of supply by elements.
Entity Type | Service Operation |
---|---|
Software Component Version |
|
Release State | Released |
Technical Name |
|
Namespace |
|
Category | A2X |
Direction | Inbound |
Mode | Synchronous |
Idempotency | Not applicable |
Change/Update Behavior | Type 1 |
P2P Communication Enabled | True |
The Find Source of Supply by Elements
service operation is used to read the transportation lane data.
SourceOfSupplyTDMByElementsQuery_sync
Receives data for the transportation lane search. This type can contain data for the following:
SellerPartyID
ReceivingLocationID
MaterialID
ProductSellerID
ProductCategoryID
SourceOfSupplyTDMByElementsResponse_sync
Returns data for the transportation lane search, product procurement cost data, and time-dependent data based on search criteria from the inbound message. At least one of the following parameters must be provided for the query:
SellerPartyID
ReceivingLocationID
MaterialID
ProductSellerID
ProductCategoryID
The output is based on the AND
operation for all input parameters provided.
FaultMessage
The generated proxy in Demand Data Foundation (DDF) is the /DMF/CL_FND_SOSTDM001QR
ABAP class. The proxy data type is used in DDF for the /DMF/FND_SOS_ELEMNTS_QUERY
request message and the /DMF/FND_SOS_ELMNTS_RSP
response message.
The Service Implementation Workbench (SIW) is used to implement the service back-end system. The SIW uses the /DMF/II_FND_SOSTDM001QR
project ID configuration name and the /DMF/CL_FND_SOSTDM001QR_SI
generated service implementation class.
DDF uses the Service Mapping Tool (SMT) for the inbound message mapping (/DMF/CL_SOSQR_SMT
Mapping
field).
If you do not select the Unlimited
checkbox and send 0 (zero) as the maximum value, the system takes the upper limit as 1.
The method calls are as follows:
/dmf/cl_sos_assist=>mapping_inbound_qr
/dmf/cl_ext_lane=>lane_m_read
/dmf/cl_sos_assist=>mapping_outbound_q
The /DMF/SE_FND_SOSTDM001QR
Business Add-In (BAdI) is available for this operation. The BAdI is used to enhance the inbound message, and it is defined as an external customer BAdI. A default implementation is not delivered.
Supplementary components are not relevant for implementing this service.