6 O
ctob
er 2
008
Max
imo
En
terp
rise
Ad
apte
r (M
EA
)In P
urc
has
ing
an
d In
ven
tory
-V
enka
tlak
shm
i Bas
kara
nIB
M M
axim
o M
on
day
sO
cto
ber
6 2
008
6 O
ctob
er 2
008
2
Agenda
About the Customer
Why MEA?
Interface Architecture
Maximo -Oracle Apps Interface
Maximo –Ariba Interface
Processing Rules
Exam
ple of Processing Cycle
Error Handling
Client Benefits
Major Achievem
ents
Q&A
6 O
ctob
er 2
008
3
•Global leader in the field of filtration and coolant
system
s
•23 Production Plants across Nine Countries
•Distribution Centers in six continents
•Employs 6000 people world wide
TCS is engaged in:
•Developing interfaces between Maximo and other
external system
s in financial and purchasing domains
•Performing screen level and MBO level
customizations to suit business requirem
ents
•Implementation of Mobile Maximo
About the Customer
6 O
ctob
er 2
008
4
Oracle Apps
•Customer uses Oracle Apps as the Core Financial System
(CFS).
•Oracle Apps is essentially used to maintain General Ledgers and handle
Accounts Payables and Receivables.
Ariba
•Customer uses Ariba as the “Source of Purchasing”
•Single platform to manage all supplier transactions
•Enables to electronically interact with suppliers using Ariba Sales Network
““MEA FORMS A BRIDGE BETWEEN MAXIMO AND EXTERNAL SYSTEMS
MEA FORMS A BRIDGE BETWEEN MAXIMO AND EXTERNAL SYSTEMS””
Why MEA?
6 O
ctob
er 2
008
5
Pol
ling
Que
stio
n
Whi
ch v
ersi
on o
f Max
imo
are
you
usin
g?•
A –
Max
imo
4.x
•B
–M
axim
o 5.
x
•C
–M
axim
o 6.
x•
D –
Not
a M
axim
o us
er
6 O
ctob
er 2
008
6
Pol
ling
Que
stio
n
Wha
t Ind
ustr
y do
you
ope
rate
in?
•A
–M
anuf
actu
ring
Pro
cess
•B
–M
anuf
actu
ring
Dis
cret
e
•C
–E
nerg
y an
d U
tiliti
es•
D –
Oil
and
Gas
•E
–O
ther
s
6 O
ctob
er 2
008
8
Oracle Financials 11.5.10
Maximo 6.1.0
GL
Com
pone
nts
Cha
rt o
f Acc
ount
s
Ven
dor
MEA For Oracle
FND_FLEX_VALUES
FND_FLEX_VALUES_TL
GLCOMPONENTS
GL_CODE_COMBINATIONS
CHARTOFACCOUNTS
PO_VENDORS
PO_VENDOR_SITES_ALL
COMPANIES
Maximo –Oracle Apps Interface
6 O
ctob
er 2
008
9
OR
AC
LE
AP
PS
SYST
EM
PL
/SQ
L
USE
R E
XIT
P
RO
OC
ED
UR
ES
PL
/SQ
L
ST
OR
ED
P
RO
CE
DU
RE
S
PL
/SQ
L
T
RIG
GE
RS
OR
AC
LE
AP
-PS
DA
TA
BA
SE
MA
XIM
OIN
TE
RF
AC
ET
AB
LE
S
MX
IN_I
NT
ER
_TR
AN
S Q
UE
UE
T
AB
LE
MA
XIM
O
USE
R E
XIT
P
RO
CE
DU
RE
PR
OC
ESS
ING
R
UL
ES
MB
O
CO
MP
ON
EN
TS
MA
XIM
O
BA
SE
TA
BL
ES
MA
XIM
O
INT
ER
FA
CE
T
AB
LE
S
IFA
CE
TA
BL
E
CO
NSU
ME
R(C
ron
Tas
k)
JMS
QU
EU
EJM
S C
ON
SUM
ER
Maximo –Oracle Apps Interface using Oracle
Adapter
Pulls Data from
MXIN_INTER_
TRANS
Queue
Pushes data to
Maximo
Interface Tables
6 O
ctob
er 2
008
10
Oracle Apps
Adapter
DB Credentials
of Oracle Apps
DB
End Point
MXESOAIFACE
TABLE
Oracle Apps External System and End Point
6 O
ctob
er 2
008
11
Cron Task
Instance
Connects to End Point
MXESOAIFACETABLE
Interface Table Polling for Oracle Apps Interface
6 O
ctob
er 2
008
12
ORGXRef
Interface
Control
Maximo
Organization
Oracle Set of
Books ID
=
Interface Controls In Maximo
6 O
ctob
er 2
008
13
Pol
ling
Que
stio
n
Is y
our
Max
imo
syst
em in
terf
aced
with
a fi
nanc
ial s
yste
m?
•A
–Y
es–
Ora
cle
•B
–Y
es -
SA
P•
C –
Yes
-O
ther
•D
–N
o
6 O
ctob
er 2
008
14
Maximo 6.1.0
Ariba 8.2.2
MEA
Purchase
Requisitions
Purchase
Orders
Receipts
Cron Task
MXPR_
IFACE
PR
Cron Task
POLLING
Ariba Interface
Table
Purchase
Requisitions
Purchase
Orders
Receipts
PR
Interface Table
Creates
PO
PO
Interface Table
PO
Cron TaskPOLLING
MXPO_
IFACE
Generates
Receipts
MXRECEIPT_
IFACE
Receipt
Cron Task
POLLING
Receipt
Interface Table
Maximo –Ariba Interface
6 O
ctob
er 2
008
15
Maximo
Adapter
End Point
MXESARIBA
DB Credentials
of Maximo DB
Ariba External System and End Point
6 O
ctob
er 2
008
17
Enable Event
Listeners for
PR and Receipt
Outbound Interfaces
Integration Events
6 O
ctob
er 2
008
18
Enable this
Check box if a backup of
existing IFACE tables
should be created
Creating Interface tables in Maximo Database
6 O
ctob
er 2
008
19
Cron Task
Instance
Connects to End Point
MXESARIBA
Interface Table Polling for Ariba Interface
6 O
ctob
er 2
008
20
Read Configuration
Param
eters defined
In Application
start( )
readConfig( )
getParam
eters( )
Initialize Log File
createLogFile( )
Get Oracle Database
Param
eters from
maximo.properties
Get all unprocessed
PRs from
MXPR_IFACE
For each unprocessed
PR in MXPR_IFACE,
Insert into Interface
Table of Ariba and
Update “PROCESSED”
Flag in MXPR_IFACE
Email the error to
the administrator
Log the error in
Log File
ON ERROR
Close
Log File
cronAction( )
closeLogFile( )
Cron Task for Outbound Interfaces
6 O
ctob
er 2
008
21
Complete path
of the class file
that contains
Cron Task
Cron task is
scheduled once
in 5 minutes
Cron task is
currently
active
Defining a Cron task in Maximo
6 O
ctob
er 2
008
22
Read Configuration
Param
eters defined
In Application
start( )
readConfig( )
getParam
eters( )
Initialize Log File
createLogFile( )
Get Oracle Database
Param
eters from
maximo.properties
Get all unprocessed
POs from
External Interface
Table
For each unprocessed
PO from external
Interface table,,
Insert into MXPO_IFACE
and MXIN_INTER_TRANS
Update “PROCESSED”
Flag in Ariba
Email the error to
the administrator
Log the error in
Log File
ON ERROR
Close
Log File
cronAction( )
closeLogFile( )
Cron Task for Inbound Interfaces
6 O
ctob
er 2
008
25
1. PR 1984 is created in Maximo and status
changed to APPR
2. MEA copies the PR data to
MXPR_IFACE table in Maximo database
3. Crontask copies the PR data from
MXPR_IFACE to Ariba PR Interface Table
PR and PO getting
processed
in Ariba (External System
)
4. Job that runs in Ariba gets the PR from
Ariba Interface table and creates an equivalent PO
Next Slide
Example of Processing Cycle
6 O
ctob
er 2
008
26
5. PO is created in Ariba and stored in Ariba PO
Interface Table
6. Cron task pulls the PO from Ariba PO Interface
Table and inserts it in MXPO_IFACE
7. Crontask also updates MXIN_INTER_TRANS
table
8. IFaceTableConsumer polls the interface table
and creates a PO in Maximo
Example of Processing Cycle (Contd)
6 O
ctob
er 2
008
29
1. On Error,
error description
islogged into a log table
in Ariba
2. Crontask that runs in
Maximo, pulls the error
and sends a mail
to the user whoever is
responsible for the PR / PO / Receipt
Error Handling in Ariba Transactions
6 O
ctob
er 2
008
30
Pol
ling
Que
stio
n
Is y
our
Max
imo
syst
em in
terf
aced
with
a p
urch
asin
g sy
stem
?•
A –
Yes
–O
racl
e
•B
–Y
es -
SA
P•
C –
Yes
–A
riba
•D
–Y
es –
Oth
er
•E
–N
o
6 O
ctob
er 2
008
31
•Real-time transfer of General Ledger and Chart of Accounts from
Oracle Apps Core Financials System
to Maximo.
•Complete automation of Purchasing flow (Requisitions, Orders andReceipts) between
Maximo and Ariba
•Maximo Users need not be trained to work on multiple system
s.
•On errors, emails are automatically sent to users with a finely defined Error Description.
•Errors or exceptions that occur due to program or crontask failure is automatically mailed
to System
Administrator.
•Interfaces can be enabled or disabled for a Maximo site within an organization, just on click
of a checkbox.
Client Benefits
6 O
ctob
er 2
008
32
•Provided a business solution by amalgam
ating Maximo with other
established system
s operating in Financial and Purchasing domain.
•Maximo 5.2 was already interfaced with Oracle Financials for a different plant operating
at the client’s site. It was a challenge to interface Maximo 6.1 with Oracle Financials as
they both operate on same Oracle Financials database.
•Data validations performed on pre processing stage reduced the percentage of processing
errors in inbound and outbound transactions, thus reducing network traffic.
•Design is user-friendly and does not expect user to perform intricate actions to interface
Maximo with external system
s.
•High end error handling mechanism has greatly reduced the involvem
ent of technical
and support team after Go-Live
Major Achievements
Top Related