SAP RECD_API_CONDITION_CHG Function Module for Change conditions
RECD_API_CONDITION_CHG is a standard recd api condition chg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change conditions 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 recd api condition chg FM, simply by entering the name RECD_API_CONDITION_CHG into the relevant SAP transaction such as SE37 or SE38.
Function Group: RECD_BAPI_CONDITION
Program Name: SAPLRECD_BAPI_CONDITION
Main Program: SAPLRECD_BAPI_CONDITION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RECD_API_CONDITION_CHG 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 'RECD_API_CONDITION_CHG'"Change conditions.
EXPORTING
IO_HAS_CONDITION = "Object with Conditions
IT_CONDITION = "
IO_MSGLIST = "Message Collector
IMPORTING Parameters details for RECD_API_CONDITION_CHG
IO_HAS_CONDITION - Object with Conditions
Data type: IF_RECD_HAS_CONDITIONOptional: No
Call by Reference: No ( called with pass by value option)
IT_CONDITION -
Data type: BAPI_RE_T_CONDITION_INTCOptional: No
Call by Reference: Yes
IO_MSGLIST - Message Collector
Data type: IF_RECA_MESSAGE_LISTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RECD_API_CONDITION_CHG 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_io_has_condition | TYPE IF_RECD_HAS_CONDITION, " | |||
| lv_it_condition | TYPE BAPI_RE_T_CONDITION_INTC, " | |||
| lv_io_msglist | TYPE IF_RECA_MESSAGE_LIST. " |
|   CALL FUNCTION 'RECD_API_CONDITION_CHG' "Change conditions |
| EXPORTING | ||
| IO_HAS_CONDITION | = lv_io_has_condition | |
| IT_CONDITION | = lv_it_condition | |
| IO_MSGLIST | = lv_io_msglist | |
| . " RECD_API_CONDITION_CHG | ||
ABAP code using 7.40 inline data declarations to call FM RECD_API_CONDITION_CHG
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