SAP PRICING_RECORD_READ Function Module for NOTRANSL: Lesen eines Konditionssatzes

Search SAP Function Modules

PRICING_RECORD_READ is a standard pricing record read 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: Lesen eines Konditionssatzes 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 record read FM, simply by entering the name PRICING_RECORD_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function PRICING_RECORD_READ 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_RECORD_READ'"NOTRANSL: Lesen eines Konditionssatzes
  EXPORTING
   COMM_HEAD_I =  "Communication header
   COMM_ITEM_I =  "Communication item
   KOMV_I =  "Condition type etc.
*  PRELIMINARY = ' ' "Control pre-step
*  PROTOKOLL_MODE = ' ' "

 IMPORTING
   COMM_HEAD_E =  "Communication header
   COMM_ITEM_E =  "Communication item
   KOMV_E =  "Condition Line
   KONP_E =  "Condition record (first)

EXCEPTIONS
   CONDITION = 1    NOT_FOUND = 2    NO_T683S = 3 

.

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 PRICING_RECORD_READ

COMM_HEAD_I - Communication header

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

COMM_ITEM_I - Communication item

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

KOMV_I - Condition type etc.

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

PRELIMINARY - Control pre-step

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

PROTOKOLL_MODE -

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

EXPORTING Parameters details for PRICING_RECORD_READ

COMM_HEAD_E - Communication header

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

COMM_ITEM_E - Communication item

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

KOMV_E - Condition Line

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

KONP_E - Condition record (first)

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

EXCEPTIONS details

CONDITION - Condition not met

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

NOT_FOUND - Condition record not found

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

NO_T683S - Condition type is missing in T683S

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

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

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