| Description | Manage Site Logistics Tasks |
| Name | ManageSiteLogisticsTaskIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Site Logistics Processing |
| Process Component Name | SiteLogisticsProcessing |
| 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 confirm Inbound Delivery, Outbound Delivery and Internal tasks for Site Logistics.
The web service Manage Site Logistics Task In enables you to connect external applications to your SAP Business By Design system and to carry out Source and Target confirmations like updating input and output materials for inbound delivery, outbound delivery and internal commonly known as Site Logistics Tasks.
The web service interface Manage Site Logistics Task In offers the operation Maintain_Bundle_V1.
The MaintainBundle operation is used to create or update one or more Site Logistics Tasks.
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, Logistics Unit ID, Quantity Unit Of Measure, Identified Stock ID 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'.
Quantities of Logistics Unit and Actual Confirmed Quantity should not be passed at the same time. This may lead to overwriting of the latter one over the first one. For example, in a line item, the open quantity is 1008 ea, whereas in a warehouse in logistics area L1, there are 10 pallets containing 100 ea each, and there are 8 ea lying separately. Now, in the A2X service, both the Logistics Unit Quantity, that is, 10 pallets, as well as the Actual Confirmed Quantity, that is, 8 ea should not be passed together, since 8 will overwrite the Logistic Unit quantity, and only 8 ea will be confirmed .
While performing the split action, the Material Output and Material Input nodes must be in the correct order for the split to happen. For example, when you are doing a split of line item 1 of Material Output, the next Material Output node should have the details of the newly split line item. So, the order that is to be followed is always 1, 1-1, 1-2, 2, 3, 4, 4-1, and so on. Please refer to the sample xmls used for this operation.
Actual Delivery Date can be changed only for the Inbound Task.
While changing the Actual Delivery Date, user should provide the actual delivery date in the format YYYY-MM-DDTHH:MM:SS.1234567Z .
Actual Delivery Date should always be in UTC Time with the required time zone.
For e.g. if the user wants to change the actual delivery of the Inbound Delivery to 18.05.2015 11:20 INDIA then the time should be in UTC i.e.
2015-05-18T05:50:00.0000000Z and the time zone should be INDIA.
<ActualDeliveryDate>
<StartDateTime timeZoneCode="INDIA">2015-05-18T05:50:00.0000000Z </StartDateTime>
<EndDateTime timeZoneCode="INDIA">2015-05-18T05:50:00.0000000Z </EndDateTime>
</ActualDeliveryDate>
Actual Execution On and Planned Start Date should be in format
YYYY-MM-DDTHH:MM:SS.1234567Z .
Actual Execution On and Planned Start Date should always be in UTC Time.
<ActualExecutionOn>2015-07-28T12:00:00.1234567Z</ActualExecutionOn>
<PlannedStartDate>2015-07-20T12:00:00.1234567Z</PlannedStartDate>
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 update and 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
Log Item attribute "LogItemSeverityCode" displays the response of the operation using following response code:
| Code | Response |
|---|---|
| S | Success |
| E | Error |
| I | Information |
| W | Warning |
| A | Abort |
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Show full documentation
Show full documentation
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>518</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163E03-390F-1EE2-AFA6-8279217E37BB</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>00163E03-390F-1EE2-AFA6-8279217E57BB</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163E03-390F-1EE2-AFA6-824F28DD77BB</OperationActivityUUID>
<MaterialInput>
<MaterialInputUUID>00163E03-390F-1EE2-AFA6-824F28DDB7BB</MaterialInputUUID>
<ProductID>MCF-0001</ProductID>
<SourceLogisticsAreaID></SourceLogisticsAreaID>
<ActualQuantity unitCode="EA">1</ActualQuantity>
</MaterialInput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>518</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163E03-390F-1EE2-AFA6-8279217E37BB</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>00163E03-390F-1EE2-AFA6-8279217E57BB</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163E03-390F-1EE2-AFA6-824F28DD77BB</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163E03-390F-1EE2-AFA6-824F28DDD7BB</MaterialOutputUUID>
<ProductID>MCF-0001</ProductID>
<TargetLogisticsAreaID>MC64920-50-10-02</TargetLogisticsAreaID>
<ActualQuantity unitCode="EA">2</ActualQuantity>
<IdentifiedStockID/>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>518</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163E03-390F-1EE2-AFA6-8279217E37BB</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>00163E03-390F-1EE2-AFA6-8279217E57BB</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163E03-390F-1EE2-AFA6-824F28DD77BB</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163E03-390F-1EE2-AFA6-824F28DDD7BB</MaterialOutputUUID>
<ProductID>MCF-0001</ProductID>
<TargetLogisticsAreaID>MC64920-50-10-80</TargetLogisticsAreaID>
<ActualQuantity unitCode="EA">8</ActualQuantity>
<IdentifiedStockID/>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>223</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163E02-9074-1ED2-AFDC-2CDC718D14D8</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>00163E02-9074-1ED2-AFDC-2CDC718D34D8</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163E02-9074-1ED2-AFDC-2CDC718A94D8</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163E02-9074-1ED2-AFDC-2CDC718B34D8</MaterialOutputUUID>
<ProductID>MCR-0015</ProductID>
<TargetLogisticsAreaID>MC64920-10</TargetLogisticsAreaID>
<ActualQuantity unitCode="EA">6</ActualQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
<MaterialOutput>
<ProductID>MCR-0015</ProductID>
<TargetLogisticsAreaID>MC64920-60</TargetLogisticsAreaID>
<ActualQuantity unitCode="EA">3</ActualQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
<MaterialOutput>
<MaterialOutputUUID/>
<ProductID>MCR-0015</ProductID>
<TargetLogisticsAreaID>MC64920-70</TargetLogisticsAreaID>
<ActualQuantity unitCode="EA">1</ActualQuantity>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>376</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163e02-9074-1ee2-b59b-22aec8fcd1e9</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>00163e02-9074-1ee2-b59b-22aec8fcf1e9</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163e02-9074-1ee2-b59b-21f51f5cd1e9</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163e02-9074-1ee2-b59b-21f51f5d31e9</MaterialOutputUUID>
<ProductID>MCF-0001-ISTP02</ProductID>
<TargetLogisticsAreaID>MC64920-10</TargetLogisticsAreaID>
<IdentifiedStockID>IS_MCF-0001-ISTP02</IdentifiedStockID>
<LogisticsPackageOutput>
<LogisticsUnitUUID>00163E02-9074-1EE2-B59B-22674BCA31E9</LogisticsUnitUUID>
<LogisticsUnitID>STD_PALLET</LogisticsUnitID>
<LogisticsUnitQuantity unitCode="PAL">1</LogisticsUnitQuantity>
</LogisticsPackageOutput>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>134</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163e06-0525-1ed4-bfa4-448e845e806b</SiteLogisticTaskUUID>
<ActualDeliveryDate>
<StartDateTime timeZoneCode="INDIA">2015-05-18T05:50:00.0000000Z</StartDateTime>
<EndDateTime timeZoneCode="INDIA">2015-05-18T05:50:00.0000000Z</EndDateTime>
</ActualDeliveryDate>
<ReferenceObject>
<ReferenceObjectUUID>00163e06-0525-1ed4-bfa4-448e845ea06b</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163e06-0525-1ed4-bfa4-448e845c406b</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163e06-0525-1ed4-bfa4-448e845ca06b</MaterialOutputUUID>
<ProductID>MCF-0001</ProductID>
<ActualQuantity unitCode="EA">10</ActualQuantity>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>532</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163e07-3d68-1ee5-829d-5bc4714074ff</SiteLogisticTaskUUID>
<ActualExecutionOn>2015-07-28T12:00:00.1234567Z</ActualExecutionOn>
<PlannedStartDate>2015-07-20T12:00:00.1234567Z</PlannedStartDate>
<ReferenceObject>
<ReferenceObjectUUID>00163e07-3d6a-1ee5-8de7-9dd1d1a9ea78</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163e07-3d6a-1ee5-8de7-9d918e128a78</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163e07-3d6a-1ee5-8de7-9d918e12ea78</MaterialOutputUUID>
<ProductID>MCF-0001-ST01</ProductID>
<ActualQuantity unitCode="EA">5</ActualQuantity>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<n0:SiteLogisticsTaskBundleMaintainRequest_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>
<SiteLogisticsTask>
<SiteLogisticTaskID>518</SiteLogisticTaskID>
<SiteLogisticTaskUUID>00163E03-390F-1EE2-AFA6-8279217E37BB</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>00163E03-390F-1EE2-AFA6-8279217E57BB</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>00163E03-390F-1EE2-AFA6-824F28DD77BB</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>00163E03-390F-1EE2-AFA6-824F28DDD7BB</MaterialOutputUUID>
<ProductID>MCF-0001</ProductID>
<TargetLogisticsAreaID>MC64920-50-10-80</TargetLogisticsAreaID>
<ActualQuantity unitCode="EA">2</ActualQuantity>
<IdentifiedStockID/>
<SerialNumber>
<SerialID>Z1</SerialID>
<SerialID>Z2</SerialID>
</SerialNumber>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</n0:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
| Description | Maintain site logistics tasks |
| Name | MaintainBundle_V1 |
| Synchronous | yes |
| Release Status | Released |
Confirm Inbound Delivery, Outbound Delivery and Internal tasks for Site Logistics.
The request message of the MAINTAIN_BUNDLE_V1 operation contains the Site Logistics Task elements node that groups all possible selection parameters.
Here is the list of available site logitics task elements and their corresponding business contexts with the UI:
SiteLogisticsTask
The following are the elements of this node:
| Elements | Description |
|---|---|
| SiteLogisticTaskID | Unique identifier of a site logistics task |
| SiteLogisticTaskUUID | Universally unique identifier of a logistics task for referencing purposes |
| ActualExecutionOn | Actual Execution On of task |
| ActualDeliveryDate | Actual Delivery Date of Inbound Delivery |
| PlannedStartDate | Planned Start Date of Task |
| ReferenceObject | The grouping of all components of a logistics task, which are relevant for the confirmation based on predefined rules. Its structure is explained in the ReferenceObject section |
ReferenceObject
The following are the elements of this node:
| Elements | Description |
|---|---|
| ReferenceObjectUUID | Universally unique identifier of a logistics task's reference object |
| OperationActivity | The grouping of all operations that can be carried out on a logistics task |
OperationActivity
The following are the elements of this node:
| Elements | Description |
|---|---|
| OperationActivityUUID | Universally unique identifier of an operation performed on a site logistics task |
| MaterialInput | This node contains the information that can be used to manage input materials needed to carry out on a site logistics task |
MaterialInput
The following are the elements of this node:
| Elements | Description |
|---|---|
| MaterialInputUUID | Universally unique identifier of an input material used to confirm a site logistics task. |
| ProductID | Product identifier of the input material |
| SourceLogisticsAreaID | The logistics area from where the material needs to be picked up to perform the activity |
| ActualQuantity | The quantity to be confirmed on the input material |
| IdentifiedStockID | The identified stock which is uniquely associated with the input material |
| ProductRequirementSpecificationID | The PRS ID which describes the specs of the product |
| InventoryRestrictedIndicator | This indicator when set to true, marks the particular input material for the given actual quantity as restricted. Normal task confirmations cannot be performed on a stock marked as restricted |
| LogisticsDeviationReasonCode | Deviation reason code contains information on why a deviation was reported by the user. The possible values for this attribute are: 1 - No Deviation 2 - Deviation 3 - Deviation Accepted 4 - Deviation Within Tolerances |
| SplitIndicator | This indicator when set to true splits the input material taking into consideration the actual quantity specified above |
| LogisticsPackageInputRequest | This node has information on the Logistics Unit used for this material. Its structure is explained in the LogisticsPackageInputRequest section |
| AutomaticIdentification | This node has barcode texts which can be used to input data for all attributes of an input material. The exceptions in which the user cannot use the barcode is while marking an inventory as Restricted or performing Split action. Please refer to the sample xmls to get better clarity |
LogisticsPackageInput
The following are the elements of this node:
| Elements | Description |
|---|---|
| LogisticsUnitUUID | Universally unique identifier of an logistics unit used to confirm a site logistics task quantity |
| LogisticsUnitID | Logistics unit identifier |
| LogisticsUnitQuantity | The quantity to be confirmed for tha particular logictics unit |
MaterialOutput
The following are the elements of this node:
| Elements | Description |
|---|---|
| MaterialOutputUUID | Universally unique identifier of an output material used to confirm a site logistics task. |
| ProductID | Product identifier of the output material |
| TargetLogisticsAreaID | The logistics area to which the material needs to be put to perform the activity |
| ActualQuantity | The quantity to be confirmed on the output material |
| IdentifiedStockID | The identified stock which is uniquely associated with the output material |
| ProductRequirementSpecificationID | The PRS ID which describes the specs of the product |
| InventoryRestrictedIndicator | This indicator when set to true, marks the particular output material for the given actual quantity as restricted. Normal task confirmations cannot be performed on a stock marked as restricted |
| LogisticsDeviationReasonCode | Deviation reason code contains information on why a deviation was reported by the user. The possible values for this attribute are: 1 - No Deviation 2 - Deviation 3 - Deviation Accepted 4 - Deviation Within Tolerances |
| SplitIndicator | This indicator when set to true splits the output material taking into consideration the actual quantity specified above |
| LogisticsPackageOutput | This node has information on the Logistics Unit used for this material. Its structure is explained in the LogisticsPackageOutput section |
| AutomaticIdentification | This node has barcode texts which can be used to input data for all attributes of an output material. The exceptions in which the user cannot use the barcode is while marking an inventory as Restricted or performing Split action. Please refer to the sample xmls to get better clarity |
| Serial Number | This node has information on the serial numbers used for this material. Its structure is explained in the Serial Number section |
Serial Number
It has table of SerialID as its element.