E1: 42I: Enhancement Request to Maintain Agreement Relationship and Pricing with Sales Order Detail Line with Future Commitments (Doc ID 3038847.1)

Last updated on AUGUST 05, 2024

Applies to:

Symptoms

Currently when a sales order line that has an existing OIM agreement attached is moved to future commitments the agreement will fully detach from the line, pricing will default from base pricing, and the line type will change from VC to S. This essentially makes the line a regular sales order line. In the legacy Agreement Module (system code 38) the agreement relationship is maintained along with the pricing.

This causes multiple issues for the customer.

1) Future commitments are used because the customer sells to distributors that will place orders for the next 6 to 7 months to manage the supply chain. If future commitments were not used then orders with shipments 6 to 7 months out will be committed to existing inventory causing over commitments and backorders. The customer sells fasteners to the automotive and non-automotive industry and it is standard to schedule shipments months out in advance. When the agreement detaches from the sales order the commitments are deleted from the F42IO21 Outbound Inventory Item Balance and F42I015 Outbound Inventory Agreement Transaction File transaction tables. When the end consumer reports consumption on a part and replenishment runs it no longer considers the future commitment orders in the calculation and will create another replenishment order thereby doubling the order. This is extremely difficult to manage in the automotive, consumer electronics, and datacom industries.

2) The customer does not use base pricing and when the agreement detaches from the order all pricing is lost because the pricing comes from the agreement. The customer runs what are called bookings each morning so that the business can see the forecast of open orders and total amounts for all open orders. Bookings are done with P42101 using a specified queries depending on what data is needed. Since future committed orders no longer have a price then the open dollar amount looks like its dropping relative to the open quantity. This prevents the customer from knowing the dollar amount they will be shipping in any given time frame. The customer uses R42565 Batch EDI - P.O. Acknowledgment Transaction (855) to send acknowledgements of when orders are entered and when they are changed. When an order is changed to future commitment and acknowledgement is sent to the end customer with zero pricing leading to incorrect data in the end customers system along with confusion regarding the price the end customer is paying for the order.

3) The customer has a PO number on the agreement which defaults into the sales order detail when the order is created. When the agreement detaches the PO number is also lost on the sales order. When acknowledgements are sent to the end customer the PO is missing and makes it difficult to match the E1 order number with the end customers PO number.

The enhancement request is to keep the agreement attached to the sales order detail line along with the pricing and not change the line type from VC to S so that the replenishments calculation takes into consideration future committed orders.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.