Sonic Alert B31540-02 User Manual

Oracle® Telecommunications Billing Integrator

Implementation Guide Release 12

Part No. B31540-02

December 2006

Oracle Telecommunications Billing Integrator Implementation Guide, Release 12

Part No. B31540-02

Primary Author:  Nuzhath Shereen

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Send Us Your Comments

Preface

1 Introduction to Telecommunications Billing Integrator



Contents

Telecommunications Billing Integrator Overview

Telecommunications Billing Integrator Features..................................................................... 1-2

Publishing Information to the Billing Applications................................................................ 1-3

Products Used in TBI................................................................................................................. 1-5

Enhancements............................................................................................................................ 1-5

Grouped Sales Order Message..................................................................................................1-6

Publish Bill To Accounts for a Sales Order.............................................................................. 1-6

Additional TCA Events for Account Update Message............................................................. 1-6

Enhancements to Account Message.......................................................................................... 1-7

Enhancements to Sales Order Message ................................................................................... 1-7

Uptake of JMS Compliant Queues in XML Gateway

...................................................................1-1

.............................................................. 1-8

2 Implementing Telecommunications Billing Integrator

Implementation Considerations

TBI with TSO

Middleware in TBI

External Billing Applications

............................................................................................................................ 2-1

.................................................................................................................... 2-2

............................................................................................... 2-1

.................................................................................................... 2-2

3 Implementation Tasks for Oracle Telecommunications Billing Integrator

Implementation Tasks

Setting Up XML Gateway

...............................................................................................................3-2

......................................................................................................... 3-3

 iii

Defining XML Gateway Profile Values.................................................................................... 3-3

Defining UTL_FILE_DIR Parameters....................................................................................... 3-3

Defining XML Standards.......................................................................................................... 3-4

Defining a Hub.......................................................................................................................... 3-4

Defining Hub Users.................................................................................................................. 3-4

Defining Transactions............................................................................................................... 3-5

Internal and External Transactions in XML Gateway.............................................................. 3-5

Transactions Enabled for TBI................................................................................................... 3-9

Defining Trading Partners...................................................................................................... 3-10

Setting Up Oracle Collaboration History............................................................................... 3-10

Defining Collaboration History Profile Values..................................................................... 3-11

Defining Lookup Values for Collaboration........................................................................... 3-11

Setting Up Collaboration Events............................................................................................ 3-12

Setting up the Final Collaboration Event

Checking Status of Agent Listeners

Setting Up Bill Summary UI................................................................................................... 3-13

Defining Bill Summary UI Profile Options........................................................................... 3-13

Providing Access and Enabling the Bill Summary UI........................................................... 3-14

Personalizing Oracle Contact Center for TBI......................................................................... 3-15

Accessing the Bill Summary UI from Oracle Contact Center................................................ 3-16

Loading Bill Summary Data....................................................................................................3-16

Integration with Order Management Workflow Processes................................................... 3-16

Integrating Workflow Process for Publishing Account Information.................................... 3-16

Integrating Workflow Process for Publishing Sales Order Information

Defining Sales Order Line Profile Option

Creating the Workflow Function

Integrating Workflow Process for Publishing Group Sales Order Information .................. 3-19

Setting Up and Running the Item Publish Concurrent Program...........................................3-19

Item Batch Export Profile Values............................................................................................ 3-20

Submitting the Item Publish Request

Subscribing to Account Update Events.................................................................................. 3-21

Supported Events

Configuring the Middleware.................................................................................................. 3-23

.................................................................................................................... 3-22

............................................................................................ 3-19

............................................................................... 3-12

........................................................................................ 3-13

..............................3-17

............................................................................. 3-18

.................................................................................... 3-21

A Configuring Oracle Applications InterConnect

Oracle Applications InterConnect Overview........................................................................... A-1

Setting Up OAI Hub

Setting up OAI Adapter for Advanced Queues....................................................................... A-3

Dropping the Hub Schema

Importing OAI Maps to the Repository

................................................................................................................. A-2

....................................................................................................... A-4

