- After the sold-to party for a sales order is changed, changes in this order will not trigger the generation of a new output item with output type of ORDER_CONFIRMATION_CHANGE.
- After the sold-to party for a sales quotation is changed, changes in this quotation will not trigger the generation of a new output item with output type of SALES_QUOTATION_CHANGE.
SAP S/4HANA Cloud
In Output Parameter Determination app, within 'Show Rules for: Sales Document' and 'Determination Step: Receiver', the sold-to party AG is maintained as the receiver role for output type ORDER_CONFIRMATION and ORDER_CONFIRMATION_CHANGE.
For the first time a sales order is being created, the receiver ID for AG is saved into the buffer with the original sold-to party. If the AG is ever changed, then the changes afterwards will not trigger the generation of a new output item for it fails for the comparison between current sold-to party and previous one in the buffer. Due to AG is maintained as the determination receiver role, the inconsistency will reject the output item with type of ORDER_CONFIRMATION_CHANGE.
The situation for sales quotation is the same.
Don't change the sold-to party for a sales order if AG is determined as the receiver role in Output Parameter Determination app. That's to avoid the inconsisitency with the buffer.
ORDER_CONFIRMATION_CHANGE, SALES_QUOTATION_CHANGE, Sales Quotation, Sales Order, Sold-To Party, Buffer, AG, ORDER_CONFIRMATION, SALES_QUOTATION , KBA , CA-GTF-OC , SAP S/4HANA output management , Problem