SAP MLCCS_SETTLEMENT_SIMULATION Function Module for
MLCCS_SETTLEMENT_SIMULATION is a standard mlccs settlement simulation 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 mlccs settlement simulation FM, simply by entering the name MLCCS_SETTLEMENT_SIMULATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: MLCCS_ORDER_SETTLEMENT
Program Name: SAPLMLCCS_ORDER_SETTLEMENT
Main Program: SAPLMLCCS_ORDER_SETTLEMENT
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MLCCS_SETTLEMENT_SIMULATION 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 'MLCCS_SETTLEMENT_SIMULATION'".
EXPORTING
IS_ORDER = "
IS_MAT_KEY = "
* I_CO_AREA_WAERS = '' "Single-Character Indicator
* I_FIX_PR_CO_PROD = '' "Single-Character Indicator
* I_CO_CURTP_IN_ML = '' "Single-Character Indicator
* I_CO_AREA_CURTP = '' "Currency type and valuation view
IS_MLCCS_CUSTOMIZING = "Customizing Switch-Actual Costing
CHANGING
T_INPUTS = "Input Materials/Output Materials from an Order
T_INPUTS_CR = "Amounts of Withdrawls and Receipts from Production Order
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for MLCCS_SETTLEMENT_SIMULATION
IS_ORDER -
Data type: MLCCS_S_ORDEROptional: No
Call by Reference: Yes
IS_MAT_KEY -
Data type: CCSOR_S_MAT_KEYOptional: No
Call by Reference: Yes
I_CO_AREA_WAERS - Single-Character Indicator
Data type: WAERSDefault: ''
Optional: Yes
Call by Reference: Yes
I_FIX_PR_CO_PROD - Single-Character Indicator
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: Yes
I_CO_CURTP_IN_ML - Single-Character Indicator
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: Yes
I_CO_AREA_CURTP - Currency type and valuation view
Data type: CURTPDefault: ''
Optional: Yes
Call by Reference: Yes
IS_MLCCS_CUSTOMIZING - Customizing Switch-Actual Costing
Data type: MLCCS_S_CUSTOMIZINGOptional: No
Call by Reference: Yes
CHANGING Parameters details for MLCCS_SETTLEMENT_SIMULATION
T_INPUTS - Input Materials/Output Materials from an Order
Data type: CKI_T_ORDER_IOOptional: No
Call by Reference: Yes
T_INPUTS_CR - Amounts of Withdrawls and Receipts from Production Order
Data type: CKI_T_ORDER_IO_CROptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MLCCS_SETTLEMENT_SIMULATION 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_is_order | TYPE MLCCS_S_ORDER, " | |||
| lv_t_inputs | TYPE CKI_T_ORDER_IO, " | |||
| lv_error_occurred | TYPE CKI_T_ORDER_IO, " | |||
| lv_is_mat_key | TYPE CCSOR_S_MAT_KEY, " | |||
| lv_t_inputs_cr | TYPE CKI_T_ORDER_IO_CR, " | |||
| lv_i_co_area_waers | TYPE WAERS, " '' | |||
| lv_i_fix_pr_co_prod | TYPE CHAR1, " '' | |||
| lv_i_co_curtp_in_ml | TYPE CHAR1, " '' | |||
| lv_i_co_area_curtp | TYPE CURTP, " '' | |||
| lv_is_mlccs_customizing | TYPE MLCCS_S_CUSTOMIZING. " |
|   CALL FUNCTION 'MLCCS_SETTLEMENT_SIMULATION' " |
| EXPORTING | ||
| IS_ORDER | = lv_is_order | |
| IS_MAT_KEY | = lv_is_mat_key | |
| I_CO_AREA_WAERS | = lv_i_co_area_waers | |
| I_FIX_PR_CO_PROD | = lv_i_fix_pr_co_prod | |
| I_CO_CURTP_IN_ML | = lv_i_co_curtp_in_ml | |
| I_CO_AREA_CURTP | = lv_i_co_area_curtp | |
| IS_MLCCS_CUSTOMIZING | = lv_is_mlccs_customizing | |
| CHANGING | ||
| T_INPUTS | = lv_t_inputs | |
| T_INPUTS_CR | = lv_t_inputs_cr | |
| EXCEPTIONS | ||
| ERROR_OCCURRED = 1 | ||
| . " MLCCS_SETTLEMENT_SIMULATION | ||
ABAP code using 7.40 inline data declarations to call FM MLCCS_SETTLEMENT_SIMULATION
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_i_co_area_waers) | = ''. | |||
| DATA(ld_i_fix_pr_co_prod) | = ''. | |||
| DATA(ld_i_co_curtp_in_ml) | = ''. | |||
| DATA(ld_i_co_area_curtp) | = ''. | |||
Search for further information about these or an SAP related objects