| Description | Create Goods and Activity Confirmations for Consignment Adjustment |
| Name | GoodsAndActivityConfirmationConsignmentAdjustmentIn |
| Namespace | http://sap.com/xi/AP/LogisticsExecution/Global |
| Process Component Description | Inventory Processing |
| Process Component Name | InventoryProcessing |
| 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 |
The service interface II_APGACFM_CONSIGN_ADJUSTMT_IN used to adjust consignment stock.
This web service is used to adjust consignment stock available at a particular site.
It has a single DO_CONSIGNMENT_ADJUSTMENT operation.
The DO_CONSIGNMENT_ADJUSTMENT operation is used to create one or more consignment adjustment postings. It will create one or more GoodsAndActivityConfirmation documents.
Consignment should be scoped in the system.
Request node elements with cardinality > 1 contain an object node sender technical identifier to relate response message elements and log items to corresponding node elements in the request message.
The object node sender technical identifiers are provided as ObjectNodeSenderTechnicalID in request message types and referred to as ReferenceObjectNodeSenderTechnicalID in corresponding response message types.
If the object node sender technical ID is initial, the object node sender technical ID of the parent node element in the request is returned as the reference object node sender technical ID. If the object node sender technical IDs of all parent node elements are initial, the reference object node sender technical ID is returned as initial as well.
Note: The values specified in the ObjectNodeSenderTechnicalID are transient values that establish the correspondence between elements for only a single call. The web service consumer is not required to specify them or to use the same values for different calls. In addition, the service provider does not interpret these values at all, but returns them to the web service consumer instead in the ReferenceObjectNodeSenderTechnicalID elements.
Note: The ObjectNodeSenderTechnicalID is also used to identify failed business document modifications in a mass operation.
Many external applications consuming web services have special requirements and restrictions regarding the format of WSDLs. Some external applications require service definition WSDLs describing the web service signature. This is normally sufficient for the creation of static client-side proxies. Other external applications, normally those that do not create static client-side proxies, require binding WSDLs including the endpoint definition and authentication policy information.
In both cases, it may be the case that the external application imposes special restrictions on the structure or the size of WSDLs.
Microsoft InfoPath requires binding WSDLs and considers elements with the attribute "minOccurs=0" as "mandatory". However "minOccurs=0" means "optional" in SAP web services. In order to circumvent this problem, the WSDL must be saved locally and an additional attribute "nillable=true" must be added to make a query parameter optional for Microsoft InfoPath.
For very small clients such as mobile devices, the size of the WSDL itself may become a problem. In most cases the client only requires a very small part of the signature, but due to the complexity of the WSDL they may end up with long runtime during serialization of the request or deserialization of the response. In order to circumvent this problem, the WSDL must be saved locally and the optional parts of the signature have to be removed before the WSDL is imported or static client-side proxies are generated.
External applications have to take into account that web service request and response message types can be enhanced with additional elements and attributes. Enhancements can be created by SAP, SAP partners, and key users. Enhancements of request message types are always optional elements or attributes. The SAP system does not require the external application to provide values in the request. Enhancements of response message types can contain mandatory elements or attributes. The external application must be able to process the extended response successfully.
XML element and attribute names are always stable. Technical definitions of data types can be enhanced in a compatible way. This may result in changed data type names. External applications can rely on XML element names and attribute names, but should not rely on data type names.
Note: You can download the WSDL file for any web service here:
• Application and User Management work center -> Input Output Management -> Communication Arrangement.
• User Management work center -> Service Explorer view.
You can find the documentation of the global data types in the SAP Community Network: Go to http://scn.sap.com/docs/DOC-17516 and click View Document.
You can find general information about Web services, their structure and consumption in the Web Services documentation. Please open the Web Services document in a new window.
| Description | Create goods and activity confirmations for consignment adjustment |
| Name | DoConsignmentAdjustment |
| Synchronous | yes |
| Release Status | Released |
Operation to create one or more Goods And Activity Confirmation for Consignment Adjustment using imported structured data. Input information like FillUp Site ID, Custodian ID, Material ID,ConsignmentAdjustmentTypeCode will be provided and on successful creation GoodsAndActivityConfirmation ID will be returned as output.
The request message of the operation contains information that is used for checking the GoodsAndActivityConfirmation documents, and response message contains the ID of the created documents.
Consignment should be scoped in the system.
The request message GoodsAndActivityConfirmationConsignmentAdjustmentRequest contains a GoodsandActivityConfirmationConsignmentAdjustment node element as well as InventoryChangeItemConsignmentAdjustment node element. It also contains Basic Message Header.
This is the root node for each Goods And Activity Confirmation being passed in the request. The GoodsandActivityConfirmationConsignmentAdjustment node can occur multiple times in the request message; this means that multiple consignment adjustments (Goods And Activity Confirmations) can be created through a single web service request. Following are the elements of this node:-
| Element | Description |
|---|---|
| ObjectNodeSenderTechnicalID | It is used to identify failed business document modifications in a mass operation. Basically, the user will be able to link the response message with the request message. Please refer to the Service Interface documentation for complete information |
| CostCenterID | Cost Center ID of the cost center where the stock is located. |
| KeyDateTime | Actual Execution datetime of adjustment. If it is not provided then system takes the current datetime. |
This node specifies the details of the stock to be adjusted along with the quantity and serial numbers. Following are the elements of this node:-
| Element | Description |
|---|---|
| ExternalItemID | External Item ID. This is mandatory field. |
| FillUpSiteID | Site ID of the site where the stock needs to be adjusted. This field is mandatory. |
| CustodianID | Custodian ID of the Custodian for whom the stock needs to be adjusted. This field is mandatory. |
| MaterialInternalID | Material ID for which stock quantity will be adjusted. This field is Mandatory. |
| IdentifiedStockID | Identified stock ID of stock for which quantity will be adjusted. |
| AccountInternalID | Account ID of the account for which stock will be adjusted. This field is Mandatory. |
| OwnerPartyInternalID | ID of the owner party. This field is Mandatory. |
| ConsignmentAdjustmentTypeCode | Indicates whether the consignment stock adjustment type is Absolute, Delta Issue, or Delta Receipt. This field is Mandatory. |
| InventoryItemChangeQuantity | Material quantity of stock to be adjusted. |
| InventoryItemChangeSerialNumber | If the product is serialized, the node is mandatory. Otherwise the node should be empty |
Note:
Possible values for ConsignmentAdjustmentTypeCode are '1' (Absolute, '2' (Delta Issue), and '3' (Delta Receipt).
The response message GoodsAndActivityConfirmationConsignmentAdjustmentResponse contains a node StockManagement.
The StockManagement displays the following information of the created Goods And Activity Confirmation:
| Element | Description |
|---|---|
| SyncGACDetails | The external ID specified in the request type |
| GACUUID | Universally unique identifier of the Goods And Activity Confirmation created |
| GACID | The Goods And Activity Confirmation ID created |
In addition, a log is also provided, which gives the details of errors encountered during the modifications, if any.
This interface operation supports extensibility.
Absolute Consignment Adjustment for 1 EA of MCF-0001, Custodian MC9785 at FillUp Site MC64000:
Show full documentation
Show full documentation
<n0:GoodsAndActivityConfirmationConsignmentAdjustmentRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<MessageHeader>
<ID>00000000000102dcade9bcb0aa000c68</ID>
<CreationDateTime>2021-06-03T17:16:16Z</CreationDateTime>
<SenderParty>
<InternalID schemeID="CommunicationPartyID" schemeAgencyID="310">MC9785</InternalID>
</SenderParty>
<RecipientParty>
<InternalID schemeID="CommunicationPartyID" schemeAgencyID="310">MC10000</InternalID>
</RecipientParty>
</MessageHeader>
<GoodsandActivityConfirmationConsignmentAdjustment>
<ObjectNodeSenderTechnicalID>EXT20210603</ObjectNodeSenderTechnicalID>
<KeyDateTime>2021-06-03T17:16:16Z</KeyDateTime>
<CostCenterID>MC21000</CostCenterID>
<InventoryChangeItemConsignmentAdjustment>
<ExternalItemID>10</ExternalItemID>
<FillUpSiteID>MC64000</FillUpSiteID>
<CustodianID>MC9785</CustodianID>
<MaterialInternalID>MCF-0001</MaterialInternalID>
<IdentifiedStockID/>
<AccountInternalID>MC9785</AccountInternalID>
<OwnerPartyInternalID>1000020</OwnerPartyInternalID>
<ConsignmentAdjustmentTypeCode>1</ConsignmentAdjustmentTypeCode>
<InventoryItemChangeQuantity>
<Quantity unitCode="EA">1</Quantity>
<QuantityTypeCode>EA</QuantityTypeCode>
</InventoryItemChangeQuantity>
</InventoryChangeItemConsignmentAdjustment>
</GoodsandActivityConfirmationConsignmentAdjustment>
</n0:GoodsAndActivityConfirmationConsignmentAdjustmentRequest>
<n0:GoodsAndActivityConfirmationConsignmentAdjustmentResponse xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"
xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1649D6EF01CB194CD7F2:804">
<StockManagement>
<SyncGACDetails>EXT20210603</SyncGACDetails>
<GACUUID>00163eac-af2d-1edb-b1dd-b70a57c823ad</GACUUID>
<GACID>23718</GACID>
</StockManagement>
</n0:GoodsAndActivityConfirmationConsignmentAdjustmentResponse>
Consignment Delta Issue Adjustment for 2 EA of MCF-0001, Custodian MC9785 at Site MC64000:
<n0:GoodsAndActivityConfirmationConsignmentAdjustmentRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<MessageHeader>
<ID>00000000000102dcade9bcb0aa000c68</ID>
<CreationDateTime>2021-06-03T17:16:16Z</CreationDateTime>
<SenderParty>
<InternalID schemeID="CommunicationPartyID" schemeAgencyID="310">MC9785</InternalID>
</SenderParty>
<RecipientParty>
<InternalID schemeID="CommunicationPartyID" schemeAgencyID="310">MC10000</InternalID>
</RecipientParty>
</MessageHeader>
<GoodsandActivityConfirmationConsignmentAdjustment>
<ObjectNodeSenderTechnicalID>EXT20210603</ObjectNodeSenderTechnicalID>
<KeyDateTime>2021-06-03T17:16:16Z</KeyDateTime>
<CostCenterID>MC21000</CostCenterID>
<InventoryChangeItemConsignmentAdjustment>
<ExternalItemID>10</ExternalItemID>
<FillUpSiteID>MC64000</FillUpSiteID>
<CustodianID>MC9785</CustodianID>
<MaterialInternalID>MCF-0001</MaterialInternalID>
<IdentifiedStockID/>
<AccountInternalID>MC9785</AccountInternalID>
<OwnerPartyInternalID>1000020</OwnerPartyInternalID>
<ConsignmentAdjustmentTypeCode>1</ConsignmentAdjustmentTypeCode>
<InventoryItemChangeQuantity>
<Quantity unitCode="EA">1</Quantity>
<QuantityTypeCode>EA</QuantityTypeCode>
</InventoryItemChangeQuantity>
<InventoryItemChangeSerialNumber>
<SerialID>TEST1</SerialID>
</InventoryItemChangeSerialNumber>
</InventoryChangeItemConsignmentAdjustment>
</GoodsandActivityConfirmationConsignmentAdjustment>
</n0:GoodsAndActivityConfirmationConsignmentAdjustmentRequest>
<n0:GoodsAndActivityConfirmationConsignmentAdjustmentResponse xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"
xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1649D6EF01CB194CD7F2:804">
<StockManagement>
<SyncGACDetails>EXT20200130</SyncGACDetails>
<GACUUID>00163eac-af2d-1edb-b1de-01864ceb045d</GACUUID>
<GACID>23720</GACID>
</StockManagement>
</n0:GoodsAndActivityConfirmationConsignmentAdjustmentResponse>