S/4HANA Proxy Z-Field Upgrade
Budget: ₹600 – ₹1,500 INR
Build time in two days Saturday Sunday.
I have an inbound proxy in S/4HANA for creates and updates materials. To extend the business process I now need several custom (Z) fields added and mapped end-to-end.
Scope
• Enhance MARA, MARC and MVKE with the required Z-fields (DDIC + append structures).
• Adjust the proxy data type so the new fields flow in from the middleware without breaking existing interfaces.
• Add ABAP logic in the proxy implementation class to populate the new fields during both “create” and “change” calls covering Purchasing, Sales and Production materials.
• Provide a short unit test / demo program or eCATT script showing that the proxy posts the fields correctly.
Key points
– Existing proxy objects (service interface, message type, class) remain; only extensions and coding are required.
– No functional changes beyond the three extra field groups.
– Use standard enhancement techniques—BADI, enhancement section or clean modification—to keep the upgrade path clear.
– Follow SAP naming conventions (Z*), include transport documentation and brief technical spec.
Deliverable is a transport or set of transports plus the test evidence so I can import straight into QA and run.
I have an inbound proxy in S/4HANA for creates and updates materials. To extend the business process I now need several custom (Z) fields added and mapped end-to-end.
Scope
• Enhance MARA, MARC and MVKE with the required Z-fields (DDIC + append structures).
• Adjust the proxy data type so the new fields flow in from the middleware without breaking existing interfaces.
• Add ABAP logic in the proxy implementation class to populate the new fields during both “create” and “change” calls covering Purchasing, Sales and Production materials.
• Provide a short unit test / demo program or eCATT script showing that the proxy posts the fields correctly.
Key points
– Existing proxy objects (service interface, message type, class) remain; only extensions and coding are required.
– No functional changes beyond the three extra field groups.
– Use standard enhancement techniques—BADI, enhancement section or clean modification—to keep the upgrade path clear.
– Follow SAP naming conventions (Z*), include transport documentation and brief technical spec.
Deliverable is a transport or set of transports plus the test evidence so I can import straight into QA and run.