................................................................................... A-5

B APIs in Telecommunications Billing Integrator

Bill Summary Bulk Insert APIs................................................................................................ B-1

Procedure: INSERT_ROW_BATCH ........................................................................................ B-1

Procedure: UPDATE_ROW_BATCH........................................................................................B-2

Bill Summary Public Table Type: BILL_SUMMARIES_TABLE............................................ B-3

Bill Summary Public Record Type: BILL_SUMMARIES_REC............................................... B-3

C Message Maps and DTDs for XML Gateway

Maps and DTDs Overview....................................................................................................... C-1

Loading and Deleting Maps..................................................................................................... C-3

Loading and Deleting DTDs.................................................................................................... C-3

D XML Messages in TBI

XML Message Overview .......................................................................................................... D-1

Outbound and Inbound BOD.................................................................................................. D-2

XML Message Format............................................................................................................... D-2

Outbound Messages ................................................................................................................ D-2

Inbound Messages ................................................................................................................... D-4

Seeded XML Messages............................................................................................................. D-7

Message Specifications for Account Information....................................................................D-7

Message Specifications for Sales Order Line.........................................................................D-20

Message Specifications for Product/Item............................................................................... D-30

Message Specifications For Group Sales Order Line

........................................................... D-32

Glossary

Index

 v



Send Us Your Comments

Oracle Telecommunications Billing Integrator Implementation Guide, Release 12

Part No. B31540-02

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example:

• Are the implementation steps correct and complete?

• Did you understand the context of the procedures?

• Did you find any errors in the information?

• Does the structure of the information help you with your tasks?

• Do you need different information or graphics? If so, where, and in what format?

• Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available).

Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Applications Release Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently.

Send your comments to us using the electronic mail address: appsdoc_us@oracle.com

Please give your name, address, electronic mail address, and telephone number (optional).

If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services.

If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

 vii

Intended Audience

Welcome to Release 12 of the Oracle Telecommunications Billing Integrator Implementation Guide.

This guide is intended for implementers and administrators of the Telecommunications Billing Integrator application. This guide assumes you have a working knowledge of the following:

• The principles and customary practices of your business area.

• Oracle Telecommunications Billing Integrator

• Oracle XML Gateway



Preface

To learn more about Oracle XML Gateway, see the Oracle XML Gateway User's Guide.

• Oracle Workflow

To know more about Oracle Workflow, see the Oracle Workflow Administrator's

Guide.

See Related Information Sources on page xi for more Oracle Applications product information.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

 ix

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ .

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure

1 Introduction to Telecommunications Billing Integrator

This chapter provides a brief introduction to the features in TBI.

2 Implementing Telecommunications Billing Integrator

This chapter lists the implementation considerations for TBI.

3 Implementation Tasks for Oracle Telecommunications Billing Integrator

This chapter discusses the tasks to implement Oracle Telecommunications Billing Integrator.

A Configuring Oracle Applications InterConnect

This appendix provides information on configuring Oracle Applications InterConnect (OAI).

B APIs in Telecommunications Billing Integrator

This appendix provides information on the APIs in TBI.

C Message Maps and DTDs for XML Gateway

This appendix provides information on the message maps and DTDs for Oracle XML Gateway.

D XML Messages in TBI

This appendix provides information on the XML messages in TBI.

Glossary

Related Information Sources

Oracle Telecommunications Billing Integrator shares business and setup information with other Oracle Applications products. Refer to other guides when you set up and use Oracle Telecommunications Billing Integrator. You can read the guides online by choosing Library from the expandable menu on your HTML help window, by reading from the Oracle Applications Document Library CD included in your media pack, or by using a Web browser with a URL that your system administrator provides.

If you require printed guides, you can purchase them from the Oracle Store at http://oraclestore.oracle.com.

Integration Repository

The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.

The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.

Guides Related to All Products

Oracle Applications User's Guide

This guide explains how to enter data, query, run reports, and navigate using the graphical user interface (GUI). This guide also includes information on setting user profiles, as well as running and reviewing reports and concurrent processes. You can access this user's guide online by choosing "Getting Started with Oracle Applications" from any Oracle Applications help.

