You can view, update, delete, and resubmit records (rows) that have failed validation and remain in the Work Order Interface (WIP_JOB_ SCHEDULE_INTERFACE) table. You can view the error messages associated with failed records. Error messages assist you in updating failed records before resubmission.

You cannot insert new job and schedule records into your interface table using this window.

Prerequisites

• Insert job and schedule data into the Work Order Interface table. See: Work Order Interface, and Open Job and Schedule Interface, Oracle Integration Repository, irep.oracle.com

   To find job and schedule interface records:

1. Navigate to the Pending Jobs and Schedules window. The Find Pending Jobs and Schedules window appears.

2. Enter your selection criteria.

   You can find all records with a specific Group ID. You can also find all records that have a specific Process Phase (Validation, Explosion, Creation, or Complete), Process Status (Pending, Running, Error, or Complete), Source Code, Source Line ID, Load Type (Create Standard job, Create Repetitive Schedule, Update Discrete Job, or Create Non-standard Job), or are for a specific Organization. You can also search for a specific Job, Assembly, or Line and Assembly.

3. Choose the Find button. The Pending Jobs and Schedules window appears with the results of your query.

   To view job and schedule interface records:

1. For each record, you can view the following information using the Pending Jobs and Schedules window's tabbed regions:

   • Process: Group ID, Phase, Status, Request ID, Source Code, and Source Line:

   • Header: Load Type, Organization, Job, Line, Assembly

   • Quantities: Discrete Start and Net Quantities, Repetitive Daily Quantity and processing Days, and Total Quantity (both discrete and repetitive)

   • Discrete: Class, Lot Number, Schedule Group, Build Seq, Project Number and Task

   • More: Status, Firm planned option, Demand Class, Scheduling Method, Unit Number

   • Dates: First Unit Start Date, First Unit Completion Date, Last Unit Start Date, and Last Unit Completion Date

   • Bill: Reference, Alternate, Revision, Revision Date, Supply Type

   • Routing: Reference, Alternate, Revision, Revision Date, and Completion Subinventory, and Completion Locator

   • Description: Description and Created By

   To view error details for failed job and schedule records:

1. In the Pending Jobs and Schedules window, select the failed (Status=Error) record.

2. Choose the Errors button. The Pending Job and Schedule Errors window appears.

   All errors for the selected record are displayed. The Type indicates whether the failed record produced an Error or a Warning. The Message explains why the transaction failed. Using these messages you can determine what fields need to be updated.

   To update job and schedule interface records:

1. Select the record to update.

   You can only update records with a processing status of Error. You can update all fields except the Group ID, processing Phase, processing Status, Request ID, and Total Quantity.

   In general, the default values are derived in the same way that they are derived when you manually enter discrete jobs and repetitive schedules in the Discrete Jobs and Repetitive Schedules windows. See: Defining Discrete Jobs Manually and Defining Repetitive Schedules Manually.

2. In the Process tabbed region, enter the Source Code and Source Line.

   The Source Code and Source Line identify the source of the interface record. For example, if you load jobs and schedules from different sources, you can use a difference Source Code to identify each.

3. In the Header tabbed region, select the Load Type.

   The Load Type indicates whether the current interface record is a planned order, update recommendation, or suggested repetitive schedule.

   Possible values include:

   • Create Standard Discrete Job

   • Create Pending Repetitive Schedule

   • Update Standard or Non-Standard Discrete Job

   • Non-Standard Discrete Job

4. Select the Organization.

   You can only select enabled organizations. See: Creating an Organization.

5. Select the Job, Line/Assembly, or Assembly.

   The assembly is the item you are building. An assembly is optional for non-standard discrete jobs.

   Select the production Line on which to build the repetitive assembly and the repetitive Assembly to be produced on that line.

6. In the Quantities tabbed region, enter the Start Quantity and Net Quantity for discrete jobs or the Daily Quantity and number of Days for repetitive schedules.

7. In the Discrete tabbed region, select the class.

   For records with a Load Type of 4 (Non-Standard Discrete Job), you can select any active Asset Non-standard, Expense Non-standard, or Project accounting class. For records with a Load Type 1 (Create Standard Discrete Job), you can select any active Standard Discrete accounting class.

8. Select the Lot Number.

9. Select the Schedule Group.

   You can optionally assign discrete jobs to any active schedule group. See: Defining Schedule Groups

10. Enter the Build Sequence identifier. See: Build Sequencing.

    The combination of schedule group and build sequence must be unique for each job.

