Objective : In this article we will learn how to Unlock XELSYSADM account in OAM with Fusion applications.

If xelsysadm user account gets locked , then you can unlock the user using ODSM.

Perform the following steps in order to unlock the xelsysadm account .:

1)Enter the odsm url http://host:port/odsm

2) Click on Connect to directory and then on the respective OID connection

3) Enter the password for connecting to OID and click on Connect

4) Click on Data Browser

5) Search for xelsysadm user

And click on the xelsysadm user

6) Click on Attributes tab

7) Set the oblockouttime and oblogintrycount values to 0  and click on Apply

8) Once the values for these attributes are set to 0 , you will be able to login using xelsyadm user .

Introduction

While this article is about creating a flow pattern it makes sense to understand what a flow pattern is and the need/importance/advantages of using the same. In simple words a Flow pattern is a combination of multiple Task Flows (seeded/manual actions) along with a provision of creating security options (to ensure who would be allowed to view/edit and execute the same).

We must have seen the guided train stop flows in Oracle Fusion Applications be it during New Hire or during Extract Creation yes you guessed it right they are indeed a Payroll Flow Pattern.

Similar to Task Flows in EBS suite where we can have completely custom processes build with a combination of Reports, Checklists, Sub Tasks, Parameters Flow patterns in Fusion also does the same.

In short a Payroll Flow Pattern may be defined as a sequential process which has certain subtasks supposed to be performed one after another.

One important thing to note here is that while Flow Patterns are generally associated with Payroll the same is used through-out the Application with Create Accounting, Create Batch,……… being the commonly used ones.

Complete details about the same can be found here .

We may add single or multiple tasks within a flow pattern and the same holds true for BI Publisher Reports and HCM Extracts too. Imagine a situation where you want to run a BI Report, verify the data using some checklists and then perform another task. Designing a Flow pattern would help you in accomplishing the same. In this example we will create a Flow pattern for a Custom BIP Report and we would be able to view the output. The Output file will be based on the template of the BIP Report.

This article would also try to address the following important questions:

Q1. When should we use Payroll Flow Patterns?

Ans. We can implement Payroll Flow Patterns to incorporate seeded flows along with checklists and custom reports/extracts/processes.

Q2. Is this just a way of stitching together multiple pre-defined tasks delivered by Oracle in a set?

Ans. The answer to this question is a bit descriptive one and we would need to go through the below table to understand the list of available tasks:

So we can see that although the Activity Type are fixed but it gives a lot of options which can be used and multiple permutations can be used to create a new flow pattern

Q3. Does it allow creation of new tasks or one can only use the seeded prebuilt ones?

Ans. Its both a YES and NO. Yes if you create a Custom HCM Extract / BIP Report / Custom Process, NO Otherwise.

Q4. Does this allows one to Build a Flow as an Activity is Performed (say Journal Entry Creation), followed by another ( Journal gets Approved), which then would get extracted and send as a flat file via BIP

Ans. Yes this can be accomplished. You would need to create one flow of Activity Type Accounting and one flow with Activity Type Statutory (Task Name – Run BI Publisher Report) and then create a third flow which would combine both of them.

So that’s about the theory part and now let-us begin with creating a Flow Pattern based upon a BIP Report.

As a first step login to the application with a user having appropriate roles (user should have access to Payroll Checklist and Data Exchange Area which are present in the Application Roles Payroll Administrator and Human Capital Management Integration Specialist Role).

We would be using hcm_impl user (who has the required roles as mentioned above) in this example.

Next we would need to navigate to the ‘Manage Flow Patterns Task’ and there could be multiple ways of reaching the same. They are:

1. Using Checklists

From the navigator icon click on ‘Checklists’ link which would take you to a new page where in you should be able to locate the Manage Payroll Flow Patterns as shown below (with help of two images)

2. Via Data Exchange -> Refine Extracts

We may even navigate to the Flow Pattern area using the Data Exchange-> Refine Extract Option (shown below)

3. From Setup and Maintenance

A click on the ‘Go to Task’ Icon takes us to the following screen:

One important observation at this point is the fact that out of the above 3 options mentioned only the 3rd option (Setup and Maintenance) provides us the feature of creating new payroll pattern. As we can clearly see the icon only on this page the other two pages are used for search and making edits ( only after a  Pattern has been created).

So we will now click on the icon and a new page will appear which would ask for a specific legislative data group for which we want this pattern to be created. We are interested in running a BIP Report here which would fetch data for all Legislative data groups hence we would keep the same as blank and proceed.                                             

When you click on the ‘Continue’ button, a new page will appear where we need to fill the relevant details as shown:

Click on Next and choose the ‘Yes’ radio buttons for ‘Flow Task Start Notifications’ / ‘Flow Task End Notifications’ / ‘Warning Notification’ and ‘Error Notification’

Once the appropriate radio button options are selected move on the next train stop (using the ‘Next’ Button) which will take you to the ‘Task Sequence’

The first task is the Start Task followed by Run BI Publisher Report and the last one being the End Task.

In the next step we should de defining the parameters for the flow pattern as shown below (Yes we need to click on the next button to move on to next train stop)

As shown above we do not need to enter any detail ( for this example as we are using a BIP Report which do not has any parameters and this is done specifically  ) and move to the next step where we need to enter the Report name and Report path

Next use the icon to delete all parameters except the report name. We do not need all the other parameters namely: Legislative Data Group (The Report we are going to use fetches data which is independent of any specific legislation) and the other parameters (argument 1, 2 ,3 .. are used in case the BIP report needs input parameter, the current report being used in this example does not has any input parameter).

After you remove the parameters there will be two parameters left as shown:

Report Name Details Screenshot (post populating the details as displayed in table above)

Report Path Details Screenshot(after populating the details as displayed in table above)

Once we have populated all the tabs we may move to the review tab to verify the same.

Once the verification is complete click on the Submit button (on the top right hand side of the screen)

Now the setup part is complete and we would now try to run the newly created Payroll Flow Pattern and try to understand the behavior.

For the same navigate to the Payroll Checklist Workarea (Navigator -> Checklists) and click on ‘Submit a Process or Report’ as shown:

Select the appropriate payroll flow pattern (CustomFlowPattern-SubmitBIPReport) and proceed to next train stop (by pressing the ‘Next’ Button)

Give a name to the payroll flow (for example TestRun1)

Again choose the familiar next button to advance to the next train-stop.

Next we should move to the schedule tab and choose the ‘As soon as possible’ option to run the payroll flow:

Now, we are ready to have a quick review of the entire payroll flow before doing a submission of the same. Once we click on the submit button we should get a confirmation message along with an informational text guiding us about what to do next.

A click on the ‘Ok and View Checklist’ takes us to the following screen:

We now need to click on the ‘Go to Task’ to view the results

Summary Tab give us the following view:

Reports and processes tab displays a snapshot which when captured appears as:

Next Click on ‘View Results’

And the below screen will appear

Click on the ‘Default Document.pdf’ and the Output appears as shown:

Thus we have now seen how to create a very simple Custom Payroll Flow Pattern making use of a BIP Report. We may add multiple tasks before or after the same to create a complex flow pattern.

This brings me to the end of this article and I hope this was a nice thing to learn.

Do explore more on similar lines and unravel the mystery which is waiting to be discovered

Good Bye ..!!

Objective: In the previous article Creating ODI Repository, we saw how to create Master and Work Repository in ODI. In this article, we will show the step by step process of implementing table to table integration in ODI.

Topology Configuration

Creating table to table integration involves only creating a interface in ODI. But there are some perquisites before we get in there.

Step 1. Create a physical server and logical servers.Check if they already exist.

Physical Servers are the configuration which point to the physical connection security details for database (oracle, sql servers, sybase etc), File, JMS, XML, Complex files etc. We can create physical connection for each environment (Dev, Test, Production) . Logical server is what used to run the interface. Based on the environment currently the interface is run, logical server points to the respective physical server.

Step 2. Check model is already existing for the database tables we are going to use. Model is nothing but reverse engineering the database tables, view, AQs etc for use in ODI objects. Model is applicable for File, XML, Complex files and JMS also. Even for File,XML, Complex Files and JMS the model is created in a relational way (as table datastores) in ODI.

Once both the steps are complete, we can create the interface. In this example, I have three schemas in XE database.

1. Oracle seeded HR schema - Has all HR related tables for demo purposes.

2. ODI_STAGE schema - I have created a new schema. This i will use for holding the temporary objects created by ODI

3. DATA_TARGET - I have created a new schema. I will use this schema to create target tables.

I have employees table in hr and data_target. hr schema employees table has some data but data_target employees table is empty. Using the interface I create in ODI, i will load the data from hr.employees to data_target.employees table. Also create a primary key constraint on the  employee_id in target.

CREATE TABLE "EMPLOYEES"

  ("EMPLOYEE_ID" NUMBER(6,0),

"FIRST_NAME" VARCHAR2(20 BYTE),

"LAST_NAME" VARCHAR2(25 BYTE) NOT NULL ENABLE,

"EMAIL" VARCHAR2(25 BYTE) NOT NULL ENABLE,

"PHONE_NUMBER" VARCHAR2(20 BYTE),

"HIRE_DATE" DATE NOT NULL ENABLE,

"JOB_ID" VARCHAR2(10 BYTE) NOT NULL ENABLE,

"SALARY" NUMBER(8,2),

"COMMISSION_PCT" NUMBER(2,2),

"MANAGER_ID" NUMBER(6,0),

"DEPARTMENT_ID" NUMBER(4,0)

  );

Physical Server and Logical Server definition

1. After connecting to the work repository, go to topology tab.

2. Under physical architecture section, right click on Technologies->Oracle->New data server

3. Create a data server connection odi_stage schema. This is the schema which is entry point for ODI. we can use any schema here for data server but it should have access to all other schemas and objects which we are dealing with for creating models, insert, select, update data.

4. Here I am using ODI_STAGE schema as data server and HR and DATA_TARGET as physical schemas4.    In the definition tab, provide name and connection details for odi_stage schema.

In the jdbc section, select the jdbc driver and connection details for oracle database instance.

Test the connection by selecting test connection. select Local(No Agent) to simulate odi client as agent.Select ok, if you get pop up to create physical schema, select ok.

Right click on the data server we just created and select new physical schema.

Right click on the data server and select new physical schema. lets create a physical schema for HR and DATA_TARGET schemas. In the create physical schema window, select the main schema and the work schema (schema where odi creates work tables like loading, error, integration tables). we can also provide prefix convention for the error, integration, loading tables which ODI creates in the work schema ODI_STAGE. we can also configure the masks which are specific to the technology we use.

Work Tables:-

Error - This table by default created with E$ prefix and it stores the primary key of the record which errored out and its corresponding error.

Loading - This table is the exact copy of the source data before any joins are done. This by default has C$ prefix.

Integration - This table is used to check the integration constraints check for data errors

Lets create a physical schema for DATA_TARGET also with schemas as data_target and work schema as ODI_STAGE.

Lets create a logical schema for hr and data_target here which maps to physical schema based on environment In logical architecture section right click on Oracle and select create logical schema. Here we are mapping it to Global context. We can also create DEV, TEST and PRODUCTION context and point the respective physical schema for context (which is nothing but environment reference).

Objective :Solution for ERROR :: "io error got minus one from a read call" while connecting to Oracle Database

You may face a minus one from read call error while trying to connect to database through sql developer

The root cause of this error is sqlnet.ora is not allowing any connection to oracle database due to below entry in the sqlnet.ora file

tcp.validnode_checking = Yes

tcp.invited_nodes=(r12.apps2fusion.com)

You can follow these steps to avoid the error:

1. Go to directory $ORACLE_HOME/network/admin

2. Modify sqlnet.ora file with following parameter:

tcp.validnode_checking = no

3. If you don’t want to disable this, you can put the machine names as follows:

tcp.invited_nodes=(machine1, machine2) (  where machine1, machine2 will be the hostname of the machine )

4. Bounce the listener (lsnrctl stop , lsnrctl start)

Once you bounce the listener , and update the sqlnet.ora file you will be able to connect to the database without any error .

Introduction

The Title of the document sounds weird isn’t it. I admit it does but only until we are not aware what a Category is as per Page we all probably know we refer to a User Interface which has input box, Text items, buttons, informational text, logo, icons.., in a nutshell a placeholder which displays some information or expects user input to capture some or other information.

But let us try to focus now on what we mean by a category. Category in simple English means Classification for example if you have multiple electronic gadgets we classify them into Laptops, Desktops, iPads, Smartphones…….

Each of the links under the category is a Application Page which points to a specific page within the application.

Until Release 9 it used to take considerable amount of effort and time in order to add custom pages/web-link onto Fusion Application but starting Release 10 onwards things have become very simple and even newbies can add a new category and application page / static URL.

Let us try to understand the same with a sample example.

Worked Example

In this example we will try to create a Custom Category say ‘Search’ and add a Static URL let us call it Google Search which when clicked upon would take us to Google Search Engine Homepage.

Once we click on the hyperlink ‘Structure’ it takes us to the below page:

Once you click on the ‘Edit’ button you would be asked to activate a sandbox (popup message would appear)

Do check that a horizontal strip appears on the top confirming that you indeed are in a Sandbox Environment

Yep, the strip does appears. So far so Good. Let us proceed further.

A mouse click on the ‘Create Category’ link brings up a new page which looks as:

Enter the following Values:

Once the values are entered the screen would appear as below:

Next Click on ‘Save and Close’.

And this would bring us to the following page:

Next, we will populate the fields with the below values from the table:

And the UI screen post the values are populated would look as below:

Next Click on the ‘Save and Close’ Button (on the top right hand side) and we would see that the new Category ‘Search’ and Page ‘Google Search’ appears on the ‘Structure’ Page

Also note that the ‘Show on Welcome Springboard’ option is unchecked for the ‘Google Search’ Page which means that the icon would not be available on the Welcome Springboard.

Hover your cursor over the ‘Google Search’ icon and

It takes us to the Google Search page

Good!