Guides Related to This Product

Oracle Telecommunications Service Ordering Process Guide

This manual provides information on setting up Oracle Order Management that is specific to the Oracle Telecommunications Service Ordering solution.

Oracle XML Gateway User's Guide

This manual describes the XML Gateway features and architecture and provides information on Message Designer, XML Gateway Setup, and Execution Engine.

 xi

Oracle Workflow Developer's Guide

This guide explains how to define new workflow business processes and customize existing Oracle Applications-embedded workflow processes. It also describes how to define and customize business events and event subscriptions.

Installation and System Administration

Oracle Applications Concepts

This book is intended for all those planning to deploy Oracle E-Business Suite Release 12, or contemplating significant changes to a configuration. After describing the Oracle Applications architecture and technology stack, it focuses on strategic topics, giving a broad outline of the actions needed to achieve a particular goal, plus the installation and configuration choices that may be available.

Oracle Applications Installation Guide: Using Rapid Install

This book is intended for use by anyone who is responsible for installing or upgrading Oracle Applications. It provides instructions for running Rapid Install either to carry out a fresh installation of Oracle Applications Release 12, or as part of an upgrade from Release 11i to Release 12. The book also describes the steps needed to install the technology stack components only, for the special situations where this is applicable.

Oracle Applications Upgrade Guide: Release 11i to Release 12

This guide provides information for DBAs and Applications Specialists who are responsible for upgrading a Release 11i Oracle Applications system (techstack and products) to Release 12. In addition to information about applying the upgrade driver, it outlines pre-upgrade steps and post-upgrade steps, and provides descriptions of product-specific functional changes and suggestions for verifying the upgrade and reducing downtime.

Oracle Applications Maintenance Procedures

This guide describes how to use AD maintenance utilities to complete tasks such as compiling invalid objects, managing parallel processing jobs, and maintaining snapshot information. Part of Maintaining Oracle Applications, a 3-book set that also includes Oracle Applications Patching Procedures and Oracle Applications Maintenance Utilities.

Oracle Applications System Administrator's Documentation Set

This documentation set provides planning and reference information for the Oracle Applications System Administrator. Oracle Applications System Administrator's Guide - Configuration contains information on system configuration steps, including defining concurrent programs and managers, enabling Oracle Applications Manager features, and setting up printers and online help. Oracle Applications System Administrator's Guide

- Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager, managing concurrent managers and reports, using diagnostic utilities, managing profile options, and using alerts. Oracle Applications System Administrator's Guide - Security describes User Management, data security,

xii

function security, auditing, and security configurations.

Oracle Alert User's Guide

This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data.

Oracle Applications Developer's Guide

This guide contains the coding standards followed by the Oracle Applications development staff and describes the Oracle Application Object Library components that are needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards for Forms-Based Products. This manual also provides information to help you build your custom Oracle Forms Developer forms so that the forms integrate with Oracle.

Telecommunications Billing Integrator Overview

Telecommunications Billing Integrator (TBI) provides a seamless integration between Oracle E-Business Suite (EBS) and one or more external billing applications to assist in customer management and enhance business benefits.

Telecommunications service providers use Oracle EBS to create and maintain data. They use external billing applications to bill the customers for the services and products ordered through Oracle EBS. Oracle TBI is an interface between Oracle EBS and the external billing applications. Oracle TBI enables exchange of information between Oracle EBS and the billing applications to ensure that data essential for billing purposes

Introduction to Telecommunications Billing Integrator 1-1

is made available to the external billing application.

TBI depends on the Oracle Telecommunications Service Ordering (TSO) solution. The TSO solution leverages multiple components in the Oracle E-Business Suite (EBS) to enable telecommunications service providers to add, change, move or disconnect telecommunication services.

