E1: 43: Requisition Order Release (P43060) Generates a Procurement Order with Amount 0 from a Requisition Order if the Current Period is Set to a Prior Period (P0010) (Doc ID 2595238.1)

Last updated on DECEMBER 11, 2019

Applies to:

Symptoms

P43060 generates a procurement order with amount 0 from a requisition order if the Current Period is set to a prior period in P0010 than the current date .

Steps to replicate:

1.     In P0010 Company Setup, Current Period is set to 6 (June) for General Accounting.
2.     Take a version of P4310 that will be used purchase requisitions. Set processing option 3. PACO Warning = Blank (Issue warning) in tab 3-Interfaces.
3.     P43060 Requisition Order release calls a version of P4310 in tab Version. For this version of P4310, set processing option 3. PACO Warning = Blank (Issue warning) in tab 3-Interfaces.
4.     Set in P40205 (Line Type Constants) a line type X with Inv. Interface = B (G/L Account & Non-Stock Purch). Also, set order activity rules in P40204 (Work With Order Activity Rules) for combination : line type X, Order type OR (Purchase Requisition) and line type X, Order type OP (Purchase Order).
5.     Enter a purchase requisition (P4310) with line type X, QTY= 0, Unit cost = 0, but with Extended Cost = 100. The order date is today (October). The system displays the warning message "Date Is in a Future Month (PACO)".  Save the requisition.
6.     Try to generate a procurement order from the requisition above. Go to P43060, inquiry requisition number, take Row exit and select Order Release menu. In <Generate POs from Reqs. - Order Release> Release Amt = 100 .
7.     Press Save button. The system displays the warning message "Date Is in a Future Month (PACO)" and delete the value (100) from Release Amt field. This is an incorrect behavior of the application. Press Save again and generate the purchase order.
8.     The purchase order was generated with Extended Cost =0 even if the purchase requisition has Extended cost = 100. This is an incorrect behavior of the application.
9.     Set the processing option 3. PACO Warning = 1 (Do not issue warning) for both version of P4310 used for requisition and purchase order.
10.     Enter another similar purchase requisition (P4310) with line type X, QTY= 0, Unit cost = 0 and Extended Cost = 100. The order date is today (October). The system will NOT displays the warning message "Date Is in a Future Month (PACO)".  Save the requisition.
11.     Try to generate a procurement order from the requisition above. Go to P43060, inquiry requisition number, take Row exit and select Order Release menu. In <Generate POs from Reqs. - Order Release>  Release Amt = 100.
12.     Press Save button. The system does not display the warning message "Date Is in a Future Month (PACO)". Generate the purchase order .
13.     The purchase order was generated with Extended Cost =0 even if the purchase requisition has Extended cost = 100. This is an incorrect behavior of the application.

P43060 has to generate procurement orders with specific amount value even if Current Period is set to a prior period in P40010 than the current date.

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.