Home

Sun SeeBeyond eWay(TM) Oracle Applications Adapter User`s Guide

Contents

1. Util_Name CDATA IMPLIED lt Error handling definition gt lt ELEMENT Error_Handle Error_Table Error_PKG gt lt relative path to the sql script for creating error table gt lt ELEMENT Error_Table PCDATA gt relative path to the sql script for error handling gt lt ELEMENT Error PKG PCDATA gt lt relative path to the sql script that needs to be compiled in order for other stored procedure to be compiled successfully gt 45 Naming Conventions Oracle Interface Name The specific name for the Open Interface which is specified in the XML file Oracle Applications eWay Intelligent Adapter User s Guide 52 Sun Microsystems Inc Section 4 5 Chapter 4 Naming Conventions Pre Validation Process Short Table Name The name used for the generated utility stored procedures for each interface table It is derived from the corresponding Oracle Interface Table name as follows If the Oracle Interface Table name is longer than 23 characters replace INTERFACE or IFACE ALL with INT to form the short table name Since there is a limitation of 30 characters placed on the function stored procedure name in Oracle the Open Interface name specified in the XML file must be no more than 23 characters Stored Procedures The utility stored procedure names are derived from the Short Table name according to the following convention Sb XXX
2. Name Description Required Value PortNumber Specifies the I O port number on which A valid port number The the server is listening for connection default is 1521 requests User Specifies the user name that the eWay Any valid string uses to connect to the database Password Specifies the password used to access the Any valid string database DriverProperties Use the JDBC driver that is shipped with this eWay Often times the DataSource implementation needs to execute additional methods to assure a connection You must identify the additional methods in the Driver Properties Any valid delimiter Valid delimiters are lt method name 1 gt lt param 1 gt lt param 2 gt lt param n gt lt method name 2 gt lt param 1 gt lt param 2 gt lt param n gt HH For example to execute the method setURL give the method a String for the URL setURL lt url gt Delimiter This is the delimiter character to be used The default is in the DriverProperties prompt TNSEntry Specifies the TNS name for the Oracle A valid TNS name if using the instance specified in TNSNAMES ORA If OCI driver otherwise do not a TNS name is specified then the OCI enter any value driver is used which further requires installation of the Oracle client If a TNS name is not specified then the thin driver is used MinPoolSize The minimum number of physical A valid numeric valu
3. SB INVTXN 20341 Transaction Interface ID is mandatory and the current value is NULL SB INVTXN 20342 Fm Serial Number is mandatory and the current value is NULL SB INVTXN 20343 Vendor Serial Number is invalid 12 Purchase Order Import Master Table 12 Import Master Errors Error Code Error Message SB POIMP 20001 Header record does not exist for Po Header ID SB POIMP 25006 Header has lines that have failed validation Headers Table 13 Import Header Errors Error Code Error Message SB POIMP 20002 Interface Header ID is mandatory and the current value is NULL Oracle Applications eWay Intelligent Adapter User s Guide 102 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 13 Import Header Errors Error Code Error Message SB POIMP 20003 Action is mandatory and the current value is NULL SB POIMP 20004 Document Type Code is mandatory and the current value is NULL SB POIMP 20006 Vendor Site Code is mandatory and the current value is NULL SB POIMP 20007 Vendor Doc Num is mandatory and the current value is NULL SB POIMP 20008 Action is mandatory and the current value is invalid SB POIMP 20009 Document Type Code is mandatory and the current value is invalid SB POIMP 20010 Vendor ID is invalid SB POIMP 20011 From Type Lookup Code
4. SB INVTXN 20301 Source Code is mandatory and the current value is NULL SB INVTXN 20302 Source Line ID is mandatory and the current value is NULL SB INVTXN 20303 SB INVTXN 20304 Source Header ID is mandatory and the current value is NULL Process Flag is mandatory and the current value is NULL SB INVTXN 20305 Transaction Mode is mandatory and the current value is NULL SB INVTXN 20306 Transaction Interface ID is mandatory and the current value is NULL SB INVTXN 20307 Inventory Item ID is mandatory and the current value is NULL SB INVTXN 20308 Organization ID is mandatory and the current value is NULL SB INVTXN 20309 Transaction Quantity is mandatory and the current value is NULL SB INVTXN 20310 Transaction UOM is mandatory and the current value is NULL SB INVTXN 20311 Transaction Date is mandatory and the current value is NULL SB INVTXN 20312 Transaction Source ID is mandatory and the current value is NULL SB INVTXN 20313 Transaction Source Name is mandatory and the current value is NULL SB INVTXN 20314 Transaction Type ID is mandatory and the current value is NULL SB INVTXN 20319 SB INVTXN 20320 Distribution Account ID is invalid Inventory Item ID is invalid SB INVTXN 20321 Organization ID is invalid SB INVTXN 20322 Acct Period ID is invalid SB INVTXN 20323 Schedule ID is invalid SB I
5. Appendix A Error Codes Provides a description of error codes returned by the validation scripts 142 Scope This document describes the process of installing configuring and running the Oracle Application eWay This document does not cover the Java methods exposed by this Oracle Applications eWay Intelligent Adapter User s Guide 13 Sun Microsystems Inc Chapter 1 Section 1 5 Introducing the Oracle Applications eWay Related Documents eWay For information on the Java methods download and view the Oracle Applications eWay Javadoc files from the Enterprise Manager 143 Intended Audience This guide is intended for experienced computer users who have the responsibility of helping to set up and maintain a fully functioning CAPS system This person must also understand any operating systems on which CAPS is to be installed Windows or UNIX and must be thoroughly familiar with Windows style GUI operations 144 Text Conventions The following conventions are observed throughout this document Table 1 Text Conventions Text Convention Used For Examples Bold Names of buttons files icons Click OK parameters variables methods On the File menu click Exit menus and objects Select the eGate sar file Monospaced Command line arguments code java jar filename jar samples variables are shown in bold italic Blue bold Hypertext links within See Text Conventions on page 14 document
6. SB POREC 20186 There must be a valid Destination Type Code when Auto Transact Code is DELIVER SB POREC 20187 Invalid Expected Receipt Date SB POREC 20188 Transaction Status Code must be ERROR or COMPLETED SB POREC 20191 Invalid Item Category SB POREC 20192 Invalid Location Code SB POREC 20193 Invalid Vendor Name SB POREC 20194 Invalid Vendor Num Requisitions Table 18 Requisition Errors Error Code Error Message SB POREQ 20100 Interface_Source_Code is mandatory and the current value is NULL SB POREQ 20101 Destination_Type_Code is mandatory and the current value is NULL SB POREQ 20102 Authorization_Status is mandatory and the current value is NULL SB POREQ 20103 Quantity is mandatory and the current value is NULL SB POREQ 20104 Preparer_ID and Preparer_Name values are NULL Either one must have a value SB POREQ 20105 Charge Account ID and Charge Account Segment1 values are NULL Either one must have a value SB POREQ 20106 Destination Organization ID and Destination Organization Code values are NULL Either one must have a value SB POREQ 20107 Deliver To Location ID and Deliver To Location Code values are NULL Either one must have a value SB POREQ 20108 Deliver To Requestor ID and Deliver To Requestor Name values are NULL Either one must have a value SB POREQ 20109 If Curre
7. S Repository fg Environment G orcl_Apps_JCE PR Orcl Apps BPEL Oracle Apps IntegrationSvr1 Filein SBJmslQMgri E FileouT LogicalHostt EN IntegrationSvr1 SBJmslOMgr1 Project Explorer Environment Explorer _OrclApps_JCE OrclApps_Fin_JCE 655 Create the Deployment Profile To create the Deployment Profile In the Project Explorer create a new Deployment Profile as shown in Create the Deployment Profile on page 74 and configure the components similar to those shown in Figures 22 through 27 skipping figure 26 since there is only one outbound file eWay 65 6 Configure the Oracle Apps External System In the Environment Explorer configure the Oracle Apps BPEL external system the same way it is configured in Configure the Oracle Apps External System on page 76 66 Using the Financial GL Budget BPEL Sample The Financial GL Budget BPEL sample project uses an eInsight business process to exchange data with the Oracle Applications system Oracle Applications eWay Intelligent Adapter User s Guide 88 Sun Microsystems Inc Chapter 6 Section 6 6 Implementing the Sample Projects Using the Financial GL Budget BPEL Sample fe eaFileln Note Figure37 The Financial GL Budget BPEL Sample no ERP gt E Oracleapps1 Libo La File to JMS1 Topic1 BudgetGL BP1 eaFileOut 25 2 JMS to File1 For the validation process Financial B
8. SB INVITM 21342 Price Tolerance Percent is less than Zero SB INVITM 21343 Shelf Life Days is less than Zero SB INVITM 21344 Repetitive Planning Flag is invalid SB INVITM 21345 Acceptable Rate Decrease is less than Zero SB INVITM 21346 Acceptable Rate Increase is less than Zero SB INVITM 21347 Assembly Pegging Flag is invalid SB INVITM 21348 Postprocessing Lead Time is less than Zero SB INVITM 21349 Vendor Warranty Flag is invalid SB INVITM 21350 Serviceable Component Flag is invalid SB INVITM 21351 Serviceable Product Flag is invalid Oracle Applications eWay Intelligent Adapter User s Guide 97 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table4 Item Errors Error Code Error Message SB INVITM 21352 Preventive Maintenance Flag is invalid SB INVITM 21353 Ship Model Complete Flag is invalid SB INVITM 21354 Prorate Service Flag is invalid SB INVITM 21355 Invoiceable Item Flag is invalid SB INVITM 21356 Invoice Enabled Flag is invalid SB INVITM 21357 Must Use Approved Vendor Flag is invalid SB INVITM 21358 Outside Operation Flag is invalid SB INVITM 21359 Costing Enabled Flag is invalid SB INVITM 21360 Cycle Count Enabled Flag is invalid SB INVITM 21361 Auto Created Config Flag is invalid SB INVITM 21362 SB I
9. SB AR LINES 10661 CUST_TRX_TYPE_NAME value should match with NAME value of RA_BATCH_SOURCES_ALL Table SB AR LINES 10662 FOB_POINT value should match with LOOKUP_CODE value of AR_LOOKUPS Table where LOOKUP_TYPE is FOB SB AR LINES 10663 INVENTORY_ITEM_ID value should match with INVENTORY_ITEM_ID value of MTL_SYSTEM_ITEMS Table Oracle Applications eWay Intelligent Adapter User s Guide 116 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 20 Auto Invoice Errors Error Code Error Message SB AR LINES 10664 MEMO LINE ID value should match with MEMO LINE ID value of AR MEMO LINES ALL B Table SB AR LINES 10665 MEMO LINE NAME value should match with NAME value of AR MEMO LINES ALL B Table SB AR LINES 10666 Enter the appropriate value in ORIG SYSTEM BILL ADDRESS ID SB AR LINES 10667 Enter the appropriate value in ORIG SYSTEM BILL ADDRESS REF SB AR LINES 10668 Enter the appropriate value in ORIG_SYSTEM_BILL_CONTACT_ID SB AR LINES 10669 Enter the appropriate value in ORIG SYSTEM BILL CONTACT REF SB AR LINES 10670 ORIG SYSTEM BILL CUSTOMER ID value should match with CUST ACCOUNT ID value of HZ CUST ACCOUNTS Table SB AR LINES 10671 ORIG SYSTEM BILL CUSTOMER REF value should match with ORIG SYSTEM REFERENCE value of HZ CUST ACCOUNTS Table SB AR LINES 10672 Enter the appropriate value i
10. STANDARD TERM NAME does not exist IN TABLE RA TERMS SB AR PROFILE 10142 STATEMENT CYCLE NAME does not exist IN TABLE AR STATEMENT CYCLES SB AR PROFILE 10143 STATEMENT CYCLE NAME must be NULL WHEN STATEMENTS IS No OR NULL Mandatory WHEN STATEMENTS IS Yes SB AR PROFILE 10144 TAX PRINTING OPTION does not exist IN TABLE AR LOOKUPS SB AR PROFILE 10145 CLEARING DAYS must be greater than OR equal TO zero SB AR PROFILE 10146 PAYMENT GRACE DAYS must be greater than OR equal TO zero SB AR PROFILE 10147 TOLERANCE must be BETWEEN 100 AND 100 SB AR PROFILE 10148 ID does not exist IN VIEW HR ORGANIZATION UNITS V 23 Cash Management Table 23 Cash Management Errors Error Code Error Message SB CE STHDR 30100 STATEMENT NUMBER is a required column Enter a valid value SB CE STHDR 30101 BANK ACCOUNT NUM is a required column Enter a valid value SB CE STHDR 30102 STATEMENT DATE is a required column Enter a valid value SB CE STHDR 30103 CURRENCY CODE is a required column Enter a valid value SB CE STHDR 30107 CURRENCY CODE should be the same as the currency code defined for the bank account in AP Banks Accounts All table SB CE STHDR 30108 CURRENCY CODE does not exist IN TABLE FND CURRENCIES SB CE STHDR 30109 CONTROL END BALANCE should be equal to CONTROL BEGIN BALANCE CONTROL TOTAL DR CONTROL TOTAL C
11. ORGANIZATION ID is mandatory and the current value is NULL SB INVCCE 23303 ACTION CODE is mandatory and the current value is NULL SB INVCCE 23304 EMPLOYEE ID is mandatory and the current value is NULL SB INVCCE 23310 ADJUSTMENT ACCOUNT ID is invalid SB INVCCE 23311 CYCLE COUNT ENTRY 10 is invalid SB INVCCE 23312 CYCLE COUNT HEADER ID is invalid SB INVCCE 23313 LOCATOR ID is invalid SB INVCCE 23314 REVISION is invalid SB INVCCE 23315 LOT NUMBER is invalid SB INVCCE 23316 SB INVCCE 23317 SB INVCCE 23318 ORGANIZATION ID is invalid SUBINVENTORY is invalid SERIAL NUMBER is invalid Oracle Applications eWay Intelligent Adapter User s Guide 95 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table3 Cycle Count Entry Errors Error Code Error Message SB INVCCE 23319 INVENTORY ITEM ID is invalid SB INVCCE 23320 TRANSACTION REASON ID is invalid SB INVCCE 23321 COUNT UNIT OF MEASURE is invalid SB INVCCE 23322 COUNT UOMi is invalid SB INVCCE 23330 EMPLOYEE ID value is not valid SB INVCCE 23331 PROJECT ID value is not valid SB INVCCE 23332 TASK ID value is not valid SB INVCCE 23333 VALID FLAG value is not valid SB INVCCE 23334 DELETE FLAG value is not valid SB INVCCE 23335 LOCK FLAG value is not valid SB INVCCE 23336
12. This property is used in conjunction with the property ConnectionRetries An integer indicating the configured length of the time in milliseconds before each reattempt to access the destination file The configured default is 1000 1 second 332 Outbound Oracle eWay Properties with XA support The Outbound Oracle Applications eWay properties with XA support accessed from the Environment Explorer tree are organized into the following sections JDBC Connector Settings with XA support on page 32 Connection Retry Settings with XA support on page 33 JDBC Connector Settings with XA support The JDBC Connector Settings section of the Outbound XA Oracle Applications Environment contains the top level parameters displayed in Table 7 Table7 Outbound XA eWay Environment JDBC Connector Settings Name Description Required Value Description Enter a description for the database A valid string ServerName Specifies the host name of the external Any valid string database server PortNumber Specifies the I O port number on which A valid port number The the server is listening for connection default is 1521 requests DatabaseName Specifies the name of the database Any valid string instance used on the Server User Specifies the user name that the eWay Any valid string uses to connect to the database Password Specifies the password used to access the Any valid string database Oracl
13. all times 0 zero indicates that there are no physical connections in the pool and new connections are created as needed default is 2 MaxPoolSize MaxldleTime The maximum number of physical connections the pool keeps available at all times 0 zero indicates that there is no maximum The maximum number of seconds that a physical connection may remain unused before it is closed 0 zero indicates that there is no limit A valid numeric value The default is 10 A valid numeric value Connection Retry Settings with XA support The Connection Retry Settings section of the Outbound XA Oracle Applications Environment contains the top level parameters displayed in Table 8 Table8 Outbound XA eWay Environment Connection Retry Settings Name Description Required Value ConnectionRetries Specifies the number of retries to establish a connection with the Oracle database upon a failure to acquire one Oracle Applications eWay Intelligent Adapter User s Guide 33 An integer indicating the number of attempts allowed to establish a connection The configured default is 0 Sun Microsystems Inc Chapter 3 Section 3 3 Configuring the Oracle Applications eWay Oracle Applications eWay Environment Configuration Properties Table8 Outbound XA eWay Environment Connection Retry Settings Name Description Required Value ConnectionRetry Specifies the configured length of the An integer
14. in the event of a connection failure Connectivity Map Generator Generates and links your Project s Connectivity Map components using a Collaboration or Business Process Many of these features are documented further in the Sun SeeBeyond eGate Integrator User s Guide or the Sun SeeBeyond eGate Integrator System Administrator Guide 14 About This Document This guide explains how to install configure and operate the Sun Java Composite Application Platform Suite Oracle Applications eWay Adapter referred to as the Oracle Applications eWay throughout this guide 141 What s in This Document This document includes the following chapters Chapter 1 Introducing the Oracle Applications eWay Provides an overview description of the product as well as high level information about this document Chapter 2 Installing the Oracle Applications Describes the system requirements and provides instructions for installing the Oracle Applications eWay Chapter 3 Configuring the Oracle Applications eWay Provides instructions for configuring the eWay to communicate with your legacy systems Chapter 4 Pre Validation Process Provides an overview of the pre validation process used by the Oracle Applications eWay Chapter 5 Using the OTD Wizard Provides information about sag files and using the Oracle wizard Chapter 6 Implementing the Sample Projects Provides instructions for installing and running the sample Projects
15. 22500 Set process ID is mandatory and the current value is NULL SB INVREV 22501 Inventory Item ID is mandatory and the current value is NULL SB INVREV 22502 Organization ID is mandatory and the current value is NULL SB INVREV 22503 Revision is mandatory and the current value is NULL SB INVREV 22504 Change Notice is invalid SB INVREV 22505 Organization id is invalid SB INVREV 22506 Inventory item id is invalid SB INVREV 22507 Primary key is invalid SB INVREV 22508 Process flag is invalid SB INVREV 22509 Item Number is invalid Replenishment Master Table 6 Replenishment Master Errors Error Code Error Message SB INVREP 22430 Header has lines that have failed validation Headers Table7 Replenishment Header Errors Error Code Error Message SB INVREP 22301 Replenishment Header ID is mandatory and the current value is NULL SB INVREP 22302 Replenishment Count Name is mandatory and the current value is NULL SB INVREP 22303 Count Date is mandatory and the current value is NULL SB INVREP 22304 Last Update Date is mandatory and the current value is NULL SB INVREP 22305 Creation Date is mandatory and the current value is NULL SB INVREP 22306 Created By is mandatory and the current value is NULL SB INVREP 22307 Last Updated By is mandatory and the current value is NULL SB INVREP 22308 Organization ID is mandatory and the current value is NULL SB INVREP 22309 SubInventory C
16. CODE does NOT exist IN AP INCOME TAX TYPES TABLE AND should be active 22 Accounts Receivable Auto Invoice Table 20 Auto Invoice Errors Error Code Error Message SB AR DIST 10400 ACCOUNT CLASS cannot be NULL SB AR DIST 10401 CODE COMBINATION ID does not exists in GL CODE COMBINATIONS table SB AR DIST 10402 ACCOUNT CLASS should be either REV FREIGHT TAX REC CHARGES UNBILL UNEARN SB AR LINES 10600 CONVERSION TYPE is a required column Enter a valid value SB AR LINES 10601 BATCH SOURCE NAME is a required column Enter a valid value Oracle Applications eWay Intelligent Adapter User s Guide 115 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 20 Auto Invoice Errors Error Code Error Message SB AR LINES 10602 SET OF BOOXRKS ID is a required column Enter a valid value SB AR LINES 10603 LINE TYPE is a required column Enter a valid value SB AR LINES 10604 DESCRIPTION is a required column Enter a valid value SB AR LINES 10605 CURRENCY_CODE is a required column Enter a valid value SB AR LINES 10606 LAST_UPDATED_BY is a required column Enter a valid value SB AR LINES 10607 LAST_UPDATE_DATE is a required column Enter a valid value SB AR LINES 10608 CREATED_BY is a required column Enter a valid value SB AR LINES 10609 CREATION_DATE is a req
17. Categories Locations Mass Additions General Ledger Budget Daily Rates Journal 121 Oracle Applications eWay Basic Operation Section 1 2 About the Oracle Applications eWay When a message for Oracle Applications is triggered in JCE or BPEL it proceeds as follows 1 Itinserts the data into a staging table contained within the Oracle database following the OTD corresponding to the current Open Interface Table For more information on the staging table refer to Staging Table Node on page 60 2 It pre validates the data in the staging table by invoking stored procedures also contained in the Oracle database The eWay checks for and manages any errors after which the validated rows are placed into the Interface Table 3 Itthen initiates a standard Oracle validation by involving the Oracle Concurrent Manager which validates the data in the Open Interface Table and stores the validated rows in the Oracle Applications Database Oracle Applications eWay Intelligent Adapter User s Guide 11 Sun Microsystems Inc Chapter 1 Section 1 3 Introducing the Oracle Applications eWay What s New in This Release This simplified procedure is depicted in Figure 2 A more detailed description including the handling of data failing validation is contained in Exchanging Data with Oracle Applications on page 67 Figure 2 CAPS to Oracle Applications Operation Oracle Applications E 0 0 0 Staging Stored Or
18. Code Error Message SB INVITM 21317 Purchasing Enabled Flag is invalid SB INVITM 21318 Customer Order Enabled Flag is invalid SB INVITM 21319 Internal Order Enabled Flag is invalid SB INVITM 21320 So Transactions Flag is invalid SB INVITM 21321 Mtl Transactions Enabled Flag is invalid SB INVITM 21322 Stock Enabled Flag is invalid SB INVITM 21323 Bom Enabled Flag is invalid SB INVITM 21324 Build In Wip Flag is invalid SB INVITM 21325 Allow Item Desc Update Flag is invalid SB INVITM 21326 Receipt_Required_Flag is invalid SB INVITM 21327 SB INVITM 21328 Rfq Required Flag is invalid Planning Time Fence Daysis less than Zero SB INVITM 21329 Pick Components Flag is invalid SB INVITM 21330 Replenish To Order Flag is invalid SB INVITM 21331 ATP Components Flag is invalid SB INVITM 21332 Cost Of Sales Account is invalid SB INVITM 21333 Sales Account is invalid SB INVITM 21334 Encumbrance Account is invalid SB INVITM 21335 Expense Account is invalid SB INVITM 21336 List Price Per Unit is less than Zero SB INVITM 21337 Taxable Flag is invalid SB INVITM 21338 Expense Billable Flag is invalid SB INVITM 21339 Time Billable Flag is invalid SB INVITM 21340 Service Duration is invalid SB INVITM 21341 Market Price is less than Zero
19. DATE is a required column Enter a valid value SB AR PAY 10304 LAST UPDATED BY is a required column Enter a valid value SB AR PAY 10305 LAST UPDATE DATE is a required column Enter a valid value SB AR PAY 10306 CREATION DATE is a required column Enter a valid value SB AR PAY 10307 CREATED BY is a required column Enter a valid value SB AR PAY 10315 Valid values for PRIMARY FLAG column are Y N SB AR PAY 10316 Valid values for VALIDATED FLAG column Y N SB AR PAY 10317 PAYMENT METHOD NAME does not exist in table AR RECEIPT METHODS SB AR PAY 10318 ORIG SYSTEM CUSTOMER REF does not exist in table RA CUSTOMERS and SB RA CUSTOMERS INTERFACE SB AR PAY 10319 ORIG SYSTEM ADDRESS REF does not exist in table RA ADDRESSES and SB RA CUSTOMERS INTERFACE SB AR PAY 10320 ORG ID does not exist IN VIEW HR ORGANIZATION UNITS V SB AR BANKS 10200 ORIG SYSTEM CUSTOMER REF cannot be NULL SB AR BANKS 10201 BANK ACCOUNT NAME cannot be NULL SB AR BANKS 10202 PRIMARY FLAG cannot be NULL SB AR BANKS 10203 START DATE cannot be NULL SB AR BANKS 10204 LAST UPDATE DATE cannot be NULL SB AR BANKS 10205 LAST UPDATED BY cannot be NULL SB AR BANKS 10206 CREATION DATE cannot be NULL SB AR BANKS 10207 SB AR BANKS 10208 SB AR BANKS 10209 CREATED BY cannot be NULL BANK ACCOUNT CURRENCY CODE cannot
20. INTERFACE 40206 DATE CREATED cannot be NULL SB GL INTERFACE 40207 CREATED BY cannot be NULL SB GL INTERFACE 40208 ACTUAL FLAG cannot be NULL Oracle Applications eWay Intelligent Adapter User s Guide 129 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table25 General Ledger Errors Error Code Error Message SB GL INTERFACE 40209 SET OF BOOKS ID does not exists in GL SETS OF BOOKS Table SB GL INTERFACE 40210 CURRENCY CODE does not exists in CURRENCIES Table SB GL INTERFACE 40211 FUNCTIONAL CURRENCY CODE does not exists in FND CURRENCIES table SB GL INTERFACE 40212 BUDGET VERSION ID does not exists in GL BUDGET VERSIONS table SB GL INTERFACE 40213 JE BATCH ID does not exists in GL JE BATCHES table SB GL INTERFACE 40214 ENCUMBRANCE TYPE ID does not exists in GL ENCUMBRANCE TYPES table SB GL INTERFACE 40215 JE HEADER ID does not exists in GL JE HEADRS table SB GL INTERFACE 40216 JE LINE NUM does not exists in GL JE LINES table SB GL INTERFACE 40217 CODE COMBINATION ID does not exists in GL CODE COMBINATIONS table SB GL INTERFACE 40218 ORIGINATING BAL SEG VALUE does not exists in FND FLEX VALUES table SB GL INTERFACE 40219 USER CURRENCY CONVERSION TYPE does not exists in GL DAILY CONVERSION TYPES table SB GL INTERFACE 40220 USER JE CATEGORY NAME does n
21. Migration Procedures on page 19 Installing Enterprise Manager eWay Plug Ins on page 22 21 Before You Install Open and review the Readme txt for the Oracle Applications eWay for any additional information or requirements prior to installation The Readme txt is located on the installation CD ROM 22 Installing the Oracle Applications eWay The Enterprise Manager a web based application is used to select and upload eWays and add on files during the installation process The following section describes how to install the components required for this eWay Refer to the readme for the latest information on Supported Operating Systems System Requirements External System Requirements Note When the Repository is running on a UNIX operating system the eWays are loaded from the Enterprise Manager running on a Windows platform connected to the Repository server using Internet Explorer Oracle Applications eWay Intelligent Adapter 16 Sun Microsystems Inc Chapter 2 Section 2 2 Installing the Oracle Applications Installing the Oracle Applications eWay 221 Installing the Oracle Applications eWay on an eGate Supported System After you have installed Core Products do the following 1 From the Sun Java Composite Application Platform Suite Installer click on the Click to install additional products link on the Administration tab 2 Expand the eWay option 3 From Select Sun Java Composite Application Platform Suite Products
22. SB INVCCE 23337 PROCESS FLAG value is not valid PROCESS MODE value is not valid SB INVCCE 23338 STATUS FLAG value is not valid Items Table4 Item Errors Error Code Error Message SB INVITM 21301 Organization_Code or Organization_ID is mandatory and the current value is NULL SB INVITM 21302 item Number or Segments 1 to 20 is mandatory and the current value is NULL SB INVITM 21303 Process_Flag is mandatory and the current value is NULL SB INVITM 21304 Transaction_Type is mandatory and the current value is NULL SB INVITM 21305 Set_Process_ID is mandatory and the current value is NULL SB INVITM 21306 Summary_Flag is invalid SB INVITM 21307 Enabled_Flag is invalid SB INVITM 21308 Purchasing ltem Flag is invalid SB INVITM 21309 Shippable Item Flag is invalid SB INVITM 21310 Customer Order Flag is invalid SB INVITM 21311 Internal Order Flag is invalid SB INVITM 21312 Service Item Flag is invalid SB INVITM 21313 Service Starting Delay is less than Zero SB INVITM 21314 Inventory Item Flag is invalid SB INVITM 21315 Eng ltem Flag is invalid SB INVITM 21316 Inventory Asset Flag is invalid Oracle Applications eWay Intelligent Adapter User s Guide 96 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table4 Item Errors Error
23. Sample Data on page 80 3 Configure each of the three file eWays as described in Configure the File eWays on page 80 4 Create an Environment for the Project as described in Create the Environment on page 80 5 Create and configure the Deployment Profile as described in Create the Deployment Profile on page 81 6 Configure the Oracleapps1 eWay the eWay that exchanges the data with the Oracle Applications as described in Configure the Oracle Apps BPEL External System on page 81 641 Import the Order Import BPEL Sample The process of importing the sample files for this Project is the same as that of the previous sample The name of the Project file to import is Oracle Applications eWay Intelligent Adapter User s Guide 80 Sun Microsystems Inc Chapter 6 Section 6 4 Implementing the Sample Projects Using the Order Import BPEL Sample prjOraApp Man f Order Import BP Sample zip Look for this file in the location where you downloaded the sample files in step 4 of procedure on page 71 For example C CAPS_Samples OraApps BPEL A message may appear warning you that you do not have the Oracle Applications eWay installed This warning is not critical for this sample Project 642 Set up the Sample Data Use Windows Explorer to extract the input files input files zip to a convenient location for example CNCAPS SamplesNOraAppsNBPEL input files Also create directory for the output files for example C CAPS_
24. Source Doc Unit Of Measure SB POREC 20170 FK Validation Invalid Shipment Header ID SB POREC 20171 FK Validation Invalid Shipment Line ID SB POREC 20172 FK Validation Invalid Primary Unit Of Measure SB POREC 20173 Value required in any one of Item Category or Category ID or Document Line Num or Po Line ID field in rcv transactions interface SB POREC 20174 Transaction Type must be SHIP or RECEIVE SB POREC 20175 Processing Status Code must be PENDINC SB POREC 20176 Processing Mode Code must be BATCH SB POREC 20177 Auto Transact Code must be RECEIVE or DELIVER or SHIP SB POREC 20178 Receipt Source Code must be VENDOR SB POREC 20179 Source Document Code must be PO SB POREC 20180 Header Interface ID value not found in rcv headers interface SB POREC 20181 Validation Flag must be Y or N SB POREC 20182 Employee ID cannot be null when Transaction Type is DELIVER SB POREC 20183 Valid Group ID not found in rcv headers interface SB POREC 20184 Invalid Ship To Location Code or Ship To Location ID when ASN TYPE is ASN SB POREC 20185 To Organization Code and To Organization ID both cannot be null Oracle Applications eWay Intelligent Adapter User s Guide 109 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 17 Receiving Transaction Errors Error Code Error Message
25. UPDATE DATE cannot be NULL SB FA MASS 50014 LAST UPDATE LOGIN cannot be NULL SB FA MASS 50015 LAST UPDATED BY cannot be NULL SB FA MASS 50016 LOCATIOD ID cannot be NULL SB FA MASS 50017 MASS ADDITION ID cannot be NULL SB FA MASS 50018 PAYABLES CODE COMBINATION ID cannot be NULL SB FA MASS 50019 PAYABLES COST cannot be NULL SB FA MASS 50020 PAYABLES UNITS cannot be NULL SB FA MASS 50021 POSTING STATUS cannot be NULL SB FA MASS 50022 QUEUE NAME cannot be NULL SB FA MASS 50023 AP DISTRIBUTION LINE NUMBER does not exists in AP INVOICE DISTRIBUTIONS ALL table SB FA MASS 50024 ASSIGNED TO does not exists in FA EMPLOYEES table SB FA MASS 50025 INVOICE ID does not exists in AP INVOICES ALL table SB FA MASS 50026 ADD TO ASSET ID does not exists in FA ADDITIONS B table Oracle Applications eWay Intelligent Adapter User s Guide 127 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 24 Fixed Assets Errors Error Code Error Message SB FA MASS 50027 ASSET NUMBER does not exists in FA ADDITIONS B SB FA MASS 50028 PARENT ASSET ID does not exists ADDITIONS B SB FA MASS 50029 ASSET KEY CCID does not exists in FA ASSET KEYWORDS SB FA MASS 50030 BOOK TYPE CODE does not exists FA BOOK CONTROLS SB FA MASS 50031 ASSET CATE
26. a complete set of transactions and reports for maintaining accounts payable control Accounts Payable Oracle Interface Tables Oracle provides the following Interface Table for Requisitions ap invoices interface ap invoice lines interface Oracle Applications eWay Intelligent Adapter User s Guide 42 Sun Microsystems Inc Chapter 4 Section 4 3 Pre Validation Process Financial Module SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb ap invoices interface sb ap invoice lines interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate ap inv pkg sql sb validate ap inv lines pkg sql These files are controlled by the following master validation file sb validate payable pkg sql 432 Accounts Receivable Module The Oracle Accounts Receivable module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining accounts receivable control Auto Invoice Oracle Interface Tables Oracle provides the following Interface Table for Requisitions ra interface distributions ra interface lines all ra interface salescredits all SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table li
27. at the OTD root level the data is counted from all Staging Tables If it is located at the Staging Table level the data is counted only for that specific Staging Table Parameters Depends upon specific implementation Typically it contains at least four input VARCHAR parameters corresponding to sb eway id sb group id sb object id Note Ifyou do not assign a value including the null value to the above parameters the procedure acts on all associated records sb pass or fail This parameter accepts the following values P records that have passed for records that have failed I all records Requirements The stored procedure name is derived from the Open Interface name or the Staging Table name according to the following convention Atthe root level If the OPEN INTERFACE tab has a Util Name attribute then this value is used FN UTILNAME Otherwise the value of the attribute Name is used FN Open Interface Name For example Customer Item CNT CUSTITEMS Item Import FN CNT ITEM IMPORT At the staging table level If the Interface Table tag has a Util Name attribute then this value is used FN UTILNAME Otherwise the short name of the Name attribute is used FN CNT Short Table Name For example Customer Item FN CNT MTL CI INTERFACE INT Item Import EN CNT MTL SYSTEM ITEMS INT Oracle Applications eWay Intelligent Adapter User s Guide 6
28. be NULL BANK ACCOUNT NUM cannot be NULL Oracle Applications eWay Intelligent Adapter User s Guide 121 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 22 Customer Interface Errors Error Code Error Message SB AR BANKS 10210 BANK BRANCH NAME cannot be NULL SB AR BANKS 10211 ORIG SYSTEM ADDRESS REF cannot be NULL if the bank details are entered Also it should be equal to BILL TO address SB AR BANKS 10212 BANK ACCOUNT CURRENCY CODE does not exist in FND CURRENCIES table SB AR BANKS 10213 BANK ACCOUNT NAME does not exist in AP BANK ACCOUNTS table SB AR BANKS 10214 BANK NUMBER does not exist in AP BANK BRANCHES table SB AR BANKS 10215 BANK NUM should be unique in AP BANK BRANCHES table SB AR BANKS 10216 BANK BRANCH COUNTRY does not exist in FND TERRITORIES table SB AR BANKS 10217 END DATE should be greater than START DATE SB AR BANKS 10218 ORIG SYSTEM CUSTOMER REF does not exist in HZ CUST ACCOUNTS table SB AR BANKS 10219 PRIMARY FLAG should be either Y or N SB AR BANKS 10220 BANK NAME BANK BRANCH NAME should be unique in AP BANK BRANCHES table SB AR BANKS 10221 BANK NAME cannot be NULL SB AR BANKS 10222 ORIG SYSTEM ADDRESS REF does not exist in HZ CUST ACCT SITES ALL or SB RA CUSTOMERS INTERFACE table The address specified must have an active BILL TO site define
29. by different users TidyUp Updates sb pass or fail columns in the staging table from INTERMEDIATE to PASS for records that were not marked as failed by the pre validation rules Validate The main validation procedure which calls the procedures that perform the pre validations for the Interface Table Oracle Applications eWay Intelligent Adapter User s Guide 36 Sun Microsystems Inc Chapter 4 Section 4 2 Pre Validation Process Manufacturing Module 42 Manufacturing Module The Manufacturing module is divided into the following sub modules Inventory Module on page 37 Purchase Order Import Module on page 40 Order Entry Module on page 41 Each submodule uses at least one corresponding set of tables and scripts as depicted in Figure 7 on page 36 421 Inventory Module The Oracle Inventory module works with other Oracle Manufacturing modules to provide a complete set of transactions and reports for maintaining inventory control Customer Items Oracle Interface Table Oracle provides the following Interface Table for Customer Items mtl ci interface SeeBeyond Staging Table The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Tables listed above sb mtl ci interface Pre Validation Script The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following file sb validate cust items pkg sgl Customer It
30. components used by your ICAN 5 0 Projects 8 Start the Sun Java Composite Application Platform Suite 5 1 2 Enterprise Designer Import the Project 9 From the Sun Java Composite Application Platform Suite 5 1 2 Enterprise Designer s Project Explorer tree right click the Repository and select Import Project from the shortcut menu The Import Manager appears 10 Browse to and select your exported Project file 11 Click Import warning message Missing APIs from Target Repository may appear at this time This occurs because various product APIs were installed on the ICAN 5 0 Repository when the Project was created that are not installed on the Sun Oracle Applications eWay Intelligent Adapter 19 Sun Microsystems Inc Chapter 2 Section 2 5 Installing the Oracle Applications ICAN 5 0 Project Migration Procedures Java Composite Application Platform Suite 5 1 2 Repository These APIs may or may not apply to your Projects You can ignore this message if you have already installed all of the components that correspond to your Projects Click Continue to resume the Project import 12 Close the Import Manager after the Project is successfully imported Deploy the Project 13 Anew Deployment Profile must be created for each of your imported Projects When a Project is exported the Project s components are automatically checked in to Version Control to write protected each component These protected components appear in the Explorer tree w
31. connect to the Oracle server Oracle Applications eWay Intelligent Adapter User s Guide 56 Sun Microsystems Inc Chapter 5 Using the OTD Wizard Figure 10 Connect to Database Select Wizard Type Connect to Database Select Oracle Applications module Specify the OTD Name Review Selections 4 Select the Business Function and Module and choose whether to use fully qualified Specify Database Connection Information Please enter the Oracle Applications database connection information below Connection Information Host name Port ID 1521 SID User name Password Back Next Finish Cancel names to replace existing stored procedures Table 11 Select Oracle Applications module Module Information Description Business Function Currently Financial and Manufacturing are the only supported business functions Module function are Auto Invoice Auto Lock Bank Statement Budget Customers Daily Rates Fixed Assets Categories Fixed Assets Mass Additions Journal Payable The available modules in the Manufacturing business function are Customer Item Customer Item Cross Reference Cycle Count Entries tem Import tem Transactions Order Requisition Order Import Order Receiving Replenishment Oracle Applications eWay Intelligent Adapter User s
32. fa locations Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate loc pkg sql These files are controlled by the following master validation file sb validate fa locations pkg sql Oracle Applications eWay Intelligent Adapter User s Guide 46 Sun Microsystems Inc Chapter 4 Section 4 3 Pre Validation Process Financial Module Mass Additions Oracle Interface Tables Oracle provides the following Interface Table for Requisitions fa mass additions SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb fa mass additions Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate additions pkg sql These files are controlled by the following master validation file sb validate fa mass add pkg sql 435 General Ledger Module The Oracle General Ledger module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining general ledger control Budget Oracle Interface Tables Oracle provides the following Interface Table for Requisitions gl budget interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interfa
33. for instructions on importing the sample Project into your repository via the Enterprise Designer 25 ICAN 5 0 Project Migration Procedures This section describes how to transfer your current ICAN 5 0 Projects to the Sun Java Composite Application Platform Suite 5 1 2 To migrate your ICAN 5 0 Projects to the Sun Java Composite Application Platform Suite 5 1 2 do the following Export the Project 1 Before you export your Projects save your current ICAN 5 0 Projects to your Repository 2 From the Project Explorer right click your Project and select Export from the shortcut menu The Export Manager appears 3 Select the Project that you want to export in the left pane of the Export Manager and move it to the Selected Projects field by clicking the Add to Select Items arrow button or click to include all of your Projects 4 Inthesame manner select the Environment that you want to export in the left pane of the Export Manager and move it to the Selected Environments field by clicking the Add to Select Items arrow button or click All to include all of your Environments 5 Browse to select a destination for your Project ZIP file and enter a name for your Project in the ZIP file field 6 Click Export to create the Project ZIP file in the selected destination Install Sun Java Composite Application Platform Suite 5 1 2 7 Install the Sun Java Composite Application Platform Suite 5 1 2 including all eWays libraries and other
34. have failed I all records Requirements The stored procedure name is derived from the Open Interface name or the Staging Table name according to the following convention At the root level Oracle Applications eWay Intelligent Adapter User s Guide 63 Sun Microsystems Inc Chapter 5 Section 5 3 Using the OTD Wizard Exposed OTD Nodes If the OPEN INTERFACE tab has a Util Name attribute then this value is used SP MOV UTILNAME Otherwise the value of the attribute Name is used SP MOV Open Interface Name For example Customer Item SP MOV CUSTITEMS Item Import SP MOV ITEM IMPORT At the staging table level If the Interface Table tag has a Util Name attribute then this value is used SP MOV UTILNAME Otherwise the short name of the Name attribute is used SP MOV Short Table Name For example Customer Item SP MOV MTL CI INTERFACE INT Item Import SP MOV MTL SYSTEM ITEMS INT 536 REQUEST Description Concurrent Manager request function This function is used to submit the concurrent management request to Oracle Applications Parameters Depends upon specific implementation Requirements The function name is derived from the Open Interface name specified in the SML and has the form FN REQUEST ORACLE INTERFACE NAME 537 REQUEST STATUS Description Function used to retrieve the status of the Concurrent Manager request Parameters INp request id IN NUMBER Request Id for the co
35. in Oracle release 11i It provides added value to the Oracle suite by allowing pre validation of data before it is uploaded to the Oracle database and providing the ability to handle error conditions These are important features since data containing even the slightest error causes a transmission to fail at runtime What s in This Chapter About Oracle Applications on page 8 About the Oracle Applications eWay on page 10 What s New in This Release on page 12 About This Document on page 13 Related Documents on page 14 Sun Microsystems Inc Web Site on page 14 Documentation Feedback on page 15 11 About Oracle Applications The Oracle E Business Suite 11i is a comprehensive enterprise resource planning ERP software package built upon Oracle s database technology It is presented within an Internet environment using online transaction processing to address the global requirements of today s typical enterprise The E Business suite includes a large number of Product Families grouped into software modules corresponding to what were once stand alone computer systems used by individual departments These Product Families are identified by their major business functions such as Financials Human Resources Oracle Applications eWay Intelligent Adapter User s Guide 8 Sun Microsystems Inc Section 1 1 Chapter 1 Introducing the Oracle Applications eWay About Oracle Applications Manufacturin
36. in RCV HEADERS INTERFACE must be VENDOR SB POREC 20110 Transaction Type field in RCV HEADERS INTERFACE must be NEW or CANCEL SB POREC 20111 Validation Flag field in RCV HEADERS INTERFACE must be Y or SB POREC 20112 Auto Transact Code field in HEADERS INTERFACE must be SHIP or RECEIVE or DELIVER SB POREC 20113 Receipt Num cannot be NULL when Auto Transact Code is SHIP SB POREC 20114 Shipped Date cannot be NULL when Asn Type is ASN or ASBN SB POREC 20115 Invoice Num cannot be NULL when Asn Type is ASBN SB POREC 20116 Invoice Date cannot be NULL when Asn Type is ASBN SB POREC 20117 Total Invoice Amount cannot be NULL or negative when Asn Type is ASBN SB POREC 20118 Both Employee ID and Employee Name cannot be null when Auto Transact Code is RECEIVE SB POREC 20119 Invalid Vendor Name SB POREC20189 Shipped Date cannot be earlier than SYSDATE or EXPECTED RECEIPT DATE SB POREC20190 Invalid Employee name Transactions Table 17 Receiving Transaction Errors Error Code Error Message SB POREC 20120 Interface Transaction ID field is mandatory in rcv transactions interface table and current value is null SB POREC 20121 Group ID field is mandatory in rcv transactions interface table and current value is null SB POREC 20122 Transaction Type field is mandatory in rcv transactions interface ta
37. indicating the Interval pause before each reattempt to access configured length of the time the destination file This property is used in conjunction with the property ConnectionRetries in milliseconds before each reattempt to access the destination file The configured default is 1000 1 second Oracle Applications eWay Intelligent Adapter User s Guide 34 Sun Microsystems Inc Chapter 4 Pre Validation Process This chapter provides an overview of the pre validation process used by the Oracle Applications eWay You can modify the pre validation scripts as required to match your business rules Brief descriptions of the error codes returned by the scripts are found in Appendix A Error Codes on page 93 Note The Sun SeeBeyond Oracle Application scripts provided are intended to be used as a template or skeleton You may need to modify these scripts to satisfy your own environment or requirements These scripts have been tested successfully in the Sun SeeBeyond environment See the Oracle Applications eWay Readme for more information What s in This Chapter Overview on page 35 Manufacturing Module on page 37 Financial Module on page 42 Building a Custom Pre Validation Package on page 49 Naming Conventions on page 52 41 Overview Each of the Oracle Applications modules is divided into submodules each representing a logical division of workflow Each submodule uses at least one corre
38. r10 table SB POREQ 20144 Rate Type is invalid FK validation failed against gl daily conversion types table SB POREQ 20145 Approver ID is invalid FK validation failed against hr employees table SB POREQ 20146 Autosource Doc Header ID is invalid FK validation failed against po autosource documents all table SB POREQ 20147 Project ID is invalid FK validation failed against pa projects all table SB POREQ 20148 Task ID is invalid FK validation failed against pa tasks table SB POREQ 20149 Note2 ID is invalid FK validation failed against po notes table SB POREQ 20150 Note3 ID is invalid FK validation failed against po notes table SB POREQ 20151 Note4 ID is invalid FK validation failed against po notes table SB POREQ 20152 Note5 ID is invalid FK validation failed against po notes table SB POREQ 20153 Note6 ID is invalid FK validation failed against po notes table SB POREQ 20154 SB POREQ 20155 Note7 ID is invalid FK validation failed against po notes table Note8 ID is invalid FK validation failed against po notes table SB POREQ 20156 Note9 ID is invalid FK validation failed against po notes table SB POREQ 20157 Note10 ID is invalid FK validation failed against po notes table SB POREQ 20158 Expenditure Type is invalid FK validation failed against pa expenditure types table SB POREQ 20159 Document Type Code is invalid FK
39. should match with TERRITORY ID value of RA TERRITORIES Table SB AR LINES 10701 TRX NUMBER value should not match with NUMBER value of RA CUSTOMER TRX ALL Table SB AR LINES 10702 UOM CODE value should match with UOM CODE value of MTL UNITS OF MEASURE Table SB AR LINES 10703 NAME value should match with UNIT OF MEASURE value of MTL UNITS OF MEASURE Table SB AR LINES 10705 AMOUNT value should be NULL when LINE TYPE CHARGES SB AR LINES 10706 AMOUNT INCLUDES TAX FLAG should be either Y or N SB AR LINES 10707 GL DATE must be OPEN or FUTURE ENTRY accounting period in GL PERIOD STATUSES SB AR LINES 10708 INVOICING RULE ID value should exist in RULE ID column of RA RULES Table SB AR LINES 10709 CUSTOMER BANK ACCOUNT ID value should exist in BANK ACCOUNT ID column of AP BANK ACCOUNTS ALL Table SB AR LINES 10710 CUSTOMER BANK ACCOUNT value should exist in BANK ACCOUNT NAME column of AP BANK ACCOUNTS ALL Table SB AR SALES 10500 INTERFACE SALESCREDIT ID cannot be NULL SB AR SALES 10530 SALES CREDIT AMOUNT SPLIT AND SALES CREDIT PERCENT SPLIT cannot be Null Not Null SB AR SALES 10531 SB AR SALES 10532 SALES CREDIT AMOUNT SPLIT cannot be Null and Should be between 0 and 100 SALES CREDIT TYPE ID cannot be Null and does not exist in SO SALES CREDIT TYPES Table Oracle Applications eWay Intelligent Adapter User s
40. the following constants Connection TRANSACTION_ READ UNCOMMITTED Connection TRANSACTION READ COMMITTED Connection TRANSACTION REPEATABLE READ Connection TRANSACTION SERIALIZABLE Connection TRANSACTION N ONE For information on Managing and Monitoring alert codes and logs see the Sun SeeBeyond eGate Integrator System Administration Guide Oracle Applications eWay Intelligent Adapter 24 Sun Microsystems Inc Chapter 3 Configuring the Oracle Applications eWay The Oracle Applications eWay contains a unique set of properties that are configurable from the Project s Connectivity Map during design time When you connect an external application such as an eWay with a Service on the Connectivity Map Enterprise Designer automatically assigns the eWay to the link allowing modification of exposed properties The Oracle Applications eWay includes two outbound modes one for XA transactions and one for non XA transactions The properties for each of these modes are configured in the Connectivity Map as well as the Environment Explorer The Outbound Oracle Applications XA eWay manages XA transactions up to the point where the Interface Table is populated with data When the Concurrent Manager is invoked the transaction has already passed to Oracle Applications and is no longer under the control of the eWay What s in This Chapter Creating and Configuring the Oracle Applications eW
41. this method before entering the loop Add a Commit method after inserting all the records If you are using a while loop add this method after exiting the loop Add a Try Catch Block The Try Block contains your current JCD code Add The rollback method to the Catch Block This method rolls back any changes that might have taken place prior to the failure Rebuild the Project JCD Sample Code new code in BOLD Oracle Applications eWay Intelligent Adapter public class jcdAutoCommitManual publ publ publ public public input logger Logger logger alerter Alerter alerter com stc codegen util CollaborationContext collabContext com stc codegen util TypeConverter typeConverter void receive com stc connector appconn file FileTextMessag uniqueTable UniqueTableOTD UniqueTable 1 throws Throwable Stc stc ic ic ic com com codegen codegen try UniqueTable 1 setAutoCommit false UniqueTable 1 getTEST insert UniqueTable 1 getTEST setFIRSTNAME Rex UniqueTable 1 getTEST setLASTNAME Chani UniqueTable 1 getTEST insertRow UniqueTable 1 getTEST setFIRSTNAME Rex UniqueTable 1 getTEST setLASTNAME Chan2 UniqueTable 1 getTEST insertRow UniqueTable 1 getTEST setFIRSTNAME Rex UniqueTable 1 getTEST setLASTNAME Chani UniqueTable 1 getTEST insertRow UniqueTable 1 com
42. to Install select the products for your Sun Java Composite Application Platform Suite and include the following FileeWay the File eWay is used by most sample Projects Oracle ApplicationseWay eInsight must be installed to use BPEL functionality 4 Once you have selected all of your products click Next in the top right or bottom right corner of the Select Sun Java Composite Application Platform Suite Products to Install box 5 Fromthe Selecting Files to Install box locate and select your first product s SAR file Once you have selected the SAR file click Next Follow this procedure for each of your products The Installing Files window appears after the last SAR file has been selected 6 From the Installing Files window review the product list If it is correct Click Install Products The Enterprise Manager starts the installation 7 When your product s installation is completed click on the prompt When installation completes click here to continue To upload the Sun SeeBeyond eWay Adapter for Oracle Applications User s Guide Help file Javadoc Readme and sample Projects do the following A Expand the Documentation option B Select Oracle ApplicationseWayDocs C Click Next in the top right or bottom right corner of the Select Sun Java Composite Application Platform Suite Products to Install box Adding the eWay to an Existing Sun Java Composite Application Platform Suite Installation It is possible to ad
43. to be run against the table Figure 8 Oracle Applications OTD Wizard Stored Validation Procedures Oracle ier Information Interface Oracle lt i Database Staging Table Graphical Interface Table Converter Structure Oracle Applications OTD Collaboration Rule Oracle Applications OTD Wizard Oracle Applications eWay Intelligent Adapter User s Guide 54 Sun Microsystems Inc Chapter 5 Section 5 2 Using the OTD Wizard Creating OTDs When building an OTD the wizard calls many JDBC APIs for example getProcedureColumns which in turn queries the database and returns the resultset It is the Oracle driver that translates the API into multiple queries The eWay itself doesn t issue the queries directly In a situation where there is a lot of data in the database it may take a while to return all the resultsets to the wizard The performance of the queries is dependent on the execution path which is formulated when a SQL call is prepared Not having good stats in the data dictionary could produce a long running query Oracle recommends doing the following to gather vital stats to improve performance 1 Setthe following in either the init ora file or spfile whichever is appropriate for their install table lookup prefetch size 0 2 Analyze the SYS schema for the system as follows A Start sqlplus B Connect as sys user C exec dbms stats gather schema stats SYS 3 Keep in mind that sig
44. 1 Sun Microsystems Inc Chapter 5 Section 5 3 Using the OTD Wizard Exposed OTD Nodes 533 DELETE Description Stored procedures for both OTD level and interface level are defined in the utility package If it is located at the OTD root level the data from all Staging Tables is deleted If it is located at the Staging Table level only the data for that specific Staging Table is deleted Parameters Depends upon the specific implementation Typically it contains at least four input VARCHAR parameters corresponding to sb eway id sb group id sb object id Note Ifyou do not assign a value including the null value to the above parameters the procedure acts on all associated records sb pass or fail This parameter accepts the following values P records that have passed for records that have failed I all records Requirements The stored procedure name is derived from the Open Interface name or the Staging Table name according to the following conventions Atthe root level If the OPEN INTERFACE tab has a Util Name attribute then this value is used SP DEL UTILNAME Otherwise the value of the attribute Name is used SP DEL Open Interface Name For example Customer Item SP DEL CUSTITEMS Item Import SP DEL ITEM IMPORT At the staging table level If the Interface Table tag has a Util Name attribute then this value is used SP DEL UTILNAME Otherwise the short name of t
45. 10 Vendor Doc Num already exists Oracle Applications eWay Intelligent Adapter User s Guide 103 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 13 Import Header Errors Error Code Error Message SB POIMP 25011 Release Date is reserved for future use and must be NULL SB POIMP 25012 Document Num must have a unique value Current value already exists SB POIMP 25013 There must be at least one line per header document SB POIMP 25014 Fob Active is invalid SB POIMP 25015 Freight Terms Active is invalid SB POIMP 25016 Document Sub Type is invalid SB POIMP 25017 Num Of Lines is invalid Lines Table 14 Import Line Errors Error Code Error Message SB POIMP 20034 SB POIMP 20035 Interface Header ID is mandatory and the current value is NULL Interface Line ID is mandatory and the current value is NULL SB POIMP 20036 Organization ID is mandatory and the current value is NULL SB POIMP 20037 Po Header ID not found for modification SB POIMP 20038 Category ID is invalid SB POIMP 20039 Line Type ID is invalid SB POIMP 20040 Un Number ID is invalid SB POIMP 20041 Hazard Class ID is invalid SB POIMP 20042 Ussgl Transaction Code is invalid SB POIMP 20043 Closed By is invalid SB POIMP 20044 From Header ID is invalid SB POIMP 200
46. 2 Financial Budget GL Table 24 Fixed Assets Errors Error Code Error Message SB FA CATE 50214 SUMMARY FLAG should be either Y or N SB FA LOC 50100 LOCATION ID is a required column Enter a valid value SB FA LOC 50101 SUMMARY FLAG is a required column Enter a valid value SB FA LOC 50102 ENABLED FLAG is a required column Enter a valid value SB FA LOC 50104 LAST UPDATED BY is a required column Enter a valid value SB FA LOC 50105 LAST UPDATE DATE is a required column Enter a valid value SB FA LOC 50110 Valid values for ENABLED FLAG column are Y N SB FA LOC 50111 Valid values for SUMMARY FLAG column are Y N SB FA MASS 50000 ACCOUNTING DATE cannot be NULL SB FA MASS 50001 ASSET CATEGORY ID cannot be NULL SB FA MASS 50002 SB FA MASS 50003 ASSET TYPE cannot be NULL BOOK TYPE CODE cannot be NULL SB FA MASS 50004 CREATED BY cannot be NULL SB FA MASS 50005 CREATED DATE cannot be NULL SB FA MASS 50006 DATE PLACED IN SERVICE cannot be NULL SB FA MASS 50007 DEPRECIATE FLAG cannot be NULL SB FA MASS 50008 DESCRIPTION cannot be NULL SB FA MASS 50009 EXPENSE CODE COMBINATION ID cannot be NULL SB FA MASS 50010 FIXED ASSETS COST cannot be NULL SB FA MASS 50011 FIXED ASSETS UNITS cannot be NULL SB FA MASS 50012 INVENTORIAL cannot be NULL SB FA MASS 50013 LAST
47. 45 From Line ID is invalid SB POIMP 20046 Tax Name is invalid SB POIMP 20047 Item Revision is invalid SB POIMP 20048 Unit Of Measure is invalid SB POIMP 20049 Unit Of Measure is invalid for the Item ID Organization ID SB POIMP 20050 Item ID is invalid SB POIMP 20052 Item is invalid SB POIMP 20054 Uom Code is invalid SB POIMP 20055 Line Type is invalid SB POIMP 20056 Line Num is invalid SB POIMP 20057 Shipment Num is invalid SB POIMP 20058 Un Number is invalid SB POIMP 20059 Hazard Class is invalid Oracle Applications eWay Intelligent Adapter User s Guide 104 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 14 Import Line Errors Error Code Error Message SB POIMP 20060 Ship To Organization Code is invalid SB POIMP 20061 Ship To Location Code is invalid SB POIMP 20062 Template Name is invalid SB POIMP 20063 Payment Terms is invalid SB POIMP 20064 Receiving Routing is invalid SB POIMP 20065 Tax Code ID is invalid SB POIMP 20066 Not To Exceed Price must be NULL since Allow Price Override Flag is N SB POIMP 20067 Not To Exceed Price has to be greater or equal to Unit Price SB POIMP 20068 Max Order Quantity must be greater than Min Order Quantity SB POIMP 20069 Closed Code must be null for QU
48. ALL table SB AR PAYMENT 10818 CUSTOMER BANK ACCOUNT ID does not exists in AP BANK ACCOUNTS ALL table SB AR PAYMENT 10819 CUSTOMER ID does not exists HZ CUST ACCOUNTS table SB AR PAYMENT 10850 RECORD TYPE value should match with RECORD IDENTIFIER value of AR TRANS RECORD FORMATS Table SB AR PAYMENT 10851 TRANSMISSION ID value should match with TRANSMISSION ID value of AR TRANSMISSIONS ALL Table SB AR PAYMENT 10852 CUSTOMER BANK ACCOUNT ID value should match with EXTERNAL BANK ACCOUNT ID value of AP BANK ACCOUNT USES ALL Table SB AR PAYMENT 10853 Valid value for the STATUS field is either NULL or AR RECORD SB AR PAYMENT 10854 ORIGINATION value should match with BANK ORIGINATION NUMBER value of AR LOCKBOXES ALL Table SB AR PAYMENT 10855 EXCHANGE RATE TYPE value should match with LOOKUP CODE value of AR LOOKUPS Table Oracle Applications eWay Intelligent Adapter User s Guide 119 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 21 Auto Lock Box Errors Error Code Error Message SB AR PAYMENT 10856 CUSTOMER BANK NAME value should match with the BANK NAME value of AP BANK BRANCHES table SB AR PAYMENT 10857 REMITTANCE BANK NAME value should match with the BANK NAME value of AP BANK BRANCHES table SB AR PAYMENT 10858 CUSTOMER BANK BRANCH NAME value should match
49. AP INVLIN 20103 AMOUNT is a required column Enter a valid value SB AP INVLIN 20111 INVOICE ID does NOT exist IN TABLE SB AP INVOICES INTERFACE SB AP INVLIN 20112 Valid values for LINE TYPE LOOKUP CODE column are ITEM TAX MISCELLANEOUS FREIGHT SB AP INVLIN 20113 LINE GROUP NUMBER value must be a positive whole number SB AP INVLIN 20114 PO NUMBER does NOT exist IN TABLE PO HEADERS SB AP INVLIN 20115 PO HEADER 10 does NOT exist IN TABLE PO HEADERS SB AP INVLIN 20116 PO LINE ID does NOT exist IN TABLE PO LINES SB AP INVLIN 20117 PO LINE NUMBER does NOT exist IN TABLE PO LINES SB AP INVLIN 20118 PO LINE LOCATION ID does NOT exist IN TABLE PO LINE LOCATIONS SB AP INVLIN 20119 PO SHIPMENT NUM does NOT exist IN TABLE PO LINE LOCATIONS SB AP INVLIN 20120 PO DISTRIBUTION NUM does NOT exist IN TABLE PO DISTRIBUTIONS SB AP INVLIN 20121 PO UNIT OF MEASURE does NOT exist IN TABLE PO DISTRIBUTIONS SB AP INVLIN 20122 INVENTORY ITEM ID does NOT exist IN TABLE MTL SYSTEM ITEMS SB AP INVLIN 20123 ITEM DESCRIPTION does NOT exist IN TABLE PO LINES SB AP INVLIN 20124 QUANTITY INVOICED value must be a positive whole number Oracle Applications eWay Intelligent Adapter User s Guide 114 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 19 Accounts Payable Errors Error Code
50. Adapter User s Guide Sun Microsystems Inc Chapter 1 Section 1 2 Introducing the Oracle Applications eWay About the Oracle Applications eWay Once data is in the Open Interface Table it cannot be withdrawn or corrected Data failing the validation process may be handled in different ways some import scripts update the original rows with error codes while other scripts log errors to a file requiring user intervention Only the default validation rules provided by Oracle are used in the validation process and may not address specific customer requirements There is no easy way to insert batches of data as a transactional unit for example where all inserts from a batch must succeed if any fail then all must fail 12 About the Oracle Applications eWay The Oracle Applications eWay provides a comprehensive integration solution for the Oracle Applications Product Family included in Oracle release 11i It provides added value to the suite by allowing pre validation of data before it is uploaded to the Oracle database as well as providing the ability to handle error conditions These are important features since data which is even slightly erroneous causes a transmission to fail at runtime Oracle contains three types of Open Interfaces API PL SOL View Tables The Oracle Applications eWay provides additional support for Open Interface Tables Additionally the eWay is highly customizable allowing you to modif
51. Blue underlined Hypertext links for Web http www sun com addresses URLs or email addresses 145 Screenshots Depending on what products you have installed and how they are configured the screenshots in this document may differ from what you see on your system 15 Related Documents The following Sun Microsystem documents provide additional information about the CAPS product suite eGate Integrator User s Guide Sun Java Composite Application Platform Suite Installation Guide Oracle Applications eWay Intelligent Adapter User s Guide 14 Sun Microsystems Inc Chapter 1 Section 1 6 Introducing the Oracle Applications eWay Sun Microsystems Inc Web Site 16 Sun Microsystems Inc Web Site The Sun Microsystems web site is your best source for up to the minute product news and technical support information The site s URL is http www sun com 17 Documentation Feedback We appreciate your feedback Please send any comments or suggestions regarding this document to CAPS docsfeedbackGsun com Oracle Applications eWay Intelligent Adapter User s Guide 15 Sun Microsystems Inc Chapter 2 Installing the Oracle Applications This chapter describes how to install the Oracle Applications eWay What s in This Chapter Before You Install on page 16 Installing the Oracle Applications eWay on page 16 After You Install on page 18 Extracting the Sample Projects and Javadocs on page 18 ICAN 5 0 Project
52. Buyer ID is invalid FK validation failed against po agents table SB POREQ 20133 Suggested Vendor ID is invalid FK validation failed against po vendors table SB POREQ 20134 Suggested Vendor Site ID is invalid FK validation failed against po vendor sites all table SB POREQ 20135 Req Distribution ID is invalid FK validation failed against Po Req Distributions All table SB POREQ 20136 Suggested Vendor Contact ID is invalid FK validation failed against Po Vendor Contacts table SB POREQ 20137 Note1 ID is invalid FK validation failed against Po Notes table Oracle Applications eWay Intelligent Adapter User s Guide 111 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 18 Requisition Errors Error Code Error Message SB POREQ 20138 Accrual_Account_ID is invalid FK validation failed against Gl Code Combinations table SB POREQ 20139 Variance_Account_ID is invalid FK validation failed against GI Code Combinations table SB POREQ 20140 Budget Account ID is invalid FK validation failed against Gl Code Combinations table SB POREQ 20141 Ussgl Transaction Code is invalid FK validation failed against gl ussgl transaction codes table SB POREQ 20142 Currency Code is invalid FK validation failed against fnd currencies table SB POREQ 20143 Rate is invalid FK validation failed against gl daily conversion rates
53. Close to close the Import Manager and refresh the repository The prjOraApp Fin BudgetGL JCD Sample appears in the Enterprise Explorer pane of the Enterprise Designer 652 Set up the Sample Data The FileIN external system uses an input file to simulate a transaction to be sent to the Oracle Applications system These files must be extracted from the sample zip files and copied to a location to be used by the input File eWays To set up the sample data 1 In Windows Explorer navigate to the location where you extracted the sample zip files in step 4 of the procedure on page 84 for example C CAPS_Samples OraApps JCD 2 Use WinZip to extract these files to a location where the input file eWay can access them at run time such as C CAPS_Samples OraApps JCD Input_Files Make a note of this location for later use 653 Configure the File eWays To configure the file eWays 1 Before you can configure any of the components in the imported Project you must first check them out of the Repository To check out the Connectivity Map right click CMapl click Check Out and click OK 2 Double click CMap1 to display the Connectivity Map 3 Double click the eWay icon between the eaFileIN external and the File to JMS1 Service to edit the eWay s properties 4 In the Directory field type the location where you extracted the sample input files in step 2 of the previous procedure Oracle Applications eWay Intelligent Adapter User s Guide 86
54. ECTOR NAME does not exist IN TABLE AR COLLECTORS SB AR PROFILE 10131 CREDIT RATING does not exist IN TABLE AR LOOKUPS SB AR PROFILE 10132 DISCOUNT GRACE DAYS Must be greater than OR equal TO 0 AND must be NULL WHEN DISCOUNT TERMS IS NULL OR No SB AR PROFILE 10133 DUNNING LETTER SET NAME does not exist IN TABLE AR DUNNING LETTER SETS SB AR PROFILE 10134 DUNNING LETTER SET NAME mandatory WHEN DUNNING LETTERS IS Yes Must be NULL WHEN DUNNING LETTERS IS No OR NULL SB AR PROFILE 10135 GROUPING RULE NAME does not exist IN TABLE RA GROUPING RULES SB AR PROFILE 10136 INTEREST PERIOD DAYS must be greater than OR equal TO zero mandatory when INTEREST CHARGES value is Y Must be NULL when INTEREST CHARGES value is N OR NULL SB AR PROFILE 10137 ORIG SYSTEM CUSTOMER REF does not exist IN TABLE RA CUSTOMERS AND SB RA CUSTOMERS INTERFACE Oracle Applications eWay Intelligent Adapter User s Guide 124 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 22 Customer Interface Errors Error Code Error Message SB AR PROFILE 10138 ORIG SYSTEM ADDRESS REF does not exist IN TABLE RA ADDRESSES AND SB RA CUSTOMERS INTERFACE SB AR PROFILE 10139 TRX CREDIT LIMIT AND OVERALL CREDIT LIMIT must both be filled IN OR both be NULL SB AR PROFILE 10140 RISK CODE does not exist IN TABLE AR LOOKUPS SB AR PROFILE 10141
55. EP 22407 Last_Updated_By is mandatory and the current value is NULL SB INVREP 22408 Inventory Item ID is mandatory and the current value is NULL SB INVREP 22409 Count Type Code is mandatory and the current value is NULL SB INVREP 22410 Count Quantity is mandatory and the current value is NULL SB INVREP 22411 Count UOM is mandatory and the current value is NULL SB INVREP 22412 Count UOM Code is mandatory and the current value is NULL SB INVREP 22413 Organization ID is invalid SB INVREP 22414 Rep Header 10 is invalid SB INVREP 22415 Inventory Item ID is invalid SB INVREP 22416 Count Uom is invalid SB INVREP 22417 Count Uom Code is invalid SB INVREP 22418 Segment is invalid SB INVREP 22419 Count Type Code is invalid SB INVREP 22420 Organization ID is invalid SB INVREP 22421 Count Type Tracked is invalid SB INVREP 22421 Count Type Tracked23 is invalid SB INVREP 22422 Inventory_item is invalid Oracle Applications eWay Intelligent Adapter User s Guide 100 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table8 Replenishment Line Errors Error Code Error Message SB INVREP 22423 MinMAx Plan is invalid SB INVREP 22424 Count_Uom_Primary is invalid Transactions Table 9 Transaction Errors Error Code Error Message
56. Error Message SB AP INVLIN 20125 SHIP TO LOCATION CODE does NOT exist IN TABLE PO LINE LOCATIONS SB AP INVLIN 20126 DISTRIBUTION SET ID does NOT exist IN TABLE AP DISTRIBUTION SETS SB AP INVLIN 20127 DISTRIBUTION SET NAME does NOT exist IN TABLE AP DISTRIBUTION SETS SB AP INVLIN 20128 DIST CODE CONCATENATED does NOT exist IN TABLE GL CODE COMBINATIONS SB AP INVLIN 20129 AWT GROUP 10 does NOT exist IN TABLE AP AWT GROUPS SB AP INVLIN 20130 AWT GROUP NAME does NOT exist IN TABLE AP AWT GROUPS SB AP INVLIN 20131 PO RELEASE ID does NOT exist IN TABLE PO RELEASES SB AP INVLIN 20132 RELEASE NUM does NOT exist IN TABLE PO RELEASES SB AP INVLIN 20133 SB AP INVLIN 20134 RCV TRANSACTION ID does NOT exist IN TABLE RCV TRANSACTIONS ORG ID does NOT exist IN VIEW HR ORGANIZATION UNITS V SB AP INVLIN 20135 DIST CODE COMBINATION ID does NOT exist IN TABLE GL CODE COMBINATIONS SB AP INVLIN 20136 ACCOUNTING date must be an open accounting period SB AP INVLIN 20138 Valid VALUES FOR PRORATE ACROSS FLAG are YN SB AP INVLIN 20139 INCOME TAX REGION does NOT exist IN AP INCOME TAX TYPES TA BLE AND should be active SB AP INVLIN 20140 PO DISTRIBUTION ID does NOT exist IN TABLE PO DISTRIBUTIONS SB AP INVLIN 20141 I YPE 1099 does NOT exist IN AP INCOME TAX TYPES TABLE AND should be active SB AP INVLIN 20142 TAX
57. GORY ID does not exists in FA CATEGORIES B SB FA MASS 50032 LOCATION ID does not exists in FA LOCATIONS SB FA MASS 50033 PARENT MASS ADDITION ID does not exists in FA MASS ADDITIONS SB FA MASS 50034 PAYABLES CODE COMBINATION ID does not exists in GL CODE COMBINATIONS SB FA MASS 50035 EXPENSE CODE COMBINATION ID does not exists in GL CODE COMBINATIONS SB FA MASS 50036 PROJECT ID does not exists in PA PROJECTS ALL SB FA MASS 50037 PROJECT ASSET LINE ID does not exists in PA PROJECT ASSET LINES ALL SB FA MASS 50038 TASK ID does not exists in PA TASKS SB FA MASS 50039 PO VENDOR ID does not exists in PO VENDORS SB FA MASS 50040 ASSET TYPE should be either CAPITALIZED CIP EXPENSED SB FA MASS 50041 DEPRECIATE FLAG should be either YES or NO SB FA MASS 50042 PAYABLES UNITS should have same value as that of FIXED ASSETS UNITS column SB FA MASS 50043 POSTING STATUS should be either NEW ON HOLD POST SB FA MASS 50044 QUEUE NAME should have same value as that of POSTING STATUS SB FA MASS 50045 INVENTORIAL should be either YES or NO SB FA MASS 50046 NEW MASTER FLAG should be either YES or NO SB FA MASS 50047 SHORT FISCAL YEAR FLAG should be either YES or NO SB FA MASS 50048 CONVERSION DATE should not be NULL when SHORT FISCAL YEAR FLAG is YES A25 General Ledger Table 25 General Ledger Er
58. Guide 57 Sun Microsystems Inc Creating OTDs The available modules in the Financial business Chapter 5 Section 5 2 Using the OTD Wizard Creating OTDs Table 11 Select Oracle Applications module Continued Module Information Description Use fully qualified names in Specifies whether the generated Java code uses the Java code fully qualified names Replace Existing Stored Specifies to replace any existing stored Procedures procedures or stop the wizard if any stored procedures exist You must select this option in order to continue with the wizard Take care to back up any stored procedures you have modified before continuing with this wizard Figure 11 Select Oracle Applications module Select Oracle Applications module Select Wizard Type Connectto Database Select Oracle Applications module Specify the OTD Name Which of the following Oracle Application module would you like to use to build your OTD Business Function Financial 7 Review Selections Module Auto Invoice 7 Use fully qualified names in the generated Java code Replace Existing Stored Procedures Connection established Host oracle11i 1523 SID VIS lt Back Next Finish Cancel Help Important A set of stored procedures are installed with the Oracle Applications eWay Unless these stored procedures are somehow deleted the only way to create the OTD
59. Guide 118 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 20 Auto Invoice Errors Error Code Error Message SB AR SALES 10533 SALES CREDIT TYPE NAME cannot be Null and SALES CREDIT TYPE NAME does not exist in SO SALES CREDIT TYPES Table SB AR SALES 10534 SALESREP ID cannot be Null and SALESREP ID does not exist in RA SALESREPS SB AR SALES 10535 SALESREP NUMBER does not exist in RA SALESREPS Auto Lock Box Table 21 Auto Lock Box Errors Error Code Error Message SB AR PAYMENT 10800 RECORD TYPE is a required column Enter a valid value SB AR PAYMENT 10801 SB AR PAYMENT 10802 ORIGINATION is a required column for record type as RECEIPT Enter a valid value BATCH NAME is a required column for record type as RECEIPT Enter a valid value SB AR PAYMENT 10803 GL DATE is a required column for record type as RECEIPT Enter a valid value SB AR PAYMENT 10804 REMITTANCE AMOUNT is a required column for record type as RECEIPT Enter a valid value SB AR PAYMENT 10805 RECEIPT METHOD 10 is a required column for record type as RECEIPT Enter a valid value SB AR PAYMENT 10815 TRANSMISSION ID does not exists in AR TRANSMISSIONS ALL table SB AR PAYMENT 10816 SB AR PAYMENT 10817 RECEIPT METHOD ID does not exists in AR RECEIPT METHODS table CUSTOMER SITE USE ID does not exists in HZ CUST SITE USES
60. HODS Table SB AR LINES 10686 SB AR LINES 10687 RECEIPT METHOD NAME value should match with NAME value of AR RECEIPT METHODS Table Enter the appropriate value in REFERENCE LINE CONTEXT Oracle Applications eWay Intelligent Adapter User s Guide 117 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 20 Auto Invoice Errors Error Code Error Message SB AR LINES 10688 REFERENCE_LINE_ID value should match with CUSTOMER_TRX_LINE_ID value of RA CUSTOMER TRX LINES Table SB AR LINES 10689 Enter the appropriate value in RELATED_BATCH_SOURCE_NAME SB AR LINES 10690 RELATED_CUSTOMER_TRX_ID value should match with CUSTOMER TRX ID value of RA CUSTOMER TRX ALL Table SB AR LINES 10692 Enter the appropriate value in RELATED TRX NUMBER SB AR LINES 10694 TAX CODE value should match with TAX CODE value of AR VAT TAX Table SB AR LINES 10695 Enter the appropriate value in TAX_EXEMPT_FLAG SB AR LINES 10696 TAX_EXEMPT_REASON_CODE value should match with LOOKUP_CODE value of AR LOOKUPS Table SB AR LINES 10697 TAX EXEMPT REASON CODE MEANING value should match with MEANING value of AR LOOKUPS Table SB AR LINES 10698 TERM ID value should match with TERM ID value of RA TERMS Table SB AR LINES 10699 TERM NAME value should match with NAME value of RA TERMS Table SB AR LINES 10700 TERRITORY ID value
61. NVITM 21363 Container Item Flag is invalid Vehicle Item Flag is invalid SB INVITM 21364 Check Org ID Code is invalid SB INVITM 21365 Wip Supply Type is invalid SB INVITM 21366 Lot Control Code is invalid SB INVITM 21367 Shelf Life Code is invalid SB INVITM 21368 Serial Number Control Code is invalid SB INVITM 21369 Restrict Subinventories Code is invalid SB INVITM 21370 Restrict Locators Code is invalid SB INVITM 21371 Planning Time Fence Code is invalid SB INVITM 21372 Bom Item Type is invalid SB INVITM 21373 Allowed Units Lookup Code is invalid SB INVITM 21374 Inventory Planning Code is invalid SB INVITM 21375 Planning Make Buy Code is invalid SB INVITM 21376 Mrp Safety Stock Code is invalid SB INVITM 21377 Material Billable Flag is invalid SB INVITM 21378 Reservable_Type is invalid SB INVITM 21379 Return_Inspection_Requirement is invalid SB INVITM 21380 Mrp_Planning_Code is invalid SB INVITM 21381 Location_Control_Code is invalid SB INVITM 21382 ITEM DESCRIPTION FIELD CANNOT BE NULL Oracle Applications eWay Intelligent Adapter User s Guide 98 Sun Microsystems Inc Appendix A Section A 1 Error Codes Manufacturing Item Revisions Table5 Item Revision Errors Error Code Error Message SB INVREV
62. NVTXN 20324 Operation Seq Num is invalid SB INVTXN 20325 Transportation Account is invalid SB INVTXN 20326 Locator ID is invalid SB INVTXN 20327 Transfer Organization is invalid SB INVTXN 20328 Transfer Locator is invalid SB INVTXN 20329 Revision is invalid SB INVTXN 20330 SubInventory Code is invalid SB INVTXN 20331 SB INVTXN 20332 SB INVTXN 20333 Transfer SubInventory is invalid Schedule Number is invalid Reason ID is invalid Oracle Applications eWay Intelligent Adapter User s Guide 101 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table9 Transaction Errors Error Code Error Message SB INVTXN 20334 Wip Entity Type is invalid SB INVTXN 20335 Substitution Type ID is invalid SB INVTXN 20344 Transaction Header ID is invalid Lots Table 10 Transaction Lots Errors Error Code Error Message SB INVTXN 20336 Transaction Interface ID is mandatory and the current value is NULL SB INVTXN 20337 Lot Number is mandatory and the current value is NULL SB INVTXN 20338 Transaction Quantity is mandatory and the current value is NULL SB INVTXN 20339 Transaction Temp ID is invalid SB INVTXN 20340 Serial Numbers Transaction Interface ID is invalid Table 11 Transaction Serial Number Errors Error Code Error Message
63. OTATION Document Type SB POIMP 20070 SB POIMP 20071 Committed Amount must be null for QUOTATION Document Type Market Price must be null for QUOTATION Document Type SB POIMP 20072 Allow Price Override Flag must be null for QUOTATION Document Type SB POIMP 20073 Not To Exceed Price must be null for QUOTATION Document Type SB POIMP 20074 Negotiated By Preparer Flag must be null for QUOTATION Document Type SB POIMP 20075 Capital Expense Flag must be null for QUOTATION Document Type SB POIMP 20076 Min Release Amount for QUOTATION BLANKET Document Type SB POIMP 20077 Min Order Quantity is less than 0 SB POIMP 20078 Max Order Quantity is less than 0 SB POIMP 20079 Over Tolerance Error Flag must be either Y or N SB POIMP 20080 Qty Rcv Tolerance must be NULL for BLANKET Document Type SB POIMP 20081 Qty Rcv Exception Code must be NULL for BLANKET Document Type SB POIMP 20082 Freight Carrier must be NULL for BLANKET Document Type SB POIMP 20083 Fob must be NULL for BLANKET Document Type SB POIMP 20084 Freight Terms must be NULL for BLANKET Document Type SB POIMP 20085 Receipt Required Flag must be NULL for BLANKET Document Type SB POIMP 20086 Inspection Required Flag must be NULL for BLANKET Document Type SB POIMP 20087 Unit Price must not be NULL or 0 SB POIMP 20088 Release Num is reserved for future us
64. Purchase Order Receiving Oracle Interface Tables Oracle provides the following Interface Tables for Receiving rcv headers interface rcv transactions interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging tables corresponding to the Oracle Open Interface Tables listed above sb rcv headers interface Oracle Applications eWay Intelligent Adapter User s Guide 40 Sun Microsystems Inc Chapter 4 Section 4 2 Pre Validation Process Manufacturing Module sb rcv transactions interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate rcv hdr pkg sql sb validate rcv trans pkg sql These files are controlled by the following master validation file sb validate rcv pkg sql Purchase Order Requisitions Oracle Interface Table Oracle provides the following Interface Table for Requisitions po requisitions interface all SeeBeyond Staging Table The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb po requisitions interface a Pre Validation Script The scripts corresponding to the SeeBeyond Staging Table listed above are packaged within the following file sb validate por req pkg sql 423 Order Entry Module The Oracle Order Entry module works with other Oracle Manufacturing modules to provide a compl
65. R SB CE STHDR 30110 Valid values for RECORD STATUS FLAG column E N SB CE STHDR 30111 BANK ACCOUNT NUM does not exist IN TABLE AP Banks Accounts All SB CE STHDR 30112 BANK NAME does not exist IN TABLE AP Bank Branches SB CE STHDR 30113 BANK BRANCH NAME does not exist IN TABLE AP Bank Branches SB CE STHDR 30114 CHECK DIGITS does not match with check digits of the bank account number entered IN TABLE AP Banks Accounts All SB CE STHDR 30115 ORG ID does not exist IN view HR ORGANIZATION UNITS V SB CE STATE 30200 Bank Account Num cannot be NULL Oracle Applications eWay Intelligent Adapter User s Guide 125 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 23 Cash Management Errors Error Code Error Message SB CE STATE 30201 Statement Number cannot be NULL SB CE STATE 30202 Line number cannot be NULL SB CE STATE 30203 TRX DATE cannot be NULL SB CE STATE 30204 Amount cannot be NULL SB CE STATE 30205 TRX CODE cannot be NULL SB CE STATE 30210 Bank Account Num does not exists in SB CE STATEMENT HEAD INTERFACE SB CE STATE 30211 Statement Number does not exists in SB CE STATEMENT HEAD INTERFACE SB CE STATE 30212 Currency code does not exist in FND CURRENCIES SB CE STATE 30220 TRX code does not exist CE TRANSACTION CODES
66. REIGHT table SB AR CUST 10032 LANGUAGE does not exists in LANGUAGES table SB AR CUST 10033 CUST TAX CODE value should match with TAX CODE value of AR VAT TAX Table SB AR CUST 10034 SITE USE TAX CODE value should match with TAX CODE value of AR VAT TAX Table SB AR CUST 10050 ADDRESS cannot be NULL SB AR CUST 10051 INSERT UPDATE FLAG should be either I Insert or U Update SB AR CUST 10052 CUSTOMER STATUS should be either A Active or Inactive SB AR CUST 10053 CUSTOMER TYPE should be either Internal or R External SB AR CUST 10054 PRIMARY SITE USE FLAG should be either Y Yes or N No or NULL SB AR CUST 10055 BILL TO ORIG ADDRESS REFP cannot be NULL SB AR CUST 10056 ORIG SYSTEM ADDRESS REF does not exist in RA ADDRESSES table SB AR CUST 10057 ORIG SYSTEM CUSTOMER REF Value should be validated against the RA CUSTOMERS Table based on Insert Update Flag Value SB AR CUST 10058 CITY PROVINCE STATE COUNTY POSTAL CODE and COUNTRY fields should not be null and have valid data when ADDRESS is Not Null SB AR CUST 10059 PRIMARY SITE USE FLAG Should be null when ADDRESS is not null SB AR PROFILE 10100 INSERT UPDATE FLAG is a required column Enter a valid value SB AR PROFILE 10101 SB AR PROFILE 10102 ORIG SYSTEM CUSTOMER REF is a required column Enter a valid value CREDIT HOLD is a required c
67. Requisition Line ID FK Validation Invalid Requisition Distribution ID SB POREC 20150 FK Validation Invalid Inspection Quality Code SB POREC 20151 FK Validation Invalid Charge Account ID Oracle Applications eWay Intelligent Adapter User s Guide 108 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 17 Receiving Transaction Errors Error Code Error Message SB POREC 20152 FK Validation Invalid Employee ID SB POREC 20153 FK Validation Invalid Wip Entity ID SB POREC 20154 FK Validation Invalid Item ID SB POREC 20155 FK Validation Invalid Transportation Account ID SB POREC 20156 FK Validation Invalid Wip Line ID SB POREC 20157 FK Validation Invalid Repetitive Schedule ID SB POREC 20158 Foreign Key Validation Invalid Wip Entity ID for wip operations SB POREC 20159 FK Validation Invalid Wip Entity ID for wip operations resources SB POREC 20160 FK Validation Invalid Bom Resource ID SB POREC 20161 FK Validation Invalid Department Code SB POREC 20162 FK Validation Invalid Freight Carrier Code SB POREC 20163 FK Validation Invalid SubInventory SB POREC 20164 FK Validation Invalid Locator ID SB POREC 20165 FK Validation Invalid Uom Code SB POREC 20166 FK Validation Invalid Currency_Conversion_Type SB POREC 20167 FK Validation Invalid Reason ID SB POREC 20168 FK Validation Invalid
68. SB CE STATE 30221 Exchange rate does not exist in GL DAILY RATES SB CE STATE 30222 SB CE STATE 30223 Exchange rate date does not exist in GL DAILY RATES Exchange rate type does not exist in GL DAILY RATES SB CE STATE 30224 Trx date cannot be greater than sysdate SB CE STATE 30225 Bank trx number does not exist in AP CHECKS V 24 Fixed Assets Table 24 Fixed Assets Errors Error Code Error Message SB FA CATE 50200 SB FA CATE 50201 CATEGORY D cannot be NULL SUMMARY FLAG cannot be NULL SB FA CATE 50202 ENABLED FLAG cannot be NULL SB FA CATE 50203 OWNED LEASED cannot be NULL SB FA CATE 50204 LAST UPDATE DATE cannot be NULL SB FA CATE 50205 LAST UPDATED BY cannot be NULL SB FA CATE 50206 CATEGORY TYPE cannot be NULL SB FA CATE 50207 CAPITALIZE FLAG cannot be NULL SB FA CATE 50208 CAPITALIZE FLAG should be either YES or NO SB FA CATE 50209 CATEGORY TYPE should be in LEASELEASEHOLD IMPROVEMENT NON LEASE SB FA CATE 50210 ENABLED FLAG should be either Y or N SB FA CATE 50211 OWNED LEASED should be either OWNED or LEASED SB FA CATE 50212 SB FA CATE 50213 PROPERTY 1245 1250 CODE should be either 1245 or 1250 PROPERTY TYPE CODE should be either PERSONAL or REAL Oracle Applications eWay Intelligent Adapter User s Guide 126 Sun Microsystems Inc Appendix A Error Codes Section A
69. SCAL YEAR does not exists in GL ENTITY BUDGETS table FROM CURRENCY is a required column Enter a valid value SB GL DLRT 40101 TO CURRENCY is a required column Enter a valid value SB GL DLRT 40102 FROM CONVERSION DATE is a required column Enter a valid value SB GL DLRT 40103 TO CONVERSION DATE is a required column Enter a valid value SB GL DLRT 40104 USER CONVERSION TYPE is a required column Enter a valid value SB GL DLRT 40105 CONVERSION RATE is a required column Enter a valid value SB GL DLRT 40106 MODE FLAG is a required column Enter a valid value SB GL DLRT 40120 FROM CURRENCY does not exist IN TABLE FND_CURRENCIES SB GL DLRT 40121 TO CURRENCY does not exist IN TABLE FND_CURRENCIES SB GL DLRT 40122 USER ID does not exist IN TABLE FND USER SB GL DLRT 40123 USER CONVERSION TYPE does not exist IN TABLE GL DAILY CONVERSION TYPES SB GL DLRT 40130 Valid values for LAUNCH RATE CHANGE column are Y N SB GL DLRT 40131 Valid values for MODE FLAG column are D I X SB GL INTERFACE 40200 STATUS cannot be NULL SB GL INTERFACE 40201 SET OF BOOKS ID cannot be NULL SB GL INTERFACE 40202 USER JE SOURCE NAME cannot be NULL SB GL INTERFACE 40203 USER JE CATEGORY NAME cannot be NULL SB GL INTERFACE 40204 ACCOUNTING DATE cannot be NULL SB GL INTERFACE 40205 CURRENCY CODE cannot be NULL SB GL
70. SHORT TABLE NAME Staging Table Node The name of the staging table node is derived from the corresponding Oracle Interface Table name by adding the prefix SB_ and truncating it to 30 characters if necessary SQL File Name If the SOL file is used to create a packaged stored procedure the file name must be the same as the package name The file name is case sensitive and must be less than or equal to 30 character due to the rules of Oracle procedure function name Concurrent Manager Request Function The function name is derived from the Open Interface name specified in the XML and has the form FN REQUEST ORACLE INTERFACE NAME Oracle Applications eWay Intelligent Adapter User s Guide 53 Sun Microsystems Inc Chapter 5 Using the OTD Wizard This chapter describes how to use the Oracle Applications Database Wizard to create Object Type Definitions OTDs based Oracle Applications tables for use in CAPS Projects What s in This Chapter Oracle Applications OTD Wizard Overview on page 54 Creating OTDs on page 55 Exposed OTD Nodes on page 60 s1 Oracle Applications OTD Wizard Overview The Oracle Applications eWay uses a wizard based OTD builder to create OTDs based on your Oracle tables The wizard queries the Oracle tables to determine the hierarchies of the interface tables for a particular module and creates a corresponding OTD It also sets up the necessary staging table and the stored validation procedures
71. SUN SEEBEYOND eWAY ADAPTER FOR ORACLE APPLICATIONS USER S GUIDE Release 5 1 2 SS 4 SUN microsystems Copyright 2006 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 U S A rights reserved Sun Microsystems Inc has intellectual property rights relating to technology embodied in the product that is described in this document In particular and without limitation these intellectual property rights may include one or more of the U S patents listed at http www sun com patents and one or more additional patents or pending patent applications in the U S and in other countries U S Government Rights Commercial software Government users are subject to the Sun Microsystems Inc standard license agreement and applicable provisions of the FAR and its supplements Use is subject to license terms This distribution may include materials developed by third parties Sun Sun Microsystems the Sun logo Java Sun Java Composite Application Platform Suite SeeBeyond eGate elnsight eVision eTL eXchange eView elndex eBAM eWay and JMS are trademarks or registered trademarks of Sun Microsystems Inc in the U S and other countries All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc in the U S and other countries Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems Inc UNIX is a registered trademark in
72. Samples OraApps BPEL output Make a note of the location where you extracted these files 643 Configure the File eWays In the Connectivity Map Configure the two inbound file eWays and the outbound file eWay For each of these eWays enter the directory where the eWay reads the input or writes the output 644 Create the Environment In the Environment Explorer create a new Environment and add the following items Table 13 Orcl_Apps_BPEL Environment Name External System Type LogicalHost1 Logical Host IntegrationSvr1 Sun SeeBeyond Integration Server SBJmsIOMgr Sun SeeBeyond JMS IQ Manager Oracle Apps BPEL Outbound Oracle Applications eWay Header In Inbound File eWay Lines In Inbound File eWay Output Outbound File eWay The Environment will look like the one in Figure 31 Oracle Applications eWay Intelligent Adapter User s Guide 81 Sun Microsystems Inc Chapter 6 Section 6 4 Implementing the Sample Projects Using the Order Import BPEL Sample Figure 31 Orcl Apps BPEL Environment File Tools View Window Help sua a MyRepository Orcl Apps JCE LogicalHost1 F EN IntegrationSvr1 g SBJmslGMgr1 Oracle Apps BPEL fe Header In Lines In Output Project Explorer x Environment Explorer 645 Create the Deployment Profile In the Project Explorer create a new Deployment Profile as shown in Create the Deployment Profile on page 74 and co
73. Sun Microsystems Inc Chapter 6 Section 6 5 Implementing the Sample Projects Using the Financial GL Budget JCD Sample Figure35 Input File Directory 3 Configuration Parameters Directory CAdatatinputiOraAppu Input file name budget in Input type Bytes Maximum bytes per record 4096 Multiple records per file False Polling interval 5000 Remove EOL False Description parameter settings Comments parameter settings Properties OK 5 Click OK to save the changes to the eWay s properties 6 Similarly configure the outbound file eWays to write the output files to an appropriate location such as C CAPS_Samples OraApps JCD Voutput files 654 Create the Environment In the Environment Explorer create a new Environment and add the following items Table 14 Oracle Apps Environment Name External System Type LogicalHost1 Logical Host IntegrationSvr1 Sun SeeBeyond Integration Server SBJmsIQMegr Sun SeeBeyond JMS IQ Manager Oracle_Apps Outbound Oracle Applications eWay FileIN Inbound File eWay FileOUT Outbound File eWay The Environment will look like the one in the following diagram Oracle Applications eWay Intelligent Adapter User s Guide 87 Sun Microsystems Inc Chapter 6 Section 6 6 Implementing the Sample Projects Using the Financial GL Budget BPEL Sample Figure 36 Orcl Apps Fin Environment
74. The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate stmt headers pkg sql sb validate stmt lines pkg sql These files are controlled by the following master validation file sb validate bank stmt pkg sql Oracle Applications eWay Intelligent Adapter User s Guide 45 Sun Microsystems Inc Chapter 4 Section 4 3 Pre Validation Process Financial Module 434 Fixed Assets Module The Oracle Fixed Assets module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining fixed asset control Categories Oracle Interface Tables Oracle provides the following Interface Table for Requisitions fa categories b SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb fa categories b Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following file sb validate cat pkg sql This file is controlled by the following master validation file sb validate fa categories pkg sql Locations Oracle Interface Tables Oracle provides the following Interface Table for Requisitions fa locations SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb
75. Way sont des marques de fabrique ou des marques d pos es de Sun Microsystems Inc aux Etats Unis et dans d autres pays Toutes les marques SPARC sont utilis es sous licence et sont des marques de fabrique ou des marques d pos es de SPARC International Inc aux Etats Unis et dans d autres pays Les produits portant les marques SPARC sont bas s sur une architecture d velopp e par Sun Microsystems Inc UNIX est une marque d pos e aux Etats Unis et dans d autres pays et licenci e exclusivement par X Open Company Ltd Ce produit est couvert la l gislation am ricaine en mati re de contr le des exportations et peut tre soumis la r glementation en vigueur dans d autres pays dans le domaine des exportations et importations Les utilisations ou utilisateurs finaux pour des armes nucl aires des missiles des armes biologiques et chimiques ou du nucl aire maritime directement ou indirectement sont strictement interdites Les exportations ou r exportations vers les pays sous embargo am ricain ou vers des entit s figurant sur les listes d exclusion d exportation am ricaines y compris mais de mani re non exhaustive la liste de personnes qui font objet d un ordre de ne pas participer d une facon directe ou indirecte aux exportations des produits ou des services qui sont r gis par la l gislation am ricaine en mati re de contr le des exportations et la liste de ressortissants sp cifiquement d sign s sont rigoureusement interdite
76. Year Update Logic Type Budget Entity Name Sample Project Overview To work with this sample you must import the project into your CAPS Repository configure the components for your environment and run the Project To import configure and run the Financial GL Budget sample you must follow these general steps 1 Import the sample Project as described in Import the Financial GL Budget JCD Sample on page 84 2 Setup the sample data on your system as described in Set up the Sample Data on page 85 3 Configure each of the four file eWays as described in Configure the File eWays on page 85 4 Create an Environment for the Project as described in Create the Environment on page 86 5 Create and configure the Deployment Profile as described in Create the Deployment Profile on page 87 Oracle Applications eWay Intelligent Adapter User s Guide 84 Sun Microsystems Inc Chapter 6 Section 6 5 Implementing the Sample Projects Using the Financial GL Budget JCD Sample 6 Configure the Oracleapps1 eWay the eWay that exchanges the data with Oracle Applications as described in Configure the Oracle Apps External System on page 87 6 51 Import the Financial GL Budget JCD Sample To download the sample from the Enterprise Manager 1 From the Documentation page of your Enterprise Manager click the link for the Oracle Applications eWay Intelligent Adapter The Oracle Applications documentation page appears 2 Click Downlo
77. acle Validation Applications Procedures eWay Concurrent Manager 3 Invoke Applications Database Disclaimer The pre validation scripts packaged with the eWay for the supported modules are rudimentary and do not cover all possible scenarios Since the requirements from Oracle occasionally change and evolve you may be required to provide additional data and or parameters to ensure that the Concurrent Manager request completes successfully without errors 1 What s New in This Release This 5 1 2 version release provides general maintenance fixes for the Oracle Applications eWay Intelligent Adapter The Oracle Applications eWay also includes the following changes and new features New for Version 5 1 1 Version Control An enhanced version control system allows you to effectively manage changes to the eWay components Oracle Applications eWay Intelligent Adapter User s Guide 12 Sun Microsystems Inc Chapter 1 Section 1 4 Introducing the Oracle Applications eWay About This Document Multiple Drag and Drop Component Mapping from the Deployment Editor The Deployment Editor now allows you to select multiple components from the Editor s component pane and drop them into your Environment component Support for Runtime LDAP Configuration eWay configuration properties now support LDAP key values Connection Retry Support Allows you to specify the number of attempts to reconnect and the interval between retry attempts
78. ad Sample 3 When you are prompted to open or save the file click Open The sample zip file opens in WinZip 4 Use WinZip to extract the Oracle Applications eWay Sample zip files to a location on your local file system such as C CAPS_Samples OraApps Make a note of where you extracted the files To import the sample in the Enterprise Designer 1 In the Enterprise Designer right click your Repository and click Import 2 Click Yes to save any changes to your Repository The Import Manager appears 3 Click Browse and navigate to the location where you downloaded the sample files in step 4 of the previous procedure In the JCD folder select the prjOraApp Fin BudgetGL JCD Sample zip file and click Open Figure 34 Import Manager Specify the ZIP file and the root to import to From ZIP file C Documention Oracle ApplicationsCEYOraApp Fin BudgetGL JCE sample zip Browse Root project Root environment Repository v Repositoryt Importing selected projects Importing 0 environments Project Exclude OraApp Fin BudgetGL J Import Close 4 In the Import Manager click Import Oracle Applications eWay Intelligent Adapter User s Guide 85 Sun Microsystems Inc Chapter 6 Section 6 5 Implementing the Sample Projects Using the Financial GL Budget JCD Sample 5 Animport status message appears when the import completes successfully Click OK to continue 6 Click
79. an add an Activity to a Business Process then associate that Activity with an eGate component for example an eWay When eInsight run the Business Process it automatically invokes that component via its Web Services interface 62 Exchanging Data with Oracle Applications Figure 15 depicts the procedure to insert or update the Oracle Applications database with a message from some external system The individual steps are described below Oracle Applications eWay Intelligent Adapter User s Guide 67 Sun Microsystems Inc Chapter 6 Section 6 2 Implementing the Sample Projects Exchanging Data with Oracle Applications Figure 15 CAPS to Oracle Operation Oracle Applications Oracle Stored Applications Validation Staging eWay Procedures 1 Subscribe Oracle Open Concurrent Interface Manager Error Queue Applications Database 9 Retrieve Error Rows 1 A Service in the Oracle Applications eWay subscribes to data coming from another system via eGate Integrator and transforms the data into the proper format for inserting into the relevant Open Interface Table OIT 2 The Collaboration Definition Script inserts the data into a SeeBeyond Staging Table corresponding to the relevant Open Interface Table OIT The SeeBeyond Staging Table mirrors the Open Interface Table structure plus additional columns for the pre validation status and ID values 3 The Collaboration Definition Script calls a SeeBeyon
80. apter User s Guide 131 MOVE OTD node 63 mtl cc entries interface 38 mtl ci interface 37 mtl ci xrefs interface 37 mtl item revisions interface 38 mtl replenish headers int 39 mtl replenish lines int 39 mtl serial numbers interface 39 mtl system items interface 38 mtl transaction lots interface 39 mtl transactions interface 39 O Object Type Definition OTD Creating 55 Exposed OTD Nodes 60 Oracle Applications eWay properties Environment Explorer properties 25 P Plug Ins Installing 22 po headers interface 40 po lines interface 40 po requisitions interface all 41 Pre Validation Building a Custom Package 49 Procedures 36 Scripts 36 properties Connectivity Map properties modifying 27 Environment Explorer properties 25 Environment properties modifying 27 modifying 27 Connectivity Map properties 27 Properties Editor 27 R rcv headers interface 40 rcv transactions interface 40 REQUEST OTD node 64 REQUEST STATUS OTD node 64 S sb mtl cc entries interface 38 sb mtl ci interface 37 Sun Microsystems Inc Index sb mtl ci xrefs interface 37 sb mtl item revisions int 38 sb mtl replenish headers int 39 sb mtl replenish lines int 39 sb mtl serial numbers interfac 39 sb mtl system items interface 38 sb mtl transaction lots inter 39 sb mtl transactions interface 39 sb po headers interface 40 sb po lines interface 40 sb po requisitions interface a 41 sb rcv headers interface 40 sb r
81. ation plug in that you added The Alert Properties Files are located in the alertcodes folder of your Sun Java Composite Application Platform Suite installation directory 5 Click Deploy The available alert codes for your application are displayed under Results A listing of available alert codes is displayed in Table 2 Table2 Alert Codes for the Oracle Applications eWay Alert Code Description Description Details User Actions DBCOMMON CONNECT FAILED000001 Failed to connect to database 0 on host 1 Reason The Pooled connection could not be allocated 2 Occurs during the initial database connection Database is down start your database External configuration information is invalid You may need to verify the following Server name Database name User Password Port DBCOMMON CONNECT FAILED000002 Operation failed because of a database connection error Reason 0 Occurs while retrieving a connection from the database or the pool Verify that the database has not terminated with unexpected errors DBCOMMON CONNECT FAILED000005 Connection handle not usable Reason 0 The connection in the pool is stale and is not usable Probably a database restart occurred causing the connection to be stale retry the operation after the database is up DBCOMMON XARESOURCE FAILED000001 Unable to get XAResource for the database Reason 0 Could not obtain XAR
82. ation_Script PCDATA gt lt relative path to the sql script file for Utility package gt lt ELEMENT Utility Script PCDATA gt e Lt E a ZH lt relative path to the sql script file for concurrent manager request function gt lt ELEMENT Concurrent Manager PCDATA gt lt parameter description for concurrent manager request function gt lt ELEM lt 1 ENT Request Param PCDATA gt elative path to the sql script file for function to retrieve concurrent manager request status gt lt ELEMENT Concurrent Manager Status PCDATA gt Oracle Open Interface table definition gt lt ELEMENT Interface Table Validation Script Interface Table name for the oracle open interface table gt lt ATTLIST Interface Table Name CDATA REQUIRED gt lt name for SB staging table this attribute is optional if this attribute is set the program directly uses its value as the SB staging table for this specific interface gt lt ATTLIST Interface Table SB Name CDATA IMPLIED gt lt utility store procedure name at specific interface level this attribute is optional if this attribute is specified it overrides the default name convention which is derived from the specific interface name gt lt ATTLIST Interface_Table
83. ay on page 25 Oracle Applications eWay Connectivity Map Properties on page 28 Oracle Applications eWay Environment Configuration Properties on page 29 31 Creating and Configuring the Oracle Applications eWay eWays contain a set of parameters with properties that are unique to that eWay type The Oracle Applications eWay properties are modified from these locations Connectivity Map These parameters most commonly apply to a specific component eWay and may vary from other eWays of the same type in the Project Environment Explorer These parameters are commonly global applying to all eWays of the same type in the Project The saved properties are shared by all eWays in the Oracle Applications External System window Collaboration or Business Process Oracle Applications eWay properties may also be set from your Collaboration or Business process in which case the settings will override the corresponding properties in the eWay s configuration file Any properties that are not overridden retain their configured default settings Oracle Applications eWay Intelligent Adapter User s Guide 25 Sun Microsystems Inc Chapter 3 Section 3 1 Configuring the Oracle Applications eWay Creating and Configuring the Oracle Applications eWay 311 Selecting Oracle Applications as the External Application To create a Oracle Applications eWay you must first create a Oracle Applications External Application in your Connectivity Ma
84. b validate gl int pkg sgl These files are controlled by the following master validation file sb validate journal pkg sql Oracle Applications eWay Intelligent Adapter User s Guide 48 Sun Microsystems Inc Chapter 4 Section 4 4 Pre Validation Process Building a Custom Pre Validation Package 44 Building a Custom Pre Validation Package Important Read sections 4 5 Naming Conventions on page 52 and 5 3 Exposed OTD Nodes on page 60 for more information on modifying the template xml correctly The Order Import xml is a good example to refer to To build a custom pre validation package for a non supported Open Interface 1 Modify the Oracle Applications master configuration file in the following location to add a new module CAPS Dir edesigner userdir modules ext oracleappsadapter wizard configs Applications xml When adding a new business function assign the business section a new name and entry for the new open interface Spaces are acceptable when creating a module name Module Name Module Name Definition moduleDefinition xml lt Module Notice that the name attribute is an English description which appears in the OTD wizard where the definition attribute locates the open interface XML definition file this attribute cannot have spaces 2 Copy and rename the template xml file from CAPS Dir edesigner userdir modules ext oracleappsadapter wizard configs templateXml xml to the appropriate direct
85. bed in Import the Order Import JCD Sample on page 71 2 Setup the sample data on your system as described in Set up the Sample Data on page 72 3 Configure each of the four file eWays as described in Configure the File eWays on page 72 4 Create an Environment for the Project as described in Create the Environment on page 73 5 Create and configure the Deployment Profile as described in Create the Deployment Profile on page 74 6 Configure the Oracleapps1 eWay the eWay that exchanges the data with Oracle Applications as described in Configure the Oracle_Apps External System on page 76 7 Deploy the Project s Deployment Profile as described in Deploying the Project on page 77 Oracle Applications eWay Intelligent Adapter User s Guide 70 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample 8 Configure the Logical Host s properties and start the bootstrap process as described in Running the Sample Project on page 77 63 1 Import the Order Import JCD Sample To download the sample from the Enterprise Manager 1 From the Documentation page of your Enterprise Manager click the link for the Oracle Applications eWay Intelligent Adapter The Oracle Applications documentation page appears 2 Click Download Sample When you are prompted to open or save the file click Open The sample zip file opens in WinZip 4 Use WinZip to extract
86. ble and current value is null SB POREC 20123 Transaction Date field is mandatory in rcv transactions interface table and current value is null SB POREC 20124 Processing Status Code field is mandatory in rcv transactions interface table and current value is null SB POREC 20125 Processing Mode Code field is mandatory in rcv transactions interface table and current value is null Oracle Applications eWay Intelligent Adapter User s Guide 107 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 17 Receiving Transaction Errors Error Code Error Message SB POREC 20126 Transaction Status Code field is mandatory in rcv transactions interface table and current value is null SB POREC 20127 Quantity field is mandatory in rcv transactions interface table and current value is null SB POREC 20128 Unit Of Measure field is mandatory in rcv transactions interface table and current value is null SB POREC 20129 Item Description field is mandatory in rcv transactions interface table and current value is null SB POREC 20130 SB POREC 20131 Value required in Document Line Num or Item Num or Vendor Item Num or Item ID or Po Line ID in rcv transactions interface table and currently all are null Auto Transact Code field is mandatory in rcv transactions interface table and current value is null SB POREC 20132 Receipt Source C
87. bles listed above sb mtl system items interface sb mtl item revisions int Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate items pkg sql sb validate invrev pkg sql Oracle Applications eWay Intelligent Adapter User s Guide 38 Sun Microsystems Inc Pie validation Module Replenishment Oracle Interface Tables Oracle provides the following Interface Tables for Item Replenishment mtl replenish headers int mtl replenish lines int SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging tables corresponding to the Oracle Open Interface Tables listed above sb mtl replenish headers int sb mtl replenish lines int Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate rep headers pkg sql sb validate rep lines pkg sql These files are controlled by the following master validation file sb validate rep pkg sql Transactions Oracle Interface Tables Oracle provides the following Interface Tables for Transactions mtl transactions interface mtl transaction lots interface mtl serial numbers interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging tables corresponding to the Oracle Open Interface Tables listed above sb mtl transa
88. cations eWay Properties A Project s eWay properties can be modified after the eWay has been established in the Connectivity Map and the Environment has been created Oracle Applications eWay Intelligent Adapter User s Guide 26 Sun Microsystems Inc Chapter 3 Section 3 1 Configuring the Oracle Applications eWay Creating and Configuring the Oracle Applications eWay Configuring the Oracle Applications eWay Connectivity Map Properties 1 From the Connectivity Map double click the eWay icon located in the link between the associated External Application and the Service 2 TheeWay Properties Editor appears with a template containing the Oracle Applications eWay Connectivity Map properties Make any necessary changes to the property values and click OK to save the settings Configuring the Oracle Applications eWay Environment Explorer Properties 1 From the Environment Explorer tree right click the Oracle Applications External System Select Properties from the shortcut menu The Properties Editor opens with the Oracle Applications eWay Environment properties 2 Make any necessary changes to the Environment property values and click OK to save the settings 313 Using the Properties Editor Modifications to the eWay configuration properties are made from the Oracle Applications eWay Properties Editor A description of each property is displayed in the Description pane when it is selected This provides a brief explanation of the req
89. ce Table listed above sb gl budget interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate gl budget pkg sql These files are controlled by the following master validation file sb validate budget pkg sql Oracle Applications eWay Intelligent Adapter User s Guide 47 Sun Microsystems Inc Pie Validation Module Daily Rates Oracle Interface Tables Oracle provides the following Interface Table for Requisitions gl daily rates interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb gl daily rates interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate gl daily rates pkg sql These files are controlled by the following master validation file sb validate dailyrates pkg sql Journal Oracle Interface Tables Oracle provides the following Interface Table for Requisitions gl interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb gl interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files s
90. cle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb ra customers interface sb ra contact phones int all sb ra cust pay method interface sb ra customer banks int all sb ra customer profiles interface Oracle Applications eWay Intelligent Adapter User s Guide 44 Sun Microsystems Inc Chapter 4 Section 4 3 Pre Validation Process Financial Module Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate cust pkg sql sb validate contact phones pkg sql sb validate cust pay mtd pkg sql sb validate cust banks pkg sql sb validate cust profiles pkg sql This file is controlled by the following master validation file sb validate customers pkg sql 433 Cash Management Module The Oracle Cash Management module works with other Oracle Financial modules to provide a complete set of transactions and reports for maintaining cash management control Bank Statement Oracle Interface Tables Oracle provides the following Interface Table for Requisitions ce statement headers int all ce statement lines interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb ce statement headers int all sb ce statement lines interface Pre Validation Scripts
91. ctions interface sb mtl transaction lots inter sb mtl serial numbers interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate trans pkg sgl sb validate trans lots pkg sgl Oracle Applications eWay Intelligent Adapter User s Guide 39 Sun Microsystems Inc Chapter 4 Section 4 2 Pre Validation Process Manufacturing Module sb validate serial nos pkg sql These files are controlled by the following master validation file sb validate tran all pkg sql 422 Purchase Order Import Module The Oracle Purchase Order Import module works with other Oracle Manufacturing modules to provide a complete set of transactions and reports for maintaining inventory control Purchase Order Import Oracle Interface Tables Oracle provides the following Interface Tables for Purchase Order Import po headers interface po lines interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging tables corresponding to the Oracle Open Interface Tables listed above sb po headers interface sb po lines interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate poi hdrs pkg sql sb validate poi lines pkg sql These files are controlled by the following master validation file sb validate poi pkg sql
92. cv transactions interface 41 sb validate cc entries pkg 95 sb validate items pkg 96 sb validate poi hdrs pkg 113 115 119 120 125 126 128 sb validate trans pkg 101 Staging Table Node OTD node 60 T text conventions 14 V VALIDATE OTD node 65 Oracle Applications eWay Intelligent Adapter User s Guide 132 Sun Microsystems Inc
93. d SB AR CUST 10000 ORIG SYSTEM CUSTOMER REF cannot be NULL SB AR CUST 10001 SITE USE CODE cannot be NULL SB AR CUST 10002 ORIG SYSTEM ADDRESS REF cannot be NULL SB AR CUST 10003 SB AR CUST 10004 INSERT UPDATE FLAG cannot be NULL CUSTOMER NAME cannot be NULL SB AR CUST 10005 CUSTOMER NUMBER cannot be NULL SB AR CUST 10006 CUSTOMER STATUS cannot be NULL SB AR CUST 10007 LAST UPDATED BY cannot be NULL SB AR CUST 10008 LAST UPDATE DATE cannot be NULL SB AR CUST 10009 CREATED BY cannot be NULL SB AR CUST 10010 CREATION DATE cannot be NULL SB AR CUST 10011 LOCATION cannot be NULL SB AR CUST 10025 SITE USE CODE does not exists in AR LOOKUPS table SB AR CUST 10026 CUSTOMER TYPE does not exists in AR LOOKUPS table SB AR CUST 10027 ORIG SYSTEM PARENT REF does not exists in RA CUSTOMERS table SB AR CUST 10028 SB AR CUST 10029 CUSTOMER CATEGORY CODE does not exists in AR LOOKUPS table CUSTOMER CLASS does not exists in AR LOOKUPS table Oracle Applications eWay Intelligent Adapter User s Guide 122 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 22 Customer Interface Errors Error Code Error Message SB AR CUST 10030 DEMAND CLASS CODE does not exists in FND COMMON LOOKUPS table SB AR CUST 10031 CUST SHIP VIA CODE does not exists in ORG F
94. d stored procedure to pre validate the rows in the SeeBeyond Staging Table 4 The stored procedure executes whatever queries are required to pre validate the data and updates the specific error code columns in the SeeBeyond Staging Table When complete each row in the staging table has been marked with a status indicating whether or not it passed pre validation If not the row s error code indicates the type of error including an explanation 5 Depending on the business rules for the process the eWay invokes a number of stored procedures to handle the rows in the SeeBeyond Staging Table there is one set of such stored procedures per SeeBeyond Staging Table For example depending on the business requirements Oracle Applications eWay Intelligent Adapter User s Guide 68 Sun Microsystems Inc Chapter 6 Section 6 2 Implementing the Sample Projects Exchanging Data with Oracle Applications all invalid rows can be deleted before proceeding to move valid rows to the Open Interface Table all invalid rows can be published to another system or be routed there by another eWay the eWay can abort on finding one or more errors if the business requirement is that all rows succeed or all rows fail After the valid records are copied from the staging tables to the Open Interface Tables the eWay invokes the relevant Oracle Concurrent Manager The Concurrent Manager performs its own validation of the data in the Open Interfac
95. d the eWay to an existing Sun Java Composite Application Platform Suite installation Steps required to add an eWay to an Existing CAPS installation include 1 Complete steps 1 through 6 on Installing the Oracle Applications eWay on an eGate Supported System on page 17 2 Open the Enterprise Designer and select Update Center from the Tools menu The Update Center Wizard appears Oracle Applications eWay Intelligent Adapter 17 Sun Microsystems Inc Chapter 2 Installing the Oracle Applications After You Install 2 2 4 Section 2 3 For Step 1 of the wizard simply click Next For Step 2 of the wizard click the Add button to move all installable files to the Include in Install field then click Next For Step 3 of the wizard wait for the modules to download then click Next The wizard s Step 4 window displays the installed modules Review the installed modules and click Finish When prompted restart the IDE Integrated Development Environment to complete the installation After You Install If you choose to use the OCI driver you must copy the classes12 jar file from the Oracle client to the Logical Host Oracle 10g users must copy the ojdbc14 jar file from the Oracle client and rename it to the classes12 jar file before copying into the Logical Host Note Be sure to create a back up of the original classes12 jar file before applying these changes Ways to load the classes12 jar file include Loadi
96. der IM passthru1 eWay Icons gt aee a POI Lines Input POI Lines IN passthru1 4 In the Directory field type the location where you extracted the sample input files in step 2 of the previous procedure Figure 19 Input File Directory co BEES X Jue ez Directory CACAN_Samples OraAppsiJCE input_files Input file name POlmport_Headers in Input type Bytes Maximum bytes perrecord 4096 Description Directory Directory Multiple records per file False Polling interval 5000 Remove EOL False Comments Directory Properties 5 Click OK to save the changes to the eWay s properties 6 Repeat steps 3 through 5 double clicking the eWay icon between the POI Lines Input external and the POI_Lines_IN_passthru1 Service the lower icon shown in Figure 19 Oracle Applications eWay Intelligent Adapter User s Guide 73 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample 7 Similarly configure the outbound file eWays to write the output files to an appropriate location such as C CAPS_Samples OraApps JCD Voutput files 634 Create the Environment To create the Environment 1 In the Environment Explorer tab of the Enterprise Explorer right click the Repository and click New Environment 2 Right click the new Environment and click Rename Name the Environment Orcl Apps JCD 3 Right click the Orcl Apps JCD Envir
97. dures to move delete and function count all interface tables and the OTD level Please refer to section 4 3 Exposed OTD Nodes on page 60 for more information on how to compose the procedure and function names Replace lt CONCURRENT_MANAGER_FUNCTION_SOL_FILE_NAME gt with the correct path and file name for the concurrent file This concurrent manager file name must be sql business_function_name lt MODULE_NAME gt lt ORACLE_INTERFACE NAME gt fn_request_ lt ORACLE_INTERFACE_NAME gt sql relative from CAPS Dir edesigner userdir modules ext oracleappsadapter wizard This function eventually invokes the concurrent manager Please refer to REQUEST on page 64 for more information on how to compose this function Replace lt INTERFACE_TABLE_NAME gt with the correct interface table name Create more entries as needed for each interface table either in the same level or as a child For example in manufacturing order import has two interface tables with child parent relationships where as item import has two interface tables with sibling relationships Replace lt TABLE VALIDATION PACKAGE SQL FILE NAME gt with the correct path and file name for the validation package for this particular interface table This validation package file name must be sql Oracle Applications eWay Intelligent Adapter User s Guide 50 Sun Microsystems Inc Chapter 4 Section 4 4 Pre Valida
98. e SB POREQ 20121 WIP_Entity_ID is invalid FK validation failed against wip_entities table SB POREQ 20122 WIP_Line_ID is invalid FK validation failed against wip_lines table SB POREQ 20123 WIP_Entity_ID or Dest_Org_ID or Wip_Operation_Seq_Num or Wip_Rept_Sch_ID either one is invalid FK validation failed against wip_operations table SB POREQ 20124 WIP_Entity_ID or Dest_Org_ID or Wip_Operation_Seq_Num or Wip_Rept_Sch_ID or Resource Seq Num either one is invalid validation failed against wip operation resources table SB POREQ 20125 WIP Repetitive Schedule ID or Dest Org ID either one is invalid FK validation failed against wip repetitive schedules table SB POREQ 20126 Requisition Line ID is invalid FK validation failed against po requisition lines all table SB POREQ 20127 Src Org ID is invalid FK validation failed against org organization definitions table SB POREQ 20128 Dest_Org_ID is invalid FK validation failed against org_organization_definitions table SB POREQ 20129 Source_Subinventory is invalid for a given Src_Org_ID FK validation failed against MTL_Secondary_Inventories table SB POREQ 20130 Destination Subinventory is invalid for a given Dest Org ID FK validation failed against MTL Secondary Inventories table SB POREQ 20131 Deliver To Requestor ID is invalid FK validation failed against hr employees table SB POREQ 20132 Suggested
99. e The connections the pool keeps available at all times 0 zero indicates that there are no physical connections in the pool and new connections are created as needed default is 2 MaxPoolSize The maximum number of physical connections the pool keeps available at all times 0 zero indicates that there is no maximum A valid numeric value The default is 10 MaxldleTime The maximum number of seconds that a physical connection may remain unused before it is closed 0 zero indicates that there is no limit A valid numeric value Connection Retry Settings The Connection Retry Settings section of the Outbound Oracle Applications Environment contains the top level parameters displayed in Table 6 Oracle Applications eWay Intelligent Adapter User s Guide 31 Sun Microsystems Inc Chapter 3 Configuring the Oracle Applications eWay Section 3 3 Oracle Applications eWay Environment Configuration Properties Table 6 Outbound eWay Environment Connection Retry Settings Name Description Required Value ConnectionRetries Specifies the number of retries to establish a connection with the Oracle database upon a failure to acquire one An integer indicating the number of attempts allowed to establish a connection The configured default is 0 ConnectionRetry Interval Specifies the configured length of the pause before each reattempt to access the destination file
100. e The that is used to implement the default value is ConnectionPoolDataSource interface oracle jdbc pool OracleConn ectionPoolDataSource Properties in the Outbound eWay with XA Support The JDBC Connector Settings section of the Oracle Applications Connectivity Map properties contains the top level parameters displayed in Table 4 Table 4 Outbound with XA Support JDBC Connector Settings Name Description Required Value Description Specifies the description for the database A valid string The default is Oracle thin driver XA Datasource ClassName Specifies the Java class in the JDBC driver A valid class name that is used to implement the The default value is ConnectionPoolDataSource interface oracle jdbc xa client OracleX ADataSource Oracle Applications eWay Environment Configuration Properties The Oracle Applications eWay configuration parameters accessed from the Environment Explorer tree are organized into the following sections Outbound Oracle eWay Properties on page 30 Outbound Oracle eWay Properties with XA support on page 32 Oracle Applications eWay Intelligent Adapter User s Guide 29 Sun Microsystems Inc Chapter 3 Section 3 3 Configuring the Oracle Applications eWay Oracle Applications eWay Environment Configuration Properties Figure 6 Oracle Applications eWay Environment Configuration Configuration JAg o EWI O Outbound Oracle Applications eWay Description O
101. e Applications eWay Intelligent Adapter User s Guide 32 Sun Microsystems Inc Chapter 3 Configuring the Oracle Applications eWay Section 3 3 Oracle Applications eWay Environment Configuration Properties Table7 Outbound XA eWay Environment JDBC Connector Settings Name Description Required Value DriverProperties Use the JDBC driver that is shipped with this eWay Often times the DataSource implementation needs to execute additional methods to assure a connection You must identify the additional methods in the Driver Properties Any valid delimiter Valid delimiters are lt method name 1 gt lt param 1 gt lt param 2 gt lt param n gt lt method name 2 gt lt param 1 gt lt param 253b a param n 7Hf HH For example to execute the method setURL give the method a String for the URL setURL lt url gt dH Delimiter This is the delimiter character to be used The default is in the DriverProperties prompt TNSEntry Specifies the TNS name for the Oracle A valid TNS name if using the instance specified in TNSNAMES ORA If OCI driver otherwise do not a TNS name is specified then the OCI enter any value driver is used which further requires installation of the Oracle client If a TNS name is not specified then the thin driver is used MinPoolSize The minimum number of physical A valid numeric value The connections the pool keeps available at
102. e Table The Concurrent Manager then imports the data into the appropriate Oracle Manufacturing database tables Prepared statements in the OTD are used to retrieve the invalid records from the staging tables along with the ID values for the failed rows Oracle Applications eWay Intelligent Adapter User s Guide 69 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample 63 Using the Order Import JCD Sample The Order Import JCD sample demonstrates the operation of the outbound Oracle Applications eWay by reading information from two files writing the information to the appropriate Oracle Applications tables and writing the results out to two output files Figure 16 The Order Import JCD Sample Wu p B Oracleapps1 i PD JMS_to_File1 Header Output fo POI Lines Input POI Lines IN passthru1 a Topic3 JMS to File2 POI Lines Output Dp a The two input files represent header and line item information for a sample order This information would typically come from an external application via another eWay or from another upstream CAPS component Sample Project Overview To work with this sample you must import the project into your CAPS Repository configure the components for your environment and run the Project To import configure and run the Order Import sample you must follow these general steps 1 Import the sample Project as descri
103. e a new Deployment Profile as shown in Create the Deployment Profile on page 74 and configure the components similar to those shown in Figures 22 through 27 skipping figure 26 since there is only one outbound file eWay Oracle Applications eWay Intelligent Adapter User s Guide 91 Sun Microsystems Inc Chapter 6 Section 6 6 Implementing the Sample Projects Using the Financial GL Budget BPEL Sample 666 Configure the Oracle Apps Fin BPEL External System In the Environment Explorer configure the Oracle Apps BPEL external system the same way it is configured in Configure the Oracle Apps External System on page 76 Oracle Applications eWay Intelligent Adapter User s Guide 92 Sun Microsystems Inc Appendix A Error Codes This chapter provides a description of each of the error codes returned by the validation scripts A description of the validation process is found in Pre Validation Process on page 35 What s in This Chapter Manufacturing on page 93 Inventory on page 93 Purchase Order on page 102 Financial Budget GL on page 113 Accounts Payable on page 113 Accounts Receivable on page 115 Cash Management on page 125 Fixed Assets on page 126 General Ledger on page 128 Note If new Error Codes are needed you must drop the current sb errors table and either manually or automatically via the OTD builder re run the sb_install sql script so that a new sb errors table is created wi
104. e and must be NULL SB POIMP 20089 Po Release ID is reserved for future use and must be NULL SB POIMP 20090 Source Shipment ID is reserved for future use and must be NULL SB POIMP 20091 Contract Num is reserved for future use and must be NULL SB POIMP 20092 Type 1099 must be NULL SB POIMP 20093 Receipt Days Exception Code must be NULL SB POIMP 20094 Need By Date must be NULL Oracle Applications eWay Intelligent Adapter User s Guide 105 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 14 Import Line Errors Error Code Error Message SB POIMP 20095 Promised Date must be NULL SB POIMP 20096 Closed Reason must be NULL SB POIMP 20097 Closed Date must be NULL SB POIMP 20098 Closed By must be NULL SB POIMP 20099 Firm Flag must be NULL SB POIMP 20100 Quantity must be greater than 0 SB POIMP 25001 Committed Amount must be greater than 0 SB POIMP 25002 Market Price must be greater than 0 SB POIMP 25003 Negotiated By Preparer Flag must be either Y or N SB POIMP 25004 Capital Expense Flag must be either Y or N SB POIMP 25005 SB POIMP 25014 Tax name and Tax Code ID must be NULL if Taxable Flag is NULL or N FOB is inactive SB POIMP 25015 Freight Terms is inactive Receiving Master Table 15 Receiving Master Errors Error C
105. e for all entries in this XML file F Modify the scripts as needed for your own implementation In the XML file refer to these new customized SQL files instead of the shipped SQL script Note Do not change either the Initialize Profile stored procedure nor its location 10 11 as the entry point for the initialization packages Replace 97e VALIDATION PACKAGE SQL FILE gt with the correct path and file name for the validation package This validation package file name must be sql business_function_name lt MODULE_NAME gt lt _ 9 gt sb validate interfaceNameAbbreviation pkg sgl this path is relative from CAPS Dir edesigner userdir modules ext oracleappsadapter wizard This package contains the VALIDATE procedure which eventually invokes all the VALIDATE procedures for all the tables Please refer to sections Pre Validation Procedures on page 36 and VALIDATE on page 65 for more information on how to compose the VALIDATE procedure Replace lt 0 PACKAGE SQL FILE NAME 0696 with the correct path and file name for the utility package This utility package file name must be sql business_function_name lt MODULE_NAME gt lt VORACLE_INTERFACE_ NAME gt sb_interfaceNameAbbreviation_utils_pkg sql this path is relative from lt CAPS Dir gt edesigner userdir modules ext oracleappsadapter wizard This package contains the proce
106. emplate DTD The Data Type Definition DTD associated with the template XML file is shown below ELEMENT OPEN INTERFACE Initialize Script Validation Script Utility Script Concurrent Manager Request Param Concurrent Manager Status Interface 1 Error Handle Pre Required Script lt Open interface name gt lt ATTLIST OPEN_INTERFACE gt Name CDATA REQUIRED lt Oracle Manufacturing Version gt lt ATTLIST OPEN_INTERFACE gt Version CDATA REQUIRED lt Application Suite gt lt ATTLIST OPEN_INTERFACE gt Application Suite CDATA REQUIRED lt Module Name gt lt ATTLIST OPEN_INTERFACE gt Module CDATA REQUIRED lt utiltiy store procedure name at root level this attribute is optional if this attribute is specified it overrides the default Oracle Applications eWay Intelligent Adapter User s Guide 51 Sun Microsystems Inc Chapter 4 Section 4 5 Pre Validation Process Naming Conventions name convention which is derived from Name attribute of OPEN INTERFACE gt lt ATTLIST OPEN_INTERFACE Util_Name CDATA IMPLIED lt relative path to the sql script file for initialize package gt lt ELEMENT Initialize Script PCDATA gt lt relative path to the sql script file for validation package gt lt ELEMENT Valid
107. ems Cross Reference Oracle Interface Table Oracle provides the following Interface Table for Customer Item Cross References mtl ci xrefs interface SeeBeyond Staging Table The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Tables listed above sb mtl ci xrefs interface Oracle Applications eWay Intelligent Adapter User s Guide 37 Sun Microsystems Inc Chapter 4 Section 4 2 Pre Validation Process Manufacturing Module Pre Validation Script The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following file sb validate ci xrefs pkg sql Cycle Count Entries Oracle Interface Table Oracle provides the following Interface Table for Cycle Count Entries mtl cc entries interface SeeBeyond Staging Table The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb mtl cc entries interface Pre Validation Script The scripts corresponding to the SeeBeyond Staging Table listed above are packaged within the following file sb validate cc entries pkg sql Items and Item Revisions Oracle Interface Tables Oracle provides the following Interface Tables for items mtl system items interface mtl item revisions interface SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging tables corresponding to the Oracle Open Interface Ta
108. er 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample 63 8 Running the Sample Project Running the sample Additional steps are required to run the deployed sample Project Steps required to run the sample Project 1 Rename one of the trigger files included in the sample Project from lt filename gt in in to lt filename gt in to run the corresponding operation The File eWay polls the directory every five seconds for the input file name as defined in the Inbound File eWay Properties window The data is then transformed and the File eWay sends the output to an Output file name as defined in the outbound File eWay Properties window 2 Verify the output data by viewing the sample output files The output files may change depending on the number of times you execute the sample Project and the content of the input files Re running the sample Because the document number field in the back end database has a unique constraint you cannot re run the sample project without modifying the sample header input file POImport Headers in The Oracle database does not allow multiple records with the same document number to be inserted Figure 29 Input Header File POlmport Headers in POlmport_Headers in Notepad File Edit Format View 4026 4026 PO PENDING ORIGINAL DEFAULT STANDARD nu11 nu11 USD 53 nu11 517 GRAINGER To update the header file edit POImport Headers in and change the nint
109. es not exist in AR LOOKUPS table SB AR PHONES 10710 ORIG SYSTEM CUSTOMER REF does not exist in HZ CUST ACCOUNTS table SB AR PHONES 10711 ORIG SYSTEM ADDRESS REF does not exist in HZ CUST ACCT SITES ALL table SB AR PHONES 10712 ORIG SYSTEM CONTACT REF does not exist in HZ ORG CONTACTS table Oracle Applications eWay Intelligent Adapter User s Guide 120 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 22 Customer Interface Errors Error Code Error Message SB AR PHONES 10713 ORIG SYSTEM TELEPHONE REF does not exist in HZ CONTACT POINTS table SB AR PHONES 10714 TELEPHONE TYPE does not exist in AR LOOKUPS table SB AR PHONES 10715 INSERT UPDATE FLAG should be either or U SB AR PHONES 10716 TELEPHONE cannot be null if ORIG SYSTEM TELEPHONE REF entered SB AR PHONES 10717 CONTACT LAST NAME cannot be null if ORIG SYSTEM CONTACT REF entered SB AR PHONES 10718 ORIG SYSTEM TELEPHONE REF cannot be null if TELEPHONE entered SB AR PHONES 10719 TELEPHONE TYPE cannot be null if ORIG SYSTEM TELEPHONE REF entered SB AR PAY 10300 ORIG SYSTEM CUSTOMER REF is a required column Enter a valid value SB AR PAY 10301 PAYMENT METHOD NAME is a required column Enter a valid value SB AR PAY 10302 PRIMARY FLAG is a required column Enter a valid value SB AR PAY 10303 START
110. esource for the connection Check if the database supports XA and has been configured for Distributed Transactions DBCOMMON XACONNECT FAILED000001 Failed to connect to database 0 on host 1 The XA connection could not be allocated Reason 2 Occurs during the initial database connection Check if the database is configured for XA and if the database is running External configuration information is invalid You may need to verify the following Server name Database name User Password Port DBCOMMON XASTART FAILED000001 Unable to perform connection error has occurred which caused Check if the database is running and that there are no network XAStart for the connection XASTART to fail issues Reason 0 Oracle Applications eWay Intelligent Adapter 23 Sun Microsystems Inc Chapter 2 Installing the Oracle Applications Section 2 6 Installing Enterprise Manager eWay Plug Ins Alert Code Description Description Details User Actions DBCOMMON XAEND FAILED000001 XA End failed Reason 0 Error occurred during commit on XA connection Look for the detailed error mentioned in the alert for the appropriate action DBCOMMON CANNOT GET ISOLATION LEVEL Unable to get isolationLevel for the transaction Reason 0 Could not read transaction isolation information of the connection Transaction isolation is one of
111. ete set of transactions and reports for maintaining order entry control Oracle Interface Tables Oracle provides the following Interface Table for Order Entry oe headers interface oe lines interface oe actions interface oe credits interface oe price adjs interface oe lotserials interface oe reservtns interface SeeBeyond Staging Tables sb oe headers interface Oracle Applications eWay Intelligent Adapter User s Guide 41 Sun Microsystems Inc Chapter 4 Section 4 3 Pre Validation Process Financial Module sb oe lines interface Sb oe actions interface sb oe credits interface sb oe price adjs interface sb oe lotserials interface sb oe reservtns interface Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following file sb validate oe pkg sql This file is controlled by the following master validation file sb validate oi pkg sgl Financial Module The Financial module is divided into the following sub modules Accounts Payable Module on page 42 Accounts Receivable Module on page 43 Cash Management Module on page 45 Fixed Assets Module on page 46 General Ledger Module on page 47 Each submodule uses at least one corresponding set of tables and scripts as depicted in Figure 7 on page 36 431 Accounts Payable Module The Oracle Accounts Payable module works with other Oracle Financial modules to provide
112. f the Enterprise Designer 632 Set up the Sample Data The POI Header Input and POI Lines Input external systems use two input files to simulate a transaction to be sent to the Oracle Applications system These files must be extracted from the sample zip files and copied to a location to be used by the input File eWays To set up the sample data 1 In Windows Explorer navigate to the location where you extracted the sample zip files in step 4 of the procedure on page 71 for example C CAPS_Samples OraApps JCD 2 Use WinZip to extract these files to a location where the two input file eWays can access them at run time such as C CAPS_Samples OraApps JCD Input_Files Make a note of this location for later use Oracle Applications eWay Intelligent Adapter User s Guide 72 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample 633 Configure the File eWays To configure the file eWays 1 Before you can configure any of the components in the imported Project you must first check them out of the Repository To check out the Connectivity Map right click CMapl click Check Out and click OK 2 Double click CMapl to display the Connectivity Map 3 Double click the eWay icon between the POI Header Input external and the POI Header IN passthrul Service the upper icon in the following figure to edit the eWay s properties Figure 18 eWay Icons a POI Header Input POI Hea
113. g Marketing Sales These Product Families are integrated together to share a common database allowing a company s various departments to quickly and easily share information and communicate with each other 111 Oracle Applications Basic Operation The basic architecture of an Oracle system contains a set of base objects which are held in highly normalized core tables within the Oracle database A de normalized view of these base objects is provided in a set of Open Interface Tables OITs also maintained in the database Data is passed from the Open Interface Tables to the core tables under the control of the Concurrent Manager Figure 1 Basic Oracle Applications Operation Oracle Applications Oracle Open Interface External Table System Concurrent I Manager Oracle Applications Database In a typical scenario an operator schedules an import job by means of the Oracle front end which initiates the following procedure 1 Data is passed from the Open Interface Tables to the core tables under the control of Import Jobs scheduled by the Concurrent Manager 2 It then invokes the Oracle Concurrent Manager which Validates the data in the Open Interface Table based on a set of stored SOL procedures Inserts the validated rows into the Oracle Applications Database This highly simplified procedure is depicted in Figure 1 There are several limitations to this very basic scheme Oracle Applications eWay Intelligent
114. h field 3632 in this example to a unique number for example 3633 Oracle Applications eWay Intelligent Adapter User s Guide 79 Sun Microsystems Inc Chapter 6 Section 6 4 Implementing the Sample Projects Using the Order Import BPEL Sample 64 Using the Order Import BPEL Sample The Order Import BPEL sample project is similar to the previous sample in that the sample uses two file eWays to simulate an inbound order and forwards the order to the Oracle Applications system However rather than using a Java Collaboration the BPEL sample uses an elnsight business process to exchange data with the Oracle Applications system Additionally the results are written to one output file rather than two Figure 30 The Order Import BPEL Sample ERP gt E Oracleapps1 a POI Header Input A POI Header _IN_passthru1 aay Topic Orderlmport BPEL1 Topic2 JMS to File 2 a POI Lines IM passthru1 POI Output POI Lines Input G Sample Project Overview This document does not cover the Order Import BPEL sample in the same level of detail as the previous sample This section assumes that you have already read and worked through the Order Sample This section provides the information you need to import configure and run the Order Import BPEL Sample 1 Import the sample Project as described in Import the Order Import BPEL Sample on page 79 2 Set up the sample data on your system as described in Set up the
115. he Name attribute is used SP DEL Short Table Name For example Customer Item SP DEL MTL CI INTERFACE INT Oracle Applications eWay Intelligent Adapter User s Guide 62 Sun Microsystems Inc Chapter 5 Section 5 3 Using the OTD Wizard Exposed OTD Nodes Item Import SP DEL MTL SYSTEM ITEMS INT 534 INITIALIZE Description This optional packaged stored procedure is used to initialize the user s profile for Oracle Applications Parameters Depends upon the specific implementation Typically it accepts the Organization ID as a parameter Requirements Inside the script package this stored procedure must have the name Initialize Profile 535 MOVE Description Stored procedures for both OTD level and interface tables level are defined in the utility package If it is located at the OTD root level it copies the data from all SeeBeyond Staging Tables to the corresponding Oracle Interface Tables If itis located at the Interface Table level then the data for only that specific Staging Table is copied to its corresponding Open Interface Table This procedure acts only on records with the ID values specified Parameters Depends upon the specific implementation Typically it contains at least four input VARCHAR parameters corresponding to sb eway id sb group id sb object id sb pass or fail This parameter accepts the following values P records that have passed for records that
116. he sample header input file POImport Headers in The Oracle database does not allow multiple records with the same document number to be inserted Figure32 Input Header File POlmport Headers in POlmport_Headers in Notepad File Edit Format View Help 4026 4026 PO PENDING ORIGINAL DEFAULT STANDARD nul 1 nul 1 050153 1 11 517 GRAINGER To update the header file edit POImport_Headers in and change the ninth field 3632 in this example to a unique number for example 3633 Oracle Applications eWay Intelligent Adapter User s Guide 83 Sun Microsystems Inc Chapter 6 Section 6 5 Implementing the Sample Projects Using the Financial GL Budget JCD Sample 65 Using the Financial GL Budget JCD Sample The Financial GL Budget sample demonstrates the operation of the outbound Oracle Applications eWay by reading information from a file writing the information to the appropriate Oracle Applications tables and writing the results out to an output file Figure33 The Financial GL Budget JCD Sample ERP gt a al Oracleapps1 eaFileln File to JMS1 z Topic2 JMS to File1 D gt eaFileOut The input file represents information for a sample budget The information would typically come from an external application via another eWay or from another upstream CAPS component Note For the validation process Financial Budget GL samples use the following fields Currency Code Fiscal
117. ired IF INTEREST CHARGES IS SET TO Y AND no PROFILE class IS specified SB AR PROFILE 10120 CHARGE ON FINANCE CHARGE FLAG not required IF INTEREST CHARGES IS SET TO N OR NULL SB AR PROFILE 10121 Valid VALUES FOR AUTO REC INCL DISPUTED FLAG COLUMN are Y N SB AR PROFILE 10122 Valid VALUES FOR CONS INV FLAG COLUMN are Y N SB AR PROFILE 10123 Valid VALUES FOR CONS INV TYPE COLUMN are SUMMARY DETAIL WHEN CON INV FLAG IS Y SB AR PROFILE 10124 CURRENCY CODE required IF ANY one OF the following COLUMNS have VALUES SB AR PROFILE 10125 CURRENCY CODE does not exist IN TABLE FND CURRENCIES SB AR PROFILE 10126 CUSTOMER PROFILE CLASS NAME does not exist IN TABLE HZ CUST PROFILE CLASSES SB AR PROFILE 10127 IF COLUMN CUSTOMER PROFILE CLASS NAME IS NULL THEN enter the following COLUMNS COLLECTOR NAME CREDIT BALANCE STATEMENTS CREDIT CHECKING AUTO REC INCL DISPUTED FLAG DISCOUNT TERMS DUNNING LETTER DUNNING LETTER SET NAME INTEREST CHARGES INTEREST PERIOD DAYS CHARGE ON FINANCE CHARGE STATEMENTS STATEMENT CYCLE NAME TOLERANCE TAX PRINTING OPTION OVERRIDE TERMS GROUPING RULE NAME STATEMENTS CHARGE ON FINANCE CHARGE FLAG AUTOCASH HIERARCHY NAME SB AR PROFILE 10128 SB AR PROFILE 10129 ACCOUNT STATUS does not exist IN TABLE AR LOOKUPS AUTOCASH HIERARCHY NAME does not exist IN TABLE AUTOCASH HIERARCHIES SB AR PROFILE 10130 COLL
118. ironment 87 Create the Deployment Profile 88 Configure the Oracle Apps External System 88 Using the Financial GL Budget BPEL Sample 88 Sample Project Overview 89 Import the Financial GL Budget BPEL Sample 89 Set up the Sample Data 90 Configure the File eWays 90 Create the Environment 91 Create the Deployment Profile 91 Configure the Oracle Apps Fin BPEL External System 92 Appendix A Error Codes 93 Manufacturing 93 Inventory 93 Customer Items 93 Customer Item Cross Reference 94 Cycle Count Entries 95 Items 96 Item Revisions 99 Replenishment 99 Transactions 101 Purchase Order 102 Import 102 Receiving 106 Requisitions 110 Financial Budget GL 113 Accounts Payable 113 Accounts Receivable 115 Auto Invoice 115 Oracle Applications eWay Intelligent Adapter 6 Sun Microsystems Inc Contents Auto Lock Box 119 Customer Interface 120 Cash Management 125 Fixed Assets 126 General Ledger 128 Index 131 Oracle Applications eWay Intelligent Adapter 7 Sun Microsystems Inc Chapter 1 Introducing the Oracle Applications eWay Welcome to the Oracle Applications eWay Intelligent Adapter User s Guide This document includes information about installing configuring and using the Oracle Applications eWay Intelligent Adapter The Oracle Applications eWay Intelligent Adapter utilizes the Sun Java Composite Application Platform Suite to provide a comprehensive integration solution for the Oracle Applications Product Family included
119. is VENDOR then the item must be purchasing enabled for the purchasing and dest org id Deliver_To_Location_ID is invalid FK validation failed against Hr_Locations table SB POREQ 20171 category_id is invalid for the given item a2 Financial Budget GL A21 Accounts Payable Table 19 Accounts Payable Errors Error Code Error Message SB AP INVOICE 20000 SB AP INVOICE 20001 SB AP INVOICE 20002 INVOICE ID cannot be NULL PO NUMBER does not exist in PO HEADERS VENDOR ID does not exist in PO VENDORS SB AP INVOICE 20003 VENDOR NUM does not exist in PO VENDORS SB AP INVOICE 20004 VENDOR NAME does not exist in PO VENDORS SB AP INVOICE 20005 VENDOR SITE ID does not exist in PO VENDOR SITES SB AP INVOICE 20006 VENDOR SITE CODE does not exist in PO VENDOR SITES SB AP INVOICE 20007 SB AP INVOICE 20008 INVOICE CURRENCY CODE does not exist in FND CURRENCIES EXCHANGE RATE TYPE does not exist in GL DAILY CONVERSION TYPES SB AP INVOICE 20009 TERMS 10 does not exist in AP TERMS SB AP INVOICE 20010 TERMS NAME does not exist in AP TERMS SB AP INVOICE 20011 AWT GROUP ID does not exist in AP AWT GROUPS SB AP INVOICE 20012 SB AP INVOICE 20013 SB AP INVOICE 20020 AWT GROUP NAME does not exist in AP GROUPS PREPAY NUM does not exist in AP INVOICES INVOICE TYPE LOOKUP CODE does not exist in AP LOOKUP CODES Oracle Applications eWa
120. is by selecting Replace Existing Stored Procedures Otherwise the existing stored procedures are not overwritten an error appears and the wizard stops 5 Typea name for the OTD to be created and click Next Oracle Applications eWay Intelligent Adapter User s Guide 58 Sun Microsystems Inc Chapter 5 Section 5 2 Using the OTD Wizard Creating OTDs Figure 12 Specify the Name Specify the OTD Name Select Wizard Type Connectto Database OTD Name Select Oracle Applications module Specify the OTD Name Review Selections 6 Click Finish to begin generating the OTD The time it takes the OTD to generate depends on the module you selected and your system performance Figure 13 Review Your Selections Review your Selections Select Wizard Type You have successfully completed the Database Wizard Please Connectto Database review your selections Select Oracle Applications module Connection Information ou aca Review Selections Port ID 1523 SID VIS Username apps Oracle Application Information ORACLE APPLICATIONS 11 5 3 Financial Auto Invoice To close this wizard click Finish e E Can The generated OTD appears in the OTD Editor Nodes and methods for your OTD depend on the module you selected and the configuration of your tables Oracle Applications eWay Intelligent Adapter User s Guide 59 Sun Microsystems Inc Chapter 5 Section 5 3 Using the OTD W
121. is invalid SB POIMP 20012 Ship To Location ID is invalid SB POIMP 20013 Terms ID is invalid SB POIMP 20014 SB POIMP 20015 Ussgl Transaction Code is invalid Buyer specified is invalid SB POIMP 20016 Bill To Location ID is invalid SB POIMP 20017 Vendor Site ID is invalid SB POIMP 20018 Vendor Contact ID is invalid SB POIMP 20019 From Header ID is invalid SB POIMP 20020 Rate Type is invalid SB POIMP 20021 Currency Code is invalid SB POIMP 20022 Document Number is invalid SB POIMP 20023 Buyer Name is invalid SB POIMP 20024 Vendor Name or Vendor Num is invalid SB POIMP 20025 Vendor Site Code is invalid SB POIMP 20026 Vendor Contact is invalid SB POIMP 20027 Ship To Location Code is invalid SB POIMP 20028 Bill To Location Code is invalid SB POIMP 20029 Payment Terms is invalid SB POIMP 20030 Rfq Num is invalid SB POIMP 20031 Amount Limit is less than Amount Agreed SB POIMP 20032 Amount Limit is less than Min Release Amount SB POIMP 20033 Amount Limit is less than Zero SB POIMP 20088 Release Number is invalid SB POIMP 25007 Document Type is Standard so Action cannot be Update or Replace SB POIMP 25008 Document Type is Standard so Approval Status must be Incomplete SB POIMP 25009 Vendor Doc Num does not exist SB POIMP 250
122. ith a red padlock in the bottom left corner of each icon Before you can deploy the imported Project the Project s components must first be checked out of Version Control from both the Project Explorer and the Environment Explorer To check out all of the Project s components do the following A From the Project Explorer right click the Project and select Version Control gt Check Out from the shortcut menu The Version Control Check Out dialog box appears B Select Recurse Project to specify all components and click OK C Select the Environment Explorer tab and from the Environment Explorer right click the Project s Environment and select Version Control Check Out from the shortcut menu D Select Recurse Environment to specify all components and click OK 14 If your imported Project includes File eWay External Systems in the Environment the Project s Environment must be reconfigured prior to deploying the Project To reconfigure your Environment do the following A The properties file for the File External System now includes both inbound and outbound properties If your Environment includes both inbound and outbound File External Systems these can now be combined Delete all but one of the File External Systems B From the Environment Explorer tree right click your remaining File External System and select Properties from the shortcut menu The Properties Editor appears C Setthe inbound and outbound directory va
123. izard Exposed OTD Nodes Figure 14 Finished Object Type Definition D zjReference I Refarence Ohject Type Definition Properties A Custo ner Item X Ref Cust Tt SB_MTL_CI_XREFS_INTERFACE j Internal External o 33 MOVE krue a XS d am DELETE Customer Item lees r ii Gd COUNT Customer Item E INITIALIZE i G E REQUEST ies REQUEST_STATUS 3 methods gt Customer Item X Ref 53 Exposed OTD Nodes 531 Staging Table Node This node represents the SeeBeyond Staging Table created inside the Oracle database columns in the table are exposed and can be dragged and dropped in the Java Collaboration The node has a name of the form SB Oracle Interface Table name having a maximum length of 30 characters The Staging Table is created from the Interface Table with the following six extra fields used to support the pre validation process SB EWAY ID SB GROUP ID SB OBJECT ID SB PASS OR FAIL SB ERROR CODE SB ERROR MESSAGE of the ID fields the first three fields shown above are used for pre validation purposes within CAPS 532 COUNT Description Stored procedures for both the OTD level and the interface tables level are defined in the utility package Oracle Applications eWay Intelligent Adapter User s Guide 60 Sun Microsystems Inc Chapter 5 Section 5 3 Using the OTD Wizard Exposed OTD Nodes If it is located
124. ld displays a submenu of property options 4 Clickon the ellipsis in the properties field to open a separate configuration dialog box This is helpful for large values that cannot be fully displayed in the parameter s property field Enter the property value in the dialog box and click OK The value is now displayed in the property field 5 After modifying the configuration properties click OK to close the Properties Editor and save your changes 32 Oracle Applications eWay Connectivity Map Properties The Oracle Applications eWay configuration parameters accessed from the Connectivity Map are organized into the following sections Properties in the Outbound eWay on page 28 Properties in the Outbound eWay with XA Support on page 29 Properties in the Outbound eWay The JDBC Connector Settings section of the Oracle Applications Connectivity Map properties contains the top level parameters displayed in Table 3 Oracle Applications eWay Intelligent Adapter User s Guide 28 Sun Microsystems Inc Chapter 3 Section 3 3 Configuring the Oracle Applications eWay Oracle Applications eWay Environment Configuration Properties Table3 Outbound Connectivity Map JDBC Connector Settings Name Description Required Value Description Specifies the description for the database A valid string The default is Oracle thin driver Connection Pool Datasource ClassName Specifies the Java class in the JDBC driver A valid class nam
125. lues and click OK 15 Deploy your Projects 251 Database Migration Issues Projects imported from previous ICAN versions can potentially display different results depending on whether the 5 0 x Java Collaboration Definition JCD included multiple insert update delete operations This only affects non XA transactions If you are using an XA transaction then you can skip this section Oracle Applications eWay Intelligent Adapter 20 Sun Microsystems Inc Chapter 2 Installing the Oracle Applications Section 2 5 ICAN 5 0 Project Migration Procedures Example In 5 0 x five new records are to be inserted into a table If one of the records fails to insert like having a duplicate key all five records will not be inserted In 5 1 2 five new records are to be inserted into a table If one of the records fails to insert like having a duplicate key the other four records will be inserted In order to achieve the same result as in 5 0 x ICAN versions you can choose one of the methods below 1 2 3 If 1 5 In the Connectivity Map delete the link to the database external application then reconnect the link and select XA Fill in the XA property for the database external system under the Environment Rebuild the Project you want to keep the non XA transaction the following changes are required Add a setAutoCommit method and set it to false before inserting any records If you are using a while loop then add
126. mit catch java sql SQLException sqle UniqueTable 1 rollback 21 Sun Microsystems Inc Chapter 2 Section 2 6 Installing the Oracle Applications Installing Enterprise Manager eWay Plug Ins 26 Installing Enterprise Manager eWay Plug Ins The Sun SeeBeyond Enterprise Manager is a Web based interface that allows you to monitor and manage your Composite Application Platform Suite applications The Enterprise Manager requires an eWay specific plug in for each different eWay you install These plug ins enable the Enterprise Manager to target specific alert codes for each eWay type as well as to start and stop the inbound eWays The Sun Java Composite Application Platform Suite Installation Guide describes how to install Enterprise Manager The Sun SeeBeyond eGate Integrator System Administration Guide describes how to monitor servers Services logs and alerts using the Enterprise Manager and the command line client The eWay Enterprise Manager plug ins are available from the List of Components to Download under the Composite Application Platform Suite Installer s DOWNLOADS tab There are two ways to add the eWay Enterprise Manager plug ins From the Sun SeeBeyond Enterprise Manager From the Sun Java Composite Application Platform Suite Installer To add plug ins from the Enterprise Manager 1 From the Enterprise Manager s Explorer toolbar click configuration 2 Click the Web Applications Manager tab go to the Auto I
127. mns are invalid SB INVCIT 25316 Commodity code is inactive SB INVCIT 25317 Constainer item org id is invalid SB INVCIT 25318 Inactive flag has invalid value SB INVCIT 25319 Container org code is invalid SB INVCIT 25320 Container org name is invalid SB INVCIT 25321 Demand tolerance positive value is invalid SB INVCIT 25322 Demand tolerance negative value is invalid SB INVCIT 25323 Min Fill Percentage is invalid SB INVCIT 25324 Departure plan required flag is invalid SB INVCIT 25325 Departure plan build flag is invalid SB INVCIT 25326 Departure plan flags combination is invalid Customer Item Cross Reference Table 2 Customer Item Cross Reference Errors Error Code Error Message SB INVCCR 22601 Process_flag is mandatory and the current value is NULL SB INVCCR 22602 Process_mode is mandatory and the current value is NULL SB INVCCR 22603 Last_update_date is mandatory and the current value is NULL SB INVCCR 22604 Last_updated_by is mandatory and the current value is NULL SB INVCCR 22605 SB INVCCR 22606 Creation_date is mandatory and the current value is NULL Created_by is mandatory and the current value is NULL Oracle Applications eWay Intelligent Adapter User s Guide 94 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table2 Custome
128. n ORIG SYSTEM SHIP ADDRESS ID SB AR LINES 10673 Enter the appropriate value in ORIG SYSTEM SHIP ADDRESS REF SB AR LINES 10674 Enter the appropriate value in ORIG SYSTEM SHIP CONTACT ID SB AR LINES 10675 Enter the appropriate value in ORIG_SYSTEM_SHIP_CONTACT_REF SB AR LINES 10676 ORIG_SYSTEM_SHIP_CUSTOMER_ID value should match with CUST ACCOUNT ID value of HZ_CUST_ACCOUNTS Table SB AR LINES 10677 ORIG SYSTEM SHIP CUSTOMER REF value should match with ORIG SYSTEM REFERENCE value of HZ CUST ACCOUNTS Table SB AR LINES 10678 ORIG SYSTEM SOLD CUSTOMER ID value should match with CUST ACCOUNT ID value of HZ CUST ACCOUNTS Table SB AR LINES 10679 ORIG_SYSTEM_SOLD_CUSTOMER_REF value should match with ORIG_SYSTEM_REFERENCE value of HZ_CUST_ACCOUNTS Table SB AR LINES 10680 PRIMARY_SALESREP_ID value should match with SALESREP_ID value of RA_SALESREPS Table SB AR LINES 10681 PRIMARY_SALESREP_NUMBER value should match with SALESREP_NUMBER value of RA_SALESREPS Table SB AR LINES 10682 PRINTING_OPTION value should match with LOOKUP_CODE value of AR_LOOKUPS Table SB AR LINES 10683 REASON_CODE value should match with LOOKUP_CODE value of AR_LOOKUPS Table SB AR LINES 10684 REASON_CODE_MEANING value should match with MEANING value of AR_LOOKUPS Table SB AR LINES 10685 RECEIPT METHOD ID value should match with RECEIPT METHOD ID value of AR RECEIPT MET
129. ncurrent Manager basically the return value from REQUEST INp interval sec IN NUMBER The interval in seconds for the program to query for the result of a Concurrent Manager request INp maximum sec IN NUMBER The maximum allowed interval in seconds for the program to time out This parameter must have a non zero value OUTp detailed status OUT VARCHAR2 Oracle Applications eWay Intelligent Adapter User s Guide 64 Sun Microsystems Inc Chapter 5 Section 5 3 Using the OTD Wizard Exposed OTD Nodes Output parameter having the detailed description of the concurrent request Requirements In order for Request Status to correctly retrieve the Concurrent Manager request you must call commit after the Request stored procedure call otherwise Request Status always returns Pending status after a time out 538 VALIDATE Description This packaged stored procedure is used to perform the pre validation of data in the Staging Table If it is located at the OTD root level the data in all Staging Tables is validated If it is located at the Staging Table level only the data in that specific Staging Table is validated Parameters Depends upon specific implementation By default it contains three input VARCHAR parameters corresponding to sb eway id sb group id sb object id sb pass or fail Requirements Inside the script package this stored procedure must have the name VALIDATE Oracle Applications eWa
130. ncy Code value present Rate Date and Rate Type are mandatory SB POREQ 20110 If Project Accounting Context is Y then you must enter relevent project accounting info like project id task id expenditure type and expenditure org id SB POREQ 20111 If Destination Type code is INVENTORY then you must enter Destination Subinventory and Item ID SB POREQ 20112 If Source Type Code is INVENTORY then you must enter Item ID SB POREQ 20113 If Destination Type Code is EXPENSE or SHOP FLOOR then you must Source Type Code SB POREQ 20114 Requisition Type value either INTERNAL or PURCHASE SB POREQ 20115 Requisition Header ID is invalid FK validation failed against po requisition headers all table Oracle Applications eWay Intelligent Adapter User s Guide 110 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 18 Requisition Errors Error Code Error Message SB POREQ 20116 Category ID is invalid FK validation failed against mtl_categories_b table SB POREQ 20117 Unit_Of_Measure is invalid FK validation failed against mtl_units_of_measure_tl table SB POREQ 20118 Line_Type_ID is invalid FK validation failed against po_line_types_b table SB POREQ 20119 UN_Number_ID is invalid FK validation failed against po_un_numbers_b table SB POREQ 20120 Hazard_Class_ID is invalid FK validation failed against po_hazard_classes_b tabl
131. nfigure the components similar to those shown in Figures 22 through 27 skipping figure 26 since there is only one outbound file eWay Configure the Oracle Apps BPEL External System In the Environment Explorer configure the Oracle Apps BPEL external system the same way it is configured in Configure the Oracle Apps External System on page 76 647 Running the Sample Project Additional steps are required to run the deployed sample Project Steps required to run the sample Project 1 Rename one of the trigger files included in the sample Project from lt filename gt in in to lt filename gt in to run the corresponding operation The File eWay polls the directory every five seconds for the input file name as defined in the Inbound File eWay Properties window The data is then transformed and the File eWay sends the output to an Output file name as defined in the outbound File eWay Properties window Oracle Applications eWay Intelligent Adapter User s Guide 82 Sun Microsystems Inc Chapter 6 Section 6 4 Implementing the Sample Projects Using the Order Import BPEL Sample 2 Verify the output data by viewing the sample output files The output files may change depending on the number of times you execute the sample Project and the content of the input files Re running the sample Because the document number field in the back end database has a unique constraint you cannot re run the sample project without modifying t
132. ng the file using Enterprise Designer Copying the file directly into the Logical Host Extracting the Sample Projects and Javadocs The Oracle Applications eWay includes sample Projects and Javadocs The sample Projects are designed to provide you with a basic understanding of how certain database operations are performed using the eWay while Javadocs provide a list of classes and methods exposed in the eWay Steps to extract the Javadoc include 1 2 3 4 Click the Documentation tab of the Suite Installer then click the Add ons tab Click the Oracle Applications eWay Intelligent Adapter link Documentation for the Oracle Applications eWay appears in the right pane Click the icon next to Javadoc and extract the ZIP file Open the index html file to view the Javadoc Steps to extract the Sample Projects include 1 Click the Documentation tab of the Suite Installer then click the Add ons tab Oracle Applications eWay Intelligent Adapter 18 Sun Microsystems Inc Chapter 2 Section 2 5 Installing the Oracle Applications ICAN 5 0 Project Migration Procedures 2 Click the Oracle Applications eWay Intelligent Adapter link Documentation for the Oracle Applications eWay appears in the right pane 3 Click the icon next to Sample Projects and extract the ZIP file Note that the Oracle Applications eWay Sample zip file contains two additional ZIP files for each sample Project Refer to Importing a Sample Project on page 69
133. nificant changes to the database would affect the data dictionary like new tables indexes etc You should consider running the analysis regularly Important Please consult your Database Administrator or Oracle before taking these steps as it may impact other applications 52 Creating OTDs To create an OTD using the Oracle Applications Database Wizard 1 In the Enterprise Designer Project Explorer right click your Project click New and then click Object Type Definition The Object Type Definition Wizard appears Oracle Applications eWay Intelligent Adapter User s Guide 55 Sun Microsystems Inc Chapter 5 Using the OTD Wizard Figure 9 Select Wizard Type Select Wizard Type OTD Wizard Description User Defined OTD Allows the userto create a custom OTD UD OTD from file Uses a textfile to create a custom OTD XSD Uses an XSD to create an OTD lt Back Finish Cancel 2 Click Oracle Applications Database and then click Next Section 5 2 Creating OTDs 3 Type the Host Name Port ID SID User name and Password and click Next Table 10 Database Connection Information Connection Information Description Host Name The name or IP address of the Oracle server Port ID The port on which the server is listening for connections SID The Oracle System Identifier SID User Name The user name used to connect to the Oracle server Password The password used to
134. nstall from Repository tab and connect to your Repository 3 Select the application plug ins you require and click Install The application plug ins are installed and deployed To add plug ins from the Sun Java Composite Application Platform Suite Installer 1 From the Sun Java Composite Application Platform Suite Installer s Download tab select the Plug Ins you require and save them to a temporary directory 2 From the Enterprise Manager s Explorer toolbar click configuration 3 Click the Web Applications Manager tab and go to the Manage Applications sub tab 4 Browse for and select the WAR file for the application plug in that you downloaded and click Deploy The plug in is installed and deployed Viewing Alert Codes You can view and delete alerts using the Enterprise Manager An alert is triggered when a specified condition occurs in a Project component The purpose of the alert is to warn the administrator or user that a condition has occurred To View the eWay Alert Codes 1 Add the eWay Enterprise Manager plug in for this eWay 2 From the Enterprise Manager s Explorer toolbar click configuration Oracle Applications eWay Intelligent Adapter 22 Sun Microsystems Inc Chapter 2 Installing the Oracle Applications Section 2 6 Installing Enterprise Manager eWay Plug Ins 3 Click the Web Applications Manager tab and go to the Manage Alert Codes tab 4 Browse for and select the Alert Properties File for the applic
135. ode Error Message SB POREC 25006 Header has lines that have failed validation Headers Table 16 Receiving Header Errors Error Code Error Message SB POREC 20100 Header Interface ID field is mandatory in RCV HEADERS INTERFACE table and current value is null SB POREC 20101 Group ID field is mandatory in RCV HEADERS INTERFACE table and current value is null SB POREC 20102 Processing Status Code field is mandatory in RCV HEADERS INTERFACE table and current value is null SB POREC 20103 Receipt Source Code field is mandatory in RCV HEADERS INTERFACE table and current value is null SB POREC 20104 Transaction Type field is mandatory in RCV HEADERS INTERFACE table and current value is null SB POREC 20105 Value Required in Vendor Name or Vendor Num field in RCV HEADERS INTERFACE table and current value is null Oracle Applications eWay Intelligent Adapter User s Guide 106 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 16 Receiving Header Errors Error Code Error Message SB POREC 20106 Validation Flag is mandatory in RCV HEADERS INTERFACE table and current value is null SB POREC 20107 ASN TYPE field in RCV HEADERS INTERFACE must be ASN or ASBN SB POREC 20108 Processing Status Code field in RCV HEADERS INTERFACE must be PENDING SB POREC 20109 Receipt Source Code field
136. ode field is mandatory in rcv transactions interface table and current value is null SB POREC 20133 Vendor Site ID field is mandatory in rcv transactions interface table and current value is null SB POREC 20134 Value required in either Vendor Name or Vendor Num fields in rcv transactions interface table and currently both are null SB POREC 20135 Source Document Code field is mandatory in rcv transactions interface table and current value is null SB POREC 20136 Value required in Document Num or Po Header ID and currently both are null SB POREC 20137 Header Interface ID field is mandatory in rcv transactions interface table and current value is null SB POREC 20138 Validation Flag field is mandatory in rcv transactions interface table and current value is null SB POREC 20139 FK Validation Invalid Routing Header ID SB POREC 20140 FK Validation Invalid Routing Step ID SB POREC 20141 FK Validation Invalid Parent Transaction ID SB POREC 20142 FK Validation Invalid Po Header ID SB POREC 20143 FK Validation Invalid Po Line ID SB POREC 20144 FK Validation Invalid Po Line Location ID SB POREC 20145 FK Validation Invalid Inv Transaction ID SB POREC 20146 FK Validation Invalid Po Distribution ID SB POREC 20147 FK Validation Invalid Po Release ID SB POREC 20148 SB POREC 20149 Foreign Key Validation Invalid
137. ode is mandatory and the current value is NULL SB INVREP 22310 Process Status is mandatory and the current value is NULL SB INVREP 22311 Process Mode is mandatory and the current value is NULL SB INVREP 22312 Organization ID is invalid Oracle Applications eWay Intelligent Adapter User s Guide 99 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table7 Replenishment Header Errors Error Code Error Message SB INVREP 22313 SubInventory Code is invalid SB INVREP 22314 Error_Flag is invalid SB INVREP 22315 Process_Mode is invalid SB INVREP 22316 Process_ Status is invalid SB INVREP 22317 Replenish_Header is invalid SB INVREP 22318 Replenish_Count is invalid SB INVREP 22319 Last_Update is invalid SB INVREP 22320 Lines is invalid Lines Table 8 Replenishment Line Errors Error Code Error Message SB INVREP 22401 Replenishment_Header_ID is mandatory and the current value is NULL SB INVREP 22402 Replenishment_Line_ID is mandatory and the current value is NULL SB INVREP 22403 Last_Update_Date is mandatory and the current value is NULL SB INVREP 22404 Creation_Date is mandatory and the current value is NULL SB INVREP 22405 Created_By is mandatory and the current value is NULL SB INVREP 22406 Last_Update_Login is mandatory and the current value is NULL SB INVR
138. ojects Using the Financial GL Budget BPEL Sample To download the sample from the Enterprise Manager 1 From the Documentation page of your Enterprise Manager click the link for the Oracle Applications eWay Intelligent Adapter The Oracle Applications documentation page appears 2 Click Download Sample 3 When you are prompted to open or save the file click Open The sample zip file opens in WinZip 4 Use WinZip to extract the Oracle Applications eWay Sample zip files to a location on your local file system such as C NCAPS SamplesNOraA pps Make a note of where you extracted the files To import the sample in the Enterprise Designer 1 Inthe Enterprise Designer right click your Repository and click Import 2 Click Yes to save any changes to your Repository The Import Manager appears 3 Click Browse and navigate to the location where you downloaded the sample files in step 4 of the previous procedure In the JCD folder select the prjOraApp Fin BudgetGL BP Sample zip file and click Open 662 Set up the Sample Data Use Windows Explorer to extract the input files input files zip to a convenient location for example CNCAPS SamplesNOraAppsNBPEL input files Also create a directory for the output files for example C CAPS_Samples OraApps BPEL output Make a note of the location where you extracted these files 663 Configure the File eWays In the Connectivity Map configure the inbound file eWay and the outbound file eWay Fo
139. olumn Enter a valid value SB AR PROFILE 10103 LAST UPDATED BY is a required column Enter a valid value SB AR PROFILE 10104 LAST UPDATE DATE is a required column Enter a valid value SB AR PROFILE 10105 CREATION DATE is a required column Enter a valid value SB AR PROFILE 10106 CREATED BY is a required column Enter a valid value SB AR PROFILE 10108 Valid values for CREDIT BALANCE STATEMENTS column are Y N SB AR PROFILE 10109 CREDIT BALANCE STATEMENTS must be N when STATEMENTS N Mandatory when STATEMENTS zY Must be null when STATEMENTS is null SB AR PROFILE 10111 Valid VALUES FOR CREDIT CHECKING COLUMN are Y N SB AR PROFILE 10112 Valid VALUES FOR CREDIT HOLD COLUMN are Y N SB AR PROFILE 10113 Valid VALUES FOR DISCOUNT TERMS COLUMN are Y N SB AR PROFILE 10114 Valid VALUES FOR DUNNING LETTERS COLUMN are Y N SB AR PROFILE 10115 SB AR PROFILE 10116 Valid VALUES FOR INTEREST CHARGES COLUMN Valid VALUES FOR STATEMENTS COLUMN are Y N Oracle Applications eWay Intelligent Adapter User s Guide 123 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 22 Customer Interface Errors Error Code Error Message SB AR PROFILE 10117 Valid VALUES FOR OVERRIDE TERMS COLUMN Y N SB AR PROFILE 10118 Valid VALUES FOR CHARGE ON FINANCE CHARGE FLAG COLUMN are Y N Requ
140. onment and click New Oracleapps External System with the following settings External System Name Oracle Apps External System Type Outbound Oracle Applications eWay 4 Right click the Orcl Apps JCD Environment and click New File External System Create four File External Systems Inbound and Outbound File eWays with the settings found in the following table Table 12 Orcl Apps Environment Name External System Type LogicalHost1 Logical Host IntegrationSvr1 Sun SeeBeyond Integration Server SBJmsIOMgr Sun SeeBeyond JMS IQ Manager Oracle Apps Outbound Oracle Applications eWay Header In Inbound File eWay Lines In Inbound File eWay Header Out Outbound File eWay Lines Out Outbound File eWay 5 Right click the Orcl Apps JCD Environment and click New Logical Host A new Logical Host LogicalHost1 appears 6 Right click LogicalHost1 and click New Sun SeeBeyond Integration Server A new Integration Server IntegrationSvr1 appears 7 Right click LogicalHost1 and click New Sun SeeBeyond JMS IO Manager A new Integration Server SBJmsIQMgr1 appears The completed Environment must look like the one shown in the following figure Oracle Applications eWay Intelligent Adapter User s Guide 74 Sun Microsystems Inc Chapter 6 Implementing the Sample Projects Section 6 3 Using the Order Import JCD Sample Figure 20 Orcl Apps JCD Environment MyRepository Orcl Apps JCE m Oracle Ap
141. ort Table Name Stored Procedures Staging Table Node SQL File Name Concurrent Manager Request Function Chapter 5 Using the OTD Wizard Oracle Applications OTD Wizard Overview Creating OTDs Exposed OTD Nodes Staging Table Node COUNT DELETE INITIALIZE MOVE REQUEST REQUEST STATUS VALIDATE Chapter 6 Implementing the Sample Projects About the Oracle Applications Sample Projects About the elnsight Engine and eGate Components Exchanging Data with Oracle Applications Using the Order Import JCD Sample Sample Project Overview Import the Order Import JCD Sample Set up the Sample Data Configure the File eWays Create the Environment Create the Deployment Profile Oracle Applications eWay Intelligent Adapter 5 54 54 55 60 60 60 62 63 63 64 64 65 66 66 67 67 70 70 71 72 73 74 75 Sun Microsystems Inc Contents Configure the Oracle Apps External System 77 Deploying the Project 78 Running the Sample Project 79 Using the Order Import BPEL Sample 80 Sample Project Overview 80 Import the Order Import BPEL Sample 80 Set up the Sample Data 81 Configure the File eWays 81 Create the Environment 81 Create the Deployment Profile 82 Configure the Oracle Apps BPEL External System 82 Running the Sample Project 82 Using the Financial GL Budget JCD Sample 84 Sample Project Overview 84 Import the Financial GL Budget JCD Sample 85 Set up the Sample Data 86 Configure the File eWays 86 Create the Env
142. ory CAPS Dir edesigner userdir modules ext oracleappsadapter wizard configs business function name moduleDefinition xml where business function name is the name attribute value for example either Manufacturing or Financial While the template XML file does not have an error package or error table entries you can look at any existing module to create these entries If you choose to modify the common sb install sql file to append more errors for the new module the SB ERRORS table needs to be removed from the database so the wizard can recreate it with new error values the next time the wizard is run 3 Replace the ORACLE INTERFACE NAMESS with the correct open interface name Do not use spaces when creating an ORACLE INTERFACE NAME 4 Replace the ORACLE APPLICATION SUITE NAME gt with the correct business suite name 5 Replace the MODULE NAMESS with the correct module name Do not use spaces when creating a MODULE NAME 6 Theinitialize and request status scripts are already specified in the XML file If you do not need these simply remove them from the XML file If you need to customize these scripts D Copy the SOL file to the desired directory Oracle Applications eWay Intelligent Adapter User s Guide 49 Sun Microsystems Inc Chapter 4 Section 4 4 Pre Validation Process Building a Custom Pre Validation Package Rename the file the package name must be the same as the SQL file name which is tru
143. ot exists in GL JE CATEGORIES table SB GL INTERFACE 40221 USER JE SOURCE NAME does not exists in GL JE SOURCES table SB GL INTERFACE 40222 PERIOD NAME does not exists in GL PERIODS table SB GL INTERFACE 40223 USSGL TRANSACTION CODE does not exists in GL USSGL TRANSACTION CODES table SB GL INTERFACE 40224 ACTUAL FLAG should be either A Actual B Budget E Encumbrance SB GL INTERFACE 40225 SB GL INTERFACE 40226 AVERAGE JOURNAL FLAG should be either Y Yes N No CURRENCY CONVERSION RATE should be entered for USER CURRENCY CONVERSION TYPE User SB GL INTERFACE 40227 CURRENCY CONVERSION DATE should be entered for USER CURRENCY CONVERSION TYPE User Oracle Applications eWay Intelligent Adapter User s Guide 130 Sun Microsystems Inc Index Index A Adding eWay to existing Installation 17 C Concurrent Manager Request Function 51 ConnectionPoolDataSource 29 conventions text 14 COUNT OTD node 60 D Data Type Definition DYD Template 51 DELETE OTD node 62 E eWays creating 26 Plug Ins 22 Exposed OTD Nodes COUNT 60 DELETE 62 INITIALIZE 63 MOVE 63 REQUEST 64 REQUEST STATUS 64 Staging Table Node 60 VALIDATE 65 External Application creating 26 INITIALIZE OTD node 63 Installation Adding eWay to an existing installation 17 Plug Ins 22 Installing Repository on UNIX 16 M Migration Procedures 19 Oracle Applications eWay Intelligent Ad
144. p Oracle Applications eWays are located between a Oracle Applications External Application and a Service Services are containers for Collaborations Business Processes eTL processes and so forth To create the Oracle Applications External Application 1 From the Connectivity Map toolbar click the External Applications icon 2 Select the Oracle Applications External Application from the menu see Figure 3 The selected Oracle Applications External Application icon now appears on the Connectivity Map toolbar Figure3 External Application menu i oe Boe E ADABAS External Application fe File External Application O f Scheduler L1 VSAM External Application 3 Drag the new Oracle Applications External Application from the toolbar onto the Connectivity Map canvas This icon now represents an external Oracle Applications system From the Connectivity Map you can associate bind the External Application to the Service to establish an eWay see Figure 4 Figure 4 eWay Location gt Service1 OracleApps Oracle Applications eWay When Oracle Applications is selected as the External Application it automatically applies the default Oracle Applications eWay properties provided by the OTD to the eWay that connects it with the Service These properties can then be or modified for your specific system using the Properties Editor 312 Configuring the Oracle Appli
145. perties Properties in the Outbound eWay Properties in the Outbound eWay with XA Support Oracle Applications eWay Environment Configuration Properties Outbound Oracle eWay Properties JDBC Connector Settings Connection Retry Settings Outbound Oracle eWay Properties with XA support JDBC Connector Settings with XA support Connection Retry Settings with XA support 25 25 26 26 27 28 28 29 29 30 31 32 32 33 Chapter 4 Pre Validation Process Overview Pre Validation Scripts Pre Validation Procedures Common Procedures Manufacturing Module Inventory Module Customer Items Customer Items Cross Reference Cycle Count Entries Items and Item Revisions Replenishment Transactions Purchase Order Import Module Purchase Order Import Purchase Order Receiving Purchase Order Requisitions Order Entry Module Financial Module Accounts Payable Module Accounts Payable Accounts Receivable Module Auto Invoice Auto Lock Customers Cash Management Module Bank Statement Fixed Assets Module Oracle Applications eWay Intelligent Adapter 4 35 35 36 36 37 37 37 37 38 38 39 39 40 40 40 41 41 42 42 42 43 43 44 44 45 45 46 Sun Microsystems Inc Contents Categories Locations Mass Additions General Ledger Module Budget Daily Rates Journal Building a Custom Pre Validation Package Concurrent Manager Request Function Template DTD Naming Conventions Oracle Interface Name Sh
146. pic3 amp Ed 8 21 EER 8 ESTEDIDED Deployment 3 Drag the components to their corresponding Logical Host or external systems as shown in the following figures Figure 22 through Figure 27 Figure 22 Oracle Apps Deployment Figure 23 Header In Deployment Oracle Applications eWay Intelligent Adapter User s Guide 76 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample Figure 24 Lines In Deployment Figure25 Header Out Deployment Figure26 Lines Out Deployment Figure 27 LogicalHost1 Deployment POI Header IN passthru1 hb JMS to Filet 15 POI Lines IN passthru1 hab 5 to File2 L Lb Order Importi SBJmslGMgr1 POI Header IN passthru1 Topic 7 2 gt JMS to Filet 0 POI Lines IN passthru1 gt Topic1 Topic3 JMS to File2 Topict gt Order Import Order Importt gt Topic2 Order Import gt Topic3 63 6 Configure the Oracle Apps External System To configure the Oracle Apps External System 1 In the Environment Explorer tab of the Enterprise Explorer right click the Oracle Apps external application and click Properties Oracle Applications eWay Intelligent Adapter User s Guide 77 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample Figure 28 The Oracle Apps External System Envi
147. ps s Header In Lines In Header Out Lines Out LogicalHostt E IntegrationSvr1 SBJmslQMgr1 Project Explorer x Environment Explorer Ord Apps JCE IntegrationSyr1 SBJmsliGMgr1 635 Create the Deployment Profile To create the Deployment Profile 1 In the Project Explorer pane of the Enterprise Explorer right click the Project click New and click Deployment Profile 2 Name the Deployment Profile Deploymentl select the Orcl Apps JCD Environment and click OK The Deployment Profile displays all of the components to be deployed as well as the Logical Host and the external systems Oracle Applications eWay Intelligent Adapter User s Guide 75 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample Figure 21 New Deployment Profile Environment Orc Apps JCD 8 g amp Map Variables f Build X Deploy feb POI Header IN passthru1 m ce m A POI Lines IN passthru1 JMS to File2 Order Import1 0 POI Header Input POI Header IN passthru1 POI Header IN passthru1 gt Topic1 2 gt JMS to File JMS to File1 gt POI Header Output POI Lines Input POI Lines IN passthru1 POI Lines IN passthru1 Topic1 Topic3 JMS to File2 JMS to File2 POI Lines Output Topic1 gt Order Importi Order Import gt Oracleapps1 Order Import1 gt Topic2 Order Import gt To
148. r Item Cross Reference Errors Error Code Error Message SB INVCCR 22607 Transaction Type is mandatory and the current value is NULL SB INVCCR 22608 Cust Item Number is mandatory and the current value is NULL SB INVCCR 22609 Preference Number is mandatory and the current value is NULL SB INVCCR 22610 Inactive flag is mandatory and the current value is NULL SB INVCCR 22611 Lock flag is mandatory and the current value is NULL SB INVCCR 22612 Cust Category is mandatory and the current value is NULL SB INVCCR 22613 Address is mandatory and the current value is NULL SB INVCCR 22614 Item Def Level is mandatory and the current value is NULL SB INVCCR 22615 Customer is mandatory and the current value is NULL SB INVCCR 22616 Customer ID is invalid SB INVCCR 22617 SB INVCCR 22618 Customer No is invalid Customer Name is invalid SB INVCCR 22619 Address Valid is invalid SB INVCCR 22620 Cust Cat Codeis invalid SB INVCCR 22621 Customer item id is invalid SB INVCCR 22622 Master Organization id is invalid SB INVCCR 22623 Inventory Item id is invalid SB INVCCR 22624 Inactive Flag is invalid Cycle Count Entries Table3 Cycle Count Entry Errors Error Code Error Message SB INVCCE 23301 CC ENTRY INTERFACE ID is mandatory and the current value is NULL SB INVCCE 23302
149. r each of these eWays enter the directory where the eWay reads the input or writes the output Figure 38 The File eWays Inbound eWay Outbound eWay x Oracleapps1 eaFileln File_to_JMS1 1 BudgetGL BP1 eaFileOut aj Topic2 JMS to File1 Oracle Applications eWay Intelligent Adapter User s Guide 90 Sun Microsystems Inc Chapter 6 Section 6 6 Implementing the Sample Projects Using the Financial GL Budget BPEL Sample 664 Create the Environment In the Environment Explorer create a new Environment and add the following items Table 15 Orcl Apps BPEL Environment Name External System Type LogicalHost1 Logical Host IntegrationSvr1 Sun SeeBeyond Integration Server SBJmsIQMgr Sun SeeBeyond JMS IQ Manager Oracleapps1 Outbound Oracle Applications eWay FilelN Inbound File eWay FileOUT Outbound File eWay The Environment will look like the one in the following diagram Figure 39 Orcl Apps Fin BPEL Environment File Tools View Window Help ema Repository Environment1 Orci Apps JCE Orcl Apps BPEL BR Orci Apps Fin JCE Oracle Apps BPEL SS IntegrationSvr1 LogicalHost SBJmslaMgr IntegrationSvr1 SBJmslQMgr FilelN FileOUT Orcl_Apps_Fin_BPEL Project Explorer x Environment Explorer Orcl Apps Fin JCE x Orcl Apps BPEL x 665 Create the Deployment Profile In the Project Explorer creat
150. racle thin driver Con O Connection Retry Settings ServerName Outbound Oracle Applications XA eWay e JDBC Connector settings O Connection Retry Settings DatabaseName PortNumber 1521 User Password Description JDBCConnectorSettings JDBC Connector settings lei Delimiter TNSEntry MinPoolSize 2 MaxPoolSize 1 Comments JDBCConnectorSettings MaxidleTime 0 Properties NN 331 Outbound Oracle eWay Properties The Outbound Oracle Applications eWay properties accessed from the Environment Explorer tree are organized into the following sections JDBC Connector Settings on page 30 Connection Retry Settings on page 31 JDBC Connector Settings The JDBC Connector Settings section of the Outbound Oracle Applications Environment contains the top level parameters displayed in Table 5 Table5 Outbound eWay Environment JDBC Connector Settings Name Description Required Value Description Enter a description for the database A valid string ServerName Specifies the host name of the external Any valid string database server DatabaseName Specifies the name of the database Any valid string instance used on the Server Oracle Applications eWay Intelligent Adapter User s Guide 30 Sun Microsystems Inc Chapter 3 p Configuring the Oracle Applications eWay Section 3 3 Oracle Applications eWay Environment Configuration Properties Table5 Outbound eWay Environment JDBC Connector Settings
151. ronment Configuratio xA ez m e LO UDBC Connector settings DatabaseName DataSourceName Delimiter Description Oracle thin driver Connection j DriverProperties Description JDBCConnectorSetti Password JDBC Connector settings PortNumber ServerName TNSEntry User Comments JDBCConnectorSetti Properties Cancel 2 Enter the following information as appropriate for your Oracle Applications system DatabaseName The system identifier SID for your Oracle Applications server Password The password for your Oracle Applications server PortNumber The port number that your Oracle Applications is listening on ServerName The machine name or IP address of your Oracle Applications server User The user name for your Oracle Applications server 3 Click OK to save the properties for the Oracle Apps external application 637 Deploying the Project To deploy the Project 1 In the Project Explorer tab of the Enterprise Explorer pane double click the Deployment1 Deployment Profile The Deployment Profile appears 2 Click Build to begin the deployment process 3 When the activation success message appears click No to avoid updating the Logical Host immediately Since you have not yet run the Logical Host service there is no active Logical Host for the Deployment to update Oracle Applications eWay Intelligent Adapter User s Guide 78 Sun Microsystems Inc Chapt
152. rors Error Code Error Message SB GL BUDGT 40000 BUDGET_NAME cannot be NULL SB GL BUDGT 40001 BUDGET_ENTITY_NAME cannot be NULL SB GL BUDGT 40002 CURRENCY_CODE cannot be NULL SB GL BUDGT 40003 FISCAL_YEAR cannot be NULL SB GL BUDGT 40004 UPDATE_LOGIC_TYPE cannot be NULL Oracle Applications eWay Intelligent Adapter User s Guide 128 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table25 General Ledger Errors Error Code Error Message SB GL BUDGT 40005 CURRENCY CODE does not exists CURRENCIES table SB GL BUDGT 40006 BUDGET ENTITY ID does not exists in GL BUDGET ENTITIES table SB GL BUDGT 40007 BUDGET VERSION ID does not exists in GL BUDGET VERSIONS table SB GL BUDGT 40008 CODE_COMBINATION_ID does not exists in GL_CODE_COMBINATIONS table SB GL BUDGT 40009 PERIOD_TYPE does not exists in GL_PERIOD_TYPES table SB GL BUDGT 40010 SET_OF_BOOKS_ID does not exists in GL_SETS_OF_BOOKS table SB GL BUDGT 40011 ACCOUNT TYPE should be either A Asset L Liability E Expense O Owners Equity R Revenue SB GL BUDGT 40012 DR_FLAG should be either Y Yes N No SB GL BUDGT 40013 UPDATE_LOGIC_TYPE should be either A Add R Replace SB GL BUDGT 40014 BUDGET ENTITY NAME does not exists in GL BUDGET ENTITIES table SB GL BUDGT 40015 SB GL DLRT 40100 FI
153. s Part Number 819 7376 10 Version 20061006154836 Oracle Applications eWay Intelligent Adapter 2 Sun Microsystems Inc Contents Contents Chapter 1 Introducing the Oracle Applications eWay 8 About Oracle Applications 8 Oracle Applications Basic Operation 9 About the Oracle Applications eWay 10 Oracle Applications eWay Basic Operation 11 Disclaimer 12 What s New in This Release 12 About This Document 13 What s in This Document 13 Scope 13 Intended Audience 14 Text Conventions 14 Screenshots 14 Related Documents 14 Sun Microsystems Inc Web Site 15 Documentation Feedback 15 Chapter 2 Installing the Oracle Applications 16 Before You Install 16 Installing the Oracle Applications eWay 16 Installing the Oracle Applications eWay on an eGate Supported System 17 Adding the eWay to an Existing Sun Java Composite Application Platform Suite Installation 17 After You Install 18 Extracting the Sample Projects and Javadocs 18 ICAN 5 0 Project Migration Procedures 19 Database Migration Issues 20 Installing Enterprise Manager eWay Plug Ins 22 Viewing Alert Codes 22 Oracle Applications eWay Intelligent Adapter 3 Sun Microsystems Inc Contents Chapter 3 Configuring the Oracle Applications eWay Creating and Configuring the Oracle Applications eWay Selecting Oracle Applications as the External Application Configuring the Oracle Applications eWay Properties Using the Properties Editor Oracle Applications eWay Connectivity Map Pro
154. sponding set of tables and scripts as shown in Figure 7 on page 36 Oracle Applications eWay Intelligent Adapter User s Guide 35 Sun Microsystems Inc Chapter 4 Section 4 1 Pre Validation Process Overview Figure7 Pre Validation Subsystem Pre Validation Interface Table 411 Pre Validation Scripts For Open Interfaces for which pre validation scripts have been supplied the SOL files shipped with the eWay are sufficient for you to create a working Project For Open Interfaces for which pre validation scripts are not currently available a template XML file templateXml xml is supplied Use this file to build your own pre validation package The procedure for you to follow is given in Building a Custom Pre Validation Package on page 49 Disclaimer The pre validation scripts packaged with the eWay for the supported modules are rudimentary and do not cover all possible scenarios Since the requirements from Oracle occasionally change and evolve you may be required to provide additional data and or parameters to ensure that the Concurrent Manager request completes successfully and without errors Pre validation scripts have been tested in 11 5 3 only 412 Pre Validation Procedures Common Procedures pre validation script packages pkg sql contain the following procedures Table 9 Common Procedures Procedure Purpose Initialize Profile Initializes the table for sharing to avoid running multiple instances
155. sted above sb ra interface distributions sb ra interface lines all sb ra interface salescredits all Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following files sb validate ra dist pkg sql sb validate ra lines pkg sql sb validate ra sales cr pkg sql Oracle Applications eWay Intelligent Adapter User s Guide 43 Sun Microsystems Inc Chapter 4 Section 4 3 Pre Validation Process Financial Module This file is controlled by the following master validation file sb validate auto inv pkg sql Auto Lock Oracle Interface Tables Oracle provides the following Interface Table for Requisitions ar payments interface all SeeBeyond Staging Tables The Oracle Applications eWay sets up the following staging table corresponding to the Oracle Open Interface Table listed above sb ar payments interface all Pre Validation Scripts The scripts corresponding to the SeeBeyond Staging Tables listed above are packaged within the following file sb validate ar payments pkg sql This file is controlled by the following master validation file sb validate auto lock pkg sql Customers Oracle Interface Tables Oracle provides the following Interface Table for Requisitions ra customers interface ra contact phones int all ra cust pay method interface ra customer banks int all ra customer profiles interface SeeBeyond Staging Tables The Ora
156. th new entries A1 Manufacturing 11 Inventory Customer Items Table 1 Customer Item Errors Error Code Error Message SB INVCIT 25301 Customer Item Number is mandatory and the current value is NULL SB INVCIT 25302 Transaction Type is mandatory and the current value is NULL Oracle Applications eWay Intelligent Adapter User s Guide 99 Sun Microsystems Inc Appendix A Error Codes Section A 1 Manufacturing Table 1 Customer Item Errors Error Code Error Message SB INVCIT 25303 Item Definition Level is mandatory and the current value is NULL SB INVCIT 25304 Customer ID Number and Name are mandatory and the current value is NULL SB INVCIT 25305 Address columns are mandatory and the current value is NULL SB INVCIT 25306 Customer category columns are mandatory and the current value is NULL SB INVCIT 25307 Commodity code columns are mandatory and the current value is NULL SB INVCIT 25308 Container item org columns are mandatory and the current value is NULL SB INVCIT 25309 Model customer item columns are mandatory and the current value is NULL SB INVCIT 25310 Customer ID is invalid SB INVCIT 25311 Customer Number is invalid SB INVCIT 25312 Customer Name is invalid SB INVCIT 25313 SB INVCIT 25314 Address D is invalid Customer Category columns are invalid SB INVCIT 25315 Model customer item colu
157. the Oracle Applications eWay Sample zip files to a location on your local file system such as C CAPS_Samples OraApps Make a note of where you extracted the files To import the sample in the Enterprise Designer 1 In the Enterprise Designer right click your Repository and click Import 2 Click Yes to save any changes to your Repository The Import Manager appears 3 Click Browse and navigate to the location where you downloaded the sample files in step 4 of the previous procedure In the JCD folder select the prjOraApp Manf Order Import JCD Sample zip file and click Open Oracle Applications eWay Intelligent Adapter User s Guide 71 Sun Microsystems Inc Chapter 6 Section 6 3 Implementing the Sample Projects Using the Order Import JCD Sample Figure 17 Import Manager Specify the ZIP file and the root to import to From ZIP file CAICAN SamplesiOraAppswCEtOraApp Manf Order Import JCE zip Browse Root project Root environment MyRepository MyRepositor mporting selected projects mporting 0 environments Project Exclude OraApp_Manf_Order_Imp NIA Import Close 4 In the Import Manager click Import 5 Animport status message appears when the import completes successfully Click OK to continue 6 Click Close to close the Import Manager and refresh the repository The prjOraApp Manf Order Import JCD Sample appears in the Enterprise Explorer pane o
158. the U S and other countries exclusively licensed through X Open Company Ltd This product is covered and controlled by U S Export Control laws and may be subject to the export or import laws in other countries Nuclear missile chemical biological weapons or nuclear maritime end uses or end users whether direct or indirect are strictly prohibited Export or reexport to countries subject to U S embargo or to entities identified on U S export exclusion lists including but not limited to the denied persons and specially designated nationals lists is strictly prohibited Copyright 2006 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 Etats Unis Tous droits r serv s Sun Microsystems Inc d tient les droits de propri t intellectuels relatifs la technologie incorpor e dans le produit qui est d crit dans ce document En particulier et ce sans limitation ces droits de propri t intellectuels peuvent inclure un ou plus des brevets am ricains list s l adresse http www sun com patents et un ou les brevets suppl mentaires ou les applications de brevet en attente aux Etats Unis et dans les autres pays L utilisation est soumise aux termes de la Licence Cette distribution peut comprendre des composants d velopp s par des tierces parties Sun Sun Microsystems le logo Sun Java Sun Java Composite Application Platform Suite Sun SeeBeyond eGate elnsight eVision eTL eXchange eView elndex eBAM et e
159. tion Process Building a Custom Pre Validation Package 12 13 Note business_function_name lt MDULE_NAME gt lt ORACLE_ INTERFACE NAME gt sb_validate_interface_TablenameAbbreviation_pkg sql this path is relative from lt CAPS Dir gt edesigner userdir modules ext oracleappsadapter wizard This package has the VALIDATE procedure for these interface tables Please refer to sections Pre Validation Procedures on page 36 and VALIDATE on page 65 for more information on how to compose the VALIDATE procedure Restart the Enterprise Designer so the OTD Wizard can load the new changes Create and compile the SQL scripts defined in the XML definition files When creating SQL files make sure that they begin with CREATE AND REPLACE The new Applications xml moduleDefinition xml and SQL scripts are stored only in the Enterprise Designer directory It is recommended to back them up periodically 44 1 Concurrent Manager Request Function The default SQL script template for Concurrent Manager Request has 100 identical input parameters for FND_REQUEST SUBMIT_REQUEST If you need to customize the input parameters for your generated script the following tags can be used to specify the input parameters lt Concurrent_Manager gt path file_name sql lt Concurrent_Manager gt Request Param parameterl Request Param Request Param parameter2 Request Param Request Param parameter3 Request Param 442 T
160. udget GL samples use the following fields Currency Code Fiscal Year Update Logic Type Budget Entity Name Sample Project Overview This document does not cover the sample in the same level of detail as the previous samples This section assumes that you have already read and worked through the Order Sample This section provides the information you need to import configure and run the Order Import BPEL Sample 1 Import the sample Project as described in Import the Financial GL Budget BPEL Sample on page 88 Set up the sample data on your system as described in Set up the Sample Data on page 89 Configure each of the three file eWays as described in Configure the File eWays on page 89 Create an Environment for the Project as described in Create the Environment on page 90 Create and configure the Deployment Profile as described in Create the Deployment Profile on page 90 Configure the Oracleapps1 eWay the eWay that exchanges the data with the Oracle Applications as described in Configure the Oracle Apps Fin BPEL External System on page 91 66 1 Import the Financial GL Budget BPEL Sample When importing the sample a message may appear warning you that you do not have the Oracle Applications eWay installed This warning is not critical for this sample Project Oracle Applications eWay Intelligent Adapter User s Guide 89 Sun Microsystems Inc Chapter 6 Section 6 6 Implementing the Sample Pr
161. uired column Enter a valid value SB AR LINES 10625 CONVERSION_TYPE does not exists in GL_DAILY_CONVERSION_TYPES table SB AR LINES 10626 SET OF BOOKS ID does not exists in AR SYSTEM PARAMETERS table SB AR LINES 10627 SB AR LINES 10650 CURRENCY_CODE does not exists in FND_CURRENCIES table Valid values for LINE TYPE column are LINE TAX FREIGHT and CHARGES SB AR LINES 10651 ACCOUNTING RULE ID value should match with RULE ID value of RA RULES Table SB AR LINES 10652 ACCOUNTING_RULE_NAME value should match with NAME value of RA_RULES Table SB AR LINES 10653 AGREEMENT_NAME value should match with NAME value of SO_AGREEMENTS Table SB AR LINES 10654 AGREEMENT 10 value should match with ID value of SO AGREEMENTS Table SB AR LINES 10655 SB AR LINES 10656 BATCH SOURCE NAME value should match with NAME value of RA BATCH SOURCES ALL Table CONS BILLING NUMBER must not already exist in AR CONS INV ALL table SB AR LINES 10657 CONVERSION RATE should be not null if CONVERSION TYPE is USER and CONVERSION RATE should be null if CONVERSION TYPE is not USER SB AR LINES 10658 Valid values for CREDIT METHOD FOR ACCT RULE column are PRORATE LIFO UNIT SB AR LINES 10659 Valid values for CREDIT METHOD FOR INSTALLMENTS column are PRORATE LIFO UNIT SB AR LINES 10660 CUST_TRX_TYPE_ID value should match with CUST_TRX_TYPE_ID value of RA_BATCH_SOURCES_ALL Table
162. uired settings or options The Comments pane provides an area to record notes and information regarding the currently selected property These comments are saved when you close the editor Modifying the Default eWay Configuration Properties 1 From the Connectivity Map or the Environment Explorer open the Properties Editor to the Oracle Applications eWay default properties 2 From the upper right pane of the Properties Editor select a subdirectory of the configuration directory The parameters contained in that subdirectory are now displayed in the Properties pane of the Properties Editor For example if you click on the JDBC Connector settings subdirectory the editable parameters are displayed in the right pane see Figure 5 Oracle Applications eWay Intelligent Adapter User s Guide 27 Sun Microsystems Inc Chapter 3 Section 3 2 Configuring the Oracle Applications eWay Oracle Applications eWay Connectivity Map Properties Figure5 Properties Editor Oracle Applications Properties Configuration vz ie Description Oracle thin driver Connection Pool Datasource ClassName oracle jdbc pool OracleConnectionPoolDataSource Description JDBCConnectorSett JDBC Connector settings Comments JDBCConnectorSett Properties ok 3 Click on any property field to make it editable For example click on the class property to edit the class value If a property value is true false or multiple choice the fie
163. ut BPEL sample see Using the Order Import BPEL Sample on page 79 The third sample uses a Java Collaboration to exchange data with the Oracle Applications system The results are written to two output files using file eWays For complete instructions for installing and running the financial sample see Using the Financial GL Budget JCD Sample on page 83 The fourth sample uses an eInsight BPEL business process to exchange the data with Oracle Applications In this sample the results are written to one output file For complete instructions for installing and running the financial BPEL sample see Using the Financial GL Budget BPEL Sample on page 87 Oracle Applications eWay Intelligent Adapter User s Guide 66 Sun Microsystems Inc Chapter 6 Section 6 2 Implementing the Sample Projects Exchanging Data with Oracle Applications The following section provides a detailed description of how the Oracle Applications eWay exchanges data with the Oracle Applications system 611 About the elnsight Engine and eGate Components You can deploy an eGate component as an Activity in an eInsight Business Process Once you have associated the desired component with an Activity the eInsight engine can invoke it using a Web Services interface Examples of eGate components that can interface with eInsight in this way are Object Type Definitions OTDs An eWay Collaborations Using the eGate Enterprise Designer and eInsight you c
164. validation failed against po document types all b table SB POREQ 20160 Kanban Card ID is invalid FK validation failed against mtl kanban cards table SB POREQ 20161 Preparer_ID is invalid FK validation failed against hr_employees table SB POREQ 20162 Item ID is invalid FK validation failed against mtl system items b table SB POREQ 20163 Item Revision is invalid FK validation failed against mtl item revisions table SB POREQ 20164 Charge Account ID is invalid FK validation failed against gl code combinations table Oracle Applications eWay Intelligent Adapter User s Guide 112 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 18 Requisition Errors Error Code Error Message SB POREQ 20165 If Dest Type Code is INVENTORY then item must be stock enabled for dest org If Dest Subinventory present then item must be valid either in subinventory or to a subinventory SB POREQ 20166 If Dest Type Code is EXPENSE then item must be purchasing enabled for purchasing and dest org SB POREQ 20167 If Dest Type Code is SHOP FLOOR then item must be an outise operation item and purchasing enabled for purchasing and dest org SB POREQ 20168 If Src_Type_Code is INVENTORY then the item must be stock enabled for the src org and internal order enabled for the purchasing SB POREQ 20169 SB POREQ 20170 If Src_Type_Code
165. with the BANK BRANCH NAME value of AP BANK BRANCHES table SB AR PAYMENT 10859 CURRENCY CODE value should match with the CURRENCY CODE value of CURRENCIES table SB AR PAYMENT 10860 SB AR PAYMENT 10861 TRANSIT ROUTING NUMBER value should match with BANK NUM value of AP BANK BRANCHES Table ACCOUNT value should match with BANK ACCOUNT NUM value of AP BANK ACCOUNTS ALL Table SB AR PAYMENT 10862 CUSTOMER BANK ACCOUNT ID value should match with BANK ACCOUNT ID value of AP BANK ACCOUNTS ALL SB AR PAYMENT 10863 LOCKBOX NUMBER value should match with LOCKBOX NUMBER value of AR LOCKBOXES ALL table SB AR PAYMENT 10864 BATCH NAME value should match with NAME value of AR BATCHES ALL table Customer Interface Table 22 Customer Interface Errors Error Code Error Message SB AR PHONES 10700 CREATED BY cannot be NULL SB AR PHONES 10701 SB AR PHONES 10702 CREATION DATE cannot be NULL INSERT UPDATE FLAG cannot be NULL SB AR PHONES 10703 LAST UPDATED BY cannot be NULL SB AR PHONES 10704 LAST UPDATE DATE cannot be NULL SB AR PHONES 10705 ORIG SYSTEM CONTACT REF cannot be NULL SB AR PHONES 10706 ORIG SYSTEM TELEPHONE REF cannot be NULL SB AR PHONES 10707 ORIG SYSTEM CUSTOMER REF cannot be NULL SB AR PHONES 10708 CONTACT JOB TITLE does not exist in AR LOOKUPS table SB AR PHONES 10709 CONTACT TITLE do
166. y Intelligent Adapter User s Guide 113 Sun Microsystems Inc Appendix A Error Codes Section A 2 Financial Budget GL Table 19 Accounts Payable Errors Error Code Error Message SB AP INVOICE 20021 PAYMENT METHOD LOOKUP CODE does not exist in AP LOOKUP CODES SB AP INVOICE 20022 SOURCE does not existin AP LOOKUP CODES SB AP INVOICE 20023 INVOICE NUM cannot be NULL SB AP INVOICE 20024 SOURCE cannot be NULL SB AP INVOICE 20025 INVOICE NUM and VENDOR ID should be unique in AP INVOICES ALL SB AP INVOICE 20026 VENDOR ID or VENDOR NUM or VENDOR NAME or PO NUMBER should be entered SB AP INVOICE 20027 VENDOR SITE ID or VENDOR SITE CODE or PO NUMBER should be entered SB AP INVOICE 20028 EXCHANGE RATE required if INVOICE CURRENCY CODE is entered and EXCHANGE RATE TYPE is User SB AP INVOICE 20029 EXCHANGE DATE required if INVOICE CURRENCY CODE is entered SB AP INVOICE 20030 WORKFLOW FLAG Should be in Y S D or NULL SB AP INVOICE 20031 ACCTS PAY CODE COMBINATION ID does not exists in GL CODE COMBINATIONS SB AP INVOICE 20032 ORG 10 does not exists in HR ORGANIZATION UNITS V SB AP INVLIN 20100 INVOICE ID is a required column Enter a valid value SB AP INVLIN 20101 LINE NUMBER is a required column Enter a valid value SB AP INVLIN 20102 LINE TYPE LOOKUP CODE is a required column Enter a valid value SB
167. y Intelligent Adapter User s Guide 65 Sun Microsystems Inc Chapter 6 Implementing the Sample Projects This chapter explains how to load the sample Oracle Applications Project into your CAPS Repository and describes the process in which eGate exchanges data with the Oracle Applications system What s in This Chapter About the Oracle Applications Sample Projects on page 66 Exchanging Data with Oracle Applications on page 67 Using the Order Import JCD Sample on page 70 Using the Order Import BPEL Sample on page 79 Using the Financial GL Budget JCD Sample on page 83 Using the Financial GL Budget BPEL Sample on page 87 About the Oracle Applications Sample Projects The Oracle Applications eWay includes two samples Both samples demonstrate reading records from input files inserting these records into the appropriate Oracle Applications tables and writing the results to the output file s The first sample uses a Java Collaboration to exchange data with the Oracle Applications system The results are written to two output files using file eWays For complete instructions for installing and running Order Input sample see Using the Order Import JCD Sample on page 70 The second sample uses an eInsight BPEL business process to exchange the data with Oracle Applications In this sample the results are written to one output file For complete instructions for installing and running Order Inp
168. y the validation rules or add your own customer specific requirements for error handling and recovery For example you can choose to have records that fail an import remain in the OIT so that an operator can use the Oracle administration tools to amend and resubmit the data Alternatively you can have errors sent back through eGate to the calling application or select a mixture of both depending on the type of message Using the eWay you can insert and update Oracle Applications with data from external systems using the eGate Enterprise Manager Information can be sent either in real time delivering prompt event driven performance or in batch store and forward form Error handling is provided through extensive pre validation business logic The following Oracle modules and Open Interfaces are currently supported Management Modules Purchasing Purchase Order Import Purchase Order Receiving Purchase Order Requisition Inventory Management Customer Items Interface Oracle Applications eWay Intelligent Adapter User s Guide 10 Sun Microsystems Inc proni m the Oracle Applications eWay Customer Items Cross Reference Interface Cycle Count Entries Interface Item Import Item Revisions Import Replenishment Interface Transactions Interface Order Entry Financial Modules Accounts Payable Accounts Receivable Auto Invoice Auto Lock Customers Cash Management Bank Statement Fixed Assets

Download Pdf Manuals

Related Search

Related Contents

Curtis FRW081UK User's Manual  mode d`emploi de MILKSTAPH, test de détection de staphylocoques  MANUAL DE INSTALAÇÃO E FUNCIONAMENTO  User Manual - Apostol Bakalov  CDJ-400 - M3 Eventtechnik  User manual  Trekstor i.Beat swap    Samsung SHV-E370D User Manual  平成28年度 - 茨城大学大学院理工学研究科  

Copyright © All rights reserved. Failed to retrieve file