Skip to Content
avatar image
Former Member

APO DP - loading from InfoCube to planning area

I am using APO DP V5.

I have the following situation:

1. I am extracting sales history data at the end of each day from a connected ECC system into an InfoCube, using delta logic, so in the Cube I just have the new sales history transactions (despatches) for the day

2. I am then loading data from the Cube to my DP planning area via transaction /SAPAPO/TSCUBE

I assume I must have the 'add data' flag set for each key figure in this transaction, to ensure I see the consolidated sales history in the planning area.

Is this the 'best practice' approach for regular loading of sales history? I assume it's better to have a 'delta' approach for the Cube, for improved performance.

Thanks, Bob Austin

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    May 11, 2007 at 01:22 PM

    Hi Bob,

    I have two questions

    1. You said you are only loading delta data into the cube, that means are you deleting all previous data from cube or giving a selection? or setting up the indicator "Delete entire content of data target."?

    2. If you set the indicator "add data", then the system ignores existing orders in the same SNP version for the same product, location and periods. This means that if you release to SNP twenty times, twenty separate orders are created in SNP. Does your scenario need two sales orders for one order?

    I think the best way is to just load the deltas into the cube and load historical data to the PA using a variant without "add data" selection.

    You can find more best practices as per scenario


    Hope this helps.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      pretty much. A lot will depend again on the planning cycle and the volume and criticality of the data that is new

      0. Load initial extract of all data to start with

      1. Daily delta load to Cube

      2. Daily/weekly Load(depending on planinng cycle and amount of data) from Cube to planning area for period that is relevant to planning

      3. Weekly/Monthly load of data into cube that will rectify errors that arise due to corrections not captured by deltas

      4. Step 2 matched to follow step 3 such that corrections are passed on to the planning process

      all this need to be tested/thought about to make sure that it doesnt fluctuate the planning results a lot.

      Remember all this makes sense when juxtaposed with the rest of the planning activities. for eg Sales history load just before you do a proportional factor job, followed by a forecasting job etc.

      also you need to take into consideration the process of CVC generation between loading the cube and loading the planning area (am not sure how much your CVCs will change based on the new data)