The request body is of type Mes.WebApi.Models.V3.Prod.SplitJob.

The response body is of type Mes.WebApi.Models.V3.Prod.Job.

This endpoint allows the quantity required for a job to be split into two jobs so that parts of it can be run on different machines.

The following Job model properties are required.

• To identify the job: wo_id, oper_id, and seq_no.
• To specify the quantity of the job to be split to the new job: qty_at_start.

For the state_cd, the following values are allowable: 1 (New), 2 (Ready), 5 (Suspended), or 6 (On Hold).

If not defined or the supplied code is invalid, then the default is the state of the current job, or the default is 2 (Ready) if the current job is either 3 (Running), 4 (Complete), or 7 (Canceled).

Additional Information

The wo_id and oper_id (operation) are retained; only a different seq_no is created for the new row in the Job table. The qty_at_start property value must be less than remaining quantity to be produced (qty_reqd – qty_prod) of the existing job, as the qty_reqd of the original job will be reduced by this amount.

For the call to succeed, the caller (user) ID passed by the authorization token must be valid and have sufficient privileges to split jobs.

The optional parameters can be used to set certain values in the new job that might be different than the original. If they are not specified, then the column values from the original job are used with the following exceptions:

• run_ent_id = null
• sched_pinned = false
• qty_prod = 0
• qty_prod_erp = null
• qty_rejected = 0
• qty_rejected_erp = null
• concurrent_link = 0
• act_start_time_utc = null
• act_finish_time_utc = null
• sched_start_time_utc = null
• sched_finish_time_utc = null

All rows in the following tables will also be cloned: Job_Bom, Job_Bom_Step, Job_Spec, Job_Step, Job_Route, and Job_Attr, with the following exceptions in the Job_Spec table:

• act_spec_value = null
• act_time = null
• complete = 0