My Oracle Support Banner

TRAN_CODE 25 Does not Capture GL_REF_No For Inventory Adjustments done from Different Buckets (Doc ID 2506976.1)

Last updated on DECEMBER 04, 2019

Applies to:

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

Symptoms

TRAN_CODE 25 is posted without GL_REF_NO when Inventory Adjustments are done.

Steps To Recreate:

1. Perform Inventory Adjustments in Store Inventory Management (SIM)
           unavailable to available and available to unavailable.
           Reasons codes are in sync across SIM and RMS.
2. Verify the TRAN_DATA table in Retail Merchandising System (RMS) and notice that it is inserting records with tan_code 25 in TRAN_DATA.
3. All these adjustments are mapping without a GL_REF_NO. Only REF_NO_2 is capturing as 1. Irrespective of whatever reason codes Users are selecting in SIM.
4. Users are unable to place these separate dispositions in separate GL accounts. Users need to send data to GL for separate accounts based on unavailable to available and available to unavailable inventory movements on the reason codes selected in SIM.

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.