Queries on GL_BALANCES [ID 14855.1]

Queries on GL_BALANCES [ID 14855.1]
		Modified 29-OCT-2010 Type HOWTO Status PUBLISHED

 Checked for relevance on 29-Oct-2010 Checked for relevance on 27-May-2009 Checked for relevance on 1-Oct-2007  The General Ledger entry reports can sometimes show errors like:      **CONFLICTS W/PER NET BAL**  which normally point to a discrepancy between an account's begin balance and  end balance - normally from the previous period.  To check out such an error  sometimes means querying on the gl_balances table. Here are some suggestions as to possible SIMPLE queries to be run.  If you do discover or suspect an imbalance, please log a service request, explaining the situation.   Note 101579.1 contains scripts that can help in identifying discrepancies. The Period Close Diagnostic can also be used to identify potential problems.   There is no end balance column in gl_balances - the following should highlight  it (this is the period end balance).  Select sum(begin_balance_dr + period_net_dr) - sum(begin_balance_cr +                                                period_net_cr) from gl_balances where period_name = and actual_flag = 'A' and currency_code = and set_of_books_id = and code_combination_id =  PLEASE NOTE:  When the general ledger entry reports work out the end balance  they work it out on a credit or debit basis - not a net of both.  That is, the  period activity total credits on gl_balances should match the journal line  credit total for the period (and CCID) number for number and visa versa with the debits. If it does not then the General Ledger Entry reports will still show  CONFLICT errors even though the account(s) actually have the correct net totals.  This is important when doing a correction on gl_balances or gl_je_lines.  To find period net activity (which forms part of the above)  Select sum(period_net_dr), sum(period_net_cr) from gl_balances where set_of_books_id = and actual_flag = 'A' and currency_code = and period_name =  At foreign currency sites you might want to include the translated_flag.  This will give the sum of every code combination.  However, if you just want to  check against one CCID then take out the sum and include the CCID in the where  clause.  This period net activity should match the amount of journals that have been put  through and for this you need to check mainly against gl_je_lines:  Select sum(j.entered_dr), sum(j.entered_cr) from gl_je_lines j, gl_je_headers h where j.je_header_id = h.je_header_id and j.period_name = and h.currency_code = and j.set_of_books_id = and j.status = 'P' and h.actual_flag =  Again, you might want to search on a particular code combination and this can be included in the where clause - along with other columns, say, from headers to  limit the data returned. The above highlighted one problem for me as the journal lines did not match the balances.  You might want to extend the select to include the sums of the headers as in one case headers for the period did not match the lines in that one journal for  November included some lines for November and some for October (which should be  impossible but happened because of a system problem - there was also a suspected problem in this area with running maintain batch periods -ie changing the period on the journal header and running posting before it completed).  Select h.je_header_id from gl_je_lines j, gl_je_headers h where j.je_header_id = h.je_header_id and j.period_name != and h.period_name = and j.status = 'P' and h.currency_code = and j.set_of_books_id = and h.actual_flag =   No update scripts are included as each case is different. Contact Oracle Support for  a solution if you suspect an imbalance in gl_balances.

Oracle E-Business Suite to Oracle Retail

Oracle E-Business Suite to Oracle Retail

1. A BPEL process extracts data from the Oracle E-Business Suite database.

BPEL processes publish XML files on the specific Java Messaging Service (JMS) topics on the Oracle Retail Integration Bus (RIB).

2. RIB is used to perform the data load into RMS.

The XML payload is verified. If any error is encountered, RIB rejects the message and sends it to the RIB hospital.

3. The XML payloads with validated data should be subscribed to by the specific RMS APIs and loaded to the RMS tables.

Oracle Retail to Oracle E-Business Suite

A BPEL process extracts the data from the Oracle Retail (ReIM, RMS, ReSA) database.

BPEL processes publish XML files in the specific Oracle E-Business Suite staging tables.

User Account Control (UAC) is enabled. Installation may lead to unpredictable results and thus will be stopped.

Error Installing EPM v11.1.2.1: "User Account Control (UAC) is enabled. Installation may lead to unpredictable results and thus will be stopped." [ID 1314042.1]
Modified 25-APR-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution

Applies to:

Hyperion Essbase - Version: 11.1.2.1.000 to 11.1.2.1.000 - Release: 11.1 to 11.1
Microsoft Windows x64 (64-bit) - Version: 2008 R2
Symptoms

Installing EPM v11.1.2.1 fails with the error:

Error: "User Account Control is enabled. Installation may lead to unpredictable results and thus will be stopped."

EPMINS-01001: One or more preinstallation checks failed. Correct the errors before continuing with the installation.

Cause

User Account Control is enabled.

Solution

Per the EPM Installation Start Here Guide, "Prepare a user account", User Account Control must be disabled.

This can be done through User Accounts in Control Panel by clicking on Change User Account Control Settings, then drag the slider to Never notify.

This can also be accomplished using the following steps:

1. Click Start -> Control Panel.
2. In Control Panel, click User Accounts.
3. In the User Accounts window, click User Accounts.
4. In the User Accounts tasks window, click "Turn User Account Control on or off."
5. Uncheck the "Use User Account Control (UAC) to help protect your computer", and then click OK.
6. Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window.

This change requires a reboot of the Windows 2008 Server.


Related
Products
Middleware > Enterprise Performance Management > Essbase > Hyperion Essbase
Keywords
FAIL; INSTALLATION; UAC; USER ACCOUNT CONTROL

Back to top

Fact sheet about Oracle database passwords

Fact sheet about Oracle database passwords


Oracle Password Algorithm (7-10g Rel.2)

Up to 30 characters long. All characters will be converted to uppercase before the hashing starts
8-byte hash, encrypted with a DES encryption algorithm without real salt (just the username).
The algorithm can be found in the book "Special Ops Host And Network Security For Microsoft, Unix, And Oracle" on page 727.

Oracle database 11g offers the (optional) possibility to use passwords up to 50 characters (uppercase/lowercase). In Oracle 11g the passwords are now hashed with DES (column: password) AND using SHA-1 (column: spare4). The SHA-1 passwords are now supporting mixed-case passwords. In 11g the password hashes are no longer available in dba_users.

Oracle (7-10g R2) encrypts the concatenation of (username||password)
and sys/temp1 and system/p1 have the identical hashkey (2E1168309B5B9B7A)
Oracle (11g R1) uses SHA-1 to hash the concatenation of (password||salt)


Oracle Password Cracker

A comparision of different password cracker can be found here. Benchmarks for different password crackers are available here (10g) and here (11g) .


Location of Oracle password hashes

Database - SYS.USER$ - Password
Oracle Password File
Data File of the system tablespace
(full) Export-Files
archive logs


Show Oracle password hashkey (old DES hash)

You should always select database users from the table not from the views (ALL_USERS, DBA_USERS). An explanation (modification of database views via rootkits) can be found here.

DBA_USERS : SELECT username, password FROM DBA_USERS;
SYS.USER$ : SELECT name,password FROM SYS.USER$ WHERE password is not null;

Show Oracle password hashkey (11g, new SHA-1 hash)

In 11g the password hash is no longer accessible via dba_users

SYS.USER$ : SELECT name,spare4 FROM SYS.USER$ WHERE password is not null;


How to change an Oracle password?

You should always use the password command because the password is sent unencrypted over the net (without Advanced Security Option) if you use the alter user syntax.
alter user myuser identified by my!supersecretpassword;
grant connect to myuser identified by my!supersecretpassword
update sys.user$ set password='F894844C34402B67' where name='SCOTT'; (restart of the database necessary)
SQL*Plus command: password or password username


How to change an Oracle password temporarily?

In Oracle it is possible to change a password temporarily. This can be useful for DBA which act as a different user.

SQL> select username,password from dba_users where username='SCOTT';

USERNAME PASSWORD
-------- ----------------
SCOTT F894844C34402B67

SQL> alter user scott identified by mypassword;


Now login with the following credentials: scott/tiger
After doing your work you can change the password back by using an undocumented feature called "by values"

SQL> alter user scott identified by values 'F894844C34402B67';


Oracle default password list

600+ default Oracle passwords


Oracle Password Policy

It is possible to setup a password policy (for strong Oracle passwords). A sample file how to do this can be found at $ORACLE_HOME/rdbms/admin/utlpwdmg.sql. If you use this functionality please be aware that the password policy function has access to the cleartext password (for the comparisions reasons). With Oracle 11gR1 Oracle greatly enhanced the password verification function.

A hacker could modify your function and log all cleartext passwords entered by the users to a table or send it to a foreign webserver with utl_http. That's why you should checksum this function, e.g. with Repscan.

Oracle brute force attacks / Oracle Password Decryption (7-10gR2)

It is not possible to decrypt a hashstring but the simple Oracle salt (=Username) it is possible to do a brute force or dictionary attack. There are several Oracle brute force or dictionary attack tools available. These tools encrypt the username/password and compare the hashkeys. If the hashkey are identical the password is known. From simple SQL based tools (<500 pw/second) up to special C programs like checkpwd. The fastest tool for brute force attacks orabf calculates 1.100.000 passwords/second. The fastest tool for dictionary attacks are checkpwd and repscan with 600.000 pw per second. On a Pentium 4 with 3 GHz it takes (26 ascii characters only, e.g. 26^5)

10 seconds to calculate all 5-ascii-character-combinations
5 minutes to calculate all 6-ascii-character-combinations
2 hours to calculate all 7-ascii-character-combinations
2,1 days to calculate all 8-ascii-character-combinations
57 days to calculate all 9-ascii-character-combinations
4 years to calculate all 10-ascii-character-combinations


You should always use strong and long passwords to avoid brute force or dictionary attacks.


Typical Error messages related to Oracle database passwords

The following error messages are related to Oracle passwords:
ORA_28000: The account is locked
Wait for PASSWORD_LOCK_TIME or contact your DBA
ORA-28001: The password has expired
Change the password or contact your DBA
ORA-00988: Missing or invalid password(s)
Use double quotes for the password (e.g. alter user scott identified by "!alex";)
ORA-01017: Invalid username/password; logon denied
Contact your DBA if the problem still persists

Oracle database passwords in cleartext

Cleartext passwords can be typically but not necessarily found at the following places
Server
Shell History files
Unix Scripts
Log Files
Dump Files
Trace Files
Application Server
JDBC-Config-Files
Trace Files
DBA Client PC
Desktop-Shortcut
Batch-Files
Configuration files of Oracle Tools (like connections.ini)
Trace Files

How to reset the password for the administrative login 'AS SYSDBA' if it is lost?

How to reset the password for the administrative login 'AS SYSDBA' if it is lost? [ID 431374.1]
Modified 09-MAR-2010 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
References

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.8 to 11.1.0.6
Information in this document applies to any platform.
Checked for relevance on 09-Mar-2010
Goal

