This client extension provides the ability to derive the To Operation Sequence and To Operation Step when using the Express Transact Components page during a move transaction. This program can have several possible results:
Errors in the processing:
The move transaction cannot be performed.
A non-null value for one of sequence/step combinations, then transaction errors.
Success and both the operation sequence and operation step have values returned; those operation sequence and step values are used in the move.
Success but both the sequence and the step are null, and derivation logic is used to determine move values.
A PL/SQL package: WIP_WS_CUSTOM, contains the custom programming instructions invoked.
Procedure: MOVE_TO_STEP_HOOK
| Parameter | IN/OUT | Type | Description |
|---|---|---|---|
| org_id | IN | NUMBER | Identification of the organization. |
| wip_entity_id | IN | NUMBER | WIP entity identification of the job. |
| fm_op_seq | IN | NUMBER | Originating operation sequence number that the assembly is being moved from. |
| fm_op_step_type | IN | NUMBER | Originating operation sequence step number that the assembly is being moved from. |
| fm_dept_id | IN | NUMBER | Identification of department where assembly is being moved from. |
| to_op_seq | IN OUT | NUMBER | Operation sequence number where assembly is being moved. |
| to_op_step_type | IN OUT | NUMBER | Operation sequence step where assembly is being moved |
| return_status | OUT | VARCHAR2 | Value indicating performance status, choices are:
|
| return_message | OUT | VARCHAR2 | Error string the program returns. |