SAP Knowledge Base Article - Preview

2745643 - Badi ME_CATALOG_INTERFACE_CUST and custom catalog field mapping

Symptom

  • You have implemented BADI ME_CATALOG_INTERFACE_CUST in order to define the mapping between custom catalog fields at OCI structure to EBAN corresponding SAP standard fields when using punch-out catalogues. 
  • When adding items from catalogs to Purchase Requisition in ME51N, not all concerned fields are updated.


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

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

NEW_ITEM-CUST_FIELD1, NEW_ITEM-CUST_FIELD2, NEW_ITEM-CUST_FIELD3, NEW_ITEM-CUST_FIELD4, NEW_ITEM-CUST_FIELD5, LMEGUICJM, MAP_CATALOG_VALUES, MY_CAT_MAPPING, ME_GUI_LAYOUT_ALV_CUST, MEREQ3211GRID   , KBA , MM-PUR-GF-CAT , Catalogues in Purchasing , 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.