SAP OIA_FEE_DETERMINATION Function Module for NOTRANSL: Gebührenermittlung

Search SAP Function Modules

OIA_FEE_DETERMINATION is a standard oia fee determination 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: Gebührenermittlung 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 oia fee determination FM, simply by entering the name OIA_FEE_DETERMINATION into the relevant SAP transaction such as SE37 or SE38.

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

Function OIA_FEE_DETERMINATION 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 'OIA_FEE_DETERMINATION'"NOTRANSL: Gebührenermittlung
  EXPORTING
*  GANZZ_INDICATOR = ' ' "
*  OIC_PFART =  "Condition Control
*  OIC_CONTR =  "Level Number
*  PRELIMINARY = ' ' "
*  COMM_ITEM_I =  "Communication Item for Pricing
*  COMM_HEAD_I =  "Communication Header for Pricing
*  CALCULATION_TYPE = 'A' "Condition Control

 IMPORTING
   COMM_ITEM_E =  "Communication Item for Pricing
   COMM_HEAD_E =  "Communication Header for Pricing

TABLES
*  TKOMV =  "Pricing: Communications Condition Record

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV61A_001
EXIT_SAPLV61A_002 Customer Exit : Pricing - Rounding Rule
EXIT_SAPLV61A_400 F&A Repricing controlling

IMPORTING Parameters details for OIA_FEE_DETERMINATION

GANZZ_INDICATOR -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

OIC_PFART - Condition Control

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

OIC_CONTR - Level Number

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

PRELIMINARY -

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

COMM_ITEM_I - Communication Item for Pricing

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

COMM_HEAD_I - Communication Header for Pricing

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

CALCULATION_TYPE - Condition Control

Data type: KOMV-KSTEU
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OIA_FEE_DETERMINATION

COMM_ITEM_E - Communication Item for Pricing

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

COMM_HEAD_E - Communication Header for Pricing

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

TABLES Parameters details for OIA_FEE_DETERMINATION

TKOMV - Pricing: Communications Condition Record

Data type: KOMV
Optional: Yes
Call by Reference: Yes

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

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