User Rating: 0 / 5
In this training article we will understand all about Reporting Currency and how to create it in the instance.
What are Reporting Currency :
Reporting Currency are the currency used for financial, legal & management reporting. If the reporting currency is not same as that of ledger currency, we can use foreign currency translation process or reporting currencies functionality to convert the ledger account balances in the reporting currency. Reporting currency can be based on primary or secondary ledger. A reporting currency can differ from its source ledger in its currency and some processing options, but shares the same chart of accounts, accounting calendar, and accounting method with its related ledger. Let say a company is operating in UK and US, UK being the head office. Both the countries are using same calendar & chart of account but different currencies - UK is using GBP and US is using USD. So when US is reporting to UK management, they need to report in GBP. In that case we need to create a reporting currency based on primary ledger of US and create reports in GBP for management purpose.
User Rating: 5 / 5
Variables are used in ODI to handle ETL parameters. It is a very powerful feature and one needs to understand them to effectively use them in your project. The purpose of this article is to explain ODI variables, different types and its usage.
What is an ODI Variable?
A variable is an object that stores a single value. This value can be a string, a number or a date. The variable value is stored in Oracle Data Integrator. It can be used in several places in your projects, and its value can be updated at run-time.
A variable has the one or more of the following properties:
Variablescan be used in any expression (SQL or others), as well as within the metadata of the repository. A variable is resolved when the command containing it is executed by the agent or the graphical interface.
User Rating: 5 / 5
Introduction of Essbase Cube in Fusion Applications
Essbase cube stores balances from multiple data sources in multidimensional cubes. Users interact, report, and analysis data in real time and along business dimensions and hierarchies in Fusion Applications. Fusion Accounting Hub leverages Fusion General Ledger and Fusion General Ledger combines traditional general ledger functionality with embedded Oracle Essbase. Fusion Accounting Hub’s reporting platform provides real-time access to financial information with exceptional reporting and analytics capabilities to all users. This makes reporting platform unique with its embedded multi-dimensional data model that leverages Oracle Essbase, the market leading online analytical processing (OLAP) server. The purpose of embedding the Essbase cube with this reporting platform is-
This allows to store large quantities of data in a way that can be accessed rapidly.
Also this helps to manage and organize this data for fast and powerful retrieval for immediate decision support
At the time users create their chart of accounts, the Oracle Essbase cube is created automatically. If a cost center is added or a date-effective hierarchy is modified, Fusion General Ledger automatically creates or modifies the corresponding cube hierarchy in Essbase. As transactions/journals are posted, Fusion General Ledger automatically updates the multi-dimensional balances to ensure that balances are always in sync and up-to-the-minute accurate. No batch programs need to be run to populate the multidimensional balances, it is all happening in real-time whenever a journal or transaction is posted.
Business Benefit of Essbase Cube
Fusion General Ledger also pre-aggregates balances at every possible summarization level across each dimension of the chart of accounts and accounting periods for multiple date-effective hierarchies. This results in extremely fast reports and queries. Reports and analytics can be refreshed on-the-fly without having to run a process or program because the balances have already been pre-calculated. Multidimensional analysis is also instantaneous. Users can quickly slice and dice data across dimensions and drill up, down, and sideways on any parent level.
Intelligence and analytics have also been embedded within the context of a business transaction, before we post a journal, the system will tell them the impact the journal will have on an account’s balance. This eliminates the need to have to navigate to a separate page to run a query or run a report. This helps users make smarter decisions faster while remaining in context of the transaction and staying focused on completing the task.
GL Posting program in Fusion General Ledger has undergone some changes due to enhancements made to the program, new features included in Fusion and especially integration with Hyperion Essbase which basically embeds Essbase into Fusion General Ledger. This offers-
Entered Currency Balancing: In Fusion all transactions will need to be balanced by entered currency at posting time. This is to be done after suspense and intercompany and before rounding imbalance.
Integration with Essbase: The posting program updates the Essbase Cube that gets created upon the completion of the ledger setup. It updates balances in both the GL_BALANCES table and the cube dimension members to keep them in synch.
User Rating: 0 / 5
Creating Account Combinations in Oracle Fusion Application
In this training article we will learn how to create account combinations in detail. We would also look carefully into the impact of cross validation rules on creation of account combinations.
Prerequisite Setup for creating account combinations:
Before creating account combinations we must configure the chart of account and value set values. In case we have specified dynamic insertion, then we are not required to create account combinations. However in case few restricted account combinations are required, we can go for it.
Creating account combinations:
Navigation- Select Implementation project from Setup & Maintenance area and go to Manage Account Combinations as shown below-
We will get the following screen-
Specify the chart of account and click on Add icon-
User Rating: 5 / 5
This quick video shows how to open your first period in Fusion General Ledger. You must attach yourself to the data role that gives access to the desired ledger.
User Rating: 5 / 5
Steps Required for Controller Extension in R12.2.X
The method to deploy controller & OAF components in pre-R12.2.x is much diffrent than in R12.2 onwards. Lets see how it is done.
User Rating: 5 / 5
Previous articles we discussed about overall Receivables process,Setups to create an Invoice & apply receipt to it.In this article we will continue with details of setups and more details around late charges,access & setups related to accounting in Receivables & upto posting Receivables journals to Oracle Fusion General ledger.
Continuing from last article below is summary of Receipt setups for various receipt application we discussed,simple table quickly identifies what setup is required is for each type of receipt creation method.
When creating the receipt classes and methods, there are four primary considerations.
First,determine whether receipts will be created manually, via a lockbox or through automatic receipt processing.
•When creating receipts manually or via lockbox, the receipt class Creation Method should be Manual.
•When using automatic receipts, the Creation Method should be Automatic.
Second, determine which bank accounts are used for remitting receipts.
•Payments received in the form of checks or electronic payments, such as, bank account transfer or credit card payment, need to be remitted to the bank. These payments can be remitted directly or factored in return for cash.
Cash payments do not need to be remitted to the bank.
•It is possible to enter several remittance bank accounts for each receipt method. However, one remittance bank account must be designated as the primary bank account for each currency used.
Third, determine the minimum receipt amount before remitting a receipts to the bank. Receivables allows the deploying company to control the minimum receipt amount allowed to be remitted to a bank account by setting a minimum threshold.
Lastly, Payments that are remitted to the bank must be cleared before they are available as cash. Users can choose to clear receipts either by using Receivables’ automatic clearing process or by Oracle Fusion Cash Management’s bank statement reconciliation.
User Rating: 5 / 5
Designing Account Hierarchies in Oracle Fusion Application- Part 2
In this training article we will learn how to create account hierarchies step by step. We would also discuss the prerequisite setups required to achieve the task.
Prerequisite Setup for designing account hierarchies:
Before creating account hierarchies we must configure the chart of account and value set values. While creating value set values for parent and child we must adhere to the following requirements. For child values we need to select Summary as No and allow posting and allow budgeting as Yes as shown below-
In case of parent values we need to select Summary as Yes and allow posting and allow budgeting as No as shown below-
Similarly we can create values for parent and child Company-
Prerequisite Setup for designing account hierarchies:
In order to create a new hierarchy we will configure the task Manage Account Hierarchies-
User Rating: 5 / 5
Oracle E-business tax is a new product in R12. It provides the infrastructure for transaction tax knowledge management and delivery using a global system architecture that is configurable and scalable for adding country-specific tax content. It is a single point solution for managing transaction-based tax. Apps2Fusion helps you learn how to use the tax software within your company, Basic Tax Setup in Oracle E-Business Tax and much more.
Tax Determination Management E-Business Tax configuration flow Regime to Rate flow Tax Zones Party Tax Profiles Self-Assessment taxes Tax configuration ownership Configuration options Fiscal classifications: party, product, and transaction Product Tax Exceptions Rule Engine Rule Types Determining factors: party, product, place, and process Tax Determining Factor Set Rules setup example Expert Tax Rule Entry Tax Recovery Rates Recovery Rate tax rule
Oracle E-Business Tax Overview
E-Business Tax key concepts
Integration within Oracle E-Business Suite
Part 1: Oracle E-Business Tax Basic Tax Configuration
Part 2: Oracle E-Business Tax Basic Tax Configuration
Additional setup options
Tax Reporting types
Managing Party Tax Profiles
Configuration Owners and Service Providers
Part 1: Setting Up Tax Rules
Tax Rule defaults
Guided Tax Rule Entry
Make tax available on transactions
Oracle Tax Simulator
Part 2: Setting Up Tax Rules
Regime Determination Set
Tax Condition Sets
Part 3: Setting Up Tax Rules
Tax Recovery processing
Managing Taxes on Transactions
Tax Determination Management
E-Business Tax configuration flow
Regime to Rate flow
Party Tax Profiles
Tax configuration ownership
Fiscal classifications: party, product, and transaction
Product Tax Exceptions
Determining factors: party, product, place, and process
Tax Determining Factor Set
Rules setup example
Expert Tax Rule Entry
Tax Recovery Rates
Recovery Rate tax rule
Start Date: 18th April 2015
Duration: 3 Days
Training Schedule: 18, 19 & 25th April 2015
Training hours: 5:30PM to 11:30PM Indian Standard Time
User Rating: 0 / 5
Profile Options in Fusion Application- Part 2
In part -2 of this training article on Profile Options, we will understand how to Plan Profile Options, Configure Profile Options and Organize Profile Options in Categories
Profile Option Hierarchies and Levels
Application developers specify at which hierarchy level a profile option is enabled in the system. The predefined profile option hierarchy levels are site, product, and user. The hierarchy levels specified in the profile option definition determine the context in which a profile option value may be set. If the profile option value at a particular level is updatable, an administrator can update the profile option value for that context.
A profile option may be enabled at any or all hierarchy levels. When enabled at all levels, the predefined ordering of profile option hierarchy levels gives precedence to the values that are set at the user level over values set at the product and site levels, and precedence to values set at the product level to values set at the site level. If there is no value for the current user, then the product value applies. If there is no value for the user or product, then the site value applies.
Below table shows the predefined profile option hierarchy and ordering.
We can configure updatable values for profile options at one or more levels depending on which levels are enabled in the profile option definition. When a profile is set at more than one level, higher levels of specificity override lower levels of specificity.
In the example, if the currency setting for the site is UK pounds sterling, but the Financials division works in the Netherlands using the Euro, a manager in the US can override that product level setting at the user level to use US dollars when accessing Financials applications. In another example, if a profile option called Printer is set only at the site and product levels. When a user logs in, the Printer profile option assumes the value set at the product level, since it is the highest level setting for the profile.
The profile option values specified at the site-level work as defaults until profile option values are specified at the other levels.
Key Considerations while Planning Profile Options:
Plan profile options before defining and configuring them. The following aspects will assist in better planning on how to manage profile options.
• Profile option tasks
• Before creating a profile option
• Profile options data model
User Rating: 0 / 5
Profile Options in Fusion Application- Part 1
In this training article we will understand all about Profile Options in Fusion Application. In part-1 of this, topics covered are like overview of profile Option, Profile option Definition and Configuration, what are different values of Profile Option in Fusion Application and profile option’s categories etc. In part -2 we will understand Planning Profile Options, Configuring Profile Options and Organizing Profile Options in Categories
Profile Options overview:
Profile options manage configuration data centrally and influence the behavior of applications. Profile options serve as permanent user preferences and application configuration parameters. We normally configure profile options with settings for specific contexts or groups of users. Users customize how their user interfaces look and behave by changing the values of available profile options.
Profile options store the following kinds of information.
We can add and configure new profile options in addition to configuring predefined profile options that are implemented as updateable.
Profile Option Definition and Configuration
Application developers add new profile options and configure ones that are not to be updated by other users. Application administrators and implementation consultants configure profile options with profile option values that are implemented as updatable. Profile option definitions consist of the following.
Profile option name
Application and module in the application taxonomy
Profile option values
Profile options categories
Profile option levels
Profile option level hierarchy
Profile options can appear on any user interface page without indication that a profile option is what is being set.
Profile Option Values
Some profile options have predefined profile option values. The Manage Profile Option Values task flow allows an administrator to set updatable profile option values at the available levels, including the user level.
We can access the Manage Profile Option Values task starting in the Setup and Maintenance Overview page and searching for profile option tasks.
Click on Go To Task, enter application name and search
User Rating: 5 / 5
Simply put , under receivables process Invoice is generated Amount against which payment is received & revenue recognized. However basic business process remaining the same, Oracle Fusion Receivables provides considerable business efficiency over earlier releases. Lets see how,where & exactly how Fusion Receivables simplifies processes to enable business focus on more important issues like Making calls to resolve Delinquencies,Customer Queries.... rather than worrying about records stuck in Autoinvoice.
Continuing from Previous article we where discussed about overall Receivables process,Setups to create an Invoice & apply receipt to it.In this article we will continue with details of setups and more details of invoicing,receipts , access & setups related to accounting in Receivables
& Continue discussing late charges , revenue management , creating write-offs & finally posting Receivables journals to Oracle Fusion General ledger in following article.
Job Roles and Duty Roles for Performing Receivables Activities
The pre-defined job roles have the following duty roles associated to them
Custom Security needs can be met by managing the duty role assignments
User Rating: 5 / 5
Oracle Fusion Receivables Process & Setups at a glance.
This series of articles aims to be a quick launchpad into Fusion Receeivables without spending hours going through numerous pages of user/implementation guides.We will do three 20minutes recap into Fusion Receivables starting with this fisrt on in series.
Simply put under receivables process Invoice is generated Amount against which payment is received & revenue recognized. However basic business process remaining the same, Oracle Fusion Receivables provides considerable business efficiency over earlier releases. Lets see how?
1. Bill Customer, which includes the creation and processing of invoices and billing adjustments, as well as template-based bill presentment options
2. Manage Revenue, which includes the processing of revenue and revenue adjustments with timely, accurate and event-based revenue recognition
3. Process Customer Payments, which includes the processing and application of customer payments, processing of bank deposits and clearing accounts receivables transactions, and processing refunds
4. Mange Accounts Receivable, which includes managing customer inquiries, processing late charges and customer statements, as well as, adjusting customer balances through automated or manual write-offs of invoices and receipts.
5. Managing Accounts Receivable also provides quick access to generating Subledger Accounting for all accounting events, reconciling receivables to the general ledger, and performing period close activities
6. To assist users with their daily and period-end activities, integration with Business Intelligence Analytics and Transactional Business Intelligence provides easy-to-use predefined reports, embedded analytics and user-configurable reporting.
• Automated creation of billing in a variety of formats to suit your company needs
• Automation of customer payment processing with new Smart Receipts engine for more efficient cash application
• Receivables management that includes interactive reporting for quicker reconciliation and period close cycle
• Contingency based Revenue Management
• Easy access to billing and payment information for managing customer inquiries and performing account adjustments
User Rating: 5 / 5
While Implementing Fusion HCM Workforce Deployment one of the activities is to create Geography and Geography Structure, Geography Validations.
You have two options to enter the geography data into the application. Depends on the complexity and volume of data, you can either enter it manually using the interface or you can import the data from the file using File-Based Import Process. If there is a large volume of geographic data, then importing the data is the most efficient way of creating your geographies.
For data integrity reasons, you cannot add new geography structures or modify existing ones after you import your geography hierarchy, so before importing you should consider the following:
1. Include all the possible geography types your application may need. For example, you may want to base some sales territories on counties even though you do not use counties in your addresses.
2. Geography reference information is shared by other applications so you must consider the needs of these applications as well. For example, financial applications may require you to include geography structures to satisfy local tax laws. Even if you are not implementing financial applications today, you may do so in the future.
3. You may want to review the seeded address styles for the countries you are going to be importing and modify them as required. The address styles indicate the required elements of a street address or a tax address. You can review the address styles from the Setup and Maintenance Work area by searching for and using the Manage Address Formats task.
4. The source and reliability of the geography data you are about to import.
5. Using the Manage Geography Structure page, you can add additional geography types to the bottom of your country structure.
6. Provided you have not yet uploaded the geography hierarchy, you can also add additional geography types in the middle of your structure. (To do so, you must first delete all the geography types below the insertion point, insert the one you missed, and then add the geography types you deleted.)
Geography Model Concepts
Geography: Any geographical region with a boundary around it, no matter what the size is, such as Kerala (a State), Russia (a Country), San Francisco (a City), Miami-Dade (a County), or Minato-ku (a Ward in the City of Tokyo).
Geography Type: The name given to a type of geographical region, for example, a country, state, province, county, or city.
Geography Structure: Defines the structure of the data you are creating for the country. It specifies the geography types that you must have for your addresses and territories for that country and how they are organized. Different countries use different geography types and different structures. In the U.S. you must include cities and states. In Japan you must include prefectures, municipalities, districts, and wards.
Geography Hierarchy: The hierarchy of the geographies for a country is based on the geography structure. Geography hierarchy is a data model that lets you establish conceptual parent-child relationships between geographies. The top level of the geography hierarchy is Country, so the hierarchy essentially contains countries and their child geographies.
User Rating: 5 / 5
Designing Account Hierarchies in Oracle Fusion Application- Part 1
In this training article we will understand what account hierarchies are and why we require those. In the subsequent articles we will learn how to design Account hierarchies in Oracle Fusion applications step by step. We will also discuss the recommendations and best practices followed for designing the same.
What are account hierarchies? :
We need to create account hierarchies in order to reflect managerial, legal or geographical relationships between the value set values. The financial balances are pre-aggregated at each parent level in the hierarchy, thus allowing fast and robust account inquiry and drill. An organization operating at multiple levels always need a track on the account balances at each level for various managerial purposes. Say for example a company has multiple sales departments selling IPAD, IPHONE, laptop, etc at various geographic locations. The top level management may not be interested on sales at granular level. They want to track the overall sales which the company has registered. In that case we need account hierarchy. Again in the said company a regional manager for a particular region responsible for IPAD and IPHONE only would be generating report from only two divisions operating in the particular allocated region using account hierarchies. In a nutshell we use account hierarchies to track the figures country wise, department wise, regional wise, territory wise, product wise and so on using Account hierarchies.
Why we create Account Hierarchies? :
Account hierarchies can be created for various requirements-
Creating multiple hierarchies for different purposes e.g. define three different hierarchies to be used for each chart of accounts segment that has roll ups, each for a particular purpose.
Hierarchies for financial reporting. It must be published to Essbase cubes. Child values in these hierarchies cannot roll up to different parents within a hierarchy as this functionality is not support when publishing such hierarchies to Essbase.
Hierarchies for allocations. It must be published to Essbase cubes. Used with Allocation Manager in creating allocation rules.
Hierarchies for cross-validation rules, revaluation and chart of accounts mapping :
a) Created within the same hierarchy and must be associated with a chart of accounts instance.
b) Only associate one hierarchy with a chart of accounts instance, per segment
c) Such hierarchies can have the same child to roll up to different parents.
d) Do not publish to the Essbase cube since multiple child assignments are not supported in the Essbase cube.
How many hierarchies should we define? :
Hierarchies are built on top of value set values. We can define as many as we want per value set. However the best practice is to creating different hierarchies for trees that serve different business purposes (e.g. management versus geographical hierarchy), and within each hierarchy define date-effective versions to reflect changes over time.
We can perform the following task-
Create account hierarchies (trees) to identify managerial, legal or geographical relationships between the value set values. A segment in the chart of account can have multiple hierarchies and each hierarchy can have multiple versions.
User Rating: 0 / 5
How to enter Daily Rates Manually in Fusion Application
This article will helps to understand how we can enter Currency daily rates manually step by steps in Oracle Fusion Applications.
As we know all the currencies are already defined in the system. Below are the Rate types already there in the system-
Corporate- this type is used for management reporting and normally defined once in a month or whenever there is drastic change in the rate of currency.
Fixed- Fixed rate are for currency which fluctuate very less like USD and AED
Spot- we upload daily we get from bank and have too much fluctuation
User- These are the rate specified by the user while entering the transactions
We can create our own exchange rate and can be used in the transaction but normally out of these 4 rates are used.
Let’s first download the installation files from Navigator - Tools - Download Desktop Integrator Installer as shown in the below screen shot-
Entering Daily Rates
To upload the daily rate we cannot use this screen manually as we have to upload by using spreadsheet functionality.
Let’s assume that we are required to enter the daily rates for currency conversion from United States dollars (USD) to Great Britain pounds sterling (GBP) to each day for our company Apps2Fusion.com
Oracle Application Development Framework (ADF) Desktop Integration is an Excel add-in that must be loaded onto each client.
1. Click the Manage Currency Rates link. Use the Currency Rates Manager page to create, edit, and review currency rate types, daily rates, and historical rates.
2. Click the Daily Rates tab. Use the Daily Rates tab to review and enter currency rates.
User Rating: 5 / 5
Reference Data Set overview in Fusion Applications
This training article will helps to understand all about Reference Data Sets in oracle Fusion Application along with important definitions.
Reference Data set is a new concept available in Oracle Fusion Application and are logical groups which provides the enterprise to decide which business unit access the reference data groups, such as grades, locations, Tax Classification codes, AR & AP payment terms, departments, and jobs. Oracle fusion provides a default Reference Data set which can be used across all Business units. However, we can define our own Reference data sets.
Below are the tasks involved to define Common Application Configuration under defining Enterprise structure for Reference Data Set-
1. Define Reference Data Sharing
a. Manage Reference Data Sets
b. Manage Set Assignments for Set Determinant Type
Main advantage of using Reference Data Sharing is to helps organizations share common transactional data without unnecessary duplication.
For example, if organization has several business units and each business unit uses different payment terms on a customer invoice. Instead of each business unit creating and maintaining individual payment terms, one can define the payment terms reference data at the organization level and use that data into partitions (create reference data sets) so that the different payment terms can be assigned to each business unit.
Reference data sharing helps to:
Create reference sets across tables or lookup types.
Share information and data processing options among the determinant types, such as business unit or asset book.
Create separate sets and subsets for each business unit depending upon its business requirement.
Create common sets or subsets to enable sharing reference data between several business units, without the need for duplicating the reference data.
Define Reference Data Sharing
Manage Reference Data Sets: We can use this page to create the Set Code, Set Name, and Description that can then be assigned to reference data.
Click on Create button to define new Reference Data Set-
User Rating: 5 / 5
Best practices on Designing Chart of Account in Fusion Application
The most important part of implementation is to plan the structure of Chart of account which should align with the business requirements and future prospects. The training article is aimed to discuss the approach which we should follow while designing a chart of account.
Chart of Account Components:
As we know that in Fusion applications the chart of account, calendar, accounting conventions and currencies are called the 4 C’s and are the main components required to create ledger. The components of Chart of account is shown below -
Chart of Account:
The chart of account is an accounting key flexfield that we configure and use as he underlying structure for organizing our financial information and reporting. In Oracle Fusion Applications, the chart of account is:
Flexible: We should design an account structure that meet our reporting needs and anticipates the way organization runs now and in future.
Hierarchical: That should summarize accounting information from multiple perspectives by creating accounting hierarchies.
Secure: We should use segment security and cross-validation rules to secure the data and prevent the creation and use of incorrect accounts.
How to decide on Chart of Account Segments:
We should assign each business dimension a separate segment
Keeping each business dimension in a separate segment to improve the reporting.
Examples are: Combining location and department into one segment can prevent retrieving data by department across locations or restricting certain departments to specific accounts.
We should avoid having more than one meaning for each segment
Multiple meaning would complicate default values in a segment during data entry, isolating different data for reporting, or logically assigning codes or numbers to segment values.
Examples are: Assigning one generic segment for sub-account, project and product elements prevent analysis of product sales by individual project.
We should consider creating one or two segments to handle any future reporting requirements.
Usage of alpha characters only in parent account segments
Enter numerical child value characters using the ten-key pad and avoid shifting hand position for alpha characters.
We should consider data entry efficiency while ordering the segments;
Place segments with defaults at the beginning, end, or in both the beginning and end of the chart of accounts so the segments requiring data entry are grouped together.
Creating Global Chart of account:
We should create uniform chart of account when we are the organization is operating globally. This help in consolidating the reports for the organization as a whole..
Creating Vertical structures:
Hierarchies can be used to summarize balances vertically. This can be used to reduce the number of required segments.
Considerations before configuring COA segments
We need to decide (???)
Whether to allow alphabetical characters in the chart of accounts.
The size of chart of account segments. Best practices recommend 5 to 9 segments.
The coding scheme for the chart of accounts values, for example asset account with 1, liability account with 2, revenue account with 3 and expense account with 4.
Numeric and alphanumeric values.
Numeric: Use for easier data entry because we can use the ten-key pad. The sort order and ranges are easier to configure.
Alphanumeric: Set up the codes in all uppercase to enable consistency and ease of sorting and querying.
Both Numeric & alphanumeric: Use numeric codes for child values and alpha codes for parent values. This would allow us to visually distinguish levels of the hierarchy for reporting and inquiry.
However regardless of whether we use numbers or alphanumeric characters, we must use the char (character) format type while defining value sets.
Few conditions should be followed while configuring-
We must create value sets first and then add the sets to the structure and instance even though the Manage Chart of Accounts Values Sets appears second in the Setup and Maintenance work area list. We should not create values before assigning the value sets to the structure and instance as the value attributes such as Allow Posting or Account type are not available for data entry. After creating the structure and instance, we should create values for value sets.
Creating cross-validation rules before creating account combinations will ensure that we do not accidentally create invalid account combinations. Cross-validation rules only affect the creation of new account combinations created after the rules are enabled.
While creating values for Chart of account we need to attaching attributes-
Whether it’s a summary (parent) code or a child code.
Allow posting for the code or not
Similarly allow budgeting or not
Account type is grouping of account like asset, liability, etc
Third party control accounts: While defining natural account segment values, we can designate an account as a control account using the attributes in the Manage Values page from the Setup and Maintenance work area.
Let us understand the meaning of options available:
Customer: Restricts journal posting to this account to those from the sub-ledgers that use a customer on a transaction, example: Receivables.
Supplier: Restricts journal posting to this account to those from the sub-ledgers that use a supplier on a transaction, example: Payables.
Restrict Manual Journals: No manual journals are allowed to use this account.
Yes: Restricts this account to all sub-ledgers
No: Not a control account.
Customer, Supplier and Yes values also restrict manual journal ledger journal entries.
User Rating: 5 / 5
Defining Cross Validation Rules in Fusion General Ledger
Overview of Cross Validation Rules
In Oracle Fusion General Ledger, cross validation rules are used to determine the account combinations that users can create dynamically when they enter transactions or journal entries. Once enabled, cross validation rule determines whether a selected value for a particular segment of the account combination can be combined with specific values in the other segments to form a new account combination.
If account combinations already exist and violate the newly enabled cross validation rules, these account combinations continue to be valid. Before disabling any existing account combinations that violate cross validation rules and that are no longer in use, we must move the balances in those accounts to the correct accounts. Then disable the account combinations manually to prevent further posting.
We should define and enable cross validation rules before-
Balances are loaded
Transactions or journal entries are imported or entered
Account combinations are created
The standard functionality in Oracle Fusion Application does not provides a central place to enable and disable all CVRs. Let us now understand how Cross Validation Rules work in Fusion Applications with examples.
Companies may have requirements to prevent certain combinations of segment values to be used in their account combinations, for example a particular cost center may not be combined with a specific company value. Once enabled, cross validation rules determine what segment values may be combined with other segment values across the different segments of chart of accounts. Cross validation rules only affect the creation of new account combinations. When creating a new account combination in user interfaces and processes, the values for each Chart of Accounts (COA) segment are cross checked to make sure they do not violate the validation rules.
A cross validation rule is now defined in terms of a condition filter and a validation filter. The condition filter describes the event under which the rule will be evaluated. If the event specified in the condition filter is not applicable, then the rule will not be evaluated even if it is enabled. The validation filter contains the condition that any account combination must satisfy (when the event specified in the condition filter is applicable) before it can be created. To summarize, a cross validation rule is now defined in terms of a condition filter and a validation filter. The rule is evaluated using the following logic-
If condition is satisfied, then perform specified validations.
If a Company has decided that a certain company value (e.g. Operations) cannot use a specific cost center (e.g. Marketing), then we can define the following cross validation rule to validate accounts accordingly: If Company is equal to 'Operations', then validate that Cost Center is not equal to 'Marketing'.
Setup of Cross Validation Rules in Fusion Applications
While implementation of Fusion General Ledger, set up of CVR is an important step. Cross validation rules should be created at implementation time not after few transactions are entered as undesired account combinations can get created in the interim. Updating and deleting existing rules takes place after the fact but it should not occur very often under normal circumstances.
The cross validation rules user interface (UI) is available from Functional Setup Manager (FSM) and below are the steps to define rules-
Navigate to 'Setup and Maintenance’
Create or Select an implementation project that includes the task 'Manage Cross-Validation Rules'
Click on the Go to Task icon for the task 'Manage Cross-Validation Rules'
User Rating: 5 / 5
Oracle Fusion Functional Setup Manager is the application used to perform the setup tasks required to complete the implementation of Oracle Fusion Applications. The application implementation process includes both manual activities and activities executed within the Setup and Maintenance work area within Oracle Fusion Applications.
Roles required to access FSM are:
• Application Implementation Manager
• Application Implementation Consultant
It utilizes some specific terminology to refer to its own functionality:
User Rating: 5 / 5
Here are top 10 reasons business users & accountants would love Fusion financials, presented in a quick on-the-go readable format for quick review & later in the series we will take deeper dive in these & related topics.
Oracle Fusion Financials offers an integrated financial management suite that is really designed to automate, streamline, and control an organization’s financial management processes end-to-end. It includes a broad suite of applications that are completely integrated. It has your traditional GL, Payables, Receivables, Assets, Expenses, Collections and Cash Management as well as the common module architecture from EBS that includes the centralized Subledger Accounting, centralized customer and supplier data (TCA :Trading Community Architecture), Tax, Payments, and Intercompany.
User Rating: 5 / 5
This training article will helps to understand basic concepts of different roles and their brief definition and we will also try to understand relationship between them. Let us first understand Role Based Access Control in Fusion applications-
Role Based Access Control (RBAC)
An organisation needs to control who can do what on which functions or sets of data under what conditions. The who is a user here. A user's access is based on the definition of the roles provisioned (assigned) to the user. Access is defined as entitlement, which consists of privileges. The what are the abstract operations or entitlement. The which represents the resources being accessed.
RBAC normalizes access to functions and data through user roles rather than only users. User access is based on the definition of the roles provisioned to the user. The roles are defined at functional and technical levels. The functional level is the business definition that is used by business users and the technical level is the implementation of roles using Oracle Technology.
RBAC is based on the following concepts:
Role assignment - A subject can exercise permission only if the subject has selected or been assigned a role.
Role authorization - A subject’s active role must be authorized for the subject. With rule mentioned above, this rule ensures that users can take on only roles for which they are authorized.
Permission authorization - A subject can exercise a permission only if the permission is authorized for the subject’s active role. With rules 1 and 2, this rule ensures that users can exercise only permissions for which they are authorized.
Basically security in Fusion Application is based on Role Based Access Control (RBAC) In Fusion Applications, the RBAC implementation is based on abstract, job, duty, and data roles that work together to control access to functions and data. The definitions of these functional roles are as follows:
This role categorizes the roles for reference implementation. It inherits duty role but does not contain security policies. For example: Employee, Manager, etc.
This role defines a specific job an employee is responsible for. An employee may have many job roles. It may require the data role to control the actions of the respective objects. For example: Benefits Manager, Accounts Receivable Specialist, etc.
This role defines access to the data within a specific duty. Who can do what on which set of data? The possible actions are read, update, delete, and manage. Only duty roles hold explicit entitlement to the data. These entitlements control the privileges such as in a user interface that can see specific screens, buttons, data columns, and other artifacts.
This role defines a set of tasks. It is the most granular form of a role. The job and abstract roles inherit duty roles. The data security policies are specified to duty roles to control actions on all respective objects. Duty Role is the most granular form of role where mainly security policies are attached and they are implemented as application role in Authorization Policy Manager (APM)
Below diagram from the “Oracle Fusion Applications Security Guide” shows relationships between these roles:
User Rating: 5 / 5
Enterprise Structure in Fusion Application – a backbone of Your Financials Implementation
The Enterprise Structures configuration deals with creating your GL structure & can be complete manually or using Enterprise Configurator, which is an interview-based tool to guide through the process of setting up a basic enterprise structure. By answering questions about enterprise, the tool creates a structure of divisions, legal entities, business units, and reference data sets that reflects your enterprise structure. Before we start looking at details of Enterprise structure, below is the Overall process in Fusion GL which will use the enterprise structure.
Financial enterprise structures are the entities that define the reporting, legal and business aspects of your enterprise
Enterprise structure now has a definition & an instance to allow users define various accounting representation.
Chart of accounts structure:
Building block of chart of accounts implementation, geared towards flexibility, minimizing setup efforts. Defines the number of segments, segment sequence, labels and default value set for each segment.
Chart of accounts structure instance:Also referred to as chart of accounts,Multiple charts of accounts can share the same structure, but each may be customized differently to fit your transactional and reporting requirements: Value set,
Account hierarchy, Dynamic combination creation
**Assuming reader is already familiar of it We will not go in much details of COA, Balancing segments, Calendars, Accounting method definitions & their setups.
User Rating: 5 / 5
Creating Implementation project in Oracle Fusion
In this training article we will understand how to create Implementation project in Fusion Financial Application.
Why we create implementation project?
Implementation project is the grouping of task which we need to perform. It decides what we want to implement in the given instance. For example we have HCM, financial and procurement available with us. In this case we can either create a single implementation project for all the offerings or we can create three different implement projects for each offering.
Creating Implementation project:
All implementation related configuration can be done in Functional setup manager (FSM). In order to get the access of FSM, it is mandatory that the roles of application implementation consultant and application implementation manager are assigned to the ID.
The screen below highlights all the offerings which we can implement in the instance. To get to this screen we need to go to functional setup manager and click on getting started. The screen highlights the flow of implementation where first we need to plan which all offering we need to implement. Then we will configure or enable the offerings which we need and also which module we want to implement (for example within financial we can implement general ledger or payable or both , ….). Then we will implement the project based on the offerings configured.
Click on any such offerings say financials. We will get the following screen giving the task list which needs to be followed while doing the implementation. The task list enclosed PDF files listing down the task details which are required to be configured if we want to enable that offering (e.g. financial in this case).
User Rating: 5 / 5
PL/SQL is a combination of SQL along with the procedural features of programming languages. It was developed by Oracle Corporation to enhance the capabilities of SQL. It provides specific syntax for this purpose and supports exactly the same datatypes as SQL. Server-side PL/SQL is stored and compiled in Oracle Database along with SQL itself and Java and runs within the Oracle executable. Gain expertise in developing performance specific queries only at apps2fusion.
What is SQL (Structured Query Language)
Uses of SQL
What is RDBMS (Relational Database Management System)
What is a database schema and its role
What is an sql table and its concepts - explaining table rows and columns
Introduction to SQL constraints such as Unique key, Primary key and Foreign key
Use of SQL constraints on tables
Introduction to SQL Data types - Character, Boolean, Varchar, Integer, Float, Date, Time, etc.,
How to create and drop database in SQL
How to create, alter and delete tables in SQL
Using SQL Data types in tables
Create tables with SQL constraints such as Primary key and Foreign key
Insert data into tables, Insert data into specific row and using WHERE clause in SQL
Update table data
Delete table from Database
Demo to insert data into tables, to Update and delete table and table data
Introduction to using Arithmetic, Comparison and Logical operators such as >=, <=, NOT NULL, etc., and operator precedence in SQL
Simple select statement to retrieve data from table
Select and display only specific column headers from the table
Select only distinct or exclusive values from the table using SELECT DISTINCT COLUMN
Manage column headers in select statement resultant
Sorting data in resultant
Retrieve data from multiple table based on conditions
SQL String functions such as CHAR(), REGEXP(), SUBSTR(), UCASE(), TRIM() and much more
SQL Mathematical functions such as SQRT(), ROUND(), SQUARE() etc.,
SQL Date functions such as CURDATE(), DATE(), DATEDIFF(), etc.,
Using GROUP BY clause, ORDER BY clause, HAVING clause in SQL query
Nested queries in SELECT SQL statement, using WHERE clause, using EXISTS operator and in INSERT statement
5-6 Hrs starting from 5:30pm Indian Standard Time
User Rating: 5 / 5
In this training article we will learn about system generated Data Roles and Data Access set in Oracle Fusion Applications to access newly created Ledger and we will also see how to add Data Roles and Access Set to the user. Let’s first understand briefly about Data Role and Data Access Set-
A data role defines components of data within which a job is performed. The data role inherits the job role that describes the job. For example, a data role entitles a user to perform a job in a business unit and data roles are implemented as job roles for a set of data. The data role inherits abstract or job roles and is granted data security privileges. Data roles carry the function security privileges inherited from job roles and also the data security privilege granted on database objects and table rows.
Let’s understand by this example- an accounts payables specialist in the UK Business Unit may be assigned the data role Accounts Payables Specialist - UK Business Unit. This data role inherits the job role Accounts Payables Specialist and grants access to transactions in the UK Business Unit. Data roles are created and maintained using data role templates in the Authorization Policy Manager (APM).
Data Access Sets
Data access sets define a set of access privileges to one or more Ledgers or Ledger Sets. The information on Ledgers that are attached to data access sets are secured by function security. Users must have access to the segment values associated with the data access sets to access the corresponding GL account.
In the security reference implementation, the IT Security Manager job role hierarchy includes the Data Access Administration Duty role, which is entitled to manage data access sets (the entitlement is Define General Ledger Data Access Set). This entitlement provides the access necessary to perform the Manage Data Access Sets task in General Ledger.
User Rating: 0 / 5
Java is a programming language which is secure, reliable and is not specific to any one processor or Operating System. Web service helps in communication between two applications for the purpose of exchanging data using XML, SOAP, REST and others. XML stands for extensible Markup Language which was designed to describe data in a format which is both human-readable and machine-readable. Learn the integrated use all the above programming aspects only at apps2fusion and gain hands on experience by implementing them.
What is OOPS and OOPS concepts overview
What is Java and its working
Introducing Java Virtual Machine (JVM), Java Development Kit (JDK) and Java Runtime Environment (JRE)
Setting up Java environment
How to use Java and Integrated Development Environment (IDE)?
Demonstrating Hello world program
Classes and Objects in Java
Importing Java libraries
Java basic Datatypes - BYTE, INT, LONG, FLOAT etc., Java Strings and arrays
Java Loops - FOR, WHILE, DO..WHILE
Java Decision making statements - IF - ELSE IF - ELSE, SWITCH-CASE
Java basic operators - Arithmetic Operators, Relational Operators, Bitwise Operators, Logical Operators,
Assignment Operators and Misc Operators
Writing Java Methods
Discussing OOPS in Java - Java Inheritance, Java overriding, Java Polymorphism, Java abstraction, Java encapsulation, Java interfaces
Concept of packages in Java
Java Variable types - local, instance, static variables and using variables in Java program
Java Modifier types - Access modifiers such as public, private, protected and package private
Non access modifiers such as static, final, abstract etc.,
Java Handling exceptions using try - catch - throw
Using Java collections - ArrayList, Linked Lists, HashMaps, Sets etc.,
Using complex data structures
Java thread concepts and Java multithreading
Java Files IO (Input/output) operations
Demonstration and assignments on topics discussed
Fundamentals of XML - What is XML?, XML structure
XML syntax - content and markup
XML element and attribute declarations
XML parameter entities and XML Namespaces
XML validation using Doctypes, Validator, XML DTD, and XML schema
XML parser, XML DOM, XML in HTML and XML in real life
What are web services? Why use web services?
Overview on - WSDL (Web Services Description Language), SOAP (Simple Object Access Protocol),
REST (Representational State Transfer)
Introduction to Java web services API
IDE setup, JavaEE Environment setup with Glassfish server to build, host and consume web service
Build web service client through Stub generation and Consume web service by Calling the service
Code custom web service and deploy to Glassfish server
Accepting input parameters through web services to achieve sending and receiving of data through
Understanding WSDL at depth and customizing WSDL
Schema types and Binding styles in WSDL
Using JAXB annotations and role of XML in web services
Testing web services using SoapUI
Duration: 8 Days
Training Scheddule: Contact us for dates
Training Hours: 5:30P.M to 11:30 P.M Indian Standard Time.
User Rating: 0 / 5
Oracle Hyperion planning helps you in creating and administering Planning applications. Oracle Hyperion Planning is a centralised, Excel and Web-based planning, budgeting and forecasting solution that integrates financial and operational planning processes and improves business predictability.At apps2fusion training, you will learn Main features, Product architecture of Hyperion Planning and also, Create planning apps, setting up security and much more.
User Rating: 5 / 5
Succession management enables your organization to develop and maintain succession plans to determine who will eventually replace personnel currently in key positions. Using Oracle Fusion Succession Management business process, users can determine who is ready to transition to positions before the positions are vacant to ensure a smooth transition, and provide visibility to the appropriate individuals to manage the process.
Succession Plans Overview:
Manage Succession Plans
Create and edit succession plans using a guided process, or disable those that are no longer needed.
View Candidate Readiness and Plan Strength
View at a glance the number of candidates, the plan strength based on the number of candidates and their readiness. Use the sunburst to focus on each readiness category and drill into more details about each candidate, such as the plans they belong to, performance compensation data, and goals
Review Succession Plan Details
Select a plan to view details, including the names of the candidates and the readiness level of each, and all the job data connected with the plan. For incumbent plans, you will see additional key data, such risk of loss and impact of loss ratings, the reason for the incumbent's departure, if available, and the estimated time in the job.
Access Candidate Detailed Information
Use the sunburst to focus on each readiness category and drill into more details about each candidate, such as the plans they belong to, performance compensation data, and goals.
User Rating: 5 / 5
Overview of Business Unit in Oracle Fusion Applications
The purpose of this document is to make the reader understand about the concept of Business Unit and points which needs to be accounted for before creating the same.
A business unit (BU) of an organization/enterprise is a unit which performs all such business transactions that are defined by the management. This of course should match with the objective of the organization. A business unit can process transactions on behalf of a legal entity which would finally be rolled up in a management hierarchy provided the Chart of account is designed accordingly. So we are required to assign the business units to one primary ledger. Usually a BU would have a manager, strategic objectives, a level of autonomy, and responsibility for its profit and loss.
A business function represents a business process, or an activity that can be performed by people working within a business unit and describes how a business unit is used. The following business functions exist in Oracle Fusion applications:
Billing and revenue management
Customer contract management
Order fulfillment orchestration
Procurement contract management
A business unit can perform many business functions in Oracle Fusion Applications. Prior to Oracle Fusion Applications, operating units in Oracle E-Business Suite were assumed to perform all business functions, while in PeopleSoft, each business unit had one specific business function. Oracle Fusion Applications blends these two models and allows defining business units with one or many business functions. In Oracle Fusion, business unit can be used in processing any transaction, reporting and data security.
Creating Business Unit:
While creating business unit we must specify the level at which it is to be created. Business units in an enterprise may be represented at the business function level, such as Sales, Consulting, Product Development, etc. We can create business units at following levels-
User Rating: 5 / 5
Using the Oracle Fusion Human Capital Management (Oracle Fusion HCM) File-Based Loader, you can load data in bulk, including business object history, from any data source to Oracle Fusion HCM.
Key Features of File Base Loader
File-Based Loader uses the Oracle Fusion HCM Load Batch Data process to load your source data to the Oracle Fusion application tables. The Load Batch Data process:
Data Loading Sequence used in Oracle Fusion HCM File-Based Loader
For successful use of File-Based Loader:
Security Roles required for FBL
To load data from the Oracle Web Center Content server, you must have the duty role File Import and Export Management Duty. By default, the following job roles inherit the File Import and Export Management Duty role:
To load data from the Load Batch Data stage tables to the Oracle Fusion application tables, you must have the HCM Batch Data Loading Duty role. By default, the following job roles inherit the HCM Batch Data Loading Duty role:
User Rating: 5 / 5
Getting Started in Oracle Fusion Applications
As we know Oracle Fusion Applications are designed by using the latest technology advances and incorporating best practices gathered from thousands of customers as well as best of Oracle acquired companies like Peoplesoft, JD Edwards, and Siebel etc. These are completely open, service-enabled enterprise applications. Designed with features for the best-in-class user-interface designs and workflows that optimize usability and deliver business value.
First of all, Lets understand different adoption option to Fusion Application for existing customers. As shown in the diagram, below are the different options to Implement Oracle Fusion Applications-
In the first Option, customer has to do nothing as they do not have to adopt Oracle Fusion Applications if they do not opt for need of Oracle Fusion Applications right now. In a coexistence option, below are the 3 adoption strategy for Oracle Fusion Apps-