Custom oracle workflow object type retrieved from seeded location instead of custom (4255217)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Custom oracle workflow object type retrieved from seeded location instead of custom
Description

When trying to add wft files, STAT is looking in wrong path. instead of looking at $MANAP_TOP/admin it is looking under $MANAP_TOP/patch/115/import/US
Cause

Custom products was registered as install.
Resolution

Run this query against the 12.1.x instance:
SELECT fa.application_id id, fa.application_short_name app
, fa.application_name, fpi.status, fpi.patch_level
FROM fnd_application_all_view fa, fnd_product_installations fpi
WHERE fa.application_id = fpi.application_id
If the product is custom then make sure it is registered as L

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title