11. Select the Project and, if required, task.

    You can only select a project if the current organization's Project References Enabled parameter is set in Oracle Inventory. You must select a task if the Project Control Level parameter is set to Task and you have entered a project. See: Organization Parameters Window and Creating Projects.

12. On the More tab, select a status for the job or repetitive assembly/line.

    You can select a status of Unreleased, Released or On Hold for any record. See: Discrete Job Statuses or Repetitive Schedule Statuses.

13. Select whether the discrete job or repetitive schedule is Firm.

14. Select the Demand Class.

    You can select any enabled and active demand class. See: Overview of Demand Classes, Oracle MRP User's Guide and Creating Demand Classes, Oracle MRP User's Guide.

15. For discrete jobs, select the Scheduling Method.

    You can choose one of the following:

    Routing: You can schedule discrete jobs using routing lead times, if the Load Type is 1 (Create Standard Discrete Job) or 3 (Update Standard or Non-Standard Discrete Job).

    Item Lead Time: You can schedule discrete jobs using item lead times, even if the item has a routing, if the Load Type is 1 (Create Standard Discrete Job) or 3 (Update Standard or Non-Standard Discrete Job).

    Manual: You can manually schedule your discrete jobs by entering start and/or completion dates.

16. Enter the Unit Number. If you have Oracle Project Manufacturing installed, this enables you to associate an end item model/unit effectivity number with the item.

    The item must be under model/unit effectivity control, and you 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.

    You can update the assembly unit number through WIP Mass Load for discrete jobs that are unreleased, project related, and use unit effectivity. You can change job status from Unreleased to Released in the same process.

17. In the Dates tabbed region, enter a First Unit Start Date (FUSD), First Unit Completion Date, a Last Unit Start Date, or a Last Unit Completion Date (LUCD).

    If you are using Manual scheduling, enter both a FUSD and a LUCD.

18. In the Bill tabbed region, select the bill of material Reference for your non-standard discrete job.

    You can select bill of material reference if the Load Type is 3 (Update Standard or Non-Standard Discrete Job) or 4 (Non-Standard Discrete Job).

19. Select the bill Alternate if creating a discrete job.

    You can select an alternate bill if alternates have been defined for the assembly. For non-standard jobs, you can enter any alternate defined for the bill Reference specified.

20. Select the bill Revision and bill Revision date. See: Item and Routing Revisions.

21. Select the Supply Type.

    You can select any of the following Supply Types: Push, Assembly Pull, Operation Pull, Bulk, or Supplier. See: Supply Types.

22. In the Routing tabbed region, select the routing Reference your non-standard discrete job.

    Routing references are used to create routings (operations and resource requirements) for non-standard discrete jobs, however, they are not required.

23. Select the routing Alternate if creating a discrete job.

    You cannot enter a value here unless you have defined alternate routings for the assembly you are building. For non-standard jobs, you can enter any alternate defined for the routing reference you specify. See: Primary and Alternate Routings.

24. Select the routing Revision and Revision Date. See: Item and Routing Revisions .

25. Select the Completion Subinventory, and if required, locator.

    You can select a Completion Subinventory if your Load Type is 1 (Create Standard Discrete Job) or if your Load Type is 4 and you have an assembly.

26. In the Description tabbed region, enter the Description

    You can optionally enter a Description that can be used to identify jobs on standard reports. They can be up to 240 characters of alpha numeric text.

27. Enter the Created By identifier.

    You can update the name of the user that created the transaction is displayed. This field can be updated.

28. Save your work.

   To select and resubmit pending job and schedule records:

1. From the queried records displayed, select which to resubmit. .

   You can only resubmit records with a processing status of Error. If you do not mark a row for re-submission, you can still update it but the WIP Mass Load Program does not process it again when polling the Open Job and Schedule Interface table.

   Note: Although Assemble to Order (ATO) jobs with errors are listed in the Pending Jobs and Schedules window, ATO jobs cannot be resubmitted in this window. Correct the errors for failed records, and resubmit them using the all flash array program.

2. Choose the Submit from the Tools menu.

   Resubmitting records resets their process status flags to 1 (Pending), and nulls their Group ID. The next time the WIP Mass Load Program polls the Open Job and Schedule Interface table, these records are reevaluated.

   To delete job and schedule interface records:

1. Select the record to delete. .

   You can only delete records with a processing status of Error. When you delete records, their corresponding error messages are deleted from the Errors table (WIP_INTERFACE_ERRORS).

2. Choose Delete from the Edit menu.