SAP MAP_MAKT_TO_BAPIMTCS Function Module for NOTRANSL: MAKT-Daten in die Übergabestruktur schreiben
MAP_MAKT_TO_BAPIMTCS is a standard map makt to bapimtcs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: MAKT-Daten in die Übergabestruktur schreiben processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for map makt to bapimtcs FM, simply by entering the name MAP_MAKT_TO_BAPIMTCS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM1
Program Name: SAPLCRM1
Main Program: SAPLCRM1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP_MAKT_TO_BAPIMTCS pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'MAP_MAKT_TO_BAPIMTCS'"NOTRANSL: MAKT-Daten in die Übergabestruktur schreiben.
EXPORTING
I_BAPICRMDH2 = "BAPI Structure for Downloading Header Data
CHANGING
P_CURRDNO = "Number of current data segment
TABLES
* TI_MAKT = "Material Descriptions
TI_DELTOP = "Operation per Data Record for Delta Download
TO_BAPIMTCSIT = "Middleware Transaction Container Structure
TO_BAPIMTCS = "Middleware Transaction Container Structure
IMPORTING Parameters details for MAP_MAKT_TO_BAPIMTCS
I_BAPICRMDH2 - BAPI Structure for Downloading Header Data
Data type: BAPICRMDH2Optional: No
Call by Reference: Yes
CHANGING Parameters details for MAP_MAKT_TO_BAPIMTCS
P_CURRDNO - Number of current data segment
Data type: CURRDNOOptional: No
Call by Reference: Yes
TABLES Parameters details for MAP_MAKT_TO_BAPIMTCS
TI_MAKT - Material Descriptions
Data type: MAKTOptional: Yes
Call by Reference: Yes
TI_DELTOP - Operation per Data Record for Delta Download
Data type: TABKEYOPOptional: No
Call by Reference: Yes
TO_BAPIMTCSIT - Middleware Transaction Container Structure
Data type: BAPIMTCSOptional: No
Call by Reference: Yes
TO_BAPIMTCS - Middleware Transaction Container Structure
Data type: BAPIMTCSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP_MAKT_TO_BAPIMTCS Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lt_ti_makt | TYPE STANDARD TABLE OF MAKT, " | |||
| lv_p_currdno | TYPE CURRDNO, " | |||
| lv_i_bapicrmdh2 | TYPE BAPICRMDH2, " | |||
| lt_ti_deltop | TYPE STANDARD TABLE OF TABKEYOP, " | |||
| lt_to_bapimtcsit | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
| lt_to_bapimtcs | TYPE STANDARD TABLE OF BAPIMTCS. " |
|   CALL FUNCTION 'MAP_MAKT_TO_BAPIMTCS' "NOTRANSL: MAKT-Daten in die Übergabestruktur schreiben |
| EXPORTING | ||
| I_BAPICRMDH2 | = lv_i_bapicrmdh2 | |
| CHANGING | ||
| P_CURRDNO | = lv_p_currdno | |
| TABLES | ||
| TI_MAKT | = lt_ti_makt | |
| TI_DELTOP | = lt_ti_deltop | |
| TO_BAPIMTCSIT | = lt_to_bapimtcsit | |
| TO_BAPIMTCS | = lt_to_bapimtcs | |
| . " MAP_MAKT_TO_BAPIMTCS | ||
ABAP code using 7.40 inline data declarations to call FM MAP_MAKT_TO_BAPIMTCS
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects