MSCA - Automatic Detailing Of WIP Returns During Backward Moves
Last updated on JULY 07, 2017
Applies to:Oracle Work in Process - Version 12.1.2 and later
Information in this document applies to any platform.
Is the following behavior intended functionality?
Should the move transaction form in MSCA for WIP allow update to project, subinventory and locator when:
a) the assembly is set to Predefined serial control,
b) single component on work order is serial controlled 'at receipt',
c) component has been backflushed onto the work order via assembly pull or operation pull,
d) serial move transaction (or completion transaction) has occurred which backflushed the component and associated the component serial number to the parent serial number
e) move backward through operation occurs and lands user to the form where a backflush reversal (WIP Return) could occur.
Our experience is that the MSCA application does not allow the user to update the subinventory/locator during WIP return - application appears to 'know' the previously issued serial number and is assuming that this is the item/serial to WIP Return
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms