This content has been marked as final. Show 2 replies
This is a problem with AME and OLM. It is described in Metalink article 338508.1.
The synopsis of the article is:
AME in 11.5.10 and above provides 3 major enhancements: -
- Generalized subordinate item class
- Parallel approvers
- Support for HR position approver types
To take advantage of these features the product teams that integrate with
AME should make use of new APIs in 11.5.10 e.g., AME_API2 and AME_API3.
If the product team is using pre-11.5.10 API, ie, AME_API and any of the
11.5.10 feature is set ON in customer instance, then behaviour would be not
predictable. Hence, starting from AME.A rollup (4433707), AME has introduced
a check in AME_API (see bug #4403150)that will identify such setup and throw
the following error: -
"Oracle Approvals Management has found parallelization configuration whereas
the context in which AME invoked using ame_api does not support parallelization."
It would appear that the OLM product team has not 'taken advantage' of these facilities yet.
Perhaps Anders can comment further?