Beruflich Dokumente
Kultur Dokumente
R12
Architecture:
Changes
in
R12:
APPMGR
Top
Details
OLD
NEW
APPL_TOP
$HOME/<SID>appl
$HOME/apps/apps_st/appl
COMMON_TOP
$HOME/<SID>comn
$HOME/apps/apps_st/comn
ORACLE_HOME
$HOME/<SID>ora/8.0.6
$HOME/apps/tech_st/10.1.2
IAS_ORACLE_HOME
$HOME/<SID>ora/iAS
$HOME/apps/tech_st/10.1.3
ORACLE
Top
Details
OLD
NEW
ORACLE_HOME
$HOME/<SID>db/10.2.0
$HOME/db/tech_st/10.2.0
ORADATA
$HOME/<SID>data
$HOME/db/apps_st/data
INST_TOP
N/A
NEW
$HOME/inst/apps/<context_name>
Example:
Types
of
Organizations:
Business
Group:
The
business
group
represents
the
highest
level
in
the
organization
structure,
such
as
the
consolidated
enterprise,
a
major
division,
or
an
operation
company.
The
business
group
secures
human
resources
information.
For
example,
when
you
request
a
list
of
employees,
you
see
all
employees
assigned
to
the
business
group
of
which
your
organization
is
a
part.
Legal
Entity:
A
legal
company
for
which
you
prepare
fiscal
or
tax
reports.
You
assign
tax
identifiers
and
other
legal
entity
information
to
this
type
of
organization.
Operating
Unit:
An
organization
that
uses
Oracle
Cash
Management,
Order
Management
and
Shipping
Execution,
Oracle
Payables,
Oracle
Purchasing,
and
Oracle
Receivables.
It
may
be
a
sales
office,
a
division,
or
a
department.
An
operating
unit
is
associated
with
a
legal
entity.
Information
is
secured
by
operating
unit
for
these
applications.
Each
user
sees
information
only
for
their
operating
unit.
To
run
any
of
these
applications,
you
choose
a
responsibility
associated
with
an
organization
classified
as
an
operating
unit.
Inventory
Organization:
An
organization
for
which
you
track
inventory
transactions
and
balances,
and/or
an
organization
that
manufactures
or
distributes
products.
The
following
applications
secure
information
by
inventory
organization:
Oracle
Inventory,
Bills
of
Material,
Engineering,
and
Work
in
Process,
Master
Scheduling/MRP,
Capacity,
and
Purchasing
receiving
functions.
To
run
any
of
these
applications,
you
must
choose
an
organization
that
has
been
classified
as
an
inventory
organization.
Note**
in
R12
Set
of
Book
concept
is
obsolete.
Its
been
replaced
by
Primary
ledger.
Ledger
Concept
Primary
Ledger:
The
core
of
companies
financial
records
where
every
transaction
flow
through
legal
Entity
accounts.
It
is
defined
by
4Cs
Chart
of
Account,
Accounting
Calendar,
Primary
Currency
and
Sub-
ledger
Accounting
Method.
Subledger:
Types
of
Ledgers:
There
are
3
types
of
ledgers,
1) Primary
Ledger
(PL):
Main
ledger
which
contains
all
information
and
can
have
any
number
of
secondary
ledger.
2) Secondary
Ledger
(SL):
It
provides
additional
accounting
representation
of
primary
ledger
and
comply
with
legal
requirements.
It
is
optional.
It
can
be
assigned
to
only
one
Primary
ledger.
3) Reporting
Currency
(RC):
When
the
currency
is
different
[Multiple
currency
reporting]
then
reporting
currencies
will
be
defined.
When
an
RC
is
not
assigned
to
PL
(or)
SL
when
translation
is
run
RC
will
automatically
added
to
the
Primary
Ledger.
When
to
use
Secondary
Ledger
(SL)
and
Reporting
Currency
(RC)
with
Primary
Ledger
(PL)?
Ledger Sets:
It
Groups
multiple
ledgers
that
shares
same
COA
and
Calendar
combination.
It
treats
multiple
ledgers
into
one.
Usually
when
we
want
to
open
Calendar
periods,
we
need
to
open
it
seperately
for
every
ledger,
instead
if
we
open
/
close
the
calendar
periods
for
a
Set
automatically
it
will
open
for
all
ledger
associating
with
the
set.
The
Ledger
permissions
are
defined
here
like
Read
only,
Read
and
Write
access.
We
can
set
permission
for
Legal
entity,
Ledgers
,
Balancing
(or)
Management
Segment
values.
Subledger
Accounting
(SLA):
Subledger
Accounting
Methods
(SLAM):
If
Subledger
Accounting
is
used,
the
method
needs
to
be
defined
for
both
primary
and
secondary
ledgers.
The
accounting
methods
can
be
changed
anytime
and
the
changes
wont
have
major
impact,
it
will
affect
only
the
new
journals.
There
are
5
Subledger
Accounting
Methods:
Release 12 Term
Subledger Accounting
Intercompany Accounts
Intercompany Balancing
Primary Ledger
Reporting Currency
Secondary Ledgers
Secondary Ledgers
Set of Books
Ledger
Translated Currency
Balance-Level-Reporting Currency
Security
Profile:
It
is
attached
to
responsibility,
which
determines
which
applicant
or
employee
records
are
available
for
the
holders
of
the
responsibility.
Security
profile
is
also
associated
with
Work
structure.
Workstructures
in
Security
Profile:
Please
Refer
oracle
Link
for
more
information:
http://docs.oracle.com/cd/A60725_05/html/comnls/us/per/scaud02.htm
Security
Definition:
The
key
definition
is
the
responsibility,
which
allows
access
to
the
records
specified
by
the
security
profile,
using
the
windows
specified
by
the
menu
structure,
and
the
reports
and
processes
specified
by
the
report
security
group.
For
more
information
please
refer:
http://docs.oracle.com/cd/A60725_05/html/comnls/us/per/scaud06.htm
Suppose
if
users
have
access
to
2
business
group,
we
need
to
create
2
different
Security
profile.
As
number
of
business
group
increases,
maintenance
of
security
profiles
becomes
complex.
To
simplify
the
administration
efforts
oracle
introduced
global
security
profiles.
Using
this
feature,
we
can
maintain
one
security
profile
which
spans
across
all
business
groups
and
reducing
creation
of
many
security
profiles.
Advantages
of
Global
Security
Profile
Reduces
creation
of
many
Security
Profiles.
Maintenance
is
easier
during
modification.
Enables
Global
reporting
across
business
Group.
Why
MOAC?
Currently
in
Oracle
11i
single
responsibility
is
pointed
to
enterprise
structure
i.e.
a
responsibility
can
be
mapped
to
only
one
OU
[Represents
modules
like
AP,
PO,INV
etc].
Consider
a
structure
with
Single
Legal
entity
(LE)
having
5
Operating
Units
[OU]
we
need
to
create
5
responsibility
and
assign
same
to
each
OU.
Every
time
to
create
invoice
(or)
Purchase
Orders
(or)
submitting
Requests
the
user
have
to
switch
responsibility
b/w
OUs.
This
is
a
time
consuming
process.
By
using
MOAC,
Single
Responsibility
can
be
mapped
to
multiple
OUs
thus
user
can
perform
multiple
tasks
across
OUs
without
changing
the
responsibility.
It
is
a
Data
Model.
It
defines
the
components
involved
in
trading
with
eBusiness
Suite.
The
main
usage
of
this
technology
is
to
create
relationships
between
entities.
It
Tracks
relationship
between
organizations
and
its
trading
partners
but
also
between
themselves.
It
maintains
a
Universal
Schema
for
Customers,
Suppliers
and
resellers,
banks
etc.
across
all
eBusiness
applications.
Key
Features:
Create
Menu:
Navigation:
SYS
ADMIN
Application
Menu
Create
Responsibility:
Navigation:
SYS
ADMIN
Security
Responsibility
Define
Similarly
create
a
custom
responsibility
for
HRMS.
Create
User:
Navigation:
SYS
ADMIN
Security
User
Define
Now
log
in
as
this
user.
Create
Currency:
Navigation:
GL
Setup
Currencies
Define
Create
Calendar:
Before
Defining
Calendars
we
need
to
select
the
Period
Types.
Navigation:
GL
Setup
Financials
Calendars
Types
Now
define
accounting
calendar
for
your
organization.
Navigation:
GL
Setup
Financials
Calendars
Accounting
Prefix
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
Type
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
MONTH
Year
2013
2013
2013
2013
2013
2013
2013
2013
2013
2013
2013
2013
Quarter
Num
1
1
1
2
1
3
2
4
2
5
2
6
3
7
3
8
3
9
4
10
4
11
4
12
From
1-Jan-13
1-Feb-13
1-Mar-13
1-Apr-13
1-May-13
1-Jun-13
1-Jul-13
1-Aug-13
1-Sep-13
1-Oct-13
1-Nov-13
1-Dec-13
To
31-Jan-13
28-Feb-13
31-Mar-13
30-Apr-13
31-May-13
30-Jun-13
31-Jul-13
31-Aug-13
30-Sep-13
31-Oct-13
30-Nov-13
31-Dec-13
Name
13-Jan
13-Feb
13-Mar
13-Apr
13-May
13-Jun
13-Jul
13-Aug
13-Sep
13-Oct
13-Nov
13-Dec
Request
Other
-
Calendar
Validation
Report
will
be
submitted
to
check
for
any
Gaps
in
Calendar.
Now
Click
Segments
to
define
structure.
D_DEPT:
D_ACT:
D_RES:
COMPANY_CODE:
D_DEPT:
D_ACCOUNT:
D_RESERVE:
In
Release
11i,
the
GL:
Set
of
Books
profile
option
controlled
the
set
of
books
that
a
responsibility
could
access.
In
Release
12,
the
GL
Ledger
Name
profile
option
replaces
the
GL:
Set
of
Books
profile
option.
All
responsibilities
to
which
set
of
books
have
been
assigned
using
the
GL:
Set
of
Books
profile
option
will
be
associated
to
a
data
access
set
using
the
GL:
Data
Access
Set
profile
option.
The
data
access
set
will
provide
full
read
and
write
access
to
the
upgraded
ledger
allowing
you
to
continue
to
use
the
ledger
the
same
way
as
you
did
in
Release
11i.
HR
Option
Purpose
HR:Business Group
HR:Security Profile
HR:User Type
Value
HR
with
Payroll
User
Level
Responsibility
Set
the
profile
option
to
all
the
custom
responsibilities
we
have
created.
Navigation:
SYS
ADMIN
Profile
System
Calendar:
Workday
Pattern:
Shifts:
Shift
Workday
Pattern:
Shift
Timings:
Dates:
Build
Calendar:
Request
Build
Workday
Calendar
will
be
submitted.
Creating
Locations:
Navigation:
HRMS
Work
Structures
Location
In
the
Location
form
to
input
address,
we
need
to
select
address
style
based
on
the
country.
Shipping
Details:
Other
Details:
Similarly
we
need
to
create
other
locations.
Location
2:
Location 3:
Location
4:
Multi-Org
Structure:
We
are
going
to
create
a
similar
Multi-Org
Structure
Creating
Organizations:
Navigation:
HRMS
Work
Structures
Organization
Description
Organization
Classification:
Classify
this
organization
as
HR
Organization
to
create
employees.
Click
Accounting
Setup
Click
Create
Legal
Entity.
Legal
Entity:
Dini
Aviation
Corporation
(Optional
Info)
Click
Apply.
Click
Next
Click
Next.
Summary:
Click
Finish.
Accounting Options:
Now
Update
Ledger
Options:
Step
1:
Skip
this
step
no
changes
required.
Click
Next.
Step
2:
Ledger
Options
Step
3:
Advance
Options
Click
Finish.
Click
Apply.
HRMS
Responsibility
GL
Super
User
Responsibility
Accounting
Setup
Manager
Using
HRMS
Responsibility:
Navigation:
HRMS
Work
Structures
Organization
Description
Let
us
create
using
accounting
Setup
Manager.
Update
Operating
unit.
Click
Apply.
Similarly
Create
New
Operating
Unit
for
Power
Business.
Click
Complete.
Now
the
Operating
Unit
status
is
Active.
Click
Complete
to
finish
Ledger
setup.
Click
Yes.
Click
Return
to
Accounting
Setups.
Ledger
Setup
Successfully
Completed.
Types
of
Security
Types:
1) View
all
Organizations:
It
will
not
allow
you
to
save
a
new
security
profile
because
it
automatically
seeds
one
and
no
need
to
create
another.
2) Secure
Organizations
by
organization
Hierarchy
and/or
Organization
List:
It
defines
a
hierarchy
such
that
only
the
organization
included
in
this
hierarchy
can
only
have
access.
3) Secure
Organizations
by
Single
Operating
Unit:
The
Operating
unit
will
be
decided
based
on
the
profile
MO:
Operating
Unit.
4) Secure
Organizations
by
Operating
Unit
and
Inventory
Organizations:
The
Operating
Unit
&
Inventory
Organization
will
be
decided
based
on
profile
MO:
Operating
Unit.
Exclude
Business
Groups:
To
avoid
including
the
business
group
in
the
hierarchy
this
check
box
can
be
checked.
Include
the
Organizations
to
which
responsibility
can
have
access
to.
Request
Executed
Successfully.
MO:
Security
Profile
Assign
this
profile
option
to
an
application
responsibility
to
provide
a
user
with
this
responsibility
access
to
multiple
operating
units.
MO:
Default
Operating
Unit
Use
this
profile
option
to
specify
a
default
operating
unit
from
the
list
of
operating
units
assigned
to
your
application
responsibility
through
the
MO:
Operating
Unit
or
MO:
Security
Profile.
Note:
If
the
MO:
Operating
Unit
is
set
or
you
are
assigned
only
one
operating
unit
in
the
MO:
Security
Profile
profile
option,
then
the
single
operating
unit
becomes
your
default
operating
unit.
MO:
Operating
Unit
Assign
this
profile
option
to
an
application
responsibility
to
provide
a
user
with
this
responsibility
access
to
one
operating
unit.
For
more
information
please
check
the
link
below.
http://docs.oracle.com/cd/E18727_01/doc.121/e13423/T443823T443827.htm
It
is
used
to
populate
the
installed
modules
seeded
values,
So
that
new
organization
can
use
the
seeded
data.
Whenever
new
organization
is
created
in
a
multi-Org
structure,
this
request
is
mandatory
to
be
submitted.
It
can
be
submitted
for
single
Operating
unit
(or)
for
all
Operating
Units.
Before
submitting
the
request
make
sure
it
is
available
for
your
responsibility.
If
not,
please
add
the
same
to
your
request
group.
Note**
this
program
is
to
be
executed
for
all
the
Operating
Units
available
in
you
enterprise
structure.
Operating
Unit
2:
Commit
Setup
and
classify
the
organization
as
Inventory
Organization.
Additional
Information:
Accounting
Information
Inventory
Information
Receiving
Information
Accounting Information:
Commit
Setup;
Inventory
Information:
Costing Information:
Other Accounts:
Receiving
Information:
Click
Save.
Accounting
Information:
Commit
Setup;
Inventory
Information:
Now
Copy
the
Master
Inventory
Organization
Setup.
Note**
since
we
have
copied
the
Master
Inventory
Org
data,
all
the
other
mandatory
setups
will
be
populated
automatically
same
as
IMO.
Receiving
Information:
Power OU:
Accounting
Information:
Inventory
Information:
Now
Copy
the
Master
Inventory
Organization
Setup.
Receiving
Information:
Click
Save.
Level
Responsibility
Responsibility
Responsibility
HR:Business
Group
HR:User
Type
HR:
Security
Profile
Value
Primary
Ledger
Primary
Ledger
ID
Set
of
Books
d_hrms1
DINI_PL1
2842
Not
Used
in
R12
d_resp1
DINI_PL1
2842
Not
Used
in
R12
DINI_BG1
HR
with
Payroll
User
DINI_BG1
DINI_BG1
DINI_BG1
HR
with
Payroll
User
Now
Click
Change
Status
to
open
the
Inventory
Accounting
period.
Click
OK.
Follow
the
above
steps
to
open
periods
for
Child
Inventory
Organization.
To
change
the
organizations,
please
click
Change
Organization.
Select
Organization:
601
Similarly
for
Organization:
602
When
the
form
Opens
indicates
the
transactions
are
enabled.
Similarly
follow
the
same
steps
for
organization
601
and
602.
What is Sub-Inventories?
Sub-Inventories
are
unique
Physical
(or)
Logical
Separations
of
Material
inventory
such
as
Raw
Material,
Finished
Goods
(or)
Defective
Goods/Materials.
All
materials
within
an
Organization
are
stored
in
Sub-inventory.
Types
of
Sub-Inventories:
In
warehouse
management
there
are
2
types
of
sub-inventories.
i.
ii.
Storage
Receiving
Storage
Receiving
Mandatory
Tracking
of
Goods
is
possible
On-Hand
Quantity
is
available
N/A
Optional
Tracking
of
Goods
is
possible
Does
not
reflect
in
on-hand
Quantity
Available
only
if
Receipts
are
created.
Similarly
create
a
sub-inventory
for
organization:
602
Create
Jobs:
Navigation:
HRMS
Work
Structures
Job
Description
Click
New.
Note**
Job
should
point
to
some
Job
Group,
if
not
please
cross
check
the
profile
HR:
Security
Profile.
Job
Name
A0
A1
A2
A3
Job
Code
1000
2000
3000
4000
Description
Junior
Senior
Asst.
Manager
Manager
Reporting
To
A1
A2
A3
--
A0:
Junior
A1: Senior
A2:
Asst.
Manager
A3:
Manager
Create
Positions:
Navigation:
HRMS
Work
Structures
Position
Description
We
are
going
to
create
positions
for
each
job
respective
to
each
department.
SALES
MFG
ADMIN
FIN
A3
A3_SALES
A3_MFG
A3_ADMIN
A3_FIN
A2
A2_SALES
A2_MFG
A2_ADMIN
A2_FIN
A1
A1_SALES
A1_MFG
A1_ADMIN
A1_FIN
A0
A0_SALES
A0_MFG
A0_ADMIN
A0_FIN
Equivalent
Position
Codes:
SALES
MFG
ADMIN
FIN
A3
4001
4002
4003
4004
A2
3001
3002
3003
3004
A1
2001
2002
2003
2004
A0
1001
1002
1003
1004
Position
Level:
A0
Hiring
Information:
Position
Level:
A1
Position
Level:
A2
Position
Level:
A3
Create
Employees:
Navigation:
HRMS
People
Enter
and
Maintain
Create
an
Employee
[Create
Employment]
and
assign
position
[Assignments].
Employee
1:
Note**
when
creating
employee
for
first
time
select
option
Correction.
Click
Yes
in
Decision
window.
Employee 2:
Employee
3:
Employee
4:
Commit
Setup;
Commit
Setup;
Now
place
the
cursor
in
the
position
section
and
go
to
query
mode
to
select
position.
Query
Mode:
Note**
Now
start
from
the
highest
position
inside
a
department
and
traverse
to
lowest.
We
are
going
to
define
hierarchy
for
Sales
Department.
Now
we
need
to
define
subordinates
for
this
current
position.
Commit
Setup;
Now
traverse
up
and
check
the
hierarchy.
When
reached
the
top
position
a
note
will
be
displayed.
Employee
-
User
Mapping:
User
Employee
Position
YO_USER1
emp1, duser1
A0_SALES
YO_USER2
emp2, duser2
A1_SALES
YO_USER3
emp3, duser3
A2_SALES
YO_USER4
emp34,
duser4
A3_SALES
Use
the
Fill
Employee
Hierarchy
process
to
create
a
direct
mapping
between
the
defined
position
hierarchies
and
the
employees
holding
positions
in
each
hierarchy.
When
you
run
this
process,
it
checks
each
position
hierarchy
and
updates
each
employee,
his
supervisor,
the
level
of
supervision
(a
direct
supervisor
is
level
1),
the
employee's
position,
and
the
supervisor's
position.
The process creates an error log which lists all positions to which no employee is
assigned, but having such positions is a benign error that does not hamper system
operation.
If you do not use hierarchical security for any of your documents and do not use position
hierarchies for your approvals, you do not need to run this process. Otherwise, you must
run this process before any of the following changes can take effect:
o
Note**
after
setting
up
the
position
run
the
request
Fill
Employee
Hierarchy
from
purchasing
responsibility
for
each
Operating
unit.
Operating Unit 1:
Operating
Unit
2: