Professional Documents
Culture Documents
A: Multiple approval chains (chains of authority) means there can be more than one
approval hierarchy for a single expense report. For example, if all expenses are
charged to two cost centers, there could be two approval chains with the cost
center owners as the starting point for each approval hierarchy.
[top]
[top]
A: No. Managers can only approve or reject expenses as a group. This is true
whether the manager is responsible for approving the entire expense report, or
just a subset of the expenses.
[top]
What are the different approval hierarchies I can use for multiple approval
chains?
A: You can enable multiple approval chains for cost center approvals, project
approvals, and award approvals.
[top]
Step 2: For Approval Type, select 'one job-level chain of authority per line item'
(Note: only job level authority is available for line level approvals)
Step 3: For Approval, select the desired level of approval
Step 4: For Ordinary-Condition Line-Item Attributes, select the attribute per your
requirements (typically this would be an expense line amount attribute)
Step 5: For Ordinary Line-Item Conditions, select the appropriate condition.
[top]
Why would I use cost center business managers as the primary approver instead of
using the cost center owners?
A: One reason would be to free up the time of cost center owners to perform more
value-added activities. Therefore, if your enterprise defines separate cost center
business or finance managers to approve expense reports and other transactions,
you can define them as the primary or default approver.
[top]
A: To define cost center business managers, it is recommended that you use the
cost center organization's descriptive flexfields (DFF's). To do this, perform the
following (see Question # 5 for related setup steps):
In the Oracle HRMS Descriptive Flexfields Segments window, query the Add'l
Organization Information segment Title. Then, define a context code. We suggest
using the following name: Organization Name Alias (same name as the context code
used for the cost center owners flexfield).
In the Segments window, define a segment called Business Manager (recommended
query assumes the Column is ATTRIBUTE2). To validate the manager names, select
HR_COST_CENTER_MANAGER as the value set.
Complete the DFF setup (freeze flexfield definition, and click Compile)
In the Organization window, query the organization for which you need to define
the cost center business manager. For the Company Cost Center classification,
click the Others button and select Reporting Information.
In the Additional Organization Information window, click in the DFF field and
enter the business manager information.
In AME, for the LINE_ITEM_STARTING_POINT_PERSON_ID attribute, define a query to
obtain the cost center manager based on the entered cost center.
[top]
A: In 11i.OIE.E, 11i.OIE.F and 11i.OIE.G, you must create and define the
transaction type and all non-mandatory attributes. You must also define the
mandatory attributes provided by AME. In 11i.OIE.H, OIE seeds the transaction type
and definitions for all mandatory attributes. In addition, OIE seeds non-mandatory
attributes based on product management's understanding of OIE customer's approval
requirements.
[top]
Do you have any examples of line-level attributes and the related queries?
[top]
A: If you are using 11i.OIE.H or a later release, you do not need to configure the
LINE_ITEM_STARTING_POINT_PERSON_ID query. If you are on an earlier release, the
query assumes the cost center segment is the 2nd segment in your organization's
accounting flexfield structure. If the cost center segment is in a different
position, change the position reference in the following query line: AND
GLCC.SEGMENT2 = FLEX_CONCATENATED. (Note: If you use project manager approvals,
you do not need to configure the query since it does not reference your accounting
flexfield structure.)
[top]
A: The rules will be ignored when AME builds the approvals chain since the
attribute will always be null.
[top]
[top]
A: No. Line-level rules can only be used with list-creation rule and list-creation
exception rule types.
[top]
[top]
What is the release schedule for the enhancements mentioned in Question # 14?
A: AME development plans to deliver these features, along with other enhancements,
as a standalone patch. The patch will be compatible with 11.5.9, and will be part
of the 11.5.10 release. Before customers can take advantage of the new AME
features, OIE development will need to perform some design and coding activities
to uptake the features. OIE development has not yet scheduled the uptake of these
enhancements.
[top]
Are there any other resources I can use to help with my implementation?