SAP FTBP_READ_BP1040 Function Module for Business Partner: Read Regulatory Reporting Data

Search SAP Function Modules

FTBP_READ_BP1040 is a standard ftbp read bp1040 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Business Partner: Read Regulatory Reporting Data 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 ftbp read bp1040 FM, simply by entering the name FTBP_READ_BP1040 into the relevant SAP transaction such as SE37 or SE38.

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

Function FTBP_READ_BP1040 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 'FTBP_READ_BP1040'"Business Partner: Read Regulatory Reporting Data
  EXPORTING
   I_PARTNR =  "Business Partner Number
*  I_BUKRS =  "Company Code
*  I_DB =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_XMEMORY =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_XWA =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

 IMPORTING
   E_BP1040 =  "Business Partner: Reporting Data in Company Code

TABLES
*  T_BP1040 =  "Business Partner: Reporting Data in Company Code

EXCEPTIONS
   WRONG_PARAMETERS = 1    NOT_FOUND = 2 

.

IMPORTING Parameters details for FTBP_READ_BP1040

I_PARTNR - Business Partner Number

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

I_BUKRS - Company Code

Data type: BUKRS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DB - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XMEMORY - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XWA - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FTBP_READ_BP1040

E_BP1040 - Business Partner: Reporting Data in Company Code

Data type: BP1040
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FTBP_READ_BP1040

T_BP1040 - Business Partner: Reporting Data in Company Code

Data type: BP1040
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

WRONG_PARAMETERS - Incorrect parameters

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND - Data Not Found

Data type:
Optional: No
Call by Reference: Yes

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

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