SAP J_3G_PRL_DETERMINATION Function Module for ETM Price List Determination
J_3G_PRL_DETERMINATION is a standard j 3g prl 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 ETM Price List Determination 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 j 3g prl determination FM, simply by entering the name J_3G_PRL_DETERMINATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: J3GJ
Program Name: SAPLJ3GJ
Main Program: SAPLJ3GJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function J_3G_PRL_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 'J_3G_PRL_DETERMINATION'"ETM Price List Determination.
EXPORTING
* APPLICATION = 'V' "
DATE = "
HEADER_COMMUNICATION = "
ITEM_COMMUNICATION = "
SCHEME = "
* PROTOKOLL = ' ' "
IMPORTING
KONDT_DATA = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for J_3G_PRL_DETERMINATION
APPLICATION -
Data type: T683-KAPPLDefault: 'V'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
HEADER_COMMUNICATION -
Data type: J_3GPRLKOKOptional: No
Call by Reference: No ( called with pass by value option)
ITEM_COMMUNICATION -
Data type: J_3GPRLKOPOptional: No
Call by Reference: No ( called with pass by value option)
SCHEME -
Data type: T683-KALSMOptional: No
Call by Reference: No ( called with pass by value option)
PROTOKOLL -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_3G_PRL_DETERMINATION
KONDT_DATA -
Data type: J_3GPRLHDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_3G_PRL_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.DATA: | ||||
lv_not_found | TYPE STRING, " | |||
lv_kondt_data | TYPE J_3GPRLHD, " | |||
lv_application | TYPE T683-KAPPL, " 'V' | |||
lv_date | TYPE SY-DATUM, " | |||
lv_header_communication | TYPE J_3GPRLKOK, " | |||
lv_item_communication | TYPE J_3GPRLKOP, " | |||
lv_scheme | TYPE T683-KALSM, " | |||
lv_protokoll | TYPE T683. " ' ' |
  CALL FUNCTION 'J_3G_PRL_DETERMINATION' "ETM Price List Determination |
EXPORTING | ||
APPLICATION | = lv_application | |
DATE | = lv_date | |
HEADER_COMMUNICATION | = lv_header_communication | |
ITEM_COMMUNICATION | = lv_item_communication | |
SCHEME | = lv_scheme | |
PROTOKOLL | = lv_protokoll | |
IMPORTING | ||
KONDT_DATA | = lv_kondt_data | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
. " J_3G_PRL_DETERMINATION |
ABAP code using 7.40 inline data declarations to call FM J_3G_PRL_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."SELECT single KAPPL FROM T683 INTO @DATA(ld_application). | ||||
DATA(ld_application) | = 'V'. | |||
"SELECT single DATUM FROM SY INTO @DATA(ld_date). | ||||
"SELECT single KALSM FROM T683 INTO @DATA(ld_scheme). | ||||
DATA(ld_protokoll) | = ' '. | |||
Search for further information about these or an SAP related objects