But let us see how the Welcome Springboard looks like. We can navigate to the same via using the ‘Home’ icon on top of the page

As we can see from the above screen that there is no visual resemblance of the new page here and that’s because we chose the same to not be visible on the springboard.

Let us now change the settings and bring the icon here.

To incorporate this change we need to again navigate to Tools->Structure, select the ‘Google Search’ page and change the ‘Show on Welcome Springboard’ attribute value to ‘Yes’ from ‘No’.

And then click on ‘Save and Close’

Next we will navigate to the homepage and we should be able to see the new page ‘Google Search’ along with the icon.

An icon does appear as shown above. But let us verify (whether the same takes us to the expected screen)  this before we conclude this demonstration. And we would do so by a simple click on the icon

We could see that we were re-directed to the Google page as expected and with this we come to the conclusion of this article.

I believe this was useful and you all would be able to use the feature in your implementation projects.

Introduction

This article is intended to be used as a ready reference handbook for either Technical/Functional/Techno-Functional/Functional Test Engineer / Business User.

While in most cases an expert Fusion Application Functional / Techno Functional Consultant is expected to be aware of how to initiate a self-service transaction in Oracle Fusion Application a newbie can face issues because implementers usually login with an Admin user profile and hence it should not be a surprise if they are unaware of initiating self-service transactions.

Also this article could be of use to Functional Tester / Business End Users who would be using Fusion Applications for the first time and would like to get started with the work in case there isn’t a formal handover or training planned.

So without much delay let’s get started.

Self-Service Transactions

As the name suggests these are some transactions which are carried out in the system by the individual. Typical examples could be Change in Location, Request for Transfer, Change Manager, Termination and many more. A complete list in tabular format below

Sample Example – Initiate Termination

While some of the above transactions are auto approved ones like Manage Person where you would be able to change personal details like Phone Number, personal email id  ..etc

Some of the transactions do go through an approval process.

In this example we would try to initiate a termination action.

Login to application with proper login credentials as shown:

Click on the ‘Sign In” button and this will take you to the HomePage:

Next click on the Navigator Icon on the top left hand side beside the Company Logo and this will bring a Pop-Up List.

This is the place where from one would be able to execute most self-service transactions

The Actions Tab on the left hand side area of the page (as shown in snapshot below) when expanded lists all available actions.

Note: Use the ‘All Actions’ hyperlink text to view all the actions.

Choose the terminate action for initiating a transaction

Once you click there you will either be navigated to the termination screen or shown a message in case there are dependencies (as in this example)

In your case if there are no dependencies you should be able to proceed with the termination.

This was just a sample example and you may try out the other available options and explore more.

Objective:In the previous article we saw Table to table integration in ODI, in this article we will learn how to create Project and Interface.

Creating Project and Interface

Let's create a project in which we have the table to table interface.

In the designer tab, Projects section, create a new project and provide a name. Project code is an important identifier which is used to identify project specific objects as compared to global objects.

Expand the project which is created, right click on knowledge modules and select import knowledge modules(IKM). we need to select three knowledge modules here for loading, integration and check constraint. Select CKM Oracle,LKM SQL to SQL and IKM SQL Incremental update. We need to select knowledge modules specific to the technology and kind of data loading we are doing. KM automates the process with predefined code for loading, integration, check constraints, reverse engineering and journalizing (change data capture).

1. LKM SQL to SQL - Automates the loading of data from source to staging. reads data from hr.employees and put it into odi_staging.c$_employees.

2. IKM SQL Incremental Update - Takes the data from staging and merges (insert or update) data to target.

3. CKM Oracle - Check for specific constraints we need to check after loading in target.

After selection, we can verify the imported KMs in knowledge modules section.

Let’s create an interface now. Under project folder right click on interfaces and select new interface.

Provide name for interface and select the schema to which we need to load.

Click on the mapping tab in interface. Drag the employees table from hr model to source area and drag employees table from data_target model to target area. drag the field from source to target to complete the mapping. select the employee id in target mapping and verify that key attribute check box is checked. if not we cannot enable flow control in IKM and so make sure that it is checked.

Go to overview tab, select staging is different from target so that staging tables are created in odi_staging schema.

Go to flow tab. Select staging in the diagram and select LKM SQL to SQL from the drop down. This LKM has only one option which is delete temporary objects. make this true so that C$ temporary table is deleted once target loading is complete.

Select target in the flow tab and select the IKM from the drop down. IKM provides few options which we configure based on our needs.

FLOW_CONTROL - checks the constraints while loading into the target. error records are placed into E$ table.

TRUNCATE - truncates the target table before loading into it.

DELETE ALL - delete the rows instead of truncate

STATIC_CONTROL - checks the constraints after loading into target table.  But target table will still have the error records

RECYCLE_ERRORS - considers the rows from E$ table along with C$ table for integration loading into target so that if any records corrected, they will be recycled and loaded to target.

COMMIT - we can make this false if needed and we can do a separate commit when this interface is part of a package so that we can maintain transaction for the objects used in ODI package.

CREATE_TARG_TABLE - creates target table if it doesn't exist at run time.

DELETE_TEMP_OBJECTS - deletes temporary I$ tables after target loading.

Select the controls tab and select the control knowledge modules. select the constraints to be enabled.

we have few options here to modify if any. we can ask ODI to drop the error table or check table here.

Save the interface.

With this we have completed creation of the interface. Lets run it now. Right click on the interface and click execute. Select global context, No agent and required log level. select ok. select ok on the session started dialog.

Go to operator tab to verify the run. expand all executions. Verify that our execution is successful. We can also expand the interface results and drill down to the steps executed at LKM, IKM and CKM levels and see the SQL generated and results here.

Let’s verify the temporary tables created now. Go to the ODI_STAGING schema and verify the  E$, check tables. If we make delete temporary objects to false in LKM and IKM options, we will see C$ and I$ tables also here.

Lets check the target table for data.

With this we have completed the table to table loading using ODI interface.

Oracle Value Chain Planning:
In Demantra Promotion Trade Planning training you will learn about Oracle Demantra Promotion Trade planning (PTP). Our expert instructors will help you develop a thorough understanding of PTP business scenarios and flows, while exploring key aspects and tips for implementation. By the end of this course you will learn to implement a Demantra Promotion Trade planning project. You will get an opportunity to explore the various capabilities of the Demantra PTP product while also learning to utilize them efficiently when implementing a Demantra PTP Solution.

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at an overview of Fusion applications and some commonly used Fusion terminologies.

Overview of Fusion Applications

The Fusion application, since its launch in October 2011, has been divided into seven pillars- Financials, Human Capital Management, Procurement, Projects, Customer Relationship Management, Supply Chain Management, and Governance Risk and Compliance.

Each of these pillars have several of their own modules, which are used to perform functions relevant to them. The following diagram depicts the seven pillars of Fusion, along with the modules they contain.

Fig. 1 - The Seven Pillars of Fusion

When we look at the Financials pillar in particular, it has got a number of modules associated with it, for performing all the respective functions related to financials. The following diagram depicts the modules contained in Oracle Fusion Financials.

Fig. 2 - Oracle Fusion Financials Offerings

