SAP PRICING_GET_DYNNR Function Module for NOTRANSL: Get dynnr of current pricing view
PRICING_GET_DYNNR is a standard pricing get dynnr 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: Get dynnr of current pricing view 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 pricing get dynnr FM, simply by entering the name PRICING_GET_DYNNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: V69A
Program Name: SAPLV69A
Main Program: SAPLV69A
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRICING_GET_DYNNR 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 'PRICING_GET_DYNNR'"NOTRANSL: Get dynnr of current pricing view.
IMPORTING
EV_DYNNR = "ABAP System Field: Current Dynpro Number
EV_PROG = "ABAP System Field: Calling Program
EXPORTING Parameters details for PRICING_GET_DYNNR
EV_DYNNR - ABAP System Field: Current Dynpro Number
Data type: SY-DYNNROptional: No
Call by Reference: Yes
EV_PROG - ABAP System Field: Calling Program
Data type: SY-CPROGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRICING_GET_DYNNR 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_ev_dynnr | TYPE SY-DYNNR, " | |||
| lv_ev_prog | TYPE SY-CPROG. " |
|   CALL FUNCTION 'PRICING_GET_DYNNR' "NOTRANSL: Get dynnr of current pricing view |
| IMPORTING | ||
| EV_DYNNR | = lv_ev_dynnr | |
| EV_PROG | = lv_ev_prog | |
| . " PRICING_GET_DYNNR | ||
ABAP code using 7.40 inline data declarations to call FM PRICING_GET_DYNNR
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 DYNNR FROM SY INTO @DATA(ld_ev_dynnr). | ||||
| "SELECT single CPROG FROM SY INTO @DATA(ld_ev_prog). | ||||
Search for further information about these or an SAP related objects