Transfers with Packs Not Shipped Are Not Closed when Running TSFCLOSE Batch (Doc ID 2942043.1)

Last updated on APRIL 13, 2023

Applies to:

Symptoms

Transfers with packs not shipped are not closed. Created a transfer with an internal finisher in the middle (with a 2nd leg) with pack items. When the TSFCLOSE batch is run and is already overdue, the days to consider the close of this Transfer - Transfer are not closed.

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

1. Create a transfer from the warehouse (wh1) to the warehouse (wh2) with an internal finisher in the middle (finish1).
2. Choose a pack item and Add the pack item (packA) to the Transfer.
3. Approve the Transfer.
4. Now notice Transfer automatically gets closed for 1st leg.
5. TSF_CLOSE_OVERDUE parameter should be 'Y'.
6. Move the VDATE so that the transfer CREATE_DATE is not within the TSF AUTO CLOSE DAYS parameter.
7. Run the TSFCLOSE.pc batch.
8. Transfers were not closed, so transfer remains with status A.

Cause

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