ISP_REPLACE_GP_BEZRUNDE SAP Function module - IS-M/SD: Replace Business Partner in BP Assignment to Delivery Rounds

ISP_REPLACE_GP_BEZRUNDE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISP_REPLACE_GP_BEZRUNDE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JV10
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISP_REPLACE_GP_BEZRUNDE - ISP REPLACE GP BEZRUNDE

CALL FUNCTION 'ISP_REPLACE_GP_BEZRUNDE' "IS-M/SD: Replace Business Partner in BP Assignment to Delivery Rounds
  EXPORTING
    verservges =                " rjv04-verservges  Service company
    jgpartner =                 " rjv04-zusteller  Business partner
    von_datum =                 " jvtbezgp-gueltigab  From Date
    bis_datum =                 " jvtbezgp-gueltigbis  To-Date
    trtyp =                     " tj180-trtyp   Transaction type for access
*   x_enable_update = SPACE     "               Activating 'Save' function
*   x_mit_commit =              "               COMMIT WORK is performed when you save
*   x_ro_zu = CON_ANGEKREUZT    " rjv04-x_ro_zu  Carrier Role
*   x_ro_ik = CON_ANGEKREUZT    " rjv04-x_ro_ik  Function 'Field collector'
  IMPORTING
    exp_ok_code =               "               OK code when exiting
  EXCEPTIONS
    WRONG_PARAMETER = 1         "               Substitution can only take place for ONE carrier
    .  "  ISP_REPLACE_GP_BEZRUNDE

ABAP code example for Function Module ISP_REPLACE_GP_BEZRUNDE

The ABAP code below is a full code listing to execute function module ISP_REPLACE_GP_BEZRUNDE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_exp_ok_code  
 
 TYPE STRING
.



DATA(ld_verservges) = some text here


DATA(ld_jgpartner) = some text here
 

SELECT single GUELTIGAB 
  FROM JVTBEZGP 
  INTO @DATA(ld_von_datum).

 

SELECT single GUELTIGBIS 
  FROM JVTBEZGP 
  INTO @DATA(ld_bis_datum).

 

SELECT single TRTYP 
  FROM TJ180 
  INTO @DATA(ld_trtyp).


DATA(ld_x_enable_update) = 'some text here'.

DATA(ld_x_mit_commit) = 'some text here'.


DATA(ld_x_ro_zu) = some text here


DATA(ld_x_ro_ik) = some text here
.

CALL FUNCTION 'ISP_REPLACE_GP_BEZRUNDE'
  EXPORTING
    verservges =                 ld_verservges
    jgpartner =                  ld_jgpartner
    von_datum =                  ld_von_datum
    bis_datum =                  ld_bis_datum
    trtyp =                      ld_trtyp
*   x_enable_update =            ld_x_enable_update
*   x_mit_commit =               ld_x_mit_commit
*   x_ro_zu =                    ld_x_ro_zu
*   x_ro_ik =                    ld_x_ro_ik
  IMPORTING
    exp_ok_code =                ld_exp_ok_code
  EXCEPTIONS
    WRONG_PARAMETER =            1
    .  "  ISP_REPLACE_GP_BEZRUNDE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_exp_ok_code
 
 TYPE STRING ,
ld_verservges
 
 TYPE RJV04-VERSERVGES ,
ld_jgpartner
 
 TYPE RJV04-ZUSTELLER ,
ld_von_datum
 
 TYPE JVTBEZGP-GUELTIGAB ,
ld_bis_datum
 
 TYPE JVTBEZGP-GUELTIGBIS ,
ld_trtyp
 
 TYPE TJ180-TRTYP ,
ld_x_enable_update
 
 TYPE STRING ,
ld_x_mit_commit
 
 TYPE STRING ,
ld_x_ro_zu
 
 TYPE RJV04-X_RO_ZU ,
ld_x_ro_ik
 
 TYPE RJV04-X_RO_IK .



ld_verservges = some text here

ld_jgpartner = some text here

SELECT single GUELTIGAB 
  FROM JVTBEZGP 
  INTO ld_von_datum.


SELECT single GUELTIGBIS 
  FROM JVTBEZGP 
  INTO ld_bis_datum.


SELECT single TRTYP 
  FROM TJ180 
  INTO ld_trtyp.

ld_x_enable_update = 'some text here'.
ld_x_mit_commit = 'some text here'.

ld_x_ro_zu = some text here

ld_x_ro_ik = some text here