Oracle ETPM-EBS Integration Implementation Guide

Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and
Accounts Payable
Release 3.1.1 Implementation Guide Oracle Enterprise Taxation and Policy Management v2.3.0 Oracle E-Business Suite Financials for General Ledger and Accounts Payable v12.1.1 E23084-01 April 2011
Copyright 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
ii
Copyright 2000, 2011, Oracle. All rights reserved.
Table of Contents
Part 1: Understanding the Integration ....................................................................................................... 1 Overview .................................................................................................................................................... 1 Additional Resources ............................................................................................................................. 1 About the Integration Product .................................................................................................................... 2 About the Products ................................................................................................................................ 2 Supported Business Processes ............................................................................................................. 2 Process Scheduling ............................................................................................................................... 4 Best Practices ...................................................................................................................................... 10 About the Integration............................................................................................................................ 14 Part 2: Implementing the Integration Product .......................................................................................... 17 Setting Up the Process Integration .......................................................................................................... 17 Prerequisites ........................................................................................................................................ 17 Assumptions ........................................................................................................................................ 17 Configuration Check List ...................................................................................................................... 18 Configuring the Integration .................................................................................................................. 22 Setting up Security ............................................................................................................................... 34 Verifying the Implementation ............................................................................................................... 35 Troubleshooting ....................................................................................................................................... 37 E-mail Notification ................................................................................................................................ 37 Locating Error Logs.............................................................................................................................. 38 Error Resolution ................................................................................................................................... 40 Customization Options ............................................................................................................................ 44 Extension Methods .............................................................................................................................. 44 Available Extension Points .................................................................................................................. 45 Extension Points .................................................................................................................................. 51 Appendix .................................................................................................................................................. 54 Data Mapping ....................................................................................................................................... 54 Database Tables Involved in Integration ............................................................................................. 82 Logic Used in the Integration Points .................................................................................................... 84 BPEL Process Overview ...................................................................................................................... 87
iii
Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Release 3.1.1 Implementation Guide
Part 1: Understanding the Integration

This section provides an overview of the participating applications and information regarding the business processes addressed by this integration.
Overview
This document provides configuration and administration information for the integration between Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger (GL) and Accounts Payable (A/P).
Additional Resources
The following additional resources are available: Resource Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Release 3.1.1 Installation Guide Oracle Enterprise Taxation and Policy Management Documentation for Release v2.3.0 Oracle E-Business Suite Financials for General Ledger and Accounts Payable Documentation for Release v12.1.1 Managing BPEL Location Same folder as this document, with the distribution for this product.
Refer to Oracle Enterprise Taxation and Policy Management documentation located on e-delivery. Refer to Oracle E-Business Suite Financials for General Ledger and Accounts Payable documentation located on e-delivery.
http://www.oracle.com/technology/documentation/index.html
About the Integration Product

This section provides general information about the functionality and processing of the Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. This is an AIA Direct Integration using SOA and does not require AIA Foundation Pack to be installed.
About the Products

Oracle Enterprise Taxation and Policy Management Oracle Enterprise Taxation and Policy Management (ETPM) is a robust application which manages every aspect of taxation operations, including registering taxpayers, processing forms, payment processing, taxpayer accounting, collections, and case management. Oracle E-Business Suite Financials for General Ledger and Accounts Payable Oracle E-Business Suite (EBS) is a resource-planning software which enforces industrys bestpractice controls on data input and process flows as tasks are completed within the system. Processes are separated into modules, and each module consists of a collection of forms where data is entered at each stage of the business process. As part of the Enterprise Resource Planning functionality, Oracle E-Business Suite Financials for General Ledger and Accounts Payable offers flexible ledger architecture, consistent financial and operational information, dynamic planning, budgeting and forecasting, and multi-dimensional profitability analysis. Oracle BPEL Process Manager The Oracle Fusion Middleware product, Oracle BPEL Process Manager, coordinates the data flow and data mapping of the integration. Used as an Oracle standard across most integrations, Oracle BPEL Process Manager provides a comprehensive solution for creating, deploying, and managing cross-application business processes with both automated and manual workflow steps. It supports standards such as BPEL, XML, XSLT, XPATH, JMS, JCA, and Web Services.
Supported Business Processes

The Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable incorporates three integration points to facilitate transfer of information between the two applications. Data is sent from Oracle Enterprise Taxation and Policy Management to Oracle E-Business Suite and vice versa to support the following transactions and actions: Oracle Enterprise Taxation and Policy Management Bill is created/ cancelled Payment is created/ cancelled
2
Oracle E-Business Suite The general ledger is updated with the journal information.
Oracle Enterprise Taxation and Policy Management Adjustment is created/ cancelled Adjustment whos type indicates A/P Request is created
Oracle E-Business Suite
Taxpayer and A/P Request information is used to create a one-time supplier and supplier site. An accounts payable invoice is created and associated with this supplier and supplier site.
Oracle E-Business Suite A payment is created for an invoice related to an Oracle Enterprise Taxation and Policy Management A/P request. A check related to an invoice linked to an A/P request is re-issued. A check related to an invoice linked to an A/P request is voidCancel and the liability is closed.
Oracle Enterprise Taxation and Policy Management Payment information is sent from Oracle E-Business Suite Revenue Accounting to Oracle Enterprise Taxation and Policy Management. The A/P request and its associated adjustment are cancelled.
The flow of data between the two systems is illustrated below:
Process Scheduling
Depending on the size and complexity of your accounting system and business practices, transactions generated in either of the participating applications are sent to the alternate application on a daily or weekly schedule. You can schedule the transfer of this information between applications to occur according to a frequency that is most appropriate for your organization.
General Ledger
For general ledger transactions, Oracle Enterprise Taxation and Policy Management is considered the sub-ledger and Oracle E-Business Suite Financials for General Ledger and Accounts Payable is considered the general ledger. General Ledger transactions are written in one direction; from Oracle Enterprise Taxation and Policy Management to Oracle E-Business Suite Revenue Accounting. Once the entries are created in the Oracle E-Business Suite Revenue Accounting staging tables, the journal creation, editing, and posting to the ledger must be executed within Oracle E-Business Suite Revenue Accounting. Financial transactions are moved from the sub-ledger to the general ledger when two consecutive Oracle Enterprise Taxation and Policy Management batch processes, GLASSIGN and GLS, are run according to a set schedule. These are standard processes released with the Oracle Enterprise Taxation and Policy Management product.
The GLASSIGN and GLS processes group all of the financial transactions in Oracle Enterprise Taxation and Policy Management that need to be included in a batch. The Integration Point looks for batches of financial transactions that are ready to be sent, extracts and summarizes the data, translates the data from a sub-ledger format to the format required by the general ledger, and writes it to the Oracle E-Business Suite Financials for General Ledger and Accounts Payable integration table. Once the entries are created in Oracle E-Business Suite Financials for General Ledger and Accounts Payable, the standard journal generation process must be executed to create the necessary journal entries within the General Ledger. This can be accomplished by scheduling the standard Oracle E-Business Suite Financials for General Ledger and Accounts Payable journal generator process or by manually running this process through the standard user interface provided within the Oracle E-Business Suite Financials for General Ledger and Accounts Payable product. You must set up a journal generator template to facilitate the Journal Generators upload of data from the Oracle E-Business Suite Financials for General Ledger and Accounts Payable staging tables.
Note: For more information on GLASSIGN and GLS refer to the Oracle Enterprise Taxation and Policy Management documentation.
GL Process Flow Diagram
A/P Request
A/P Request transactions are written in one direction from Oracle Enterprise Taxation and Policy Management to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Information about a taxpayer, taxpayer account, and A/P Request is extracted from Oracle Enterprise Taxation and Policy Management and exported to Oracle E-Business Suite Financials for General Ledger and Accounts Payable as single payment voucher information. Once the taxpayer and refund request data is loaded into Oracle E-Business Suite Financials for General Ledger and Accounts Payable, the standard voucher build process must be executed. This can be accomplished using a scheduled process or by manually running the process through the standard user interface provided within the Oracle E-Business Suite Financials for General Ledger and Accounts Payable product. You must have set up a single payment vendor to represent the Oracle Enterprise Taxation and Policy Management refund taxpayer. It is also necessary to pre-configure an accounting entry template in Oracle E-Business Suite Financials for General Ledger and Accounts Payable to indicate the accounts that accompany the refund. The integration extracts A/P Requests from Oracle Enterprise Taxation and Policy Management where the status of the A/P Request is N which indicates that the A/P Request is Not Selected for Payment. Once the data has been integrated, the integration software updates the A/P Request status in Oracle Enterprise Taxation and Policy Management to R indicating it has been Requested for Payment.
Accounts Payable Request Process Flow Diagram
A/P Data
A/P Data transactions are written in one direction from Oracle E-Business Suite Financials for General Ledger and Accounts Payable to Oracle Enterprise Taxation and Policy Management. Payment information for system-generated checks is created and processed in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable, then exported to Oracle Enterprise Taxation and Policy Management. This payment information corresponds to the A/P Refund Requests originally generated in Oracle Enterprise Taxation and Policy Management and exported to Oracle E-Business Suite Financials for General Ledger and Accounts Payable for payment processing. The Integration Point updates the original A/P Request in Oracle Enterprise Taxation and Policy Management with the details of the payment, including the check number and date. Once a payment has been created in Oracle E-Business Suite Financials for General Ledger and Accounts Payable and the information is integrated to Oracle Enterprise Taxation and Policy Management, the A/P Request status in Oracle Enterprise Taxation and Policy Management is updated to P indicating that the A/P Request has been paid. Additional statuses that can occur include C Closed or Held and X Cancelled.
The table below provides information about how canceled payments are handled. Oracle E-Business Suite Financials for General Ledger and Accounts Payable Action Payment Completed Payment cancelled and placed on hold Payment is re-issued Payment is cancelled and the liability is closed. Oracle Enterprise Taxation and Policy Management A/P Request Resulting Action Payment information updated and status changes to P for Paid. Payment status changes to C for closed. Payment information updated and status changes to P for Paid. Payment status changes to X for cancelled. Oracle Enterprise Taxation and Policy Management Adjustment Resulting Action No change. No change. No change. Adjustment is cancelled.
Payment Cancellation Process

When a payment is cancelled in Oracle E-Business Suite Revenue Accounting, the following options are available:
Initiate Stop If a payment is stopped, the cancellation information is sent to Oracle Enterprise Taxation and Policy Management as updates to the A/P Request. The A/P Request payment status flag in Oracle Enterprise Taxation and Policy Management is set to C, indicating a Closed status. This affects only the A/P Request, but does not impact Oracle Enterprise Taxation and Policy Management.
Void Hold If a payment is put on hold, the cancellation information is sent to Oracle Enterprise Taxation and Policy Management as updates to the A/P Request. The A/P Request payment status flag in the Oracle Enterprise Taxation and Policy Management is set to C, indicating a Closed status. This affects only the A/P Request, but does not impact the adjustment in Oracle Enterprise Taxation and Policy Management.
Void Cancel If the payment is void cancelled and all liability is closed, the integration cancels the A/P Request, and then calls an Oracle Enterprise Taxation and Policy Management service to cancel the adjustment related to the request. The A/P Request payment status flag in Oracle Enterprise Taxation and Policy Management is set to X indicating a Cancelled status. The adjustment transaction is also cancelled using the standard adjustment maintenance object within the Oracle Enterprise Taxation and Policy Management application software. There is an algorithm that can optionally be configured within Oracle Enterprise Taxation and Policy Management to create a ToDo entry to notify the users of adjustment and A/P Request cancellation. This standard adjustment cancellation algorithm CI_ADCA-CRTD Adjustment Cancellation Create ToDo Entry, for creating ToDo entries, is shipped and documented as part of the Oracle Enterprise Taxation and Policy Management application software. Once it is added to a collection of Adjustment Type algorithms the system will create the configured ToDo Entry when an adjustment of this type is cancelled.
Re-Issue If a check is re-issued, for any reason, in Oracle E-Business Suite Revenue Accounting, the new information is sent across the integration and is updated on the A/P Request in Oracle Enterprise Taxation and Policy Management. The A/P Request status is set to P indicating that the A/P Request has been paid. The A/P Request in Oracle Enterprise Taxation and Policy Management only holds the most recent check information sent (no history of re-issued checks is kept).
A/P Data Process Flow Diagrams
Best Practices
The following sections provide business information that helps achieve accurate and error free movement of data between the Oracle Enterprise Taxation and Policy Management and Oracle EBusiness Suite Financials for General Ledger and Accounts Payable products. Note: For information on how to configure settings specific to the integration, see Setting Up the Process Integration. Refer to the product-specific documentation for information on how to complete product-specific configuration tasks.
One-Time Configuration Settings

Few one-time configuration settings must be coordinated manually to ensure proper results from the movement of data between the two applications.
General Ledger Configuration Oracle E-Business Suite Financials for General Ledger and Accounts Payable is the overriding source for all General Ledger information. Oracle Enterprise Taxation and Policy Management is considered to be the sub-ledger. It is assumed that the General Ledger has already been configured to accommodate your business needs.
Distribution Codes Oracle Enterprise Taxation and Policy Management uses distribution codes to map sub-ledger transactions to the Oracle E-Business Suite Financials for General Ledger and Accounts Payable General Ledger accounts. As part of your Oracle Enterprise Taxation and Policy Management setup it is assumed that you have properly mapped your distribution codes to the General Ledger chart of accounts.
General Ledger Divisions for Non-Integrated Transactions If few transactions created in Oracle Enterprise Taxation and Policy Management should not be integrated to your General Ledger, then configure a separate General Ledger Division for these transactions. You should then configure the integration product to distinguish which General Ledger Division should be integrated with the General Ledger (it ignores all the others).
General Ledger Integration

Oracle E-Business Suite Revenue Accounting General Ledger accounts are structured using account segments. These are set up in your existing Oracle E-Business Suite Revenue Accounting Flexfield according to your business practices. Oracle Enterprise Taxation and Policy Management distribution codes must be configured to mirror the segments in Oracle E-Business Suite Revenue Accounting. The segment positions are separated by dots . in Oracle Enterprise Taxation and Policy Management according to the Oracle E-Business Suite Revenue Accounting segments defined in the Accounting Flexfield. Create your Accounting Flexfield in the Oracle E-Business Suite Revenue Accounting General Ledger (if it does not exist), and then set up your Oracle Enterprise Taxation and Policy Management distribution codes to map to the General Ledger account structure using dot separators.
10 Copyright 2000, 2011, Oracle. All rights reserved.
Oracle E-Business Suite Financials for General Ledger and Accounts Payable General Ledger Settings
Configure the General Ledger settings in Oracle E-Business Suite Financials for General Ledger and Accounts Payable according to the following guidelines, keeping in mind that Oracle E-Business Suite Financials for General Ledger and Accounts Payable is the source of truth for the general ledger. Journal Import Process: Schedule the Journal import process to create journals from Oracle Enterprise Taxation and Policy Management information inserted into Oracle EBusiness Suite Financials for General Ledger and Accounts Payable interface tables by the integration software. When you configure Oracle E-Business Suite Financials for General Ledger and Accounts Payable to run this process automatically (at a preset time), ensure you have matched this timing with the timing of other actions completed by Oracle Enterprise Taxation and Policy Management and the integration product. Alternatively, you may use the Standard Request Submission (SRS) within Oracle EBusiness Suite Financials for General Ledger and Accounts Payable to run the Journal Import process manually. Accounting Entry Definition: If not already configured, pre-configure an Accounting Flexfield definition in Oracle E-Business Suite Financials for General Ledger and Accounts Payable to indicate the staging table where incoming accounting entries must be stored. Ensure that all mandatory fields on the staging tables are mapped. The integration software relies on other Oracle E-Business Suite Financials for General Ledger and Accounts Payable configuration information, including: Calendars, Ledger, Journal source, and Journal Category. These are usually already configured as part of your implementation. If these do not already exist, configure them for the integration software to run accurately.
Oracle Enterprise Taxation and Policy Management General Ledger Settings

Configure General Ledger settings in Oracle Enterprise Taxation and Policy Management according to the following guidelines, and keeping in mind that Oracle E-Business Suite Financials for General Ledger and Accounts Payable is the overriding source for the general ledger. Schedule the GLASSIGN and GLS batch processes to run at an appropriate time of day. These processes will get sub-ledger information in Oracle Enterprise Taxation and Policy Management, on financial transactions that have not been sent to the General Ledger, making them ready to extract, transform, and load to the General Ledger. When you configure Oracle Enterprise Taxation and Policy Management to run this process automatically, ensure you have coordinated this timing with the timing of other actions done by Oracle E-Business Suite Financials for General Ledger and Accounts Payable and the integration product. (Alternatively, you may use the standard user interface within Oracle Enterprise Taxation and Policy Management to run these batch processes manually). Verify that the Oracle Enterprise Taxation and Policy Management General Ledger Division matches the General Ledger Business Unit in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Ensure that Distribution Codes are configured in Oracle Enterprise Taxation and Policy Management to properly reflect the General Ledger accounts that should be debited or credited for each type of financial transaction created.
Integration Software General Ledger Settings

As part of the technical configuration the following information must be configured:
11
E-mail address of the person who should notified if the integration software detects and logs an error while performing the integration. General Ledger line description to use for journal voucher lines in Oracle E-Business Suite Financials for General Ledger and Accounts Payable that came from Oracle Enterprise Taxation and Policy Management through the integration. The Journal ID, General Ledger, and Ledger group to use for journal vouchers in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable that came from Oracle Enterprise Taxation and Policy Management through the integration. If you enter a Oracle Enterprise Taxation and Policy Management GL Division name in the BPEL configuration table, then only financial transactions associated with this GL Division will be extracted for integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL. Leave this configuration information blank if you want all Oracle Enterprise Taxation and Policy Management financial transactions to be integrated to Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL.
Note: If all Oracle Enterprise Taxation and Policy Management financial transactions should come across the integration, then do not specify any General Ledger Divisions in the integration product configuration table.
Accounting
The following table shows basic accounting debits and credits that can be achieved through the setup indicated above. Oracle Enterprise Taxation and Policy Management Event Charges generated by billing and adjustments Payments made by taxpayer A/P Request adjustment Debit Account Credit Account
Accounts Receivable Cash Accounts Receivable
Revenue Accounts Receivable Accounts Payable Clearing
Accounts Payable (A/P) Request and A/P Data Integrations

Oracle E-Business Suite Financials for General Ledger and Accounts Payable A/P Settings
The Oracle E-Business Suite Financials for General Ledger and Accounts Payable Payables Open Interface Import (APXIIMPT) must be run to read the data from the A/P Invoice Interface tables and create invoices corresponding to the Oracle Enterprise Taxation and Policy Management A/P Requests. This process can be executed manually or scheduled to run at pre-determined. Configuration needed for A/P Request and A/P Payment integrations includes:
12
Payables Open Interface Import (APXIIMPT): Schedule this process to create A/P Invoices based on Oracle Enterprise Taxation and Policy Management information inserted into interface tables by the integration product software. When you configure Oracle E-Business Suite Financials for General Ledger and Accounts Payable to run this process automatically, ensure you have coordinated this timing with the other activities that take place in Oracle Enterprise Taxation and Policy Management and the integration product. (Alternatively you can use the standard Request Submission (SRS) within Oracle E-Business Suite Financials for General Ledger and Accounts Payable to run the Payables Open Interface Import (APXIIMPT) process manually). Payment Terms Code: Create a new payment terms code to process the payments for Oracle Enterprise Taxation and Policy Management taxpayers. These codes are used to define defaults, such as when payments must be made based on the invoice date, which status must be paid, any applicable discounts, rebates, and other pertinent payment information. Invoice Source: Create an Invoice Source to identify the invoices that come from Oracle Enterprise Taxation and Policy Management in Oracle E-Business Suite Revenue Accounting system.
Note: For more information on configuration settings, refer to the Implementation Guide for this product.
Oracle Enterprise Taxation and Policy Management A/P Settings

Configure Accounts Payable settings in Oracle Enterprise Taxation and Policy Management according to the following guidelines, and keeping in mind that Oracle E-Business Suite Financials for General Ledger and Accounts Payable is the overriding source for the general ledger account information. Division: The Oracle Enterprise Taxation and Policy Management Division characteristic value for A/P Business Unit must match the AP Org Id in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Characteristic for Distribution Code: Oracle Enterprise Taxation and Policy Management characteristics associated with the distribution code assigned to an adjustment type that is used to create A/P Requests in Oracle Enterprise Taxation and Policy Management, must be setup. Their values must match the values in the Accounting Combinations defined in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
Note: For more information on configuration settings, refer to the Oracle Enterprise Taxation and Policy Management Implementation Guide.
Integration Software A/P Settings

The integration product extracts unprocessed A/P Requests from Oracle Enterprise Taxation and Policy Management. After the necessary translations and transformations on the Supplier/Invoice data (extracted from Oracle Enterprise Taxation and Policy Management) are applied, the data is loaded into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable AP Invoice Interface tables As part of the technical configuration of this integration product, indicate certain values to the product so that it can properly extract data from one application, transform it, and then insert it for use by the other application. It is assumed that you have configured this information, including:
13
The E-mail address of the person who should be notified if the integration software detects and logs an error while performing the A/P Request and A/P Data integrations. A/P Invoice information required by Oracle E-Business Suite Financials for General Ledger and Accounts Payable (including Vendor, Vendor Site, Invoice Source, Payment terms, and the Oracle Enterprise Taxation and Policy Management characteristic types holding the Oracle E-Business Suite Financials for General Ledger and Accounts Payable A/P Org ID) must be setup to valid values in the integration settings table.
Note: For more information on configuration settings, refer to the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Implementation Guide.
Accounting
The following table shows basic accounting debits and credits that can be achieved through the above A/P setup. Event A/P Request Adjustment in Oracle Enterprise Taxation and Policy Management (As part of the General Ledger Integration) A/P Invoice Created in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable A/P Invoice Payment in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable Debit Account Accounts Receivable Credit Account Accounts Payable Clearing
Accounts Payable Clearing
A/P Liability
A/P Liability
Cash
About the Integration

Oracle BPEL Process Manager uses standard data mapping to extract, transform, and load data to take it from the source system and insert into the target system. After the source system generates financial data: o o o o BPEL extracts and consolidates the data as XML-based data. BPEL then transforms the data into appropriate format based on the mapping XSLT. BPEL then loads the data into the appropriate table in the target. When the target system receives this data, it validates and converts imported data into the appropriate format of entries in the target application.
The process integration points do not use Enterprise Business Objects (EBOs) or other Application Integration Architecture (AIA) objects to complete the integration. Rather, the integration uses Oracle BPEL Process Manager to extract, transform, and load data into the target system.
14
The following table shows the integration process, source application, and target application, tables, and process used to load the data that is imported from the other system.
Integration Process General Ledger AP Request AP Data
Source System ETM ETM EBS
Target System EBS EBS ETM
Process Journal Import Payables Open Interface Import
Target Table GL_INTERFACE AP_INVOICES_INTERFACE AP_INVOICE_LINES_INTERFACE The appropriate AP Request within Oracle Enterprise Taxation and Policy Management.
ETM User Enterprise Tax Management BPEL Process Manager E-Business Suite
EBS User
Invoke Application Web Service Response
Integration Point Process Flow
Application
API BPEL Services Application Data Read Interface Tables Read/Write ETM DBAdapter (SQL) Mapping (XSLT) Write E-Business Suite DBAdapter (SQL) Call
Read Application Data
ORABPEL Schema
Interface Tables
Dehydration Store
Read/Write Write Email Notification Process Flow
Error Handling Process Flow Import Procedure
Error Table
Read/update
High Level Architecture Diagram
Integration Schema
The integration requires a database to host the required integration schema. This schema can be created in any of the following: An integration database, if one exists. As part of the Oracle Enterprise Taxation and Policy Management database.
15
As part of another database as determined by your specific technical needs.
The tables listed here are created in the integration schema defined during installation, for the purpose of this integration product. Note: The integration does not require any database objects to be added to Oracle Enterprise Taxation and Policy Management or Oracle E-Business Suite Financials for General Ledger and Accounts Payable databases other than the objects mentioned here. The following new database tables are required to operate the Oracle Enterprise Taxation and Policy Management process integration for the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Financials product. Table Name INTEGRATION_LOOKUP_TABLE Description A lookup table to store all the configuration parameters used by the BPEL processes. This table is also used to configure the E-mail addresses to be notified, if errors occur. This table is seeded with data at the time of integration product installation. This table is used to activate or de-activate various integration points available in the integration product. This table is seeded with data at the time of integration pack installation and is by default populated to activate all the available integration points in the product. The table is used to hold the information regarding the errors encountered during integration transactions. A record is inserted for each error encountered by the BPEL processes. The E-mail notification process, MailNotification, accesses this table to get the error information needed to construct the notification E-mail. This table is delivered with no data.
INTEGRATION_PROCESS_ACTIVATION
INTEGRATION_ERROR_STORE
16
Part 2: Implementing the Integration Product

This section provides details about how to configure the participating applications and the middle layer for integration. Information on error handling, monitoring, customization options, and data mapping is also included.
Setting Up the Process Integration

This section provides a configuration checklist which shows an overview of configuration tasks. Detailed steps and information are included in the following sections along with instructions on how to set up security, configure error-handling, and how to verify the implementation after all steps are complete.
Prerequisites
To implement and configure this product you must have installed the appropriate prerequisite edge applications and operating platforms. Complete and verify the following before starting this implementation: Install and configure Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Install BPEL Process Manager. Install Oracle Enterprise Taxation and Policy Management and either install the provided sample data or preconfigure the software ready for the additional configuration identified in this document. Completed, and verified, all the steps identified in the installation guide for this product.
Note: For detailed installation steps, refer the installation guide for this product.
Assumptions
It is assumed that the person installing the product has basic knowledge of Oracle SOA Suite programs, including the ability to log into BPEL, access the process monitor, invoke a BPEL process, and view a process flow. Knowledge of, and access to, database tools, such as SQLDeveloper are also required to implement this product.
17
Configuration Check List

This section provides a quick list of configuration tasks. You can print the checklist for reference as you complete the tasks. The Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable is based on the integration objects created for the Oracle Enterprise Taxation and Policy Management (ETPM) Integration to E-Business Suite. The integration object names were not modified to be specific to the Oracle E-Business Suite application and you will therefore see references to objects with ETPM in the name. These references are correct.
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Configuration
Step A1 Information Accounting Flexfield Configuration Value(s) Comments Identify and document the Accounting Flexfield to be used with the integrated data. This needs to be decided at the start of integrations, so all the journals are accounted and posted to these accounts. Specifies to which Ledger all the accounting entries should be created and posted. This is the Source of the Journal from which it is created This is the Category to which the entire Journals belong. Document the A/P Operating Unit(s) to be used with the integrated data. For example: Vision Operations. Derive the Organization id with respect to the Operating Unit. For example: 204.This is used in checklist step B3. A6 A/P Single Payment Vendor and corresponding Vendor Site Payment Terms Code Create and document the Single Payment Vendor to be used with the integrated data. For example: ETMVENDOR. Vendor Site. For example: ETM EBS. This is used in checklist steps D2 and D3. Create or document the payment terms code to be used for paying A/P vouchers coming from Oracle Enterprise Taxation and Policy Management. For example: Net07 (ETMREFUND). This is used in checklist step D5.
A2 A3 A4 A5
Ledger Id Journal Source Journal Category Organization ID
A7
18
Step A8
Information Invoice Source
Configuration Value(s)
Comments Create the Invoice source when the Payables import program is executed, we give this source. For example: ETM to group all invoices coming from Oracle Enterprise Taxation and Policy Management.
Oracle Enterprise Taxation and Policy Management Configuration

Step B1 Information GL Division Configuration Value(s) Comments Configure the GL Division(s) to be used in the integration. For example: US001 This must match the GL Division specified in step C7. B2 Distribution Codes Configure your distribution codes. See the details of required setup in this document. For example: 01.520.5250.0000.000 With 01 corresponding to Company, 520 corresponding to Department and so on. See the details of all mapping segments later in this document. This needs to be set up in sync with the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Flexfield. B3 Operating Unit Characteristic Type Configure a characteristic type to hold the value of the Operating Unit to be used. Example characteristic type: EBSORGID. This is used in checklist step D6. The value you create in this characteristic (For example: 204) must match what you documented in step A5 B4 Verify Service and Cancel Reason C1AdjustmentMaintenance WRNG Verify that the cancel service C1AdjustmentMaintenance is configured and that the Cancel Reason to which it refers is also configured accurately. The Division you are using (For example: CA) will now have a characteristic type linked to it (For example: EBSORGID) that holds the name of the Org id to use (For example: 204).
B5
Link the characteristic type created in step B3 with the Division
19
Integration Product Configuration

The default settings for the INTEGRATION_PROCESS_ACTIVATION table are shown below.
Step C1
PROCESS_NAME START_PROCESS (Y/N) ETM_EBS_GL ETM_EBS_AP EBS_ETM_APDATA Y Y Y
RUN_FREQUENCY (Seconds) 0 0 0
NEXT_RUN_INTERVAL (System Use) 0 0 0
Configuration is done in the INTEGRATION_LOOKUP_TABLE (GL Integration Point), except item C1 that uses a different table as identified in the comments. Most of these columns receive a default value as part of the installation of the product. You may choose to override the default as needed. Note: No user interface exists in this release. Use approved database tools to set column values. Step C1 INTEGRATION_KEY ETM_EBS_GL ETM_EBS_AP EBS_ETM_APDATA C2 ETM.EBS.GL.EMAIL INTEGRATION_ VALUE Y Y Y Comments Ensure that integration points are enabled in the INTEGRATION_PROCESS_ACTIVATION table as needed. Enter the E-mail address to be notified if errors occur in the GL integration point. For example: abc.gl@xyz.com. C3 ETM.EBS.GL. LEDGER_ID The Ledger to which the journals needs to be created. For example: Vision Operations (USA) (1) C4 C5 C6 C7 ETM.EBS.GL. USER_JE_CATEGORY_NAME ETM.EBS.GL. USER_JE_SOURCE_NAME ETM.EBS.GL. ACTUAL_FLAG ETM.EBS.GL.GL_DIVISION This is journal category. For example: ETM EBS This is the Journal Source. For example: ETM EBS To create the Actual Journals. For example: A If this value is blank then financial transactions associated with all GL divisions in Oracle Enterprise Taxation and Policy Management are integrated. If this column has a value, then only financial transactions associated with this specific GL Division indicated are integrated. For example: blank or US1
20
Configuration is done in the INTEGRATION_LOOKUP_TABLE (A/P Integration Point). Most of these columns will receive a default value as part of the installation of the product. You may choose to override the default as needed. Note: No user interface exists in this release. Use approved database tools to set column values. Step D1 INTEGRATION_KEY ETM.EBS.APREQUEST.EMAIL INTEGRATI ON_VALUE Comments Enter the E-mail address to be notified if errors occur in the A/P Request integration point. For example: abc.A/P@oracle.com. D2 D3 D4 ETM.EBS.APREQUEST.VENDOR_ID 40182 Not used. Do not change. Not used. Do not change. Invoice Source to use when the integration creates invoices in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Should be set to valid ID for Payment terms in EBusiness Suite. Characteristic Type to store Oracle E-Business Suite Financials for General Ledger and Accounts Payable A/P Operating Unit. This must match what you documented in step B3. For example: EBSORGID. D7 ETM.EBS.APREQUEST.ORG_ID 204 Valid ID for Organization code in Oracle E-Business Suite Financials for General Ledger and Accounts Payable to be used when integration creates vendors in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. ETM.EBS.APREQUEST.VENDOR_SITE_ID 7004 ETM.EBS.APREQUEST.INVOICE_SOURCE ETM
D5 D6
ETM.EBS.APREQUEST.TERMS_ID ETM.EBS.AP.CHAR_TYPE_CD_ORGID
10194 EBSORGID
Configuration is done in the INTEGRATION_LOOKUP_TABLE (A/P Data Integration Point) Note: No user interface exists in this release. Use approved database tools to set column values. Step INTEGRATION_KEY E1 E2 EBS.ETM.APDATA.EMAIL INTEGRATION _VALUE abc@oracle.com Comments Enter the E-mail address to be notified if errors occur in the A/P Data integration point. Last updated time of BPEL process run. This is used to determine the payment data to be extracted and moved across the integration point. This column is updated by the integration application each time it is run. Valid cancel reason code to be passed to Oracle Enterprise Taxation and Policy Management when cancelling the adjustment associated with the AP Request.
EBS.ETM.APDATA.LASTRU 11-02-2008 NDTTM 10:01:01
E3
EBS.ETM.CANCEL.CANCEL WRNG _REASON
21
Verify Configuration
To verify the configuration you should manually create data and run each integration point to verify results.
Step F1 F2
Information GL Integration Point A/P Request Integration Point A/P Data Integration Point
Success Y/N
Comments Use the steps outlined in this document to test the integration point. Verifying the Implementation: GL Integration Point. Use the steps outlined in this document to test the integration point. Verifying the Implementation: A/P Request Integration Point. Use the steps outlined in this document to test the integration point. Verifying the Implementation: A/P Data Integration Point.
F3
Note: If the integration point tests are not successful, refer to the User Guide for troubleshooting and error correction information.
Configuring the Integration

The integration between Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger and Accounts Payable Financials incorporates three integration points to facilitate transfer of information between the two applications. Configuration must be completed for all involved products to prepare the integration product for use. The following sections describe how to configure each area for each integration point.
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Configuration
Configure GL accounts (Accounting Flexfield) and other information in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Note: For steps to configure the GL, refer to the product specific user documentation.
GL Integration Point
As long as the Accounting Flexfield and respective segments and other GL definitions and settings (Ledger) are configured in Oracle E-Business Suite Financials for General Ledger and Accounts Payable, there are no new settings required for the GL integration point.
22
A/P Request Integration Point

Configure the Payment Terms in Oracle Applications Account Payables To configure the payment terms in Oracle E-Business Suite Financials for General Ledger and Accounts Payable follow these steps: 1. Open Oracle E-Business Suite Revenue Accounting and navigate to Payables Vision Operations (USA) Responsibility. 2. Go to Set Up Invoice Payment Terms. 3. Define the payment terms as per the table below: Field Label Name Description Effective Date From % Due Days Net 07 Payment Due after 7 Days 01-JAN-1990 100 7 Value
4. Capture the TERMS_ID by navigating to Help Diagnostics Examine. Change the Field name to 'TERM_ID'. This value must be specified in Step A6 of the checklist.
Configure the Invoice Source in Oracle E-Business Suite Financials for General Ledger and Accounts Payables To configure the Invoice Source follow these steps: 1. Open Oracle E-Business Suite and navigate to Payables Vision Operations (USA) Responsibility. 2. Navigate to Setup Lookups Payable. 3. Search for lookup type 'SOURCE' and add a new lookup code as follows: Field Label Code Meaning Description ETM Oracle Enterprise Taxation and Policy Management Oracle Enterprise Taxation and Policy Management Value
The Code value must be specified in Step A7 of the checklist.
Configure the Journal Source in Oracle E-Business Suite Financials for General Ledger and Accounts Payables To configure the Journal Source follow these steps: 1. Open Oracle E-Business Suite and navigate to General Ledger Vision Operations (USA) Responsibility.
23
2. Navigate to Setup Journal Sources. 3. Add a new source as follows: Field Label Source Source Key Description Import Journal References ETM EBS ETM EBS ETM EBS Journals Select the checkbox Value
The Source value must be specified in Step A3 of the checklist.
Configure the Journal Category in Oracle E-Business Suite Financials for General Ledger and Accounts Payables To configure the Journal Category follow these steps: 1. Open Oracle E-Business Suite and navigate to General Ledger Vision Operations (USA) Responsibility. 2. Navigate to Setup Journal Categories. 3. Add a new category as follows: Field Label Category Category Key Description ETM EBS ETM EBS Oracle Enterprise Taxation and Policy Management Value
The Category value must be specified in Step A4 of the checklist.
Configure the Lookup for Multi-Org setup in Oracle E-Business Suite Financials for General Ledger and Accounts Payables User and Responsibility are required to set the Org Context in the PL/SQL procedure to create a Supplier and Site. To setup the Lookup values follow these steps: 1. Open Oracle E-Business Suite and navigate to Applications Developer Responsibility. 2. Navigate to Application Lookups Common. 3. Search for INT_ETM_EBS_MORG_SETUPS Lookup Type: Code INT_USER INT_PAYABLES_RESP Meaning OPERATIONS Payables, Vision Operations (USA) Comments Provide the user name Provide the payables responsibility name
24
A/P Data Integration Point

