SAP ISP_LIEFBAR_GP_ZUORDNUNG Function Module for IS-M/SD: Assign Business Partner to Delivery Viability Sets (Researcher)









ISP_LIEFBAR_GP_ZUORDNUNG is a standard isp liefbar gp zuordnung SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Assign Business Partner to Delivery Viability Sets (Researcher) 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 isp liefbar gp zuordnung FM, simply by entering the name ISP_LIEFBAR_GP_ZUORDNUNG into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_LIEFBAR_GP_ZUORDNUNG 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 'ISP_LIEFBAR_GP_ZUORDNUNG'"IS-M/SD: Assign Business Partner to Delivery Viability Sets (Researcher)
EXPORTING
* BIS_DATUM = CON_TIME_INFINITY "To-Date
* GPRECH = ' ' "Researcher
LOC_RJV1001 = "
TRTYP = "
* VERSERVGES = ' ' "
* VON_DATUM = CON_TIME_BEGIN "From Date
* X_MIT_COMMIT = CON_ANGEKREUZT "

IMPORTING
EXP_OK_CODE = "

TABLES
GP_DATEN_TAB = "
LIEFBAR_TAB = "
.



IMPORTING Parameters details for ISP_LIEFBAR_GP_ZUORDNUNG

BIS_DATUM - To-Date

Data type: JVTBEZGP-GUELTIGBIS
Default: CON_TIME_INFINITY
Optional: Yes
Call by Reference: No ( called with pass by value option)

GPRECH - Researcher

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

LOC_RJV1001 -

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

TRTYP -

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

VERSERVGES -

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

VON_DATUM - From Date

Data type: JVTBEZGP-GUELTIGAB
Default: CON_TIME_BEGIN
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_MIT_COMMIT -

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

EXPORTING Parameters details for ISP_LIEFBAR_GP_ZUORDNUNG

EXP_OK_CODE -

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

TABLES Parameters details for ISP_LIEFBAR_GP_ZUORDNUNG

GP_DATEN_TAB -

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

LIEFBAR_TAB -

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

Copy and paste ABAP code example for ISP_LIEFBAR_GP_ZUORDNUNG 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_bis_datum  TYPE JVTBEZGP-GUELTIGBIS, "   CON_TIME_INFINITY
lv_exp_ok_code  TYPE JVTBEZGP, "   
lt_gp_daten_tab  TYPE STANDARD TABLE OF RJV1301, "   
lv_gprech  TYPE RJV13-GPRECH, "   SPACE
lt_liefbar_tab  TYPE STANDARD TABLE OF RJV1003, "   
lv_loc_rjv1001  TYPE RJV1001, "   
lv_trtyp  TYPE TJ180-TRTYP, "   
lv_verservges  TYPE RJV13-VSGRCHEUR, "   SPACE
lv_von_datum  TYPE JVTBEZGP-GUELTIGAB, "   CON_TIME_BEGIN
lv_x_mit_commit  TYPE JVTBEZGP. "   CON_ANGEKREUZT

  CALL FUNCTION 'ISP_LIEFBAR_GP_ZUORDNUNG'  "IS-M/SD: Assign Business Partner to Delivery Viability Sets (Researcher)
    EXPORTING
         BIS_DATUM = lv_bis_datum
         GPRECH = lv_gprech
         LOC_RJV1001 = lv_loc_rjv1001
         TRTYP = lv_trtyp
         VERSERVGES = lv_verservges
         VON_DATUM = lv_von_datum
         X_MIT_COMMIT = lv_x_mit_commit
    IMPORTING
         EXP_OK_CODE = lv_exp_ok_code
    TABLES
         GP_DATEN_TAB = lt_gp_daten_tab
         LIEFBAR_TAB = lt_liefbar_tab
. " ISP_LIEFBAR_GP_ZUORDNUNG




ABAP code using 7.40 inline data declarations to call FM ISP_LIEFBAR_GP_ZUORDNUNG

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 GUELTIGBIS FROM JVTBEZGP INTO @DATA(ld_bis_datum).
DATA(ld_bis_datum) = CON_TIME_INFINITY.
 
 
 
"SELECT single GPRECH FROM RJV13 INTO @DATA(ld_gprech).
DATA(ld_gprech) = ' '.
 
 
 
"SELECT single TRTYP FROM TJ180 INTO @DATA(ld_trtyp).
 
"SELECT single VSGRCHEUR FROM RJV13 INTO @DATA(ld_verservges).
DATA(ld_verservges) = ' '.
 
"SELECT single GUELTIGAB FROM JVTBEZGP INTO @DATA(ld_von_datum).
DATA(ld_von_datum) = CON_TIME_BEGIN.
 
DATA(ld_x_mit_commit) = CON_ANGEKREUZT.
 


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!