ORDAUTCL (The Order Auto Close) Batch Does Not Consider ORD_APPR_CLOSE_DELAY (Doc ID 2986821.1)

Last updated on NOVEMBER 14, 2023

Applies to:

Symptoms

On: MFCS/RMS 23.1.201.6 version

The ORDAUTCL (The Order Auto Close) batch closes the Orders the next day instead of waiting for the number of days configured in the parameter ORD_APPR_CLOSE_DELAY.

The following conditions should be met:

  1. The order is not in Completed status and was previously approved.
  2. The number of days between the latest ship date and the current date is greater than the ‘Approved PO Close Delay' system parameter.
  3. There are no open shipments for the order.
  4. End of week date should not be null.

All the above conditions should be accomplished, but in this case, condition number 2 is not met, and the auto-close batch closes the Purchase Orders anyway.

Steps to Reproduce
-----------------------

1. Go to the MFCS application and create a new order
2. Approve the order
3. Ship the Purchase Order
4. Receive the Purchase Order
5. Wait for the Run Nightly batch

Note: the ORDAUTCL batch (which runs on the nightly batch) is not expected to close the Order. The latest shipment is later than the current date, so the process is calculating the absolute between LATEST_SHIP_DATE and VDATE, and it is wrong, which allows to close the Order when it is not expected. In this case, the Purchase Order should not be closed automatically

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.