Skip to Content

Transporting DP Planning Area related objects


What is the best practice to transport following objects from development system to production system? Which of them can be created/changed directly in production system without having any impact?

1. new planning area/data view/data source. If the new planning area is using existing key figures/chars which are already in production system, do we need to select 'With InfoObject transport' in /sapapo/tsobj transaction ?

2. time stream ID period changes

3. key figure addition/removal from data view.

4. new data view for a given planning book

5. Macros

Apart from this, we have a case where the planning area and the related planning book exist in Quality (Test) system when transported from Dev system. But in production system, we could see only the planning area. How do we rectify the case?



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 07 at 07:29 AM

    Hi Yogesh

    Below is the sequence one should ideally follow for transporting DP planning area in APO. I have used this approach numerous times with 100% success rate. Once you have done your required changes or updates related to the PA please make sure

    1) using /sapapo/tsobj you include the DP PA with at-least this option,

    But before that ensure that the existing extractor using the planning area has been regenerated and activated ( /n/sapapo/sdp_extr)

    2) Now coming on to planning books, macros, and BW objects like PSA, ODS & transformation.

    3) If planning book changes or macro changes, directly in individual environment, is an practice in your organization ( which is not an recommended approach, but I have seen in many cases), then it is better to transport planning books first in a different transport after checking the KF sequencing and KF no.s. The same applies for macros. In such case first transport planning books in a separate TR and then macros in a separate TR.

    4) Based on your last case that you mentioned it is evident that someone has created the planning book / dataview in the test system, since you haven't moved any transports yet. This is very bad and should be stopped at all cost. Before you approach with the above mentioned steps ( 1 to 3), please delete the PB/DV created in the test system as it will create lot of mismatch due to different GUID once you move the transport, which in turn will impact your jobs, activities and extractors as well.

    Hope this helps you in solving your issue. Do let me know if you need any further inputs.

    pa1.png (12.5 kB)
    Add comment
    10|10000 characters needed characters exceeded