SAP GET_POSTING_RULE Function Module for NOTRANSL: Bestimmung der Buchungsregel ueber ext. Vorgang, Buchungstext od

Search SAP Function Modules

GET_POSTING_RULE is a standard get posting rule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Bestimmung der Buchungsregel ueber ext. Vorgang, Buchungstext od 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 get posting rule FM, simply by entering the name GET_POSTING_RULE into the relevant SAP transaction such as SE37 or SE38.

Function Group: F030
Program Name: SAPLF030
Main Program: SAPLF030
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_POSTING_RULE 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 'GET_POSTING_RULE'"NOTRANSL: Bestimmung der Buchungsregel ueber ext. Vorgang, Buchungstext od
  EXPORTING
*  I_VORGC =  "External transaction
*  I_BUTXT =  "Posting Text
*  I_TEXTS =  "
   I_VOZPM =  "+/- Sign
   I_VGTYP =  "Trans. Cat.
*  I_VGEXT =  "External business transaction
*  I_USING_DEFAULT = 'X' "

 IMPORTING
   E_VGEXT =  "
   E_VGINT =  "Posting Rule
   E_INTAG =  "Interpretation algorithm
   E_VGSAP =  "SAP bank transaction
   E_PFORM =  "Processing Type
   E_USING_DEFAULT =  "
   E_DADET =  "

EXCEPTIONS
   NOT_FOUND = 1    INPUT_WRONG = 2 

.

IMPORTING Parameters details for GET_POSTING_RULE

I_VORGC - External transaction

Data type: FEBEP-VORGC
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUTXT - Posting Text

Data type: FEBEP-BUTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TEXTS -

Data type: FEBEP-TEXTS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VOZPM - +/- Sign

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

I_VGTYP - Trans. Cat.

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

I_VGEXT - External business transaction

Data type: FEBEP-VGEXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_USING_DEFAULT -

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

EXPORTING Parameters details for GET_POSTING_RULE

E_VGEXT -

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

E_VGINT - Posting Rule

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

E_INTAG - Interpretation algorithm

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

E_VGSAP - SAP bank transaction

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

E_PFORM - Processing Type

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

E_USING_DEFAULT -

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

E_DADET -

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

EXCEPTIONS details

NOT_FOUND -

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

INPUT_WRONG - No entry

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

Copy and paste ABAP code example for GET_POSTING_RULE 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.

ABAP code using 7.40 inline data declarations to call FM GET_POSTING_RULE

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.

Search for further information about these or an SAP related objects