| Description | Manage Production Lots |
| Name | ManageProductionLotsIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Production |
| Process Component Name | Production |
| 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 manage production lots.
The web service Manage Production Lot In enables you to connect external applications to your SAP Business By Design system and to carry out operations like adding or updating input and output materials for production, assigning new resources for certain activities, and updating the service utilization details.
The web service interface Manage Production Lot In offers the operation Maintain_Bundle_V1.
The MaintainBundle operation is used to create or update one or more production 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 ByDesign UI screen.
When the quantity is updated for a planned input material, the confirmation method must be specified as 'explicit' with code ‘02’.
While adding a new input material, the request xml must contain references for fields such as OperationActivityUUID, OperationUUID and ReportingPointUUID.
This is not a mandatory field, but if specified, this can determine which material was consumed for which activity.
In order to finish or restart a task of a production lot, the request xml may not contain other details such as adding or updating an input or output material or resource/service
utilization. The request xml must only contain details pertaining to the finish or restart task.
Request xml parameters for the finish task:
Processor Employee ID (optional parameter): This field specifies the employee who performed the finish task
Execution Date Time (mandatory parameter): This field gives information about the time when this task was finished.
Confirmation Completed Required Indicator (mandatory parameter): This field when set, marks the task as 'completed'.
Task UUID (mandatory parameter): The request must contain this field to determine the task that needs to be finished.
Request xml parameters for the restart task:
Processor Employee ID (optional parameter): This field specifies the employee who performed the restart task
Execution Date Time (optional parameter): This field gives information about the time when this task was restarted.
RestartOfTaskIndicator (mandatory parameter): This field when set, it restarts the task
Task UUID (mandatory parameter): The request must contain this field to determine the task that needs to be restarted.
In order to set responsible for a task of a production lot, The request xml should not contain other details such as adding or updating an input or output material or resource/service.
Request xml parameters for set responsible of a task:
Processor Employee ID (mandatory parameter): This field gives information about who has been assigned as responsible for a task.
AssignResponsibleIndicator (mandatory parameter): This field when set, it will assign responsible for the task
While updating reporting point related fields, request xml must only contain details pertaining to 'ReportingPoint' and 'ProductionTask'. It should not contain other details such as adding or updating an input or output material or resource/service utilization.
While updating confirmed scrap, confirmed quantity, and confirmation finished indicator at the reporting level, it is mandatory to pass ReportingPointUUID.
While adding a new resource or a service for an activity, please ensure that the same resource or service is not added multiple times. It is recommended that the user first performs a query on the task, determines which resources and services are already present, and then performs the create operation with a new resource or service.
Each resource can be consumed by only one service, that is, one resource cannot perform multiple services.
While updating Resource Utilization, ‘Resource UUID’ is mandatory. Provide "Resource Utilization UUID" as an input to "ResourceUUID" tag.
While creating/updating service utilization, providing a unit code for confirmed quantity is mandatory.
Confirmed quantity for service can be updated only when the value of ServiceConsumptionCalculationMethodCode is 2.
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.
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.
While updating the confirm quantity for input product in supply task use the "MaterialOutput" tag.
While updating for splitting input product, the confirm quantity can be updated using the "MaterialInput" tag
While updating the input product that is split, quantity can be confirmed using the "MaterialOutput" tag.
While split action is performed, Confirmation finished Indicator cannot be updated.
Confirmation Finished Indicator cannot be unchecked once it is set.
Adding <ActivityType>13</ActivityType> is mandatory for the splitting line item to determines the task type as supply task
"ProcessedOnDateTime" tag is used to update the Processed on date of Production Confirmation and posting date of the Journal Entry .If this tag is not filled, system will by default take the current date and time.
In case of a Standard Fault message, like the one below, the whole Request Message will be rejected. The user has to resend the request with correct xml data.
<nm:StandardFaultMessage xmlns:nm="http://sap.com/xi/AP/Common/Global" xmlns:prx="urn:sap.com:proxy:ASL:/1SAI/TAS5118194EC91140F9E030:804"> <standard> <faultText>Negative stock not permitted in logistics area MC64920-40-10-05, material HVS_INPUT_002</faultText> <faultUrl>AP_INVENTORY107</faultUrl> <faultDetail> <severity>E</severity> <text>Negative stock not permitted in logistics area MC64920-40-10-05, material HVS_INPUT_001</text> <id>AP_INVENTORY107</id> </faultDetail> <faultDetail> <severity>E</severity> <text>Negative stock not permitted in logistics area MC64920-40-10-05, material HVS_INPUT_002</text> <id>AP_INVENTORY107</id> </faultDetail> </standard> <addition/> </nm:StandardFaultMessage>
You can find general information about Web services, their structure and consumption in the Web Services documentation.
A simple example to update Output Material Quantity, Material Input Quantity and add a new Input Material for a single Production Task:
Request:
Show full documentation
Show full documentation
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>49</ProductionLotID>
<ProductionLotUUID>00163E02-870C-1EE1-B9F4-55CED93E8569</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1EE1-B9F4-55CED9424569</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-870C-1EE1-B9F4-55CED940A569</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">6</ConfirmedQuantity>
</MaterialOutput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163E02-870C-1EE1-B9F4-55CED9404569</MaterialInputUUID>
<ProductID>MCA-0009</ProductID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">15</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-40-10-05</SourceLogisticsAreaID>
</MaterialInput>
<MaterialInput ActionCode="01">
<ProductID>MCF-0001</ProductID>
<IdentifiedStockID>ZJN31</IdentifiedStockID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">20</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-50-30-01</SourceLogisticsAreaID>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
Response:
<nm:ProdLotBundleMaintainConfirmation_sync_V1 xmlns:nm="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ASL:/1SAI/TAE94D741CC599032FE5D7C:804"> <ProductionLotResponse> <ProductionLotID>49</ProductionLotID> <ProductionLotUUID>00163e02-870c-1ee1-b9f4-55ced93e8569</ProductionLotUUID> <ProductionLotLog> <NodeName>MATERIAL_INPUT</NodeName> <NodeID>00163E02870C1EE1B9F455CED9404569</NodeID> <SeverityCode>S</SeverityCode> <Note> Successfully created </Note> </ProductionLotLog> <ProductionLotLog> <NodeName>MATERIAL_INPUT</NodeName> <NodeID>00163E0286381EE281C1691B3CD2B0A6</NodeID> <SeverityCode>S</SeverityCode> <Note>Successfully created</Note> </ProductionLotLog> <ProductionLotLog> <NodeName>MATERIAL_INPUT_QUANTITY</NodeName> <NodeID>00163E0286381EE281C1691B3CD2B0A600163E0286381EE281C1691B3CD2B0A6</NodeID> <SeverityCode>S</SeverityCode> <Note>Successfully updated</Note> </ProductionLotLog> <ProductionLotLog> <NodeName>MATERIAL_INPUT_QUANTITY</NodeName> <NodeID>00163E02870C1EE1B9F455CED940456900163E02870C1EE1B9F455CED9404569</NodeID> <SeverityCode>S</SeverityCode> <Note>Successfully updated</Note> </ProductionLotLog> <ProductionLotLog> <NodeName>MATERIAL_OUTPUT_QUANTITY</NodeName> <NodeID>00163E02870C1EE1B9F455CED940A56900163E02870C1EE1B9F455CED940A569</NodeID> <SeverityCode>S</SeverityCode> <Note>Successfully updated</Note> </ProductionLotLog> </ProductionLotResponse> </nm:ProdLotBundleMaintainConfirmation_sync_V1>
Request: Request to update Material Output Quantity with wrong UUID
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>49</ProductionLotID>
<ProductionLotUUID>00163E02-870C-1EE1-B9F4-55CED93E8569</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1EE1-B9F4-55CED9424569</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-8701-1EE1-B9F4-55CED940A569</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">-8</ConfirmedQuantity>
</MaterialOutput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
Response with failure notification:
<nm:ProdLotBundleMaintainConfirmation_sync_V1 xmlns:nm="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ASL:/1SAI/TAE94D741CC599032FE5D7C:804"> <ProductionLotResponse> <ProductionLotID>49</ProductionLotID> <ProductionLotUUID>00163e02-870c-1ee1-b9f4-55ced93e8569</ProductionLotUUID> <ProductionLotLog> <NodeName>MATERIAL_OUTPUT_QUANTITY</NodeName> <NodeID>00163E0287011EE1B9F455CED940A56900163E0287011EE1B9F455CED940A569</NodeID> <SeverityCode>E</SeverityCode> <Note>Modification failed</Note> </ProductionLotLog> </ProductionLotResponse> </nm:ProdLotBundleMaintainConfirmation_sync_V1>
1. Create new Input Material (MCA-0010) under a Confirmation Group with Confirmation Method Code as Explicit, Quantity of 1 each, and Source Logistics Area MC64050-10
ConfirmQuantity is an optional field here. You can also create a new input material without specifying the quantity. Request xml must contain all other fields to add a new unplanned material.
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>31</ProductionLotID>
<ProductionLotUUID>00163E02-8660-1EE1-B597-3BB56C496A6D</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-8660-1EE1-B597-3BB56C4C6A6D</ConfirmationGroupUUID>
<MaterialInput ActionCode="01">
<ProductID>MCA-0010</ProductID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">1</ConfirmQuantity>
<SourceLogisticsAreaID>MC64050-10</SourceLogisticsAreaID>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
2. Update Material Output Quantity, Target Logistics Area and Material Input Back Flush Quantity and Source Logistics Area
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>71</ProductionLotID>
<ProductionLotUUID>00163E02-86FA-1EE1-BA86-6523352DAA5E</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-86FA-1EE1-BA86-65233530AA5E</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-86FA-1EE1-BA86-6523352FCA5E</MaterialOutputUUID>
<TargetLogisticsAreaID>MC64050-20</TargetLogisticsAreaID>
<ConfirmedQuantity unitCode="EA">4</ConfirmedQuantity>
</MaterialOutput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163E02-86FA-1EE1-BA86-6523352F8A5E</MaterialInputUUID>
<ProductID>MCA-0001</ProductID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">15</ConfirmQuantity>
<SourceLogisticsAreaID>MC64050-10</SourceLogisticsAreaID>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
3. Update ConfirmedQuantity, TargetLogisticsArea, SourceLogisticsArea for a Supply Task
Note that the ActivityType field with value 13 determines that the type of task is “supply”.
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>11</ProductionLotID>
<ProductionLotUUID>00163E02-870C-1EE1-B4CA-B3E4AF6C8E8E</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1EE1-B4CA-B3E4AF70AE8E</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-86FA-1ED1-BC80-3CDBB846C1BE</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">3</ConfirmedQuantity>
<TargetLogisticsAreaID>MC64920-50-10-01</TargetLogisticsAreaID>
</MaterialOutput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163E02-86FA-1ED1-BC80-3CDBB846E1BE</MaterialInputUUID>
<ActivityType>13</ActivityType>
<SourceLogisticsAreaID>MC64920-40-10-05</SourceLogisticsAreaID>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
4. Update Material Output Quantity, Material Input Quantity and add new Input Material (all in one Confirmation Group)
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>49</ProductionLotID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1EE1-B9F4-55CED9424569</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-870C-1EE1-B9F4-55CED940A569</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">6</ConfirmedQuantity>
</MaterialOutput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163E02-870C-1EE1-B9F4-55CED9404569</MaterialInputUUID>
<ProductID>MCA-0009</ProductID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">15</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-40-10-05</SourceLogisticsAreaID>
</MaterialInput>
<MaterialInput ActionCode="01">
<ProductID>MCF-0001</ProductID>
<IdentifiedStockID>ZJN31</IdentifiedStockID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">20</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-50-30-01</SourceLogisticsAreaID>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
5. Add new Resource for an Activity of an Operation
Note that the ConfirmDuration field must have the value in the format PTxHyMzS (x Hrs, y Mins, z Secs)
While creating a resource, the request must contain the resource ID with action code “01”. ConfirmedQuantity is a mandatory field for adding/updating a resource. ConfirmDuration for a resource is calculated based on the value of ConfirmedQuantity and must not be specified in the request. In the request below, we are adding a new resource CM-WAM101 for a certain activity with the value of ConfirmedQuantity as 4.
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>1221</ProductionLotID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1ED1-BE82-34186BBC1BCD</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-870C-1ED1-BE82-34186BAB7BCD</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">4</ConfirmedQuantity>
</MaterialOutput>
<Activity>
<ActivityUUID>00163E02-870C-1ED1-BE82-34186BAABBCD</ActivityUUID>
<ResourceUtilization ActionCode="01">
<ResourceID>CM-WAM101</ResourceID>
</ResourceUtilization>
</Activity>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
6. Update ConfirmDuration for Activity
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>12</ProductionLotID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e07-3d62-1ee4-8a8b-3cd0da82e12b</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163e07-3d62-1ee4-8a8b-3cd0da82012b</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">4</ConfirmedQuantity>
</MaterialOutput>
<Activity ActionCode="02">
<ActivityUUID>00163e07-3d62-1ee4-8a8b-3cd0da80812b</ActivityUUID>
<ConfirmDuration>PT4H45M0S</ConfirmDuration>
</Activity>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
7. Update ConfirmedDuration for ResourceUtilization
This request xml will update the confirmed duration of a resource with the below resource UUID to 4 hrs, 45 mins, 0 secs. ConfirmedQuantity and ResourceUUID fields are mandatory for updating a resource. Provide "Resource utilization UUID" as an input to ‘ResourceUUID’ tag.
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>1221</ProductionLotID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1ED1-BE82-34186BBC1BCD</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-870C-1ED1-BE82-34186BAB7BCD</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">4</ConfirmedQuantity>
</MaterialOutput>
<Activity>
<ActivityUUID>00163E02-870C-1ED1-BE82-34186BAABBCD</ActivityUUID>
<ResourceUtilization ActionCode="02">
<ResourceUUID>00163E02-8638-1EE1-BEE5-206DDFF1295E</ResourceUUID>
<ConfirmedDuration>PT4H45M0S</ConfirmedDuration>
</ResourceUtilization>
</Activity>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
8. Add new by-product (MCREP-0003) under MaterialOutput
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-8660-1EE1-B596-A9C0F33B4951</ConfirmationGroupUUID>
<MaterialOutput ActionCode="01">
<ProductID>MCREP-0001</ProductID>
<TargetLogisticsAreaID>MC64920-50-30-01</TargetLogisticsAreaID>
<ConfirmedQuantity unitCode="EA">2</ConfirmedQuantity>
</MaterialOutput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
9. Perform Finish action on ProductionTask 201 of ProductionLot 91
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>91</ProductionLotID>
<ProductionLotUUID>00163E02-86FA-1EE1-BCCD-62EB0A0140FE</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-86FA-1EE1-BCCD-630B641280FE</ConfirmationGroupUUID>
<ProductionTask>
<ProductionTaskID>201</ProductionTaskID>
<ProducionTaskUUID>00163E02-86FA-1EE1-BCCD-630B641300FE</ProducionTaskUUID>
<ProcessorEmployeeID>MC2101</ProcessorEmployeeID>
<ExecutionDateTime>2012-08-28T12:00:00.1234567Z</ExecutionDateTime>
<ConfirmationCompletedRequiredIndicator>true</ConfirmationCompletedRequiredIndicator>
</ProductionTask>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
10. Create new Service with ID MCPRDCE001 for Resource CM_ISTP01_MULTI with ConfirmedQuantity 2
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>109</ProductionLotID>
<ProductionLotUUID>00163E02-8638-1ED1-BDFB-E1EEF9BD206D</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-8638-1ED1-BDFB-E1EEF9C0206D</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-8638-1ED1-BDFB-E1EEF9BF406D</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">1</ConfirmedQuantity>
</MaterialOutput>
<Activity>
<ActivityUUID>00163E02-8638-1ED1-BDFB-E1EEF9BE806D</ActivityUUID>
<Service ActionCode="01">
<Service_ID>MCPRDCE001</Service_ID>
<Resource_ID>CM_ISTP01_MULTI</Resource_ID>
<Confirmed_Quantity unitCode=”HUR”>1</Confirmed_Quantity>
<ServiceConsumptionCalculationMethodCode>2</ServiceConsumptionCalculationMethodCode>
</Service>
</Activity>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
11. Update ConfirmedQuantity field for Service MCPRDCE001 to 2
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>109</ProductionLotID>
<ProductionLotUUID>00163E02-8638-1ED1-BDFB-E1EEF9BD206D</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-8638-1ED1-BDFB-E1EEF9C0206D</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-8638-1ED1-BDFB-E1EEF9BF406D</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">1</ConfirmedQuantity>
</MaterialOutput>
<Activity>
<ActivityUUID>00163E02-8638-1ED1-BDFB-E1EEF9BDC06D</ActivityUUID>
<Service ActionCode="02">
<ServiceUUID>00163E02-8638-1ED1-BDFB-E1EEF9BE606D</ServiceUUID>
<Service_ID>MCPRDCE001</Service_ID>
<Resource_ID>CM-WMR001</Resource_ID>
<Confirmed_Quantity unitCode"HUR">1</Confirmed_Quantity>
<ServiceConsumptionCalculationMethodCode>2</ServiceConsumptionCalculationMethodCode>
</Service>
</Activity>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
12. Split Material Output Only
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>41</ProductionLotID>
<ProductionLotUUID>00163e07-3d66-1ed4-8b88-a35ba2f6b4dc</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e07-3d66-1ed4-8b88-a35ba2f9b4dc</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163e07-3d66-1ed4-8b88-a58daa1b94dc</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">10</ConfirmedQuantity>
<TargetLogisticsAreaID>MC64050-20</TargetLogisticsAreaID>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID/>
<ConfirmedQuantity unitCode="EA">20</ConfirmedQuantity>
<TargetLogisticsAreaID>MC64050-20</TargetLogisticsAreaID>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
13. Split Material Input and Material Output both
Note that in this case, Material Output needs to be split first.
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>52</ProductionLotID>
<ProductionLotUUID>00163e07-3d62-1ed4-8bb4-91b2498f9f15</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e07-3d62-1ed4-8bb4-91b249929f15</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163e07-3d62-1ed4-8bb4-91b24991bf15</MaterialOutputUUID>
<TargetLogisticsAreaID>MC64050-20</TargetLogisticsAreaID>
<ConfirmedQuantity unitCode="EA">10</ConfirmedQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID/>
<TargetLogisticsAreaID>MC64920-40-10-01</TargetLogisticsAreaID>
<ConfirmedQuantity unitCode="EA">20</ConfirmedQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialOutput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163e07-3d62-1ed4-8bb4-91b249915f15</MaterialInputUUID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">10</ConfirmQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
<MaterialInput ActionCode="02">
<MaterialInputUUID/>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">20</ConfirmQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163e07-3d62-1ed4-8bb4-91b249917f15</MaterialInputUUID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">10</ConfirmQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
<MaterialInput ActionCode="02">
<MaterialInputUUID/>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">20</ConfirmQuantity>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
14. Perform Restart action on ProductionTask 593 of ProductionLot 81
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>81</ProductionLotID>
<ProductionLotUUID>00163E07-3D66-1EE5-85B3-7620DEED6EB7</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E07-3D66-1EE5-85B3-7620DEEF8EB7</ConfirmationGroupUUID>
<ProductionTask>
<ProductionTaskID>593</ProductionTaskID>
<ProducionTaskUUID>00163E07-3D66-1EE5-85B3-7620DEF00EB7</ProducionTaskUUID>
<ProcessorEmployeeID>MC2101</ProcessorEmployeeID>
<ExecutionDateTime>2015-06-18T12:00:00.1234567Z</ExecutionDateTime>
<RestartOfTaskIndicator>true</RestartOfTaskIndicator>
</ProductionTask>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
15. Update confirmation finished indicator at reporting point
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>81</ProductionLotID>
<ProductionLotUUID>00163E07-3D66-1EE5-85B3-7620DEED6EB7</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E07-3D66-1EE5-85B3-7620DEEF8EB7</ConfirmationGroupUUID>
<ProductionTask>
<ProductionTaskID>593</ProductionTaskID>
<ProducionTaskUUID>00163E07-3D66-1EE5-85B3-7620DEF00EB7</ProducionTaskUUID>
</ProductionTask>
<ReportingPoint>
<ReportingPointUUID>00163E07-3D66-1EE5-85B3-7620DEEF4EB7</ReportingPointUUID>
<ConfirmationFinishedIndicator>false</ConfirmationFinishedIndicator>
</ReportingPoint>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
16. Update confirmed scrap at reporting point
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>81</ProductionLotID>
<ProductionLotUUID>00163E07-3D66-1EE5-85B3-7620DEED6EB7</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E07-3D66-1EE5-85B3-7620DEEF8EB7</ConfirmationGroupUUID>
<ProductionTask>
<ProductionTaskID>593</ProductionTaskID>
<ProducionTaskUUID>00163E07-3D66-1EE5-85B3-7620DEF00EB7</ProducionTaskUUID>
</ProductionTask>
<ReportingPoint>
<ReportingPointUUID>00163E07-3D66-1EE5-85B3-7620DEEF4EB7</ReportingPointUUID>
<ConfirmedScrap unitCode="EA">2</ConfirmedScrap>
</ReportingPoint>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
17. Update confirmed quantity at reporting point
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>81</ProductionLotID>
<ProductionLotUUID>00163E07-3D66-1EE5-85B3-7620DEED6EB7</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E07-3D66-1EE5-85B3-7620DEEF8EB7</ConfirmationGroupUUID>
<ProductionTask>
<ProductionTaskID>593</ProductionTaskID>
<ProducionTaskUUID>00163E07-3D66-1EE5-85B3-7620DEF00EB7</ProducionTaskUUID>
</ProductionTask>
<ReportingPoint>
<ReportingPointUUID>00163E07-3D66-1EE5-85B3-7620DEEF4EB7</ReportingPointUUID>
<ConfirmedQuantity unitCode="EA">2</ConfirmedQuantity>
</ReportingPoint>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
18. Set responsible for a task
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>81</ProductionLotID>
<ProductionLotUUID>00163E07-3D66-1EE5-85B3-7620DEED6EB7</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E07-3D66-1EE5-85B3-7620DEEF8EB7</ConfirmationGroupUUID>
<ProductionTask>
<ProductionTaskID>593</ProductionTaskID>
<ProducionTaskUUID>00163E07-3D66-1EE5-85B3-7620DEF00EB7</ProducionTaskUUID>
<ProcessorEmployeeID>MC2101</ProcessorEmployeeID>
<AssignResponsibleIndicator>true</AssignResponsibleIndicator>
</ProductionTask>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
19. Update Material Output Quantity with Processed On Date and Time
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>71</ProductionLotID>
<ProductionLotUUID>00163E02-86FA-1EE1-BA86-6523352DAA5E</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-86FA-1EE1-BA86-65233530AA5E</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-86FA-1EE1-BA86-6523352FCA5E</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">4</ConfirmedQuantity>
</MaterialOutput>
<ProductionTask>
<ProductionTaskID>3884</ProductionTaskID>
<ProducionTaskUUID>00163E07-3D66-1ED6-9EFD-A497696A904C</ProducionTaskUUID>
<ProcessedOnDateTime>2016-09-13T12:00:00.1234567Z</ProcessedOnDateTime>
</ProductionTask>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
20. Split Material Input in supply task and confirm quantity
<n0:ProductionLotsBundleMaintainRequest_sync_V1xmlns:n0=" http://sap.com/xi/SAPGlobal20/Global ">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>12</ProductionLotID>
<ProductionLotUUID>00163e61-3683-1ee9-87ab-286507ed8c9</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e61-3683-1ee9-87ab-286507f20c99</ConfirmationGroupUUID>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163e61-3683-1ee9-87ab-286507ee8c99</MaterialInputUUID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<SourceLogisticsAreaID>MC64920-50-10-04</SourceLogisticsAreaID>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
<MaterialInput ActionCode="02">
<MaterialInputUUID/>
<ActivityType>13</ActivityType>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">1</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-50-10-05</SourceLogisticsAreaID>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
<MaterialInput ActionCode="02">
<MaterialInputUUID>00163e61-3683-1ee9-87ab-286507eeac99</MaterialInputUUID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<SourceLogisticsAreaID>MC64920-50-10-04</SourceLogisticsAreaID>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
<MaterialInput ActionCode="02">
<MaterialInputUUID/>
<ActivityType>13</ActivityType>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">2</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-50-10-05</SourceLogisticsAreaID>
<SplitIndicator>true</SplitIndicator>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
21. Confirmation Finished Indicator for Supply Task
<ProductionLot>
<ProductionLotID>1154</ProductionLotID>
<ProductionLotUUID>00163e5f-4d76-1ee9-8cea-4a34d708ee12</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e5f-4d76-1ee9-8cea-4a5a66e2ce12</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163e5f-4d76-1ee9-8cea-4a34d70a6e12</MaterialOutputUUID>
<ConfirmedQuantity unitCode="EA">3</ConfirmedQuantity>
<TargetLogisticsAreaID>MC64920-10</TargetLogisticsAreaID>
<ConfirmationFinished>true</ConfirmationFinished>
</MaterialOutput>
</ConfirmationGroup>
</ProductionLot>
22. Confirmation Finished Indicator for Make task while adding new product in Material Input
<ProductionLot>
<ProductionLotID>1137</ProductionLotID>
<ProductionLotUUID>00163e5f-4da7-1ed9-8db3-535b28547daa</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e5f-4da7-1ed9-8db3-535b285afdaa</ConfirmationGroupUUID>
<MaterialInput ActionCode="01">
<ProductID>MCR-0004</ProductID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">20</ConfirmQuantity>
<SourceLogisticsAreaID>MC64920-40-10-68</SourceLogisticsAreaID>
<ConfirmationFinished>true</ConfirmationFinished>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
23. Confirmation Finished Indicator for Make task while adding new By-product in Material Output
<ProductionLot>
<ProductionLotID>1137</ProductionLotID>
<ProductionLotUUID>00163e5f-4da7-1ed9-8db3-535b28547daa</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163e5f-4da7-1ed9-8db3-535b285afdaa</ConfirmationGroupUUID>
<MaterialOutput ActionCode="01">
<ProductID>MCR-0005</ProductID>
<TargetLogisticsAreaID>MC64050-30</TargetLogisticsAreaID>
<ConfirmedQuantity unitCode="EA">2</ConfirmedQuantity>
<ConfirmationFinished>true</ConfirmationFinished>
</MaterialOutput>
</ConfirmationGroup>
</ProductionLot>
24. Confirmation Finished Indicator for Make task while Updating Confirmed Quantity
<ProductionLot> <ProductionLotID>1194</ProductionLotID> <ProductionLotUUID>00163e5f-4d8f-1ed9-8fd4-037dc47f778e</ProductionLotUUID> <ConfirmationGroup> <ConfirmationGroupUUID>00163e5f-4d8f-1ed9-8fd4-037dc482778e</ConfirmationGroupUUID> <MaterialOutput ActionCode="02"> <MaterialOutputUUID>00163e5f-4d8f-1ed9-8fd4-037dc481978e</MaterialOutputUUID> <TargetLogisticsAreaID>MC64050-40-01-01</TargetLogisticsAreaID> <ConfirmedQuantity unitCode="EA">5 </ConfirmedQuantity> </MaterialOutput> <MaterialInput ActionCode="01"> <ProductID>MCR-0004</ProductID> <ConfirmationMethodCode>2</ConfirmationMethodCode> <ConfirmQuantity unitCode="EA">20 </ConfirmQuantity> <SourceLogisticsAreaID>MC64920-40-10-68</SourceLogisticsAreaID> <ConfirmationFinished>true</ConfirmationFinished> </MaterialInput> <MaterialInput ActionCode="01"> <ProductID>MCR-0005</ProductID> <ConfirmationMethodCode>2</ConfirmationMethodCode> <ConfirmQuantity unitCode="EA">40 </ConfirmQuantity> <SourceLogisticsAreaID>MC64920-40-10-84</SourceLogisticsAreaID> <ConfirmationFinished>true</ConfirmationFinished> </MaterialInput> </ConfirmationGroup> </ProductionLot>
| Description | Maintain production lots |
| Name | MaintainBundle_V1 |
| Synchronous | yes |
| Release Status | Released |
To create or update one or more production tasks.
The request message of the MAINTAIN_BUNDLE_V1 operation contains the ProductionLotSelectionByElements node that groups all possible selection parameters.
The request message contains the ProductionLotSelectionByElements node that groups all possible selection parameters.
Below is the list of available production lot elements and their corresponding business contexts with the UI:
Production Lot
After a certain quantity of materials is produced as a group with reference to an order, the production lot collects all the actual information during the production process that is described by operations and activities.
The ProductionLot node element maintains this information.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ProductionLotId | Unique identifier of a production lot |
| ProductionLotUUID | Universally unique identifier of a logistics lot for referencing purposes |
| ConfirmationGroup | The grouping of all components of a logistics lot, which are relevant for the confirmation based on predefined rules. Its structure is explained in the Confirmation Group section. |
Confirmation Group
The ConfirmationGroup node can be used to maintain the grouping of all components of a logistics lot, which are relevant for the confirmation based on predefined rules.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ConfirmationGroupUUID | Universally unique identifier of the confirmation, each specific to one production task |
| ProductionTask | A task in production that a processor executes at a specific time at a predefined production step in a production process. Its structure is explained in the Production Task section. |
| Activity | A part of an operation in which a material was produced, packed or transported. This includes the actual duration taken to complete the current activity. Its structure is explained in the Activity section. |
| MaterialInput | Input materials needed to create a product. Its structure is defined in the Material Input section.) |
| MaterialOutput | Output product. Its structure is defined in the Material Output section.) |
| ReportingPoint | END point of production. Its structure is defined in the Reporting Point section.) |
Production Task
The ProductionTask node can be used to represent a task in production that a processor executes at a specific time in a predefined production step in a production process.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ProductionTaskID | An identifier for production task |
| ProductionTaskUUID | A globally unique identifier for a production task for referencing purposes |
| OperationTypeCode | A coded representation of the operation type of the logistics task. Its default value is taken from the referenced production lot operation. If a production task references more than one operation, the type that directly precedes the reporting point is related to the operation. |
| OperationActivityTypeCode | A coded representation of the OperationActivity type of the production task. Its default value is taken from the referenced production lot operation activity for the production task. |
| ResourceUUID | An identifier for the resource of a logistics task. For the production task, the default value is taken from the main operation resource of the production order referenced by the logistics task. If a production task references more than one operation, the resource that directly precedes the reporting point is related to the operation. |
| ProcessorEmployeeID | The employee who will perform the Finish or restart task |
| ExecutionDateTime | The execution date and time stamp of the production task |
| ConfirmationCompletedRequiredIndicator | The ConfirmCompletedIndicator field |
| RestartOfTaskIndicator | An indicator field which when set to true will restart a finished task |
| AssignResponsibleIndicator | An indicator field which when set to true will assign responsible for a task |
Activity
The Activity node can be used to maintain a part of an operation in which a material was produced, packed or transported, and includes the actual duration taken to complete the current activity.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ActivityID | Unique identifier of the OperationActivity. It is unique within the operation. |
| ActivityUUID | Universally unique identifier of the OperationActivity for referencing purposes |
| TypeCode | Specifies the type of the operation activity, for example, setup, make, single, or move |
| CategoryCode | Describes the main usage of this operation activity, for example, produce, teardown, single move, or collective move |
| ConfirmationCompletedIndicator | Indicates whether all confirmations have been entered for the OperationActivityStep |
| ResourceUtilization | The resource used in order to fulfill an operation activity. Its structure is explained in the Resource Utilization section. |
| Service | The service product that was used to perform an operation activity. Its structure is explained in the Service section. |
Resource Utilization
The ResourceUtilization node can be used to represent the resource used to fulfill an operation activity.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ResourceID | Unique identifier of the resource to be confirmed at the ResourceUtilization |
| ConfirmedDuration | Time period reported at the ResourceUtilization |
| ConfirmationFinished | Indicates that the ResourceUtilization will not be confirmed any more |
Service
The Service node can be used to maintain the service product that was used to perform an operation activity.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ServiceID | Unique identifier of the service being done as part of an activity |
| ResourceID | Unique identifier of the resource being used for the service |
| ConfirmedQuantity | Quantity to be confirmed |
| ConfirmationFinished | Indicates if confirmation is over |
Material Input
The MaterialInput node can be used to manage input materials needed to create a product.
The following are the elements of this node:
| Elements | Description |
|---|---|
| MaterialInputUUID | Universally unique identifier for a material input for referencing purposes. |
| ProductID | Unique identifier of the product |
| ProductUUID | Universally unique identifier of the product for referencing purposes |
| SupplyPlanningArea | An identifier for an area in planning for which the punctual availability of products is guaranteed |
| IdentifiedStockID | Unique identifier of an identified stock |
| ActivityID | Unique identifier of the OperationActivity. It is unique within the operation. |
| ActivityType | Specifies the type of the operation activity. For example, setup, make, or single move |
| ActivityUUID | Universally unique identifier of the OperationActivity for referencing purposes |
| ConfirmationFinished | Indicates whether all confirmations have been entered for the material input |
| ConfirmQuantity | Quantity to be confirmed at the material input |
| OperationID | Unique identifier of the operation at which an unplanned material input entered a process |
| SourceLogisticsAreaID | Unique identifier of the logistics area to be confirmed at this material input |
| SiteID | Unique identifier of the site |
| PlannedIndicator | Indicates whether the material input has been planned in the production order |
| SplitIndicator | This indicator when set to true splits the input material taking into consideration the actual quantity specified |
Activity Type
| Code Value | Description |
|---|---|
| 1 | Set Up |
| 10 | Final Inspection |
| 11 | Move All |
| 12 | Move Per Item |
| 13 | Supply |
| 2 | Produce |
| 3 | Tear Down |
| 4 | Move per Source and Destination |
| 5 | Move per Destination |
| 6 | Move per Source |
Material Output
The MaterialOutput node can be used to maintain the output product of the production process.
The following are the elements of this node:
| Elements | Description |
|---|---|
| MaterialOutputUUID | Universally unique identifier for a material output for referencing purposes |
| ProductID | Unique identifier of the product |
| ProductUUID | Universally unique identifier of the product for referencing purposes |
| SupplyPlanningArea | An identifier for an area in planning for which the punctual availability of products is guaranteed |
| IdentifiedStockID | Unique identifier of an identified stock |
| ActivityID | Unique identifier of the OperationActivity. It is unique within the operation. |
| ActivityType | Specifies the type of the operation activity, for example, setup, make, or single move |
| ActivityUUID | Universally unique identifier of the OperationActivity for referencing purposes |
| TargetLogisticsAreaID | Unique identifier of the logistics area to be confirmed at the material output |
| ConfirmationFinished | Indicates whether all confirmations have been entered for the material output |
| PlannedIndicator | Indicates whether the material output has been planned in the site logistics order or the site logistics request |
| OperationID | Unique identifier of the operation involved in the material output |
| SiteID | Unique identifier of the site |
| SplitIndicator | This indicator when set to true splits the output material taking into consideration the actual quantity specified |
Reporting Point
The Reporting point node can be used to maintain the scrap quantity , confirmation status and confirmed quantity of both output and input product.
The following are the elements of this node:
| Elements | Description |
|---|---|
| ReportingPointUUID | Universally unique identifier for a reporting point for referencing purposes |
| ConfirmedQuantity | An Quantity field which carries confirm quantity |
| ConfirmedScrap | An Quantity field which carries confirm scrap quantity |
| ConfirmationFinishedIndicator | An indicator field when set to true will set the task status to confirmation finished and when set to false will set the task status to in process |
General Rules for Using this Web Service
Action code is a coded representation of an instruction to the recipient of a message, telling it how to process a transmitted node/element. It is modeled as an attribute (attribute name: ActionCode) in every structure element of the message payload.
List of available action codes:
| ActionCode | Description |
|---|---|
| 01 | Create |
| 02 | Change |
| 03 | Delete |
| 04 | Save |
| 05 | Remove |
| 06 | No action (Check) |
The action codes 01 (Create), 02 (Change), 03 (Delete), and 06 (No Action) model strict semantics that lead to errors at the recipient if the nodes/elements corresponding to the actions requested by the sender exist (01) or do not exist (02, 03, 06) at the recipient. Using strict semantics, therefore, requires that the sender has and uses information about the messages it has already sent.
The action codes 04 (Save) and 05 (Remove) model soft semantics that do not lead to errors if the respective nodes/elements do not exist at the recipient. These soft semantics, therefore, do not require that the sender has and uses information about the messages it has already sent.
Note: If no action code is provided for a respective node, the system defaults it value to 04.
For certain nodes with cardinality from 0 - *, the UUID is used as an identifier for each of the respective nodes. UUID will be generated when the operation type is ‘create’. UUIDs must be passed to the relevant fields in the request structure for an update operation.
Maintain bundle operation is 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.
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.
Request xml to create a new Input Material (MCA-0010) under a Confirmation Group with Confirmation Method Code as Explicit, Quantity of 1 each, and Source Logistics Area MC64050-10
ConfirmQuantity is an optional field here. You can also create a new input material without specifying the quantity. Request xml must contain all other fields to add a new unplanned material.
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>31</ProductionLotID>
<ProductionLotUUID>00163E02-8660-1EE1-B597-3BB56C496A6D</ProductionLotUUID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-8660-1EE1-B597-3BB56C4C6A6D</ConfirmationGroupUUID>
<MaterialInput ActionCode="01">
<ProductID>MCA-0010</ProductID>
<ConfirmationMethodCode>2</ConfirmationMethodCode>
<ConfirmQuantity unitCode="EA">1</ConfirmQuantity>
<SourceLogisticsAreaID>MC64050-10</SourceLogisticsAreaID>
</MaterialInput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>
When the quantity is updated for a planned input material, the confirmation method must be specified as 'explicit' with code ‘02’.
While adding a new input material, the request xml must contain references for fields such as OperationActivityUUID, OperationUUID and ReportingPointUUID.
This is not a mandatory field, but if specified, this can determine which material was consumed for which activity.
In order to finish or restart a task of a production lot, the request xml may not contain other details such as adding or updating an input or output material or resource/service utilization. The request xml must only contain details pertaining to the Finish or restart task.
Request xml parameters for the Finish task:
Processor Employee ID (optional parameter): This field specifies the employee who performed the Finish task.
Execution Date Time (mandatory parameter): This field gives information about the time when this task was finished.
Confirmation Completed Required Indicator (mandatory parameter): This field when set marks the task as 'completed'.
Task UUID (mandatory parameter): The request must contain this field to determine the task that needs to be finished.
Request xml parameters for the restart task:
Processor Employee ID (optional parameter): This field specifies the employee who performed the restart task
Execution Date Time (optional parameter): This field gives information about the time when this task was restarted.
RestartOfTaskIndicator (mandatory parameter): This field when set, it restarts the task
Task UUID (mandatory parameter): The request must contain this field to determine the task that needs to be restarted.
In order to set responsible for a task of a production lot, The request xml should not contain other details such as adding or updating an input or output material or resource/service.
Request xml parameters for set responsible of a task:
Processor Employee ID (mandatory parameter): This field gives information about who has been assigned as responsible for a task.
AssignResponsibleIndicator (mandatory parameter): This field when set, it will assign responsible for the task
While updating reporting point related fields, request xml must only contain details pertaining to 'ReportingPoint' and 'ProductionTask'. It should not contain other details such as adding or updating an input or output material or resource/service utilization.
While updating confirmed scrap, confirmed quantity, and confirmation finished indicator at the reporting level, it is mandatory to pass ReportingPointUUID.
While adding a new resource or a service for an activity, please ensure that the same resource or service is not added multiple times. It is recommended that the user first performs a query on the task, determines which resources and services are already present, and then performs the create operation with a new resource or service.
Each resource can be consumed by only one service, that is, one resource cannot perform multiple services.
While creating/updating service utilization, providing a unit code for confirmed quantity is mandatory.
"ProcessedOnDateTime" tag is used to update the Processed on date of Production Confirmation and posting date of the Journal Entry. If this tag is not filled, system will by default take the current date and time.
Confirmed quantity for service can be updated only when the value of ServiceConsumptionCalculationMethodCode is 2.
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.
This interface supports extensibility
Example
The following XML tag could be used to update an extension field which is added in production lot material output.
This extension field would also (return) as part of the response to the query operation.
Request
<n0:ProductionLotsBundleMaintainRequest_sync_V1 xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<ProductionLot>
<ProductionLotID>1221</ProductionLotID>
<ConfirmationGroup>
<ConfirmationGroupUUID>00163E02-870C-1ED1-BE82-34186BBC1BCD</ConfirmationGroupUUID>
<MaterialOutput ActionCode="02">
<MaterialOutputUUID>00163E02-870C-1ED1-BE82-34186BAB7BCD</MaterialOutputUUID>
<n1:EXT12345600163E0290741EE292A110819C698C78 xmlns:n1="http://sap.com/xi/AP/CustomerExtension/BYD/ZZZZZ">ABC</n1:EXT12345600163E0290741EE292A110819C698C78>
</MaterialOutput>
</ConfirmationGroup>
</ProductionLot>
</n0:ProductionLotsBundleMaintainRequest_sync_V1>