2.7 Bulk move and batch-to-Finish for workshop tasks

2.6.1 Business Scenario Description

In general, the production of discrete tasks in a large number of tasks, the operation of the task of moving and report as finished operations, one to do, the pressure on the operator is very high. In order to simplify the business operations of such operations and reduce human error, in order to achieve the discrete task of bulk operation movement and batch finished inventory.

2.6.2 Business Scenario Logic control

1. The criteria for standard discrete lookups require that the following field information be established for the operability of [bulk Move/Batch completion]:

1) Tasks, task Description, assembly parts, assemblies description;

2) There is no route (need to query the assembly has no route, the column is also not allowed to edit, there is a "Y", no display "N";);

3) The completed sub-inventory (editable, whose value set is a valid sub-inventory within the organization), planned quantity, completed quantity, remaining quantity;

4) In addition to the completed sub-inventory can be edited, the above mentioned fields are only displayed, not editable;

2. Feedback fields are feedback on the results of bulk movement/completion and are not editable by the user. There are only two types of transactions that need to be performed: One is bulk moving, and the other is batch completion;

3. The discrete tasks selected by the conditions are only allowed to be manually checked to ensure that the [bulk move/Batch completion] operation is required.

4. Bulk move:

1) All items in the bulk move parameter are valid only if the transaction type is bulk move and not valid when the transaction type is bulk complete.

2) When bulk moving, the required parameters include: Starting operation, starting step, terminating operation, terminating step, quantity to be moved;

3) for the starting operation, the starting step, the termination process, the termination step of the four fields, if there is a value is the default fill in the value, if no value is determined according to the following conditions:

A-start Operation no value defaults to the first operation of the task;

B-Start step no value defaults to queued steps;

C-Stop Operation no value defaults to the last operation of the task;

D-Stop step no value defaults to move step;

4) for the number that needs to be moved, there are two options for the user to choose, one is a specific number, the user can enter a value in this text box, representing all the tasks need to move the same quantity, and the other is the "default maximum number of moves", that is the maximum amount of each task in the starting operation, the starting step,

5) When the transaction type is bulk move: In addition to the "No Route" column is "N", the check box is not checked, the rest of the situation needs to be optional, that is, no route assembly is not allowed to do mobile transaction processing.

6) You can "view the number of task operations", and for the task line where the cursor line is located, when the cursor is focused on a task that has a route line, you can see how much of the assembly is on each step of the task.

7) You cannot "view the quantity on a task operation" when the transaction type is bulk complete or when the task has no route.

5. Batch completion:

1) When the transaction type is bulk complete, when the remaining quantity is 0 o'clock, the check box is not selectable and the rest of the situation needs to be optional. That is, all completed tasks do not need to be completed;

2) "Quantity to be completed" defaults to "remaining quantity", which the user can edit, but the system should be able to automatically prompt for errors when the number of edits is greater than the remaining quantity.

3) When doing bulk transaction processing, you should search for each task and do it as finished. We need to follow the sequence number of the operation, the steps within the process to extract the quantity until the completion quantity is reached.

4) Operation sequence number according to from small to large, and then for each work sequence number, its sequence of steps is: queue, run, move, reject, scrap;

A-such as an assembly of the process line has 4 processes, respectively, 10,20,30,40;

B-the order in which the quantities are extracted is:

10: Queue, run, move, reject, scrap;

20. Queue, run, move, reject, scrap;

30. Queue, run, move, reject, scrap;

40. Queue, run, move, reject, scrap;

5) When you are done with bulk transactions, you need to feedback the results based on the processing results:

A-processing success;

The number of assembly parts in the start step of the B-start operation is less than the number to be moved;

c No termination process;

D-no initial operation;

2.7.3 Business Solution Execution Control

Not currently