No configuration is required in Oracle E-Business Suite Financials for General Ledger and Accounts Payable for this integration point. Standard application tables are used for selecting data from Oracle E-Business Suite Financials for General Ledger and Accounts Payable to export payment information to Oracle Enterprise Taxation and Policy Management.
Oracle Enterprise Taxation and Policy Management Configuration

To configure the Oracle Enterprise Taxation and Policy Management portion of the integration you will define settings for all three integration points. Note: For instructions regarding specific configuration steps in Oracle Enterprise Taxation and Policy Management, refer the user documentation.
To enable this integration point you must configure the following information in Oracle Enterprise Taxation and Policy Management.
Configure GL Division You must map your GL Division in Oracle Enterprise Taxation and Policy Management to the GL Business Unit in Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL Business Unit. To do this you should first find out what GL Business Unit(s) you will be using within the GL. Then, create GL Divisions in Oracle Enterprise Taxation and Policy Management to match these exactly. You can then associate these GL Divisions with the appropriate Service Agreement Types in Oracle Enterprise Taxation and Policy Management. If you decide to integrate the financial transactions for a specific GL Division in Oracle Enterprise Taxation and Policy Management to Oracle E-Business Suite Financials for General Ledger and Accounts Payable, identify the GL Division. This value need to be specified in Step C7.
Configure Distribution Codes You must map your distribution codes in Oracle Enterprise Taxation and Policy Management with the appropriate GL Accounts in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL. First, configure the distribution codes and then assign them to various entities within the Oracle Enterprise Taxation and Policy Management applications. Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL accounts are structured using account segments. These are set up in your existing Oracle E-Business Suite Financials for General Ledger and Accounts Payable configuration according to your business practices. Oracle Enterprise Taxation and Policy Management distribution codes must be configured to mirror the segments in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. The segment positions in Oracle Enterprise Taxation and Policy Management are dot . separated so that the first segment is Account, the second segment is Department ID, and so on, as shown in the following table. Oracle E-Business Suite Financials for General Ledger and Accounts Payable Account Column name Oracle Enterprise Taxation and Policy Management Distribution (GL_ACCT ) segment position
25
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Account Column name ACCOUNT DEPTID OPERATING_UNIT PRODUCT CLASS_FLD PROGRAM_CODE ALTACCT PROJECT_ID AFFILIATE AFFILIATE_INTRA1 AFFILIATE_INTRA2 BUDGET_REF CHARTFIELD1 CHARTFIELD2 CHARTFIELD3
Oracle Enterprise Taxation and Policy Management Distribution (GL_ACCT ) segment position Position1 Position 2 Position 3 Position 4 Position 5 Position 6 Position 7 Position 8 Position 9 Position 10 Position 11 Position 12 Position 13 Position 14 Position 15
* Use a dot (.) as the delimiter to indicate a break between positions. Use 2 dots (..) to indicate skipping a position and giving that position a null value. A sample GL Account string is 01.520.5250.0000.000 When interpreted by the standard mapping in the product this GL Account String in the sub ledger equates to the following in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL: Company - 01 Department - 520 Account - 5250 Sub-Account 0000 Product - 000
Note: Only fields relevant to the integration are included in this table. Field Label Distribution Code Description GL Account Algorithm Value For example: A/P-OVPY A/P overpayment GLCNST-DFLT Comments The distribution code to be used for financial transactions of a certain type. A description of how the distribution code is used. The standard product, or customer modified, algorithm you use for determining the GL Account
26
Field Label GL Account Details 1 of 1
Value
Comments String from the distribution code. Create at least one set of account details as needed by your chosen algorithm above. Only one will be used based on status and effective date. The date you wish the following GL Account string to become active and used by the system, and therefore the integration software. Only active status accounts will be used by the product and therefore the integration. Input the GL Account String as explained above.
Effective Date
01-01-1900
Status GL Account
Active 01.520.5250.0000.000.
Note: If you are using fund accounting you will also need to configure the appropriate fund codes. Ensure that the length of the FUND_CD is not greater than five (5) characters as this is the maximum number of characters supported by the Oracle E-Business Suite Financials for General Ledger and Accounts Payable fund code.
Configure GLASSIGN, and GLS for Oracle Enterprise Taxation and Policy Management Extract To successfully execute extracts from Oracle Enterprise Taxation and Policy Management, two processes must be configured with the appropriate batch parameters and set to run on a scheduled basis. These processes can be scheduled using the Oracle Enterprise Taxation and Policy Management scheduling tool or an enterprise scheduler that meets the open architecture standards used by Oracle Enterprise Taxation and Policy Management.

Configure the A/P Business Unit Characteristic Type For each Division used, in Oracle Enterprise Taxation and Policy Management, the A/P Business Unit to be used in Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL must be configured. Complete the following configuration in Oracle Enterprise Taxation and Policy Management to reference the A/P Business Unit corresponding to the Division as follows. 1. Create a Characteristic Type. Admin Menu C Characteristic Type The value for this characteristic type stores the value of Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID. In this example, it is ETMTMPLT. Use the name of the template you have established for this purpose in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. 2. Set the details on the Characteristic Type as follows: Field Label Characteristic Type EBSORGID Value Comments The code associated with your characteristic type. This will be used in future steps.
27
Field Label Description Type of Char Value Allow Search by Char Val Characteristic Value EBS Org Id
Value
Comments A description of the use for this characteristic type. No freeform text is allowed, only a predefined set of values. Allow Searches The name of the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID to be used.
Predefined Value Allowed 204
Description
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Operating Unit
3. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the Distribution Code: Field Label Characteristic Entity Division Value Comments This characteristic type can be inserted on a Division.
4. Attach the Characteristic Type, created above, to any Divisions that will be used for A/P Request Adjustments. In sample data, an example is provided as the CA Division. Admin Menu Division Field Label Division Description Characteristic Tab Effective Date For example: 01-01-1900 The date you wish the characteristic type and value to become active and used by the system, and therefore the integration software. The characteristic type you created above. Value For example: CA For example: California The Division to be used. A description of how the Division is used. Comments
Characteristic Type
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Org ID For example: 204
Characteristic Value
The value you gave to the characteristic type created above.
Note: Only fields relevant to the integration are included here.

No Oracle Enterprise Taxation and Policy Management configuration is required to enable this integration point.
A/P payment data is extracted from Oracle Applications when an A/P Request invoice is paid. This data is then translated by the BPEL service and inserted into the Oracle Enterprise Taxation and Policy Management A/P Request that initiated the invoice in the first place. Oracle BPEL Process Manager invokes the Oracle Enterprise Taxation and Policy Management service, named C1AdjustmentMaintenance, when a payment is canceled and the Invoice is cancelled in Oracle Applications. The service uses the cancel reason contained in its configuration when canceling the adjustment associated with an A/P Request. The sample data cancel reason comes preconfigured as WRNG in Oracle Enterprise Taxation and Policy Management version 2.2.0 and later. You should verify that the cancel service C1AdjustmentMaintenance is configured and that the Cancel Reason to which it refers is also configured correctly. Admin Menu X XAI Inbound Service Field Label XAI In Service Name Description Long Description Active Request Schema Response Schema Transaction Type Value Adjustment Maintenance Adjustment Maintenance for A/P Cancel Adjustment Maintenance for A/P Cancel Checked C1AdjustmentMaintenance.xsd C1AdjustmentMaintenance.xsd Update Active check box checked. Used by BPEL to call this service. Used by BPEL to receive the response from this service. Service used to update an existing adjustment transaction. Comments This service is used to change data associated with adjustment transactions.
You can test this service using XAI Dynamic Submission as follows: Admin Menu X XAI Dynamic Submission Field Label XAI In Service Name Transaction Type Cancel Adjustment ID Cancel Reason Value Adjustment Maintenance Update Checked For example: 078644601179 For example: WRNG Cancel check box checked. The key value of the adjustment for which you wish to test the cancel service. This must be a configured cancel reason. This value should be same as that of INTEGRATION_LOOKUP_TABLE. Comments This service is used to change data associated with adjustment transactions.
Click Submit to review the results.
29
Integration Product Configuration

At this time there is no user interface for entering the configuration parameters associated with Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. The implementer should use an approved database access tool to establish the appropriate configuration parameters in the following tables and columns.
Process Activation Manager

The table INTEGRATION_PROCESS_ACTIVATION controls the activation or deactivation of the specific integration points. The initial install defaults all of the START_PROCESS values to Y. Set the START_PROCESS value to N for any given PROCESS_NAME that you will not be using. Set the run frequency to the time interval you wish to have between integration runs for each of the integration points. PROCESS_NAME ETM_EBS_GL ETM_EBS_AP EBS_ETM_APDATA START_PROCESS (Y/N) Y Y Y RUN_FREQUENCY (Seconds) 0 0 0 NEXT_RUN_INTERVAL (System Use) 0 0 0
Note: You cannot use APDATA if you do not also use AP.
Lookup Table
The database table INTEGRATION_LOOKUP_TABLE is used to manage external parameters used in the integration for the GL, A/P Data, and A/P Request integration points.
GL Integration Point The INTEGRATION_LOOKUP_TABLE contains configurable parameters for the GL Transaction Integration process. The values for these parameters should be set to match your configuration of Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger and Accounts Payable. INTEGRATION_KEY ETM.EBS.GL.EMAIL ETM.EBS.GL. LEDGER_ID INTEGRATION_V ALUE Abc.gl@xyz.com 1 Comments Enter the E-mail address to be notified if errors occur in a GL integration point. The Ledger to which the journals needs to be created. This is journal category
ETM.EBS.GL. ETM EBS USER_JE_CATEGORY_NAM E ETM.EBS.GL. USER_JE_SOURCE_NAME ETM EBS
This is the Journal Source. To create the Actual Journals. Example: A

ETM.EBS.GL. ACTUAL_FLAG A
30
INTEGRATION_KEY ETM.EBS.GL.GL_DIVISION
INTEGRATION_V ALUE US1 or Leave Blank
Comments If this value is blank then financial transactions associated with all GL divisions in Oracle Enterprise Taxation and Policy Management are integrated. If this column has a value then only financial transactions associated with this specific GL Division indicated are integrated.
A/P Request Integration Point INTEGRATION_LOOKUP_TABLE contains configurable parameters for the A/P Request Integration process. The values for these parameters can be changed as per user requirement. INTEGRATION_KEY ETM.EBS.APREQUEST.EMAIL INTEGRATION_VA LUE Comments
Abc.apreq@oracle.com Enter the E-mail address to be notified if errors occur in an A/P Request integration point error. 40182 7004 ETM Not used. Do not change. Not used. Do not change. Invoice Source to use when the integration creates invoices in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Should be set to valid ID for Payment terms in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Characteristic Type to store Oracle EBusiness Suite Financials for General Ledger and Accounts Payable A/P Org ID. Valid ID for Organization code in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable to be used when integration creates vendors in EBS.
ETM.EBS.APREQUEST.VENDOR_ID ETM.EBS.APREQUEST.VENDOR_SITE_ID ETM.EBS.APREQUEST.INVOICE_SOURCE
ETM.EBS.APREQUEST.TERMS_ID
10194
ETM.EBS. AP. CHAR_TYPE_CD_ORGID
EBSORGID
ETM.EBS.APREQUEST.ORG_ID
204
A/P Data Integration Point INTEGRATION_LOOKUP_TABLE contains configurable parameters for the A/P Data Integration process. The values for these parameters can be changed as per user requirement. INTEGRATION_KEY EBS.ETM.APDATA.EMAIL INTEGRATION_ VALUE abc@oracle.com Comments Enter the E-mail address to be notified if errors occur in the A/P Data integration point.
31
INTEGRATION_KEY EBS.ETM.APDATA.LASTRUNDTTM
INTEGRATION_ VALUE 11-02-2008 10:01:01
Comments Last updated time of BPEL process run. This is used to determine the payment data to be extracted and moved across the integration point. This column is updated by the integration application each time it is run. Valid cancel reason code to be passed to Oracle Enterprise Taxation and Policy Management when cancelling the adjustment associated with the AP Request.
EBS.ETM.CANCEL.CANCEL_REASON
WRNG
Process Scheduling
You may schedule these processes independently or using an enterprise scheduling tool. To schedule the processes independently you may schedule the Oracle Enterprise Taxation and Policy Management processes using the standard tools available with the Oracle Enterprise Taxation and Policy Management product. You may schedule the Oracle E-Business Suite Financials for General Ledger and Accounts Payable processes using the standard tools shipped with the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable product. You may schedule the BPEL processes to the time intervals you have configured. Each of the main BPEL processes that form this process integration have been designed to first look and see if data exists that should be extracted. If data exists, then it is extracted, transformed, and loaded to the target system. If data does not exist, then the process does nothing until the next time it tries again. For example, schedule the Oracle Enterprise Taxation and Policy Management GL processes to run at 6:00 AM each weekday morning. Then, initiate the BPEL GL process at 7:00 AM and have it run every 4 hours to see if data exists. Accounting staff could then schedule the Journal Generator to run at 9:00 AM each morning using the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Process Scheduler. You can run the integration manually by initiating each process using the tools provided with each application. Or, you can use an enterprise scheduler to initiate all, or some, of the processes mentioned above. The frequency of the run for each integration point is at the clients discretion. As a default each integration point will run every half hour from the time you start them the first time. If data exists the integration will be done for the integration point. Else, the system will do nothing and then the integration point will try again 30 minutes later. If you wish to extend the time between runs you may insert a value of time, in seconds, in the RUN_FREQUENCY column of the INTEGRATION_PROCESS_ACTIVATION table for the appropriate integration point. This column controls the timing of the integration points waking up to see if there is data to integrate. The integration points only check this table every 30 minutes, so you cannot schedule the runs in less than 30 minute increments. You can schedule shorter increments if desired. Set the run frequency to the time interval, in 1800 second increments, you wish to have between integration runs for each of the integration points.
32
PROCESS_NAME ETM_EBS_GL ETM_EBS_AP EBS_ETM_APDATA
START_PROCESS (Y/N) Y Y Y
RUN_FREQUENCY (Seconds) 14400 7200 7200
NEXT_RUN_INTERVAL (System Use) 0 0 0
In the above example, the GL integration point looks for data every 4 hours (14,400 second) and the A/P Request and A/P Data integration points look for data to integrate every 2 hours (7200 seconds). Note: If you were to insert a value of 40 minutes (2400 seconds) the integration would actually run every 60 minutes as the integration points are set to a 30 minute timing granularity. Every 30 minutes each integration point will check this table with the following logic:
If START_Process flag is NOT Y do nothing else If Run Frequency is 0 run the IP else If next run interval is =< 0 run the integration point AND set Next_run_interval = run_frequency else DO not run the Integration Point, just set Next_run_interval = Next_run_interval 1800 (the polling interval set in BPEL)
General Ledger (GL)

The following processes must be run in sequence to extract, transform and load GL transactions from Oracle Enterprise Taxation and Policy Management to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Product ETM Process Name GLASSIGN Description Assigns GL account numbers to the GL details associated with financial transactions by referencing the distribution code that calls the appropriate assignment algorithm. Follows GLASSIGN to create financial transaction (FT) download staging records for all financial transactions that are ready to be posted to the GL. Extracts financial transactions from Oracle Enterprise Taxation and Policy Management into BPEL to be transformed and prepared for upload to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Reads the staged data in the GL_INTERFACE Interface Table and creates journal entries in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL. This process can be scheduled or run manually.
ETM BPEL
GLS ETMToEBSGLBPELProcess
EBS
EBS Journal Import Process
33
A/P Request
The following processes must be run in sequence to extract, transform and load A/P Requests from Oracle Enterprise Taxation and Policy Management to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Product BPEL Process Name ETMToEBSAPBPELProcess Description Extracts A/P Requests from Oracle Enterprise Taxation and Policy Management into BPEL to be transformed and prepared for upload to Oracle E-Business Suite Financials for General Ledger and Accounts Payable. Creates invoices in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
EBS
Payables Open Interface Import (APXIIMPT)
A/P Data
The following process must be run, sometime after the Oracle E-Business Suite Financials for General Ledger and Accounts Payable check run, to extract, transform and load A/P Data from Oracle E-Business Suite Financials for General Ledger and Accounts Payable to Oracle Enterprise Taxation and Policy Management. Product BPEL Process Name EBSToETMAPDataBPELProcess Description Extracts all payments and cancellations created during pay cycle processing.
Note: The BPEL processes mentioned above are exposed as standard, stand alone, SOAP Web Services. They can therefore be invoked as regular Web services by the BPEL console or any platform supporting scheduling web service invoke activities. These services do not require any external inputs to run. Industry standard enterprise scheduling tools that support this capability may therefore be used to initiate these processes if desired. There is an open source tool bundled with the SOA Suite called Quartz, which can be used as a scheduler. In fact, the BPEL Process Manager uses the Quartz scheduler internally.
Setting up Security
Steps to enable security for connecting to Oracle Enterprise Taxation and Policy Management from SOA11g middleware: 1. Login to the WebLogic em console using admin username and password. 2. Expand Weblogic Domain and right click on soa_domain Security Credentials. 3. Select Create Map and enter oracle.wsm.securtiy as the MAP name. 4. Click OK.
34
5. Select the newly created oracle.wsd.security map, then click Create. This opens a pop-up window where you can select oracle.wsd.security MAP. 6. Enter the Key name as OU_ETMEBS_01. Key name must set to this value or else the authentication will fail. 7. From the dropdown select Type as Password. User Name and Password should be valid userid and password for the installed Oracle Enterprise Taxation and Policy Management instance. 8. Click OK.
Verifying the Implementation

