SAP MAP2I_BAPI_ORDER_HEADER_TO_PMS Function Module for NOTRANSL: bapi_order_header -> pmsdo
MAP2I_BAPI_ORDER_HEADER_TO_PMS is a standard map2i bapi order header to pms 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: bapi_order_header -> pmsdo 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 map2i bapi order header to pms FM, simply by entering the name MAP2I_BAPI_ORDER_HEADER_TO_PMS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRMO
Program Name: SAPLCRMO
Main Program: SAPLCRMO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2I_BAPI_ORDER_HEADER_TO_PMS 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 'MAP2I_BAPI_ORDER_HEADER_TO_PMS'"NOTRANSL: bapi_order_header -> pmsdo.
EXPORTING
BAPI_ORDER_HEADER = "Mobile Service: Order Header
CHANGING
PMSDO = "PM organizational data for SD documents
EXCEPTIONS
ERROR_CONVERTING_ISO_CODE = 1
IMPORTING Parameters details for MAP2I_BAPI_ORDER_HEADER_TO_PMS
BAPI_ORDER_HEADER - Mobile Service: Order Header
Data type: BAPI_ORDER_HEADEROptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2I_BAPI_ORDER_HEADER_TO_PMS
PMSDO - PM organizational data for SD documents
Data type: PMSDOOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_CONVERTING_ISO_CODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MAP2I_BAPI_ORDER_HEADER_TO_PMS 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: | ||||
| lv_pmsdo | TYPE PMSDO, " | |||
| lv_bapi_order_header | TYPE BAPI_ORDER_HEADER, " | |||
| lv_error_converting_iso_code | TYPE BAPI_ORDER_HEADER. " |
|   CALL FUNCTION 'MAP2I_BAPI_ORDER_HEADER_TO_PMS' "NOTRANSL: bapi_order_header -> pmsdo |
| EXPORTING | ||
| BAPI_ORDER_HEADER | = lv_bapi_order_header | |
| CHANGING | ||
| PMSDO | = lv_pmsdo | |
| EXCEPTIONS | ||
| ERROR_CONVERTING_ISO_CODE = 1 | ||
| . " MAP2I_BAPI_ORDER_HEADER_TO_PMS | ||
ABAP code using 7.40 inline data declarations to call FM MAP2I_BAPI_ORDER_HEADER_TO_PMS
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