My Oracle Support Banner

DROPSHIP CREATEPO LINE_LOCATION_ID IS NOT SORTED AS PO_LINE_ID (Doc ID 2558369.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Purchasing Processes

ACTUAL BEHAVIOR
---------------
When running 'Requisition Import' concurrent after entering DropShip SO,
the new Purchase Order created via CREATEPO process because they set ASL&SourceRule.

At the created PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID is not sorted as PO_LINE_ID as below.

- Example
po_line_locations_all:
LINE_NUM PO_LINE_ID LINE_LOCATION_ID
-----------------------------------------
8 1427525 1444031
7 1427524 1444032
6 1427523 1444033
5 1427522 1444034
4 1427521 1444035
3 1427520 1444036
2 1427519 1444037
1 1427518 1444038

This issue only occured when they set the workflow activity 'GROUPING_ALLOWED_FLAG' as "Y"
and creating PO via CREATEPO process for the DropShipOrder.
NonReproduceCase:
- non DropShipOrder
- Create PO via Autocreate Screen
- Set the workflow activity 'GROUPING_ALLOWED_FLAG' as "N"


EXPECTED BEHAVIOR
-----------------------
PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID is sorted as PO_LINE_ID as below.

- Example
po_line_locations_all:
LINE_NUM PO_LINE_ID LINE_LOCATION_ID
-----------------------------------------
8 1427525 1444038
7 1427524 1444037
6 1427523 1444036
5 1427522 1444035
4 1427521 1444034
3 1427520 1444033
2 1427519 1444032
1 1427518 1444031


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create DropShip Sales Orders
(N)OM > Orders, Returns > Sales Orders

2.Run WFBP for OEOL

3.Run Requisition Import
(N)PO > Requests
Import Source:ORDER ENTERY
Group By:Vendor
Initiate Approval after ReqImport:Yes

4.Check the new REQ#

5.Check the new PO created from above REQ
po_lines_all:
LINE_NUM PO_LINE_ID
------------------------
1 1427518
2 1427519
3 1427520
4 1427521
5 1427522
6 1427523
7 1427524
8 1427525


po_line_locations_all:
LINE_NUM PO_LINE_ID LINE_LOCATION_ID
-----------------------------------------
8 1427525 1444031
7 1427524 1444032
6 1427523 1444033
5 1427522 1444034
4 1427521 1444035
3 1427520 1444036
2 1427519 1444037
1 1427518 1444038

=> LINE_LOCATION_ID is not sorted as PO_LINE_ID.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
They use PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID value in their report
so the end user confused with LINE_LOCATION_ID was not sorted as PO_LINE_ID.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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