For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Development is delivering support for the order number parameter on the ESS job in 19A. They believe this will resolve the issue for dropship orders with less than 500 lines (since each batch is a single order). however, the 500-line limit is still a significant issue even with the parameterized ESS job.
Thanks Shyam.
So, in case we import a heavy order having more than 500 lines say 800 then does the system creates 2 orders or just 1 with 500 lines and ignore the rest 300 lines? Alternatively, can we setup transformation rule to auto-create next order with 300 lines. Parts businesses might run with this workaround till a permanent fix is available.
Thanks to help.
Cheers,
Prasad.
Hi Prasad,
Long Story, in short, we had a long discussion with the Product development team on this issue. in our business, we had every sales order with more than 500 lines and it goes to 1600 lines per sales order and this was not agreed by the business which is running on EBS R12.2.4 and had a custom solution there.
This SR was for Dropship SO and PO and see the important conversation we had with Oracle.
Final Solution: Development working on this solution and in next 1-2 version release we get this functionality. interim solution development gave to include sales order as a parameter in Generate orders program which we will get in 19.01 1st Feb 2019 release.
unable to group multiple requisitions to single PO in Drop Ship (Doc ID 2398453.1) ----- this start from here since we are using SO -PO mapper
SR 3-18962131531 : Generate Orders program created drop ship PO for only half of the SO lines
Enh 28937159 - INCREASE THE LIMIT OF PO LINES ON GENERATE ORDERS PROGRAM
Thanks Shyam for the deeper insights. It really helps.
Now we can create single purchase Order for More than 1000 Lines. Development provides us one custom Profile Solution.
Still SO -PO Line Number Sync an issue.( SO Line 1 "Generate Order ESS" change to PO Line 6, this SO-PO lines still not in sync)
SR 3-19992198581: Dropship Purchase Order Line Should Be in Sync with Order Management Line
Old SR : SR 3-19073898291 Dropship SO and PO Line numbers not in sync - Need information on req extraction logic
BUG 26951761
The Logic I have mentioned above is applicable when GROUP_REQUISITION_LINES = Y.
When GROUP_REQUISITION_LINES = N, then the PO Line Number is determined in order of Requisition Line ID.
Feedback from development
========================
The line determining logic for Touchless PO creation sorts the interface lines with several attributes and logic is not always straight forward, some attributes are considered based on setups and agreement controls.
Following is the list of attributes and order in which lines are sorted and ranked accordingly:
1. ITEM_ID,
2. ITEM_DESCRIPTION,
3. CATEGORY_ID,
4. If Group Requisition Lines is 'N' then REQUISITION_LINE_ID,
5. If Requisition Lines is FIXED PRICE then REQUISITION_LINE_ID,
6. Based on setup NEED_BY_DATE,
7. Based on setup SHIP_TO_LOCATION_ID,
8. Based on setup SHIP_TO_ORGANIZATION_ID,
9. LINE_TYPE_ID,
10. ITEM_REVISION,
11. UOM_CODE,
12. FROM_HEADER_ID (Blanket Agreement Header ID),
13. FROM_LINE_ID (If Line Price Override is Not-Allowed then Blanket Agreement Line ID should match; Else Grouping not allowed),
14. OKE_CONTRACT_HEADER_ID,
15. OKE_CONTRACT_VERSION_ID,
16. VENDOR_PRODUCT_NUM,
17. CONTRACT_ID (Contract Agreement Header ID),
18. SUPPLIER_REF_NUMBER,
19. NOTE_TO_VENDOR,
20. NEGOTIATED_BY_PREPARER_FLAG,
21. WORK_ORDER_PRODUCT,
22. EXTERNAL_ATTACHMENT_ID
SELECT
/* SR# 3-19073898291 */
prh.requisition_number
, prl.line_number req_line_number
, prl.line_status
, ph.segment1 AS po_number
, prl.requisition_header_id
, prh.creation_date req_creation_date
, prl.requisition_line_id
, pl.unit_price
, pl.line_num po_line_number
, pl.FROM_CO_SEQ
, prl.creation_date req_line_creation_date
, ph.document_creation_method
, ph.prc_bu_id AS po_prc_bu
, ph.document_status
, ph.po_header_id
, pl.po_line_id
, pl.from_header_id
, prl.req_po_instance_id
, ph.document_status
, ph.vendor_id
, ph.vendor_site_id
FROM
fusion.po_headers_all ph
, fusion.po_lines_archive_all pl
, fusion.por_requisition_lines_all prl
, fusion.por_requisition_headers_all prh
WHERE
+ph.po_header_id(+) = pl.po_header_id+
+AND prl.po_line_id = pl.po_line_id(+)+
AND prl.requisition_header_id = prh.requisition_header_id
AND ph.segment1 in ('P101104935','P101104928')
AND pl.FROM_CO_SEQ = 0
ORDER BY
ph.po_header_id
, prl.requisition_line_id
, pl.line_num;
NEW SR 3-19992198581 : Drop ship Purchase Order Line Should Be in Sync with Order Management Line where Oracle need to work on Bug 26951761
Now we can create single purchase Order for More than 1000 Lines. Development provides us one custom Profile Solution.
Still SO -PO Line Number Sync an issue.( SO Line 1 "Generate Order ESS" change to PO Line 6, this SO-PO lines still not in sync)
SR 3-19992198581: Dropship Purchase Order Line Should Be in Sync with Order Management Line