cancel
Showing results for 
Search instead for 
Did you mean: 

recursive allowed at client level

Former Member
0 Kudos

Dear Gurus,

One component B is used in a BOM of A in 2 plants. In one plant it is recursive & in another plant it is not recursive. But as per my experience if we activate check box for "recursive allowed" in component details of one plant then in another plant it is getting activated automatically as the field is at client level. System is not allowing to remove the tick in plant where it is not recursive. Is there any solution for this? We want to remove this  tick in a plant where BOM is not recursive.

Regards,

SAP cons

Accepted Solutions (0)

Answers (1)

Answers (1)

kiran_kumar179
Active Contributor
0 Kudos

SAPCons,

Check below SAP Note whether it is useful to you 1354946 - Recursion check and low-level code assignment?


BR
KK

Former Member
0 Kudos

Dear Kiran,

Note not suitable. Is there any workaround solution to avoid this issue?

Reagrds,

SAP CONS

kiran_kumar179
Active Contributor
0 Kudos

SAPCONS,

As far as I know in standard there is no other alternative approach I see check with any enhancement for BOM explosion whether you can restrict this at particular plant?

BR
KK

Former Member
0 Kudos


SAPCONS,

We also faced same issue during data migration in our projects, but could not find any solution for it.

Searched many SAP Notes but not found any solution.

Former Member
0 Kudos

Dear Vishal Joshi,

We deleted the component in one plant to make it non recursive. Then removed the tick from another plant. Then reassigned the component again in forst plant.

Regards,

Yogesh

kiran_kumar179
Active Contributor
0 Kudos

SAPCONS,

In this case after reassigning the component in first plant did you check the recursive indicator again if so it should have activated in another plant too right?

BR
KK

Former Member
0 Kudos

Dear Kiran Kumar,

After reassigning material in BOM of first material indicator is not getting activated in first plant where it is not needed.

Regards,

SAP CONS

kiran_kumar179
Active Contributor
0 Kudos

SAPCONS,

Thanks for sharing the workaround which would certainly useful to someone in future, if your issue has been resolved please close the issue.

BR
KK