My Oracle Support Banner

Move Orders Are Not Getting Created for All Ingredients In OPM Batches When Move Order Timefence is set to Zero (0) or blank (Doc ID 2941333.1)

Last updated on MAY 18, 2023

Applies to:

Oracle Process Manufacturing Process Execution - Version 12.2.7 and later
Information in this document applies to any platform.


When the Create Move Orders field on the Create Batch tab of the Process Execution Parameters form (Production Supervisor > Setup > Parameters) is checked, and the Move Order Timefence is left blank, only ingredients with a requirement date that exactly matches the batch planned start date are being included on move orders. If an Automatic by Step ingredient is associated to a step that starts even a few minutes later, and therefore gets a Requirement Date that is a few minutes later, the ingredient is left out of the move order.

It was believed that a blank move order time fence used to be, and is supposed to be, interpreted as no timefence, or to put it another way, an infinite timefence. Therefore all eligible ingredients, regardless of Requirement Date, should be considered for the move order.

The issue can be reproduced at will with the following steps:
1. Production Supervisor > Setup > Parameters > Create Batch tab
2. Check the Create Move Orders field and leave the Move Order Timefence blank.
3. Create a batch in which an Automatic by Step ingredient is associated to a step that is planned to start later than the batch is planned to start.
4. Click the Move Orders button from that ingredient, get message:
APP-INV-05507: There were no Move Order records found




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.