Production Schedule Reports

Question

Hi Team,We are using Production Schedule reporting in IFS Cloud and have observed that some records in the Production Schedule Reports page remain in “Created” status. If a report remains in Created status, what configuration, background jobs, material transactions, or other processes should be checked? Is there any standard IFS process/job that should be executed to process such records further? How can we identify the exact reason why a particular report has remained in Created status? What subsequent process or event changes the status from Created to Backflush Complete?We would appreciate clarification on the complete status flow and the expected system behaviour.

Yathartha Karunananda · Answer

Hi ​@Asit Sahu,What does the “Created” status indicate?When a production receipt or progress-point report is submitted with the Background Job option enabled, IFS creates the report with the status Created and defers backflush processing to a background process.The status changes to Backflush Complete once the backflush processing completes. If background processing is not selected, backflush is executed inline as part of the reporting transaction.What configurations and processes should be checked?The following areas can be used for the investigation functionally:Background Jobs: Check for failed, waiting, or stuck jobs and review any available error messages.Component availability: Verify component stock and the configured backflush locations, including work center, production line inbound, floor stock, and picking locations, where applicable.Product structure: Review repetitive backflush settings, particularly the Phantom Consume configuration.Inventory settings: Check the site's negative inventory policy and any relevant serial- or lot-tracking constraints.These are potential investigation areas; the actual cause must be established from the affected report's processing history and available error details.Is there a standard process or job that changes the status?The status transition occurs when the deferred backflush processing completes. This may include component issues, inventory transaction creation, applicable operation history updates, and production schedule updates.How can the exact reason be identified?For an affected report:Record the Report ID and relevant production schedule details.Check the Background Jobs page for the associated job and review its status and error logs.Review Inventory Transaction History to determine whether component issue transactions were created.Verify component availability and the relevant backflush configurations.Correlating these findings should help establish where processing stopped.You may start by checking the associated background job and transaction history. If the report remains in Created status without an identifiable error or pending job, further investigation may be required.

What does the “Created” status indicate?

What configurations and processes should be checked?

Is there a standard process or job that changes the status?

How can the exact reason be identified?

Did you find what you're looking for? If not:

Sign up

Login to the community