Showing posts with label Oracle Application - Common Modules. Show all posts
Showing posts with label Oracle Application - Common Modules. Show all posts

Friday, January 30, 2015

How to Define Segment Values in Accounting Flex field in Release 12.2

How to Define Segment Values in Accounting Flex field in Release 12.2 

Not able to Search Value sets in R12.2

In Release 12.2 Value set Insert/Update depends on Security access. To Insert/Update the Accounting Flex filed segment values for a specific user, User need to follow below steps
By Default in R12.2 a user will not be able to see any values in the value set / Key Flexfield values Form and will receive an error
FRM-40212: Invalid value for field FLEX_VALUE_SET-NAME




To Insert/Update the Accounting Flex filed segment values for a specific user, User need to be provided with appropriate Grants.
Please follow below steps toad Grants for User to Insert and update Value Sets.

Responsibility : Functional Administrator
Go to Navigation : Security à Grants à  Create Grant

1.Name            :Give Name as Required
2.Grantee Type :Select as Specific User
3.Grantee         :Select the Required User Name from List of Values
4.Object           :Select Object as ''Flexfield Value Set Security Object(1)'' from List of Values
5.Set               :Select the Set as ''Flexfield Value Set Security Insert/Update Set'' from List of values .
6. Click on ''Apply'' Button


Add the Object Data Context : All Rows



Select the Set as ''Flexfield Value Set Security Insert/Update Set'' from List of values






After creating the grants from functional administrator, we will be able to perform the following in Value set and Key Flex field Values form:

i) Access the values in Name field LOV, when we Find Values By Value Set.
ii) Access the values in Application,Title,Structure & Segment field LOV's, when we Find Values By Key 
Flexfield
iii) Access the values in Application,Title,Structure & Segment field LOV's, when we Find Values By 
Descriptive Flexfield
iv) Access the values in Application, Name & Parameter LOV's, when we Find Values By Concurrent Program.


Monday, February 10, 2014

Sub-ledger Accounting Configuration - Part 1

Sub Ledger Accounting method (SLAM):

SLA is a rule based accounting Engine that introduced the ability to define how transactions originating in Sub Ledgers can be Accounted. Hence in order achieve this high level of flexibility SLA is accommodated with lot of configurable and predefined components.

This article will talk about different Predefined and configurable components of SubLedger Accounting which are used to setup accounting rules in order to achieve various accounting requirement.

Below mentioned are Predefined Components of SLA. We will talk about their specific Examples as we move on.

Predefined Components of SLA:
Entities:

Entities in SLA represent a Specific Document category in the Application. For example an Invoice or Payment in Account Payables. 









Event Class:
Event Class in SLA represents a specific type of the entity for which the Corresponding accounting entry will be generated. For Example a Standard Invoice is a Type Of invoice there by Standard Invoice will be an Event class for the Entity AP Invoice.


Event Type:
Event type is an Action or an event which should be defined as trigger for the creation of accounting entries.

For example: in reference to a Standard accounting requirement an Standard Invoice should get accounted once it is validated. Hence the Event which will initiate the accounting for the invoice is Validation. So Standard invoice validation is the Event Type for Event Class Standard Invoice
In Order to explain the complete concept let’s take one more example.

There should be accounting entries generated for Cancellation of a credit memo. And hence Credit Memo is a Type of Account Payables invoice.

Entities à AP invoice
Event Class à Credit Memo

Event à Cancellation.

Monday, January 27, 2014

Sub-Ledger Accounting


Sub-Ledger Accounting

Sub ledger accounting traditionally had accounting rules spread across multiple Products and Sub ledger applications hence it was Difficult to keep the rules up to date and manage.
And if there used to be any requirement which requires a different Accounting treatment as per different geographies, Regulations  or entity it was extremely difficult to implement and many times the ultimate solution was to implement a customization or pass manual Adjustment entries.
The New Sub Ledger accounting feature of oracle E-business Suite R12 popularly known as SLA addresses such issues through a central accounting rule engine allowing among other things, Superior controller ship of definition of accounting rules.

SLA is a rule based accounting Engine that introduced the ability to define how transactions originating in Sub Ledgers can be Accounted. One of the significant benefits of SLA is the ability to generate multiple accounting representations (IFRS and local GAAP) for a single sub ledger transaction.

Hence in Simple words, Different from 11i where accounting Entries used to get created in respective Sub ledgers and then get transferred to GL, In R12 the Entries get created using SLA for all the Sub ledger applications and then gets transferred to GL. Hence it would be appropriate to say SLA is placed between different Sub ledgers such as AP, AR, CE, PA and General Ledger as mentioned in below. 



