Multi Org. Fundamentals

Fundamentals of Multi-Org
Overview
Copyright Oracle Corporation, 2002. All rights reserved.
Fundamentals of Multi-Org 2!2"#!$$.doc
%ffective 0&'0('0 )age & of *ev &
System References
Examples: (Please delete the red text examples once you have added your information)
Product Name > Window / Form Name
racle Wor! in Process > "iscrete #o$s
racle rder %ana&ement > 'ales rders
racle (nventory > )ransactions
Distribution
#o$ )itle
*
Ownership
)he #o$ )itle +list,-our.ompany/com0'u$1ect2E"3xxxxx4 is responsi$le for ensurin& that this
document is necessary and that it reflects actual practice/
%ffective 0&'0('0 )age 2 of *ev &
%ffective 0&'0('0 )age # of *ev &
O+,ectives
Objectives
After completing this module you should be able to do
the following!
- "#plain what Multi-Org is
- "#plain the Multi-Org entities
- "#plain how data is secured
- "#plain cross organi$ational reporting
- %dentify &ey implementation considerations
%ffective 0&'0('0 )age of *ev &
Agenda
Agenda
- 'nderstand what is meant by Multi-Org
- 'nderstand the types of organi$ations supported
in the Multi-Org model
- 'nderstand organi$ational models
- 'nderstand how Multi-Org secures data
- 'nderstand reporting across entities
- 'nderstand &ey implementation considerations
%ffective 0&'0('0 )age . of *ev &
/hat 0s Multi-Org1
(hat %s Multi-Org)
- Applications and database enhancement
- Allows you to consolidate your operations under
one installation of Oracle Applications on a single
global instance
- Allows you to &eep transaction data secure by line
of business
(hat %s Multi-Org)
%ulti5r& is a server5side (applications and data$ase) enhancement that ena$les multiple
$usiness units in an enterprise to use a sin&le installation of racle 6pplications products while
!eepin& transaction data separate and secure/ )he %ulti5r& enhancement uses native data$ase
views to $uild a security layer on top of a sin&le installation of racle 6pplications/ (n racle
6pplications 7elease 88i9 the followin& products support %ulti5r& capa$ilities:
: .ash %ana&ement
: rder %ana&ement9 'hippin& Execution and 7elease %ana&ement
: Paya$les
: Property %ana&er
: Pro1ects
: Purchasin&
: 7eceiva$les
: 'ales .ompensation
: 'ales and %ar!etin&
: 'ervice
%ffective 0&'0('0 )age $ of *ev &
2asic 2usiness 3eeds
- Support for multiple business units even if they
use a different set of boo&s
- Secure access to data on a single instance by line
of business
- Define different organi$ational models
*asic *usiness +eeds
*asic *usiness +eeds
)he %ulti5r& enhancement to racle 6pplications provides features necessary to satisfy the
followin& $asic $usiness needs/ -ou should $e a$le to:
: 3se a sin&le installation of any racle 6pplications product to support any num$er of
$usiness units9 even if those $usiness units use different sets of $oo!s/
: 'upport any num$er of $usiness units within a sin&le installation of racle 6pplications/
: 'ecure access to data so that users can access only information that is relevant to them/
%ffective 0&'0('0 )age " of *ev &
2asic 2usiness 3eeds 4Cont.5
- Sell and ship from different legal entities
- ,rocure and receive from different legal entities
- ,roduce reports across entities or within a single
entity
*asic *usiness +eeds -.ont/0
*asic *usiness +eeds -.ont/0
)he %ulti5r& enhancement to racle 6pplications provides features necessary to satisfy the
followin& $asic $usiness needs/ -ou should $e a$le to:
: Procure products from an operatin& unit that uses one set of $oo!9 $ut receive them from
another operatin& unit usin& a different set of $oo!s/
: 'ell products from an operatin& unit that uses one set of $oo!s9 $ut ship them from
another operatin& unit usin& a different set of $oo!s9 automatically recordin& the
appropriate intercompany sales $y postin& intercompany accounts paya$le and accounts
receiva$le invoices/
: 7eport at any level of the or&ani;ational structure/
%ffective 0&'0('0 )age ( of *ev &
Agenda
Agenda
%ffective 0&'0('0 )age ! of *ev &
Organi6ation Model
12 FA
A, ,O
AR OM 3
%+4 MF1
Ship
*alancing
"ntity5Funds
6R
%nventory
Organi$ation
Operating 'nit
2egal "ntity
Set of *oo&s
*usiness 1roup
*al Seg 7
*al Seg 8
Fle#field
Security Rule
Organi$ation Model
Organi$ation Model
)he %ulti5r& model provides a hierarchy that dictates how transactions flow throu&h different
$usiness units and how those $usiness units interact/ -ou define the or&ani;ations and the
relationships $etween them/ (n the dia&ram a$ove9 note the different shapes used for each
or&ani;ation type/ )he shapes are helpful when drawin& multiple or&ani;ation dia&rams/
%ffective 0&'0('0 )age &0 of *ev &
2usiness 7roup
*usiness 1roup
6R *usiness 1roup
*usiness 1roup
)his is an r&ani;ation that represents the consolidated enterprise9 a ma1or division9 or an
operation company and has no accountin& impact/ )he <usiness =roup partitions >uman
7esources information and the Purchasin& 6pproval >ierarchy/ (f you re?uest a list of
employees (in any module) you will see only those employees in the <usiness =roup of which
your peratin& 3nit is a part/ %ultiple @e&al Entities can relate to a sin&le <usiness =roup/
-ou must have at least one <usiness =roup/ For a new installation9 racle 6pplications
provides a default $usiness &roup9 'etup <usiness =roup/ -ou can define additional $usiness
&roups as re?uired for your enterprise/
%ffective 0&'0('0 )age && of *ev &
8et of 2oo9s
Set of *oo&s
12 FA
6R
Set of *oo&s
*usiness 1roup
Set of *oo&s
6 set of $oo!s ('<) is a financial reportin& entity that shares the three .s: a particular chart
of accounts (accountin& flexfield structure)9 functional currency9 and financial accountin&
calendar/ )he '< concept is similar in a %ulti5r& environment/ =eneral @ed&er secures
transaction information (1ournal entries9 $alances) $y set of $oo!s/ When you use =eneral
@ed&er9 you choose a responsi$ility that specifies a set of $oo!s/ -ou then see information only
for that set of $oo!s/
-ou create sets of $oo!s usin& the 'et of <oo!s window in =eneral @ed&er/ -ou define all
other types of or&ani;ations usin& the r&ani;ations window/
%ffective 0&'0('0 )age &2 of *ev &
:egal %ntity
2egal "ntity
12 FA
6R
2egal "ntity
Set of *oo&s
*usiness 1roup
2egal "ntity
6 le&al entity represents a le&al company for which you prepare fiscal or tax reports/ -ou
assi&n tax identifiers and other le&al entity information to these types of or&ani;ations/ Future
enhancements will include &reater functionality at this or&ani;ation level/
%ffective 0&'0('0 )age &# of *ev &
Operating ;nit
Operating 'nit
12 FA
A, ,O
AR OM 3
6R
Operating 'nit
2egal "ntity
Set of *oo&s
*usiness 1roup
Operating 'nit
6n operatin& unit represents an or&ani;ation that uses any racle su$led&er application9 for
example9 rder %ana&ement9 Paya$les/ (t may $e a sales office9 a division9 or a department/
6n operatin& unit is associated with a le&al entity/ (nformation is secured $y operatin& unit for
these applications/ Each user sees information only for their operatin& unit/ 7esponsi$ilities
are lin!ed to a specific operatin& unit $y the %: peratin& 3nit profile option/
2alancing %ntity
*alancing "ntity
12 FA
A, ,O
AR OM 3
6R
Operating 'nit
2egal "ntity
Set of *oo&s
*usiness 1roup
*al Seg 7
*al Seg 8
Fle#field
Security Rule
*alancing
"ntity5Funds
*alancing "ntity
)his is an entity for which you prepare a $alance sheet9 represented as a $alancin& se&ment
value in the 6ccountin& Flexfield structure/ )here can $e multiple $alancin& entities within the
same operatin& unit structure and each of these must $alance within itself/ 6ll re?uired inter5
company entries will $e automatically created within the 'et of <oo!s to ensure companies can
never $e out of $alance/ 6 $alancin& se&ment could $e a company or a division9 for example/
(t is important to !eep in mind that a le&al entity may $e comprised of one or more than one
$alancin& se&ments/ For example9 you may have multiple companies defined in your chart of
accounts that roll up to a sin&le le&al entity for reportin& purposes/ 6lternatively9 each
company you define in your chart of accounts may have multiple divisions for which you
produce $alance sheets/ (n that case9 each company in the chart of accounts will most li!ely $e
set up as a le&al entity and each division will most li!ely $e set up as an operatin& unit/ racle
does not automatically secure $alancin& se&ment values within your chart of accounts with
specific le&al entities or operatin& unit/ -ou can create security rules to do this/ For example9
you may want the Paya$les team to only $e a$le to enter invoices for a specific division
associated with a particular operatin& unit/ (f there are no security rules defined9 they will $e
a$le to access all divisions re&ardless of the operatin& unit they are associated with/ )he
solution is to create a security rule that allows access to only the divisions that roll up into their
%ffective 0&'0('0 )age &. of *ev &
operatin& unit/ )he security rule (li!e the operatin& unit) is then associated with their
responsi$ility/
%ffective 0&'0('0 )age &$ of *ev &
2alancing %ntity %<amples
*alancing "ntity "#amples
.7
2"7
.8
89 79
2O* 7
2"7
2O* 8
79 :9 89
7
8
:
Div 7
2"7
Div 8
79
79
:9
89
*alancing
segment
values
*alancing "ntity "#amples
6 $alancin& se&ment may $e associated with a sin&le operatin& unit $ut this is not always the
case/ (t is important to !eep in mind that a le&al entity may $e comprised of one or more than
one $alancin& se&ments/ For example9 you may have multiple companies defined in your chart
of accounts that roll up to a sin&le le&al entity for reportin& purposes/ 6lternatively9 each
company you define in your chart of accounts may have multiple divisions for which you
produce $alance sheets/ (n that case9 each company in the chart of accounts will most li!ely $e
set up as a le&al entity and each division will most li!ely $e set up as operatin& units/
For each of the three examples9 assume there is one =@ set of $oo!s9 the $alancin& se&ment
value is the company se&ment and there are three companies defined (8A9 BA and CA)/ 6lso9
!eep in mind that operatin& units are associated with responsi$ilities/ )hat is9 each
responsi$ility is associated with one and only one operatin& unit/
Example 8: .ompany is a le&al entity/ <alancin& se&ment value (company 8A) is a le&al entity
in and of itself/ )wo divisions have $een defined as operatin& units and roll up to it/ 6
flexfield security rule that allows access to company 8A has $een created and associated with
the responsi$ility that points to the "iv8 and "ivB operatin& units/ When userDs lo& in with
either responsi$ility9 they will only $e a$le to enter transactions associated with company 8A
(and not BA and CA)/
%ffective 0&'0('0 )age &" of *ev &
Example B: .ompany is an operatin& unit/ <alancin& se&ments 8A and BA are operatin& units
in and of themselves/ <oth roll up to the same le&al entity/ )wo different security rules will $e
defined/ 6ll responsi$ilities associated with operatin& unit .8 will have a security rule that
allows them to enter transactions associated with company 8A/ 6ll responsi$ilities associated
with operatin& unit .B will have a different security rule that allows them to enter transactions
associated with company BA/
Example C: .ompany is part of a line of $usiness/ <alancin& se&ment 8A is associated with
one line of $usiness and $alancin& se&ment BA and CA are associated with a separate line of
$usiness/ 6s in the prior examples9 security rules will $e created to allow appropriate access to
data/
%ffective 0&'0('0 )age &( of *ev &
0nventory Organi6ation
%nventory Organi$ation
12 FA
A, ,O
AR OM 3
%+4 MF1
Ship
6R
%nventory
Organi$ation
Operating 'nit
2egal "ntity
Set of *oo&s
*usiness 1roup
*al Seg 7
*al Seg 8
Fle#field
Security Rule
*alancing
"ntity5Funds
%nventory Organi$ation
6n inventory or&ani;ation represents an or&ani;ation for which you trac! inventory
transactions and $alances9 and manufactures or distri$utes products/ Examples include
manufacturin& plants9 warehouses9 distri$ution centers9 and sales offices/ )he followin&
products and functions secure information $y inventory or&ani;ation: (nventory9 <ills of
%aterial9 En&ineerin&9 Wor! in Process9 %aster 'chedulin&/%7P9 .apacity9 and purchasin&
receivin& functions/ )o run any of these products or functions9 you must choose an
or&ani;ation that is classified as an inventory or&ani;ation/
With the %ulti5r& enhancement9 multiple sets of $oo!s can use the same E&lo$alF item master
or&ani;ation9 since the item master or&ani;ation is used for item definition and not item
accountin& information/ 6ll accountin& related attri$utes in the (tem %aster are controlled at
the item or or&ani;ation level/
%ffective 0&'0('0 )age &! of *ev &
8ample Organi6ation 8tructure
2"
2"
2"
2"
Set of *oo&s
%O
%O
O'
O'
O'
O'
%O
%O
%O
%O
O'
O'
%O
%O
%O
%O
%O
%O
M%O
M%O
Sample Organi$ation Structure
Sample Organi$ation Structure
With racle 6pplications accountin&9 distri$ution9 and materials mana&ement functions9 you
define the relationships $etween inventory or&ani;ations9 operatin& units9 le&al entities9 and
sets of $oo!s to create a multilevel company structure/
Legal Entities Post to a Set of Books
Each or&ani;ation classified as a @e&al Entity must specify a 'et of <oo!s to post accountin&
transactions/ 6 @e&al Entity can point to one and only one 'et of <oo!s/
Operating Units are Part of a Legal Entity
Each or&ani;ation that you classify as an peratin& 3nit must reference a le&al entity/ 6n
peratin& 3nit can point to one and only one @e&al Entity/
Inventory Organizations are Part of an Operating Unit
Each or&ani;ation that you classify as an (nventory r&ani;ation must reference an operatin&
unit/ 6n (nventory r&ani;ation points to one and only one peratin& 3nit9 $ut throu&h
standard functionality can $e referenced $y any peratin& 3nit havin& the same 'et of <oo!s
as the attached peratin& 3nit/ (tems are defined in the master inventory or&ani;ation (master
parts list) and added to the appropriate child inventory or&ani;ations/ 6ny inventory
transactions are then secured $y operatin& unit/
Agenda
Agenda
%ffective 0&'0('0 )age 2& of *ev &
8ecurity Model
'sers
'sers
Responsibilities
Responsibilities
Operating
'nit
Operating
'nit
Select
;ied
to an
Security Model
;he responsibility is &ey to multi-
org security and reporting
- Determines operating unit
- Determines reporting ability
Security Model
)he &raphic a$ove shows how security is defined within racle 6pplications/ 6s shown in the
dia&ram9 users have responsi$ilities9 which are attached to operatin& units (or inventory
or&ani;ations)/
=ata 8ecurity +y Application
Data Security by Application
Application ,artitioned *y Secure
12 12 Set of *oo&s <es
FA .orp *oo& <es
6R *usiness 1roup <es
OM AR A, ,O
." ,A AS S.
Operating 'nit <es
%+4 MF1 %nventory Organi$ation <es
Data Security by Application
"ata is partitioned (secured) in racle 6pplications in many different ways/
: =eneral @ed&er and Fixed 6ssets are partitioned $y =@ 'et of <oo!s/ (n addition9
hierarchies of asset $oo!s may also $e set up within assets that can effectively secure
assets $y asset $oo!/
: >uman 7esources is partitioned $y <usiness =roup/
: rder %ana&ement9 6ccounts 7eceiva$le9 6ccounts Paya$le9 Purchasin&9 .ash
%ana&ement9 Pro1ects9 'ervice9 'ales .ompensation9 and 'ales and %ar!etin& are
partitioned $y peratin& 3nit/
: %anufacturin& applications are partitioned $y (nventory r&ani;ation/
%ffective 0&'0('0 )age 2# of *ev &
7lo+al *egistries
Singapore
Operations
'S
+ew <or&
Supplier A*.
.orporation
Address 7!
+ew <or& +<
Address 8!
Orlando F2
Address :!
1reen *ay (%
Address 7!
Austin ;=
Address 8!
+ew <or& +<
- +ote the separation of supplier sites by O'
1lobal Registries
Distribution
S+1
1lobal Registries
For the &lo$al re&istries of $oth customers and suppliers a EheaderF level of information is
stored in an unpartitioned ta$le for all entities within an instance/ )his allows for custom
reports to consolidate information at either the 'et of <oo!s or @e&al Entity levels/
)axpayer ("9 Federal and 'tate reporta$le options are still at the customer or supplier level/ (f
a &lo$al customer or supplier has su$sidiaries in multiple countries9 define a separate customer
or supplier for each country/
(n the a$ove example9 the supplier 9 6<. .orporation9 is shared across the two peratin&
3nits/ Each peratin& 3nit has its own &roupin&s of address information/ (f two peratin&
3nits share the same address for a supplier9 they must currently enter the information
separately/
Refer to 1uided Demonstration - "nter a .ustomer and Address -Re>uired0
?2A*7@"*<A
Refer to 1uided Demonstration - "nter a ;ransaction -Re>uired0 ?2A*7@".<A
Refer to 1uided Demonstration - Switch Responsibilities and +ote Secured Data
-Re>uired0 ?2A*7@"D<A
Refer to ,ractice - 'nderstand how Multi-Org Secures Application Data -Re>uired0
?2A*7A97<A
%ffective 0&'0('0 )age 2. of *ev &
Agenda
Agenda
%ffective 0&'0('0 )age 2$ of *ev &
Cross Organi6ation *eporting
.ross Organi$ation Reporting
Report at multiple levels
- Set of *oo&s
- 2egal "ntity
- Operating 'nit
Security ,rofile
- MO! ;op Reporting 2evel
Report ,arameters
- Reporting 2evel
- Reporting .onte#t
.ross Organi$ation Reporting
)he %: )op 7eportin& @evel profile option can $e set to control the level of reportin& access/
: 7eportin& @evel: 3sers can choose at which level they want to report/ )he valid options
are 'et of <oo!s9 @e&al Entity9 and peratin& 3nit/
: 7eportin& .ontext: 3sers can choose an entity within the 7eportin& @evel they have
selected/ Galid options are 'et of <oo!s names9 @e&al Entity names9 or peratin& 3nit
names/ Galid options are restricted $ased on the %: )op 7eportin& @evel profile option/
Note that only select reports for each su$led&er are ena$led for cross or&ani;ation reportin&/
=eneral @ed&er F'=s (financial statements) are not affected $y the settin& of this profile
option/
%ffective 0&'0('0 )age 2" of *ev &
Organi6ation *eporting Options 8et of 2oo9s
Organi$ation Reporting Options
Set of *oo&s
- MO! ;op Reporting
2evel set to Set of
*oo&s
- Reporting 2evel
parameter set to
Set of *oo&s
- Reporting .onte#t
parameter set to
SO*7
- .onnected as O'7
responsibility
-shown by arrow0
O'7
Op 'nit
2"7 2egal
"ntity
O'8
Op 'nit
O':
Op 'nit
2"8 2egal
"ntity
SO*7 Set of
*oo&s
Set of *oo&s
(f the %: )op 7eportin& @evel profile option is set to 'et of <oo!s9 you can run your reports
at set of $oo!s level9 le&al entity level9 or operatin& unit level/ <ecause the %: )op 7eportin&
@evel is set to @e&al Entity for the 38 responsi$ility9 users will $e only a$le to select a
reportin& level of 'et of <oo!s9 @e&al Entity or peratin& 3nit/ (n this example9 the user will
$e a$le to see a consolidated su$led&er report of all operatin& unit activity that rolls up to
'<8
%ffective 0&'0('0 )age 2( of *ev &
Organi6ation *eporting Options :egal %ntity
2egal "ntity
- MO! ;op Reporting
2evel set to 2egal
"ntity
- Reporting 2evel
parameter set to
2egal "ntity
- Reporting .onte#t
parameter set to
2"8
- .onnected as O'7
responsibility
-shown by arrow0
O'7
Op 'nit
2"7 2egal
"ntity
O'8
Op 'nit
O':
Op 'nit
2"8 2egal
"ntity
SO*7 Set of
*oo&s
2egal "ntity
(f the %: )op 7eportin& @evel profile option is set to @e&al Entity9 you can run your reports
at the le&al entity level or operatin& unit level/ <ecause the %: )op 7eportin& @evel is set to
@e&al Entity for the 38 responsi$ility9 users will $e only a$le to select a reportin& level of
@e&al Entity or peratin& 3nit/ (n this example9 the user will $e a$le to see a consolidated
su$led&er report of all operatin& unit activity that rolls up to @EB/
%ffective 0&'0('0 )age 2! of *ev &
Organi6ation *eporting Options Operating ;nit
Operating 'nit
- MO! ;op Reporting
2evel set to
Operating 'nit
- Reporting 2evel
parameter set to
Operating 'nit
- Reporting .onte#t
parameter set to
O':
- Run report as O':
responsibility
-shown by arrow0
O'7
Op 'nit
2"7 2egal
"ntity
O'8
Op 'nit
O':
Op 'nit
2"8 2egal
"ntity
SO*7 Set of
*oo&s
Operating 'nit
(f the %: )op 7eportin& @evel profile option is set to peratin& 3nit9 you can run your
reports at the operatin& unit level only/ -ou are only allowed to view data in the operatin& unit
assi&ned to your responsi$ility/ (n this example9 the user will $e a$le to see a consolidated
su$led&er report of all operatin& unit activity for 3C/
%ffective 0&'0('0 )age #0 of *ev &
Cross Organi6ation *eporting >ey 2enefits
.ross Organi$ation Reporting Bey
*enefits
- Ability to report across operating units for many
reports
- Simple reporting security setup
- Financial reporting across business groups
- Multi-Org reporting A,% for custom reports
%ffective 0&'0('0 )age #& of *ev &
Agenda
Agenda
%ffective 0&'0('0 )age #2 of *ev &
2asic 8teps to %na+le Multi-Org
*asic Steps to "nable Multi-Org
- Define organi$ation structure
- .onvert to Multi-Org
- ,erform setups uni>ue to each operating unit -ie/
Financials options customer address setup
supplier site setup ban& accounts0
%ffective 0&'0('0 )age ## of *ev &
=efine the Organi6ation 8tructure
'S
'S
'S
'S
.hicago
.hicago
Capan
Capan
Capan
Capan
.orporate
.orporate
.anada
.anada
.anada
.anada
"ast
"ast
;o&ara
%slands
;o&ara
%slands
%nventory
.algary
Manufacturing
Duebec
Manufacturing
Montreal
%nventory
(arehouse
(est
(est
Define the Organi$ation Structure
Define the Organi$ation Structure
Plan and define the entities in your or&ani;ational structure/
6 successful implementation of %ultiple r&ani;ation 'upport in racle 6pplications
primarily depends on correctly definin& your or&ani;ation structure in the hierarchy used $y
racle 6pplications/ 6 careful analysis and desi&n of a companyDs or&ani;ation structure is
critical for future success/
)he followin& points descri$e how the %ulti5r& model relates or&ani;ations:
: 6 <usiness =roup is the hi&hest level of the structure and has no accountin& impact/ )he
<usiness =roup determines which employees will $e availa$le to 'ets of <oo!s and
peratin& 3nits related to that <usiness =roup/
: 'et of <oo!s is the hi&hest level which impacts the accountin& side of $usiness/
: 'et of <oo!s is associated with a sin&le <usiness =roup9 multiple 'ets of <oo!s may $e
associated with a sin&le <usiness =roup/
: Each 'et of <oo!s may have a different chart of accounts structure9 calendar9 or
functional currency/
: Each @e&al Entity is associated with a sin&le 'et of <oo!s9 multiple @e&al Entities may
$e associated with a sin&le 'et of <oo!s/
: Each peratin& 3nit is associated with a sin&le @e&al Entity9 multiple peratin& 3nits
may $e associated with a sin&le @e&al Entity/
: 6n (nventory r&ani;ation may $e associated with any peratin& 3nit within the same
'et of <oo!s/
%ffective 0&'0('0 )age #. of *ev &
Convert to Multi-Org
.onvert to Multi-Org
- Run ADADM%+ to convert to Multi-Org
- Run Seed Data Replication for one or more
operating units
.onvert to Multi-Org
6fter definin& at least one operatin& unit9 use 6"6"%(N to convert to %ulti5r&/ )his step
only needs to $e perform one time/ 6fter 6"6"%(N is run9 the 'eed "ata 7eplication
pro&ram copies the applica$le setup data delivered with racle 6pplications for each defined
operatin& unit/ (f you add additional operatin& units9 you can run the 'ee "ata 7eplication
pro&ram manually at any time/ Note that seed data is only data that comes with the data$ase
and does not include any operatin& unit specific setups you may perform/
Run ADADMIN to onvert to Multiple Org
: When you select the adadmin option9 .onvert to %ultiple r&ani;ation architecture9 the
%ulti5r& switch is automatically turned onH a fla& called multiIor&Ifla&9 is set to -/ )he
seed data replication pro&ram is then executed and processes accordin& to the value of the
multiIor&Ifla&/
Run See! Data Repli"ation
'eed data is replicated under the followin& circumstances:
: 'u$mit the 7eplicate 'eed "ata concurrent re?uest usin& the 'ystem 6dministrator
responsi$ility/
)he seed data replication pro&ram wor!s in two modes:
%ffective 0&'0('0 )age #$ of *ev &
: 'in&le or&ani;ation: )his mode applies when the seed data replication pro&ram is
executed within the context of a particular operatin& unit (or r&I(")/
: 6ll or&ani;ations: )his mode applies when the seed data replication pro&ram is executed
without an operatin& unit context/
)he followin& steps are re?uired to add new operatin& units to your r&ani;ational 'tructure:
: 7evise the r&ani;ation 'tructure
: "efine 'ets of <oo!s (optional)
: "efine r&ani;ations and 7elationships
: "efine 7esponsi$ilities
: 'et Profile ptions for each 7esponsi$ility
: "efine (nventory r&ani;ation 'ecurity (optional)
: (mplement the 6pplication products
: 'ecure <alancin& 'e&ment Galues (optional)
: 7un the 'etup Galidation 7eport (recommended)
: (mplement "ocument 'e?uencin& (optional)
: "efine (ntercompany 7elations (optional)
%ffective 0&'0('0 )age #" of *ev &
)erform 8etups ;ni?ue to %ach Operating ;nit
,erform Setups 'ni>ue to "ach Operating
'nit
Many setups must be repeated for each operating unit/
For e#ample!
- Supplier sites
- .ustomer addresses
- System options -System Financial ,urchasing
,ayables etc/0
- ,ayment terms
- ;a# names
- ,rice lists discounts and >uantity price brea&s
,erform setups uni>ue to each operating unit
%any setups have to $e repeated for each operatin& unit you define/ .hec! the appropriate
userDs &uide to determine which setups must $e repeated and maintained per operatin& unit/
%ffective 0&'0('0 )age #( of *ev &
Adding to the Organi6ation 8tructure
(est Ops
-O'0
,lant 7
-%O0
(id .o/
-SO*0
,lant 7
-%O0
(id .o/
-SO*0
"astOps
-O'0
,lant 8
-%O0
'S 7
-2"0
'S 8
-2"0
(estOps
-O'0
'S 7
-2"0
Adding to the Organi$ation Structure
Original Add +ew
Adding to the Organi$ation Structure
)he %ulti5r& enhancement allows you to add or&ani;ations at any time/ Enterprises with
su$stantial ac?uisition and divestiture activities9 as well as $usinesses prone to re5
or&ani;ations9 are a$le to define new $usiness units and disa$le old $usiness units as re?uired/
ne approach for dynamic $usinesses that have le&al entities and operatin& units continually
movin& around within the or&ani;ational structure is to define new $usiness or&ani;ations as
re?uired9 while leavin& the old structure and data untouched/ With this approach9 it is easy to
!eep day5to5day $usiness transactions recorded/ (f addin& to9 or chan&in&9 the or&ani;ation
structure9 your setup should include notifyin& your data$ase administrator so that the proper
technical updates can $e applied/
)o add additional operatin& units:
: .reate the operatin& unit
: 7un the 7eplicate 'eed "ata concurrent re?uest
: .reate new responsi$ilities as necessary and set the %: peratin& 3nit profile option/
%ffective 0&'0('0 )age #! of *ev &
Organi6ation 3aming Considerations
Organi$ation +aming .onsiderations
Organi$ation +aming .onsideration
%ulti5r& namin& conventions should $e used to identify the racle r&ani;ations
.lassification (for example9 'et of <oo!s9 peratin& 3nit9 (nventory r&ani;ation) and itDs
uni?ue characteristics li!e country or currency9 location name9 and usa&e/
)he followin& are &eneral &uidelines for creatin& r&ani;ation Names:
'ets of <oo!s where:
: '<IH is an operational $oo! that o$tains 1ournal entries directly from a su$led&er
system (for example9 accounts paya$le9 inventory)/
: .<IH is a consolidation set of $oo!s/
: 7<IH is a reportin& set of $oo!s when usin& the %ultiple 7eportin& .urrency (%7.)
feature/
: <usiness =roup: <=I
: >uman 7esources r&ani;ation: >7I
: @e&al Entity: @EI
: peratin& 3nit: 3I
(nventory r&ani;ations where:
: (IH is an (nventory r&ani;ation intended to $e a su$led&er in the racle applications or
a plannin& entity/ )his or&ani;ation will contain either inventory transactions or %aster
"emand 'chedule entries9 or $oth/
: =%I H is the =lo$al (tem %aster/ (f more are than one (tem %aster is used (which is not
advised) then follow with a currency desi&nation (for example9 3'")/
Organi6ation 3aming Considerations 4Cont.5
Organi$ation +aming .onsiderations
-.ont/0
Organi$ation +aming .onsiderations -continued0
: GIH is an (nventory r&ani;ation used only for validation purposes (for example9 for
maintainin& G6) rates $y item) and is not an (nventory su$led&er/ (t will never contain
inventory transactions/
: PIH used for plannin& purposes only with no transactions/ For example9 a "7P
schedule9 with plannin& processes9 and related setups for particular product lines
crossin& many plants and distri$ution centers9 could $e esta$lished and controlled from
this r&ani;ation/
.ountry codes9 @ocations9 <usiness Names9 Functions and (corporate) Proper Names are used
in the r&ani;ation namin& conventions to distin&uish the actual site location and country
ownership9 for example:
: .ountry .odesH are a$$reviations used to identify the r&ani;ationDs country of
re&istration and residence/ )hey are usually three characters in len&th followed $y a
se?uentially num$ered di&it for the country9 for example9 3'689 3'6B/
: @ocationsH are the .ity and 'tate or Province address of the r&ani;ation/ )hey are
delineated $y an EIF $etween the .ity and 'tate and sometimes a$$reviated to fit into the
CA character su&&ested Name len&th9 for example9 "6@@6'I)J)/
Example
: '<I3'68I6<.H 3I3'68I%(@W63KEEI6<..7P
8ummary
Summary
%n this lesson you should have learned how to!
- "#plain what Multi-Org is
- "#plain the Multi-Org entities
- "#plain how data is secured
- "#plain cross organi$ational reporting
- %dentify &ey implementation considerations
%ffective 0&'0('0 )age of *ev &

Multi Org. Fundamentals

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Multi Org. Fundamentals

Cargado por

Copyright:

Formatos disponibles

Fundamentals of Multi-Org

También podría gustarte