SAP FSBP_TC_READ_DATA Function Module for
FSBP_TC_READ_DATA is a standard fsbp tc read data 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 fsbp tc read data FM, simply by entering the name FSBP_TC_READ_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FSBP_TC_MAIN
Program Name: SAPLFSBP_TC_MAIN
Main Program: SAPLFSBP_TC_MAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FSBP_TC_READ_DATA 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 'FSBP_TC_READ_DATA'".
EXPORTING
* I_PARTNER = "Business Partner Number
* I_PARTNER_GUID = "Business Partner GUID
* I_CONTEXT = 'DEFAULT' "Call Context
* I_SELVAR = "Selection Variant
* I_CURRENCY = "Currency for Display
* I_LANGU = SY-LANGU "Display Language for Texts
* I_GROUP_NOT_ACTIVE = "
IMPORTING
E_TAB_HEADER = "Total Commitment: Header Information
E_TAB_ITEMS = "Total Commitment: Formatted Data for Contracts ('Items')
E_STR_SUM = "Total Commitment: Totals Structure (Totaled Values)
IMPORTING Parameters details for FSBP_TC_READ_DATA
I_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: Yes
I_PARTNER_GUID - Business Partner GUID
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: Yes
I_CONTEXT - Call Context
Data type: BP_TC_DTE_CONTEXTDefault: 'DEFAULT'
Optional: Yes
Call by Reference: Yes
I_SELVAR - Selection Variant
Data type: BP_TC_DTE_SELVAROptional: Yes
Call by Reference: Yes
I_CURRENCY - Currency for Display
Data type: WAERSOptional: Yes
Call by Reference: Yes
I_LANGU - Display Language for Texts
Data type: LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
I_GROUP_NOT_ACTIVE -
Data type: BP_TC_DTE_GROUP_NOT_ACTIVEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FSBP_TC_READ_DATA
E_TAB_HEADER - Total Commitment: Header Information
Data type: FSBP_TC_TTY_HEADEROptional: No
Call by Reference: Yes
E_TAB_ITEMS - Total Commitment: Formatted Data for Contracts ('Items')
Data type: FSBP_TC_TTY_ITEM_DISPOptional: No
Call by Reference: Yes
E_STR_SUM - Total Commitment: Totals Structure (Totaled Values)
Data type: FSBP_TC_STR_SUMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FSBP_TC_READ_DATA 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_i_partner | TYPE BU_PARTNER, " | |||
| lv_e_tab_header | TYPE FSBP_TC_TTY_HEADER, " | |||
| lv_e_tab_items | TYPE FSBP_TC_TTY_ITEM_DISP, " | |||
| lv_i_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_e_str_sum | TYPE FSBP_TC_STR_SUM, " | |||
| lv_i_context | TYPE BP_TC_DTE_CONTEXT, " 'DEFAULT' | |||
| lv_i_selvar | TYPE BP_TC_DTE_SELVAR, " | |||
| lv_i_currency | TYPE WAERS, " | |||
| lv_i_langu | TYPE LANGU, " SY-LANGU | |||
| lv_i_group_not_active | TYPE BP_TC_DTE_GROUP_NOT_ACTIVE. " |
|   CALL FUNCTION 'FSBP_TC_READ_DATA' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_PARTNER_GUID | = lv_i_partner_guid | |
| I_CONTEXT | = lv_i_context | |
| I_SELVAR | = lv_i_selvar | |
| I_CURRENCY | = lv_i_currency | |
| I_LANGU | = lv_i_langu | |
| I_GROUP_NOT_ACTIVE | = lv_i_group_not_active | |
| IMPORTING | ||
| E_TAB_HEADER | = lv_e_tab_header | |
| E_TAB_ITEMS | = lv_e_tab_items | |
| E_STR_SUM | = lv_e_str_sum | |
| . " FSBP_TC_READ_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FSBP_TC_READ_DATA
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.| DATA(ld_i_context) | = 'DEFAULT'. | |||
| DATA(ld_i_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects