SAP ISB_TR_PARTNER_EXT_COMPLETE Function Module for NOTRANSL: TR-FDÜ: Komplettieren GP-Daten









ISB_TR_PARTNER_EXT_COMPLETE is a standard isb tr partner ext complete 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: TR-FDÜ: Komplettieren GP-Daten 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 isb tr partner ext complete FM, simply by entering the name ISB_TR_PARTNER_EXT_COMPLETE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISB_TR_PARTNER_EXT_COMPLETE 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 'ISB_TR_PARTNER_EXT_COMPLETE'"NOTRANSL: TR-FDÜ: Komplettieren GP-Daten
EXPORTING
* I_TEST_RUN = ' ' "ABAP System Field: Background Processing Active

TABLES
ERROR_ITAB = "IS-B: Interface for Error Handling
PARTNER_ITAB = "TR Business partner transfer with internal fields

EXCEPTIONS
ERROR_FOUND = 1
.



IMPORTING Parameters details for ISB_TR_PARTNER_EXT_COMPLETE

I_TEST_RUN - ABAP System Field: Background Processing Active

Data type: SY-BATCH
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISB_TR_PARTNER_EXT_COMPLETE

ERROR_ITAB - IS-B: Interface for Error Handling

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

PARTNER_ITAB - TR Business partner transfer with internal fields

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

EXCEPTIONS details

ERROR_FOUND -

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

Copy and paste ABAP code example for ISB_TR_PARTNER_EXT_COMPLETE 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_error_itab  TYPE STANDARD TABLE OF SPROT_X, "   
lv_i_test_run  TYPE SY-BATCH, "   SPACE
lv_error_found  TYPE SY, "   
lt_partner_itab  TYPE STANDARD TABLE OF JBIUPPA1. "   

  CALL FUNCTION 'ISB_TR_PARTNER_EXT_COMPLETE'  "NOTRANSL: TR-FDÜ: Komplettieren GP-Daten
    EXPORTING
         I_TEST_RUN = lv_i_test_run
    TABLES
         ERROR_ITAB = lt_error_itab
         PARTNER_ITAB = lt_partner_itab
    EXCEPTIONS
        ERROR_FOUND = 1
. " ISB_TR_PARTNER_EXT_COMPLETE




ABAP code using 7.40 inline data declarations to call FM ISB_TR_PARTNER_EXT_COMPLETE

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 BATCH FROM SY INTO @DATA(ld_i_test_run).
DATA(ld_i_test_run) = ' '.
 
 
 


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!