MIGO_GR authorization issue

[Former Member]

Hi gurus,

I have authorization requirement to distinguish GR cases. There are two cases:

1. GR based on PO which goes to stock
2. GR based on PO where material goes directly to consumption.

Business case: There are two types of purchasing. First, when we purchase materials and when they are stored. And second, when we purchase materials and they are not stored but directly consumed. In both cases GR is required (for business it is must). But different persons are responsible for such GRs. How to make authorizations in that way to eliminate conflict? Please advice.

Thanks,

Anna

[PollyGan]

Hi Anna,

There's no standard authority objects for above scenarios.

You have to create your own authority objects and implement them into user-exit or BAdI to trigger the check.

Thanks and regards,

Polly

[Former Member]

Hi Polly Gan,

Thanks on you replay, I found auth object M_MSEG_LGO. Could I use that? In first case its must go to storage location, but in second one there is no possibility to enter storage location.

Regards,

Anna

[PollyGan]

Hi Anna,

Yes, you're right.  For PO with account assignment, system doesn't check

M_MSEG_LGO as no storage location posting is relevant. I double checked via debugging.

But you cannot prevent users which are supposed to only post GR to stock from posting to consumption, right? As M_MSEG_LGO is not checked during the consumption posting.

Thanks and regards,

Polly