SAP ISB_SFGDT_PRICING_UNIT Function Module for Open-Reporting: Ermittlung Kennzahlen Risikoträgerobjekt









ISB_SFGDT_PRICING_UNIT is a standard isb sfgdt pricing unit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Open-Reporting: Ermittlung Kennzahlen Risikoträgerobjekt 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 isb sfgdt pricing unit FM, simply by entering the name ISB_SFGDT_PRICING_UNIT into the relevant SAP transaction such as SE37 or SE38.

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



Function ISB_SFGDT_PRICING_UNIT 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 'ISB_SFGDT_PRICING_UNIT'"Open-Reporting: Ermittlung Kennzahlen Risikoträgerobjekt
EXPORTING
* I_PROTOCOL_LEVEL = 1 "Protokoll-Level
* I_DATE = SY-DATUM "Datum zu dem die Kennzahl ermittelt wird
* I_ROOT = "
I_IT_RISKOBJ = "Mit Marktdaten angereicherte Risikoträger

IMPORTING
E_IT_RESULTOBJ = "Ergebnistabelle

TABLES
I_IT_METHOD = "Tabelle mit Kennzahlen die ermittelt werden
* ERROR_ITAB = "Error-Tabelle

EXCEPTIONS
GENERAL_ERR = 1 PRICING_UNIT_ERR = 2
.



IMPORTING Parameters details for ISB_SFGDT_PRICING_UNIT

I_PROTOCOL_LEVEL - Protokoll-Level

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

I_DATE - Datum zu dem die Kennzahl ermittelt wird

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ROOT -

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

I_IT_RISKOBJ - Mit Marktdaten angereicherte Risikoträger

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

EXPORTING Parameters details for ISB_SFGDT_PRICING_UNIT

E_IT_RESULTOBJ - Ergebnistabelle

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

TABLES Parameters details for ISB_SFGDT_PRICING_UNIT

I_IT_METHOD - Tabelle mit Kennzahlen die ermittelt werden

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

ERROR_ITAB - Error-Tabelle

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

EXCEPTIONS details

GENERAL_ERR -

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

PRICING_UNIT_ERR -

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

Copy and paste ABAP code example for ISB_SFGDT_PRICING_UNIT 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_general_err  TYPE STRING, "   
lt_i_it_method  TYPE STANDARD TABLE OF BAPI_METHD, "   
lv_e_it_resultobj  TYPE JBO02_RESULT_TAB, "   
lv_i_protocol_level  TYPE JBO02_RESULT_TAB, "   1
lv_i_date  TYPE SY-DATUM, "   SY-DATUM
lt_error_itab  TYPE STANDARD TABLE OF BAPIERR, "   
lv_pricing_unit_err  TYPE BAPIERR, "   
lv_i_root  TYPE TV1_KNOT_ID, "   
lv_i_it_riskobj  TYPE JBO02_OBJSFGDT_TAB. "   

  CALL FUNCTION 'ISB_SFGDT_PRICING_UNIT'  "Open-Reporting: Ermittlung Kennzahlen Risikoträgerobjekt
    EXPORTING
         I_PROTOCOL_LEVEL = lv_i_protocol_level
         I_DATE = lv_i_date
         I_ROOT = lv_i_root
         I_IT_RISKOBJ = lv_i_it_riskobj
    IMPORTING
         E_IT_RESULTOBJ = lv_e_it_resultobj
    TABLES
         I_IT_METHOD = lt_i_it_method
         ERROR_ITAB = lt_error_itab
    EXCEPTIONS
        GENERAL_ERR = 1
        PRICING_UNIT_ERR = 2
. " ISB_SFGDT_PRICING_UNIT




ABAP code using 7.40 inline data declarations to call FM ISB_SFGDT_PRICING_UNIT

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.

 
 
 
DATA(ld_i_protocol_level) = 1.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date).
DATA(ld_i_date) = SY-DATUM.
 
 
 
 
 


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!