Skip to main content

 

HI

We are currently reviewing and validating costing behaviour in IFS Cloud, and we need detailed insights into the following specific system cost parameters:

  • KEEP_MCA_SNAPSHOT

  • USE_START_DATE_FOR_SO_VAR

  • UPD_INV_EST_MTRL_COST

  • COPY_WC_LC_COSTS

  • COPY_SUPP_DELOH

For each of these parameters, we are looking for the following information:

  1. Purpose & Functionality

    • What is the role of this parameter in the costing process?

  2. System Behaviour

    • How does enabling this setting influence standard cost roll-ups, cost updates, or transaction recording?

  3. Activation Requirements

    • Are there specific modules, data configurations, or system setups required before this parameter can be effectively used?

  4. Impact on System Processes

    • Which modules (e.g., Inventory, Manufacturing, Finance) are affected?

    • Does it change historical data or only affect transactions going forward?

  5. Recommended Test Scenarios

    • What transactions or data setups should we use to verify expected behaviour?

    • Any particular reports or screens where the impact can be clearly observed?

We want to ensure our costing configuration is done correctly and in line with best practices. If you have implementation experience or documentation references for any of the above parameters, your guidance would be greatly appreciated.

KEEP_MCA_SNAPSHOT is relevant only if a company is using the Manufacturing Cost Allocation process that was introduced in 22R2 and updated in 23R1. I am not familiar with this functionality, but from the presentations it appears that snapshots of information are created or used in the jobs Update Inventory Transactions and Process Inventory Revaluation. This parameter controls the number of days the snapshots are kept in the system.

USE_START_DATE_FOR_SO_VAR determines which date on the shop order will be used when calculating variances, either the start date (Yes) or the actual close date (No). This would likely be relevant for companies that change standard costs frequently and have shop orders that remain open for long periods, during which time the standards could change.

UPD_INV_EST_MTRL_COST, COPY_WC_LC_COSTS, and COPY_SUPP_DELOH determine the default behavior of these toggles in the Copy Costs to Cost Set One dialog, i.e., either On or Off.

KEEP_MCA_SNAPSHOT is relevant only if a company is using the Manufacturing Cost Allocation process that was introduced in 22R2 and updated in 23R1. I am not familiar with this functionality, but from the presentations it appears that snapshots of information are created or used in the jobs Update Inventory Transactions and Process Inventory Revaluation. This parameter controls the number of days the snapshots are kept in the system.

USE_START_DATE_FOR_SO_VAR determines which date on the shop order will be used when calculating variances, either the start date (Yes) or the actual close date (No). This would likely be relevant for companies that change standard costs frequently and have shop orders that remain open for long periods, during which time the standards could change.

UPD_INV_EST_MTRL_COST, COPY_WC_LC_COSTS, and COPY_SUPP_DELOH determine the default behavior of these toggles in the Copy Costs to Cost Set One dialog, i.e., either On or Off.

Thank you very much for providing such detailed information.

Reply


Terms & ConditionsCookie settings