As can be seen from the illustration above, Oracle Fusion Financials consists of the following modules:

• General Ledger

• Accounts Payable

• Fixed Assets

• Accounts Receivable

• Revenue Management

• Advanced Collection

• Cash Management

• Financial Reporting

• Expense Management

• Fusion Tax, and

• Sub-ledger Accounting

The Revenue Management module, in particular, is not usually made available by Oracle to all of its customers. This is because it is an up-and-coming department, especially in the United States, where the government has issued regulations to be followed by companies. They have to implement revenue management policies and put them into effect by the start of 2018. Oracle has been working on this and will be implementing these features in the future.

Key Features of Oracle Fusion Financials

The key features offered by Oracle Fusion Financials are:

• Innovative embedded multi-dimensional reporting platform

• Role-based dashboards that push issues and work to users

• Embedded transactional intelligence that guides users’ decisions

• Imaging integration for supplier invoices

• Extensive spreadsheet integration across finance functions

• Simultaneous accounting of multiple reporting requirements

• Self Service Reporting

Benefits of Oracle Fusion Financials

Oracle Fusion Financials provides a number of benefits to its users. With the help of Oracle Fusion Financials, the user would be able to:

• Gain real-time access to live financial data

• Comply with global accounting standards and multiple legislative, industry, or geographic requirements

• Proactively resolve issues to expedite automated processing

• Improve decision making and increase accuracy during transaction entry

• Reduce transaction processing costs and data entry errors

• Utilise a cooperative system to work on, since the hardware, software, and processes are engineered to work together efficiently.

Fusion Terminologies

Some of the common terminologies used when talking about Oracle Fusion have been explained below:

• Functional Setup Manager (FSM)
  It is a tool used to configure applications across a project in Fusion.

• Oracle Identity Manager (OIM)
  The OIM is a tool used for user authentication, which includes validating user credentials, creating new users, managing users, deleting users, etc.

• Authorization Policy Manager (APM)
  The APM is another user-related tool used for user authorization, which deals with granting users access to particular areas.

• Weblogic Server
  The weblogic server is the server on which the business logic, pages, and codes are hosted.

• Business Unit
  A business unit is an entity that performs relevant business functions.

• Business Functions
  They are business-related functions that include payables invoicing, payment, requisitioning, customer payment processing, billing, etc. They are enabled through business units.

• Reference Set
  A reference set consists of a set of configuration settings that can be used across business units, like payment terms, payment type, etc.

• Date Effective Hierarchies
  This is a feature of Oracle Fusion, where hierarchies can be given an ‘End Date,’ after which a new version of the hierarchy will be used. Reports can also be generated from earlier versions of the hierarchies.

• COA Structure and Instances
  Chart of Accounts (COA) are divided into two levels: structures and instances.
  The COA structure describes the number of segments, sequence of the segments, segment labels, etc., along with a default value set for each of those segments.
  COA instances use the COA structures to define the required segments, which can have modified value sets according to the instance.

• Role Based Access Control (RBAC)
  This is a feature of Oracle Fusion, which means that the access of users to certain pages and functions is dependent on the role(s) associated with the particular user that have been defined in the OIM or APM.

• Essbase Cube
  It is a multidimensional database that stores data in a pre-aggregate format. This allows the data to be used in reports instantaneously, instead of waiting for a batch process to be submitted and run.

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at Financial Enterprise Structures and the security feature of Oracle Fusion.

Financial Enterprise Structures

One of the most critical decisions for any project is the financial structure. In Oracle Fusion, the financial enterprise structure exists as depicted in the below illustration:

Fig. 1 - The financial enterprise structure with legal entities and primary ledgers

Here, the Enterprise is on top, and there can be only one enterprise for a project in Fusion.

Under the enterprise, there exist the Legal Entities. These legal entities will be associated with Primary Ledgers. Note that there can be multiple legal entities for a single primary ledger. In such a case, each legal entity has to be associated with a balancing segment. In case of a one-to-one relationship, the balancing segment is optional.

Fig. 2 - A financial enterprise structure with business units

Under the primary ledger, there will be Business Units. A business unit is an entity that performs certain business functions. Each business unit will have Inventory Organisations associated with it.

Fig. 3 - The structure of a primary ledger

As seen in the above chart, each primary ledger has a Chart of Accounts, currency, calendar, and accounting method associated with it. In case of any difference in those components, either a reporting currency or a secondary ledger is created.

When creating a secondary ledger with a different currency, it cannot be done directly. First, the secondary ledger is created with the same currency as the primary ledger. Then, a reporting currency is created for the secondary ledger.

Business Functions

Business functions are those that are performed by a business unit. Oracle Fusion Financials has a number of financial-related business functions available to be performed by the users, according to their roles and duties. The various business functions related to financials that can be performed are:

• Payables Invoicing

• Billing and Revenue Management

• Customer Payments

• Service Request Management

• Order Fulfillment Orchestration

• Collections Management

• Materials Management

• Customer Contracts Management

• Project Accounting

• Procurement

• Requisitioning

• Receiving

• Expense Management

• Order Capture

• Sales

• Marketing

• Procurement Contracts Management

• Incentive Compensation

Fusion Security - Roles in Fusion Applications

There are different roles available in Fusion applications. As specific roles will be able to perform only those functions for which they have access to, this type of system enhances its security and prevents mistakes or any unauthorised access. There are different types of roles applicable to users in Fusion:

• Duty Role (Application Roles)
  Any employee of an organisation performs certain tasks (e.g. invoice creation, approval, enquiry, etc.). These tasks are related to the employee’s duties that are a part of his/her work. Duty Roles have certain privileges and access to these duty-related tasks.

• Job Role (External Roles)
  Job Roles are collections of duty roles, or duties. For example, the person who performs the tasks of invoice creation, invoice approval, invoice enquiry, etc. is called the Payables Clerk, which is the employee’s designation.

• Abstract Role
  Abstract Roles are roles that are not related to business activities. They can include leave application, viewing salary, etc. which basically are self service activities for the employees.

• Data Role
  Data Roles are created for job roles. These data roles are the ones which provide access to the actual data associated with the job roles. If the appropriate data role is not assigned to a user, he/she can only view the page for the job role, but not the data in that page.

• Data Access Set
  The Data Access Set is used to control the access of users to a ledger or a specific balancing segment. A data access set will be created automatically upon the completion of the ledger configuration along with data roles. Further data access sets can be created to restrict access to a particular balancing segment value or ledger set level.

Role Based Security

The following illustration depicts how the role based security in Oracle Fusion works in Fusion Financials:

Fig. 4 - Role based security in Oracle Fusion Financials

Here, the user ‘Fred’ has the following roles associated to him: Accounts Payable Manager - US-West (here, US-West is a business unit), Employee, and Line Manager. Each of these roles has got certain functional privileges and data access granted to it, as depicted above.

The role Accounts Payable Manager - US-West grants Fred the following functional privileges: Manage Payables Invoices, Apply or Unapply Payables, and Prepayments. These privileges grant Fred access to the following data: Payables Invoices in US-West Business Unit. Similarly, the Employee and Line Manager roles follow suit with their functional privileges and data access.

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at the interface of the Fusion applications.

