Procurement - EBS (MOSC)

MOSC Banner

PO_CHANGE_API1_S.UPDATE_PO removed concurrent request context before launching PO Approval workflow

edited Aug 24, 2015 4:22PM in Procurement - EBS (MOSC) 3 commentsAnswered

In package PO_REQAPPROVAL_INIT1.Start_Wf_Process, line #1787, it UNNECESSARILY calls

fnd_global.APPS_INITIALIZE (l_user_id, l_responsibility_id, l_application_id);

before starting workflow. This is called by update_po API to approve the PO.

when called within a concurrent request, it removes concurrent context including FND_GLOBAL.CONC_REQUEST_ID so that the concurrent log stopped where the API is called.

Oracle does not want to remove the UNNECESSARY TROUBLEMAKING line that was the root cause of the issue.

Anybody experienced the same issue and have some workaround?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center