cancel
Showing results for 
Search instead for 
Did you mean: 

Replication of DNL_CUST_SRVMAS fails - COMM_PR_UNIT not allowed for produc

Former Member
0 Kudos

Hi there

We are experiencing a problem when trying to replicate object DNL_CUST_SRVMAS via transaction R3AS in SRM 7.0

When we execute the replication of object DNL_CUST_SRVMAS from ECC6 to SRM 7 (transaction R3AS) we get a short dump in SRM 7stating that "Set type COMM_PR_UNIT is not allowed for product type".

Material replication worked fine.

We are on the latest support packages for SRM 7.

Thanks.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

We had the same problem in SRM5.0 and solved the problem with deactivating the BADI implementation HIERARCHY_UPDATE_BSP.

The function where the dump is occuring COM_SET_VIEW_CREATE_BLUEPRINT

is used in PC-UI applications for Products in CRM to create blue print

table entries for categories and settypes.

In your case since you are downloading data to an SRM system it is not

relevant to create blueprint entries. This is very time consuming as

well, therefore we suggest you to switch off PC-UI. Inorder to do so

you need to deactivate the badi implementation HIERARCHY_UPDATE_BSP.

In transaction se19, do the following

1. Give the implementation name as HIERARCHY_UPDATE_BSP in classic

BADI implementation under Edit Implementation

2. Open the implementation in change mode.

3. In the menu select Implementation->Deactivate.

Before deactivating the badi, Please stop the existing initial load

of service master (DNL_CUST_SRVMAS), then deactivate the badi

mplementation and finally start the initial load again.

I hope you can solve your problem with this solution too.

Regards,

Jos van den Berg

Former Member
0 Kudos

Hi Deepa,

We are having the same issue DNL_CUST_SRVMAS. could you please explian in detail what ABAP change you guys did and where? Please help me..

Thanks

Srini.

Former Member
0 Kudos

HI

This has been solved. It was something in the ABAP code where it was looking at the CRM version (Have no idea why). Changed the code to read CRM versions higher than 500 I think and it seems to have solved the issue.

Thanks