My Oracle Support Banner

Transfers With Packs Not Shipped Are Not Closed When Running TSFCLOSE Batch (Doc ID 2471784.1)

Last updated on NOVEMBER 23, 2019

Applies to:

Oracle Retail Merchandising System - Version 15.0.1 and later
Information in this document applies to any platform.

Symptoms

On : 15.0.1 version, Inventory Movement

Transfers with packs not shipped are not closed.
Created a transfer with an external finisher in the middle (with a 2nd leg) with pack items - no assortment information is generated for packs.
When tsfclose run and it already overdue the days to consider the close of this transfer - transfer is not closed.

The issue can be reproduced at will with the following steps:

  1. Create a transfer from warehouse (wh1) to warehouse (wh2) with an external finisher in the middle (finish1).
  2. Choose a pack item that doesn't have any assortment information available for a pack item and the external finisher (finish1) - no information in item_loc for item = packA and loc = finish1.
  3. Add a pack item (packA) to the transfer. The form will ask to create the assortment, answer Yes.
  4. No assortment information is created for the pack item (added to the transfer) and the external finisher - no information in item_loc for item = packA and loc = finish1.
      Note: Assortment information is correctly created for the component items of the pack.
  5. Approve the transfer.
  6. TSF_CLOSE_OVERDUE parameter should be 'Y'.
  7. Move the VDATE so that the transfer CREATE_DATE is not within the TSF AUTO CLOSE DAYS parameter.
  8. Run the TSFCLOSE.pc batch.
  9. Transfers were not closed (status = 'D').

Changes

 

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
Changes
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.