Telecommunications service providers also use Oracle EBS to conduct post-sale interactions with customers, such as processing service requests and billing inquiries. Oracle EBS provides information on customers, accounts, products and sales orders which is replicated and synchronized in the external billing applications. Oracle TBI provides the customer care agent with the bill summary information and actual customer bill images from the billing application. It provides bill summary data in Oracle Contact Center. Oracle TBI thus addresses the need for fast and efficient access to billing information and EBS data.

Telecommunications Billing Integrator Features

The key features of TBI are:

• Information Exchange: TBI enables exchange of information between Oracle EBS and external billing applications. TBI publishes details on accounts, products, and sales orders to the external billing applications and Oracle EBS receives acknowledgements for the published messages.

• Integration with multiple billing systems: TBI can integrate with multiple heterogeneous billing applications simultaneously.

• Status Tracking: TBI integrates with the Oracle Collaboration History to monitor communication between EBS and the billing applications. TBI uses Collaboration History to:

• Support integration with multiple heterogeneous billing systems. TBI uses

Collaboration History to determine if each of the billing application has successfully created accounts and orders. It checks the account messages and sales order messages in Collaboration History.

• Ensure that order information is published to billing systems only after each

billing system has successfully created a party and account.

• Publish updates to party and account relevant to the billing system.

• Track the status of each message that is published to the external billing

application.

• Allow users to query for specific collaborations by account numbers, order

numbers, or product/item numbers. Users can view the contents of the messages being published and the history of the events.

1-2 Oracle Telecommunications Billing Integrator Implementation Guide

For more information, see Setting Up Collaboration History, page 3-10.

• Middleware independent: TBI requires a middleware as an integration point to billing applications for messaging, transforming, and routing the XML messages. TBI can integrate with any middleware that has a native AQ or JMS adapter. TBI has been tested and certified using Oracle Applications InterConnect (OAI 9.0.4). For information on configuring Oracle Applications InterConnect (OAI 9.0.4), see Configuring Oracle Applications InterConnect, page A-1.

• Display bill summary and bill image: TBI provides access to the bill summary data through Oracle Contact Center. The Bill Summary UI displays the bill summary for a single account number. The customer service agents can view the bill summary from the 'Bill Summary' option in Oracle Contact Center. The bill number provided in the bill summary UI is linked to the image data supplied by the billing application. To enable the 'Bill Summary' option in Oracle Contact Center, see Setting up Bill Summary UI, page 3-13.

• Business Event Enabled: Business Event System is a real-time notification system. The Business Event System notifies TBI when an account or sales order is created or updated. For account update, the TBI users can choose the TCA events they wish to subscribe to. For more information, see Subscribing to Account Update Events, page 3-21.

Publishing Information to the Billing Applications

TBI publishes information on the following EBS entities to the external billing applications:

• New Account

• Account Update

• Item/Product

• Sales Order

• Grouped Sales Order

Publishing New Account Details

Account information is maintained in Oracle Trading Community Architecture (TCA) and is published to the external billing application only when an order is booked for the first time for an account.

For more information, see Integrating Workflow Process for Publishing Account Information, page 3-16 and Message Specifications for Account, page D-7.

Publishing Account Update Details

Introduction to Telecommunications Billing Integrator 1-3

TBI subscribes to a set of TCA events related to account updates. TBI generates and publishes an account message to the billing system when changes relevant to the billing system are made to accounts in TCA.

The updated information is marked in the message. For example: If the credit classification information of an account (relevant to the billing system) is changed in TCA, TBI publishes the account message with the Credit Classification section marked as "U" (Updated).

If multiple changes are made to an account in TCA, TBI publishes multiple account messages.

For more information, see Subscribing to Account Update Events, page 3-21 and Message Specifications for Account, page D-7.

Publishing Item/Product Details

TBI provides a concurrent manager program to synchronize the product catalog in Oracle EBS with the billing system. Synchronization helps in maintaining accurate pricing and billing information. To synchronize a large number of items between EBS and the billing system, the concurrent program generates an XML or CSV file for all EBS product catalog items that must be uploaded to the billing system. For synchronizing small additions, the concurrent program can generate and asynchronously publish an XML message of items from the EBS product catalog to the billing system.

