SAP FSBP_TC_API_APPL_DATA_WRITE Function Module for









FSBP_TC_API_APPL_DATA_WRITE is a standard fsbp tc api appl data write 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 api appl data write FM, simply by entering the name FSBP_TC_API_APPL_DATA_WRITE into the relevant SAP transaction such as SE37 or SE38.

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



Function FSBP_TC_API_APPL_DATA_WRITE 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_API_APPL_DATA_WRITE'"
  EXPORTING
   I_APPL =  "Application
   I_TAB_TRANSFER =  "Data Structure
*  I_FLG_COMMIT_WORK =  "COMMIT WORK - Perform Command
*  I_LOCAL_MODE =  "Local Mode = No Business Partner Conversion Using BPID0001
*  I_STR_GENERAL =  "FS-BP: BAPI Structure for General Switches and Data
*  I_TESTRUN =  "Single-Character Flag
*  I_TRACE =  "Return Extended Log

 IMPORTING
   E_TAB_TRANSFER_ERROR =  "Table Type for Transfer Structure
   E_TAB_RETURN =  "Return Table

EXCEPTIONS
   ERROR_APPLICATION = 1
.



IMPORTING Parameters details for FSBP_TC_API_APPL_DATA_WRITE

I_APPL - Application

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

I_TAB_TRANSFER - Data Structure

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

I_FLG_COMMIT_WORK - COMMIT WORK - Perform Command

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

I_LOCAL_MODE - Local Mode = No Business Partner Conversion Using BPID0001

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

I_STR_GENERAL - FS-BP: BAPI Structure for General Switches and Data

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

I_TESTRUN - Single-Character Flag

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

I_TRACE - Return Extended Log

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

EXPORTING Parameters details for FSBP_TC_API_APPL_DATA_WRITE

E_TAB_TRANSFER_ERROR - Table Type for Transfer Structure

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

E_TAB_RETURN - Return Table

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

EXCEPTIONS details

ERROR_APPLICATION - Application Inactive or Not Defined etc.

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FSBP_TC_API_APPL_DATA_WRITE 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_appl  TYPE BP_TC_DTE_APPL, "   
lv_error_application  TYPE BP_TC_DTE_APPL, "   
lv_e_tab_transfer_error  TYPE FSBP_TC_TTY_TRANSFER, "   
lv_e_tab_return  TYPE BAPIRET2_T, "   
lv_i_tab_transfer  TYPE FSBP_TC_TTY_TRANSFER, "   
lv_i_flg_commit_work  TYPE XFELD, "   
lv_i_local_mode  TYPE XFELD, "   
lv_i_str_general  TYPE BUSISB990_GEN, "   
lv_i_testrun  TYPE CHAR1, "   
lv_i_trace  TYPE XPROT. "   

  CALL FUNCTION 'FSBP_TC_API_APPL_DATA_WRITE'  "
    EXPORTING
         I_APPL = lv_i_appl
         I_TAB_TRANSFER = lv_i_tab_transfer
         I_FLG_COMMIT_WORK = lv_i_flg_commit_work
         I_LOCAL_MODE = lv_i_local_mode
         I_STR_GENERAL = lv_i_str_general
         I_TESTRUN = lv_i_testrun
         I_TRACE = lv_i_trace
    IMPORTING
         E_TAB_TRANSFER_ERROR = lv_e_tab_transfer_error
         E_TAB_RETURN = lv_e_tab_return
    EXCEPTIONS
        ERROR_APPLICATION = 1
. " FSBP_TC_API_APPL_DATA_WRITE




ABAP code using 7.40 inline data declarations to call FM FSBP_TC_API_APPL_DATA_WRITE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!