Retail Merchandising System (MOSC)

MOSC Banner

What is the Architectural Design for Keeping TRAN_DATA_HISTORY and KEY_MAP_GL in the job SALPRG

edited Aug 26, 2018 5:03AM in Retail Merchandising System (MOSC) 2 commentsAnswered

Hello,

I have question to Oracle Experts, We are in the process of cleaning up the TRAN_DATA_HISTORY table as it is getting bigger and causing lot of performance issue. Off course we will be purging TRAN_DATA_HISTORY based on the TRAN_DATA_RETAINED_DAYS_NO from the SYSTEM PARAMETER.

The question i have her is what is the Architectural Design behind keeping TRAN_DATA_HISTORY and KEY_MAP_GL in THE SALPRG job? What is the impact of purging KEP_MAP_GL table?

Thanks

Vignesh

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center