GET_RULE SAP Function module - Get Billing Method Posting Rules

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

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

Pattern for FM GET_RULE - GET RULE

CALL FUNCTION 'GET_RULE' "Get Billing Method Posting Rules
  EXPORTING
    i_billing_method =          " t8j0f-bmethod  Billing Method
    i_company =                 " t8j0f-bukrs
    i_jvfunc =                  " t8j0f-jvfunc  Joint Venture Function
  IMPORTING
    e_record_t8j0f =            "               Export: Table T8J0F Field String
  EXCEPTIONS
    INV_BILLMETH = 1            "               Invalid Billing Method
    INV_FUNCTION = 2            "               Invalid JV Function
    NO_POSTING_RULE = 3         "               No Posting Rules Found
    NO_RULE_DETAIL = 4          "               No Rule Details Found
    .  "  GET_RULE

ABAP code example for Function Module GET_RULE

The ABAP code below is a full code listing to execute function module GET_RULE 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_e_record_t8j0f  
 
 TYPE STRING
.

 

SELECT single BMETHOD 
  FROM T8J0F 
  INTO @DATA(ld_i_billing_method).

 

SELECT single BUKRS 
  FROM T8J0F 
  INTO @DATA(ld_i_company).

 

SELECT single JVFUNC 
  FROM T8J0F 
  INTO @DATA(ld_i_jvfunc).

.

CALL FUNCTION 'GET_RULE'
  EXPORTING
    i_billing_method =           ld_i_billing_method
    i_company =                  ld_i_company
    i_jvfunc =                   ld_i_jvfunc
  IMPORTING
    e_record_t8j0f =             ld_e_record_t8j0f
  EXCEPTIONS
    INV_BILLMETH =               1
    INV_FUNCTION =               2
    NO_POSTING_RULE =            3
    NO_RULE_DETAIL =             4
    .  "  GET_RULE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_e_record_t8j0f
 
 TYPE STRING ,
ld_i_billing_method
 
 TYPE T8J0F-BMETHOD ,
ld_i_company
 
 TYPE T8J0F-BUKRS ,
ld_i_jvfunc
 
 TYPE T8J0F-JVFUNC .



SELECT single BMETHOD 
  FROM T8J0F 
  INTO ld_i_billing_method.


SELECT single BUKRS 
  FROM T8J0F 
  INTO ld_i_company.


SELECT single JVFUNC 
  FROM T8J0F 
  INTO ld_i_jvfunc.