Delivery Orders with appointment creates a PO only after multiple attempts

Technote (troubleshooting)


Problem(Abstract)

Delivery Orders with appointment creates a PO only after multiple attempts

Cause

This issue is coming due to wrong implementation of YFSGetExternalInventoryUE user exit where First and last date for the supply is same and is less than the appointment date taken. Infact dates can be same but should not be less than the appointment date. If appointment is taken it should be fulfilled by the supply present on that date.

Environment

Foundation v8.5

Configuration Required:
Enterprise: E1
Role: Enterprise, Seller
Catalog Organization - > E1
Inventory Organization - > E1
Capacity Organization - > Default

E1N1: Child node for E1
Role: Node, Seller
Inventory Organization - > E1
Catalog Organization - > E1
Capacity Organization - > Default
Procurement Allowed, Work Order Creation allowed,

Item: Item1 created for E1
Item1 is associated with Delivery Service ‘Delivery Service’.

E1N1 has resource pool that does not have Capacity Information available and services all regions.

Enterprise: E2
Role: Seller, Enterprise, Legal entity
Inventory Organization - > E2, Maintains external inventory
Catalog Organization - > E1
Capacity Organization - > Default


E2N2: Child node for E2.
Role: Node, Seller
Catalog Organization - > E1
Inventory Organization - > E2

Implement GetExternalInventoryUE such that it will return Inventory available from a future date say T+3.

Simulation Steps
1. Create an Order for E1 for Item1 with Delivery Method DEL
2. ShipNode- E1N1, ProcureFromNode= E2N2
3. Create WorkOrder
4. Take Appointment on a future date say T+4.
5. Schedule Order -> Order goes to backorder (do not check Release Immediately or Override release date flag)
6. Schedule Order Again-> Order goes to Reservedstatus (do not check Release Immediately or Override release date flag)
7. Schedule Order Again -> Order goes to Awaiting Procurement Purchase Order Creation (do not check Release Immediately or Override release date flag)

Order has to be scheduled thrice for Procurement Order to be cut.


Resolving the problem

The expected behavior in this case should be back-order every time since supply is coming earlier and is consumed before the appointment date(First and Last ship date is same).
If purchase order creation is required then the supply Last Ship date should be increased.

The inconsistency in product behavior where rather than backordering the orderline every time it moves it to a different status has been accepted as a defect and is planned to be fixed in a higher version of the product.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling Order Management

Software version:

9.0

Operating system(s):

All

Reference #:

1616361

Modified date:

2013-03-31

Translate my page

Machine Translation

Content navigation