My Oracle Support Banner

First Time Sku (FSTSKU) And Pending First Time Sku (PFSKU) Wip Codes Get Applied Wrongly After Performing Container Split of a Multi-Sku Container (Doc ID 2574287.1)

Last updated on AUGUST 08, 2019

Applies to:

Oracle Retail Warehouse Management System - Version 16.0.1 to 16.0.1 [Release 16.0]
Information in this document applies to any platform.

Symptoms

If item with NEW_ITEM='N' was split out of the received multi-sku container with new item, then PFSKU (Pending First time Sku) gets applied to container with just old item.

Steps To Recreate:
1. Have a C Type ASN with two items - one item with NEW_ITEM = 'Y' and the other item with NEW_ITEM = 'N'.
2. Receive the ASN.
3. Verify that the container received has the wip_code FSTSKU (First time sku) associated, in addition to MXDSKU.
4. Split the container so that the item with NEW_ITEM = 'Y' is sent to a new generic container.
5. Notice that the container with the item with NEW_ITEM = 'N' gets with the wip_code FSTSKU and the container with the item with NEW_ITEM = 'Y' gets with the wip_code PFSKU.

Expected behavior: container with the item ( NEW_ITEM = 'N' ) should not have any First Time related wip assigned and the other container with the item ( NEW_ITEM = 'Y' ) should get FSTSKU applied. MXDSKU wip should not be assigned to single SKU container.

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.