The best way to verify implementation is to start each application individually and then manually run the integration points.
1. Identify financial transactions in the CI_FT table that need to be sent to Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL for creating journal entries. If needed, generate a bill, adjustment or payment event to create financial transactions. 2. Run the GLASSIGN process to assign the Account Number to the FT in CI_FT. 3. Run the GLS process to mark the FTs in the CI_FT table for download. The staging process to create a GL download (GLS) creates a staging record for every financial transaction that is ready for download. This process populates the FT/ Batch Process table with the unique ID of all financial transactions to be interfaced to the GL. This process marks each staging record with the batch process ID (defined on the installation record) for the GL interface. It also stamps the current run number for the respective batch control record. Note: The integration BPEL process uses the information on this staging table to create the consolidated journal entries that are interfaced to your GL. The Oracle BPEL process reads the CI_BATCH_JOB table to check for new BATCH_JOB_ID and BATCH_JOB_STAT_FLG. 4. Invoke the GL Integration Point process from Oracle BPEL Process Manager or wait for its next run to occur. The package should do the following: a. Select the FT in the CI_FT table based on the batch code and the run number provided to it by Oracle BPEL Process Manager. b. Extract and group (summarize) the Financial Transactions (FT) and push them into Oracle BPEL Process Manager. c. Update the Distribution status to D after extracting the FT and increment the NEXT _BATCH_NBR in the CI_BATCH_CTL table.
d. Data is transformed by the BPEL process and written to the GL journal staging table in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. 5. Use the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Journal Generator to Load the GL data into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Generic Accounting Entry Table: PeopleSoft_JGEN_ACCNT_ENTRY.
35

1. Create an A/P Request for a refund customer in Oracle Enterprise Taxation and Policy Management. You will need to generate an adjustment of the appropriate type to do this. 2. Invoke the Oracle BPEL Integration Point Process to extract the A/P Request Information, and the corresponding customer information from Oracle Enterprise Taxation and Policy Management, transform it, and load it into Oracle E-Business Suite Financials for General Ledger and Accounts Payable A/P voucher build integration tables. 3. Run the voucher build process in Oracle E-Business Suite Financials for General Ledger and Accounts Payable to create vouchers from the A/P Check Request and Customer data that is staged in the voucher build integration tables.

1. Generate a payment in Oracle E-Business Suite Financials for General Ledger and Accounts Payable Payables for a voucher created by the Oracle Enterprise Taxation and Policy Management A/P Request process above. 2. Invoke the Oracle BPEL Integration Point process to update the A/P Check Request table (CI_ADJ_APREQ) with the Payment Information from Oracle E-Business Suite Financials for General Ledger and Accounts Payable . 3. If you wish to further test a cancellation of payment functionality, cancel the Payment you made above in Oracle E-Business Suite Financials for General Ledger and Accounts Payable Payables and close the liability. 4. Invoke the Oracle BPEL Process Manager process to update the A/P Check Request table (CI_ADJ_APREQ) with the Payment Information from Oracle E-Business Suite Financials for General Ledger and Accounts Payable . This should also cancel the A/P request and adjustment.
36
Troubleshooting
If your integration is configured properly and your data entry into Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger and Accounts Payable is correct, you should not experience errors related to the integration. The following sections address some common scenarios which may produce errors and offer possible solutions toward error resolution.
E-mail Notification
If errors occur during the main integration processes, these errors are logged to the Oracle BPEL Process Manager error table. Error information is stored in the error table and the notification sub process is invoked. The E-mail notification sub process reads the information in the error table, INTEGRATION_ERROR_STORE (see the Appendix), and sends an E-mail notification based on your settings. Each time the E-mail notification process runs it picks up records from the BPEL error table for which notifications have not been sent yet (NOTIFIED not equal to Y). It loops through all the distinct INTERFACE_NAME entries and sends one E-mail to the corresponding E-mail address (specific to the interface name) with the error information of all the entries in the table. So, if there are 6 records with INTERFACE_NAME=GL one E-mail is sent out to the E-mail address corresponding to the GL interface. This E-mail contains the following information about each of the 6 GL transactions that failed: Subject: Source System Target System Interface Name Process Instance Body Source system Integration batch number BPEL Instance ID Error Code Error Summary Error Message
Once the E-mail has been sent it will update the NOTIFIED to Y for all the GL records. Steps to enable e-mail notification: 1. Login to the Enterprise Manager console. 2. In the console, navigate to SOA right-click soa-infra SOA Administration Workflow Notification Properties.
3. Select EMAIL from the drop-down list.
37
4. Provide the E-mail IDs for From address.
Locating Error Logs

The following sections indicate where to locate error messages and logged error data in each of the integration products. In general, the following types of errors are reported in the location indicated. Error Errors occurring when GLASSIGN or GLS batches are run Reported In Oracle Enterprise Taxation and Policy Management product batch run tree. If an error occurs in the Oracle Enterprise Taxation and Policy Management batch processes, correct the underlying condition causing the error, then rerun the batch processes. The rest of the integration cannot occur until the two Oracle Enterprise Taxation and Policy Management batch processes have successfully completed. The monitor shows the status of the process and an error log. Use standard database (SQL based) tools to view the error information in the table if necessary, however the E-mail notification you receive should include all the information necessary to investigate and correct the error.
Errors occurring during the execution of the journal generator Errors occurring during the integration such as when financial transactions are extracted or summarized, when data formats are translated, or when data is inserted into one of the edge applications.
Oracle E-Business Suite Financials for General Ledger and Accounts Payable process monitor. Logged and reported by the integration product in the INTEGRATION_ERROR_STORE table.
BPEL Processing Errors

The integration has an error table in the integration schema which keeps a record of all transactions that have failed during BPEL processing, including insertion of data in the target system. When errors are found during data extraction Oracle BPEL Process Manager inserts errors into the error table, INTEGRATION_ERROR_STORE. There is no user interface to access this table. The INTEGRATION_ERROR_STORE table includes the following information: COLUMN SOURCE_SYSTEM INT_BATCH_NUMBER INTERFACE_NAME BPEL_INSTANCE_ID
38
DATA TYPE VARCHAR2 (3) NUMBER VARCHAR2 (30) NUMBER

COLUMN ERROR_CODE ERROR_SUMMARY ERROR_MESSAGE NOTIFIED LAST_UPDATE_DATE_TIME NUMBER VARCHAR2 (3000) VARCHAR2 (3000) VARCHAR2 (1) DATE
DATA TYPE
If errors occur during the extraction or load process for any of the integration points, the system logs an error in INTEGRATION_ERROR_STORE. Business data is stored in the ERROR_MESSAGE field of the table, and the information is also included in the notification E-mail.
GL Integration Point Extraction of financial transactions from Oracle Enterprise Taxation and Policy Management or load of transactions into the PeopleSoft_JGEN_ACCT_ENTRY table. TABLE CI_FT_PROC CI_FT_GL CI_FT_GL CI_FT CI_FT DST_ID GL_ACCT CIS_DIVISION GL_DIVISION COLUMN BATCH_NBR DATA TYPE NUMBER (10) CHAR (10) VARCHAR2 (48) CHAR (5) CHAR (5)
The GL integration point utilizes set based processing. If BPEL detects an error, with any part of the batch, the entire batch is rejected.
A/P Request Integration Point Extraction of financial transactions from Oracle Enterprise Taxation and Policy Management tables or loads of transactions into the voucher build integration tables. TABLE CI_ADJ_APREQ AP_REQ_ID BATCH_NBR ENTITY_NAME SCHEDULED_PAY_DT CI_ADJ ADJ_ID CRE_DT ADJ_TYPE_CD ADJ_AMT CI_SA CIS_DIVISION COLUMN DATA TYPE CHAR (12) NUMBER (10) VARCHAR2 (64) DATE CHAR (12) CHAR (12) CHAR (8) NUMBER (15,2) CHAR (5)
39
A/P Data Integration Point Extraction of financial transactions from Oracle Enterprise Taxation and Policy Management tables or loads of transactions into the voucher build integration tables. TABLE AP_CHECKS_ALL CHECK_ID CHECK_DATE AMOUNT BANK_ACCOUNT_NUM AP_INVOICES_ALL INVOICE_NUM PAYMENT_REASON_COMMENTS INVOICE_ID VENDOR_ID VENDOR_SITE_ID COLUMN CHECK_NUMBER DATA TYPE NUMBER (15) NUMBER (15) DATE NUMBER VARCHAR2 (30) VARCHAR2 (50) VARCHAR2 (240) NUMBER (15) NUMBER (15) NUMBER (15)
Error Resolution
The following sections detail error scenarios which may occur, and how to resolve them. Usually, when errors occur you will need to correct configuration settings, data errors, or both.
Any Integration Point

Error Scenario System or Network Down Process BPEL Process Details If BPEL goes down in the middle of an integration process. Resolution If BPEL goes down in the middle of a long running process, it can be restarted and will resume where it went down. A retry policy can be set up in the Oracle BPEL Process Manager which administratively enables BPEL process instances to retry adapter connectivity.
General Ledger
The General Ledger Integration uses set based processing. This means that either all of the transactions in a batch will succeed or none will.
40
Error Scenario Data failed to insert in the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable interface table.
Process BPEL Process
Details If one row fails to insert into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable Interface table during a batch, the entire batch rolls back. In this instance, the BPEL process shows a status of error and an error notification is sent via E-mail. If the integration process completes successfully and data is inserted into the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable interface tables, but the data has errors in it, the Journal Generator process may not be able to process the data and create journal vouchers from it. When the Journal Generator process encounters errors, the error status/reason associated with the Journal Generator process is also identified in the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable Process monitor. All the rows in the interface table remain unprocessed and the Distribution Status remains unchanged as N. In this instance journals are created for the row of bad data, which can be detected and rectified by viewing, editing, and loading the journal online.
Resolution Re-establish the connections between BPEL and the edge applications if necessary. Correct the configuration and/or transactional data in the Oracle Enterprise Taxation and Policy Management database, if necessary. Make sure that the GLASSIGN and GLS processes are run again. The Integration process must also be rerun once you have taken the above actions. Correct the information directly in the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable application, and load the journal voucher using the online tools provided in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
Data successfully inserted in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable interface table, but data has errors.
EBS Process
Journal Generator process cannot complete successfully.
EBS Process
Correct the information directly in the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable application, and load the journal voucher using the online tools provided in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
Journal Generator process completes successfully with bad data.
EBS Process
Correct the information directly in the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable application, and load the journal voucher using the online tools provided in Oracle E-Business Suite Financials for General Ledger and Accounts Payable. After the process is successfully completed, the Distribution Status of all the rows in the Interface table is updated to D.
Row of bad data in Oracle E-Business Suite Financials for General Ledger and Accounts Payable interface table does not get picked up.
EBS Process
The Journal Generator process does not error out and the row of bad data in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable interface table does not get picked up. This situation can occur if the Accounting Date lies outside the Open Period.
Correct the Accounting Date manually in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable application. After the process has completed successfully the Distribution Status of the row still remains in N (does not change to D).
41
Error Scenario GL Account Mapping inconsistency
Process BPEL, ETM Setup
Details When the Journal Voucher is created in Oracle E-Business Suite Financials for General Ledger and Accounts Payable, the Accounting information is incorrect.
Resolution Since the source of truth is Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL, the user needs to correct the Accounting Structure in the Oracle Enterprise Taxation and Policy Management distribution code using information from the Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL. Correct the GL Division setup in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable to match the GL Business Unit in Oracle E-Business Suite Financials for General Ledger and Accounts Payable.
Wrong GL Business Unit
ETM
The financial information being sent to Oracle E-Business Suite Financials for General Ledger and Accounts Payable has the wrong business unit associated with it.
A/P Request
The A/P Request Integration uses row-by-row processing. Error Scenario Data in A/P Request row and BPEL process does not fail. Process ETM Process Details If a particular A/P Request has an error in Oracle Enterprise Taxation and Policy Management, it will not be picked by the integration process, but the remaining requests of that BPEL run will be picked up and inserted into the interface tables and the BPEL process status will be successful. If one or more rows have failed at any point in the integration their information will be logged in the integration log table and an error E-mail is generated. All data is successfully inserted into the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable Interface tables, but there is an error while running the voucher build process. Resolution Correct the specific A/P Request in error using the tools provided by Oracle Enterprise Taxation and Policy Management. Then, rerun the BPEL integration process.
Error Data in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable staging table and Oracle E-Business Suite Financials for General Ledger and Accounts Payable process fails.
EBS Process
Load the vouchers directly into the Oracle E-Business Suite Financials for General Ledger and Accounts Payable application and resolve any incorrect data.
42
Error Scenario Error Data in Oracle EBusiness Suite Financials for General Ledger and Accounts Payable staging table and Oracle E-Business Suite Financials for General Ledger and Accounts Payable process does not fail.
Process EBS Process
Details Oracle E-Business Suite Financials for General Ledger and Accounts Payable Voucher Build process ends successfully but the vouchers are in recycle status.
Resolution Load the vouchers directly in the Oracle E-Business Suite Financials for General Ledger and Accounts Payable application and resolve any incorrect data.
A/P Data
The A/P Data Integration uses row-by-row processing. Error Scenario The integration is unable to update the A/P Request table with payment information. The integration is unable to invoke the Adjustment Maintenance Service. Process BPEL Process Details It is likely that the error is technical in nature (data mapping etc). It is likely that the error is technical in nature (service retired etc). Resolution Review BPEL error table and product error logs. Update BPEL and/or product configurations as needed to correct the errors reported. Rerun the integration when corrections have been made. Review BPEL error table and product error logs. Update BPEL and/or product configurations as needed to correct the errors reported. Rerun the integration when corrections have been made.
BPEL Process
43
Customization Options
Extension Methods
The integration process allows extensibility of transaction messages using the following methods: Pre-transformation Extension Point Post-transformation Extension Point Custom Transformations
Pre-transformation Extension Point

The pre-transformation extension point is invoked before the main transformation is executed. This transformation will help in transforming the source XML coming as an input to the integration process. The integration layer defines an external call from the pre-transformation extension point which accepts the source XML as input and gives the source XML as output. The integration layer points to an abstract WSDL and can be plugged in by a concrete WSDL by the implementation team. This helps the implementation to invoke any external Web service and transform the input XML.
Post-transformation Extension Point

The post-transformation extension point is invoked after the main transformation is executed. This transformation will help in transforming the target XML going as an input to the Target queue. The integration layer defines an external call from the post-transformation extension point which accepts the target XML as input and gives the target XML as output. The integration layer points to an abstract WSDL and can be plugged in by a concrete WSDL by the implementation team. This helps the implementation to invoke any external Web service and transform the output XML.
Custom Transformations
This integration has placeholders for custom elements in the incoming schema and outgoing schema at record level. When querying data into incoming message, the custom elements will be empty. This can be populated through the Extension points. The custom transformations have a standard template to map elements to existing fields that are still unmapped and a custom template to map custom elements. The main transformation invokes custom transformation. Empty custom transformations are shipped with the product. Note: The custom elements in the Target variable are not passed to the Database Adapter, but they are passed to Post-Collection Extension point.
Available Extension Points

When the BPEL process invokes an extension point to call another BPEL process that needs to be in the same global transaction as the main BPEL process, ensure that the transaction flag on the BPEL component is set to Required. Integration Point GL AP Data A/P Request BPEL process ETMToEBSGLBPELProcess EBSToETMAPDataBPELProcess ETMToEBSAPBPELProcess
45
Extension Points Available in GL
Main BPEL Process - ETMToEBSGLBPELProcess Process where extensibility options are stored:
ETMToEBSGLBPELProcess
46
Pre Transformation Collection Extension Point
ETM.EBS.GL.XFORMETMCOLL.PRE.EXTN.FLAG If this value defined in the integration lookup table is set to true, the pre transformation extension point is invoked at the collection level before any transformation is executed. ETM.EBS.GL.AFTEREBSCOLLINSERT.POST.EXTN.FLAG If this value defined in the integration lookup table is set to true, the post transformation extension point is invoked after all the records are inserted into the GL_INTERFACE table in EBS.
Post Transformation Collection Extension Point
The custom transformation is used to map elements coming from the GL/FT tables in Oracle Enterprise Taxation and Policy Management to fields in the GL_INTERFACE table in Oracle E-Business Suite Financials for General Ledger and Accounts Payable that are still unmapped. The main transformation invokes the custom transformation. (For example: main transformation is TransformationETMToEBSGLData.xsl; custom transformation is TransformationETMToEBSGLData_Custom.xsl)
47
Extension Points Available in AP Request
Main BPEL Process - ETMToEBSAPBPELProcess