How to reset the password for the administrative login 'AS SYSDBA' if it is lost?

If for some reason you forgot the remote login password or the passwordfile was corrupted, this document describes how you can recreate the passwordfile. You can only do this if you have the proper privileges to access the passwordfile on the Operating System filesystem. The alternative to this is to use OS authentication to connect to the database as SYSDBA and then change the password with "alter user sys identified by newpassword".
Solution

1. Check v$pwfile_users to list the users having been granted SYSDBA or SYSOPER currently.


SQL> connect system/manager
Connected.
SQL> select * from v$pwfile_users;

USERNAME SYSDB SYSOP
------------------------------ ----- -----
SYS TRUE TRUE
EXTJOB_USER TRUE FALSE
SYSTEM TRUE FALSE

If the database cannot be accessed anymore, use strings on the passwordfile (Unix only):

$ strings $ORACLE_HOME/dbs/orapw$ORACLE_SID

ORACLE Remote Password file
INTERNAL
EXTJOB_USER
SYSTEM

This will give you the usernames that have been granted SYSDBA or SYSOPER.


2. Check that 'init.ora' parameter REMOTE_LOGIN_PASSWORDFILE was set to to EXCLUSIVE:


SQL> show parameter remote_login_passwordfile

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
remote_login_passwordfile string EXCLUSIVE

3. Shutdown the instance for which this passwordfile can provide authentication, use OS authentication to login, if this was disabled, terminate the instance by killing the smon background process.

4. Just in case backup your current passwordfile.

5. Create a new password file using the following command syntax:

orapwd file= password= entries= force= nosysdba=

where
file - name of password file (mand),
password - password for SYS (mand),
entries - maximum number of distinct DBA,
force - whether to overwrite existing file (opt),
nosysdba - whether to shut out the SYSDBA logon (opt for Database Vault only).
There are no spaces around the equal-to (=) character.

On Unix/Linux the passwordfile convention is : $ORACLE_HOME/dbs/orapw$ORACLE_SID
On MS Windows the passwordfile convention is : %ORACLE_HOME%\database\PWD%ORACLE_SID%.ORA

6. You can now restart the database.

7. Now you can try to connect using the new passwordfile, note that for local connections you can likely use OS authentication, so for a true test, make a remote connection as follows:

$ sqlplus sys/manager@v1020 as sysdba

8. Grant all the users (except internal) you listed in step 1 the SYSDBA or SYSOPER privilege again:

SQL> grant sysdba to SYSTEM;

How to recover from lost sys password

How to recover from lost sys password [ID 805084.1]
Modified 28-JUL-2010 Type HOWTO Status MODERATED
In this Document
Goal
Solution
Recovering from lost sys password using OS authentication on Unix.
Recovering the lost sys password using passwordfile authentication on Unix
Recovering from lost sys password using NTS authentication on Windows
Recovering the lost sys password using passwordfile authentication on Windows
References

Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Applies to:

Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.1.0.7 - Release: 8.1.7 to 11.1
Information in this document applies to any platform.
Goal

How to recover from lost sys password.

Solution

The methods to be used rely on:
1. OS authentication
2. passwordfile authentication.
It is outside the scope of this note to explain how OS or passwordfile authentication work in detail, for this, please check My Oracle Support document:

Note.50507.1 SYSDBA and SYSOPER Privileges in Oracle

Recovering from lost sys password using OS authentication on Unix.

#1. Make sure that the OS user that is logged on is member of the dba group. If the dba group is not known, check the file:

$ORACLE_HOME/rdbms/lib/config.c (or config.s)

#2. Make sure that the sqlnet.ora file does not contain the:

sqlnet.authentication_services

parameter. If this parameter exist, it should be commented.

#3. check the ORACLE_HOME, ORACLE_SID and PATH parameters. They must correspond to the parameters of the Oracle instance where the SYS password has been lost.

If the instance is already started, use the document:

Note.373303.1 How to Check the Environment Variables for an Oracle Process

to determine the environment variables that were used when the instance was started.

#4. connect to the instance using:

sqlplus /nolog
connect / as sysdba

#5. Change the sys password using:
alter user sys identified by ;

If a passwordfile is in use, the command would update the password file as well, so there is no need to recreate this file.

Recovering the lost sys password using passwordfile authentication on Unix

If the SYS password is not known and the OS authentication is not an option, this method can be used. This method assumes that the SYS account is not accessible, hence an abrupt shutdown for the database could be needed.

#1. Make sure that the initialization parameter REMOTE_LOGIN_PASSWORDFILE is set to SHARED or EXCLUSIVE. Changing this parameter value requires an instance restart.

#2. Disable OS authentication, if it is enabled for some reason, by setting:

sqlnet.authentication_services=(none)

in the sqlnet.ora file (previously, backup the existing sqlnet.ora file).

#3. go to the OS destination for the passwordfile:

cd $ORACLE_HOME/dbs

#4. Make a backup of the previous passwordfile:

cp orapw$ORACLE_SID orapw$ORACLE_SID.bak

#5. Recreate the passwordfile using the orapwd command:

orapwd file=orapw$ORACLE_SID password=

#6. Try to connect using the new password.

sqlplus /nolog
connect sys as sysdba

#7. As an additional check, if the above is successful, query:

select * from v$pwfile_users;

If it returns at least one line, then everything is ok and the new passwordfile is in use.

#8. Change the sys password in the data dictionary using:

alter user sys identified by ;

Of course, the new password must match the new password of the passwordfile, if that password is to be kept, or it can be set to something else, if the initial password is to be changed. This command would update the passwordfile as well.

#9. If the test in step does not succeed, the instance must be restarted. It could be that, if no sysdba or sysoper access are possible, that the instance must be brought down abruptly, do this by:
+ killing a background process (preferrably kill SMON, so PMON can still do some cleanup)
+ removing the shared memory resources using ipcrm if they are not removed by my PMON

#10. After restarting the instance, check if the SYS password is operational and if there is at least one entry in v$pwfile_users. If other users previously had entries in the passwordfile, grant them SYSDBA or SYSOPER again.

#11. Restore the sqlnet.ora file from the backup executed at step #2, if needed.
Recovering from lost sys password using NTS authentication on Windows

1. Make sure that the OS user that is logged on is member of the Windows ORA_DBA group.

#2. Also make sure that the sqlnet.ora file has the following line:

sqlnet.authentication_services = (nts)

#3. Connect to the instance using:
sqlplus /nolog
connect / as sysdba

#4. Change the sys password using:
alter user sys identified by ;

If a passwordfile is in use, the command would update the password file as well, so there is no need to recreate this file.

Recovering the lost sys password using passwordfile authentication on Windows

If the SYS password is not known and the OS authentication is not an option, this method can be used. This method assumes that the SYS account is not accessible, hence a shutdown for the database could be needed, this can be accomplished by stopping the OracleServiceSID on your system.

#1. Make sure that the initialization parameter REMOTE_LOGIN_PASSWORDFILE is set to SHARED or EXCLUSIVE.
#2. disable OS authentication, if it is enabled for some reason, by setting:
sqlnet.authentication_services=(none)

in the sqlnet.ora file
#3. go to the OS destination for the passwordfile:
cd %ORACLE_HOME%\database

#4. Make a backup of the previous passwordfile:
cp pwd.ora pwd.ora.bak

#5. Recreate the passwordfile using the orapwd command:
orapwd file=pwd.ora password=

#6. Try to connect using the new password.
sqlplus /nolog
connect sys as sysdba

#7. As an additional check, if the above is successful, query:
select * from v$pwfile_users;

If it returns at least one line, then everything is ok and the new passwordfile is in use.
#8. change the sys password in the data dictionary using:
alter user sys identified by ;

Of course, the new password must match the new password of the passwordfile, if that password is to be kept, or it can be set to something else, if the initial password is to be changed. This command would update the passwordfile as well.
#9. If the test in step does not succeed, the instance must be restarted. This can be done by restarting the service.
#10. After restarting the instance, check if the SYS password is operational and if there is at least one entry in v$pwfile_users. If other users previously had entries in the passwordfile, grant them SYSDBA or SYSOPER again.

#11. re-enable NTS authentication by setting:

sqlnet.authentication_services=(nts)

if needed.

cronjob hotbackupscripts and begin backup and end backups scripts

@daily sh /u01/d01/backupscripts/starthotbackup_12AM.sh #Oracle Database Hotbackup daily
* 22 * * * sh /u01/d01/backupscripts/compressarchive.sh


alter system switch logfile;
alter tablespace SYSTEM begin backup;
alter tablespace CTXD begin backup;
alter tablespace OWAPUB begin backup;
alter tablespace ODM begin backup;
alter tablespace PORTAL begin backup;
alter tablespace APPS_UNDOTS1 begin backup;
alter tablespace APPS_TS_TX_DATA begin backup;
alter tablespace APPS_TS_TX_IDX begin backup;
alter tablespace APPS_TS_SEED begin backup;
alter tablespace APPS_TS_INTERFACE begin backup;
alter tablespace APPS_TS_SUMMARY begin backup;
alter tablespace APPS_TS_NOLOGGING begin backup;
alter tablespace APPS_TS_ARCHIVE begin backup;
alter tablespace APPS_TS_QUEUES begin backup;
alter tablespace APPS_TS_MEDIA begin backup;
alter tablespace OLAP begin backup;

exit
~

[oraprod@jtlprod backupscripts]$ vi endbackup.sql
alter tablespace SYSTEM end backup;
alter tablespace CTXD end backup;
alter tablespace OWAPUB end backup;
alter tablespace ODM end backup;
alter tablespace PORTAL end backup;
alter tablespace APPS_UNDOTS1 end backup;
alter tablespace APPS_TS_TX_DATA end backup;
alter tablespace APPS_TS_TX_IDX end backup;
alter tablespace APPS_TS_SEED end backup;
alter tablespace APPS_TS_INTERFACE end backup;
alter tablespace APPS_TS_SUMMARY end backup;
alter tablespace APPS_TS_NOLOGGING end backup;
alter tablespace APPS_TS_ARCHIVE end backup;
alter tablespace APPS_TS_QUEUES end backup;
alter tablespace APPS_TS_MEDIA end backup;
alter tablespace OLAP end backup;
alter system switch logfile;
exit
~
~

