cancel
Showing results for 
Search instead for 
Did you mean: 

URGENT - Problems with 0SRM standard extractors

Former Member
0 Kudos

Hi all,

I have the following issue which is now really blocking for me.

I tried to use the new SRM 5.x extractors 0SRM_TD_CF, 0SRM_TD_PO, 0SRM_TD_PO_ACC but I got the following dump when testin through RSA3.

Runtime Errors CREATE_DATA_UNKNOWN_TYPE

Except. CX_SY_CREATE_DATA_ERROR

CREATE DATA: The specified type "\PROGRAM=GP46ACP8LVJXGTI62I0SR" is no valid.

We are running SRM Server 5.5 - SP 6 and BI7.

I chased some OSS notes but found nothing related to this problem.

Please any feedback on this error? It is very urgent.

Thanks

Chris

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Chris,

Did you find any solution for this problem? I get the same short dump and, ofcourse, the data exctraction by InfoPackage has red status on the monitor...

Did anyone solve this problem or has more information about it?

Thanx,

Andreea

Former Member
0 Kudos

Hi,

No, we still have this problem. We raised a message to SAP. I will let you know the outcomes.

Thanks

chris

Former Member
0 Kudos

Hi,

Thanks a lot!

Regards,

Andreea

Former Member
0 Kudos

Hi,

Finally, we got the solution and fixed this issue:

This is a problem of data object length. Please proceed as follow:

- Go in function module named BBP_BI_GEX_CONSOLIDATE.

- Find lv_struc_name and access the declaration.

- Change v_struc_name TYPE char30 to v_struc_name TYPE char200.

- Activate.

Do the same in module fonction named BBP_BI_GEX_DENORMALIZE.

This will fix the issue for all 0SRM extractors (PO, GR, PO Acc, IV).

FYI, we requested the creation of a sap note as this fix above is a modification of the standard.

I am sure that helps.

Regards

Former Member
0 Kudos

Thanks Chris! I will try this as soon as I get back to work. If you don't mind, please tell me when the SAP note is released.

Again, thanks!

Regards,

Andreea

Former Member
0 Kudos

Hi,

They have created the note. Please apply note # 1093706 in order to fix this issue.

Thanks & regards

chris

Former Member
0 Kudos

Hi,

Thanx!

Best regards,

Andreea