Process where extensibility options are stored: Pre Transformation Collection Extension Point
ETMToEBSAPBPELProcess
ETM.EBS.AP.XFORMETMCOLL.PRE.EXTN.FLAG If this value defined in the integration lookup table is set to true, the pre transformation extension point is invoked at the collection level before any transformation is executed. ETM.EBS.APREQUEST.XFORMETMRECORD.PRE.EXTN.FLAG If this value defined in the integration lookup table is set to true, the pre transformation extension point is invoked at the record level before the AP Request record coming from Oracle Enterprise Taxation and Policy Management transformed to the Oracle E-Business Suite Financials for General Ledger and Accounts Payable format. ETM.EBS.APREQUEST.XFORMEBSRECORD.POST.EXTN.FLAG If this value defined in the integration lookup table is set to true, the post transformation extension point is invoked at the record level after the AP record coming from Oracle Enterprise Taxation and Policy Management transformed to the EBS format but before inserting into the AP_INVOICES_INTERFACE table in EBS.
Pre Transformation Record extension point
Post Transformation Record extension point
The custom transformation is used to map elements from the Adjustment AP Request tables in Oracle Enterprise Taxation and Policy Management to fields in the Oracle E-Business Suite Invoice Interface tables that are still unmapped. The main transformation invokes the equivalent custom transformation. (For example: main transformation is TransformationETMPaymentTOEBSInvoice.xsl; custom transformation is TransformationETMPaymentTOEBSInvoice_Custom.xsl)
Extension Points Available in AP Data
49
Main BPEL Process EBSToETMAPDataBPELProcess Process where extensibility options are stored: Pre Transformation Collection Extension Point
EBSToETMAPDataBPELProcess
EBS.ETM.APDATA.XFORMEBSPAYMENTSCOLL.PRE.EXTN.FLAG If this value defined in the integration lookup table is set to true, the pretransformation extension point is invoked at the collection level before any transformation is executed. EBS.ETM.APDATA. XFORMEBSPAYMENTSRECORD.PRE.EXTN.FLAG If this value defined in the integration lookup table is set to true, the pretransformation extension point is invoked at the record level before the Payment or Cancellation record coming from EBS is transformed to the ETPM format. EBS.ETM.APDATA.PROCESSPAYMENTINFO.PRE.EXTN.FLAG If this value is defined in the integration lookup table is set to true, the preprocessing extension point is invoked instead of updating the ETPM AP Request table or calling the ETM service to Cancel the Adjustment. EBS.ETM.APDATA.PROCESSPAYMENTINFO.POST.EXTN.FLAG
Pre Transformation Record extension point
Pre Processing extension point
Post Processing extension
50
point
If this value defined in the integration lookup table is set to true, the postprocessing extension point is invoked after the ETM AP Request table is updated and the ETPM service is called if the payment was cancelled.
The custom transformation is used to map elements coming from the Oracle E-Business Suite table to fields in the ETPM Adjustment AP Request table that are still unmapped. The main transformation invokes the equivalent custom transformation.
Extension Points
This integration has pre- and post- transformation extension points which can be used to invoke webservices and transform the payload. The desired extension point can be triggered from the process by enabling the pre- and posttransformation extension flags defined in the integration lookup table. The processes that include extension points have their own concrete WSDL. This is used to read the endpoint location for the extension service. The binding and service elements for the extension service must be added to the concrete wsdl in the product install home at ETM-EBS/MDS-Artifacts/MetaData/ExtensionServiceLibrary and the wsdl must be updated in MDS. These concrete wsdl files are located in MDS under the directories /apps/ETM-EBS/MetaData/ExtensionServiceLibrary. For instructions on how to update MDS, refer to the Installation Guide. To implement extension points: 1. Re-deploy the composite or restart the SOA server for the extension point to invoke the Web service in the concrete wsdl. For example: To enable the extension points for ETMToEBSAPBPELProcess add the binding and service elements to the ETMToEBSAPBPELProcessExtensionConcrete.wsdl
<binding name="ETMToEBSAPBPELProcessV1ExtensionServiceSOAP11Binding" type="tns:ETMToEBSAPBPELProcessV1ExtensionService"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="PreXformCollectionETMtoEBS"> <soap:operation style="document" soapAction="http://xmlns.oracle.com/ETMToEBSAPBPELProcess/ETMToEBSAPBPELProcessExtension/V1/PreXformCollectionETMtoEBS"/ > <input> <soap:body use="literal" parts="CollectionETMtoEBS"/> </input> <output> <soap:body use="literal" parts="CollectionETMtoEBS"/> </output> <fault name="fault"> <soap:fault name="fault" use="literal"/> </fault> </operation> <operation name="InvokeInsertInvoiceExt"> <soap:operation style="document"
51
soapAction="http://xmlns.oracle.com/ETMToEBSAPBPELProcess/ETMToEBSAPBPELProcessExtension/V1/InvokeInsertInvoiceExt"/> <input> <soap:body use="literal" parts="EBSRecord"/> </input> <output> <soap:body use="literal" parts="EBSRecord"/> </output> <fault name="fault"> <soap:fault name="fault" use="literal"/> </fault> </operation> </binding> <service name="ETMToEBSAPBPELProcessV1ExtensionService"> <port name="ETMToEBSAPBPELProcessV1ExtensionService" binding="tns:ETMToEBSAPBPELProcessV1ExtensionServiceSOAP11Binding"> <soap:address location="http://xyz.us.oracle.com:0000/soainfra/services/default/APReqExtensionService/ETMToEBSAPBPELProcessV1ExtensionService"/> </port> </service>
2. For the custom BPEL process invoked from the extension point to be in the same global transaction as the main BPEL process, make sure that the transaction flag on the Custom BPEL component is set to Required. Example for SOA Suite 11g: In the Custom BPEL process composite xml, add the bpel.config.transaction property set to Required into the bpel component.
<component name="ExtensionService"> <implementation.bpel src="ExtensionService.bpel"/> <property name="bpel.config.transaction" many="false" type="xs:string">required</property> </component>
3. Also, if security policies are attached to the composites, then oracle/ Utilities_wss_http_token_service_policy_OPT_ON must be attached to the service and oracle/Utilities_wss_http_token_client_policy_OPT_ON must be attached to all the references of the custom BPEL process invoked from the Extension Points.
Custom Transformations
Each process in the integration has its own xsd files for the incoming and outgoing messages. The messages have custom elements at record level which can be used to pass additional data. Each xsd has a corresponding CustomType xsd in which the complexType elements for each customElements tag are defined. To pass additional elements in the customElements tag, the corresponding complexType needs to be modified. Add the additional elements required in both the complexType elements i.e. xsd for both edge applications. The custom xsd files are located in the product install home under the directories ETM-EBS/MDSArtifacts/ETM-EBS/MetaData/ApplicationObjectLibrary/OUETM/V1/schemas and ETM-EBS/MDSArtifacts/ETM-EBS/MetaData/ApplicationObjectLibrary/EBS/schemas/
52
The custom elements in the incoming message can be populated through the Extension points. Each transformation file has a corresponding Custom xsl, and standard and custom templates are defined in the Custom xsl. Each transformation invokes the standard and custom templates at the record level. The Custom xsl has a standard template to map elements that are still unmapped coming from the Oracle Enterprise Taxation and Policy Management DB Adapter Table schema to fields in the Oracle E-Business Suite DB Adapter Table schema or vice versa. The Custom xsl has a custom template to map custom elements. The custom xsl files are located in the product install home under the directory ETMEBS/services/industry/Utilities/EnterpriseBusinessFlow/<Process Name>/xsl. To implement custom transformations: 1. After updating the xsd and xsl files in the product install home, update MDS using the ant scripts and restart the SOA server. For instructions on how to update MDS, refer to the Installation Guide. For example: ETM Schema: GetETMAPData.xsd EBS Schema: InsertIntoEBSAPInvoiceInterfaceTable_table.xsd To modify the AP Request integration process to map GEO_CODE from ETM to Oracle E-Business Suite, modify TransformationETMPaymentTOEBSInvoice_Custom.xsl.
<xsl:template name="ApInvoicesInterface_customElements"> <xsl:template name="CiAdjApreq_standardElements"> <ns0:attribute1> <xsl:value-of select="/ns1:GetETMAPDataProcessResponse/ns1:result/ns2:SelectETMAPRecordsWithTemplate Output/ns2:B.GEO_CODE"/> </ns0:attribute1> </xsl:template> <xsl:template name="CiAdjApreq_customElements">  </xsl:template> </xsl:stylesheet>
53
Appendix
For Known Issues and Workaround, refer to the Oracle Support Knowledge article Document 1316041.1 ETPM (Oracle Enterprise Taxation and Policy Management,) - EBS Integration.
Data Mapping
The following sections show the fields that are mapped for integration.
GL Transaction
Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL Table Mapping to Oracle Enterprise Taxation and Policy Management
Column STATUS LEDGER_ID Data Type VARCHAR2 (50) NUMBER Descripti on ETM Table Column Data Type Remarks NEW, for all new transactions Derived from BPEL Identifies the Oracle EBusiness Suite Financials for General Ledger and Accounts Payable ledger to use for posting. Value = 1 (Corresponds to Vision Operations (USA) Ledger Name) ACCOUNTING_DATE DATE Effective date of the transaction (Required) Currency (Required) (Required) CREATED_BY ACTUAL_FLAG NUMBER VARCHAR2 (1) Standard Who column (Required) Balance type (actual, budget, or encumbrance)(Required) CI_FT ACCOUNTING _DT DATE Date used by GL to define the accounting period into which the Financial Transaction is booked.
Journal Import status (Required field) Ledger defining column
CURRENCY_CODE DATE_CREATED
VARCHAR2 (15) DATE
CI_FT
CURRENCY_ CD
CHAR (3) Derived from BPEL Value =sysdate Value= -1 A
Standard Who column
54
Column USER_JE_CATEGOR Y_NAME USER_JE_SOURCE_ NAME CURRENCY_CONVE RSION_DATE ENCUMBRANCE_TY PE_ID BUDGET_VERSION_I D USER_CURRENCY_ CONVERSION_TYPE CURRENCY_CONVE RSION_RATE AVERAGE_JOURNAL _FLAG ORIGINATING_BAL_ SEG_VALUE SEGMENT1
Data Type VARCHAR2 (25) VARCHAR2 (25) DATE NUMBER NUMBER VARCHAR2 (30) NUMBER VARCHAR2 (1) VARCHAR2 (25) VARCHAR2 (25)
Descripti on
ETM Table
Column
Data Type
Remarks ETM EBS ETM EBS Value = BLANK Value = BLANK Value = BLANK Value = BLANK Value = BLANK Value = BLANK Value = BLANK
Journal entry category user defined name (Required) Journal entry source user defined name (Required) Date of exchange rate Encumbrance type defining column Budget version defining column Type of exchange rate Foreign currency exchange rate Average journal flag Originating balancing segment value COMPANY CI_FT_GL GL_ACCT Position1 Varchar2 (254)
Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null.
55
SEGMENT2
VARCHAR2 (25)
DEPARTME NT
CI_FT_GL
GL_ACCT Position 2
Varchar2 (254)
SEGMENT3
VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25)
ACCOUNT
CI_FT_GL
GL_ACCT Position 3
Varchar2 (254)
SEGMENT4
SUBACCOUNT PRODUCT
CI_FT_GL
GL_ACCT Position 4
Varchar2 (254)
SEGMENT5
CI_FT_GL
GL_ACCT Position 5
Varchar2 (254)
SEGMENT6
PROGRAM CODE ALTERNATE ACCOUNT
CI_FT_GL
GL_ACCT Position 6
Varchar2 (254)
SEGMENT7
CI_FT_GL
GL_ACCT Position 7
Varchar2 (254)
Column SEGMENT8
Data Type VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25)
Descripti on PROJECT
ETM Table CI_FT_GL
Column GL_ACCT Position 8
Data Type Varchar2 (254)
Remarks Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Use (dot) as the delimiter to extract this information from Gl_Acct. 2 dots (..) indicates skip or null. Only used when fund accounting is enabled in Oracle Enterprise Taxation and Policy Management. Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK
SEGMENT9
AFFILIATE
CI_FT_GL
GL_ACCT Position 9
Varchar2 (254)
SEGMENT10
FUND AFFILIATE OPERATING UNIT AFFILIATE BUDGET REFERENC E CHARTFIEL D1 CHARTFIEL D2 CHARTFIEL D3 FUND CODE
CI_FT_GL
GL_ACCT Position 10
Varchar2 (254)
SEGMENT11
CI_FT_GL
GL_ACCT Position 11
Varchar2 (254)
SEGMENT12
CI_FT_GL
GL_ACCT Position 12
Varchar2 (254)
SEGMENT13
CI_FT_GL
GL_ACCT Position 13
Varchar2 (254)
SEGMENT14
CI_FT_GL
GL_ACCT Position 14
Varchar2 (254)
SEGMENT15
CI_FT_GL
GL_ACCT Position 15
Varchar2 (254)
SEGMENT16
CI_DST_CO DE_EFF
FUND_CD
Varchar2 (12)
SEGMENT17 SEGMENT18 SEGMENT19 SEGMENT20
Key flexfield segment
56
Column SEGMENT21 SEGMENT22 SEGMENT23 SEGMENT24 SEGMENT25 SEGMENT26 SEGMENT27 SEGMENT28 SEGMENT29 SEGMENT30 ENTERED_DR
Data Type VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) NUMBER
Descripti on
ETM Table
Column
Data Type
Remarks Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK Derived from BPEL Value = BLANK
Transaction debit amount, entered currency Transaction credit amount, entered currency Transaction debit amount, base currency Transaction credit amount, base currency
CI_FT_GL
AMOUNT
NUMBE R (15,2)
Base Currency Amount Leave the field blank if the amount is negative Leave it blank if the amount is positive.
ENTERED_CR
NUMBER
CI_FT_GL
AMOUNT
NUMBE R (15,2)
ACCOUNTED_DR
NUMBER
CI_FT_GL
AMOUNT
NUMBE R (15,2)
Base Currency Amount Leave the field blank if the amount is negative. Leave it blank if the amount is positive.
ACCOUNTED_CR
NUMBER
CI_FT_GL
AMOUNT
NUMBE R (15,2)
57
Column TRANSACTION_DAT E REFERENCE1 REFERENCE2 REFERENCE3
Data Type DATE
Descripti on
ETM Table
Column
Data Type
Remarks Do not enter a value in this column.
Date of transaction VARCHAR2 (100) VARCHAR2 (240) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (240) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) Journal Import reference column
Value = BLANK Leave blank Leave blank NULL. Do not enter a value in this column. Value = BLANK Leave blank Value = BLANK Leave blank Value = BLANK Leave blank Value = BLANK Leave blank Value = BLANK Leave blank Value = BLANK Leave blank Value = BLANK Leave blank Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK
REFERENCE4 REFERENCE5 REFERENCE6 REFERENCE7 REFERENCE8 REFERENCE9 REFERENCE10 REFERENCE11
REFERENCE12
Journal Import reference column
REFERENCE13
REFERENCE14
REFERENCE15
58
Column REFERENCE16
Data Type VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (100) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240) VARCHAR2 (240)
Descripti on
ETM Table
Column
Data Type
Remarks NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this column. Value = BLANK Leave blank Value = BLANK Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank
REFERENCE17
REFERENCE18
REFERENCE19
REFERENCE20
REFERENCE21 REFERENCE22 REFERENCE23 REFERENCE24 REFERENCE25 REFERENCE26 REFERENCE27 REFERENCE28 REFERENCE29 REFERENCE30
Journal Import reference column
Leave blank Leave blank
59
Column JE_BATCH_ID
Data Type NUMBER
Descripti on
ETM Table
Column
Data Type
Remarks NULL. Do not enter a value in this column. Value = BLANK Populated by the Import Process when the Record errors Value=Blank NULL. Do not enter a value in this column. Value = BLANK Populated by the Import Process when the Record errors NULL. Do not enter a value in this column. Value = BLANK Populated by the Import Process when the Record errors NULL. Do not enter a value in this column.
Journal entry batch defining column PERIOD_NAME JE_HEADER_ID VARCHAR2 (15) NUMBER Accounting period
Journal entry header defining column JE_LINE_NUM NUMBER
Journal entry line number CHART_OF_ACCOU NTS_ID FUNCTIONAL_CURR ENCY_CODE CODE_COMBINATIO N_ID DATE_CREATED_IN_ GL STATUS_DESCRIPTI ON NUMBER Key flexfield structure defining column VARCHAR2 (15) Ledger base currency NUMBER Key flexfield combination defining column DATE Date Journal Import created batch VARCHAR2 (240)
Value = BLANK NULL. Do not enter a value in this column. Value = BLANK Derived from the segments entered above Value =Blank NULL. Do not enter a value in this column. Value = BLANK NULL. Do not enter a value in this Column. Value = BLANK Populated by the Import Process when the Record errors Leave blank
Journal import status description STAT_AMOUNT NUMBER Statistical amount
60
Column GROUP_ID
Data Type NUMBER
Descripti on Interface group defining column
ETM Table CI_FT_PRO C
Column BATCH_NBR
Data Type NUMBE R (10)
Remarks This is the ETM GLDL Batch Number.
REQUEST_ID
NUMBER
Concurrent program request ID
Leave blank Populated by the Import Process when the Record errors
SUBLEDGER_DOC_S EQUENCE_ID SUBLEDGER_DOC_S EQUENCE_VALUE ATTRIBUTE1 ATTRIBUTE2 GL_SL_LINK_ID GL_SL_LINK_TABLE ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13
NUMBER NUMBER VARCHAR2 (150) VARCHAR2 (150) NUMBER VARCHAR2 (30) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150)
Sequential numbering sequence defining column Sequential numbering sequence value Descriptive flexfield segment Descriptive flexfield segment Link to associated subledger data Table containing associated subledger data
Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank
Descriptive flexfield segment
Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank
Descriptive flexfield segment
Leave blank Leave blank Leave blank
61
Column ATTRIBUTE14 ATTRIBUTE15 ATTRIBUTE16 ATTRIBUTE17 ATTRIBUTE18 ATTRIBUTE19 ATTRIBUTE20 CONTEXT CONTEXT2 INVOICE_DATE TAX_CODE INVOICE_IDENTIFIE R INVOICE_AMOUNT CONTEXT3 USSGL_TRANSACTI ON_CODE DESCR_FLEX_ERRO R_MESSAGE JGZZ_RECON_REF REFERENCE_DATE SET_OF_BOOKS_ID BALANCING_SEGME NT_VALUE MANAGEMENT_SEG MENT_VALUE FUNDS_RESERVED_ FLAG
Data Type VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) DATE VARCHAR2 (15) VARCHAR2 (20) NUMBER VARCHAR2 (150) VARCHAR2 (30) VARCHAR2 (240) VARCHAR2 (240) DATE NUMBER VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (1)
Descripti on
ETM Table
Column
Data Type
Remarks Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank
Descriptive flexfield context column Descriptive flexfield context column Value added tax descriptive flexfield column Value added tax descriptive flexfield column Value added tax descriptive flexfield column Value added tax descriptive flexfield column Descriptive flexfield context column Government transaction code Descriptive flexfield error message
Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank NULL. Do not enter a value in this column. Value = BLANK Leave blank Leave blank Leave blank Leave blank Leave blank Leave blank
Global reconciliation reference Reference Date Ledger defining column Balancing segment value Management segment value Reserved for Oracle internal use
62
A/P Request
AP_INVOICES_INTERFACE
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
INVOICE_ID INVOICE_NUM INVOICE_TYPE_LOO KUP_CODE INVOICE_DATE PO_NUMBER VENDOR_ID
Number VARCHAR2 (50) VARCHAR2 (25) DATE VARCHAR2 (20) NUMBER (15)
Invoice identifier Invoice number CI_A DJ ADJ_ID CHAR (12)
AP_INVOICES_interface_S .nextval
Type of Invoice (can be STANDARD or CREDIT) Invoice date CI_A DJ CRE_DT DATE
STANDARD
Purchase order number
Value = BLANK Value =40182 Configuration parameter or Select vendor_id from po_vendors where vendor_name like (Entity Name from the ETPM) Value = BLANK Value = BLANK Value =7004Or select vendor_site_id from po_vendor_Sites_All where vendor_id = <vendor_id>(from above) and org_id =<p_org_id> Value = BLANK
Supplier identifier. Validated against PO_VENDORS.VENDOR_ID. VENDOR_NUM VENDOR_NAME VENDOR_SITE_ID VARCHAR2 (30) VARCHAR2 (240) NUMBER (15,0) Supplier number Supplier name
Supplier site identifier. Validated against PO_VENDOR_SITES_ALL.VENDOR_SITE_ID VENDOR_SITE_COD E INVOICE_AMOUNT INVOICE_CURRENC Y_CODE EXCHANGE_RATE EXCHANGE_RATE_T YPE VARCHAR2 (15) NUMBER VARCHAR2 (15) NUMBER VARCHAR2 (30) Supplier site code Invoice amount CI_A DJ ADJ_AMT Number (15,2)
Currency of invoice. Validated against FND_CURRENCIES.CURRENCY_CODE. Exchange rate for foreign currency invoices Exchange rate type for foreign currency invoices. Validated against GL_DAILY_CONVERSION_TYPES.CONVERSION_TYP E. Date exchange rate is effective, usually accounting date of a transaction.
Value = Blank Value = Blank Value = Blank
EXCHANGE_DATE
DATE
Value = Blank
63
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
TERMS_ID
NUMBER (15,0)
Payment terms identifier. Validated against AP_TERMS_TL.TERM_ID. Payment terms name CI_A DJ_A PRE Q ENTITY_NAM E|CITY|COUN TRY|ADDRES S1|COUNTY| STATE| POSTAL VARCHAR2 (240)
Derived from BPELValue = 10194Configuration parameter Value = Null
TERMS_NAME DESCRIPTION
VARCHAR2 (50) VARCHAR2 (240)
Invoice description AWT_GROUP_ID AWT_GROUP_NAME LAST_UPDATE_DAT E LAST_UPDATED_BY LAST_UPDATE_LOGI N CREATION_DATE CREATED_BY ATTRIBUTE_CATEG ORY ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 NUMBER (15,0) VARCHAR2 (25) DATE NUMBER (15,0) NUMBER (15,0)
Withholding tax group identifier. Validated against AP_AWT_GROUPS.AWT_GROUP_ID. Withholding tax group name Standard Who column - date when a user last updated this row. Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). Standard who column - date when this row was created Standard who column - user who created this row (foreign key to FND_USER.USER_ID). Descriptive flexfield structure definition column. Descriptive flexfield segment
Value = Blank Value = Blank Sysdate Value= Blank Value= Blank
DATE NUMBER (15,0) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150)
Sysdate Value= Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
64
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 GLOBAL_ATTRIBUTE _CATEGORY GLOBAL_ATTRIBUTE 1 GLOBAL_ATTRIBUTE 2 GLOBAL_ATTRIBUTE 3 GLOBAL_ATTRIBUTE 4 GLOBAL_ATTRIBUTE 5 GLOBAL_ATTRIBUTE 6 GLOBAL_ATTRIBUTE 7 GLOBAL_ATTRIBUTE 8 GLOBAL_ATTRIBUTE 9 GLOBAL_ATTRIBUTE 10 GLOBAL_ATTRIBUTE 11 GLOBAL_ATTRIBUTE 12
VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) Reserved for country-specific functionality
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
65
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
GLOBAL_ATTRIBUTE 13 GLOBAL_ATTRIBUTE 14 GLOBAL_ATTRIBUTE 15 GLOBAL_ATTRIBUTE 16 GLOBAL_ATTRIBUTE 17 GLOBAL_ATTRIBUTE 18 GLOBAL_ATTRIBUTE 19 GLOBAL_ATTRIBUTE 20 STATUS
VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (25) Status of the data in or after the Payables Open Interface Import Prepayment Reference Reserved for country-specific functionality
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Import Process will insert Value = PROCESSED/REJECTED Derived from BPEL Value = ETM Value = Blank Value = Blank Group identifier Concurrent Program who column - concurrent request ID of the program that last updated this row (foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID). Cross currency payment rate type (must be EMU Fixed in Release 11) Cross currency payment rate date Exchange rate between invoice and payment; in Release 11 the value is always 1 unless they are associated fixedrate currencies. Cross currency payment currency. Validated against FND_CURRENCIES.CURRENCY_CODE. Flag that indicates if the Payables Open Interface Workflow should process the record (Y or N). Sequential numbering (voucher number) document category. Validated against FND_DOC_SEQUENCE_CATEGORIES.CODE.
SOURCE GROUP_ID REQUEST_ID
VARCHAR2 (80) VARCHAR2 (80) NUMBER
PAYMENT_CROSS_ RATE_TYPE PAYMENT_CROSS_ RATE_DATE PAYMENT_CROSS_ RATE PAYMENT_CURREN CY_CODE WORKFLOW_FLAG DOC_CATEGORY_C ODE
VARCHAR2 (30) DATE NUMBER
VARCHAR2 (15) VARCHAR2 (1) VARCHAR2 (30)
66
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
VOUCHER_NUM
VARCHAR2 (50)
Voucher number; validated (Sequential Numbering enabled), or non-validated (Sequential Numbering not enabled). Name of payment method Name of pay group Date invoice items received Date invoice received Accounting date to default to invoice distributions
Value = Blank
PAYMENT_METHOD _LOOKUP_CODE PAY_GROUP_LOOK UP_CODE GOODS_RECEIVED_ DATE INVOICE_RECEIVED _DATE GL_DATE ACCTS_PAY_CODE_ COMBINATION_ID USSGL_TRANSACTI ON_CODE
VARCHAR2 (25) VARCHAR2 (25) DATE DATE DATE NUMBER (15,0)
Value =Blank Value = BLANK Value = Blank Value = Blank Derived from BPEL Value = Blank Value = Blank
Accounting Flexfield identifier for A/P liability account. Validated against GL_CODE_COMBINATIONS.CODE_COMBINATION_ID Default transaction code for creating US Standard GL journal entries (Oracle Public Sector Payables). Validated against GL_USSGL_TRANSACTION_CODES.USSGL_TRANSA CTION_CODE Flag that indicates whether to pay invoice on a separate payment document Organizati on identifier CI_CI S_DI V_CH AR CHAR_VAL CHAR (16)
VARCHAR2 (30)
Value = Blank
EXCLUSIVE_PAYME NT_FLAG ORG_ID
VARCHAR2 (1) NUMBER (15,0)
Value = Null The Value Picked from the Mapping existing in the ETPM system. Value = Null Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
AMOUNT_APPLICAB LE_TO_DISCOUNT PREPAY_NUM PREPAY_DIST_NUM PREPAY_APPLY_AM OUNT PREPAY_GL_DATE INVOICE_INCLUDES _PREPAY_FLAG
NUMBER VARCHAR2 (50) NUMBER (15,0) NUMBER DATE VARCHAR2 (1)
Amount of invoice applicable to a discount The invoice number of an existing, fully paid prepayment to be applied to the imported invoice. No longer used The amount of prepayment that the user wants to apply to the invoice. This amount has to be positive. The accounting date to be used for the prepayment application. If left null, the invoices GL_DATE is used. Prorate Discount
67
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
NO_XRATE_BASE_A MOUNT
NUMBER
Invoice amount in the functional currency. Used only when the Calculate User Exchange Rate option is enabled, and used only for foreign currency invoices when the exchange rate type is User. The system uses this value and the invoice amount to calculate the exchange rate. Supplier E-mail address for XML invoice rejections. Date used with payment terms to calculate scheduled payment of an invoice. Requester of invoice is used by the Invoice Approval Workflow process to generate the list of approvers. Ship to location for purchase order matching. Used for XML invoices. Internal document reference number from Accounts Receivables system. Used for XML invoices. The invoice line of an existing Prepayment to be applied to the imported invoice. The first name of the employee who requested goods or services on the invoice line. This value is used to derive the requester ID. If you use Invoice Approval Workflow then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line. The last name of the employee who requested goods or services on the invoice line. This value is used to derive the requester ID. If you use Invoice Approval Workflow then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line. Application Identifier Product source table name
Value = Blank
VENDOR_EMAIL_AD DRESS TERMS_DATE REQUESTER_ID SHIP_TO_LOCATION EXTERNAL_DOC_RE F PREPAY_LINE_NUM REQUESTER_FIRST _NAME
VARCHAR2 (2000) DATE NUMBER (10,0) VARCHAR2 (40) VARCHAR2 (240) NUMBER VARCHAR2 (150)
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
REQUESTER_LAST_ NAME
VARCHAR2 (150)
Value = Blank
APPLICATION_ID PRODUCT_TABLE
NUMBER (15,0) VARCHAR2 (30)
Value = Blank Value = Blank
REFERENCE_KEY1 REFERENCE_KEY2 REFERENCE_KEY3 REFERENCE_KEY4 REFERENCE_KEY5
VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150 VARCHAR2 (150) VARCHAR2 (150) Primary key information that will uniquely identify a record in other products view.
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
68
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
APPLY_ADVANCES_ FLAG CALC_TAX_DURING _IMPORT_FLAG CONTROL_AMOUNT ADD_TAX_TO_INV_A MT_FLAG TAX_RELATED_INVO ICE_ID TAXATION_COUNTR Y DOCUMENT_SUB_T YPE SUPPLIER_TAX_INV OICE_NUMBER
VARCHAR2 (1) VARCHAR2 (1) NUMBER VARCHAR2 (1) NUMBER (15,0) VARCHAR2 (30)
A value of Y indicates that applicable advances will be applied against expense reports and other invoices Indicates whether tax should be calculated or not for the imported invoice Allows user to enter total tax amount to be prorated by EBusiness Tax Indicates whether the invoice amount should be grossed up by the calculated tax Tax Driver: Invoice ID of related document for tax purposes. Replaces a GDFF: This country sets the context for other tax drivers. The value defaults to the LE country but can be overridden by the user. Replaces a GDFF: In certain countries, a tax or governmental authority defines and classifies document types for reporting purposes. Replaces a GDFF: In some countries such as Thailand, there is a requirement to report on a supplier issued "tax" invoice that is distinct from the regular invoice. The tax invoice is either attached to the standard Supplier Invoice (when the value = Goods); or, the supplier may issue it when he receives the payment. Replaces a GDFF: To satisfy reporting requirements in certain countries, the Tax Invoice Date on the supplierissued tax invoice needs to be recorded. Replaces a GDFF: The supplier exchange rate is entered in online invoices to calculate the supplier tax amount for foreign currency invoices. The gain/loss in the tax amount for foreign currency invoices is the difference between the in-house tax amount using the in-house exchange rate and the supplier tax amount using the supplier exchange rate that you enter here. A manual journal entry is posted to the GL to incorporate the gain/loss. Replaces a GDFF: To satisfy reporting requirements in certain countries, the company-specific Tax Invoice Date and Number needs to be captured. This field is used to record the date the company receives/ records the supplier-issued tax invoice and is required to comply with reporting requirements.
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Null
Value = Blank
Value = Blank
SUPPLIER_TAX_INV OICE_DATE SUPPLIER_TAX_EXC HANGE_RATE
DATE
Value = Blank
NUMBER
Value = Blank
TAX_INVOICE_RECO RDING_DATE
DATE
Value = Blank
69
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
TAX_INVOICE_INTER NAL_SEQ
VARCHAR2 (150)
Replaces a GDFF: To satisfy reporting requirements in certain countries, the company-issued Tax Invoice Date and Number. This field is used to record the companyspecific tax invoice number, in sequence, issued by the company for a supplier-issued tax invoice. This is required to comply with reporting requirements. Legal Entity Identifier Legal Entity Name A reference to a record in another application A reference to a record in another application Organization name Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. Remittance message for use in payment processing Remittance message for use in payment processing Remittance message for use in payment processing Unique remittance identifier provided by the payee Unique remittance identifier check digit The priority with which the financial institution or payment system should settle payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. Payment reason code Free text field available for entering a reason for the payment CI_A DJ_A PRE Q AP_REQ_ID CHAR (12)
Value = Blank
LEGAL_ENTITY_ID LEGAL_ENTITY_NAM E REFERENCE_1 REFERENCE_2 OPERATING_UNIT BANK_CHARGE_BEA RER REMITTANCE_MESS AGE1 REMITTANCE_MESS AGE2 REMITTANCE_MESS AGE3 UNIQUE_REMITTAN CE_IDENTIFIER URI_CHECK_DIGIT SETTLEMENT_PRIO RITY
NUMBER (15,0) VARCHAR2 (50) VARCHAR2 (30) VARCHAR2 (30) VARCHAR2 (240) VARCHAR2 (30) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (30) VARCHAR2 (2) VARCHAR2 (30)
Value = Blank Value = Blank Value = Blank Value = Blank Value= Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
PAYMENT_REASON_ CODE PAYMENT_REASON_ COMMENTS
Value = Blank
PAYMENT_METHOD _CODE DELIVERY_CHANNE L_CODE
Payment method identifier Delivery channel code
Value = CHECK Value = Blank
70
Columns
Data Type
Descript ion
ETM Tabl e
Column
Data Type
Remarks
PAID_ON_BEHALF_E MPLOYEE_ID
NUMBER (15,0)
When an expense report gets split in Both Pay scenario, the new expense report's paid_on_behalf_employee_id gets populated with the original expense report's employee_id. Flag to indicate invoice amount is net of retainage The employee number of the employee who requested goods or services on the invoice line. Customer legal registration code Customer legal registration number Party identifier Party Site identifier Type of payment processing transaction or document The function or purpose of the payment Number representing payment priority of a scheduled payment (1 to 99) Customs location code External bank account identifier
Value = Blank
NET_OF_RETAINAG E_FLAG REQUESTER_EMPL OYEE_NUM CUST_REGISTRATIO N_CODE CUST_REGISTRATIO N_NUMBER PARTY_ID PARTY_SITE_ID PAY_PROC_TRXN_T YPE_CODE PAYMENT_FUNCTIO N PAYMENT_PRIORITY PORT_OF_ENTRY_C ODE EXTERNAL_BANK_A CCOUNT_ID
VARCHAR2 (1) VARCHAR2 (30) VARCHAR2 (30) VARCHAR2 (30) NUMBER (15,0) NUMBER (15,0) VARCHAR2 (30) VARCHAR2 (30) NUMBER (2,0) VARCHAR2 (30) NUMBER (15,0)
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
AP_INVOICE_LINES_INTERFACE
Columns
Data Type NUMBER (15,0) NUMBER (15,0) NUMBER (15,0) VARCHAR2 (25)
Descripti on
ETM Table
Column
Data Type
Remarks AP_INVOICES_interfac e_S.currval AP_INVOICE_lines_inte rface_S.nextval Value =1 'MISCELLANEOUS'
INVOICE_ID INVOICE_LINE_ID LINE_NUMBER LINE_TYPE_LOOKU P_CODE
Invoice identifier. Validated against AP_INVOICES_INTERFACE.INVOICE_ID Invoice line identifier Invoice line number Type of invoice line (Item, Freight, Tax, Miscellaneous)
71
Columns LINE_GROUP_NUM BER AMOUNT ACCOUNTING_DAT E
Data Type
Descripti on
ETM Table
Column
Data Type
Remarks Value = Blank
NUMBER NUMBER DATE
Value to identify each item line to which you want to prorate Line amount Accounting date CI_ADJ ADJ_AMT Number (15,2)
SYSDATE Value =Refund Request from Oracle Enterprise Taxation and Policy Management Value = Blank Value = Blank Value = Blank N, Since we are not matching to PO Value = Blank
DESCRIPTION AMOUNT_INCLUDE S_TAX_FLAG PRORATE_ACROSS _FLAG TAX_CODE FINAL_MATCH_FLA G
Description No Longer Used Prorate indicator for this line to be prorated across all lines with the same LINE_GROUP_NUMBER Tax code. Validated against AP_TAX_CODES_ALL.NAME Final match indicator for distribution line matched to purchase order Purchase order header identifier used for PO matching. Validated against PO_HEADERS_ALL.PO_HEADER_ID Purchase order number used for PO matching. Validated against PO_HEADERS_ALL.SEGMENT1 Purchase order line identifier used for PO matching. Validated against PO_LINES_ALL.PO_LINE_ID Purchase order line number used for PO matching. Validated against PO_LINES_ALL.PO_LINE_NUM Purchase order line location identifier used for PO matching. Validated against PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID Purchase order shipment number used for PO matching. Validated against PO_LINE_LOCATIONS_ALL.SHIPMENT_NUM Purchase order distribution line identifier used for PO matching. Validated against PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID Purchase order distribution line number used for PO matching. Validated against PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_NUM No longer used Inventory item identifier. Validated against MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID
PO_HEADER_ID PO_NUMBER PO_LINE_ID PO_LINE_NUMBER PO_LINE_LOCATIO N_ID PO_SHIPMENT_NU M PO_DISTRIBUTION_ ID PO_DISTRIBUTION_ NUM PO_UNIT_OF_MEAS URE INVENTORY_ITEM_I D
72
NUMBER VARCHAR2 (20) NUMBER NUMBER
Value = Blank Value = Blank Value = Blank Value = Blank
NUMBER
Value = Blank
NUMBER
Value = Blank
NUMBER
Value = Blank
NUMBER VARCHAR2 (25) NUMBER
Columns
Data Type
Descripti on Inventory item description
ETM Table
Column
Data Type
ITEM_DESCRIPTIO N QUANTITY_INVOICE D SHIP_TO_LOCATIO N_CODE UNIT_PRICE DISTRIBUTION_SET _ID DISTRIBUTION_SET _NAME
VARCHAR2 (240) NUMBER VARCHAR2 (60) NUMBER NUMBER (15,0) VARCHAR2 (50)
Quantity invoiced against purchase order shipment Ship to location code Unit price for purchase order matched invoice items Distribution set identifier. Validated against AP_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SET _ID Distribution set name. Validated against AP_INVOICE_DISTRIBUTION_SETS_ALL.DISTRIBU TION_SET_NAME Accounting flexfield for account associated with a distribution line CI_DST_CO DE_EFF GL_ACCT VARCHAR 2 (48)
Value = Blank Value = Blank Value = Blank Value = Blank
Value = Blank
Extract all the segments that comes from the ETM side and separate them by -
DIST_CODE_CONC ATENATED
VARCHAR2 (250)
DIST_CODE_COMBI NATION_ID AWT_GROUP_ID AWT_GROUP_NAM E LAST_UPDATED_BY LAST_UPDATE_DAT E LAST_UPDATE_LO GIN CREATED_BY CREATION_DATE ATTRIBUTE_CATEG ORY ATTRIBUTE1
NUMBER (15,0) NUMBER (15,0) VARCHAR2 (25) NUMBER (15,0) DATE NUMBER (15,0) NUMBER (15,0) DATE VARCHAR2 (150) VARCHAR2 (150)
Accounting flexfield identifier for account associated with a distribution line. Validated against GL_CODE_COMBINATIONS.CODE_COMBINATION_I D Withholding tax group identifier. Validated against AP_AWT_GROUPS.GROUP_ID Withholding tax group name Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). Standard Who column - date when a user last updated this row. Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). Standard who column - user who created this row (foreign key to FND_USER.USER_ID). Standard who column - date when this row was created Descriptive flexfield structure definition column. Descriptive flexfield segment Value = Blank Value = Blank Value= Blank SYSDATE Value= Blank
Value= Blank SYSDATE Value = Blank Value = Blank
73
Columns
Data Type VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150)
Descripti on
ETM Table
Column
Data Type
Remarks Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 GLOBAL_ATTRIBUT E_CATEGORY GLOBAL_ATTRIBUT E1 GLOBAL_ATTRIBUT E2 GLOBAL_ATTRIBUT E3 GLOBAL_ATTRIBUT E4 GLOBAL_ATTRIBUT E5 GLOBAL_ATTRIBUT E6
74
Reserved for country-specific localizations
Columns GLOBAL_ATTRIBUT E7 GLOBAL_ATTRIBUT E8 GLOBAL_ATTRIBUT E9 GLOBAL_ATTRIBUT E10 GLOBAL_ATTRIBUT E11 GLOBAL_ATTRIBUT E12 GLOBAL_ATTRIBUT E13 GLOBAL_ATTRIBUT E14 GLOBAL_ATTRIBUT E15 GLOBAL_ATTRIBUT E16 GLOBAL_ATTRIBUT E17 GLOBAL_ATTRIBUT E18 GLOBAL_ATTRIBUT E19 GLOBAL_ATTRIBUT E20
Data Type VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150)
Descripti on
ETM Table
Column
Data Type
Remarks Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
Reserved for country-specific localizations
PO_RELEASE_ID
NUMBER
Blanket purchase order release identifier used for PO matching. Validated against PO_RELEASES_ALL.PO_RELEASE_ID Blanket purchase order release number used for PO matching. Validated against PO_RELEASES_ALL.RELEASE_NUM Value for account segment of accounting flexfield. Payables will overlay this value on the accounting flexfield during import. Value for balancing segment of accounting flexfield. Payables will overlay this value on the accounting flexfield during import. Value for cost center segment of accounting flexfield. Payables will overlay this value on the accounting flexfield during import.
Value = Blank
Value = Blank
RELEASE_NUM ACCOUNT_SEGME NT BALANCING_SEGM ENT COST_CENTER_SE GMENT
NUMBER VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25)
Value = Blank
Value = Blank
Value = Blank
75
Columns
Data Type
Descripti on
ETM Table
Column
Data Type
PROJECT_ID
NUMBER (15,0) NUMBER (15,0) VARCHAR2 (30) DATE NUMBER (15,0) VARCHAR2 (30) VARCHAR2 (1) NUMBER (22,5)
Identifier for project used to build default accounting flexfield. Validated against PA_PROJECTS_ALL.PROJECT_ID Identifier for project task used to build default accounting flexfield. Validated against PA_TASKS.TASK_ID Project expenditure type used to build default accounting flexfield. Validated against PA_EXPENDITURE_TYPES.EXPENDITURE_TYPE Project expenditure item date used to build default accounting flexfield Identifier for project organization used to build default accounting flexfield. Validated against PA_EXP_ORGS_IT.ORGANIZATION_ID No longer used Flag that indicates if project related invoice distributions have been transferred into Oracle Projects (Y or N) Project item quantity used to build accounting flexfield for project-related distribution line USSGL transaction code for creating US Standard GL journal entries (Oracle Public Sector Payables). Validated against GL_USSGL_TRANSACTION_CODES.USSGL_TRAN SACTION_CODE Amount associated with a distribution line for measuring statistical quantities 1099 type Reporting region for distribution line for 1099 supplier. Validated against AP_INCOME_TAX_REGIONS.REGION_SHORT_NAM E Flag that indicates if distribution line is tracked in Oracle Assets (Y or N) Flag that indicates if line produces price correction Organizatio n identifier The receipt number to which an invoice will be matched. Validated against RCV_SHIPMENT_HEADERS.RECEIPT_NUM
Value = Blank
TASK_ID EXPENDITURE_TYP E EXPENDITURE_ITE M_DATE EXPENDITURE_OR GANIZATION_ID PROJECT_ACCOUN TING_CONTEXT PA_ADDITION_FLA G PA_QUANTITY
Value = Blank
Value = Blank
USSGL_TRANSACTI ON_CODE STAT_AMOUNT TYPE_1099
VARCHAR2 (30) NUMBER VARCHAR2 (10)
INCOME_TAX_REGI ON ASSETS_TRACKING _FLAG PRICE_CORRECTIO N_FLAG ORG_ID
VARCHAR2 (10) VARCHAR2 (1) VARCHAR2 (1) NUMBER (15,0) VARCHAR2 (30)
Value = Blank
RECEIPT_NUMBER
76
Columns
Data Type
Descripti on
ETM Table
Column
Data Type
RECEIPT_LINE_NU MBER MATCH_OPTION PACKING_SLIP RCV_TRANSACTIO N_ID PA_CC_AR_INVOIC E_ID PA_CC_AR_INVOIC E_LINE_NUM
VARCHAR2 (25) VARCHAR2 (25) VARCHAR2 (25) NUMBER NUMBER (15,0) NUMBER (15,0)
The receipt line number to which an invoice will be matched. Validated against RCV_SHIPMENT_LINES.LINE_NUM The value of the Invoice Match option on the PO shipment Packing slip identifier Receipt identifier used for Receipt matching. Validated against RCV_TRANSACTIONS.TRANSACTION_ID Identifier of the corresponding receivable intercompany invoice in Oracle Receivables Line number of the corresponding receivable intercompany invoice in Oracle Receivables A reference to a record in another application CI_ADJ_AP REQ AP_REQ_ ID CHAR (12)
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
REFERENCE_1 REFERENCE_2 PA_CC_PROCESSE D_CODE TAX_RECOVERY_R ATE TAX_RECOVERY_O VERRIDE_FLAG TAX_RECOVERABL E_FLAG TAX_CODE_OVERR IDE_FLAG TAX_CODE_ID CREDIT_CARD_TRX _ID AWARD_ID VENDOR_ITEM_NU M TAXABLE_FLAG PRICE_CORRECT_I NV_NUM
VARCHAR2 (30) VARCHAR2 (30) VARCHAR2 (1) NUMBER VARCHAR2 (1) VARCHAR2 (1) VARCHAR2 (1) NUMBER (15,0) NUMBER (15,0) NUMBER (15,0) VARCHAR2 (25) VARCHAR2 (1) VARCHAR2 (50)
A reference to a record in another application Indicates the processing status of this invoice line by Oracle Projects in the Receiver Operating Unit No Longer Used No Longer Used No Longer Used No Longer Used Tax code identifier for the tax code to be used. Validated against AP_TAX_CODES_ALL.TAX_ID Credit card transaction ID if the line is a credit card charge Grants requirement to store award Optional. Validated against PO_LINES_ALL.VENDOR_PRODUCT_NUM A value of Y indicates that the line is taxable Number of the invoice that this price correction invoice is correcting. Validated against AP_INVOICES_ALL.INVOICE_NUM
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
77
Columns EXTERNAL_DOC_LI NE_REF
Data Type VARCHAR2 (240) VARCHAR2 (35) VARCHAR2 (30) VARCHAR2 (40) VARCHAR2 (15) VARCHAR2 (1) DATE DATE
Descripti on
ETM Table
Column
Data Type
Remarks Value = Blank Value = Blank
Internal document reference number from Accounts Receivables system. Used for XML invoices Serial number for item Name of the manufacturer Model information Warranty number Flag that indicates whether to generate deferred accounting for this line The start date of the deferred expense period The end date of the deferred expense period Number of periods to generate deferred expenses. Used in combination with PERIOD_TYPE. Alternative to END_DATE Period type used in combination with NUMBER_OF_PERIODS to generate deferred expenses. Validated against XLA_LOOKUPS with lookup type XLA_DEFERRED_PERIOD_TYPE Unit of Measure for quantity invoiced. Validated against MTL_UNITS_OF_MEASURE.UNIT_OF_MEASURE Invoice line subject to the price correction Asset Book Defaults to the distributions candidate for transfer to Oracle Assets Asset Category Defaults to the distributions candidate for transfer to Oracle Assets Requester identifier. Valid values from active HR employees. Validated against PER_ALL_PEOPLE_F.PERSON_ID The first name of the employee who requested goods or services on the invoice line. This value is used to derive the requester ID. If you use Invoice Approval Workflow then, you can define rules that use the requester ID to generate a hierarchical list of approvers for the line.
SERIAL_NUMBER MANUFACTURER MODEL_NUMBER WARRANTY_NUMB ER DEFERRED_ACCTG _FLAG DEF_ACCTG_STAR T_DATE DEF_ACCTG_END_ DATE DEF_ACCTG_NUMB ER_OF_PERIODS
NUMBER
Value = Blank
DEF_ACCTG_PERIO D_TYPE UNIT_OF_MEAS_LO OKUP_CODE PRICE_CORRECT_I NV_LINE_NUM ASSET_BOOK_TYP E_CODE ASSET_CATEGORY _ID
VARCHAR2 (15) VARCHAR2 (25) NUMBER VARCHAR2 (15) NUMBER (15,0) NUMBER (15,0)
REQUESTER_ID
Value = Blank
REQUESTER_FIRST _NAME
VARCHAR2 (150)
78
Columns
Data Type
Descripti on
ETM Table
Column
Data Type
REQUESTER_LAST _NAME
VARCHAR2 (150)
The last name of the employee who requested goods or services on the invoice line. This value is used to derive the requester ID. If you use Invoice Approval Workflow, then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line. The employee number of the employee who requested goods or services on the invoice line. This value is used to derive the requester ID. If you use Invoice Approval Workflow, then you can define rules that use the requester ID to generate a hierarchical list of approvers for the line. Application Identifier Product source table name Primary key information that will uniquely identify a record in other products view Primary key information that will uniquely identify a record in other products view Primary key information that will uniquely identify a record in other products view Primary key information that will uniquely identify a record in other products view Primary key information that will uniquely identify a record in other products view Item category concatenated segments Item category unique identifier Identifier of the cost component class. Cost Component Classes are used to identify the individual buckets or component costs that make up the total cost of an item, for example, direct material costs, freight costs, labor costs, production, or conversion costs, and so on. Cost component class name. Cost Component Classes are used to identify the individual buckets or component costs that make up the total cost of an item, for example, direct material costs, freight costs, labor costs, production, or conversion costs, and so on. Optional, user-enterable value to ensure that the calculated tax will be the same as on the physical document
Value = Blank
REQUESTER_EMPL OYEE_NUM APPLICATION_ID PRODUCT_TABLE REFERENCE_KEY1 REFERENCE_KEY2 REFERENCE_KEY3 REFERENCE_KEY4 REFERENCE_KEY5 PURCHASING_CAT EGORY PURCHASING_CAT EGORY_ID
VARCHAR2 (30) NUMBER (15,0) VARCHAR2 (30) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (150) VARCHAR2 (2000) NUMBER (15,0)
Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
COST_FACTOR_ID
NUMBER (15,0)
Value = Blank
COST_FACTOR_NA ME CONTROL_AMOUN T
VARCHAR2 (80)
Value = Blank
NUMBER
79
Columns ASSESSABLE_VALU E
Data Type
Descripti on
ETM Table
Column
Data Type
Remarks Value = Blank Value = Blank
NUMBER
User-enterable amount to be used as taxable basis Already addressed by lines project Tax Driver: Code combination identifier of the GL account associated with the transaction line. Note that this is necessary to support the Account Method VAT feature. Tax Driver: The purpose for which a product may be used. The actual use will be stored at the distribution level. Tax Driver: Ship to location ID. Value entered by user only if line is not PO matched. Tax Driver: Type of product. Possible values are: Goods, Service. This value will default from Inventory Item attributes. Otherwise, value will be entered by user. Tax Driver: Product category Tax Driver: Product fiscal classification Tax Driver: Fiscal Classification. Tax Driver: Transactions category assigned by user. Tax Regime Code: The set of tax rules that determines the treatment of one or more taxes administered by a tax authority. For example: VAT Regime in Argentina A classification of a charge imposed by a government through a fiscal or tax authority. Internal ID of the Tax Jurisdiction Tax status code. For example: taxable standard rate, zero rated, exempt, non-taxable Internal identifier for tax rate effective on the invoice date. Tax rate name associated with tax rate identifier. Tax_rate_id is unique while a tax_rate_code may have different tax rates based on date ranges The rate specified for a tax status in effect for a period of time. Flag to indicate if the amount in the tax line is included or not in the taxable line
DEFAULT_DIST_CCI D PRIMARY_INTENDE D_USE SHIP_TO_LOCATIO N_ID
NUMBER (15,0) VARCHAR2 (30) NUMBER (15,0)
Value = Blank
PRODUCT_TYPE PRODUCT_CATEGO RY PRODUCT_FISC_CL ASSIFICATION USER_DEFINED_FI SC_CLASS TRX_BUSINESS_CA TEGORY
TAX_REGIME_COD E TAX TAX_JURISDICTION _CODE TAX_STATUS_COD E TAX_RATE_ID
VARCHAR2 (30) VARCHAR2 (30) VARCHAR2 (30) VARCHAR2 (30) NUMBER (15,0) VARCHAR2 (150) NUMBER VARCHAR2 (1)
TAX_RATE_CODE TAX_RATE INCL_IN_TAXABLE_ LINE_FLAG