For more information, see Setting up and Running the Item Publish Concurrent Program, page 3-19 and Message Specifications for Item/Product, page D-30

Publishing Sales Order Details

Sales order information is created and maintained in Oracle Order Management. Sales orders with multiple order lines are created in Oracle Order Management when:

• A new telecommunications service (example: wireless service) is ordered

• New features (example: voice mail) are added to a service

• Changes are made to features (example: number of rings before voice mail is activated)

• Changes (upgrade/downgrade) are made to price packages

• Provisioning actions (example: service is suspended, resumed, moved or disconnected) are performed on an active service.

In the TSO solution, each order line includes a provisioning action, an item (example: service, feature, price package, one-time charge, recurring charge), pricing, address, and other information. The billing system requires all the information in the order. TBI publishes an XML message for each sales order line, to the billing system after each order line is fulfilled (provisioned).

1-4 Oracle Telecommunications Billing Integrator Implementation Guide

The sales order is published after confirming that the account that created the sales order is also published. If the account is published, the sales order flow continues to publish the sales order message. If the account is not published, the account is published before publishing the sales order message.

For more information, see Integrating Workflow Process for Publishing Sales Order Information., page 3-17

Publishing Group Sales Order Message Details

A Group Sales Order message is a consolidated sales order XML message which contains all the order lines published to the third party billing application instead of order lines as individual message. TBI allows you to publish a single message for each line or a single grouped sales order message for all the lines in a sales order. Both of these options are mutually exclusive.

Products Used in TBI

TBI uses the following Oracle applications that provide the underlying technology stack, schema, and structure for TBI.

• Oracle Telecommunications Service Ordering (TSO)

• Oracle Collaboration History

• Oracle Contact Center

• Oracle Workflow Business Systems

• Oracle XML Gateway

• Oracle Advanced Queuing

Enhancements

The enhancements in this release are:

• Creation of a Grouped Sales Order message that includes all the lines of an order.

• Publish Bill-To account information for a sales order.

• Additional TCA events for Account Update Message.

• Enhancements to the Account Message.

• Enhancements to the Sales Order Message.

• Uptake of JMS compliant queues in XML Gateway.

Introduction to Telecommunications Billing Integrator 1-5

Grouped Sales Order Message

This feature provides a single XML message that includes all the lines of an order. This enables the billing system to initiate the billing process for the entire order at the same time. The complete sales order message is grouped by order number and published to the billing application. A single message per order ensures that the dependencies and relationships across order lines are maintained when the message is delivered to the billing system and the billing system can initiate the billing process for the entire order at the same time.

A group sales order message is useful when an order contains different parts or order lines that are provisioned at the same time and the billing also happens at the same time. For example: An order for provisioning Wireless Service, Voice Mail and SMS for an account. These services are activated immediately and do not have a long waiting time. These services also can be billed immediately.

In the earlier version of TBI, three separate messages would have been created for each of the services provided. With group sales order message, billing information for all these three items can be sent in a single message. The group sales order message is generated after all the billable lines in the order have been successfully fulfilled and the products and services on the order are reflected in the customer's installed base.

Group sales order and sales order line messages are mutually

Note:

exclusive.

Publish Bill To Accounts for a Sales Order

The Bill To account (payee account) for each order line is published to the billing application. In the previous release, the bill-to accounts were part of the sales order line message. In this release, the Bill To accounts are published separately as independent account messages.

Additional TCA Events for Account Update Message

The TCA events added to the existing Account Update message are:

• oracle.apps.ar.hz.Person.update: This event is triggered when there are changes to personal information about a person.

• oracle.apps.ar.hz.Organization.update: This event is triggered when there are changes to information related to an organization.

• oracle.apps.ar.hz.CustomerProfile.update: This event is triggered when there are changes to information about the credit characteristics of a single customer account, customer account site or a party.

1-6 Oracle Telecommunications Billing Integrator Implementation Guide

• oracle.apps.ar.hz.ContactPoint.update: This event is triggered when there are changes to information about how to communicate to parties or party sites using electronic media such as Electronic Data Interchange (EDI), e-mail, telephone, telex, and the Internet.

Enhancements to Account Message

The information added to the account message is:

• Customer profile amount for the account.

• Credit classification details of the account.

Obsoleted Billing Preference Events

The Billing Preference Events obsoleted in this release are:

• oracle.apps.ar.hz.BillingPreference.create

• oracle.apps.ar.hz.BillingPreference.update

Obsoleted Billing Preference Information

The billing preference information obsoleted in this release is:

• BILL_DISPATCH_METHOD

• BILL_FORMAT

• BILL_LANGUAGE

• BILL_TYPE

• BILL_CURRENCY

Enhancements to Sales Order Message

The following enhancements have been added to a sales order message:

• Ship To Address of the Order Line: Include Ship To address details like Address (Street, City, County, Zip Code, Country), Contact Name (Salutation, First Name, Middle Name, Last Name), Contact Phone Number (Primary) and Contact E-mail Address (if available) for each order line

• Ship To Contact of the Order Line: Include the Ship to Contact details

Introduction to Telecommunications Billing Integrator 1-7

• Payment Term for the Order Line: Include the payment terms. This information is used to calculate when a payment is due and factor in any discounts that are given for early payment.

• Periodicity Details of the Order Line: Include periodicity details to indicate how often a service is charged.

Uptake of JMS Compliant Queues in XML Gateway

XML Gateway generates XML messages in JMS format. There are two new JMS enabled AQs: WF_JMS_OUT and WF_JMS_IN that can be setup to directly process outbound and inbound JMS messages.

In outbound transactions, XML Gateway generates the XML message directly in the JMS format and enqueues the messages onto the queue WF_JMS_OUT. The middleware should be configured to connect to the WF_JMS_OUT queue so that it can dequeue the message and utilize it for further processing.

The Inbound transaction is similar to the outbound transaction. The Middleware enqueues the message onto WF_JMS_IN, which is the inbound AQ provided by XML Gateway. The XML Gateway dequeues this message and processes it.

1-8 Oracle Telecommunications Billing Integrator Implementation Guide

Implementing Telecommunications Billing

Integrator

This chapter lists the implementation considerations for TBI.

This chapter covers the following topics:

• Implementation Considerations

• TBI with TSO

• Middleware in TBI

• External Billing Applications

Implementation Considerations

TBI with TSO

Consider the following implementation points before implementing Oracle TBI:

• TBI with TSO, page 2-1

• Middleware in TBI, page 2-2

• External Billing Applications, page 2-2

Oracle TBI depends on the Oracle Telecommunications Service Ordering (TSO) solution.

The TSO solution leverages multiple components of the Oracle EBS to enable telecommunications service providers to order new telecommunications services for their customers and to order updates to existing telecommunications service configurations. All products, accounts, and orders for telecommunications services captured in EBS are synchronized with the third party billing system(s) that rate and generate bills for the services ordered.

Implementing Telecommunications Billing Integrator  2-1

Refer Oracle Telecommunications Service Ordering Process Guide for details.

Middleware in TBI

TBI integrates with any middleware that has a native AQ or JMS adapter. TBI has been tested and certified with Oracle Applications InterConnect (OAI 9.0.4). For details, see Configuring the Middleware., page 3-23

External Billing Applications

TBI provides a robust two-way integration which enables exchange of information between Oracle E-Business Suite and the external billing applications.

Routing rules in the middleware allow integration with multiple heterogeneous billing applications. Middleware tracks the billing applications and the E-Business Suite communicates with the middleware.

2-2 Oracle Telecommunications Billing Integrator Implementation Guide

Implementation Tasks for Oracle

Telecommunications Billing Integrator

This chapter discusses the tasks to implement Oracle Telecommunications Billing Integrator.

This chapter covers the following topics:

• Implementation Tasks

• Setting Up XML Gateway

• Defining XML Gateway Profile Values

• Defining UTL_FILE_DIR Parameters

• Defining XML Standards

• Defining a Hub

• Defining Hub Users

• Defining Transactions

