Home

Sonic Alert B31540-02 User's Manual

Contents

1. lt REFERENCEID gt C12X4MST US ORACLE COM oracle apps xnb salesorder create XN B SALESORDER LINE 43125 294654 lt REFERENCEID gt lt CONFIRMATION gt 2 lt CONFIRMATION gt lt LANGUAGE gt US lt LANGUAGE gt lt CODEPAGE gt UTF8 lt CODEPAGE gt lt AUTHID gt APPS lt AUTHID gt lt SENDER gt lt DATETIME qualifier CREATION gt lt YEAR gt 2005 lt YEAR gt lt MONTH gt 01 lt MONTH gt lt DAY gt 04 lt DAY gt lt HOUR gt 21 lt HOUR gt lt MINUTE gt 06 lt MINUTI ti V D 6 Oracle Telecommunications Billing Integrator Implementation Guide lt SECOND gt 06 lt SECO lt SUBSECON lt TIMEZONE lt CNTRO D gt D gt 0000 lt SUBSECO gt D gt 0000 lt TIMEZONE gt lt DATE m IME gt AREA STATUS iV gt 00 lt STATUSLVL gt lt DESCRI lt CONFIRM gt PT lt CONFIR lt DATAAREA gt lt CONFIRM BOD 004 gt Seeded XML Messages gt THE BOD WAS BOD gt PROCE SS ED SUCCESSFULLY lt DESCRIPTN gt TBI provides seeded XML messages for the following e Account information e Sales order information e tem information e GSO Message Specifications for Account Information The following table lists the message specificat
2. HubDB TNS Name Importing OAI Maps to the Repository Seeded integration maps are provided as database export files This metadata must be imported into an existing OAI 9 0 4 hub repository Before importing the OAI maps to the repository you must drop the existing Hub Schema Use this procedure to import an OAI map 1 Run the following script at the command prompt OAI HOM E oai 9 0 4 repository oaiimport lt IntegrationMap file gt hub user name gt system lt system_user pwd hub user pwd gt lt HubDB T S Name Note The values are hub user name Hub schema owner user name Default is oaihub904 IntegrationMap file The path to the database export file containing the map HubDB TNS Name The TNS entry for the database If the repository service stops run the following script to start the repository service OAI HOMI E oai 9 0 4 repository start If the adapter service stops run the following script from the console to start the adapter service OAI HOMI E gt oai 9 0 4 adapters lt ADAPTER NAME gt start Configuring Oracle Applications InterConnect A 5 B APIs in Telecommunications Billing Integrator This appendix provides information on the APIs in TBI This appendix covers the following topics e Bill Summary Bulk Insert APIs e Procedure INSERT ROW BATCH e Procedure UPDATE ROW BATCH e Bill Summary Public Table Type BILL SUMMARI
3. 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 Preface 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 e The principles and customary practices of your business area e Oracle Telecommunications Billing Integrator e Oracle XML Gateway To learn more about Oracle XML Gateway see the Oracle XML Gateway User s Guide e Oracle Workflow T
4. CITY COUNTRY COUNTY STATEPROVN POSTALCODE CUST PROFILE AM TS INFO CUST ACCT PROFI LE AMT ID CURRENCY CODE AMOUNT ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS DATAAREA CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CONTACT HZ_LOCATIONS AD DRESS1 HZ_LOCATI ONS ADDRESSZ HZ LOCATIONS ADDRE S53 HZ LOCATIONS ADDRESS4 HZ_LOCATIONS CI TY HZ LOCATIONS CO UNTRY HZ LOCATIONS CO UNTY HZ LOCATIONS ST ATE HZ LOCATIONS POSTAL CODE Customer Profile Amounts Information HZ CUST PROFILE AMTS CUST ACCT PROFI LE AMT ID HZ CUST PROFILE AMTS CURRENCY CODE HZ CUST PROFILE AMTS TRX CREDIT LIMIT Bill To Address Line of the Account City Country County State Postalcode Profile Amount Identifier Currency code Transaction Credit Limit XML Messages in TBI D 17 AMOUNT AMOUNT AMOUNT MAX INTEREST CH ARGE AMOUNT AMOUNT INTEREST RATE AMOUNT AMOUNT CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO HZ CUST PROFILE AMTS OVERALL CREDIT LIMIT HZ CUST PROFILE AMTS MIN DUNNING A MOUNT HZ CUST PROFILE AMTS MIN DUNNING IN VOICE AMOUNT HZ CUST PROFILE AMT
5. INVENTORY ITEM ID MTL SYSTEM ITEM S_VL SEGMENT1 MTL_SYSTEM_ITEM S_VL ITEM_TYPE FND_LOOKUP_VAL UES_VL MEANING MTL_SYSTEM_ITEM S_VL BOM_ITEM_TYPE MFG_LOOKUPS ME ANING MTL_SYSTEM_ITEM S_VL PRIMARY_UNIT_OF _MEASURE MTL_SYSTEM_ITEM S_VL DESCRIPTION MTL_SYSTEM_ITEM S_VL INVENTORY_ITEM_ STATUS_CODE MTL_ITEM_STATUS DESCRIPTION Description EBS Inventory Item Identifier EBS Inventory item Inventory Item Type Inventory Item Type Description E Business Suite BOM item type code E Business Suite BOM item type description Primary Unit of Measure for the item in inventory Item Product description Inventory Item status code Inventory Item status description XML Messages in TBI D 31 DATETIME ITEM INFO DATETIME ITEM INFO ITEM CLASS ITEM INFO ATTRIBUTEI to ITEM INFO ATTRIBUTEI5 MTL SYSTEM ITEM S VL START DATE ACTI VE MTL SYSTEM ITEM S VL END DATE ACTIVE MTL SYSTEM ITEM S VL PRIMARY UOM CO DE MTL SYSTEM ITEM S VL ATTRIBUTE1 to ATTRIBUTE15 Start date for the item End date for the item Derive from the UOM CLASS As this is not stored in any entity and it is derived from UOM we need to know all the distinct values of UOM Descriptive Flexfield segment for Item Message Specifications For Group Sales Order Line The following table lists the message specifications for Group Sales Order Line Message Specifications for Group S
6. QUANTITY QUANTITY INVOICE TO ORG I D ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO MTL SYSTEM ITEM S_VL SEGMENT1 MTL_SYSTEM_ITEM S_VL DESCRIPTION OE_ORDER_LINES_ ALL ORG_ID OE_ORDER_LINES_ ALL PRICING_DATE OE_ORDER_LINES_ ALL UNIT_SELLING_PRI CE OE_ORDER_LINES_ ALL UNIT_LIST_PRICE OE_ORDER_LINES_ ALL ORDERED_QUANTI TY OE_ORDER_LINES_ ALL PRICING_QUANTIT Y OE_ORDER_LINES_ ALL INVOICE_TO_ORG I D Name of the Product Description of the Product Operating Unit which performed this transaction Determines effective list and price modifiers Actual price charged to customer Price List price for the item Quantity Ordered Quantity based on pricing unit of measure Invoice To Organization ID D 22 Oracle Telecommunications Billing Integrator Implementation Guide SHIP TO ORG ID ACTION CURRENCY CODE CHARGE PERIODIC ITY CODE CHARGE PERIODIC ITY CODE DESC ADDRESS ADDRLINE CITY COUNTRY COUNTY ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ADDRESS ADDRESS ADDRESS ADDRESS OE ORDER LINES ALL SHIP TO ORG ID OE TRANSACTION TYPES TL ACTION OP LIST HEADERS VL CURRENCY CO DE OE ORDER LINES ALL CHARGE PERI ODICITY CODE MTL UOM CONVE RSIONS
7. Implementation Considerations ssssssssssssse eee eene 2 1 IBILwith ESQ cete Rt eri ete e Ed uh cones eb op ER Mina dede Ts aan 2 1 Middleware in BI itecto netiis fue intret Dh deci ic rst a aiarad 2 2 External Billing Applications e retten ie tdt Dg d e ra e LX ea uan 2 2 3 Implementation Tasks for Oracle Telecommunications Billing Integrator Implementation Tasks cnet eti et rire b d eb e n dne adn 3 2 Setting Up XML Gateway beu ete bd de aee eer repe reete peces 3 3 Defining XML Gateway Profile Values sss ee 3 3 Defining UTL FILE DIR Parameters nnne 3 3 Defining XML Standards niit eie ilti til t tied det a Ene Padre ids 3 4 Defining H b afry nennen eee ete aset eee 3 4 Defining Hub Users netu duae e tede dts 3 4 Defining Transacthoris eden e epe e re OG Rer eR e teal dd ad 3 5 Internal and External Transactions in XML Gateway eee 3 5 Transactions Enabled for TBL sssssssssssssss eene nennen nennen 3 9 Defining Trading Partners pe pe egere teet etta a e aea 3 10 Setting Up Oracle Collaboration History sssssssssseeee eee 3 10 Defining Collaboration History Profile Values 3 11 Defining Lookup Values for Collaboration e em 3 11 Setting Up Collaboration Events sss eee eem enne nns 3 12 Setting up the Final Collaboration Event ccc ee ee ee reece eee 3 12 Checking Stat
8. Tax code that this exemption applies to Percentage that is exempt from tax Exemption certificate number Last date that this exemption is effective XML Messages in TBI D 9 DATETIME REASON CODE EXEMPT_PERCENT1 EXEMPT_PERCENT2 EXEMPT PERCENTS3 EXEMPT_PERCENT4 RECEIPT_METHODS CUST_RECEIPT_ME THOD _ID RECEIPT_METHOD_ ID TAX_EXEMPTIONS TAX_EXEMPTIONS TAX_EXEMPTIONS TAX_EXEMPTIONS TAX_EXEMPTIONS TAX_EXEMPTIONS DATAAREA RECEIPT_METHODS RECEIPT_METHODS RA_TAX_EXEMPTIO NS_ALL START_DATE RA_TAX_EXEMPTIO NS_ALL REASON_CODE RA_TAX_EXEMPTIO NS_ALL EXEMPT_PERCENT1 RA_TAX_EXEMPTIO NS_ALL EXEMPT_PERCENT2 RA_TAX_EXEMPTIO NS_ALL EXEMPT_PERCENT3 RA_TAX_EXEMPTIO NS_ALL EXEMPT_PERCENT4 Various Receipt Methods RA_CUST_RECEIPT_ METHODS CUST_RE CEIPT_METHOD_ID RA_CUST_RECEIPT_ METHODS RECEIPT _METHOD_ID First date that this exemption is effective The reason for this exemption Percentage of the exemption to apply to this portion of the Sales Tax Location Flexfield Percentage of the exemption to apply to this portion of the Sales Tax Location Flexfield Percentage of the exemption to apply to this portion of the Sales Tax Location Flexfield Percentage of the exemption to apply to this portion of the Sales Tax Location Flexfield Uniquely identifies the customer receipt method Identifies the receipt method identif
9. lt BSR gt lt VERB value CONFIRM gt CONFIRM lt VERB gt lt NOUN value BOD gt BOD lt NOUN gt lt REVISION value 004 gt 004 lt REVISION gt lt BSR gt lt SENDER gt lt LOGICALID gt NO_VALUE SNDR lt LOGICALID gt COMPONENT BILLAPP 1 COMPONENT lt TASK gt CONFIRM lt TASK gt lt REFERENCEID gt NO_ VALUE REF lt REFERENCEID gt lt CONFIRMATION gt 0 lt CONFIRMATION gt lt LANGUAGE gt en lt LANGUAGE gt lt CODEPAGE gt ISO 8859 1 lt CODEPAGE gt lt AUTHID gt NO_VALUE AUTHID lt AUTHID gt lt SENDER gt lt DATETIME qualifier CREATION gt lt YEAR gt 2004 lt YEAR gt lt MONTH gt 05 lt MONTH gt lt DAY gt 12 lt DAY gt lt HOUR gt 11 lt HOUR gt lt MINUTE gt 12 lt MINUTE gt lt SECOND gt 39 lt SECOND gt lt SUBSECOND gt 1010 lt SUBSECOND gt lt TIMEZONE gt 0000 lt TIMEZONE gt lt DATETIME gt lt CNTROLAREA gt lt DATAAREA gt lt CONFIRM BOD gt lt CONFIRM gt lt CNTROLAREA gt lt BSR gt lt VERB value ADD gt ADD lt VERB gt lt NOUN value ACCOUNT gt ACCOUNT lt NOUN gt lt REVISION value 001 gt 001 lt REVISION gt lt BSR gt lt SENDER gt lt LOGICALID gt ORACLE lt LOGICALID gt lt COMPONENT gt XNB lt COMPONENT gt lt TASK gt AAO lt TASK gt
10. Either a forward or a backward relationship code Date relationship ends Identifier for the customer contact point Lookup CONTACT POINT T YPE of phone fax e mail web telex or EDI Flag to Identify the Primary Contact Information ANSI standard code for EDI transaction type EDI trading partner number for the supplier site Indicates how a payment is to be made through EDI Valid methods are ACH and BOP D 14 Oracle Telecommunications Billing Integrator Implementation Guide EDI PAYMENT FOR MAT EMAIL ADDRESS URL PHONE LINE TYPE PHONE NUMBER PHONE COUNTRY CODE PHONE AREA COD E PHONE EXTENSIO N CUSTOMER CONT ACT INFO CUSTOMER CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO HZ_CONTACT_POI NTS EDI PAYMENT FORMAT HZ CONTACT POI NTS EMAIL ADDRE SS HZ CONTACT POI NTS URL HZ CONTACT POI NTS PHONE LINE TYPE HZ CONTACT POI NTS PHONE NUMB ER HZ CONTACT POI NTS PHONE COUN TRY CODE HZ CONTACT POI NTS PHONE AREA CODE HZ CONTACT POI NTS PHONE AREA CODE Indicates type of information being transmitted with the funds if using EDI PAYMENT ME THOD ACH Valid values are CCD CCP CHZ CTX PPD and PPP E mail address of the contact point Uniform resource locator Lookup code for the
11. RA TERMS VL DES NFO CRIPTION D 36 Oracle Telecommunications Billing Integrator Implementation Guide County State Postalcode Tax code for the line The tax rate in percentage It will store the date for tax calculation The Tax amount in order currency Payment Term Identifier Payment Term Name Payment Term Description EXT ATTRIBUTES ATTRIBUTEI to ATTRIBUTEI5 INSTALL BASE INF O INSTANCE_ID INSTANCE_NAME DATETIME DATETIME DATETIME QUANTITY INSTALL_LOCATIO N_ID ORDER_LINE_INFO EXT_ATTRIBUTES ORDER_LINE INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O Order Line Extended Attributes OE_ORDER_LINES_ ALL ATTRIBUTE1 INSTALL BASE INF O CSI ITEM INSTANC ES INSTANCE ID CSI ITEM INSTANC ES INSTANCE DESC RIPTION CSI ITEM INSTANC ES INSTALL DATE CSI ITEM INSTANC ES ACTIVE START DA TE CSI ITEM INSTANC ES ACTIVE END DATE CSI ITEM INSTANC ES QUANTITY CSI ITEM INSTANC ES INSTALL LOCATIO N ID Descriptive Flexfield segment for Order Line Unique ID that identifies an item unit instance Used to describe the Instance Id Installation Date for an Instance Activation Start Date Activation End Date Quantity Install Location Identifier XML Messages in TBI D 37 LAST OE ORDER L INE ID ADDRESS ATT
12. S VALUE_INFO VALUE_INFO VALUE_INFO VALUE_INFO ORDER_LINE CSI I EXTENDED A TTRIBS ATTRIBUTE NAME CSI I EXTENDED A TTRIBS ATTRIBUTE CATEGORY CSI I EXTENDED A TTRIBS DESCRIPTIO N CSI I EXTENDED A TTRIBS ACTIVE STA RT DATE CSI I EXTENDED A TTRIBS ACTIVE EN D DATE CSI I EXTENDED A TTRIBS SECURITY G ROUP ID Value Information CSI IEA VALUES A TTRIBUTE VALUE I D CSI IEA VALUES A TTRIBUTE VALUE CSI IEA VALUES A CTIVE START DAT E CSI IEA VALUES A CTIVE END DATE BILL TO PARTY IN FO Attribute Name Attribute Category Description Activation Start Date Activation End Date Security Group Identifier Instance Extended Attribute Value Identifier Instance Extended Attribute Value Activation Start Date Activation End Date XML Messages in TBI D 39 BILL TO OWNER F LAG PRIMARY BILL TO BILL TO PARTY IN FO BILL TO PARTY IN FLAG BILL TO PARTY N UMBER BILL TO PARTY N AME BILL TO ACCOUNT NUMBER BILL TO ACCOUNT _NAME ADDRESS ADDRLINE CITY COUNTRY COUNTY FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO ADDRESS ADDRESS ADDRESS ADDRESS HZ_PARTIES BILL_T O_OWNER_FLAG HZ_PARTIES PRIMA RY_BILL_TO_FLAG HZ_PARTIES PARTY _NUMBER HZ_PARTIES PARTY _NAME HZ_CUST_ACCOUN TS ACCOUNT_NUMBE R HZ_CUST_ACCOUN TS ACCOUNT_NAME Bill T
13. repository metadata Configuring OAI as the middleware for TBI involves 1 Setting Up OAI Hub page A 2 2 Setting up OAI Adapter for Advanced Queues page A 3 3 Dropping the Hub Schema page A 4 Configuring Oracle Applications InterConnect A 1 4 Importing OAI maps to the Repository page A 5 Setting Up OAI Hub Use this procedure to set up the OAI hub 1 Choose the hub machine 2 Install Oracle 9iR2 database version 9 2 0 2 1 or higher on the hub machine Use Oracle Database Configuration Assistant to create an empty database instance to serve as the hub repository Set the following parameters e HOST SID PORT information for the new database instance e Passwords for system and users for the new database instance e TNS name entry for the new database instance 3 Install Oracle Applications InterConnect Hub version 9 0 4 0 1 on the hub machine The OAI Hub must be installed in a separate Oracle Home Provide the following details e Hub DB Parameters Provide the Host Port SID information e Schema Names Default name for the OAI hub repository schema is oaihub904 4 Provide the following schema details e Schema Oaihub904 owf mgr e Schema User Name oaihub904 Owf mgr e Password hub user password workflow user password 5 Tocreate database objects in the hub schema change folder to OAI_HOME oai 9 0 4 repository 6 Run the following command hubschema create system lt system_user_pwd g
14. ADDRESS ADDRESS OE ORDER LINES ALL INVOICE TO ORG I D OE ORDER LINES ALL SHIP TO ORG ID OE TRANSACTION TYPES TL ACTION OP LIST HEADERS VL CURRENCY CO DE OE ORDER LINES ALL CHARGE PERI ODICITY CODE MTL UOM CONVE RSIONS UNIT OF M EASURE OE ORDER LINES ALL SHIP TO ORG ID CONCAT HZ LOCATIONS AD DRESSI HZ LOCATI ONS ADDRESSZ HZ LOCATIONS ADDRE S53 HZ LOCATIONS ADDRESS4 HZ_LOCATIONS CI TY HZ LOCATIONS CO UNTRY Invoice To Organization ID Ship To Organization ID Type of Service performed on the Order Currency Code Charge Periodicity Code Charge Periodicity Code Description Ship To Address Ship To Address Line of the Account City Country XML Messages in TBI D 35 COUNTY STATEPROVN POSTALCODE TAX INFO TAX CODE TAX RATE DATETIME AMOUNT PAYMENT TERM I NFO PAYMENT TERM I D PAYMENT TERM N AME DESCRIPTION ADDRESS ADDRESS ADDRESS ORDER LINE INFO TAX INFO TAX INFO TAX INFO TAX INFO ORDER LINE INFO PAYMENT TERM I HZ LOCATIONS CO UNTY HZ LOCATIONS ST ATE HZ LOCATIONS POSTAL CODE Tax Information OE ORDER LINES _ ALL TAX CODE OE ORDER LINES _ ALL TAX RATE OE ORDER LINES _ ALL TAX DATE OE ORDER LINES ALL TAX VALUE Payment term Information OE ORDER LINES NFO PAYMENT TERM I ALL PAYMENT TER M ID RA TERMS VL NA NFO PAYMENT TERM I ME
15. ATTRIBUTE INFO ATTRIBUTE INFO CSI ITEM INSTANC ES LAST OE ORDER L INE ID CSI ITEM INSTANC ES INSTALL AT ADDR ESS Attribute Value Pairs of Install Base Attribute Information CSI I EXTENDED A TTRIBS ATTRIBUTE ID CSI I EXTENDED A TTRIBS ATTRIBUTE LEVEL CSI I EXTENDED A TTRIBS MASTER OR GANIZATION ID CSI I EXTENDED A TTRIBS INVENTORY _ITEM_ID CSI I EXTENDED A TTRIBS ITEM CATE GORY ID CSI I EXTENDED A TTRIBS ATTRIBUTE CODE Last Order Line Identifier that touched the instance Install At Address Attribute Identifier Attribute Level Master Organization Identifier Inventory Item Identifier Item Category Identifier Attribute Code D 26 Oracle Telecommunications Billing Integrator Implementation Guide ATTRIBUTE NAME ATTRIBUTE CATEG ORY DESCRIPTION ACTIVE START DA TE ACTIVE END DATE SECURITY GROUP ID VALUE INFO ATTRIBUTE VALUE ID ATTRIBUTE VALUE ACTIVE START DA TE ACTIVE END DATE BILL TO PARTY IN FO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE VALUE S VALUE_INFO VALUE_INFO VALUE_INFO VALUE_INFO DATAAREA CSI I EXTENDED A TTRIBS ATTRIBUTE NAME CSI I EXTENDED A TTRIBS ATTRIBUTE CATEGORY CSI I EXTENDED A TTRIBS DESCRIPTIO N CSI I EXTENDED A TTRIBS ACTIVE STA RT DATE CSI I EXTENDED A TTRIBS ACTIVE EN D DATE CSI I EXTENDED A
16. 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
17. CLN Debug Level 3 CLN Debug Log Directory Defining Lookup Values for Collaboration Lookup values are used to integrate XML Gateway with the Supply Chain Trading Connector to enable Collaboration History Tracking Use the applications Developer responsibility to define the lookup values Navigation Application Lookups Application Object Library Notes The following table lists the lookup values Lookup Types Lookup Type Lookup Code Description Enable d CLN APPLICATION ID 881 Oracle Y Telecommunications Billing Integrator CLN COLLABORATION XNB ITEM TBI Item Y TYPE Implementation Tasks for Oracle Telecommunications Billing Integrator 3 11 Lookup Type Lookup Code Description Enable d CLN COLLABORATION XNB ACCOUNT TBI Account Y TYPE CLN COLLABORATION XNB SALESORDER TBI Sales Order Y TYPE CLN COLLABORATION XNB SYNC ITEM TBI Sync Item Y DOC TYPE CLN COLLABORATION XNB SYNC ACCOUNT TBI Sync Account Y DOC TYPE CLN COLLABORATION XNB ADD SALESORDE TBI Add Sales Order Y DOC TYPE R Note After updating the lookup values bounce the Apache server on the environment only if the values are not reflected in the Collaboration Setup UI Setting Up Collaboration Events A Collaboration Event represents a system component acting on information in a message or XML Payload Navigation Workflow Administrator Collaboration Monitor SetUp Collaboration Event Definition Notes Applicat
18. Transaction Subtype GSOO Transaction Description XNB OM Group Sales Order Outbound External Transactions for Group Sales Order Outbound External Transactions for Group Sales Order Outbound STD CODE DIR EXT TXN EXT TXN QUEUE TYPE SUBTYPE OAG OUT GRP SALESOR ADD DER Internal Transacations for Inventory Item Outbound Implementation Tasks for Oracle Telecommunications Billing Integrator 3 7 Inventory Item Outbound Attribute Value Party Type Customer Transaction Type XNB Transaction Subtype IO Transaction Description XNB Inventory Item Outbound External Transactions for Inventory Item Outbound External Transactions for Inventory Item Outbound STD CODE DIR EXT TXN EXT TXN QUEUE TYPE SUBTYPE OAG OUT ITEM SYNC Internal Transaction for Confirm BOD Inbound Confirm BOD Inbound Attribute Value Party Type Customer Transaction Type XNB Transaction Subtype CBODI Transaction Description XNB Confirm BOD Inbound External Transactions for Confirm BOD Inbound 3 8 Oracle Telecommunications Billing Integrator Implementation Guide External Transactions for Confirm BOD Inbound STD CODE OAG DIR EXT TXN TYPE EXT TXN IN BOD SUBTYPE CONFIRM QUEUE APPS ECX IN OAG Q Transactions Enabled for TBI The following table lists the transactions enabled for TBI A XNB CBODI transaction must be enabled for each hub user representing a billing application with the c
19. Workflow Processes Oracle TBI works in conjunction with the following Order Management Workflow processes e XNBFLOWS ACCOUNT PROCESS Publishes new account information The XNBFLOWS SALES ORDER PROCESS Publishes the sales order line information e XNBFLOWS GROUP SALESORDER PUBLISH Publishes the Group Sales Order information Integrating Workflow Process for Publishing Account Information When an order is created for a new account an account that has not been published to the billing system in Order Management the Order Management header flow uses the Business Event System to trigger the TBI account publish process The TBI account publish process generates the XML and loads it into the AQ You must create the workflow function for publishing accounts The figure below shows the workflow process for publishing account information 3 16 Oracle Telecommunications Billing Integrator Implementation Guide Workflow Process for Publishing Account Information TBI Group S alesorder Publish Defaulb Defaut amp a Enter Book Order Service Fulilment TBI Close Order End Manual Order Navigation In WorkFlow Builder open the OM Order Header OEOH workflow Notes Enter the following parameters e Internal Name XNB ACCOUNT PUBLISH e Display Name XNB Account Publish e Function Name xnb cmn pvt publish account info Integrating Workflow Process for Publishing Sales Order Information When an orde
20. a bracket or brace Accessibility of Links to External Web Sites in Documentation Structure 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 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 OATI 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
21. 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 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 Other Implementation Documentation Oracle Workflow Administrator s Guide This guide explains how to complete the setup steps necessary for any Oracle Applications product that includes workflow enabled processes as well as how to monitor the progress of runtime workflow Oracle Workflow Developer s Guide This guide explains how to de
22. 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 gt 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 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 e Account Outbound pag
23. order currency Payment Term Identifier Payment Term Name Payment Term Description ATTRIBUTEI to ATTRIBUTEI5 INSTALL BASE INF O INSTANCE_ID INSTANCE_NAME DATETIME DATETIME DATETIME QUANTITY INSTALL_LOCATIO N_ID EXT_ATTRIBUTES DATAAREA INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O INSTALL_BASE_INF O OE_ORDER_LINES_ ALL ATTRIBUTEI to ATTRIBUTEI5 INSTALL_BASE_INF O CSI ITEM INSTANC ES INSTANCE ID CSI ITEM INSTANC ES INSTANCE DESC RIPTION CSI ITEM INSTANC ES INSTALL DATE CSI ITEM INSTANC ES ACTIVE START DA TE CSI ITEM INSTANC ES ACTIVE END DATE CSI ITEM INSTANC ES QUANTITY CSI ITEM INSTANC ES INSTALL LOCATIO N ID Descriptive Flexfield segments for Order Line Unique ID that identifies an item unit instance Used to describe the Instance Id Installation Date for an Instance Activation Start Date Activation End Date Quantity Install Location Identifier XML Messages in TBI D 25 LAST OE ORDER L INE ID ADDRESS ATTRIBUTE VALUE 5 ATTRIBUTE INFO ATTRIBUTE ID ATTRIBUTE LEVEL MASTER ORGANIZ A TION ID INVENTORY ITEM ID ITEM CATEGORY I D ATTRIBUTE CODE INSTALL BASE INF O INSTALL_BASE_INF O INSTALL_BASE_INF O ATTRIBUTE_VALUE S ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO
24. point within your network Hub Schema Schema in the database where OAI hub repository resides Hub User Represents an application that takes part in the message exchange JMS Java Message Service JMS API is a messaging standard that allows application components based on the Java 2 Platform Enterprise Edition J2EE to create send receive and read messages OAI Hub Contains all the mapping and transformation data required for integration in its repository OAI Maps Specification for transforming XML message from application view to common view and vice versa Trading Partner Entity that exchanges messages with the XML Gateway Glossary 1 Glossary 2 Transaction Transmission of information between Oracle EBS and Billing application Workflow Function Activity in a workflow process which invokes Pl Sql procedure or function XML Gateway Generates the appropriate xml message based on the specifications provided in the XML gateway map file The message is validated using a DTD XML Gateway places the generated message on the Advanced Queue AQ for further processing XML Payload Data present within the XML message A Agent Listeners list of 3 13 B Billing Preference obsoleted 1 7 Billing Preference event obsoleted 1 7 Bill Summary UI Accessing 3 16 C Collaboration History 3 10 profile values 3 11 F Final Collaboration Event 3 12 G Grouped Sales
25. the Menu Entry list select SpecialXX XX represents the number that is not used by any other entry e Inthe Menu Label field enter Bill Summary e To separate menu items with a line enable Render Line Before Menu Create another function Name the function OA Bill Summary Page or as appropriate Select the Enabled check box to enable the function Select the Conditions Tab and enter the following details Select the Trigger event It must be same as the one specified in the Menu SpecialXX e From the Type list select Builtin e For Builtin Type select Launch a Function Implementation Tasks for Oracle Telecommunications Billing Integrator 3 15 e Inthe Function Code field enter XNB OA ACCT BILL SUMMARY e Inthe Parameters field enter AccountNumber CUSTOMER HEADER BLK CUST ACCOUNT NUMB ER Accessing the Bill Summary UI from Oracle Contact Center To access the Bill Summary UI select an account from Oracle Contact Center From the Tool or More Tools menu select the menu that you had set up in the previous procedure The Bill summary UI appears Loading Bill Summary Data Data must be uploaded at required intervals to the XNB BILL SUMMARIES table for billing details to be displayed accurately in the Bill Summary Load the data at the end of every billing cycle To upload the data call the bill summary APIs Refer Bill Summary Bulk Insert APIs for details page B 1 Integration with Order Management
26. the integrity of your data and you lose the ability to audit changes to your data Because Oracle Applications tables are interrelated any change you make using an Oracle Applications form can update many tables at once But when you modify Oracle Applications data using anything other than Oracle Applications you may change a row in one table without making corresponding changes in related tables If your tables get out of synchronization with each other you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications When you use Oracle Applications to modify your data Oracle Applications automatically checks that your changes are valid Oracle Applications also keeps track of who changes information If you enter information into database tables using database tools you may store invalid information You also lose the ability to track who has changed your information because SQL Plus and other database tools do not keep a record of changes 1 Introduction to Telecommunications Billing Integrator This chapter provides a brief introduction to the features in TBI This chapter covers the following topics 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 Acc
27. type of phone line For example general fax inbound or outbound A telephone number formatted in the local format The number should not include area code country code or extension International country code for a telephone number For example 33 for France The area code within a country code XML Messages in TBI D 15 PARTY GROUP GROUP BANK ACCOUNT I NFO BANK ACCOUNT NUMBER BANK ACCOUNT NAME BANK BRANCH ID CURRENCY CODE ACCOUNT HOLDE R NAME DATETIME BANK NUMBER ADDRESS CUSTOMER CONT ACT _INFO PARTY_GROUP DATAAREA BANK ACCOUNT I Party Group Code AST PARTY CLASSI FICATION V CLASS _CODE Bank Account Information IBY_EXT_BANK_AC NFO BANK ACCOUNT I COUNTS BANK AC COUNT NUM IBY EXT BANK AC NFO BANK ACCOUNT I COUNTS BANK ACCOUNT NAME IBY EXT BANK AC NFO BANK ACCOUNT I COUNTS BRANCH ID IBY EXT BANK AC NFO BANK ACCOUNT I NFO BANK ACCOUNT I COUNTS CURRENCY CODE HZ PARTIES PARTY NAME IBY PMT INSTR US NFO BANK ACCOUNT I NFO DATAAREA ES ALL END DATE HZ ORGANIZATIO N PROFILES BANK OR BRANCH NUMBER Bill To Address Classification code Bank Account Number Bank Account Name Bank Branch Identifier Currency Code Account Holder Name Inactive Date Bank Number D 16 Oracle Telecommunications Billing Integrator Implementation Guide ADDRLINE
28. 2 Configuring the Middleware eee ee tene edt dede der iid a 3 23 A Configuring Oracle Applications InterConnect Oracle Applications InterConnect Overview ssssssssssse eene A 1 Setting Up OALHU b bn eee te ee ehe ien Op ei ende ed pee d pe Poe A 2 Setting up OAI Adapter for Advanced Queues ssssssssssssee eee A 3 Dropping the Hub Schema eiii tre e te ni de RR HER E art a ERR RM au A 4 Importing OAI Maps to the Repository eene ene enne A 5 B APIs in Telecommunications Billing Integrator Bill Summary Bulk Insert APIS iiia aaa ainei anarien Eaa rA nennen enn nnne nnns B 1 Procedure INSERT ROW BATCH aerea arane aana eeina a ad i sss sese sedens B 1 Procedure PDATE ROW BATCGH ete ett eret ede erede tdeo ene B 2 Bill Summary Public Table Type BILL SUMMARIES TABLE L 4 B 3 Bill Summary Public Record Type BILL SUMMARIES REC sese B 3 C Message Maps and DTDs for XML Gateway Maps and DIDS Overvlew teen edi ten metere dae en Ere edi eu tradant a tie apnea C 1 Loading and Deleting Maps cese ee lee toe dr rta Rl a n n ia C 3 Loading and Deleting DIDS ikee eea atanapi eerie meme nennen nennen C 3 D XML Messages in TBI XML Message Overview ic uie ede eed e de en D 1 Outbound and Inbound BOD 1 sss enne nnne D 2 XME Messape Format coetus D 2 Outbound Messages eed ee teret de e ei edi eda eres D 2 In
29. 72 OUT xgm XNB Confirm BOD XNB CLN CBOD OAG72 IN xgm OM Group Sales Order Publish XNB OM GRPSALESORDER OAG72 OUT xgm Note The names of message maps are based on the internal names of the map and have an xgm extension For example the file name for TCA Account Publish Map is XNB TCA ACCOUNT OAG72 OUT xgm DTDs in XML Gateway DTDs in XML Gateway Map Internal Name DTD Root Element XNB TCA ACCTUPDATE xnb update account 001 dtd CUSTOMER ACCOUNT 001 OAG72 OUT xgm XNB OM SALESORDER O xnb add salesorder 001 dtd SALES ORDER 001 AG72 OUT XNB INV ITEM OAG72 OU nb update item 001 dtd ITEM SYNC 001 T XNB CLN CBOD OAG721 xnb 002 confirm bod 004 dt CONFIRM BOD 004 N d XNB OM GRPSALESORDER xnb add grpsalesorder 001 GRPSALES ORDER 001 _OAG72_OUT xgm td Open Applications Group OAG Conforming DTDs TBI provides the following OAG conforming DTDs e oagis_domains dtd C 2 Oracle Telecommunications Billing Integrator Implementation Guide e oagis entity extensions dtd e oagis extensions dtd e oagis fields dtd e oagis_resources dtd e oagis_segments dtd The OAG Integration Specification DTDs are available in XNB_TOP xml oag72 This folder also contains the XNB specific DTDs when they are loaded into the XML Gateway repository Loading and Deleting Maps Maps can be reloaded manually into the repository using the XML Gateway Map loader Run the following command from the APPL TOP to load the
30. BER 15 last_updated_by NUMBER 15 last_update_login NUMBER 15 object_version_number NUMBER Used for locking purposes attribute_category VARCHAR2 30 Descriptive flexfield structure defining column attributel to attribute 15 VARCHAR2 150 Descriptive flexfield segment column APIs in Telecommunications Billing Integrator B 5 C Message Maps and DTDs for XML Gateway This appendix provides information on the message maps and DTDs for Oracle XML Gateway This appendix covers the following topics e Maps and DTDs Overview e Loading and Deleting Maps e Loading and Deleting DTDs Maps and DTDs Overview TBI provides predefined maps and the corresponding DTDs for the XML Gateway All the maps and DTDs are automatically loaded into the XML Gateway repository during the installation process and attached to the transactions in the XML Gateway The map files are located at XNB_TOP patch 115 xml US XNB TOP is the top level folder for the TBI related files The DTD files for TBI and OAGIS are located in XNB_TOP xml oag72 Maps in XML Gateway The following table lists the maps in XML Gateway Maps in XML Gateway Supported Flow Map Internal Name TCA Account Publish Add and Update XNB TCA ACCOUNT OAG72 OUT xgm OM Sales Order Publish XNB OM SALESORDER OAG72 OUT xgm Message Maps and DTDs for XML Gateway C 1 Supported Flow Map Internal Name Inventory Item Publish XNB INV ITEM OAG
31. CKING HZ CUSTOMER PR OFILES NEXT CREDIT REVI EW DATE HZ CUSTOMER PR OFILES TOLERANCE HZ CUSTOMER PR OFILES CREDIT HOLD HZ CUSTOMER PR OFILES CREDIT RATING Expiration date Attribute category Extended Attributes Credit Classification identifier Credit checking flag Next credit review date Tolerance Credit hold flag Credit rating XML Messages in TBI D 19 STANDARD TERMS OVERRIDE TERMS DATETIME CREDIT CLASSIFIC ATION CREDIT_EXTENDED _ATTRIBUTES ATTRIBUTEI to ATTRIBUTEI5 CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT EXTENDED ATTRIBUTES HZ CUSTOMER PR OFILES STANDARD TERMS HZ CUSTOMER PR OFILES OVERRIDE TERMS HZ CUSTOMER PR OFILES LAST CREDIT REVI EW DATE HZ CUSTOMER PR OFILES CREDIT CLASSIFIC ATION Credit classification extended attributes HZ_CUSTOMER_PR OFILES ATTRIBUTEI to A TTTRIBUTE15 Standard terms Override terms Last credit review date Credit classification Extended attributes Message Specifications for Sales Order Line The following table lists the specifications for sales order line information Message Specifications for Sales Order Line XML TagT ORDER LINE INFO ORDER LINE ID XML Parent Tag DATAAREA ORDER LINE INFO Field in E Business Suite Sales order line informatio
32. 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 e Anew telecommunications service example wireless service is ordered e 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 u
33. DRESS PHONE LINE TYPE PHONE COUNTRY CODE PHONE AREA COD E PHONE NUMBER PHONE EXTENSIO N URL CONTACT NAME SHIP TO CONTACT _INFO SHIP_TO_CONTACT _INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO HZ_PARTIES PERSO N NAME SUFFIX HZ PARTIES SALUT ATION Ship to Contact Information HZ_CONTACT_POI NTS CONTACT_POI NT_TYPE HZ_CONTACT_POI NTS EMAIL_ADDRE SS HZ_CONTACT_POI NTS PHONE_LINE_ TYPE HZ_CONTACT_POI NTS PHONE_COUN TRY_CODE HZ_CONTACT_POI NTS PHONE AREA CODE HZ CONTACT POI NTS PHONE NUMB ER HZ CONTACT POI NTS PHONE EXTEN SION HZ CONTACT POI NTS URL Suffix Salutation Contact Point Type Email Address Phone Purpose Country Code Area Code Phone Number Extension Url Message Specifications for Product Item The following table lists the specifications for product D 30 Oracle Telecommunications Billing Integrator Implementation Guide Message Specifications for Product XML Tag ITEM INFO ITEMID ITEM NAME ITEM TYPE ITEM TYPE DESC BOM ITEM TYPE BOM ITYPE DESC UOM ITEM DESCRIPTION ITEM STATUS ITEM STATUS DES C Parent Component DATAAREA ITEM INFO ITEM INFO ITEM INFO ITEM INFO ITEM INFO ITEM INFO ITEM INFO ITEM INFO ITEM INFO ITEM INFO Field in E Business Suite Item Information MTL SYSTEM ITEM S VL
34. Date when the customer account was originally established Tax code for this customer Indicate if item is tax header or a line item Indicates if the bill receivable should be held or not Descriptive Flexfield segment for Account Related Customer Account Id Related Customer Account Number Related Customer Account Name D 8 Oracle Telecommunications Billing Integrator Implementation Guide RELATIONSHIP TY PE ORG ID BILL TO FLAG SHIP TO FLAG TAX EXEMPTIONS EXEMPTION TYPE STATUS TAX CODE PERCENT EXEMPT CUSTOMER EXEMP TION NUMBER DATETIME RELATED ACCOUN TS RELATED ACCOUN TS RELATED ACCOUN TS RELATED ACCOUN TS DATAAREA TAX EXEMPTIONS TAX EXEMPTIONS TAX EXEMPTIONS TAX EXEMPTIONS TAX EXEMPTIONS TAX EXEMPTIONS HZ CUST ACCT RE LATE ALL RELATIONSHIP TY PE HZ CUST ACCT RE LATE ALL ORG ID HZ CUST ACCT RE LATE ALL BILL TO _FLAG HZ_CUST_ACCT_RE LATE_ALL SHIP_TO _FLAG Tax Data RA_TAX_EXEMPTIO NS_ALL EXEMPTION_TYPE RA_TAX_EXEMPTIO NS_ALL STATUS RA_TAX_EXEMPTIO NS_ALL TAX_CODE RA_TAX_EXEMPTIO NS_ALL PERCENT_EXEMPT RA_TAX_EXEMPTIO NS_ALL CUSTOMER_EXEMP TION _NUMBER RA_TAX_EXEMPTIO NS_ALL END_DATE Relationship Type Organization Id Bill To Relationship Flag Ship To Relationship Flag Exemptions can be for customers at a location or for items at a location Approval status for this exemption
35. E Business Suite and the external billing applications These DTDs must be used to define BODs in the messaging middleware TBI generates outbound BODs corresponding to 1 TCA Account Add and Update 2 OM Sales Order 3 Inventory Item 4 Grouped Sales Order There is only one inbound BOD for TBI This is the ConfirmBOD CBOD The CBOD is used by the billing application to return the status of processing the outbound BODs Note The DTDs for BODs must be used along with the OAG based DTDs to define the business objects in the messaging middleware The OAG based DTDs are modified to include extensions for TBI XML Message Format Oracle XML Gateway generates the TBI outbound messages and they are delivered as Advanced Queue payloads The inbound messages CBOD messages from a billing application must contain information that the E Business Suite can use to track success or failure of a published outbound message Outbound Messages The outbound messages publish information on the Oracle E Business Suite objects such as customers products sales orders and so on to the external billing applications Messages are delivered to the Outbound AQ XNB JMS OUTBOUND queue and are picked up by the middleware adapters from the queue JMS Message Structure The table below lists the structure of the JMS standard message D 2 Oracle Telecommunications Billing Integrator Implementation Guide JMS Message Structure HEADER HEADER REP
36. EC Attribute Name Data Type Description Mandatory attributes account number VARCHAR2 30 Account Number of the customer that must exist in Oracle E Business Suite This field is mandatory for insert record The foreign key is hz_cust_accounts account_nu mber bill number VARCHAR2 30 Bill reference number This field is for insert and update record and must be unique billing vendor name VARCHAR 240 Name of the billing vendor bill cycle end date DATE Billing cycle contains an end date of the cycle This is required for insert API only not for update API Optional Attributes total amount due VARCHAR 2 30 Total amount due for all open bills adjustments VARCHAR2 30 Unapplied adjustments or payments up to this bill cycle unresolved disputes VARCHAR 2 30 Total amount of open disputes bill cycle start date DATE Start date of the billing cycle due date DATE Timestamp indicating when the bill is due new charges VARCHAR 2 30 New charges for this bill B 4 Oracle Telecommunications Billing Integrator Implementation Guide Attribute Name Data Type Description Payment VARCHAR2 30 Total payment received on this bill up to this billing cycle Balance VARCHAR2 30 Balance for this bill after the payments etc previous_balance VARCHAR 30 bill_location_url VARCHAR 240 Location of the bill online due_now VARCHAR2 30 Amount currently due for an account created_by NUM
37. ES TABLE e Bill Summary Public Record Type BILL SUMMARIES REC Bill Summary Bulk Insert APIs The summary data in the Bill Summary UI is fetched from the XNB BILL SUMMARIES table in Oracle E Business Suite The XNB BILL SUMMARIES PKG public package provides the API to do a bulk insert in the XNB Bill Summary tables Procedure INSERT ROW BATCH The INSERT ROW BATCH procedure is used to insert new bill summary records from external billing applications into Oracle E Business Suite Syntax XNB BILL SUMMARIES PKG Insert Row Batch p api version bill summaries x return status x msg data The following table lists the parameters for the procedure APIs in Telecommunications Billing Integrator B 1 Procedure INSERT ROW BATCH Parameter Name IN Out Data Type Description p api version IN NUMBER Version of the API p bill summaries IN bill summaries table PL SQL table type that contains the record type required for creating bill summaries x return status OUT VARCHAR2 Returns the status of the create operation The values returned are S When the operation is a success E When the operation is not a success due toa known error x msg data OUT VARCHAR2 A concatenated string of all the error and warning messages that are put into the message stack Procedure UPDATE ROW BATCH The UPDATE ROW BATCH procedure is used to update existing bill summary records from external billing application into Ora
38. LYTO HEADER REPLYTO NAME HEADER REPLYTO ADDRESS HEADER REPLYTO PROTOCOL HEADER USERID HEADER APPID HEADER GROUPID HEADER GROUPSEQ HEADER PROPERTIES TEXT LEN TEXT VC LOB Main Header Reply to Information Name of the Application Replied To Address of the Application Replied To Protocol Used in Replying User Id Application Id Group Id Group Sequence Properties Length of the Payload Has the Payload If TEXT LEN lt 4000 bytes Has the Payload If TEXT LEN gt 4000 bytes JMS Message Header Properties for CBOD The message properties contains fields that identify the type of message the standard it uses the entity that the message refers to the sender details the transportation and the authentication information In CBOD messages XML Gateway refers these properties to identify the correct map to execute The following table explains the properties that are published in the Advanced Queue message XML Messages in TBI D 3 Fields in the Advanced Queue Message Field Value ECX MESSAGE TYPE XML ECX MESSAGE STANDARD OAG ECX TRANSACTION TYPE BOD ECX TRANSACTION SUBTYPE CONFIRM ECX PARTY SITE ID Sender Billing application BES EVENT NAME oracle apps ecx jms receive Seeded BES EVENT KEY Unique key for every run Inbound Messages Inbound messages contain acknowledgements for the published messages or information on the bill summary The Confirm BOD message
39. Map java oracle apps ecx loader LoadMap lt uname gt passwd lt host port sid gt map name xgm To delete maps from the repository run the following command java oracle apps ecx loader DeleteMap uname passwd host port sid map internal name Loading and Deleting DTDs Every time a patch is applied and the existing DTDs are updated or new DTDs are introduced the DTDs are automatically loaded to the repository so there is no need to load them manually For more information on loading DTDs and maps refer Oracle XML Gateway User s Guide The OAG conformant DTDs need not be loaded into the repository Before loading the TBI Specific DTDs ensure that the OAGIS DTDs are present in the same directory To load the DTDs while debugging open the XNB TOP xml oag72 directory under APPL TOP and run the following command java oracle apps ecx loader LoadDTDToClob uname lt passwd gt host port sid dtd name dtd root element runtime location To delete the DTD associated with a map run the following command java oracle apps ecx loader DeleteDTDFromClob uname lt passwd gt host port sid dtd name dtd root element runtime location The script values are e uname passwd host port sid Database connection parameters Message Maps and DTDs for XML Gateway C 3 e dtd name dtd TBI specific DTDs e root element root element of the DTD runtime location Set to xn
40. NAME State Postalcode Descriptive Flexfield segment for Customer Descriptive Flexfield segment for Account Person Identifier Title Pre Name Adjunct Middle Name Last Name XML Messages in TBI D 41 PERSON NAME SU FFIX SALUTATION CONTACT INFO CONTACT POINT T YPE EMAIL ADDRESS PHONE LINE TYPE PHONE COUNTRY CODE PHONE AREA COD E PHONE NUMBER PHONE EXTENSIO N URL CONTACT NAME SHIP TO CONTACT _INFO SHIP_TO_CONTACT _INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO CONTACT_INFO HZ_PARTIES PERSO N NAME SUFFIX HZ PARTIES SALUT ATION Ship to Contact Information HZ_CONTACT_POI NTS CONTACT_POI NT_TYPE HZ_CONTACT_POI NTS EMAIL_ADDRE SS HZ_CONTACT_POI NTS PHONE_LINE_ TYPE HZ_CONTACT_POI NTS PHONE_COUN TRY_CODE HZ_CONTACT_POI NTS PHONE AREA CODE HZ CONTACT POI NTS PHONE NUMB ER HZ CONTACT POI NTS PHONE EXTEN SION HZ CONTACT POI NTS URL Suffix Salutation Contact Point Type Email Address Phone Purpose Country Code Area Code Phone Number Extension Url D 42 Oracle Telecommunications Billing Integrator Implementation Guide Glossary Advanced Queuing Adapter Used to integrate OAI hub with an Advanced Queue in the spoke application Agent Listener Type of service component that processes event messages on agents Hub An integration
41. ORACLE 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 Copyright 2005 2006 Oracle All rights reserved 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
42. Order Message 1 6 Example 1 6 H Hub user defining 3 4 O OAI hub A 1 Overview 1 1 XML Message D 1 Overview OAI A 1 index P Profile Option Bill Summary UI 3 13 Publishing Account Update Details 1 3 Bill To accounts for a Sales Order 1 6 Item Product Details 1 4 New Account Details 1 3 Sales Order Details 1 4 S Starting Adapter A 4 Stopping Adapter A 4 T Transactions internal 3 5 Index 1
43. PERSON MIDDLE NAME PERSON LAST NA ME PERSON NAME SU FFIX SALUTATION ADDRESS CUSTOMER INFO CUSTOMER INFO CUSTOMER NAME CUSTOMER NAME CUSTOMER NAME CUSTOMER NAME CUSTOMER NAME CUSTOMER NAME CUSTOMER NAME CUSTOMER INFO CUSTOMER INFO HZ PARTIES EMAIL ADDRESS Name of the Customer HZ PARTIES PERSO N IDENTIFIER HZ PARTIES PERSO N TITLE HZ PARTIES PERSO N PRE NAME ADJ UNCT HZ PARTIES PERSO N FIRST NAME HZ PARTIES PERSO N MIDDLE NAME HZ PARTIES PERSO N LAST NAME HZ PARTIES PERSO N NAME SUFFIX HZ PARTIES SALUT ATION Identifying Address Email Address Personal identifier such as driver s license or passport number A professional or family title For example Don or The Right Honorable Salutary introduction such as Mr or Herr First name of the person Middle name of the person Last or surname of the person Indicates the place in a family structure For example in Tom Jones III the III is the suffix Phrase used to address a party in any correspondence D 12 Oracle Telecommunications Billing Integrator Implementation Guide ADDRLINE CITY COUNTRY COUNTY STATEPROVN POSTALCODE CUSTOMER EXT A TTRIBUTES ATTRIBUTEI to ATTRIBUTEI5 RELATIONSHIP INF O PARENT_PARTY_ID PARENT_PARTY_N AME ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS CUSTOMER_INFO CUSTOMER_EXT_ ATTRIBUTES CUSTOME
44. 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 1 Setting Up XML Gateway page 3 3 Setting Up Collaboration History page 3 10 Starting Agent Listeners page 3 13 Setting Up Bill Summary UI page 3 13 Integration with Order Management Workflow Processes page 3 16 Setting Up and Running the Item Publish Concurrent Program page 3 19 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 gt 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 2 Definin
45. Products Used in TBI TBI uses the following Oracle applications that provide the underlying technology stack schema and structure for TBI e Oracle Telecommunications Service Ordering TSO e Oracle Collaboration History e Oracle Contact Center e Oracle Workflow Business Systems e Oracle XML Gateway e Oracle Advanced Queuing Enhancements The enhancements in this release are e Creation of a Grouped Sales Order message that includes all the lines of an order e Publish Bill To account information for a sales order e Additional TCA events for Account Update Message e Enhancements to the Account Message e Enhancements to the Sales Order Message e 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 provisione
46. RIBUTE VALUE 5 ATTRIBUTE INFO ATTRIBUTE ID ATTRIBUTE LEVEL MASTER ORGANIZ A TION ID INVENTORY ITEM ID ITEM CATEGORY I D ATTRIBUTE CODE INSTALL BASE INF O INSTALL_BASE_INF O INSTALL_BASE_INF O ATTRIBUTE_VALUE S ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO CSI ITEM INSTANC ES LAST OE ORDER L INE ID CSI ITEM INSTANC ES INSTALL AT ADDR ESS Attribute Value Pairs of Install Base Attribute Information CSI I EXTENDED A TTRIBS ATTRIBUTE ID CSI I EXTENDED A TTRIBS ATTRIBUTE LEVEL CSI I EXTENDED A TTRIBS MASTER OR GANIZATION ID CSI I EXTENDED A TTRIBS INVENTORY _ITEM_ID CSI I EXTENDED A TTRIBS ITEM CATE GORY ID CSI I EXTENDED A TTRIBS ATTRIBUTE CODE Last Order Line Identifier that touched the Instance Install At Address Attribute Identifier Attribute Level Master Organization Identifier Inventory Item Identifier Item Category Identifier Attribute Code D 38 Oracle Telecommunications Billing Integrator Implementation Guide ATTRIBUTE NAME ATTRIBUTE CATEG ORY DESCRIPTION ACTIVE START DA TE ACTIVE END DATE SECURITY GROUP ID VALUE INFO ATTRIBUTE VALUE ID ATTRIBUTE VALUE ACTIVE START DA TE ACTIVE END DATE BILL TO PARTY IN FO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE INFO ATTRIBUTE VALUE
47. R_INFO RELATIONSHIP_INF O RELATIONSHIP_INF O CONTACT HZ_PARTIES ADDR ESSI HZ PARTIES ADDR ESS2 HZ PARTIES ADDR ESS3 HZ PARTIES ADDR ESS4 HZ PARTIES CITY HZ PARTIES COUN TRY HZ PARTIES COUN TY HZ PARTIES STATE HZ PARTIES POSTA L CODE Customer Extended Attributes HZ PARTIES ATTRI BUTE to HZ PARTIES ATTRI BUTE15 Customer Relationship Information HZ PARTIES PARTY ID HZ PARTIES PARTY NAME Identifying Address Line of the Customer City Country County State Postal code Descriptive Flexfield segment for Customer Parent Customer Id Parent Customer Name XML Messages in TBI D 13 PARENT RELATIO NSHIP TYPE DATETIME CUSTOMER CONT ACT INFO CONTACT POINT I D CONTACT POINT T YPE PRIMARY EDI TRANSACTION HANDLING EDI ID NUMBER EDI PAYMENT ME THOD RELATIONSHIP INF O RELATIONSHIP_INF O CUSTOMER_INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO CUSTOMER_CONT ACT _INFO HZ_RELATIONSHIP 5 RELATIONSHIP_CO DE HZ_RELATIONSHIP S END_DATE Customer Contact Information HZ_CONTACT_POI NTS CONTACT_POI NT_TYPE HZ_CONTACT_POI NTS CONTACT_POI NT_TYPE HZ_CONTACT_POI NTS PRIMARY_FLA G HZ_CONTACT_POI NTS EDI TRANSAC TION HANDLING HZ CONTACT POI NTS EDI ID NUMBE R HZ CONTACT POI NTS EDI PAYMENT METHOD
48. S MAX INTEREST CH ARGE HZ CUST PROFILE AMTS MIN STATEMENT AMOUNT HZ CUST PROFILE AMTS AUTO REC MIN R ECEIPT AMOUNT HZ CUST PROFILE AMTS INTEREST RATE HZ CUST PROFILE AMTS MIN FC BALANCE _ AMOUNT HZ CUST PROFILE AMTS MIN FC INVOICE AMOUNT Over All Credit limit Minimum dunning amount Minimum invoice amount Maximum interest charge Minimum statement amount Minimum receipt amount Interest rate Minimum balance amount Minimum invoice amount D 18 Oracle Telecommunications Billing Integrator Implementation Guide DATETIME ATTRIBUTE CATEG ORY PROFILE AMTS EX TENDED ATTRIBUT ES ATTRIBUTEI to ATTRIBUTEI5 CREDIT CLASSIFIC ATION INFO CUST ACCOUNT P ROFILE ID CREDIT CHECKING DATETIME TOLERANCE CREDIT HOLD CREDIT RATING CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO CUST PROFILE AM TS INFO PROFILE AMTS EX TENDED ATTRIBUT ES DATAAREA CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO CREDIT CLASSIFIC ATION INFO HZ CUST PROFILE AMTS EXPIRATION DATE HZ CUST PROFILE AMTS ATTRIBUTE CATEG ORY Profile Amounts Extended Attributes HZ CUST PROFILE AMTS ATTRIBUTE1 to ATTRIBUTE15 Credit classification information HZ CUSTOMER PR OFILES CUST ACCOUNT P ROFILE ID HZ CUSTOMER PR OFILES CREDIT CHE
49. S Format is published to the JMS Outbound queue WF JMS OUT The Collaboration history is updated to reflect the account message publish status Note If Oracle Applications Interconnect OAI 9 0 4 is used as the middleware refer Appendix A for details on configuring OAI 9 0 4 If a non OAI middleware is used refer to the respective documentation for the configuration details Implementation Tasks for Oracle Telecommunications Billing Integrator 3 23 A Configuring Oracle Applications InterConnect This appendix provides information on configuring Oracle Applications InterConnect OAD This appendix covers the following topics e Oracle Applications InterConnect Overview e Setting Up OAI Hub e Setting up OAI Adapter for Advanced Queues e Dropping the Hub Schema e Importing OAI Maps to the Repository Oracle Applications InterConnect Overview Oracle Applications InterConnect OAI 9 0 4 is the middleware for TBI The components of OAI applicable to TBI are OAI Hub and OAI Adapter for Advanced Queues AQ The OAI Hub contains all the mapping and transformation data required for integration in its repository The repository is maintained in an Oracle database on the hub machine The OAI adapter is attached to an application participating in the integration and is responsible for transfer of data from and to the respective application and the OAI hub Each adapter performs the necessary data transformation based on the OAI
50. TTRIBS SECURITY G ROUP ID Value Information CSI IEA VALUES A TTRIBUTE VALUE I D CSI IEA VALUES A TTRIBUTE VALUE CSI IEA VALUES A CTIVE START DAT E CSI IEA VALUES A CTIVE END DATE BILL TO PARTY IN FO Attribute Name Attribute Category Description Activation Start Date Activation End Date Security Group Identifier Instance Extended Attribute Value Identifier Instance Extended Attribute Value Activation Start Date Activation End Date XML Messages in TBI D 27 BILL TO OWNER F LAG PRIMARY BILL TO BILL TO PARTY IN FO BILL TO PARTY IN FLAG BILL TO PARTY N UMBER BILL TO PARTY N AME BILL TO ACCOUNT NUMBER BILL TO ACCOUNT _NAME ADDRESS ADDRLINE CITY COUNTRY COUNTY FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO BILL_TO_PARTY_IN FO ADDRESS ADDRESS ADDRESS ADDRESS HZ_PARTIES BILL_T O_OWNER_FLAG HZ_PARTIES PRIMA RY_BILL_TO_FLAG HZ_PARTIES PARTY _NUMBER HZ_PARTIES PARTY _NAME HZ_CUST_ACCOUN TS ACCOUNT_NUMBE R HZ_CUST_ACCOUN TS ACCOUNT_NAME Bill To Address CONCAT HZ_LOCATIONS AD DRESS1 HZ_LOCATI ONS ADDRESS2 HZ_ LOCATIONS ADDRE S3 HZ_LOCATIONS ADDRESS4 HZ_LOCATIONS CI TY HZ LOCATIONS CO UNTRY HZ LOCATIONS CO UNTY Bill To Owner Flag Primary Bill To Flag Unique Identifier of the Customer Customer Name Unique Identifier of t
51. UNIT OF M EASURE OE ORDER LINES ALL SHIP TO ORG ID CONCAT HZ LOCATIONS AD DRESS1 HZ_LOCATI ONS ADDRESS2 HZ_ LOCATIONS ADDRE S53 HZ LOCATIONS ADDRESS4 HZ_LOCATIONS CI TY HZ LOCATIONS CO UNTRY HZ LOCATIONS CO UNTY Ship To Organization ID Type of Service performed on the Order Currency Code Charge Periodicity Code Charge Periodicity Code Description Ship To Address Ship To Address Line of the Account City Country County XML Messages in TBI D 23 STATEPROVN POSTALCODE TAX INFO TAX CODE TAX RATE DATETIME AMOUNT PAYMENT TERM I NFO PAYMENT TERM I D PAYMENT TERM N AME DESCRIPTION EXT ATTRIBUTES ADDRESS ADDRESS ORDER LINE INFO TAX INFO TAX INFO TAX INFO TAX INFO ORDER LINE INFO PAYMENT TERM I HZ LOCATIONS ST ATE HZ LOCATIONS POSTAL CODE Tax Information OE ORDER LINES _ ALL TAX CODE OE ORDER LINES _ ALL TAX RATE OE ORDER LINES _ ALL TAX DATE OE ORDER LINES ALL TAX VALUE Payment term Information OE ORDER LINES NFO PAYMENT TERM I ALL PAYMENT TER M ID RA TERMS VL NA NFO PAYMENT TERM I ME RA TERMS VL DES NFO ORDER LINE INFO CRIPTION Order Line Extended Attributes D 24 Oracle Telecommunications Billing Integrator Implementation Guide State Postalcode Tax code for the line Tax rate in percentage Date for tax calculation Tax amount in
52. ales Order Line XML Tag XML Parent tag ORDER HEADER I NFO DATAAREA ORDER NUMBER ORDER HEADER I Field in E Business Suite Order Header Information OE ORDER HEADE NFO RS ALL ORDER NU MBER Description Unique Identifier for Order D 32 Oracle Telecommunications Billing Integrator Implementation Guide SOLD TO ACCOUN T NUMBER SOLD_TO_ACCOUN T NAME SOLD_TO_PARTY_ NUMBER SOLD_TO_ PARTY_NAME ORDER_LINE ORDER_LINE_INFO ORDER_LINE_ID TOP MODEL LINE ID LINK TO LINE ID PRICE LIST ID PRICE LIST NAME ORDER HEADER I NFO ORDER HEADER I NFO ORDER HEADER I NFO ORDER HEADER I NFO ORDER HEADER I NFO ORDER LINE ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO HZ CUST ACCOUN TS ACCOUNT NUMBE R HZ CUST ACCOUN TS ACCOUNT NAME HZ PARTIES PARTY NUMBER HZ PARTIES PARTY NAME Salesorder Line Informations Sales order line information OE ORDER LINES ALL LINE ID OE ORDER LINES ALL TOP MODEL LINE ID OE ORDER LINES ALL LINK TO LINE ID OE ORDER LINES ALL PRICE LIST ID OP LIST HEADERS VL DESCRIPTION Unique Identifier for Account Account Name Unique Identifier for Customer Customer Name Primary Key to Identify the Order Line Identifier of configuration top parent line Identifier of immediate parent component line Price List Price List Name
53. alesorder info Setting Up and Running the Item Publish Concurrent Program You must have the System Administrator responsibility and the Telecommunications Implementation Tasks for Oracle Telecommunications Billing Integrator 3 19 Billing Integrator Administrator responsibility to setup and run the concurrent program for Oracle TBI Setting up and running the item publish concurrent program involves 1 Defining Item Batch Export Profile Values 2 Submitting the Item Publish Request Item Batch Export Profile Values The following table lists the profile values for Item Batch Export Profile Item Batch Export Profile Values Profile Option Value XNB Items Batch Message Type The values are CSV Batch File Generates a batch file in Comma Separated Values format XML Batch File Generates a batch file in XML format XML Message Generates an XML message for each inventory item and is published through the middleware XNB Items Batch File Location Name of the folder in which TBI generates the Inventory Items Batch file XML or CSV The file is generated by the Item Batch Export Concurrent Request This is required if the XNB Items Batch Message Type profile value is set to CSV Batch File or XML Batch File The following table lists the seeded values for Item Batch Export concurrent program Seeded Values for Item Batch Export Concurrent Program Name Value Program Telecom Billing Integrat
54. 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
55. ated 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 xii 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 pa
56. b oag72 C 4 Oracle Telecommunications Billing Integrator Implementation Guide D XML Messages in TBI This appendix provides information on the XML messages in TBI This appendix covers the following topics XML Message Overview Outbound and Inbound BOD XML Message Format Outbound Messages Inbound Messages Seeded XML Messages Message Specifications for Account Information Message Specifications for Sales Order Line Message Specifications for Product Item Message Specifications For Group Sales Order Line XML Message Overview TBI uses XML Gateway to generate XML messages The XML messages in TBI conform to the Open Applications Group Integration Specifications OAGIS standard and are published as OAG Business Object Documents BODs to the external billing applications A BOD contains the following 1 Control Area CNTROLAREA This is the header area defining the identification of the message the purpose the sender details and the time stamp information AII BODs have the same structure for the Control Area Data Area DATAAREA The data area contains the business specific data that is being communicated by the BOD This area defines the actual business object such XML Messages in TBI D 1 as the TCA account or the OM Sales Order The structure and content of this area varies based on the DTD for each message Outbound and Inbound BOD TBI provides the XML DTDs for all the messages exchanged between
57. bound Messages ente tee dte tet e anh e e ee ema aL deeem te D 4 Seeded XML M ssages eerte dede iden ct a der ta eate e dee a ee ede kd D 7 Message Specifications for Account Information sssssssseeee eee D 7 Message Specifications for Sales Order Line sssssssssee eme D 20 Message Specifications for Product Item ssssssssssssseeeeeeneeennns D 30 Message Specifications For Group Sales Order Line sess D 32 Glossary Index 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 e Are the implementation steps correct and complete e Did you understand the context of the procedures e Did you find any errors in the information e Does the structure of the information help you with your tasks e Do you need different information or graphics If so where and in what format e 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
58. cle E Business Suite Syntax XNB BILL SUMMARIES PKG Update Row Batch p api version bill summaries x return status x msg data The table below lists the parameters for the UPDATE ROW BATCH procedure B 2 Oracle Telecommunications Billing Integrator Implementation Guide Procedure UPDATE ROW BATCH Parameter Name In Out Data Type Description p api version IN NUMBER p bill summaries IN bill summaries table x return status OUT VARCHAR2 x msg data OUT VARCHAR2 Version of the API PL SQL table type that contains the record type required for creating bill summaries Returns the status of the update operation The values returned are S When the operation is a success E When the operation is not a success due to a known error A concatenated string of all the error and warning messages that are put into the message stack Bill Summary Public Table Type BILL SUMMARIES TABLE The following table lists the specifications for the BILL SUMMARIES TABLE Specifications for BILL SUMMARIES TABLE Table Type Name Record Type Description bill summaries table TABLE OF bill summaries rec PL SQL record type that contains all the attributes required for creating bill summaries Bill Summary Public Record Type BILL SUMMARIES REC The following table lists the specifications for BILL SUMMARIES REC APIs in Telecommunications Billing Integrator B 3 Specifications for BILL SUMMARIES R
59. d a confirmation BOD with status SUCCESS to the Oracle E Business Suite e ONERROR Account information in the sales order line is published only if a failure confirmation BOD with status ERROR was sent by at least one of the billing applications and that billing application has not sent a confirmation BOD with status SUCCESS in the past 3 18 Oracle Telecommunications Billing Integrator Implementation Guide Creating the Workflow Function Create the workflow function for publishing sales order information Navigation In WorkFlow Builder open the OM Order Line OEOL workflow Notes Internal Name XNB SALESORDER PUBLISH Display Name XNB Sales Order Publish e Function Name xnb cmn pvt publish salesorder info Integrating Workflow Process for Publishing Group Sales Order Information Create the workflow function for publishing group sales order information The figure below shows the workflow process for publishing Group Sales Order Information Workflow Process for Publishing Group Sales Order Information TBI Account Publish yo _ LI Enter Book Order Service Fulfillment TBI Close Order End Manual Order TBI Group alesorder Publi Navigation In Workflow Builder open the OM Order Header OEOH workflow Notes Enter the following parameters for the new function Internal Name XNB GRP SALESORDER PUBLISH e Display Name XNB Group Sales Order Publish e Function Name xnb cmn pvt publish grps
60. d 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 Note Group sales order and sales order line messages are mutually 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 1 6 The TCA events added to the existing Account Update message are e oracle apps ar hz Person update This event is triggered when there are changes to personal information about a person e oracle apps ar hz Organization update This event is triggered when there are changes to informati
61. dates to party and account relevant to the billing system e Track the status of each message that is published to the external billing application e 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 Ul 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
62. e 3 6 e Sales Order Outbound page 3 6 e Group Sales Order Outbound page 3 7 Implementation Tasks for Oracle Telecommunications Billing Integrator 3 5 e Inventory Item Outbound page 3 8 e 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 EXT TXN QUEUE TYPE SUBTYPE OAG OUT ACCOUNT SYNC s 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 Attribute Value Transaction Subtype SOO Transaction Description XNB OM Sales Order Outbound External Transactions for Sales Order Outbound External Transactions for Sales Outbound STD CODE DIR EXT TXN EXT TXN QUEUE TYPE SUBTYPE OAG OUT SALESORDER ADD Internal Transactions for Group Sales Order Outbound Group Sales Order Outbound Attribute Value Party Type Customer Transaction Type XNB
63. er profile amount is updated 7 oracle apps ar hz CustAccount up Customer Account Triggered when a date Update customer account information is updated 8 oracle apps ar hz Person update Person Update Triggered when Party Details of type Person is updated 9 oracle apps ar hz Organization up Organization Update Triggered when Party date Details of type Organization is updated 3 22 Oracle Telecommunications Billing Integrator Implementation Guide SI No Event Name Event Display Name Description 10 11 oracle apps ar hz CustomerProfile update oracle apps ar hz ContactPoint up date Customer Profile Update Contact Points Update Triggered when Customer Profile details are updated Triggered when Contact Point details are updated Configuring the Middleware Oracle TBI uses generic XML gateway compatible Advance Queues AQ for all outgoing and incoming messages They are 1 WF JMS IN This inbound queue is used for all inbound messages that are sent to TBI Once the billing application receives the message it sends a Confirmation Business Object Document CBOD with appropriate status to the Middleware which queues it onto the WF JMS IN The Workflow Agent configured on the WF JMS IN queue picks up the message and calls the workflow handlers to process the message WF JMS OUT This is the JMS Outbound queue that processes outbound transactions The Account XML message generated in JM
64. etwork Navigation Oracle XML Gateway Setup gt 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 gt 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 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 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 3 4 Oracle Telecommunications Billing Integrator Implementation Guide e The names representing the billing applications setup in the hub must be unique e Hub entity code values for the various billing applications must be same as the key value from BSR SENDER COMPONENT Defining Transactions Internal transactions
65. fine 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 Oracle Workflow User s Guide This guide describes how Oracle Applications users can view and respond to workflow notifications and monitor the progress of their workflow processes Oracle Workflow API Reference This guide describes the APIs provided for developers and administrators to access Oracle Workflow Oracle eTechnical Reference Manuals Each eTechnical Reference Manual eTRM contains database diagrams and a detailed description of database tables forms reports and programs for a specific Oracle Applications product This information helps you convert data from your existing applications integrate Oracle Applications data with non Oracle applications and write custom reports for Oracle Applications products Oracle eTRM is available on OracleMetalink Do Not Use Database Tools to Modify Oracle Applications Data Oracle STRONGLY RECOMMENDS that you never use SOL Plus Oracle Data Browser database triggers or any other tool to modify Oracle Applications data unless xiii xiv otherwise instructed Oracle provides powerful tools you can use to create store change retrieve and maintain information in an Oracle database But if you use Oracle tools such as SQL Plus to modify Oracle Applications data you risk destroying
66. g 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 SORACLE HOMEJ dbs initsSID 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 n
67. generated by a billing application is another BOD and follows the OAG definition for a BOD This message contains a control area as well as a data area The value of CNTROLAREA SENDER COMPONENT in the inbound messages should correspond to the XML Gateway hub user identification Hub Entity Code that is set for the respective external billing application TBI uses this field to identify the billing application that sent a given confirm BOD The DATAAREA CONFIRM_BOD CONFIRM CNTROLAREA field should contain the control area of the message being confirmed For example if a CBOD is confirming a TCA account message this field should contain the control area of the account message The SENDER REFERENCEID field is used by the XML Gateway to identify the message being confirmed The control area of the message being confirmed can be copied exactly in this field The DATAAREA CONFIRM BOD CONFIRM STATUSLVL field D 4 Oracle Telecommunications Billing Integrator Implementation Guide contains the status of the processing done on the message being confirmed If the status is 00 it indicates that the processing was successful If the status is 99 it indicates that the processing was a failure XML Messages in TBI D 5 Structure of the CBOD XML Message Structure of the CBOD XML Message lt xml version 1 0 standalone no lt DOCTYPE CONFIRM BOD 004 SYSTEM xnb 002 confirm bod 004 dtd lt CONFIRM BOD 004 lt CNTROLAREA gt
68. gration 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 3 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
69. 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 Rel
70. he Account Account Name Bill To Address Line of the Account City Country County D 28 Oracle Telecommunications Billing Integrator Implementation Guide STATEPROVN POSTALCODE PARTY EXT ATTRI BUTES ATTRIBUTEI to ATTRIBUTEI5 ACCOUNT EXT AT TRIBUTES ATTRIBUTEI to ATTRIBUTEI5 SHIP TO CONTACT INFO CONTACT NAME PERSON IDENTIFIE R PERSON TITLE PERSON PRE NAM E ADJUNCT PERSON MIDDLE NAME PERSON LAST NA ME ADDRESS ADDRESS BILL TO PARTY IN FO PARTY EXT ATTRI BUTES BILL TO PARTY IN FO ACCOUNT EXT AT TRIBUTES DATAAREA SHIP TO CONTACT _INFO CONTACT_NAME CONTACT_NAME CONTACT_NAME CONTACT_NAME CONTACT_NAME HZ_LOCATIONS ST ATE HZ_LOCATIONS POSTAL_CODE Party Extended Attributes HZ_PARTIES ATTRI BUTE to HZ_PARTIES ATTRI BUTE15 Account Extended Attributes HZ CUST ACCOUN TS A TTRIBUTEI to ATTRIBUTEI15 Ship to Contact Information Ship to Contact Name HZ_PARTIES PERSO N_IDENTIFIER HZ_PARTIES PERSO N_TITLE HZ_PARTIES PERSO N PRE NAME ADJ UNCT HZ PARTIES PERSO N MIDDLE NAME HZ PARTIES PERSO N LAST NAME State Postal code Descriptive Flexfield segment for Customer Descriptive Flexfield segment for Account Person Identifier Title Pre Name Adjunct Middle Name Last Name XML Messages in TBI D 29 PERSON NAME SU FFIX SALUTATION CONTACT INFO CONTACT POINT T YPE EMAIL AD
71. ier D 10 Oracle Telecommunications Billing Integrator Implementation Guide RECEIPT METHOD NAME PRIMARY FLAG DATETIME DATETIME CUSTOMER INFO PARTY NUMBER PARTY NAME PARTY TYPE TAX REFERENCE JGZZ FISCAL CODE RECEIPT METHODS RECEIPT METHODS RECEIPT METHODS RECEIPT METHODS DATAAREA CUSTOMER INFO CUSTOMER INFO CUSTOMER INFO CUSTOMER INFO CUSTOMER INFO AR RECEIPT METH ODS RECEIPT METHOD NAME RA CUST RECEIPT METHODS PRIMAR Y FLAG RA CUST RECEIPT METHODS START D ATE RA CUST RECEIPT METHODS END DA TE Customer Personal Information HZ PARTIES PARTY NUMBER HZ PARTIES PARTY NAME HZ PARTIES PARTY TYPE HZ PARTIES TAX R EFERENCE HZ PARTIESJGZZ FISCAL CODE Receipt Method Name Indicates if customer receipt method is primary Start date of the customer receipt methods End date of the customer receipt methods Unique identification number for the customer Customer Name The party type can only be Person Organization Group or Relationship Taxpayer registration number also known as the VAT number Taxpayer identification number a unique identifier of person or organization This can be SSN or income taxpayer ID in the US fiscal code or NIF in Europe XML Messages in TBI D 11 EMAIL ADDRESS CUSTOMER NAME PERSON IDENTIFIE R PERSON TITLE PERSON PRE NAM E ADJUNCT PERSON FIRST NA ME
72. ile Options page 3 13 2 Providing Access to Bill Summary UI to a Responsibility page 3 14 3 Personalizing the Form page 3 15 4 Accessing the Bill Summary UI from Oracle Contact Center page 3 16 5 Loading Bill Summary Data page 3 16 Defining Bill Summary UI Profile Options The following table lists the profile values for Bill Summary UI Implementation Tasks for Oracle Telecommunications Billing Integrator 3 13 Bill Summary UI Profiles Values Profile Option Value XNB Bill Image Source XNB Bill Image Location XNB Bill Image Format Specifies the source of the image displayed on the bill The values are Application The source of the bill image is application specific The billing application provides the URL to the bill details and the bill summary File System The bill image can be retrieved from the file system Specifies the location of the bill image in the file system XNB Bill Image Source must be set to File System The path specified must be a relative path accessible to the application web server The path specified is appended to the O0A_HTML path of the web server to retrieve the bill image Specifies the format of the bill image This value is used as the file extension for the image name which is same as the bill number For example gif jpeg Providing Access and Enabling the Bill Summary UI To access Bill Summary UI from Oracle Contact Center select a res
73. ing topics Implementation Considerations e TBI with TSO Middleware in TBI e External Billing Applications Implementation Considerations Consider the following implementation points before implementing Oracle TBI e TBI with TSO page 2 1 Middleware in TBI page 2 2 e External Billing Applications page 2 2 TBI with TSO 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 inte
74. ion Select the Oracle Application that owns the collaboration Document Type Select the Document Message Payload identified for the event Setting up the Final Collaboration Event The final collaboration event must be set up in Collaboration History to record the final status of the overall collaboration The final event is generally the occurrence of an inbound or outbound message in the XML Gateway After the collaboration is created or updated from the business flow the collaboration can be tracked using the Collaboration History function Navigation Workflow Administrator Collaboration Monitor SetUp Collaboration 3 12 Oracle Telecommunications Billing Integrator Implementation Guide Final Event Definition Checking Status of Agent Listeners The following Agent Listeners must be running for TBI to function e Workflow Deferred Agent Listener e Workflow Deferred Notification Agent Listener e Workflow Error Agent Listener e Workflow Inbound Notifications Agent Listener e Workflow Inbound JMS Agent Listener Navigation Workflow Administrator Oracle Applications Manager Workflow Manager Click the Agent listeners icon Setting Up Bill Summary UI The Bill Summary Ul is integrated with Oracle Contact Center and can be accessed from Oracle Contact Center through a special menu Oracle TBI uses the OA Framework for Bill Summary UI Setting up Bill Summary UI involves the following 1 Defining Bill Summary UI Prof
75. ions for account information Message Specifications for Account XML Tag ACCOUNT INFO CUST ACCOUNT I D ACCOUNT NUMBE R STATUS XML Parent Tag DATAAREA ACCOUNT INFO ACCOUNT INFO ACCOUNT INFO Field in E Business Suite Account information HZ CUST ACCOUN TS CUST ACCOUNT I D HZ CUST ACCOUN TS ACCOUNT NUMBE R HZ CUST ACCOUN TS STATUS Description Customer account identifier Account Number Customer status flag XML Messages in TBI D 7 ACCOUNT NAME DATETIME TAX CODE TAX HEADER LEV EL _FLAG HOLD_BILL_FLAG ACCOUNT_EXT _ATTRIBUTES ATTRIBUTEI to ATTRIBUTEI5 RELATED ACCOUN TS RELATED CUST ACCOUNT ID RELATED CUST ACCOUNT NUMB ER RELATED CUST ACCOUNT NAME ACCOUNT INFO ACCOUNT INFO ACCOUNT INFO ACCOUNT INFO ACCOUNT INFO ACCOUNT INFO ACCOUNT EXT ATTRIBUTES DATAAREA RELATED_ACCOUN TS RELATED_ACCOUN TS RELATED_ACCOUN TS HZ_CUST_ACCOUN TS ACCOUNT_NAME HZ_CUST_ACCOUN TS ACCOUNT_ESTABLI SHED_DATE HZ_CUST_ACCOUN TS TAX_CODE HZ_CUST_ACCOUN TS TAX_HEADER_LEV EL_FLAG HZ_CUST_ACCOUN TS HOLD_BILL_FLAG Extended Attributes HZ_CUST_ACCOUN TS ATTRIBUTEI to HZ_CUST_ACCOUN TS ATTRIBUTE15 Related Accounts Information HZ_CUST_ACCT_RE LATE_ALLRELATED CUST ACCOUNT I D HZ CUST ACCOUN TS ACCOUNT NUM BER HZ CUST ACCOUN TS ACCOUNT NAM E Description chosen by external party
76. mance of the adapter agent pipeline to hub false e agent pipeline from hub false e agent log level 2 0 5 Copy the DTDs from APPL TOP at the following location XNB_TOP xml oag72 and place them in the home folder of the adapter on the host file system i e lt OAI_HOME gt oai 9 0 4 adapters lt ADAPTER_NAME gt The AQ Adapter requires the DTDs of the XML messages that it reads and writes into the AQs 6 Tostart an adapter service run the following script from the console XOAI HOME 0ai 9 0 4 adapters ADAPTER NAME start 7 To stop an adapter service run the following script from the console XOAI HOME 0ai 9 0 4 adapters ADAPTER NAME stop Note The following file contains the log of adapter activities OAI HOME oai 9 0 4 adapters ADAPTER NAME logs latest ti mestamp gt oailog txt Dropping the Hub Schema A 4 To drop the hub schema you must stop the adapters and the repository service The steps are 1 Run the following script from the console to stop the adapters XOAI HOME 0ai 9 0 4 adapters ADAPTER NAME stop Oracle Telecommunications Billing Integrator Implementation Guide Run the following script from the console to stop the repository service OAI HOME 0ai 9 0 4 repository stop Run the following script at the command prompt OAI HOME 0ai 9 0 4 repository hubschema drop system system user pwd hub user pwd
77. n OE ORDER LINES ALL LINE ID Description Primary Key to identify the Order Line D 20 Oracle Telecommunications Billing Integrator Implementation Guide TOP MODEL LINE ID LINK TO LINE ID ORDER NUMBER SOLD TO PARTY NUMBER SOLD TO PARTY NAME SOLD TO ACCOUN T NUMBER SOLD TO ACCOUN T NAME PRICE LIST ID PRICE LIST NAME INVENTORY ITEM ID ORDER LINE INFO ORDER LINE INFO ORDER HEADER I OE ORDER LINES ALL TOP MODEL LINE ID OE ORDER LINES ALL LINK TO LINE ID OE ORDER HEADE NFO ORDER HEADER I NFO ORDER HEADER I NFO ORDER HEADER I NFO ORDER HEADER I NFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO RS ALL ORDER NU MBER HZ PARTIES PARTY NUMBER HZ PARTIES PARTY NAME HZ CUST ACCOUN TS ACCOUNT NUMBE R HZ CUST ACCOUN TS ACCOUNT NAME OE ORDER LINES ALL PRICE LIST ID OP LIST HEADERS VL DESCRIPTION OE ORDER LINES ALL INVENTORY ITEM ID Identifier of configuration top parent line Identifier of immediate parent component line Unique Identifier for Order Unique Identifier for Customer Customer Name Unique Identifier for Account Account Name Price List Price List Name used to identify the Price List Name Inventory Item Id XML Messages in TBI D 21 INVENTORY ITEM NAME INVENTORY ITEM DESCRIPTION ORG ID DATETIME UNIT SELLING PRI CE UNIT LIST PRICE
78. ng Partners Notes Company Admin Email Enter the System Administrator s e mail ID The System Administrator will receive notifications regarding warnings and errors Connection Hub Enter XNB_HUB This is required only for outbound messages Destination Trading Partner Location Code Leave this field blank Document Confirmation Specifies if the trading partner would like to send or receive a confirmation Select 2 Always send a confirmation for outbound messages and select 0 Never send a confirmation for inbound messages Setting Up Oracle Collaboration History Oracle Collaboration History maintains a history or record of the communication between EBS and the billing applications Using Collaboration History you can track all the events and messages exchanged during a collaboration including exceptions and the XML Payloads where available Setting up Oracle Collaboration History involves the following 3 10 Oracle Telecommunications Billing Integrator Implementation Guide 1 Defining Collaboration History Profile Values page 3 11 2 Defining Lookup Values page 3 11 3 Settingup Collaboration Events page 3 12 4 Setting up Final Collaboration Event page 3 12 Defining Collaboration History Profile Values Log into Oracle Forms and navigate to TBI Setup Profile System Values and set up profile values for Collaboration History Notes The profile values for Collaboration History are 1 CLN Enable History Tracking 2
79. o Address CONCAT HZ_LOCATIONS AD DRESS1 HZ_LOCATI ONS ADDRESS2 HZ_ LOCATIONS ADDRE S3 HZ_LOCATIONS ADDRESS4 HZ_LOCATIONS CI TY HZ LOCATIONS CO UNTRY HZ LOCATIONS CO UNTY Bill To Owner Flag Primary Bill To Flag Unique Identifier of the Customer Customer Name Unique Identifier of the Account Account Name Bill To Address Line of the Account City Country County D 40 Oracle Telecommunications Billing Integrator Implementation Guide STATEPROVN POSTALCODE PARTY EXT ATTRI BUTES ATTRIBUTEI to ATTRIBUTEI5 ACCOUNT EXT AT TRIBUTES ATTRIBUTEI to ATTRIBUTEI5 SHIP TO CONTACT INFO CONTACT NAME PERSON IDENTIFIE R PERSON TITLE PERSON PRE NAM E ADJUNCT PERSON MIDDLE NAME PERSON LAST NA ME ADDRESS ADDRESS BILL TO PARTY IN FO PARTY EXT ATTRI BUTES BILL TO PARTY IN FO ACCOUNT EXT AT TRIBUTES ORDER LINE SHIP TO CONTACT _INFO CONTACT_NAME CONTACT_NAME CONTACT_NAME CONTACT_NAME CONTACT_NAME HZ_LOCATIONS ST ATE HZ_LOCATIONS POSTAL_CODE Party Extended Attributes HZ_PARTIES ATTRI BUTE to HZ_PARTIES ATTRI BUTE15 Account Extended Attributes HZ CUST ACCOUN TS A TTRIBUTEI to ATTRIBUTEI15 Ship to Contact Information Ship to Contact Name HZ_PARTIES PERSO N_IDENTIFIER HZ_PARTIES PERSO N_TITLE HZ_PARTIES PERSO N PRE NAME ADJ UNCT HZ PARTIES PERSO N MIDDLE NAME HZ PARTIES PERSO N LAST
80. o 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 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
81. on related to an organization e 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 Oracle Telecommunications Billing Integrator Implementation Guide e 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 e Customer profile amount for the account e Credit classification details of the account Obsoleted Billing Preference Events The Billing Preference Events obsoleted in this release are e oracle apps ar hz BillingPreference create e oracle apps ar hz BillingPreference update Obsoleted Billing Preference Information The billing preference information obsoleted in this release is e BILL DISPATCH METHOD e BILL FORMAT e BILL LANGUAGE e BILL TYPE e BILL CURRENCY Enhancements to Sales Order Message The following enhancements have been added to a sales order message e 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 Prima
82. or Items Publish 3 20 Oracle Telecommunications Billing Integrator Implementation Guide Name Value Short Name XNB ITEMS PUBLISH Application Telecommunications Billing Integrator Executable XNB ITEMS PUBLISH Submitting the Item Publish Request Update the billing application each time an item is added or updated in the inventory You can do this in two ways 1 Use the batch mode which supports CSVs and XML files 2 Publish the details in a real time asynchronous mode using Item Publish Flow XNBFLOWS ITEM PROCESS TBI uses the workflow process to publish the item product information For both options use the Item Batch Export concurrent program Select the items that need to be published based on the parameters of the concurrent program which initiate the item publish flow Only the items that are invoiceable INVOICEABLE ITEM FLAG N by the external billing applications are published Select the TBI Administrator responsibility to submit an item publish request Navigation Requests Submit Request Notes Request Name Select Telecommunications Billing Integrator Items Publish Billing Application Name of the hub entity code of the billing application From Date Publishes all items updated between the from date and the current date Inventory Organization Inventory organization of the items to be published exported Inventory Category Set Inventory category set of the items to be published exported In
83. orrect Source Trading Partner Location Code All transactions must be set as ENABLED Transactions Enabled for TBI TXN TYPE TXNSUB MAP TYPE CONN HU B USERNAM SRCTP E LOC CODE DOC CONF XNB XNB XNB XNB AO SOO GSO IO XNB TCA _ACCOUN T_OAG72_ OUT XNB_OM_ SALESOR DER_OAG 72_OUT XNB_OM_ GRPSALES ORDER_O AG72 OU T XNB INV ITEM OA G72 OUT XNB HUB XNB HUB XNB HUB XNB HUB XNB XNB XNB XNB XNB XNB XNB XNB 2 If GSO Implementation Tasks for Oracle Telecommunications Billing Integrator 3 9 TXN TYPE TXNSUB MAP CONN HU USERNAM SRCTP DOC TYPE B E LOC CONF CODE XNB CBODI XNB CLN Hub 0 _CBOD_O Entity AG72_IN Code of Billing Applicatio ns gt Defining Trading Partners A trading partner is an entity which exchanges messages with the XML Gateway The trading partner has many transactions enabled for each hub user The transactions enabled for each hub user determines the type of messages generated and the direction of the message The Protocol Type is populated for outbound messages from the hub protocol type Protocol Type is not applicable for inbound messages For more information about setting up trading partners see the Oracle XML Gateway User s Guide Party and Location for the Hub must be created in TCA For details see Oracle Trading Community Architecture User Guide Navigation XML Gateway Setup gt Define Tradi
84. ount Update Message Enhancements to Account Message Enhancements to Sales Order Message Uptake of JMS Compliant Queues in XML Gateway 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 orde
85. password to connect to the Application Spoke DB Consumer WF_JMS_OUT After installation ensure that the aq bridge owner parameter in the adapter ini file is set to the schema name in the Spoke DB Example APPLSYS Optionally to configure the adapter after installation customize the parameters in the adapter ini file Locate the adapter ini file in lt OAI_HOME gt oai 9 0 4 adapters lt ADAPTER_NAME gt folder on the host OAI HOME is the Oracle home of OAI and ADAPTER NAME is the application name given to the adapter Edit the following parameters in adapter ini file application The application name given to the adapter aq bridge host The host name of the Application Spoke DB aq bridge port The DB port of the Application Spoke DB aq bridge instance The SID of the Application Spoke DB Configuring Oracle Applications InterConnect A 3 aq bridge username The username to connect to the Spoke DB e encrypted aq bridge password The encrypted password of the aq bridge username To encrypt a password use the OAI HOME oai 9 0 4 bin encrypt utility from the console This utility generates cipher text and prints it on the console which can be copied to the adapter ini file aq bridge owner The name of the schema to which the AQs in the spoke database belongs This value should be set to a valid schema name before the adapter is started 4 Optionally you can configure the following parameters to improve the perfor
86. pgrade downgrade are made to price packages e 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
87. ponsibility that has access to Oracle Contact Center Use the System Administrator responsibility Navigation Security Responsibility gt Define Steps 1 Query for Menu to identify the root level menu attached to the responsibility 2 Navigate to Application Menu Query for the menu identified in the previous step 3 Add the seeded function XNB OA ACCT BILL DETAILS to the menu with the following values e Function XNB OA BILL DETAILS e Description XNB Account Bill Details OA Page 4 Toenable the Bill Summary UI add the seeded function 3 14 Oracle Telecommunications Billing Integrator Implementation Guide XNB OA ACCT BILL DETAILS to the menu with the following values e Function XNB OA ACCT BILL SUMMARY e Description XNB Account Bill Summary OA Page Personalizing Oracle Contact Center for TBI TBI allows personalization in Oracle Contact Center to invoke the Bill Summary UI You can do this from the Contact Center form Navigation Help Diagnostic Custom Code Personalize 1 Create a Function Name the function Bill Summary Function or as appropriate Select the Enabled check box to enable the function Select the Condition tab and enter the following details e Inthe Trigger Event field enter WHEN NEW FORM INSTANCE e In the Processing Mode field enter Not in Enter Query Mode Select the Actions tab and enter the following details e From the Type list select Menu e From
88. r is created in Oracle Order Management the Order Management order line flow uses the Business Event System to trigger the TBI sales order publish process Each Sales Order line is an individual XML message because each order line corresponds to an item ordered by a customer The figure below gives the workflow process for publishing sales order information Implementation Tasks for Oracle Telecommunications Billing Integrator 3 17 Workflow Process for Publishing Sales Order Information Urreserve 8 99 nd d 3d E Schedule Line Create Supaly Line Ship Line Manual Fulil instaled Base Invoice Interface Line lt Detauk gt Ed poesi Enter Line Service Fullliment Fulil Delened Close Line Fat Activation Required Items End Integrating Workflow Process for Publishing Sales Order Information involves the following 1 Defining Sales Order Line Profile Values page 3 18 2 Creating the Workflow Function page 3 19 Note GSO and Sales Order Line are mutually exclusive Defining Sales Order Line Profile Option The profile option to set the sales order line is XNB Account Republish The values are e NEVER Account information in the sales order line is published only if that account was never published This is the default value e ALWAYS Account information in the sales order line is published till all the billing applications in case of multiple Billing Applications sen
89. rs 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 e 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 e Status Tracking TBI integrates with the Oracle Collaboration History to monitor communication between EBS and the billing applications TBI uses Collaboration History to e 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 e Ensure that order information is published to billing systems only after each billing system has successfully created a party and account e Publish up
90. rt 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
91. ry and Contact E mail Address if available for each order line e Ship To Contact of the Order Line Include the Ship to Contact details Introduction to Telecommunications Billing Integrator 1 7 e 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 e 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 2 Implementing Telecommunications Billing Integrator This chapter lists the implementation considerations for TBI This chapter covers the follow
92. t hub user pwd HubDB TNS Name 7T Runthe following script to start the repository service OAI HOME 0ai 9 0 4 repository start 8 Tostop the repository service use the following command OAI HOME 0ai 9 0 4 repository stop A 2 Oracle Telecommunications Billing Integrator Implementation Guide Setting up OAI Adapter for Advanced Queues The Advanced Queuing Adapter AQ Adapter allows an instance of E Business Suite to send or receive information to and from the OAI Hub The AQ adapter connects to the E Business Suite database and OAI Hub It reads and writes into the advanced queues in the E Business database Use this procedure to install and setup the OAI Adapter for Advanced Queues 1 Install Oracle Application Server InterConnect AQ Adapter v 9 0 4 Provide the following details Hub DB parameters Host Port SID Connection information to the hub database Password Password of the hub schema user App Name Used to identify an application participating in the integration Every instance of an AQ adapter is associated with a particular application Example ORA APPS Application Spoke DB Host Port SID Connection information to the application database on which the advanced queues are configured This information usually pertains to an applications database instance For example myserver domain com lt port number gt mySID Spoke Application Database User and Password User name and
93. us of Agent Listeners sssssssssssseee eene enne 3 13 Setting Up Bill Summary UL sess ener tentent enne nennen 3 13 Defining Bill Summary UI Profile Options sss 3 13 Providing Access and Enabling the Bill Summary UI sssseemm 3 14 Personalizing Oracle Contact Center for TBIL sss Hee 3 15 Accessing the Bill Summary UI from Oracle Contact Center sessssess 3 16 Loading Bill Summary Data eem eem enemies 3 16 Integration with Order Management Workflow Processes sse 3 16 Integrating Workflow Process for Publishing Account Information 3 16 Integrating Workflow Process for Publishing Sales Order Information 3 17 Defining Sales Order Line Profile Option sess eee 3 18 Creating the Workflow Function ssssssssssee eene eene nnne 3 19 Integrating Workflow Process for Publishing Group Sales Order Information 3 19 Setting Up and Running the Item Publish Concurrent Program ussssss 3 19 Item Batch Export Profile Values sssssssssseee eee ene eene 3 20 Submitting the Item Publish Request sess eene 3 21 Subscribing to Account Update Events sss eee ens 3 21 Supported Events nite toe tede ete sient ite nerf Rc rede e de aera 3 2
94. used to identify the Price List Name XML Messages in TBI D 33 INVENTORY ITEM ID INVENTORY ITEM NAME INVENTORY ITEM DESCRIPTION ORG ID DATETIME UNIT SELLING PRI CE UNIT LIST PRICE QUANTITY QUANTITY ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO OE ORDER LINES ALL INVENTORY ITEM ID MTL SYSTEM ITEM S_VL SEGMENT1 MTL_SYSTEM_ITEM S_VL DESCRIPTION OE_ORDER_LINES_ ALL ORG_ID OE_ORDER_LINES_ ALL PRICING_DATE OE_ORDER_LINES_ ALL UNIT_SELLING_PRI CE OE_ORDER_LINES_ ALL UNIT_LIST_PRICE OE_ORDER_LINES_ ALL ORDERED_QUANTI TY OE_ORDER_LINES_ ALL PRICING_QUANTIT Y Inventory Item Id Name of the Product Description of the Product Operating Unit which performed this transaction Determines effective list and price modifiers Actual price charged to customer Price List price for the item Quantity Ordered Quantity based on pricing unit of measure D 34 Oracle Telecommunications Billing Integrator Implementation Guide INVOICE TO ORG I D SHIP TO ORG ID ACTION CURRENCY CODE CHARGE PERIODIC ITY CODE CHARGE PERIODIC ITY CODE DESC ADDRESS ADDRLINE CITY COUNTRY ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ORDER LINE INFO ADDRESS
95. ventory Category Inventory category of the items to be published exported Subscribing to Account Update Events TBI allows you to subscribe to a set of TCA events When the subscribed event occurs TBI verifies if the account updated in TCA is relevant to the billing system If so TBI publishes the account XML message to the billing system The qualifier within the XML message is marked with a U next to the updated information Implementation Tasks for Oracle Telecommunications Billing Integrator 3 21 Navigation TBI Setup gt Subscribe to Events gt Account Update Events Supported Events The following table lists the supported events SI Event Name Event Display Name Description No 1 oracle apps ar hz CustAcctSiteUse CustomerAccount Site Triggered when a new create Usage Create customer account site usage is created 2 oracle apps ar hz CustAcctSiteUse CustomerAccount Site Triggered when a update Usage Update customer account site usage is updated 3 oracle apps ar hz CustAcctRelate c Related Accounts Triggered when a new reate Create customer account relation is created 4 oracle apps ar hz CustAcctRelate u Related Accounts Triggered when a pdate Update customer account relation is updated 5 oracle apps ar hz CustProfileAmt c Customer Profile Triggered when a new reate Amounts Create customer profile amount is created 6 oracle apps ar hz CustProfileAmt u Customer Profile Triggered when a pdate Amounts Update custom
96. 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 Contents Send Us Your Comments Preface 1 Introduction to Telecommunications Billing Integrator Telecommunications Billing Integrator Overview sess 1 1 Telecommunications Billing Integrator Features sss 1 2 Publishing Information to the Billing Applications sssssssee 1 3 Products Used in TBE eoe eoi esee AEE deseen catia t ado ee omae 1 5 Indtunoutiucpeg EEUU 1 5 Grouped Sales Order Message eee emen nemen nnne enn ne 1 6 Publish Bill To Accounts for a Sales Order eem 1 6 Additional TCA Events for Account Update Message 1 6 Enhancements to Account Message ee eene nennen nnne nnne nennen 1 7 Enhancements to Sales Order Message sssssssssssssee eee eene 1 7 Uptake of JMS Compliant Queues in XML Gateway sssssssee ee 1 8 2 Implementing Telecommunications Billing Integrator

Download Pdf Manuals

Related Search

Related Contents

日本語  Hunter Indoor Ceiling Fan User's Manual  Operating Instructions blueplanet 3.0 TL1  Blue Cat`s PatchWork User Manual  Philips 1-cup podholder HD5013/01    Sterling 882.00249.00 Home Theater Server User Manual  SM300 user manual  Product information TD200 english - Service, Support    

Copyright © All rights reserved. Failed to retrieve file