Inclusion of field Requisitioner in Production Operations

[KeLaw]

Hello,

In order to fulfill our production demands, we create Operations within Production Orders which can trigger Purchase Requisitions.

Via BADI YY1_MM_PUR_S4_PR_CHECK we have set the field Requisitioner (Field Name: AFNAM) as a mandatory field for all Purchase Requisitions.

Now we are facing the issue, that the field can not be filled directly from within a Operation of a Production Order.

Does anybody know a way how we could integrate the field Requisitioner (Field Name: AFNAM) in the “External Processing” Tab of an Operation?

Best regards,

Kerisha

[Chris1973 · Accepted solution]

Hello @KeLaw 

Thank you for your question.

Below are some insightful links to support you:

Implementing a Business Add-in (BAdI): Check a Purchase Requisition, App Extensibility: My Purchase Requisitions, KBA 2955651

The simple answer to your question is NO, not in a supported way. Let me explain.

In summary, the public cloud due to its modular approach does not support adding the Requisitioner (AFNAM) field to the External Processing tab of an operation’s production-order. This is because it is a GUI application. Also, you cannot extend the GUI screen with key-user tools.

The choice of making AFNAM mandatory in your system will therefore block purchase requisitions that your system created automatically from external-processing operation because users have no place to maintain that field beforehand.

Instead of changing the PP operations UI, my suggestion is for you to use BAdI MM_PUR_S4_MODIFY_ITEM in the Custom Logic app to enable you derive and populate AFNAM automatically for your PR items which originate from production orders and then keep your existing check in MM_PUR_S4_PR_CHECK. This will ensure every purchase requisition has a valid requisitioner and you will also be sticking with the clean-core approach.

You may consider building a logic. below is a quick guide.

In your Custom Logic App, create a new enhancement implementation

Select as described in the screen (Business Context: Procurement: Purchase Requisition Item, BAdI: MM_PUR_S4_PR_MODIFY_ITEM). You can add logic that detects PR item,

derive a suitable requisitioner such as MRP Controller, set PurchaseRequisitionItem-Requistioner accordingly when it is initial.

You can keep your existing logic but only raise an error if AFNAM is still not initial after the system has run the modify BAdI.

Best regards

Chris

[KeLaw · Accepted solution]

@Chris1973: Hello Chris, thank you once again for your helpful input. We will look more into setting up MM_PUR_S4_PR_MODIFY_ITEM accordingly. Best regards, Kerisha