Backflush Not Getting Created On Work Order-less Form For Multiple Schedules At a Time

(Doc ID 2337183.1)

Last updated on DECEMBER 08, 2017

Applies to:

Oracle Work in Process - Version 12.2.6 and later
Information in this document applies to any platform.

Symptoms

On WIP - Oracle Work in Process, 12.1.3 version, Work Order Definition

ACTUAL BEHAVIOR
----------------------
If users have more that one assembly listed on work order-less form and form is exited without hitting the save button, users are presented with a save-warning dialog box. If users commit/save the form via the save-warning dialog, only the last assembly listed on the form will get the backflush (wip material issue) transactions created, but all completions are saved.

EXPECTED BEHAVIOR
-----------------------
Expect that all assemblies on form will be processed correctly having the backflush records created correctly.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. From WIP responsibility,
2. select work order-less transaction form.
3. WIP Completion transaction is selected, and a list of assemblies are entered.
4. the form is exited without saving, when the warning box is displayed asking if we want to save or not, we select "yes" and the form closes.
5. Upon inspection, we notice that only WIP ISSUE transactions are created for the last assembly in the list only. (or the last highlighted)

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms