Symptom
When confirming an inbound task using the standard API service ManageSiteLogisticsTaskIn, the Restricted Indicator remains marked for the new split line item, even if it's set as false in the request payload.
Environment
SAP Business ByDesign
Reproducing the Issue
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
<soap:Header/>
<soap:Body>
<glob:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
<BasicMessageHeader/>
<SiteLogisticsTask>
<SiteLogisticTaskID>?</SiteLogisticTaskID>
<SiteLogisticTaskUUID>?</SiteLogisticTaskUUID>
<ReferenceObject>
<ReferenceObjectUUID>?</ReferenceObjectUUID>
<OperationActivity>
<OperationActivityUUID>?</OperationActivityUUID>
<MaterialOutput>
<MaterialOutputUUID>?</MaterialOutputUUID>
<ProductID>?</ProductID>
<TargetLogisticsAreaID>?</TargetLogisticsAreaID>
<ActualQuantity unitCode="?">?</ActualQuantity>
<IdentifiedStockID>?</IdentifiedStockID>
<InventoryRestrictedIndicator>true</InventoryRestrictedIndicator>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
<MaterialOutput>
<ProductID>?</ProductID>
<TargetLogisticsAreaID>?</TargetLogisticsAreaID>
<ActualQuantity unitCode="?">?</ActualQuantity>
<IdentifiedStockID>?</IdentifiedStockID>
<InventoryRestrictedIndicator>false</InventoryRestrictedIndicator>
</MaterialOutput>
</OperationActivity>
</ReferenceObject>
</SiteLogisticsTask>
</glob:SiteLogisticsTaskBundleMaintainRequest_sync_V1>
</soap:Body>
</soap:Envelope>
Cause
In the user interface (UI), when a task is split and the "Restricted" checkbox is checked, all split line items will also have the "Restricted" checkbox checked. The user can choose to keep or uncheck the box and proceed with confirming the task.
When the task is split using the provided API, it currently works the same way as the UI. The split task inherits the same attribute as the parent task. So, if the parent item is restricted, the split lines will also be restricted. However, the items are fulfilled directly and the user will not have the opportunity to change the attribute later.
Resolution
Our development team is aware of the missing functionality and has included it in the upcoming work schedule. It will be fixed in a future release. This improvement will enable users to choose which split lines should not be restricted. As a result, the "Restricted" checkbox will be unchecked for those particular lines. This enhancement will offer users greater flexibility and control when splitting tasks using the API.
Keywords
ManageSiteLogisticsTaskIn, InventoryRestrictedIndicator, Restricted, Task, Split. , KBA , AP-SLP-TSK , Site Logistics Task , Problem