Release 12 Demo

8/7/2019 Release 12 Demo

1/27

Demo Release 12 Functionalities

--


2/27

Definition:-

Business Group

Legal Entity

Operating Unit


3/27

Architecture Organization Model Release 12

Business GroupThis is an Organization thatrepresents the consolidatedenterprise, a major division,

or an operation company andhas no accounting impact.The Business Group partitionsHuman Resources informationand the Purchasing Approval

Hierarchy.

Oracle Modules:

HRMS

Payroll


4/27

Legal Entity Oracle Modules:

GL

FA

A legal entity represents a legal company

for which you prepare fiscal or tax reports.

You assign tax identifiers and other legal entity

information to these types of organizations.

Future enhancements will include greater

functionality at this organization level.


Organization Definition:


5/27

Operating Unit

Oracle Modules:

PO

Payables

Payments

AR

Cash Management


Organization Definition:

The Operating Unit is an organization that uses

Oracle, Cash Management, Order Management

and Shipping Execution, Oracle Payables,

Oracle Purchasing and Oracle Receivables.

The operating unit may be a sales office, a

division or a department. The Operating Unit has

to be assigned to a Legal Entity and a Set of

Books.


6/27

What is TCA and its Background

A Trading Community is The participants in a community and their

relationship to one another

Competitor

Employee

Partner

Customer /Organization

Supplier

Competitor of Partner of

Employee of Supplier of


7/27

What is TCA and its Background TCA = Trading Community Architecture Provides a single, universal definition of trading

partners across applications and job function

TCA is an Data Model it is not a Module

TCA Data Model

HZ Schema

TCA Enabling InfrastructureCommon Party UI, DQM, D&B Integration, APIs

Sales /

ServiceMarketing

Financials

AP, AR

Financials

GL, FA, POHR

Oracle E-Business Suite Application Families*

3rd PartySystems


8/27

What is TCA and its Background

TCA (Trading Community Architecture) Party Definition

TCA Central Data Model

Supplier Representation

New Bank Model


9/27

TradingCommunityArchitecture


Payables

PayablesPurchasi

ngPurchasi

ng

GlobalTax

RecievaRecievablesbles

Governments,Geographies,Authorities, etc

PartyInformatio

n

CashManageme

ntBanks and

Branches

Suppliers

OracleOracle

ERPERP CRMCRM 3rd Party3rd Party



TCA in R12: Leveraging centralized datamodel


10/27

TCA in R12: Supplier

Representation Suppliers are organizations in TCA Supplier organization, address, contact, phone, email

etc. are all in TCA

Employees are already in TCA, Payables use the same

employee records in TCA New supplier maintenance are done using UI in TCA

components (DQM)

Terms of doing business with the supplier are

in Purchasing / Payables


11/27

TCA in R12

New Bank Account Model

Central place to define internal bankaccounts Keep track of all bank accounts in one place

Explicitly grant account access to multipleoperating units/functions and users

Multi-Org Access In the new model, bank accounts are owned by

Legal Entities with the option to grant accountuse to Operating Unit (Payables, Receivables),Legal Entity (Treasury), Business Group (Payroll)


12/27

TCA in R12: Bank Account Model

OU A

OU B

OU CBankSingle

Payment

Instruction

Invoices

Payments

SubSub

LedgerLedger

AccountiAccounti

ngng

SubSub

LedgerLedger

AccountiAccounti

ngng

New Payments Module

New Bank Module

New Bank & Credit Card Features

Pay invoices from different OUs with 1 instruction


13/27

MOAC: Multi-Org Access Control

Role based access to Operating Units

Define Security Profile

MOAC Usage


14/27

Area of Impact Single Organizations Multiple Organizations

Impact on Business Processes

Day-to-day business processese.g., Invoice creation, Payment

processing etc

Potentially executed once for all threebusiness functions combined

Executed multiple times once for eachorganization

Running Reports in Sub-ledger Potentially executed once for all three

business functions combined

Depending on security and access typically

executed multiple times once for eachorganization. Consolidated reports can be

run for those with multiple organizationalaccess

Month-end operations Done once per month in each module To be done multiple times once per

organization per month in each module.

However R12 allows users to close multipleorganizations at once in order to streamline

efficiency.

Visibility of master data e.g.

Vendors (Suppliers), Customers

etc.

Visible for all business functions within

the same organization

Only master data is shared between the

organizations. The other data needs to be

assigned to each organization e.g.: onlyVendor header level data is shared while

vendor-site level data needs to be assignedseparately in each organization. This is

handled through a centralized access

screen


15/27

Impact on Project (Implementation Effort)

Application configuration Configuration is required for oneorganization (less effort).

However, the complexity of configurationmay increase (more effort).

Configuration is required for each organization(more effort).

However, it offers more flexibility to meetrequirements of each business function.

