We have been using CPQ with XA for over 10 years. Since implementation, we have consistently encountered an issue where the Current/Standard Cost does not update properly during the Cost Roll-Up process. I have previously discussed this matter with Ross F. and MJ and have submitted an Enhancement Request (ER 112565) to address the problem. This ER is currently open and requires endorsements in order to move forward into production.

As you may know, each Configuration ID is  Read more...classified as an Alternate BOM, and only the Primary BOM is included in the Cost Roll-Up. Infor has updated their process so that whenever a Configuration is received from CPQ, the system performs a Single Item Cost Roll-Up, which includes the Configuration’s BOM and all lower-level components. While this helps, it only runs once per day. If a lower-level BOM is changed after the process has already run, the item will not be re-costed until the following day at the earliest.

This approach may work when Configurations are added to orders frequently. However, when a Configuration is used only occasionally (for example, once every few months), the cost may not reflect current component costs or updates to lower-level BOMs caused by supply or manufacturing changes. Additionally, the Single Item Cost Roll-Up only applies to Configurations currently available within CPQ. Older but still valid Config IDs, which can still be ordered, are not re-costed at all, leaving them with outdated unit costs.

It is my belief that all Configured Items with a Config ID should be re-costed during the Cost Roll-Up process, whether that occurs daily, weekly, monthly, or on an individually selected basis.

I would greatly appreciate your support by endorsing ER 112565 so this enhancement can be incorporated into the XA Cost Roll-Up process.

Thank you for your time and consideration.

Best regards,

Mark Show less...