0PC_C01

[Former Member]

Dear Gurus,

We are planning to implement the product cost controlling infoprovider 0PC_CO01 which is currently available as standard business content. I have extracted r/3 information with the standard business content and it works perfectly. Unfortunately the datasource is not delta capable and this is a constraint for us. We also prefer a customized infoprovider/data sources/extractors based on the standard rather that using the standard directly.

Is it possible to implement a "Z" environment for profitability analysis(including infoproviders,data sources & extractors) based the info provider 0PC_CO01? If yes, what are the steps I should follow for this?

Thanks & Regards

Suneeth

[Former Member · Accepted solution]

Hi

This Cube talks about Production Analysis (NOT Profit).

If your Data Source doesnot support Delta it would be difficult to get the same on BI Side.

So Go for Generic Delta

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb...

Hope it helps and clear

[Former Member · Accepted solution]

Thanks for the information on creating generic extractors. In this case, can I select the extractor and extract structure from the standard content itself? How do I manage this part since I want the exact data flow as in the standard. Thanks

Suneeth

[Former Member · Accepted solution]

Hi,

I am also in process of implmenting 0PC_C01, but not able to validate data in Bi against ECC.

Can you please tell me how do you validate 0PC_C01 data against ECC?

Any reports / transactions with which you can validate data?

Thanks in advance for your time

SA

[Former Member · Accepted solution]

You can use the transaction S_ALR_87013127 in ECC to validate the data in BIW.

Suneeth

[Former Member · Accepted solution]

Hi,

Thanks for the reply. I tried using this report but still not able to validate data.

Can you tell me which layout you are using to validate data? e.g for me layout coming by defualt is /SE02. () It is last column there in the report.

Which all chars on BI side you are using ? if you can give me some pointers to validate data, it would be helpful.

Thanks again for your time and help,

SA

[Former Member · Accepted solution]

Hi

You cannot use Standard Extractor, as far my knowledge goes. But you can copy/ call the Same Fields/Tables specified in Standard Extract Structure and maintain the flow via Generic Extractor.

Hope it helps

[former_member181964]

Hi,

We are using 0CO_PC_01 and 0CO_PC_02 infosources to get the data into 0PC_C01, it si working fine ad you told that delta is not supporting is correct. But you can use it based on Period wise.

I also faced the same problem, but now it is Ok, because I'm using Data Extraction full mode only but everyday before data load, it will delete the overlaping req and then load, this we can set it in InfoPackage level.

Use the following code in InfoPackage for 0FISCPER and

In DataTarget tab -->Automatic Loading of Similar/Identical option is there here you can set ->

Delete existing Req
InfoSourcea are same
Some or More Comprehensive

DATA: l_idx LIKE sy-tabix,
        zzdate LIKE sy-datum,
        zzbuper LIKE t009b-poper,
        zzbdatj LIKE t009b-bdatj,
        zzperiod(7) TYPE c.
  READ TABLE l_t_range WITH KEY
       fieldname = 'FISCPER'.
  l_idx = sy-tabix.
  zzdate = sy-datum - 1.
  CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
    EXPORTING
      i_date               = zzdate
*             I_MONMIT             = 00
      i_periv              = 'V3'
           IMPORTING
     e_buper              = zzbuper
     e_gjahr              = zzbdatj.
*           EXCEPTIONS
*             INPUT_FALSE          = 1
*             T009_NOTFOUND        = 2
*             T009B_NOTFOUND       = 3
*             OTHERS               = 4
  .
  IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ENDIF.

*....
  CONCATENATE zzbdatj zzbuper INTO zzperiod.
  l_t_range-low = zzperiod.
  l_t_range-option = 'EQ'.
  l_t_range-sign = 'I'.
  MODIFY l_t_range INDEX l_idx.

  p_subrc = 0.

Note: To get the correct values in BW, END USERS must to Settelment in ECC.

Thanks

Reddy