SAP BBP_CUSTOMIZING_VENDOR_GET_31 Function Module for NOTRANSL: used to get content of T052, T042Z, T008, T003, T047U, T8JW and
BBP_CUSTOMIZING_VENDOR_GET_31 is a standard bbp customizing vendor get 31 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: used to get content of T052, T042Z, T008, T003, T047U, T8JW and 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 bbp customizing vendor get 31 FM, simply by entering the name BBP_CUSTOMIZING_VENDOR_GET_31 into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBPA
Program Name: SAPLBBPA
Main Program: SAPLBBPA
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_CUSTOMIZING_VENDOR_GET_31 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 'BBP_CUSTOMIZING_VENDOR_GET_31'"NOTRANSL: used to get content of T052, T042Z, T008, T003, T047U, T8JW and.
EXPORTING
* TABLE_NAME = "
TABLES
* BBP_T003 = "Document Types
* BBP_T615 = "
* BBP_T618 = "
* BBP_T008 = "Blocking Reasons for Automatic Payment Transcations
* BBP_T042Z = "Payment methods for automatic payment
* BBP_T052 = "Terms of Payment
* BBP_T052U = "
* BBP_T074U = "Special G/L Indicator Properties
* BBP_T8JW = "
* BBP_TQ02B = "
* BBP_TQ02U = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLBBPA_001 change acc object for budget
IMPORTING Parameters details for BBP_CUSTOMIZING_VENDOR_GET_31
TABLE_NAME -
Data type: DD02D-TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_CUSTOMIZING_VENDOR_GET_31
BBP_T003 - Document Types
Data type: T003Optional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T615 -
Data type: T615Optional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T618 -
Data type: T618Optional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T008 - Blocking Reasons for Automatic Payment Transcations
Data type: T008Optional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T042Z - Payment methods for automatic payment
Data type: T042ZOptional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T052 - Terms of Payment
Data type: T052Optional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T052U -
Data type: T052UOptional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T074U - Special G/L Indicator Properties
Data type: T074UOptional: Yes
Call by Reference: No ( called with pass by value option)
BBP_T8JW -
Data type: T8JWOptional: Yes
Call by Reference: No ( called with pass by value option)
BBP_TQ02B -
Data type: TQ02BOptional: Yes
Call by Reference: No ( called with pass by value option)
BBP_TQ02U -
Data type: TQ02UOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_CUSTOMIZING_VENDOR_GET_31 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: | ||||
| lt_bbp_t003 | TYPE STANDARD TABLE OF T003, " | |||
| lv_table_name | TYPE DD02D-TABNAME, " | |||
| lt_bbp_t615 | TYPE STANDARD TABLE OF T615, " | |||
| lt_bbp_t618 | TYPE STANDARD TABLE OF T618, " | |||
| lt_bbp_t008 | TYPE STANDARD TABLE OF T008, " | |||
| lt_bbp_t042z | TYPE STANDARD TABLE OF T042Z, " | |||
| lt_bbp_t052 | TYPE STANDARD TABLE OF T052, " | |||
| lt_bbp_t052u | TYPE STANDARD TABLE OF T052U, " | |||
| lt_bbp_t074u | TYPE STANDARD TABLE OF T074U, " | |||
| lt_bbp_t8jw | TYPE STANDARD TABLE OF T8JW, " | |||
| lt_bbp_tq02b | TYPE STANDARD TABLE OF TQ02B, " | |||
| lt_bbp_tq02u | TYPE STANDARD TABLE OF TQ02U. " |
|   CALL FUNCTION 'BBP_CUSTOMIZING_VENDOR_GET_31' "NOTRANSL: used to get content of T052, T042Z, T008, T003, T047U, T8JW and |
| EXPORTING | ||
| TABLE_NAME | = lv_table_name | |
| TABLES | ||
| BBP_T003 | = lt_bbp_t003 | |
| BBP_T615 | = lt_bbp_t615 | |
| BBP_T618 | = lt_bbp_t618 | |
| BBP_T008 | = lt_bbp_t008 | |
| BBP_T042Z | = lt_bbp_t042z | |
| BBP_T052 | = lt_bbp_t052 | |
| BBP_T052U | = lt_bbp_t052u | |
| BBP_T074U | = lt_bbp_t074u | |
| BBP_T8JW | = lt_bbp_t8jw | |
| BBP_TQ02B | = lt_bbp_tq02b | |
| BBP_TQ02U | = lt_bbp_tq02u | |
| . " BBP_CUSTOMIZING_VENDOR_GET_31 | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CUSTOMIZING_VENDOR_GET_31
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.| "SELECT single TABNAME FROM DD02D INTO @DATA(ld_table_name). | ||||
Search for further information about these or an SAP related objects