Defer Backflush Option Missing APPS10

Hi The option in the new form is “Background Job”

Hi dameenda,

Thank you for your reply - When we tested using the Background option in APPS10 the only difference we can see is - if there is a shortage on a production receipt this will fail in the background without creating a receipt.

I believe the advantage we had of using the Defer Backflush capability is that the operation would create a receipt even with the component shortage - we could then continue to move the stock and address the shortage later in the day. This is so one line is not waiting for the other to be completed.

In this scenario - is there a way of us still achieving this outcome?

Many Thanks,

Dan

@DanTrayton have you been able to accomplish this result in AAPS10?

dameenda wrote:

Hi The option in the new form is “Background Job”

 

Hi @dameenda , could you please clarify if this the same option in IFS Cloud as highlighted below?
And could you please clarify if there are any functional behavioral difference here compared to App8?
 

Thank you,
Dinushi

HI Dinushi, Yes

Hi, The reason why we did this initially was because we needed to have all issue transactions and auto-reporting transactions AND the receipt of the manufactured part in one go so to say, because customers ended up sometimes with strange PSDIFF transactions (or was it when they were using actual costing - I don’t remember the details here at top of my head, but it was related to costing)

Cheers,

Mats 

Thanks @dameenda and @majose for the input. Much appreciated!

The fact that IFS removed the option to be able to generate (add to inventory) a part from a production receipt -when the components are not in the system (deferred backflush) is really impacting our company, and our ability to move from Apps8 to IFS Cloud. The answer given by IFS -that we needed to better our inventory controls and processes in the system, was one that was not welcomed by upper management.