80
Columns SOURCE_APPLICAT ION_ID SOURCE_ENTITY_C ODE SOURCE_EVENT_C LASS_CODE SOURCE_TRX_ID SOURCE_LINE_ID SOURCE_TRX_LEV EL_TYPE TAX_CLASSIFICATI ON_CODE
Data Type
Descripti on
ETM Table
Column
Data Type
Remarks Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank Value = Blank
NUMBER VARCHAR2 (30) VARCHAR2 (30) NUMBER NUMBER VARCHAR2 (30) VARCHAR2 (30)
Source document application identifier Source document entity code Source document event class code Source document transaction identifier Identifier of the lowest level for which Tax is calculated Source document transaction level type Tax Classification Code
A/P Data
Oracle E-Business Suite Financials for General Ledger and Accounts Payable A/P data table mapping to Oracle Enterprise Taxation and Policy Management
ETM Table CI_ADJ_APRE Q CI_ADJ_APRE Q CI_ADJ_APRE Q CI_ADJ_APRE Q CI_ADJ_APRE Q Colum ns PAY_DO C_ID PAY_DO C_DT PYMNT_ ID PAID_A MT PYMNT_ SEL_ST AT_FLG Data Type VARCHAR2 (20) DATE CHAR (10) NUMBER (15,2) CHAR (1) Descripti on Advice ID Advice Date Payment Number Paid Amount Payment Selections Status EBS Table AP_CHECKS_A LL AP_CHECKS_A LL AP_CHECKS_A LL AP_CHECKS_A LL Columns CHECK_ID CHECK_DAT E CHECK_NUM BER AMOUNT Data Type NUMBER (15) DATE NUMBER (15) NUMBER Remarks
Derived from BPEL. Value = P (For valid Payment) Value =C (For Void hold or Initiate stop) And Value =X (For Void Cancel) AP_INVOICES_ ALL PAYMENT_R EASON_CO MMENTS VARCHAR2 (240)
CI_ADJ_APRE Q
AP_REQ _ID
CHAR (12)
AP Request ID
81
ETM Table CI_ADJ_APRE Q
Colum ns ADJ_ID
Data Type CHAR (12)
Descripti on Adjustment ID
EBS Table AP_INVOICES_ ALL
Columns INVOICE_NU M
Data Type VARCHAR2 (50)
Remarks If liability is closed, the Adjustment Maintenanc e service will be invoked for this Adjustment ID.
CI_ADJ_APRE Q
PYMNT_ SEL_ST AT_FLG
CHAR (1)
Payment Selections Status
Derived from BPEL. When AP_CHECKS_ALL.STOPPED_DATE IS NOT NULL or . AP_CHECKS_ALL. VOID_DATE IS NOT NULL then Value=C When AP_INVOICES_ALL.CANCELLED_DATE IS NOT NULL then Value=X
CI_ADJ
CAN_RS N_CD
CHAR (4)
Cancel Reason Code
WRNG
Database Tables Involved in Integration

