Restrict PO at company code level

[pardeep_malik]

Hi,

We have near about 10 number of company code and lot of plants attached to each company code.

and only one purchase organisation.

Now business require that PO shold be created only for 2 company codes not for all. there are alreday roles available for PO creation .

Now how to restrcit the PO creation at company code level because at plant level it is not possible due to large number of plants.

Regards,

Pardeep Malik

[Former Member · Accepted solution]

Hi,

Use BADI- ME_PROCESS_PO_CUST for the Process

Ask your ABAPer to write with your Logic that system should not allow other Company code while creating PO.

If user enter other Company Code it will throw an Error.

Regards,

Rahul Patil.

[pardeep_malik · Accepted solution]

thanks for answer.....

but i want ot resolve issue with roles only first.

For ABAP code there will be huge coding and Z Tables also. So i want to avoid this.

[Former Member · Accepted solution]

Hi Pradeep,

This BADI dont require Big process & Z Tables.

Only 3-4 line Code is sufficient for this process.

Better u can discuss with ABAPers also.

And creating a role is also a good but you can check with Basis Guy whether Role is available or not??

Rahul Patil.

[former_member193326 · Accepted solution]

Hi,

Please kindly be informed that the following authorization objects are checked when an Enjoy purchase order is created (activity 01) or changed (activity 02):

- M_BEST_BSA (document type in PO)

- M_BEST_EKG (purchasing group in PO)

- M_BEST_EKO (purchasing organization in PO)

- M_BEST_WRK (plant in PO)

So this is somthing you can not solve by only using roles. You will need as suggested to make the check in the BADI.

Best Regards,

Arminda Jack.

[namitha_pk]

You can take ABAPer s help to put validation. so that error message is thrown whenver other compnay codes are used.