Need for custom extensions The FAO HQ and Field share similar

business processes but their focus differs.As a result, there is a higher likelihood of

custom extensions to support thesedifferences. (more effort) This isparticularly true with respect to the FAO

HQ requirements.

Custom extensions are less likely (less effort)

Reporting Report development could be complex

particularly if the reporting requirements

between the three areas differsignificantly. There will also be an issue

to segregate the FAO HQ and Field reportdata.

Reporting will be less of a challenge with

separation by organization and will not have

the complexity of a single organization.



16/27

Testing With all of the FAOs business processessharing the same organization, the potentialfor intrusive customizations (changes toOracle code) may be required. Future

Oracle patches could increase IT effort(testing and planning). Since all of the FAOHQ business processes would be containedin one organization, only one organizationwould require testing, which could involve ashorter testing cycle.However, if the future business processesvary significantly, even though, one

organization is used, future testing

complexity is increased.

Testing effort will be higher as the testing needswill have to ensure each Field & FAO HQ are inplace.

Configuration Migration Final configuration will need to be migratedonly once per organization per applicationsenvironment setup

Configuration needs to migrated for eachorganization environment (more effort).However, configuring separate organizations isless of an effort with R12.

Training The training process and learning curve will

be similar regardless of the number oforganizations. The difference will be user

access as some users may have access tomultiple legal entities. This data restrictionmight be more of an issue with only oneorganization.

The training process and learning curve will be

similar regardless of the number oforganizations. The difference will be user

access as some users may have access tomultiple legal entities. Data restriction andsecurity is not an issue with multipleorganizations. Data segregation is a standardfeature.



17/27


IT Efforts With all of the FAO HQ & Field businessprocesses sharing the same

organization, the potential for intrusive

customizations (changes to Oracle

code) may be required. Future Oraclepatches could increase IT effort (testingand planning). This would primarily be

due to ensuring mock data segregationand to meet reporting requirements.

With custom code, there is always a

risk of invaliding areas of support fromOracle.

With Multiple organizations, intrusivecustomizations will likely not be required.

Therefore, impact to the FAOs patching

strategy and upgrades could be reduced.

Oracle Support With one organization, as mentionedabove, there is a potential for the

requirement for intrusivecustomizations (changes to Oraclecode). This could impact the

effectiveness of Oracle Support asintrusive customizations, by nature, are

not supported by Oracle.

With Multiple organizations, intrusivecustomizations will likely not be required.

In this scenario, there should be littleimpact to the effectiveness of OracleSupport.


18/27

Perform multiple tasks across operatingunits without changing responsibilities

MOAC: Multi-Org Access ControlRole based access to Operating Units

ResponsibilityResponsibility ResponsibilityResponsibility ResponsibilityResponsibility

HQ

Legal Entity Functional TasksRequisition,Purchase Orders

Receiving & DropShip

Supplier Invoices

PaymentsCustomer Data

Management

Accounting Setup

Functional TasksRequisition,

Purchase Orders

Receiving & DropShip

Supplier Invoices

PaymentsCustomer Data

Management

Accounting Setup

SingleResponsibility

Mozambique

OperatingUnit

FAO HQ

OperatingUnit

Congo

OperatingUnit


19/27

MOAC - UsageTypical Screen in daily use

Invoice Entry

Quick Invoices

PO EntryReceiving

Supplier Sites

Customer Sites

OU Specific Set Ups

OU Specific Reports


20/27

&Q U E S T I O SA N S W E R S


21/27

FAO Architecture

Components of TCATCA and its implications w.r.t

FAO

MOAC Definitions &

Implications

MOAC Demos

Oracle Architecture / TCA /

MOAC


22/27

Buyers Workbench

Personalization of Buyers

Workbench

PO Types

Line Types

PO Requisitions

Standard POs, ContractAgreements,

Global POs

Service Orders, Goods

Purchasing Part 1


23/27

PO on the Field

Receiving Pay on Receipt

6 Different Scenarios

iProcurement

Purchasing - Part 2


24/27

Quick Invoices

Invoice Import Centralized Shared Services

Invoice Workbench

Payables


25/27


26/27

Organizations

(Organization)

AR(Customer)

John, XYZ Inc fao.org

Party:ABC Co.

Party:John, XYZ

Inc.

Old Model

TCA Model

AP/PO(Supplier)

John, XYZ Inc

Customerof

Supplierof *


27/27

TCA Data Model: Visualization

PARTY

SITE

PARTY

SITE

PARTY

SITE

Bill to

Ship to

Division Of

Bill to

Ship to

Bill to

Ship to

Account Account Account

Bill to, Ship to Bill to, Ship to Bill to, Ship to

Acct

Site

Acct

Site

Acct

Site

Release 12 Demo

Documents

Transcript of Release 12 Demo