The following sections identify the database tables involved in this integration. Note: For information on Oracle Applications and Oracle Enterprise Taxation and Policy Management tables, refer to the product documentation.
Oracle Enterprise Taxation and Policy Management
The following Oracle Enterprise Taxation and Policy Management tables are used when extracting Financial Transaction data for sending to the GL as Journal Vouchers. CI_FT CI_FT_GL CI_DST_CODE_EFF CI_FT_PROC (FT Process) CI_BATCH_CTRL (Batch Control)
82
CI_BATCH_RUN CI_BATCH_JOB
Neither the GLDL flat file header record layout nor the GLDL flat file detail record layout is used in this integration.
Oracle E-Business Suite Financials for General Ledger and Accounts Payable Tables
GL_INTERFACE is used to stage the incoming accounting entries from Oracle Enterprise Taxation and Policy Management.
A/P Request
The Oracle Enterprise Taxation and Policy Management APREQ table is considered an interface table for this integration point even though it is a core table within Oracle Enterprise Taxation and Policy Management. BPEL extracts the data directly from the core tables. The following tables are used when extracting A/P Request information from Oracle Enterprise Taxation and Policy Management. CI_ADJ_APREQ CI_ADJ CI_SA CI_ACCT CI_ACCT_PER CI_PER CI_PER_NAME
Oracle Applications A/P Tables

The following A/P Invoice staging tables are used to stage the incoming A/P Requests from Oracle Enterprise Taxation and Policy Management. AP_INVOICES_INTERFACE AP_INVOICE_LINES_INTERFACE Oracle Application APIs to create Vendor and Vendor Site AP_VENDOR_PUB_PKG.CREATE_VENDOR AP_VENDOR_PUB_PKG.CREATE_VENDOR_SITE AP_VENDOR_SITES_PKG.UPDATE_ROW
83