Fusion Apps User Interface

Logging in to the Application

Follow the steps below to log in to Fusion Applications:

1. Go to the URL fa119.apps2fusion.net:10634/homePage.

2. You will be directed to the Oracle Fusion Applications log in page. You can use the dropdown list at the bottom to select the preferred language.

3. Enter your user credentials in the input area for your User ID and Password.

4. Click on the Sign In button (circled in the screenshot below).

5. In case you have forgotten your password, use the Forgot Password link. After answering security questions, your password will be reset.

Fig. 1 - The Fusion Applications login page

Fig. 2 - The login input area for entering the credentials

Fig. 3 - The home page of Fusion Applications after logging in

After logging in to Fusion Applications, the home page will appear, the screenshot of which has been shown above. The different elements present on the home page are discussed below.

The Global Area

The top portion of the page is called the Global Area (circled in the screenshot below). This Global Area will be visible on all pages within the application, irrespective of the function.

Fig. 4 - The Global Area of the Fusion Applications

Home

The first icon is the Home icon, which brings you to the home page of the application.

Navigator

The second icon from the left, the Navigator icon (circled in the screenshot below), brings up the Navigator menu. The Navigator menu provides a list of all the tasks available for the user to perform, depending on his/her role defined in the system.

Fig. 5 - The Navigator icon and menu

Favourites and Recent Items

The Favourites icon (circled in the screenshot below) will show favourites and recent items for the user. To add pages to your favourites, click on the Add to Favorites… link. Recent items are added based on the page history of the user.

Fig. 6 - The ‘Favourites’ icon

Watchlist

The Watchlist icon (circled in the screenshot below) brings up the Watchlist menu, which has a list of items that require the user’s attention, depending on his/her role. A dashboard version of the watchlist is also viewable on the home page of the application, as discussed subsequently.

Fig. 7 - The Watchlist menu

Recent Notifications

The bell icon (circled in the screenshot below) brings up the notifications and approvals for the user that are related to his/her tasks. A dashboard version of this is viewable on the home page of the application, as discussed subsequently.

Fig. 8 - The ‘Notifications’ icon

Accessibility

The Accessibility icon (circled in the screenshot below) can be used to modify the look and feel of the interface - fonts, colours, etc.

Fig. 9 - The ‘Accessibility’ icon

Help

The Help icon is a very useful tool for getting information about the items on a page. When you click on the Help icon, it turns orange (as shown in the screenshot below), and smaller orange icons appear next to the items on the page (circled in the screenshot below). Click on one of these will bring up a help menu on the right of the screen with context-sensitive help articles about the items.

Fig. 10 - The ‘Help’ icon turns orange after clicking it

Fig. 11 - The context-sensitive help menu pops up

Settings and Actions

When you click on your username on the right of the Global Area, a menu of Settings and Actions for the user will drop down. The items on the menu are used for configuring settings for the user.

Fig. 12 - The ‘Settings and Actions’ menu for the user

For example, the Set Preferences… option is used to configure preference settings for the user, like regional preferences, language preferences, accessibility preferences, password, etc.

Fig. 13 - The ‘Preferences’ settings for the user

Fig. 14 - Changing the password settings for the user

Fig. 15 - Regional preferences for the user

The Watchlist preferences can be used to enable or disable any item that shows up on the Watchlist.

Fig. 16 - Enabling and disabling items in the Watchlist

Dashboards

Dashboards are sections that appear on pages in the applications. The dashboards present on the home page are discussed below.

Watchlist

The Watchlist dashboard (circled in the screenshot below) shows a list of exception items that require your attention. This depends on the role of the user that has signed in to the application. In this case, the role of the user is FAAdmin. The numbers in the bracket denote the number of such instances of the respective item.

Fig. 17- The Watchlist dashboard

Worklist: Notifications and Approvals

The Worklist: Notifications and Approvals dashboard (circled in the screenshot below) present to the right of the Watchlist displays any notifications or approvals related to tasks that need to be brought to the attention of the user. The user can then perform relevant activities on those notifications when they appear.

Fig. 18 - The ‘Worklist: Notifications and Approvals’ dashboard

Activity Stream

The Activity Stream dashboard (circled in the screenshot below) present below the Worklist is something of an “internal social media”. Here, the user can share, discuss, and converse with his/her colleagues and clients. It is also called the Oracle Social Network (OSN). The conversation history is saved and stored along with the project.

Fig. 19 - The ‘Activity Stream’ dashboard

(continued in Part 2)

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at the interface of the Fusion applications.

Fusion Apps User Interface

(continued from Part 1)

The Navigator Menu

The Navigator menu has got several sub-divided sections. These sections depend upon the role of the user who has logged in to the application.

Fig, 1 - The Navigator menu

The items in the navigator menu are shown in the screenshot above. Since the user that has logged in is the FAAdmin, the tasks displayed on his navigator menu are related to his duties: Revenue Management, Collections, Contract Management, Receivables, Procurement, Payables, Cash Management, Fixed Assets, etc. There are many other tasks available as well, which is not visible in the screenshot, like General Accounting, Payroll, Expenses, etc.

As an example, let us look into the Tools section of the Navigator menu below.

Tools

The Tools present on the Navigator menu are:

• Reports and Analytics - For generating analytical reports on data

• Scheduled Processes - For scheduling certain processes to be run by the application

• Setup and Maintenance - For configuration of settings related to the role of the user

• Customisation - For personalising settings for the user

• File Import and Export - For integration and data migration

• Audit Reports - For generating reports related to auditing

• Download Desktop Integration - For integration of data with spreadsheets

Fig. 2 - The ‘Tools’ section on the Navigator menu

As an example, the Scheduled Processes page is shown below:

On the Navigator menu, go to Tools -> Scheduled Processes to view a list of the scheduled processes in the application. Here, you can schedule a new process as well as resubmit, put on hold, cancel, or release processes.

Fig. 3 - The Scheduled Processes page

Let us look into the Journals task under General Accounting as an example of viewing and performing tasks related to the role of the user.

The Journals Page

The Journals page can be visited from the Navigator menu as follows:

1. On the Navigator menu, go to General Accounting -> Journals (circled in the screenshot below).

2. Select the Data Access Set from the dropdown list of ledgers available, then click on the OK button.

3. The Journals page will open. Here, the list on the left (circled in the screenshot below) has links to several tasks that are related to journals.

4. The Overview panel on the right shows the exception items that require the user’s attention and approval.

5. Scroll down from the Overview to view the Process Monitor, which shows all the scheduled processes that are related to journals without the need of going to the Scheduled Processes tool. However, new processes cannot be scheduled from the Process Monitor.

Fig. 4 - The ‘Journals’ link on the Navigator menu

Fig. 5 - Selecting the Data Access Set

Fig. 6 - The ‘Journals’ page. The task list on the left is circled

Fig. 7 - The ‘Process Monitor’

Creating a Journal

To create a journal, follow the steps below:

1. From the Journals page, go to Journals -> Create Journal from the task list on the left.

