Oracle Fusion Cloud R11 Overview updated from my learning

Fusion Over view 


Oracle Fusion cloud is an application works on the PAAS (Platform as a Service) Provided on the cloud database

• we define a project and enable the offering (Modules ) and assign the Tasks (Setup steps) to the users to define and complete steps
• we can monitor at each task level the task is started , progress and completed etc.
• Offering are the Module like ( OM, PO, PIM etc. )
• We have Navigator, Tasks and Dash Boards 
• FBDI (file based data integrator) template for easy migration for transaction data
• OTBI report (Oracle transnational business intelligence)
• ? indicate Help at point on the web page
• No BOM Module covered as Structure in PIM under item definition
• Resources are defined in WIP used in Work definition.
• Most of the setups tasks have a Default values which we can make use of it or define user specific.
• one more Quick or simplified setups available in one go using train stops we can define the costing related or Inventory related Required setups with no time.
• SCO : Supply chain Orchestration process
• All are Web pages and have hyper link which will open a new page
• Landing page will have Spring Board withe all the Offerings and Tasks
• On top we have Notifications, Favorites, Help, home etc.
• New concept of Social Network using which we can chat with other users for any help or clarification
• SFO : Supply chain financial Orchestration process

Integrate fulfillment services/ applications. Order Management comes integrated with the following Oracle cloud services:

• Oracle Inventory Cloud
• Oracle Cost Management Cloud
• Oracle Manufacturing Cloud
• Oracle Procurement Cloud
• Oracle Product Hub Cloud
• Oracle Financials Cloud

Oracle Configure, Price, and Quote Cloud.

Extensible Flexfield:

EFF are similar to to Descriptive Flexfield
Can add as many context-sensitive segments to the flexfield as needed. It is not dependent on the number of segments predefined and registered for the flexfield.
You can configure a one-to-many relationship between the entity and its extended attribute rows.
A product business object row can be extended to have multiple contexts.
A product business object row can have multiple occurrences of the same context.
You can configure contexts in groups so the attributes in the context always appear together in the user interface.
You can use existing hierarchical categories so that entities inherit the contexts that are configured for their parents. Contexts are reusable throughout categories

Security 

user level security similar to the CRM User definition and access in EBS

we have different roles provided to the user for performing the activity in the fusion

•       Abstract Roles: Roles associated with the user irrespective of job or job function. Example: Employee, Contingent worker, Manager 
•        Job Role: Roles associated with the job of the employee. Example: Procurement Manager, Project Administrator 
•        Duty Role: Defines the duties as a user can perform. Example: Processing Payables invoices , Posting Journals 
•        Data Role: Specific to a job with a dimension of data and augments the inherited abstract, duty, or job roles with entitlement to access specific data. Example: access as a procurement manager in a particular BU 

• 
  
