You can also bring up a user form to enter or complete your dataset. To open the user form, click on the ‘Forms’ ribbon button.
You can also double-click on any cell below row 10 to open the user-form.
Using the form you can enter or complete your dataset. The user form provides validation using data cached from your EBS instance during login.
Below, the key fields in the WIP Discrete Job Loader form is functionally described.
Fields marked with a yellow background are mandatory fields. For each record uploading through the loader, mandatory fields are required to fill in the values.
Greyed-out fields are read only. Those fields contain supplementary details for the user information purpose. These values do not upload during the uploading process.
Group ID and Interface ID fields are purely display only columns and these numbers will automatically be populated. Internally, these IDs are used in the upload. Do not modify or adjust these values as they are imperative for the upload process and are used as a part of the concurrent program and refresh process.
Job Number will be populated with a defaulted number from Oracle. If desired this can be changed to suit your own job numbers, however they cannot be the same as already existing numbers in Oracle.
Download by Start Date and Download by End Date fields are only used as a download filter criteria. Note that these fields can only support downloading via dates when the date value is in a date format, e.g. 12/08/2017. This will not work if the date value has a time, e.g.15-AUG-2017 07:00:00.
Assembly is a searchable field for the item that you wish to create the job for. It is a required field for both standard and non-standard jobs in this loader.
Unit Number enables to associate an end item model/unit effectivity number with the item. To enable this functionality, Oracle Project Manufacturing must be installed, the item must be under model/unit effectivity control, and the assembly(item) must have a model/unit number associated with it. If the item is not under model/unit number control, this field is disabled. See: Model/Unit Effectivity, Oracle Project Manufacturing Implementation Manual.
Bill Revision Date and Routing Revision Date are available on the form. Standard Oracle form rules are applicable to these dates i.e. if Oracle form allows selecting these dates for the combinations of the selected Job Type, assembly etc. then the loader will allow selecting these dates value.
Routing Reference allows searching items only when the job type is Non-Standard. When Routing Reference is selected, then the Routing Revision field is enabled. Routing Revision defaults the Routing Revision Date.
Explode Materials determines if the bill of material explodes or not. When the selected value is “No”, the job requires both start date and end date values. When Explode is “Yes” then only the start date is allowed.
When the Explode Materials value is “Yes”, it will reset the discrete job material requirements as per the bill of materials. When the value is “No”, it will keep the material requirement changes done for the selected discrete job.
(If the material requirement for a Discrete Job is updated when the job status was “unreleased”, then at the time of releasing the job the user must select Explode Materials’ value of “No”. Otherwise, the material requirement will be reset back to original as per the bill of material, and the previous changes will no longer be available.)
Scheduling direction decides the date expansion when updating wip job quantity. The selection of ‘forward’ will keep the start date the same and adjust the end date respective to the job quantity. The ‘backward’ selection will keep the end date the same and adjust the start date accordingly.
For a standard job,
- When Explode Materials is ‘Yes’, it will reset the start date/end date according to scheduling direction.
- When Explode Material is ‘No’, it needs both start and end dates and it will ignore the scheduling direction.
For a non-standard job,
scheduling direction is effective ONLY when the scheduling method is ‘Routing-Based’ and
- When Explode Materials is ‘Yes’, it will reset the start date/end date according to scheduling direction.
- When Explode Material is ‘No’, it needs both dates and it will ignore the scheduling direction.
Tolerance Type is an optional field. However, when a tolerance type is selected then the Tolerance Value field becomes required. Furthermore, when the Tolerance Type is null then the Tolerance Value must be blank.
