ISP_CALL_AGENT_CONTRACT SAP Function module - IS-M/AM: Access Sales Agent Contract

ISP_CALL_AGENT_CONTRACT 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_CALL_AGENT_CONTRACT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ISP_CALL_AGENT_CONTRACT - ISP CALL AGENT CONTRACT

CALL FUNCTION 'ISP_CALL_AGENT_CONTRACT' "IS-M/AM: Access Sales Agent Contract
  EXPORTING
*   in_vtyp = SPACE             " jjtvv-vtyp
*   in_fcode = SPACE            " t185-fcode    Function Code
*   in_gv_flg_update = SPACE    " sy-batch
*   in_t185 = SPACE             " t185          Next screen contr.
*   in_t185f = SPACE            " t185f         Next screen contr.
*   in_t185v = SPACE            " t185v         Next screen contr.
    in_tj180 =                  " tj180         Next screen contr.
  IMPORTING
    out_gv_flg_update =         " sy-batch
    .  "  ISP_CALL_AGENT_CONTRACT

ABAP code example for Function Module ISP_CALL_AGENT_CONTRACT

The ABAP code below is a full code listing to execute function module ISP_CALL_AGENT_CONTRACT 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_out_gv_flg_update  
 
 TYPE SY-BATCH
.

 

SELECT single VTYP 
  FROM JJTVV 
  INTO @DATA(ld_in_vtyp).

 

SELECT single FCODE 
  FROM T185 
  INTO @DATA(ld_in_fcode).


DATA(ld_in_gv_flg_update) = 'some text here'.

DATA(ld_in_t185) = 'some text here'.

DATA(ld_in_t185f) = 'some text here'.

DATA(ld_in_t185v) = 'some text here'.

DATA(ld_in_tj180) = 'some text here'.
.

CALL FUNCTION 'ISP_CALL_AGENT_CONTRACT'
  EXPORTING
*   in_vtyp =                    ld_in_vtyp
*   in_fcode =                   ld_in_fcode
*   in_gv_flg_update =           ld_in_gv_flg_update
*   in_t185 =                    ld_in_t185
*   in_t185f =                   ld_in_t185f
*   in_t185v =                   ld_in_t185v
    in_tj180 =                   ld_in_tj180
  IMPORTING
    out_gv_flg_update =          ld_out_gv_flg_update
    .  "  ISP_CALL_AGENT_CONTRACT

IF SY-SUBRC EQ 0.
  "All OK
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_out_gv_flg_update
 
 TYPE SY-BATCH ,
ld_in_vtyp
 
 TYPE JJTVV-VTYP ,
ld_in_fcode
 
 TYPE T185-FCODE ,
ld_in_gv_flg_update
 
 TYPE SY-BATCH ,
ld_in_t185
 
 TYPE T185 ,
ld_in_t185f
 
 TYPE T185F ,
ld_in_t185v
 
 TYPE T185V ,
ld_in_tj180
 
 TYPE TJ180 .



SELECT single VTYP 
  FROM JJTVV 
  INTO ld_in_vtyp.


SELECT single FCODE 
  FROM T185 
  INTO ld_in_fcode.

ld_in_gv_flg_update = 'some text here'.
ld_in_t185 = 'some text here'.
ld_in_t185f = 'some text here'.
ld_in_t185v = 'some text here'.
ld_in_tj180 = 'some text here'.