Oracle Applications A/P Tables
No Oracle E-Business Suite Financials for General Ledger and Accounts Payable interface tables are used in this integration point. The Payment Information is extracted from the following application tables: AP_INVOICES_ALL AP_CHECKS_ALL AP_INVOICE_PAYMENTS_ALL

The CI_ADJ_APREQ application table is updated with the Payment Information received from Oracle E-Business Suite Financials for General Ledger and Accounts Payable. This table is considered an interface table for the purpose of this integration point even though it is a core Oracle Enterprise Taxation and Policy Management product table. The Payment Information is inserted into the following application tables: CI_ADJ_APREQ
Logic Used in the Integration Points

The following describes the logic used in the BPEL services that form part of this integration product.
Oracle BPEL Process Manager Poll Oracle Enterprise Taxation and Policy Management to verify whether Financial Transactions are ready for extraction
If GLS has run since the last run of the integration AND the GLS run has completed successfully Retrieve the Batch of Rows identified in CI_BATCH_RUN (created by GLS) Else Do nothing
Update the NEXT BATCH NUMBER in CI_BATCH_CNTRL

Increment by 1 the NEXT_BATCH_NBR in CI_BATCH_CTRL WHERE BATCH_CD is GLDL
Extract Financial Transactions from Oracle Enterprise Taxation and Policy Management
Select the information shown in the table below: FROM CI_FT_PROC, CI_FT_GL, CI_FT FT, CI_DST_CODE_EFF WHERE the rows were marked by GLS as belonging to the latest batch that is ready to be integrated Summarize and group the rows 84 Copyright 2000, 2011, Oracle. All rights reserved.
Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Release 3.1.1 Implementation Guide BY FTPR.BATCH_NBR, FTGL.DST_ID, FTGL.GL_ACCT, FT.CIS_DIVISION, FT.GL_DIVISION, FT.CURRENCY_CD, DST.STATISTICS_CD, FT.ACCOUNTING_DT, DST.FUND_CD
Extract Information Field Name Source System BATCH_NBR DIST_ID Set to ETM The batch number for the group of FTs extracted. It is assigned to the financial transaction when GLS is run. The distribution code used in Oracle Enterprise Taxation and Policy Management to derive the GL account information. A sample data example is R ELERES for electric residential revenue financial transactions. The actual GL account with . separating the substructure numbers like department. For example: 101.73653.8873..87 The Division The GL Division The currency the amount, such as USD. The identifier of the type of statistical amount being sent to GL such as KWH for electricity or CCF for gas. The effective accounting date for the GL transactions The dollar amount of the GL debit or credit The quantity associated with the Statics Code. Source/Value/Description
GL_ACCT CIS_DIVISION GL_DIVISION CURRENCY_CD STATISTICS_CD ACCOUNTING_DT AMOUNT STATISTIC_AMOUNT
When the above is executed successfully, continue by executing the following:
Update the LAST UPDATE TIME FOR GLDL in CI_BATCH_CNTRL

Set the last update date and time by setting CI_BATCH_CTRL LAST_UPDATE_DTTM to SYSDATE WHERE BATCH_CD = 'GLDL'
Update the NEXT BATCH NUMBER in CI_BATCH_CNTRL

Increment by 1 the NEXT_BATCH_NBR in CI_BATCH_CNTRL where the BATCH_CD is GLDL

Update the NEXT BATCH NUMBER in the CI_BATCH_CNTRL
Increment by 1 the NEXT_BATCH_NBR in CI_BATCH_CNTRL where the BATCH_CD is APDL
Oracle BPEL Process Manager Poll Oracle Enterprise Taxation and Policy Management to Verify Whether A/P Requests are Ready for Extraction
If there are A/P Requests where the CI_ADJ_APREQ PYMNT_SEL_STAT_FLG is N (Not selected for Payment) AND the associated adjustment is in a frozen status
85
Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Release 3.1.1 Implementation Guide Process the A/P Requests that have not been integrated before and mark them all with the next APDL Batch Number Else do nothing.
Sample logic for the extract of Customer and A/P Refund Request from Oracle Enterprise Taxation and Policy Management
Select the following information AP_REQ_ID, GL_ACCT,CHAR_VAL, SA_ID, ADJ_ID, CRE_DT, ADJ_TYPE_CD, CIS_DIVISION, CHAR_VAL, ENTITY_NAME, COUNTRY, ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, NUM1, NUM2, COUNTY, HOUSE_TYPE, STATE, POSTAL, CURRENCY_CD, CURRENCY_PYMNT, GEO_CODE, IN_CITY_LIMIT, PYMNT_METHOD_FLG, ADJ_AMT, SCHEDULED_PAY_DT (see mapping table within this document for more details) FROM CI_ADJ_APREQ, CI_ADJ, CI_SA, CI_ADJ_TYPE, CI_DST_CODE_EFF, CI_DST_CD_CHAR, CI_CIS_DIV_CHAR Where the PYMNT_SEL_STAT_FLG status flag is N (Not Selected for Payment) AND the Adjustment is frozen
Sample logic for Updating CI_ADJ_APREQ Status

UPDATE CI_ADJ_APREQ SET PYMNT_SEL_STAT_FLG to R (Requested for Payment)
Update the NEXT BATCH NUMBER in the CI_BATCH_CNTRL table

Increment by 1 the NEXT_BATCH_NBR in CI_BATCH_CNTRL where the BATCH_CD is APDL

Extract the Payment Information from Oracle E-Business Suite Financials for General Ledger and Accounts Payable
select APA.invoice_id , APA.invoice_num ADJ_ID , APA.invoice_date ,APA.PAYMENT_STATUS_FLAG ,APA.POSTING_STATUS ,APA.CANCELLED_BY ,APA.CANCELLED_DATE ,APA.CANCELLED_AMOUNT ,AIPA.BANK_ACCOUNT_NUM ,AIPA.REVERSAL_FLAG ,AIPA.REVERSAL_INV_PMT_ID ,ACA.CHECK_DATE payment_date ,ACA.CHECK_NUMBER payment_number ,ACA.STATUS_LOOKUP_CODE ,ACA.VOID_DATE ,ACA.STOPPED_BY , ACA.STOPPED_DATE , APA.PAYMENT_REASON_COMMENTS AP_REQ_ID , ACA.CHECK_ID ,ACA.amount , ACA.released_date FROM ap_invoices_all APA ,AP_INVOICE_PAYMENTs_all AIPA ,ap_checks_all ACA WHERE APA.invoice_id = AIPA.invoice_id AND AIPA.check_id = ACA.check_id AND APA.source = ETM
86
Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Release 3.1.1 Implementation Guide AND (APA.CANCELLED_DATE >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run OR APA.CREATION_DATE >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run OR ACA.stopped_date >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run OR ACA.released_date >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run OR ACA.void_date >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run ) ORDER BY APA.CREATION_DATE ASC
For each payment selected above, check if this payment is already applied in Oracle Enterprise Taxation and Policy Management.
If AP_INVOICES_ALL.CANCELLED_DATE IS NOT Null and AP_INVOICES_ALL. PAYMENT_STATUS_FLAG<>Y
(Payment is void/ cancelled) If the Payment has been canceled in Oracle E-Business Suite Financials for General Ledger and Accounts Payable, update the CI_ADJ_APREQ PYMNT_SEL_STAT_FLG to X(Canceled) and invoke the service C1AdjustmentMaintenance to cancel the Adjustment corresponding to this payment.
BPEL Process Overview

The following describes the process flows within the BPEL services that form this product.
GL Transaction Integration
The following is the list of processes that comprise the GL Integration between Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger and Accounts Payable: Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors ETMToEBSGLRequestScheduler Polls the INTEGRATION_PROCESS_ACTIVATION table in the Integration Schema at predefined intervals and invokes the ETMToEBSGLBPELProcess. ETMToEBSGLBPELProcess None None None Asynchronous Possible Exceptions - None
87
Process Name Description
ETMToEBSGLBPELProcess Main process of the GL Integration. Gets the GL data from Oracle Enterprise Taxation and Policy Management, transforms it, and inserts it into Oracle E-Business Suite Financials for General Ledger and Accounts Payable GL_INTERFACE Table. Additionally, updates Oracle Enterprise Taxation and Policy Management. Batch Control table with the next batch number. Invokes services for error handling and Email notification. GetETMGLData UpdateETMGLControlTable ErrorhandlingProcess (if an error occurs) MailNotification ETMToEBSGLRequestScheduler None None Asynchronous Possible Exceptions - BPEL Remote Fault, BPEL Binding Fault. GetETMGLData Check if GL data is available in Oracle Enterprise Taxation and Policy Management for transfer. If data is available, it returns a dataset to the calling program. ErrorhandlingProcess (if an error occurs) ETMToEBSGLBPELProcess Input String object contains the Integration Point name invoking this BPEL process. For example: PS, EBS, JDE, etc. SelectETMGLRecordsOutput xml object Synchronous Possible Exceptions BPEL Remote Fault, BPEL Binding Fault UpdateETMGLControlTable Update the next batch number in the GL Batch Control table available in Oracle Enterprise Taxation and Policy Management database. ErrorhandlingProcess (if an error occurs) ETMToEBSGLBPELProcess None None Synchronous Possible Exceptions BPEL Remote Fault, BPEL Binding Fault
Calls to
Calls from Inputs Outputs Synch/Asynch Exceptions/Errors Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors
88
BPEL flow for GL Transaction Integration Point is shown below:
A/P Request Integration

The following is the list processes that comprise the A/P Request Integration between Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger and Accounts Payable: Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors ETMToEBSAPRequestScheduler Polls the INTEGRATION_PROCESS_ACTIVATION table in the Integration Schema at pre-defined intervals and invokes the ETMToEBSAPBPELProcess. ETMToEBSAPBPELProcess None None None Asynchronous Possible Exceptions - None
89
ETMToEBSAPBPELProcess Main process of the AP Integration. Gets the AP Data from Oracle Enterprise Taxation and Policy Management, transforms it, and inserts it into Oracle E-Business Suite Financials for General Ledger and Accounts Payable AP Invoice Interface tables (AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE). Additionally, updates status in two of the Oracle Enterprise Taxation and Policy Management tables. Invokes services for error handling and email notification. GetETMAPData UpdateETMAPControlTable UpdateETMAPAdjReqTable ErrorhandlingProcess (if an error occurs) MailNotification ETMToEBSAPRequestScheduler None None Asynchronous Possible Exceptions BPEL Remote Fault, BPEL Binding Fault. GetETMAPData Checks if AP Data is available in Oracle Enterprise Taxation and Policy Management for transfer. If data is available, it returns a dataset to the calling process. ErrorhandlingProcess (if an error occurs) ETMToEBSAPBPELProcess Input String object containing the Integration Point name invoking this BPEL process. For example: PS, EBS, JDE, etc SelectETMRecordsWithTemplate xml object Synchronous Possible Exceptions - BPEL Remote Fault, BPEL Binding Fault UpdateETMAPControlTable Updates the next batch number in the AP Batch Control table available in the Oracle Enterprise Taxation and Policy Management Database ErrorhandlingProcess (if an error occurs) ETMToEBSAPBPELProcess None None Synchronous Possible Exceptions -
Calls to
Calls from Inputs Outputs Synch/Asynch Exceptions/Errors Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors
90
Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors
UpdateETMAPAdjReqTable Updates PYMNT_SEL_STAT_FLG to R in the Oracle Enterprise Taxation and Policy ManagementAP Adjustment Request table CI_ADJ_APREQ for the provided AP Request ID. None ETMToEBSAPBPELProcess CiAdjApreqCollection xml object None Synchronous Possible Exceptions None
Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors
ETMToEBSAPProcedureCall Process to create/update Supplier and site in Oracle E-Business Suite. Invokes Integration package ETM_EBS_SUPPLIERS_IMPORT_PKG. Invokes services for error handling and E-mail notification. ErrorhandlingProcess (if an error occurs) ETMToEBSAPBPELProcess ETMToEBSAPProcedureCallProcessRequest xml object None Asynchronous Possible Exceptions BPEL Remote Fault, BPEL Binding Fault.
BPEL flow for A/P Request Integration Point is shown below:
91
A/P Data Integration

The following list of processes comprise the A/P Data Integration between Oracle Enterprise Taxation and Policy Management and Oracle E-Business Suite Financials for General Ledger and Accounts Payable . Process Name Description Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors EBSToETMAPDataRequestScheduler Polls the INTEGRATION_PROCESS_ACTIVATION table in the Integration Schema at pre-defined intervals and invokes the EBSToETMAPDataBPELProcess. EBSToETMAPDataBPELProcess ErrorhandlingProcess (if an error occurs) None None None Asynchronous Possible Exceptions None
92
EBSToETMAPDataBPELProcess Main process of the AP Data Integration. Collects all the Oracle E-Business Suite Financials for General Ledger and Accounts Payable payment information from Oracle E-Business Suite Financials for General Ledger and Accounts Payable application tables (AP_INVOICES_ALL, AP_CHECKS_ALL, and AP_INVOICE_PAYMENTS_ALL), transforms the data, and updates the information in the Oracle Enterprise Taxation and Policy Management table application table CI_ADJ_APREQ. ETMCancellationWebService ErrorhandlingProcess (if an error occurs) MailNotification EBSToETMAPDataRequestScheduler None None Asynchronous Possible Exceptions - BPEL Binding fault, BPEL Remote Fault. ETMCancellationWebService This process is a BPEL wrapper to call the Adjustment Maintenance web service in Oracle Enterprise Taxation and Policy Management to cancel the Adjustment ID corresponding to the AP Request ID for the given payment. ErrorhandlingProcess (if an error occurs) EBSToETMAPDataBPELProcess String object - AdjustmentID String result containing APRequest ID for success or error messages Synchronous Possible Exceptions - BPEL Binding Fault, BPEL Remote Fault.
Calls to
Calls from Inputs Outputs Synch/Asynch Exceptions/Errors Process Name Description
Calls to Calls from Inputs Outputs Synch/Asynch Exceptions/Errors
BPEL flow for A/P Data Integration Point is shown below:
93
Shared Integration Processes

These BPEL processes are used across multiple integration points within this product.
Process Name Description Calls to Calls from
ErrorhandlingProcess Invoked only when errors occur. Inserts data into error table INTEGRATION_ERROR_STORE in the Integration Schema. None GetETMGLData UpdateETMGLControlTable ETMToEBSGLBPELProcess GetETMAPData UpdateETMAPControlTable ETMToEBSAPBPELProcess ETMCancellationWebService EBSToETMAPDataBPELProcess
Inputs Outputs
94
ErrorHandlingProcessRequest xml object String result

Process Name Synch/Asynch Exceptions/Errors Process Name Description
ErrorhandlingProcess Synchronous Possible Exceptions - None MailNotification This process is invoked at the end of each batch run. If there was any error generated, it assimilates all these messages into an E-mail and sends the E-mail to configured E-mail address. None ETMToEBSGLBPELProcess ETMToEBSAPBPELProcess EBSToETMAPDataBPELProcess MailNotificationInputParameters xml object None Asynchronous Possible Exceptions - None
Calls to Calls from
Inputs Outputs Synch/Asynch Exceptions/Errors
95

Oracle ETPM-EBS Integration Implementation Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Oracle ETPM-EBS Integration Implementation Guide

Загружено:

Авторское право:

Доступные форматы

Oracle Enterprise Taxation and Policy Management Integration to Oracle E-Business Suite Financials for General Ledger and

Copyright 2000, 2011, Oracle. All rights reserved.

Copyright 2000, 2011, Oracle. All rights reserved.

Part 1: Understanding the Integration

Copyright 2000, 2011, Oracle. All rights reserved.

About the Integration Product

About the Products

Supported Business Processes

Copyright 2000, 2011, Oracle. All rights reserved.

Oracle E-Business Suite

Copyright 2000, 2011, Oracle. All rights reserved.

The flow of data between the two systems is illustrated below:

Copyright 2000, 2011, Oracle. All rights reserved.

GL Process Flow Diagram

Copyright 2000, 2011, Oracle. All rights reserved.

Accounts Payable Request Process Flow Diagram

Copyright 2000, 2011, Oracle. All rights reserved.

Payment Cancellation Process

Copyright 2000, 2011, Oracle. All rights reserved.

Copyright 2000, 2011, Oracle. All rights reserved.

A/P Data Process Flow Diagrams

Copyright 2000, 2011, Oracle. All rights reserved.

One-Time Configuration Settings

General Ledger Integration

Oracle Enterprise Taxation and Policy Management General Ledger Settings

Integration Software General Ledger Settings

Copyright 2000, 2011, Oracle. All rights reserved.

Accounts Receivable Cash Accounts Receivable

Revenue Accounts Receivable Accounts Payable Clearing

Accounts Payable (A/P) Request and A/P Data Integrations

Copyright 2000, 2011, Oracle. All rights reserved.

Oracle Enterprise Taxation and Policy Management A/P Settings

Integration Software A/P Settings

Copyright 2000, 2011, Oracle. All rights reserved.

Accounts Payable Clearing

About the Integration

Copyright 2000, 2011, Oracle. All rights reserved.

Integration Process General Ledger AP Request AP Data

Source System ETM ETM EBS

Target System EBS EBS ETM

Process Journal Import Payables Open Interface Import

Invoke Application Web Service Response

Integration Point Process Flow

Read Application Data

Read/Write Write Email Notification Process Flow

Error Handling Process Flow Import Procedure

High Level Architecture Diagram

Copyright 2000, 2011, Oracle. All rights reserved.

As part of another database as determined by your specific technical needs.

Copyright 2000, 2011, Oracle. All rights reserved.

Part 2: Implementing the Integration Product

Setting Up the Process Integration

Copyright 2000, 2011, Oracle. All rights reserved.

Configuration Check List

Ledger Id Journal Source Journal Category Organization ID

Copyright 2000, 2011, Oracle. All rights reserved.

Information Invoice Source

Oracle Enterprise Taxation and Policy Management Configuration

Link the characteristic type created in step B3 with the Division

Copyright 2000, 2011, Oracle. All rights reserved.

Integration Product Configuration

PROCESS_NAME START_PROCESS (Y/N) ETM_EBS_GL ETM_EBS_AP EBS_ETM_APDATA Y Y Y

NEXT_RUN_INTERVAL (System Use) 0 0 0

Copyright 2000, 2011, Oracle. All rights reserved.