To define a repetitive schedule: When defining repetitive schedules, you can:
Define repetitive schedules to build assemblies repetitively on a production line. Repetitive schedules are used to schedule production, resources, and material requirements, and to collect the costs of manufacturing a repetitive assembly on a production line.
Assign bills and routings to repetitive schedules to create material requirements, schedule operations, and create resource requirements. Neither bills of material nor routings are required however.
Specify the line, the assembly you are building, daily quantity, processing days, and/or total quantity, and a date to schedule.
Attach illustrative or explanatory files - in the form of text, images, word processing documents, spreadsheets, video, and so on - to repetitive schedules. See: About Attachments, and Attaching Files to Jobs, Schedules, and Operations
Define at least one production line. See: Defining Production Lines.
Define at least one Repetitive Line/Assembly Association. See: Associating Lines and Assemblies.
To define a repetitive schedule: Navigate to the Repetitive Schedules window. The Repetitive Schedule Summary window appears.
Choose the New button to open the Repetitive Schedules window.
Note: You can define several repetitive schedules simultaneously in the Repetitive Schedules Summary window. You can, however, also define repetitive schedules one-at-a-time using the Repetitive Schedules window.
Select the production Line and the repetitive Assembly.
You can select any production Line and associated Assembly. The routing, bill, accounting class, supply type, and completion subinventory/locator defined for the Repetitive Line/Assembly Association selected are defaulted. See: Associating Lines and Assemblies.
Select the schedule Status.
When you define a repetitive schedule, its default status is Unreleased but can be changed to Released or On Hold. See: Repetitive Schedule Statuses.
Enter the Daily Quantity for the repetitive schedule.
If you do not enter the daily quantity, enter the number of processing days and the total quantity.
The number of completed assemblies you plan to produce on the schedule each day. This quantity is effective from the schedule start date to the schedule end date.
Enter the number of Days for the repetitive schedule. Use decimal numbers to indicate partial days (up to 6 decimal places).
This is the number of days that the repetitive schedule requires, from the first assembly completion date through the last assembly completion date, to manufacture the total number of assemblies.
If you enter the number of days, the total quantity is automatically calculated based on the daily quantity. If you do not enter the number of days, enter the daily quantity and total quantity.
Enter the Total Quantity of assemblies that you plan to manufacture with this schedule.
If you enter the total quantity, the processing days are calculated based on the daily quantity. If you do not enter the total quantity, enter the daily quantity and number of processing days.
Select the Demand Class.
You can select any enabled and active demand class. Demand classes are not required. See: Overview of Demand Classes, Oracle MRP User's Guide and Creating Demand Classes, Oracle MRP User's Guide.
Check the Firm check box to firm your schedule.
Firming repetitive schedules prevents MRP from suggesting rescheduling and replanning recommendations when changes to supply or demand occur. Firming a repetitive schedule locks in that schedule's daily quantity as the recommended daily quantity for future schedules using that line/assembly association. See: Firm Order Planning, Oracle MRP User's Guide.
Enter the Description.
Descriptions can be used to identify repetitive schedules on standard reports. They can be up to 240 characters of alpha numeric text. They are not required.
To schedule a repetitive schedule with a routing or a fixed lead time repetitive schedule without a routing:Select a First Unit Start Date (FUSD) or First Unit Complete Date (FUCD) or a Last Unit Start Date (LUSD) or Last Unit Complete Date (LUCD).
Only one date (FUSD, FUCD, LUSD, or LUCD) is required for repetitive assemblies with routings and repetitive assemblies without routings that are associated with production lines that have Fixed lead time. The repetitive schedule is automatically forward or backward scheduled based upon the dates entered.
To schedule a repetitive schedule without a routing that has a routing-based lead time:Select the FUSD and FUCD or select the LUSD and LUCD.
A set of start or completion dates is required for repetitive schedules without routings that are associated with production lines that have Routing-based lead times. The system uses the processing days to schedule the dates not entered.
To assign bill of material and routing revisions and dates:Select the bill of material Revision.
The bill of material defaults based on the repetitive line and assembly selected. You can however, select an alternate revision and revision date and time if alternates have been defined.
You can update the bill revision as long as the repetitive schedule remains unreleased. You can update the revision for standard bills or alternate bills. See: Item and Routing Revisions.
You can explode item revisions that have associated ECOs with Release, Schedule, and Implement statuses. If you set the WIP:Exclude ECOs profile option to None, you can also explode revisions for ECOs that have an Open status. See: Implementing ECOs in the Oracle Engineering User's Guide..
Select the bill Revision Date and time.
You can update the bill revision date for standard bills or alternate bills. You can update the bill revision date as long as the repetitive schedule remains unreleased.
Select the routing Revision.
The routing defaults based on the repetitive line and assembly selected. You can, however, update the routing revision as long as the schedule remains unreleased. See: Item and Routing Revisions
Select the routing Revision Date and time.
You can update routing revision dates for standard and alternate routings. You can update the routing revision date as long as the schedule remains unreleased. If you do not enter a revision date, the system uses the first unit start date (FUSD).
Save your work.
To view outside processing workflows: