![\"SAP\"](\"http:\/\/oprsteny.cz\/wp-content\/uploads\/SAP.jpg\")
Due to fact that BAPI structures uses different field names than standard SAP tables I used to apply a trick I’m going to present in this article – map BAPI fileds to SAP fields in a Z-table and fill BAPI structures dynamically during runtime<\/p>\nDue to fact that BAPI structures uses different field names than standard SAP tables I used to apply a trick I’m going to present in this article – map BAPI fileds to SAP fields in a Z-table and fill BAPI structures dynamically during runtime<\/p>\n
In this article we will use as an example BAPI structure and SAP table for material master global data<\/p>\n
At first we create a mapping table in the following format with some example data – it can be of course extended with further info you might find usefull, but we will use it in this simple format just to demonstrate the approach. Let’s call it Z_BAPIMAP<\/em><\/p>\n When it comes to code filling the BAPI from SAP structures, you can encapsulate it to a nice class method, function module or a form – I’ll present a form\/perform code.<\/p>\n Now we can call our new FORM to fill a BAPI structure from a SAP structure:<\/p>\n Due to fact that BAPI structures uses different field names than standard SAP tables I used to apply a trick I’m going to present in this article – map BAPI fileds to SAP fields in a Z-table and fill BAPI … Continue reading \n\n
\n \nTABNAME<\/th>\n FIELDNAME<\/th>\n BAPIFIELD<\/th>\n<\/tr>\n<\/thead>\n \n MARA<\/td>\n MSTAE<\/td>\n PURCH_STATUS<\/td>\n<\/tr>\n \n MARA<\/td>\n MATKL<\/td>\n MATL_GROUP<\/td>\n<\/tr>\n \n MARA<\/td>\n NTGEW<\/td>\n NET_WEIGHT<\/td>\n<\/tr>\n \n MARA<\/td>\n GEWEI<\/td>\n UNIT_OF_WT<\/td>\n<\/tr>\n \n MARC<\/td>\n MINBE<\/td>\n REORDER_PT<\/td>\n<\/tr>\n \n MARC<\/td>\n EISBE<\/td>\n SAFETY_STK<\/td>\n<\/tr>\n \n MARC<\/td>\n BSTMI<\/td>\n MIN_LOT_SIZE<\/td>\n<\/tr>\n \n MARC<\/td>\n BSTMA<\/td>\n MAX_LOT_SIZE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n FORM fill_bapi \r\n USING i_source_line TYPE any\r\n i_tabname TYPE tabname16\r\n CHANGING\r\n c_bapi TYPE any\r\n c_bapix TYPE any.\r\n\r\n DATA:\r\n lt_mapping TYPE TABLE OF z_bapimap.\r\n\r\n FIELD-SYMBOLS:\r\n <fs_bapimap> TYPE z_bapimap,\r\n <fs_source_field> TYPE any,\r\n <fs_bapi_field> TYPE any,\r\n <fs_bapi_fieldx> TYPE any.\r\n\r\n* The following SELECT command can be done \r\n* on global scope and here only global itab would be accessed\r\n SELECT * \r\n INTO TABLE lt_mapping\r\n FROM z_bapimap\r\n WHERE tabname = i_tabname.\r\n\r\n LOOP AT lt_mapping ASSIGNING <fs_bapimap>.\r\n\r\n ASSIGN COMPONENT <fs_bapimap>-fieldname OF STRUCTURE i_source_line TO <fs_source_field>.\r\n CHECK <fs_source_field> IS ASSIGNED.\r\n\r\n* Uncomment the following line in case you don't want blank \r\n* values to be sent to SAP\r\n* CHECK <fs_source_field> IS NOT INITIAL. \r\n\r\n ASSIGN COMPONENT <fs_bapimap>-bapifield OF STRUCTURE c_bapi TO <fs_bapi_field>.\r\n ASSIGN COMPONENT <fs_bapimap>-bapifield OF STRUCTURE c_bapix TO <fs_bapi_fieldx>.\r\n CHECK <fs_bapi_field> IS ASSIGNED AND\r\n <fs_bapi_fieldx> IS ASSIGNED.\r\n\r\n <fs_bapi_field> = <fs_source_field>.\r\n <fs_bapi_fieldx> = 'X'. \r\n\r\n ENDLOOP.\r\n\r\nENDFORM.<\/pre>\n
FORM update_material\r\n USING i_mara TYPE mara.\r\n\r\n DATA:\r\n l_bapi_mara TYPE bapi_mara,\r\n l_bapi_marax TYPE bapi_marax.\r\n\r\n PERFORM fill_bapi\r\n USING i_mara\r\n 'MARA'\r\n CHANGING l_bapi_bara\r\n l_bapi_marax. \r\n\r\n* ... The rest of code for update material\r\n* i.e. Call the BAPI function module ...\r\n* ...and Rollback\/Commit work :-)\r\n\r\nENDFORM.<\/pre>\n","protected":false},"excerpt":{"rendered":"