Contact at mumbai.academics@gmail.com or 8097636691
Responsive Ads Here

Friday, 2 February 2018

System Integration Between Interconnect And Erp


System Integration Between Interconnect

 And Erp


Abstract
This project constitutes the integration specification for the billing export interface from Carrier Cockpit™ to Qtel’s financial system Oracle e-Business suite ERP systems (Oracle Finance).
Carrier Cockpit is an interconnect application, web-based solution providing end-to-end process support for the supply chain of trade and exchange of voice traffic between telecom operators.
Oracle e-Business suite ERP systems (Oracle Finance) is a financial system that is existing in Qtel which generates billing for the calls generated from them and received to them.
The connection between Carrier Cockpit and the Oracle Finance system will be established through TIBCO Enterprise Application Integrator (EAI). The invoices are exported from Carrier Cockpit to Oracle Finance through TIBCO EAI. The invoices about the traffic which is present between telecommunications is send through interface to the Oracle Finance to generate billing to that data.
TIBCO-EAI is a middleware architecture which is used to provide integration between two applications. This architecture consists of web service and adaptor. Web service will be mapping the invoices entered in carrier cockpit with ERP data based on some rules. If they are same then carrier cockpit will export data, it was collected by adaptor and send to ERP there it will import data and generates payments. These may be General Ledger journals or Accounts Payable invoices.
The project includes details on the exchanged data, interaction and exception handling. The details in this specification have been prepared based on billing workshops, with major input from the key business groups.
INTRODUCTION
Overview of the system
In the proposed solution for integration Carrier Cockpit™ will be the source of data for the invoices that will be sent by Qtel to other customers. This data will be exported to Carrier Cockpit™ database tables. Oracle Finance will collect the data through TIBCO EAI.
Qtel will use the Recurring Account functionality in Carrier Cockpit™ to generate billing data. The export will be done by an Autopilot Job in Carrier Cockpit™ and can be scheduled by the users to run at any time and periodicity. It can also be called to run on a single occasion, just like all other Autopilot Jobs in Carrier Cockpit™. The job will export all data from all generated Recurring Accounts with state Normal which have not been exported before (regardless of which period they belong to). Drafts will never be exported.
The job will know which Recurring Accounts have already been exported by a unique id. However, if a Recurring Account is cancelled in Carrier Cockpit™ (traffic data released from it) and then a new Recurring Account is created for that period, the new one will also be exported to Oracle Finance by the next job, since it has its own unique id.
Exporting accounts that have already been exported can be done only in exceptional cases and it requires editing a table in the Carrier Cockpit™ database.
Two kinds of billing data will be exported. Estimates will go to General Ledger (GL) whereas the data to be sent to customers and suppliers will go to the Accounts Payable (AP). No data will be prepared for Accounts Receivable (AR) from the current version of the interface. However the design of the interface will consider a future integration with AR and facilitate development of this case as an add-on in a later version.
Services
1.     Call Traffic
 For Voice traffic Carrier Cockpit™ will prepare four (4) accounts for Oracle Finance:
·         Hubbing (AP)
·         Bilateral Outgoing (Buy) ( AP)
·          Refile (GL)
·          Bilateral Incoming (Sell) (GL)
2. Internet Traffic
Event traffic includes Telex, Telegram, X25, SMS and MMS. General Agreements are used in Carrier Cockpit™ for event traffic. Traffic in these agreements is either incoming (inbound) or outgoing (outbound). Two accounts will be exported.
·         Outgoing traffic (Buy) ( AP)
·         Incoming traffic (Sell) ( GL)
Existing System
In the existing system, the interface between the Carrier Cockpit and Oracle Finance is the simple Database link. There is a Database link between the databases. so that  everyone can get data and transfer data without any security between the databases. Invoices are transferred manually also.
Drawbacks
In the existing system many drawbacks are present
·         Lack of security, due to direct link transferring among databases is easy.
·         The client who generates the job not able to know about the information that is send correctly or not.
·         If more servers are there, then there is a lack of control on data.
Proposed System       
In the proposed system, Enterprise Application Integrator (EAI) is used between the Carrier Cockpit and the Oracle Finance to transfer the invoices between them. Which provides security that is data can be exported based on specific user id. The EAI is a middleware architecture.
Advantages
The advantages are
·         Eliminates the delays and errors caused by the direct link or by the manual re-entry of information.
·         Allows all systems to have the latest data by automatically synchronizing information as it changes.
·         It is very flexible, reliable and easy to maintain.
·         Through this Tibco interface we provide security with specific user ids.
H/W And S/W  Requirements Specification
Hardware Requirements
PROCESSOR               :         Intel Pentium IV Processor
PROCESSOR SPEED  :        1.86 GHz
RAM                             :        1 GB
HARD DISK                :         80 GB
Software Requirements
OPERATING SYSTEM    :      WINDOWS XP PROFESSIONAL
FRONTEND                      :       JAVA 1.4
BACKEND                        :      ORACLE 9i  
BROWSER                        :      INTERNET EXPLORER 6.0 AND ABOVE
SOFTWARE                      :      RATIONAL ROSE
PACKAGE                        :      MS OFFICE
CISCO VPN CONNECTIVITY             

No comments:

Post a Comment