SAP FDM_P2P_MAP_LOCAL_GEN2AR Function Module for
FDM_P2P_MAP_LOCAL_GEN2AR is a standard fdm p2p map local gen2ar SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fdm p2p map local gen2ar FM, simply by entering the name FDM_P2P_MAP_LOCAL_GEN2AR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDM_COLL_SERVICES_P2P
Program Name: SAPLFDM_COLL_SERVICES_P2P
Main Program: SAPLFDM_COLL_SERVICES_P2P
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FDM_P2P_MAP_LOCAL_GEN2AR 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 'FDM_P2P_MAP_LOCAL_GEN2AR'".
EXPORTING
IS_GEN_P2P_LOCAL = "Promise to Pay: Local Data
IMPORTING
ES_P2P_LOCAL = "Local Data of Promise to Pay
IMPORTING Parameters details for FDM_P2P_MAP_LOCAL_GEN2AR
IS_GEN_P2P_LOCAL - Promise to Pay: Local Data
Data type: FDM_GEN_P2P_LOCALOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FDM_P2P_MAP_LOCAL_GEN2AR
ES_P2P_LOCAL - Local Data of Promise to Pay
Data type: FDM_P2P_LOCALOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FDM_P2P_MAP_LOCAL_GEN2AR 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_es_p2p_local | TYPE FDM_P2P_LOCAL, " | |||
| lv_is_gen_p2p_local | TYPE FDM_GEN_P2P_LOCAL. " |
|   CALL FUNCTION 'FDM_P2P_MAP_LOCAL_GEN2AR' " |
| EXPORTING | ||
| IS_GEN_P2P_LOCAL | = lv_is_gen_p2p_local | |
| IMPORTING | ||
| ES_P2P_LOCAL | = lv_es_p2p_local | |
| . " FDM_P2P_MAP_LOCAL_GEN2AR | ||
ABAP code using 7.40 inline data declarations to call FM FDM_P2P_MAP_LOCAL_GEN2AR
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