SAP FB_ICRC_REPLACE_PLACEHOLDERS Function Module for Replace Placeholders in Template Text
FB_ICRC_REPLACE_PLACEHOLDERS is a standard fb icrc replace placeholders SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Replace Placeholders in Template Text 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 fb icrc replace placeholders FM, simply by entering the name FB_ICRC_REPLACE_PLACEHOLDERS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB_ICRC_SERVICES
Program Name: SAPLFB_ICRC_SERVICES
Main Program: SAPLFB_ICRC_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FB_ICRC_REPLACE_PLACEHOLDERS 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 'FB_ICRC_REPLACE_PLACEHOLDERS'"Replace Placeholders in Template Text.
EXPORTING
* ID_COMPANY = "
* IT_PLHID_VALUE = "Placeholder Values
* IB_LAYOUT_GET = 'X' "'X' = Have User Select Layout
* IT_DATA = "Data Container
* ID_PARTNER = "
* IR_ORGUNIT_DATA = "OrgUnit Data
* IR_PARTNER_DATA = "Partner Data
* IR_ASSIGNED_DATA = "
* ID_LANGUAGE_KEY = "Language Key
* ID_RPROC = "Reconciliation Process
* IT_RECIPIENTS = "Table type to hold contact person data.
* ID_KEY_DATE_CHAR = "Formatted Key Date
CHANGING
CD_TITLE = "Comment
CT_TEMPLATE_TEXT = "Template Text Table
* CD_EXIT = "User Cancelled
IMPORTING Parameters details for FB_ICRC_REPLACE_PLACEHOLDERS
ID_COMPANY -
Data type: RCOMP_DOptional: Yes
Call by Reference: Yes
IT_PLHID_VALUE - Placeholder Values
Data type: FBICRC_T_VALUEOptional: Yes
Call by Reference: Yes
IB_LAYOUT_GET - 'X' = Have User Select Layout
Data type: FB_ICRC_FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
IT_DATA - Data Container
Data type: FBICC_T_DATAOptional: Yes
Call by Reference: Yes
ID_PARTNER -
Data type: RASSCOptional: Yes
Call by Reference: Yes
IR_ORGUNIT_DATA - OrgUnit Data
Data type: DATAOptional: Yes
Call by Reference: Yes
IR_PARTNER_DATA - Partner Data
Data type: DATAOptional: Yes
Call by Reference: Yes
IR_ASSIGNED_DATA -
Data type: DATAOptional: Yes
Call by Reference: Yes
ID_LANGUAGE_KEY - Language Key
Data type: LANGUOptional: Yes
Call by Reference: Yes
ID_RPROC - Reconciliation Process
Data type: FB_RC_RPROCOptional: Yes
Call by Reference: Yes
IT_RECIPIENTS - Table type to hold contact person data.
Data type: STANDARD TABLEOptional: Yes
Call by Reference: Yes
ID_KEY_DATE_CHAR - Formatted Key Date
Data type: CHAR10Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for FB_ICRC_REPLACE_PLACEHOLDERS
CD_TITLE - Comment
Data type: CHAR50Optional: No
Call by Reference: Yes
CT_TEMPLATE_TEXT - Template Text Table
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
CD_EXIT - User Cancelled
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FB_ICRC_REPLACE_PLACEHOLDERS 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_cd_title | TYPE CHAR50, " | |||
| lv_id_company | TYPE RCOMP_D, " | |||
| lv_it_plhid_value | TYPE FBICRC_T_VALUE, " | |||
| lv_ib_layout_get | TYPE FB_ICRC_FLAG, " 'X' | |||
| lv_it_data | TYPE FBICC_T_DATA, " | |||
| lv_id_partner | TYPE RASSC, " | |||
| lv_ct_template_text | TYPE STANDARD TABLE, " | |||
| lv_cd_exit | TYPE FB_ICRC_FLAG, " | |||
| lv_ir_orgunit_data | TYPE DATA, " | |||
| lv_ir_partner_data | TYPE DATA, " | |||
| lv_ir_assigned_data | TYPE DATA, " | |||
| lv_id_language_key | TYPE LANGU, " | |||
| lv_id_rproc | TYPE FB_RC_RPROC, " | |||
| lv_it_recipients | TYPE STANDARD TABLE, " | |||
| lv_id_key_date_char | TYPE CHAR10. " |
|   CALL FUNCTION 'FB_ICRC_REPLACE_PLACEHOLDERS' "Replace Placeholders in Template Text |
| EXPORTING | ||
| ID_COMPANY | = lv_id_company | |
| IT_PLHID_VALUE | = lv_it_plhid_value | |
| IB_LAYOUT_GET | = lv_ib_layout_get | |
| IT_DATA | = lv_it_data | |
| ID_PARTNER | = lv_id_partner | |
| IR_ORGUNIT_DATA | = lv_ir_orgunit_data | |
| IR_PARTNER_DATA | = lv_ir_partner_data | |
| IR_ASSIGNED_DATA | = lv_ir_assigned_data | |
| ID_LANGUAGE_KEY | = lv_id_language_key | |
| ID_RPROC | = lv_id_rproc | |
| IT_RECIPIENTS | = lv_it_recipients | |
| ID_KEY_DATE_CHAR | = lv_id_key_date_char | |
| CHANGING | ||
| CD_TITLE | = lv_cd_title | |
| CT_TEMPLATE_TEXT | = lv_ct_template_text | |
| CD_EXIT | = lv_cd_exit | |
| . " FB_ICRC_REPLACE_PLACEHOLDERS | ||
ABAP code using 7.40 inline data declarations to call FM FB_ICRC_REPLACE_PLACEHOLDERS
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.| DATA(ld_ib_layout_get) | = 'X'. | |||
Search for further information about these or an SAP related objects