Wednesday Jun 12, 2013

How to Create A Minimal Enterprise Structure

This article describes a minimal representation of an enterprise
structure to support shared sourcing and procurement services to
requisitioners from multiple companies in multiple divisions and in
multiple countries. The document is targeted at implementation
consultants, particularly those deploying the Fusion Procurement
offering and aims to provide an introduction to the key concepts of
shared services and complement this introduction with a sample
organization representation. In addition to procurement professionals,
financial staff in the deploying enterprise will also need knowledge of
the deployment options and the reasoning behind the selection of a
particular model.

The Concept of Shared Service Centers

Shared Service Centers are corporate level organizations tasked with
conducting common operations that support the core lines of business of
an Enterprise. Technically, companies or other legally recognized
entities literally share the services, and the practice involves sharing
cost, profitability and taxation too. Informally, internal assignment of
services to businesses within an individual company is sometimes called
shared services too. The services provided can be in the areas of Human
Resources Management, Payroll, Subledger Processing, General Accounting,
Inventory Management (bonded warehouses, etc.), and Procurement. The
paper focuses on Procurement Shared Services.
Consolidating procurement services into a single procuring entity that
serves multiple business units within an enterprise could, if properly
implemented, result in the following benefits:
• Increased bargaining power, economies of scale, and cost savings
• Formation of a more focused procurement workforce
• Increase in buyer specialization and better generation of
specifications, and more accurate efficient catalog management
• Centralized and standardized Information deployed across the enterprise
• Centralized processes which could result in the reduction of
redundancy and effort duplication, and a more responsive procurement

For More Details see this white paper on MOS - Setting Up a Minimal Enterprise Structure to Support Procurement Shared Services [ID 1465612.1]

How to customize the user experience in Fusion Apps - Part 1 Composer Security Expressions

Access to resources such as taskflows, regions, buttons, and menus in Fusion Applications is granted by entitlements stored in a policy store and managed through the Authorization Policy Manager (APM).  Users are assigned roles comprised of  a set of entitlements (Oracle makes this quite easy  by providing you with job based seeded roles) authorizing them to  access  only the data and functions neccessary to perform their jobs and no more. On a more granular level it is also possible to control the rendering of certain UI objects by controlling their display attribute at runtime using Page Composer.

An example illustrating a conditional rendering of a Button is outlined below. The condition used in this example is the Role of the authenticated user.

2 Users and 2 Roles

In this example we have two HR Specialists, we want to prevent one of these users from saving Person records.

Figure1 Roles of Louise Beckham

Figure2. Roles of Megan Davis

Customizing the Object

Using Page Composer, the Administartor creates a security condition in Expression Builder. This condition states that the "Save" field on the "Person Management" page will be displayed if and only if the session authenticated user has the PER_HUMAN_RESOURCE_SPECIALIST_VIEW_ALL_DATA role. This happnes to be a role that our user Megan Davis has but that has not been granted to user Louise Beckham.

The statement, written in Expression Language (EL), used in this example is


NB: It is possible to have a include multiple roles as follows: #{securityContext.userInRole['Role 1'||'Role2']}, it is also possible to exclude a role by include a '!' at the beginning of the expression as follows: #{!securityContext.userInRole['Role 1']}

Figure3. Selecting the ADF Object that we want to customize

Figure4. Creating a dynamically calculated attribute value using Expression Builder

Different Display for Different Users

Below is how each of our two users sees the same UI that has now been conditionally customized. We can see the "Save" button displayed on Morgan's UI but not on Louise's.

Figure 5 - .Louise's UI without the Save Button

Figure 6.Megan's UI with the Save Button


This blog shares with the broader Fusion Applications community instructional material in the areas of Enterprise Structures, Extensibility, Integration and Security with the a focus on implementation. This blog is updated by the Fusion Applications Functional Architecture organization.


« June 2013 »