Purchase Requisition mandatory in Purchase Order

[Former Member]

Hi

I have a requirement to configure 5 document types and among that 2 documents types must have PR as mandatory and the remaining 3 document types will not have PR as mandatory.

I've tried in screen variant but it is not working.

kindly let me know the other way to configure the above requirement.

Regards

Bala

[Former Member]

Hi Bala

Masa wanted to know, do you want to create the POs in SRM or not. SRM POs also end up reaching ERP in Classic and Extended classic Scenarios.

Try this BADI in ECC ME_PROCESS_PO_CUST, This may help you build some check while using ME21N, ME21 or BAPI_PO_CREATE1 to check what doc type is selected for PO and then you may throw an error if it is not referencing a PR

The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.

You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.

Typical applications for this BAdI include:

Processing of own objects

Processing of additional data on standard objects

Implementation of additional checks and derivations

Change of data in standard fields

Note

Ensure that data integrity is guaranteed.

Change in field selection

Regards

Virender Singh

[masa_139]

Hi,

Are you talking about PO in SRM or PO in ERP?

What is deployment mode? Classic or Extended Classic?

Regards,

Masa

[Former Member]

Hi Masa,

Thanks for the reply.

This is a PO in ERP and dont know what do you meant by Classic/Extended classic.

Kindly let me know how to proceed further.

Thanks & Regards

Bala