Sub Ledger Accounting Gives capability to Massage/ Change the accounting entries which gets generated as part of the Standard Sub Ledger application specific account so as to have the accounting entries posted to the desired accounts to address various geographies or entity specific accounting requirement




Above Example shows how the accounting String (A.B.C.D) generated by SubLedger Applications (Eg: AP, AR, CE) can be altered to A1.B1.C1.D1 to achieve specific Accounting requirement and then can be transferred to general Ledger.


Wednesday, July 25, 2012

Different Documents Used at Different Levels in Application Implementation Methodology ::

Different Documents Used at Different Levels in Application Implementation Methodology ::

1. Business Process Architecture [BP] –

This Document Addresses ::
  • Existing Business Practices
  • Catalog change practices
  • Leading practices
  • Future practices
2. Business Requirement Definition [RD]

            This phase explains about the initial baseline questionnaire and gathering of requirements

3. Business Requirement Mapping [BR]

In this phase the requirements of business are matched with the standard functionality of the oracle applications.

4. Application and Technical Architecture [TA]

 This outlines the infrastructure requirements to implement oracle applications.

5. Build and Module Design [MD]

            This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.

6. Data Conversion [CV]

            Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.

7. Documentation [DO] 
             Documentation prepared per module that includes user guides and implementation manuals.

8. Business System Testing [TE] – A process of validating the setup’s and functionality by QA(functional consultant) to certify status.

9. Performance Testing [PT] - Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc

10. Adoption and Learning [AP] – This phase explains the removal of the legacy system and oracle application roll out enterprise wide.


11. Production Migration [PM] – The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

Monday, July 23, 2012

Application Implementation Methodology

Application Implementation Methodology::


AIM consists of a project management methodology together with the underlying documentation templates that support the tasks you perform within this methodology. This combination of a methodology together with documentation templates makes AIM a powerful tool for assisting implementation participants in running and managing projects successfully.

There are 6 phases in AIM


  1. Definition ::
    1. Establish the business objectives and related Requirements,
    2. Define the Project Plan

  1. Operations Analysis :
    1. Analyze the operations and identify the fit between Organizational requirements and Standard Applications Functionality

  1. Design :
    1. Develop detailed design for the optimal Solutions to meet the future business requirements

  1. Build : (Implementation)
    1. Physical Software system Build and testing

  1. Transition:
    1. Deploying the Finished solution in to Organization

  1. Production Go live

** Each Phase has Number of tasks to be followed.


** There are more than 150 templates, which can be used through out the AIM Process.

There are two types of AIM Documentation template:
-        Project management related (Project plan, Change Orders, Quality control document. Etc.)

-        Oracle Applications Implementation related Docs (RD50, BR100, MD200 etc.)

Saturday, June 23, 2012

Security Profiles in Oracle Application R12

Security Profiles

Oracle Applications 11i had a limitation where, the Business Personnel’s responsible for a particular business function who had access to multiple organizations had to navigate to individual Organization specific responsibilities for taking action on the transactions. For example: a buyer who can create Purchase orders for multiple organizations will have to Navigate to each operating Unit specific responsibility to create or manage purchasing Documents.

R12 comes as a blessing for such user of Oracle applications where Multi Organization Access control features enabled such users to take action on documents and transactions without navigating between various organizations specific responsibilities. This feature can be implemented using Security Profiles in R12.

Security profiles is a feature in R12 which can be used for grouping the organizations logically such that a set of users can access a Set of Organizations using the responsibility which are assigned with particular Security profile.

There are two types of Security Profiles.

Security Profile: If it is required to group multiple operating units for the same business group.
Global Security Profile: If it is required to group multiple operating units for the different business group.
After the security profiles are defined it is required to run the Security List Maintenance program, before assigning the Security profile to the Responsibilities





A Security profile can be assigned to a responsibility by using the MO: Security Profile option.





If you set the MO: Security Profile option, you can also set the MO: Default Operating Unit profile option to specify a default operating unit.
It is important to note that if the MO: Security Profile option is not set for the responsibility it will behave same as R11i.

The MO: Operating Unit profile option still exists in R12 but it should only be used if Multi organization access control is not desired.

HR: Security Profile

Oracle Applications also has HR: Security Profile feature. This profile option is used for defining association between a Business group and the Organizations hierarchy. HR: Security Profile options needs to be setup before defining any new organizations or organization hierarchies under a Business group.




Friday, December 23, 2011

Setting Up Organization in Oracle Applications R12

Setting Up Organization in Oracle Applications:

An Organization represents a business unit in an Enterprise which has a business need to secure transaction data, Setups and Seed data. It can be a major division, sales office, a department, or a separate company within an enterprise. Since the transaction Information is secured at organization level for the various modules within Oracle applications, A single application responsibility can access, process, and report on data for one or more operating units that is assigned to its Security profile.

