Documentation >
MAC-PAC Reference and Help >
Reference File Categories >
JIT PLANT DEFAULTS
Function Select
RFK03S01 - Function Select
WILLIAMS COMMON FEATURES 2/25/93
DSP01 REFERENCE FILE CATEGORY K03 FUNCTION SELECT
Category Name JIT PLANT DEFAULTS
PLANT
Category Key BEL
XXX
Request Code 4
1 - Add
2 - Change
3 - Delete
4 - Inquire
F2=Command F3=Exit F7=End Category F8=Display List
F9=Inquiry
This JIT Plant Defaults screen contains default processing information for JIT plants. Two fields on the Detail screen are for memo purposes only, and are reserved for future use.
PLANT
Required. Must be a valid plant defined on the Plant/Warehouse Description File.
Detail
RFK03S02 - Detail
WILLIAMS COMMON FEATURES 5/31/95
DSP01 REFERENCE FILE CATEGORY K03 INQUIRE
Category Name JIT PLANT DEFAULTS
PLANT
Category Key BEL
PRODUCTION CENTER SYNCHRONIZATION GRACE PERIOD
Data MSDAILY 000
XXXXXXX NNN
PREV REVISION LEVEL USE USE PRIM PART/PROD CTR REL
Data N N
Y Y
FORCE AD-HOC FA CREATION ALLOW FLOW RECPT OVER-REVERSAL
Data N Y
Y Y
F2=Command F3=Exit F9=Inquiry F10=Function Select
PRODUCTION CENTER
Required. Must be a valid production center defined through Production Center Maintenance.
SYNCHRONIZATION GRACE PERIOD
(This field is for memo purposes only; there is no validation. This field is reserved for future use.) This numeric field is used to determine a JIT synchronization date, which is offset from today's date by the number of days defined in this field.
For example, if the value in this field is 000, the synchronization of a production center or part would close out schedules earlier than today--the same as the current processing. If the value in this field is 005, and today is February 11, 1996 (02/11/96), (assume a 7-day working calendar), then schedules earlier than 02/06/96 would be synchronized, or closed, and schedules from 02/06/96 to 02/10/96 would remain in their existing status--either planned or firmed.
PREVIOUS REVISION LEVEL USE
(This field is for memo purposes only; there is no validation. This field is reserved for future use.) Valid values are Y (yes) or N (no). This flag controls which flow authorization would be accessed by the JIT Production Schedule Programs (maintenance/inquiry) when two flow authorizations exist for different revision levels on the same day(s). This can occur when production exists on day X for revision level 001, but the user creates an ad-hoc flow authorization on day X for revision 000.
USE PRIMARY PART/PRODUCTION CENTER RELATIONSHIP
Valid values are Y (yes) or N (no). If this flag is set to Y, the programs listed below will always use the default or primary part/production center relationship when accessing information for either the parent and/or component parts related to receipts and/or issues. This is true even if a non-primary production center is entered on any of the Function Select screens for the following programs: JT120E, JT125E, JT140E, JT145E, JT150E, JT170E, BC120E, BC140E, and BC170E. (This does not apply to BC150E, because no JT160M/JT160ML1 files are defined.)
Therefore, all JIT/productivity information will come from the Part Master Maintenance Productivity screen (DE100S06) for the parent and/or component part, even if non-primary part/production center relationship records exist. With this feature, you may create JIT production schedules in non-primary production centers. If non-primary part/production center relationship records exist for the parent or component part, but are incomplete (e.g., relief/producing locations are undefined; no inventory in the component's relief location), the JIT module will ALWAYS use the default or primary part/production center relationship.
Backflush issues would use the component part's primary part/production center relationship record relief location.
The following example demonstrates what happens if the flag is set to N (no):
Assume that the primary production center for parent part "A" and components "B" and "C" is PC01. (This is defined in Part Master Maintenance and on the default part/production center relationship.) However, non-primary part/production center relationships exist for "A," "B," and "C" in PC02. "B" and "C" are backflushed components, and a production schedule exists for "A" in PC02. If you enter a flow receipt for "A" in PC02, the non-primary part/production center relationship will be accessed for "A," "B," and "C," and backflush locations for "B" and "C" will come from their relationship to PC02. If NO relationship existed between PC02 and "A," "B," and "C," the logic would revert to the parts' relationship to their primary production center--PC01.
FORCE AD-HOC FLOW AUTHORIZATION CREATION
Valid values are Y (yes) or N (no). If the flag is set to Y, then all parts in this plant will use the plant, part, production center, revision level, and transaction date (probably today's date, unless you are back dating a receipt), against which to receive. If no such flow authorization exists, an ad-hoc flow authorization will be created that meets the criteria.
If the flag is set to N (no), the flow receipt will be recorded against the earliest flow authorization with the same plant, part, production center, and revision level. This flow authorization may be in the past or past due (over/under bucket in Production Schedule Maintenance/Inquiry).
ALLOW FLOW RECEIPT OVERREVERSAL
Valid values are Y (yes) and N (no). If the flag is set to Y (yes), you will be able to overreverse a flow authorization receipt. This would permit the reversal quantity to be greater than the original receipt quantity. If the flag is set to N (no), you will not be able to overreverse a flow authorization receipt.