• Internal and External Transactions in XML Gateway

• Transactions Enabled for TBI

• Defining Trading Partners

• Setting Up Oracle Collaboration History

• Defining Collaboration History Profile Values

• Defining Lookup Values for Collaboration

• Setting Up Collaboration Events

• Setting up the Final Collaboration Event

• Checking Status of Agent Listeners

• Setting Up Bill Summary UI

• Defining Bill Summary UI Profile Options

Implementation Tasks for Oracle Telecommunications Billing Integrator 3-1

• Providing Access and Enabling the Bill Summary UI

• Personalizing Oracle Contact Center for TBI

• Accessing the Bill Summary UI from Oracle Contact Center

• Loading Bill Summary Data

• Integration with Order Management Workflow Processes

• Integrating Workflow Process for Publishing Account Information

• Integrating Workflow Process for Publishing Sales Order Information

• Defining Sales Order Line Profile Option

• Creating the Workflow Function

• Integrating Workflow Process for Publishing Group Sales Order Information

• Setting Up and Running the Item Publish Concurrent Program

• Item Batch Export Profile Values

• Submitting the Item Publish Request

• Subscribing to Account Update Events

• Supported Events

• Configuring the Middleware

Implementation Tasks

Implementing Oracle TBI involves the following:

Setting Up XML Gateway, page 3-3

2. Setting Up Collaboration History, page 3-10

3. Starting Agent Listeners, page 3-13

Setting Up Bill Summary UI, page 3-13

5. Integration with Order Management Workflow Processes, page 3-16

Setting Up and Running the Item Publish Concurrent Program, page 3-19

7. Subscribing to Account Update Events, page 3-21

Configuring the Middleware, page 3-23

Setting up Profile Values

To set up profile values in TBI, select the TBI administrator responsibility.

3-2 Oracle Telecommunications Billing Integrator Implementation Guide

Navigation: TBI setup > profile system values.

Notes

Unless otherwise mentioned, use the TBI administrator responsibility to complete the setups mentioned in this chapter.

Setting Up XML Gateway

You must have the TBI Administrator responsibility to access Oracle XML Gateway database and forms. Setting up XML Gateway or TBI involves the following:

1. Defining XML Gateway Profile Values, page 3-3

Defining UTL_FILE_DIR Parameters, page 3-3

3. Defining XML Standards, page 3-4

4. Defining a Hub, page 3-4

5. Defining Transactions, page 3-5

6. Defining Trading Partners, page 3-10

Defining XML Gateway Profile Values

To set the profile options, login to Oracle Forms with the System Administrator responsibility.

Navigation: TBI Setup > Profile System Values

For details on the XML gateway profile values to be set, refer Oracle XML Gateway

User's Guide.

Defining UTL_FILE_DIR Parameters

Oracle XML Gateway uses the UTL_FILE package to read and write to the server. To use Oracle XML Gateway, create folders to store the XML message process logs and the XSLT style sheets.

Use the utl_file_dir parameter in the $ORACLE_HOME/dbs/init<SID>.ora file to define folders. Each folder is indicated as ''utl_file_dir = directory_name'' in this file. The folder name must be the same as the value defined for the Oracle XML Gateway profile ECX_UTL_LOG_DIR file path (ECX:Log File Path).

For details, refer Oracle XML Gateway User's Guide.

Implementation Tasks for Oracle Telecommunications Billing Integrator 3-3

Defining XML Standards

Define Open Applications Group (OAG) as the XML standard.

Navigation: Oracle XML Gateway Setup > Define XML Standards.

Notes

Standard Code: This is the name or code for the standard body of the XML messages.

Enter 'OAG'

Standard Type: Enter 'XML'.

Defining a Hub

A hub is defined as an integration point within your network.

Navigation: Oracle XML Gateway Setup > Define Hubs.

Notes

Name: Enter 'XNB_HUB'.

Protocol Type: Select JMS. This value identifies the type of messages that are passed

through the hub and provides a method for inbound and outbound agent listeners to filter the messages from a common queue. If this value is not available in the LOV, it must be enabled for the XML Gateway. To enable the values:

