SAP PRCH_SHIFT_ANCHOR_BLANK Function Module for
PRCH_SHIFT_ANCHOR_BLANK is a standard prch shift anchor blank 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 prch shift anchor blank FM, simply by entering the name PRCH_SHIFT_ANCHOR_BLANK 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: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRCH_SHIFT_ANCHOR_BLANK 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 'PRCH_SHIFT_ANCHOR_BLANK'".
EXPORTING
LF_RELEASED_CE = "Costing Record for Released Cost Estimate
I_MATNR = "Material Number
I_BWKEY = "Valuation Area
BDATJ = "Posting date YYYY
POPER = "Posting Period
I_WAERS = "Currency Key
I_PERTYP = "Period category (current, previous, last from prev. year...)
S_PRICE_PROP_CTRL = "Control Toolbar for the Module Prices_purpose
P_CALC_OBLIG = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
CHANGING
PROPOSAL_FOUND = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
TABLES
T_MATPR_BLANK = "
IMPORTING Parameters details for PRCH_SHIFT_ANCHOR_BLANK
LF_RELEASED_CE - Costing Record for Released Cost Estimate
Data type: RELEASED_COST_ESTIMATEOptional: No
Call by Reference: Yes
I_MATNR - Material Number
Data type: MBEW-MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_BWKEY - Valuation Area
Data type: MBEW-BWKEYOptional: No
Call by Reference: No ( called with pass by value option)
BDATJ - Posting date YYYY
Data type: CKI_PAE_PP-BDATJOptional: No
Call by Reference: No ( called with pass by value option)
POPER - Posting Period
Data type: CKI_PAE_PP-POPEROptional: No
Call by Reference: No ( called with pass by value option)
I_WAERS - Currency Key
Data type: WAERSOptional: No
Call by Reference: No ( called with pass by value option)
I_PERTYP - Period category (current, previous, last from prev. year...)
Data type: PERTYPOptional: No
Call by Reference: No ( called with pass by value option)
S_PRICE_PROP_CTRL - Control Toolbar for the Module Prices_purpose
Data type: PRICE_PROP_CTRLOptional: No
Call by Reference: No ( called with pass by value option)
P_CALC_OBLIG - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for PRCH_SHIFT_ANCHOR_BLANK
PROPOSAL_FOUND - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
TABLES Parameters details for PRCH_SHIFT_ANCHOR_BLANK
T_MATPR_BLANK -
Data type: CKMPR_MAT_PRICEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRCH_SHIFT_ANCHOR_BLANK 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: | ||||
| lt_t_matpr_blank | TYPE STANDARD TABLE OF CKMPR_MAT_PRICE, " | |||
| lv_lf_released_ce | TYPE RELEASED_COST_ESTIMATE, " | |||
| lv_proposal_found | TYPE BOOLE-BOOLE, " | |||
| lv_i_matnr | TYPE MBEW-MATNR, " | |||
| lv_i_bwkey | TYPE MBEW-BWKEY, " | |||
| lv_bdatj | TYPE CKI_PAE_PP-BDATJ, " | |||
| lv_poper | TYPE CKI_PAE_PP-POPER, " | |||
| lv_i_waers | TYPE WAERS, " | |||
| lv_i_pertyp | TYPE PERTYP, " | |||
| lv_s_price_prop_ctrl | TYPE PRICE_PROP_CTRL, " | |||
| lv_p_calc_oblig | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'PRCH_SHIFT_ANCHOR_BLANK' " |
| EXPORTING | ||
| LF_RELEASED_CE | = lv_lf_released_ce | |
| I_MATNR | = lv_i_matnr | |
| I_BWKEY | = lv_i_bwkey | |
| BDATJ | = lv_bdatj | |
| POPER | = lv_poper | |
| I_WAERS | = lv_i_waers | |
| I_PERTYP | = lv_i_pertyp | |
| S_PRICE_PROP_CTRL | = lv_s_price_prop_ctrl | |
| P_CALC_OBLIG | = lv_p_calc_oblig | |
| CHANGING | ||
| PROPOSAL_FOUND | = lv_proposal_found | |
| TABLES | ||
| T_MATPR_BLANK | = lt_t_matpr_blank | |
| . " PRCH_SHIFT_ANCHOR_BLANK | ||
ABAP code using 7.40 inline data declarations to call FM PRCH_SHIFT_ANCHOR_BLANK
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 BOOLE FROM BOOLE INTO @DATA(ld_proposal_found). | ||||
| "SELECT single MATNR FROM MBEW INTO @DATA(ld_i_matnr). | ||||
| "SELECT single BWKEY FROM MBEW INTO @DATA(ld_i_bwkey). | ||||
| "SELECT single BDATJ FROM CKI_PAE_PP INTO @DATA(ld_bdatj). | ||||
| "SELECT single POPER FROM CKI_PAE_PP INTO @DATA(ld_poper). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_p_calc_oblig). | ||||
Search for further information about these or an SAP related objects