SAP PRICES_POST Function Module for
PRICES_POST is a standard prices post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 prices post FM, simply by entering the name PRICES_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: CKM_PRICECHANGES_2
Program Name: SAPLCKM_PRICECHANGES_2
Main Program: SAPLCKM_PRICECHANGES_2
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function PRICES_POST 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 'PRICES_POST'".
EXPORTING
* I_BKTXT = "
* I_KONGR = "Account Assignment Reason
* IV_TCODE = "
BUKRS = "
* LIS_UPDATE = 'X' "
* SUBS_DBT = "
* I_AWREF = "
* I_AWORG = "
* I_AWTYP = "
* I_AWSYS = "
* NO_MESSAGE = "
IMPORTING
O_BELNR = "
O_KJAHR = "
TABLES
T_MATPR = "
IMPORTING Parameters details for PRICES_POST
I_BKTXT -
Data type: ACCHD-BKTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_KONGR - Account Assignment Reason
Data type: MLHD-KONGROptional: Yes
Call by Reference: Yes
IV_TCODE -
Data type: SYTCODEOptional: Yes
Call by Reference: Yes
BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
LIS_UPDATE -
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUBS_DBT -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AWREF -
Data type: ACCHD-AWREFOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AWORG -
Data type: ACCHD-AWORGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AWTYP -
Data type: ACCHD-AWTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AWSYS -
Data type: TBDLS-LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
NO_MESSAGE -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PRICES_POST
O_BELNR -
Data type: MLHD-BELNROptional: No
Call by Reference: No ( called with pass by value option)
O_KJAHR -
Data type: MLHD-KJAHROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PRICES_POST
T_MATPR -
Data type: CKMPR_MAT_PRICEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PRICES_POST 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_i_bktxt | TYPE ACCHD-BKTXT, " | |||
lv_o_belnr | TYPE MLHD-BELNR, " | |||
lt_t_matpr | TYPE STANDARD TABLE OF CKMPR_MAT_PRICE, " | |||
lv_i_kongr | TYPE MLHD-KONGR, " | |||
lv_iv_tcode | TYPE SYTCODE, " | |||
lv_bukrs | TYPE T001-BUKRS, " | |||
lv_o_kjahr | TYPE MLHD-KJAHR, " | |||
lv_lis_update | TYPE BOOLE-BOOLE, " 'X' | |||
lv_subs_dbt | TYPE BOOLE-BOOLE, " | |||
lv_i_awref | TYPE ACCHD-AWREF, " | |||
lv_i_aworg | TYPE ACCHD-AWORG, " | |||
lv_i_awtyp | TYPE ACCHD-AWTYP, " | |||
lv_i_awsys | TYPE TBDLS-LOGSYS, " | |||
lv_no_message | TYPE BOOLE-BOOLE. " |
  CALL FUNCTION 'PRICES_POST' " |
EXPORTING | ||
I_BKTXT | = lv_i_bktxt | |
I_KONGR | = lv_i_kongr | |
IV_TCODE | = lv_iv_tcode | |
BUKRS | = lv_bukrs | |
LIS_UPDATE | = lv_lis_update | |
SUBS_DBT | = lv_subs_dbt | |
I_AWREF | = lv_i_awref | |
I_AWORG | = lv_i_aworg | |
I_AWTYP | = lv_i_awtyp | |
I_AWSYS | = lv_i_awsys | |
NO_MESSAGE | = lv_no_message | |
IMPORTING | ||
O_BELNR | = lv_o_belnr | |
O_KJAHR | = lv_o_kjahr | |
TABLES | ||
T_MATPR | = lt_t_matpr | |
. " PRICES_POST |
ABAP code using 7.40 inline data declarations to call FM PRICES_POST
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 BKTXT FROM ACCHD INTO @DATA(ld_i_bktxt). | ||||
"SELECT single BELNR FROM MLHD INTO @DATA(ld_o_belnr). | ||||
"SELECT single KONGR FROM MLHD INTO @DATA(ld_i_kongr). | ||||
"SELECT single BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
"SELECT single KJAHR FROM MLHD INTO @DATA(ld_o_kjahr). | ||||
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_lis_update). | ||||
DATA(ld_lis_update) | = 'X'. | |||
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_subs_dbt). | ||||
"SELECT single AWREF FROM ACCHD INTO @DATA(ld_i_awref). | ||||
"SELECT single AWORG FROM ACCHD INTO @DATA(ld_i_aworg). | ||||
"SELECT single AWTYP FROM ACCHD INTO @DATA(ld_i_awtyp). | ||||
"SELECT single LOGSYS FROM TBDLS INTO @DATA(ld_i_awsys). | ||||
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_no_message). | ||||
Search for further information about these or an SAP related objects