EXIT_SAPMV45A_001 SAP Function module - User Exit for Determining the Billing Plan Type

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

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

Pattern for FM EXIT_SAPMV45A_001 - EXIT SAPMV45A 001

CALL FUNCTION 'EXIT_SAPMV45A_001' "User Exit for Determining the Billing Plan Type
  EXPORTING
    ivbak =                     " vbak          Order Header
*   ivbap =                     " vbap          Order Item
    ivbkd =                     " vbkd          Business Data (Header or Item)
    itvak =                     " tvak          Sales DOcuments: Types (VVAK)
*   itvap =                     " tvap          Sales Documents: Item Categories (TVAP)
  CHANGING
    billingplantype =           " tvap-fpart    Billing Plan Type
    .  "  EXIT_SAPMV45A_001

ABAP code example for Function Module EXIT_SAPMV45A_001

The ABAP code below is a full code listing to execute function module EXIT_SAPMV45A_001 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).

 

SELECT single FPART 
  FROM TVAP 
  INTO @DATA(ld_billingplantype).


DATA(ld_ivbak) = 'Check type of data required'.

DATA(ld_ivbap) = 'Check type of data required'.

DATA(ld_ivbkd) = 'Check type of data required'.

DATA(ld_itvak) = 'Check type of data required'.

DATA(ld_itvap) = 'Check type of data required'.
.

CALL FUNCTION 'EXIT_SAPMV45A_001'
  EXPORTING
    ivbak =                      ld_ivbak
*   ivbap =                      ld_ivbap
    ivbkd =                      ld_ivbkd
    itvak =                      ld_itvak
*   itvap =                      ld_itvap
  CHANGING
    billingplantype =            ld_billingplantype
    .  "  EXIT_SAPMV45A_001

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_billingplantype
 
 TYPE TVAP-FPART ,
ld_ivbak
 
 TYPE VBAK ,
ld_ivbap
 
 TYPE VBAP ,
ld_ivbkd
 
 TYPE VBKD ,
ld_itvak
 
 TYPE TVAK ,
ld_itvap
 
 TYPE TVAP .



SELECT single FPART 
  FROM TVAP 
  INTO ld_billingplantype.

ld_ivbak = 'Check type of data required'.
ld_ivbap = 'Check type of data required'.
ld_ivbkd = 'Check type of data required'.
ld_itvak = 'Check type of data required'.
ld_itvap = 'Check type of data required'.