Key fields for ADSO for Production planning(PP) SAP BW4HANA 1.0

[former_member216525]

Planned to implement Production Planning and controlling (PP) related BW reports in SAP BW/4HANA 1.0 by using only the standard business content along with standard reports provided SAP but unfortunately SAP hasn’t delivered any complete solution for PP in BW and nothing is promised yet in their nearby roadmap for a Full proof business content in BW related to Production Planning.

Technically, SAP have provided business content for PP till the Integrated DWH layer only, but not the Virtual Mart layer & standard BW reports in SAP BW4HANA 1.0 like they have in other modules (SD, MM, FI & etc.)

Considering this I am trying to build ADSO Integrated layer from the underlying ADSO (Corporate) and Info source objects and this ADSO:DW layer- delta calculation need to have key fields to be declared. Since I am not familiar with key fields for this functionally, I thought of using the ADSO: DW layer- Data mart(acts like Infocube), is this approach correct to use this type of ADSO properties.

Also if anyone can be help me with Keyfields for the ADSO based on 7X /or any other reference will be greatly appreciated, I have got the key feilds for two datasource based on below link, but looking out for others datasources as well.

Datasource

2LIS_04_P_MATNR

0PP_WCCP_20

2LIS_04_P_ARBPL_20

2LIS_04_P_COMP

https://answers.sap.com/questions/6646936/bi-pp-datasources-dso.html

Thanks,

Mahesh. A

[burns_sh]

Hi Mahesh,

I am currently trying to implement Production Planning PP reporting in BW4HANA 1.0 similar to what you were doing this time last year, and coming across the same issues with partial business content.

I have currently set up the 2LIS_04_P_MATNR flow to an standard type ADSO referencing the DSO 0PP_C01 (Plan /Actual Comparison Order/Material View) in previous versions of BW.

However, I cannot find similar references for building the 2LIS_04_P_ARBPL_20 flow.

I was just wondering if you had any documentation etc of what you did for this flow?

Thanks,

Shane.

[former_member71289 · Accepted solution]

Hi Mahesh,

yes, you are right. There was a DSO in BW 7.x based on 2LIS_04_P_MATNR extractor called 'Planned/Actual Comparison Order/Material View' 0PP_DS01 with the following key

- 0ORDERITEM Order item number

- 0PLANT Plant

- 0PRODORDER Manufacturing Order

- 0FISCVARNT Fiscal Variant

If the delta mode of the DataSource allows to load the data into an "ADSO DW layer - Datamart" yes, you can use this option.

To be frank, my preference would be to use DSO with keys (these days called "standard DSO") using update with aggregation type 'overwrite' / 'move' for the metrics instead of 'summation' as it makes it easier to load / reload single records / documents. (Happy to hear other opinions on this!)

The Datamart DSO ("Info Cube"-like ADSO) should only be defined with the inventory flag if non-cumulative key figures are used in the DSO. So 'no', only a very few Data Mart DSOs would need the inventory flag.

Loading the transactional into one DSOs per DataSource and having a CompositeProvider union the information instead of loading data from the different DataSources into one ADSO - yes, I strongly believe this is the right approach.

Reason is also that the data loads for one data source does not interfere with load requests of another DataSource. - There were very complex content models in the past; I remember the Overhead Cost Controlling InfoCube (0COOM_C02) with data loaded from 12 data sources into one single data target, which was a nightmare in case of load issues.

All the best for your project,

Andreas

[former_member71289]

Hi Mahesh,

following information I found somewhere but not for 2LIS_04_P_MATNR:

"For 2lis_04_P_arbpl_20: If you want to do a comparison between plan data and actual data the key should be the 0PRODORDER mapped to the field AUFNR and 0OPERATION mapped to the field VORNR. You could also use this key if you just want to report on the actual data reflecting the actual status of the order at the last loading date.

For 2lis_04_P_COMP: If you want to do a comparison between plan data and actual data the key should be the 0PRODORDER mapped to the field AUFNR and 0COMPONENT mapped to the field IDNRK. You could also use this key if you just want to report on the actual data reflecting the actual status of the order at the last loading date. It would make sense to restrict the data to records where 0ACTRELDATE (mapped to field FTRMI ) is filled, to ensure that plan and actual data is available for the order.

For 0PP_WCCP_20: You can use 0WORKCENTER, 0PLANT and 0CALDAY as key."

Best regards,
Andreas

[former_member216525]

Hi Andreas,

Thanks for your inputs and quick response as always.

Will consider to build ADSO based on your inputs and will you let you know if I get any issues, meanwhile I would appreciate if you can find the Key fields for 2lis_04_P_MATN. This should be available in the previous version(7X) of DSO I assume.

Also I would like to know if the "ADSO DW layer - Datamart" can be used in the integrated layer instead is "ADSO - delta calculation", because if I use the former I dont need to declare the Keyfields, moreover it will act as Infocube like only, which should be fine I presume, but I would also like to rise a point this, is this option can be used only with Inventory check. (as per below blog)

https://www.just-bi.nl/all-you-need-to-know-about-adso/

Correct me here, If I can proceed with this option "ADSO DW layer - Datamart" in the integrated layer and unions all 4 ADSO in CP and build reports on same. Plan is to built similar std reports used in 7X version.

Thanks,

Mahesh. A