SAP MAP2E_CAUFVD_TO_HEADER_I Function Module for NOTRANSL: caufvd -> ibapi_header_in
MAP2E_CAUFVD_TO_HEADER_I is a standard map2e caufvd to header i 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: caufvd -> ibapi_header_in 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 map2e caufvd to header i FM, simply by entering the name MAP2E_CAUFVD_TO_HEADER_I into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBAPI_ALM_ORDER_MAPPING
Program Name: SAPLIBAPI_ALM_ORDER_MAPPING
Main Program: SAPLIBAPI_ALM_ORDER_MAPPING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2E_CAUFVD_TO_HEADER_I 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 'MAP2E_CAUFVD_TO_HEADER_I'"NOTRANSL: caufvd -> ibapi_header_in.
EXPORTING
CAUFVD = "
CHANGING
IBAPI_HEADER_IN = "Import Structure for ALM Order Header
IMPORTING Parameters details for MAP2E_CAUFVD_TO_HEADER_I
CAUFVD -
Data type: CAUFVDOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2E_CAUFVD_TO_HEADER_I
IBAPI_HEADER_IN - Import Structure for ALM Order Header
Data type: BAPI_ALM_ORDER_HEADER_IOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP2E_CAUFVD_TO_HEADER_I 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_caufvd | TYPE CAUFVD, " | |||
| lv_ibapi_header_in | TYPE BAPI_ALM_ORDER_HEADER_I. " |
|   CALL FUNCTION 'MAP2E_CAUFVD_TO_HEADER_I' "NOTRANSL: caufvd -> ibapi_header_in |
| EXPORTING | ||
| CAUFVD | = lv_caufvd | |
| CHANGING | ||
| IBAPI_HEADER_IN | = lv_ibapi_header_in | |
| . " MAP2E_CAUFVD_TO_HEADER_I | ||
ABAP code using 7.40 inline data declarations to call FM MAP2E_CAUFVD_TO_HEADER_I
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