#/bin/bash
compress /u01/d01/archivelog/*.dbf

#!/bin/bash
. /u01/d01/jtlproddb/9.2.0/JTLPROD_jtlprod.env
sqlplus system/manager @/u01/d01/backupscripts/beginbackup.sql
cd /u01/d01
NOWDATE=`date +%d-%m-%y-%H_HOT`
export NOWDATE
tar cf - jtlproddata | gzip -c > /u01/d01/hotbackup/$NOWDATE.tgz
. /u01/d01/jtlproddb/9.2.0/JTLPROD_jtlprod.env
sqlplus system/manager @/u01/d01/backupscripts/endbackup.sql

Supported ODBC Configurations On Windows

Supported ODBC Configurations On Windows

The ODBC (Open Database Connectivity) interface allows applications to access data in DBMS (Database Management Systems) using SQL (Structured Query Language). The Oracle ODBC driver on windows is a DLL that implements ODBC function calls and interacts with a data source.

The flow of control when communicating from an application through ODBC to an Oracle database is shown below:

Application
|
ODBC Driver Manager
|
Oracle ODBC Driver
|
OCI layer
|
SQL*Net Driver
|
Network Software
(PCTCP, Novell Netware, Microsoft LAN Manager, etc,.)
|
SQL*Net Listener
|
Oracle RDBMS

When a third party application communicates with the Oracle database in a Client/Server environment, several Dynamic Link Libraries (DLLs) are involved.

The ODBC driver communicates with the OCI layer. DLLs used in the OCI layer are part of Required Support Files (RSFs). Required Support Files are bundled with SQL*Net.

Each version of the ODBC driver is linked with a specific version of RSF. Each version of SQL*Net is also dependent on a specific version of RSF. The matrix below shows the dependency.
Supported Versions Matrix
ODBC Driver Version

Supported Operating System

Sql*Net Requirements

RDBMS

Release Notes

Patchset Number
11.2.0.1.0 Windows 2000/XP/2003/Vista/2008/7 11.2.0.1.0 9.2.0.4 or higher

N/A *
11.1.0.7.0 Windows 2000/XP/2003/Vista/2008 11.1.0.7.0 9.2.0.4 or higher

Patch 6890831
10.2.0.5.0

Windows 2000/XP/2003/Vista/2008/7

10.2.0.5.0

8.1.7 or higher

Note 402885.1

Patch 8202632 *

Note: If you are running an ODBC driver not listed in the above matrix, we strongly recommend that you upgrade your ODBC driver.

* Starting in 10.2 all Oracle ODBC Driver patches are contained in the Oracle Database (AKA Oracle Database Family) patchsets. However, they assume that the base Oracle ODBC Driver has been installed in the Oracle Home.

Basics

If your application is 32-bit, you must use a 32-bit Oracle ODBC driver and 32-bit SQL*Net for the platform where your application is targeted.

As of December 31, 2000 all the 16-bit products from Oracle have been desupported.

ODBC Documentation

For Oracle8, the ODBC driver help file name is Sqora.hlp and is located in windowsNT/system32/.

For other ODBC Documentation such as white papers and bulletins written by Oracle Support Services, refer to the MetaLink web site at:

http://metalink.oracle.com/

For ODBC API documentation, refer to the "ODBC 3.0 Programmer's Reference and SDK Guide" from Microsoft Press. The online version of this manual is part of the MSDN Library.

Version of Oracle product: How to find ?

To find the versions of Oracle software installed on your machine, run the Oracle Universal Installer and click on Installed Products. In case of errors, versions numbers are an important part of problem definition.

API Conformance Level

The Oracle 8i and 9i ODBC Drivers are numbered according to the Oracle Client they work with. The API Conformance Level of the ODBC Driver can be found in the Release Notes for that Oracle ODBC Driver.

General Suggestions

Read the release notes and online documentation which contain important information. If an error occurs, write down the entire error message as seen on the monitor(screen). An error message is key in finding the problem.

Where can I obtain Oracle ODBC drivers from ?

The Oracle ODBC driver is bundled with the Oracle client and server software. It is available to be downloaded from http://otn.oracle.com.

Also, starting in 10.2 all Oracle ODBC Driver patches are contained in the Oracle Database (AKA Oracle Database Family) patchsets. However, they assume that the base Oracle ODBC Driver has been installed in the Oracle Home.

http://metalink.oracle.com

Supportable Operating System

Currently, Oracle no longer supports the Windows 3.11 or Windows for Workgroups for 16-bit ODBC. Win/OS2 sessions are NOT SUPPORTED.

The only supported Windows 95 versions are Windows 95 or Windows 95 service pack 1 which are identified with a lower case 'a' after the version number, i.e. 4.00.95a. Windows95 OSR2 identified with an uppercase 'B' after the version number is NOT SUPPORTED.

Oracle also supports the Oracle odbc drivers running on Windows 2000, Windows 2003 and Windows XP.

Configure and use ERPi 11.1.2 to Load Data into Financial Data Quality Management from EBS

Configure and use ERPi 11.1.2 to Load Data into Financial Data Quality Management from EBS [ID 1169565.1]
Modified 30-SEP-2010 Type WHITE PAPER Status PUBLISHED

In this Document
Abstract
Document History
Configure and use ERPi 11.1.2 to Load Data into Financial Data Quality Management from EBS
Installation of ERPi and ODI
Configure the ODI Software Component for ERPi
Configuration and Initialization of ERPi
Using ERPi for EBS/FDM Data Loads into HFM

Applies to:
Oracle Financial Data Quality Management ERP Integration Adapter for Oracle - Version: 11.1.2.0.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Abstract

The following White Papers in this KM article will cover the following topics:

* Installation of ERPi and ODI
* Configure the ODI Software Component for ERPi
* Configuration and Initialization of ERPi
* Using ERPi for EBS/FDM Data Loads into HFM


Document History
Author: Wayne Paffhausen
Create Date 12-Oct-2009
Update Date
Expire Date
Configure and use ERPi 11.1.2 to Load Data into Financial Data Quality Management from EBS
Installation of ERPi and ODI

1. Install the ERPi Component
2. Install the ODI Component

Click here to download the ERPIStage1.pdf

Configure the ODI Software Component for ERPi

1. Create the ERPi Master Repository
2. Configure the Topology Manager
3. Create Logical Schemas
4. Create Physical Schemas
5. Create the Logical/Physical Context
6. Configure the ERPi Work Repository
7. Create a Physical Agent
8. Configure the Operator
9. Import the Scenarios

Click here to download the ERPIStage2.pdf

Configuration and Initialization of ERPi

1. Create ERPi Source Systems
2. Initialize ERPi Source System

Click Here to download the ERPIStage3.pdf

Using ERPi for EBS/FDM Data Loads into HFM

1. Create a Link inside of ERPi to the HFM Application
2. Create an Import Format
3. Create a Location
4. Create the Metadata
5. Create the Member Mappings
6. Create a Data Rule

Click Here to download the ERPIStage4.pdf

BPEL Integration Questions On Retail Merchandising System (RMS) And E-Buiness Suite (EBS)

BPEL Integration Questions On Retail Merchandising System (RMS) And E-Buiness Suite (EBS) [ID 845338.1]
Modified 31-MAR-2011 Type FAQ Status PUBLISHED

In this Document
Purpose
Questions and Answers
How can the user change the execution interval for the RMS and E-Business Suite integration BPEL processes?Once deployed and configured, it seems to run by itself at a specific interval. These BPEL include: SendCurrRatesToRetek, SendFreightTermsToRetek, SendGLCCToRetek, SendPaymentTermsToRetek and SendVendorToRetek
In the wsdl file there is "SelectVendorService.wsdl", for example, where there is an PollingInterval = "300". Does this mean 300 minutes or 300 seconds? Is the BPEL process running at this defined interval once it is deployed?
Is the BPEL process running at this defined interval once it is deployed? If the select statement does not retrieve any record, will it publish anything, like the empty JMS message?
The Descriptor page of the BPEL console does not allow this internal configuraion. There is display only field named as "retryInterval=60" for SendFreightTermsToRetek, SendPaymentTermsToRetek, SendVendorToRetek and SendGLCCToRetek. This field does not correspond to the PollingInterval in the each wsdl. a. What does this field mean? b. Is it for minutes or seconds?
These BPEL processes will publish an empty XML message if there is no record selected. How do I disable the action of sending empty XML message? The desired behavior is to send XML message when there is records selected, and don't send anything if there is no record selected.
References

Applies to:
Oracle Retail Merchandising System - Version: 12.0.9 and later [Release: 12 and later ]
Information in this document applies to any platform.
Purpose

The Oracle Retail Merchandising System (RMS) can be integrated to the E-Business Suite (EBS) with the Oracle Business Process Execution Language (BPEL) processes. The BPEL processes are delivered in EBS Patch 6252889. Here are a few questions and answers for that integration.
Questions and Answers
How can the user change the execution interval for the RMS and E-Business Suite integration BPEL processes?

Once deployed and configured, it seems to run by itself at a specific interval.

These BPEL include:
SendCurrRatesToRetek,
SendFreightTermsToRetek,
SendGLCCToRetek,
SendPaymentTermsToRetek and
SendVendorToRetek

The user can do it in the Adapter wizard section by changing the value of Polling Interval.
Or in the wsdl file of the adapter.

Example:



ActivationSpec="oracle.tip.adapter.db.DBActivationSpec"

DescriptorName="PollingControlTableStrategy.Moviesctrl"
QueryName="PollingControlTableStrategyService"
PollingStrategyName="DeletePollingStrategy"
PollingInterval="10"
MappingsMetaDataURL="toplink_mappings.xml" />



Please see the example for DBAdapter from BPEL_HOME/bpel/samples/tutorials/122.DBAdapter

In the wsdl file there is "SelectVendorService.wsdl", for example, where there is an PollingInterval = "300". Does this mean 300 minutes or 300 seconds? Is the BPEL process running at this defined interval once it is deployed?

It is 300 seconds. Yes, the BPEL process is running at this defined interval once it is deployed. So, the polling frequency is every 5 mins.
Is the BPEL process running at this defined interval once it is deployed? If the select statement does not retrieve any record, will it publish anything, like the empty JMS message?

BPEL process will poll records once immediately after deploy. Then continue to poll every 5 mins.
If the select statement does not retrieve any record, it should not publish anything.
The Descriptor page of the BPEL console does not allow this internal configuraion.

There is display only field named as "retryInterval=60" for
SendFreightTermsToRetek,
SendPaymentTermsToRetek,
SendVendorToRetek and
SendGLCCToRetek.

This field does not correspond to the PollingInterval in the each wsdl.
a. What does this field mean?
b. Is it for minutes or seconds?

a. This is connection property. Please view the below link for more details
http://docs.sun.com/app/docs/doc/820-4388/cnfg_oracle-env_r?l=Ja&a=view
b. It is milliseconds.
These BPEL processes will publish an empty XML message if there is no record selected. How do I disable the action of sending empty XML message? The desired behavior is to send XML message when there is records selected, and don't send anything if there is no record selected.

This is not expected behaviour. If there are no records, then BPEL will not publish an empty XML
message.





References
PATCH:6252889 - Oracle Retail 12.0.5 Integration with E-Business Suite Financials 12.0.2: BPEL 10.1.3
Service Request (SR) 7330307.993

Show Related Information Related

RMS - EBS 2.5: Integration of rms 13.0.x with EBS 12.0.4 using AIA 2.5

RMS - EBS 2.5: Integration of rms 13.0.x with EBS 12.0.4 using AIA 2.5 [ID 1299565.1]
Modified 28-FEB-2011 Type HOWTO Status MODERATED

In this Document
Goal
Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:
Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandise Operations Management and Oracle E-Business Suite Financials - Version: 2.5 and later [Release: 2.5 and later ]
Information in this document applies to any platform.
Goal

=== ODM Question ===
We need information to integrate RMS 13.0.x with EBS 12.0.4 using AIA 2.5.


Solution

=== ODM Answer ====
AIA Foundation Pack Release 2.5

PIP Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandise Operations Management and Oracle E-Business Suite Financials release 2.5

Certified SOA release :
==================
Oracle SOA Suite 10.1.3.4 (MLR#8 or higher) - 32 bit
OR
Oracle SOA Suite 10.1.3.5 (MLR#2)
[4 Requires patch 9247257 and 9804031
5 Requires patch 10255190]

Certified Participating Applications:
===========================
ODI
EBS 12.1.1
Retail 13.1

Implementation Guide Note :
=======================

Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandise Operations Management and E-Business Suite Financials 2.5 - Implementation Guide (Doc ID 956247.1)

Master Support Note:
================
"Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandise Operations Management and E-Business Suite Financials" Master Support Note (Doc ID 1264900.1)

Retail Merchandising System (RMS) Version 13 Integration to Oracle EBS (AP Financials) Through Retail Integration Bus (RIB) Version 13

Retail Merchandising System (RMS) Version 13 Integration to Oracle EBS (AP Financials) Through Retail Integration Bus (RIB) Version 13 [ID 737075.1]
Modified 10-AUG-2010 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
References

Applies to:
Oracle Retail Integration Bus - Version: 13.0.1 and later [Release: 13 and later ]
Information in this document applies to any platform.
Checked for relevance on 21-May-2010
Goal
The current documentation for Retail Integration Bus (RIB) version 13 outlines that Retail Merchandising System (RMS) version 13 integrates with Oracle E-Business Suite (EBS) Financials (as an external system) but there is no mention on how this occurs. There are external-to-RMS input adaptors in RIB version 13 (e.g., supplier, freight terms) and from what is available on the Oracle Financials side there is a mechanism called the XML Gateway, but there is no description of how these two systems are coupled.

Is there information that outlines how this process occurs?
Solution

For integration with Oracle EBS, an Oracle Retail integration accelerator patch is available for download, Patch 7330263. This patch enables the integration between Oracle EBS and some Oracle Retail applications. The hot fix downloads associated with the following defect numbers are required to implement this integration patch:

Patch 7330263 (RMS 13.0: RETAIL13 AND EBS12 INTEGRATION ACCELERATOR - MASTER DEFECT)

Patch 7291971 (RMS 13.0: RETAIL13 AND EBS12 INTEGRATION ACCELERATOR - RMS RELATED FIXES)

Patch 7330290 (RMS 13.0: RETAIL13 AND EBS12 INTEGRATION ACCELERATOR - BPEL/EBS RELATED FIXES)

Patch 7331912 (ReIM 13.0: UPLOAD OF REIM 13.0.1.1 EBS INTEGRATION)

Also see the Oracle RIB Release Notes for RIB Release 13.0.1.1 (documentation-only release) Patch 7332432.
References
PATCH:7291971 - RETAIL13 AND EBS12 INTEGRATION ACCELERATOR - RMS RELATED FIXES.
PATCH:7330263 - RETAIL 13 AND EBS12 INTEGRATION ACCELERATOR - MASTER DEFECT
PATCH:7330290 - RETAIL13 AND EBS12 INTEGRATION ACCELERATOR - BPEL/EBS RELATED FIXES.
PATCH:7331912 - UPLOAD OF REIM 13.0.1.1 EBS INTEGERATION

Workflow Service Containers Activate/Deactivate Script [ID 1124356.1]

Workflow Service Containers Activate/Deactivate Script [ID 1124356.1]

--------------------------------------------------------------------------------

Modified 15-JUN-2010 Type SCRIPT Status PUBLISHED

In this Document
Purpose
Software Requirements/Prerequisites
Configuring the Script
Running the Script
Caution
Script
References



--------------------------------------------------------------------------------



Applies to:
Oracle Workflow Cartridge - Version: 11.5.9 and later [Release: 11.5 and later ]
Information in this document applies to any platform.

Purpose
This is an admin script to start and stop the Workflow Service Containers. from sqlplus.
Software Requirements/Prerequisites
SQL Plus
Configuring the Script
N/A
Running the Script


sqlplus apps/ @atg_supp_wf_srv_ctl.sql

Type Number to Perform Operation:

1. Activate

2. Deactivate

3. Abort (Deactivate hangs)



Caution
This script is provided for educational purposes only and not supported by Oracle Support Services. It has been tested internally, however, and works as documented. We do not guarantee that it will work for you, so be sure to test it in your environment before relying on it.
Proofread this script before using it! Due to the differences in the way text editors, e-mail packages and operating systems handle text formatting (spaces, tabs and carriage returns), this script may not be in an executable state when you first receive it. Check over the script to ensure that errors of this type are corrected.

Script
Click here or right click to save the file: atg_supp_wf_srv_ctl.sql
References
NOTE:742340.1 - Oracle Support Applications Technology Group Data Collection Script Repository

Attachments



--------------------------------------------------------------------------------
WF Service Control Script (2.56 KB)


Related



--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------

Oracle E-Business Suite > Applications Technology > Integration > Oracle Workflow Cartridge




Back to top

Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement Rate this document Article Rating
Rate this document
Excellent
Good
Poor

Did this document help you?
Yes
No
Just browsing

How easy was it to find this document?
Very easy
Somewhat easy
Not easy
Comments
Provide feedback for this article. Please use 'Contact Us' for other feedback.
Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.


Cancel

How to Implement Printing for Oracle Applications: Getting Started

How to Implement Printing for Oracle Applications: Getting Started [ID 269129.1]
Modified 11-FEB-2011 Type HOWTO Status PUBLISHED
Applies to:

Oracle Application Object Library - Version: 11.5.1 to 11.5.10.0 - Release: 11.5.10 to 11.5.10

Goal

How to get started on installing printers for E-Business Suite (EBS)? What are the general steps for installing a printer in order to successfully generate and print concurrent report programs from EBS?
Solution

I. PRINTER

The Oracle Applications printer name must be the same printer name that works at the Operating System (OS) command line on the server where the concurrent processing server resides.

If files in Postscript format will be generated and printed from Oracle Applications, make sure to setup a raw OS print queue so that Postscript files will be passed to the target printer without any filtering or actions by the OS print queue or print command. On the Windows Platform, ensure that the printer’s operating systems driver supports the Postscript language and supports the make and model of printer being installed.

Any printer that can be controlled with embedded printer commands, such as PCL, or supports the Postscript language can be used with Oracle Applications, see Note 353071.1 "Where Can I Find A List Of Supported Printers For EBS?"

The only EBS OS print queue requirement is that the print queue is defined and functional from the Concurrent Processing (CP) servers. The same OS print command that works at the OS command line will be used within the EBS printer driver and configuration files. As per Oracle Applications System Administrator's Guide, the Common UNIX Printing System (CUPS) can be used but not required.

The target printer does not have to be physically connected to the CP server. The printer can be a remote printer connected to the CP server with any OS networking software tool, such as TCP/IP printing. Please contact your OS Administrator or OS vendor for assistance with any OS print queue and/or networking issues.


II. PRINTER TYPE

A printer type lists which styles and drivers are available to the assigned printer.

Group printers according to make or family model and utilize a unique printer type name. All printers are not the same or possess the same capabilities and functions. Using only one printer type such as the "HPLJ4SI" type, with one set of printer drivers, to support all make and model of printers may not allow for fine adjustments to one particular printer or a group of printers. That is to say, a change or fine adjustment intended for a specific printer may adversely affect all printers on the instance using the same printer type or driver.


III. PRINT STYLE

A print style specifies the layout of the report’s output file. It is also matched with a driver that supports the same layout for printing.

In a full installation of Oracle Applications there are some 7,500 registered programs, of which 2,800 programs are defined as Oracle Reports. Approximately 70% of these Oracle Reports programs are designed as landscape reports--portrait and landwide are the next two widely used styles.

Therefore, setup the three most widely used styles (landscape, portrait, and landwide) for all printers and do not attempt to make corrections to the associated drivers on a "report by report" basis. Individual reports that do not work well with the three main print styles and printer drivers may need a special or custom style / driver to print correctly. Custom reports will typically require a custom print style or driver, see Note 357941.1 "Applications Product Support Guidelines Regarding Custom Reports and Programs"

Hint: For ease and convenience in release 11i, rather than creating new styles, use the existing styles “as is” or modify them as needed. The bulk of the printing instructions are contained in the printer driver and the SRW driver; therefore, the same print style can normally be re-used with several different printers and printer types.


IV. PRINT DRIVER

A printer driver provides the needed commands to initialize a printer and to invoke an OS print command or a print program or routine.

Oracle Applications provides a simple beginning set of printer drivers. These generic or plain drivers are working examples intended for the printer make or model stated in driver name and description. They may or may not work optimally with other printers. Oracle does not provide additional deliverable examples; therefore, outside of this set, a custom printer driver needs to be defined.

An initialization and reset string is needed to define a printer driver in Oracle Applications. The initialization string, also known as a "setup string", is printer dependent information. It instructs the printer on which printing characteristics are needed for the document to be printed. The printer’s vendor typically supplies the initialization string or provides information on how to construct printer-controlling commands.

Typically a simple initialization string can be found in the printer's user guide or technical reference manual. The back of the manual should have a section on supported printer command languages and/or commonly used printer commands and control characters, see Note 152285.1 "Building a Printer Initialization String for Oracle"

The best setup method is to create an initialization string using the printer command language utilized by your printer. An alternate setup method is to test existing printer drivers for compatibility with your printer. Unfortunately, the latter choice is a "trial and error" approach that may or may not achieve the desired printing appearance. For precision printing, like checks or pre-printed forms, the initialization string will likely require fine tuning, see Note 106186.1 "How to Test an Initialization String Outside of Oracle Applications".

The Apps driver’s “Arguments” field needs to contain the print command that works at the operating systems command line on the server where the concurrent manager resides. Printers on the Windows platform with shared and/or networked printers may need to be registered with the Windows Universal Naming Convention (UNC) of \\Server_Name\Printer_Name, according to the print command that works form a DOS / Command window.

When using the UNC to register the printer in the Apps form, include the slashes with the names.


V. SETUP STEPS

Existing printer types, styles, and drivers can be modified or a new record can be created. Adding a new record is the preferred approach. The printer type, styles, or drivers can have any name that best describe its usage. Additionally, it is more secured during upgrades than modifying seeded records; that is, Oracle seeded records can be overwritten by a patch or an upgrade process.

Concisely, the steps required to defined a printer for Oracle Applications are as follows:

1. Setup and verify the operation of the printer and print queue at the operating system level--test from the OS command line prompt.

2. Identify, select, or define a new Apps printer drivers that will support the specified printer make or model.

3. Identify, select, or define a new Apps printer type to register all needed printer styles and drivers.

4. Register an Apps printer name and associate an Apps printer type to the newly registered printer name.


For detailed setup instructions, please review the chapter titled "Printers" in the Oracle Applications System Administrator's Guide. Also see Note 123140.1 "How to Setup Printer for Oracle Applications 10.7 - 11.5.x" and Note 112172.1 "Oracle Applications Character Printing"

NOTE 1: Please keep in mind that Apps printer driver information is cached in memory, the concurrent manager will need to be bounced in order to make any recent changes take effect.

The following Notes may be helpful with common setup problems and oversights:

Note 262796.1 "Standard Reports Just Print the First Row or Double Space"
Note 359716.1 "Apps Reports Generate and/or Print With Incorrect Page Break Points"
Note 352384.1 "Reprint Does Not Correctly Print When The Original Request Is Formatted By Noprint"
Note 189708.1 "Oracle Reports 6i Setup Guide for Oracle Applications 11i"


VI. PASTA

If the target printer supports the Postscript language and a quick & effective setup is desired, without having to seek, utilize, or understand PCL initialization strings or line termination commands, Pasta can greatly help with setting up a printer.

Oracle Applications has a printing tool called PASTA that can help Administrator quickly configure a Postscript ready printer. Although Pasta is optional for most installations, it required for multilingual installations and installations using the Unicode / UFT8 character set, see Note 356501.1 "How to Setup Pasta Quickly and Effectively"

PASTA is the only viable solution when dealing with multiple languages and multiple printers in a UTF8 / AL32UTF8 character set environment. Otherwise, an extensive amount of time will be spent identifying which fonts are supported by a particular symbol set and which symbol set matches up well with the Unicode super set. "Most printers can not handle UTF8 encoded data". As per the Printing chapter in the Oracle Applications System Administrator's Guide, "In order to print reports with the UFT8 character set, you 'must' configure PASTA".

UNABLE TO PRINT CHECKS AFTER RESTARTING A PAYMENT BATCH

UNABLE TO PRINT CHECKS AFTER RESTARTING A PAYMENT BATCH [ID 1042458.6]
Modified 28-OCT-2008 Type PROBLEM Status PUBLISHED

Problem Description
-------------------
You are attempting to reprint checks after experiencing a printer problem.
You have restarted a payment batch; however, you are unable to reprint
checks from the Actions form.


Product Name: Oracle Payables AP
Module Title: Invoice Payment Workbench
Technical Name: APXPAWKB


Steps Required to replicate problem
-----------------------------------
1. Payment Batches -> Actions -> Confirm.
2. Press the Restart button and then enter the first check number.

The Oracle Payables User Guide 10SC Volume 1 p. 5-28 leads you
to think that you can print from the Actions form before confirming.



Solution Description
--------------------
You must use the reprint function on the Concurrent Requests
Summary form to reprint checks.

Navigation Path: Payables \ Navigate Other Concurrent

1. Query the Request ID for the specific payment format process.

2. Under the top menu bar click on Special then Reprint.

How to reprint damaged/spoiled checks in the middle of a Payment Batch printing process

How to reprint damaged/spoiled checks in the middle of a Payment Batch printing process ? [ID 269721.1]
Modified 05-DEC-2010 Type HOWTO Status PUBLISHED
Applies to:

Oracle Payables - Version: 11.5.8 to 11.5.10.2 - Release: 11.5.10 to 11.5.10
Information in this document applies to any platform.
Goal

How to reprint specific documents in a payment batch where one or more checks before
the last printed check are damaged during printing without having to print those checks
in a separate payment batch?
Solution

Do a quick check on this only check and print it.
NOTE : The check number will be a different one.
References

How to Restrict Access to Dedictated Check Printer

How to Restrict Access to Dedictated Check Printer [ID 145070.1]
Modified 29-MAY-2009 Type HOWTO Status PUBLISHED


goal: How to restrict access to dedicated check printer
fact: Oracle Payables



fix:

Oracle applications does not have an option to totally restrict access to the
check printer, but a certain level of control can be executed as follows:

System Administrator:

1. Set up a printer style called PRINT CHECKS (or something similar to flag the
printer)
Navigate > Install > Printer > Style
2. Install > printer => register
query up that printer
click on printer types
click on style
and assign that style to that printer
save

This will not stop the users from having access to this printer but to print to
this printer the style must be changed in the completion options when selecting
a printer.

If the style is not changed the reports will error out and this might make them
think twice about choosing your check printer. Possibliy the check printer is
locked in the check printing room which would raise another flag for users not
to use this printer.

Check Printing Frequently Asked Questions

Check Printing Frequently Asked Questions [ID 110406.1]

Frequently Asked Questions
Oracle Payables
Check Printing
Release 10.7, 11, 11.5 (11i)


1. Q: Checkstock: How can I determine what has locked my check stock file?
2. Q: Checkstock: How can I utilize checkstock that falls in the middle of a voided range of checks?
3. Q: Checkstock: How do I determine the Program name for my Checks?
4. Q: Format: Which Oracle Payables check format should I use?
5. Q: Format: How can I change the currency verbiage on my checks?
6. Q: Format: Does Oracle Payables provide EFT output in NACHA format?
7. Q: Print: What information do I need to troubleshoot a check alignment issue?
8. Q: Print: How do I determine what printer Style is being used for my Payables checks?
9. Q: Print: When I print my checks print to the printer, I see a big exclamation point on the check.
10. Q: Print: How can I reprint checks after the payment batch has been formatted?
11. Q: Void: How can a voided check that was actually cashed be corrected?
12. Q: What are the MetaLink keywords I should use when searching for Payables reports on MetaLink?
13. Q: What articles, white papers, or manuals should I read for more information on Payables check printing issues?
14. Q: The questions listed in this guide do not address my question.
1. Q: Checkstock: How can I determine what has locked my check stock file?
When I attempt to select my check stock I get a message that it is unavailable as it is in use by another payment batch, however, I do not have another batch in process.

A: Run the following scripts to determine why the check stock is considered in use:


SELECT CHECKRUN_NAME
FROM AP_INVOICE_SELECTION_CRITERIA
WHERE CHECK_STOCK_ID = :b1
AND STATUS NOT IN
( 'CONFIRMED','CANCELED','QUICKCHECK' )
SELECT CHECKRUN_NAME, CHECK_STOCK_ID, ORG_ID, STATUS
FROM AP_INV_SELECTION_CRITERIA_ALL
WHERE STATUS NOT IN
( 'CONFIRMED','CANCELED','QUICKCHECK' );


[TOP]
2. Q: Checkstock: How can I utilize checkstock that falls in the middle of a voided range of checks?

I have voided some check stock that actually fell in the middle of my check number range.

Now I cannot utilize the numbers at the beginning of my range. How can I use the earlier check numbers? There is valid checkstock from before the range that is now unusable. Here is an example.

Original checkstock: Last Used: 10 Last Available:100
Voided checkstock: 20 through 30.
Current listing of checkstock: Last Used: 30 Last Available:100

I now wish to use checks 11 through 19. This payment document starts on check 31

A: You need to define a new payment document that uses the missing checkstock range. As per the example:

Define a new checkstock with the following values: Last Used:10 Last Available:19
You will now be able to use these checks.

Here are some select statements to help you make sure the check range is not accounted for :
Verify check status at sqlplus for the range you want to define.

select bank_account_name, bank_account_id
from ap_bank_accounts_all
where bank_account_name like '';
select check_stock_id, name, bank_account_id
from ap_check_stocks_all
where bank_account_id = ;
select check_number, check_stock_id, status_lookup_code
from ap_checks_all
where bank_account_id =
and check_number >
and check_number < ;
After confirming the above, define a new payment document for the missing range.

[TOP]

3. Q:Checkstock: How do I determine the Program name for my Checks?

A:
Navigate within AP Manager responsibility: Setup=>Payment=>Banks
Query up Bank that using the format in question.
Click on Bank Accounts button.
Query up correct account.
Click on Payables Documents button.
For the document being used, note the Payment Format.

2. Navigate within AP Manager responsibility: Setup=>Payment=>Formats
Query up the Format from above step.
Payment method should be Check.
At the bottom of the screen, in the Programs box note the value for Format
Payments.
Place cursor in Format Payments field and call up the list of values.
For the noted value, find the associated Program name and document it.

[TOP]

4. Q: Format: Which Oracle Payables check format should I use?

A:There are two executables for printing checks APXPBFEG is called the 'Evergreen Format'. Evergreen is the company that supplies forms and printer cartridges that are compatible with the Evergreen check format. APXPBFOR is called the 'Oracle Standard Format'.

Oracle Payables includes five concurrent programs that print checks. Each of these five programs use one of the two executables, with varying Execution Options. You may view these programs in the Define Concurrent Program form when you are signed on with System Administrator responsibilities.

Evergreen Format
If you query the Executable APXPBFEG, you will see three different concurrent programs in the Short Name field (i.e., APXPBFEG, APXPBFEF, APXPBFEL).

The following is a description of each of the concurrent programs:
a. APXPBFEG: The default name for this program is Evergreen, Long. This is the basic Evergreen payment format. It has no special formatting and is designed for non-laser printers. It does not use any Execution Options.
b. APXPBFEF: The default name for this program is Evergreen, Form Feed. This format is designed to be used with laser printers when printing on preprinted check stock. There is a form feed (Control L) after every page which is required for laser printers. The print style is portrait and the Execution Option is p_continuous_stationery='N'.

c. APXPBFEL: The default name for this program is Evergreen, Laser. This
format is designed to be used with laser printers when printing on blank check stock. This process requires a laser printer which uses a cartridge (normally purchased from Evergreen). It prints all the information on the check, including company name and logo, bank name, signature(s) and the MICR encoded line at the bottom of the check. If this program is used without the printer cartridge, you will see two large exclamation marks (!!) near the signature line. The print style is Portrait, Laser and the Execution Options vary, but it must contain at least p_printer_code_mask = '101,102,111,121,122,141'and p_continuous_stationery='N'.

Oracle Standard Format
If you query on the Executable APXPBFOR, you will see two concurrent programs (i.e., APXPBFOR and APXPBFOF).

The following is a description of each of the concurrent programs:

a. APXPBFOR: The default name for this program is Standard Oracle. This
format is designed for non-laser printers. The print style is Dynamic Portrait and there are no Execution Options.

b. APXPBFOF: The default name for this program is Standard Oracle, Form Feed. This format is designed for laser printers

[TOP]

5. Q: Format: How can I change the currency verbiage on my checks?

For example, I would like 'POUNDS' instead of 'DOLLARS'. Currently my check reads 1000 Dollars and 50 cents. It should read 1000 Pounds and 50 pennies

A: You need to change the verbiage in the options field for the payment format. (This is the explanation for GUI users.)

Copy your Format Payment and add some options to it to make the verbiage read Pounds and pennies. Then create a new Payment Format that uses this new Format Payment. Then put this new Payment Format on the Bank Payment Document for the bank account that needs to pay in Irish Pounds.
1. Define a new Payment Program under System Administrator.
Navigate to Concurrent -> Program -> Define
Query up the Evergreen payment program you are using (ex. APXPBFEG).

2. Click on the 'Copy to' button.
Enter a value in the 'Program' field type, for example, "Irish Pounds Program".
Enter a value in the 'Short name' field type, for example, "APXPBIPP".

3. Edit the Options field in the Executable zone (Do not click the 'Parameters' button.) In the 'Options' field, enter the following 4 options on one line with one blank space between each option:
P_UNIT_SINGULAR="Pound"
P_UNIT_PLURAL="Pounds"
P_SUB_UNIT_SINGULAR="penny"
P_SUB_UNIT_PLURAL="pennies"


(For other currencies, replace "Pound" with "Lira", "Peso",etc.)

4. Define a Payment Program under payables: Login as the Payables Manager responsibility. Navigate to Setup -> Payment -> Programs
Enter a value in the Name field type, for example, Irish Pounds Programs. In the Type field, use the list of values to select Format Payments. In the Registered Name field type the new program name that you created in step number 2, for example, "APXPBIPP".

5. Define a new Payment Format under payables: Navigate to Setup -> Payment -> Formats

Query up the Payment Format you are using for the U.S.A., for example, Evergreen Long (Laser). Enter a value in the Payment Format field type, for example, Irish Pounds Payment Format. In the Format Payments field, use the list of values to select Irish Pounds Programs.

6. Change the bank account to use this the new Payment Format. Navigate to Setup -> Payment -> Banks. Query up your bank. Select the 'Bank Accounts' button. Query the account that you would like to use that the new format. Select the Payables Documents button. Use the list of values in the Payment Format field to select the new Document, for example, Irish Pounds Payment Format.

7. Format and print your checks again. They will print now print your new verbage.

[TOP]

6. Q: Format: Does Oracle Payables provide EFT output in NACHA format?

A: Previous to Family Pack G, the EFT process supported BACS, the UK standard, but not NACHA. A third party software or a customized payment format was being used. The following companies could provide a solution: Oracle consulting (800) 578-4672, Bottomline Technology (603) 559-5305 http://www.bottomline.com, Sterling Commerce (949) 623-8350, St. Paul Software http://www.stpaulsoftware.com. In addition, to the above alternatives, an enhancement request was opened for this issue. Enhancement request #315512. It was implemented on 11i.FIN_PF.G.

[TOP]

7. Q: Print: What information do I need to troubleshoot a check alignment issue?

A: You will need to know the Program name associated with your check format, the printer Style that is attached to the Program, and the Printer Make and Model.

[TOP]

8. Q: Print: How do I determine what printer Style is being used for my Payables checks?

A: Perform the following steps in order to determine the printer Style being used for your Payables checks:

1. Navigate within AP Manager responsibility: Setup=>Payment=>Banks
Query up Bank that using the format in question.
Click on Bank Accounts button.
Query up correct account.
Click on Payables Documents button.
For the document being used, note the Payment Format.
2. Navigate within AP Manager responsibility: Setup=>Payment=>Formats
Query up the Format from above step.
Payment method should be Check.
At the bottom of the screen, in the Programs box note the value for Format
Payments.
Place cursor in Format Payments field and call up the list of values.
For the noted value, find the associated Program name and document it.

3. Check the following from the System Administrator Responsibility:

Navigate: Concurrent=>Program=>Define Query using the Program name documented from the Setup=>Payments=>Format screen in the short name field.

Note the values for Style and Printer
Navigate: Install=>Printer=>Register
Find the printer from above step, and note the associated type.
Click on the Printer Type button, then query the printer type that from above.
Check the style and note the driver associated with the style from previous step.

[TOP]

9. Q: Print: When I print my checks print to the printer, I see a big exclamation point on the check.

It does not appear on Help=>View My Requests, however. How do I prevent this from printing on my check?

A: You have selected the Evergreen ROM cartridge check format but do not own a ROM cartridge. The cartridge it designed to print graphics, such a logos and MICR encoding. You must select a different check program.
1. Navigate: Setup=>Payment=>Formats
2. Query your check format name.
Place your cursor in the Format Payments field in the Programs zone. Use
the list of values (LOV) to select a program OTHER than APXPBFEL (Evergreen Format (Laser)). You should select APXPBFEG (Evergreen: USD) if you are using a tract driven printer Evergreen. You should select APXPBFEF (Evergreen (Form Feed) if you are using a laser printer.

[TOP]

10. Q: Print: How can I reprint checks after the payment batch has been formatted?

A: Please note, these instructions are for SmartClient or NCA, not character.
Navigate to the concurrent request summary form: Other->Concurrent Either query the format payment concurrent request, or query all and Select tools (or special depending on versions)...reprint from the toolbar. This opens the reprint dialog box. Select the number of copies, printer, and print style, then ok.

[TOP]

11. Q: Void: How can a voided check that was actually cashed be corrected?

In Accounts Payable, a check was paid against an invoice and then voided, yet the check went out and was cashed.

A: Create a 0$ invoice with 2 distribution lines, 1 for the expense account as a debit and the other distribution lines to the cash account as a credit. Make a manual payment against this invoice. If this was just a simple invoice that had been created and paid, then payment voided the following would have occurred:

Original Invoice Payment Void Payment
debit expense 1300 debit liability 1300 debit cash 1300
credit liability 1300 credit cash 1300 credit liability 1300

In order to resolve the issue, you would create a 0$ invoice with two new distribution lines:
Line 1 1300
debit expense 1300
credit liability 1300
Line 2 -1300 (fill in the expense account as the cash account) which will generate these entries:
Debit liability 1300
Credit cash account 1300 (this is used in place of the expense account)

The invoice is still owed. You will need to issue a 0 manual payment check that will debit liability and credit cash. This will allow the invoice to be paid without incorrectly affecting the cash account.

If this is a 1099 vendor you need to fill in the income tax type for the expense distribution, but for the distribution for the cash, take off the income tax type. That will correct your 1099 values.

Most reports are based on the distributions rather than the invoice total. Make sure to post the new invoice in order to ensure that your reports are correct as well.

[TOP]

12. Q: What are the MetaLink keywords I should use when searching for Payables check printing issues on MetaLink?

A: apxpbfeg, alignment, printer, style, Evergreen, void, remittance

[TOP]

13. Q: What articles, white papers, or manuals should I read for more information on
Payables check printing issue.

A:
Payable Printing FAQ
Payables Check Printing FAQ
System Administrator's Guide release 10.7
System Administrator's Guide release 11
System Administrator's Guide release 11i
AP News Volume 4
[TOP]
14. Q: The questions listed in this guide do not address my question.

A: If the FAQ list for check printing does not answer your question, please click here to log an iTAR.

[TOP]

Checked for relevance on 14-Jan-2008

Frequently Asked Questions
Oracle Payables
Check Printing
Release 10.7, 11, 11.5 (11i)


1. Q: Checkstock: How can I determine what has locked my check stock file?
2. Q: Checkstock: How can I utilize checkstock that falls in the middle of a voided range of checks?
3. Q: Checkstock: How do I determine the Program name for my Checks?
4. Q: Format: Which Oracle Payables check format should I use?
5. Q: Format: How can I change the currency verbiage on my checks?
6. Q: Format: Does Oracle Payables provide EFT output in NACHA format?
7. Q: Print: What information do I need to troubleshoot a check alignment issue?
8. Q: Print: How do I determine what printer Style is being used for my Payables checks?
9. Q: Print: When I print my checks print to the printer, I see a big exclamation point on the check.
10. Q: Print: How can I reprint checks after the payment batch has been formatted?
11. Q: Void: How can a voided check that was actually cashed be corrected?
12. Q: What are the MetaLink keywords I should use when searching for Payables reports on MetaLink?
13. Q: What articles, white papers, or manuals should I read for more information on Payables check printing issues?
14. Q: The questions listed in this guide do not address my question.
1. Q: Checkstock: How can I determine what has locked my check stock file?
When I attempt to select my check stock I get a message that it is unavailable as it is in use by another payment batch, however, I do not have another batch in process.

A: Run the following scripts to determine why the check stock is considered in use:


SELECT CHECKRUN_NAME
FROM AP_INVOICE_SELECTION_CRITERIA
WHERE CHECK_STOCK_ID = :b1
AND STATUS NOT IN
( 'CONFIRMED','CANCELED','QUICKCHECK' )
SELECT CHECKRUN_NAME, CHECK_STOCK_ID, ORG_ID, STATUS
FROM AP_INV_SELECTION_CRITERIA_ALL
WHERE STATUS NOT IN
( 'CONFIRMED','CANCELED','QUICKCHECK' );


[TOP]
2. Q: Checkstock: How can I utilize checkstock that falls in the middle of a voided range of checks?

I have voided some check stock that actually fell in the middle of my check number range.

Now I cannot utilize the numbers at the beginning of my range. How can I use the earlier check numbers? There is valid checkstock from before the range that is now unusable. Here is an example.

Original checkstock: Last Used: 10 Last Available:100
Voided checkstock: 20 through 30.
Current listing of checkstock: Last Used: 30 Last Available:100

I now wish to use checks 11 through 19. This payment document starts on check 31

A: You need to define a new payment document that uses the missing checkstock range. As per the example:

Define a new checkstock with the following values: Last Used:10 Last Available:19
You will now be able to use these checks.

Here are some select statements to help you make sure the check range is not accounted for :
Verify check status at sqlplus for the range you want to define.

select bank_account_name, bank_account_id
from ap_bank_accounts_all
where bank_account_name like '';
select check_stock_id, name, bank_account_id
from ap_check_stocks_all
where bank_account_id = ;
select check_number, check_stock_id, status_lookup_code
from ap_checks_all
where bank_account_id =
and check_number >
and check_number < ;
After confirming the above, define a new payment document for the missing range.

[TOP]

3. Q:Checkstock: How do I determine the Program name for my Checks?

A:
Navigate within AP Manager responsibility: Setup=>Payment=>Banks
Query up Bank that using the format in question.
Click on Bank Accounts button.
Query up correct account.
Click on Payables Documents button.
For the document being used, note the Payment Format.

2. Navigate within AP Manager responsibility: Setup=>Payment=>Formats
Query up the Format from above step.
Payment method should be Check.
At the bottom of the screen, in the Programs box note the value for Format
Payments.
Place cursor in Format Payments field and call up the list of values.
For the noted value, find the associated Program name and document it.

[TOP]

4. Q: Format: Which Oracle Payables check format should I use?

A:There are two executables for printing checks APXPBFEG is called the 'Evergreen Format'. Evergreen is the company that supplies forms and printer cartridges that are compatible with the Evergreen check format. APXPBFOR is called the 'Oracle Standard Format'.

Oracle Payables includes five concurrent programs that print checks. Each of these five programs use one of the two executables, with varying Execution Options. You may view these programs in the Define Concurrent Program form when you are signed on with System Administrator responsibilities.

Evergreen Format
If you query the Executable APXPBFEG, you will see three different concurrent programs in the Short Name field (i.e., APXPBFEG, APXPBFEF, APXPBFEL).

The following is a description of each of the concurrent programs:
a. APXPBFEG: The default name for this program is Evergreen, Long. This is the basic Evergreen payment format. It has no special formatting and is designed for non-laser printers. It does not use any Execution Options.
b. APXPBFEF: The default name for this program is Evergreen, Form Feed. This format is designed to be used with laser printers when printing on preprinted check stock. There is a form feed (Control L) after every page which is required for laser printers. The print style is portrait and the Execution Option is p_continuous_stationery='N'.

c. APXPBFEL: The default name for this program is Evergreen, Laser. This
format is designed to be used with laser printers when printing on blank check stock. This process requires a laser printer which uses a cartridge (normally purchased from Evergreen). It prints all the information on the check, including company name and logo, bank name, signature(s) and the MICR encoded line at the bottom of the check. If this program is used without the printer cartridge, you will see two large exclamation marks (!!) near the signature line. The print style is Portrait, Laser and the Execution Options vary, but it must contain at least p_printer_code_mask = '101,102,111,121,122,141'and p_continuous_stationery='N'.

Oracle Standard Format
If you query on the Executable APXPBFOR, you will see two concurrent programs (i.e., APXPBFOR and APXPBFOF).

The following is a description of each of the concurrent programs:

a. APXPBFOR: The default name for this program is Standard Oracle. This
format is designed for non-laser printers. The print style is Dynamic Portrait and there are no Execution Options.

b. APXPBFOF: The default name for this program is Standard Oracle, Form Feed. This format is designed for laser printers

[TOP]

5. Q: Format: How can I change the currency verbiage on my checks?

For example, I would like 'POUNDS' instead of 'DOLLARS'. Currently my check reads 1000 Dollars and 50 cents. It should read 1000 Pounds and 50 pennies

A: You need to change the verbiage in the options field for the payment format. (This is the explanation for GUI users.)

Copy your Format Payment and add some options to it to make the verbiage read Pounds and pennies. Then create a new Payment Format that uses this new Format Payment. Then put this new Payment Format on the Bank Payment Document for the bank account that needs to pay in Irish Pounds.
1. Define a new Payment Program under System Administrator.
Navigate to Concurrent -> Program -> Define
Query up the Evergreen payment program you are using (ex. APXPBFEG).

2. Click on the 'Copy to' button.
Enter a value in the 'Program' field type, for example, "Irish Pounds Program".
Enter a value in the 'Short name' field type, for example, "APXPBIPP".

3. Edit the Options field in the Executable zone (Do not click the 'Parameters' button.) In the 'Options' field, enter the following 4 options on one line with one blank space between each option:
P_UNIT_SINGULAR="Pound"
P_UNIT_PLURAL="Pounds"
P_SUB_UNIT_SINGULAR="penny"
P_SUB_UNIT_PLURAL="pennies"


(For other currencies, replace "Pound" with "Lira", "Peso",etc.)

4. Define a Payment Program under payables: Login as the Payables Manager responsibility. Navigate to Setup -> Payment -> Programs
Enter a value in the Name field type, for example, Irish Pounds Programs. In the Type field, use the list of values to select Format Payments. In the Registered Name field type the new program name that you created in step number 2, for example, "APXPBIPP".

5. Define a new Payment Format under payables: Navigate to Setup -> Payment -> Formats

Query up the Payment Format you are using for the U.S.A., for example, Evergreen Long (Laser). Enter a value in the Payment Format field type, for example, Irish Pounds Payment Format. In the Format Payments field, use the list of values to select Irish Pounds Programs.

6. Change the bank account to use this the new Payment Format. Navigate to Setup -> Payment -> Banks. Query up your bank. Select the 'Bank Accounts' button. Query the account that you would like to use that the new format. Select the Payables Documents button. Use the list of values in the Payment Format field to select the new Document, for example, Irish Pounds Payment Format.

7. Format and print your checks again. They will print now print your new verbage.

[TOP]

6. Q: Format: Does Oracle Payables provide EFT output in NACHA format?

A: The EFT process supports BACS, the UK standard, but not NACHA. Currently, a Third party software or a customized payment format must be used. The following companies can provide a solution: Oracle consulting (800) 578-4672, Bottomline Technology (603) 559-5305 http://www.bottomline.com, GEIS (800)560-GEIS http://www.geis.com/html/edi09.html, Sterling Commerce (949) 623-8350 http://www.sterlingcommerce.com/csol/edi/index.html, St. Paul Software http://www.stpaulsoftware.com. In addition, to the above alternatives, an enhancement request has been opened for this issue. Enhancement request #315512

[TOP]

7. Q: Print: What information do I need to troubleshoot a check alignment issue?

A: You will need to know the Program name associated with your check format, the printer Style that is attached to the Program, and the Printer Make and Model.

[TOP]

8. Q: Print: How do I determine what printer Style is being used for my Payables checks?

A: Perform the following steps in order to determine the printer Style being used for your Payables checks:

1. Navigate within AP Manager responsibility: Setup=>Payment=>Banks
Query up Bank that using the format in question.
Click on Bank Accounts button.
Query up correct account.
Click on Payables Documents button.
For the document being used, note the Payment Format.
2. Navigate within AP Manager responsibility: Setup=>Payment=>Formats
Query up the Format from above step.
Payment method should be Check.
At the bottom of the screen, in the Programs box note the value for Format
Payments.
Place cursor in Format Payments field and call up the list of values.
For the noted value, find the associated Program name and document it.

3. Check the following from the System Administrator Responsibility:

Navigate: Concurrent=>Program=>Define Query using the Program name documented from the Setup=>Payments=>Format screen in the short name field.

Note the values for Style and Printer
Navigate: Install=>Printer=>Register
Find the printer from above step, and note the associated type.
Click on the Printer Type button, then query the printer type that from above.
Check the style and note the driver associated with the style from previous step.

[TOP]

9. Q: Print: When I print my checks print to the printer, I see a big exclamation point on the check.

It does not appear on Help=>View My Requests, however. How do I prevent this from printing on my check?

A: You have selected the Evergreen ROM cartridge check format but do not own a ROM cartridge. The cartridge it designed to print graphics, such a logos and MICR encoding. You must select a different check program.
1. Navigate: Setup=>Payment=>Formats
2. Query your check format name.
Place your cursor in the Format Payments field in the Programs zone. Use
the list of values (LOV) to select a program OTHER than APXPBFEL (Evergreen Format (Laser)). You should select APXPBFEG (Evergreen: USD) if you are using a tract driven printer Evergreen. You should select APXPBFEF (Evergreen (Form Feed) if you are using a laser printer.

[TOP]

10. Q: Print: How can I reprint checks after the payment batch has been formatted?

A: Please note, these instructions are for SmartClient or NCA, not character.
Navigate to the concurrent request summary form: Other->Concurrent Either query the format payment concurrent request, or query all and Select special...reprint from the toolbar. This opens the reprint dialog box. Select the number of copies, printer, and print style, then ok.

[TOP]

11. Q: Void: How can a voided check that was actually cashed be corrected?

In Accounts Payable, a check was paid against an invoice and then voided, yet the check went out and was cashed.

A: Create a 0$ invoice with 2 distribution lines, 1 for the expense account as a debit and the other distribution lines to the cash account as a credit. Make a manual payment against this invoice. If this was just a simple invoice that had been created and paid, then payment voided the following would have occurred:

Original Invoice Payment Void Payment
debit expense 1300 debit liability 1300 debit cash 1300
credit liability 1300 credit cash 1300 credit liability 1300

In order to resolve the issue, you would create a 0$ invoice with two new distribution lines:
Line 1 1300
debit expense 1300
credit liability 1300
Line 2 -1300 (fill in the expense account as the cash account) which will generate these entries:
Debit liability 1300
Credit cash account 1300 (this is used in place of the expense account)

The invoice is still owed. You will need to issue a 0 manual payment check that will debit liability and credit cash. This will allow the invoice to be paid without incorrectly affecting the cash account.

If this is a 1099 vendor you need to fill in the income tax type for the expense distribution, but for the distribution for the cash, take off the income tax type. That will correct your 1099 values.

Most reports are based on the distributions rather than the invoice total. Make sure to post the new invoice in order to ensure that your reports are correct as well.

[TOP]

12. Q: What are the MetaLink keywords I should use when searching for Payables check printing issues on MetaLink?

A: apxpbfeg, alignment, printer, style, Evergreen, void, remittance

[TOP]

13. Q: What articles, white papers, or manuals should I read for more information on
Payables check printing issue.

A:
Payable Printing FAQ
Payables Check Printing FAQ
System Administrator's Guide release 10.7
System Administrator's Guide release 11
System Administrator's Guide release 11i
AP News Volume 4
[TOP]
14. Q: The questions listed in this guide do not address my question.

A: If the FAQ list for check printing does not answer your question, please click here to log an iTAR.

Oracle E-Business Suite Release 11i Technology Stack Documentation Roadmap

Oracle E-Business Suite Release 11i Technology Stack Documentation Roadmap [ID 207159.1]
Modified 30-MAR-2011 Type REFERENCE Status PUBLISHED
This note acts as a master list of My Oracle Support knowledge documents written and maintained by Oracle E-Business Suite Development to describe the use, configuration, and management of the various components that make up the Technology Stack in Oracle E-Business Suite Release 11i. Some of the components mentioned are standard, while others are optional.

The documents listed do not replace the standard books in the Documentation Library, but should be read in conjunction with the relevant books: for example, a document may refer the reader to a book for background information, and a book may point to a document as the best source of up-to-date information on a new or rapidly-changing topic.

The most current version of this document can be obtained in My Oracle Support Knowledge Document 207159.1.

Note: The Release 12 equivalent of this document is My Oracle Support Knowledge Document 380482.1.

There is a change log at the end of this document.

In This Document

The various notes written and maintained by Oracle E-Business Suite Development have been divided into the following categories:

Section 1: Installation and Configuration
Section 2: Database Tier
Section 3: Application Tier
Section 4: Client Tier and Java
Section 5: Security
Section 1: Installation and Configuration

1.1 General

Document 165195.1, Using AutoConfig to Manage System Configurations with Oracle Applications 11i
Document 218089.1, Frequently Asked Questions About Using AutoConfig With Oracle Applications Release 11i
Document 217368.1, Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i
Document 240744.1, Technology Validation Utility for Oracle Applications Release 11.5.9
Document 403311.1, United States and Canada 2007 Daylight Saving Time (DST) Compliance for Oracle E-Business Suite
Document 458452.1, Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite 11i
Document 302859.1, Using Cygwin to Maintain Oracle Applications Release 11i on Windows
Document 277535.1, Recommended Setup For Client/Server Products With Oracle E-Business Suite Release 11i
Document 781366.1, Search Modeler 1.1 for Oracle E-Business Suite Readme
Document 975182.1, Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate
Document 1112325.1, Deploying Oracle GoldenGate to Achieve Operational Reporting for Oracle E-Business Suite
1.2 Cloning

Document 230672.1, Cloning Oracle Applications Release 11i with Rapid Clone
Document 216664.1, Frequently Asked Questions About Cloning Oracle Applications 11i
Document 783188.1, Certified Oracle RAC Scenarios for Oracle E-Business Suite Cloning
1.3 Oracle VM

Document 465915.1, Using Oracle VM with Oracle E-Business Suite Release 11i or Release 12
1.4 Secure Enterprise Search

Document 953378.1, Enabling Secure Enterprise Search for Oracle E-Business Suite, Release 11i
Section 2: Database Tier

2.1 General

Document 285267.1, Oracle E-Business Suite Release 11i and Database FAQ
Document 216205.1, Database Initialization Parameters and Configuration for Oracle Applications 11i
Document 351646.1, Configuring Oracle E-Business Suite Release 11i with 10g Database on Raw Devices
Document 343917.1, Frequently Asked Questions: Using Oracle Applications with an x86-64 Database Server,
Document 311717.1, Frequently Asked Questions: Using Oracle Applications with an Itanium Database Server
Document 332977.1, Using Oracle Applications with an HP OpenVMS Alpha Database Server
Document 554539.1, Using Database Partitioning with Oracle E-Business Suite
2.2 Interoperability Notes

Document 216550.1, Interoperability Notes Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
Document 282038.1, Interoperability Notes Oracle Applications Release 11i with Oracle Database 10g Release 1 (10.1.0)
Document 362202.1, Interoperability Notes Oracle Applications Release 11i with Oracle Database 10g (10.1.0.4)
Document 362203.1, Interoperability Notes Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0)
Document 452783.1, Interoperability Notes Oracle E-Business Suite Release 11i with Oracle Database 11g Release 1 (11.1.0)
Document 881505.1, Interoperability Notes Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0)
2.3 Oracle Real Application Clusters and High Availability

Document 312731.1, Configuring Oracle Applications Release 11i with 10g Real Application Clusters and 10g Automated Storage Management
Document 362135.1, Configuring Oracle E-Business Suite Release 11i with 10g Release2 RAC and ASM
Document 455398.1, Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i
Document 823586.1, Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 11i
Document 279956.1, Oracle E-Business Suite Release 11i with 9i RAC (Installation and Configuration Using AutoConfig)
Document 216212.1, Business Continuity for Oracle Applications Release 11i, Database Releases 9i and 10g
Document 341437.1, Business Continuity for Oracle Applications Release 11i Using Oracle Real Application Clusters and Physical Standby Database
Document 294652.1, Configuration of Forms/Self-Service for Oracle E-Business Suite 11i RAC Environments (Load Balancing and Load Direction)
Document 403347.1, Maximum Availability Architecture and Oracle E-Business Suite Release 11i
Document 406652.1, Upgrading Oracle Applications 11i Database to Oracle Database 10gR2 with Physical Standby in Place
2.4 Patching

Document 244040.1, Recommended Performance Patches for Oracle E-Business Suite
Document 1147107.1, Database Patch Set Update Overlay Patches Required by E-Business Suite
2.5 Export/Import

Document 204015.1, Export/Import Process for Oracle Applications Release 11i Database Instances Using Oracle8i Enterprise Edition
Document 230627.1, Export/Import Process for Oracle Applications Release 11i Database Instances Using Oracle9i Enterprise Edition
Document 331221.1, Export/Import Process for Oracle Applications Release 11i Database Instances Using Oracle10g Enterprise Edition
Document 362205.1, Export/Import Process for Oracle Applications Release 11i Database Instances Using Oracle Database 10g Release 2
Document 557738.1, Export/Import Process for Oracle E-Business Suite Release 11i Database Instances Using Oracle Database 11g Release 1 or 2
2.6 Split Configurations

Document 304489.1, Using Oracle Applications with a Split Configuration Database Tier on Oracle9i Release 2
Document 356839.1, Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 1
Document 369693.1, Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2
Document 946413.1, Using Oracle E-Business Suite with a Split Configuration Database Tier on Oracle 11g Release 2 Release 2
Section 3: Application Tier

3.1 General

Document 186981.1, Oracle Application Server with Oracle E-Business Suite Release 11i Frequently Asked Questions
Document 223927.1, Oracle Application Server Integration with Oracle E-Business Suite: Statement of Direction
Document 233428.1, Sharing the Application Tier File System in Oracle E-Business Suite11i
Document 242480.1, Using a Staged Applications System to Reduce Patching Downtime
Document 225165.1, Oracle Applications 11i Patching Best Practices and Reducing Downtime
Document 125767.1, Upgrading Developer 6i with Oracle Applications 11i
Document 164317.1, Upgrading Oracle JDBC Drivers with Oracle E-Business Suite 11i
Document 201340.1, Using Forms Listener Servlet with Oracle Applications 11i
Document 181244.1, Configuring an X Display Server for Applications on UNIX Platforms
Document 146468.1, Installing Oracle9i Application Server with Oracle Applications 11i
Document 254618.1, HTTP Server Patches Certified to be used with E-Business Suite 11i
Document 238276.1, Migrating to Linux with Oracle Applications Release 11i
Document 232313.1, Information on Previous Versions of Developer 6i Patchsets
Document 1112325.1, Deploying Oracle GoldenGate to Achieve Operational Reporting for Oracle E-Business Suite
3.2 External Integrations

Document 233436.1, Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
Document 261914.1, Integrating Oracle E-Business Suite Release 11i with Oracle Internet Directory and Oracle Single Sign-On
Document 295606.1, Oracle Application Server 10g with Oracle E-Business Suite Release 11i Troubleshooting Guide
Document 216208.1, Oracle9i Application Server (9iAS) with Oracle E-Business Suite Release 11i Troubleshooting
Document 313418.1, Using Discoverer 10g with Oracle Applications 11i
Document 305918.1, Using Oracle Portal 10g with Oracle E-Business Suite 11i
Document 1074344.1, Using Oracle Portal 11.1.1 with Oracle E-Business Suite Release 11i
Document 306653.1, Installing and Configuring Oracle Application Server Web Cache with Oracle E-Business Suite 11i
Document 1073963.1, Using Discoverer 11.1.1 with Oracle E-Business Suite Release 11i
3.3 Obsolete (Desupported) Configurations

Document 146469.1, Configuring Oracle Applications with Oracle Portal
Document 150832.1, Implementing Oracle Applications Synchronization with LDAP
Document 139516.1, Discoverer 4i with Oracle Applications 11i
Document 257798.1, Using Discoverer 10g (9.0.4) with Oracle Applications 11i
Section 4: Client Tier

Document 1155883.1, Oracle E-Business Suite Desktop Client Hardware and Software Requirements
Document 300482.1, Overview of Using Java with Oracle E-Business Suite Release 11i
Document 124606.1, Upgrading Oracle JInitiator with Oracle Applications 11i
Document 285218.1, Recommended Browsers for Oracle Applications 11i
Document 290807.1, Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
Section 5: Security

Document 189367.1, Best Practices for Securing Oracle E-Business Suite
Document 287176.1, Oracle E-Business Suite 11i Configuration in a DMZ
Document 123718.1, A Guide to Understanding and Implementing SSL with Oracle Applications 11i
Document 340178.1, Enabling SSL with Oracle Application Server 10g and the E-Business Suite
Document 234599.1, Enabling Oracle Label Security in Oracle E-Business Suite
Document 391248.1, Encrypting Oracle E-Business Suite Release 11i Network Traffic Using Advanced Security Option and Advanced Networking Option
Document 403294.1, Using TDE Column Encryption with Oracle E-Business Suite Release 11i
Document 828223.1, Using TDE Tablespace Encryption with Oracle E-Business Suite Release 11i
Document 428503.1, Integrating Oracle E-Business Suite Release 11i with Oracle Database Vault 10.2.0.4
Document 859399.1, Integrating Oracle E-Business Suite Release 11i with Oracle Database Vault 11.1.0.7
Change Log

Date Description
Mar 30, 2011
Corrected title shown for Doc 403294.1.
Added Docs 828223.1 and 554539.1.
Mar 10, 2011
Corrected link for Doc 823586.1 (Section 2.3).
Nov 11, 2010
Added Doc 1112325.1.
Nov 02, 2010
Added Docs 232313.1, 244040.1, 975182.1, and 1147107.1.
Created subsections in Section 1 to match Release 12 roadmap document where applicable.
Reorganized some documents into product-specific groups.
Oct 09, 2010
Added Doc 1074344.1.
Aug 23, 2010
Added Doc 1073963.1.
Aug 04, 2010
Added Doc 1155883.1.
Jan 08, 2010
Fixed typo in preamble.
Dec 14, 2009
Added Documents 238276.1, 557738.1, 881505.1, and 946413.1.
Amended terminology to refer to "My Oracle Support knowledge document" instead of "OracleMetaLink note".
Oct 30, 2009
Added Notes 953378.1 and 781366.1.
Oct 09, 2009
Added Notes 823586.1 and 859399.1.
Aug 10, 2009
Added Note 277535.1.
Jul 01, 2009
Added Notes 403347.1, 216212.1, and 406652.1.
Mar 16, 2009
Added Note 302859.1.
Mar 02, 2009
Added Note 783188.1.
Oct 27, 2008
Added Note 455398.1.
Apr 29, 2008
Added Notes 290807.1, 458452.1, 428503.1, 452783.1, 465915.1; Removed 134375.1.
Feb 22, 2007
Added Notes 403311.1, 285267.1, 341437.1, 2799561.1, 351646.1, 362135.1, 242480.1, 225165.1.
Feb 21, 2007
Updated template; restructured organization and added new references.
Document 207159.1 by Oracle E-Business Suite Development
Copyright © 2007, 2011, Oracle.


Related
Products
Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library
Keywords
9IAS; DISCOVERER; OID; PORTAL; SSO

Back to top