SAP BBP_PDC_TP_PT_READ Function Module for Read all purchasing teams
BBP_PDC_TP_PT_READ is a standard bbp pdc tp pt read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read all purchasing teams 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 pdc tp pt read FM, simply by entering the name BBP_PDC_TP_PT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDC_TP
Program Name: SAPLBBP_PDC_TP
Main Program: SAPLBBP_PDC_TP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BBP_PDC_TP_PT_READ 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_PDC_TP_PT_READ'"Read all purchasing teams.
EXPORTING
IV_LANGUAGE = "Language ID (ISO Standard)
IMPORTING
ET_PURCHTEAMS = "BBP Team Purchasing Texts (language dependent)
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for BBP_PDC_TP_PT_READ
IV_LANGUAGE - Language ID (ISO Standard)
Data type: SYLANGUOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_PDC_TP_PT_READ
ET_PURCHTEAMS - BBP Team Purchasing Texts (language dependent)
Data type: BBPT_SC_APP_PT_TEXTOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR - System error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_PDC_TP_PT_READ 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_iv_language | TYPE SYLANGU, " | |||
lv_et_purchteams | TYPE BBPT_SC_APP_PT_TEXT, " | |||
lv_internal_error | TYPE BBPT_SC_APP_PT_TEXT. " |
  CALL FUNCTION 'BBP_PDC_TP_PT_READ' "Read all purchasing teams |
EXPORTING | ||
IV_LANGUAGE | = lv_iv_language | |
IMPORTING | ||
ET_PURCHTEAMS | = lv_et_purchteams | |
EXCEPTIONS | ||
INTERNAL_ERROR = 1 | ||
. " BBP_PDC_TP_PT_READ |
ABAP code using 7.40 inline data declarations to call FM BBP_PDC_TP_PT_READ
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