1. Select XML Gateway Setup > Define Lookup Values.

2. Query for the lookup type 'COMM_METHOD'.

3. Locate the lookup value with code 'JMS' and enable it.

Protocol Address: Enter 'WF_JMS_OUT'. This is the outbound queue to process outbound transactions.

Defining Hub Users

A hub user represents an application that takes part in the message exchange.

To define middleware as a hub user, enter XNB as the user name and the hub entity code.

To define the billing application as a hub user, enter the name of the billing application as the user name and hub entity code.

Note:

Middleware should be configured accordingly, so that it picks up the outbound messages from WF_JMS_OUT and enqueues the inbound messages to WF_JMS_IN.

3-4 Oracle Telecommunications Billing Integrator Implementation Guide

• The names representing the billing applications setup in the hub

• Hub entity code values for the various billing applications must be

Defining Transactions

Internal transactions are used by the XML Gateway Execution Engine. Internal transactions are associated with the trading partner in the trading partner setup. Each internal transaction is associated with a number of external transactions that participate in the integration.

For more information about defining transactions, see the Oracle XML Gateway User's

Guide.

Navigation: Oracle XML Gateway Setup > Define Transactions.

Notes

Queue: The standard inbound queue used in TBI is APPS.ECX_IN_OAG_IN. The field

is disabled for outbound messages. Default queues are defined during installation.

must be unique.

same as the key value from BSR.SENDER.COMPONENT.

Standard Code: Select 'OAG'.

Transaction Type: This is the product short name for the base Oracle Application. Enter

'XNB', which is the product short code for TBI.

Transaction Subtype: This refers to particular transaction within the application specified by the Transaction Type. The last letter of the code represents the direction of the transaction, that is, "I" for inbound and "O" for outbound. The combination of the Transaction Type and the Transaction Subtype identifies an Oracle transaction with which the message is associated.

External Transaction Type: Enter a primary external identifier for the XML message.

External Transaction Subtype: Enter a secondary external identifier for the XML

message.

Internal and External Transactions in XML Gateway

The following internal transactions have associated external transactions in XML Gateway:

• Account Outbound, page 3-6

• Sales Order Outbound, page 3-6

• Group Sales Order Outbound, page 3-7

Implementation Tasks for Oracle Telecommunications Billing Integrator 3-5

• Inventory Item Outbound, page 3-8

• Confirm BOD Inbound, page 3-8

Account Outbound Internal Transaction

The following table lists the attributes and values for the account outbound transaction.

Account Outbound Transaction Values

Attribute Value

Party Type Customer

Transaction Type XNB

Transaction Subtype AO

Transaction Description XNB TCA Account Outbound

External Transactions for Account Outbound

The following table lists the details of the external transactions for account outbound message.

External Transactions for Account Outbound

STD CODE DIR EXT. TXN.

TYPE

OAG OUT ACCOUNT SYNC -

EXT. TXN. SUBTYPE

QUEUE

Internal Transaction for Sales Order Outbound

Sales Order Outbound

Attribute Value

Party Type Customer

Transaction Type XNB

3-6 Oracle Telecommunications Billing Integrator Implementation Guide

+ 80 hidden pages

Sonic Alert B31540-02 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Preface

Telecommunications Billing Integrator Overview

Telecommunications Billing Integrator Features

Publishing Information to the Billing Applications

Products Used in TBI

Enhancements

Grouped Sales Order Message

Publish Bill To Accounts for a Sales Order

Additional TCA Events for Account Update Message

Enhancements to Account Message

Enhancements to Sales Order Message

Uptake of JMS Compliant Queues in XML Gateway

Implementation Considerations

TBI with TSO

Middleware in TBI

External Billing Applications

Implementation Tasks

Setting Up XML Gateway

Defining XML Gateway Profile Values

Defining UTL_FILE_DIR Parameters

Defining XML Standards

Defining a Hub

Defining Hub Users

Defining Transactions

Internal and External Transactions in XML Gateway