Sales Order Form And Oe_order_pub Creating Incorrect Demand
(Doc ID 2226944.1)
Last updated on JUNE 06, 2018
Applies to:Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
oe_order_pub creating incorrect demand
While using oe_order_pub for creating sales-orders, it's creating demand, but the Sales Orders are not created.
Also, occurs when enter a Sales Order, but do not save it, the demand is still being created.
Should be creating the Sales Orders also.
False Demand issues on Sales Order form:
1. Via the Order Management Responsibility.
2. Navigate: Orders, Returns > Sales Orders.
3. Sales Order header creation
4. No demand yet for the order as no line created yet
5. Enter Sales Order lines and go to next lines and lines are auto scheduled and close the form to not save lines
6. Do not save lines
7. Re-query sales order and see there are no lines on the sales order
8. Verify the demand for the sales order and it exists but expectation it should remove
9. Verify ATP inquiry as well to confirm demand still exists
False Demand issue with oe_order_pub for creating Sales Orders:
Case 1: If using single item (which is valid), it is creating a record in MSC_Sales_Orders and OE_Order_headers_all.. - No Issues
Case 2: If using single item (which is invalid), it is not creating a record in MSC_Sales_Orders and OE_Order_headers_all (its rolling/revert it back).. - No Issues
Case 3: If using multiple items (first one in the list is invalid), it is not creating record in MSC_Sales_Orders and OE_Order_headers_all.. - No Issues
Case 4: If using multiple items (Last one in the list is invalid), it is creating record in MSC_Sales_ORders, for all valid items, and NO record in OE_Order_headers_all.. - Big Issues
With such demand (explained in above case#4), ATP is giving incorrect//bad date to actual orders in the system. and when we track back, ATP allocated quantity to orders that does not exists in the system.
The processing is such that if
- There are 3 records in upload file
- Error creating record is second in order
- the record that are before this error record (I.e. first in this case) hits ATP, the second errors hence does not hit ATP and the third record after the error record does not hit ATP.
If move the error record to third record then both 1st and 2nd record item hit ATP. (attached code ATP_API)
Tested removing commits from program, made another API code today and ran with different users for testing and observation is same as yesterday.
The order API rollbacks order data but ATP related API/processing does not rollback ATP whether one gives explicit commit or commit after success of API or rollback after failure of API, ATP data remains.
Have tried removing custom workflow from UK Closeout Order In Dev01 and placing standard workflow but still same ATP issue appears. Oracle SR can be followed up.
Order# Line # Notes
110 1.1 Good SKU
110 2.1 SKU Blocked
110 3.1 Good SKU
For the above example:
Action# Action Result Arun Comments Additional Comments
1 Called the Oracle Order Import API ONLY + Explicit COMMIT from SQL Developer Although Order error out BUT the ATP shows demand for line #1.1 and 3.1 Order not created.
ATP shows demand for 1.1 If Blocked SKU was third in order then all SKUs before that blocked SKU hold ATP, these results are irrespective of commits/rollback or explicit commit.
2 Called the Oracle Order Import API ONLY + NO Explicit COMMIT from SQL Developer Although Order error out BUT the ATP shows NO demand for line #1.1 and 3.1 Order not created.
ATP shows demand for 1.1 If Blocked SKU was third in order then all SKUs before that blocked SKU hold ATP these results are irrespective of commits/rollback or explicit commit.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!