Oracle Fusion Learning

 Oracle Fusion introduced Item class concept in Oracle inventory .Item class is like categories and it will be defined as part of Root Item class Hierarchy (Tree) structure .Primary purpose of Item class is 1.        To provide numbering for Item definition like AC 1001 ,AC 1002 2.        Item security – Item class restricts the Role/user at Inventory organization level   with specific privileges like a.        Maintain Item data (Edit/Update   Item parameters) b.       View Item Data   3.        Item templates are assigned based on item class definition. E.g Item class : Raw Materials It includes Purchased goods Template and not Finished goods template. Please find the detail description of Item class definition with screenshots In Fusion, Item classes are created at the root item class or within a parent item class, and inherit values based on selections made when defining the item class . Item class creation is connected with the following attributes groups Header

  In Oracle Fusion, Suppliers are classified as 1.      Prospective suppliers 2.  Spend Authorized suppliers   Prospective suppliers: Suppliers who are not registered vendors , but they participate in bidding process and submit the quotation for any potential contract  Spend authorized suppliers: These suppliers are registered vendors and will be created in the system as Spend authorized suppliers. These suppliers will be involved in both sourcing(RFQ and Quotation) and Procurement process(PO creation )   Prospective suppliers will be converted into Spend Authorized supplier once their quotation is shortlisted in the bidding process. There is a convert button in Prospective supplier which will do the conversion from prospective to spend authorized supplier .There will be two user roles involved pertaining to supplier conversion . 1.      Supplier Manager 2.   Supplier Administrator User with Supplier manager role, user can create the prospective supplier and can make th

In Oracle EBS , Chart of Accounts will be set it up like    General Ledger => Accounting KFF => COA structure => List of segments(Segment combination)  In a typical MNC company like GE Healthcare,COA structure will be   defined as below for two different countries in Oracle EBS 1.     GL è Accounting KFF è GE US COA structure è List of segments 2.     GL è Accounting KFF è GE UK COA structure è List of segments   In Oracle Fusion , same above scenario is handled through COA structure instance Using one global structure, we will create multiple instances to accommodate different countries on COA setup. Advantage is that Global COA structure will maintain same segment combination on all different instances and we can only change value sets on each segment at instance level to accommodate different countries implementation requirement. In Oracle EBS COA setup, COA structure definition is multi line and there is no link between structures, though these structures ar

Oracle Fusion Fundamentals   There are two main concepts, one must know before we go deep dive into Oracle apps modules. i.e   1. Multi org        2. Flex fields In this blog, Multi Org definition is explained with in depth detail. Multi Org : Oracle apps modules (Financials,SCM,HRMS and Projects) are conceptualized based on Multi org concept. In Multi org we have the following Organization definition 1. Enterprise  2. Division  3. Legal enitity 4. Business Unit 5. Inventory Org   Enterprise:  Enterprise is the HR Organization and Oracle Fusion Liecsne is procured in the name of Enetrprise. Only one Organization as Enetrprise and cannot be defined muliple.     Division:   Division is also HR orgnization and we can have mulitple Org defined as Diccisons . Like Souther Reliance Division , Northern reliance Division etc.. Main purpose for this Orgnization is for HR reporting purpose on Employee Grouping. Tjsi definition is optional and bLeaaed on requirement we cam define in Multi

  Oracle Fusion User security in comparison with Oracle EBS     I n Oracle EBS, setting up the user security is like assigning responsibity to users . E.g Responsibility : Payables Vision Operations   , Payables is the module and Vision Operations is the Operating unit. we assign this to specific users and also setup the profile option as  MO:Operating unit - Vision Operations . This combination controls the suer security at R12. In additon if we need multiple operating unit access then Please go in for  MO: Security profile option where Organization hierarchy value is set      in Oracle Fusion , User, responsibility and profile option is eliminated and instead User - roles functionality introduced . Every user , there will be a seeded role on each module and it needs to be assigned to provide access to that module .E.g user - Muthu and role for General ledger module is   General accountant .      Muthu - assign role ==> General accountant (Role)    Based on above co