• Inventory : 
•        We call calendar (EBS) as Schedule (Fusion
•       Inventory Orgs do not have any kind of accounting information captured 
•        we can define the contract manufactures as a External Inventory org and assign the Supplier for making payment to contractor
•         No costing information is defined at inventory org (Separate cost org are defined )
•         Item is not KFF it is a single segment 
•        Under the Ware house offering we have inventory , Receipt, Shipment, Counts, pick slip, Pick wave etc. 
•        We call the Delivery in the receiving process as Put away 
•        No Cost Manager 
•        Item as different status as Item Status, Life cycle Status , Approval Status etc. 
• 
  

Costing : 

Only Sub ledger accounting (SLA) is used for creating distribution and transfer to GL.
No more : Pending, standard , Average cost types as in EBS.

Cost orgs : Org in which we store the Cost information 

Cost Book : Act a container of cost accounting data, helps to provide multiple representation of Cost 

Valuation Structure : Level at which we can define the cost ( KFF)cost org
cost org. inventory org
cost org, inventory org. sub inventory
cost org, inventory org. lot
cost org, inventory org. lot. grade
cost org, inventory org. Serial

Cost Profile : include cost method, Valuation structure, Cost elements Programs we use to process the transaction from other offering to costing

•Transfer Transitions from Inventory to costing
•Transfer Transactions from Receiving to Costing
•Transfer Transactions from Payable to Costing
•Transfer Transactions from Production to costing
•Import Revenue Lines – To be run from Receivables

Order management :

No Workflows , transaction types,

Order Management – 


Cloud is an Supply Chain Management Application that improves the business processes and easy order fulfillment.
It has a predefined integration, global availability and can be centrally managed.
Order fulfillment can be monitored which increases the customer satisfaction and order profitability.
Can be used as for organization centralization and capture multiple orders from different channels.
We can manage fulfillment methods, monitor the order status and manage the exceptions
We have Sales order orchestration process which will execute the fulfillment line.

OBR - oracle Business rules used to  select appropriate process

Pretransformation Rules: 

Order Management cloud allows to write the rule to populate order attribute before transforming the source order. Use Predefined attribute value that product transformation rule already contains.

Product Transformation Rules:

Product transformation is executed using combination of Product relationships, product structure, Transactional item attributes (TIA) & Oracle Business Rules (OBR)

Different types of Product transformation rules:

Product to Product

Product to Attribute

Attribute to Product

Attribute to Attribute

Context to Product

Context to Attribute

Post transformation Rule:

Populates an order attribute after Order Management transforms the item.

Orchestration Process:

•      A Orchestration is the automated sequence of fulfillment steps for processing an order. Orchestration processes are defined to mirror the actual business processes, much like a blueprint.

•Orchestration Process Definition includes sequence of service calls, planning details, change management parameters and status conditions.

Jeopardy : 

Jeopardy indicates the severity of the delay of a task in an orchestration process. Jeopardy indicators appear in the Order Management work area, so that an order manager can quickly identify the fulfillment lines in which issues exist.

It Is based on forward and backward planning across an orchestration process, which calculates the accurate promise dates for each task. When one of these tasks is delayed, jeopardy indicates how severe the delay is, based on the jeopardy settings.


It Is calculated when planning runs. You can use it on planned dates, as well as actual dates. This means that an order manager can learn about jeopardy conditions before they actually happen, so that the order manager can provide remedies to maintain customer satisfaction.

Fusion Pricing :

Pricing profile, Pricing Segment, Pricing strategies

GOP 

(Global order promising) make uses of below setups and arrives the schedule ship dates and using the supply chain orchestration process create the supply order to fulfill demands.

includes

• Sourcing rules and assignment sets 
• ATP (Available to Promise)

• Oracle Global Order Promising (GOP), Available-To-Promise (ATP), provides an internet-based, sophisticated, and fast order promising tool that provides accurate and reliable delivery promises. 
• Oracle Global Order Promising is a comprehensive order promising solution that determines current and projected demands and supplies across a supply chain and on an extended supply chain, when a customer order can be fulfilled. 
• This functionality includes distributed global order promising and multi-level supply chain Available-To-Promise (ATP), Capable-To-Promise (CTP), and Capable-To-Deliver (CTD) capability.

• Product Management, Order Management, Global Order Promising, Supply chain Orchestration, Inventory Cloud are common in all below type:

• Back to Back fulfillment Standard Item 
• Back to Back fulfillment process Buy - additionally involve Procurement Cloud 
• Back to Back fulfillment Make - additionally involve Manufacturing Cloud
• Back to Back fulfillment Transfer
• Back to Back fulfillment On Hand Supply

Supply Chain Orchestration Business Processes Flows SCO supports the following business process flows:

• Plan-to-Produce Contract Manufacturing
• Back-to-Back Contract Manufacturing 
• Back-to-Back In-house Manufacturing 
• Back-to-Back Purchasing 
• Back-to-Back Transfer 
• Transfer Order Creation

EBS R12 and Cloud R11 Difference in Costing modules

EBS	Fusion
Inventory org is cost org	Cost Org defined and Inventory org assign to it
Costing happens at Inventory Org level	Costing happens at cost org level &  Based on level at which Valuation structure defined
Provide Accounting Information at INV org  like Material , PPV, COGS etc.	No accounting information at Inventory org only at the Cost Profile and cost books etc.
Provision to use cost method and SLA	Only SLA (Sub ledger accounting )
Cost Methods : Average, FIFO, LIFO, Standard	Cost Methods : Average, FIFO(Actual),Standard
Landed Costing as separate module	Landed  Cost as Part of Cost Management
One item in the one INV org one cost	one item in one Inv org  can have more than one Cost associated with different cost books and ledgers / with out ledger
We have limited no of Cost elements  like material, over heads, Resources , OSP etc.	We can define cost elements types, cost elements  like  Direct Material , Inbound Freight, Tax Freight Charges , Invoice Price Variance ,Tax Invoice Price Variance at Item level or cost org level

oracle fusion Product Information management PIM

Oracle Fusion PIM / Product Development

Earlier product definition and release to production is done in Agile now in fusion we can use Product development and release item for production

Definition of item  is done in item organisation

Item organisation definition task  for defining  the item master organisation.

Item class is pre requisite which is a broader classification of items

At item level:

1.  Picture of item can be captured  and stored at master and org level
2.  Lot expiration days (shelf life days) / expiry Date facility  available any once can be used
3.Item assignment is called as  Association in Fusion
4. Item structure is  nothing but Bills of Material
5. we have transnational attributes  which can be captured at the time of transactions like we can define  width , length and width for an item and capture values as the transactions
6. Item level we have  life cycle status.
7. we have ECO engineering change order  which help to monitor changes on item followed with the approvals on approval hierarchy
8. We have People tab in which we can assign user or group of user to restrict the  item attribute modification
9. In order management we have Back to Back attribute to enable if we want to use item on B2B process
10. We have EFF (Extensive Flexi Field )  to store additional user defined attributes
11.  Primary and secondary unit of Measure
12. In Order management we can have pricing defined on the Secondary UOM
13. Internal Transfer enabled can be used to do IMT ( Internal Material Transfer) for an item
14.  In product development we can define the Workflow and approvals for which approval is need to make ECO released

EBS R12 and Cloud R11 Difference in Inventory and costing modules

EBS	Fusion
Inventory as one Module	Warehouse Operation which include Inventory , Counts, Shipments, Pick slip, Pick wave & receipts
Java Form or the OAF pages	All  are Web pages  with Over view Tab having the Dash boards and Data Shown in GUI (Pie charts )
Control at the Responsibility Definition  for  Org Access	We have Role Based  Security Rules Defined and Data Roles for the User to enter DATA at Inventory org.
Item  is a KFF with segments	Item is not a part of Key Flexi Field
Master inventory Item org as item master	Master Inventory item org as Item organization
BOM as separate module  to capture  components and its quantities	PIM  as a repository stores  Structure (BOM) , Capture pictures, transactional attributes, user defined attributes etc.

oracle fusion inventory and costing concepts

Cost Organizations and Inventory Organizations

A cost organization can represent a single inventory organization, or a group of inventory organizations that roll up to a profit center business unit. You can group several inventory organizations under a cost organization for financial reporting purposes as long as they all map to a single profit center business unit. Because the inventory organizations that are assigned to a cost organization must all belong to the same business unit, it follows that they also belong to the business unit's legal entity.

The inventory organizations that are assigned to a cost organization must all belong to the same legal entity.

For each cost organization, define an item validation organization from which the processor should derive the default units of measure. You can designate one of the inventory organizations assigned to the cost organization to be the item validation organization, or you can designate the item master organization to be the item validation organization.

Cost Books

A cost book sets the framework within which accounting policies for items can be defined. You can define different cost books for each of your financial accounting, management reporting, and analysis needs. By assigning multiple cost books to a cost organization, you can calculate costs using different rules simultaneously, based on the same set of transactions.

Every cost organization must have one primary cost book that is associated with the primary ledger of the legal entity to which the cost organization belongs. You can also assign secondary ledger-based cost books for other accounting needs, as well as cost books that don't have an associated ledger, for simulation purposes. For example, you could assign a primary cost book for financial reporting, a secondary cost book for business analysis, and a third cost book to simulate results using different cost calculations.

When you assign a cost book to a cost organization, you can optionally associate it with a ledger. The cost book then inherits the currency, conversion rate, cost accounting periods, and period end validations of that ledger. If you are assigning a cost book that is not associated with a ledger, then you define these elements manually.

Prerequisites to setup cost organization 

•Legal Entity

•Business unit (profit center setting in mandatory )

•Inventory organization

•Set IDs (not required if seeded sets are used )