Retail Merchandising System (MOSC)

MOSC Banner

event_run_type in COST_EVENT_RUN_TYPE_CONFIG

edited Sep 1, 2016 5:00AM in Retail Merchandising System (MOSC) 1 commentAnswered

Hi, can anyone please let me know the difference between COST_EVENT_RUN_TYPE_CONFIG.event_run_type 'ASYNC' and 'SYNC'.  AS per my understanding, for both the cases we don't need to execute batches to populate Future_cost tables. But I am curious to know the exact difference between event_run_type  'ASYNC' and 'SYNC'.

For an instance, Event_Desc 'Deal', if we set event_run_type  as 'ASYNC' and if we set event_run_type  as 'SYNC', what difference it actually makes in data flow and functional impact on it.

What are the advisable configurations and why?   In case of 'NIL', it is set as 'SYNC'. what impact /difference it makes if we set it to 'ASYNC'. we are in RMS 15.0

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