An Operating unit can be associated to a Single Legal Entity and Ledger. But multiple operating units can be Associated to a Single Legal entity and Ledger.
Organization can be classified in to a set of system-defined attributes that categorize an organization. Examples

  • ·        Business group
  • ·        operating unit
  • ·        project expenditure organization
  • ·        inventory organization
  • ·        Human resources organization

Organization in Oracle Applications is an autonomous Business Entity having business activities corresponding either of the below Modules like Receivables, Order Management, Payables, Purchasing, Projects, Inventory.


Navigation to define Organization:
HR Responsibility à Work Structure à Organizations

Organization can also be defined and viewed from the accounting Setup manager as well.
Whenever a New Organization is defined in oracle application it needs to be added appropriately in the Security profile if the Security Profile is a List of Organizations based Security profile and The Security List Maintenance programs needs to be run.

Defining an Operating Unit:

In order to use an Organization for transactions in the Oracle Applications in the Modules like Receivables, Order Management, Payables, Purchasing. It is required to define the Organization as an Operating Unit.
It is Mandatory to decide and Setup the below mentioned Oracle application multi organization entities before we setup an Operating unit.

  • ·        Business group
  • ·        Ledger
  • ·        Legal Entity

Operating unit is an Organization classification and once an organization is defined as an operating Unit the Organization Attributes need to be defined. Before setting UP operating unit below Profile options should be defined so that the Organization gets created under appropriate business group

HR: Business Group at Responsibility Level
HR: Security Profile at Responsibility Level


As mentioned above The Ledger and Legal Entity needs to defined in the organization Information. And this is how the Legal Entity and Ledger are assigned to the Operating Unit.
Also It is important to note that in Oracle Applications R12 the Legal Entity which is Attached in the Organization information screen is the Default legal Context. Transnational

Legal Entities Defined at the ledger level can be used on the basis of the Mapping Defined between the Balancing Segment and Legal Entity as per the Ledger Definition.





Tuesday, August 23, 2011

Ledger Configuration in Oracle R12 Part -3

In this Article we will look in to the Steps and necessary configurations involved in defining Ledger in Oracle R12

Setting Up Ledger:

Create Legal Entity: If it is required to assign a legal entity, It can be crated and assigned to a Ledger from accounting setup manager.

Assign the Legal Entity to Ledger

Setting Up Ledger Options:,
Before setting up Ledger options Decide up on the values that are required to be entered in the corresponding fields in the Ledger options.

Define Ledger:

While defining the ledger you may use the calendar, Chart of Accounts, Currency and Sub-Ledger Accounting method defined earlier. As part of ledger setup it is mandatory to finalize these values before defining Ledger.








Define Ledger options.
As part of the Ledger options Definition Below mentioned are the Values which needs to be defined which will control how journals and transactions are processed for that ledger hence it is very important to have the values for all the below mentioned Options Decided before setting up the Ledger on the basis of business Functional requirement:

• First Ever Opened Period
• Number of Future Enterable Periods
• Retained Earnings Account
• Sub-ledger accounting method,
• Option to track balances using a secondary segment
• Suspense Account
• Rounding Differences Tracking Account
• Intercompany Balancing option
• Journal Approval
• Journal Entry Tax
• Journal Reversal Criteria Set
• Default Period End Rate Type
• Default Period Average Rate Type
• Cumulative Translation Adjustment Account
• Journal Reconciliation
• Budgetary Control
• Reserve for Encumbrance Account
• Average Balance Processing
• Average Balance Consolidation
• Net Income Account
• Transaction Calendar









If there are legal entities that require any one of the above ledger processing options to be different, then define a separate primary ledger for each legal entity and therefore, a new accounting setup
You will not be able to use the Ledger Unless the Ledger options setup Shows as Complete in the ledger setup Screen.




Ledger Configuration in Oracle R12 Part 2

Accounting Setup Steps:

There are mainly three steps for creation of accounting Setups. Each accounting setup is a grouping of accounting-related setup components as mentioned below.

1.       Create an accounting setup structure.
a.      Create and Assign legal entities
b.      Specify the ledger attributes for the primary ledger.
c.      If Secondary Ledger setup is required, Specify the ledger attributes for secondary ledgers
d.      Assign reporting currencies.

2.       Update accounting options.
a.      Complete ledger options as per the requirement.
b.      Assign balancing segment values to legal entities and Ledger
c.      Define Subledger accounting options.
d.      Define and assign operating units to the primary ledger.
e.      Define relevant intercompany setups including Accounts and Intercompany balancing Rules.
f.       Define sequencing options.

3.       Complete the accounting setup
Review and Complete accounting setups. The status of the accounting setup should be completed before it can be used for the transactions.

Ledger Setup Prerequisites:

In Order to create a Ledger in Oracle Applications in R12, It is required to complete certain Prerequisite setups before creating Ledger.

  • ·        Chart of Accounts Setup.
  • ·        Calendar and Periods related Setup.
  • ·        Legal Entity Setup.
  • ·        Currency and Conversion Rate type Setups.
  • ·        Subledger Accounting Method Setup.
  • Define Account Code Combinations and Values that needs to be setup for Ledger Options. 

Wednesday, August 10, 2011

Ledgers in Oracle R12 Part -1

Ledger in Oracle Applications R12:

Ledger is a financial reporting entity, which represents an accounting representation for an organization that is accountable in a self-contained way. Ledger is the highest level which impacts accounting. Ledger uses below mentioned components to secure and Manage the transaction information such as Journal entries and Balances) by ledger

·        Chart of accounts
·        Functional currency
·        Accounting calendar
·        Sub-ledger accounting method.

Ledger represents the core of a Company’s financial records where every transaction flows through.  It provides balanced ledger accounting for the accounting entity and serves as a repository of financial information. Multiple Legal entities can be assigned to a Ledger. A Ledger can be associated with multiple Legal Entities and operating Units. Ledger in R12 replaces the Set of Books in 11i Version of Oracle applications.

Accounting Setup Manager:

Accounting Setup manager is a new feature in R12 which is a centralized location for setup and maintenance of common financial components within an accounting setup. The status of the accounting setup should be completed before it can be used for the transactions. Each accounting setup is a grouping of accounting-related setup components.

Below Components can be setup and Maintained using Accounting Setup Manager.
  • ·        Legal Entities Setup and Assignment to balancing segments and Ledger.
  • ·        Ledger and Ledger options Setup and Maintenance (Primary and Secondary Ledger).
  • ·        Operating Unit
  • ·        Reporting Currencies
  • ·        Intercompany balancing Rules and Intercompany Accounts
  • ·        Sequencing (Accounting and Reporting Sequence)

Saturday, July 23, 2011

HR Locations in Oracle R12

Defining Locations
Locations are the most basic Entity which is the base for setting up a business in Oracle Applications. Locations are a Shared Entity which can be shared between Oracle Inventory, Purchasing, and Human Resource Modules.

Locations are required for setting up important Entities like
  • ·        Business group
  • ·        Organization (Including all organizations.)
  • ·        Legal Entity

Oracle Applications Modules use locations for requisitions, receiving, shipping, billing, and employee assignments.

Navigation:
HRMS Responsibility à Work Structure à Locations

Locations Flagged as Global locations are available to all defined Business groups in the oracle apps instance. Locations have many to one relationship with Organizations. One Organization can be attached only one Location But one Locations can be attached to Multiple Organization.
It is important to select the options such as Ship-to Site, Bill-to Site Etc. to enable the location to be used for those transactions in future in various Modules in oracle Applications.



Thursday, June 23, 2011

Business Groups in Oracle Application R12


This Article talks about the Importance of business group in Multi organization Setups, Definition and necessary setups.

Business group:

The business group is the highest level in the organization structure which represents a consolidated enterprise, a major division, or an operation company. Oracle Applications secures human resources information, including organization definition, by business group.
It is mandatory to define at least one business group for defining Organization structure in Oracle applications.

While Implementation even the predefined business group provided by Oracle application can be used but if we intend to define a business group we also need to consider defining the mandatory HR Flexfileds which we will discuss in this article below.

Business group Can be defined using the Navigation :

HR Super user responsibility àWork Structureà Organizations.
(Organization Type: Business group)




For every business group for Organization setup Business Group profile option at the responsibility level for the new business group needs to Assigned before creating the Organizations as the Default business group is assigned on the basis of this profile

Profile option:
HR: Business Group at Responsibility Level
HR: Security Profile at Responsibility Level

Oracle Human Resources also automatically creates a security profile with the business group name when you define a new business group. Please see the Security Profiles article for further details.
Multiple ledgers can share the same business group if they share the same business group attributes, including HR flexfield structures.

Defining Mandatory HR Key Flexfields.

Here we will see the Mandatory HR Key Flexfields which are required for an Oracle Applications implementation.
These Key flexfields are required to be defined even if the HRMS module is installed in Shared mode, because these Key flexfields are required for defining the Business groups.
Below is the list of the Mandatory Key Flex fields Required.
Human Resource Application Key Flexfields
·        Human resource               -- Job flexfield
·        Human resource               -- Position flexfield
·        Human resource               -- Grade flexfield
·        Human resource               -- Competence Flexfield
Payroll Application Key FlexFields
·        Payroll   -- Cost Allocation Flexfield
·        Payroll   -- People Group Flexfield