Oracle® Telecommunications Billing Integrator Implementation Guide Release 12 Part No.
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.
Contents Send Us Your Comments Preface 1 Introduction to Telecommunications Billing Integrator Telecommunications Billing Integrator Overview...................................................................1-1 Telecommunications Billing Integrator Features..................................................................... 1-2 Publishing Information to the Billing Applications................................................................ 1-3 Products Used in TBI.......................................
Defining XML Gateway Profile Values.................................................................................... 3-3 Defining UTL_FILE_DIR Parameters....................................................................................... 3-3 Defining XML Standards.......................................................................................................... 3-4 Defining a Hub.....................................................................................................................
B APIs in Telecommunications Billing Integrator Bill Summary Bulk Insert APIs................................................................................................ B-1 Procedure: INSERT_ROW_BATCH ........................................................................................ B-1 Procedure: UPDATE_ROW_BATCH........................................................................................B-2 Bill Summary Public Table Type: BILL_SUMMARIES_TABLE.........................................
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.
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: • The principles and customary practices of your business area.
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.
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.
Oracle Workflow Developer's Guide This guide explains how to define new workflow business processes and customize existing Oracle Applications-embedded workflow processes. It also describes how to define and customize business events and event subscriptions. Installation and System Administration Oracle Applications Concepts This book is intended for all those planning to deploy Oracle E-Business Suite Release 12, or contemplating significant changes to a configuration.
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.
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 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.
1 Introduction to Telecommunications Billing Integrator This chapter provides a brief introduction to the features in TBI.
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.
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.
TBI subscribes to a set of TCA events related to account updates. TBI generates and publishes an account message to the billing system when changes relevant to the billing system are made to accounts in TCA. The updated information is marked in the message. For example: If the credit classification information of an account (relevant to the billing system) is changed in TCA, TBI publishes the account message with the Credit Classification section marked as "U" (Updated).
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.
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.
• oracle.apps.ar.hz.ContactPoint.update: This event is triggered when there are changes to information about how to communicate to parties or party sites using electronic media such as Electronic Data Interchange (EDI), e-mail, telephone, telex, and the Internet. Enhancements to Account Message The information added to the account message is: • Customer profile amount for the account. • Credit classification details of the account.
• Payment Term for the Order Line: Include the payment terms. This information is used to calculate when a payment is due and factor in any discounts that are given for early payment. • Periodicity Details of the Order Line: Include periodicity details to indicate how often a service is charged. Uptake of JMS Compliant Queues in XML Gateway XML Gateway generates XML messages in JMS format.
2 Implementing Telecommunications Billing Integrator This chapter lists the implementation considerations for TBI.
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.
3 Implementation Tasks for Oracle Telecommunications Billing Integrator This chapter discusses the tasks to implement Oracle Telecommunications Billing Integrator.
• Providing Access and Enabling the Bill Summary UI • Personalizing Oracle Contact Center for TBI • Accessing the Bill Summary UI from Oracle Contact Center • Loading Bill Summary Data • Integration with Order Management Workflow Processes • Integrating Workflow Process for Publishing Account Information • Integrating Workflow Process for Publishing Sales Order Information • Defining Sales Order Line Profile Option • Creating the Workflow Function • Integrating Workflow Process for Publis
Navigation: TBI setup > profile system values. Notes Unless otherwise mentioned, use the TBI administrator responsibility to complete the setups mentioned in this chapter. Setting Up XML Gateway You must have the TBI Administrator responsibility to access Oracle XML Gateway database and forms. Setting up XML Gateway or TBI involves the following: 1. Defining XML Gateway Profile Values, page 3-3 2. Defining UTL_FILE_DIR Parameters, page 3-3 3. Defining XML Standards, page 3-4 4.
Defining XML Standards Define Open Applications Group (OAG) as the XML standard. Navigation: Oracle XML Gateway Setup > Define XML Standards. Notes Standard Code: This is the name or code for the standard body of the XML messages. Enter 'OAG' Standard Type: Enter 'XML'. Defining a Hub A hub is defined as an integration point within your network. Navigation: Oracle XML Gateway Setup > Define Hubs. Notes Name: Enter 'XNB_HUB'. Protocol Type: Select JMS.
• The names representing the billing applications setup in the hub must be unique. • Hub entity code values for the various billing applications must be same as the key value from BSR.SENDER.COMPONENT. Defining Transactions Internal transactions are used by the XML Gateway Execution Engine. Internal transactions are associated with the trading partner in the trading partner setup. Each internal transaction is associated with a number of external transactions that participate in the integration.
• Inventory Item Outbound, page 3-8 • Confirm BOD Inbound, page 3-8 Account Outbound Internal Transaction The following table lists the attributes and values for the account outbound transaction.
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. TYPE EXT. TXN.
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. TYPE EXT. TXN.
External Transactions for Confirm BOD Inbound STD CODE DIR EXT. TXN. TYPE EXT. TXN. SUBTYPE QUEUE OAG IN BOD CONFIRM 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 correct Source Trading Partner Location Code. All transactions must be set as ENABLED.
TXN TYPE TXN SUB TYPE MAP CONN/HU B USERNAM E SRCT P LOC CODE DOC CONF XNB CBODI XNB_CLN _CBOD_O AG72_IN - - 0 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.
1. Defining Collaboration History Profile Values, page 3-11 2. Defining Lookup Values, page 3-11 3. Setting up 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. CLN: Debug Level 3.
Lookup Type Lookup Code Description Enable d? CLN_COLLABORATION _TYPE XNB_ACCOUNT TBI Account Y CLN_COLLABORATION _TYPE XNB_SALESORDER TBI Sales Order Y CLN_COLLABORATION _DOC_TYPE XNB_SYNC_ITEM TBI Sync Item Y CLN_COLLABORATION _DOC_TYPE XNB_SYNC_ACCOUNT TBI Sync Account Y CLN_COLLABORATION _DOC_TYPE XNB_ADD_SALESORDE R TBI Add Sales Order Y Note: After updating the lookup values, bounce the Apache server on the environment only if the values are not reflected in the Collaboration
Final Event Definition Checking Status of Agent Listeners The following Agent Listeners must be running for TBI to function: • Workflow Deferred Agent Listener • Workflow Deferred Notification Agent Listener • Workflow Error Agent Listener • Workflow Inbound Notifications Agent Listener • Workflow Inbound JMS Agent Listener Navigation: Workflow Administrator : Oracle Applications Manager > Workflow Manager. Click the Agent listeners icon.
Bill Summary UI Profiles Values Profile Option Value XNB: Bill Image Source Specifies the source of the image displayed on the bill. The values are: XNB: Bill Image Location • 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_OA_ACCT_BILL_DETAILS to the menu with the following values: • Function: XNB_OA_ACCT_BILL_SUMMARY • 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. 2.
• In the Function Code field, enter XNB_OA_ACCT_BILL_SUMMARY. • In the 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.
Workflow Process for Publishing Account Information Navigation: In WorkFlow Builder, open the OM Order Header (OEOH) workflow. Notes Enter the following parameters: • Internal Name: XNB_ACCOUNT_PUBLISH • Display Name: XNB Account Publish • Function Name: xnb_cmn_pvt.
Workflow Process for Publishing Sales Order Information 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.
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 • 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.
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.
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'.
Navigation: TBI Setup > Subscribe to Events > Account Update Events. Supported Events The following table lists the supported events. 3-22 Sl. No Event Name Event Display Name Description 1 oracle.apps.ar.hz.CustAcctSiteUse. create CustomerAccount Site Usage Create Triggered when a new customer account site usage is created. 2 oracle.apps.ar.hz.CustAcctSiteUse. update CustomerAccount Site Usage Update Triggered when a customer account site usage is updated. 3 oracle.apps.ar.hz.
Sl. No Event Name Event Display Name Description 10 oracle.apps.ar.hz.CustomerProfile. update Customer Profile Update Triggered when Customer Profile details are updated. 11 oracle.apps.ar.hz.ContactPoint.up date Contact Points Update 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.
A Configuring Oracle Applications InterConnect This appendix provides information on configuring Oracle Applications InterConnect (OAI). This appendix covers the following topics: • Oracle Applications InterConnect Overview • Setting Up OAI Hub • Setting up OAI Adapter for Advanced Queues • Dropping the Hub Schema • Importing OAI Maps to the Repository Oracle Applications InterConnect Overview Oracle Applications InterConnect (OAI 9.0.4) is the middleware for TBI.
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: 3. 4. • HOST: SID: PORT information for the new database instance. • Passwords for system and users for the new database instance.
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.
4. • aq_bridge_username: The username to connect to the Spoke DB. • 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.
2. Run the following script from the console to stop the repository service: /oai/9.0.4/repository/stop 3. Run the following script at the command prompt: /oai/9.0.4/repository/hubschema –drop system/ 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.
B APIs in Telecommunications Billing Integrator This appendix provides information on the APIs in TBI. This appendix covers the following topics: • Bill Summary Bulk Insert APIs • Procedure: INSERT_ROW_BATCH • Procedure: UPDATE_ROW_BATCH • Bill Summary Public Table Type: BILL_SUMMARIES_TABLE • 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.
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: x_msg_data OUT VARCHAR2 • S: When the operation is a success. • E: When the operation is not a success due to a known error.
Procedure: UPDATE_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 update operation. The values returned are: x_msg_data OUT VARCHAR2 • S : When the operation is a success. • E: When the operation is not a success due to a known error.
Specifications for BILL_SUMMARIES_REC Attribute Name Data Type Description VARCHAR2(30) Account Number of the customer that must exist in Oracle E-Business Suite. This field is mandatory for insert record. Mandatory attributes account_number The foreign key is hz_cust_accounts.account_nu mber. B-4 bill_number VARCHAR2(30) Bill reference number. This field is for insert and update record and must be unique. billing_vendor_name VARCHAR2 (240) Name of the billing vendor.
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 VARCHAR2 (30) - bill_location_url VARCHAR2 (240) Location of the bill online. due_now VARCHAR2 (30) Amount currently due for an account.
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: • Maps and DTDs Overview • Loading and Deleting Maps • Loading and Deleting DTDs Maps and DTDs Overview TBI provides predefined maps and the corresponding DTDs for the XML Gateway.
Supported Flow Map Internal Name Inventory Item Publish XNB_INV_ITEM_OAG72_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_ OAG72_OUT.
• oagis_entity_extensions.dtd • oagis_extensions.dtd • oagis_fields.dtd • oagis_resources.dtd • 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 Map. $ java oracle.apps.ecx.loader.
C-4 • dtd_name.dtd : TBI specific DTDs. • root_element: root element of the DTD.
D XML Messages in TBI This appendix provides information on the XML messages in TBI.
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 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.
JMS Message Structure HEADER Main Header HEADER.REPLYTO Reply to Information HEADER.REPLYTO.NAME Name of the Application Replied To HEADER.REPLYTO.ADDRESS Address of the Application Replied To HEADER.REPLYTO.PROTOCOL Protocol Used in Replying HEADER.USERID User Id HEADER.APPID Application Id HEADER.GROUPID Group Id HEADER.GROUPSEQ Group Sequence HEADER.
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.
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.
Structure of the CBOD XML Message Structure of the CBOD XML Message
06 0000 +0000 00 THE BOD WAS PROCESSED SUCCESSFULLY Seeded XML Messages TBI provides seeded XML messages for the following: • Account information • Sales order information • Item information • GSO Message Specifications for Account Information The following table lists the message specifications for account info
ACCOUNT_NAME ACCOUNT_INFO HZ_CUST_ACCOUN TS. ACCOUNT_NAME Description chosen by external party. DATETIME ACCOUNT_INFO HZ_CUST_ACCOUN TS. ACCOUNT_ESTABLI SHED_DATE Date when the customer account was originally established. TAX_CODE ACCOUNT_INFO HZ_CUST_ACCOUN TS. TAX_CODE Tax code for this customer. TAX_HEADER_LEV EL ACCOUNT_INFO HZ_CUST_ACCOUN TS. TAX_HEADER_LEV EL_FLAG Indicate if item is tax header or a line item. HOLD_BILL_FLAG ACCOUNT_INFO HZ_CUST_ACCOUN TS.
RELATIONSHIP_TY PE RELATED_ACCOUN TS HZ_CUST_ACCT_RE LATE_ALL. RELATIONSHIP_TY PE Relationship Type ORG_ID RELATED_ACCOUN TS HZ_CUST_ACCT_RE LATE_ALL.ORG_ID Organization Id BILL_TO_FLAG RELATED_ACCOUN TS HZ_CUST_ACCT_RE LATE_ALL.BILL_TO _FLAG Bill To Relationship Flag SHIP_TO_FLAG RELATED_ACCOUN TS HZ_CUST_ACCT_RE LATE_ALL.SHIP_TO _FLAG Ship To Relationship Flag TAX_EXEMPTIONS DATAAREA Tax Data - EXEMPTION_TYPE TAX_EXEMPTIONS RA_TAX_EXEMPTIO NS_ALL.
DATETIME TAX_EXEMPTIONS RA_TAX_EXEMPTIO NS_ALL. START_DATE First date that this exemption is effective. REASON_CODE TAX_EXEMPTIONS RA_TAX_EXEMPTIO NS_ALL. REASON_CODE The reason for this exemption. EXEMPT_PERCENT1 TAX_EXEMPTIONS RA_TAX_EXEMPTIO NS_ALL. EXEMPT_PERCENT1 Percentage of the exemption to apply to this portion of the Sales Tax Location Flexfield. EXEMPT_PERCENT2 TAX_EXEMPTIONS RA_TAX_EXEMPTIO NS_ALL.
RECEIPT_METHOD_ NAME RECEIPT_METHODS AR_RECEIPT_METH ODS. RECEIPT_METHOD_ NAME Receipt Method Name PRIMARY_FLAG RECEIPT_METHODS RA_CUST_RECEIPT_ METHODS.PRIMAR Y_FLAG Indicates if customer receipt method is primary. DATETIME RECEIPT_METHODS RA_CUST_RECEIPT_ METHODS.START_D ATE Start date of the customer receipt methods DATETIME RECEIPT_METHODS RA_CUST_RECEIPT_ METHODS.
EMAIL_ADDRESS CUSTOMER_INFO HZ_PARTIES.EMAIL _ADDRESS Email Address CUSTOMER_NAME CUSTOMER_INFO Name of the Customer - PERSON_IDENTIFIE R CUSTOMER_NAME HZ_PARTIES.PERSO N_IDENTIFIER Personal identifier, such as driver's license or passport number. PERSON_TITLE CUSTOMER_NAME HZ_PARTIES.PERSO N_TITLE A professional or family title. For example, Don or The Right Honorable. PERSON_PRE_NAM E_ CUSTOMER_NAME HZ_PARTIES.PERSO N_PRE_NAME_ADJ UNCT Salutary introduction, such as Mr. or Herr.
ADDRLINE ADDRESS CONTACT( HZ_PARTIES.ADDR ESS1; HZ_PARTIES.ADDR ESS2; HZ_PARTIES.ADDR ESS3; HZ_PARTIES.ADDR ESS4) Identifying Address Line of the Customer CITY ADDRESS HZ_PARTIES.CITY City COUNTRY ADDRESS HZ_PARTIES.COUN TRY Country COUNTY ADDRESS HZ_PARTIES.COUN TY County STATEPROVN ADDRESS HZ_PARTIES.STATE State POSTALCODE ADDRESS HZ_PARTIES.
PARENT_RELATIO NSHIP_TYPE RELATIONSHIP_INF O HZ_RELATIONSHIP S. RELATIONSHIP_CO DE Either a forward or a backward relationship code DATETIME RELATIONSHIP_INF O HZ_RELATIONSHIP S.END_DATE Date relationship ends CUSTOMER_CONT ACT_INFO CUSTOMER_INFO Customer Contact Information - CONTACT_POINT_I D CUSTOMER_CONT ACT HZ_CONTACT_POI NTS.CONTACT_POI NT_TYPE Identifier for the customer contact point. HZ_CONTACT_POI NTS.
EDI_PAYMENT_FOR MAT CUSTOMER_CONT ACT _INFO EMAIL_ADDRESS CUSTOMER_CONT ACT _INFO URL CUSTOMER_CONT ACT HZ_CONTACT_POI NTS.EDI_PAYMENT _FORMAT 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. HZ_CONTACT_POI NTS.EMAIL_ADDRE SS E-mail address of the contact point HZ_CONTACT_POI NTS.URL Uniform resource locator HZ_CONTACT_POI NTS.PHONE_LINE_ TYPE Lookup code for the type of phone line.
PARTY_GROUP CUSTOMER_CONT ACT Party Group Code - _INFO GROUP PARTY_GROUP AST_PARTY_CLASSI FICATION_V.CLASS _CODE Classification code BANK_ACCOUNT_I NFO DATAAREA Bank Account Information - BANK_ACCOUNT BANK_ACCOUNT_I NFO IBY_EXT_BANK_AC COUNTS.BANK_AC COUNT_NUM Bank Account Number BANK_ACCOUNT_ NAME BANK_ACCOUNT_I NFO IBY_EXT_BANK_AC COUNTS. BANK_ACCOUNT_ NAME Bank Account Name BANK_BRANCH_ID BANK_ACCOUNT_I NFO IBY_EXT_BANK_AC COUNTS.
ADDRLINE ADDRESS CONTACT( HZ_LOCATIONS.AD DRESS1;HZ_LOCATI ONS.ADDRESS2;HZ_ LOCATIONS.ADDRE SS3;HZ_LOCATIONS . Bill To Address Line of the Account ADDRESS4) CITY ADDRESS HZ_LOCATIONS.CI TY City COUNTRY ADDRESS HZ_LOCATIONS.CO UNTRY Country COUNTY ADDRESS HZ_LOCATIONS.CO UNTY County STATEPROVN ADDRESS HZ_LOCATIONS.ST ATE State POSTALCODE ADDRESS HZ_LOCATIONS.
D-18 AMOUNT CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS. OVERALL_CREDIT_ LIMIT Over All Credit limit AMOUNT CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS. MIN_DUNNING_A MOUNT Minimum dunning amount AMOUNT CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS. MIN_DUNNING_IN VOICE_AMOUNT Minimum invoice amount MAX_INTEREST_CH ARGE CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS. MAX_INTEREST_CH ARGE Maximum interest charge AMOUNT CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS.
DATETIME CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS. EXPIRATION_DATE Expiration date ATTRIBUTE_CATEG ORY CUST_PROFILE_AM TS_INFO HZ_CUST_PROFILE_ AMTS. ATTRIBUTE_CATEG ORY Attribute category PROFILE_AMTS_EX TENDED_ATTRIBUT ES CUST_PROFILE_AM TS_INFO Profile Amounts Extended Attributes - ATTRIBUTE1 to ATTRIBUTE15 PROFILE_AMTS_EX TENDED_ATTRIBUT ES HZ_CUST_PROFILE_ AMTS.
STANDARD_TERMS CREDIT_CLASSIFIC ATION_INFO HZ_CUSTOMER_PR OFILES. STANDARD_TERMS Standard terms OVERRIDE_TERMS CREDIT_CLASSIFIC ATION_INFO HZ_CUSTOMER_PR OFILES. OVERRIDE_TERMS Override terms DATETIME CREDIT_CLASSIFIC ATION_INFO HZ_CUSTOMER_PR OFILES. LAST_CREDIT_REVI EW_DATE Last credit review date CREDIT_CLASSIFIC ATION CREDIT_CLASSIFIC ATION_INFO HZ_CUSTOMER_PR OFILES.
TOP_MODEL_LINE_ ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. TOP_MODEL_LINE_ ID LINK_TO_LINE_ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. LINK_TO_LINE_ID Identifier of configuration top parent line Identifier of immediate parent component line ORDER_NUMBER ORDER_HEADER_I NFO OE_ORDER_HEADE RS_ALL.ORDER_NU MBER Unique Identifier for Order SOLD_TO_PARTY_ ORDER_HEADER_I NFO HZ_PARTIES. Unique Identifier for Customer SOLD_TO_ PARTY_NAME ORDER_HEADER_I NFO HZ_PARTIES.
INVENTORY_ITEM_ NAME ORDER_LINE_INFO MTL_SYSTEM_ITEM S_VL.SEGMENT1 Name of the Product INVENTORY_ITEM_ DESCRIPTION ORDER_LINE_INFO MTL_SYSTEM_ITEM S_VL.DESCRIPTION Description of the Product ORG_ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. Operating Unit which performed this transaction ORG_ID DATETIME ORDER_LINE_INFO OE_ORDER_LINES_ ALL. PRICING_DATE UNIT_SELLING_PRI CE ORDER_LINE_INFO OE_ORDER_LINES_ ALL.
SHIP_TO_ORG_ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. Ship To Organization ID SHIP_TO_ORG_ID ACTION ORDER_LINE_INFO OE_TRANSACTION _TYPES_TL.ACTION Type of Service performed on the Order CURRENCY_CODE ORDER_LINE_INFO QP_LIST_HEADERS_ VL.CURRENCY_CO DE Currency Code CHARGE_PERIODIC ITY_CODE ORDER_LINE_INFO OE_ORDER_LINES_ ALL.CHARGE_PERI ODICITY_CODE Charge Periodicity Code CHARGE_PERIODIC ITY_CODE_DESC ORDER_LINE_INFO MTL_UOM_CONVE RSIONS.
STATEPROVN ADDRESS HZ_LOCATIONS.ST ATE State POSTALCODE ADDRESS HZ_LOCATIONS. Postalcode POSTAL_CODE TAX_INFO ORDER_LINE_INFO Tax Information - TAX_CODE TAX_INFO OE_ORDER_LINES_ ALL. Tax code for the line TAX_CODE TAX_RATE TAX_INFO OE_ORDER_LINES_ ALL. Tax rate in percentage TAX_RATE DATETIME TAX_INFO OE_ORDER_LINES_ ALL. Date for tax calculation TAX_DATE AMOUNT TAX_INFO OE_ORDER_LINES_ ALL.
ATTRIBUTE1 to ATTRIBUTE15 EXT_ATTRIBUTES OE_ORDER_LINES_ ALL. ATTRIBUTE1 to ATTRIBUTE15 Descriptive Flexfield segments for Order Line INSTALL_BASE_INF O DATAAREA INSTALL_BASE_INF O - INSTANCE_ID INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. Unique ID that identifies an item unit instance INSTANCE_ID INSTANCE_NAME INSTALL_BASE_INF O CSI_ITEM_INSTANC ES.INSTANCE_DESC RIPTION Used to describe the Instance Id DATETIME INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. Installation Date for an Instance.
LAST_OE_ORDER_L INE_ID INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. LAST_OE_ORDER_L INE_ Last Order Line Identifier that touched the instance ID ADDRESS INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. Install At Address INSTALL_AT_ADDR ESS D-26 ATTRIBUTE_VALUE S INSTALL_BASE_INF O Attribute Value Pairs of Install Base - ATTRIBUTE_INFO ATTRIBUTE_VALUE S Attribute Information - ATTRIBUTE_ID ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.
ATTRIBUTE_NAME ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.ATTRIBUTE_ NAME Attribute Name ATTRIBUTE_CATEG ORY ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.ATTRIBUTE_ CATEGORY Attribute Category DESCRIPTION ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.DESCRIPTIO N Description ACTIVE_START_DA TE ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.ACTIVE_STA RT_DATE Activation Start Date ACTIVE_END_DATE ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.
BILL_TO_OWNER_F LAG BILL_TO_PARTY_IN FO HZ_PARTIES.BILL_T O_OWNER_FLAG Bill To Owner Flag PRIMARY_BILL_TO_ FLAG BILL_TO_PARTY_IN FO HZ_PARTIES.PRIMA RY_BILL_TO_FLAG Primary Bill To Flag BILL_TO_PARTY_N UMBER BILL_TO_PARTY_IN FO HZ_PARTIES.PARTY _NUMBER Unique Identifier of the Customer BILL_TO_PARTY_N AME BILL_TO_PARTY_IN FO HZ_PARTIES.PARTY _NAME Customer Name BILL_TO_ACCOUNT _NUMBER BILL_TO_PARTY_IN FO HZ_CUST_ACCOUN TS.
STATEPROVN ADDRESS HZ_LOCATIONS.ST ATE State POSTALCODE ADDRESS HZ_LOCATIONS. Postal code POSTAL_CODE PARTY_EXT_ATTRI BUTES BILL_TO_PARTY_IN FO Party Extended Attributes - ATTRIBUTE1 to ATTRIBUTE15 PARTY_EXT_ATTRI BUTES HZ_PARTIES.ATTRI BUTE1 to HZ_PARTIES.ATTRI BUTE15 Descriptive Flexfield segment for Customer ACCOUNT_EXT_AT TRIBUTES BILL_TO_PARTY_IN FO Account Extended Attributes - ATTRIBUTE1 to ATTRIBUTE15 ACCOUNT_EXT_AT TRIBUTES HZ_CUST_ACCOUN TS.
PERSON_NAME_SU FFIX CONTACT_NAME HZ_PARTIES.PERSO N_NAME_SUFFIX Suffix SALUTATION SHIP_TO_CONTACT _INFO HZ_PARTIES.SALUT ATION Salutation CONTACT_INFO SHIP_TO_CONTACT _INFO Ship to Contact Information - CONTACT_POINT_T YPE CONTACT_INFO HZ_CONTACT_POI NTS.CONTACT_POI NT_TYPE Contact Point Type EMAIL_ADDRESS CONTACT_INFO HZ_CONTACT_POI NTS.EMAIL_ADDRE SS Email Address PHONE_LINE_TYPE CONTACT_INFO HZ_CONTACT_POI NTS.
Message Specifications for Product XML Tag Parent Component Field in E-Business Suite Description ITEM_INFO DATAAREA Item Information - ITEMID ITEM_INFO MTL_SYSTEM_ITEM S_VL. INVENTORY_ITEM_ ID EBS Inventory Item Identifier ITEM_NAME ITEM_INFO MTL_SYSTEM_ITEM S_VL.SEGMENT1 EBS Inventory item ITEM_TYPE ITEM_INFO MTL_SYSTEM_ITEM S_VL.ITEM_TYPE Inventory Item Type ITEM_TYPE_DESC ITEM_INFO FND_LOOKUP_VAL UES_VL.
DATETIME ITEM_INFO MTL_SYSTEM_ITEM S_VL. Start date for the item START_DATE_ACTI VE DATETIME ITEM_INFO MTL_SYSTEM_ITEM S_VL. End date for the item END_DATE_ACTIVE ITEM_CLASS ATTRIBUTE1 to ATTRIBUTE15 ITEM_INFO ITEM_INFO MTL_SYSTEM_ITEM S_VL. Derive from the UOM CLASS. PRIMARY_UOM_CO DE As this is not stored in any entity and it is derived from UOM we need to know all the distinct values of UOM MTL_SYSTEM_ITEM S_VL.
SOLD_TO_ACCOUN T_ ORDER_HEADER_I NFO NUMBER SOLD_TO_ACCOUN T_ Unique Identifier for Account ACCOUNT_NUMBE R ORDER_HEADER_I NFO NAME SOLD_TO_PARTY_ HZ_CUST_ACCOUN TS. HZ_CUST_ACCOUN TS. Account Name ACCOUNT_NAME ORDER_HEADER_I NFO HZ_PARTIES. SOLD_TO_ PARTY_NAME ORDER_HEADER_I NFO HZ_PARTIES.
INVENTORY_ITEM_ ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. Inventory Item Id INVENTORY_ITEM_ ID INVENTORY_ITEM_ NAME ORDER_LINE_INFO MTL_SYSTEM_ITEM S_VL.SEGMENT1 Name of the Product INVENTORY_ITEM_ DESCRIPTION ORDER_LINE_INFO MTL_SYSTEM_ITEM S_VL.DESCRIPTION Description of the Product ORG_ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. Operating Unit which performed this transaction ORG_ID DATETIME ORDER_LINE_INFO OE_ORDER_LINES_ ALL.
INVOICE_TO_ORG_I D ORDER_LINE_INFO OE_ORDER_LINES_ ALL. Invoice To Organization ID INVOICE_TO_ORG_I D SHIP_TO_ORG_ID ORDER_LINE_INFO OE_ORDER_LINES_ ALL. Ship To Organization ID SHIP_TO_ORG_ID ACTION ORDER_LINE_INFO OE_TRANSACTION _TYPES_TL.ACTION Type of Service performed on the Order CURRENCY_CODE ORDER_LINE_INFO QP_LIST_HEADERS_ VL.CURRENCY_CO DE Currency Code CHARGE_PERIODIC ITY_CODE ORDER_LINE_INFO OE_ORDER_LINES_ ALL.
COUNTY ADDRESS HZ_LOCATIONS.CO UNTY County STATEPROVN ADDRESS HZ_LOCATIONS.ST ATE State POSTALCODE ADDRESS HZ_LOCATIONS. Postalcode POSTAL_CODE TAX_INFO ORDER_LINE_INFO Tax Information - TAX_CODE TAX_INFO OE_ORDER_LINES_ ALL. Tax code for the line TAX_CODE TAX_RATE TAX_INFO OE_ORDER_LINES_ ALL. The tax rate in percentage TAX_RATE DATETIME TAX_INFO OE_ORDER_LINES_ ALL. It will store the date for tax calculation TAX_DATE AMOUNT TAX_INFO OE_ORDER_LINES_ ALL.
EXT_ATTRIBUTES ORDER_LINE_INFO Order Line Extended Attributes - ATTRIBUTE1 to ATTRIBUTE15 EXT_ATTRIBUTES OE_ORDER_LINES_ ALL. Descriptive Flexfield segment for Order Line ATTRIBUTE1 INSTALL_BASE_INF O ORDER_LINE INSTALL_BASE_INF O - INSTANCE_ID INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. Unique ID that identifies an item unit instance INSTANCE_ID INSTANCE_NAME INSTALL_BASE_INF O CSI_ITEM_INSTANC ES.
LAST_OE_ORDER_L INE_ID INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. LAST_OE_ORDER_L INE_ Last Order Line Identifier that touched the Instance ID ADDRESS INSTALL_BASE_INF O CSI_ITEM_INSTANC ES. Install At Address INSTALL_AT_ADDR ESS D-38 ATTRIBUTE_VALUE S INSTALL_BASE_INF O Attribute Value Pairs of Install Base - ATTRIBUTE_INFO ATTRIBUTE_VALUE S Attribute Information - ATTRIBUTE_ID ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.
ATTRIBUTE_NAME ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.ATTRIBUTE_ NAME Attribute Name ATTRIBUTE_CATEG ORY ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.ATTRIBUTE_ CATEGORY Attribute Category DESCRIPTION ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.DESCRIPTIO N Description ACTIVE_START_DA TE ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.ACTIVE_STA RT_DATE Activation Start Date ACTIVE_END_DATE ATTRIBUTE_INFO CSI_I_EXTENDED_A TTRIBS.
BILL_TO_OWNER_F LAG BILL_TO_PARTY_IN FO HZ_PARTIES.BILL_T O_OWNER_FLAG Bill To Owner Flag PRIMARY_BILL_TO_ FLAG BILL_TO_PARTY_IN FO HZ_PARTIES.PRIMA RY_BILL_TO_FLAG Primary Bill To Flag BILL_TO_PARTY_N UMBER BILL_TO_PARTY_IN FO HZ_PARTIES.PARTY _NUMBER Unique Identifier of the Customer BILL_TO_PARTY_N AME BILL_TO_PARTY_IN FO HZ_PARTIES.PARTY _NAME Customer Name BILL_TO_ACCOUNT _NUMBER BILL_TO_PARTY_IN FO HZ_CUST_ACCOUN TS.
STATEPROVN ADDRESS HZ_LOCATIONS.ST ATE State POSTALCODE ADDRESS HZ_LOCATIONS. Postalcode POSTAL_CODE PARTY_EXT_ATTRI BUTES BILL_TO_PARTY_IN FO Party Extended Attributes - ATTRIBUTE1 to ATTRIBUTE15 PARTY_EXT_ATTRI BUTES HZ_PARTIES.ATTRI BUTE1 to HZ_PARTIES.ATTRI BUTE15 Descriptive Flexfield segment for Customer ACCOUNT_EXT_AT TRIBUTES BILL_TO_PARTY_IN FO Account Extended Attributes - ATTRIBUTE1 to ATTRIBUTE15 ACCOUNT_EXT_AT TRIBUTES HZ_CUST_ACCOUN TS.
D-42 PERSON_NAME_SU FFIX CONTACT_NAME HZ_PARTIES.PERSO N_NAME_SUFFIX Suffix SALUTATION SHIP_TO_CONTACT _INFO HZ_PARTIES.SALUT ATION Salutation CONTACT_INFO SHIP_TO_CONTACT _INFO Ship to Contact Information - CONTACT_POINT_T YPE CONTACT_INFO HZ_CONTACT_POI NTS.CONTACT_POI NT_TYPE Contact Point Type EMAIL_ADDRESS CONTACT_INFO HZ_CONTACT_POI NTS.EMAIL_ADDRE SS Email Address PHONE_LINE_TYPE CONTACT_INFO HZ_CONTACT_POI NTS.
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 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.
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.
Index A P Agent Listeners, list of, 3-13 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 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 S Starting Adapter, A-4 Stopping Adapter, A-4 T Transactions, internal, 3-5
