Skip to Content
0
Dec 09, 2020 at 02:46 AM

Cumulative Received Quantity Updating in Sales Scheduling Agreements

385 Views

Hi Experts,

We have implemented SAP S/4Hana Cloud in an automotive supplier.

Sales Scheduling Agreements are being updated with the following API:

SAP_COM_0444 - Delivery Schedule of Sales Scheduling Agreement – Receive, Update (B2B)

We have realised that the CumulativeReceivedQuantity field is being automatically updated by the system when the customer does not include the field "CumulativeReceivedQuantity" in the XML file send in the communication.

We have the following Sales Scheduling Agreement:

An outbound delivery has already been created and issued for this Sales Scheduling Agreement:

The customer then updates the Sales Scheduling Agreement with a new delivery schedule (PurchasingDeliveryScheduleCreationDate = 01.12.2020).

<?xml version="1.0" encoding="ISO-8859-1" ?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edi="http://sap.com/xi/EDI" xmlns:yy1="http://SAPCustomFields.com/YY1_">

<soapenv:Body>

<edi:SchedulingAgreementRequest>

<MessageHeader>

<CreationDateTime>2020-11-30T21:27:00Z</CreationDateTime>

<SenderParty>

<InternalID>VOLVO-C83FA</InternalID>

</SenderParty>

</MessageHeader>

<SchedulingAgreement>

<PurchasingSchedulingAgreementID>385925258767</PurchasingSchedulingAgreementID>

<Release>

<PurchasingDeliveryScheduleID>12</PurchasingDeliveryScheduleID>

</Release>

<Party PartyType="Supplier">

<BuyerPartyID>VOLVO-C83FA</BuyerPartyID>

</Party>

<Item>

<PurchasingReceivingPlant>CHN06</PurchasingReceivingPlant>

<PurchasingUnloadingPoint>PD3</PurchasingUnloadingPoint>

<PurchasingSchedulingAgreementItem>00010</PurchasingSchedulingAgreementItem>

<Product>

<BuyerProductID>32310505</BuyerProductID>

</Product>

<Release>

<SchedulingAgreementReleaseType>1</SchedulingAgreementReleaseType>

<PurchasingDeliveryScheduleID>12</PurchasingDeliveryScheduleID>

<PurchasingDeliveryScheduleCreationDate>2020-12-01</PurchasingDeliveryScheduleCreationDate>

<ScheduleLine>

<ScheduleLineDeliveryDate>2020-12-01</ScheduleLineDeliveryDate>

<ScheduleLineOrderQuantity>1</ScheduleLineOrderQuantity>

</ScheduleLine>

<ScheduleLine>

<ScheduleLineDeliveryDate>2020-12-02</ScheduleLineDeliveryDate>

<DeliveryDateFormat>D</DeliveryDateFormat>

</ScheduleLine>

</Release>

<yy1:YY1_SD_DS>12</yy1:YY1_SD_DS>

<yy1:YY1_SD_SP_V1>C83FA</yy1:YY1_SD_SP_V1>

<yy1:YY1_SD_VS>2020-12-01</yy1:YY1_SD_VS>

</Item>

</SchedulingAgreement>

</edi:SchedulingAgreementRequest>

</soapenv:Body>

</soapenv:Envelope>

As you can see, the customer is not including the field "CumulativeReceivedQuantity" in the communication.

If we check the Sales Scheduling Agreement we can verify that the system has automatically updated the field CumulativeReceivedQuantity.

We do understand that the system is proposing the value "1" because there is an outbound delivery of the same quantity that the customer has already received according to the delivery date.

The system is behaving as if somebody clicks on "Propose CRQ":

However, we would like to know if there is a way to avoid this behaviour. Some customers do not always inform about the CumulativeReceivedQuantity and that does not always mean that they have already received the last outbound delivery.

We have tried to update the Sales Scheduling Agreement with the following XML file (CumulativeReveivedQuantity = 0.000)

<?xml version="1.0" encoding="ISO-8859-1" ?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:edi="http://sap.com/xi/EDI" xmlns:yy1="http://SAPCustomFields.com/YY1_">

<soapenv:Body>

<edi:SchedulingAgreementRequest>

<MessageHeader>

<CreationDateTime>2020-11-30T21:27:00Z</CreationDateTime>

<SenderParty>

<InternalID>VOLVO-C83FA</InternalID>

</SenderParty>

</MessageHeader>

<SchedulingAgreement>

<PurchasingSchedulingAgreementID>385925258767</PurchasingSchedulingAgreementID>

<Release>

<PurchasingDeliveryScheduleID>13</PurchasingDeliveryScheduleID>

</Release>

<Party PartyType="Supplier">

<BuyerPartyID>VOLVO-C83FA</BuyerPartyID>

</Party>

<Item>

<PurchasingReceivingPlant>CHN06</PurchasingReceivingPlant>

<PurchasingUnloadingPoint>PD3</PurchasingUnloadingPoint>

<PurchasingSchedulingAgreementItem>00010</PurchasingSchedulingAgreementItem>

<Product>

<BuyerProductID>32310505</BuyerProductID>

</Product>

<Release>

<CumulativeReceivedQuantity>0.000</CumulativeReceivedQuantity>

<SchedulingAgreementReleaseType>1</SchedulingAgreementReleaseType>

<PurchasingDeliveryScheduleID>13</PurchasingDeliveryScheduleID>

<PurchasingDeliveryScheduleCreationDate>2020-12-01</PurchasingDeliveryScheduleCreationDate>

<ScheduleLine>

<ScheduleLineDeliveryDate>2020-12-01</ScheduleLineDeliveryDate>

<ScheduleLineOrderQuantity>1</ScheduleLineOrderQuantity>

</ScheduleLine>

<ScheduleLine>

<ScheduleLineDeliveryDate>2020-12-02</ScheduleLineDeliveryDate>

<DeliveryDateFormat>D</DeliveryDateFormat>

</ScheduleLine>

</Release>

<yy1:YY1_SD_DS>13</yy1:YY1_SD_DS>

<yy1:YY1_SD_SP_V1>C83FA</yy1:YY1_SD_SP_V1>

<yy1:YY1_SD_VS>2020-12-01</yy1:YY1_SD_VS>

</Item>

</SchedulingAgreement>

</edi:SchedulingAgreementRequest>

</soapenv:Body>

</soapenv:Envelope>



However, the systems is automatically updating the CumulativeReceivedQuantity field with a value of "1".

Is it possible to ignore this behaviour? Is there a field in the communication that we can use to avoid the CumulativeReceivedQuantity field updating?

Thank you very much in advance for your comments,

Best regards,

Jorge.

Attachments

32245-image.png (180.1 kB)
32246-image.png (191.0 kB)
32248-image.png (174.8 kB)
32250-image.png (174.9 kB)
32251-image.png (125.6 kB)