| Best practices for apps integration with third party systems ? [message #216039] |
Wed, 24 January 2007 15:24  |
rrb2
Messages: 2
Registered: January 2007
|
Junior Member |
|
|
Hi all
I would like to know if there is any document from oracle or from your own regarding best practices for apps integration with third party systems.
For example, in particular, let's say we need customization in a given module(ex:payables) need to provide data to a third party system, consider following:
outbound interface:
1)should third party system should be given with direct access to oracle database to access a particular payments data information table/view to look for data ?
2) should oracle create a file to third party system, so that it can read and do what it need to do?
inbound:
1) should third party should directly login and insert data into tables which holds response data?
2) again, should third party create file and oralce apps will pick up for further processing?
again, there could be lot of company specific scenarios like it has to be real time or not... etc...
How does companies make sure third party systems are not directly dipping into other systems (oracle apps/others), so that it will follow certain integration best practices.
how does enterprise architectute will play a role in this? can we apply SOA standards? should use request/reply using Tibco etc?
Many oracle apps implementations customizations are more or less directly interacting with third party systems by including code to login into respective third party systems and vice versa.
Let me your know if you have done differently and that would help oracle apps community.
thanks
rrb.
|
|
|
|
| Re: Best practices for apps integration with third party systems ? [message #216295 is a reply to message #216039] |
Fri, 26 January 2007 03:52  |
David.K.Dickson
Messages: 413
Registered: October 2005
Location: Surrey, England
|
Senior Member |
|
|
I am not an expert in this field, but in my humble opinion you should not give 3rd parties direct access to update your Oracle Applications with Invoice, Credit Memo or Payment data.
I specialise in Financials, so I cannot comment on Manufacturing and Supply Chain. However, iPayables and iReceivables allow you to give your Suppliers and Customers access via the Internet to information regarding their own invoices, credit memos, payments etc., but do not allow them to update this information and do not allow them to look at information relating to other Suppliers and Customers. Please refer to the relevant User Guides for more information.
As for exchanging invoices etc. with 3rd parties, one good way to do this is via Electronic Data Interchange (EDI). EDI uses XML to hold Invoice, Credit Memo and Remittance Advice information. After creating your EDI file, you can send it to the third party and they can read it into their financial applications. Similarly, when the third party sends you an EDI file, because Oracle Applications understand the XML used in the file, it can load the Invoice, Credit Memo or Remittance Advice directly into the appropriate Application. Again, please refer to the relevant User Guides for more information on both Inbound and Outbound EDI.
 HTH
David
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
