SAP FDM_P2P_TRANSFER Function Module for

Search SAP Function Modules

FDM_P2P_TRANSFER is a standard fdm p2p transfer 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 transfer FM, simply by entering the name FDM_P2P_TRANSFER into the relevant SAP transaction such as SE37 or SE38.

Function Group: FDM_P2P_SERVICES
Program Name: SAPLFDM_P2P_SERVICES
Main Program: SAPLFDM_P2P_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FDM_P2P_TRANSFER 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_TRANSFER'"
  EXPORTING
   I_GUID =  "
   I_BUKRS =  "
   I_BELNR =  "
   I_GJAHR =  "
   I_BUZEI =  "
   I_KUNNR =  "
   I_OLD_OBJ_KEY =  "
*  I_XVBUP = 'X' "

 IMPORTING
   ES_RETURN =  "

EXCEPTIONS
   GET_NUMBER_FAILURE = 1 

.

IMPORTING Parameters details for FDM_P2P_TRANSFER

I_GUID -

Data type: BDM_CASE_GUID
Optional: No
Call by Reference: Yes

I_BUKRS -

Data type: BUKRS
Optional: No
Call by Reference: Yes

I_BELNR -

Data type: BELNR_D
Optional: No
Call by Reference: Yes

I_GJAHR -

Data type: GJAHR
Optional: No
Call by Reference: Yes

I_BUZEI -

Data type: BUZEI
Optional: No
Call by Reference: Yes

I_KUNNR -

Data type: KUNNR
Optional: No
Call by Reference: Yes

I_OLD_OBJ_KEY -

Data type: SWO_TYPEID
Optional: No
Call by Reference: Yes

I_XVBUP -

Data type: OFIWA-XVBUP
Default: 'X'
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FDM_P2P_TRANSFER

ES_RETURN -

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

EXCEPTIONS details

GET_NUMBER_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FDM_P2P_TRANSFER 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.

ABAP code using 7.40 inline data declarations to call FM FDM_P2P_TRANSFER

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