Description | Manage Customer Return Notification |
Name | ManageCustomerReturnNotificationIn |
Namespace | http://sap.com/xi/A1S/Global |
Process Component Description | Inbound Delivery Processing |
Process Component Name | InboundDeliveryProcessing |
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 customer return notifications.
The web service Manage Customer Return Notification In enables you to connect external applications to your SAP Business by Design system and to create general information and items for customer return notification.
The web service interface Manage Customer Return Notification In offers the operation CreateBundle.
The CreateBundle operation is used to create one or more customer return notifications.
Due to the stateless behavior of A2X service operations, it is not possible to enforce any kind of transactional or logical locking.Despite 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.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Description | Create customer return notifications |
Name | CreateBundle |
Synchronous | yes |
Release Status | Released |
To create customer return notifications.
The create bundle operation is used to create one or more customer return notifications.
The following are the elements of Customer Return Notification Bundle Create Request
Elements | Description |
---|---|
BasicMessageHeader | Message header |
CustomerReturnNotification | Customer Return Notification Structure |
Details of message sub node Customer Return Notification
The cardinality of the node is 0..*, which implies that multiple customer return notifications can be created together.
The following are the attributes of Requested Elements
Attributes | Description |
---|---|
ActionCode | Determine the action that will be executed |
DeliveryNotificationID | Alternative key for create customer return notification |
ProcessingTypeCode | Processing type code |
DeliveryDate | Delivery date of customer return notification |
GrossWeight | Gross weight |
GrossVolume | Gross volume |
IncotermsClassificationCode | Incoterms classification code |
IncotermsTransferLocationName | Incoterms transfer location name |
ShipToLocationID | Ship to location ID |
FunctionalUnitID | Functional unit ID |
ProductRecipientID | Product recipient ID |
VendorID | Vendor ID |
FreightForwarderID | Freight forwarder ID |
WithWarehouseProviderBusinessProcessVariantTypeCode | With warehouse provider business process variant type code |
WarehouseProviderID | Warehouse provider ID |
Item | Item |
AttachmentFolder | Attachment folder |
TextCollection | Text collection |
TransportationTerms | Details of transportation tracking like tracking ID and tracking URL |
To create the customer return notification, the processing type code must be set as "CRD".
The coded representation of Incoterms classification code has been given as below:
Incoterms Classification Code Value | Description |
---|---|
CFR | Cost and freight |
CIF | Cost, insurance and freight |
CIP | Carriage and insurance paid to |
CPT | Carriage paid to |
DAF | Delivered at frontier |
DAP | Delivered at place |
DAT | Delivered terminal |
DDP | Delivered duty paid |
DDU | Delivered duty unpaid |
DEQ | Delivered ex quay (duty paid) |
DES | Delivered ex ship |
EXW | Ex works |
FAS | Free alongside ship |
FCA | Free carrier |
FOB | Free on board |
The following are the attributes of customer return notification items
Attributes | Description |
---|---|
ActionCode | Determine the action that will be executed |
LineID | Line item ID |
ItemProduct | Product information of item |
DeliveryQuantity | Delivery quantity |
CustomerReturnReasonCode | Code of customer return reason |
SellerPartyID | Seller party ID |
BuyerPartyID | Buyer party ID |
ProcessingTypeCode | Item processing type code |
ReturnFollowupActivityCode | Return follow up activity code |
IdentifiedStockID | Identified stock ID |
IdentifiedStockProductID | Identified stock product ID |
IdentifiedStockTypeCode | Identified stock type code |
ProductRequirementSpecificationID | Product requirement specification ID |
ItemBusinessTransactionDocumentReference | Referenced business transaction document |
This is a coded representation of return follow up activity code.
Return Follow up Activity Code Value | Description |
---|---|
1 | Post to Own Stock |
3 | Repair at Own Service Center |
The following are the attributes of item business transaction document reference
Attributes | Description |
---|---|
ActionCode | Determine the action that will be executed |
OutboundDeliveryID | Outbound delivery ID |
OutboundDeliveryItemID | Outbound delivery item ID |
SalesOrderID | Sales order ID |
SalesOrderItemID | Sales order item ID |
CustomerInvoiceID | Customer invoice ID |
CustomerInvoiceItemID | Customer invoice item ID |
CustomerInvoiceRequestID | Customer invoice request ID |
CustomerInvoiceRequestItemID | Customer invoice request item ID |
Request xml to create customer return notification
<n0:CustomerReturnNotificationBundleCreateRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <ID>Token 4</ID> <UUID>12345128-90AB-CDEF-0123-4567A9ABCDEF</UUID> <ReferenceID>Token 10</ReferenceID> <ReferenceUUID>12345878-90AB-CDEF-0123-456789ABCDEF</ReferenceUUID> </BasicMessageHeader> <CustomerReturnNotification ActionCode="01"> <DeliveryNotificationID>CRN_TEST_05</DeliveryNotificationID> <ProcessingTypeCode>CRD</ProcessingTypeCode> <DeliveryDate> <StartDateTime timeZoneCode="EST">2015-05-23T22:30:00Z</StartDateTime> <EndDateTime timeZoneCode="EST">2015-05-23T22:31:00Z</EndDateTime> </DeliveryDate> <IncotermsClassificationCode/> <IncotermsTransferLocationName/> <ShipToLocationID>MC64000</ShipToLocationID> <FunctionalUnitID/> <ProductRecipientID>MC10000</ProductRecipientID> <VendorID>MC9785</VendorID> <FreightForwarderID/> <WithWarehouseProviderBusinessProcessVariantTypeCode/> <WarehouseProviderID/> <Item ActionCode="01"> <LineID>10</LineID> <ItemProduct ActionCode="01"> <ProductID>MCF-0001</ProductID> <SerialNumbers ActionCode="01"> <SerialID>1000</SerialID> </SerialNumbers> </ItemProduct> <DeliveryQuantity unitCode="EA">1</DeliveryQuantity> <CustomerReturnReasonCode/> <SellerPartyID>MC10000</SellerPartyID> <BuyerPartyID>MC9785</BuyerPartyID> <ProcessingTypeCode/> <ReturnFollowupActivityCode>1</ReturnFollowupActivityCode> <IdentifiedStockID/> <IdentifiedStockProductID/> <IdentifiedStockTypeCode/> <ProductRequirementSpecificationID/> <ItemBusinessTransactionDocumentReference ActionCode="01"> <OutboundDeliveryID/> <OutboundDeliveryItemID/> <SalesOrderID>1527</SalesOrderID> <SalesOrderItemID>10</SalesOrderItemID> <CustomerInvoiceID/> <CustomerInvoiceItemID/> <CustomerInvoiceRequestID/> <CustomerInvoiceRequestItemID/> </ItemBusinessTransactionDocumentReference> </Item> <TransportationTerms ActionCode="01"> <TransportTracking> <ID>125</ID> <WebURI>http://sap.com/anyURI</WebURI> </TransportTracking> </CustomerReturnNotification> </n0:CustomerReturnNotificationBundleCreateRequest_sync>
Response containing created customer return notification ID and UUID
<n0:CustomerReturnNotificationBundleCreateConfirmation_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <CustomerReturnNotificationConfirmationBody> <ReferenceObjectNodeSenderTechnicalID> </ReferenceObjectNodeSenderTechnicalID> <ChangeStateID>20150623053443.6483440</ChangeStateID> <DeliveryNotificationID>CRN_TEST_05</DeliveryNotificationID> <UUID>00163e07-3d6a-1ed5-86ad-319ddf835adb</UUID> </CustomerReturnNotificationConfirmationBody> </n0:CustomerReturnNotificationBundleCreateConfirmation_sync>