Retail Predictive Application Server (MOSC)

MOSC Banner

Non-Template MFPCS SaaS v24 Implementation Guidelines

edited Dec 19, 2024 9:36PM in Retail Predictive Application Server (MOSC) 5 commentsAnswered ✓

Hi Experts,

We are working on MFPCS / APCS Implementation. Due to extensive customer specific requirements we are forced to use non-template version for both applications. Their must have requirements include planning Sales R at Day level. Due to which we are expected to source Sales at Day level and a lot of custom processes which doesn't align with GA / base MFP in any shape or form.

Questions:

  1. In RAP we noticed table W_RTL_SLS_ITC_LC_DY_A in DW which is expected to hold day level aggregated sales from transaction level sales being loaded in RAP. Currently this is empty in our environment, We assume there must be additional batches to be enabled / run to populate this table? Note: Week level tables are populated in our RAP for all key metrics and we have been successfully able to load data in MFPCS via RAP Integration.

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center