Solution : https://service.sap.com/sap/support/notes/1168811 (SAP Service marketplace login required)
Summary :
In this SAP Note, it is explained that creating purchase orders through transaction ME21 without ME21N leads to omitted FM fields like EKPO-KPLNR and EKPO-KBLPOS, crucial for managing Earmarked Funds in contract references. The solution includes a two-step process: storing FM fields using a custom Form Routine in OGSD Multireference and extending the Data Collation process to consider FM screens via Posting Rule BA01. This involves adjusting IMG settings for Form Routines and Document Schema under OGSD, and customizing the OGSD table /ICO/MOC_VBI for batch input scenarios, ensuring the FM fields are captured and processed effectively.
Key words :
fm documentcall function 'mecp_read_commitment_plan' exporting im_ebeln = <ls_ekpo>-konnr im_ebelp = <ls_ekpo>-ktpnr im_multi_sel = ' ' im_refresh_buffer = 'x' im_dunkel = 'x' importing ex_ekcph = ex_t_ekcpi = ex_t_ekcpa = lt_ekcpa, target field bdc_okcode source field field const entr field entry 3 entry 4 postr ba01 ba01 itmno 5210 5220 program saplfmsv scno 100, field entry 1 entry 2 postr ba01 ba01 itmno 3280 3295 program saplfmsv scno 100, target field bdc_okcode source field field const entr, ogsd->purchasing->multireference-> document schema-> define document schemaselect schema 'bp1', -oil->ogsd->purchasing->general settings->define purchasing form routinesdefine, ogsd->purchasing->multireference-> document schema-> define document categrories doc, ogsd->purchasing->multireference->assign document schema, multireference<ls_ekpo>-kblnr = c_item-rbeln, data collation posting rule ba01
Related Notes :
| 481034 | FAQ: Data transfer (batch input) in purchasing |