Setup
There are a few key screens and fields that need to be set up prior to using the advanced repetitive functionality. They are Advanced Repetitive Control (18.22.24), which enables advanced repetitive, the Auto Labor Report field in Routing Maintenance (14.13.1), Routing Maintenance (Rate Based) (14.13.2), and the Op field in Product Structure Maintenance (13.5). These are discussed on the following pages.
Repetitive Control Program Screen
Advanced Repetitive Control (18.22.24)
Next Picklist:
The number you want the next picklist issued to be.
Picklist Prefix:
A code to put in front of the picklist
Enable New Repetitive
To enable Advanced Repetitive, set this field to Yes
Transfer WIP
Values are Yes or No. This becomes the default for the field of the same name in Cumulative Order Close (18.22.10). See Closing the Cumulative Order.
Note: The WIP Transfer Account is in Advanced Repetitive Accounting Control (36.9.12).
WIP Transfer Account
The GL account debited or credited when closing a cumulative order and transferring WIP to a new cumulative order.
End Eff Default Method
Set to the method you normally use to end effectivity dates on cumulative orders. You have four options:
• Blank: Start and end effective dates are not set
• 1: Start and end effective dates match the dates of the GL period in effect during the transaction
• 2: Start and end effective dates match the calendar start and end effective dates of the month of the transaction
• 3: Start and end effective dates cover a number of days, so the transaction effective date falls in that interval
End Eff Days
Value is zero or greater. Use if the End Eff Default Method is set to method 3. Shows the number of days that the start and end effective dates cover.
Include Yield
Set this to Yes to have the system include the yield percent established in Routing Maintenance (14.13.1) in the cumulative order cost.
Zero Balance WIP
The system uses Zero Balance WIP logic or Pulling WIP logic based on the setting in this field. The default setting is Yes, and the following functions are affected by this field: Backflush Transaction (18.22.13), Rework Transaction (18.22.17), Sub Shipper Issue (18.22.5.11), and PO Shipper Receipt (5.5.5.5).
• If Zero Balance WIP is Yes, then the system considers the quantity processed at the current milestone/non-milestone operation to be the quantity processed through all prior non-milestone operations up to the current operation.
• If Zero Balance WIP is No, then the system uses a Pulling WIP logic.
When the quantity processed at any milestone or non-milestone operation is more than the quantity processed at earlier non-milestone operations, WIP quantity in the input queue of the current operation and input/output queues of prior non-milestone operations are pulled appropriately. Components are backflushed at earlier non-milestone operations in order to balance the component quantity backflushed at the current operation.
When the quantity processed at any operation is the same or less than the quantity processed at prior non-milestone operations, only the input queue of the current operation is relieved
Reason Code Criticality
Specify the system response when an invalid reason code is entered while recording repetitive backflush transactions.
W (Warning): The system displays a warning message and pauses; the system accepts the value when you press any key. This is the default value.
C (Critical): The system displays an error message and prompts you to continue. If you choose No, the system returns to the Reason field so you can modify it. If you choose Yes, the system accepts the value.
Allow Zero Run Rate
Specify whether item-level records defined in Production Line Maintenance can include a 0 (zero) value in the Units/Hour field.
No (default): The item Units/Hour defaults from the production-line run rate. The system always uses the item run rate when calculating schedules for the item. Although you can change the default, you cannot set it to 0.
Yes: The item Units/Hour defaults to 0. Unless you change it, the system uses the production line run rate when scheduling the item. Otherwise, it uses the specified non-zero item-level value.
Set the field to Yes to define a global run rate for all items on each production line. In Production Line Maintenance, you can then specify a Units/Hour value at the production-line level and leave all or most item-level fields set to 0. If individual items are exceptions, you can define item-specific run rates just for them.
Auto Labor Report Field
The Auto Labor Report field is in Routing Maintenance (14.13.1) (and 14.13.2).
• For non-milestone operations, set the Auto Labor Field to Yes. This will automatically close the labor out at the standard value when the work order is closed. Labor reporting is not required.
• For milestone operations, if actual labor times are being reported, the field should be set to No. This indicates that the labor reported at that operation is the actual labor and will only be compared to the standard.
If a milestone operation has the field set to Yes, any labor reported will be added to the standard labor on that operation
Note: Setup is never part of automatically reported costs in Advanced Repetitive. This means that to record setup time at an operation, you must enter it manually using Setup Labor Transaction (18.22.15). The Auto Labor Report field does not affect setup. If there are change over times in the repetitive schedule records for an item, and you track costs, you should report this time as setup labor.
