SAP ALM_ONE_LEVEL_EVALUATION Function Module for One-Level Pricing of a Financial Instrument in the P+L Evaluation









ALM_ONE_LEVEL_EVALUATION is a standard alm one level evaluation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for One-Level Pricing of a Financial Instrument in the P+L Evaluation 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 alm one level evaluation FM, simply by entering the name ALM_ONE_LEVEL_EVALUATION into the relevant SAP transaction such as SE37 or SE38.

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



Function ALM_ONE_LEVEL_EVALUATION 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 'ALM_ONE_LEVEL_EVALUATION'"One-Level Pricing of a Financial Instrument in the P+L Evaluation
EXPORTING
GUV_PARAMETER = "Depreciation Rules
GFORM = "Transaction Form
GDETAIL = "Transaction Form - Detail Information

CHANGING
GUV_ARRAY = "Profit and Loss Results Object
GUV_RESULTS = "Table for Profit and Loss Results Object

EXCEPTIONS
INVALID_DATA = 1
.



IMPORTING Parameters details for ALM_ONE_LEVEL_EVALUATION

GUV_PARAMETER - Depreciation Rules

Data type: ALM_GUV_PARAMETER
Optional: No
Call by Reference: Yes

GFORM - Transaction Form

Data type: TV0_BEST_TYP-GFORM
Optional: No
Call by Reference: Yes

GDETAIL - Transaction Form - Detail Information

Data type: TV0_BEST_TYP-GDETAIL
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ALM_ONE_LEVEL_EVALUATION

GUV_ARRAY - Profit and Loss Results Object

Data type: ALM_GUV_TYP
Optional: No
Call by Reference: Yes

GUV_RESULTS - Table for Profit and Loss Results Object

Data type: ALM_GUV_RESULT_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_DATA - Invalid Data

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

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

DATA:
lv_guv_array  TYPE ALM_GUV_TYP, "   
lv_invalid_data  TYPE ALM_GUV_TYP, "   
lv_guv_parameter  TYPE ALM_GUV_PARAMETER, "   
lv_gform  TYPE TV0_BEST_TYP-GFORM, "   
lv_guv_results  TYPE ALM_GUV_RESULT_TAB, "   
lv_gdetail  TYPE TV0_BEST_TYP-GDETAIL. "   

  CALL FUNCTION 'ALM_ONE_LEVEL_EVALUATION'  "One-Level Pricing of a Financial Instrument in the P+L Evaluation
    EXPORTING
         GUV_PARAMETER = lv_guv_parameter
         GFORM = lv_gform
         GDETAIL = lv_gdetail
    CHANGING
         GUV_ARRAY = lv_guv_array
         GUV_RESULTS = lv_guv_results
    EXCEPTIONS
        INVALID_DATA = 1
. " ALM_ONE_LEVEL_EVALUATION




ABAP code using 7.40 inline data declarations to call FM ALM_ONE_LEVEL_EVALUATION

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.

 
 
 
"SELECT single GFORM FROM TV0_BEST_TYP INTO @DATA(ld_gform).
 
 
"SELECT single GDETAIL FROM TV0_BEST_TYP INTO @DATA(ld_gdetail).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!