2. Enter the details of the journal in the fields that appear on the main panel. Then click on the Save button, followed by either Save and Close or Save and Add Another, depending on your requirement.

Fig. 8 - The ‘Create Journal’ task

Fig. 9 - Creating a journal

Managing Journals

To search for and manage journals that are already existing in the application, follow the steps below:

1. From the Journals page, go to Journals -> Manage Journals from the task list on the left.

2. You can use the buttons available (circled in the screenshot below) to accordingly search for journals. Fields marked with double asterisks (**) mean that at least one of those fields have to be entered for searching. After entering the search field(s), click on the Search button.

3. The search results will be displayed below the fields.

4. Click on the View button from the search results to add or remove columns to be displayed, sort the results, query by example, etc.

5. To query the search results by example, use the blank fields that appear on top of the column names.

Fig. 10 - The ‘Manage Journals’ task

Fig. 11 - The ‘Manage Journals’ page

Fig. 12 - Viewing the search results

Fig. 13 - The ‘View’ menu of the search results

Fig. 14 - Querying search results by example

In this course, you will learn the basics of the Oracle Financial Applications, which includes General Ledger, Purchasing, Payables, Fixed Assets, Order Management, Accounts Receivables, Cash Management, and Projects. Learn the core concepts that are integral to these applications, such as Suppliers, Customers, and Items. Additionally, learn how they work together in different flows to suit your business needs. Business flows include Procure to Pay and Order to Cash Flow. You will also be able to try many of these products during the course of your study using a series of hands on practices, which build on one another, thus allowing you to experience both the tools and the workflow of which they are a part.

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at an overview of the Functional Setup Manager (FSM) in Oracle Fusion.

The Functional Setup Manager (FSM)

The Functional Setup Manager (FSM) in Oracle Fusion is a centralised place where configurations are done for the user. It is also called as the Setup and Maintenance work area.

The Oracle Fusion Functional Setup Manager enables rapid and efficient planning, implementation, and deployment of Oracle Fusion Applications through self service administration.

By using the Functional Setup Manager, the organisation can:

• Learn and analyse implementation requirements of Oracle Fusion Applications.

• Configure Oracle Fusion Applications to match the organisation’s business needs.

• Get complete visibility to setup requirements through guided and sequential task lists.

• Enter setup data through user interfaces available directly from the task lists.

• Export and import to rapid start functional setup at different instances.

• Validate setup by reviewing setup data reports.

The Functional Setup Manager is used to implement all Oracle Fusion Applications through a standard and consistent process.

In addition, the Functional Setup Manager allows application developers to manage application design objects, which are the core components of Oracle Fusion Applications, and to add and modify the functionality of the Oracle Fusion Applications.

Navigating to the Functional Setup Manager

There are two ways to navigate to the Functional Setup Manager:

• Through the Navigator menu

  1. Click on the Navigator icon in the Global Area on the top of the application (circled in the screenshot below).

  2. Go to Tools -> Setup and Maintenance

Fig, 1 - The Navigator icon in the Global Area is circled

Fig. 2 - The ‘Setup and Maintenance’ link on the Navigator menu

• Through the Settings and Actions menu

  1. Click on the name of the user with which you have logged in to the application.

  2. On the Settings and Actions menu, go to Administration -> Setup and Maintenance.

Fig. 3 - The name of the user logged in

Fig. 4 - The ‘Setup and Maintenance’ link on the Settings and Actions menu

An important point to note about the Functional Setup Manager is that it is role driven. This means that it can only be accessed by the users who have administrative privileges. Not every user can configure the application using the Setup and Maintenance work area.

Specifically, a user with either of the two roles, Application Implementation Consultant or Application Implementation Manager, can configure the application by using the Functional Setup Manager.

The Setup and Maintenance Work Area

When you navigate to the Setup and Maintenance work area by either of the two methods shown above, you will be taken to the Setup and Maintenance home page.

Fig. 5 - The home page of the Setup and Maintenance work area

If you click on the Getting Started link under Implementations from the task list on the left, a sequence of the implementation process will be shown: Plan, Configure, Implement, Export and Import, Transact, and Maintain. You can click on the links below each step of the process to perform the respective tasks.

Fig. 6 - Getting started with Oracle Fusion Applications - Setup and Maintenance

1. Plan
   Here, you plan all of the details of the application.

2. Configure
   The details of the application are configured. The task is Configure Offerings, where you configure the settings of the features of the application.

3. Implement
   The various projects of the application, called “implementation projects,” are managed using the Manage Implementation Projects task.

4. Export and Import
   Here, the configuration settings can be imported and exported between different instances, as long as they are of the same version or patch level. The task is Manage configuration Packages.

5. Transact
   The actual transaction takes place. The “transactions” is nothing but the actual operation of the application to be run.

6. Maintain
   Maintenance such as reports, error checking, etc. can be done by using the Perform Maintenance Tasks task.

Offerings

The first step is to choose the offerings to be implemented. When you scroll down from the implementation process, you will be able to see a variety of “offerings” available that can be implemented in the application. Click on each of the offering’s name to view the contents and documents related to that offering.

Fig. 7 - Various offerings available to be implemented

Fig. 8 - The contents of the ‘Financials’ offering

Configure Offerings

In order to configure the settings of the offerings that are required, go to the Configure Offerings task under Implementations from the task list on the left.

Fig. 9 - The ‘Configure Offerings’ task

You will see that the offerings that have been installed will have their Provisioned field set to Yes. This means that the offering has been provisioned for the user.

In order to use the offerings and the tasks associated with it, the checkbox under the Enable for Implementation field has to be checked. Note that checking the parent (Financials) checkbox alone is not enough. You will have to expand the offering name to view the subdivisions, and then check each box individually in order to have that component enabled for implementation.

Fig. 10 - The ‘Financials’ offering on the Configure Offerings page

There are three levels to the offerings and their modules. They are the offering itself, its options, and the features.

To select the choice of features available in the offering, click on the pencil icon (circled in the screenshot below) under the Select Feature Choices column.

Fig. 11 - The three levels of the offerings

After selecting the checkboxes of the required features, click on the Save and Close button.

Fig. 12 - Selecting the feature choices

(The next tutorial deals with the next step of Setup and Maintenance, which is Managing Implementation Projects)

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at the creation and management of implementation projects in Oracle Fusion.

Manage Implementation Projects

The next step to be undertaken after selecting the offerings in Setup and Maintenance is to manage the projects in which the offerings are being implemented, i.e. the implementation projects.

What Is an Implementation Project?

An implementation project is the list of setup tasks that need to be completed to implement selected offerings and options. First, a project is created by selecting the offerings and options that the organisation wants to implement together. The project is then managed as a single unit throughout the implementation lifecycle. These tasks will be assigned to users and their completion will be tracked using the project management tools.

Therefore, an implementation is nothing but a list of tasks to be performed together that are grouped as a unit. For example, an organisation may choose to create a single implementation project for Human Capital Management, Financials, and Supply Chain Management. Or it may choose to create three separate implementation projects for the three offerings.

Furthermore, there may be multiple implementation projects inside the financials department itself. All of these implementations are at instance level.

