Salmth Does Not Calculate Cumulative Markon Percent (CMO) Properly In Exception Scenarios
Last updated on OCTOBER 19, 2016
Applies to:Oracle Retail Merchandising System - Version 14.0.3 and later
Information in this document applies to any platform.
In certain exception scenarios, SALMTH updates MONTH_DATA.CUM_MARKON_PCT with the value from the previous dept/class/subclass/location record instead of getting it from DEPS.BUD_INT.
SALWEEK works as expected for the same scenario. The attachment has the comparison of cmo between week_data and month_data for given month of daily_data transactions.
Steps to recreate
1. Daily_data has activity but it does not impact cmu calc (like sales or inv adj or custom tran code like 100 which will create a DD record with all zero values)
2. GAFS retail should be zero for the dept/class/subclass/location combination
3. There must be other locations for which GAFS retail exists.
4. Run stockledger batches and observe the salmth batch result in month_data table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms