on 2024 Jun 27 3:14 PM
Hello ,
My Business requirement involves posting a material document either from MIGO screen for some of the movement types or From Delivery App(VL32N or VL02N) depending whether a delivery is created using a PO or a STO in SAP S/4 HANA Public Cloud.
Also, we have created custom Fields in Custom Fields APP in following 2 ways :
1. Creating a standalone custom field for Business Context Material Document Item.
2. Creating a Custom Field for Business Context Procurement: Purchasing Document Item and then enabling business scenarios for Delivery and Material Document respectively. This feature helps us to flow the custom field value from PO to material without any code.
Issue i am facing is listed below for both the scenarios :
A.] Scenario 1 : Posting material document from MIGO Screen.
When a material document is processed using MIGO app, custom logic written in BADI Change Item Data in Material Documents MMIM_ITEM_PROVIDE_DATA is triggered and user has complete freedom to functionalities like auto populate/grey out etc. for standalone custom fields created using approach 1 mentioned above but the extended custom fields(approach 2) are greyed out . I was expecting these fields to be enabled so user can get values from F4 help. Currently these are greyed out and take some value from random PO/STO. Screen Shot ref : CF_MIGO
B.] Scenario 2 : Posting material document from Delivery Screen(eg. Post Goods Receipt).
When a material document is created using Inbound/Outbound Delivery App; the extended custom field possess values from preceding PO/STO document but the standalone Custom fields(approach 1) created are greyed out here .Screen Shot ref(CF_Preceding_Doc) Also, i tried calling class for above mentioned Materiel BADI in Delivery BADI Modify LE_SHP_SAVE_DOCUMENT_PREPARE Standard and Custom Fields for Delivery Header and Items and was able to insert data in to changing parameter but its not getting committed.
Request clarification before answering.
User | Count |
---|---|
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.