Description | Manage Logistics Layout Execution |
Name | ManageLogisticsLayoutExecutionViewIn |
Namespace | http://sap.com/xi/A1S/Global |
Process Component Description | Logistics Control |
Process Component Name | LogisticsControl |
Process Component Namespace | http://sap.com/xi/AP/LogisticsExecution/Global |
Deployment Unit Description | Production and Site Logistics Execution |
Endpoint Activation | By Scoping of Process Component | Operations |
Release Status | Released |
An interface to request Replenishment Task and Removal Task for Internal Logistics.
The web service Manage Logistics Layout Execution View In enables you to connect external applications to your SAP Business By Design system, and to create Replenishment Tasks and Removal Tasks for Internal Logistics.
The web service interface Manage Logistics Layout Execution View In offers the operation Manage_Bundle_V1.
The Manage_Bundle_V1 operation is used to create one or more Replenishment Tasks or Removal Tasks for Internal Logistics.
Due to the stateless behavior of A2X service operations, it is not possible to enforce any kind of transactional or logical locking. In spite of this, clients may be required to enforce that a modifying operation is not executed because the state of the underlying business object instance in the database has changed since the client read its data.
Operations in the service are called synchronously; no message header element is required. It is added to the request of synchronous writing operations to allow the implementation of idempotency, that is, 'exactly once execution' of the operation.
Filling this field is optional for the service consumer.
Modifications performed using the A2X service will resemble the modifications performed in the SAP Business ByDesign UI screen.
Values of Product ID , Logistics Area ID, Barcode Text are all case sensitive. Therefore, the customer or the partner consuming this service through PDI or any means has to pass the Values in proper Upper Case Or Lower Case. This depends on how they have maintained these values in the Master Data. For example, the material 'MCF-0001' can be treated different from 'mcf-0001'.
Currently, there are no validations performed on the request xml. It is the user’s responsibility to ensure that the xml is in correct format and contains precise values for create operations.
Communication Timeout
Maintain bundle and check maintain bundle operations are mass-enabled stateless synchronous web service operations. Transferring or requesting amounts of data that are too large causes communication timeouts. The web service consumer is responsible for ensuring reasonable sizes of data for mass operations.
Response Message
The structure of the response message consists of two parts:
A business document-specific part containing information about IDs and UUIDs of the created and changed business documents
Log items containing system messages including errors, warnings.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <LogisticsAreaID>MC64920-40-A2X-REP-TEST</LogisticsAreaID> <ProductID>MCF-0001</ProductID> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <ProductionOrderID>35</ProductionOrderID> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <LogisticsAreaID>MC64920-40-A2X-REM-TEST</LogisticsAreaID> <ProductID>MCF-0001</ProductID> <ProcessType>2</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <BarcodeText>91MCF-0001]C193MC64920-40-A2X-REP-TEST</BarcodeText> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <BarcodeText>40235</BarcodeText> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <BarcodeText>91MCF-0001]C193MC64920-40-A2X-REM-TEST</BarcodeText> <ProcessType>2</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <LogisticsAreaID>MC64920-40-LEX-MEX</LogisticsAreaID> <ProductID>MCF-0001</ProductID> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> <LogisticsLayoutExecutionView> <LogisticsAreaID>MC64920-40-LEX-MEX</LogisticsAreaID> <ProductID>MCA-0001</ProductID> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <LogisticsAreaID>MC64920-40-A2X-REM-TEST</LogisticsAreaID> <ProductID>MCF-0001</ProductID> <ProcessType>2</ProcessType> </LogisticsLayoutExecutionView> <LogisticsLayoutExecutionView> <LogisticsAreaID>MC64920-40-LEX-MEX-REM</LogisticsAreaID> <ProductID>MCF-0001</ProductID> <ProcessType>2</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID schemeID="Token 1" schemeAgencyID="Token 2" schemeAgencySchemeAgencyID="Tok">Token 4</ID> <UUID schemeID="Token 5" schemeAgencyID="Token 6">12345678-90AB-CDEF-0123-456789ABCDEF</UUID> <ReferenceID schemeID="Token 7" schemeAgencyID="Token 8" schemeAgencySchemeAgencyID="Tok">Token 10</ReferenceID> <ReferenceUUID schemeID="Token 11" schemeAgencyID="Token 12">12345678-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <LogisticsLayoutExecutionView> <ProductionOrderID>354</ProductionOrderID> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> <LogisticsLayoutExecutionView> <ProductionOrderID>355</ProductionOrderID> <ProcessType>1</ProcessType> </LogisticsLayoutExecutionView> </n0:LogisticsLayoutExecutionViewBundleMaintainRequest_sync_V1>
<nm:LogisticsLayoutExecutionViewBundleMaintainResponse_sync_V1 xmlns:nm="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ASL:/1SAI/TAS0AF2157F5026885615B5:804"> <LogisticsLayoutExecutionViewResponse> <LogisticsLayoutExecutionViewLog> <SiteLogisticsRequestNodeID>00163E02870C1EE2B3D083596D886BB2</SiteLogisticsRequestNodeID> <SiteLogisticsRequestNode>ROOT</SiteLogisticsRequestNode> <LogisticsLayoutExecutionViewSeverityCode>S</LogisticsLayoutExecutionViewSeverityCode> <LogisticsLayoutExecutionViewNote>WareHouse request successfully created</LogisticsLayoutExecutionViewNote> </LogisticsLayoutExecutionViewLog> </LogisticsLayoutExecutionViewResponse> </nm:LogisticsLayoutExecutionViewBundleMaintainResponse_sync_V1>
Description | Maintain logistics layout execution |
Name | MaintainBundle_V1 |
Synchronous | yes |
Release Status | Released |
Request Replenishment Tasks, Removal Tasks for Internal Logistics.
The request message of the MANAGE_BUNDLE_V1 operation contains the Logistics Layout Execution View elements node that groups all possible selection parameters.
Here is the list of available Logistics Layout Execution View elements and their corresponding business contexts with the UI:
Logistics Layout Execution View
The following are the elements of this node:
Elements | Description |
---|---|
LogisticsAreaID | Unique identifier of the logistics area for requesting replenishment, removal tasks |
ProductID | Unique identifier of the product |
ProductionOrderID | Unique identifier of the production order for referencing purposes |
BarcodeText | Barcode text for material, logistics area |
ProcessType | Specifies the process type. For example, replenishment, removal |
Process Type
Code Value | Description |
---|---|
1 | Replenishment Requirement |
2 | Removal Requirement |