cancel
Showing results for 
Search instead for 
Did you mean: 

Same material type in different backends

Former Member
0 Kudos

Hi Experts,

We have SRM 5.5 server with two R/3 backend systems. We have the following BDoc problem during material replication:

***

Data cannot be maintained for set type COMM_PR_PUR_1

Diagnosis

The data for a set can be maintained only if the product is assigned to a category to which the set type is assigned.

Procedure

Check whether the product is assigned to a category that allows the set

***

We have found out that the reason for this error is that the material type UNBW in the first R/3 is not assigned to Purchasing on "Define Attribute to Material Types" screen. However the same material type UNBW in the second R/3 is assigned to Purchasing. And we have replicated the products from first R/3 before the materials were replicated from second R/3. Therefore the system does not permit to download the materials belonging to UNBW from 2nd R/3 to SRM.

This seems strange for us because SRM creates separate hierarchies for Material Groups from 2 Backends (i.e. under R3MATCLASS there are different hierarchies for different R/3 backend systems). But why there is only one hierarchy for R3PRODSTYP? Did we maybe do something wrong in customizing activities? Does anyone have any clue?

Thanks

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Please follow below steps to resolve issue

"Data cannot be maintained for set type COMM_PR_PUR_1"

In SRM System:

1. Go to transaction code COMM_HIERARCHY

2. Search on Hierarchy

3. Select 'R3PRODSTYP' - Product Subtype

4. Go to Category ID 'MAT_'

5. Go to Set type Tab and maintain below entry.

Set Type: COMM_PR_PUR_1

Position: 10
View ID: PURCHASING

View Description: Purchasing

and reprocess the Bdocs or process the materials which got struck in SMQ2

Former Member
0 Kudos

Hi Emre,

We also faced a similar issue of "Data cannot be maintained for set type COMM_PR_PUR_1" in SRM 5.5 server with two R/3 backend systems.

Please find our observation:

In comm_hierarchy, set type COMM_PR_PUR_1 was missing for material type XXXX, we maintained it manually.

Change one field in material in R/3 (Say add a space in material text) & save.

Material will get replicated to SRM.

Thanks to RK, I hope information is useful.

Ashutosh Tripathi

Former Member
0 Kudos

It is standard SRM functionality