Creating an Implementation Project

To create an implementation project in the Fusion application, follow the steps below:

1. Go to the Manage Implementation Projects task under Implementations from the task list on the left.

2. Click on the Create icon (circled in the screenshot below) to create a new implementation project.

3. Enter the basic information of the implementation project: Name, Code, and Start Date. Click on the Next button.

4. Select the offerings to be included in the implementation project by checking the checkbox under the Include column. Once you select a main offering, its list will be expanded, and you have to select its options and features individually. Once you are done selecting, click on the Save and Open Project button.

5. The created implementation project will then be opened and shown on the screen.

Fig. 1 - The ‘Manage Implementation Projects’ task

Fig. 2 - The ‘Manage Implementation Projects’ page. The Create icon is circled

Fig. 3 - Entering the basic information of the implementation project

Fig. 4 - Selecting the offerings to be included in the implementation project

Once you are done creating an implementation project, you can continue configuring the tasks under the project. To view the individual tasks in the implementation project, click on its name from the main list of search results on the Manage Implementation Projects page.

Fig. 5 - The created implementation project shows up in the main list

Click on the arrow next to the name of the offering to view all of the task lists and tasks that come under it. An asterisk (*) next to a task list name denotes that there is at least one task under it that needs to be configured mandatorily. Most of the tasks are ordered according to the generally accepted sequence to be followed when configuring them.

Fig. 6 - Expanding the task list to view the individual tasks

Tasks in an Implementation Project

In order to configure and run tasks after creating an implementation project, first go to the required implementation project by clicking on its name from the Manage Implementation Projects page.

Fig. 7 - The required implementation project

The ‘Run User and Roles Synchronization Process’ Task

Oracle Identity Management (OIM) maintains Lightweight Directory Access Protocol (LDAP) user accounts for users of Oracle Fusion applications. OIM also stores the definitions of abstract, job, and data roles, and holds information about roles provisioned to users. During implementation, any existing information about users, roles, and roles provisioned to users must be copied from the LDAP directory to the Oracle Fusion Applications tables. Once the Oracle Fusion Applications tables are initialised with this information, it is maintained automatically. To perform the initiation, this process should be executed.

To run this task, click on the Go to Task icon (circled in the screenshot below) next to the task name in the task list.

Fig. 8 - The ‘Run User and Roles Synchronisation Process’ task

Click on the Submit button on the page that follows.

Fig. 9 - Submitting the ‘Run User and Roles Synchronisation Process’ task

Fig. 10 - Confirmation of the task being submitted

To check the status of this process, go to the Scheduled Processes page under Tools in the Navigator menu.

Fig. 11 - The ‘Scheduled Processes’ link in the Navigator menu

Click on the Refresh button (circled in the screenshot below). The status of the process will change from Running to Completed, and finally to Succeeded upon successful completion of the process.

Fig. 12 - The status of the process tells that it is successful

(The next tutorial will discuss about the creation of Implementation Users)

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at the creation of implementation users in Oracle Fusion.

Creating Implementation Users

Implementation users are the ones who view, access, and manage the implementation projects in the Fusion application. To create implementation users, follow the steps detailed below:

1. Go to the required implementation project by clicking on its name from the Manage Implementation Projects page.

2. Expand the task list and click on the Go To Task icon (circled in the screenshot below) corresponding to the Create Implementation Users task under Define Implementation Users.

3. The Oracle Identity Manager - Self Service window opens up. Click on the Administration link on the top right of the page (circled in the screenshot below). Note that in order to access this, the IT Security Manager role has to be assigned to the user.

4. The Oracle Identity Manager - Delegated Administration window opens up. Click on the Create User under the Users section to create a new implementation user.

5. Enter the details of the implementation user: First Name, Last Name, User Type, User Login, Password, etc.

6. Click on the magnifying glass icon (circled in the screenshot below) next to the Organisation field to search and select the organisation of the user.

7. Use the Search field to search for the name of the organisation. From the search results, select the required organisation’s name and click on the Add button.

8. Once all the required details of the user are entered, click on the Save button on the top right of the area.

Fig. 1 - The required implementation project

Fig. 2 - The ‘Create Implementation Users’ task

Fig. 3 - The ‘Oracle Identity Manager - Self Service’ window

Fig. 4 - The ‘Oracle Identity Manager - Delegated Administration’ window

Fig. 5 - Entering the details of the implementation user to be created

Fig. 6 - Searching and selection the organisation

Assigning Roles to the User

After creating a user, roles have to be assigned to him/her. To do so, follow the steps detailed below:

1. Once the user has been created, a confirmation message will appear, along with tabs named Attributes, Roles, Resources, Proxies, Direct Reports, and Requests. Click on the Roles tab (circled in the screenshot below).

2. By default, the ALL USERS role will be assigned to the user. Click on the Assign button (circled in the screenshot below) to assign further role(s) to the user.

3. As of now, the user will only be a consultant. Hence, they cannot access basic tools like Scheduled Processes, Setup and Maintenance, Reports and Analytics, etc. Therefore, the first role to be assigned must be the Employee role.
   
   Search for the Employee role using the search fields and buttons available. From the search results, select the name of the role and click on the Add button.

4. The next roles to be added are Application Implementation Administrator, Application Implementation Consultant, and Application Implementation Manager. Use the Assign button again to search and select the required roles. You can use the “%” symbol as a wildcard while searching.
   
   To select more than one role to be assigned at once, hold the Ctrl key on your keyboard while selecting the roles. Click on the Add button after selecting the roles.

5. Click on the Assign button again and search for “General Accountant%”. You will get a list of roles as results.
   The General Accountant role is simply a job role; this means that the user with this role can only view the ledger pages but not any data.
   In order to enable the user to view the data of the ledger, he/she has to be assigned the appropriate data role corresponding to that ledger. These data roles are created automatically upon creation of the ledgers themselves. Select the required ledger data role and click on the Add button.

6. Once you are done assigning roles to the user, you can go back to the Fusion application.

Fig. 7 - After the successful creation of the user

Fig. 8 - Assigning roles to the user

Fig. 9 - Searching for the ‘Employee’ role

Fig. 10 - Adding three roles at once

Searching for Users

In order to search for users in the system, follow the steps below:

1. Go to the Oracle Identity Manager - Delegated Administration window as detailed in the above steps.

2. Click on the Advanced Search - Users link under the Users section (circled in the screenshot below).

3. Search for the required user using the fields available: User Login, First Name, Last Name, Email, Organisation, etc. Then click on the Search button.

4. A list of users matching your search fields will be displayed in the search results below the fields. Click on the Display Name of the required user to view their user information.

Fig. 11 - The ‘Advanced Search - Users’ link

Fig. 12 - Searching for a user

(The next tutorial explains how to configure the enterprise structure of a project.)

This tutorial deals with Oracle Fusion Financials, and how it functions. In this tutorial,we look at the definition of the enterprise structure in Oracle Fusion.

Defining the Enterprise Structure

One of the most critical decisions for any project is the enterprise structure. As discussed before, the Enterprise is on top of the structure. There can be only one enterprise for a project in Fusion.

