SAP Knowledge Base Article - Preview

3753182 - Missing Extension Mapping in Method MAP_MEOUT_EXTENSION_TO_GFN During Central Contract Distribution - SAP ERP &SAP S/4 HANA

Symptom

During API-based central contract distribution, extension/custom fields are not transferred to the target system when BAdI MEOUT_BAPI_CUST_INBOUND is active.
The extension data is available before BAdI processing but becomes empty afterward without any error.


Read more...

Environment

  • Materials Management (MM)
  • SAP ERP Central Component
  • SAP ERP
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA
  • SAP S/4HANA

Keywords

MEOUT_BAPI_CUST_INBOUND, extensions, extension fields, custom fields missing, central contract distribution, api, soap, bapi inbound, purchasing document, outline agreement, contract, mapping, empty method, inbound processing, s/4hana procurement *** The Updated value: ***MEOUT_BAPI_CUST_INBOUND, extensionin, extension fields, badi, central contract distribution, api inbound, soap, bapi, purchasingdocument, extension mapping, custom fields, contracts, sourcing and procurement, inbound processing, mapping , KBA , MM-PUR-HUB-CTR , Central Contract , MM-PUR-OA-CON , Contract , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.