Replacement of ETRM/IREP for Fusion Application is Oracle Enterprise Repository. You can access this using following link.
What Is OER?
Very simply this is a standalone catalog of technical information about Oracle’s Application products. For E-Business Suite users it equates to the iRepository tool (http://irep.oracle.com/index.html), or for PeopleSoft its similar to the PeopleSoft Interactive Services Repository.
It contains a wealth of information, with the primary purpose of facilitating the creation of Application to Application integrations, and creating extensions and customizations. With this detailed technical knowledge of the inner workings and API’s available for Oracle Applications a better level of code reuse and overall accuracy can be achieved.
Access is available either from Oracle’s globally shared public OER instance, or as part of your local Fusion Application instance deployment. Detail on creating a local OER installation is found in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository (E15745-07). The URL’s for OER will be:
- Your local instance URL: http://%5BFusionInstance%5D:%5Bport%5D/oer
- Oracle’s public instance URL: https://fusionappsoer.oracle.com
An OER login may be required, although Oracle’s public instance also supports guest access at this time.
OER catalogs technical components by various attributes, with the key ones being Name, Type, and Logical Business Area (LBA). LBA is the lower level of the Fusion Applications Taxonomy and is used to tag each technical object with the feature and product that it is owned by and associated with.
The general keyword search actually uses indexes of all the fields/attributes associated with a entry.
Whilst the basic Asset Search should suffice in most cases, and is a simpler UI, the Browse feature (IE required) provides many powerful features and graphical views, including an object hierarchy and the Navigator to display objects related to each other
How To Get The Most From Oracle Enterprise Repository For Troubleshooting Fusion Applications [ID 1399910.1]
Key features exist in Fusion Procurement approvals
There are many useful features that can be used with Fusion Procurement. Here are just some of the more significant examples:
- Both Serial and Parallel Approval for all document types.
- Various ways to configure responses, including features like first responder wins to help avoid lengthy processing times.
- Notification by email as well as several rich dashboard components (e.g. worklist) to show items currently awaiting action.
- Expiration, reminder and escalation features on pending actions.
- Delegation and vacation rules to forward actions to dedicated proxies as needed
- Rich notification content including clickable links to go directly to document details.
- Wide range of attribute values to use in the creation of custom approval processing rules.
What hierarchies can be used to generate approval lists?
Fusion Applications provides standard support for the following methods to derive the list of approvers
- Supervisor Hierarchy. This uses the HCM employee definition, leveraging the specific assignment of a supervisor person to each employee. AMX engine calls HCM to request the users that are in the hierarchy and passes in a starting position (normally the person submitting the purchasing document) and the maximum number of levels in the hierarchy to climb up.
- Position Hierarchy. This uses the Job definitions in HCM and selects all employees tied to the position that gets included in the selected hierarchy. Again this accepts the starting position (person) and the top job level to climb to before completing.
- Approval Group is simple a group of predefined people. This can be a static list or may be custom to generate at run-time based on approval document attribute data.
- Job Level. This works very similarly to the Position Hierarchy whereby it uses start and end Job definitions to traverse the hierarchy and select approvers.
What is Approvals Management (AMX)
Approvals Management (AMX) is an independent product that comes from the Fusion Middleware SOA Server, and provides general approval services to any product in Fusion Applications. AMX can be considered the meeting point between the powerful and flexible Oracle Business Rules capability and the advanced process control capabilities of Oracle Human Workflow.
The BPEL process that controls approvals has points at which it invokes the AMX services to initiate the approval process. The BPEL process controls the procurement process around approvals, however AMX and Human Workflow are responsible for the entire approval process.
AMX features include:
- The execution of rules that govern the selection and generation of approver lists.
- The sending of notifications to the participants on the generated list.
- The processing of responses from those approvers, and selection of appropriate next approval action.
- The return of the completion status back to the Procurement BPEL process for actioning.
Still eRecords and eSignatures are not supported by AMX in version 1.0.
For Complete Details Please refer to Document Approval in Fusion Procurement Products [ID 1319614.1]