WIP Move Transaction Upload Copy link

Description

Categories
Enginatics, Upload
Repository
GitHub
Creates move transactions as in the Move Transactions form: moves between operations and intraoperation steps, including moves into and out of Reject and Scrap, Move and completion transactions and Return and move transactions, for discrete jobs and for the repetitive schedules of a line and assembly. Each row is posted immediately, with backflush, completion, outside processing and autocharge resources as for a move entered in the form.

Upload Mode Create opens an empty sheet. Create, Update downloads the Queue, Run and To move steps of the selected jobs and schedules that hold a quantity, with their Available quantity, as new move rows: enter To Step and Quantity on the rows to move, rows left unchanged are not uploaded. An existing move is never updated; correct it with another move, for example a backward move or a Return and move transaction.

Completions, returns and overcompletions follow the Transaction Types and Allow Overcompletion parameters, not the function Move Transactions is launched from. A .csv or plain .xlsx file, and an add-in upload of a sheet another user downloaded, run with the parameter defaults of the template named in the upload, else with the parameter defaults.

With E-Records and E-Signatures set to Yes, discrete job moves create e-records as in the Move Transactions form, also where the move or material processing profiles are set to background, where the form creates none. A move that needs an e-signature is refused and has to be entered in the form. With the parameter cleared, moves are posted without e-records, as through the WIP move interface.

Not supported: operations added on the fly, manual resource transactions, serialized jobs and backflush lot and serial entry. A move fails when a backflush component is serial controlled, or lot controlled with a lot that cannot be derived; derived lots are not verified. Mandatory quality collection plans are not enforced, as by the WIP move interface, and No Move shop floor statuses always apply, also for users of the form function that overrides them.

To enter descriptive flexfield values, add the Move Attribute Category and Move Attribute1-15 columns, which show the segment prompts, to a template of your own.

SQL 214 lines

Parameters 10

ParameterTypeList of values SQL
Upload ModeLOV
:p_upload_mode like '%'||xxen_upload.action_update
Organization CodeLOV
x.organization_code=:organization_code
Sales OrderLOV
x.wip_entity_id in (select wrv.wip_entity_id from mtl_sales_orders_kfv msok, wip_reservations_v wrv where msok.concatenated_segments=:sales_order and msok.sales_order_id=wrv.demand_source_header_id)
Order LineLOV
x.wip_entity_id in (select wrv.wip_entity_id from wip_reservations_v wrv where wrv.demand_source_line_id=:order_line_id)
LineLOV
x.line=:line_code
AssemblyLOV
x.assembly=:assembly
JobLOV
x.job=:job
Transaction TypesLOV
Allow OvercompletionLOV Oracle
E-Records and E-SignaturesLOV