The next step after the creation of an implementation project and implementation users is to configure the enterprise structure of the project. The following steps detail the method of configuring the enterprise structure:

1. Go to the required implementation project by clicking on its name from the Manage Implementation Projects page.

2. Expand the task list and click on the Go To Task icon (circled in the screenshot below) corresponding to the Manage Enterprise HCM Information task under Define Enterprise for Financials.

3. The details of the enterprise will be shown. By default, the name of the enterprise will be “Setup Enterprise.” To change the name or any other detail of the enterprise, click on the Edit button, followed by the Update or Correct option (circled in the screenshot below). The fields will then become editable. After making any necessary changes, click on the Submit button.
   The difference between the two options is the maintenance of history. If you choose the Update option, the detail(s) will be updated in the database along with a version history. The Correct option simple changes the detail(s) in the same version of the entry, without a historical record of the previous data, rather than updating it.

4. Click on the Done button after making any changes required.

Fig. 1 - The required implementation project

Fig. 2 - The ‘Manage Enterprise HCM Information’ task

Fig. 3 - The details of the enterprise

Fig. 4 - The ‘Update’ and ‘Correct’ options to change the details of the enterprise

Fig. 5 - After clicking on ‘Update’ or ‘Correct,’ all of the fields will become editable

Managing Locations

To create a location for the enterprise, follow the steps detailed below:

1. Expand the task list of the implementation project and click on the Go To Task icon (circled in the screenshot below) corresponding to the Manage Location task under Define Enterprise for Financials.

2. The Manage Locations page will open. To create a location, click on the Create button, followed by the Create option (circled in the screenshot below). In case a large number of locations need to be created, the Create in Spreadsheet option may be used.

3. Enter the basic details and other location information. Make sure that all of the mandatory fields, marked by an asterisk (*), are filled.

4. After entering the required details, click on the Submit button.

5. A pop-up message will appear asking you to confirm the submission of the details. Click on the Yes button.

6. A confirmation message will pop up. Click on the OK button.

Fig. 6 - The ‘Manage Locations’ task

Fig. 7 - Creating a location for the enterprise

Fig. 8 - Entering the basic details and location information

Fig. 9 - Entering the contact details and shipping details of the location

Fig. 10 - The submission prompt

Fig. 11 - The confirmation message

Managing Legal Jurisdictions

A jurisdiction is a physical territory, such as a group of countries, country, state, county, or parish, where a particular piece of legislation applies. French Labour Law, Singapore Transactions Tax Law, and U.S. Income Tax Laws are some examples of particular legislations that apply to legal entities operating in different countries’ jurisdictions. Judicial authority may be exercised within a jurisdiction.

The following steps detail how to manage legal jurisdictions in an implementation project in Oracle Fusion:

1. Go to the required implementation project by clicking on its name from the Manage Implementation Projects page.

2. Expand the task list and click on the Go To Task icon (circled in the screenshot below) corresponding to the Manage Legal Jurisdictions task under Define Legal Jurisdictions and Authorities  for Financials.

3. In order to search for the territory, click on the arrow of the Territory field dropdown and click on the Search… option (shown in the screenshot below).

4. Search for the name of the territory (you can use the ‘%’ symbol as a wildcard character). Select the territory from the search results and click on the OK button (circled in the screenshot below).

5. Click on the Search button.

6. From the search results, click on the name of the required jurisdiction (circled in the screenshot below).

7. The details of the legal jurisdiction will be displayed. After making any edits if necessary, click on the Save and Close button, otherwise the Cancel button.

Fig. 12 - The ‘Manage Legal Jurisdictions’ task

Fig. 13 - Searching for a territory

Fig. 14 - Searching and selecting the territory

Fig. 15 - The search results of the jurisdiction search

Fig. 16 - Viewing and editing the details of the legal jurisdiction

Managing Legal Addresses

The next step in configuring the enterprise structure of the project is to manage the legal addresses of the enterprise. The following steps detail the method of managing the legal addresses:

1. Expand the task list and click on the Go To Task icon (circled in the screenshot below) corresponding to the Manage Legal Addresses task under Define Legal Jurisdictions and Authorities for Financials.

2. The Manage Legal Addresses page will open. To create a new legal address, click on the Create icon (circled in the screenshot below).

3. Enter the details of the location and click on the OK button.

Fig. 17 - The ‘Manage Legal Addresses’ task

Fig. 18 - The ‘Manage Legal Addresses’ task page. The ‘Create’ icon is circled

Fig. 19 - Creating a legal address

(The next tutorial explains about legal entities in the enterprise)

{tab Course Contents | orange}

{tab-l1 Day 1 | orange}

Introduction

What is ERP ? , comparison of Oracle Apps with other ERPS
Types of Roles , Types of projects, AIM documents
Oracle Apps file structure, database structure and 3-tier architecture
Application Object Library
Levels of Oracle Applications, Creating users, WHO columns, Creating responsibilities
Menu construction, Defining concurrent program
Concurrent program with parameters, Creating Value sets, incompatibilities
Scheduling concurrent program, Creating request group, Creating request set
Concurrent program creation using API

Module Overviews

Inventory Module flow with base tables
Accounts Receivable module flow with base tables
Order Management module flow with base tables

{tab-l1 Day 2 | green}

Reports

Report development process, Report registration process
Bind parameters, lexical parameters, reports with value set, Building report manually
Using repeating frames, Summary columns , Standard report customization

Interfaces

Introduction to Interfaces, working with Out Bound Interfaces, using UTL_FILE package
Inbound Interface process, Working with SQL*Loader tool
Different option in SQL *Loader tool, bad file, discard file
Using Interface table approach
Using API Approach

{tab-l1 Day 3 | red}

Conversions

Introduction to conversions, Creation of staging table
Developing the validation package, Explaining the real time project code.
Completing the conversion task, Differences between Inbound interfaces and Conversions

Forms

Form development process using TEMPLATE.FMB , Form registration process
Form personalization
Using Custom.pll

{tab-l1 Day 4 | blue}

Workflows

Workflow Introduction, Workflow development process, running the workflow
Sending notifications, branching the workflow using resultout variable

XML Publisher

Introduction to XML publisher, Report development process
Creating reports for multiple rows, Creating Data definitions, Creating templates

{/tabs}

{tab Enroll | orange}

{tab Training Hours | red}
5-6 Hrs starting from 5:30pm Indian Standard Time
{/tabs}

Oracle Application Development Framework (Oracle ADF) is a new and groundbreaking Java EE development framework that is supported and enabled by Oracle JDeveloper 11g. Oracle ADF simplifies Java EE development by minimizing the need to write code that implements the application’s infrastructure. It allows developers to focus on the features of the actual application. Java EE is a standard, robust, scalable, and secure platform that forms the basis for many of today’s enterprise applications. This course is aimed at developers seeking to build Fusion web applications using Oracle ADF. Participants use Oracle JDeveloper 11g to build, test and deploy an end-to-end application. The data model is built with ADF Business Components and the user interface is built with ADF Faces. During the course, participants learn to build each part of the application with the Fusion technology stack for deployment to the WebLogic Server.