: Oracle Error Messages And Codes Manual

Oracle%20Error%20Messages%20and%20Codes%20Manual

User Manual:

Open the PDF directly: View PDF .
Page Count: 952 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Oracle Applications

Messages Manual

his manual contains a detailed listing of application

messages that appear across the Oracle Applications product

families.

☞

Overview

This manual includes shared messages that appear in Oracle

Financials, Oracle Public Sector Financials, Oracle

Manufacturing, Oracle Human Resources, and Oracle

Application Object Library.

Shared Oracle Applications messages include messages in the

message number range APP–0001 to APP–1999. In addition,

you can find messages for each Oracle Applications product in

this manual.

To help you understand messages that Oracle Applications

display, each message description includes, where appropriate,

the probable cause of the problem and the actions you can take

to solve the problem.

How This Manual Is Organized

This manual contains messages in the range APP–0001 to

APP–72999. Use these messages to help diagnose and solve

application problems.

Messages that are specific to particular applications in the

Oracle Financials, Oracle Public Sector Financials, Oracle

Human Resources, Oracle Manufacturing, and Oracle

Application Object Library are clustered in message number

ranges. For product–specific messages, refer to the message

ranges listed on the Ranges page.

Attention: Many Oracle Application Object Library

messages are shared across all Oracle Applications

Messages from Other Oracle Products

Some messages you may encounter in Oracle Applications

products are generated by Oracle tools and products other than

Oracle Applications. These messages use prefixes other than

APP.

Use the manual appropriate to the Oracle product whose prefix

appears in the message. For example, the Oracle8 Server

product uses the prefix ORA. For ORA messages, such as

”ORA–00018: maximum number of sessions exceeded”, you

would refer to the ORACLE8 Server Messages and Codes

Manual to determine how to fix the problem.

Notational Convention

Throughout this manual you will see terms prefaced by an

ampersand, such as &Routine Name. When Oracle

Applications displays a message online, Oracle Applications

replaces these terms prefaced by an ampersand with the actual

text the term represents. The actual text depends on the

conditions that cause Oracle Applications to display the

message. For example the message ”APP–22104 Request

&REQUEST_ID is on hold” becomes ”APP–22104 Request

17247 is on hold” when you see it online.

Message Ranges

Application Names Message

Ranges

Application Object Library 0000 – 2999

30000 – 31999

Applications Implementation Wizard 54000 – 54999

Applications Data Warehouse 46000 – 46999

Oracle Alert 4000 – 4999

Oracle Assets 47000 – 48999

Oracle Automotive 44000 – 44999

Oracle Bills of Material 20000 – 20999

Oracle Common Modules 55000 – 56999

Oracle Configurator 28000 – 28999

Oracle Cost Management 24000 – 24999

Oracle EDI Gateway 4800 – 4999

Oracle Electronic Commerce 27000 – 27999

Oracle Engineering 21000 – 21999

Oracle Enterprise Peformance Indica-

tors 57000 – 57999

Oracle FastFormula/Human Re-

sources/Payroll/DateTrack 33000 – 34999

Oracle General Ledger (including Re-

port Generator) 8000 – 9999

Oracle Human Resources/Oracle Pay

roll 6000 – 7999

roll

50000 – 52999

Oracle Inventory 5000 – 5999

43000 – 43999

Oracle Manufacturing 23000 – 23999

Oracle Master Scheduling/MRP 22000 – 22999

Oracle Order Entry 17000 – 18999

26000 – 26999

Message

Ranges

Application Names

Oracle Payables 10000 – 10999

Oracle Project Accounting 19000 – 19999

Oracle Project Manufacturing 58000 – 58999

Oracle Public Sector 37000 – 38999

Oracle Purchasing 14000 – 14999

Oracle Quality 16000 – 16999

Oracle Receivables 11000 – 12999

15000 – 15999

42000 – 42999

Oracle Release Accounting 44500 – 44999

Oracle SSP 35000 – 36999

Oracle Sales and Marketing 45000 – 45999

Oracle Service 3000 – 3999

Oracle Supplier Scheduling 29000 – 29999

Oracle Time Management 39000 – 39999

Oracle Training 13000 – 13999

Oracle Work in Process 25000 – 25999

LOCALIZATIONS

Asia Pacific Localizations 66000 – 67999

Canadian Localizations 64000 – 65999

European Localizations 60000 – 61999

Japanese Localizations 72000 – 73999

Latin American Localizations 62000 – 63999

Middle East and Africa Localizations 70000 – 71999

Regional Localizations 68000 – 69999

RESERVED FOR FUTURE USE

32000 – 32999

40000 – 40499

40500 – 40999

41000 – 41999

49000 – 49999

53000 – 53999

59000 – 59999

Messages

[APP–1] Abort

[APP–1] ECO Documents

[APP–1] Interval to date calculation cannot have payment type as Fixed Amount.

[APP–1] Standard Processes

[APP–1] Target should be greater than 0 for a quota based or unit based quota plan element.

[APP–1] Target should be greater than 0 for a quota based or unit based quota plan element. Please

change the target to a value greater than 0 in plan element form.

[APP–2] A window system failure has been detected in Window &WINDOW, Routine &ROUTINE

with error code &ERRCODE &MESSAGE.

[APP–3] Line Operations

[APP–4] Please alphabetize your #&TYPE user exit list. Your sub user exits are not listed in

alphabetical order in your file xit<app>.c, where <app> is your application short name.

Application Object Library can find your sub user exits faster if you alphabetize the list.

[APP–6] User exit #&EXIT is not defined. Please correct the user exit call in your form, or create

the indicated user exit.

[APP–8] Please write your user exit in the C programming language. You attempted to call a user

exit that was not written in the C programming language. Tokenized user–exits must be written in

[APP–10] AuditTrail was unable to add column &COLUMN to the audit table &TABLENAME

because the type &COLUMNTYPE is not supported. Check to see that your column is not of type

LONG or RAW; these types cannot be audited.

[APP–12] Routine &ROUTINE requested more than 64K of memory. Please contact your system

administrator.

[APP–14] Unable to connect to Application user. Please correct password information for user, or

use the username/password of Application Object Library rather than the application’s

username/password.

[APP–16] No primary key information exists for table &TABLENAME, audit table not made.

Action: Define primary key information for table. Auditing cannot occur on tables without

primary keys.

[APP–20] Please enter a start date less than or equal to the end date You entered a start date

&START that is greater than the end date &END. You must temporarily change the start date to be

less than or equal to the end date in order to move from the start date field to the end date field.

[APP–22] Please enter an end date greater than or equal to the start date You entered an end date

&END that is less than the start date &START. You must temporarily change the end date to NULL

in order to move from the end date field to the start date field.

[APP–24] Table &TABLENAME has too many auditing columns. Column &COLUMN was

rejected. Please disable auditing for this table and audit fewer columns.

[APP–32] The application that owns this form is unknown. To correct this problem, make sure the

form calls the FORM_INFO trigger at the WHEN–NEW–FORM–INSTANCE event.

[APP–36] Cannot find a readable book file named ’&FILE’.

[APP–44] Module &MODULE encountered an error while passing communication channel

&CHANNEL to a child process. Check that your program does not use too many communication

channels. Ensure that it does not pass channels that will not be used by the child process. Exit

Application Object Library and try again immediately, or later when your system is not as busy.

[APP–52] Concurrent Manager cannot find application for concurrent program of your concurrent

request &REQUEST. Please check if the application is registered with Application Object Library.

[APP–54] You have specified invalid arguments for your concurrent program &ROUTINE.

Argument &ARGUMENT exceeds the maximum length allowed. Please enter arguments within the

limits allowed.

[APP–56] Argument &ARGNO is longer than maximum allowed length of 240

[APP–58] You have specified an illegal value for the IMPLICIT token. Legal values are NO, YES,

ERROR or WARNING.

[APP–60] You have specified an invalid resubmit interval type. Valid types are END or START.

[APP–62] The request resubmission unit you specified is not valid or currently supported. Valid

units are: MINUTES, HOURS, DAYS or MONTHS.

[APP–64] You have entered an invalid work shift time. The time must be between 00:00 and 23:59,

in accordance with the HH24:MI time format.

[APP–66] You have entered an invalid time for this work shift. The correct format for the time is

HH24:MI. Example: 14:35.

[APP–70] Routine &ROUTINE cannot construct a file name &FILENAME with extension

&EXTENSION. Check that the specified file name and extension are correct and valid on your

system.

[APP–72] Routine &ROUTINE cannot construct the name of an executable file for your concurrent

request &REQUEST. Check that the file name components are correct and valid on your system.

Check that the environment for the person who started the concurrent manager is correctly set and

that Application Object Library environment variables have the correct value. Important

Application Object Library environment variables include, but are not limited to, FND_TOP,

APPLBIN, and your application’s basepath. Refer to your installation manual for a complete list.

[APP–74] Routine &ROUTINE cannot construct the name of your concurrent request’s log file for

concurrent program &PROGRAM_NAME. Check that the file name components are correct and

valid on your system. Application Object Library constructs your log file name from the concurrent

request ID. Check that the environment for the person who started the concurrent manager is

correctly set and that Application Object Library environment variables have the correct value.

Important Application Object Library environment variables include, but are not limited to,

FND_TOP, APPLLOG, and your application’s basepath. Refer to your installation manual for a

complete list.

[APP–76] Routine &ROUTINE cannot construct the name of the concurrent manager log file

&FILENAME with path &PATH. Check that the file name components are correct and valid on

your system. Check that the environment for the person who started the concurrent manager is

correctly set and that Application Object Library environment variables have the correct value.

Important Application Object Library environment variables include, but are not limited to,

FND_TOP, APPLLOG, and your application’s basepath. Refer to your installation manual for a

complete list.

[APP–78] Routine &ROUTINE cannot construct the name of your concurrent request’s output file

for the concurrent program &PROGRAM_NAME. Check that the file name components are correct

and valid on your system. Application Object Library constructs your output file name from your

user name and the concurrent request ID. Check that the environment for the person who started the

concurrent manager is correctly set and that Application Object Library environment variables have

the correct value. Important Application Object Library environment variables include, but are not

limited to, FND_TOP, APPLOUT, and your application’s basepath. Refer to your installation

manual for a complete list.

[APP–80] Routine &ROUTINE cannot construct the name of your concurrent request’s log file for

your concurrent request &REQUEST. Check that the file name components are correct and valid on

your system. Application Object Library constructs your log file name from the concurrent request

ID. Check that the environment for the person who started the concurrent manager is correctly set

and that Application Object Library environment variables have the correct value. Important

Application Object Library environment variables include, but are not limited to, FND_TOP,

APPLLOG, and your application’s basepath. Refer to your installation manual for a complete list.

[APP–82] Routine &ROUTINE cannot construct the name of your concurrent request’s output file

for your concurrent request &REQUEST. Check that the file name components are correct and valid

on your system. Application Object Library constructs your output file name from your user name

and the concurrent request ID. Check that the environment for the person who started the

concurrent manager is correctly set and that Application Object Library environment variables have

the correct value. Important Application Object Library environment variables include, but are not

limited to, FND_TOP, APPLOUT, and your application’s basepath. Refer to your installation

manual for a complete list.

[APP–84] Routine &ROUTINE cannot create a process ID for your concurrent manager process

&REASON. Check that the unique sequence to generate concurrent process IDs exists. If the

sequence does not exist, contact your system administrator or support representative to create the

sequence. Run the following SQL statement to check that concurrent process ID’s are not obtained

from Application Object Library’s (old) unique identifier table. Run the next SQL statement to

check that the sequence exists. SQL: SELECT NEXT_UNIQUE_IDENTIFIER FROM

FND_UNIQUE_IDENTIFIER_CONTROL WHERE TABLE_NAME =

’FND_CONCURRENT_PROCESSES’; SQL: SELECT

FND_CONCURRENT_PROCESSES_S.NEXTVAL FROM SYSTEM.DUAL;

[APP–86] Routine &ROUTINE cannot create a request ID for your concurrent request &REASON

Cause: &ROUTINE encountered an error while creating a request ID for your concurrent

request. &REASON.

Action: Check that the unique sequence to generate concurrent request IDs exists. If the

sequence does not exist, contact your system administrator or support representative to create the

sequence. Run the following SQL statement to check that concurrent request ID’s are not obtained

from Application Object Library’s (old) unique identifier table. Run the next SQL statement to

check that the sequence exists. SQL: SELECT NEXT_UNIQUE_IDENTIFIER FROM

FND_UNIQUE_IDENTIFIER_CONTROL WHERE TABLE_NAME =

’FND_CONCURRENT_REQUESTS’; SQL: SELECT

FND_CONCURRENT_REQUESTS_S.NEXTVAL FROM SYSTEM.DUAL;

[APP–88] The concurrent manager could not delete your concurrent request’s output file

&FILENAME. Your concurrent request may not have generated an output file. If your request did

generate an output file, then it was not in the expected location or the concurrent manager does not

have privileges to delete the file.

[APP–90] Routine &ROUTINE cannot not run the concurrent program &PROGNAME Check that

the person who started the concurrent manager has privileges to run (execute) the concurrent

program. Contact your system administrator to assign execute privileges.

[APP–92] Routine &ROUTINE cannot find the file &FILENAME to reprint. Check if the file

exists. Check if the person who started the concurrent manager has read privileges on the directory

and on the file. Contact your system administrator to assign read privileges.

[APP–94] Routine &ROUTINE cannot find the logical database with application ID &APPLID and

logical database ID &QUEUEID. Please contact your support representative.

[APP–96] Routine &ROUTINE cannot find the subroutine concurrent program &PROGRAM

belonging to application &APPLSHORT. Please contact your support representative.

[APP–98] Routine &ROUTINE failed to get attribute name for node &NODE, platform

&PLATFORM

Cause: &REASON:

[APP–100] Routine &ROUTINE cannot construct the name of the concurrent manager executable

file for the concurrent manager &QNAME and library &LIBRARY. Check that the file name

components are correct and valid on your system. Check that the environment of the person who

started the concurrent manager is correctly set and that Application Object Library environment

variables have the correct value. Important Application Object Library environment variables

include, but are not limited to, FND_TOP, APPLBIN, and your application’s basepath. Refer to

your installation manual for a complete list.

[APP–102] The basepath environment variable &APPLBASE for the concurrent manager library

&LIBRARY has not been set. &ROUTINE cannot locate the library. Shutdown the concurrent

managers. Set the environment variable to the basepath for the concurrent program. Restart the

concurrent managers.

[APP–104] Routine &ROUTINE cannot construct the name of the concurrent manager log file with

basepath &BASEPATH and subdirectory &DIR. Check that the directory components are correct

and valid on your system.

[APP–106] Routine &ROUTINE cannot get next queue ID – &REASON

[APP–108] Routine &ROUTINE cannot get profile option value for &PROFILE. &REASON Check

that the profile option exists and that users have read privileges to the profile option. Contact your

system administrator for read privileges.

[APP–110] Could not retrieve system information (node name, version, release, machine, platform

and system name). Please contact your support representative.

[APP–112] Routine &ROUTINE cannot initialize concurrent request information for &REQUEST.

Review the concurrent manager log file for more detailed information.

[APP–114] You cannot modify or delete an incompatible program that was defined by an

application developer.

[APP–116] Routine &ROUTINE cannot open argument file &FILE for writing Check that the file

name is correct and valid on your system. Check that the person who started the concurrent

manager has privileges to create and write to files in the argument file directory. Contact your

system administrator to obtain create and write privileges.

[APP–118] Routine &ROUTINE cannot open your concurrent request’s log file &FILENAME

Check that the file name is correct and valid on your system. Check that the person who started the

concurrent manager has privileges to create and write to files in the concurrent program’s log

directory. Contact your system administrator to obtain privileges.

[APP–120] Concurrent Manager cannot open manager’s log file &AFPLOG Check that the person

who started the concurrent manager has privileges to create and write to files in the Application

Object Library log directory. Contact your system administrator to obtain create and write

privileges.

[APP–122] Concurrent Manager cannot open your concurrent request’s log file &AFPLOG Check

that the person who started the concurrent manager has privileges to create and write to files in the

concurrent program’s log directory. Contact your system administrator to obtain create and write

privileges.

[APP–124] Concurrent Manager cannot open your concurrent request’s output file &AFPOUT in

append mode. Check that the person who started the concurrent manager has privileges to create

and write to files in the concurrent program’s log directory. Contact your system administrator to

obtain create and write privileges.

[APP–126] This request has previously been run by the concurrent manager, and cannot be rerun.

Please submit a new request with the required parameters.

[APP–128] Routine &ROUTINE cannot set profile option value for &PROFILE. &REASON Check

that the profile option exists and that you have write privileges to the profile option. If the profile

option does not exist, you also need create privileges. Contact your system administrator for write

and create privileges.

[APP–130] Unable to activate Internal Concurrent Manager. Your account may not have the

privilege to activate the Internal Concurrent manager. Contact your system administrator to seek

privilege in starting the Internal Concurrent Manager. Check for execution privilege of ’startmgr’.

[APP–132] Routine &ROUTINE cannot terminate the concurrent manager process with ORACLE

process ID &ORACLEID and operating system process ID &OSPID. Shut down the concurrent

manager to terminate the process or use port–specific operating system commands to terminate the

process. Contact your support representative.

[APP–134] Routine &ROUTINE cannot terminate the concurrent process with concurrent process

ID &CPID and operating system process ID &OSPID Shut down the concurrent managers to

terminate the process or use port–specific operating system commands to terminate the process.

Contact your support representative.

[APP–136] Routine &ROUTINE cannot terminate concurrent request &REQUEST_ID with

controlling manager ID &CPID and manager’s operating system process ID &OSPID Shut down the

database to terminate the process or use port–specific operating system commands to terminate the

process. Contact your support representative.

[APP–138] This is the definition of the Internal Concurrent Manager as required by Oracle

Application Object Library. You cannot change any of its information.

[APP–140] This is the definition of the Standard work shift as required by Oracle Application

Object Library. You may not update or delete the record. If you wish to create a different work

shift, please enter a new one.

[APP–142] You attempted to change a concurrent program from standard submission to

non–standard submission, but the program has standard submission arguments defined. Please delete

all arguments for your concurrent program and save your changes before changing your program

from standard submission to non–standard submission.

[APP–146] Routine &ROUTINE has encountered a fatal error. &REASON Contact your system

administrator or support representative.

[APP–148] A concurrent program has been incorrectly defined as a concurrent manager control

program. Contact your support representative.

[APP–150] You cannot submit concurrent requests for a disabled concurrent program &PROGRAM.

Contact your System Administrator to enable the concurrent program.

[APP–152] Concurrent Manager encountered an error connecting to the database. Check if you have

specified a correct ORACLE username and password. Check if your ORACLE environment is

setup correctly. Check if you have reached the maximum number of users on the database. Contact

your Database Administrator to increase the maximum number of users on the database.

[APP–154] Please provide a valid value for the WAIT option

[APP–156] You entered an incorrect number of arguments to the program CONCSUB. CONCSUB

is a program that allows you to submit concurrent requests from your operating system. It expects

arguments that it would normally get from the user profiles, as well as the arguments to your

concurrent program. Syntax: CONCSUB <ORACLE ID> <Responsibility Application

Short Name> <Responsibility Name> <User Name> [WAIT=<Wait Flag]

CONCURRENT <Concurrent Program Application Short Name> <Concurrent Program

Name> [START=<Requested Start Date>] [REPEAT_DAYS=<Repeat Interval>]

[REPEAT_END=<Request Resubmission End Date>] <Concurrent Program Arguments

...> Example: CONCSUB SCOTT/TIGER SYSADMIN ’System Administrator’ SYSADMIN

WAIT=Y CONCURRENT FND FNDMNRMT START=’”01–JAN–1999 23:00:00”’

REPEAT_DAYS=1 REPEAT_END=’”01–JAN–2001 23:59:00”’ Y 0 0 ORACLE ID: Username and

password of the ORACLE ID for Applications. Enter the username and password without any

spaces and separated by a slash (”/”). Responsibility Application Short Name: Enter the short name

of the application for your responsibility. This name, along with your responsibility name, will be

used to select a responsibility for your concurrent request to run in. Responsibility Name: This

name, along with your responsibility application short name, will be used to select a responsibility

for your concurrent request to run in. User Name: Enter the name of your Application Object

Library user. This name will be used to update the Who information for any data your concurrent

program changes and to create report output file name for this request

[APP–158] Your complex rule line is conflicting with another rule line already defined for this type.

All rules combined must form valid criteria for specializing a concurrent manager.

[APP–160] Routine &ROUTINE cannot find a logical database with application ID &APPLID and

logical database ID &CONFLICT_SET. Contact your support representative.

[APP–162] Concurrent Manager encountered an error while setting the value for a SQL*Forms

global variable to your request ID &REQUEST. Contact your support representative.

[APP–164] Concurrent Manager cannot set a value for the field. Check that the field exists and is

writeable.

[APP–168] &MANAGER manager is currently running or its definition is being used. You cannot

delete the definition until it is no longer being used. Shut down the concurrent managers before

deleting the concurrent manager definition.

[APP–170] Routine &ROUTINE cannot construct discard file name for the SQL*Loader program

for your concurrent request &REQUEST. Check that the file name components are correct and valid

on your system. Application Object Library constructs your output file name from your concurrent

request ID. Check that the operating system environment of the person who started the concurrent

manager is correctly set and that Application Object Library environment variables have the correct

value. Important Application Object Library environment variables include, but are not limited to,

FND_TOP, APPLOUT, and program’s application’s basepath. Refer to installation manual for a

complete list.

[APP–174] A program library by the same name already exists for the same application. Please

enter a unique Library Name/Application combination.

[APP–175] Need–By Date

[APP–176] Please enter a unique name for your concurrent program. This concurrent program name

is already in use for your application. Concurrent program name, along with application name,

uniquely identifies a concurrent program.

[APP–178] Concurrent Manager cannot insert with a duplicate request ID &REQUEST_ID

Cause: Concurrent Manager has generated a duplicate request ID &REQUEST_ID for your

concurrent request.

Action: Check that the unique sequence to generate concurrent request IDs exists. If the

sequence does not exist, contact your system administrator or support representative to create the

sequence. Run the following SQL statement to check that request ID’s are not generated from

Application Object Library’s (old) unique identifier table. Run the next SQL statement to check

that the sequence exists and to get its current value. SQL: SELECT NEXT_UNIQUE_IDENTIFIER

FROM FND_UNIQUE_IDENTIFIER_CONTROL WHERE TABLE_NAME =

’FND_CONCURRENT_REQUESTS’; SQL: SELECT

FND_CONCURRENT_REQUESTS_S.NEXTVAL FROM DUAL; The number returned must be

greater than the highest request ID in FND_CONCURRENT_REQUESTS table.

Action: Check that the current sequence number is higher than the highest request ID in the

concurrent requests table. If the sequence number is low, contact your system administrator to

correct the sequence number and set it higher. Run the following SQL statement to get the highest

request ID in the concurrent requests table. SQL: SELECT MAX(REQUEST_ID) FROM

FND_CONCURRENT_REQUESTS;

[APP–180] This concurrent program is already incompatible with the registered concurrent

program. Enter a concurrent program that is not already incompatible, or clear your changes.

[APP–182] Routine &ROUTINE received failure code while parsing or running your concurrent

program &PROGRAM Review your concurrent request log file for more detailed information.

Make sure you are passing arguments in the correct format.

[APP–184] Routine &ROUTINE cannot initialize error handling information for the concurrent

manager. Contact your support representative.

[APP–186] Routine &ROUTINE cannot close the output file &FILENAME. Check that you have

sufficient disk space on your system. Remove unnecessary files to free disk space. Contact your

system administrator to obtain more disk space.

[APP–188] Unable to copy the file Check that the file name you entered is valid on your system.

Check that you have privileges to create and write to files in the file’s directory. Check that there is

sufficient disk space on your system to create a file. If necessary, contact your system administrator

to obtain create and write privileges or to obtain more disk space.

[APP–190] Routine &ROUTINE cannot load profile option values for your concurrent request

&REQUEST. &REASON Check if the user and responsibility information associated with the

concurrent request are valid. Contact your support representative.

[APP–192] Concurrent Manager encountered an error while running the Flexfield Preprocessor for

your concurrent request &REQUEST. Review your concurrent request log file for more detailed

information.

[APP–194] Concurrent Manager encountered an error while running SQL*Loader for your

concurrent request &REQUEST. Review your concurrent request log file for more detailed

information.

[APP–196] Concurrent Manager encountered an error while running &TOOLCODE for your

concurrent request &REQUEST. Review your concurrent request log file for more detailed

information.

[APP–200] Concurrent Manager encountered an error while running SQL*Plus for your concurrent

request &REQUEST. Review your concurrent request log and/or report output file for more detailed

information.

[APP–202] Concurrent Manager encountered an error while running Oracle*Report for your

concurrent request &REQUEST. Review your concurrent request log and/or report output file for

more detailed information.

[APP–204] Concurrent Manager encountered an error while running the spawned concurrent

program &PROGRAM for your concurrent request &REQUEST. &REASON. Review your

concurrent request log file for more detailed information.

[APP–206] Routine &ROUTINE cannot write to log file &LOGNAME Check that the person who

started the concurrent managers has privileges to create and write to files in Application Object

Library’s log directory. Contact your system administrator to obtain create and write privileges.

[APP–208] Routine &ROUTINE has encountered an error while writing to the argument file

&FILE. Check that the person who started the concurrent managers has privileges to create and

write to files in the argument file directory. Contact your system administrator to obtain create and

write privileges.

[APP–210] Concurrent manager routine &ROUTINE encountered an error writing to parameter file

[File Name]. Check that you have sufficient disk space on your file system that is assigned for

Oracle Financials temporary files. Contact your System Administrator to obtain more disk space.

[APP–212] You cannot delete an executable that is currently assigned to a concurrent program.

Remove the executable from the program(s) that reference it.

[APP–214] Please register your concurrent program executable &FILENAME with Application

Object Library

[APP–216] Routine &ROUTINE encountered an error while constructing the name of a temporary

&FILE_TYPE file. Check that the file name components are correct and valid on your system.

Check that the environment of the person who started the concurrent manager is correctly set and

that Application Object Library environment variables have the correct value. Important

Application Object Library environment variables include, but are not limited to, FND_TOP,

APPLTMP, and your application’s basepath. Refer to your installation manual for a complete list.

[APP–218] Cannot find status of concurrent managers. Review your error messages (Help Error) to

see the cause of the error. Contact your system administrator.

[APP–220] Routine &ROUTINE cannot find ORACLE process ID for system process &OSPID

Routine &ROUTINE returned no rows from V$PROCESS table for the system process ID &OSPID.

Contact your support representative.

[APP–222] Encountered an error while getting the ORACLE user account for your concurrent

request to run from. Review your error messages (Help Error) to see the cause of the error. Contact

your system administrator.

[APP–224] Concurrent Manager cannot get report parameter names for your Oracle*Report report.

&REASON. Contact your support representative.

[APP–226] Encountered an error while submitting your concurrent request. Cannot get a request

ID. Review your error messages to see the cause of the error.

Action: Check that the unique sequence to generate concurrent request IDs exists. If the

sequence does not exist, contact your system administrator or support representative to create the

sequence. Run the following SQL statement to make sure that the request ID for concurrent

requests is NOT obtained from Application Object Library’s (old) unique identifier table. Run the

next SQL statement to check that the sequence exists. SQL: SELECT

NEXT_UNIQUE_IDENTIFIER FROM FND_UNIQUE_IDENTIFIER_CONTROL WHERE

TABLE_NAME = ’FND_CONCURRENT_REQUESTS’; SQL: SELECT

FND_CONCURRENT_REQUESTS_S.NEXTVAL FROM SYSTEM.DUAL;

Action: Check that SYSTEM.DUAL has only one row in the table.

Action: Check that the current sequence number is higher than the highest request ID in the

concurrent requests table. If the sequence number is too low, contact your system administrator to

correct the sequence number and set it higher. Run the following SQL statement to get the highest

request ID in the concurrent requests table. SQL: SELECT MAX(CONCURRENT_REQUEST_ID)

FROM FND_CONCURRENT_REQUESTS;

[APP–228] Routine &ROUTINE encountered an error changing request &REQUEST status.

Contact your support representative.

[APP–230] Concurrent Manager encountered an error while attempting to start your immediate

concurrent program &PROGRAM. Routine &ROUTINE received a return code of failure. Contact

your support representative.

[APP–232] Cannot submit your concurrent request Review the previous error messages

[APP–236] You have not specified any arguments for the concurrent program FDPPEV Enter the

names of environment variables you wish to know the value of. FDPPEV will return the values

used by the concurrent manager.

[APP–238] Please enter arguments to the concurrent program FDPSEV using a valid format.

Arguments to FDPSEV should be in <Environment Variable Name>=<Environment

Variable Value> ... format. Environment Variable Name: Enter the name of the environment

variable whose value you wish to set. FDPSEV will set the environment variable value to the value

you enter. Environment Variable Value: Enter the value to which you wish to set the environment

variable. FDPSEV will set the environment variable value to the value you enter.

[APP–240] You entered an incorrect number of arguments to the concurrent program FDPSEV, or

the arguments you entered are not the type expected. Syntax: FDPSEV <Environment

Variable>=<Value> <Environment Variable>=<Value> ...

[APP–242] Routine &ROUTINE encountered an error while initializing log and output files for

your concurrent request. &REASON. Contact your support representative.

[APP–244] FDWHOAMI environment variable contains invalid value &USERID for user ID

[APP–246] Cannot set field value for &FIELD Review your error messages (Help Error) to see the

cause of the error. Check that the field exists and is writeable.

[APP–248] Routine &ROUTINE cannot read the file &FILENAME. Check if the file exists under

correct product directory. Check if the person who started the Concurrent Manager has read

privileges on the directory and on the file. Contact your system administrator to assign read

privileges.

[APP–250] Concurrent Manager encountered an error writing to the file &FILENAME.

&REASON. Check that the person who started the concurrent manager has privileges to create and

write to files in the file’s directory. Contact your system administrator to assign create and write

privileges. Check that there is sufficient disk space on your system to create a file. Contact your

system administrator to obtain more disk space.

[APP–252] Your concurrent program did not specify input, output, or log file name information to

routine &ROUTINE. Change your concurrent program to pass all the required file name

information to routine &ROUTINE.

[APP–254] You could not insert program context information Your ORACLE ID may not have

insert privileges or another ORACLE error may have occurred while attempting to insert the record.

Ensure your ORACLE ID has insert database privileges on the FND_DESCR_FLEX_CONTEXTS

table. Check for any database error message using \ Help Error (Database).

[APP–256] Concurrent Manager cannot find requestor for concurrent request &REQUEST Check if

the requestor of this concurrent request is a valid application user.

[APP–258] Concurrent Manager error handler cannot find the error class for the specified error

description. Contact your support representative.

[APP–260] Concurrent Manager error handler cannot process an undefined or NULL error. Contact

your support representative.

[APP–262] Concurrent Manager cannot find an error handler Concurrent Manager has encountered

an error, but no error handler is currently defined on the error stack or the error was raised outside of

an error catch region. Contact your support representative.

[APP–264] Concurrent Manager cannot allocate memory because system is out of memory. Contact

your system administrator or support representative.

[APP–266] Routine &ROUTINE received a return code of failure from routine &FUNCTION.

Review your concurrent request log file for more information.

[APP–268] Please specify a valid printer. Either you have not specified a printer for your report, or

the printer name you have given does not match that in the program definition. Please specify a

printer in the program definition, report set definition, run reports form or as a profile option.

[APP–276] Routine &ROUTINE received an incorrect number of arguments You passed the routine

&ROUTINE or your spawned concurrent program the incorrect number of arguments

(&NUMBER). Refer to the Oracle Application Object Library Reference Manual for the required

number of arguments for the routine &ROUTINE. Enter the correct number of arguments to your

spawned concurrent program.

[APP–278] The Internal Concurrent Manager has encountered an error. Review concurrent manager

log file for more detailed information.

[APP–280] Concurrent program associated with invalid application information. Cannot retrieve

application information associated with this concurrent program. Contact your system administrator.

[APP–282] Cannot find application information for short name &APPLNAME Cannot find rows

while selecting for application short name &APPLNAME. Check if the application short name is

valid. Contact your System Administrator.

[APP–284] Program &PROGRAM is not registered under application &APPLICATION

Cause: You submitted a concurrent request for a concurrent program &PROGRAM belonging

to application &APPLICATION, which is not registered with Application Object Library.

Action: Register your concurrent program with Application Object Library.

Cause: Concurrent program &PROGRAM is registered under a different application.

Action: Check that you specified the correct application name for your concurrent program.

[APP–286] Routine &ROUTINE cannot find Concurrent manager &QUEUE with Application

&APPLSNAM

Cause: The concurrent manager &QUEUE with Application short name &APPLSNAM is not

registered with Application Object Library, or is registered with a different Application. Routine

&ROUTINE cannot start the concurrent manager. Contact your system administrator.

[APP–288] Cannot find an ORACLE account based on the current responsibility. The responsibility

information is incorrect. Contact your system administrator to verify the current responsibility

information. Responsibility application ID is &APPLID. Responsibility ID is &RESPID.

[APP–290] Cannot find application short name for application ID &ID.

Action: Check if the application ID is valid. Run the following SQL statement to select

information about applications that have been registered with Application Object Library. SQL:

SELECT APPLICATION_ID, APPLICATION_NAME, APPLICATION_SHORT_NAME,

APPLICATION_PREFIX, DESCRIPTION, BASEPATH FROM FND_APPLICATION;

[APP–292] Concurrent manager &QUEUE with application ID &APPLID cannot find row to update

in routine &ROUTINE. Contact your system administrator to shut down and restart the concurrent

managers.

[APP–294] You have specified invalid arguments for the program

[APP–296] Cannot submit concurrent request for program &PROGRAM Check if the concurrent

program is registered with Application Object Library. Check if you specified the correct

application short name for your concurrent program.

[APP–298] You have invalid data group information. Failed to find an ORACLE account for the

data group of the current responsibility. Contact your system administrator to verify the information

for this data group. Data group ID is &GROUPID. Responsibility application ID is &APPLID.

[APP–300] The executable file &EXECUTABLE for this concurrent program cannot be executed.

Contact your system administrator or support representative. Verify that the execution path to the

executable file is correct. Verify that the executable file exists and has execution permission.

[APP–302] Routine &ROUTINE encountered an error constructing the directory path and file

components from the file name &FILE. Check that the file name is correct and valid on your

system.

[APP–304] Routine &ROUTINE encountered an error constructing the root file and extension

components from the file name &FILE. Check that the file name is correct and valid on your

system.

[APP–306] Invalid option given for PRINT_TOGETHER token

[APP–308] Cannot submit concurrent requests to run from Oracle username &USER You cannot

submit concurrent requests to run from the Oracle username &USER, because the username is not

registered with Application Object Library. Contact your System Administrator to register Oracle

username.

[APP–310] Oracle username &ONAME is invalid because it is too long. Please enter the correct

name.

[APP–312] Please enter a valid print style for the concurrent program &PROGRAM.

[APP–314] Invalid printer ( &PRINTER ) and print style ( &STYLE ) combination.

[APP–316] Please enter a valid application short name for your concurrent program. The

application short name &APPLSNAME is not valid.

[APP–318] An invalid argument method &ARG_METHOD has been defined for the concurrent

program &PROGRAM for your concurrent request &REQUEST. Contact your system administrator

to enter a valid argument method for your concurrent program.

[APP–320] An invalid execution method &EXEC_METHOD has been defined for the concurrent

program &PROGRAM for your concurrent request &REQUEST. Contact your system administrator

to enter a valid execution method for your concurrent program.

[APP–322] Cannot find concurrent program &PROGRAM because it is not registered with

Application Object Library. Register your concurrent program with Application Object Library and

check that you specified the correct application short name for your concurrent program.

[APP–324] You have entered an invalid request start date and time: &START_DATE. Could not

submit your concurrent request or report. Verify that the value for the profile option

”Concurrent:Request Start Time” is in the correct date and time format of DD–MON–YY

HH24:MI:SS. For example: 25–DEC–91 12:30:00. Enter a NULL value for the profile option

(make it blank) if you wish to have the concurrent request or report to start immediately. Please try

again to submit the concurrent request or report in your application form using the correct format

for the start date and time.

[APP–326] Your concurrent request &REQUEST has an invalid status code. Contact your support

representative.

[APP–328] Please enter a valid application short name for your responsibility. The application short

name &APPLSNAME is not valid for your responsibility.

[APP–330] Please enter a valid responsibility. The responsibility &RESPNAME does not exist or is

not active. Check that the correct application short name is specified for your responsibility.

[APP–332] Your concurrent request or report could not be submitted due to the following invalid

resubmission end date and time: &END_DATE Please try again to submit the concurrent request or

report in your application form with the correct resubmission end date and time, or enter NULL

(blank) if no end date and time are desired. Use the date and time format of DD–MON–YY

HH24:MI:SS. For example: 25–DEC–91 15:45:00

[APP–334] An invalid concurrent program information type &TYPE was requested

[APP–336] Please enter a valid application username. The application username &USERNAME

does not exist or is not active.

[APP–338] The log file &FILENAME for your concurrent request is not initialized Your concurrent

program execution was not preceded by calls to standard Application Object Library routines to

initialize concurrent processing. Routine &ROUTINE received a return code of failure. Change

your concurrent program to initialize files by calling standard Application Object Library routines.

[APP–340] Routine &ROUTINE cannot find log file name information Contact your support

representative.

[APP–344] Concurrent Manager encountered an error inserting login information for login ID

&LOGIN for your concurrent request. Contact your support representative.

[APP–346] &CONCURRENT_MANAGER is not active. Activate manager before choosing this

option.

[APP–348] Routine &ROUTINE encountered an error while starting concurrent manager

&MANAGER with library &LIBRARY. Check that your system has enough resources to start a

concurrent manager process. Contact your system administrator to obtain more resources. Check

that the concurrent program library exists under the correct product directory. Make sure that the

person who started the concurrent manager has privileges to read and execute files in the directory

containing the program library.

[APP–350] Marking request &REQUEST as Error Concurrent Manager cannot get the necessary

information to complete your concurrent request &REQUEST successfully. Review concurrent

manager log file for error messages indicating the missing information.

[APP–352] Routine &ROUTINE encountered an error while parsing your arguments. An expected

token or separator is missing from the argument list. Enter the correct arguments for the routine.

[APP–354] Concurrent Manager cannot find error description for &ERROR_NAME Contact your

support representative.

[APP–356] Concurrent Manager error handler cannot find the name of the error. Contact your

support representative.

[APP–358] Program Library &LIBRARY has invalid program definitions

[APP–360] &ROUTINE cannot find concurrent manager &QID with application ID &APPLID to

update.

Cause: Internal Manager found no rows while selecting manager &QID with application ID

&APPLID from FND_CONCURRENT_QUEUES for update of running processes information.

Action: Contact your system administrator to shutdown and restart the concurrent managers.

[APP–362] Routine &ROUTINE cannot execute request &REQUEST for program &PROGRAM,

because the environment variable &BASEPATH is not set for the application to which the

concurrent program executable &EXECUTABLE belongs. Shut down the concurrent managers. Set

the basepath environment variable for the application. Restart the concurrent managers.

[APP–364] Routine &ROUTINE cannot get information for your concurrent request &REQUEST

Routine &ROUTINE found no rows while selecting your concurrent request &REQUEST from

FND_CONCURRENT_REQUESTS. Contact your System Administrator.

[APP–366] Routine &ROUTINE cannot run ORACLE Import utility without required parameters

Please pass all the parameters to the Import utility in <Token>=<Value> format with

each parameter separated by a \n. Refer to ORACLE RDBMS Utilities User’s Guide for the required

parameters.

[APP–368] Could not get line width and number of lines per page information for the requested

print style &STYLE

[APP–370] Routine &ROUTINE: Please register a Oracle*Report driver for printer &PRINTER and

print style &STYLE

[APP–372] Could not get concurrent program details since the executable name is not unique

[APP–374] Routine &ROUTINE cannot find &BLOCK block information

[APP–380] You cannot delete this concurrent library because there is a concurrent manager defined

to use this concurrent library. Change any concurrent manager definitions that use this concurrent

library before trying to delete the library.

[APP–382] Cannot find concurrent manager information on request &REQUEST The record of the

concurrent manager process that processed request &REQUEST has been purged. No action

required.

[APP–384] Cannot find concurrent manager information on request &REQUEST The record of the

Internal Concurrent Manager that was active during the processing of request &REQUEST has been

purged. No action required.

[APP–388] Program failed to set the report print style.

[APP–390] Routine &ROUTINE:Failed to update request with new print style &STYLE.

[APP–392] There are no immediate concurrent programs assigned to library &LIBRARY

[APP–394] Concurrent Manager cannot find any concurrent requests for program &PROGRAM You

requested the status of concurrent requests for concurrent program &PROGRAM belonging to

application &APPL, but no concurrent requests have been submitted.

[APP–398] Request type is currently in use. There is a concurrent program defined with this request

type, or there is a concurrent manager defined to run this request type. You cannot delete this

request type unless it is no longer being used.

[APP–402] The concurrent program for your concurrent request exited to wait, but has no pending

child requests to wait for. Routine &ROUTINE received a return code of failure.

[APP–404] Cannot find concurrent program information

[APP–406] Username/Password is required for the program to connect to database

[APP–408] Concurrent Manager could not find the ORACLE user ID associated with your

concurrent request &REQUEST. Check if the ORACLE user ID associated with the concurrent

request is valid.

[APP–410] Routine &ROUTINE encountered an ORACLE error. &REASON. Review your error

messages for the cause of the error.

[APP–412] The output file &FILENAME for your concurrent request is not initialized.

Cause: Your concurrent program execution was not preceded by calls to standard Application

Object Library routines to initialize concurrent processing. &ROUTINE received a return code of

failure.

Action: Change your concurrent program to initialize files by calling standard Application

Object Library routines.

[APP–414] &ROUTINE cannot find output file name information. Concurrent manager did not

specify output file name information to &ROUTINE. Please contact your support representative.

[APP–416] &FUNCTION_CALLED cannot allocate memory for &IDENTIFIER because system is

out of memory. &ROUTINE received a return code of failure.

Cause: &FUNCTION_CALLED cannot allocate memory for &IDENTIFIER because system is

out of memory. &ROUTINE received a return code of failure.

Action: Contact your system administrator or support representative.

[APP–418] Output file for this request is not available.

Cause: You requested the Concurrent Manager to automatically delete your output file for you

by setting the profile option Save Output to No before submitting your concurrent request, or

request generates no output.

Action: Change the profile option Save Output to Yes and resubmit your concurrent request if

you wish to save your request output file.

[APP–420] The parent concurrent request completed before the child request started

[APP–422] &ROUTINE cannot find the parent concurrent request &PARENT_ID of child

concurrent request &CHILD_ID.

Cause: &ROUTINE found no rows while selecting the parent concurrent request

&PARENT_ID of child concurrent request &CHILD_ID.

Action: Contact your support representative.

[APP–424] The parent request completed with error before the child request started

[APP–426] &ROUTINE cannot parse your arguments

Cause: &ROUTINE encountered an error while parsing your arguments. Argument string has

invalid argument separators or has invalid characters.

[APP–430] &ROUTINE cannot print the output file for your concurrent request &REQUEST

Cause: &ROUTINE encountered an error printing the output file for your concurrent request

&REQUEST.

Action: Review your concurrent request log file for more detailed information. Contact your

system administrator.

[APP–432] &ROUTINE cannot find concurrent manager with process ID &CPID

Cause: &ROUTINE found no rows while selecting concurrent manager &CPID from

FND_CONCURRENT_PROCESSES for update.

Action: Contact your support representative.

[APP–434] &ROUTINE:Failed to initialize profile option values : &REASON

[APP–440] Program name differs from executable name or program not registered

Cause: Program name is different from the executable.

Action: You may change executable name to match the program name, if you wish to.

Cause: Program is not registered.

Action: Register the program with AOL.

[APP–442] Program exited with error.

[APP–444] Concurrent program &PROGRAM exited with error

Cause: &ROUTINE received a return code of failure from concurrent program &PROGRAM.

Action: Review your concurrent request log file for more information.

[APP–446] &ROUTINE received a return code of failure from concurrent program &PROGRAM.

Cause: &ROUTINE received a return code of failure from concurrent program &PROGRAM.

&REASON.

Action: Review your concurrent request log file for more detailed information.

[APP–448] Concurrent Manager cannot find concurrent program for request &REQUEST

Cause: Concurrent Manager found no rows while selecting the concurrent program for your

concurrent request &REQUEST.

Action: Check if the concurrent request refers to a concurrent program registered with

Application Object Library.

[APP–450] Could not purge concurrent manager records and log files

[APP–452] Could not purge concurrent request records and request log/output files

[APP–456] Failed to submit concurrent request for reprint of output file

Cause: Encountered an error while submitting a request to reprint your output file.

Action: Review your error messages (\Help Error) to see the cause of the error.

[APP–458] Concurrent Manager cannot find information for your concurrent request from

&TABLES

Cause: Concurrent Manager found no rows while selecting information for your concurrent

request from &TABLES.

Action: Review your concurrent manager log file &LOG for more detailed information.

[APP–460] &ROUTINE cannot find concurrent manager with ORACLE process ID &ORACLE for

request &REQUEST

Cause: &ROUTINE found no rows while selecting concurrent manager with ORACLE process

ID &ORACLE for request &REQUEST.

Action: Contact your support representative.

[APP–462] Your concurrent request exited abnormally

Cause: The concurrent program for your request exited without calling standard Application

Object Library exit routines or the process could have been terminated by the operating system.

Action: Review concurrent manager log file for more detailed information. Change the

concurrent program to exit by calling Application Object Library routines.

[APP–464] &ROUTINE cannot get information about concurrent request &REQUEST to reprint the

output file.

Cause: &ROUTINE encountered an error getting information for concurrent request

&REQUEST to reprint its output file.

Action: Request could have been deleted since the request to reprint its output was submitted.

Contact your System Administrator.

[APP–466] &ROUTINE cannot find your concurrent request &REQUEST &ROUTINE found no

rows while selecting your concurrent request &REQUEST. Please contact your support

representative.

[APP–468] &ROUTINE cannot resubmit your concurrent request &REQUEST. &REASON

Cause: &ROUTINE encountered an error while resubmitting your concurrent request

&REQUEST. &REASON.

Action: Review your concurrent request log file for more detailed information.

[APP–474] Concurrent manager server for &NODE is already running

[APP–476] &ROUTINE cannot set file options for your concurrent request &REQUEST.

Cause: &ROUTINE encountered an error setting log and output file options for your

concurrent request &REQUEST. &REASON.

Action: Contact your support representative.

[APP–478] Shutting down Internal Concurrent Manager

[APP–480] Failed to submit concurrent request for concurrent program &PROGRAM

Cause: The concurrent request submission for concurrent program &PROGRAM failed.

Action: Refer to previous error messages for exact cause.

[APP–482] Internal manager failed to spawn manager process : &REASON

[APP–484] Please enter an end time greater than the start time

Cause: You entered an end time that is less than the start time.

Action: Enter a start time less than the end time.

Action: Enter an end time greater than the start time.

[APP–488] &ROUTINE received a return code of failure from concurrent program &PROGRAM

Cause: &ROUTINE received a return code of failure from subroutine concurrent program

&PROGRAM.

Action: Review your concurrent request log file for more detailed information.

[APP–490] &ROUTINE cannot initialize information for concurrent program &PROGRAM

Cause: &ROUTINE encountered an error while initializing information for the subroutine

concurrent program &PROGRAM.

Action: Review your concurrent request log file for more detailed information.

[APP–492] &ROUTINE cannot get environment variable value for &VARIABLE

Cause: &ROUTINE cannot get a value for the environment variable &VARIABLE.

Action: Shutdown the concurrent managers. Set the environment variable and restart the

concurrent managers.

[APP–494] There are too many arguments for this program

Cause: Too many arguments or reports parameters have been specified for this program or

report.

Action: Contact your support representative. Additional information for support representative:

Concurrent programs and reports may have a maximum of 100 arguments or report parameters, each

of which may be no more than 240 characters long. Change your program or report to accept the

proper number of arguments. You may also need to change the report parameters you have defined

for your report, or you may also need to change the way your forms request your concurrent

program.

[APP–496] This concurrent manager cannot run the following registered, immediate concurrent

programs because they are not linked to this concurrent manager’s library ”&LIBRARY”

Cause: The immediate concurrent programs listed have been registered through Application

Object Library as part of the concurrent manager library &LIBRARY, but the actual codes for those

programs are not linked to the library executable.

Action: Ensure that the immediate concurrent programs are entered in the application catalog

files, each with an associated subroutine name. Refer to the Oracle Application Object Library

Reference Manual for more information.

[APP–498] This concurrent manager cannot run the following immediate concurrent programs

because they are not registered under the concurrent manager’s program library ”&LIBRARY”

Cause: The listed immediate concurrent programs are linked to the concurrent manager library

&LIBRARY executable, but are not registered as part of the concurrent manager library.

Action: Register the concurrent programs as part of the concurrent manager library

&LIBRARY through Application Object Library’s Define Program Library form.

[APP–500] &ROUTINE received a return code of failure from routine &CALLED. &REASON

Cause: &ROUTINE received a return code of failure from the OSD routine &CALLED.

&REASON.

Action: Review your concurrent request log file for more detailed information.

[APP–502] You can only view details of a concurrent request you submitted

Cause: You attempted to view the details of a concurrent request that you did not submit. You

can only view concurrent requests that you submitted.

[APP–504] Failed to build Concurrent Request Queue View

Cause: Failed to build Concurrent Request Queue View due to a lock on the view by another

user.

Action: Request has been resubmitted to try again after 15 minutes.

[APP–506] Please enter a unique subroutine name that is not already in use for your application.

[APP–508] Please enter a unique execution file name that is not already in use for your application.

[APP–510] Please enter a unique program executable name that is not already in use for your

application.

[APP–522] No information found for the currency code &CODE &APPLICATION cannot find

information for your currency code &CODE. Check that your currency code is valid and enabled.

[APP–526] You entered a minimum accountable unit that is too small

Cause: You entered a minimum accountable unit value that is the same as or less than the

lowest denomination for this currency. This causes rounding calculations to unnecessarily loose

processing efficiency.

Action: Enter a minimum accountable unit value that is not less than or equal to 1 / power( 10,

precision ). In this case, enter a minimum accountable unit greater than

&LOWEST_DENOMINATION.

[APP–528] You entered a value that is not a multiple of the lowest denomination

Cause: You entered a minimum accountable unit value that is not a multiple of the lowest

denomination for this currency.

Action: Enter a minimum accountable unit value that is a multiple of 1 / power( 10, precision ).

In this case, enter a minimum accountable unit that is a multiple of &LOWEST_DENOMINATION.

[APP–531] The amount &amount could not be correctly formatted. The correct format is &pos_val

or &neg_val.

[APP–546] &FUNCTION function is currently not available

Cause: You pressed a function key &FUNCTION that is currently not available.

Action: Review help text for your form (\Screen Help) to determine the purpose of the form.

You may need to navigate to another form to perform the function.

Action: If query is not available, you may be in a control zone. Try entering your row

information.

Action: If insert, update, or delete is not available, you may be in a query–only form. Query

your row information, or navigate to an edit form to edit your data.

Action: If delete is not available, you may not be allowed to delete rows of information. Try

disabling your row by setting an enable flag or end date field.

[APP–548] Function is currently not available

Cause: You pressed a function key that is currently not available.

Action: Review help text for your form (\Screen Help) to determine the purpose of the form.

You may need to navigate to another form to perform the function.

Action: If query is not available, you may be in a control zone. Try entering your row

information.

Action: If insert, update, or delete is not available, you may be in a query–only form. Query

your row information, or navigate to an edit form to edit your data.

Action: If delete is not available, you may not be allowed to delete rows of information. Try

disabling your row by setting an enable flag or end date field.

[APP–552] Error executing &NAME user exit .

[APP–554] You have specified an invalid argument for the user exit DISPFILE

Cause: The first argument to the user exit DISPFILE is not of the correct type.

Action: Specify the correct file type as the first argument to the user exit.

[APP–556] You cannot update a pseudo–column You tried to update a SQL*Plus ”pseudo–column”

such as USER or SYSDATE. You are not allowed to change this type of value. No action required.

[APP–558] Examine cannot get the value of &FIELD

Cause: An error occurred while getting the value of &FIELD.

Action: Check if the field or variable exists.

Action: Review your error messages with \ Help Error for more information.

[APP–560] Examine cannot set the value of &FIELD

Cause: An error occurred while setting the value of &FIELD.

Action: Check if the field or variable exists.

Action: Check if the field or variable is allowed to be changed. You cannot change the value

of system variables. You cannot change the value of profile options that are write–protected.

Action: Review your error messages with \ Help Error for more information.

[APP–561] Unable to get the flexfield title because the flexfield definition is not available. Please

try again from the block where the descriptive flexfield occurs, or try querying data in that block.

[APP–563] There are no descriptive flexfields defined. Please try again from the block where the

descriptive flexfield occurs.

[APP–563] You must finish the action you are performing in Excel before exporting.

[APP–564] Cannot delete file &FILENAME

Cause: Application Object Library encountered an error while deleting the file &FILENAME.

Action: Check that you have privileges to delete files in the file directory. Contact your system

administrator to obtain delete privileges. If your file contains secure data, be sure to delete it

manually, from the operating system command line, if necessary.

[APP–565] The export failed in &proc. PL/SQL error: &err_text. OLE error: &ole_err.

[APP–566] &ROUTINE attempted to open a stream for the log or report file &FILENAME but that

stream is already open. Contact your support representative.

[APP–570] &ROUTINE cannot write to a file

Cause: &ROUTINE encountered an error while writing to a file.

Action: Check that you have privileges to create and write to files in the file’s directory.

Contact your system administrator to obtain create and write privileges.

Action: Check that there is sufficient disk space on your system to create a file. Contact your

system administrator to obtain more disk space.

[APP–572] &ROUTINE cannot flush file stream

Cause: &ROUTINE encountered an error while flushing the file stream.

Action: Check that you have sufficient disk space on your system. Remove unnecessary files

to free disk space. Contact your system administrator to obtain more disk space.

[APP–574] Application Object Library cannot write to temporary directory

Cause: The user–specified temporary directory is not a valid directory for creating temporary

files.

Action: Choose a different temporary directory. This is usually specified as an environment

variable. See your installation guide for details.

[APP–576] Cannot open file &FILE for writing

Cause: &MODULE encountered an error while opening the file &FILE for writing.

Action: Check that the file name is correct and valid on your system.

Action: Check that you have privileges to create and write files in the file directory. Contact

your system administrator to obtain create and write privileges.

[APP–580] Cannot read file &FILENAME

Cause: Application Object Library encountered an error while reading the file &FILENAME.

Action: Check if the file exists. Contact your system administrator to create the file.

Action: Check if you have read privileges on the directory and on the file. Contact your

system administrator to obtain read privileges.

[APP–582] Cannot rename file &FILENAME1 to &FILENAME2

Cause: Application Object Library tried to rename file &FILENAME1 to the new name

&FILENAME2. That operation failed.

Action: Check that &FILENAME1 exists and that you have privileges to read it.

Action: Check that you have privileges to write to &FILENAME2 and/or its directory.

[APP–584] Cannot write to file &FILENAME

Cause: Application Object Library encountered an error writing to file &FILENAME.

Action: Check that the file name is correct and valid on your system.

Action: Check that you have privileges to create and write files in the file directory. Contact

your system administrator to obtain create and write privileges.

[APP–586] Program error: The Flexfield C API function &ROUTINE has been called with an input

structure that was not initialized. Please contact your support representative. Initialize the input

structure at the beginning of your routine by calling &ROUTINE with the FFINIT mode. Initialize

the input structure between calls to &ROUTINE by calling &ROUTINE with the FFMODEINIT

mode. The FFMODEINIT mode is only required between calls to &ROUTINE that require

different mode–specific input.

[APP–588] Program error: An error has occurred while looking up a flexfield segment combination.

Please inform your support representative that: The FND_FLEX_SERVER validation function has

encountered a null or negative combination ID (&CCID) while trying to look up the segment values

for this combination. This may indicate an invalid entry in the unique ID column of the

combinations table.

[APP–590] Program error: Please contact your support representative. The server PLSQL function

FND_FLEX_EXT.GET_COMBINATION_ID() has been called incorrectly. An incomplete segment

array has been passed into this function. Values must be assigned to all elements in the array even if

they are null. Please refer to the Flexfields Server–Side Validation documentation for proper use of

this function.

[APP–592] Program error: Please contact your support representative. The server PLSQL function

FND_FLEX_EXT.GET_CCID() has been called incorrectly. An invalid format for validation date

string has been passed into this function. Please refer to the Flexfields Server–Side Validation

documentation for proper use of this function.

[APP–594] Invalid application column name in &ROUTINE : parameter &PARAM : row

&ROWNUM You have specified a column name in a table validated value set for a column that

does not exist

[APP–596] FlexBuilder failed to generate a CCID for row &ROWNUM in &ROUTINE. Please

view any previous messages

[APP–598] FlexBuilder failed to generate a CCID for row &ROWNUM in &ROUTINE due to :

&REASON &EXPLANATION

[APP–600] Infinite recursion encountered in &ROUTINE : parameter &PARAM : row

&ROWNUM FlexBuilder has detected that a derived parameter is derived from itself in a circular

fashion

[APP–602] No conditional parameter match in &ROUTINE : parameter &PARAM : row

&ROWNUM FlexBuilder has found that a parameter is conditional on a non–existent parameter

[APP–604] FlexBuilder : Dynamic inserts not allowed in &ROUTINE : row &ROWNUM

Cause: FlexBuilder cannot generate a new code combination because dynamic inserts are not

allowed for this flexfield structure.

Action: Contact your system administrator to create the combination or have your flexfield

structure allow dynamic inserts

[APP–606] FlexBuilder : Cannot retrieve error messages in &ROUTINE

[APP–608] FlexBuilder PLSQL function &ROUTINE failed. Please review any previous messages

[APP–616] FlexBuilder : Internal error – parameter number &NUMBER

[APP–618] FlexBuilder : Row number &NUMBER out of range in &ROUTINE

[APP–620] Value &VALUE is not valid in value set ID &VSET_ID

[APP–622] FlexBuilder failed for parameter &PARAM : row &ROWNUM due to the following:

&REASON &EXPLANATION

[APP–624] Too many segments with this qualifier in &ROUTINE : parameter &PARAM : row

&ROWNUM A FlexBuilder parameter or assignment specified a flexfield qualifier used by more

than one segment.

[APP–626] Invalid argument &ARG specified for the FlexBuilder user exit BUILDID.

[APP–628] No assignments have been created for FlexBuilder function &FUNCTION

[APP–630] No segments with this qualifier in &ROUTINE : parameter &PARAM : row

&ROWNUM A FlexBuilder parameter or assignment specified a flexfield qualifier that is not used

by the flexfield structure.

[APP–632] Cannot get value for field &FIELD in FlexBuilder user exit BUILDID

[APP–634] Cannot compile FlexBuilder function &FUNC : Application &APPID Please review

previous messages using [menu] Help Error.

[APP–636] No FlexBuilder assignments defined for function &FUNCTION for flexfield structure

&CODE : num &NUM

[APP–638] FlexBuilder out of memory in &ROUTINE : row &ROWNUM

[APP–640] No parameters have been created for FlexBuilder function &FUNCTION

[APP–642] Invalid FlexBuilder parameter type &TYPE in routine &ROUTINE

[APP–644] FlexBuilder : Row &ROWNUM – Parameter &PARAM is not defined in &ROUTINE

You have attempted to use a Raw parameter that has not been passed to FlexBuilder OR You have

attempted to use a parameter in a value set WHERE clause, but the parameter has not yet been

defined through a FlexBuilder form

[APP–646] FlexBuilder : Row &ROWNUM : Parameter &PARAM is not defined in &ROUTINE A

FlexBuilder parameter or assignment referenced a parameter that has not been defined.

[APP–648] FlexBuilder usage : FNDFBTST < test name >

[APP–650] Invalid column name in &ROUTINE : value set parameter &PARAM : row

&ROWNUM

Cause: A FlexBuilder assignment specified an output column for a value set that is not

allowed.

Action: You may only use the VALUE or DESCRIPTION columns as output for a value set.

[APP–652] &ROUTINE: You have not defined a context column for this flexfield

[APP–654] &ROUTINE: &COLNAME has not been assigned as a descriptive flexfield column The

flexfield compiler has detected that an unrecognized application column is being assigned to a

flexfield segment. Please check the FND_COLUMNS table for data integrity problems.

[APP–656] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE was unable to find the error message for your value

validation rule. The flexfield user exits #FND LOADID, #FND POPID, or #FND VALID have been

called incorrectly. Make sure the VRULE= parameter is correct. Make sure the value is in quotes,

the \n’s are in lower case, there are no spaces around the \n’s, and all the information is provided.

[APP–658] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE was unable to find the include exclude/indicator on your

value validation rule. The flexfield user exits #FND LOADID, #FND POPID, or #FND VALID

have been called incorrectly. Make sure the VRULE= parameter is correct. Make sure the value is

in quotes, the \n’s are in lower case, there are no spaces around the \n’s, and all the information is

provided.

[APP–664] Flexfield routine &ROUTINE cannot find a flexfield value security rule element.

Action: Contact your system administrator. Make sure Security Rule Elements are defined in

the Define Flexfield Rule form.

[APP–666] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE cannot find the segment qualifier name for your value

validation rule. The flexfield user exits #FND LOADID, #FND POPID, or #FND VALID have been

called incorrectly. Make sure the VRULE= parameter is correct. Make sure the value is in quotes,

the \n’s are in lower case, there are no spaces around the \n’s, and all the information is provided.

[APP–668] The data that defines the flexfield on this field may be inconsistent. Inform your system

administrator that the function: &ROUTINE could not find the structure definition for the flexfield

specified by Application = &APPL, Code = &CODE and Structure number = &NUM

[APP–670] Program error: You have a flexfield value security rule that is neither Include nor

Exclude. The rule type is not valid. Please contact your system administrator. Make sure the

Security Rule Elements defined in the Define Flexfield Security Rule form all have valid types.

[APP–672] Cross–validation rule has incorrect elements. Contact system administrator.

[APP–674] Program error: Flexfields could not parse the bind variable near &VARIABLE. Legal

characters for bind variables are A–Z a–z 0–9 ’_’, ’.’, ’:’, ’$’, and ’#’. Bind variables must be at

least two characters long.

Action: Find the value set that uses this bind variable and make sure it is defined correctly.

The full SQL statement is &SQL.

[APP–676] The flexfield routine &ROUTINE cannot read the default reference field specified for

this descriptive flexfield. The developer specified a context field (via the Register Descriptive

Flexfields form) that does not exist in this block of this form.

Action: Contact your system administrator, and choose another default reference field for this

descriptive flexfield.

[APP–680] Program error: Application Object Library has detected an internal flexfields error.

Please contact your system administrator or support representative. Flexfields use special pseudo

fields to communicate with QuickPick and other Application Object Library features. This error has

probably occurred because the system is out of memory, and the routine &ROUTINE cannot read

from a pseudo field.

[APP–682] Program error: Routine &ROUTINE cannot read structure ID field. The developer

specified a structure ID column (via the Register Descriptive Flexfields form) that does not exist in

this block of this form.

Action: Contact your support representative.

[APP–684] Flexfield routine &ROUTINE cannot find flexfield definition for application &APPID,

and code &CODE.

[APP–686] Program error: Please contact your system administrator or support representative.

Cause: Flexfields use special pseudo fields to communicate with QuickPick and other

Application Object Library features. This error has probably occurred because the system is out of

memory, and the routine &ROUTINE cannot write to a pseudo field.

[APP–688] Program error: Please contact your system administrator or support representative.

Cause: Flexfields use special pseudo fields to communicate with QuickPick and other

Application Object Library features. This error has probably occurred because the system is out of

memory, and the routine &ROUTINE cannot write to the !FLEX pseudo field.

[APP–690] Program error: The data that defines the flexfield on this field may be inconsistent.

Inform your system administrator that the routine &ROUTINE could not find any segments for the

flexfield specified by Application ID = &APPID, Code = &CODE and structure number = &NUM

[APP–692] Program error: Please contact your support representative. FLEXFIELDS

SERVER–SIDE VALIDATION package could not determine whether GL is installed because of an

exception in FND_INSTALLATION.GET()

[APP–694] The unique ID number for this code combination is too large. Inform your system

administrator that the database sequence &SEQNAME should not exceed &CCIDLIMIT.

[APP–698] Flexfield segment combination not found. Inform your system administrator that the

combination identified by the unique ID number &CCID could not be found in the combinations

table for the flexfield structure identified by Application = &APNM, Flexfield Code = &CODE and

Structure Number &NUM

[APP–700] Concatenated segment values or descriptions exceed the maximum length of

&MAXFLDLEN.

Action: The maximum length of the each segment value or description must be reduced so that

the maximum concatenated length will not exceed &MAXFLDLEN. Contact your system

administrator.

[APP–703] Program error. Please inform your support representative that the descriptive flexfields

server validation function has been called incorrectly. The segment ids for column &COLNAME of

type &COLTYPE were not initialized using FND_FLEX_DESCVAL.SET_COLUMN_VALUE()

prior to calling FND_FLEX_DESCVAL.VALIDATE_DESCCOLS(). The error is either in a form,

or in a server–side package that calls the descriptive flexfields validation routine.

[APP–704] Program error. Please inform your support representative that the descriptive flexfield

&DESCR_FLEX_NAME in the application &APPID could not be found.

[APP–705] Program error. Please inform your support representative that the descriptive flexfields

server validation function has been called with an invalid data field, &DATAFIELD, or with an

alternate table, &TABLE, that does not exist or does not contain this data field. The error is either

in the form, or in a server–side package that calls the flexfields validation routine.

[APP–706] Routine &ROUTINE: Detected a data error.

[APP–707] Program error. Please inform your support representative that the descriptive flexfields

server validation function has been called with an alternate table, &TABLE, that either does not

exist or does not contain the same segment columns as those specified in the flexfield definition.

The error is either in the form, or in a server–side package that calls the flexfields validation

routine.

[APP–708] The data that defines the flexfield on this field may be inconsistent. Please inform your

support representative that the SQL statement that selects default values for one or more segments

of this flexfield has returned more than one row. The first 1000 bytes of the SQL statement that

caused the error are: &SQLSTR

[APP–709] Program error. Please inform your support representative that the descriptive flexfields

server validation function has been called with a rowid, &ROWID, that does not represent an

existing row in the table, &TABLE. The error is either in the form, or in a server–side package that

calls the flexfields validation routine.

[APP–710] An unexpected error has occurred. Please inform your system administrator that the

error: &MSG occurred when the FND_FLEX_SERVER package tried to execute the SQL

statement below. If tables or sequences do not exist this may indicate a problem with your

installation. Make sure grants and synonyms exist so that all tables, views, and sequences in the

SQL statement are visible from the database account in which the FND_FLEX_SERVER package

resides (usually APPLSYS). If this is a select statement and the last portion of the where clause is in

incorrect, then an invalid where clause may have been supplied in the flexfield definition. The error

is probably either in the form, or in a server–side package that calls the flexfield validation routine.

SQL statement (first 1000 bytes): &SQLSTR

[APP–712] You have two global segments, segments ”&SEG1” and ”&SEG2”, in your descriptive

flexfield whose segment names map to identical view column names. The view generator uses

underscores ( _ ) to replace all characters in the segment name that are other than alphanumeric

characters and underscores. For example, the names ”Segment 1’s Name” and

”Segment_1_s_Name” would be the same once the space and apostrophe become underscores ( _ ).

Change one of your segment names to a new name so that the segment names in a structure will not

be identical after correction for non–alphanumeric characters.

[APP–714] You have two segments, segments ”&SEG1” and ”&SEG2”, for the &CTX context (that

is, two segments in the same descriptive flexfield structure) whose segment names map to identical

view column names. The view generator uses underscores ( _ ) to replace all characters in the

segment name that are other than alphanumeric characters and underscores. For example, the

names ”Segment 1’s Name” and Segment_1_s_Name” would be the same once the space and

apostrophe become underscores ( _ ). Change one of your segment names to a new name so that the

segment names in a structure will not be identical after correction for non–alphanumeric characters.

[APP–716] The combinations table for this flexfield contains more than one entry that matches the

entered values. Inform your system administrator that the combination identified by the number

&CCID is duplicated.

[APP–718] Please enter a unique Key Flexfield &CONTEXT. This Key Flexfield &CONTEXT is

already defined for some other key flexfield.

[APP–722] Program error: Please contact your support representative. There are two rows in the

FND_FLEX_VALIDATION_RULE_STATS table that have the same combination of

APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM. This should not be possible due to

the unique index FND_FLEX_VAL_RULE_STATS_U1. Check to make sure this index is correctly

installed.

[APP–724] The data that defines the flexfield on this field may be inconsistent. Inform your system

administrator that the routine: &ROUTINE found a duplicate flexfield structure definition for

Application = &APPL, Code = &CODE, and Structure number = &NUM

[APP–726] This is a duplicate sequence for the specified structure.

Cause: The combination of structure and sequence that you have entered already exists.

Action: Update the sequence number to make the combination unique. For this Structure the

record with the highest sequence will be evaluated first.

[APP–728] A %TYPE% validation rule already exists. You cannot add another.

[APP–730] This flexfield has an invalid value set. It may use a special value set that uses an Edit

event user exit, and the user exit has failed. If you are using a form on a graphical user interface

(GUI) you may have an invalid value set of a different type, possibly a table–validated value set

where the table or view does not exist or where there is an invalid WHERE clause. Contact your

system administrator or support representative to check and correct the value sets this flexfield uses.

[APP–734] Please enter a valid value for the &ATTRIB segment qualifier using the Segment

Qualifiers pop–up window. Or, contact your system administrator to define a default value for this

segment qualifier using the Register Key Flexfield form.

[APP–736] Error loading special value set for shorthand aliases in routine &ROUTINE

[APP–738] Error detected when attempting to load value sets in routine &ROUTINE

[APP–746] Program error: Flexfield compiler could not write compiled definition to table.

[APP–750] An unexpected error has occurred. Please contact your support representative and

forward the following additional information: FLEXFIELDS SERVER–SIDE VALIDATION

package could not find the PLSQL function GL_FLEX_INSERT_PKG.FDFGLI(): &MSG

[APP–756] Cannot find combination CCID=&CCID CODE=&FLXCODE &QTSET&CCID2

[APP–760] Program error. Please inform your support representative that: Flexfields HASH_LOCK

PLSQL function returns &ERRNUM to fdfhlk

[APP–762] Routine &ROUTINE found segment &COLNAME has invalid range validation data.

The flexfield segment &COLNAME is defined as either a Low or a High segment and there is no

corresponding High or Low segment in this flexfield structure. Range segments that use Low or

High designations must occur in matched pairs within a flexfield structure. Redefine your flexfield

segments so that you define matched pairs of Low and High segments, preferably as consecutive

segments. Your segments do not necessarily need to use the same value set.

[APP–766] You cannot delete a rollup group being used by a flexfield

Cause: You attempted to delete this rollup group. For a rollup group to be deleted, it must not

be used by any values (enabled or disabled).

Action: Change all values that use this rollup group to use another rollup group, then delete

this rollup group.

[APP–768] Please do not make this change. It will cause a hierarchy loop

Cause: You tried to make a change to your hierarchy definitions that would cause a loop in

your hierarchy. One of the descendants of the new range is &PARENT. This value is a parent of

the current value.

Action: Reduce the scope of the range to not include &PARENT.

[APP–770] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Flexfield cannot interpret combination QuickPick column clause. The flexfield

user exit #FND POPID has been called incorrectly. Make sure the COLUMN= parameter is correct.

Make sure the display width is specified properly with no spaces, and with both open and close

parentheses.

[APP–774] The value passed for the mode parameter to one of the Flexfield API functions is not

valid. Consult the documentation for the list of valid modes.

[APP–776] Invalid column name ”&COLNAME”. Contact system administrator.

[APP–778] Invalid context field value ”&CONTEXT” passed to flexfield routine &ROUTINE

Action: Pass an existing context field value or define this context value using the Define

Descriptive Segments form.

[APP–780] Program error: Please contact your support representative. Invalid value for the COPY

parameter in one of the #FND POPID | VALID | LOADID user exits.

Action: Pass the COPY parameter in the form: COPY=”:block.field ##n{ALL | flexfield

qualifier | segment number}”.

[APP–782] The COPY field you specified contains an invalid value

Cause: The COPY field specified in the COPY parameter to one of the #FND POPID | VALID |

LOADID user exits contains invalid values for the segments specified in the COPY parameter. The

value &VALUE is invalid for segment &SEGNAME.

Action: Change the value in the COPY field so that it contains valid values for the segments

specified in the COPY parameter.

Action: Change the field specified as the COPY field so that it contains valid values for the

segments specified in the COPY parameter.

[APP–784] Invalid reference &REFVAL in default value defined for segment &SEGMENT Please

check the default values you have specified for your segments.

[APP–786] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that the default type for the &SEGNAME segment is not recognized.

[APP–788] Routine &ROUTINE cannot calculate derived value due to an invalid derivation rule

code.

Action: Contact your system administrator or support representative. Check the

DERIVATION_RULE_CODE column of the FND_VALUE_ATTRIBUTE_TYPES table. The only

currently supported value is G12.

[APP–790] Program error: Please contact your support representative. Invalid DERIVED parameter

to one of the flexfield user exits #FND POPID | VALID | LOADID. The DERIVED parameter must

be in the form: DERIVED=”:block.field ##nsegment qualifier”.

[APP–792] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE was unable to interpret the include/exclude indicator

&INCPTR on your value validation rule. The flexfield user exits #FND LOADID, #FND POPID, or

#FND VALID have been called incorrectly. Make sure the VRULE= parameter is correct. Make

sure the value is in quotes, the \n’s are in lower case, there are no spaces around the \n’s, and all the

information is provided. Valid include/exclude indicator values are I and E.

[APP–794] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE has been called with an invalid cross–validation mode and

cannot interpret control parameter. Routine must be called only with FULL or FOR_INSERT

cross–validation modes.

[APP–796] The data that defines the flexfield on this field may be inconsistent. Inform your system

administrator that the $FLEX$ reference in the flexfield bind variable &BTOKEN has a syntax

error. This token must reference either the VALUE, ID or MEANING of some previous segment.

This flexfield bind variable is in either a WHERE clause in a table–validated value set, or in a

default value for one of the segments of this flexfield.

[APP–798] Invalid reference &REFVAL in value set attached to segment &SEGMENT Please

check the WHERE clauses of your table validated value sets.

[APP–800] The data that defines the flexfield on this field may be inconsistent. Inform your system

administrator that the profile specified in &BTOKEN could not be found. This profile is either

referenced by a WHERE_CLAUSE token passed into the flexfield definition in the form, a WHERE

clause in a table–validated value set, or a default value for one of the segments of this flexfield.

[APP–802] You entered an invalid query condition. Valid query conditions are constants, ”<

’value’”, ”> ’value’”, ”= ’value’”, ”<= ’value’”, ”>= ’value’”, ”!= ’value’”, ”<>

’value’”. and ”#BETWEEN ’value1’ and ’value2’”. You may enter one of the above conditions, or

clear the field.

[APP–804] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE unable to find flexfield qualifier &ATTYPE. The flexfield

user exits #FND LOADID, #FND POPID, or #FND VALID have been called incorrectly. Make sure

the flexfield qualifiers specified match those defined in the Register Key Flexfield form.

[APP–806] The default value &DEFVAL is invalid for the &SEGNAME segment. Your default

value will be ignored. Please inform your system administrator that: Add the value &DEFVAL to

the value set for segment &SEGNAME, or choose another default value in the Key Flexfield

Segments form or Descriptive Flexfield Segments form. Use the Edit Concurrent Program or

Define Report Set form for Standard Report Submission report defaults.

[APP–808] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE cannot find segment &SEGNAME. This segment may not

be defined.

[APP–810] Program error: Please inform your support representative that: Invalid segment

number(&SEGNUM) passed to flexfield routine &ROUTINE. Routine must receive a segment

number between 1 and the total number of segments in the descriptive flexfield context or the key

flexfield structure.

[APP–812] Program error: Please contact your support representative. Invalid TYPE parameter

specified for one of the flexfield user exits #FND POPIDR | VALIDR | LOADIDR

Action: Pass the TYPE parameter in the form: TYPE=”concatenated types field##ntype field

suffix”.

[APP–814] Program error: Please contact your support representative. Invalid TYPE_SIZES

parameter passed for one of the flexfield user exits #FND POPIDR | VALIDR | LOADIDR

Action: Pass the TYPE_SIZES parameter in the form: TYPE_SIZES=”value display

size##ndescription display size”. Value display size must be between 1 and the maximum value

size defined in the value set. Description display size must be between 0 and the maximum

description size defined in the value set.

[APP–816] Program error: Please contact your support representative. Invalid TYPE_VALIDATION

parameter specified for one of the flexfield user exits #FND POPIDR | VALIDR | LOADIDR

Action: Pass the TYPE_VALIDATION parameter in the form: TYPE=”value

set##nrequired##ndefault”.

[APP–818] Program error: Please contact your support representative. Invalid VALATT parameter

specified for one of the flexfields user exits #FND POPID | VALID | LOADID

Action: Pass the VALATT parameter in the form: VALATT=”:block.field ##nflexfield

qualifier##nsegment qualifier”.

[APP–820] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE cannot interpret validation type. The flexfield user exits

#FND LOADID, #FND POPID, or #FND VALID have been called incorrectly. Make sure the

VALIDATE= parameter is correct. Valid validation types are: NONE, PARTIAL, FULL,

FOR_INSERT, QUERY, and QUERY_BASE.

[APP–822] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE was unable to find the segment qualifier. The flexfield

user exits #FND LOADID, #FND POPID, or #FND VALID have been called incorrectly. Make sure

the segment qualifiers specified match those defined in the Define Qualifiers form.

[APP–824] You cannot use the menu from within this flexfield. Contact your support

representative. Certain flexfields defined with the old trigger definition do not support the menu.

The #FND POPID call in the form must be changed to use the new trigger format, including the

argument NAVIGATE=Y.

[APP–826] The flexfield concatenated segments field does not contain values for all the enabled

segments that are displayed.

[APP–828] Please enter the required context field value in the &FLEXFIELD flexfield. The

context field (also known as a structure field) appears as one of the first segments in your flexfield.

[APP–830] Program error: Please contact your support representative. DATA_FIELD parameter

missing from a flexfield user exit. If you specify USEDBFLDS=”N” in one of the #FND POPDESC

| VALDESC | LOADDESC user exits, you must use the DATA_FIELD parameter.

Action: Pass the DATA_FIELD parameter in the form: DATA_FIELD=”:block.field”.:

[APP–836] Please enter the required &VALTYPE value for the &SEGMENT segment in the

&FLEXFIELD flexfield

[APP–838] &ROUTINE: Shorthand prompt is missing when shorthand is enabled

[APP–840] Program error: Please inform your support representative that: The flexfield on this field

has been called incorrectly. Inform your support representative that the &TOKNAME token was

specified incorrectly to the flexfields server–side validation function. Segment qualifier names

cannot be null. The error is either in the form, or in a server–side package that calls the flexfields

validation routine.

[APP–842] Program error: Please contact your support representative. You must pass the

TYPE_HEADING parameter to a flexfield user exit

Cause: For every TYPE parameter you pass to one of the #FND POPIDR | VALIDR |

LOADIDR user exits, you must pass a TYPE_HEADING parameter in the form:

TYPE_HEADING=”heading”.

Action: Pass one TYPE_HEADING parameter to the flexfield user exits for every TYPE

parameter.

[APP–844] Program error: Please contact your system administrator. You must pass the

TYPE_SIZES parameter to a flexfield user exit

Cause: For every TYPE parameter you pass to one of the #FND POPIDR | VALIDR |

LOADIDR user exits, you must pass a TYPE_SIZES parameter in the form: TYPE_SIZES=”value

display size##ndescription display size”.

Action: Pass one TYPE_SIZES parameter to the flexfield user exits for every TYPE parameter.

[APP–846] Program error: Please contact your support representative. You must pass the

TYPE_VALIDATION parameter to a flexfield user exit

Cause: For every TYPE parameter you pass to one of the #FND POPIDR | VALIDR |

LOADIDR user exits, you must pass a TYPE_VALIDATION parameter in the form:

TYPE_VALIDATION=”value set##nrequired##ndefault”.

Action: Pass one TYPE_VALIDATION parameter to the flexfield user exits for every TYPE

parameter.

[APP–850] Descriptive flexfield context field is currently in use

[APP–852] This flexfield uses an invalid value set

Cause: This flexfield uses a special value set, and that value set is incompletely defined.

Action: Contact your support representative. Additional information for support

representative: Check the value sets this flexfield uses. At least one of the value sets uses Special

Validation. This value set is missing an expected Edit event user exit. Add the correct Edit event

user exit to your value set.

[APP–854] &ROUTINE: Cannot find descriptive column information.

[APP–856] Cannot find enabled global segment. Descriptive flexfields require the mandatory

Global Context to be enabled.

[APP–858] Flexfield compiler cannot find enabled key flexfield columns.

[APP–862] Program error: Please contact your system administrator. The flexfield on this field has

been called incorrectly. The WHERE_CLAUSE token was specified incorrectly to the flexfields

server–side validation function. The WHERE_CLAUSE token cannot refer to a previous segment

using the :$FLEX$ mechanism. The error is either in the form, or in a server–side package that

calls the flexfields validation routine.

[APP–864] &Routine: Cannot find flexfield data

[APP–866] Out of memory

Cause: &ROUTINE cannot allocate memory for WHERE= parameter of the flexfield user

exits, or the SQL where clause of a table validated value set because the system is out of memory.

Action: Contact your system administrator or support representative.

[APP–868] Allow Summary Values must be set to ”No ” for this value set . You cannot specify

summary values for table validated value sets containing a ID Column or Additional Columns.

[APP–870] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that: The parent value set for the dependent segment &CHILD could not be

found in the flexfield structure specified by Application ID = &APPID, Code = &CODE and

structure number = &NUM

[APP–874] Routine &ROUTINE found no rows in table &TAB. Please contact your system

administrator or support representative.

[APP–876] No rows found in DUAL

Action: Ensure one and only one record exists in DUAL.

[APP–878] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE was unable to find the values for your value validation

rule. The flexfield user exits #FND LOADID, #FND POPID, or #FND VALID have been called

incorrectly. Make sure the VRULE= parameter is correct. Make sure the value is in quotes, the \n’s

are in lower case, there are no spaces around the \n’s, and all the information is provided.

[APP–880] &ROUTINE cannot find segment qualifier

Cause: &ROUTINE cannot find segment qualifier for this segment. The segment qualifier

position is &VALPOS.

Action: Define the segment qualifiers for this value by querying it up in the Define Key

Segment Values form.

[APP–882] &ROUTINE cannot find segment qualifier

Cause: &ROUTINE cannot find segment qualifier for segment number &SEGNUM. The

segment qualifier position is &VALPOS. This is caused by defining values for a value set before it

is assigned to all of the flexfields that will use it.

Action: Define the segment qualifiers for this value by querying it up in the Define Key

Segment Values form. Use the segment qualifiers window, and save your changes. Because

flexfield segment values are cached, you must change responsibilities to restore the value.

[APP–884] There is an empty required flexfield in this row. Enter values

Cause: The flexfield in this row requires values for one or more segments, but it currently does

not contain any segment values.

Action: Enter the flexfield window, choose valid values for all required segments, and save

your changes.

[APP–888] Program error: Invalid arguments to the flexfield routines. Please inform your support

representative that: Routine &ROUTINE was unable to find the segment qualifier. The segment

qualifier name parameter is required.

[APP–890] The flexfield view generator cannot create a view with more than 256 columns. Your

descriptive flexfield contains more than 253 uniquely named segments. Change the names of some

of your context–sensitive segments so that they share names and will both occupy the same view

column (change segments in structures to share names with segments in different structures).

Regenerate your view (refreeze and recompile your flexfield).

[APP–892] Out of memory

Cause: FDFQPC unable to allocate temporary 64K memory for code combination QuickPick

statement because the system is out of memory.

Action: Contact your system administrator or support representative.

[APP–894] Out of memory

Cause: FDFQPC cannot allocate temporary memory for QuickPick statement because the

system is out of memory.

Action: Contact your system administrator or support representative.

[APP–896] Out of memory

Cause: &ROUTINE cannot allocate memory because the system is out of memory.

Action: Contact your system administrator or support representative.

[APP–898] The output structure parameter is required in routine &ROUTINE

Cause: You passed a null pointer for the output structure in &ROUTINE.

Action: Pass a pointer to an allocated output structure.

[APP–900] Routine &ROUTINE found an unmatched Pair value set on segment &COLNAME

Cause: The flexfield routine &ROUTINE has found that the segment &COLNAME uses a Pair

value set and that no other segment in this flexfield structure uses the same Pair value set. A Pair

value set must be used for two segments in the same flexfield structure.

Action: Redefine your flexfield segments so that you use the same Pair value set on two

segments, preferably as consecutive segments.

[APP–902] The data that defines the flexfield on this field may be inconsistent. Inform your system

administrator that the segment referred to by the flexfield bind variable &BTOKEN could not be

found. Make sure this variable references the segment or value set name of a prior segment in the

flexfield structure. This flexfield bind variable is in either a WHERE clause in a table–validated

value set, or in a default value for one of the segments of this flexfield.

[APP–904] Missing required value in a prior segment

Cause: The value for this segment depends upon the value in a prior segment, and there is no

value in the prior segment.

Action: Enter a value for the prior segment. Additional information for support representative:

This may also be caused by incorrect use of the DISPLAY= token to the flexfield user–exits. You

may also need to specify a default value for the prior segment.

[APP–906] You can only query existing flexfield code combinations. You entered query criteria in

your flexfield that does not identify an existing code combination. Therefore, your query will not

return any rows. Enter a valid code combination, or enter only the flexfield segment values you

know, or do not enter any values in the flexfield.

[APP–910] The flexfield on this field has been called incorrectly. Inform your support

representative that the &TOKNAME token was specified incorrectly to the flexfields server–side

validation function. The qualifier name: &NAME... is longer than its maximum length of 30

characters. The error is either in the form, or in a server–side package that calls the flexfields

validation routine.

[APP–914] Required flexfield segment is empty but not displayed

Cause: A required segment of this flexfield is blank, but the segment is not displayed and thus

cannot be entered.

Action: Exit the flexfield using the [Exit] key. Contact your support representative.

Action: Exit the flexfield using the [Exit] key. Change the value set of the non–displayed

required segment to not be required, or add a valid default value for the non–displayed required

segment.

Action: Exit the flexfield using the [Exit] key. Change the flexfield routine calls in your form

so that the non–displayed required segment is displayed.

[APP–920] You have a segment, &SEG1 in context &CTX, whose name maps to the same view

column name as the context prompt. The view generator uses underscores ( _ ) to replace all

characters in the segment name that are other than alphanumeric characters and underscores.

Change your segment name to a new name so that the segment name and context prompt will not be

identical after correction for non–alphanumeric characters.

[APP–922] You have a context–sensitive segment, &SEG1 in context &CTX, whose name maps to

the same view column name as the global segment &SEG2. The view generator uses underscores (

_ ) to replace all characters in the segment name that are other than alphanumeric characters and

underscores. Change your context–sensitive segment name to a new name so that the

context–sensitive segment name and the global segment name will not be identical after correction

for non–alphanumeric characters.

[APP–924] You chose a segment number that is used by another segment

Cause: You chose a segment number that is used by another segment in this flexfield. If

segment number is not unique, then the order (in the window) of the segments with duplicate

segment numbers is random. Flexfields allows you to have duplicate segment numbers to make

reordering your segments easier.

Action: Choose a unique segment number for this segment, or change the segment number for

other segments that share this number.

[APP–926] &ROUTINE: Compiler found data integrity problem with segment attribute data

[APP–936] The data that defines the flexfield on this field may be inconsistent. Inform your system

administrator that the SQL WHERE clause listed below does not contain the correct number of

quotation marks. This SQL clause may be in a WHERE_CLAUSE token passed into the flex

definition in the form, a WHERE clause in a table–validated value set, or a default value for one of

the segments of this flexfield. The first 1000 bytes of the SQL statement that caused the error is:

&CLAUSE

[APP–938] The flexfield on this field has been defined incorrectly. Inform your support

representative that the FND_FLEX_SERVER.VALIDATE_COMBINATION() function has been

called incorrectly. An invalid flag has been specified to this function. To continue using this form,

have the system administrator turn off wide area operation by setting profile option – Flexfields:

Validate on Server to N

[APP–940] The flexfield on this field has been defined incorrectly. Inform your support

representative that the FND_FLEX_SERVER.VALIDATE_COMBINATION() function has been

called incorrectly. Flexfields server–side validation does not support invoking modes other than

VALID (V), POPID (P), and LOADID(L). To continue using this form, have the system

administrator turn off wide area operation by setting profile option – Flexfields: Validate on Server

to N

[APP–942] The flexfield on this field has been defined incorrectly. Inform your support

representative that the FND_FLEX_SERVER.VALIDATE_COMBINATION() function has been

called incorrectly. Flexfields server–side validation does not support validation modes other than

FULL, PARTIAL or PARTIAL_IF_POSSIBLE. To continue using this form, have the system

administrator turn off wide area operation by setting profile option – Flexfields: Validate on Server

to N

[APP–944] Program error: Please inform your support representative that: FLEXFIELDS

SERVER–SIDE VALIDATION package reports error: &MSG

[APP–946] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that the value set &VSNAME is missing its table validation information.

[APP–948] The flexfield on this field contains a table–validated value set, &VSNAME, that has an

Additional Columns clause that contains the word INTO. This prohibits operation in the mode that

optimizes performance over a wide–area network. To continue using this form, have the system

administrator either remove all table–validated value sets from this flexfield definition, or turn off

wide area operation by setting the profile option – Flexfields: Validate on Server to N

[APP–950] The flexfield on this field contains a segment whose default type is FIELD or

ENVIRONMENT. This prohibits operation in the mode that optimizes performance over a

wide–area network. To continue using this form, have the system administrator either change the

default type, or turn off wide area operation by setting the profile option – Flexfields: Validate on

Server to N.

[APP–952] The flexfield on this field contains a value set (&VSNAME) that uses special or pair

user–exit validation. This prohibits operation in the mode that optimizes performance over a

wide–area network. To continue using this form, have the system administrator either remove the all

special or pair validated value sets from this flexfield definition, or turn off wide area operation by

setting the profile option – Flexfields: Validate on Server to N

[APP–956] The flexfield on this field has been called incorrectly. Inform your support

representative that the DISPLAYABLE, INSERTABLE, or UPDATABLE token was specified

incorrectly to the flexfields server–side validation function. The qualifier &QTOKEN was not

found. The error is either in the form, or in a server–side package that calls the flexfields validation

routine.

[APP–958] The flexfield on this field has been called incorrectly. Inform your support

representative that the DISPLAYABLE, INSERTABLE, or UPDATABLE token was specified

incorrectly to the flexfields server–side validation function. The segment number &SEGNUM is

invalid. The error is either in the form, or in a server–side package that calls the flexfields

validation routine.

[APP–960] The flexfield on this field has been called incorrectly. Inform your support

representative that the DISPLAYABLE, INSERTABLE, or UPDATABLE token was specified

incorrectly to the flexfields server–side validation function. A qualifier name or segment number is

null. The error is either in the form, or in a server–side package that calls the flexfields validation

routine.

[APP–966] Program error: The flexfield on this field has been called incorrectly. Please inform your

support representative that: The VALATT token was specified incorrectly to the flexfields

server–side validation function. A separator (&SEP) is missing from the qualifier: &NAME. The

error is either in the form, or in a server–side package that calls the flexfields validation routine.

[APP–968] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. The include–exclude flag does not start with I or E for the rule with segment

qualifier name: &NAME. The error is either in the form, or in a server–side package that calls the

flexfields validation routine.

[APP–970] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. The application short name is longer than 50 characters in the rule with

segment qualifier name: &NAME. The error is either in the form, or in a server–side package that

calls the flexfields validation routine.

[APP–971] The flexfield on this field has been called incorrectly. Inform your support

representative that the &ARG argument in the flexfield definition exceeds its maximum length of

&MAXLEN bytes. The error is either in the form, or in a server–side package that calls the

flexfields validation routine. Try removing unnecessary white space from the argument if possible.

[APP–972] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. The error message is longer than 100 characters in the rule with segment

qualifier name: &NAME. The error is either in the form, or in a server–side package that calls the

flexfields validation routine.

[APP–974] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. The portion of the token that specifies included or excluded values is longer

than 240 characters in the rule with segment qualifier name: &NAME. The error is either in the

form, or in a server–side package that calls the flexfields validation routine.

[APP–976] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. No include or exclude flag was found for the rule with segment qualifier name:

&NAME. The error is either in the form, or in a server–side package that calls the flexfields

validation routine.

[APP–978] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. No error message was found for the rule with segment qualifier name:

&NAME. The error is either in the form, or in a server–side package that calls the flexfields

validation routine.

[APP–980] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. No error message name was found for the rule with segment qualifier name:

&NAME. The error is either in the form, or in a server–side package that calls the flexfields

validation routine.

[APP–982] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. No values to be included or excluded were found for the rule with segment

qualifier name: &NAME. The error is either in the form, or in a server–side package that calls the

flexfields validation routine.

[APP–984] The flexfield on this field has been called incorrectly. Inform your support

representative that the VRULE token was specified incorrectly to the flexfields server–side

validation function. A separator (&SEP) is missing from VRULE number &TOKNUM. The error

is either in the form, or in a server–side package that calls the flexfields validation routine.

[APP–988] Routine &ROUTINE found too many rows in table &TAB. Please contact your system

administrator or support representative.

[APP–990] The unique qualifier you have enabled is already being used by another segment.

Disable this unique qualifier for this segment.

[APP–992] Flexfields was unable to freeze flexfield data because of an error. Determine the cause

of the error. Once you resolve it, you can recompile your flexfield. Likely problems include

incompletely–specified flexfield qualifiers (especially for the Accounting Flexfield) or other

incomplete segment information.

[APP–994] Flexfields could not freeze flexfield data because of an error. Determine the cause of

the error. Once you resolve it, you can recompile your flexfield. A likely problem is incomplete

segment information.

[APP–996] Flexfields was unable to find values for VRULE routine &ROUTINE because of

improper formatting of the VRULE parameter. The proper format for the VRULE parameter is:

VRULE=”flexfield qualifier\nsegment qualifier\n {I[nclude] | E[xclude]}\nerror message

text\nvalidation value1\n validation value2...”

[APP–999] An invalid token ’&TOKEN’ was passed to a user exit.

[APP–999] Could not find basepath environment variable ’&BASEPATH’ for the

’&APPLICATION_NAME’ application. The variable is not set in your environment.

[APP–999] Duplicate row, please try a different key.

[APP–999] File ’&FILE’ could not be opened for reading.

[APP–999] File ’&FILE’ could not be opened for writing.

[APP–999] Incorrect arguments were passed to user exit #&USRXIT. Please correct the user exit

call in your form exit.

[APP–999] Possible infinite loop detected in &ROUTINE. Abort current list.

Cause: This form is corrupted. It may be caused by a duplicate field within this block.

Action: Please contact your support representative.

[APP–999] Read error occured on line &LINE of file ’&FILE’.

[APP–999] The reference form cannot be launched from the current login context.

&ERROR_MESSAGE

[APP–999] The routine &ROUTINE was unable to retrieve the name of the current language.

[APP–999] The routine &ROUTINE was unable to set the working language to &NLSLANG.

[APP–999] Unmatched quote marks in string (&STRING) detected in routine &ROUTINE.

[APP–999] Write error occured on line &LINE of file ’&FILE’.

[APP–1000] Flexfields routine &ROUTINE unable to read compiled attributes field &FLDNAM.

This is often caused because the field does not exist. Please contact your support representative.

[APP–1002] Flexfields routine &ROUTINE unable to read field &FLDNAME. This is often caused

by the field not being defined. Contact your support representative, or check to see if the field exists

and define it if it does not.

[APP–1006] Flexfields routine &ROUTINE was unable to write to the compiled attribute field

&FLDNAM. This often happens because the field does not exist. Please contact your support

representative.

[APP–1008] Program error: Unable to write to the field &FLDNAME. Please inform your support

representative that: Flexfields routine &ROUTINE was unable to write to the specified field,

&FLDNAME. This is often caused by the field’s not existing or not being defined properly. Check

the form to see if the field is defined and define it if it is not.

[APP–1016] Routine &ROUTINE: Unknown structure ID &NUM for flexfield code &CODE with

application ID &APPID

[APP–1020] Routine &ROUTINE detected an unknown flexfield shorthand alias profile value

[APP–1022] The flexfield on this field contains a flexfield bind variable with a :BLOCK.FIELD

reference. This prohibits operation in the mode that optimizes performance over a wide–area

network. To continue using this form, have the system administrator either remove all

:BLOCK.FIELD references, or turn off wide area operation by setting the profile option –

Flexfields: Validate on Server to N. The reference may be in a WHERE_CLAUSE token passed

into the flexfield definition in the form, a WHERE clause in a table–validated value set, or a default

value for one of the segments of this flexfield.

[APP–1024] You passed an incorrect value to a flexfield user exit.

Cause: You passed USEDBFLDS=”Y” to one of the flexfield user exits #FND POPID |

LOADID | VALID | POPDESC | LOADDESC | VALDESC and the form does not have all the

database SEGMENT1 – SEGMENTn or ATTRIBUTE1 – ATTRIBUTEn fields.

Action: Set USEDBFLDS=”N” if the form does not use the SEGMENTn or ATTRIBUTEn

fields.

Action: Check that all the SEGMENTn or ATTRIBUTEn fields are in the form. View previous

messages to see which field is missing.

[APP–1028] The value set field for the segment &SEGMENT cannot be left blank since the

underlying application table column is of a column type other than Character.

[APP–1030] Value &VALUE is longer than its maximum length of &LENGTH characters.

[APP–1032] You have a context–sensitive segment, &SEG1 in context &CTX1, whose name maps

to the same view column name as the context–sensitive segment &SEG2in context &CTX2, and

these segments use different view column types (for example, one uses a number format and the

other uses a date format). The view generator uses underscores ( _ ) to replace all characters in the

segment name that are other than alphanumeric characters and underscores, and columns whose

names map to the same view column must use the same column format type. Either change one of

your context–sensitive segment names to a new name so that the two segment names will not be

identical after correction for non–alphanumeric characters, or have both segments use the same

value set format type.

[APP–1034] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that the value set &VSNAME has an incorrect date or date–time format.

[APP–1036] The data that defines the flexfield on this field may be inconsistent. Inform your

system administrator that the value set &VSNAME has an incorrectly formatted date or date–time

in the minimum or maximum range field.

[APP–1038] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that the value set &VSNAME has an incorrect format type (&FMT).

[APP–1040] The data that defines the flexfield on this field may be inconsistent. Inform your

system administrator that the value set &VSNAME has an incorrectly formatted number in the

minimum or maximum range field.

[APP–1041] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that the value set &VSNAME has an invalid precision. The precision must be

at least 0, but must be less than the value set maximum size.

[APP–1042] The data that defines the flexfield on this field may be inconsistent. Please inform your

system administrator that the value set &VSNAME has an incorrect validation type (&VTYPE).

[APP–1044] Routine &ROUTINE: Error in Value Set Extension specifications

[APP–1048] Use of this combination restricted by WHERE clause ’&WHERE ’.

[APP–1050] This flexfield cannot be opened because it has no displayed segments. Please contact

your system administrator. Modify your flexfield definition to display one or more segments. This

may also be caused by incorrect use of the DISPLAY= token to the flexfield user exits in the form.

In that case, please contact your support representative.

[APP–1052] You attempted to create a segment combination that is not valid. The system

administrator has defined a flexfield cross–validation rule named &RULENAME that excludes this

combination of segments. However, the error message for this rule could not be found. Contact

your system administrator to correct this problem.

[APP–1054] You attempted to create a segment combination that is not valid. The system

administrator has defined a flexfield cross–validation rule named &RULENAME that excludes this

combination of segments. However, the error message for this rule is not unique. Contact your

system administrator to correct this problem.

[APP–1056] You cannot delete a segment with associated reporting attributes

[APP–1058] &HNAME is not a valid rollup group in the &TNAME template

[APP–1066] Routine &ROUTINE: There is no account segment

[APP–1068] There is no rollup segment in the &SUMTEMP template

[APP–1070] Error appending file &FILENAME1 to file &FILENAME2

Cause: Application Object Library encountered an error appending the file &FILENAME1 to

the file &FILENAME2.

Action: Check that the file names are correct and valid on your system.

Action: Check that the file &FILENAME1 exists. Check that you have privileges to read the

file in the file directory. Contact your system administrator to obtain read privileges.

Action: Check that you have privileges to write the file &FILENAME2. If the file does not

exist, check that you have privileges to create files in the file directory. Contact your system

administrator to obtain create and write privileges.

[APP–1072] &APPLICATION_NAME is invalid.

Cause: You have entered an application name that is unknown to Application Object Library.

Action: Please enter a valid application name.

Action: Contact your system administrator to verify that the specified application name is

installed in your system.

[APP–1080] Error copying file &FILENAME1 to file &FILENAME2

Cause: Application Object Library encountered an error copying the file &FILENAME1 to the

file &FILENAME2.

Action: Check that the file names are correct and valid on your system.

Action: Check that the file &FILENAME1 exists. Check that you have privileges to read the

file in the file directory. Contact your system administrator to obtain read privileges.

Action: Check that you have privileges to write the file &FILENAME2 if the file exists.

Check that you have privileges to create files in the file directory. Contact your system

administrator to obtain create and write privileges.

[APP–1092] You entered an incorrect number of arguments for routine &ROUTINE

Cause: You entered an incorrect number of arguments to the routine &ROUTINE.

Action: Enter the correct number of arguments for the routine.

[APP–1094] This message is already in use. Please enter a unique name

Cause: Message name uniquely identifies a message. You entered a message name that has

already been used to identify another message.

Action: Enter a message name that is not already in use. Message names are case insensitive

so an uppercase message name is the same as a lowercase message name.

[APP–1096] Cannot find application or user information

Cause: The concurrent output file cannot be located because a directory path to the file cannot

be created. Information about the application that created the output file is not available.

Action: Please contact your system administrator.

[APP–1102] Cannot read form name &FORMNAME

Cause: Application Object Library cannot find your form &FORMNAME.

Action: Check that the file name components are correct and valid on your system.

Action: Check that your environment is correctly set and that Application Object Library

environment variables have the correct values. Important Application Object Library environment

variables include, but are not limited to, FND_TOP, APPLFRM, and your application’s basepath.

Refer to your installation manual for a complete list.

Action: Check if your form exists.

Action: Check if you have read and execute privileges on the directory and on the form.

Contact your system administrator to obtain any necessary privileges.

[APP–1112] Out of memory

Cause: &ROUTINE cannot allocate memory because system is out of memory.

Action: Contact your system administrator or support representative.

[APP–1114] You cannot delete the printer type as a printer uses it

Cause: This printer type cannot be deleted because it is used by at least one printer on your

system.

Action: You must call a different printer type for the printers that use this printer type or delete

those printer definitions before you can delete this printer type.

[APP–1118] This menu is used by responsibility &RESPONSIBILITY. It cannot be deleted.

[APP–1122] Cannot close communication channel

Cause: Regression Tester received an error status when attempting to close a communication

channel with the program it was testing.

Action: Contact your support representative.

[APP–1126] Cannot set up communication channel

Cause: Regression Tester received an error status when attempting to establish a

communication channel with the program it was testing.

Action: Contact your support representative.

[APP–1142] Cannot delete &RECORD. This record is referenced in &BLOCK.

[APP–1162] This name is already in use. Please enter a unique name

Cause: You entered a name that has already been used to identify another form or other object

in your application.

Action: Either enter a new name that is not already in use or change and save the name of the

existing object first and then re–enter your name.

[APP–1172] This form name is already in use. Please enter a unique name

Cause: Form name, along with application name, uniquely identifies a form. You entered a

form name that has already been used to identify another form in your application.

Action: Enter a form name that is not already in use.

[APP–1206] This record already exists. You entered a duplicate value or sequence of values that

must be unique for every record.

[APP–1212] Cannot find application information

Cause: The application you specified is not registered.

Action: Register your application using the Register Applications form.

[APP–1214] Invalid currency information type &TYPE was requested

Cause: An attempt was made to get information regarding a currency that is not supported.

Action: Contact your support representative.

Cause: You specified an invalid type argument &TYPE when calling fdugci().

Action: Use one of the supported application types defined in the Application Object Library

header file fdugci.h.

[APP–1218] Error in getting the next sequence value for &SEQUENCE.

[APP–1222] Cannot find language information

Cause: The language you specified is not defined.

Action: Contact your support representative.

[APP–1231] No default web browser was found in your system registry. Please install a web

browser and try again.

[APP–1232] Cannot create new record

Cause: You are not allowed to create new rows in this zone. This may be because this is a

query–only form and you need to navigate to another form to define new rows, or because you do

not have the ability (privileges) to create these objects.

Action: No action required. Refer to your on–line help or documentation for the purpose of

this form.

[APP–1233] Your default web browser could not be started. Please make sure your browser is

installed correctly and try again.

[APP–1234] Cannot delete record

Cause: You are not allowed to delete rows in this zone. This may be prevented for referential

integrity reasons or because the form is not based on a data table.

Action: No action required. Refer to your on–line help or documentation for the purpose of

this form.

[APP–1238] Cannot set value for field &FIELDNAME

Cause: Application Object Library was unable to put a value in the field &FIELDNAME.

Action: Review your error messages with \ Help Error for more information.

[APP–1240] Cannot set a SQL*Forms global variable &GLOBAL

Cause: Application Object Library encountered an error while setting the value for a

SQL*Forms global variable &GLOBAL.

Action: Contact your support representative.

[APP–1242] Cannot read value from field &FIELDNAME

Cause: The field &FIELDNAME could not be located or read.

Action: This error is normally the result of an incorrectly–entered field name string in a trigger,

or a field name string that does not uniquely specify a field in your form. Correct your trigger logic

to precisely specify a valid field.

[APP–1246] You have specified invalid arguments for the routine &ROUTINE

Cause: Some of the arguments to &ROUTINE were either missing or had invalid values.

Action: Correct your program or trigger so as to pass proper arguments to the routine.

[APP–1250] You have entered an incorrect number of arguments for the routine &ROUTINE

Cause: You entered an incorrect number of arguments to the routine &ROUTINE.

Action: Enter the correct arguments for &ROUTINE.

[APP–1256] Cannot run user exit in this context

Cause: The routine &ROUTINE could not run a user–exit because there is no run user–exit

function in this context.

Action: This error is normally the result of setting up a flexfield with user–exit validation.

This flexfield is invoked from outside SQL*Forms, and user–exits have no meaning.

[APP–1260] Valid characters are &VALID

Cause: You may enter only the specified characters in this field. You entered a character(s) not

in the list.

Action: Re–enter your value using the valid characters.

[APP–1264] You cannot delete this product installation.

Cause: You cannot delete this product installation, because the product installation for

application &APP in ORACLE username &USER depends on it.

Action: Change the product dependencies so that no other product installation depends on this

one. Then delete this product installation.

[APP–1266] The Application &APPL for Oracle ID &USERID has already been entered as a

dependency for this installation. Please enter a unique Application/Oracle ID pair.

[APP–1268] The installation of Application &APPL for Oracle ID &USERID has already been

entered. To modify it, you must first enter query mode and find that record.

[APP–1270] Error generating Julian SYSDATE.

Cause: Application Object Library could not generate the current database date as a Julian

value.

[APP–1272] This language ID already exists in the database. Please choose another ID.

[APP–1274] Invalid application ID or language ID.

Cause: Your application_ID (&APPID) and/or your language_ID (&LANGID) is invalid.

[APP–1316] An invalid menu ID was found when building this menu. Please check that all entries

for this menu and all its submenus are valid menu or form names.

[APP–1324] Please enter menus that do not call your menu

Cause: You attempted to make a menu a sub–menu of itself. This loop may be indirect via

several layers of sub–menus.

Action: Change your menu definition so as not to not call earlier menus.

[APP–1330] Application Object Library was unable to build the menu for this responsibility in the

current language. Please check that the menu named for this responsibility is valid, and that all

entries for this menu and all its sub–menus are valid menu or function names in the current

language.

[APP–1343] This currency does not use a decimal. Please enter a whole number.

[APP–1345] List of Values is not available for this field while in Enter–Query mode.

[APP–1346] Ensure database password for this ORACLE username matches new password

Cause: You have registered a new password for this ORACLE username with Application

Object Library. You must ensure that the actual database password matches this value. Until the

registered password and the database password are identical you cannot use the ORACLE ID

through Oracle Financials and you cannot register any ORACLE ID. If you are changing the

password of an APPS schema in Application Object Library release 10.7 or later, you must also

change the password of the APPLSYS account and all other APPS schema accounts to match.

Action: Ensure you change the password in the database if you have not already done so.

Connect to the ORACLE username to which you wish to change the password then issue the

following SQL statement to change your password. SQL: GRANT CONNECT TO [ORACLE

username] IDENTIFIED BY [Password];

[APP–1350] Message file already open

Cause: &APPLICATION attempted to reopen an already open message file while using the

routine msgopn().

Action: No action required.

[APP–1352] Program &OUTCOME

Cause: The program completed execution – in particular it &OUTCOME.

Action: If the program completed normally, no action is required.

Action: If the program completed with a status code indicating failure, consult your installation

guide for the meaning of that status code.

Action: If the program was terminated by a signal, consult your installation guide and

operating system manuals for the meaning of that signal. It could represent an internal error or a

termination request from another process.

[APP–1356] Your new password must be different from your old password

Cause: You entered your old password as your new password. Security requires that you enter

a new password that is different from your old password.

Action: Enter a new password that is different from your old password.

[APP–1360] Driver is currently in use

Cause: A printer type currently uses this driver. You may not delete the driver until it is no

longer in use.

Action: Change the definition of the printer type using this driver.

[APP–1362] You have entered a duplicate printer driver name for the platform entered.

Cause: A printer driver by the same name is already assigned to this platform.

Action: Please enter a unique printer driver name/platform combination.

[APP–1364] You have entered a duplicate style name for the printer type selected.

Cause: A printer style by the same name is already assigned to this printer type.

Action: Please enter a unique style name.

[APP–1366] You have entered invalid dimensions for this printer style

Cause: The dimensions &WIDTH and &LENGTH exceed the boundaries defined by the

maximum and minimum length and width of a concurrent program to which this style is defined

[APP–1372] Please register system printer &PRINTER with Application Object Library

Cause: You have a printer specified in your profile option that is not registered with

Application Object Library (if profile option is not set, the value defaults from the environment

variable PRINTER, which may not correspond to an registered printer).

Action: Register the printer with Application Object Library.

[APP–1374] In order to see profile values, it is necessary to first indicate which profile values you

want to see by checking at least one of the following check boxes: Site, Application, Responsibility,

or User.

[APP–1378] Cannot set value for profile option &OPTION

Cause: User Profiles was unable to set the value for profile option &OPTION.

Action: Check that you are accessing the correct profile option name.

Action: If the profile option &OPTION is defined in the database, you can query the profile

option from the ”Define User Profile Option” form. Check that the ”Allow Write” flag for the

profile option is set to ”Yes”.

Action: If the profile option &OPTION is not defined in the database, then it is created from a

subroutine. Check that the subroutine that creates the profile option &OPTION allows its value to

be changed by passing the ”ENABLE_WRITE” flag.

[APP–1388] Cannot read value for profile option &OPTION in routine &ROUTINE.

Cause: You attempted to read a profile option that either does not exist or was set to be not

readable.

Action: Check that you are accessing the correct profile option name.

Action: If the profile option &OPTION is defined in the database, you can query the profile

option from the ”Define User Profile Option” form. Check that the ”Allow Read” flag for the

profile option is set to ”Yes”.

Action: If the profile option &OPTION is defined in the database, check that the profile option

has a default value set at the site level. A profile option that is not set at any level does not exist

during your session.

Action: If the profile option &OPTION is not defined in the database, then it is created by a

subroutine. Check that the subroutine that creates the profile option &OPTION allows its value to

be read by passing the ”ENABLE_READ” flag.

Action: If the profile option &OPTION is created by a subroutine, check that the subroutine

has already been called.

[APP–1404] An invalid style, &STYLE, is specified

Cause: AOL cannot find a record for the print style &STYLE

Action: Check that the print style &STYLE is a valid style and that a record exists in

FND_PRINTER_STYLES

[APP–1406] Cannot find a printer driver for printer type &TYPE and print style &STYLE

Cause: A printer driver for printer type &TYPE and print style &STYLE does not exist

Action: Check that print style &STYLE is supported on printer type &TYPE and a record

exists in FND_PRINTER_INFORMATION

[APP–1408] Print style &STYLE is invalid for the given dimension and/or printer

Cause: The print style &STYLE is invalid for the given dimension minimum width:

&MINWIDTH maximum width: &MAXWIDTH minimum length: &MINLENGTH maximum

length: &MAXLENGTH or

Cause: The print style &STYLE is not supported for printer &PRINTER or

Cause: The print style &STYLE is invalid for the given dimension and not supported for the

printer

[APP–1410] Cannot find a valid print style for the given dimensions and printer

Cause: Cannot find a valid print style for the given dimension minimum width: &MINWIDTH

maximum width: &MAXWIDTH minimum length: &MINLENGTH maximum length:

&MAXLENGTH or

Cause: Cannot find a valid print style with the given dimension for printer &PRINTER

[APP–1412] An error occurred in getting printer driver information from the database for printer

type &TYPE and print style &STYLE

[APP–1414] An error occurred in getting print style information from the database for &STYLE

[APP–1416] An error occurred in getting printer type information from the database for printer

&PRINTER

[APP–1418] An error occurred while AOL tried to spawn the print process

[APP–1420] You have specified invalid arguments for the routine &ROUTINE

Cause: You entered an incorrect number of arguments to the routine &ROUTINE, or the

arguments you entered are not the type expected.

Action: Enter the correct arguments for &ROUTINE as follows.

[APP–1426] QuickPick definition contains invalid or unspecified key column.

Cause: QuickPick could not find a match for the key column specified.

Cause: QuickPick was not supplied a key column to match against.

Action: Correct the QuickPick definition to contain a valid key column and regenerate the

form.

[APP–1428] QuickPick cannot initialize window

Cause: &ROUTINE encountered an error initializing your QuickPick window.

Action: Check that you have entered valid parameters for the window size.

[APP–1430] Cannot get selected Responsibility values

Cause: The Application Object Library security system did not receive the responsibility you

selected from QuickPick.

Action: Contact your support representative.

[APP–1432] QuickPick cannot return your selected value

Cause: &ROUTINE encountered an error returning your QuickPick choice to a field.

Action: Check that your QuickPick definition specifies a destination field for every selected

column.

Action: Check that your QuickPick definition specifies fields that exist and are writeable.

[APP–1434] &ROUTINE cannot find FROM clause in QuickCode statement

Cause: &ROUTINE encountered an error parsing your SQL statement. FROM clause is

missing.

Action: Check that you have entered your QuickCode definition correctly. Check that your

SQL statement works in SQL*Plus.

[APP–1436] List of Values cannot find any values for you to choose

Cause: The List of Values execution failed to find any values.

Cause: The SQL statement specified to fdlfch() failed to return any values.

Action: Check the message stack for any SQL statement failure messages. Check to make sure

your SQL statement works in SQL*Plus.

[APP–1438] List of Values has no SQL statement

Cause: The List of Values definition contains no SQL= clause, and does not reference a named

SQL object (via SQLNAME=).

Action: Correct the List of Values definition and regenerate your form.

[APP–1440] QuickPick definition must have visible column.

Cause: You have specified a QuickPick definition which contains no visible columns.

Action: Correct the QuickPick and ensure that at least one selected column appears in the

COLUMN= portion of the DEFINE_LISTVAL statement.

[APP–1442] QuickPick cannot open QuickPick window

Cause: QuickPick routine &ROUTINE encountered an error opening your QuickPick window.

Action: Contact your support representative.

[APP–1444] Please enter display column names only for selected columns

Cause: You entered a display column name that does not correspond to any selected columns.

&ROUTINE received a return code of failure.

Action: Enter a display column name that corresponds to a selected column. Enter the column

alias if you have aliased the selected column.

[APP–1446] Opening this window may exceed available system resources. We recommend closing

other windows or applications before opening this window.

[APP–1466] Cannot open file &FILENAME for regression test log file

Cause: The concurrent manager failed to open the regression test log file &FILENAME.

Action: Verify that the file directory has correct write file privileges.

[APP–1470] Changed lines found between reference and test file:

[APP–1472] Differences were detected between the control and test output files. See the error

report in &ERRFILE file for details.

[APP–1474] No differences found between control and test output files.

[APP–1476] Deleted lines in reference file not in test file:

[APP–1478] A fatal error was encountered in processing. Execution has been aborted.

[APP–1480] Comparison completed. &ERRCOUNT difference(s) found.

[APP–1482] Comparison of test and reference output files:

[APP–1484] Inserted lines in test file not in reference file:

[APP–1486] Maximum DIFFERENCES count has been exceeded. Comparison is being aborted.

[APP–1488] Maximum FAILURES count has been exceeded. Execution is being aborted.

[APP–1490] File &FILE could not be found.

[APP–1491] A change of ’&OLDTEXT’ to ’&NEWTEXT’ occurs &COUNT times between

reference and test file.

[APP–1492] Incorrect arguments to FNDRTR45. Usage: FNDRTR45 applsys/pwd 0 Y

<appl_short_name> [<subdir>/]<testname> {GEN||RUN|COMP|RCOMP|COPY}

[<start_label> [<end_label>]]

[APP–1496] Cannot access application ORACLE password

Cause: Application Object Library was unable access your ORACLE password.

Action: Contact your support representative.

[APP–1498] This data group is assigned to a responsibility

Cause: You cannot delete a data group which is assigned to a responsibility.

Action: Change the data group for all responsibilities which reference this data group before

deleting it.

[APP–1500] This application in this data group is assigned to a responsibility

Cause: You cannot delete an application from a data group which is assigned to a responsibility.

Action: Change the application or data group for all responsibilities which reference this

application in this data group before deleting it.

[APP–1502] Cannot encrypt application ORACLE password

Cause: Application Object Library was unable encrypt your ORACLE password.

Action: Contact your support representative.

[APP–1504] This application has already been assigned to this data group

Cause: You chose an application which has already been assigned to this data group. An

application is unique within a data group, so you can only assign each application once.

Action: Choose an application which has not already been assigned to this data group or erase

your changes.

[APP–1506] This responsibility name is already in use. Enter a unique name

Cause: Responsibility name, along with application name, uniquely identifies a responsibility.

You entered a responsibility name that is already being used to identify a responsibility in this

application.

Action: Enter a responsibility name that is not in use in this application.

[APP–1508] Failed to connect

Cause: Application Object Library was unable to connect to the ORACLE database.

Action: Check for ORACLE errors to find out why the connect failed.

Action: Check that you entered the correct username and password by using SQL*Plus and

entering the same username and password.

[APP–1516] Invalid application username, password, or database. Username: &USERNAME

Password: &PASSWORD Database: &DATABASE

[APP–1518] Cannot access application system password

Cause: Application Object Library was unable to access the application system password.

Action: Contact your support representative.

[APP–1524] You cannot delete ORACLE IDs used in installation

Cause: You attempted to delete an ORACLE ID used in installation. You cannot delete the

ORACLE ID.

[APP–1528] Cannot reconnect to gateway

Cause: Application Object Library is unable to reconnect to your gateway ORACLE account

after you unsuccessfully attempted to sign–on.

Action: Check that your gateway environment variable is set correctly.

[APP–1530] Monitor cannot find the user name for an active user

Cause: Application Object Library found no rows while selecting the name of a user to

monitor. This means that there is a referential integrity problem in your database.

Action: Contact your system administrator.

[APP–1540] Unsuccessful logins since your last session : &NUMBER

Cause: Someone has attempted to log in to Oracle Applications using your username

&NUMBER times.

Action: If you suspect that someone without authorization is trying to log in as you by guessing

your password, contact your system administrator for assistance. Change your password

immediately.

[APP–1544] ORACLE ID is currently in use

Cause: A concurrent manager currently uses this ORACLE ID. You cannot delete the

ORACLE ID until it is no longer in use.

Action: Reassign concurrent managers that currently use this ORACLE ID to use a different

ORACLE ID.

[APP–1546] ORACLE ID is currently in use

Cause: A data group currently uses this ORACLE ID. You cannot delete the ORACLE ID

until it is no longer in use.

Action: Reassign data groups that currently use this ORACLE ID to use a different ORACLE

ID.

[APP–1550] ORACLE ID is currently in use

Cause: A sequence currently uses this ORACLE ID. You cannot delete the ORACLE ID until

it is no longer in use.

Action: Reassign sequences that currently use this ORACLE ID to use a different ORACLE

ID.

[APP–1554] Number to CACHE must be less than one cycle

[APP–1560] The Increment By value cannot be zero.

Cause: The Increment By value cannot be zero.

Action: Set the Increment By field to a positive value if you want the sequence to increase. Set

the Increment By field to a negative value if you want the sequence to decrease.

[APP–1562] Application Object Library cannot get information from table &TABLENAME

Cause: Application Object Library encountered an error selecting information from the table

&TABLENAME.

Action: Check that your ORACLE user has select privileges on the table.

Action: Check that the table has been defined correctly.

[APP–1564] ORACLE error &ERRNO in &ROUTINE

Cause: &ROUTINE failed due to &REASON. The SQL statement being executed at the time

of the error was: &SQLSTMT and was executed from the file &ERRFILE.

[APP–1566] SQL statement contains an invalid field reference

Cause: A field referenced in the SQL statement does not exist, or it is not in the form

:BLOCK.FIELD.

Action: Check all fields referenced in the SQL statement.

[APP–1568] Cannot delete row from &TABLE

Cause: Application Object Library was unable to delete a row from the &TABLE table.

Action: Check that the table exists and that your ORACLE user has the correct privileges on

the table.

[APP–1570] Cannot insert row into &TABLE

Cause: Application Object Library was unable to insert a row into the &TABLE table.

Action: Check that the table exists and that your ORACLE user has the correct privileges on

the table.

[APP–1572] Invalid foreign key data was found for this record. Value &VALUE for column

&COLUMN does not exist in table &TABLE.

[APP–1574] Report set terminated due to failure of report: &PROGRAM

Cause: You defined this report set to abort if any of the reports in the report set end in error.

[APP–1576] Standard Report Submission cannot find arguments for &NUMBER reports

Cause: The arguments for &NUMBER reports in this report set are missing and thus these

reports cannot be run.

Action: Resubmit the report set.

[APP–1578] You cannot delete a group that is assigned to a responsibility

Cause: You cannot delete this report security group because it is assigned to a responsibility.

Action: Remove this group from all responsibilities before you delete it.

[APP–1580] You cannot delete a set that is included in a report security group

Cause: You cannot delete this set because it is included in a report security group.

Action: Remove this set from all report security groups before you delete it.

Action: Disable the set by setting the end date rather than deleting it. This will prevent the set

from being submitted.

[APP–1586] This group code is already in use. Please enter a unique code

Cause: Report group code, along with application name, uniquely identifies a report group.

You entered a report group code that has already been used to identify another report group in this

application.

Action: Enter a report group code that is not already in use for this application.

[APP–1588] Please enter a unique application, set or program

Cause: An application, set or program may only be included in a report security group once.

This application, set or program is already in this report security group.

Action: Enter an application, set or program which is not already in this report security group.

[APP–1590] This group name is already in use. Please enter a unique name

Cause: Report security group name, along with application name, uniquely identifies a report

security group. You entered a report security group name that has already been used to identify

another report security group in this application.

Action: Enter a report security group name that is not already in use for this application.

[APP–1592] This sequence number is already in use. Enter a unique number

Cause: Sequence number is unique within a report set. You entered a sequence number that

has already been used in this report set.

Action: Enter a sequence number that has not already been used in this report set.

[APP–1594] This request set name is already in use within this application. Please enter a name

unique within the specified application.

[APP–1600] You have specified invalid arguments for the program &PROGRAM_NAME

Cause: You entered an incorrect number of arguments to the concurrent program

&PROGRAM_NAME, or the arguments you entered are not the type expected.

Action: Enter the correct arguments for &PROGRAM_NAME as follows. Syntax:

&PROGRAM_NAME <ORACLE ID> <Request ID> <OS Flag> <Set

Application ID> <Set ID> <Sequence>

[APP–1602] Delete incompatible programs before changing Incompatibilities Allowed

Cause: You changed Incompatibilities Allowed to ’No’, but incompatible programs have

already been defined for the concurrent program associated with this report set.

Action: Delete all incompatible programs defined for the concurrent program associated with

this report set before changing Incompatibilities Allowed to ’No’.

[APP–1604] Cannot find the segment for your report parameter

Cause: Flexfields cannot find the segment &SEGNAME for your report parameter in its

internal data structures.

Action: Contact your support representative.

[APP–1606] You must specify the printer before running a report.

Cause: There is no printer specified for this report/program

Action: Navigate to the Print Options zone and specify a printer. You may also specify the

printer in the program definition and/or as a profile option.

[APP–1608] Default values specific to report sets (Report Set level defaults) should not contain

:$FLEX$, :$PROFILES$, or :PARAMETER ”bind” references. Request set–level default values

with bind references are supported in report sets only when the parameter record is not modified

from its program–level definition. To proceed, either remove the bind reference from the default

value, or clear this record.

[APP–1610] Please enter a report group code that does not contain a space

Cause: You entered a report group code containing one or more spaces.

Action: Enter a report group code that does not contain any spaces.

[APP–1612] Cannot process report # &SEQUENCE

Cause: Standard Report Submission has encountered an error processing report #

&SEQUENCE. &PROGRAM has not completed yet.

Action: Contact your support representative.

[APP–1616] You cannot enter more than &NUMBER arguments

Cause: You exceeded the maximum number of arguments allowed for a program.

Action: Erase arguments so that you have no more than &NUMBER arguments defined for this

program.

[APP–1618] Column &COLUMN not found

Cause: The column &COLUMN could not be found.

Action: Check your report to make sure this column exists. Contact your support

representative.

[APP–1622] Token &TOKEN1 and value &VALUE1 is incompatible with token &TOKEN2 and

&VALUE2

Cause: The value &VALUE1 for token &TOKEN1 is inconsistent with value &VALUE2 for

token &TOKEN2.

Action: Contact your support representative. Additional information for support representative:

Check the combination for the two token values is correct. See API document for more

information.

[APP–1624] The token value &VALUE for token &TOKEN is inconsistent in the user exit:

&USER_EXIT

Cause: The specified value &VALUE for the token &TOKEN is either invalid or inconsistent

with the other tokens specified in the &USER_EXIT user exit.

Action: Contact your support representative. Additional information for support representative:

Check that the token values are correctly specified.

[APP–1626] Token &TOKEN is too long. Maximum length allowed is &LENGTH

Cause: The length of the token &TOKEN is too long. The maximum length allowed is

&LENGTH.

Action: Check that the token &TOKEN is limited to length &LENGTH.

[APP–1628] Cannot close file &FILENAME

Cause: Application Object Library encountered an error writing to the end of the file

&FILENAME and closing the file.

Action: Check that you have sufficient disk space on your system. Remove unnecessary files

to free disk space. Contact your system administrator to obtain more disk space.

[APP–1630] Cannot open file &FILENAME for &MODE

Cause: &ROUTINE encountered an error when attempting to open file &FILENAME for

&MODE.

Action: Verify that the filename is correct and that the environment variables controlling that

filename are correct.

Action: If the file is opened in read mode, check that the file exists. Check that you have

privileges to read the file in the file directory. Contact your system administrator to obtain read

privileges.

Action: If the file is opened in write or append mode, check that you have privileges to create

and write files in the file directory. Contact your system administrator to obtain create and write

privileges.

[APP–1632] Cannot open file &FILENAME for reading

Cause: [Routine] encountered an error when attempting to open file &FILENAME for reading.

Action: Verify that the filename is correct, the environment variables controlling that filename

are correct, and the file exists.

Action: Verify that protections on that file permit reading by this program.

[APP–1634] The log file &FILENAME does not exist or this program is restricted from reading it.

If the concurrent request has completed then please contact your system administrator.

[APP–1636] No report available for this concurrent process

Cause: There is no report available for this concurrent process. The report file &FILENAME

either does not exist or this program is restricted from reading it. In some cases, a concurrent

program may not be intended to produce a report file, and it may generate only a log file.

Action: Verify that the concurrent request has completed.

Action: Check the log file for this request. Verify that this request is intended to produce a

report file.

Action: Verify that protections on the file permit reading by this program.

Action: Ask your system administrator if the file has been deleted.

Action: Verify that the filename is correct by checking the APPLOUT and application

(app_TOP) environment variables for both the user and the Concurrent Manager.

Action: Check the log file for the concurrent manager that attempted to process this request.

Action: Check the log file for the internal concurrent manager.

[APP–1644] System error: &MESSAGE

Cause: Application Object Library encountered a system error: &MESSAGE.

Action: Take appropriate action for your operating system, or contact your system

administrator.

[APP–1646] Application Object Library has detected an internal error.

Cause: An argument representing an invalid address was passed to Application Object Library

routine [Routine].

Action: Contact your support representative.

[APP–1648] Invalid arguments to routine &ROUTINE

Cause: Invalid arguments were passed to routine &ROUTINE.

Action: Ensure the arguments are correct.

[APP–1654] Out of memory in routine &ROUTINE

Cause: &ROUTINE cannot allocate memory because system is out of memory.

Action: Contact your system administrator or support representative.

[APP–1660] Application Object Library cannot set environment variable &LOGICAL

Cause: The system is out of memory or a system error occurred.

Action: Contact your system administrator to check for available system memory.

[APP–1662] Cannot get the value of environment variable &LOGICAL

Cause: The named environment variable is undefined or the system is out of memory.

Action: Verify that the &LOGICAL variable is defined in your environment.

Action: Contact your system administrator to check for available system memory.

[APP–1680] Cannot find file &FILENAME

Cause: The specified system file could not be located or opened.

Action: Ask your system administrator to verify that the system file exists, and to check the

directory and file protections to be sure you have access to it.

[APP–1682] Cannot create canvas

Cause: The specified text display canvas could not be created. Canvas creation failures can

occur for many reasons, such as memory allocation failures, window system failures, etc.

Action: Consult the message listing to determine the cause of the failure. If necessary, contact

your support representative.

[APP–1696] This territory cannot be deleted because it is being referenced by the a Currency code.

Use the Currencies form to remove the reference and then try deleting.

[APP–1700] This sequence is used on an active assignment.

Cause: You are trying to deactivate a sequence that is used on an active assignment record.

Action: Deactivate the assignment record in the Assign Sequences screen first or leave the end

date null.

[APP–1702] An assignment does not exist for these parameters and one is mandatory.

Cause: The profile option Sequential Numbering is defined to have sequential numbering

always used. The current set of parameters does not have a sequence assigned.

Action: Go to the Assign Sequences screen and assign a sequence to the current set of

parameters.

[APP–1706] Error updating &COLUMN in &TABLE.

[APP–1710] The date range overlaps with other assignments for this flexfield.

Cause: There can only be one active assignment record for a given date. You have attempted

to enter dates that overlap with and existing assignment record for this Document Flexfield.

Action: Query up the existing assignments for this Document Flexfield and review their dates.

Then enter this new record so the date ranges do not overlap.

[APP–1714] You have entered a duplicate code for this Application.

Cause: This code is a duplicate for this application.

Action: Please update the code. Category Code must be unique within an Application.

[APP–1716] This sequence number is already in use. Enter a unique number.

Cause: Sequence number is unique within a sequence. You entered a sequence number that has

already been used for this sequence.

Action: Enter a sequence number that has not already been used for this sequence.

[APP–1718] The assigned sequence, &SEQUENCE is disabled.

Cause: The sequence assigned to this document flexfield has been disabled.

Action: Go to the Assign Sequences screen and disable the current assignment and enter a new

one using an active sequence.

[APP–1720] You cannot insert this sequence record because there are no accesses defined for it.

Navigate to the Access block, and enter one or more accesses. Then try to commit.

[APP–1726] No accesses have been defined for this sequence.

Cause: This sequence does not have any access records defined. Without access records this

sequence can never be used.

Action: Go to the Access zone of the Define Document Sequences form and enter an Oracle

user name for this sequence.

[APP–1728] An assignment does not exist for these parameters.

Cause: An attempt was made to find a sequence for this document flexfield. The profile option

says Sequential Numbering is only partially used.

Action: None is necessary unless you expected this document flexfield to have a sequence

defined.

[APP–1730] This Category cannot be deleted. It is already used on an Assignment.

Cause: This category code has already used in a sequence Assignment. It may not be deleted.

Action: You can update the name and description, or you can enter a new record with a

different code.

[APP–1734] No rows to process.

[APP–1736] A synonym does not exist for the sequence &SEQUENCE.

Cause: The sequence exists in the database, however a synonym within the current Oracle id

does not exist.

Action: Go to the Define Sequences screen and make an update. This will cause a concurrent

program to be submitted that will create the missing synonym.

[APP–1738] The sequence &SEQUENCE is type Manual. You must enter a value.

[APP–1740] An assignment with a null end date already exists.

Cause: An assignment record for this document flexfield already exists with a null end date.

Since a given document flexfield can only have one active assignment record for a given date, only

one assignment record for the flexfield can have a null end date.

Action: Either enter an end date or query the existing assignment record and enter an end date

for the existing record.

[APP–1742] This sequence is already associated with a different table.

Cause: A give sequence can only be assigned to documents that are all stored in the same table.

As such a sequence is associated with a transaction table. You attempted to assign this sequence to

a document that is stored in a different table from the other documents this sequence is assigned to.

Action: Choose a different sequence.

[APP–1744] Please register the unique identifier &TABLE with Application Object Library

Cause: The unique identifier &TABLE has not been registered with Application Object

Library. Application Object Library cannot generate a unique number.

Action: Register the unique identifier with Application Object Library.

[APP–1746] Usage is : FNDCPPUR <Username/Password> 0 Y [[keyword=]value ... ] Valid

keywords: ENTITY – Type of records to purge : REQUEST, MANAGER, ALL MODE – Purge

records based on : AGE, COUNT MODEVALUE – Age of records to be purged ( in number of days

) OR Number of records to retain The following are optional keywords: ORACLEUSER – Oracle

username USERNAME – Financials user name RESPAPPL – Responsibility Application short name

RESPNAME – Responsibility name PROGRAMAPPL – Program Application short name

PROGRAMNAME – Program name MANAGERAPPL – Manager Application short name

MANAGERNAME – Manager name Optional keywords and values can be used to purge records

that belong to a given responsibility, program, oracle account, requestor OR run by a given manager.

Usage is Purge request | manager age= count = ...

[APP–1750] &ROUTINE cannot redirect standard input

Cause: &ROUTINE encountered an error redirecting standard input for a child process.

Action: If standard input is redirected to a file, check that the file name is correct and valid on

your system. Check that the file exists. Check that you have privileges to read the file in the file

directory. Contact your system administrator to obtain read privileges.

Action: If standard input is redirected to a communication channel or a character string, check

that your system has enough resources to open a communication channel. Contact your system

administrator to obtain more resources.

Action: Exit Application Object Library and try again immediately, or later when your system

is not as busy. You may have reached a process limit for open channels and files.

[APP–1752] &ROUTINE cannot redirect standard output

Cause: &ROUTINE encountered an error redirecting standard output for a child process.

Action: If standard output is redirected to a file, check that the file name is correct and valid on

your system. Check that you have privileges to create and write the file in the file directory.

Contact your system administrator to obtain create and write privileges.

Action: If standard output is redirected to a communication channel or a character string, check

that your system has enough resources to open a communication channel. Contact your system

administrator to obtain more resources. Exit Application Object Library and try again immediately,

or later when your system is not as busy. You may have reached a process limit for open channels

and files.

[APP–1754] Cannot close standard input

Cause: Application Object Library has encountered system error &ERRNUM while closing

standard input.

Action: Consult your operating system error manual. Take appropriate action for that error

number, or contact your system administrator.

[APP–1756] &ROUTINE cannot close file handle

Cause: Application Object Library routine &ROUTINE has encountered a system error while

closing a duplicated file handle.

Action: Consult your operating system error manual. Take appropriate action for that error, or

contact your system administrator.

[APP–1758] System error closing pipe communications

Cause: &ROUTINE encountered a system error attempting to close one end of a

communications channel pipe.

Action: Take appropriate action for your operating system, or contact your system

administrator.

[APP–1760] System error &ERRNUM closing pipe &HANDLE

Cause: &ROUTINE encountered system error &ERRNUM attempting to close one end of a

communications channel pipe – descriptor &HANDLE.

Action: Take appropriate action for your operating system, or contact your system

administrator.

[APP–1762] &ROUTINE cannot create a new process

Cause: &ROUTINE encountered an error creating a new process. [Reason].

Action: Check that your system had enough resources to start a new process. Contact your

system administrator to obtain more resources.

Action: Try again immediately, or later when your system is not as busy.

[APP–1764] &ROUTINE cannot create pipe

Cause: &ROUTINE encountered a system error creating a pipe for inter–process

communications.

Action: Verify that your process has enough resources, including memory and file handles, or

contact your system administrator.

[APP–1766] &ROUTINE cannot duplicate file handle

Cause: &ROUTINE encountered system error &ERRNUM duplicating a file handle.

Action: Take appropriate action for your operating system, or contact your system

administrator.

[APP–1768] &ROUTINE cannot access environment

Cause: &ROUTINE encountered system error attempting to access the process’s environment

and arguments via DosGetEnv.

Action: Contact your system administrator.

[APP–1770] Child process &CHILDID &ACTION

Cause: A child process stopped or completed execution – in particular it &ACTION.

Action: If the program completed normally, no action is required.

Action: If the program completed with a status code indicating failure, consult your installation

guide for the meaning of that status code.

Action: If the program was terminated by a signal, consult your installation guide and

operating system manuals for the meaning of that signal. It could represent an internal error or a

termination request from another process.

Action: If the program was stopped by a signal, consult your installation guide and operating

system manuals for the procedure to restart that program.

[APP–1772] An event of unknown class &EVENTCLASS occurred.

Cause: &ROUTINE was asked to describe an event of unknown class &EVENTCLASS.

Action: Contact your support representative.

[APP–1774] Failure handling an event of class &EVENTCLASS; &OUTCOME

Cause: Application Object Library routine fdewev() received an event of class

&EVENTCLASS that it failed to handle. &OUTCOME.

Action: Contact your support representative.

[APP–1778] &ROUTINE cannot redirect standard input to a character string

Cause: usdsln() cannot set the value of logical name SYS$INPUT to redirect standard input.

&ROUTINE received a return code of failure.

Action: Contact your system administrator.

[APP–1780] You requested in invalid file type when calling routine &ROUTINE

Cause: You did not request a concurrent program file type of either AFWRT_LOG or

AFWRT_OUT.

Action: Ensure your concurrent program requests a file type of either AFWRT_LOG or

AFWRT_OUT when calling routine &ROUTINE.

Action: Check for any database error message using \ Help Error (Database).

[APP–1782] Invalid process ID &PID passed to routine &ROUTINE

Cause: &ROUTINE was passed &PID as an process id argument, but that argument is invalid

for your system.

Action: Contact your support representative.

[APP–1784] Cannot get process ID

Cause: Application Object Library encountered a system error getting process ID. &EXPLAIN

Action: Contact your system administrator.

[APP–1786] System error &ERRNUM occurred opening a file for standard input

Cause: usdspn received system error &ERRNUM while opening a file for standard input.

Action: Check that environment variables are set correctly. Check that the file exists. Check

that you have privileges to read the file in the file directory. Contact your system administrator to

obtain read privileges.

[APP–1788] System error &ERRNUM opening log file &FNAME

Cause: Application Object Library received system error &ERRNUM while opening log file

&FNAME for writing.

Action: Consult your operating system error manual. Take appropriate action for that error, or

contact your system administrator.

Action: Check that the file name is correct and valid on your system. Check that relevant

environment variables are set correctly.

Action: Check that you have privileges to create and write files in the log directory and on that

logfile. Contact your system administrator to obtain create and write privileges.

[APP–1792] &ROUTINE cannot write to pipe

Cause: &ROUTINE attempted to write data to another process using a pipe, but an error

occurred during the write.

Action: Check the other process for abrupt termination. Check that you have sufficient

resources for this operation.

[APP–1794] Program exited with status &STATUS

Cause: The program terminated, returning status code &STATUS.

Action: Check your installation manual for the meaning of this code on this operating system.

[APP–1796] Program killed by outside signal

Cause: Another process terminated this process by sending a signal.

Action: Run the program again, if desired.

[APP–1798] Program terminated by hard error

Cause: The program received a hard error from the operating system and was forced to

terminate.

Action: Check the logfile for the program. Try running it by hand if the problem recurs.

[APP–1800] Program terminated by trap

Cause: The program received a trap from the operating system and was forced to terminate.

Action: Check the logfile for the program. Try running it by hand if the problem recurs.

[APP–1804] &ROUTINE cannot reset standard output or standard error

Cause: &ROUTINE attempted to reset standard output and standard error to normal by

deleting the logical names SYS$OUTPUT and SYS$ERROR, but received a system error doing so.

Action: Contact your system administrator.

[APP–1806] The program received a signal while waiting for events

Cause: A signal was received while the program was waiting for events. This signal could

either represent an internal trap or an external signal.

Action: Check the program for parallel (asynchronous) logic. Check that such logic is not

causing a trap signal.

[APP–1808] Invalid arguments passed to usdsop()

Cause: The Application Object Library routine usdsop() was called with a null pointer rather

than program arguments.

Action: Ensure that the program enters the correct arguments for the child process.

[APP–1810] The routine spiini failed in routine &ROUTINE

Cause: The operating system dependent routine spiini failed when called by the routine

&ROUTINE.

Action: Review your error messages with \ Help Error for more information.

[APP–1814] Unknown USD signal: &SIGNUM

Cause: Application Object Library routine usdiop() was called to terminate a process, but the

second argument (ussig) was not a valid usdsig signal.

Action: Contact your support representative.

[APP–1816] Routine afuepp cannot free tokens

Cause: Routine afuepp encountered an error freeing a token structure.

Action: Contact your support representative.

[APP–1818] Routine afuepp subroutine failed

Cause: Routine afuepp encountered an error running a concurrent subroutine.

Action: Contact your support representative. Be sure to note the name of the subroutine that

failed, if displayed.

[APP–1820] Routine afuepp tokenizer failed

Cause: Routine afuepp encountered an error creating a token structure for a concurrent

subroutine.

Action: Contact your support representative.

[APP–1824] Your buffer allocation size must be 1

[APP–1832] Please enter a valid SQL statement

Cause: The SQL statement had unbalanced quote marks.

Action: Contact your support representative.

[APP–1834] Please enter a table name for your unique identifier

Cause: A NULL table name was specified for a unique identifier request to fduuid.

Action: Contact your support representative.

[APP–1836] You have requested a buffer size that exceeded the maximum limit

[APP–1842] Cannot get value for field

Cause: Application Object Library cannot get the value for a form field.

Action: Check that the field exists and is uniquely specified (often the same field name is used

in multiple blocks in a form).

[APP–1844] Incorrect password. Diagnostics not enabled

Cause: You entered an incorrect password. The diagnostics system cannot be activated until a

correct password is entered.

Action: Please enter the correct password. Contact your system administrator if you do not

know the correct password.

[APP–1854] The view name &VIEW_NAME is already in use.

[APP–1860] An error has occurred in workflow processing: &ERROR_MESSAGE The stack trace

of the error is: &ERROR_STACK

[APP–1872] &FORMAT is not a valid date format for FND SYSDATE.

Cause: A trigger specified an unrecognized format for FND SYSDATE.

Action: Correct the trigger code and regenerate the form.

[APP–1874] Please link in &OWNER program library

Cause: A user–exit was requested from a product library that is not included in this version of

Application Object Library.

Action: Contact your system administrator to verify that the specified product library is

included with Application Object Library. If necessary, contact your support representative for that

product to request its inclusion in Application Object Library.

[APP–1882] Unable to put date into field &FIELDNAME

Cause: You encountered an error when trying a write a value into the field &FIELDNAME.

Action: Ensure that the field exists and is writeable.

[APP–1896] Program error: The ”context” argument passed to FND_CLIENT_INFO.&ROUTINE is

too long. The ”context” that caused this error was ”&BAD_ARG”. Please inform your support

representative that: Your current ORG_ID (or similar system–generated ID) is too long.

[APP–1900] Attempt to process folder failed with error: &ERROR_MESSAGE

[APP–3000] Please enter bill–to address; otherwise clear Bill To Customer

[APP–3002] Component is not valid for the current product. Please enter another

[APP–3004] You cannot create new rows in this zone

[APP–3006] You cannot delete rows in this zone

[APP–3008] Please enter the name of the zone you want to see

[APP–3010] This value already exists. Please enter a different, unique value

[APP–3012] Please enter an end date that equals or follows the start date

[APP–3014] This function does not have any effect in this zone

[APP–3016] Enter a number greater than zero

[APP–3018] Please enter install address; otherwise clear Installed At Customer

[APP–3020] Invalid Order Type: &ORDER_TYPE

[APP–3022] Invalid Unit Of Measure Code: &UOM_CODE

[APP–3024] Please mark ”x” or ”X” to select the current row

[APP–3026] This zone contains only one record

[APP–3028] Enter a number greater than or equal to zero

[APP–3030] You cannot query in this zone

[APP–3032] Please requery next zone first

[APP–3034] Please enter a value for this field

[APP–3036] Please save your pending changes before proceeding

[APP–3038] Please enter ship–to address; otherwise clear Ship To Customer

[APP–3040] Enter a date that equals or follows the current date

[APP–3042] Please enter the value in the format HOURS:MINUTES

[APP–3044] You cannot update the value in this field

[APP–3046] Enter a high value that is greater than or equal to the low value

[APP–3048] Please enter a value between &LOW and &HIGH

[APP–3050] You cannot change this value to a non–set value because it has values assigned to it

[APP–3052] Please use flex to update values. Press FIND Key for Flex.

[APP–3054] Error encountered while calculating credit

[APP–3056] CP is cancelled so you cannot change its most recent status

[APP–3058] CP’s most recent status is No so you cannot cancel it

[APP–3060] CP is cancelled so you cannot change its status

[APP–3062] You cannot change the CP’s current status to a different status

[APP–3064] You cannot copy a CP that was created from order entry information

[APP–3066] You cannot copy a revision that was created from order entry information

[APP–3068] The end date of the CP has been cleared since you changed the status

[APP–3070] CP is not cancelled or terminated so you must clear end date

[APP–3072] Customer Product is Cancelled, so its end date must be less than or equal to the current

date.

[APP–3074] CP is terminated so it must have an end date

[APP–3076] You cannot define customer products manually in this form

Cause: You tried to enter information to define a new customer product. Oracle Service does

not allow manual definition of customer products when both of the following are true: 1) Oracle

Order Entry is also installed and Oracle Service is creating customer products automatically from

order entry information. 2) The Application Object Library profile option ”OCS:Manual CP

Definition Allowed” has been set to No.

Action: Verify that the profile option listed above is actually set to No. If the profile option is

set to No, use this form only to view and update existing customer products and to define usage

measurements and revisions for these customer products.

Action: If the profile option is set to Yes, contact Oracle Service support personnel and report

the problem.

[APP–3078] Another CP with the same original CP already has most recent status of Yes

Cause: You tried to change the current customer product’s most recent status to Yes when a

related customer product’s most recent status is already Yes.

Action: Leave the current customer product’s most recent status set to No. If you need to

change this status to Yes, first change the related customer product’s most recent status to No, then

return to this customer product and change its most recent status to Yes. A related customer

product is a customer product that has the same original customer product as your current customer

product.

[APP–3080] CP is not under Revision Control

[APP–3082] Customer product not present; you cannot navigate to Details zone

[APP–3084] You cannot terminate first revision; terminate the CP instead

[APP–3086] CP is Copy License parent of another CP so you cannot make it a Copy License child

[APP–3088] Copy License Reference is invalid, probably because target product is ineligible to be

copied.

[APP–3090] Current customer product is unconfirmed; you cannot order services

[APP–3092] Current customer product has no services. Please choose another option

[APP–3094] ATO products can not be split

[APP–3096] Split completed. Requery Customer Products zone to view results

[APP–3098] Customer product could not be split. Review CP information to determine why

[APP–3100] You must confirm the CP before you can split it

[APP–3102] Current customer product is not most recent so you cannot split

[APP–3104] Current customer product has quantity of 1 so it cannot be split

[APP–3106] Please enter a new, positive quantity that is less than the current quantity

[APP–3108] Current customer product is no longer active so it cannot be split

[APP–3110] Current customer product is not most recent so it cannot be split

[APP–3112] Current customer product reserved for update or upgrade so it cannot be split

[APP–3114] Current customer product has pending service order so it cannot be split

[APP–3115] Please enter all required information and save before leaving this window

[APP–3116] Current customer product reserved for order creation so you cannot split

[APP–3118] Current customer product reserved for order processing so you cannot split

[APP–3120] Current CP’s service reserved for termination so you cannot split

[APP–3122] Status change is not allowed for a cancelled type status

Cause: You tried to enter Yes in both the Cancelled and Status Change Allowed fields.

Action: Enter No in the Status Changed Allowed field.

Action: If you want to allow subsequent status changes to customer products that have or will

have the current status, make this status a non–cancelled–type status by entering No in the

Cancelled field.

[APP–3124] Current status reserved for special use, so you cannot update its dates

Cause: You tried to change the start date or end date of a customer product status that Oracle

Service automatically provides and uses for specific Oracle Order Entry transactions.

Action: Do not change the start date or end date of the current customer product status.

Action: Define additional customer product statuses with the availability dates you want.

[APP–3126] Current status reserved for special use, so you cannot update its name

Cause: You tried to change the name of a customer product status that Oracle Service

automatically provides and uses for specific Oracle Order Entry transactions.

Action: Do not change the name of the current customer product status.

Action: Define additional customer product statuses with the names you want.

[APP–3128] CP is cancelled so you cannot change it

[APP–3130] You cannot set a status to be both cancelled and terminated

Cause: You tried to enter Yes in both the Cancelled and Terminated fields.

Action: Enter No in either or both the Cancelled and Terminated fields.

[APP–3132] Current customer product has no system. Please choose another option

[APP–3134] Please enter in a Product Agreement for the CPs new customer.

Cause: You tried to transfer a product to a new customer without entering a Product Agreement.

Action: Enter a Product Agreement for the CP.

[APP–3136] Please enter a Bill To Address for the CP’s new customer

Cause: You tried to transfer a product to a new customer without entering a Bill To Address.

Action: Enter a Bill To Address for the CP.

[APP–3138] Please enter a Bill To Contact Name for the CP’s new customer.

Cause: You tried to transfer a product to a new customer without entering a Billing To Contact

Person.

Action: Enter a Bill To Contact Person for the CP.

[APP–3140] Please enter an Install Address for the CP’s new customer.

Cause: You tried to transfer a product to a new customer without entering an Install address.

Action: Enter an Install Address for the CP.

[APP–3142] You tried to update/insert CP data without entering a New Customer.

Cause: You tried to update/insert product information before entering a New Customer.

Action: Enter a New Customer

[APP–3144] Please enter a Ship To Address for the CP’s new customer.

Cause: You tried to transfer a product to a new customer without entering a Ship To Address.

Action: Enter a Ship To Address for the CP.

[APP–3146] Please enter a Ship To Contact Person for the CP’s new customer.

Cause: You tried to transfer a product to a new customer without entering a Ship To Contact

Person.

Action: Enter a Ship To Contact Person for the CP.

[APP–3148] Please enter a Technical Support Name for the CP’s new customer.

Cause: You tried to transfer a product to a new customer without entering a Technical support

person.

Action: Enter a Technical Support Person for the CP.

[APP–3150] Current customer product is unconfirmed; you cannot enter usage measurements

[APP–3152] You cannot enter date ranges that overlap for duplicate product measurements

Cause: The usage measurement you entered for the current customer product is the same as one

that already exists and the active dates of the two measurements overlap.

Action: Enter an end date for the existing usage measurement entry. Then, enter a start date for

the new entry that is greater than the end date of the first entry.

[APP–3154] Do you want this product’s Warranty Dates to be updated?

[APP–3156] Please enter the customer’s number; otherwise enter the customer’s name

[APP–3158] From Revision must be less than or equal to the To Revision

[APP–3160] To Revision must be greater than or equal to the From Revision

[APP–3162] From Serial Number must be less than or equal to the To Serial Number

[APP–3164] To Serial Number must be greater than or equal to the From Serial Number

[APP–3166] Current availability information already entered; enter unique information

[APP–3168] Enter the product, customer, date range, or product revision range to which the service

is to be limited.

[APP–3170] Current type automatically provided, so you cannot change name

[APP–3172] You must enter a status since you entered No for Revision Only

[APP–3174] Current usage automatically provided, so you cannot change name

[APP–3176] Required fields need to be entered before the transfer of this product

[APP–3178] Product already notified or reserved for notification and cannot be selected

[APP–3180] This record has been updated

[APP–3182] Update not allowed – service being used as an active base warranty

[APP–3184] You cannot classify the item as both a serviceable and service item

[APP–3186] The current item is not eligible to be serviced by the new service

[APP–3188] You cannot terminate a service whose end date follows the effective date

[APP–3190] You cannot change all selected services because their dates overlap

[APP–3192] The lead selected cannot be selected since it is reserved

[APP–3194] Failed to delete record(s) from &TABLE

[APP–3196] Please enter an effective through date that follows the effective date

[APP–3198] CP shipment/delivery pending so service cannot be ordered yet

[APP–3200] Shipped date plus shipping delay days is greater than the end date so service can not be

ordered.

[APP–3202] Product already has the current service for dates that will overlap

[APP–3204] The current service for this product overlaps another existing service.

[APP–3206] Please enter a duration period; otherwise clear the duration amount

[APP–3208] Please enter an end date or duration and period

[APP–3210] Please enter an ending date that follows the starting date

[APP–3212] You have an entered an invalid date or duration

[APP–3214] You have not selected anything so you cannot generate your order

[APP–3216] No order to cancel

[APP–3218] No row selected

[APP–3220] Current service has no start or end date.

[APP–3222] Order cancelled

[APP–3224] No order generated since you entered No in the Generate Order field

[APP–3226] Please enter the number of the order that you want to add lines to

[APP–3228] Order Import successfully created order &ORDER_NUM

[APP–3230] Order Import could not create your order

[APP–3232] Please enter a price list for your new order

[APP–3234] Product is not eligible to be serviced by your selected service

[APP–3236] Product needs to be selected

[APP–3238] Please enter a renewal duration or renew–through date

[APP–3240] New end date does not follow current end date so you cannot renew current service.

[APP–3242] There has been a lapse in service. The lapse in the service will be billed.

[APP–3244] Service reserved for a different transaction so it cannot be selected

[APP–3246] Service order not allowed because customer product’s status prohibits it

[APP–3248] Please enter a start date and/or starting delay

[APP–3250] You cannot adjust the current transaction’s credit amount

[APP–3252] Multiple transactions affected; adjust credit amount in next zone

[APP–3254] Please enter a credit amount between zero and total transaction amount

[APP–3256] Please enter a credit percent between 0 and 100

[APP–3258] Please enter a credit amount

[APP–3260] Effective date must be between service’s current start and end dates

[APP–3262] No service present so you cannot navigate to next zone

[APP–3264] This service has expired, so you cannot terminate it.

[APP–3266] Effective date invalid because it falls within an uninvoiced transaction

[APP–3268] Please commit your changes before performing this function

[APP–3270] Do you wish these changes to reflect in all Customer Products which make up this

System?

[APP–3272] Please enter a coterminate day; otherwise clear Coterminate Month

[APP–3274] Please enter a unique system name

Cause: You have entered a system name that has already been used for another system.

Action: Enter a different name for this system.

[APP–3276] Please enter install address; otherwise clear Installed At Customer

[APP–3278] Please enter invoice–to address; otherwise clear Invoice To Customer

[APP–3280] You must enter a name for this system

Cause: You did not specify the name for the new system.

Action: Enter a name for the new system.

Action: Contact your System Administrator to change the setting of the application profile

option ”CS: Auto–generate System Name” to Yes.

[APP–3282] Please enter a non–numeric name for your system

Cause: You attempted to change the name of the current system to a numeric name.

Action: Enter a unique, non–numeric name for the current system.

[APP–3284] Please enter ship–to address; otherwise clear Ship To Customer

[APP–3286] You cannot update system type while system usage measurements exist

Cause: You tried to change the system type for the current system while system usage

measurements based on the current system type still exist.

Action: Leave the system type unchanged for the current system while active usage

measurements of this system type exist.

Action: To change the system type of the current system, navigate to the Usage Measurements

zone and inactivate all existing system usage measurements that are based on the current system

type. Inactivate measurements by entering the date that you you longer want them active in the

End Date field. Then, return to the System zone and change the system type to the type you want.

[APP–3288] You cannot enter date ranges that overlap for duplicate system measurements.

Cause: You entered a usage measurement for this system that is the same as one that already

exists, for the same time.

Action: If you want to have the same usage measurement active for this system, be sure that the

active dates don’t overlap.

[APP–3290] Please enter a unique line number for this usage measurement.

Cause: You entered a line number for this usage measurement that has already been used for

this system.

Action: Change the line number to one that has not already been used.

[APP–3292] One or more contacts is no longer valid for your system’s new customer

Cause: Your system has one or more invalid contacts because these contacts are not related to

your system’s new owning customer.

Action: Change the invalid contact(s) to valid contact(s).

Action: Relate the customer associated with your invalid contact(s) to your system’s new

customer so that your contact(s) remain valid.

Action: Remove the invalid contact(s) from your system.

[APP–3294] Invalid date. Please re–enter.

[APP–3296] You have entered an invalid coterminate day or month

[APP–3298] One or more locations is no longer valid for your system’s new customer

Cause: Your system has one or more invalid locations because these locations are not related to

your system’s new owning customer.

Action: Change the invalid location(s) to valid location(s).

Action: Relate the customer associated with your invalid location(s) to your system’s new

customer so that your location(s) remain valid.

Action: Remove the invalid location(s) from your system.

[APP–3300] You cannot change the name of the current system

Cause: You tried to change the name of the current system.

Action: Do not change the name of the system.

Action: Contact your System Administrator to change the setting of the application profile

option ”Service: System Name Update Allowed” to Yes. Then, change the name of the system, as

desired.

[APP–3302] Parent system is invalid because it is child of another system

[APP–3304] Current system is already parent so it cannot have parent system

[APP–3306] System has been transfered. Requery before transfering it again

[APP–3308] Please transfer your system to a new customer first

[APP–3310] Enter a new customer or clear the system to cancel your transfer

[APP–3312] Contact no longer valid. Please validate or choose different contact

Cause: You tried to navigate past the Relate field while the current contact for your system is no

longer valid.

Action: Validate the contact by relating the contact’s customer to your system’s new customer.

Action: Choose a different, valid contact.

Action: Clear the contact altogether.

[APP–3314] Location no longer valid. Please validate or choose different location

Cause: You tried to navigate past the Relate field while the current location for your system is

no longer valid.

Action: Validate the location by relating the location’s customer to your system’s new customer.

Action: Choose a different, valid location.

Action: Clear the location altogether.

[APP–3316] System cannot be deleted. Possible causes: 1. It comprises of some Customer Products.

Terminate those Customer Products before deleting the System.

[APP–3501] This location already has a different Trading Partner value. Overwrite?

[APP–3502] No gaps allowed between keys.

[APP–3503] This Category Code is assigned to a transaction. You cannot delete it.

[APP–3504] *** OBSOLETE ***

[APP–3505] *** OBSOLETE ***

[APP–3506] *** OBSOLETE ***

[APP–3507] *** OBSOLETE ***

[APP–3508] *** OBSOLETE ***

[APP–3509] *** OBSOLETE ***

[APP–3510] *** OBSOLETE ***

[APP–3511] *** OBSOLETE ***

[APP–3512] *** OBSOLETE ***

[APP–4000] Oracle Alert was unable to substitute output values in your action. This occurred most

likely because your system is out of memory. Contact your system administrator.

[APP–4002] Oracle Alert was unable to substitute output values in your action because it could not

find the output variable &VALUE. Check that all outputs you reference in your action are the

correct enabled outputs for your alert.

[APP–4003] Syntax: ALUPCR <ORACLE ID> <Request ID> <OS Flag>

<Application Basepath> <Request ID>. Example: ALUPCR apps/apps 0 Y FND_TOP

12345

[APP–4004] Oracle Alert was passed an unknown action type. Contact your support representative.

[APP–4006] Oracle Alert was passed an invalid error type. Contact your support representative.

[APP–4007] Oracle Alert could not process a response because the alert message &VALUE has

already been closed to responses. Check that the response was within the number of follow–up days

defined for the alert message. Check that another response to the alert message had not already

been received.

[APP–4008] Oracle Alert did not perform the detail action because it is disabled

[APP–4008] Your alert references an invalid alert output: &VALUE. Check that your alert only

references outputs that exist.

[APP–4009] Oracle Alert was unable to perform the detail action because it was unable to find an

action at the action level that was last performed.

[APP–4010] Oracle Alert could not find an enabled alert definition for the parameters that were

passed to this program. Check that you have passed a valid set of arguments to Oracle Alert. Check

that your alert is enabled and active.

[APP–4010] Oracle Alert was unable to find the critical exception group for an exception in file

&FILE in routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4012] Oracle Alert cannot recognize a structure type. Contact your support representative.

[APP–4012] Oracle Alert was passed an unknown event alert type of &VALUE. Valid types are

”INSERT” and ”UPDATE”

[APP–4013] Oracle Alert was unable to initialize a mail posting in file &FILE in routine

&ROUTINE on line &LINE. This may most likely occur because your system is out of memory.

Contact your system administrator.

[APP–4014] Oracle Alert was unable to insert header information into a mail message in file &FILE

in routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4014] Your alert references a variable (&VALUE) that is too long. Alert cannot substitute a

value for &VALUE because it is cannot search for a valid output of this length. This restricts the

length of any word in an action to be less than the valid length for an output variable. Check that

your alert actions do not contain words with ampersands that exceed the valid length for an output.

[APP–4015] Oracle Alert was unable to insert a body into a mail message in file &FILE in routine

&ROUTINE on line &LINE. Contact your support representative.

[APP–4016] Oracle Alert did not successfully end a mail system posting session in file &FILE in

routine &ROUTINE on line &LINE. Check with your mail system administrator to see if the mail

system is working correctly.

[APP–4016] The alert &VALUE already exists on the destination database account

[APP–4018] Syntax: ALUTAD <ORACLE ID> <Request ID> <OS Flag>

<Source Application Name> <Source Alert Name> <Destination Application

Name> <Destination Alert Name> <Destination ORACLEID> Example: ALUTAD

applsys/fnd 0 Y ”Oracle Purchasing” ”Expense Reports On Hold” ”Oracle Purchasing” ”New

Expense Reports On Hold” applsys/fnd

[APP–4020] Oracle Alert was unable to execute ”&VALUE”. Check that this file exists and that its

read protection is set correctly.

[APP–4020] There are &VALUE action output(s) not copied

[APP–4021] Oracle Alert was unable to perform the command ”&VALUE”. Check that this is a

valid command on your operating system.

[APP–4022] Oracle Alert was unable to find the concurrent program specified for your action.

Check that the concurrent program that you specified for this action exists and is enabled.

[APP–4022] There are &VALUE action set input(s) not copied

[APP–4023] Oracle Alert was unable to successfully terminate response processing. Check that the

mail system is working properly.

[APP–4024] Oracle Alert was unable to read the file ”&VALUE”. Check that the file exists and that

its read protection is set correctly.

[APP–4024] There are &VALUE action set member(s) not copied

[APP–4026] There are &VALUE action set output(s) not copied

[APP–4028] Oracle Alert was unable to format your summary message because it does not contain a

summary template. Check that your summary message contains a summary template. You should

be careful not to remove the summary template, even if you choose not to display text within the

summary template.

[APP–4028] There are &VALUE group member(s) not copied

[APP–4029] Oracle Alert was unable to check for duplicates because you have defined too many

outputs for Oracle Alert to handle with duplicate suppression. This is a limitation that requires you

to reduce the number of outputs in your duplicate check configuration.

[APP–4030] Oracle Alert was unable to get the current mail account message in file &FILE in

routine &ROUTINE on line &LINE. Check with your mail system administrator that the mail

system is working correctly.

[APP–4030] There are &VALUE response action(s) not copied

[APP–4031] Oracle Alert was unable to open the mail account inbox in file &FILE in routine

&ROUTINE on line &LINE. Check with your mail system administrator that the mail system is

working.

[APP–4032] Oracle Alert was unable to log out of the mail system. Check with your mail system

administrator to see if the mail system and all appropriate network connections are working.

[APP–4032] There are &VALUE response variable(s) not copied

[APP–4033] Oracle Alert did not perform any actions because you have not definedany enabled

actions for your response set.

[APP–4034] Oracle Alert was unable to get values for your response variables. This is most likely

caused by the database going down or by running out of memory on your system. Check that the

database is operational.

[APP–4034] There are &VALUE response set action(s) not copied

[APP–4035] Oracle Alert was unable to get actions for your response set. Check that you have

defined enabled actions for your response set.

[APP–4036] Oracle Alert requires that your response actions are ordered sequentially starting with

sequence number 1. You cannot skip sequence numbers. Check that your response actions are

ordered sequentially.

[APP–4036] There are &VALUE valid response(s) not copied

[APP–4037] Oracle Alert was unable to initialize response processing either because it was unable

to connect to the mail system or because it was unable to resubmit the response processor. Check

that Oracle Alert is properly configured with the mail system. Check that the mail system password

registered with Oracle Alert is defined correctly.

[APP–4038] Invalid destination application name

[APP–4038] Oracle Alert was unable to get new mail from the inbox. Contact your support

representative.

[APP–4039] Oracle Alert was unable to get all of the mail messages from the inbox in file &FILE in

routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4040] Oracle Alert was unable to get a mail message from the inbox in file &FILE in routine

&ROUTINE on line &LINE. Contact your support representative.

[APP–4040] Oracle Alert was unable to get the current date and time. Contact your support

representative.

[APP–4041] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4042] Oracle Alert was unable to get the message text from Message Dictionary. Check if

the message exists or contact your support representative.

[APP–4042] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4043] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4044] Oracle Alert failed to retrieve the next value for the sequence &VALUE. Check that

either the sequence exists or the proper grants and synonyms exist for this sequence.

[APP–4044] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4045] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4046] Oracle Alert was unable to open the temporary file for the following reasons:

&VALUE. Check that you have the proper write permissions to create a temporary file.

[APP–4046] Oracle Alert was unable to retrieve information for one of your actions because of data

integrity problems. This error occurred in file &FILE in routine &ROUTINE in line &LINE.

Contact your support representative.

[APP–4047] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4048] Oracle Alert was unable to print the file &VALUE. Check that the file &VALUE

exists with the proper read permissions. Check that the printing executables portrait, qldprint,

qlwprint, and qa4print all exist with the proper execute permissions under the BIN directory for

Application Object Library.

[APP–4048] Oracle Alert was unable to process your response because of an invalid response set ID

in file &FILE in routine &ROUTINE on line &LINE. This most likely occurs because of a data

integrity problem. Contact your support representative.

[APP–4049] Oracle Alert was unable to process your response because it contains a null value for a

response variable ID in file &FILE in routine &ROUTINE on line &LINE. This error most likely

occurs because of data integrity problems.Contact your support representative.

[APP–4050] Oracle Alert was unable to process your response because it contains a null value for a

response variable type in file &FILE in routine &ROUTINE online &LINE. This error occurs most

likely because of a data integrity problem. Contact your support representative.

[APP–4050] Oracle Alert was unable to submit the concurrent program &VALUE. Contact your

support representative.

[APP–4051] Oracle Alert was unable to create a mail header structure in file &FILE in routine

&ROUTINE on line &LINE. This may most likely occur because your system is out of memory.

Contact your system administrator.

[APP–4052] Oracle Alert was unable to get the value for a profile option for the following reason:

&VALUE

[APP–4052] Oracle Alert was unable to update the table ALR_ACTION_SET_CHECKS in file

&FILE in routine &ROUTINE on line &LINE. Check that the table exists.

[APP–4053] Oracle Alert was unable to update the date last checked for your alert in file &FILE in

routine &ROUTINE on line &LINE. Check that the table is not locked.

[APP–4054] Oracle Alert was unable to initialize the concurrent program for the following reason:

&VALUE

[APP–4056] Oracle Alert was unable to resubmit the Periodic Alert Checker to the concurrent

manager in file &FILE in routine &ROUTINE on line &LINE. Check with your database

administrator.

[APP–4056] Retrieve action history data (output variables) failed.

[APP–4057] Oracle Alert was unable to purge history in file &FILE in routine &ROUTINE on line

&LINE. Check that all of the Oracle Alert history tables exist.

[APP–4058] Oracle Alert was unable to request periodic alert checks in file &FILE in routine

&ROUTINE on line &LINE. Check with your database administrator.

[APP–4058] Unable to lock ALR_ACTION_SET_INPUTS in SHARE UPDATE MODE. Contact

your database administrator.

[APP–4060] Oracle Alert was unable to purge outdated action history in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ACTION_HISTORY exists.

[APP–4060] Unable to lock ALR_ACTION_SET_OUTPUTS in SHARE UPDATE MODE.

Contact your database administrator.

[APP–4061] Oracle Alert was unable to purge outdated alert inputs in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ALERT_INPUTS exists.

[APP–4062] Unable to schedule &VALUE. Contact your system administrator.

[APP–4064] Unable to terminate &VALUE. Contact your system administrator.

[APP–4065] Oracle Alert was unable to connect to the ORACLE ID &VALUE. Check that this

ORACLE ID exists and that the password registered with this ORACLE ID is correct.

[APP–4066] Oracle Alert was unable to reconstruct history. Contact your support representative.

[APP–4068] Oracle Alert could not insert the alert check information into the table

ALR_ALERT_CHECKS in file &FILE in routine &ROUTINE on line &LINE. Check that the

table exists.

[APP–4068] You did not specify a valid Alert name.

[APP–4070] Oracle Alert was unable to update the success flag in ALR_ALERT_CHECKS or

ALR_ACTION_SET_CHECKS in file &FILE in routine &ROUTINE on line &LINE. Check that

both tables exist.

[APP–4070] You did not specify a valid Application Name.

[APP–4071] Oracle Alert was unable to insert history information into ALR_ACTION_HISTORY

in file &FILE in routine &ROUTINE on line &LINE. Check that the table exists.

[APP–4072] Oracle Alert was unable to build your exception history report. Contact your support

representative.

[APP–4072] Oracle Alert was unable to successfully check for duplicates and escalate actions in file

&FILE in routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4074] The folder &VALUE does not exist. Create the folder in the mail account

[APP–4074] This installation has already been defined. If you wish to modify it, please query the

existing row.

[APP–4075] Oracle Alert was unable to login to the mail system account. Check with your mail

system administrator to see if the mail system and all appropriate network connections are working.

Check that the mail account password registered with Oracle Alert is correct.

[APP–4076] Syntax: ALECTC <ORACLE ID> <Request ID> <OS Flag>

where <Mode> is ’I’ for an insert event and ’U’ for an update event. Example: ALECTC

apps/apps 0 Y APPS FND_DUAL 003.0000.001 ’U’ jatims

[APP–4076] You cannot delete this custom installation as there is one or more alerts registered for

this application. If you wish to delete this installation, you must first delete the alert definitions.

[APP–4077] Syntax: ALECDC <ORACLE ID> <Request ID> <OS Flag>

<Application ID> <Alert ID or Periodic Set ID> <Alert Type> where <Alert

Type> is ’A’ for an alert and ’S’ for a periodic set. Example: ALECDC apps/apps 0 Y 160 10001

[APP–4078] Oracle Alert was unable to interpret the message handle &VALUE in file &FILE in

routine &ROUTINE on line &LINE. Check that the message handle is in the proper format and has

not been altered.

[APP–4078] You cannot delete this default installation –– it has been created by AutoInstall. You

may only delete custom installations.

[APP–4080] Oracle Alert was unable to connect to the database. Contact your support

representative.

[APP–4080] Oracle Alert was unable to run your mail action. Check that the mail system is

working properly.

[APP–4081] Oracle Alert was unable to run your SQL action. Check that you have defined a valid

SQL command or that your SQL script exists.

[APP–4082] Oracle Alert was unable to get the value for the profile option &VALUE. Check that

the Oracle Alert profile option exists.

[APP–4082] Oracle Alert was unable to run your Operating System action. Check that you have

defined a valid operating system command or that your operating system executable file exists.

[APP–4083] Oracle Alert was unable to submit your concurrent program request action to the

concurrent manager. Check that you have defined an enabled concurrent program for your action.

[APP–4084] Oracle Alert was unable to find a response account

[APP–4084] Oracle Alert was unable to process your response because it was passed an unknown

action type in file &FILE in routine &ROUTINE on line &LINE. Contact your support

representative.

[APP–4085] Oracle Alert was unable to process your no response actions. Check that you have

properly defined your actions for the no response case.

[APP–4086] Oracle Alert was unable to find the end of your response message. Contact your

support representative.

[APP–4086] Your response message references an invalid response variable &VALUE. Check that

the response variable is properly defined for your response set.

[APP–4088] Oracle Alert cannot interpret the response variable in your response message because it

is not properly formatted. Check that all response variables are formatted in this manner:

RESPONSE_VARIABLE=”VALUE”. Be sure that the value is enclosed in double quotes.

[APP–4090] You cannot delete an action that is a member of a response set

[APP–4091] Oracle Alert was unable to free a mail header in file &FILE in routine &ROUTINE on

line &LINE. Contact your support representative.

[APP–4092] &PROGRAM is activated.

[APP–4092] Oracle Alert was unable to create the folder &VALUE in file &FILE in routine

&ROUTINE on line &LINE. Contact your mail system administrator.

[APP–4093] Oracle Alert was unable to move a mail message to the folder &VALUE in file &FILE

in routine &ROUTINE on line &LINE. Check that the folder exists.

[APP–4094] Oracle Alert was passed an unknown return code from the mail system in file &FILE

in routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4094] Submitted request &REQUEST_ID to deactivate the Internal Concurrent Manager.

[APP–4095] Invalid arguments were passed to routine &ROUTINE in file &FILE on line &LINE.

Contact your support representative.

[APP–4096] &PROGRAM is deactivated.

[APP–4098] The Internal Concurrent Manager is not active.

[APP–4100] SQL error number &NUM occurred

[APP–4102] Internal SQL error occurred.

[APP–4104] SQL error &ERROR_MESSAGE occurred while performing the following: &DESC

[APP–4106] Oracle Alert was unable to reconstruct history because of data integrity problems in file

&FILE in routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4106] Please correct the user–defined SQL statement for this alert.

[APP–4108] SQL error &ERROR_MESSAGE occurred while executing the user–defined SQL

statement for this alert

[APP–4110] Oracle Alert found an invalid number of bind variables in the SQL Statement:

&VALUE

[APP–4111] Oracle Alert was unable to purge outdated alert inputs in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ALERT_INPUTS exists.

[APP–4112] Oracle Alert was unable to interpret the inputs in the SQL Statement: &VALUE

[APP–4112] Oracle Alert was unable to purge outdated actions in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ACTIONS exists.

[APP–4113] Oracle Alert was unable to purge outdated output history in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_OUTPUT_HISTORY exists.

[APP–4114] Oracle Alert was unable to purge outdated action data history in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ACTION_DATA exists.

[APP–4114] Oracle Alert was unable to set inputs and outputs for your SQL statement. Check

previous errors to determine the cause of this problem.

[APP–4115] Oracle Alert was unable to purge outdated action set checks in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ACTION_SET_CHECKS exists.

[APP–4116] Oracle Alert was unable to purge outdated alert checks in file &FILE in routine

&ROUTINE on line &LINE. Check that the table ALR_ALERT_CHECKS exists.

[APP–4116] Oracle Alert was unable to remove comments from the SQL Statement: &VALUE.

[APP–4117] Oracle Alert was unable to purge outdated running alerts in file &FILE in routine

&ROUTINE on line &LINE. Contact your support representative.

[APP–4118] Oracle Alert found more than one output name for ”&VALUE”. Check that you have

chosen a different name for each output in your SQL Statement. Check that this output name does

not conflict with an existing response variable name for your alert.

[APP–4118] Oracle Alert was unable to purge outdated running alert checks in file &FILE in

routine &ROUTINE on line &LINE. Contact your support representative.

[APP–4120] An invalid number of outputs was found in the user–defined SQL Statement. The

number of outputs must match the number of items in the select clause. &VALUE

[APP–4122] Oracle Alert was unable to locate the FROM clause in the SQL statement: &VALUE

[APP–4123] Oracle Alert was unable to find the response set associated with youralert message

&VALUE in file &FILE in routine &ROUTINE on line &LINE. Check that the response set

associated with this message is enabled. Check that only one installation of Oracle Alert is sending

response messages to this mail system account.

[APP–4124] Oracle Alert was unable to deliver your message

[APP–4124] Oracle Alert was unable to locate the INTO clause in the SQL statement: &VALUE

[APP–4126] Oracle Alert was unable to close the temporary message file – &VALUE. Delete this

file manually.

[APP–4126] Oracle Alert was unable to locate the SELECT clause in the SQL Statement: &VALUE

[APP–4127] Oracle Alert was unable to output the message to an external file. Verify with your

system administrator that Oracle Alert has the write privilege to /tmp directory and /tmp is not full.

[APP–4128] Oracle Alert requires a SQL statement to define an alert. You must enter a SQL

statement when you define an alert.

[APP–4128] Oracle Alert was unable to delete the temporary message file – &VALUE.

[APP–4129] Oracle Alert was unable to delete the temporary message file (&VALUE). This may

indicate that Oracle Alert does not have delete privilege or file system error has occurred. You need

to delete the file manually.

[APP–4130] Oracle Alert was passed an unknown data type for the input &VALUE. Contact your

support representative.

[APP–4130] Oracle Alert was unable to retrieve the optional arguments for mail command. Verify

with your system administrator that MAIL_COMMAND_FLAGS profile option exists.

[APP–4131] Cannot send mail (system failed)

[APP–4132] Invalid or no mail system specified. Your system administrator either defined an

invalid mail system or did not define at all. Inform your system administrator about this problem.

[APP–4132] Oracle Alert was unable to allocate sufficient memory. Contact your system

administrator.

[APP–4133] Your system administrator should specify the mail system for you. Inform your system

administrator about this problem.

[APP–4134] Oracle Alert was unable to find a matching ID while transferring your alert definition.

This is most likely because of data integrity problems in your alert definition from your source

database account. Check that the alert definition on the destination database account is accurate.

[APP–4134] You need to specify one or more users to receive the message. The recipient name is

the name that the user used to log in. Oracle Alert does not verify whether the recipient names are

valid.

[APP–4135] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4136] Oracle Alert was unable to commit changes to the database. Contact your database

administrator.

[APP–4136] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4137] Oracle Alert was unable to retrieve information for an action because of data integrity

problems. This error occurred in file &FILE in routine &ROUTINE on line &LINE. Contact your

support representative.

[APP–4138] Oracle Alert was unable to establish a database connection. Contact your database

administrator.

[APP–4139] Syntax: ALUMMM <ORACLE ID> <Request ID> <OS Flag>

[APP–4140] Oracle Alert was passed an unknown datatype. Contact your support representative.

[APP–4142] Oracle Alert encountered the following UPI error: &VALUE

[APP–4144] Oracle Alert was passed an invalid variable type. Contact your support representative.

[APP–4146] An action with this name already exists for this alert.

[APP–4146] Oracle Alert was unable to get the value from field &VALUE. Check that the field

exists.

[APP–4147] Action is required.

[APP–4148] Oracle Alert was unable to set the value for field &VALUE. Check that the field

exists.

[APP–4150] Alert is required

[APP–4150] Oracle Alert found an invalid input name &VALUE. Input names must only contain

alphanumeric characters.

[APP–4151] Application is required

[APP–4152] One or more arguments are missing for routine.

[APP–4153] Days between checks is required for this type of periodic alert.

[APP–4154] This message was truncated by Oracle Alert because it exceeds maximum length of

64K

[APP–4154] Unable to check list name.

[APP–4155] Whether to check once daily is required for periodic alerts.

[APP–4156] You cannot clear this zone.

[APP–4157] You cannot clear this record.

[APP–4158] Copy action history failed.

[APP–4159] Copy application_id failed.

[APP–4160] Copy fnd_recid failed.

[APP–4161] Copy response set fields failed.

[APP–4162] Unable to copy Who information

[APP–4164] Day name is required for weekly periodic alerts.

[APP–4165] Day number must be greater than or equal to 1.

[APP–4166] Day number is required for monthly periodic alerts.

[APP–4167] Day number must be less than or equal to 31.

[APP–4168] Days to keep history must be greater than or equal to zero.

[APP–4173] You cannot delete an installation with alerts assigned to it

[APP–4178] You can only delete custom installations

[APP–4179] You cannot delete an action that is a member of an action set

[APP–4180] Delete record is not allowed in this zone.

[APP–4181] You cannot delete an action that is a member of a response set

[APP–4182] This message has already been deleted by another user

[APP–4184] You cannot disable a response set that has been assigned to a message.

[APP–4186] Duplicate installation found; not inserted.

[APP–4187] End date must be less than or equal to today’s date.

[APP–4191] This folder already exists. Please try again.

[APP–4192] Please enter the folder name

[APP–4193] Frequency type is required for periodic alerts.

[APP–4194] &VALUE function is not available.

[APP–4195] Unable to get unique id for alr_distribution_lists.

[APP–4198] Whether to check on insert is required for event alerts.

[APP–4200] Insert into alr_outputs failed.

[APP–4201] Insert not allowed in this zone.

[APP–4202] Inserting old version into alr_actions failed.

[APP–4203] This installation has already been defined for this alert.

[APP–4204] Days between checks must be greater than or equal to one.

[APP–4205] Start time for check must not be later than or equal to end time.

[APP–4206] End time for check must be later than start time.

[APP–4207] At last record.

[APP–4208] Could not load ALR_MAIL_FOLDERS.

[APP–4209] Unable to lock FND_COMPILED_FORM_INFORMATION.

[APP–4210] Field must be entered.

[APP–4211] Message number &NUM has been deleted by another user.

[APP–4212] This message is not marked for moving or deletion

[APP–4213] Message printed.

[APP–4216] Program name must be specified.

[APP–4217] Please specify at least one recipient in the ’To:’ field

[APP–4218] Unique id for alr_actions failed.

[APP–4221] Verification failed. Password not changed.

[APP–4223] Printer is required.

[APP–4224] Program Name is required.

[APP–4225] Query is not allowed.

[APP–4226] Querylong failed.

[APP–4227] Search Criteria retrieved no exceptions. Please adjust and try again...

[APP–4228] RAM_RMH failed.

[APP–4231] Copy new_recid failed.

[APP–4232] Start date must be less than or equal to today’s date.

[APP–4233] Start time is required for scheduled periodic alerts.

[APP–4234] Storelong failed.

[APP–4235] Table application name is required for event alerts.

[APP–4237] Time between checks is required for multiply executed periodic alerts.

[APP–4242] Unable to view log file. Request has been purged or archived.

[APP–4243] Update alr_actions failed.

[APP–4244] Whether to check on update is required for event alerts.

[APP–4245] Unable to update alr_distribution_lists.

[APP–4246] Update failed.

[APP–4247] Body update flag failed.

[APP–4248] Version step failed.

[APP–4249] Oracle Alert was unable to find the original message. The most likely reason is

because history for this alert has already been purged.

[APP–4251] Oracle Alert was unable to close your response in file &FILE in routine &ROUTINE

on line &LINE. The most likely cause for this error is a databaseproblem. Contact your DBA.

[APP–4252] Oracle Alert was unable to find your response set in file &FILE on line &LINE in

routine &ROUTINE. This is most likely caused by data integrity. Contact your system

administrator.

[APP–4253] Started &VALUE

[APP–4255] Submitted request to terminate &VALUE

[APP–4256] Terminated &VALUE

[APP–4269] Cannot submit a concurrent request to run Event Alert

[APP–4800] Run EDI Inbound Datafile Import Process

[APP–4801] Program Error: An error occurred at &PROGRESS_LEVEL. Process Aborted.

[APP–4802] Program Error: UTL_FILE. The file handle was invalid.

[APP–4803] Program Error: UTL_FILE. An unspecified error in PL/SQL.

[APP–4804] Program Error: UTL_FILE. An operating system error occurred during the write

operation.

[APP–4805] Program Error: UTL_FILE. An operating system error occurred during the read

operation.

[APP–4806] Program Error: UTL_FILE. The open_mode parameter in FOPEN was invalid.

[APP–4807] Program Error: UTL_FILE. The file could not be opened or operated on as requested.

[APP–4808] Program Error: UTL_FILE. File location or file name was invalid.

[APP–4809] Program Error: PL/SQL position not found for &COLUMN_NAME.

[APP–4810] Program Error: Sequence not found for &CONVERSION_ID, Sequence:

&SEQUENCE.

[APP–4811] Program Error: Conversion ID not found for &CONVERSION_ID.

[APP–4812] Program Error: Record number not found for &RECORD_NUM.

[APP–4813] Program Error: Address not found for Trading Partner &TRADING_PARTNER.

[APP–4814] Program Error: Location Code not found for Address &ADDRESS_ID.

[APP–4815] Program Error: Cross Reference Data not found for &DATA1 &DATA2 &DATA3

&DATA4 &DATA5

[APP–5000] WIP Supply Type is required when BOM Item Type is Standard

Cause:

You have not chosen a value for the WIP Supply Type attribute

Action:

Go to the Define Item form and choose a value for the WIP Supply Type attribute

[APP–5001] Error validating demand source header ID

An error has been encountered in validating the demand header ID for. Please check the demand

source header ID and/or demand source header segments.

[APP–5002] You may not use this selection when total compile value is zero

[APP–5003] Invalid source type

[APP–5003] You cannot use this form to delete a physical inventory

Cause:

You cannot use this form to delete a physical inventory.

Action:

Use the Purge Physical Inventory form.

[APP–5004] You cannot query in this zone. Use quickpick

[APP–5005] Cannot add the given information to the quantity tree

System could not add the quantity information to the specified quantity tree. Please check

additional messages for further explanation.

[APP–5005] Please use \ Row Delete to erase committed rows

[APP–5006] Please enter a valid category

[APP–5007] Cannot build dynamic SQL statement in routine &ROUTINE

Cause:

The routine you called had a failure in building dynamic SQL statements.

Action:

Please refer to additional messages to determine the actual cause.

[APP–5008] Required when vendor warranty is ”yes”

[APP–5009] New quantity tree could not be constructed with information

Cause:

Quantity tree recently created could not be constructed with information from the database.

Action:

Please check additional messages in the stack for further explanation.

[APP–5011] Cannot convert quantities to &UOM in routine &ROUTINE

Cause:

Calculated quantites could not be converted to the &UOM from the primary unit of measure for the

item.

Action:

Please check the correctness of the value for UOM parameter.

[APP–5012] Items under lot/serial control must have the same UOM across organizations

[APP–5013] Items to be transacted must have the same UOM classes across organizations

[APP–5013] New quantity tree could not be created

Cause:

A new quantity tree could not be created.

Action:

Please refer to additional messages for further explanation.

[APP–5015] Cannot delink the configuration item

Cause:

Your request to delink a configuration could not be completed. Following may be the reasons: (1) a

work order has already been opened or completed for any or all order line quantity; (2) any or all

quantity of configuration item has already been shipped to the customer; (3) models and options

associated with the configuration item may not exist in the demand table. Delinking a configuration

automatically enables the models and options which created the configuration item.

[APP–5017] Cannot find the quantity tree node

Cause:

System could not find the quantity tree node with the given set of item attributes. This error

occurred in &ROUTINE. Following may be the causes for this error: (1) quantity tree would not

have been built yet; (2) item attribute combinations may be invalid or nonexistent; (3) given set of

item attributes may have been created newly, and the tree information may be old.

[APP–5017] This count has been submitted for processing and cannot be updated

[APP–5019] Cannot query available quantity information from quantity tree

Cause:

System had some type of internal error which caused an error in querying up available quantity

information from the quantity tree.

Action:

To identify the root cause, please refer to additional error information.

[APP–5021] Backflush lot error

[APP–5021] Cannot update auto serial data for this &ENTITY

[APP–5022] Lot number records for this backflush transaction are missing, lot quantity is not

enough to fulfill this pull requirement, or lot number records require verification

[APP–5023] Backflush serial number error

[APP–5023] No SQL statement found to execute the query

[APP–5024] Serial number records for this backflush transaction are missing

[APP–5025] An application–related data corruption was found in database by &ROUTINE

Cause:

An application–related data corruption or inconsistency was found by &ROUTINE in file

&ERRFILE. This corruption was found by the SQL statement &SQLSTMT. Possible problems

are: (1) &ROUTINE was trying to update a row based on rowid, and the rowid may not exist; (2)

&ROUTINE was trying to delete a row based on rowid and the rowid may not exist.

Action:

Please call your Support representative for further help and explanation on this.

[APP–5025] You cannot update this field when you use average costing

[APP–5027] You must define an organization first

[APP–5028] Tag quantity cannot be less than zero

[APP–5029] ”To” locator must be entered for item &entity

[APP–5029] Cannot find the parent row while performing &ENTITY

Cause:

Your &ENTITY request could not be completed because the system could not find the parent row.

The function you called expects a parent (summary) demand row to exist before creating or

modifying a child record.

Action:

Please check your function call and parameters, and for additional help, contact your support

representative.

[APP–5030] ”To” subinventory is not in the restricted list for this item

Cause:

The item has a restricted list of subinventories. ”To” subinventory is not in this list.

Action:

Choose a subinventory from the list of restricted subinventories for the item

[APP–5031] Cannot reserve a quantity of (&QUANTITY) Cause

You had requested a quantity of (&QUANTITY) to be reserved and the system could not complete

your request. Currently, the system has an available quantity of (&AVAILQTY) to reserve in the

unit of measure &UOM. If you have asked to increase the existing reservation quantity, then

quantity to be reserved also includes the existing reservation quantity.

[APP–5031] You must select an asset or expense, tracked subinventory

[APP–5033] One of the demand/reservations requests in the group has failed

Cause:

One of the requests in the current group of demand/reservations requests has failed. You may have

requested that if any of the requests in the group were to fail, treat all the requests in the group as

failed.

Action:

Please review all your requests to identify the root cause of failure.

[APP–5033] This subinventory is not locator–controlled

[APP–5034] Bad option

[APP–5035] Error validating demand source header ID

Cause:

System has encountered an error while validating the demand header ID in &ROUTINE. Following

may be reasons: (1) you may have passed no demand source header ID nor any demand source

header flexfield segments. Please check the parameters have passed; (2) the demand header ID you

have passed does not exist against the demand source type you have specified. Please check the

valid list of values for Demand header ID and type; (3) setup for demand source type you have

specified may not allow dynamic creation of demand header ID’s or impose few restrictions which

may disallow creation of new Demand header ID’s.

Action:

Please check the additional error messages for further explanation and/or call your support

representative.

[APP–5035] Immediate processing is not available

[APP–5036] No MRP plan is available

[APP–5037] Message not found

[APP–5037] The action code provided for the routine &ROUTINE is invalid

Cause:

The action code that was passed to the routine &ROUTINE was an invalid one.

Action:

Please check the list of valid action codes and pass the action code again.

[APP–5038] Primary unit of measure and unit of issue must be in the same UOM class

[APP–5039] Set of books is different from Purchasing’s

The set of books used by the organization is different from the one used by Oracle Purchasing. To

create requisitions and purchase orders, these two have to be the same.

[APP–5039] You have specified invalid values for control options

Cause:

You have specified an invalid value for an item control option. Possibly, you have specified value

other than 1 or 2 for lot control or serial control options.

Action:

Please check your list of parameters and their values again.

[APP–5041] Invalid demand quantity (&QUANTITY) is given in the demand request

Cause:

Your demand request cannot be processed with the specified demand quantity (&QUANTITY).

Following may be the reasons: (1) a new demand row cannot be created with a quantity of zero; (2)

quantity to be removed from an existing demand row cannot exceed total demand or reservation

quantity; (3) quantity to be reserved cannot be lower than existing completed quantity for that

demand.

[APP–5042] Unprocessed material transaction(s) exist(s) for this period

[APP–5043] Invalid demand type

[APP–5043] Uncosted material transaction(s) exist(s) for this period

[APP–5044] Pending WIP costing transaction(s) exist(s) in this period

[APP–5045] Quantity on hand fails to satisfy reservation

[APP–5045] You cannot use an expense item in an in–transit transfer

[APP–5046] You cannot transfer from an expense item/sub to an asset item/sub

If either of your source subinventory or current item is expensed, you cannot transfer it to another

organization where both the item and subinventory are considered non–expensed (ie. asset).

[APP–5047] Requested item is not a reservable item

Cause:

You have requested to reserve an item which is not reservable.

Action:

Please check the item master attributes for the current item. An item can be made reservable only if

it is an inventory item. Please turn on the reservable attribute for the item and try again.

[APP–5049] More than one calendar found in a group ATP

[APP–5051] Locator restrict code requires at least one locator per subinventory

[APP–5051] Quantity to be transacted exceeds on–hand quantity

Cause:

The transaction quantity you have requested exceeds the on–hand quantity. Your system setup

indicates that negative inventory balances are not allowed.

Action:

Please review your transaction before trying again.

[APP–5052] Locators are already assigned to this subinventory

[APP–5053] Lot/serial numbers must be entered for item &entity

[APP–5053] Warning: Quantity will drive negative if the transaction is performed

Cause:

The transaction you have requested will cause the quantity on this location to be negative.

However, your setup indicates that negative quantities are allowed.

Action:

Please review the transaction and proceed further.

[APP–5054] Lot number length must be at least 3 greater than alpha prefix

[APP–5055] &entity1 are not required for this &entity2

[APP–5055] Unable to find ATP calendar for ATP calendar organization. Possible causes for this

error are (1) ATP calendar organization is not defined in group ATP or (2) BOM calendar is not

associated with ATP calendar organization.

[APP–5057] There are no auto–load serial values defined for this item or organization

[APP–5058] The count type you selected may only be used for min–max planned items

[APP–5059] Unable to find the corresponding calendar date for the requirement date

Make sure that calendar date is defined for the organization and that calendar extends long enough

into the future

[APP–5060] Inventory item is not defined in the destination organization

Cause:

Item must exist in organization where you are performing transaction

Action:

Use Define Item form to enable item in destination organization

[APP–5061] Cannot find an item master record for this item

[APP–5062] &entity1 is not permissible to transact. &entity2

[APP–5063] At last record

[APP–5063] No primary unit of measure could be found for the given item

Cause:

Primary Unit of Measure or Primary UOM code is not found in the item master for the given item.

Action:

Please verify the item information and define the primary unit of measure and primary UOM code

for the item.

[APP–5065] Item cost should be defined before you transact

Action:

Check if the cost–enabled flag is set correctly in the item master, and also check if the item cost is

defined in the costing module.

[APP–5066] Locator control is required

[APP–5067] A maximum of 30 characters may be specified for a serial number

[APP–5067] Parent model row not found to create configuration item demand

Cause:

Your request to create demand for the configuration item has failed, because the system could not

find the model item associated with the configuration item. Following may be the reasons: (1) the

RTO model line given may not exist or may not have any model item associated with it; (2) the

demand source header information may be incorrect; (3) BASE_ITEM_ID in item master for the

configuration may be null, pointing to a non–model item or pointing to an inconsistent model item

from the demand table; (4) either model item or the configuration item is not defined in the item

master for the current organization.

[APP–5069] Cannot create any more quantity trees

Cause:

The system cannot create any more quantity trees, as existing slots are now filled.

Action:

Please either free up all trees to obtain space or contact your support representative to recompile the

program with increase number of slots.

[APP–5071] Cannot find any information for the given organization

Cause:

No information can be found in inventory parameters table for the given organization.

Action:

Please check the organization ID or the existence of information about the organization.

[APP–5073] Unable to find requirement date

[APP–5075] Rule not found

[APP–5077] No subinventory record found for &SUBINV in organization &ORG

Cause:

The Subinventory record is missing in MTL_SECONDARY_INVENTORIES for the &SUBINV in

organization &ORG.

Action:

Define the subinventory using inventory setup forms.

[APP–5079] Request does not have adequate &ENTITY information

Cause:

Your demand management request does not have all necessary &ENTITY information to process.

You may not have provided supply source information for a function to link/unlink a supply source

to/from a demand source.

Action:

Please check your demand request elements and the action code

[APP–5080] One download on date &DATE is processing

[APP–5081] Quantity to be transacted exceeds available to transact. Please re–enter

Cause:

The transaction quantity you have requested exceeds the quantity available to transact. You may

not be able to perform the transaction under this situation.

Action:

Please check your on–hand balances and available to transact and try the transaction again.

[APP–5082] The original download process is missing

[APP–5083] Cannot find the root node for the quantity tree

Cause:

System cannot find the root node for the quantity tree with specified item parameters.

Action:

Please check the value of the parameters.

[APP–5083] Return to page 1 to erase, delete, insert or copy rows

[APP–5085] An error occurred while executing quickpick function

Cause:

Your request to list item details for available quantity [QUICKPICK] has failed with an error code

of &ERRORCODE.

Action:

Please refer to additional error messages and/or call your support representative.

[APP–5086] Cycle count control item ignored unless automatic scheduling enabled

[APP–5087] Cannot construct serial numbers from null starting serial number

[APP–5087] Your &ENTITY request failed with an error code &ERRORCODE

Cause:

Your &ENTITY request failed with an error code &ERRORCODE in &ROUTINE. Following may

be the reasons: (1) the action you have requested may be invalid; (2) the action you have requested

may be incompatible with some other action, such as demand–modify and reservation–modify

together in a single call; (3) demand and/or reservation action would have failed due to an error in

another routine called by the current function.

Action:

Please review additional messages regarding this

Action:

Please review the list of parameters and function calls to correct the problem

Action:

For additional help, contact your support representative.

[APP–5088] Please enter Service Level

Service level must be entered when method is mean absolute deviation (MAD)

[APP–5089] Please enter Safety Stock Percent

Safety stock percent must be entered if the method is user–defined percentage

[APP–5089] You must define a set of books for this organization

[APP–5090] Error from &FDFUNC: &ERROR

Cause:

An error occurred while creating the item flexfield view

Action:

Contact your support representative

[APP–5091] ”From” locator must be entered for item &entity

[APP–5091] Subinventory &SUBINV is not reservable

[APP–5092] ”From” subinventory is not in the restricted list for this item

Cause:

The item has a restricted list of subinventories. From subinventory is not in this list

Action:

Choose a subinventory from the list of restricted subinventories for the item

[APP–5093] Check the class breakpoint assignments. Every class has to have a breakpoint assigned

to it and it has to be greater than the breakpoint of the previous class.

[APP–5094] The input percent exceeds percent remaining

[APP–5095] You have specified an incorrect number of arguments for &TOKEN

[APP–5095] You should assign classes to your group first.

[APP–5097] You have to assign a compile to the group first.

[APP–5097] You must enter &ENTITY1

[APP–5098] You must enter a forecast

Forecast must be entered when reload safety stock is ”yes.”

[APP–5099] &entity1 is not valid

[APP–5099] You must have items in your compile.

[APP–5100] You must enter Method field

You must choose a forecast method before doing a reload safety stock

[APP–5101] Acceptable early days must be greater than zero

[APP–5101] You must enter a value for MRP percent

Cause:

You must enter MRP percent for safety stock type = ”MRP planned percent”

Action:

Enter an MRP percent greater than 50% and less than 100%

[APP–5102] Please enter a value for ”Reload Safety Stock”

Cause:

You have not entered a value for the field ”Reload Safety Stock”

Action:

You must enter ”Yes” or ”No” in the field ”Reload Safety Stock”

[APP–5103] Adjustment(s) processed

[APP–5105] An error occurred while processing adjustment transactions. Please contact your

system administrator or support representative for further assistance.

[APP–5105] Please enter a count name before navigating to the Items zone

[APP–5107] &ENTITY already exists

[APP–5108] Please enter search option(s) before going to next screen

[APP–5109] Approver is required

[APP–5109] You must select a physical inventory before continuing

[APP–5110] Please enter a subinventory before proceeding

[APP–5111] &ENTITY are required

[APP–5111] &ENTITY1 must equal &ENTITY2

[APP–5112] You have entered an effective date that already exists

[APP–5113] Assemble to Order cannot = ”No” because ATP Components = ”Yes”

[APP–5113] Unit conversion already exists for item. Please query

[APP–5114] Select different locators for the same subinventory

[APP–5115] You must assign all items of this type to the new set first

[APP–5117] Cannot update to ”yes”

Cause:

Cannot update to ”Yes” unless Assemble to Order is ”Yes” or Pick Components is ”Yes” or WIP

Supply Type is ”Phantom”

[APP–5117] Dynamic creation of locator is not allowed

[APP–5118] Employee not defined for the user

Cause:

The user is not associated with the employee

Action:

Please associate the employee name to the user in the Define Application User form

[APP–5119] Warning: This change could cause incorrect ATP results

Cause:

If any bills of material exist for this item that contain components with Check ATP = ”Yes,”

available to promise calculations for these components could be incorrect. Demand for these

components will not be captured when demand is placed for the parent item

Action:

Use View Bill of Material to see if any components are Check ATP = ”Yes”

[APP–5121] ATP Calendar too short.

Cause: One or more of the ATP rules used in this inquiry has an infinite supply time fence that

is beyond the last date for which the calendar has been built.

Action: Rebuild the calendar with a later End Date in the Define Workday Calendar form or

decrease the number of Infinite Supply Days for the ATP rule in the Define Available to Promise

Rule form

[APP–5121] Digit increments field is required

[APP–5122] Check ATP setting of ”Material and Resource” for a Standard Assembly could cause

incorrect ATP results.

Cause:

ATP will be calculated based on the material availability of the end assembly and the routing

resource requirements.

Action:

Either change ATP to ”Material Only”, or proceed anyway. Proceed anyway?

[APP–5123] Starting lot number prefix is required when Lot Control = Full lot control

[APP–5124] Verifying that subinventory is not in use...

[APP–5125] Duplicate conversions have been entered

[APP–5125] Starting serial number prefix is required

Cause:

Starting serial number prefix is required when Serial Number Control = Predefined serial numbers

[APP–5127] Reservable not allowed –– &SUBINV is a backflush subinventory

[APP–5127] You have entered duplicate organizations. Please erase

[APP–5128] You have specified the same category set more than once

Cause:

A particular category set can only be associated with any particular item once for each organization

Action:

Please clear any duplicate associations before committing

[APP–5129] &ROW_PROCESSED record(s) marked for background processing

[APP–5129] Duplicate tag number found during tag generation. Tag &TAG_NUM already exists!

Cause:

Tags may have already been generated

Action:

A purge of tags might be necessary to delete these tags. CAUTION! A tag purge will delete all

existing tags for this physical inventory

[APP–5130] Standard unit conversion already exists. Please query

[APP–5131] Subinventory information could not be found. Please contact your DBA or Oracle

Support.

[APP–5132] You do not have privileges to access this form

Cause:

You tried to access a form to which you do not have access privileges

Action:

Please contact your system administrator to request access.

[APP–5133] Item costs are different in this costing organization

Cause:

Changing the master organization will also change the costing organization. The item costs for the

new organization you selected are different from the item costs for the current costing organization.

[APP–5133] This item cannot have a base model

Cause:

An item cannot have a Base Model when the BOM Item Type is not ”Standard” or when Pick

Components is ”Yes”

[APP–5134] Costing organization is using a different set of books

Cause:

The current organization and the costing organization are not using the same set of books

[APP–5135] Base Model specified does not exist in &ORG You must assign the model to &ORG

first. Or, choose a Base Model that exists in all organizations to which you will be assigning this

item.

[APP–5135] Prior physical inventory snapshot failed or incomplete

Cause:

A physical inventory is defined for which a snapshot has not been completed. This could be the

result of an error, or because the snapshot program has not yet completed, or because a snapshot was

not requested.

Action:

The physical inventory may be queried up and a snapshot requested

[APP–5137] Model is not defined in all organizations where &ITEM is defined. When Base Model

is controlled at the Item–level, the model you choose will be the Base Model for this item in all

organizations where this item is defined.. Therefore, you must select a model that exists in all

organizations where this item exists. Or, assign the model to all organizations where this item exists

[APP–5138] Warning: &ENTITY1 is more than one month from today

[APP–5139] The date entered is not open in &ENTITY

[APP–5139] You may only define or query inter–class conversions for base units of measure

[APP–5140] Default locator is not defined in the destination organization

Action:

Either the transfer locator should be populated or a default locator should be setup for the

destination organization using the inventory forms

[APP–5141] BOM Allowed can be set to ”Yes” only if the item is an Inventory Item or a Support

Service Item under Vendor Warranty

[APP–5141] Default subinventory is not defined in the destination organization

Action:

Either the transfer subinventory should be populated or a default subinventory should be setup for

the destination organization using the inventory forms

[APP–5143] Cannot update because the item exists in a bill of material

[APP–5143] You cannot delete a status that is not pending

Cause:

The status rows which have already been processed cannot deleted. This restriction ensures that

item status history will be complete.

[APP–5145] Conversion &VALUE1 to &VALUE2 is already defined

[APP–5145] When BOM Item Type is ”Option Class” or ”Model,” then either Assemble to Order or

Pick Components must be ”Yes”

[APP–5146] Cannot update BOM Item Type

Cause:

The item exists in a bill of material.

[APP–5146] You must create an organization

[APP–5147] Build in WIP cannot be ”Yes”

Cause:

Build in WIP must be ”No” when either Inventory Item is ”No” or BOM Item Type is not

”Standard”

[APP–5148] Cannot change BOM Item Type to ”Product Family”

Cause:

Item exists in an open sales order

[APP–5148] Either ”from” or ”to” organization must be current organization

Action:

You must select the current organization as either the ”From” organization or the ”To” organization

[APP–5149] Inventory value entered greater than total ABC compile value

[APP–5149] Record not reserved for update or delete. Try again later

[APP–5150] Category flexfield Product Family structure definition is inconsistent with the System

Items flexfield System Items structure definition

Action: Please ensure identical segment mapping for the Product Family and System Items

structures.

[APP–5150] Please complete the line information

[APP–5151] You cannot approve an unentered count record

[APP–5152] Cannot delete product family item

Cause:

Category flexfield segments for the Product Family structure currently are not enabled or have not

been defined.

Action:

Please define Product Family structure of the Category flexfield to be identical to System Items

structure of the System Items flexfield.

[APP–5153] Adjustment transaction failed due to internal error

Cause:

Oracle error &ERROR occurred at &SQL in the CYCC_TRANSACT user exit while trying to

create the adjustment transaction.

Action:

Please contact your system administrator.

[APP–5153] You cannot change the serial number entry format while there are rows in the serial

number zone.

[APP–5154] Item must have BOM Allowed set to Yes when BOM Item Type is Product Family

[APP–5154] You cannot assign subinventories to organization–oriented cycle counts

Cause:

Your cycle count has Scope = Organization

Action:

If you want to cycle count items that exist in specific subinventories only, then you must ensure that

Scope = Subinventory

[APP–5155] Period Close may not continue.

[APP–5156] Product family item template not found

Cause:

A template specified in the ”INV: Product Family Item Template Name” profile option does not

exist or the profile option value has not been set.

Action:

Contact your system administrator to have the profile option assigned an existing template for

product family items.

[APP–5156] You may not enter a later date unless zone is cleared

[APP–5157] You cannot delete &ENTITY

[APP–5158] BOM Item Type for this item cannot be set to ”Product Family”

Cause:

The item is not an inventory item.

Action:

Set Inventory Item flag to ”Yes” then change BOM Item Type to ”Product Family”.

[APP–5158] Code has been disabled

[APP–5159] The status of this item indicates that it is not permissible to transact

Cause:

Value of attribute Transactable = ”No”

Action:

Go to Define Item form and set Transactable = ”Yes”

[APP–5159] This catalog is associated with an item

[APP–5160] Category flexfield segments for the Product Family structure are not enabled or have

not been defined. Proceed with commit?

[APP–5161] Deletion of a category is not allowed.

[APP–5161] You cannot delete rows with past start date

[APP–5163] You cannot delete this picking rule

Cause:

You cannot delete this picking rule because it is referenced by an item, an item template, or the

organization level parameters.

[APP–5165] Failed to get the next period ID

[APP–5166] Category set must be maintained at the item/organization level

[APP–5167] You cannot recount a count entry already marked for recount

[APP–5168] You cannot dynamically create tags for this physical inventory

Cause:

Allow Dynamic Tag Entry = ”No” for this physical inventory

Action:

Go to Define Physical Inventory form and set Allow Dynamic Tag = ”Yes”

[APP–5169] You cannot recount an unentered count record

[APP–5170] Cannot insert new records

[APP–5170] You cannot update &ENTITY

[APP–5171] Unable to update End Date.

[APP–5171] You cannot query in this &ENTITY

[APP–5172] You cannot recount a completed count record

[APP–5173] You cannot delete effective revisions

[APP–5174] You cannot recount a rejected count record

[APP–5175] Not allowed –– the following period’s status must be ’Future’

[APP–5176] You cannot reject a completed count record

[APP–5177] Start date has passed. You may not revert period to a future status.

[APP–5177] You cannot reject a count record that is already rejected

[APP–5178] You cannot specify a subinventory scope

Cause:

You cannot specify a subinventory scope for this physical inventory because you have already

specified that this physical inventory is for all subinventories.

Action:

Change the count all subinventories field to ”No” to specify a subinventory scope

[APP–5179] You cannot add new data in a query–only screen

[APP–5179] You must commit or clear pending changes in the units of measure window before

navigating to the conversions window.

[APP–5180] You cannot approve a completed count record

[APP–5181] You cannot approve a rejected count record

[APP–5183] You cannot commit on query forms

[APP–5184] You cannot create &ENTITY

[APP–5185] This category has been assigned to an item

[APP–5185] You cannot create requisitions –– employee not assigned to user ID

[APP–5187] This category has been set up as a category set default category

[APP–5188] You cannot delete data in a query–only screen

[APP–5189] This category has been assigned to a category set valid category list

[APP–5189] You cannot delete a tag –– void it instead

Action:

Go to Void Physical Inventory Tags form and void tags

[APP–5190] Cannot disable transaction source type

Cause:

Corresponding transaction type(s) must be disabled before disabling this transaction source type

Action:

Go to Define Transaction Type form and disable transaction type(s) corresponding to source type

[APP–5191] This category set is used in an Item Catalog Group.

[APP–5193] &ENTITY1 must be between &ENTITY2 and &ENTITY3

[APP–5193] This category set has valid categories assigned to it.

[APP–5195] You have already assigned a category to this item

[APP–5197] Warning: Changing organization will clear associated queries

[APP–5198] Invalid Check ATP value

Cause:

Check ATP cannot be set to ”Materials and Resources” or ”Resources Only” unless Assemble to

Order is set to ”Yes”.

[APP–5199] All remaining items must be assigned to the last class

[APP–5199] Cannot set Check ATP to ”None” for this item

Cause:

Bills of material exist for this item that contain components with Check ATP = ”Yes”.

[APP–5201] Available to promise code is required

[APP–5201] You may not enter a close date that is less than the start date

[APP–5202] Error occurred during attribute update

[APP–5203] Closing current accounting period...

[APP–5205] Leave this field blank if you want the system average cost

[APP–5205] There has been a database insert error, contact your dba or Oracle Support

[APP–5206] Adjustments still pending approval –– no adjustments posted

Cause:

There are still adjustments requiring approval in this physical inventory. Oracle Inventory has not

posted any adjustments for this physical inventory

Action:

Approve adjustments in Approve Physical Inventory Adjustments form

[APP–5207] All items have been assigned. Please commit your changes

[APP–5207] Please commit your changes and re–query the data

Cause:

Modifying this attribute will update related attributes in the database

Action:

You must commit and re–query the data in order to keep the database and form information

consistent

[APP–5208] Tag numbers may only be alphanumeric

[APP–5209] Concurrent request &REQUEST_ID submitted.

[APP–5210] &ENTITY are not required

[APP–5211] Transaction(s) request &REQUEST_ID has been sent to the concurrent manager

[APP–5212] You must assign items to all classes

[APP–5213] Lengths of tag numbers and digit increments must be consistent

[APP–5214] The item details you have specified do not follow reservation structure

Cause:

The item details you have specified for reservation violates the hierarchical structure defined by

Oracle Inventory at level &LEVEL. The hierarchical structure is item, revision, lot number,

subinventory and locator. You cannot specify lower level of details by missing some higher level

details. For example, if an item is under lot control and locator control, you cannot reserve an item

by just specifying the item, subinventory.

Action:

Please check the values passed to the reservation scheduler function

[APP–5215] This change may cause data inconsistencies

Cause:

The value of this attribute for an item could be different for different organizations even though it

would be specified as being maintained at the item level. In the course of regular item maintenance,

an attribute that is maintained at the item level propagates its value down to all the child

organizations in which the item is defined. However, this consistency is not enforced here when the

control level is switched to the item level.

Action:

You should first ensure that the attribute values are the same across organizations before making this

change

[APP–5216] Accounting rule is required for invoiceable items

[APP–5217] Item must have the same &ENTITY setting across organizations

[APP–5217] This change will cause data inconsistencies in WIP –– update not allowed

Setting the control level to Item level will cause the costing organization to be set to the item master

organization for all organizations under standard costing. This action will cause inconsistencies in

Oracle Work in Process if an organization does not point to itself for costs.

[APP–5219] Conversion rate must be entered

[APP–5220] Reservation transfer

[APP–5221] This category set is used in cost update history.

[APP–5223] An Oracle error occurred – ORA–&ERRNO

Cause: Oracle error ORA–&ERRNO occurred while accessing the database

[APP–5223] This category set is used in default costing for item overheads.

[APP–5225] Planning items may not be customer–ordered items

Cause:

Customer Ordered Item may not be ”yes” when BOM Item Type is ”Planning”

[APP–5227] Customer Orders Enabled cannot be ”Yes” unless Customer Ordered is ”Yes”

[APP–5229] &entity1 must be greater than or equal to &entity2

[APP–5231] This category set is defaulted for a functional area.

[APP–5233] Warning: Clearing organization will clear associated queries

[APP–5235] Cancel the transfer of transactions to General Ledger?

[APP–5235] Invalid locator control code (&LOCCODE) found

Cause:

The system has found invalid locator control code &LOCCODE for item ID &ITEMID under the

organization ID &ORGID. Possible causes are: (1) locator control code value may be out of bounds

of the defined set of values; (2) locator control may have been defined in a recursive fashion.

Action:

Please refer to the valid list of choices available to determine the locator control and correct the data

[APP–5237] Demand time fence days is required

Cause:

You must enter a value for Demand Time Fence Days when your choice for Demand Time Fence =

User–defined time fence

[APP–5238] Please navigate to the main information page

[APP–5239] Disable date must be greater than or equal to current date

[APP–5241] Disable Date must be greater or equal to Effective Date

[APP–5243] Download process failed

[APP–5244] Item status you have entered already exists

[APP–5245] &VALUE1 is already defined

[APP–5245] Processing the demand request will cause an invalid &ENTITY state

Cause:

Your demand request will cause an invalid &ENTITY state if processed. You may have asked for a

new demand row to be added or update an existing demand quantity for an item under a specific

disposition, for which there is already a row with inactive status. Specifically, if the item is a model

or an option and there exists a row for that item under same dispositions, but with inactive status.

[APP–5247] Error consuming open demand for your reservation request Cause

Your request to modify an existing/create a new reservation has failed, as the system encountered an

error while consuming the open demand for the same demand source line.

Action:

Please check the quantities and the state of open demand and/or reservation.

Action:

Please check additional error messages for further explanation on the cause of error and/or call your

support representative.

[APP–5247] You have entered a duplicate item. Please clear your changes

[APP–5249] Period already opened by another user

[APP–5251] The status entered for this effective date already exists

[APP–5253] Default receiving locator exists.

Cause:

A default receiving locator already exists for this item and subinventory.

[APP–5255] Default receiving subinventory exists.

Cause:

A default receiving subinventory already exists for this item.

[APP–5257] Duplicate Report Sequence Number, must be unique.

[APP–5259] Locators cannot be restricted with dynamic entry allowed

Cause:

Item is under Locator Control = Dynamic entry locator control

Action:

Locator control should be either ”Prespecified locator control” or ”No locator control”

[APP–5261] Effective date must be greater or equal to current date

[APP–5263] Token QUANTITY must be greater than zero

[APP–5265] Invalid date –– cannot enter past date for period end date

[APP–5265] Specify a prefix and beginning number for the item or organization

Action:

In the Define Organization Parameters form, if serial number generation is at the organization level,

you must specify the prefix and starting number in the Define Organization Parameters form. If

serial number generation is at the item level, you must specify the prefix and starting number for

that item in the Define Item form.

[APP–5266] No workdays defined for the current year

Action:

You must compile the calendar first.

[APP–5267] Cannot close this period –– Period’s ’To’ Date has not passed.

[APP–5269] Please enter an inventory item

[APP–5270] Quantity entered exceeds maximum available receipt quantity

Cause:

At any time, you can only a receive a maximum of RMA quantity – delivered quantity

[APP–5271] Please enter either an inventory item or a subinventory

[APP–5271] Receipt quantity must be positive

[APP–5273] Error creating quantity tree in &ROUTINE

Cause:

A fatal error has occurred in constructing the quantity tree while calling &ROUTINE.

Action:

Please refer to additional support messages for the cause and call your support representative

[APP–5274] A child of an average costing organization must also use average costing

[APP–5275] Expense Account is required when Inventory Asset Value is ”No” and Inventory Item is

”Yes”

[APP–5275] Transactions exist –– update not allowed

Cause:

If you are trying to update the master organization to one that is under average costing, you may

also be changing the child’s costing method to average costing. If transactions exist for this child,

you cannot change the costing method and therefore, you cannot change the master organization.

[APP–5276] &ENTITY should be an expense item for the given &ENTITY2 combinations

[APP–5277] Quantity on hand exists for this subinventory –– cannot change field

[APP–5277] You must enter field

[APP–5278] Quantity on hand exists for this subinventory –– account cannot be edited

[APP–5279] Date must be greater than or equal to current date

[APP–5280] Item is already associated with all organizations for this item master

All of the organizations belonging to this Item Master Organization are already associated with this

item.

[APP–5281] You can only delete rows that have a status of ’Error’

[APP–5283] One GL download is processing. Please close the period later

[APP–5285] &ENTITY1 must be greater than or equal to &ENTITY2

[APP–5286] Bucket–type must be periodic to enter seasonality indices

Bucket type must be periods to enter seasonality indices

[APP–5287] &ENTITY1 must be greater than &ENTITY2

[APP–5287] Transaction completed –– &NUMBER rows processed

[APP–5288] You must select a physical inventory before continuing

[APP–5289] ”From” serial number must be specified

[APP–5289] You must choose a physical inventory name

[APP–5290] Must open this period if any period afterward is open

[APP–5291] Primary issue subinventory is required before WIP supply locator

[APP–5291] Ranges cannot be built over different alphanumeric prefixes

[APP–5293] All serial numbers in a range must have the same number of digits

[APP–5294] Nettable code is required

[APP–5295] Serial number &token1 is currently used in the system

[APP–5297] Invalid transaction and serial control combination

[APP–5298] Item is manufactured, cannot be purchased

[APP–5299] On–hand quantity is negative for item ID &token choose a different update option

[APP–5301] Total lot transaction quantity does not match transaction quantity

[APP–5303] Lot transaction quantity cannot be zero

[APP–5303] You cannot commit until all items are assigned

[APP–5304] Item was not copied

[APP–5305] Transaction quantity cannot be zero

[APP–5307] &ENTITY1 must be a whole number greater than or equal to zero

[APP–5307] Bad safety stock code for item &item –– changed to non–MRP planned

The MTL_SYSTEMS_ITEMS row for item &item contained an invalid value in the column

MRP_SAFETY_STOCK_CODE. This problem should be reported as a bug. The data problem has

been corrected by your form and you should be able to continue.

[APP–5309] &ENTITY1 must be a whole number greater than or equal to 1

[APP–5311] &ENTITY1 must be a whole number greater than zero

[APP–5312] You must enter a source organization when Source Type is inventory

[APP–5313] &ENTITY must be an integer quantity in the primary UOM under serial control

You have entered a transaction quantity of &QTY1 which converts to &QTY2 in primary unit of

measure. Please re–enter the transaction quantity.

[APP–5314] Invoicing rule is required for invoiceable items

[APP–5315] Planning items may not be internally–ordered items

Internal Ordered item may not be ”Yes” when BOM Item Type = ”Planning”

[APP–5317] Internal Orders Enabled cannot be ”Yes” unless Internal Ordered is ”Yes”

[APP–5319] Internal error in user exit &UXIT

There is an internal error in user exit &UXIT. Please contact application support for resolution

[APP–5320] &ENTITY not valid. Please re–enter

[APP–5321] &entity1 is not valid. &entity2

[APP–5321] BOM Item Type must be ”Standard” when Internal Ordered Item is ”Yes”

[APP–5323] You must define an inter–organization shipping network for this Source organization

You must have an inter–organization shipping network defined between the current organization and

the Source Organization.

[APP–5325] You must choose a Source Subinventory that is non–nettable For intra–organization

replenishment of an MRP planned item, you must choose a non–nettable Source Subinventory.

[APP–5326] Value adjustment not allowed for item with no onhand quantities

[APP–5327] Lot number is not unique across items

[APP–5327] Subinventory is not reservable. Choose another

[APP–5328] Subinventory not defined for item. Please define or change restriction code

[APP–5329] Transaction date cannot be a future date

[APP–5331] Error launching tag generation concurrent process

[APP–5331] Invalid action code to the routine &ROUTINE

An invalid action was requested to the &ROUTINE. Please check the call parameters to the

&ROUTINE.

[APP–5333] Invalid conversion rate between &VALUE1 and &VALUE2

The error is probably caused by a division by zero.

[APP–5334] You cannot commit until attributes have been queried

[APP–5335] Interclass conversion between &VALUE1 and &VALUE2 is not defined

Use Define Interclass Conversions form to define interclass conversions

[APP–5335] Invalid transfer subinventory

[APP–5336] Transfer subinventory is not valid for the given transfer organization

[APP–5337] Invalid transaction source segments

[APP–5337] Item not found. Please re–enter

[APP–5338] The transaction source segments are invalid. Please re–enter

[APP–5339] Invalid transaction source type

[APP–5339] Please enter a period start date as defined by your manufacturing calendar

[APP–5340] The entered source type ID is either invalid or not supported by the open interface

[APP–5341] Invalid subinventory

[APP–5342] Subinventory code is either not entered or not valid for the given organization

[APP–5343] Invalid transaction date

[APP–5343] UOM conversion between &VALUE1 and &VALUE2 is not defined

Action:

Use Define Unit of Measure Conversions form to define conversions

[APP–5345] Invalid transaction UOM

[APP–5345] Please enter a week start date as defined by your manufacturing calendar

[APP–5347] Please enter a valid work day as defined by your manufacturing calendar

[APP–5347] Transaction UOM is invalid for the given item and organization combinations

[APP–5348] Invalid transfer locator

[APP–5349] Invoice enabled cannot be ”yes” unless item is invoiceable

Cause:

You cannot set Invoice enabled = ”Yes” unless you set Invoiceable Item = ”Yes”

[APP–5349] The Transfer Locator segments are invalid for the given transfer subinventory transfer

organization combination

[APP–5350] Invalid transfer organization

[APP–5351] Item not found. Please re–enter

[APP–5351] Transfer organization is either missing, invalid, or not setup in the interorganization

shipping network

[APP–5352] Invalid item segments

[APP–5353] The entered item segments are invalid or not found

[APP–5353] You have items assigned to the existing flex structure

[APP–5354] Invalid locator segments

[APP–5355] Change rejected –– default category set/item attribute control level mismatch

Cause:

You cannot change the maintenance level to Item for a Category Set that is a Default Category Set if

the controlling attributes are maintained at the item/organization level

Action:

Use Define Default Category Sets to see which functional areas your Category set is attached to.

Use the following table to see which attributes to change maintenance level for in the Define Item

Attributes form. Functional Area Item Attribute ––––––––––––––– ––––––––––––––––––––––

Inventory Inventory Item Purchasing Purchasing Item Planning MRP Planning Method Service

Service Item Cost Costing Enabled Engineering Engineering Item Order Entry Customer Ordered

Item

[APP–5355] The Locator segments are invalid for the given subinventory, organization combination

[APP–5357] For this transaction row either the lot records are missing or the lot quantity does not

match the transaction quantity

[APP–5357] Warning: Altering the category set maintenance level may corrupt your data

[APP–5359] Item is not under serial number control

[APP–5360] Invalid organization

[APP–5361] &ENTITY1 must be less than or equal to &ENTITY2

[APP–5361] Organization ID is either blank or invalid. Please re–enter

[APP–5363] Invalid transaction source

[APP–5363] Locator selected has already been assigned to this item and subinventory

[APP–5364] Transaction source is either invalid or blank for this WIP transaction

[APP–5365] Can’t be ”dynamic” when locators are restricted

[APP–5365] Invalid distribution account segments

[APP–5366] The distribution account segments are invalid. Please re–enter

[APP–5367] Invalid item

[APP–5367] Locator is disabled or defined for another subinventory

[APP–5368] Engineering items are not allowed

[APP–5369] Locators cannot be restricted if subinventories are not restricted

[APP–5370] Cannot update when Internal Ordered Item = ”Yes”

[APP–5371] Locator is not valid for subinventory

[APP–5372] Transaction processor error

[APP–5373] Failed to generate lot number automatically. Please check lot defaulting controls.

[APP–5374] Demand–relieve error

[APP–5375] Oracle error

[APP–5375] There has been a database error in cleaning up lot numbers

[APP–5376] This item cannot be built because build in WIP = ”No”

The Make or Buy attribute may not be ”Make” unless the Build in WIP attribute is ”Yes”

[APP–5377] Only purchasable items may be bought

Make or Buy cannot be ”Buy” unless the Purchasable attribute is ”Yes”

[APP–5377] There has been a database insert error, please contact your dba or Oracle Support

[APP–5379] Category must be entered

[APP–5379] Lot number length must be greater than or equal to alpha prefix and less than or equal

to 30.

[APP–5381] Lot numbers exist that have been used for different items Lot uniqueness will be

violated – update not allowed

[APP–5381] Unit of measure conversions do not exist for this item

[APP–5383] No dynamic locators in an issue if negative on–hand balances are not allowed

[APP–5383] Warning: This master does not contain all the items defined in the child

[APP–5385] Maximum quantity must be greater than or equal to minimum quantity

[APP–5386] No valid item–revision combination exists in the destination organization

[APP–5387] Maximum order quantity must be a multiple of the fixed lot multiple

[APP–5388] Could not set new organization value

[APP–5389] Minimum quantity must be less than maximum quantity

[APP–5390] No transactions to commit

[APP–5391] Item is not an assembly

[APP–5391] The minimum min–max quantity must not exceed the maximum min–max quantity

[APP–5393] Item exists in another master organization –– catalog groups must match

Cause:

This item has already been created in another master organization. Oracle Inventory ensures that

the Item Catalog Group for an item is consistent across organizations. The ICG currently specified

is not the same as the ICG of the existing item

Action:

Please change the ICG

[APP–5393] Option only enterable when in purchasing validation organization

[APP–5394] &ENTITY is not under lot or serial number control

[APP–5395] Item exists in another master organization –– UOM’s must be in the same class

Cause:

This item has already been created in another master organization. Oracle Inventory ensures that

the primary unit of measure for an Item belongs to the same unit of measure class across master

organizations. The primary unit of measure currently specified does not belong to the unit of

measure class of the existing item.

Action:

Please select a new primary unit of measure

[APP–5395] Not valid for item

[APP–5397] Average Cost has not been initialized for this item

[APP–5397] Item is defined in another master organization. Please clear your changes

Cause:

The same item has just been inserted into another master organization with a different inventory

item ID. Oracle Inventory ensures that the same item will have the same unique identifier across

organizations. In this case, the duplicate item was inserted during the small window of time

between the integrity check and commit time. This item cannot be inserted without causing severe

data integrity problems

Action:

Please clear your changes

[APP–5398] You must select statistical forecast method to add seasonality indices

[APP–5399] There are required descriptive element values that are missing

The Catalog Complete status for an item cannot be Yes until all the required descriptive elements

values have been specified. If you have specified all the required descriptive element values, the

form may not recognize this until you have committed your changes since the form checks the

database to determine which descriptive elements are required and which ones have values

specified.

[APP–5401] Pick Components must be ”Yes” when Ship Model Complete is ”Yes”

[APP–5401] Subinventory field is mandatory. Please enter

[APP–5403] Item cannot have pick components and be MRP– or MPS– or DRP– planned. Item

cannot have Pick Components = ”Yes” if MRP Planning Method is not ’Not Planned’

[APP–5405] This item cannot be OE–transactable

An item may not have OE Transactable = ”Yes” unless Reservation Control = ”Reservable” and

Calculate ATP = ”Yes”

[APP–5405] You must have at least one approval tolerance specified

Cause:

When approval is required for out of tolerance adjustments, at least one tolerance must be specified.

[APP–5407] Quantity will drive inventory negative

[APP–5408] Starting serial number is required when serial number control is ”Predefined serial

numbers”

[APP–5409] To serial number must be after from serial number

[APP–5410] Failed to fetch status details

Update of the function controlling attribute failed because the relevant status and status attribute

value information could not be found.

[APP–5411] Changing conversions that have been used in transactions may cause severe data

corruption. Please make certain that this conversion has not been used before accepting changes.

[APP–5413] You can’t delete this ABC Class. It is used either in an ABC Group or as a Cycle Count

Class.

[APP–5415] You cannot delete &ENTITY that is in use

[APP–5417] &ENTITY is not defined

[APP–5419] Requested serial quantity &token exceeds possible range of serial numbers

[APP–5419] You cannot create additional &ENTITY

[APP–5421] ATP Components cannot = ”Yes” when Pick Components = ”No,” Assemble to Order =

”No,” and WIP Supply Type is not ”Phantom”

[APP–5421] Service level must be greater than or equal to 0.5 and less than 1.0

[APP–5423] You may not define intra–class conversions for base units. Please select a non base

unit of measure before attempting to define or query intra–class item–specific conversions.

[APP–5425] No calendar for this organization: Create a calendar via the Define Workday Calendar

form and link that calendar to your organization via the Define Organization Parameters form.

[APP–5427] No changes to commit

[APP–5429] Cannot delete/update default category if Use Valid Category List is Yes.

[APP–5429] Cannot inspect items being received into stores

[APP–5430] Scheduled return quantity has already been received

[APP–5431] Please select an item with non–MRP planned safety stock

[APP–5431] You can not define conversions for inactive units of measure or classes with inactive

base units. Requery the zone to view existing conversions, or select a non–disabled unit of measure

for which to define conversions.

[APP–5432] Sequence number exceeds number of items in ABC compile

[APP–5433] Dynamic tag entry is not enabled for this physical inventory

[APP–5435] &ENTITY is a future date

The date you have entered cannot be a date in the future. Please enter a past date or today’s date.

[APP–5437] Item not defined under the organization

[APP–5439] The locator you selected does not exist within this subinventory

[APP–5439] You must enter a value for &ENTITY

You must enter a value for &ENTITY

[APP–5440] Reservable type is required

[APP–5441] Form is unable to find master organization information

Navigate to the Define Organization Parameters form and either associate your organization with a

Master Organization or make your organization a Master Organization by associating it with itself.

If Oracle Inventory is not installed, verify that the MFG_ORGANIZATION_ID profile is set.

[APP–5441] Required when response time period is specified

[APP–5442] Please enter a value greater than or equal to &MINVALUE and less than

&MAXVALUE

[APP–5443] Negative balances not allowed

[APP–5443] Receiving parameters must be defined before items

[APP–5445] Cannot close this period –– No open period exists for this organization

[APP–5447] No open period found for date entered

[APP–5449] &ENTITY cannot be a past date

The date you have entered cannot be a date in the past. Please enter a future date or today’s date

[APP–5451] &ENTITY is in the past open period

The date you have entered is in the past open period

[APP–5453] You cannot delete a status which is pending assignment

[APP–5455] You cannot delete a status which has item assignments

[APP–5456] Quantity must be entered for item &entity

[APP–5457] Quantity does not convert to integer number of serial numbers. Please re–enter

[APP–5457] You cannot delete a status which has item template assignments

[APP–5458] Please query first to view information

[APP–5459] Please query an existing record first

[APP–5459] You cannot delete a Transaction Source Type associated to a Transaction Type or

Material Reservation

[APP–5460] The character ”’” is not allowed. Please re–enter

[APP–5461] Digit increments must be numerical

[APP–5461] Previous accounting period is not opened yet

[APP–5462] Only one primary subinventory allowed per item

[APP–5463] Only one primary locator allowed per subinventory

[APP–5463] Warning: Sales order line processing may be affected At least one open sales order

line exists which has a different value for &ATTRIBUTE than the value you are trying to enter. If

such an order line has not passed all of the following cycle actions or processes, you are likely to

encounter problems processing the order line(s):* Order Scheduling* Demand Interface* Pick

Release* Ship Confirmation* Update Shipping* Inventory Interface

[APP–5464] Sequence for inventory value must be greater than prior class end sequence

[APP–5465] Error while finding the difference between two Oracle numbers

[APP–5465] Sequence number must be greater than last sequence number of prior class

[APP–5466] Value must be greater than prior class value

[APP–5467] The minimum order quantity must not exceed the maximum order quantity

[APP–5468] &PROCESS completed

[APP–5469] You can update records only related to the previously selected item

[APP–5471] On–hand quantity exists for this locator –– subinventory cannot be changed

[APP–5471] This organization is a master for other organizations –– update not allowed

[APP–5473] The physical inventory you selected does not require approvals

[APP–5473] Warning: Another organization has specified that serial numbers be unique across

organizations

[APP–5475] This adjustment has been posted. No changes may be made

[APP–5475] Updatable only when Purchased Item is ”Yes”

[APP–5477] Outside Processing Unit Type is required for Outside Processing items

If Outside Processing = ”Yes” then you must choose a value for Outside Processing Unit Type

[APP–5477] Purchasing information only enterable when item is purchased

[APP–5478] Option only enterable when Oracle Purchasing is available

[APP–5479] Item is purchased –– cannot be manufactured

[APP–5479] Please commit or clear your changes first

[APP–5480] You are over–receiving item &token

[APP–5481] Partial values must be entered

[APP–5481] Pending changes to the status exist at the item/org level –– cannot change

You cannot change the control level of the Item Status to Item Level when there are pending

changes to the Item Status at the Item/Organization level. Oracle Inventory ensures that item

attributes that are controlled at the Item level have consistent values across organizations. However,

pending changes at the Item/Organization level would violate this constraint. These pending

changes must be deleted from the Pending Status form (or from the mtl_pending_item_status table)

[APP–5483] Period Close cancelled

[APP–5485] Period Close failed

[APP–5486] Further information not yet available –– period not closed

[APP–5487] Order of period end dates must be preserved

[APP–5488] Material parameters must be defined before defining items

[APP–5489] Item cannot have Pick Components = ”Yes” when Assemble to Order = ”Yes” or BOM

Item Type = ”Planning” or MRP Planning Method is other than ”Not Planned”

[APP–5490] &MINMAX order quantity must be a multiple of the fixed lot multiple

[APP–5491] Pick Components cannot = ”No” because ATP Components = ”Yes”

[APP–5493] Inventory parameters must be defined for &ENTITY

[APP–5493] Picking rule already used

[APP–5495] Planning time fence days is required

Planning Time Fence Days is required when the Planning Time Fence is ”User–Defined”

[APP–5496] Release Time Fence Days is required

Cause:

Release Time Fence Days is required when Release Time Fence is ”User–Defined”

[APP–5497] An error has occurred while building RMA information for querying. Please check

your RMA number.

[APP–5497] Subinventory must be entered

[APP–5498] You cannot enter unscheduled counts for this header

[APP–5499] An item may not be purchasable unless it is a purchased item An item may not have

Purchasable set to ”Yes” unless Purchased is also set to ”Yes”

[APP–5499] This physical inventory has generated adjustments and cannot be updated

[APP–5500] Zone Erase is not allowed in this zone

[APP–5501] &PROCESS failed

[APP–5501] &VALUE number already used

[APP–5503] Purge tags only (alternatively, purge the entire physical inventory)?

[APP–5505] Not valid for phantom assembly

[APP–5505] You cannot update this field when on–hand quantity exists

[APP–5506] Purchasing class must be entered

[APP–5507] There were no &ENTITY records found

[APP–5507] You cannot update this field when: – On–hand quantity exists – Pending transactions

exist – Uncosted transactions exist

[APP–5508] Row copy not allowed

[APP–5509] Cannot update when using the form in Query Mode

[APP–5509] Row create not allowed

[APP–5510] Row delete not allowed

[APP–5511] No safety stocks are stored for MRP–planned safety stock type

You cannot navigate to the Item Safety Stock Zone for an MRP Planned Item because MRP will

calculate the Safety Stock, not this form. If you wish to calculate your own safety stock you must

change Safety Stock Type to: Non–MRP planned.

[APP–5511] Results will return a subset of rows selected through main query

[APP–5512] Screen Erase is not allowed in this zone

[APP–5513] Status must be entered

[APP–5513] Token ISSUE_RECEIPT must be either I or R

[APP–5515] At least one numeric digit must be specified to use ranges

[APP–5516] &ROUTINE cannot allocate enough memory to &VAR

[APP–5517] All serial numbers in a range must have same number of digits

[APP–5517] MRP not installed

You selected an option that required MRP to be installed. The MRP application is not installed.

[APP–5519] ”To” serial number must be greater than ”from” serial number

[APP–5521] Ranges cannot be built over different alphanumeric prefixes

[APP–5521] Receipt quantity exceeds available quantity

Receipt quantity should always be less than or equal to (RMA Quantity – Received Quantity)

[APP–5522] Return quantity exceeds available quantity

The total return quantity should always be less than or equal to (Received Quantity – Delivered

Quantity)

[APP–5523] Quantity must be greater than zero

[APP–5524] You must define receiving parameters for the destination org

[APP–5525] On–hand quantity exists for item, cannot change this value

[APP–5526] Invalid locator

[APP–5527] Invalid item revision

[APP–5527] Warning: On–hand quantity exists for this subinventory

[APP–5528] Invalid transaction reason

[APP–5529] Invalid transaction type

[APP–5529] Receipt quantity exceeds available quantity (difference between total and already

received quantities)

[APP–5530] Invalid transaction action

[APP–5531] Invalid user

[APP–5531] You cannot relate an item to itself

[APP–5532] Invalid shipment number

[APP–5533] Invalid freight code

[APP–5533] This shipping network is being used by a transaction. It cannot be deleted.

[APP–5534] Invalid freight account

[APP–5535] Invalid distribution account

[APP–5535] Repetitive planning is required for MRP– or MPS– or DRP– planned items You must

choose either ”Yes” or ”No” for the attribute Repetitive Planning if your item is an MRP or MPS or

DRP planned item

[APP–5536] Invalid transaction quantity

[APP–5537] Cannot update because the item has already been scheduled

Cannot update when rows exist for this item in the mrp_schedule_items table

[APP–5537] Invalid job

[APP–5538] Transaction source –– sales order is invalid. Please re–enter

[APP–5539] Item cannot have Assemble to Order = ”Yes”

This condition applies when Pick Components = ”Yes” or BOM Item Type = ”Planning”

[APP–5539] Transaction source –– GL account is invalid. Please re–enter

[APP–5540] Transaction source –– account alias is invalid. Please re–enter

[APP–5541] Report request &REQUEST_ID has been sent to the concurrent manager

[APP–5541] Subinventory code is not in the restricted list of subinventories for the item

[APP–5542] Locator is not valid. Please re–enter

[APP–5543] &ENTITY is required.

[APP–5543] Locator is not in the restricted list of locators for the item

[APP–5544] The item revision is not valid. Please re–enter

[APP–5545] Transaction reason is not valid. Please re–enter

[APP–5545] You must enter a value for &ENTITY

[APP–5546] Transaction action is not valid or not supported by open interface. Please re–enter

[APP–5547] Field is required

[APP–5547] Transaction type is not valid or not supported by open interface. Please re–enter

[APP–5548] Transaction quantity has an incorrect sign for the given transaction action

[APP–5549] Inventory item is not valid in the transfer organization or does not have the right status

to be processed

[APP–5549] Item cannot be ”not reservable” when there are reservations defined

[APP–5550] The user processing the transaction is not defined

[APP–5551] Cannot be restricted

Cannot be Restricted when Subinventories are not restricted or when Locators may be Dynamically

specified.

[APP–5551] The subinventories have incompatible types with respect to transaction type and item

type

[APP–5552] The shipment number is not unique, it has been used previously

[APP–5553] An error occurred while retrieving the open period ID

[APP–5553] Freight code is not valid. Please re–enter

[APP–5554] The transportation account is not valid for the given freight code

[APP–5555] Return quantity exceeds available quantity (quantity in inspection)

[APP–5555] Transfer locator is not in the restricted list for the given item in transfer organization

[APP–5556] Transfer locator is not valid for the item in the transfer organization

[APP–5557] Revision and effectivity date must be in the same order

[APP–5557] Transfer subinventory is not in the restricted list for the item in transfer organization

[APP–5558] Distribution account is not valid for the given organization. Please re–enter

[APP–5559] An error has occurred while updating the RMA tables.

[APP–5559] Replenishment count item(s) must be entered first

[APP–5561] Rolling back database changes...

[APP–5563] Attempting to reserve record for update or delete (^C to cancel)...

[APP–5565] An error has been encountered while cleaning up database changes made by RPC.

[APP–5565] You cannot generate tags for this physical inventory

Cause: You have selected a physical inventory the snapshot for which has not completed.

Action: Wait for the snapshot to complete and then reselect.

Action: Select another physical inventory.

[APP–5566] Inconsistent data found in the On–hand quantity stack This error is due to inconsistent

data in the On–hand quantity stack table (MTL_ONHAND_QUANTITIES). In particular, the

locator control attribute for an item with On–hand quantity different from zero is flipped.To fix this

problem, you need to put the On–handquantity information for the item that failed in synch with the

item’s current locator controlattributes.For example: if the item is no longer under locator control,

then you would first empty out all the locatorswith item quantity, then change the locator control

attribute, and finally receive item’s quantities backin.

[APP–5567] A database error has occurred for transaction header id = &header_id

[APP–5567] You have not entered values for all required columns in mtl_system_items_interface

Cause:

You cannot create an item unless you enter values for all required columns in

mtl_system_items_interface.

Action:

Please enter values for process_flag, organization_code or organization_id, item_number or

segment1 through segment20, process_flag and transaction_type.

[APP–5568] You entered an invalid value for the attribute

Cause:

Invalid value for attribute

[APP–5569] Safety Stock cannot be ’MRP planned percent’ unless MRP– or MPS– or DRP–

planned. MRP Planning Method must not be ’Not Planned’ for Safety Stock to be ’MRP planned

percent’

[APP–5569] You have violated one or more interdependency conditions between two attributes

[APP–5571] There has been database error cleaning up serial numbers

[APP–5573] Compile Header not found. Cannot Purge.

[APP–5573] Length of prefix plus number cannot exceed 30 digits

[APP–5574] Compile is currently used in an ABC Group. Cannot Purge.

[APP–5575] Count quantity for items under serial control must be 1 or 0

[APP–5575] Successfully purged MTL_ABC_COMPILES table.

[APP–5576] Successfully purged MTL_ABC_COMPILE_HEADERS table.

[APP–5577] ABC Group not found. Cannot Purge.

[APP–5577] You are trying to use one or more serial numbers that are not available for use in this

transaction.

[APP–5578] ABC Group used in Cycle Count. Cannot Purge.

[APP–5579] Successfully purged MTL_ABC_ASSIGNMENTS table.

[APP–5579] There are serial numbers that already violate this uniqueness constraint – update not

allowed

[APP–5580] Successfully purged MTL_ABC_ASSGN_GROUP_CLASSES table.

[APP–5581] Successfully purged ABC Group.

[APP–5581] Total serial numbers does not match the transaction quantity

[APP–5583] Service Item cannot be ”Yes” when Serviceable Product is ”Yes”

[APP–5585] Required when service duration period has been specified

[APP–5587] Serial number &token has an invalid current status

The valid current status for a serial number is1,3,4,5.

[APP–5588] You can only delete records that have a status of ’Processing’

[APP–5589] Serial number &token1 resides in a different locator

[APP–5591] Serial number &token1 is defined for under a different lot number

The serial number &token1 is defined under a different lot number &token2.

[APP–5593] Serial number &token does not exist for the given item

The serial number does not exist for this item. Also you cannot dynamically create a serial number

for this item.

[APP–5595] &ENTITY cannot be a date in the past

The date you have entered is in the past. Pleaseenter today’s date.

[APP–5595] Serial number &token is defined in a different organization

[APP–5596] Internal applications error has occurred

Cause:

An internal error has occurred in this application. Please contact your support representative for

assistance.

[APP–5597] Serial number &token1 is defined for a different revision

The serial number &token1 is defined for a different revision number &token2

[APP–5598] &ENTITY1 must be Unique.

[APP–5599] Please enter all &SOURCE_TYPE information before continuing

[APP–5599] Serial number &token is not available for this transaction

The serial number has a current status that is invalid for this transaction.

[APP–5601] Do you wish to re–calculate the &ITEM?

[APP–5601] Serial number &token1 resides in a different subinventory &token2

[APP–5603] Serial number &token1 is used in another organization and it fails the uniqueness

constraint across organizations

Cause:

In the Define Organization Parameters form, the Serial Number Uniqueness option = Unique across

organizations

Action:

Use another serial number

[APP–5605] Serial number &token1 is currently used in this organization

[APP–5606] You cannot update or delete a frozen movement

[APP–5607] You must maintain the related category set at the Item/Org level

Cause:

The default category set for a functional area must be maintained at a level equal to or below that of

the related item–defining attribute. By changing the control level of the current item defining

attribute, you would be violating this requirement.

Action:

Do not change the control level of the current item–defining attribute

[APP–5608] The deletion of this movement will be immediately commited. Continue?

[APP–5609] Required when under shelf–life control

[APP–5609] This is the first page for zoom transactions

[APP–5610] Movement Parameters already exist for this Entity Name

[APP–5611] Planning items and Support Service items may not be shippable items. Shippable Item

may not be ”Yes” when BOM Item Type = ”Planning” or Support Service is ”Yes”

[APP–5611] You cannot delete records for entities used in movement statistics

[APP–5612] You can only enter movement details for In–transit Transfers

[APP–5613] Please enter a transaction before recording the movement details

[APP–5613] Shrinkage must be less than 1

[APP–5614] No closed period found for date entered

[APP–5615] Source Organization is required when Source Type is Inventory

[APP–5616] You cannot delete a Transaction Type associated with material transactions

[APP–5617] OE transactable cannot be ”no” when demand exists for the item

[APP–5617] You can only decrease the Quantity

[APP–5619] Ending tag digits must match starting tag digits

[APP–5621] Starting lot number is required when lot control code is ”full lot control”

[APP–5623] This attribute is not updatable because it is under status control

[APP–5625] The control level may not be updated when there are pending changes

When updating the control level for the item status attribute, the form ensures that the status

attributes that are under status control or default control are maintained at the same level. If

pending changes are not committed or cleared, the form may not be using the current state of the

status attributes and may not correctly keep the control levels consistent.

[APP–5627] An item may not be stockable unless it is an inventory item

An item may not have Stockable = ”Yes” unless the Inventory Item attribute is also ”Yes”

[APP–5629] Subinventory selected is already assigned to this item

[APP–5631] Subinventory is required

[APP–5633] Submission of transaction worker to process header ID &TOKEN failed

[APP–5635] Warning: This may cause on–hand balances in subinventories to be invalid

[APP–5637] Non–numeric digits must be constant

[APP–5639] Ending tag number must be greater than or equal to starting tag number

You have entered a starting and ending tag combination in which the ending tag is less than the

starting tag. Oracle Inventory will not generate any tags

[APP–5641] Digit increments must be numerics

[APP–5643] This tag already exists. Please enter a unique tag number

[APP–5645] You must have enough digits in your tag numbers to accommodate this number of tags

[APP–5647] The Remote Call failed because no manager was available.

[APP–5649] The Remote Call failed due to a time out.

[APP–5651] You must define a Transaction Source Type before defining Transaction Type

[APP–5653] An item may not be transactable unless it is stockable

Cause:

An item may not have Transactable = ”yes” unless Stockable = ”yes.”

Action:

First set Stockable = ”yes” and then set Transactable = ”yes”

[APP–5655] &ENTITY failed. Try again?

[APP–5657] Transactions exist –– update not allowed

[APP–5659] &VALUE1 is already assigned to another class

[APP–5661] Unit of measure information for &UOM is not found

Unit of measure &UOM does not exist

[APP–5663] If you change your costing method you must update your setup accounts

[APP–5665] You must review your item, subinventory and organization encumbrance accounts

[APP–5667] Row exists. Query this row and update

[APP–5669] Warning: Altering this value will cause every item’s (assigned this status) attribute to

be updated

[APP–5670] Posting is not allowed for this account

[APP–5671] Updating the item master organization may corrupt your data. The compatibility of

items, item attributes, and item costs in the new item master should be verified before proceeding.

Accept changes?

[APP–5673] Warranty must be ”No” if BOM Item Type is not ”Standard” or Support Service is set

to ”No”

[APP–5675] WIP Supply Type must = ”Phantom” because ATP Components = ”Yes”

[APP–5677] Calculation and update of WIP cumulative values failed

[APP–5679] Warning: WIP will not build this item when Pick Components = ”Yes”

[APP–5681] Value must be a number

[APP–5683] Zero count, no adjustment performed.

[APP–5685] This function will clear the entire form

[APP–5688] Inventory item ID is invalid or does not have the flags enabled correctly to be

processed by material processor

[APP–5691] An error occurred while cleaning up orphaned dynamic serial numbers.

[APP–5694] Transaction quantity is greater than available RMA quantity in inspection.

[APP–5695] Item should be Container for Container Type to exist

[APP–5696] Make the item Container or Vehicle before entering values here

[APP–5699] An error occurred while relieving reservations.

[APP–5700] Returnable must be ”No” when Support Service is set to ”Yes”

[APP–5700] Warning: Mandatory Intercompany Relation not defined

Cause:

The selling and shipping operating unitbelong to different legal entities but the

intercompanyrelation has not been defined.

Action:

Use the Define Intercompany Relations formto define the intercompany relation between these

twooperating units.

[APP–5701] Inventory Item cannot be ”Yes” when Support Service is set to ”Yes”

[APP–5701] Warning: Cannot retrieve the currency exchange rate

Cause:

Currency conversion rate for the desired dateand rate type has not been defined.

Action:

Use the Define Daily Conversion Rates formin Oracle General Ledger to define the required

conversionrate.

[APP–5702] Purchased Item must be ”No” when Support Service is set to ”Yes”

[APP–5702] Warning: Cannot create invoice header

[APP–5703] Cycle Count Enabled must be ”No” when Support Service is set to ”Yes”

[APP–5703] Warning: Set of books info not found for id &ID

[APP–5704] Check ATP must be ”No” when Support Service Item is set to ”Yes”

[APP–5704] Warning: Cannot create invoice line

[APP–5705] Postprocessing Lead Time must be 0 when Make or Buy = ”Make”

[APP–5705] Warning: FlexBuilder failed to generate a CCID for this invoice line

[APP–5706] Cannot enter Tax Code

Cause:

The item is not taxable.

Action:

Set Taxable to Yes.

[APP–5706] Warning: Cannot retrieve transfer price for the item

[APP–5707] Customer and site use info not found for this operating unit.

[APP–5708] Vendor and/or vendor site information not found

[APP–5709] Invalid Receivables transaction type for id &ID

[APP–5710] Source length must be less than 30

[APP–5711] Cannot get profile value &PROFILE for the operating unit &ORG.

[APP–5711] Successfully purged MTL_CC_SCHED_COUNT_XREFS table.

[APP–5712] Multiple, conflicting profile values &PROFILE for the operating unit &ORG.

[APP–5712] Successfully purged MTL_CYCLE_COUNT_ENTRIES table.

[APP–5713] Successfully purged MTL_CC_SCHEDULE_REQUESTS table.

[APP–5713] Warning: Cannot retrieve code combination

[APP–5714] Successfully purged MTL_CYCLE_COUNT_ITEMS table.

[APP–5714] Warning: Cannot retrieve freight code combination

[APP–5715] Successfully purged MTL_CC_SUBINVENTORIES table.

[APP–5715] Warning: Tax code &CODE does not have a code combination

[APP–5716] Successfully purged MTL_CYCLE_COUNT_CLASSES table.

[APP–5716] Warning: This vendor site has no default tax code

[APP–5717] Successfully purged MTL_CYCLE_COUNT_HEADERS table.

[APP–5717] Warning: Invalid batch source attribute

Cause:

Batch source &BATCH does not allow sales credit whileyour AutoAccounting rule for operating

unit &OUuses salesrep in one or moer of the account segmentassignments.

Action:

Please change the Allow Sales Credit flag for the batchsource to Yes before proceeding.

[APP–5718] The subinventory you specified was not found. It may have been non–reservable.

[APP–5718] Warning: Invoice creation aborted

[APP–5719] Warning: Cannot retrieve seeded batch source information

[APP–5720] Warning: Invalid freight item

[APP–5721] Warning: Cannot retrieve price list from bill–to site information

[APP–5723] Warning: Cannot retrieve payment term from bill–to site information

[APP–6001] &MISSING_FIELD is required. Please enter a valid value

[APP–6004] Please enter the time in the 24 hour format: HH:MM

[APP–6005] Please enter the date in the format DD–MON–YYYY

[APP–6007] Save your &INFORMATION_TYPE or display another before continuing

[APP–6009] The Inactive Date must be on or after today’s date.

[APP–6012] This record has been entered already

[APP–6013] System Error: Concurrent manager failure

[APP–6014] Element rules already exist for this Classification.

Cause:

You are trying to &INS_OR_DEL a &CLASSIFICATION_NAME classification rule for which

&INC_OR_EXC element rules already exist within this set.

Action:

Please delete the &INC_OR_EXC element rules for the &CLASSIFICATION_NAME classification

first.

[APP–6015] Too many hours for the frequency you have chosen.

Cause:

You are trying to define too many working hours for the frequency you have chosen.

Action:

Enter a suitable number of working hours: Up to 24 working hours per Day ” 168 ” per Week ” 744

” per Month ” 8784 ” per Year.

[APP–6016] The value name includes reserved words or characters

Action:

Only alphanumeric or underscore (_) characters are valid. Also, you cannot start a name with a

number.

[APP–6018] &MINIMUM value must be less than or equal to &MAXIMUM value

[APP–6020] You cannot update predefined system data.

[APP–6021] End Date must be later than the Start Date

[APP–6024] You cannot delete information in a ’query–only’ region

[APP–6028] A restriction with this value already exists

[APP–6030] A customization with this name already exists

[APP–6034] You created this employee in another Set of Books

Cause:

You are trying to enter the expense account field for an employee someone created in another set of

books.

Action:

You must use that set of books to edit the employee’s expense account information.

[APP–6035] Warning: Invalid data in key flexfield

[APP–6039] Cannot get &FLEXFIELD_STRUCTURE flexfield structure

[APP–6041] This screen cannot be accessed when Human Resources is installed

Cause:

The screen attached to this menu optioncannot be used when either Oracle Human Resources or

Oracle Payroll is installed.

Action:

Replace the screen with the appropriatescreen from Oracle Human Resources.

[APP–6042] You cannot update predefined system data

[APP–6043] Please define a security profile for your Business Group

[APP–6044] You cannot delete predefined system data

[APP–6045] You cannot delete predefined system data

[APP–6046] Your user–profile options are set incorrectly to use this screen.

Cause:

Your ’HR:Business Group’ user–profile option is not set correctly.

Action:

Your System Administrator should set your ’HR:Business Group’ user–profile option to a valid

business group.

[APP–6047] This employee is not assigned to a Payroll

Cause:

You cannot create Nonrecurring, additional, adjustment or override element entries for employees

who are not assigned to a Payroll.

[APP–6048] You cannot delete this record. It is used by Oracle Purchasing

[APP–6050] This set is used in a form customization

Action:

You must first delete this element set from the form customization that uses it.

[APP–6051] You cannot delete a set that is used in an element definition.

Cause:

You are trying to delete a set that is used in the definition of an element on the Define Element

Form.

Action:

You must first delete the element definition on the Define Element form, if it is not being used,

before you can delete this set.

[APP–6052] You cannot insert generic data.

Cause:

You are attempting to insert data in generic mode without defining any ownership definitions for

this session.

Action:

Remove the changes you have made. Then enter at least one ownership definition using the ’Define

Default Owning Parameters’ (PAYLODOP) screen.

[APP–6053] You cannot insert startup data.

Cause:

You are attempting to insert data in startup mode without defining any ownership definitions for this

session.

Action:

Remove the changes you have made. Then enter at least one ownership definition using the ’Define

Default Owning Parameters’ (PAYLODOP) screen.

[APP–6054] You cannot delete a set that is used by a payroll action.

Action:

You must delete the payroll action that uses this set before you can delete the set from this form.

[APP–6055] Enter a unique name for this set

[APP–6058] You cannot delete a period type that is used by a Payroll

[APP–6064] This element has been closed for entry

[APP–6067] This application has a future end–date

Cause:

You cannot create an assignment for anapplication that already has an end date in the future.This

may have been caused by hiring or terminating theapplicant, or by a date–effective deletion.

[APP–6068] You must choose a &RECORD before you can continue

[APP–6069] This action will interrupt the assignment continuity

Cause:

An application must have at least one assignment at all times. This operation will delete or date

effectively end the assignment so that the continuity is broken.

[APP–6071] You cannot end an assignment with future changes

[APP–6073] Invalid or inactive status

[APP–6074] Current or future payroll periods are closed

You cannot create or modify any element entries unless the period is open for input or the element

cannot be processed.

[APP–6075] A recurring entry for &ENTRY_TYPE already exists

You can change the existing entry to show the new values, or delete the existing entry.

[APP–6076] These dates overlap those for an existing hierarchy

[APP–6077] You cannot enter duplicate hierarchy version numbers

[APP–6078] System Error: Form &FORM Block &BLOCK Trigger &TRIGGER Step &STEP

Cause:

System Error at Form : &FORM Block : &BLOCK Trigger: &TRIGGER Step : &STEP

[APP–6080] You cannot use this status

The first status for an assignment must have a system value of ’ACTIVE_APL’

[APP–6083] This assignment has a future status of TERM_APL or ACTIVE_ASSIGN

[APP–6084] You cannot delete this hierarchy while versions still exist

[APP–6085] You may have only one primary hierarchy

[APP–6087] This is the top position in this hierarchy

[APP–6088] System Error: Form &FORM Trigger &TRIGGER Step &STEP

Cause:

System Error at Form : &FORM Trigger : &TRIGGER Step : &STEP

[APP–6091] Cannot get &LOOKUP_TYPE lookup type

[APP–6093] System Error: Cannot retrieve information from &TABLE

[APP–6094] System Error: Cannot update &TABLE

[APP–6099] System Error: Failure retrieving &USER_PROFILE user profile

[APP–6102] The position is now inconsistent with the new organization

Cause:

You have changed the organization but not the position. The position does not exist in the

organization you have selected.

Action:

Enter a valid position for the organization.

[APP–6105] The dates overlap those of an existing budget version

[APP–6107] This budget version number already exists

[APP–6108] A balance with this name already exists

[APP–6110] Delete recruiting for records first. This recruitment activity is recruiting for one or

morevacancies.

[APP–6111] Other recruitment activities are within this activity. Update or delete the subsidiary

recruitment activitiesbefore you delete this one.

[APP–6113] A recruitment activity with this name already exists

[APP–6114] The closing date must be later than the start date

[APP–6116] This element classification already feeds this balance

[APP–6117] This dimension already exists for this balance

[APP–6120] This vacancy already exists for the recruitment activity

[APP–6121] Vacancy does not exist at start of recruitment activity

Cause:

You have changed the start date of the recruitment activity so that one of the vacancies is no longer

valid.

Action:

The recruitment activity start date must be on or before the start dates of all the vacancies covered

by that activity.

[APP–6122] Organization is not valid at start of recruitment activity

Cause:

The ’Run By’ organization must exist at the start date of the recruitment activity. You have changed

the start date of the activity so that this is no longer true.

Action:

Check the start date of the ’Run By’ organization for the earliest start date of the activity.

[APP–6123] This &INFORMATION_TYPE name already exists

[APP–6124] You must delete any vacancies for this requisition first

[APP–6125] This vacancy has an applicant assigned to it

You must delete the applicant assignment before you can delete the vacancy.

[APP–6126] This vacancy is used in a recruitment activity

Delete the &VACANCY_NAME vacancy from any recruitment activity that uses it. Then delete

the vacancy.

[APP–6127] &INPUT_VALUE_NAME must be entered

[APP–6128] There is no hot default value for &INPUT_VALUE_NAME

Cause:

&INPUT_VALUE_NAME has been defined with a ’hot’ default, but no value can be found for the

default at the element type or element link levels.

Action:

Ask your System Administrator to check the definitions for this element. If you do not require a

default value for &INPUT_VALUE_NAME, then enter the value.

[APP–6130] You cannot delete this organization, people are assigned to it

[APP–6131] You cannot delete this Organization, Jobs exist for it

[APP–6132] Element link does not exist for the duration of the entry

Cause:

The link has been purged or date effectively deleted.

Action:

Check the effective start and end dates on the link definitions for this element.

[APP–6136] This classification is not enabled

[APP–6137] This name already exists

[APP–6138] This Reporting Name already exists

[APP–6140] You cannot define a standard link for a nonrecurring element

[APP–6141] You cannot have a supplementary run for a nonrecurring element

[APP–6142] Nonrecurring elements cannot have an additional entry

[APP–6143] An ’HR User’ cannot define elements with indirect results

[APP–6144] An ’HR User’ cannot define elements as adjustment only

[APP–6145] Output currency must match the currency of your business group

[APP–6146] This assignment number already exists

[APP–6147] You cannot update this field

If element links exist for this element you cannot change any of the following attributes: Standard

Link, Input Currency, Output Currency, Adjustment Only, Indirect Only, Additional Entries

Allowed, Termination Rule. Changes to these attributes could cause processing to become

inconsistent.

You must delete the links before you can update any of these fields.

[APP–6148] System Error : A unique assignment number cannot be generated

[APP–6149] You cannot update the processing priority

This may produce a formula result rule with a result that conflicts with the element that feeds it.

Check the processing priority values of your elements.

[APP–6150] Probation end date must be greater than assignment start date

[APP–6151] Projected Date must be less than or equal to Actual Date

[APP–6152] Projected Date must be greater than Start Date

[APP–6153] System Error: Procedure &PROCEDURE at Step &STEP

Cause:

The procedure &PROCEDURE has created an error at Step &STEP.

Action:

Contact your system administrator quoting the procedure &PROCEDURE and Step &STEP.

[APP–6154] Termination notified date must be greater than start date

[APP–6155] You cannot delete an element while links exist

You must delete the element links before you can delete the element.

[APP–6157] You cannot delete elements that have formula result rules

Delete any formula result rules before trying to delete the element.

[APP–6158] Standard Process date must be greater than Actual Termination date

[APP–6159] Final Process date must be greater than Standard Process date

[APP–6160] Final Process date must be greater than Actual Termination date

[APP–6161] You cannot delete an organization that has a classification

[APP–6162] No translation can be found for this Pay Value name

[APP–6163] This User Name already exists

[APP–6164] The Default value must also be Active

[APP–6167] You can define only six input values for an element

[APP–6168] This input value name already exists for this element

[APP–6169] Database items for nonrecurring input values must be numeric

[APP–6170] This validation combination is incorrect

The only combinations that will be accepted are:

Default, Maximum and Minimum

Default and Lookup (Default must be valid forlookup type)

Formula Id (No other validation)

[APP–6171] Default value is invalid for Lookup Type

[APP–6173] You cannot update a vacancy that has an applicant assignment

[APP–6176] You cannot update a vacancy that has an applicant assignment

[APP–6177] You cannot update the input value name

Possible causes are: The input value is the ’Pay Value’; You are trying to make this input value the

’Pay Value’; You are trying to date effectively update the name; You have already used this input

value name in a compiled formula.

[APP–6178] You cannot change the unit of measure

You can only update units of measure for elementsthat are not processed in a payroll run.

[APP–6179] You cannot make this a required value if links already exist

[APP–6181] You cannot update the ’Error’ option when entries exist

[APP–6183] This is the top organization in the hierarchy

[APP–6185] This balance feed already exists

[APP–6186] This subordinate already exists

[APP–6187] An override already exists for this element

You can override the entry for an element only once in a period. Check the override entry that

already exists.

[APP–6188] This date would invalidate part of your vacancy

This would make the start date of the vacancy before the start date of the &PART in your vacancy.

[APP–6189] You cannot override an entry when an adjustment already exists

[APP–6190] You cannot delete organizations that also have subordinates

[APP–6191] You cannot delete this default value

You are trying to delete a hot default value that may invalidate some of the entries for this element.

Replace the default value and check the links for this element to make sure that all your entries will

have a default value that is available at run time.

[APP–6192] You cannot delete the minimum value

This action would mean that some hot defaulted mandatory values wouldnot have a value at run

time.

Check that all your element links have a minimum default value.

[APP–6193] You cannot delete the maximum value

This action might result in maximum values not being available at run time for mandatory entries

Check that all the links for this element have maximum default values or re–enter the maximum

value.

[APP–6194] The entry does not exist for the duration of the adjustment

You are trying to enter an adjustment when the recurring entry does not exist for the whole of this

period.

Check the start and end dates of the recurring entry before trying to make the adjustment.

[APP–6195] You cannot adjust an entry that already has an override

Check the entry and the override values for more information.

[APP–6196] You can enter an adjustment only once in each period

Check the existing adjustment for this entry formore information.

[APP–6197] You cannot enter new input values

YIf you are trying to define a required input value there must be no existing element entries.

If the input value is not required there must be no entries that have been processed in a payroll run.

[APP–6200] This operation is not allowed

You cannot remove an assignment that has been terminated by the termination of the Period of

Service.

[APP–6202] Cannot view results when status is incomplete or error

[APP–6203] Cannot view results for an action that is marked for retry

[APP–6204] You cannot delete this version, it contains organizations

[APP–6205] You cannot delete this version it contains positions

[APP–6209] Future change delete not allowed

[APP–6210] You cannot delete input values if links exist

[APP–6211] You cannot delete input values if entries exist

[APP–6212] You cannot delete input values if run results exist

[APP–6213] Formula result rules use this input value

Check your formula result rules for indirectresults that feed this input value.

[APP–6214] Absence or attendance records exist that use this input value

[APP–6215] Backpay rules exist that use this input value

[APP–6216] You cannot rollback the assignment action &ACTION_ID

You can only roll back the most recent run, reversal, Quickpay or balance adjustment.

An assignment action cannot be rolled back if it is a PURGE action or it has other sequenced

actions that follow it and depend on it.

[APP–6219] Input value is invalid for standard links

Check that all required input values have a default value that can be used when entries are created

automatically. Also, check that none of the input values have formula validation. This is not

allowed with a standard link.

[APP–6220] The account must be in territory &TERITORY

[APP–6221] Amount or percentage must be given

[APP–6223] The specified external account does not exist

[APP–6224] This payment method does not exist

[APP–6225] This assignment already has a payment method with this priority

[APP–6226] Pre–payments exist for this payment method

[APP–6227] Formula and validation flag must be supplied for category ’MT’

[APP–6228] Validation days or validation value must be supplied

[APP–6229] You cannot use a payment method of this category as default

[APP–6230] You must specify an account and a type for the payment method

[APP–6231] This payment method should use a currency of &CURRENCY

[APP–6232] You must enter a valid payment type for the payment method

[APP–6233] No payments balance has been defined

[APP–6234] Future pre–payments exist for this method

[APP–6235] Personal payment methods exist for this payment method

[APP–6236] This payment method is used as a default for a payroll

[APP–6237] You cannot delete this person, assignment actions exist

[APP–6238] There is no default payment method for this payroll

[APP–6239] The override payment method is invalid

[APP–6242] You cannot delete this element, it has run results

[APP–6254] This person is not a current employee

You cannot update assignment information after the period of service has been terminated.

[APP–6259] You must commit outstanding changes before deleting a person

[APP–6274] You cannot delete application users

[APP–6281] Cannot remove future changes, the link is deleted in the future

[APP–6283] You cannot remove future changes

This entry has been closed in the future accordingto a termination processing rule. You cannot

removethis future change for the entry.

[APP–6284] You cannot remove future changes, there is an assignment deletion

[APP–6303] You must enter a value within the minimum and maximum range

[APP–6304] You cannot delete this entry while it has future adjustments

[APP–6305] You cannot delete this record

This person has an assignment that is the onlymember of an assignment set. Deleting this person

wouldcreate an empty set, and this would mean that allassignments are members of the set.

You must delete the assignment set before you candelete this record.

[APP–6306] Incorrect format for &UNIT_OF_MEASURE unit of measure

[APP–6307] Terminated Date must be on or after the Received Date

[APP–6310] This classification name already exists

[APP–6311] This priority is out of sequence

Cause:

You are trying to define a priority that isout of sequence with the other default priorities.

Action:

Enter the priorities in sequence; Low isless than or equal to the Default, is less than or equal toHigh.

[APP–6313] You cannot delete this record while secondary classifications exist

[APP–6314] This classification is used by existing elements

[APP–6315] This classification is used in an element classification rule

[APP–6316] This classification is used in a balance definition

[APP–6317] This classification is used in a sub classification rule

[APP–6318] You must have only one default name for &SYSTEM_NAME

You can have any number of active user names for each system name, but you must set only one as

the default type.

[APP–6320] You cannot delete this terminated assignment

You are trying to delete a ’terminated’ assignment status record. The next datetracked record for

this assignment also has a terminated status, but it begins after the actual termination date for the

employee. The deletion would mean that there would be a time after termination when the

assignment would not be ’terminated’

Cancel the employee termination before you try to make this change.

[APP–6323] The primary employee assignment does not include a payroll

[APP–6324] You cannot delete people who have changed their ’person’ type

[APP–6325] You cannot delete people with letter requests

[APP–6326] You cannot delete people who are contacts, or who have contacts

[APP–6328] You cannot delete people who are contacts for an event

[APP–6329] You cannot delete interviewers or people who are booked on events

[APP–6330] You cannot delete people who have assignment changes

[APP–6331] You cannot delete people who are recruiters or supervisors

[APP–6332] You cannot delete people who have accepted terminations

[APP–6334] You cannot delete people with special information details

[APP–6335] You cannot delete people who have absence information

[APP–6336] You cannot delete people who have replaced or authorized absences

[APP–6337] You cannot delete people who are recruitment contacts or authorizors

[APP–6338] You cannot delete people who have raised requisitions

[APP–6339] You cannot delete people who have authorized vacancies

[APP–6340] You cannot delete people who have element entries

[APP–6341] You cannot delete people with extra assignment information

[APP–6342] You can only enter a zero adjustment if the action is ’replace’

[APP–6343] You cannot enter negative adjustment values

[APP–6344] You cannot delete people who have scheduled interviews

[APP–6346] This person does not have a current period of service

[APP–6361] A &OBJECT with this name already exists

[APP–6365] This name cannot be used as a database item

Database item names must start with an alphabetic character and contain no special characters such

as ? * &

[APP–6366] The assignment does not exist for the duration of the entry

The entry cannot be created for this assignment. Check for future changes on the assignnment, or

the element link rules.

[APP–6368] You must delete the table columns first

[APP–6369] You must delete table rows first

[APP–6370] You cannot create an entry past the termination rule date

Cause:

You are trying to create an element entry for an employee assignment which does not end before the

termination rule date.

Action:

Please remove your current changes.

[APP–6371] You must enter a Terminated Date before terminating an applicant.

Cause:

You are trying to terminate an applicant without putting an end date on the application.

Action:

Please enter an end date that is later than the Application Received Date.

[APP–6374] You cannot delete people with grade step placements.

[APP–6375] You cannot delete people with entry overrides or adjustments

[APP–6379] You cannot delete people with quickpaint results

[APP–6380] The End Date of this Assignment is before the Final Process Date.

Cause:

In order for an Assignment to become the Primary Assignment it must not end before the

Employees Period of Service Final Process Date.

[APP–6381] Assignment cannot be Primary. It is terminated before Actual Termination Date

Cause:

The assignment has a termination status before the actual termination date. If this assignment is

becomes the Primary Assignment it will be Primary for some time after termination. The only time

an assignment can be Primary after termination is after the Actual Termination Date on the

Employee’s Period of Service.

[APP–6382] You cannot terminate the applicant because person type changes exist.

Cause:

You are trying to terminate an applicant on &DATE but the applicant has a person type change after

this date and so you cannot terminate the applicant.

Action:

You must change the Termintion Date to a date after the applicant has any person type changes

before you can terminate the applicant.

[APP–6383] You cannot change the category as absence details exist for this type

[APP–6384] This operation removes a primary assignment. Another one cannot be found.

Cause:

The operation removes a future primary assignment record. Ther must be one and only one primary

assignment at any point within the duration of a period of service. No candidate assignment can be

found to meet this requirement.

[APP–6385] Future person changes exist. You cannot cancel the termination.

Cause:

You are trying to cancel the application termination when future changes exist for the person after

the Termination Date.

Action:

You must first delete any changes that the person’s record has after the termination date before you

can cancel the termination on this form.

[APP–6387] Cannot terminate an assignment that has non–terminate future changes

Cause:

You can only terminate an assignment if the changes in the future are of type TERM_ASSIGN

[APP–6390] This is not the payments defined balance for this legislation

[APP–6391] This payroll ends in the future. It cannot be entered on an assignment.

Cause:

The Payroll has been deleted at some time in the future. Payrolls must be continuous until

31–DEC–4712 in order that they can be inserted or updated on an assignment record. Deletion of

future changes will also be prevented if the current payroll has been deleted at some time in the

future.

[APP–6392] Payroll cannot be entered for an Employee who has no Date of Birth.

Cause:

The Payroll procedures require that a Date of Birth be entered for the Employee

[APP–6395] A set with this name already exists. Enter a new name.

[APP–6396] You cannot delete this set, it is a default for a payroll

[APP–6397] You cannot delete this set, payroll actions exist

[APP–6398] This element link is not mutually exclusive.

If it is possible for a person to have an element assigned to them more than once through different

links then the links entered are not mutually exclusive. To ensure that links are mutually exclusive

at least one of the criteria must always be different for links which are for the same element.

[APP–6399] The Payroll does not exist for all the duration of the entry

[APP–6404] Input Value cannot be costed

Only input values that belong to costed elementlinks can be costed. The costable type must be

either ’Costed’ or ’Fixed’. All Pay Values can be costed but any other input value must have units

of hours type to be costed.

Action:

Change flag to No or change element link costable type.

[APP–6405] No exchange rate exists to convert &RATE1 to &RATE2

[APP–6408] You cannot change the &TYPE as future assignment changes exist.

Cause:

You are trying to update the &TYPE for this applicant assignment but this applicant’s assignment

has changes further in the future than your current Session Date. You cannot therefore change the

&TYPE.

Action:

You must first delete the future assignment changes before you can change the &TYPE on this

form.

[APP–6412] Date Received must be less than Effective Date.

[APP–6413] Applicant Number Already Exists.

[APP–6414] Applicant has Date Effective Changes. Delete Not Permitted.

[APP–6415] Applicant has more than one address. Delete not Allowed.

[APP–6416] You cannot delete amended startup assignment statuses

[APP–6417] You can only delete non–startup assignment statuses

[APP–6420] You cannot delete default assignment statuses

[APP–6421] Cannot remove future changes when Assignment Ended in Future.

[APP–6422] Cannot remove Last Change when Assignment has Ended.

[APP–6424] You cannot delete primary statuses used by assignments

[APP–6425] You cannot delete secondary statuses used by assignments

[APP–6427] You cannot delete statuses used to generate letters

[APP–6428] The person has no accepted assignments. Hire cannot continue.

Cause:

You have tried to hire an applicant with no accepted assignments.

Action:

Accept one of the applicant’s applications.

[APP–6429] Future applicant assignments exist for this person. Hire is aborted.

Cause:

You have tried to hire an applicant who has future applicant assignments.

Action:

Delete the future assignments and try again.

[APP–6433] You can only have one budget value for a unit of measure

[APP–6434] You cannot enter a new assignment for a closed period of service

RORTEXT

[APP–6435] You cannot delete an employee’s first assignment

Cause:

You are trying to delete the first assignment created for an employee.

Action:

This assignment is created when you first enter the employee into &APPLICATION and you cannot

delete this assignment.

[APP–6436] A user status cannot start more than once on the same day

Cause:

You are trying to enter a user status that starts on the same day as an existing identical user status.

Action:

If you want to enter this user status again for this assignment, change the start date to be different to

that of the existing identical user status.

[APP–6438] Primary Assignment End Date will be set earlier than end of Period of Service

Cause:

As a result of the operation being performed future Assignment Termination rows will be removed.

This has the effect of moving the Assignment End Date to the Day after the Actual Termination

Date. At the same time an attempt to make this Assignment the Primary Assignment is made. A

Primary Assignment must be continuous until the End of the Period of Service therefore this

operation will result in an invalid state.

Action:

Ensure that the Assignment is continuous until the End of the Period of Service before attempting to

make it the Primary Assignment.

[APP–6439] Please choose an element before continuing.

[APP–6440] Cannot delete this rate as Pay Bases exist for this rate.

[APP–6441] Grade Name is required. Please enter a valid value

[APP–6442] The payment cannot be fully paid with the monetary units available

[APP–6443] Cannot delete this Grade. Valid Grades exist

[APP–6444] Cannot delete this Grade. Vacancies exist for it

[APP–6447] Cannot delete Grade. Budget Elements exist

[APP–6448] You cannot delete this grade because a grade scale exists for it.

[APP–6456] Cannot Enter Interview Future Changes to Assignment Exist

[APP–6457] Projected date is outside the dates fro this absence type

[APP–6460] The process in run flag must be the same for the lifetime of the element

The process in run flag can only be changed by correction and this is only valid if there are no date

effective changes for the duration of the element type.

[APP–6461] The Parent Recruitment Activity is not valid at the start of the Child Activity

Cause:

The parent recruitment activity either starts after or ends before the start date of the child

recruitment activity.

Action:

Change the start date of the recruitment activity or choose another parent from the QuickPick List.

[APP–6462] Distributed elements cannot be in distribution sets.

[APP–6464] This status must start on or after the start date of the assignment

Cause:

For an assignment status, you are trying to enter a start date which is outside the start and end dates

for the assignment.

Action:

Enter a start date for this assignment status which is within the start and end dates for the

assignment.

[APP–6465] Costable type cannot be updated if entries exist

This would cause a breakdown in data integrity in the system as the entries would contain different

information from the link.

Action:

Delete entries and then update costable type or change costing information on entries.

[APP–6466] Costable type must be corrected over the whole lifetime of the link

The costable type must be the same over the whole lifetime of the link. This is to ensure data

integrity in the system.

[APP–6467] You cannot delete links which have non–recurring entries

[APP–6468] Bank Details need to be filled

[APP–6471] Cannot delete. Personal Payment Methods exist

[APP–6472] Cannot delete. Pre Payments exist

[APP–6473] Cannot delete. Valid Payment Methods exist for Payrolls

[APP–6475] Currency cannot be changed

[APP–6476] You cannot delete people with enrollments to COBRA

[APP–6478] This Formula Result Rule record already exists.

[APP–6488] Cannot delete. Payroll actions exist for this payroll

[APP–6489] Cannot delete. Assignment sets exist

In order to delete this payroll you need to delete assignment sets defined for this payroll.

[APP–6490] Cannot delete. Payroll lists exist

[APP–6491] Cannot delete. Security payrolls exist

[APP–6495] Can only update Number of Years to a greater number

[APP–6497] Cannot delete. Personal Payment Methods have been assigned

[APP–6498] Cannot delete. Pre Payments exist for this payment method

[APP–6500] This Assignment has no Payroll, you cannot enter Payment methods.

[APP–6501] Invalid unit of measure

Cause:

The unit of measure of the Pay Value of theElement for which you are trying create a Direct

FormulaResult is inconsistent with the data type of the selectedFormula Result Name.

Action:

Check unit of measure of the Pay Value and Item Name, amend if required and retry.

[APP–6503] A Direct Formula Result already exists

Cause:

There can only be one Direct Formula Result per Processing Rule.

Action:

Removing the existing Direct Formula Result.

[APP–6510] This Person already has a primary address during this period.

[APP–6513] Employee has already been terminated.

Cause:

You are trying to terminate an employee whose current period of service has already been

terminated.

Action:

If you want to change the termination details then cancel the termination and re–terminate

specifying the correct details.

[APP–6514] Employee has not been terminated

Cause:

You are trying set the final process date for an employee who has not yet been terminated.

Action:

Initiate termination by setting the actual termination date. You can set the final process date when

terminating or you can terminate and set the final process date later.

[APP–6515] Employee has not been terminated. Can not initiate cancellation

Cause:

You tried to initiate cancellation for an employee whose period of service is still open.

Action:

n/a:

[APP–6516] Can not terminate employee, future actions exist.

Cause:

You were trying to terminate an employee which has actions beyond the actual termination date.

Action:

Rollback / remove actions beyond the actual termination date before trying to terminate this

employee again.

[APP–6517] Can not set final process date, future actions exist.

Cause:

You are trying to set the final process date for an employee which has actions beyond that date.

Action:

Rollback / remove actions beyond the final process date or set the final process date beyond the

latest action.

[APP–6522] National Identifier is invalid

Cause:

You have tried to enter a National Identifier which is invalid within your current legislation.

Action:

Correct the format of the National Identifier

[APP–6523] The Date of Birth is greater than start date

[APP–6524] You must enter sex for an employee.

Cause:

You have tried to enter an employee without entering a value for their sex.

Action:

Enter a value for the employee’s sex.

[APP–6527] The details entered for gender/sex and title are inconsistent.

[APP–6528] Cannot enter. Name exists already

[APP–6537] Termination date must be later than employee’s start date

[APP–6541] Invalid number of parameters passed to routine

[APP–6543] You cannot enter this date if the actual termination date is blank

[APP–6547] You cannot create a classification for &CREDIT_OR_DEBIT costing

Cause:

You are trying to create an element classification rule for a distribution set which does not have

corresponding &CREDIT_OR_DEBIT costing classification rule.

Action:

Remove the selected element classification rule or select an element classification rule which is not

defined as being a &CREDIT_OR_DEBIT costing.

[APP–6552] The date must lie within a time period

[APP–6557] You cannot delete this Organization, Positions exist.

[APP–6558] You cannot delete this Organization, Budget values exist.

[APP–6568] You cannot delete this Organization, Recruit Activities Exist.

[APP–6569] You cannot delete this Organization, it exists in a hierarchy.

[APP–6570] You are not permitted to delete this QuickCode

[APP–6571] You cannot delete this Organization, it is a current Business group.

[APP–6583] You cannot terminate the applicant because assignment changes exist.

Cause:

You are trying to terminate an application when the applicant has future assignment changes at a

date after &DATE.

Action:

You must first delete any future assignment changes which exist beyond the date on which you wnat

this application to end. You can either change the termination date you have entered to a future date

after the applicant’s last assignment change or you can delete the applicant’s assignment changes.

Use DateTrack History on a form that has assignments to see the last assignment change for this

applicant.

[APP–6584] Cannot increase the end date beyond that of the payroll

Cause:

In performing the delete selected the end date of the exchange rate would be greater than that of the

payroll.

Action:

The only way to increase the duration of this exchange is to increase the end date of the payroll

first.

[APP–6585] You must enter a currency

All Legislation specific Elements must have a currency

[APP–6588] Unprocessed nonrecurring entries will be invalidated

[APP–6589] &TYPE nonrecurring entries will be invalidated

[APP–6590] Payroll does not exist for the duration of the assignment

[APP–6591] Assignment actions exist for a payroll being altered

[APP–6592] You cannot insert a row for system defined data

Cause:

You are trying to insert a row where the definition has been created as part of the product.

Action:

Please remove your changes and see your System Administrator.

[APP–6593] Please commit before moving on

[APP–6601] Invalid period type

An unrecognised period type was specified for the payroll.

[APP–6602] You cannot have duplicate balance feed controls

[APP–6603] No periods can be generated for this payroll

No processing periods can be generated for this payroll. The start and end dates of processing

periods must both lie within the start and end dates of their payroll. This problem should only arise

because the start date of the first processing period is before the start date of the payroll. To solve

this, specify a later first period end date.

[APP–6604] The number of years must be greater than zero

The number of years’ worth of processing periods to be generated must be greater than zero. The

form should trap this data error.

[APP–6608] You cannot delete balance feeds with balance type &BALANCE

Balance feeds that feed this balance have been created by balance classifications and balance

control rules. They can be deleted by deleting the balance classification or the balance control rule

for this balance feed

[APP–6609] Hot defaulted values must be mandatory

[APP–6611] This Information type already exists for this Organization.

[APP–6612] Organizations with this classification must have a location

[APP–6614] No time periods exist for this payroll currently

[APP–6616] Hot defaulted values must be 58 characters long or less

[APP–6618] You cannot delete default Person Types

[APP–6619] You cannot delete this person type, its currently in use

[APP–6621] Start Date is after Child Recruitment Activity Start Dates.

Cause:

The Recruitment Activvity Start Date has been changed such that it is now after the Start Date of

one or more Subordinate Recruitment Activities.

Action:

Alter the Start Date so that it is on or before the Start Date of all its Subordinate Recruitment

Activities.

[APP–6622] End Date is before Start Date of Child Recruitment Activity Start Dates.

Cause:

The Recruitment Activity End Date has changed such that it is now before the Start Date of one or

more of its Subordinate Recruitment Activities Start Dates.

[APP–6624] You cannot update the name of an element on a startup record

Some elements have been supplied with your legislation specific installation. You cannot update

the name of these elements.

[APP–6627] The Organization is no longer valid – you may not change this event.

[APP–6628] The location is no longer valid – you may not change this event

[APP–6629] Cannot move status start date. Use Enter Applicant Assignment.

[APP–6632] The input value name must be corrected for the entire input value.

If the input value has been date effectively updated then it is no longer possible to update the name.

This is so it is constant over the entire lifetime of the input value.

[APP–6633] You must correct the db flag over the entire input value

If the input value has been date effectively updated previously it will no longer be possible to do an

update correction on this record. This is to ensure that the Database items flag remain the same

over the entire lifetime of the input value.

[APP–6634] The uom must be corrected over the entire input value

If the input value has previously been date effectively updated then it will no longer be possible to

do a correction for this field. This is to prevent the unit of measure being different over the lifetime

of the input value.

[APP–6636] This person already has an interview at this time. Continue?

[APP–6637] This interview is outside the current period of service. Continue?

[APP–6638] This vacancy name already exists. Please enter a new name.

Cause:

You are trying to insert a new vacancy name or update an existing vacancy name for the

&REQ_NAME requisition but the vacancy name is not unique for this requisition. Vacancy names

must be unique for each requisition name.

Action:

Please enter a new vacancy name or amend your existing vacancy name so that it is unique for this

requisition.

[APP–6639] You cannot delete links which have additional entries

[APP–6640] The vacancy Date From date is outside the Requisition dates.

Cause:

You are trying to insert or update the vacancy Date From date, but it must be within the requisition

dates. It must be on or after the requisiiton Date From date, and before the requisition Date To date,

if there is one.

Action:

Please change your vacancy Date From to a date that is on or after the Requisition Date From date,

and before the requisition Date To date if one exists.

[APP–6641] The date is invalid for a recruitment activity that uses this vacancy

Cause:

You are trying to update the Date From of the vacancy but the vacancy is used by a recruitment

activity and the date you are trying to enter is outside the Start and End Dates of the recruitment

activity.

Action:

Please enter a date that is valid for the recruitment activity that uses this vacancy.

[APP–6642] This date is not valid for the recruiter.

Cause:

You are trying to update the Date From date for the vacancy but the recruiter will be invalid on this

new date since the recruiter’s personal details had not been entered into the system by this date.

Action:

Please enter a date that is valid for the recruiter of this vacancy.

[APP–6643] This date has made the Raised By person invalid.

Cause:

You are trying to update the requisition Date From date but you have changed it to a date which

now means the person in the Raised By field is invalid. The person who raises the requisition must

have personal details in the system at the start of the requisition.

Action:

Please enter a date which does not make the person invalid.

[APP–6644] This requirement has already been entered.

[APP–6645] This operation will cause duplicate Costing Data to be Created.

Cause:

For a given Assignment on a specific day there may only be one occurrence of any Cost Code

Combination. This operation will cause duplicate information to created for one or more days

during the lifetime of the Assignment.

Action:

Rollback the change and ensure that any further operations will not cause duplicate data.

[APP–6646] Job keyflex must be compiled and have Dynamic Inserts set to Yes

[APP–6648] Your formula has failed with an error status

Cause:

Your formula validation for the current entry value has failed with an error status and no associated

user error message.

Action:

Examine your formula or enter a correct value which satisfies your formula validation. For a more

meaningful error message it is always a good idea to supply an error message from within the

formula being executed.

[APP–6656] You may not update this event – the booking will become invalid

[APP–6657] This requirement has already been entered – please enter another.

[APP–6660] You cannot update the event – the internal contact will be invalid

[APP–6661] This product already exists.

[APP–6667] A payroll with this name already exists

[APP–6673] The Business Group is not defined.

Cause:

You tried to run the form when either the Business Group Profile was not set or there was no row in

FINANCIAL_ SYSTEM_PARAMETERS.

Action:

Either create the profile , using a current existing Business Group or add a row to

FINANCIAL_SYSTEM_PARAMETERS with a current Business Group identifier.

[APP–6674] Cannot delete. Assignments exist

[APP–6675] Cannot delete. Element links exist

[APP–6676] Cannot delete. Exchange rates exist

[APP–6678] Bank details needed for magnetic tape payment types

[APP–6679] Cannot delete. Pre payments exist

[APP–6680] Either amount or percentage need to be entered

[APP–6682] This Recruitment Activity cannot be deleted as it is used by Assignments

Cause:

This Recruitment Activity is referenced on an Applicant Assignment record. It therefore cannot be

deleted.

Action:

Remove the reference to the Recruitment Activity from the Assignment.

[APP–6684] Cannot delete. Grade rules exist

[APP–6694] You cannot view the same inquiry twice for the same assignment

[APP–6695] The &PER_TYPE1 &PER_TYPE2 is not a current employee on this start date.

[APP–6697] Position keyflex must be compiled and dynamic inserts set to Yes

[APP–6698] If the element is costed then the Balancing keyflex must be available

It is essential that the balancing keyflex be populated at this stage as it cannot be found at any other

level. If a costing account is specified at any level then there must be a balancing account.

[APP–6699] A Distribution set must be specified for Distributed Links

[APP–6700] Distribution set must be of the same type as the classification

When a distribution set is created all the members of that set will be costed either as a credit or a

debit. The classification of the element must have the same credit or debit type as the element set.

[APP–6701] You are trying to enter more than one grade with the same name

Cause:

For a grade rate, you are trying to enter two or more grade rules with the same name.

Action:

Enter a unique name for your grade rate.

[APP–6703] A rate with this name already exists. Please enter a new name

Cause:

You are trying to enter more than one rate with the same name.

Action:

Enter a unique name for your rate.

[APP–6704] Incorrect format for the rate units

Cause:

You are trying to enter a value in a format inconsistent with the units of the rate.

Action:

Check the value you enter in this field is consistent with the units of the rate. For example, if the

Units are Numbers, ensure you only enter numbers in this field.

[APP–6705] This point already exists for the rate. Enter a different point or query the existing point

and change the information, if required.

[APP–6706] You must enter a pay scale when the rate type is ’Scale’.

[APP–6707] Recurring Entries cannot be indirect only

[APP–6712] Recurring elements cannot be adjustment only

[APP–6713] You cannot purge this element because it is used in an element set.

An element set uses this element.

Action:

Remove the element from the element set ordate–effectively delete on the element instead

[APP–6714] This payment type name already exists.

[APP–6717] Cannot Create Business Group, Payrolls exist.

Cause:

You have tried to create a Business Group and it has Payrolls attached to it.

Action:

Delete the Payrolls or cancel operation.

[APP–6718] Cannot Create Business Group, Assignments exist.

Cause:

You have tried to create a Business Group and it has assignments attached to it.

Action:

Delete the assignments or cancel operatio.

[APP–6719] Cannot Create Business Group, Element links exist.

Cause:

You have tried to create a Business Group and it has element links attached to it.

Action:

Delete the element links or cancel operation.

[APP–6720] Cannot Create Business Group,Budget elements exist.

Cause:

You have tried to create a Business Group and it has Budget Elements attached to it.

Action:

Delete the Budget Elements or cancel the operation.

[APP–6721] Cannot Create Business Group, Events exist.

Cause:

You have tried to create a Business Group and it has events attached to it.

Action:

Delete the events or cancel the operation.

[APP–6722] Cannot Create Business Group, Organization is in a hierarchy.

Cause:

You have tried to create a Business Group and it exists in an organization hierarchy.

Action:

Delete from hierarchy,if possible, or cancel operation.

[APP–6723] Cannot Create Business Group, Recruitmant Activities exist.

Cause:

You have tried to create a Business Group and it has Recruitment activities attached to it.

Action:

Delete the Recruitment activities or cancel the operation.

[APP–6724] Cannot Create Business Group, Security Profiles exist.

Cause:

You have tried to create a Business Group and it has security profiles defined.

Action:

Delete the security profile or cancel the operation.

[APP–6725] Cannot Create Business Group, Vacancies exist.

Cause:

You have tried to create a Business Group and it has vacancies defined.

Action:

Delete the vacancy or cancel the operation.

[APP–6726] Cannot Create Business Group, Positions exist.

Cause:

You have tried to create a Business Group and it has positions defined.

Action:

Delete the positions or cancel the operation.

[APP–6727] The element name must be for the lifetime of the element

If the element name is date effectively updated this will invalidate the database items as these exist

for all time.

Action:

If there is only one date effective record for this element then do a correction rather than a date

effective update. If you wish to do this and there are more than one date effective records then do a

next change delete on this record and do a correction.

[APP–6731] You cannot delete a payroll which has a message line.

Cause:

You are trying to delete a payroll that has a message line (created by a payroll action).

Action:

You must delete the message line that belongs to this payroll before you can delete the payroll from

this form

[APP–6732] You cannot cancel this termination, there are commits outstanding

[APP–6735] Either Final Process Date or Termination Status must be entered

[APP–6737] You cannot view the same inquiry twice for the same assignment set

[APP–6739] This payment method has been used as a default

Cause:

You are trying to delete–next–change or date–effectively–delete a payment method that has been

used as a default payment method by a payroll.

Action:

Remove this as a default payment method for all payrolls.

[APP–6740] You Cannot Delete this link, Hierarchy structure depends upon it.

[APP–6744] You cannot move your Actual Start Date outside the current period

Cause:

You have specified an Actual Start Date which falls outside the period for your current absence

entry.

Action:

If you want to keep your current absence entry then, specify an Actual Start Date which falls

between the current period range: &PERIOD_FROM to &PERIOD_TO. If you require the absence

to fall outside of the period range then, delete and recreate the absence with the new Actual Start

Date.

[APP–6747] The location is not valid for this start date.

[APP–6749] THe payment type chosen does not exist

[APP–6750] You cannot delete a pay–method that is used by a personal pay–method

Cause:

You are trying to delete a payment method that is used by a personal payment method

Action:

You must delete the personal payment method that uses this payment method before you can delete

the payment method from this form

[APP–6751] This assignment has ended. You cannot change the status.

Cause:

You are trying to change the assignment status of an applicant assignment that has already ended.

You cannot therefore change the status of the assignment on this form.

Action:

If you want to change the status of this applicant assignment you must first delete the change that

ended the assignment on the Enter Applicant Assignment form.

[APP–6752] This interview date will invalidate current interviewers.

[APP–6753] You cannot delete security profile organizations from hierarchies

[APP–6758] The Date From must be earlier or the same as the Date To.

Cause:

You are trying to enter a Date From which is later than the Date To you have entered. The Date

From must be earlier or the same as the Date To date value.

Action:

Please enter a new date that is earlier or the same as the date in the Date To field.

[APP–6777] A monetary unit with this name already exists. Enter a new name

Cause:

For a currency, you are trying to enter more than one monetary unit with the same name.

Action:

Enter a unique name for each monetary unit of a currency.

[APP–6779] Please enter a monetary value greater than zero

Cause:

You are trying to enter a value for a monetary unit equal to or less than zero.

Action:

Enter a value greater than zero.

[APP–6780] You cannot delete monetary units used by cash analyses

Cause:

You are trying to delete monetary units which are used by one or more cash analyses.

Action:

If you want to delete this monetary unit, first delete the cash analysis rule. You cannot change the

currency of a cash analysis rule.

[APP–6782] Please commit change before moving.

[APP–6784] Please save your changes before navigating.

[APP–6785] Cannot make this a business group, it is not an Internal Organization.

[APP–6788] Grade keyflex must be compiled and have Dynamic Inserts set to Yes.

[APP–6789] ELement details invalid for this date

[APP–6790] Change of start date will invalidate some absence entries

[APP–6791] This person type change is invalid, the person has no unaccepted assignments.

Cause:

You have tried to change a person type to one which requires that unaccepted assignments exist, and

there are no unaccepted assignments.

Action:

Ensure an unaccepted assignment exists currently or choose a diiferent person type.

[APP–6796] A current period of service already exists, you cannot insert a new one.

[APP–6797] You may not delete this profile – defaulted by a business group

[APP–6802] A period with this name exists in the calendar. Enter a new name

Cause:

You are trying to enter more than one period in a calendar year with the same name.

Action:

Enter a unique name for your period in the calendar year. Periods can have the same name in

different calendar year.

[APP–6807] Invalid date. Please check format is correct and the date exists

Cause:

You are trying to enter a date in a format other than DD–MON.

Action:

Enter the date in the format DD–MON, for example enter August 13 as 13–AUG.

Cause:

You are trying to enter a date which does not exist, for example April 31 or February 29 in a year

other than a leap year.

Action:

Enter a date which exists.

[APP–6809] You must set view all records to Yes for base user

[APP–6815] You Cannot create employee without them having a valid sex defined.

[APP–6820] This sequence already exists for this set. Enter a new sequence.

[APP–6824] Condition must be blank for the first criteria

Cause:

You are trying to define the first criteria with a value in the Condition field. This field must be

blank for the criteria with the lowest sequence number.

Action:

Blank out the Condition field.

[APP–6825] Cannot be less than or equal to lowest sequence number

[APP–6828] Condition can only be blank for the first criteria

[APP–6829] Value/Database Item type must match the Database Item type

[APP–6831] You cannot delete a set, when set criteria exist

[APP–6834] The Requisition Date From now invalidates a vacancy.

Cause:

You are trying to change the requisition Date From but it is now rendering invalid a vacancy that is

within this requisition.

Action:

If you want to change the Requisition Date From then you must change it to a date that will not

invlidate a vacancy that is within this requisition. Alternatively you could delete the vacancy that is

causing the requisition’s new date to be invalid.

[APP–6835] The Requisition Date To now invalidates a vacancy.

Cause:

You are trying to change the requisition Date To but this new date is now rendering invalid a

vacancy that is within this requisition.

Action:

If you want to change the Requisition Date To then you must change it to a date that will not

invlidate a vacancy that is within this requisition. Alternatively you could delete the vacancy that is

causing the requisition’s Date To to be invalid.

[APP–6836] Entries exist between the old and new dates.

[APP–6837] Grade step placements exist between the old and new dates.

[APP–6838] Assignment status changes exist between the old and new dates.

[APP–6839] Assignment changes exist between the old and new dates.

[APP–6840] The new date is in a previous period of service

Cause:

You are trying to enter a Start Date for an employee which overlaps with a previous period of

service for the employee.

[APP–6841] Person changes exist between the old date and the new date.

[APP–6843] The Vacancy Date To date is outside the Requisition dates.

Cause:

You are trying to insert or update the vacancy Date To date but it must be within the requisition

dates. It must be on or before the requisition Date To date, and after the requisition Date From date.

Action:

Please change your vacancy Date To date to a date that is on or before the Requisition Date To date.

[APP–6844] This operation invalidates Personal Payment Methods for the Assignment

Cause:

The operation resulted in an attempt to transfer a payroll (i.e. to change the Payroll at some point

on the Assignment). This is only allowed as long as any Personal Payment Methods for the

Assignment remain valid for the new Payroll. In this case one or more Personal Payment Methods

does not have a Payment Method that is valid for the new Payroll.

Action:

Ensure that all Personal Payment Methods for the Assignment have Payment Methods that are valid

for the new Payroll before attempting to transfer the Payroll.

[APP–6847] Actual date must be greater than &ABS_DATE_FROM and less than

&ABS_DATE_TO.

This is because this is the effective date range of the absence attendance type.

[APP–6851] The Status End Date must be within the duration of the Assignment

Cause:

The Status End Date is either earlier than the Start Date of the Assignment or later than its End

Date.

[APP–6855] Cannot restart, Payroll is processing.

Cause:

The payroll action you are attempting to start is marked as currently processing. This can mean that

you are attempting to restart an already running process, or one that may have errored in a severe

way and appears to be running.

Action:

You may force the process to run by using the FORCE_CONTINUE option, or you may roll back

using the FORCE_UNDO option. However, in any case be sure that the process is not really

running when you attempt this.

[APP–6856] The assignment chunk size you have set is invalid.

Cause:

The value of the CHUNK_SIZE parameter set in the table PAY_ACTION_PARAMETERS is either

less than one or greater than the allowed maximum.

Action:

change the value of the parameter to be positive and less than the maximum. Values in the region of

20 tend to be optimal.

[APP–6857] Payroll Action is currently locked by another process.

Cause:

Interlock Failure. The specified Payroll was locked by another process.

Action:

Wait for the current processing of the Payroll is complete before attempting to run the process

yourself.

[APP–6858] Invalid process name.

Cause:

an invalid process name, i.e. not in the following list has been specified: SLAVE,

FORCE_CONTINUE, RUN, PREPAY, MAGTAPE, CHEQUE, CASH, COSTING, TRANSGL,

ROLLBACK, FORCE_UNDO, RETRY.

Action:

please enter a correct process name from the list above.

[APP–6859] An error has been detected by another process.

Cause:

During processing, the master or another slave process has detected an error, communicated by

setting the Payroll status to ’Error’.

Action:

Examine the error log file and payroll messages to investigate the cause of the error.

[APP–6860] Specified payroll is invalid.

Cause:

The Payroll specified does not exist.

Action:

Enter a valid (existing) Payroll value.

[APP–6862] An invalid number of arguments has been specified for this process.

Cause:

Either too few or too many arguments have been specified for the current process.

Action:

specify the correct number of arguments.

[APP–6863] Must specify Payment Type

Cause:

Payment Type has not been specified for this process.

Action:

re–run process, specifying Payment Type.

[APP–6864] Please specify value for Payroll parameter.

Cause:

a value has not been specified for the Payroll parameter.

Action:

re–run the process, specifying a value for Payroll.

[APP–6865] The output datatype of formula &FORMULA_NAME does not match data type of

input value name &TARGET_INPUT_VALUE_NAME.

Cause:

the data type of an output from the formula &FORMULA_NAME does not match the Unit Of

Measure of the Input Value name &TARGET_INPUT_VALUE_NAME.

Action:

please inspect the data types of the formula returns and the Input Value Unit Of Measure for

inconsistencies.

[APP–6866] Mandatory input value name &INPUT_NAME is missing for Element Type Name

&ELEMENT_NAME.

Cause:

a mandatory Input Value &INPUT_NAME is missing for the Element &ELEMENT_NAME.

Action:

please supply a value for the missing input value.

[APP–6867] An error occurred during formula execution: &FORMULA_ERROR_TEXT

&ORACLE_ERROR_TEXT

[APP–6868] You cannot extend this record

Cause:

You are trying to extend an end date of a record which cannot be extended because it has already

reached the maximum end date of the payroll.

Action:

Extend the end date of the payroll.

[APP–6869] You cannot extend this record

Cause:

You are trying to extend an end date of a record which cannot be extended because there already

exists another valid payment method with the same name starting on the day after the current end

date.

Action:

Remove that valid payment method.

[APP–6871] You cannot delete a formula used by a QuickPaint inquiry

[APP–6872] You cannot delete a formula used by an assignment set

[APP–6873] You cannot delete a formula used by an input value

[APP–6876] This currency has an exchange rate defined at some point in time

Cause:

For a currency, you are trying to define more than one exchange has been defined over all time.

Action:

Enter another currency, or date effectively change the existing record for the currency’s exchange

rate.

[APP–6878] You cannot delete a formula used by a processing rule

[APP–6879] You cannot delete a formula used by a User Column

[APP–6881] Error &SQLERRMC has occurred in table &TABLE_NAME at location &SQL_NO

Cause:

an oracle error has occurred. The failure was reported on table &TABLE_NAME at location

&SQL_NO with the error text &SQLERRMC.

Action:

please contact your Oracle Support Representative.

[APP–6883] The result data type for &RESULT_NAME is not compatible with Input Value.

Cause:

The formula result data type for result name &RESULT_NAME returned from the formula

&FORMULA_NAME is not compatible with the data type of the input value

&TARGET_INPUT_VALUE_NAME, for element &TARGET_ELEMENT_NAME

Action:

please refer to your setup.

[APP–6884] This element does not exist

Cause:

You are trying to select element information on the &DATE_SUPPLIED when the element does not

exist.

Action:

Please change your session date to the effective start date of the element.

[APP–6886] Costing flexfield structure could not be found for this Organization

Cause:

The Classification of business group has been disabled for this Organization.

Action:

Re–query the classification of Business Group and set it’s Enabled flag to Yes.

[APP–6887] You Cannot delete mandatory information.

[APP–6888] You cannot disable the business group of your responsibility.

[APP–6890] Legislation subgroup already exists.

[APP–6891] You cannot insert legislation sub groups.

[APP–6892] You can only update the status field.

[APP–6893] You cannot delete legislation sub groups.

[APP–6898] Projected Hire Date Must be greater than Date Received.

[APP–6899] Your legislation code profile is not defined

Cause:

You are trying to use a startup data logic form without using the ’Define Owner Parameters’

(PAYLODOP) form first.

Action:

Navigate to the ’Define Owner Parameters’ form and enter your legislation details.

[APP–6901] Cannot Cancel Hire. Employee has multiple contracts.

[APP–6904] Adjustment only and Multiply value cannot both be yes.

[APP–6905] Formula Validation must have error flag and no max and min

If the input value is to be validated using a formula then it must have a warning or error flag. This

is so when the input value is entered and the formula fails the system will know how to react to this.

No default, Maximum or Minimum is allowed with formula validation.

[APP–6906] Lookup validation is incorrect

If a lookup type is entered to validate the input value then no maximum, minimum or warning or

error flag can be entered. A default may be entered from the quickcode list.

[APP–6907] Minimum and maximum validation is incorrect

If a minimum or maximum value is entered for an input value then there can be no lookup or

formula validation. A warning or error flag must be entered.

[APP–6908] Warning or Error flag must have other validation with it.

If you have entered the warning or error flag then you must enter some other validation for the

warning or error to fire. This can be either a maximum and/or minimum value or a validation

formula.

[APP–6909] Processing fields cannot be updated if Run results exist

If any processing has been done for this element then you cannot update the Indirect Only flag, the

adjustment only flag or the Termination Processing rule. This is to prevent any processing that has

been done becoming invalid.

[APP–6911] This &TABLE is not valid for the duration of the &BASE_TABLE record

[APP–6912] The processing fields cannot be updated.

If there exist any Formula result rules where this element is the subject of indirect results then the

Indirect only flag, Process in run flag and Termination Processing Rule cannot be updated. If they

were then this could invalidate any processing that has already taken place.

[APP–6913] No new input values can be inserted if there are run results

If any run results exist for this element then no new input values can be inserted. This would mean

that the existing run results would become invalid.

[APP–6914] Next change delete will result in invalid priorities

By effecting a next change delete you have changed the processing priority over a portion of the

lifetime of the element. This has resulted in an indirect result which feeds an element higher in the

processing chain (ie with a lower number) than the one you are changing.

Action:

Change the priority or cancel the next change delete.

[APP–6915] Please delete lower levels in the hierarchy before this level

[APP–6916] You have selected an empty distribution set

The distribution set has no elements available to be distributed over.

Action:

Make sure that the distribution set has some sets available or choose another distribution set.

[APP–6919] You must enter both the increment and frequency

[APP–6921] You can only create one restriction of this type for the specifed form

Cause:

The restriction type you have specified can only be used once for this customized form.

Action:

Either clear the current row or update the previously defined restriction type.

[APP–6922] Failed to open the output file.

The magnetic tape process failed to open the output file required for the transfer of data to magnetic

tape.

[APP–6923] No formula id has been specified.

The magnetic tape process has not received a formula id from the format specifying procedure.

Execution cannot continue.

[APP–6924] An iFormula input not found

An input to the specified formula is missing. The formula cannot be executed unless all inputs are

specified by the format procedure.

[APP–6925] Error while writing to the output file.

An error has occurred while the magnetic tape process has been attempting to write to the output

file for transfer to magnetic tape.

[APP–6926] Maximum return parameters exceeded.

The maximum number of return parameters permitted from a formula by the magnetic tape process

has been exceeded.

[APP–6927] Failed to close the output file.

The magnetic tape process has failed to close the output file for transfer of data to magnetic tape.

[APP–6928] No payment type found.

No payment type has been found when attempting to create a magnetic tape following a payroll run.

[APP–6929] No payroll action found.

No payroll action id has been found when attempting to create a magnetic tape file following a

payroll run.

[APP–6930] Cannot create the output file path.

Failed to create the output path for the requested output file.

[APP–6931] FORMULA CONTEXT NOT FOUND

The magnetic tape process does not have a required context value for execution of the specified

formula. The formula cannot be executed.

[APP–6932] This valid payment method cannot be deleted

Cause:

The valid payment method that you are trying to purge has been used by this payroll as a default

payment method in the past.

Action:

In order to continue ti pusge you need to insure that the payment method has not been use as a

default payment method in the past

[APP–6937] There is not keyflex for source bank

Cause:

A payment method requires source bank details but no keyflex has been constructed for that source

bank country

Action:

Contact your system administrator who can provide you with a keyflex

[APP–6938] Earlier Marked For Retry action exists for this Assignment.

Cause:

At least one Marked For Retry AssignmentAction exists in the past for this Assignment

Action:

Please retry those assignment actions before proceeding.

[APP–6939] The formula’s inputs do not match the elements input values

This is a warning that either: – the formulas inputs do not match the input values of the element, the

data types of the formula’s inputs do not match the data types of the element’s input values or the

formula has not been verified. It is not an error because the formula inputs and/or the element’s

input values may change before a payroll is run when this information will actually be used.

[APP–6939] The formula’s inputs do not match the elements input values

This is a warning that either: – the formulas inputs do not match the input values of the element, the

data types of the formula’s inputs do not match the data types of the element’s input values or the

formula has not been verified. It is not an error because the formula inputs and/or the element’s

input values may change before a payroll is run when this information will actually be used.

[APP–6941] Payroll cannot be nulled – Amendments exist.

Cause:

A payroll cannot be removed or updated if amendments exist for it.

Action:

Remove amendments first.

[APP–6942] Assignment already exists

Cause:

Duplicate Assignment Number entered.

Action:

Enter a different Assignment Number.

[APP–6943] Assignments must be either all Exclusions or all Inclusions

As there are no criteria specified for this Assignment set, Assignment records must be either all

Inclusive or all Exclusive.

[APP–6944] Mixed Inclusions/Exclusions exist for this Set.

Cause:

Amendments exist with combinations of Inclusive/Exclusive attributes.

Action:

Delete the amendments OR change them all to either Exclusive only or Inclusive only.

[APP–6945] You cannot delete a Job for which a recruitment activity exists

[APP–6946] You cannot delete a Job to which an element is linked

[APP–6949] Please set the &PROFILE profile for your responsibility

[APP–6954] ’Multiple Entries Allowed’ cannot be updated while the element is subject to an

update–recurring formula result rule.

This element is subject to ’Update Recurring’Formula result rules, hence the Multiple Entries

Allowed flag cannot be updated.

[APP–6955] You cannot delete a formula used by an Element Type

[APP–6956] Element entry overlaps with another entry of the same type

[APP–6957] Only one balance in a legislation can be the ’Remuneration’ balance

[APP–6958] Defined Balance Types are used by Organization Payment Methods

This error is displayed when : – updating the Remuneration flag from ’Y’ to ’N’ OR – deleting a

Balance Type with Remuneration of ’Y’ AND Organization Payment Methods exist which use any

of the Defined Balance Types of the Balance Type.

[APP–6962] You have already mapped this Accounting flexfield segment

[APP–6965] You cannot delete input values if Salary Bases exist.

[APP–6968] COBRA Benefits exist after the proposed Final Process Date

Cause:

COBRA Coverage Benefits exist after the proposed Final Process Date. These must date effectively

deleted manually before the Employee record can be shutdown.

[APP–6970] Cheque procedure name is mandatory

Cause:

No Cheque Procedure name was specified as a parameter to the Cheque Writer process.

Action:

This is an internal parameter that is usually set up as a hidden parameter. Check this and if missing

reset it.

[APP–6971] Cheque report name is mandatory

Cause:

No report name was entered as a parameter to the Cheque Writer process.

Action:

The report name must be entered as it tells the Cheque Writer process which report to run to

produce a batch of cheques.

[APP–6972] Cheque start number is mandatory

Cause:

No start cheque number was entered for the Cheque Writer process.

Action:

Enter the start number and retry.

[APP–6974] You cannot delete a Time Period used by a COBRA Coverage Enrollment

Cause:

The Time Period that you are attempting to delete is referenced by a COBRA Coverage Enrollment.

Action:

Change the Time Period on the COBRA Coverage Enrollment before attempting to delete this Time

Period.

[APP–6975] Cannot delete this Contact as they have COBRA enrollments

Cause:

The Contact you are attempting to delete has COBRA Coverage Enrollments.

[APP–6980] You must delete the &ROWCOL values first before deleting the &ROWCOL

Cause:

You attempted to remove a row or column from a table while there are values defined for it.

Action:

Remove the values defined for this row or column.

[APP–6981] Cannot delete this person while a contact has COBRA coverage

Cause:

An attempt has been made to delete a person who has contacts with COBRA Coverage. COBRA

Coverage is related to the assignment of the person, and deletion would result in removal of the

assignments.

Action:

Remove the COBRA records for the Contact before deleting the Person.

[APP–6982] You must date effectively delete the values for this row first

Cause:

You attempted to date effectively remove a Row while there were values that were still active.

Action:

Date effectively remove all values for this row and then the row can be date effectively removed.

[APP–6985] Bad parameters passed to the user exit

Cause:

The user exit was called with bad parameters

Action:

Check the parameters passed to the user exit.

[APP–6986] User exit is unable to insert an Assignment Action

Cause:

The user exit in date mode called the PL/SQL procedure hrbaldtm.get_bal_ass_action which was

unable to return an Assignment Action.

Action:

Check the PL/SQL procedure, and the parameters passed to it.

[APP–6987] Cheque Writer report name is null

Cause:

The report name supplied as a parameter to the Cheque Writer process was null.

Action:

Enter a valid report, present in PAY_TOP/srw

[APP–6988] Output file name is invalid

Cause:

The output file name specified as a parameter to the Cheque Writer process was found to be invalid.

Action:

Check filename for length and the use of alphanumeric characters.

[APP–6990] Cheque Writer report failed with an error

Cause:

The report failed to complete and returned an error condition.

Action:

Check the report logfile in PAY_TOP/APPLOUT/xx.lg for reason for the failure.

[APP–6991] Report name is invalid

Cause:

The report name generated by concatenating the path PAY_TOP/srw/<report name> was

invalid.

Action:

Check the process log file and retry with valid name.

[APP–6992] The Pay Date offset must be within the range 0 and &MAX_OFFSET

[APP–6993] The Pay Date offset must be less than zero

[APP–6999] Regular Pay Date lies outside Time Period – No periods created

Cause:

The Regular Pay Date must lie within the Period to which it applies.

[APP–7000] Rollback mode should be RETRY, ROLLBACK or RETROPAY

[APP–7001] Items for assignment process &ASSACTID require rollback Run Results, Message

Lines, Assignment LatestBalances, Person Latest Balances or Element Entries existfor this

assignment process. You must roll these backfirst.

[APP–7002] The Time From must be earlier than the Time To

[APP–7003] The Date To must be equal to or later than the Date From. Enter a new date

[APP–7004] The Date From must be earlier than the Date To. Enter a new date

[APP–7005] You can book an &EMP_OR_APP on an event only once

Cause:

For an event, you are trying to book an &EMP_OR_APP more than once.

Action:

As this &EMP_OR_APP is already booked for this event, either delete the information you have

already entered (using \ Row Erase) or change the &EMP_OR_APP

[APP–7006] Please delete all bookings for this event before deleting the event

Cause:

You are trying to delete an event for which people have been booked at some time.

Action:

If you want to delete this event, first delete all bookings made for the event at any time.

[APP–7007] You must roll back assignment processes before a payroll process.

[APP–7008] Cannot roll back assignment process : &FAILING_ASSACT Unable to roll back this

assignment process because of an interlock. Check whether a sequenced process exists later for this

assignment or the row is locked by another process.

[APP–7009] Future purge prevents assignment process insert

Cause:

You are attempting to insert an assignmentprocess when there exists a purge assignment process in

thefuture.

Action:

Change your effective date.

[APP–7010] Cannot insert assignment process

Cause:

You are attempting to insert an assignmentprocess when there is a future process or an

incompletepast process for this assignment.

Action:

Either roll back future processes, rerunpast processes to completion, or change your effective date.

[APP–7011] Cannot reverse process on this date. The effective date of the reversal cannot be

earlierthan the effective date of the assignment process you arereversing.

[APP–7012] Element is not valid at the effective date of reversal.

[APP–7013] Assignment process has already been reversed

[APP–7014] You cannot update an element entry that was not created by this form This element

entry was created for &CREATOR_MEANING andmust be updated where it was created.

[APP–7015] You cannot delete an entry that was created by another form You must delete this

&CREATOR_MEANING element entry fromthe owning form.

[APP–7016] Your changes will affect element entries. Do you want to continue?

[APP–7017] You cannot correct or delete this salary element entry. To update the entry, either create

a newsalary proposal or perform a dateeffective update. To delete the entry, deletethe salary

proposal or perform a date effective delete.

[APP–7019] Warning: the underlying basis for the Salary Basis has changed. Adjust the salary value

accordingly.

[APP–7021] Your effective date cannot be earlier than &DATE

Cause:

You are trying to change your effective date, before the minimum start date of the parent record.

Action:

Change your effective date to on or after &DATE.

[APP–7022] Your effective date cannot be later than &DATE

Cause:

You are trying to change your effective date, after the maximum end date of the parent record.

Action:

Change your effective date to on or before &DATE.

[APP–7023] Rate values exist – they will be deleted

[APP–7024] The row must be of type &FORMAT

[APP–7026] The assignment does not exist on &DATE

[APP–7027] The element link does not exist on &DATE

[APP–7028] The partial cost code does not exist

[APP–7029] The comment does not exist

[APP–7030] The adjustment is not valid

[APP–7031] The setting of original_entry_id is invalid

[APP–7032] The element entry reason is invalid

[APP–7033] The QuickCode is invalid for &LOOKUP_TYPE

[APP–7034] The type of this payroll process is invalid. The valid typesare Reversal, Balance

Adjustment or Non Tracked.

[APP–7035] This function is not available

Cause:

The function you have requested is not available.

Action:

Contact your system administrator.

[APP–7036] This retropay rule already exists for this retropay set

[APP–7037] This rule will cause a balance to be fed twice by the same input value

[APP–7038] A value already exists for this row and column

[APP–7039] System Error: The #PAY QUICKPAINT exit call has failed

Cause:

The #PAY QUICKPAINT user exit has returned a status of fail. This user exit attempts to create a

file in $PAY_TOP/log and will return a status of fail if it is unable to do so.

Action:

Check that $PAY_TOP/log exists and you have permission to write into it.

[APP–7040] Percentage must be between 0 and 100.

[APP–7041] Priority must be unique within an organizational payment method.

[APP–7042] Invalid value for amount

[APP–7044] The Pay Date must lie between &P_START_DATE and &P_END_DATE

Cause:

The Pay Date does not lie between the Period Start Date, &P_START_DATE, and the Period End

Date &P_END_DATE.

Action:

Change the date so that it lies between &P_START_DATE and &P_END_DATE.

[APP–7046] Dimension is used by a Backpay set

[APP–7047] Balance feeds exist in the future

[APP–7048] Balance feed must exist within lifetime of input value

[APP–7050] You cannot enter this form in GENERIC mode

[APP–7053] Cannot Update REE for assigment &ASSIGNMENT and element

&ELEMENT_NAME.

Reason: The attempt to update the standard REE for assignment number &ASSIGNMENT and

element &ELEMENT_NAME has failed. This is due to the payroll run being asked to perform a

correction on the entry. This is not allowed.

Action:

Either perform the payroll run on a different date or alter the entry to avoid it’s effective start date

being on the date of the payroll run.

[APP–7055] This organization already has a parent in this hierarchy

[APP–7056] The Social Security Number is Invalid

Cause:

You have tried to enter a Social Security Number with an incorrect format. The correct format is

999–99–9999, for example 123–45–6789.

Action:

Correct the format to be as specified above.

[APP–7060] You cannot delete a reason used for an employee absence

[APP–7061] This payroll already exists for the security profile

Cause:

For a security profile, you are trying to enter the same payroll more than once.

Action:

As the payroll already exists for the security profile either erase (using \ Row Erase) the information

you have entered or enter another payroll.

[APP–7062] A security profile with this name already exists. Enter a new name

Cause:

You are trying to enter more than one security profile with the same name.

Action:

Enter a unique name for your security profile.

[APP–7063] This Oracle Username already has a security profile

Cause:

For an Oracle Username, you are trying to define a security profile when a profile already exists for

that username.

Action:

A username can have only one security profile. Rather than inserting a new profile, change the

current profile. Notice that you must run the pyucsl program before the information you save can

be used in &APPLICATION

[APP–7068] An invalid workflow was specified, no navigation available

[APP–7069] The date must be on or after the employees hire date

[APP–7072] This menu option is invalid. There are no customizations with this name.

Cause:

The menu option you have chosen has been defined to pass an incorrect form customization name.

No customizations exist with this name.

Action:

Ask your System Administrator to correct the error.

[APP–7073] &PERSON is not valid for the duration of the absence

[APP–7074] This menu option is invalid. Customization not enabled.

Cause:

The menu option you have chosen has been defined to pass an incorrect form customization name.

The customization is not enabled.

Action:

Ask your System Administrator to correct the error.

[APP–7075] You cannot terminate the only Assignment on this screen.

This is the only assignment for this person. In order to terminate it you must use the Terminate

Assignment Screen.

[APP–7077] You cannot cancel the hire of employees with no previous person type

[APP–7078] Cannot cancel this hire. The employee has future person type changes

[APP–7079] HR is not Installed. You cannot use an HR Responsibilty

[APP–7080] You Cannot cancel application, further Person type Changes exist.

[APP–7081] You Cannot cancel application, no Previous Person type Changes exist.

[APP–7087] At least one year of time periods must exist

[APP–7088] Time periods are used for budgetting

[APP–7089] You may not update the standard link flag to ’Yes’ if entries already exist.

Cause:

Updating the standard link flag to ’Yes’ would cause standard entries to be created for all

assignments matching the link criteria, but there are existing (discretionary) entries, which may

clash with the standard entries.

Action:

Remove any discretionary entries before updating the standard link flag to ’Yes’, or create all

required entries as discretionary ones.

[APP–7092] This action is invalid for the current record

[APP–7093] Cannot Mark Payment Process for Retry.

Cause:

You were attempting to mark for retry a &ACTION_NAME assignment action. This is a Payment

type of action and this is not allowed for this type of action.

Action:

Roll back the entire Payroll Process and re–run.

[APP–7095] Standard Links must have defaults

Cause:

Standard entries cannot be created for the link because it has a mandatory input value with no

default value.

Action:

Ensure a default is present for all mandatory input values, make the offending input value

non–mandatory, or make the link non–standard.

[APP–7096] The effective dates for using this payment method (with)/(as default for) this payroll

must lie within the effective dates of the payment method.

Action:

If the start date of the payroll is before the start date of the payment method you should choose to

update the payroll definition with the payment method.

[APP–7097] Enter a valid &ASS_SET before running the quickpaint report

Cause:

You must enter a valid assinment or assignment set before running the quickpaint report.

[APP–7098] There are no future changes to delete.

Cause:

You may only delete future changes to the input value, and none exists.

Action:

None.:

[APP–7099] This operatiYou cannot perform this operation on system data

Cause:

You are trying to perform an operation on data which was supplied with the product or the

legislation.

Action:

n/a:

[APP–7100] Cannot delete as a Pay Change exists for this employee.

[APP–7101] You cannot delete this person. Addresses exist

Cause:

You are trying to delete an person for whom one or more addresses exist.

Action:

If you want to delete this person, first delete any addresses for the person. Use the next zone on this

form to delete addresses.

[APP–7102] Classification rule already exists for the element’s classification

Cause:

You are trying to insert an element for which a classificatio rule already exists within the set. The

element is already a member of the set.

Action:

Do not add the element to the set.

[APP–7103] Function cannot be performed as insufficient criteria has been entered

[APP–7104] The location is not valid for the date specified.

Cause:

You have entered a location which is not valid on the date entered. Remedy: Enter a valid location

or change the date.

[APP–7105] This application is already terminated.

Cause:

You are trying to terminate this application but the application is already terminated.

Action:

Reverse the termination and then re–terminate the application.

[APP–7106] This Unit has already been defined

[APP–7109] Global Values should be preceeded by ’G_’ .

[APP–7111] Are you sure there are many units in this Form

[APP–7112] You cannot enter a placement for this assignment because there is no grade scale

defined for its grade.

[APP–7114] Oracle error &ERRNO in &ROUTINE

[APP–7115] Error scanning button number (&TEXT) in &ROUTINE

[APP–7116] Could not access navigation information in &ROUTINE.

[APP–7117] Could not convert string &STR to number in &ROUTINE.

[APP–7119] Call to &CALL failed from &ROUTINE

[APP–7120] Could not obtain name of current form.

[APP–7122] Future person changes exist. You cannot cancel the termination

Cause:

You are trying to cancel a termination when there are future person type changes.

Action:

You must undo all person type changes that exist after the termination date before you can cancel

the termination from this form.

[APP–7124] You may not enter more than 15 input values for an element.

Cause:

You have entered too many input values for a single element.

Action:

Do not enter so many input values.

[APP–7125] This employee already has a primary contact

Cause:

You are trying to enter more than one primary contact for an employee.

Action:

Enter ’No’ in the Primary Contact field and save your contact information.

[APP–7127] You have entered a duplicate sequence number

[APP–7128] This balance feed control already exists.

Cause:

You have attempted to duplicate a balance feed control which is already defined.

Action:

Remove the offending record.

[APP–7129] Phase &PHASE_NUMBER will cause exceptions to be raised.

[APP–7130] You cannot say ’yes’ to all the view options if the ’view all records’ option is not

selected. Please say ’No’ to one or more of the other ’view’ options

Only the base table Oracle user can see all the records.

[APP–7133] A valid balance must be given

[APP–7134] You cannot delete links which have entries within the deletion period.

Cause:

You have attempted to shut down a link whichhas entries within the deletion period you have

selected.

Action:

Delete all entries starting after the session date and try again or do not shut down the link.

[APP–7135] Delete result rules before updating formula.

Cause:

You have attempted to update a formula and this will invalidate result rules that fall within the

update period.

Action:

Delete all result rules for the period of the update before trying again.

[APP–7136] Please enter the cost as a number.

[APP–7137] You Cannot Delete Statuses in Startup or Generic mode

[APP–7138] You cannot query a detail record when there is no master record.

[APP–7139] You cannot CORRECT the first assignment status

Cause:

You attempted to modify the status to one with a system status value of something other than

’ACTIVE_ASSIGN’. Only ’ACTIVE_ASSIGN’ is permissible for the first occurrence of each

employee assignment.

[APP–7143] You cannot enter Actual Start Time without Actual Start Date

[APP–7144] A person must have a primary address

[APP–7145] You must enter Start and End Times if you have entered Duration Hours

[APP–7147] This replacement will be terminated before the Actual Start Date

Cause:

You are trying to enter a replacement whose employment is due to be terminated before this absence

or attendance occurs.

Action:

Choose another replacement.

[APP–7148] Warning: Replacement’s employment is terminated before absence is over

Information: You have entered a replacement whose employment is due to be terminated before the

last day of this period of absence.

[APP–7151] FORM_MODE parameter not set

You must set up the FORM_MODE parameter

Cause:

The FORM_MODE parameter is required but has not been set for this form

Action:

Please see your system administrator.

[APP–7152] &G_NAME cannot be Mandatory Input and Output for same unit

[APP–7153] &G_GLOBAL is already inserted as &pram – Duplicate not allowed

[APP–7154] Cannot delete &G_GLOBAL as it is used in Context Rules

[APP–7155] The HR object is invalid

Cause:

The HR object which is attempted to be locked is inconsistent with the corresponding object in the

HR Schema.

Action:

Retry the action with the correct object version number.

[APP–7165] The current row is locked

Cause:

You are trying to lock a row in the &TABLE_NAME table which is currently being locked by

another user.

Action:

Re–query and attempt to lock the row again.

[APP–7166] Constraint violation against the &TABLE_NAME table

Cause:

The check constraint &CONSTRAINT_NAME has been violated against the &TABLE_NAME

table.

Action:

Examine the arguments to establish the offending column violation.

[APP–7167] Cannot delete unit &F_NAME – Incompatibility Rules exist

[APP–7168] Cannot delete unit &F_NAME – as it is used in Navigation Nodes

[APP–7172] The Actual End Date and Time must be after the Start Date and Time

[APP–7174] Referential Error

Cause:

Referential Integrity error – &node exists in NAVIGATION NODE USAGES

Action:

You must delete &node from NAVIGATION NODE USAGES

[APP–7176] You cannot delete a type used for an employee absence

[APP–7177] You cannot navigate to another zone when QuickPay changes to this or other records

have not been saved. Do you want to commit your changes?

[APP–7178] You cannot start or retry a process when QuickPay change to this or other records have

not been saved. Do you want to commit your changes?

[APP–7179] DateTrack update not allowed for a record which started today

Cause:

You have tried to complete a date effective update for the record which starts on the same day.

Action:

Change your DateTrack mode to correction or alter your effective date.

[APP–7180] No DateTrack row found in table &TABLE_NAME as of &SESSION_DATE

Cause:

For the effective date of &SESSION_DATE no corresponding row was found in the table

&TABLE_NAME

Action:

Please ensure that the table name, primary key name and value have been correctly specified.

[APP–7181] DateTrack has detected overlapping rows in the table &TABLE_NAME

Cause:

DateTrack has detected that overlapping rows exist on the DateTracked table &TABLE_NAME as

of the effective date &SESSION_DATE

Action:

Please call your local support representative quoting the error message number and the following

details: Table Name : &TABLE_NAME Effective date : &SESSION_DATE Primary Key Value:

&PRIMARY_VALUE:

[APP–7182] No DateTrack row found in table &TABLE_NAME

[APP–7183] Cannot perform the mode &DT_MODE when future rows do not exist

Cause:

The DateTrack mode &DT_MODE cannot be perform if no future rows exist after the current

effective date.

Action:

Either perform a DateTrack update operation or clear your changes.

[APP–7184] The DateTrack mode &DT_MODE is unknown

Cause:

The DateTrack mode &DT_MODE supplied to the DateTrack Application Program Interface

(DT_Api) is unknown therefore, is invalid.

Action:

Please specify a valid DateTrack mode.

[APP–7185] DateTrack delete not allowed

Cause:

You cannot perform the DateTrack deleteoperation because your effective date is set to the

lastdatetracked row.

Action:

Clear your changes and move your currenteffective date back in time.

[APP–7186] Please specify value for Earned Date parameter.

[APP–7187] You cannot extend the end date using the DateTrack mode &DT_MODE

Cause:

You are trying to extend the end date of the current record by using the DateTrack mode

&DT_MODE which cannot be extended.

Action:

Clear your changes

[APP–7188] You cannot extend your end date past the end of time

Cause:

You are currently trying to extend your end date past the end of time.

Action:

Clear your changes.

[APP–7192] You cannot terminate this employee, future assignment changes exist

Cause:

You are trying to terminate an employee for whom you have entered assignment changes in the

future, although this employee does not have element entries in the future.

Action:

If you want to terminate this employee, first delete all assignment changes scheduled in the future.

[APP–7194] You have not entered a top node for this task flow

[APP–7195] This node cannot be the top node of a task flow

This node cannot be the top node of a task flow. It must be passed context information from another

node.

[APP–7196] Sequence numbers of all nodes following the same node must be unique

[APP–7197] This sequence number does not correspond to a button position

[APP–7198] There may only be one top node in a task flow

[APP–7199] This node already exists in this task flow

[APP–7201] Cannot perform a delete with child rows existing in the future

Cause:

You are attempting to do a date effective delete where child rows will exist in the future.

Action:

Clear your changes and remove any future child rows.

[APP–7202] Cannot select comment text

Cause:

The comment text does not exist for the specified comment identifier.

Action:

Please contact your local support representative.

[APP–7203] The datetrack update mode supplied is invalid

Cause:

An invalid datetrack update mode has been passed to an API which is datetracked

Action:

Specify a correct datetrack update mode when calling the required datetrack API.

[APP–7204] The datetrack delete mode supplied is invalid

Cause:

An invalid datetrack delete mode has been passed to an API which is datetracked.

Action:

Specify a correct datetrack delete mode when calling the required datetrack API.

[APP–7207] The mandatory argument &ARGUMENT value cannot be null

Cause:

The mandatory argument &ARGUMENT has either not been specified or has been explicitly set to

null in the API &API_NAME .

Action:

Either specify a value for the &ARGUMENT argument which is not null or contact your local

support representative.

[APP–7208] The business group specified is invalid

Cause:

You have specified an incorrect business group identifier or name.

Action:

Correct the business group value or call your local support represenative.

[APP–7209] The lookup code you have specified is invalid

Cause:

You have specified a lookup code which is invalid.

Action:

Respecify the lookup code.

[APP–7210] The attribute &ARGMENT cannot be updated

Cause:

The attribute &ARGUMENT cannot be updated with the API &API_NAME because it has already

be set.

Action:

Respecify the attribute value for &ARGUMENT or contact your local support representative.

[APP–7211] You cannot perform a DateTrack update where rows exist in the future

Cause:

The DateTrack update operation cannot be performed where rows exist in the future.

Action:

Consider performing a Datetrack Change Insert or Override operation.

[APP–7212] Cannot rollback payroll of type &ACTION_NAME

Reason: You have attempted to roll back a Payroll Action of type &ACTION_NAME. This is not

allowed.

Action:

Do not attempt to roll this back.

[APP–7213] Error return from Fast Formula in the wrong format.

[APP–7214] You must have one and only one default assignment status for each personnel system

status

[APP–7215] You cannot perform a delete operation when child rows exist

Cause:

You are doing a delete operation where dependant child rows exist for &TABLE_NAME .

Action:

Delete the dependant child rows in &TABLE_NAME before attempting to delete this row.

[APP–7216] The datetrack update has violated integrity rules

Cause:

The datetrack update operation has cause an integrity error for &TABLE_NAME

Action:

Contact your local support representaive.

[APP–7217] Invalid return name from Fast Formula

[APP–7218] Could not map onto costing flexfield

[APP–7220] The primary key specified is invalid

Cause:

The primary key values specified are invalid and do not exist in the schema.

Action:

Check the primary key values before attempting to carry out the operation again.

[APP–7224] No assignment process.

You have tried to include an element entry in QuickPay for an assignment process that does not

exist. The p_rec.assignment_action_id (or p_assignment_action_id) argument has been set to an

incorrect value.

[APP–7227] You must commit outstanding changes before deleting this person

[APP–7228] You can only have one budget value for a period

[APP–7230] Invalid payroll process type.

You have tried to include an element entry in QuickPay for an invalid type of payroll process. The

payroll process corresponding to the assignment process (p_rec.assignment_action_id) must be of

the type QuickPay Run.

[APP–7231] Please enter a unique combination for the Budget Element record

[APP–7232] No element entry.

You have tried to include a non–existent element entry for QuickPay. The p_rec.element_entry_id

(or element_entry_id) argument has been set to an incorrect value.

[APP–7233] Element entry not date effective.

You have tried to include an element entry for QuickPay that does not exist at Date Earned. You

can only include element entries that are date effective at this date.

[APP–7234] Element entry does not match assignment.

You have tried to include an element entry for QuickPay that is not for the same assignment as

defined for the QuickPay run.

[APP–7236] Element cannot be processed.

You have tried to include an element entry for QuickPay for an element that cannot be processed in

a payroll run.

[APP–7237] Wrong element category.

You have tried to include an element entry in a QuickPay run that can only be used for a balance

adjustment, replacement adjustment or additive adjustment.

[APP–7238] Double entry.

You have tried to include the same element entry more than once in the QuickPay run.

[APP–7239] Status change required.

You have tried to include or exclude an element entry for a QuickPay run that has completed

successfully. To do this you must change the assignment process status to Marked for Retry.

[APP–7240] Run in progress.

You have tried to include or exclude an element entry from a QuickPay run while the run is

processing.

[APP–7241] Run in progress.

You have tried to update a field or to delete the QuickPay run while the run is processing.

[APP–7242] No payroll component.

You have tried to define QuickPay for an assignment that has no payroll component valid at Date

Paid. For the run to process, you must create a payroll component that is valid at this date.

[APP–7243] Effective date invalid.

You cannot change to this effective date, because the current assignment is not on a payroll as of the

new date.

[APP–7244] Wrong assignment.

You have tried to define QuickPay for an assignment that is to a different Business Group, or does

not exist at Date Paid.

[APP–7245] Wrong consolidation set.

You have tried to define QuickPay for a consolidation set that does not exist, or does not exist in the

Business Group defined for the run.

[APP–7246] No payroll component.

You have tried to define QuickPay for an assignment that has no payroll component defined at Date

Paid.

[APP–7247] No payroll period.

You have tried to define QuickPay for an assignment that has no payroll period defined at Date

Paid.

[APP–7248] You cannot delete a &STRUCTURE defined in a security profile

[APP–7249] No payroll component.

You have tried to define QuickPay for an assignment that has no payroll component defined at Date

Earned.

[APP–7250] No payroll period.

You have tried to define QuickPay for an assignment that has no payroll period defined at Date

Earned.

[APP–7251] Different payroll components.

You have tried to define QuickPay for an assignment that has different payroll components for Date

Earned and Date Paid. The assignment must be to the same payroll for both dates.

[APP–7252] Wrong status update.

You have tried to enter an invalid status for a completed QuickPay run. You can only update a

completed assignment process status to Marked for Retry.

[APP–7253] Cannot alter flag.

You have tried to alter the Regular/Supplemental flag for a completed QuickPay run. You can only

change this flag before a run commences.

[APP–7254] Wrong parameter setting.

For US Business Groups the payroll process legislative_parameters must be set to ’R’ (for Regular)

or ’S’ (for Supplemental).

[APP–7255] Parameters attribute must be null.

For this legislation, you must set the payroll process legislative_parameters attribute to null.

[APP–7256] Payroll process still running.

You have tried to update or delete a QuickPay Pre–payment while the corresponding payroll process

has a status of Processing.

[APP–7257] Invalid QuickPay Pre–payment.

You have tried to create a QuickPay Pre–payment for a target_payroll_action_id that does not exist,

or for a QuickPay run that does not have the status Complete.

[APP–7258] Pre–payment already exists for this QuickPay run.

You cannot create more than one QuickPay Pre–payment for the same run.

[APP–7259] Pre–payment invalid because of batch process.

You cannot create a QuickPay Pre–payment if the QuickPay run has been or will be processed by

the batch Pre–payments process.

[APP–7260] Wrong Pre–payment attributes.

The business_group and date_paid attributes for the QuickPay Pre–payment must have the same

values as the business_group and date_paid for the QuickPay run.

[APP–7261] Invalid Override Payment Method.

The Override Payment Method you have tried to enter does not exist as at Date Paid, or is not in the

same Business Group as the QuickPay Pre–payment.

[APP–7262] Wrong payment category.

You cannot enter the payment category Magnetic Transfer for the QuickPay Pre–payment

org_payment_method_id.

[APP–7263] Choose a QuickPay run.

Query a QuickPay process with a status of Complete before trying to define or process a QuickPay

Pre–payment.

[APP–7264] Request is still waiting or running.

You cannot update or delete a QuickPay definition when a request is still running or waiting to run

on the AOL concurrent manager. You may need to contact your system administrator to resolve this

problem. Please quote AOL concurrent request_id &REQUEST_ID.

[APP–7265] Query and repeat operation.

You have attempted to issue a Start or Retry operation, after querying this record but before another

operation has finished. You need to query this record and issue the operation again.

[APP–7266] No request submitted.

You have attempted to wait for a request to finish, when no request has been submitted for this

QuickPay Run or QuickPay Pre–payment.

[APP–7267] Operation not started.

You have requested to Start or Retry a QuickPay operation. Your request has been submitted but

has not started to run yet. You may need to contact your system administrator to resolve this

problem. Quote AOL concurrent manager request_id &REQUEST_ID. Possible causes are the

AOL concurrent manager is not running or the concurrent manager is too busy to run your request.

Once this request has finished you will need to query this record to see the most up–to–date status.

[APP–7268] Operation started but not finished.

You have requested to Start or Retry a QuickPay operation. Your request has been submitted and

has started to run on the AOL concurrent manager. You may need to contact your system

administrator to resolve this problem. Quote AOL concurrent manager request_id &REQUEST_ID.

Once this request has finished you will need to query this record to see the most up–to–date status.

[APP–7269] Too many errors encountered while processing

[APP–7270] This legislation has no bank keyflex structure defined

You cannot create payment methods for this legislation, because no bank keyflex structure has been

defined for it. Your System Administrator should install the keyflex structure by loading the startup

data for your current legislation.

[APP–7271] Database item requires context &CONTEXT_NAME to be set

[APP–7272] No rows returned for DB item : &DATABASE_NAME

[APP–7273] Database item returned more than 1 row

[APP–7274] Unable to execute package : &EXPIRY_CODE

[APP–7275] Failed in Expiry Checking code : &ERROR_MESSAGE

[APP–7276] Dynamic SQL for DB item failed : &ERROR_MESSAGE

[APP–7277] Cost allocation structure is null.

[APP–7278] No balence keyflex id given.

[APP–7279] No set Id exists for distributed costs

[APP–7280] Unknown cost type.

[APP–7281] Costing sum for assignment &ASSIGN not 100 percent

[APP–7282] No suspense account in pay_payrolls_f table

[APP–7283] Unable to find distribution member

[APP–7284] Element Entry already processed.

You have tried to include an element entry in a QuickPay run that has already been processed. It is

either a processed non–recurring entry or a processed recurring, additional or override entry.

[APP–7285] You have tried to start a QuickPay Run process without saving a QuickPay definition.

Do you want to commit this default definition, use the automatically included element entries and

start the Run process?

[APP–7286] Invalid Date Paid.

The QuickPay Date Paid must be the same as a payroll period regular payment date.

[APP–7287] You have tried to start a QuickPay Pre–payment process without saving a QuickPay

definition. Do you want to commit this default definition and start the Pre–payment process?

[APP–7288] Invalid Date Earned.

You must use the default value for the QuickPay Run Date Earned, when using GB legislation.

[APP–7289] You cannot navigate to the Element Selection zone, without saving a QuickPay

definition. Do you want to commit this default definition?

[APP–7290] You cannot make any changes on this form

This is because there is no period defined for your payroll at your effective date. Change your

effective date or increase the number of years defined for the payroll.

[APP–7291] QuickPay Pre–payment is being defined.

You cannot retry the QuickPay Run while defining a QuickPay Pre–payment.

[APP–7292] You can only delete the latest salary administration record

[APP–7293] You cannot create new salary proposals when future approvals exist

[APP–7294] You may only have one unapproved proposal at any time.

[APP–7295] Please save your salary administration changes first

[APP–7296] Invalid value.

This version of the API does not support the &ARG_NAME argument being set to &ARG_VALUE.

[APP–7297] Invalid value.

This version of the API only supports the &ARG_NAME being set to &ARG_ONLY.

[APP–7298] This person does not exist.

[APP–7299] This address type does not exist.

The value you have entered for the address type does not exist, or has been disabled, or is not

currently date effective for the current address.

[APP–7300] Non–existent country.

This country does not exist in the system.

[APP–7301] Date To must be later than or equal to Date From.

[APP–7302] A non Primary Address cannot exist without a corresponding Primary Address. The

Date change has left a Non Primary Address without a corresponding Primary Address.

[APP–7302] A non Primary Address cannot exist without a corresponding Primary Address. The

Date change has left a Non Primary Address without a corresponding Primary Address.

[APP–7303] Date From must be earlier than or equal to Date To.

[APP–7304] No address format has been defined for the style you have chosen.

[APP–7306] Postal Code cannot be longer than 8 characters

[APP–7307] The value for Region_1 is invalid.

The value you have entered for Region_1 does not exist, or has been disabled, or is linked to a non

GB address style.

[APP–7308] Cannot delete this Primary Address.

You cannot delete a person’s primary address unless you first delete all their date–corresponding

non–primary addresses.

[APP–7309] Invalid start date

You have tried to enter a position start date which is outside the active date range for the

organization.

[APP–7310] Invalid Rate Type

You have tried to enter an invalid rate type for a grade rule. The rate type you enter must be ’Spinal

Point’ or ’Grade’.

[APP–7311] Invalid Grade

You have linked the grade rule to a grade that has not been defined , or does not exist as of the

effective date

[APP–7312] Invalid spinal point

You have linked the grade rule to a spinal point that has not been defined.

[APP–7313] This grade rule combination already exists as of effective date

[APP–7314] Non–existent pay rate

No pay rate with this ID exists in the system

[APP–7315] Invalid pay rate combination

The combination of rate id and rate type has not been defined in the system.

[APP–7316] Invalid value

The value you have entered is outside the ’minimum’ or ’maximum’ range.

[APP–7318] Invalid grade sequence

The value you have entered for the grade sequence is not defined in the system.

[APP–7319] Invalid spinal point sequence

The value you have entered for the spinal point sequence is not defined in the system.

[APP–7320] Please select a letter request before generating the mail merge file

[APP–7321] Please specify a mail merge file to generate

[APP–7323] At this date the location you chose is not active

You have tried to enter a position start date which is after the date on which the location became

inactive.

[APP–7324] Attribute must not be entered

The attribute &ARGUMENT must not be entered for this address style.

[APP–7325] Invalid Primary Flag

Primary Flag must be ’Y’ or ’N’

[APP–7326] Element entries currently reference this benefit contribution record

[APP–7327] A Primary Address already exists in the date range. There can only be one Primary

Address on a given date. Check the addresses and make one address the Primary or Main Address.

[APP–7327] Primary address already exists in date range.

[APP–7328] Cannot find Recurring Entry to Update.

An attempt was made to process an Update Recurring Entry Formula Result Rule for Input Value

&IV_NAME of Element &ELEMENT_NAME. The updated value would have been

&UPDATED_VALUE. However, no entry could be found to update. Most likely cause is that the

entry does not exist for assignment at date paid.

Action:

check that the assignment has an entry for Element &ELEMENT_NAME at date paid.

[APP–7329] Cannot find Recurring Entry to Stop

An attempt was made to process a Stop Recurring Entry Formula Result for Element Name

&ELEMENT_NAME. However, no entry could be found to stop. Most likely cause is that no entry

exists for assignment as of Date Paid. This may be because the entry has already been stopped.

Action:

check that there is an entry for assignment for Element &ELEMENT_NAME at Date Paid.

[APP–7330] You Cannot delete this record, element links exist.

[APP–7331] You cannot delete this Organization , Payrolls exist.

[APP–7333] You cannot delete this Organization , Assignments exist.

[APP–7334] You cannot delete this Organization, Events exist.

[APP–7335] You cannot delete this Organization, Budget Elements exist

[APP–7336] You cannot delete this Organization, Recruitment Activities exist.

[APP–7337] You cannot delete this Organization , vacancies exist.

[APP–7339] You cannot delete this Organizaion, exists in Security Profile.

[APP–7340] The assignment is terminated as of this review date

[APP–7341] You cannot delete a formula used to generate magnetic tapes

[APP–7342] Cannot create a reporting Establishment without a location

[APP–7343] You cannot change batch totals when the batch status is set to Ready. First set the batch

status to Hold.

[APP–7344] Unknown context &CONTEXT_NAME required by formula &FORMULA_NAME

Cause:

The formula &FORMULA_NAME requires a value to be supplied for context

&CONTEXT_NAME. However, no such value could be found in the udca User Context area.

Action:

Please check that you have supplied values for all the relevant contexts to the udca structure and

that the set flag has been set to true in the structure.

[APP–7345] Your software is out of date. Ask your system administrator to upgrade the file

&filename.

The latest version of the file &filename is &latest_version. You are using version number

&old_version. Failure to upgrade may mean that your application does not work correctly or you

may not take advantage of new features. Ask your system administrator to upgrade this file.

[APP–7347] Invalid organization payment method

This organization payment method has not been defined for the payment type

[APP–7348] Non–existent assignment

No assignment with this ID exists in the system on the current effective date

[APP–7349] Amount not enterable

You cannot enter an amount

[APP–7350] This letter request already exists. Please reenter

Cause:

You are trying to enter more than one letter request with the same letter name, date and automatic or

manual status.

Action:

As this letter request already exists, either change the letter request details or erase (using \ Row

Erase) the information you have entered.

[APP–7351] This letter has no letter request lines

[APP–7352] This person is already included in this letter request

Cause:

For a letter request, you are trying to enter the same person more than once.

Action:

As this person already exists for the letter request either change the person or erase (using \ Row

Erase) the information you have entered.

[APP–7354] Percentage error

The percentage must be 100 for non–remunerative balance types

[APP–7355] Amount less than 0

Enter 0 or positive numbers only

[APP–7356] External account not enterable

Only enter an external account for magnetic payments

[APP–7357] Priority required

The priority of the personal payment method must be entered

[APP–7358] Priority out of range

The value for Priority must be between 1 and 99 for remunerative balance types

[APP–7359] Priority must be 1 for non–remunerative balance types

[APP–7360] Delete not allowed

You cannot delete a personal payment method if pre–payments exist for future payroll processes

[APP–7361] Negative price

Price of car cannot be negative

[APP–7362] A surcharge with this name already exists for this state

[APP–7363] A surcharge with this formula position already exists for this state

[APP–7364] You must enter the first formula position first

[APP–7365] You must delete the second formula position before the first

[APP–7366] Invalid mileage band

Invalid mileage band

[APP–7367] Invalid car registration date

Registration date is invalid

[APP–7368] Invalid fuel scale charge

Invalid fuel scale charge

[APP–7369] Invalid annual payment

Invalid amount for annual payment for private use of company car

[APP–7370] Invalid payroll

This payroll does not exist at all, or is not completely within the assignment’s date range.

[APP–7371] Invalid business group for grade.

The business group entered is invalid for the grade defined for this assignment.

[APP–7372] Invalid business group for assignment status type.

The business group entered is invalid for the assignment status type defined for this assignment.

[APP–7373] Invalid business group for payroll.

The business group entered is invalid for the payroll defined for this assignment.

[APP–7374] Invalid business group for person.

The business group entered is invalid for the person linked to this assignment.

[APP–7375] Invalid business group for special ceiling step.

The business group entered is invalid for the special ceiling step defined for this assignment.

[APP–7376] Invalid business group for organization.

The business group entered is invalid for the organization to which the assignment is linked.

[APP–7378] Date of birth required.

You cannot enter a payroll component when no date of birth has been defined for this person.

[APP–7379] Invalid special ceiling step

This special ceiling step does not exist at all, or is not completely within the assignment’s date

range.

[APP–7380] Invalid special ceiling step for grade.

The special ceiling step entered is invalid for the grade specified for the assignment.

[APP–7381] Value for special ceiling step too high

The special ceiling step value is greater than the spinal point placement defined for the assignment.

[APP–7382] The location you entered does not exist or is flagged as inactive.

[APP–7383] Invalid soft coded keyflex value.

[APP–7384] Soft coded keyflex link problem.

The soft coded keyflex value cannot be linked to the legislation defined for the assignment’s busines

group.

[APP–7385] Invalid people group

This people group does not exist at all, or is not completely within the assignment’s date range.

[APP–7386] People group link problem.

The people group value entered is not linked to the people group structure defined for the

assignment’s business group.

[APP–7387] Normal hours value required.

The value for frequency cannot be entered without a corresponding value for normal hours.

[APP–7388] You have entered an invalid frequency value.

[APP–7389] Invalid organization. This organization does not exist at all, or is not completely

within the assignment’s date range.

[APP–7390] An employee number is required for the employee

[APP–7391] Invalid period of service

This period of service does not exist at all, or is not completely within the assignment’s date range.

[APP–7392] Delete not allowed

You cannot delete an assignment unless there is at least one contiguous primary assignment running

either to the end of time or to the end of the person’s period of service.

[APP–7393] Invalid grade

This grade does not exist at all, or is not completely within the assignment’s date range.

[APP–7396] Frequency value required.

The value for frequency must be entered if a corresponding value exists for normal hours.

[APP–7399] You cannot delete a non primary assignment that is changed to primary in the future.

[APP–7400] You cannot delete an assignment that has events linked to it.

[APP–7401] You cannot delete an assignment that has letter requests linked to it.

[APP–7402] You cannot delete an assignment that has cost allocations linked to it.

[APP–7403] You cannot delete an assignment that has payroll actions linked to it.

[APP–7404] You cannot delete an assignment that has personal payment methods linked to it.

[APP–7405] You cannot delete an assignment that has COBRA coverage enrollments linked to it.

[APP–7406] You cannot delete an assignment that has COBRA coverage benefits linked to it.

[APP–7407] You cannot delete an assignment that has secondary assignment statuses linked to it.

[APP–7408] This position already exists in the hierarchy

[APP–7410] You cannot delete an assignment that has assignment set amendments linked to it.

[APP–7412] You cannot delete an assignment if it is terminated in the future.

[APP–7413] The new amount is outside the range defined at the link level

[APP–7414] The new amount is outside the range defined at the element level

[APP–7415] A position with this name already exists. Please enter a new name

Cause:

You are trying to enter more than one position with the same name.

Action:

Enter a unique name for your position.

[APP–7416] You cannot delete a position that is within a hierarchy

Cause:

You are trying to delete a position whilst the position is part of a position hierarchy.

Action:

If you want to delete this position, first remove it from the position hierarchy to which it currently

belongs. Use \ Navigate Define Work Position Hierarchy, the Define Position Hierarchy form, to

delete positions from a hierarchy.

[APP–7417] You cannot delete a position to which employees are assigned

Cause:

You are trying to delete a position to which employees are currently assigned.

Action:

If you want to delete this position, first assign the employees to another position using \ Navigate

Employee Assignment Enter, the Enter Employee Assignment form.

[APP–7418] You cannot delete parent positions when subordinates exist

Cause:

You are trying to delete the parent position of the current position, when the current position has

subordinate positions.

Action:

The current position is the link between the parent position and the subordinate positions. You

cannot delete this link between the positions.

Action:

If you want to delete the current position, first remove any subordinates from the hierarchy using \

Navigate Define Work Position Hierarchy, the Define Position Hierarchy form.

[APP–7419] This parent must already exist in the hierarchy

Cause:

You are trying to enter a parent position for the current position when the parent position does not

exist in the position hierarchy.

Action:

Choose a parent for the current position from the positions which exist within the hierarchy.

Action:

Enter the parent position you require into the current position hierarchy using \ Navigate Define

Work Position Hierarchy, the Define Position Hierarchy form.

[APP–7420] This parent already exists in the hierarchy

Cause:

You are trying to enter a parent position for the current position when the parent already exists in the

position hierarchy.

Action:

A position may appear only once in a position hierarchy. If you want the current position to be

below this parent, find the parent in the hierarchy and enter the current position below.

[APP–7421] This parent already exists in the hierarchy below the position

Cause:

You are trying to enter a parent position for the current position when this position is currently a

subordinate of the current position.

Action:

If the parent position you chose is the parent you want, remove the parent from lower in the

hierarchy and enter it here.

Action:

If the parent position you chose is in the right place in the hierarchy; enter a new parent for the

position.

Action:

If you want the parent position you chose to remain in its current place in the hierarchy, BUT you

want to show a hierarchical relationship between the current position and the parent, define a new

position hierarchy.

[APP–7423] Invalid ID

The &ARGUMENT value does not exist as of the effective date.

[APP–7424] At this date the job you chose is not active

Cause:

You entered a position start date earlier than the start date of the job you chose in the Position zone.

Action:

Enter a position start date later than the start date of the job you chose in the Position zone.

[APP–7425] You must commit outstanding changes before setting state to Ready.

[APP–7426] Employees age must be between &MIN and &MAX, please re–enter Birth date.

[APP–7427] Invalid assignment type.

The assignment type must be set to ’E’(Employee) or ’A’(Applicant).

[APP–7428] Invalid primary flag.

The primary flag must be set to ’Y’ or ’N’.

[APP–7429] The manager flag must be set to ’Y’ or ’N’.

[APP–7431] You may not update the input value name or sequence.

There are Paylink Batch Lines which rely on the ordering of this element’s input values. You may

not update the name or sequence of any input value for this element until all batch lines which use it

are purged.

[APP–7432] The person you entered does not exist.

This person does not exist at all, or is not completely within the assignment’s date range.

[APP–7433] This value should be between &LOW and &HIGH, please re–enter.

[APP–7434] Grade required.

The value for grade must be entered if a value exists for the special ceiling step.

[APP–7435] This person already has a primary assignment for these dates.

[APP–7436] No primary assignment exists during the date range of the non primary assignment.

[APP–7437] The coverage level is not valid for this benefit plan

[APP–7438] Invalid reference field value.

The reference field value for the descriptive flexfield is not supported.

[APP–7439] Invalid attribute argument.

You have tried to set attribute arguments when the descriptive flexfield reference field is null or

validation logic has not been implemented.

[APP–7440] Cannot terminate , future person changes exist.

[APP–7441] Invalid value.

This version of the API does not support the &ARG_NAME argument. This argument must be left

blank.

[APP–7442] Element Entries including at least one Salary Entry have changed. Do you want to

continue?

[APP–7443] Case Number must be unique

The Case Number entered for an OSHA incident report must be unique. The Case Number entered

has been used previously.

[APP–7444] Cannot alter balance feeds

The balance is defined using classifications and as such all the balance feeds exist due to the

classifications. To preserve the definition of the balance, the creation, alteration, or removal of

individual balance feeds is not allowed.

[APP–7445] Cannot create balance classification

The balance has been defined using individual balance feeds and as such it is not possible to feed

the balance using classifications.

[APP–7446] Hot Defaults must have a default value

You may leave the creation of a default value until you create the link, but this is a warning in case

you wanted to enter a default here. A default here will be inherited by all links for this element.

[APP–7448] This person is not eligible for the element associated with this absence type.

[APP–7449] A value must be entered for &COLUMN_NAME

[APP–7450] A body has not been defined for the user validation package

[APP–7451] You may not delete next change this processing rule.

There are result rules for future versions of this processing rule. These must be deleted before the

processing rule may be overridden by your action.

[APP–7452] Entry values exceed number of input values associated with this element at the

effective date

[APP–7453] Costing details have been entered for a non costable element

[APP–7454] Multiple entries are not allowed for this entry

[APP–7455] An entry exists for this element at the effective date

[APP–7456] Cannot update as more than one entry for this element exists at the effective date

[APP–7457] Future changes exist for this entry

[APP–7458] Entry values not required as there are no input values associated with this element at

the effective date

[APP–7459] Employee is not eligible for this element entry at the effective date

[APP–7460] A cost allocation structure has not been defined for business group

&BUSINESS_GROUP_ID

[APP–7462] An invalid value has been entered for &COLUMN_NAME

[APP–7464] Element type id &ELEMENT_TYPE_ID is invalid at the effective date

[APP–7465] Element &ELEMENT_NAME is invalid at the effective date

[APP–7466] Assignment number &ASSIGNMENT_NUMBER is invalid at the effective date

[APP–7467] Assignment id &ASSIGNMENT_ID is invalid at the effective date

[APP–7468] A status must be returned by &USER_PROCEDURE

[APP–7469] An invalid status was returned by &USER_PROCEDURE

[APP–7470] &USER_PROCEDURE returned a status that is invalid in this context. Valid statuses

are (V)alid,(E)rror,(W)arning

[APP–7471] The external account flexfield structure is invalid

[APP–7472] Unable to process batch &BATCH_ID as it contains transferred record(s)

[APP–7473] Job Requirements using this type exist currently

This Special Information Type cannot be removed from this category because there are Job

Requirements currently using the type.

[APP–7477] Control types have not been defined by the user

[APP–7478] Either the element type id &ELEMENT_TYPE_ID or element name

&ELEMENT_NAME does not exist on the effective date, or the element type id and element

name do not match.

[APP–7479] Either the assignment id &ASSIGNMENT_ID or the assignment number

&ASSIGNMENT_NUMBER does not exist on the effective date, or the assignment id and

assignment number do not match

[APP–7481] An error occurred within &USER_PROCEDURE

[APP–7482] Both &COL1 and &COL2 are null. At least one value should be entered

[APP–7483] When a payroll is assigned, the Last Standard Process Date must equal the last

assignment end date.

[APP–7484] The Final Process Date must be blank when creating a new Period of Service.

[APP–7485] The Leaving Reason must exist within the HR Lookups values.

[APP–7486] The Notified Termination Date must be on or after the Date Start.

[APP–7487] The Notified Termination Date must be blank when creating a new Period of Service.

[APP–7488] The person accepting the termination date must be different to the person terminated.

[APP–7489] The Leaving Reason must be blank when creating a new Period of Service.

[APP–7490] The person must exist as an employee at the time specified by Date Start.

[APP–7491] The Projected Termination Date must be on or after the Date Start.

[APP–7492] The Accepted Termination Date must be blank when creating a new Period of Service.

[APP–7493] The Actual Termination Date must be on or after the Date Start.

[APP–7496] The Final Process Date must be blank when creating a new Period of Service.

[APP–7497] The Last Standard Process Date must be blank if the Actual Termination Date is blank.

[APP–7499] The Projected Termination Date must be blank when creating a new Period of Service.

[APP–7500] The Termination Accepted By person is not valid.

The person accepting the termination must be an employee at the Actual Termination

Date.@PARAAGRAPHEND

[APP–7501] The Termination Accepted Person must be blank when creating a new Period of

Service.

[APP–7502] The Actual Termination Date must be blank when creating a new Period of Service.

[APP–7503] The Final Process Date must be blank if the Actual Termination Date is blank.

[APP–7504] The Final Process Date must be on or after the Last Standard Process Date.

[APP–7505] The Last Standard Process Date must be on or after the Actual Termination Date.

[APP–7506] Can only mark for retry a completed assignment action

Cause:

an attempt was made to mark for retry an assignment action that did not have an action status of

Complete. This is not allowed. The assignment action is for Assignment Number &ASG_NO

Action:

either rollback or rollforward the assignment action.

[APP–7507] Assignment action interlock rule failure You cannot mark this process for retry as there

has been subsequent post–run processing for this payroll. To remedy this you can mark the

subsequent process for retry. Marking for retry deletes the results of the subsequent process and

enables you to retry the first process. Please note an exception to this procedure. If the subequent

process is a payments process (magnetic transfer, check, or cash) you can only delete it in order to

retry the preceding process.

[APP–7507] Assignment action interlock rule failure You cannot mark this process for retry as there

has been subsequent post–run processing for this payroll. To remedy this you can mark the

subsequent process for retry. Marking for retry deletes the results of the subsequent process and

enables you to retry the first process. Please note an exception to this procedure. If the subsequent

process is a payments process (magnetic transfer, check, or cash) you can only delete it in order to

retry the preceding process.

[APP–7508] Undo rule failure for action name &ACTION_NAME

Cause:

the rollback or mark for retry of an individual assignment action for an action of

&ACTION_NAME is not allowed.

Action:

either rollback/mark for retry the entire payroll action or do not perform either action.

[APP–7509] Bad dml mode

Cause:

the dml_mode parameter to the rollback procedure can only have the values FULL, PARTIAL or

NONE.

Action:

specify one of the values above.

[APP–7510] You cannot continue, Future changes exist.

[APP–7511] The entry for gender/sex is not recognized. Check and re–enter M or F.

[APP–7512] The entry for Title is not recognized. Check and re–enter the Title.

[APP–7513] Invalid person type

You have tried to enter a person type that does not exist on the system.

[APP–7514] Invalid start date

You have tried to enter a start date that does not exist on the system

[APP–7515] The interview start date must be on or after: &RECEIVED_DATE

Cause:

For an applicant interview, you are trying to enter a Start Date which is before &RECEIVED_DATE

– the start date of the application.

Action:

You are trying to interview an employee before he or she has applied to your business! Enter a

interview Start Date which is on or after the Date Received of the application.

[APP–7516] The interview end date must be on or before: &END_DATE

Cause:

For an applicant interview, you are trying to enter an End Date which is after &END_DATE – the

end date of the application.

Action:

You are trying to interview an applicant after his or her application has lapsed! Enter an interview

End Date which is on or before the Terminated Date of the application.

[APP–7517] You cannot delete this interview, interviewers are booked for it

Cause:

For an application, you are trying to delete an interview for which you have booked interviewers.

Action:

If you want to delete this interview, first delete all interviewers booked to participate in the

interview. Use the next zone to delete interviewers.

[APP–7518] The entry for Marital Status is not recognized. Check and re–enter the Marital Status.

[APP–7522] The entry for Nationality is not recognized. Check and re–enter the Nationality.

[APP–7523] You cannot enter an employee number for this person type

[APP–7524] Invalid ethnic origin

You have tried to enter a value for ethnic origin (PER_INFORMATION1) that does not exist on the

system

[APP–7525] Director (PER_INFORMATION2) must be Y(for Yes) or N(for No)

[APP–7526] Pensioner (PER_INFORMATION4) must be Y(for Yes) or N(for No)

[APP–7527] Work Permit (PER_INFORMATION5) cannot be longer than 30 characters

[APP–7528] Enter the Work Permit value (PER_INFORMATION5) in upper case

[APP–7529] Do not enter PER_INFORMATION&NUM for this legislation

[APP–7530] Save your report or display another before continuing.

[APP–7531] Save your rate or display another before continuing

[APP–7532] Save your link or display another before countining.

[APP–7533] Save your set of books or display another before continuing.

[APP–7534] Save your budget or display another before continuing.

[APP–7535] Save your budget element or display another before moving.

[APP–7536] Save your customization or display another before continuing.

[APP–7537] Save your job or display another before continuing

[APP–7538] Save your Organization Classification or display another before continuing.

[APP–7539] Save your Parent Organization or display another before continuing

[APP–7540] Save your Organization Units or display another before continuing.

[APP–7542] Save your contact or display another before continuing.

[APP–7543] Save your Position or display another before continuing.

[APP–7544] Save your Pay Scale or display another before continuing.

[APP–7545] Save your COBRA Coverage or display another before continuing.

[APP–7546] Save your Person or display another before continuing.

[APP–7547] Save your Review or display another before continuing.

[APP–7548] Save your Salary Information before continuing.

[APP–7549] Save your Reviewers’ or display another before continuing.

[APP–7551] Save your Event or display another before continuing.

[APP–7554] Enter a valid Assignment before running the quickpaint report.

[APP–7555] Enter a valid assignment set before running the quickpaint report.

[APP–7556] Employee’s Resident Address state is missing or employee has no primary address.

[APP–7557] Employee’s work state is missing or employee has no primary address.

[APP–7560] Value fields’ value must be greater than or equal to minimum value.

[APP–7561] Mid value value must be greater than or equal to minimum.

[APP–7564] This name includes reserved words or characters. Acceptable values are A–Z, a–z, 0–9

or underscore (_) characters. Also you cannot start the name with a number. Please Re–enter.

[APP–7565] Please choose a Link before moving to the next zone.

[APP–7566] Please choose a job before moving to the next zone.

[APP–7568] Please choose a career path before moving to the next zone.

[APP–7569] Please choose a benefit before moving to the next zone.

[APP–7570] Please choose a Quickcode Type before moving to the next zone.

[APP–7571] Style is required. Please enter a valid value.

[APP–7572] Input value is required. Please enter a valid value.

[APP–7573] Further information is required. Please enter a valid value.

[APP–7574] Version Number is required. Please enter a valid value.

[APP–7575] Date From is required. Please enter a valid value.

[APP–7576] Last Standard Process is required. Please enter a valid value.

[APP–7578] National Insurance is required. Please enter a valid value.

[APP–7579] You must enter an Application Number.

[APP–7580] Social security Number is required. Please enter a vaild value.

[APP–7581] Employee number is required. Please enter a valid value.

[APP–7582] Hours or Days is required. Please enter a valid value.

[APP–7583] Increasing or Decreasing is required. Please enter a valid value.

[APP–7584] Delete is disabled for this zone

[APP–7585] Please enter a job before moving to the career path map.

[APP–7586] Please enter a career path before moving to the career path map.

[APP–7587] You can only use Quickpick if there is more than one holder.

[APP–7588] This step is not valid for the duration of the grade scale.

[APP–7589] This step is not valid for the duration of the assignment.

[APP–7594] You cannot cancel the termination of a hired applicant

Cause:

You are trying to cancel the termination of an application that you have not actually terminated.

You have hired the applicant, that filed this application, into the assignment he/she applied for and

the application has ended, not terminated.

Action:

If you want to cancel the hire, Use the Enter Employee Personal Information form.

[APP–7597] This application is not terminated, you cannot cancel it

Cause:

You have entered ’Yes’ in the Initiate Cancellation field, when you have not entered any termination

details for the application.

Action:

You are trying to cancel a termination when you have not entered termination information! Enter

’No’ in the Initiate Cancellation field.

[APP–7599] Supervisor is not valid for the duration of the assignment.

[APP–7600] Standalone Personnel users cannot query a Payroll Status

[APP–7601] You can have only one default status for primary system status type

[APP–7602] This user status already exists. Please enter a new user status

[APP–7603] Personnel status is for applicants, cannot enter a Payroll status

Cause:

You are trying to enter a Payroll system status for a Personnel system status relating to applicants.

Action:

Personnel system statuses for applicants do not require corresponding Payroll system statuses.

[APP–7604] Please enter a Payroll status for this Personnel status

Cause:

You are trying to define a Personnel system status for employees without entering a related Payroll

system status.

Action:

Personnel system statuses for employees require a related Payroll system status. Enter a Payroll

system status for this Personnel system status.

[APP–7605] Please enter ’P’ for Primary or ’S’ for Secondary

[APP–7607] You must an active default value for a primary status

[APP–7610] Job is not valid for the duration of the assignment.

[APP–7612] Grade is not valid for the duration of the assignment.

[APP–7614] Payroll is not valid for the duration of the assignment.

[APP–7615] Progression point step has changed or there are future deletes.

[APP–7616] The actual end date must be after the actual start date.

[APP–7617] The projected end date must be after the projected start date.

[APP–7618] The actual End time must be after the actual Start Time.

[APP–7619] The Projected end Time must be after the Projected Start time.

[APP–7620] You cannot enter Actual End Time without Actual End Date.

[APP–7621] You cannot enter Projected End Time without Projected End Date.

[APP–7622] The absence duration in Days is greater than the length of time absent.

[APP–7623] The absence duration in hours is greater than the actual time absent.

[APP–7625] You cannot delete the assignment when application assignment rows exist.

[APP–7628] Please enter a frequency for the working hours

[APP–7634] You cannot delete the assignment when Letter Requests rows exist.

[APP–7637] You cannot end the assignment when future Letter Requests rows exist.

[APP–7638] You cannot delete the assignment when Costing rows exist.

[APP–7641] you can not end the assignment when future Costing rows exist.

[APP–7642] You cannot delete the assignment when Extra Assignment Information rows exist.

[APP–7646] You must enter a value for Organization Hierarchy

[APP–7647] You must enter a value for Top Organization

[APP–7648] You must enter a value for Position Hierarchy

[APP–7649] You must enter a value for Top Position

[APP–7651] You cannot change View All Payrolls to ’Yes’, specific payrolls exist

Cause:

You are trying to change a security profile to view all records when you have already defined the

View All Payrolls field as ’No’ and entered the payroll(s) which the profile includes or excludes.

Action:

If you want this security profile to viewall records, first remove these payrolls.

[APP–7652] you cannot delete the assignment when Secondary Assignment Status rows exist.

[APP–7655] You cannot end the assignment when future Secondary Assignment Status rows exist.

[APP–7656] You cannot delete the assignment when Payment Method rows exist.

[APP–7659] You cannot end the assignment when future Payment Method rows exist.

[APP–7660] You cannot delete a period type which is used in a calendar

Cause:

You are trying to delete a period type used by a calendar.

Action:

You cannot delete a period type once it is used by a calendar. Delete the calendar if you wish to

delete the period type.

[APP–7662] At least one period type of &PERIOD_TYPE must exist

Cause:

You are trying to delete the only &PERIOD_TYPE period type.

Action:

&APPLICATION requires at least one &PERIOD_TYPE period type. If you want to delete this

period type, first define and save another.

[APP–7663] A time period with this name already exists. Enter a new name

Cause:

You are trying to define more than one time period type with the same name.

Action:

Enter a unique name for your time period type.

[APP–7664] You cannot delete the assignment when Assignment Action rows exist.

[APP–7667] You cannot end the assignment when future Assignment Action rows exist.

[APP–7671] You cannot end the assignment when future COPBRA Befefits rows exist.

[APP–7672] You cannot delete the assignment when COBRA Enrolments rows exist.

[APP–7675] You can end the assignment when future COBRA Enrolmets rows exist.

[APP–7676] This person is not an Employee as of this effective date.

[APP–7677] This Person is not an Applicant as of this effective date.

[APP–7678] This person is not an Employee/Applicant as of this effective date.

[APP–7679] Assignments’ Payroll not exist at this date.

[APP–7680] Assignments’ Supervisor not exist at this date.

[APP–7681] A location with this name already exists. Enter a new name.

[APP–7682] An organization with this name already exist. Enter a new name.

[APP–7683] A position with this name already exists. Enter a new name.

[APP–7684] A pay scale with this name already exists. Enter a new name.

[APP–7685] An assignment status with this name already exists. Enter a new name.

[APP–7686] A job with this name already exists. Enter a new name.

[APP–7687] A grade with this name already exists. Enter a new name.

[APP–7688] A position with this name already exists. Enter a new name.

[APP–7689] A table with this name already exists. Enter a new name.

[APP–7692] Employee Number already exists.

[APP–7693] Applicant number already exists.

[APP–7694] You cannot delete a hierarchy version used by a security profile.

[APP–7696] The internal Contact is not a current employee in this start date.

[APP–7697] The Authoriser is not a current employee in this start date.

[APP–7699] A recurring entry for standard already exists for this assignment.

[APP–7700] A recurring entry for Additional already exists for this assignment.

[APP–7701] Please enter a unique element rule for this set.

[APP–7702] Assignment does not exist.

[APP–7703] Element does not exist.

[APP–7704] Element link does not exist.

[APP–7705] Action Code does not exist.

[APP–7706] Shift Type does not exist.

[APP–7708] Rate code does not exist.

[APP–7711] SCL Org. Payment method level not found.

[APP–7712] Please enter a birth date earlier than the current date

[APP–7713] Workers compensation element does exist or is not linked to Payroll.

[APP–7714] You must enter actual start and end dates to enter days duration

[APP–7715] The employee was terminated on or before the projected start date

[APP–7716] The actual start date must be less than or equal to the actual end date.

[APP–7717] This element input already being used to mainatain a absence balance

[APP–7719] You can not have more than one rule for the same state.

[APP–7720] You can not have more than one rule for the same location.

[APP–7722] Attempted to process more than &COMMIT_LIMIT actions in single commit unit.

Cause:

an attempt was made to process more than &COMMIT_LIMIT number of assignmetn actions in a

single commit unit.

Action:

the number of actions that may be rolled back or marked for retry is controlled by the action

parameter MAX_SINGLE_UNDO. Please check the value of this parameter in comparison with the

number of assignment action you were attempting to process. Either increase the size of the

parameter as appropriate, or remember that the default size of this parameter is 50.

[APP–7723] There is no payment method specified.

[APP–7724] Invalid DateTrack mode.

You cannot use the DateTrack UPDATE_CHANGE_INSERT mode when changing the system

person type.

[APP–7726] Delete not allowed.

You cannot use a DateTrack mode of Delete for a system person type with future changes.

[APP–7727] The territory code specified for the external account is invalid

[APP–7728] No run exists for this payment. Contact your System Administrator.

The payroll runs processed by this Payment cannot be found. Contact your System Administrator.

[APP–7729] No information found for this run.

Payroll Action data could not be found. Contact your System Administrator.

[APP–7730] Cannot change session date from this window.

Change session date is not allowed from the SOE. To view SOE for other runs, use ”Next Run”,

”Previous Run” buttons, or return to Assignment Process Results screen and select a different

payroll action.

[APP–7732] Cannot access employee information; Employee setup is incomplete.

Employee setup must include Tax Information, Salary Basis for SOE viewing.

[APP–7733] SOE is not available for this process type.

The SOE is used to view ”Payroll Run”, ”QuickPay Run”, ”Payment”, and ”QuickPay Payment”

information.

[APP–7735] No QuickPay Run found for this QP Payment. Contact Sys Admin.

Could not find QuickPay Run processed by this QuickPay Payment. Contact your System

Administrator.

[APP–7736] No more runs found for this employee.

No more payroll actions exist for this employee.

[APP–7737] No payment detail information found. Contact your Sys Admin.

Payment information could not be found. Contact your System Administrator.

[APP–7738] Startup data is missing for balance dimensions.

Startup data provided with Oracle Payroll is missing – PAY_BALANCE_DIMENSIONS. Contact

your System Administrator.

[APP–7739] Please delete the base element, not the Special Features element.

The base element must be queried from the database and deleted. You cannot delete the ”Special

Features” or ”Special Inputs” elements. These are deleted when the base element is deleted.

[APP–7740] Please delete the base element, not the Special Inputs element.

Special Inputs and Special Features elements are deleted when you delete the base element. Query

base element and retry deletion.

[APP–7743] You must re–query this earning before deletion.

Earnings cannot be deleted immediately after insertion. Please re–query the element and try delete

again.

[APP–7745] Please PURGE all links before deleting this earnings type.

Elements may not be deleted when element links for the element exist.

[APP–7746] You cannot delete an earnings type that has run results.

Rollback any runs including this element type before deletion.

[APP–7749] Batch Lines for this earnings type must be PURGED.

All batch lines for this earning must be purged before delete.

[APP–7751] Please PURGE all COBRA coverage benefits for this earning.

COBRA coverage benefits must be purged for this earning before deleting.

[APP–7752] Element Name must be entered.

[APP–7753] Element Name must be less than 25 characters.

The earnings generator creates additional data for you when you commit. Some of this data uses the

name you have entered as a basis for the name of another object. If the concatenated name is too

long, an error will occur. Please enter an element name less than 25 characters.

[APP–7754] Please select a Calculation Method.

[APP–7755] Calc Rule must use ”Hours” when FLSA Hours = Y

Hours entered for this earning get included in the FLSA Overtime base rate calculation (FLSA = Y),

so you must select a Calculation Method using ”Hours” – ie. Hours x Rate.

[APP–7756] Element names must start with a letter of the alphabet.

[APP–7757] Element names can include only letters, numbers and underscores.

[APP–7759] Reporting names must begin with a letter of the alphabet.

[APP–7760] Reporting names can include only letters, numbers, and underscores.

[APP–7761] Element names must begin with a letter of the alphabet.

[APP–7762] Element names can include only letters, numbers and underscores.

[APP–7763] Payroll Table must be entered.

When calculation method is ”Payroll Table”, you must provide the table information required for

processing of this deduction.

[APP–7764] Table Column must be entered.

Payroll Table details are required for processing of this deduction – ie. calculation method =

”Payroll Table”.

[APP–7765] Row Type must be entered.

[APP–7766] Please delete base element, not Special Features element

Special Features and Special Inputs elements are deleted when the base element is deleted.

[APP–7767] Please delete base element, not Special Inputs element.

Special Inputs and Special Features elements are deleted when the base element is deleted.

[APP–7768] You cannot delete deductions included with the system.

Startup data deductions cannot be deleted by the user.

[APP–7769] You must query a deduction before you can delete it.

Deductions cannot be deleted immediately after insertion. Requery deduction before deleting.

[APP–7772] Please PURGE all links before deleting this deduction.

[APP–7776] Please PURGE all COBRA coverage benefits for this deduction.

[APP–7777] Please delete contributions before deleting this benefit.

Data entered on the Benefit Contributions form for this benefit must be purged before deleting.

[APP–7778] Please delete element set rules referencing this deduction.

[APP–7779] You cannot delete earnings included with the system.

[APP–7781] Delete element set rules referencing this earning before deletion.

[APP–7782] Could not find latest assignment action for this assignment.

[APP–7783] No assignment or assignment action passed to SOE.

Contact your System Administrator.

[APP–7784] Cannot find balance &BAL_DIM_ID. Contact your system administrator.

[APP–7785] No GRE is on record for this employee’s assignment. Please enter one.

[APP–7786] Enter Zip Code correctly, should be between &zip_start and &zip_end.

[APP–7787] You cannot set up a third party payment method for this payment type.

[APP–7788] The Address identified must be of style GB.

[APP–7789] Assignment is not linked to payroll on &ADJ_DATE

[APP–7790] Cannot delete. Element Entries exist for this payment method

[APP–7792] Failure when attempting to open file &FILE

Cause:

a failure was reported when attempting to open the file $FILE.

Action:

check that you have the permissions to open a file for writing in the particular directory. Also check

that the directory actually exists.

[APP–7793] The date earned must be within the effective dates of the entry.

The date earned of an entry must be a date within the payroll period to which the entry belongs.

[APP–7794] The date earned may not be entered for recurring entries.

You may only enter a date earned for entries which are nonrecurring. This could be an entry for a

nonrecurring element, or an additional, adjustment or override entry for a recurring element.

[APP–7795] You may not enter a payee for this entry.

Only elements denoted as being for third party payments may have a payee on the entry.

[APP–7796] There is no such payee.

The payee specified is not valid for the assignment specified.

[APP–7797] The payee record does not exist for the lifetime of the entry.

The effective dates of the entry must fall within the effective dates of the payee selected.

Otherwise, there is ambiguity in the details which should be used for the entry.

[APP–7798] You cannot delete this entry.

This entry has been processed in a payroll run. Backpay is not currently supported for third party

payments (garnishments in the US). If you want to remove this entry, you must first rollback or

mark for retry the run in which this entry was processed.

[APP–7800] This element’s end date is before that of the absence type

Cause:

You are trying to associate an element with an absence type but the element does not exist for the

entire duration of the absence type.

Action:

Choose another element to associate with this absence type OR Navigate to the Define Element

form and perform a remove future changes delete, with your session date set to a date for which the

element exists. You can then associate the required element with this absence type.

[APP–7801] The unit of measure for this absence type is Days. PayMIX currently supports only

absences measured in Hours

[APP–7804] Employee will not be terminated.

You have not entered an Actual Termination Date so the employee will not be terminated. Choose

OK if you want to save the information you have entered.

[APP–7805] You cannot delete this absence/attendance type, reasons exist

Cause:

You are trying to delete an absence or attendance type for which reasons exist.

Action:

If you want to delete this absence or attendance type, first delete all reasons defined for the type.

[APP–7806] This absence/attendance type already exists. Please enter a new name

Cause:

You are trying to enter more than one absence or attendance type with the same name.

Action:

Enter a unique name for your absence or attendance type.

[APP–7807] This reason already exists. Please enter a new name

Cause:

For an absence or attendance type, you are trying to enter more than one reason with the same

name.

Action:

Enter a unique name for your reason.

[APP–7808] This grade must become valid on or before grades are valid for jobs

Cause:

You are trying to change the date on which the grade becomes valid, when that date is after the

grade has been defined as valid for one or more jobs.

Action:

Either change the date from which this grade is valid, or change the date the grade is valid for jobs.

[APP–7809] This employee is not terminated.

You cannot cancel the termination of an employee who is not currently terminated.

[APP–7810] This job already exists. Please enter a new name

Cause:

You are trying to enter more than one job with the same name.

Action:

Enter a unique name for your job.

[APP–7811] You cannot delete this job, it exists in a career path

Cause:

You are trying to delete a job which is included in a career path.

Action:

If you want to delete this job, first delete it from any career paths currently using the job. Use \

Navigate Define Work Job Map, the Map Career Path form, to delete jobs.

[APP–7812] You cannot delete this job, it has valid grades

Cause:

You are trying to delete a job for which valid grades exist.

Action:

If you want to delete this job, first delete all grades defined as valid for this job. Use this form to

delete such grades.

[APP–7813] You cannot delete this job, it has positions

Cause:

You are trying to delete a job for which positions exist.

Action:

If you want to delete this job, first delete any positions which use this job. Use \ Navigate Define

Work Position Description, the Define Position form, to delete jobs.

[APP–7814] You cannot delete this job, it has job requirements

Cause:

You are trying to delete a job for which job requirements exist.

Action:

If you want to delete this job, first delete all job requirements defined for the job. Use this form to

delete job requirements.

[APP–7815] You cannot delete this job, it has job evaluations

Cause:

You are trying to delete a job for which job evaluations exist.

Action:

If you want to delete this job, first delete all job evaluations defined for the job. Use this form to

delete job evaluation.

[APP–7816] You cannot delete this job, it has budget values

Cause:

You are trying to delete a job for which budget values exist.

Action:

If you want to delete this job, first delete all budget values defined for the job. Use \ Navigate

Define Work Position Budget, the Define Budget form, to delete budget values.

[APP–7817] You cannot delete this job, employees are assigned to it

Cause:

You are trying to delete a job to which employees are assigned.

Action:

If you want to delete this job, first reassign employees to other jobs. Use \ Navigate Employee

Assignment Enter, the Enter Employee Assignment form, to reassign employees.

[APP–7818] This grade already exists. Please enter a new name

Cause:

For this job, you are trying to enter the same grade as a valid grade more than once.

Action:

As this grade already exists for this job, erase (using \ Row Erase) the information you have entered

in this zone and enter another grade.

[APP–7820] Invalid payee details.

You can only enter payee and payee type when the organization payment method is for a third party

payee.

[APP–7821] Grade must become valid on or after the grade start date: &DATE

Cause:

You are trying to define the date on which this grade is valid for the job, when that date is prior to

the start date you have defined for the grade.

Action:

You are trying to use the grade before it exists in &APPLICATION Enter the date after which the

grade becomes valid for the job as on or after the start date which you have defined for the grade.

[APP–7822] Incomplete payee details.

You must enter both the payee and the payee type when the organization payment method is for a

third party payee.

[APP–7823] This grade must become valid on or after the job start date

Cause:

You are trying to define the date on which this grade is valid for the job, when that date is prior to

the start date you have defined for the job.

Action:

You are trying to use the grade for a job before the job exists in &APPLICATION

Action:

Enter the date after which the grade becomes valid for the job as on or after the start date you have

defined for the job.

[APP–7824] This grade must no longer be valid on or before the job end date

Cause:

You are trying to define the date on which this grade is no longer valid for the job, when that date is

after the end date you have defined for the job.

Action:

You are trying to use the grade for a job after the job has ceased to exist in &APPLICATION

Action:

Enter the date after which the grade is no longer valid for the job on or before the end date you have

defined for the job.

[APP–7825] This job must become valid on or before all grade start dates

Cause:

You are trying to change the date from which this job is valid, when that date is after the start date

for at least one of the grades you have entered for the job.

Action:

Either change the start dates of grades starting before the job, or change the start date of the job to

be before the first grade.

[APP–7826] This job must still be valid on or after all grade end dates

Cause:

You are trying to change the date on which the job is no longer valid for the job, when that date is

before the last date of one or more grades valid for the job.

Action:

Either change the end dates of grades valid for the job, or change the end date of the job to be after

all grades.

[APP–7830] A grade with this name already exists. Please enter a new name

Cause:

You are trying to enter more than one grade with the same name.

Action:

Enter a unique name for your grade.

[APP–7833] Please enter an integer sequence number greater than zero

Cause:

You are trying to enter a Sequence Number which is not an integer, or is less than zero.

Action:

Enter a Sequence number which is an integer.

Action:

Enter a Sequence number greater than zero.

[APP–7834] You cannot delete this grade, it is currently assigned

Cause:

You are trying to delete a grade which is currently assigned to one or more employees in your

business.

Action:

If you want to delete this grade, first assign a new grade to all employees currently at this grade.

Use \ Navigate Employee Assignment Enter, the Enter Employee Assignment form, to change

employee grades.

[APP–7836] An information type with this name already exists. Enter a new name

Cause:

You are trying to enter more than one further information type with the same name.

Action:

Enter a unique name for your further information type.

[APP–7837] You cannot delete this information type, people are using the type

Cause:

You are trying to delete a further information type used by one or more person in or applying to

your business.

Action:

If you want to delete this further information type, first delete the information type from the records

of all people currently using the type.

[APP–7839] The payee organization does not exist.

[APP–7840] You cannot delete this career path, career maps use it

Cause:

You are trying to delete a career path used by one or more career maps.

Action:

If you want to delete this career path name, first delete all career maps using the career path.

[APP–7841] A career path with this name already exists. Please enter a new name

Cause:

You are trying to enter more than one career path with the same name.

Action:

Enter a unique name for your career path.

[APP–7843] The organization you have entered is not active or of type payee.

[APP–7845] You cannot delete a job to which other jobs progress

Cause:

You are trying to delete a job to which other jobs progress.

Action:

If you want to delete this job from the career path map, first delete any jobs which progress to this

job. Use the Job Progression From zone to delete jobs below the current path.

[APP–7846] The payee person does not exist as of the effective date.

[APP–7847] Invalid payee contact.

The payee you have entered is not a contact with a contact relationship of the correct type for third

party payments.

[APP–7848] Invalid payee type.

[APP–7849] Cannot delete payment method.

You cannot remove this personal payment method because it is referenced by at least one element

entry in the delete date range.

[APP–7851] Only the value attribute can be set for a pay scale value – not the maximum, mid–value

and minimum attributes.

[APP–7852] A budget with this name already exists. Please enter a new name

Cause:

You are trying to enter more than one budget with the same name.

Action:

Enter a unique name for your budget.

[APP–7853] Assignment not yet eligible for this accrual

The assignment period of service is not yet long enough to be eligible for this accrual plan. Time

taken against this accrual cannot be entered until ineligibility period has expired.

[APP–7854] The Value Rule identified must be for a Grade Rate.

[APP–7855] The Value Rule identified must be of Pay Scale type.

[APP–7856] A letter type with this name already exists. Please enter a new name

Cause:

You are trying to enter more than one letter type with the same name.

Action:

Enter a unique name for your letter type.

[APP–7857] You cannot delete this letter type. Statuses exist

Cause:

You are trying to delete a letter type for which one or more statuses are defined.

Action:

If you want to delete this status, first delete any statuses defined for this letter type. Use the

Application Statuses zone of this form to delete statuses.

[APP–7858] You cannot delete this letter type. Requests exist

Cause:

You are trying to delete a letter type for which letter requests exist.

Action:

If you want to delete this letter type, first delete any requests for this type of letter. Use \ Navigate

Start Letter, the Request Letter form, to delete requests for letters.

[APP–7859] This status already exists for the letter type. Please reenter

Cause:

For a letter type, you are trying to enter the same application status more than once.

Action:

As this application status already exists for the letter type, either change or erase (using \ Row

Erase) the information you have entered on this form.

[APP–7860] Costing records exist between the old and new dates.

[APP–7861] You cannot delete a position for which a recruitment activity exists

[APP–7862] You cannot delete a position for which staff budgets exist

[APP–7863] You cannot delete a position having element links

[APP–7865] You cannot delete this position, it has valid grades

[APP–7866] You cannot delete this position, it has position requirements

[APP–7867] You cannot delete this position, it has position evaluations

[APP–7868] This grade already exists. Please enter a new name

[APP–7869] A valid payment method does not exist for the employee assignment payroll

[APP–7870] This grade must become valid on or after the position start date

[APP–7871] Grade must become valid on or after the grade start date: &DATE

[APP–7872] This position must still be valid on or after all grade end dates

[APP–7873] Warning, unable to reinstate one or more element entries

Cause:

The run that you are trying to reverse has the following entries that have been either deleted or

updated as of the payroll run and is unable to reinstate the entries. Check the entries by looking at

the Element History screen, and manually reinstate the entries before performing the reversal:

&ELEMENT_NAME1 &ELEMENT_NAME2 &ELEMENT_NAME3 &ELEMENT_NAME4

&ELEMENT_NAME5 &ELEMENT_NAME6 &ELEMENT_NAME7 &ELEMENT_NAME8

&ELEMENT_NAME9 &ELEMENT_NAME10 &ELEMENT_NAME11 Do you want to continue

with the reversal run ?

[APP–7874] You cannot update value, Person is recipient of Payment.

[APP–7875] There can only be a single initial balance feed

[APP–7876] This input value has been processed in a Payroll Run

Cause:

You are trying to use or update the usage of an input value as a balance feed where the input value

has been processed in a payroll run.

[APP–7877] Database constraint violated

The database check or unique constraint &CONSTRAINT_NAME has been violated. Please

contact your system administrator quoting the package procedure &PROCEDURE and constraint

&CONSTRAINT_NAME.

[APP–7878] National Identifier Number already exists. Continue?

National Identifier Number already exists. Continue?

[APP–7879] Please enter a unique Classification rule for this set

[APP–7882] Location does not exist

[APP–7883] A retropay set with this name already exists. Enter a new name

[APP–7884] A row with this name already exists. Enter a new name

[APP–7885] A column with this name already exists. Enter a new name.

[APP–7886] Authorisor is not valid for the duration of the abscence

[APP–7887] Replacement is not valid for the duration of the abscence

[APP–7888] A requisition with this name already exists. Enter a new name

[APP–7889] A letter type with this name already exists. Enter a new name

[APP–7890] Letter gen status with this name already exists. Enter a new name

[APP–7891] A vacancy with this name already exists. Enter a new name

[APP–7892] An organisation strucwith this name already exists. Enter a new name

[APP–7893] A budget with this name already exists. Enter a new name

[APP–7894] A recruitment activity with this name exists. Enter a new name

[APP–7895] Cannot open Magnetic Tape File for reading

Cause:

an attempt was made to open the file: &FILENAME for reading.

Action:

check that you have specified the correct filename, that it exists, is in the correct directory and has

the correct permissions for you to access it.

[APP–7896] Cannot open deivice ’&DEVICE_NAME’ for reading.

Cause:

an attempt was made to open ’&DEVICE_NAME’ for reading, but it failed.

Action:

check that you have specified the full path to the correct device and have the correct name; that the

device has the correct permissions and is on line.

[APP–7897] An error occurred while writing to device ’&DEVICE_NAME’

Cause:

an error occurred while attempting to write to device ’&DEVICE_NAME’.

Action:

check that the specified device is on line, and has enough storage available for the file you are

attempting to write to it.

[APP–7898] The legislation for the employee assignment business group is not GB

[APP–7899] This organisation is not valid for the duration of the assignment

[APP–7900] This position is not valid for the duration of the assignment

[APP–7901] You cannot enter duplicate records

[APP–7902] Please choose a contact before moving to next zone

[APP–7904] You cannot delete an organisation defined in a security profile.

[APP–7905] Save your information or display another before continuing.

[APP–7907] This booking will overlap an existing booking. Continue ?

[APP–7908] HR ERROR: in PAYWSDOR, trig WHEN–NEW–FORM–INSTANCE, step &STEP

System Error: Form PAYWSDOR Trigger WHEN–NEW–FORM–INSTANCE Step &STEP

[APP–7909] The argument &ARG_NAME is not in the correct Uppercase format

All the characters for the value &ARG_VALUE must be in an Uppercase format for the argument

&ARG_NAME

[APP–7910] The argument &ARG_NAME is not in the correct Lowercase format

All the characters for the value &ARG_VALUE must be in an Lowercase format for the argument

&ARG_NAME

[APP–7911] The argument &ARG_NAME is not in the correct Initcap format

The initial character for the value &ARG_VALUE must be in uppercase with preceeding characters

in a lowercase format

[APP–7912] The argument &ARG_NAME is not in the correct Money format

The value &ARG_VALUE must be in the Money format for the current business group legislation

[APP–7913] The argument &ARG_NAME is not in the correct Integer format

The value &ARG_VALUE must be a valid Integer

[APP–7914] The argument &ARG_NAME is not in the correct Number format

The value &ARG_VALUE must be a valid Number

[APP–7915] The assignment status can only be updated with an effective date after the effective

date of the initial assignment insert.

[APP–7916] The argument &ARG_NAME is not in the correct Time format HH:MM

The value &ARG_VALUE must be a valid Time where the HH indicates the hour of the day and

must be a valid integer in the range 0 to 23, MM indicates the minute of the hour and must be a

valid integer in the range 0 to 59

[APP–7917] The assignment status must be one of ACTIVE_ASSIGN, SUSP_ASSIGN, or

TERM_ASSIGN.

[APP–7918] The argument &ARG_NAME is not in the correct &DECIMAL_POINT Decimal Point

format

The value &ARG_VALUE must be a valid number with a maximum precision of

&DECIMAL_POINT decimal points

[APP–7919] The argument &ARG_NAME is not in the correct HR Naming format

The value &ARG_VALUE must begin with an alpha character and it must include only

alphanumeric or underscore characters

[APP–7920] A pay scale with this name already exists. Enter a new name.

[APP–7921] You cannot delete this pay scale because progression points exist for it. Delete the

progression points first.

[APP–7922] You cannot delete this pay scale because a grade scale uses it. Delete the grade scale

first.

[APP–7923] You cannot delete this pay scale because a rate exists for it. Delete the rate first.

[APP–7924] This progression point already exists for this pay scale. Enter a new point.

[APP–7925] This sequence already exists for this pay scale. Enter a new sequence.

[APP–7926] You cannot delete this progression point because grade steps exist for it. Delete the

grade steps first.

[APP–7927] You cannot delete this progression point because values are entered against it for one or

more rates. First query the rates for this pay scale and delete any values held for this progression

point.

[APP–7928] A grade step placement already exists for this assignment. You can only have one grade

step placement for anemployee assignment. Clear the information you have entered. Query the

existing placement and change the information if required.

[APP–7929] A grade step placement exists for this assignment in the future. If you want to enter a

placement for this assignment onthis date, first change your effective date to a date inthe future and

delete the existing placement.

[APP–7930] The argument &ARG_NAME is not in the correct NACHA format

The value &ARG_VALUE] must begin with an uppercase character. Other valid characters are,

numbers, ampersand, asterisk, comma, hyphen, period, dollar, underscore, space or uppercase

characters

[APP–7932] A grade scale already exists for this grade. Enter a different grade or query the existing

grade scale for this grade.

[APP–7933] You cannot delete this grade scale because assignments are placed on steps from this

scale. First delete these grade step placements.

[APP–7934] You cannot delete this grade scale. One or more steps of this grade scale are used as the

special ceiling for employee assignments. First delete the special ceiling entries for

employeeassignments on this grade.

[APP–7935] You cannot lower the ceiling because placements with a higher step exist. if you want

to lower the ceiling, first delete the placements to a higher grade step.

[APP–7936] This point already exists for this grade scale. Clear the duplicate information that you

have entered.

[APP–7936] This point already exists for this grade scale. Clear the duplicate information that you

have entered.

[APP–7937] You cannot delete the grade step that is the ceiling for the grade scale. First change the

ceiling for the grade scale.

[APP–7938] You cannot delete this step because employee assignments are placed on it. First delete

these grade step placements.

[APP–7939] You cannot delete this step because employee assignments are using it as a special

ceiling. First delete the special ceiling entries that use this grade step.

[APP–7940] The assignment status type id does not exist.

[APP–7941] The assignment must have a system status of ACTIVE_ASSIGN on insert.

[APP–7942] The assignment is terminated: only another TERM_ASSIGN status can be allocated.

[APP–7943] This covered dependent exists in the future starting &DATE

[APP–7944] The format supplied is invalid

[APP–7946] An assignment with status TERM_ASSIGN cannot have any other attributes updated.

[APP–7947] The expected system status must be either ACTIVE_ASSIGN or SUSP_ASSIGN.

[APP–7948] The assignment must be an employee assignment as of the effective date.

[APP–7949] An assignment status type with a system status of &SYSTYPE must be specified.

[APP–7950] Date of birth must be set when any of the assignments include a payroll component.

[APP–7951] A personal payment method may not be entered for an applicant assignment.

[APP–7952] You must enter a valid state for this address.

[APP–7953] You must enter a valid County for this address.

[APP–7954] Given city is not an unknown city.

[APP–7955] Once set, the actual termination date cannot be changed.

[APP–7956] The actual termination date must be after the initial insert date of the last assignment

for the specified person.

[APP–7957] The actual termination date must not be before any future changes to the person

specified.

[APP–7958] US legislation requires the last standard process date to be blank.

[APP–7959] If the actual termination date is set, then the last standard process date must also be set.

[APP–7960] Once set, the last standard process date cannot be changed.

[APP–7961] Either the legislation for the person business group is not &LEG_CODE or the person

is invalid.

[APP–7962] The final process date cannot be changed.

[APP–7963] If the last standard process date is blank the final process date must be on or after the

actual termination date.

[APP–7964] The legislation code of the assignment status type must be the same as that of the

business group.

[APP–7965] The total distribution is greater than 100% for benefit level &BENEFIT_LEVEL.

The total distribution exceeds 100% for benefit level &BENEFIT_LEVEL.

[APP–7966] The total distribution is less than 100%.

The total distribution is less than 100% for benefit level &BENEFIT_LEVEL.

[APP–7967] This beneficiary exists in the future, commencing &DATE.

This beneficiary exists in the future, commencing &DATE.

[APP–7968] The beneficiary, &ENT_VALUE, has been entered more than once.

The beneficiary, &ENT_VALUE, has been entered more than once.

[APP–7969] The assignment must not have personal payment methods that cannot be used for the

payroll specified.

[APP–7970] A person type with a system person type &SYSTYPE must be specified.

[APP–7972] No default person type exists for the system type of &SYS_TYPE.

[APP–7973] The person type specified is not active.

[APP–7974] The person type specified is not for the correct business group.

[APP–7975] There must not be any future assignment actions arising after the change effective date.

[APP–7977] The person type specified is not valid for a new person.

[APP–7978] You cannot use the DateTrack CORRECTION mode when the system person type has

already been changed on the effective start date.

[APP–7979] The specified DateTrack mode cannot be used if there is a change of system person

type in the future.

[APP–7980] For this element, you cannot go to the Covered Dependents form.

It is not possible to navigate to the Covered Dependents form for this element.

[APP–7981] For this element, it is not possible to go to the Beneficiaries form.

Cannot navigate to the Beneficiaries form for this element.

[APP–7982] A city with this name already exists

This message is used by US cities Form.

[APP–7983] You cannot delete or update this city.

This message is used by US cities Form.

[APP–7984] DateTrack mode CORRECTION cannot be used to modify the system person type as

there are no previous changes to this person.

[APP–7985] Save your changes, or query another city to continue.

[APP–7987] The change of person type would result in an invalid change to the system person type.

[APP–7990] There is a mutually exclusive link in the future.

This link matches another which starts in the future. Therefore, the end of this link is being set to

the date before the start of the mutually exclusive link.

[APP–7991] Semi–monthly periods may end on the 15th or the month end date only.

You must enter a date which is the fifteenth day of a month or the end date of a month.

[APP–7992] Cannot delete this Contact as they have benefit coverage.

Cannot delete this contact as the contact is currently covered for benefits.

[APP–7993] Cannot delete this contact who is designated as a beneficiary.

Cannot delete this contact who is designated as a beneficiary.

[APP–7994] Cannot delete this organization. It is designated as a beneficiary.

Cannot delete this organization. It is designated as a beneficiary.

[APP–7995] This position must become valid on or before all grade start dates

[APP–7996] This position is specified as the successor for another position

[APP–7997] This position is specified as the absence relief for another position

[APP–7998] &MESSAGE

[APP–7999] The assignment must not be a primary assignment.

[APP–8000] The assignment must not already have a status type of TERM_ASSIGN on or after the

actual termination date.

[APP–8000] You cannot have more than 35 days in an accounting period when average balances is

enabled.

[APP–8001] You cannot update business day creation defaults for existing transaction calendars.

[APP–8002] You cannot delete this transaction calendar because it is assigned to at least one set of

books.

[APP–8003] This account has not been assigned an entry type of ”Calculated” for this currency in

the Define Budget Organization form.

[APP–8004] Oracle General Ledger can only allocate quarter–to–date or project–to–date account

balances for ALL or STAT currencies.

[APP–8005] Oracle General Ledger can only allocate encumbrance balances when Currency is

ALL.

[APP–8006] All your existing budgets require journal entries.

[APP–8007] You have already archived all &TYPE for this year.

[APP–8009] This batch is frozen.

[APP–8010] The funds check/reservation process returned an invalid code. Contact your support

representative.

[APP–8011] To check or reserve funds for a batch, the batch must have at least one line.

[APP–8012] You cannot clear the default budgetary control rule.

[APP–8013] You cannot delete the default budgetary control rule.

[APP–8014] Oracle General Ledger cannot lock the timestamp for your chart of accounts. Contact

your system administrator.

[APP–8015] You cannot update the source or category for the default budgetary control rule.

[APP–8016] A fatal error occurred during the funds check process. Contact your system

administrator.

[APP–8017] A fatal error occurred during the funds reservation process. Contact your system

administrator.

[APP–8018] A fatal error occurred during the funds unreservation process. Contact your system

administrator.

[APP–8019] The Budget Posting program is processing this account.

[APP–8020] Budget AutoCopy must complete before opening a budget year.

[APP–8021] There are no budget journal transactions available for this action.

[APP–8022] You can only have one ALL budget organization in a set of books.

[APP–8023] Please allow Budget AutoCopy to complete before changing the Status.

[APP–8024] Oracle General Ledger cannot lock the selected account assignment range. Contact

your system administrator.

[APP–8025] This budget organization is being deleted.

[APP–8026] Please disable password security before changing the organization name.

[APP–8027] This account is not within the account range you defined.

[APP–8028] You can only AutoCopy to a budget organization that has not been assigned account

ranges.

[APP–8029] This account range overlaps another range with the same currency in this set of books.

[APP–8030] This master budget is no longer valid.

[APP–8031] Due to the minimum accountable unit of this currency, Oracle General Ledger could

not distribute exactly the amount specified.

[APP–8032] You can only have one current budget.

[APP–8033] You can only change the last budget period for budgets that are not master or detail

budgets.

[APP–8034] No budgets available for AutoCopy.

[APP–8035] There are no valid periods defined for this accounting period range. Please check your

calendar definitions.

[APP–8036] Another user has updated this row. Clear this record, save your changes to other rows,

then requery.

[APP–8037] There are no valid balances for this account that are applicable to your budget rule.

[APP–8038] This account is frozen for the budget organization &BUDORG and the budget

&BUDGET.

[APP–8039] Choose an account that is assigned to a budget organization with currency

&CURR_CODE.

[APP–8040] Choose an account that is assigned to an unfrozen budget organization.

[APP–8041] This account is assigned to the budget organization &BUDORG, which is being

deleted.

[APP–8042] Please enter a period name that does not contain any spaces.

[APP–8043] Only adjusting periods can overlap with another accounting period.

[APP–8044] You can only modify periods that have never been used.

[APP–8045] You cannot change a period status of Never Opened, Permanently Closed or

Future–Entry.

[APP–8046] The batch you selected is either not postable, already selected for posting, or being

posted.

[APP–8047] Oracle General Ledger was unable to get installation industry from &ROUTINE.

Contact your system administrator.

[APP–8048] You must permanently close all periods of a fiscal year before purging balances or

journals.

[APP–8049] You must permanently close all periods of a fiscal year before purging balances.

[APP–8050] You must permanently close all periods of a fiscal year before purging journals.

[APP–8051] Oracle General Ledger could not save your transactions at this time. Please contact

your system administrator.

[APP–8052] You have overlapping account ranges in your mapping rules.

[APP–8053] You cannot delete periods that have been used.

[APP–8054] You cannot disable budgetary control because you have summary templates or account

ranges with a funds check level of Advisory or Absolute.

[APP–8055] You cannot delete the suspense account with source and category Other.

[APP–8056] You can only enter query criteria in Worksheet Mode.

[APP–8057] Oracle General Ledger could not get a unique sequence number from &SEQUENCE.

Contact your system administrator.

[APP–8058] This form failed to submit your &MODULE concurrent request. Please ensure that

your concurrent manager is running.

[APP–8059] All existing budgets must require budget journals before you can select the Require

Budget Journals option for your set of books.

[APP–8060] Your &FUNDS_ACTION cannot proceed because Oracle General Ledger is creating or

dropping a summary template that affects available funds. Please try again later.

[APP–8061] An Account Hierarchy Editor session is already open. Please close the start up form

before opening another session.

[APP–8062] You must use the historical rate type with a historical amount.

[APP–8063] You can only use this budget rule with a twelve period calendar.

[APP–8064] You cannot delete the default intercompany account.

[APP–8065] You cannot update the source, category, or type for the default intercompany account.

[APP–8066] You have entered an invalid budget organization password.

[APP–8067] Oracle General Ledger could not retrieve profile option &PROFILE. Contact your

system administrator.

[APP–8068] The summary account included in your formula is not defined for your current set of

books.

[APP–8069] Oracle General Ledger could not find a validation type for the value set ID &VSID.

Please contact your support representative.

[APP–8070] Your journal batch is out of balance and suspense posting is not allowed for this set of

books.

[APP–8071] The conversion date must be within the period selected for this journal batch.

[APP–8072] The effective date must be within the period selected for this journal batch.

[APP–8073] There are no business days in this period.

[APP–8074] Your journal batch is out of balance and there is no reserve for encumbrance account

defined for your set of books.

[APP–8075] This period is after the reversal period of one or more of the journals in your batch.

[APP–8076] The budget you selected for this journal is not defined.

[APP–8077] The category of this journal has not been defined.

[APP–8078] No conversion rate has been defined for the given currency, conversion date, and

conversion type.

[APP–8079] The conversion type for this journal has not been defined.

[APP–8080] The encumbrance type for this journal has not been defined.

[APP–8081] The period for this journal has not been defined.

[APP–8082] The source of this journal has not been defined.

[APP–8083] This date is not a business day.

[APP–8084] Please enter an effective date in an Open or Future Enterable period.

[APP–8085] There are no business days in the period containing this date.

[APP–8086] One or more of the journal entries in your batch is marked for reversal into a period

that is not Open or Future Enterable.

[APP–8087] Your journal entry is marked for reversal into a period that is not Open or Future

Enterable.

[APP–8088] All journals in your batch have already been reversed or are unreversable.

[APP–8089] Please wait until funds checking completes before reversing your journal.

[APP–8090] Please open the period you have selected for this batch before posting.

[APP–8091] Please open the budget year for your batch before posting.

[APP–8092] Please open the encumbrance year for your batch before posting.

[APP–8093] Please correct your batch control total violation before posting.

[APP–8094] One or more of the budget journals in your batch is for a frozen budget. Please

unfreeze the budget before posting your batch.

[APP–8095] Your batch is already selected for posting.

[APP–8096] Your batch is already being posted.

[APP–8097] You can only reverse batches that have one or more journal entries.

[APP–8098] Your reversal date must be the same as or after the effective dates of all of the journals

within your batch.

[APP–8099] Your reversal date must be the same as or after your effective date.

[APP–8100] There are no business days after the journal effective date in this period.

[APP–8101] You must require budget journals for funding budgets.

[APP–8102] Your account must have a natural account segment.

[APP–8103] You can only copy actual batches and journal entries.

[APP–8104] The Net Income account must be non–postable. Enter a different account or disable

posting for this account using the GL Accounts form.

[APP–8105] You cannot enable posting for a net income account.

[APP–8106] The Net Income account must be non–postable. Enter a different account or disable

posting for at least one segment value using the Define Segment Values form.

[APP–8107] You must archive your &TYPE before you can purge.

[APP–8108] There is no account segment defined in your chart of accounts structure. Please assign

the Account segment qualifier to one segment using the Key Segments form.

[APP–8109] No balance retrieved for this account.

[APP–8110] There are no child accounts associated with this summary account.

[APP–8111] There are no Open or Future Enterable periods in your set of books.

[APP–8112] Oracle General Ledger could not get a unique ID from the sequence &SEQUENCE.

Contact your system administrator.

[APP–8113] You cannot drill down this journal line. Verify that subledger drilldown is enabled and

the journal originated from AP/AR subledger.

[APP–8114] You can only consolidate actual balances using the transactions method.

[APP–8115] You can only generate this batch between the defined start and end dates.

[APP–8116] You can only define one Detail Rollup rule per parent segment value. Use the

subsidiary segment ranges region to enter additional subsidiary ranges.

[APP–8117] You cannot define additional rules when using a copy value or single value rule.

[APP–8118] You cannot assign more than one unit of measure to an account.

[APP–8119] You entered overlapping account ranges for your Detail Rollup rule.

[APP–8120] You cannot requery without selection criteria. Please close this window and open the

Account Inquiry form again.

[APP–8121] Your summary account does not exist. Please use the Summary Accounts form to

create new summary accounts.

[APP–8122] You can only enter subsidiary segment ranges for the Detail Rollup rule.

[APP–8123] You cannot run consolidation for budget balances if your parent and subsidiary sets of

books have different calendars.

[APP–8124] Use transactions method only for sets of books with the same functional currency.

[APP–8125] Oracle General Ledger was unable to allocate memory for variable &VAR in

&ROUTINE. Contact your system administrator.

[APP–8126] Oracle General Ledger was unable to create account &CSEGVALS in &ROUTINE.

Please verify that all segment values are enabled and that this account does not violate any cross

validation rules.

[APP–8127] Oracle General Ledger was unable to write value &VALUE to form field &FIELD

from &ROUTINE. Contact your support representative.

[APP–8128] Oracle General Ledger detected an invalid value &VALUE for argument &ARG

passed to &ROUTINE. Contact your support representative.

[APP–8129] Oracle General Ledger detected an invalid number of arguments passed to

&ROUTINE. Contact your support representative.

[APP–8130] Oracle General Ledger could not retrieve any set of books information for set of books

ID &SOB_ID. Contact your system administrator.

[APP–8131] Oracle General Ledger could not retrieve your set of books information. Please make

sure the profile option GL Set of Books Name is set up properly for your responsibility.

[APP–8132] You cannot update the source or category for the default suspense account.

[APP–8133] &PROCEDURE procedure raised unhandled exception &EVENT.

[APP–8134] You cannot enter a formula when using AutoOffset.

[APP–8135] Oracle General Ledger was unable to get the install status of JG from &ROUTINE.

Contact your system administrator.

[APP–8136] The reversal period for this journal has not been defined.

[APP–8137] This date is after the reversal date of one or more of the journals in your batch.

[APP–8138] You can only use standard amount types (PTD or YTD) with budget balances.

[APP–8139] You can only use standard amount types (PTD or YTD) with revenue and expense

accounts.

[APP–8140] This date must be within an open encumbrance year.

[APP–8141] There is a gap in your &CALENDAR_NAME calendar. Not all dates between

&START_DATE and &END_DATE are assigned to a period. Please fix the calendar or pick

another one.

[APP–8142] Please reverse your batch from the primary set of books.

[APP–8143] Please reverse your journal from the primary set of books.

[APP–8144] You cannot drill down from this journal line. Please ensure that:

– Payables is the journal source.

– Import Journal References is enabled for Payables in the Journal Sources form.

– Accounts Payable is installed on the same instance as General Ledger.

[APP–8145] You cannot drill down from this journal line. Please ensure that:

– Receivables is the journal source.

– Import Journal References is enabled for Receivables in the Journal Sources form.

– Accounts Receivable is installed on the same instance as General Ledger.

[APP–8146] You cannot drill down from this journal line. Please ensure that:

– Consolidation is the journal source.

– Import Journal References is enabled for Consolidation in the Journal Sources form.

– The consolidation data is from a subsidiary in the same instance as this set of books.

[APP–8147] You cannot drill down from this journal line. Please ensure that Move/Merge is the

journal source.

[APP–8148] Consolidated amount does not tie to subsidiary balance. Please verify validity.

[APP–8149] You cannot enter ’D’ for every segment of a summary template because this would

create a summary account for every detail account. Summary accounts are meant to summarize

groups of detail accounts.

[APP–8150] Only Standard balances are available for budgets.

[APP–8151] There is no record for the lookup type ’ALL’ in the lookup table.

[APP–8152] Could not find an approver for this employee.

[APP–8153] Cannot find a manager for this employee.

[APP–8154] If you want to enable average balance processing, your accounting periods must

include no more than 35 days. Please choose a different accounting calendar or period type.

[APP–8155] Invalid GL Find Approver Method.

[APP–8156] This date is either in a Never Opened period or in an undefined period. Please choose

another date.

[APP–8157] The period for this batch is in an unopened budget year.

[APP–8158] You cannot use this budget rule with the current rounding option because your period

range does not contain all periods to which the amount should be distributed. Please choose a

different rounding option.

[APP–8159] This batch has a control total violation.

[APP–8160] The period for this batch is in an unopened encumbrance year.

[APP–8161] One or more of the budget journals in this batch is for a frozen budget.

[APP–8162] The batch period is not open or future enterable for the set of books.

[APP–8163] Funds are not reserved for this batch.

[APP–8164] There is no consolidation journal for the current consolidation process status.

[APP–8165] This batch contains untaxed journals.

[APP–8166] Your subsidiary, as specified by your Intercompany: Subsidiary profile option, must

have the same chart of accounts as your set of books, as specified by your GL Set of Books Name

profile option.

[APP–8167] This consolidation hierarchy is currently being constructed for another user. Please try

again later.

[APP–8168] Please enter a valid amount type.

[APP–8169] This mapping set consolidates a parent set of books as a subsidiary of itself. Please

check your mapping and mapping set definitions.

[APP–8170] You cannot delete this mapping because you have consolidated at least once using this

mapping.

[APP–8171] This mapping is part of a mapping set. Remove the mapping from the mapping set

before deleting this mapping.

[APP–8172] You have already translated average balances using different optional amount types.

Changing your optional amount types would invalidate your past translated average balances.

Therefore, you must purge all translated average balances before changing your optional average

translation amount types.

[APP–8173] You cannot use detail ranges with a summary transfer level.

[APP–8174] You must assign an action for each parent segment.

[APP–8175] You cannot use parent ranges with the detail transfer level.

[APP–8176] Quarter Average–to–Date balances are consolidated into the first period of the quarter

of the standard period you selected. This period does not exist.

[APP–8177] You may only select the Summary Transfer Level when the Using is Parent or Parent

Ranges.

[APP–8178] You may only select Detail Transfer Level when the Using is Parent or Detail Ranges.

[APP–8179] You may only select between Parent and Parent Ranges when the Transfer Level is

Summary.

[APP–8180] You may only select between Parent and Detail Ranges when the Transfer Level is

Detail.

[APP–8181] This consolidation includes Parent Value and/or Parent Rollup Ranges rules, which are

only available when consolidating balances.

[APP–8182] Year Average–to–Date balances are consolidated into the first period of the year of the

standard period you selected. This period does not exist.

[APP–8183] You may only select Parent or Detail Ranges when your consolidation method is

transactions.

[APP–8184] Quarter Average–to–Date balances are consolidated into the first period of the quarter

of the standard period you selected. This period must be Open or Future enterable.

[APP–8185] This consolidation mapping has expired.

[APP–8186] Oracle General Ledger could not retrieve your subsidiary information. Please make

sure the profile option Intercompany: Subsidiary is set up properly for your responsibility.

[APP–8187] The current set of books does not match the parent or the subsidiary set of books for

this consolidation mapping.

[APP–8188] The Usage is Average. Average balances is not enabled for the subsidiary set of books

in this consolidation mapping.

[APP–8189] The Amount type is EOD. Average balances is not enabled for the subsidiary set of

books in this consolidation mapping.

[APP–8190] This form failed to submit your concurrent request for mapping &MAPPING. Please

ensure that your concurrent manager is functioning.

[APP–8191] You can only use the Balances method when you have defined Summary rollup rules.

[APP–8192] Please note: You have one or more unmapped subsidiary segments. This consolidation

will include summary accounts which total all values for the unmapped segments. Therefore, please

ensure that your summary templates are defined with ’T’ for the unmapped segments.

[APP–8193] You can only consolidate average balances if: – Average balance processing is enabled

in both the subsidiary and parent sets of books. – The parent set of books is a consolidation set of

books. – The consolidation method is Balances.

[APP–8194] Year Average–to–Date balances are consolidated into the first period of the year of the

standard period you selected. This period must be Open or Future Enterable.

[APP–8195] This rollback segment is currently not available. Please ensure that this rollback

segment is online before running the applicable programs.

[APP–8196] GL_CALCULATE_TAX_PKG.setup received an invalid batch ID &BATCH_ID.

Please contact your system administrator.

[APP–8197] GL_CALCULATE_TAX_PKG.setup received an invalid journal entry ID

&HEADER_ID. Please contact your system administrator.

[APP–8198] The tax account for tax code &TAX_CODE does not exist.

[APP–8199] GL_CALCULATE_TAX_PKG.setup received an invalid tax level &TAX_LEVEL.

Please contact your system administrator.

[APP–8200] No tax options have been defined for the current set of books.

[APP–8201] No tax options have been defined for this batch’s set of books and organization.

[APP–8202] No tax options have been defined for this journal’s set of books and organization.

[APP–8203] Please do not change this effective date rule to ensure that consolidation journals are

always posted on the first day of an accounting period.

[APP–8204] Your transaction(s) failed &FUNDS_ACTION.

[APP–8205] There is an invalid account segment value associated with one of your summary

accounts.

[APP–8206] You cannot define conversion rates for an EMU currency. Oracle General Ledger will

default to the EURO currency.

[APP–8207] You cannot define conversion rates to an EMU currency. Oracle General Ledger will

default to the EURO currency.

[APP–8208] If you choose not to import journal references for consolidation journals, you will not

be able to drill between sets of books from consolidation journal entries.

[APP–8209] Please enter a GL Date which is in an Open or Future Enterable period in both the

sender’s and receiver’s sets of books.

[APP–8210] Please enter a GL Date which is in an Open or Future Enterable period in the receiver’s

set of books.

[APP–8211] Please enter a GL Date which is in an Open or Future Enterable period in the sender’s

set of books.

[APP–8212] Your journal contains one or more taxable lines. Please remove the tax codes before

changing the Tax field to Non–Taxable.

[APP–8213] No tax options have been defined for the current set of books.

[APP–8214] No tax options have been defined for this journal’s set of books and organization.

[APP–8215] Your current set of books is different from the set of books associated with this batch.

Please use a responsibility associated with your batch’s set of books to view this batch.

[APP–8216] Your current set of books is different from the set of books associated with this journal.

Please use a responsibility associated with your journal’s set of books to view this journal.

[APP–8217] One or more of your tax accounts is invalid. The invalid tax accounts are displayed in

your journal line descriptions. Please correct these tax accounts before posting this journal.

[APP–8218] The Source Account is an asset or liability account. Please use an asset or liability

account for the Target Account.

[APP–8219] For Move/Merge requests, please use the same value for the

&BAL_SEG_LEFT_PROMPT balancing segment in both the Source and Target Accounts.

[APP–8220] The Source Account is a budgetary debit or credit account. Please use a budgetary

debit or credit account for the Target Account.

[APP–8221] The Source Account is an owner’s equity account. Please use an owner’s equity

account for the Target Account.

[APP–8222] The Source Account is a revenue or expense account. Please use a revenue or expense

account for the Target account.

[APP–8223] The segments specified or left blank in the Target Account must correspond to the

segments specified or left blank in the Source Account.

[APP–8224] You can have only one Detail Rollup rule for each combination of subsidiary segment

and parent segment detail value.

[APP–8225] You can have only one Parent Rollup rule for each combination of subsidiary segment,

subsidiary segment parent value, and parent segment detail value.

[APP–8226] The current set of books is not the parent set of books. Please switch to the parent set of

books before posting your consolidation journals.

[APP–8227] A batch with batch ID &BID does not exist

[APP–8228] A budget organization with ID &BID does not exist

[APP–8229] A budget with budget version id &BUDID does not exist

[APP–8230] A consolidation with consolidation ID &CID does not exist

[APP–8231] The journal batch was not created by Consolidation using Transaction method with

Create Summary Journals option set to No

[APP–8232] There is no corresponding period for the given date.

[APP–8233] An encumbrance type with id &ENCID does not exist

[APP–8234] The first period &PERIOD does not exist for the set of books &SOBID

[APP–8235] A period with name &PERIOD does not exist in the set of books &SOBID

[APP–8236] A set of books with ID &SOBID does not exist

[APP–8237] The lookup code &CODE of lookup type &TYPE is missing

[APP–8238] The segment qualifier &QUAL must be assigned for your chart of accounts

[APP–8239] There is no corresponding open period for the given date.

[APP–8240] Your summary account is no longer valid because its summary template has either been

deleted or recreated. Please update the summary account.

[APP–8241] Your journal entry header’s effective date &DATE does not fall between your recurring

header’s: &HEADER_NAME start and end dates

[APP–8242] A period rate is not defined for the currency and the period to be revalued. You cannot

change rates between EMU currencies in this form. Please define a period rate in the Period Rates

form.

[APP–9500] A fatal error occurred when submitting your request to the concurrent manager.

[APP–9501] Please delete calculations before assigning accounts.

[APP–9502] Please delete account assignments before defining calculations.

[APP–9503] This operation will exceed the maximum report width of 255 characters.

[APP–9504] You can only define one exception per column.

[APP–9505] You cannot update a standard column set. Please use the AutoCopy form to copy this

column set and then update the new column set.

[APP–9506] You cannot delete a column that belongs to a standard column set.

[APP–9507] You cannot delete a standard column set.

[APP–9508] You cannot use list of values until you assign a row set or column set.

[APP–9509] You cannot delete a report that is used in a report set.

[APP–9510] You cannot create a new report for the report set in this form. Use the Financial Report

Set form.

[APP–9511] You cannot delete a report from a report set in this form. Use the Financial Report Set

form.

[APP–9512] Error in submitting report. Please check your concurrent manager.

[APP–9513] A database error occurred. Please contact your system administrator.

[APP–9514] An internal applications error occurred. Please contact your support representative.

[APP–9515] This period does not exist.

[APP–9516] For a row or column, you can assign accounts OR calculations, but not both.

[APP–9517] You have reached the maximum of 20 columns in the column set builder. You cannot

add any more columns using the column set builder.

[APP–9518] An error occurred while creating a database link. Please ensure that all entered

parameters are correct.

[APP–9519] Unable to drop the database link. Please contact your system administrator.

[APP–9520] You cannot delete the Time dimension.

[APP–9521] You cannot delete segments from a hierarchy.

[APP–9522] You can only change the status from New to Cancel.

[APP–9523] A financial data set already exists for this chart of accounts.

[APP–9524] Please assign the Time dimension to this financial data item.

[APP–9525] A &OBJECT that you have modified or deleted cannot be saved because it is used in a

frozen financial data set. Please re–query without saving.

[APP–9526] Please enter a root node for every segment assigned to this dimension.

[APP–9527] Please enter a valid object name.

[APP–9528] Please enter a valid object prefix.

[APP–9529] This root node value is invalid.

[APP–9530] Please enter a valid value prefix.

[APP–9531] A financial data item cannot have more than &NUM_DIM dimensions.

[APP–9532] You cannot delete a dimension that is used in a financial data item or hierarchy.

[APP–9533] The base dimension of this hierarchy is used in a frozen data set. You cannot delete

this hierarchy.

[APP–9534] You cannot delete a segment range set that is used in a dimension or financial data

item.

[APP–9535] You cannot delete a financial data item that is used in a financial data set.

[APP–9536] Internal Flexfield Exception

[APP–9537] A fatal error occurred: the account cannot be loaded. Please contact your system

administrator.

[APP–9538] Warning: Unable to set printer options for this FSG report. Using default printer

options.

[APP–9539] &PROGRAM errored out with the following message:

[APP–9540] Page expand range has no values.

[APP–9541] A fatal error occurred: Cannot find report with report ID &REPORT_ID. Request was

not submitted.

[APP–9542] This column set has more than 20 columns. You can only view the first 20 columns

using the column set builder.

[APP–9543] ERROR: Encountered error while transferring &SUB_COMP_TYPE for

&COMP_TYPE ’&COMP_NAME’. Aborting transfer of this &COMP_TYPE.

[APP–9544] WARNING: A &COMP_TYPE named ’&COMP_NAME’ already exists in the target

database. The existing definition in the target database will be used.

[APP–9545] ERROR: A &COMP_TYPE named ’&COMP_NAME’ does not exist in the source

database.

[APP–9546] LOG: EXCEPTION RAISED! Error number: &ERROR_NUM. Error message:

[APP–9547] LOG: Chart of accounts mismatch. Source id = &SRC_ID. Id specified in submission =

&SUB_SRC_ID.

[APP–9548] Encountered error while transferring &COMP_TYPE ’&COMP_NAME’. Cancelling

transfer of this &COMP_TYPE.

[APP–9549] WARNING: Column ’&COLUMN_NAME’ does not exist in any column set in the

target database. Omitting column name from row order ’&COMP_NAME’.

[APP–9550] ERROR: Chart of accounts ’&COA’ does not exist in the source database.

[APP–9551] WARNING: Encountered error while transferring &SUB_COMP_TYPE for

&COMP_TYPE ’&COMP_NAME’. Omitting &SUB_COMP_TYPE from &COMP_TYPE

definition.

[APP–9552] WARNING: A &SUB_COMP_TYPE named ’&SUB_COMP_NAME’ does not exist in

the target database. Omitting &SUB_COMP_TYPE from &COMP_TYPE ’&COMP_NAME’.

[APP–9553] Encountered warning while transferring &COMP_TYPE ’&COMP_NAME’.

[APP–9554] WARNING: Chart of accounts mismatch for &COMP_TYPE ’&COMP_NAME’ in the

source database. Aborting transfer of this &COMP_TYPE.

[APP–9555] Another user is creating a database link. Please try again.

[APP–9556] You do not have permission to create database links. Please contact your system

administrator.

[APP–9557] Encountered error while trying to release lock. Please contact your system

administrator.

[APP–9558] You cannot add this dimension because it contains a segment that is already used by

another dimension of this summary financial data item.

[APP–9559] You cannot enter multiple segments for a summary dimension.

[APP–9560] This summary template is no longer valid. Please select a valid summary template.

[APP–9561] Fatal Error – Cannot find content set with content set ID: &CONTENT_SET_ID.

Request is not submitted.

[APP–9562] The sort column in your row order does not exist

[APP–9999] FNDXLOAD – Not enough arguments or argument mismatched Usage: FNDXLOAD

<data filespec> [<entity> <param=value>] where

<username/password> is the APPS account.

<config filespec> identifies the loader config file.

<data filespec> identifies the script file to read or to write.

<filespec> could be in the form:

@<application_short_name>:<subdir>/.../<file>

<mode> is the mode of operation:

DOWNLOAD

UPLOAD The loader works in either download or upload mode. If the ”DOWNLOAD” argument is

given with one or more download parameters, it will download matching values to the data file. If

the ”UPLOAD” argument is given, it will upload the data file to the database.

[APP–9999] Modifying the currency derivation fields will cause inconsistencies in the revaluation,

translation, and period rates calculation processes. Do you wish to continue?

[APP–9999] No Euro base currency has been defined. No Euro derived currencies may be defined

until the Euro base currency is set.

[APP–9999] Only one Euro base currency may be defined.

[APP–9999] The effective date of a Euro Derived currency must be later than the effective date of

the Euro Currency (&EFFDATE).

[APP–9999] This employee is already assigned to user &USER. Employees assigned to more than

one user may cause errors in applications.

[APP–9999] Usage: WFLOAD <apps/pwd> 0 Y {UPLOAD | DOWNLOAD | UPGRADE |

FORCE} [@<appl–shortname>:]<filepath> [<item type>]

[APP–9999] Usage: WFMAIL <apps/pwd> 0 Y

[@<appl–shortname>:]<config–filepath>

[APP–9999] Usage: WFRESGEN <apps/pwd> 0 Y {DATABASE | FILE} <destination file

or database> <source message file> ...

[APP–9999] You no longer have access to the specific information requested in this screen.

[APP–10000] &ERROR occurred in &CALLING_SEQUENCE with parameters

(&PARAMETERS) while performing the following operation: &DEBUG_INFO

[APP–10001] You cannot enter an amount which is greater than the total amount of the invoice.

Re–enter.

[APP–10002] You cannot enter an amount which is greater than the amount available on the

prepayment. Re–enter.

[APP–10003] You are about to &ACTION for &TYPE number (&NUMBER). Continue?

[APP–10004] Enter the amount you wish to apply.

[APP–10005] You must specify either percent due or amount due.

[APP–10006] The date you entered is not in an Open accounting period. Open the period in ”AP

Accounting Periods.”

[APP–10007] The date you entered is beyond the latest open encumbrance year. Update the latest

encumbrance year in general ledger, or contact the system administrator.

[APP–10008] You cannot release a hold without entering a Release Name. Enter a Release Name.

[APP–10009] You cannot manually release this type of hold. Correct the condition that caused the

hold and resubmit Approval.

[APP–10010] You cannot apply the same hold more than once for an invoice.

[APP–10011] Payables cannot get the proper application installation information. Contact your

Oracle Support representative.

[APP–10012] Please choose the button corresponding to the process you wish to begin.

[APP–10013] You attempted to initiate a purge process while a purge process is already running.

Wait for the current process to complete before initiating another process.

[APP–10014] You cannot commit before you enter values in all required fields. Enter all required

values before you commit.

[APP–10015] You entered a duplicate purge name. Enter a unique name.

[APP–10016] You cannot enter a duplicate period name. Re–enter.

[APP–10017] You cannot enter a number for Days From that is less than the number for Days To.

Re–enter.

[APP–10018] You cannot enter a duplicate period line Sequence Number. Re–enter.

[APP–10019] You cannot delete an invoice batch that contains invoices. Delete all invoices in a

batch, then delete the batch.

[APP–10020] Rate information is not available for this currency, date, and exchange rate type. Enter

rate information for this currency, date, and exchange rate type in ”Daily Rates.”

[APP–10021] The exchange rate may not be zero or a negative number. Re–enter.

[APP–10022] The Document Number you entered is below the Next Available Number. Verify that

the Document Number you entered is unused then either confirm that you want to proceed, or

re–enter the Document Number.

[APP–10023] The first Document Number you entered is greater than the last Document Number.

Adjust either the first Document Number or the Last Document Number.

[APP–10024] This value already exists. Re–enter.

[APP–10025] This must be a positive number. Re–enter.

[APP–10026] The Payment Date must be on or after the system date. Re–enter.

[APP–10027] Payables is reserving the payment document...

[APP–10028] The minimum amount cannot be greater than the maximum amount. Re–enter.

[APP–10029] The High Payment Priority you entered has a lower priority than the Low Priority you

entered. Adjust either the High Payment Priority or the Low Payment Priority. Remember, Payables

considers 1 to be the highest payment priority and 99 to be the lowest.

[APP–10030] Manual Numbering Document Sequences are not supported for payment batches.

[APP–10031] All required fields have not been entered.

[APP–10032] The payment amount plus the discount amount cannot be greater than the amount due.

Re–enter.

[APP–10033] You cannot partially pay a prepayment.

[APP–10034] You cannot pay a Pay Alone invoice with other invoices on the same payment

document unless the payment document is a Manual payment. Update the Pay Alone status of an

invoice in the Invoice Workbench.

[APP–10035] This invoice is past due. Interest is due on this invoice.

[APP–10036] You cannot commit if a record has not been selected. Select a record.

[APP–10037] The payment amount cannot be different from the running total. Re–enter the

payment amount.

[APP–10038] You can only pay &STUB invoices per single computer–generated payment with this

Payment Document. Create another payment for the additional invoice(s), or select a Payment

Document that can accommodate more invoices.

[APP–10039] The start date cannot be after the end date. Re–enter.

[APP–10040] The To Document number you entered is less than the From Document number.

Re–enter.

[APP–10041] Payables could not flexbuild valid accounts for some payment distributions. Fix the

invalid accounts in ”Invalid GL Accounts”.

[APP–10042] The bank account you selected does not allow zero amount payments. Select a bank

account that allows zero amount payments.

[APP–10043] The payment document format you chose is for zero amount payments only.

Continue?

[APP–10044] Payables will use the Asset GL Account since you have not defined a Cash Clearing

GL Account for this payment document.

[APP–10045] The Document Number you entered is below the last document used.

[APP–10046] Enter a number between 1 and &NUM.

[APP–10047] The Hold All Payments option is enabled for this supplier site. You can only pay

invoices entered for this supplier site by using a manual payment. Control the Hold All Payments

option in ”Suppliers.”

[APP–10048] You have not selected a record. Select at least one record.

[APP–10049] You chose Enter/Adjust Invoices or View Invoices for a payment document that does

not have any invoices associated with it because it is a Spoiled, Set Up or Overflow payment

document. Payment documents with these statuses have no associated invoices and are

automatically voided by Payables when you confirm a payment batch.

[APP–10050] You cannot perform an action on the payment you selected.

[APP–10051] You can only perform actions on payments of the same type. Deselect one or more

payments.

[APP–10052] The Allow Print system option is not enabled. Enable the Allow Print system option

in ”Payables Options,” or contact the system administrator.

[APP–10053] You cannot void a payment document that has been used to pay prepayments that

have been applied to invoices. Unapply the prepayments paid by this payment then void the

payment document.

[APP–10054] Enter a Void Date that is on or after the most recent invoice payment GL Date of

&GL_DATE. Re–enter.

[APP–10056] Payables is unable to submit your concurrent request. Contact the system

administrator.

[APP–10057] Payables submitted the program to create your single computer–generated payment.

The request number is &REQUEST. Check the status in the ”Concurrent Requests Summary”.

[APP–10058] Request number is &REQUEST. Check the status of the request in ”Concurrent

Requests Summary.”

[APP–10059] You have not entered a Hold Name.

[APP–10060] The Allow Void and Replace option is not available. Enable the Allow Void and

Replace option in ”Payables Options,” or contact the system administrator.

[APP–10061] You can only select one payment for this action. Deselect one or more payments.

[APP–10062] The payment document has no associated invoice payments.

[APP–10063] You cannot enter a negative payment amount. Re–enter.

[APP–10064] The Payment Amount you entered is not equal to the invoice total. Adjust either the

Payment Amount or the invoices you selected for payment.

[APP–10065] The supplier name has changed since payment creation due to a supplier merge.

[APP–10066] The supplier site has changed since payment creation due to a supplier merge.

[APP–10067] You have not entered a Match Amount.

[APP–10068] Starting match to invoice &INVOICE_NUM...

[APP–10069] The total of the distribution match amounts does not equal the Control Total. Adjust

either the Match Amount in the Match to PO window or adjust the Match Amount of one or more of

the purchase order distributions to which you matched.

[APP–10070] You cannot prorate across all invoice distributions if at least one of the invoice

distributions was created through PO matching. Choose Distribute to manually distribute the tax,

freight, or miscellaneous amount.

[APP–10071] This must be a negative number. Re–enter.

[APP–10072] Starting match to invoice &INVOICE_NUM, distribution &DIST_NUM...

[APP–10073] You cannot adjust the Quantity Billed for a shipment line to be less than zero.

Re–enter the Quantity Invoiced.

[APP–10074] This purchase order line is closed.

[APP–10075] The payment terms you entered for this invoice differ from the payment terms on the

purchase order (&PO_TERMS). Payables defaults the supplier site’s payment terms

(&VENDOR_TERMS) to the invoice, unless the Recalculate Scheduled Payment option is Yes, in

which case the most advantageous terms will be used. You can optionally modify the terms. Verify

that the payment terms for the invoice are correct and adjust if necessary.

[APP–10076] Starting shipment match to PO &PO_NUM, shipment &SHIP_NUM...

[APP–10077] Starting shipment price correction to PO &PO_NUM, shipment &SHIP_NUM...

[APP–10078] You have not entered a Match Amount. Enter two of the following fields and Payables

automatically calculates and displays the third: Quantity Invoiced, Unit Price, Match Amount. For

example, if you enter Quantity Invoiced and Unit Price, Payables uses the equation Quantity

Invoiced x Unit Price = Match Amount to determine Match Amount.

[APP–10079] This number cannot be zero. Re–enter.

[APP–10080] This match would result in an overbill.

[APP–10081] You cannot reduce the total Quantity Billed below zero. Re–enter the Quantity

Invoiced.

[APP–10082] For a Price Correction, you cannot enter a Quantity Invoiced that is greater than the

Quantity Billed. Re–enter the Quantity Invoiced.

[APP–10083] This number cannot be a negative number. Re–enter.

[APP–10084] This number cannot be a positive number. Re–enter.

[APP–10085] Starting shipment match to PO &PO_NUM, shipment &SHIP_NUM, distribution

&DIST_NUM...

[APP–10086] Starting price correction to PO &PO_NUM, shipment &SHIP_NUM, and distribution

&DIST_NUM...

[APP–10087] This number cannot be zero or a positive number. Re–enter.

[APP–10088] This number cannot be zero or a negative number. Re–enter.

[APP–10089] You cannot enter a date in the past. Re–enter.

[APP–10090] The total percent distribution for a Distribution Set must be either 0 or 100.

[APP–10091] This action is not allowed. Refer to the User’s Guide or to the on–line help.

[APP–10092] You cannot simultaneously perform actions on payment batches with different

statuses. Deselect one or more payment batches.

[APP–10093] Payables submitted your payment batch request to Select Invoices. The request

number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10094] Payables submitted your payment batch request to Build Payments. The request

number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10095] Payables submitted your payment batch request to print the Preliminary Register. The

request number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10096] Payables submitted your payment batch request to Format Payments. The request

number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10097] Payables submitted your payment batch request to Confirm Payment Batch. The

request number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10098] Payables submitted your payment batch request to print the Final Register. The

request number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10099] Payables submitted your payment batch request to print the Separate Remittance

Advice. The request number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10100] Payables submitted your payment batch request to Cancel Payment Batch. The

request number is &request. Check the status in the ”Concurrent Requests Summary”.

[APP–10101] There is at least one unfinished concurrent request for this payment batch. Check the

status of this request in the ”Concurrent Requests Summary”.

[APP–10102] No payments exist for this payment batch. Use the Modify Payment Batch window of

the Payment Workbench to add invoice payments to this payment batch, or cancel this payment

batch, review the payment batch criteria and submit another payment batch.

[APP–10103] You cannot reverse this distribution. See ”Adjusting Invoices” in the User’s Guide or

in the on–line help.

[APP–10104] Prepayments cannot have more than one Tax type distribution.

[APP–10105] Oracle Projects is not installed.

[APP–10106] The Transaction Code profile option is currently disabled. Enable the profile option in

”System Profile Values” or contact the system administrator.

[APP–10107] You cannot enter more than one Item type distribution and one Tax type distribution

for a prepayment.

[APP–10108] An error has occurred while trying to commit.

[APP–10109] You cannot delete this invoice distribution. See ”Adjusting Invoices” in the User’s

Guide or in on–line help.

[APP–10110] You cannot enter new distributions for this invoice. See ”Adjusting Invoices” in the

User’s Guide or in on–line help.

[APP–10111] When you update the sign (+/–) of an invoice distribution amount, you must also

update the sign of the Statistical Quantity of the invoice distribution.

[APP–10112] You cannot choose Done for Final Matching. Enter Yes and Payables automatically

updates the field to Done when you commit.

[APP–10113] You cannot adjust an invoice distribution if the invoice has been selected for payment.

[APP–10114] You cannot prorate if the distribution amount is zero.

[APP–10115] Payables defaults the payment terms from the supplier site to the invoice. Verify the

payment terms for credit or debit memos. You may want to change the payment terms to Immediate

for credit and debit memos.

[APP–10116] You cannot reduce the amount of a credit or debit memo below the amount already

applied to another invoice(s). Adjust the amount of the credit or debit memo so that the amount is

greater than or equal to the amount to the amount already applied to another invoice(s).

[APP–10117] You cannot delete a prepayment that has been applied to an invoice(s). Unapply all

prepayment applications, void the payment document that paid the prepayment, then delete the

prepayment.

[APP–10118] You cannot delete an invoice to which prepayments have been applied. Unapply all

prepayment applications for the invoice, then delete the invoice.

[APP–10119] The invoice distribution total is not equal to the invoice amount. During Approval,

Payables will place a Distribution Variance hold to all invoices where the invoice distribution total

does not equal the invoice amount. This hold prevents both payment and the creation of journal

entries. Adjust the distribution total.

[APP–10120] The amount subject to discount cannot be greater than the invoice amount. Adjust the

amount subject to discount.

[APP–10121] The invoice payment amount cannot be greater than the Amount Remaining on the

scheduled payment. Re–enter the Payment Amount.

[APP–10122] WARNING: You entered an invoice date that is in the future.

[APP–10123] The Hold Future Invoices option is enabled for this supplier site. A supplier hold will

automatically be placed on this invoice. Use ”Suppliers” to control the Hold Future Invoices option.

[APP–10124] This supplier is on hold. Payables will calculate the balance anyway.

[APP–10125] You entered an invoice amount that exceeds the invoice limit for this supplier site.

An Amount hold will automatically be applied to this invoice and will prevent payment. Use

”Suppliers” to control the invoice amount limit for a supplier site. You can manually release

Amount holds in the Holds window of the Invoice Workbench.

[APP–10126] You cannot reduce the liability amount below the amount already paid. Re–enter.

[APP–10127] You cannot delete invoices that have a status of Posted or invoices that are matched to

a purchase order.

[APP–10128] There is no active pay site available for this supplier. Verify the supplier site for the

invoice. Use ”Suppliers” to either enable the Pay Site option for an existing supplier site or enter a

new supplier pay site.

[APP–10129] You cannot adjust or delete this invoice distribution because you are using

encumbrance accounting and the invoice distribution has been approved. You can reverse and

re–enter invoice distributions in the ”Distributions” window in the Invoice Workbench.

[APP–10130] The system option that controls the ability to update paid or partially paid invoices

has been disabled. Enable the Allow Paid Invoice Adjustments system option in ”Payables

Options”, or contact the system administrator.

[APP–10131] When you update the supplier name, number, or site for an existing invoice, Oracle

Payables does not update the invoice with the defaults from the new supplier or site. Update each

invoice value individually.

[APP–10132] This invoice is selected for payment and cannot be adjusted or deleted.

[APP–10133] You must enter a purchase order number for this invoice type. Enter a valid purchase

order or change the invoice type.

[APP–10134] Invoice number &SIMILAR is similar to this credit/debit memo. You are entering a

credit or debit memo for the same supplier, site, currency and amount as an existing debit or credit

memo. Verify that this is not a duplicate.

[APP–10135] If you adjust tax information at the invoice header level after invoice distributions

have been created, Payables will not automatically update the invoice distributions with the updated

tax information. Manually update each invoice distribution with the updated tax information.

[APP–10136] This date is more than one year old. Verify that this is the date you wish to enter.

[APP–10137] The date you entered is before the invoice date.

[APP–10138] The date you entered is before the terms date.

[APP–10139] You cannot enter a Discount Amount that is greater than Payment Amount. Re–enter.

[APP–10140] The Discount Date you entered is after the Due Date. Re–enter.

[APP–10141] You entered a Discount Date without entering a corresponding Discount Amount.

Enter a Discount Amount or clear the Discount Date.

[APP–10142] You entered a Second Discount Date without entering a corresponding Second

Discount Amount. Enter a Second Discount Amount or clear the Second Discount Date.

[APP–10143] You entered a Third Discount Date without entering a corresponding Third Discount

Amount. Enter a Third Discount Amount or clear the Third Discount Date.

[APP–10144] Enter a value greater than or equal to zero.

[APP–10145] Enter a value less than or equal to zero.

[APP–10146] &TOTAL prepayments exist for this supplier. &AVAILABLE are available. To apply

or unapply prepayments, choose Actions and check Apply/Unapply Prepayments.

[APP–10147] The payment terms you entered for the invoice differ from the payment terms on the

purchase order (&PO_TERMS). Payables defaults the supplier site’s payment terms

(&VENDOR_TERMS) to the invoice, where you can optionally modify them. Verify that the

payment terms on the invoice are correct and modify them if necessary.

[APP–10148] Payables will use the default invoice currency you entered for the invoice batch rather

than the supplier site default invoice currency (&curr).

[APP–10149] You selected an electronic payment method but have not yet entered bank information

for the supplier and its sites. You must enter bank information for the supplier and its sites if you

want to pay the supplier using an electronic payment method. Enter bank information for suppliers

and supplier sites in ”Suppliers.”

[APP–10150] The Voucher Number you enter must be a number of 8 digits or less. Re–enter.

[APP–10151] Automatically calculate the invoice tax amount?

[APP–10152] The Cancel Invoice action is currently unavailable.

[APP–10153] You cannot apply a prepayment to a credit or debit memo.

[APP–10154] Select the document for which you would like to see an overview. If you select

”Prepayment,” Payables will show you an overview of the invoice that the prepayment was applied

to. If you select ”Payment,” Payables will show you the Payment Overview of the payment that paid

the invoice.

[APP–10155] You have not indicated the type of match you wish to perform. Indicate the type of

match.

[APP–10156] You cannot perform actions on a cancelled invoice.

[APP–10157] This window cannot be opened while performing a credit match. Close the Credit

Match window.

[APP–10158] This window cannot be opened while the Distributions window is active. Close the

Distributions window.

[APP–10159] This window cannot be opened while you are in Enter–Query mode. Execute the

query or cancel Enter–Query.

[APP–10160] This window cannot be opened while the Scheduled Payments window is active.

Close the Scheduled Payments window.

[APP–10161] This window cannot be opened while performing a match to a purchase order. Close

the Match to PO window.

[APP–10162] This window cannot be opened while performing a prepayment application. Close the

Apply Prepayments window.

[APP–10163] Use the Invoice Date as the Invoice Number?

[APP–10164] The last document number is greater than last available document number for the

payment document. Re–enter.

[APP–10165] The field you have selected to display is not used because the USSGL option, used

primarily in public sector accounting, is not enabled.

[APP–10166] The Discount Date you entered is before the Invoice Date. Re–enter.

[APP–10167] The Discount Date you entered is before the Terms Date. Re–enter.

[APP–10168] The field you have chosen to display is not used because Oracle Projects is not

installed.

[APP–10169] The purchase order number you entered is not valid. Enter the number of an approved

and open purchase order.

[APP–10170] An invoice you selected for payment cannot be paid because the supplier is different

from that of other invoices you also selected for payment. Check the supplier of each invoice.

[APP–10171] An invoice you chose for full payment cannot be paid because the supplier site is

different from that of other invoices that have also been selected for full payment. Check the

supplier site of each invoice.

[APP–10172] When selecting multiple invoices for full payment, all of the invoices must be the

same currency.

[APP–10173] An invoice or scheduled payment that you selected for full payment cannot be paid

because the payment method is different from that of other invoices or scheduled payments you

selected. Check the payment method of each invoice.

[APP–10174] An invoice you selected for full payment cannot be paid because it is designated as a

Pay Alone invoice and you selected multiple invoices for payment. Check the Pay Alone status of

each invoice.

[APP–10175] The number of invoices you selected to pay exceeds the number of invoices that

Payables can pay at once using this Pay In Full feature. Deselect one or more invoices.

[APP–10176] The USER EXIT (&USER_EXIT_NAME) did not run successfully. Contact your

Oracle Support representative.

[APP–10177] You can only clear or delete the last row of data shown in this window.

[APP–10178] You cannot enter a Gross Amount that is greater than the invoice amount. Re–enter

the Gross Amount.

[APP–10179] You cannot enter a positive Gross Amount for credit or debit memos. Re–enter the

Gross Amount.

[APP–10180] You cannot enter a Gross Amount that is less than zero for Standard, QuickMatch, and

PO Default invoice types. Re–enter the Gross Amount.

[APP–10181] You cannot choose Split for paid or partially paid scheduled payments.

[APP–10182] You cannot enter a total gross amount that exceeds the invoice amount. Re–enter the

Gross Amount.

[APP–10183] Check Funds

[APP–10184] Budgetary Control

[APP–10185] You cannot use the same Sequence Number for another period line. Re–enter.

[APP–10186] Please commit or clear your changes before continuing.

[APP–10187] An invoice you selected for full payment cannot be paid because it is not approved.

[APP–10188] An invoice or scheduled payment you selected for full payment cannot be paid

because it is already fully paid.

[APP–10189] You have made net adjustments to the liability of this invoice. Payables has made the

corresponding adjustments to the gross amount of the scheduled payments. You may also want to

adjust payment discounts for the scheduled payments.

[APP–10190] You have made net adjustments to the liability and/or discounts for this invoice.

Payables has made corresponding adjustments to the gross amount of one or more scheduled

payments. Any uncommitted changes you made in the Scheduled Payments window will be ignored.

You may want to adjust additional scheduled payments using the Scheduled Payments window.

[APP–10191] You cannot adjust the Liability GL Account of a fully encumbered invoice. Enter a

new, unencumbered invoice distribution. Then adjust the Liability GL Account.

[APP–10192] You cannot adjust the Liability GL Account of a fully posted invoice. Enter a new,

unposted invoice distribution. Then you can adjust the invoice Liability GL Account.

[APP–10193] You can not adjust distributions on this invoice because it has been paid and the

Allow Adjustments to Paid Invoices option is not enabled. Enable the Allow Adjustments to Paid

Invoices option in ”Payables Options” or contact the system administrator.

[APP–10194] Cash Basis Accounting is your Accounting Method and you are attempting to adjust

an invoice associated with a void payment that has not transferred to the general ledger. You cannot

adjust/delete this invoice until the void payment is transferred to the general ledger. Transfer

payments to the general ledger then adjust this invoice.

[APP–10195] This invoice has no scheduled payments. Create one or more scheduled payments for

this invoice.

[APP–10196] Payables must create a scheduled payment(s) before you can adjust the liability of this

invoice.

[APP–10197] Take all available discounts on these invoices?

[APP–10198] The action you are attempting to perform is not available to you. Either this form is

display only, or you do not have sufficient privileges to perform this action. Contact the system

administrator.

[APP–10199] You cannot navigate to ”Invoice Batches” because the invoice batch control system

option has been disabled. Navigate to the Invoice Workbench through ”Invoices”, enable the invoice

batch control system option in ”Payables Options”, or contact the system administrator.

[APP–10200] The document number you entered in the From field is not a set up check. Re–enter.

[APP–10201] The document number you entered in the To field is not a set up check. Re–enter.

[APP–10202] This range includes at least one document number that is not a set up check. Re–enter.

[APP–10203] The To document number you entered is a set up check. Re–enter.

[APP–10204] You cannot record a range with a status of Printed if the last document in the range is

an overflow document.

[APP–10205] The document number you entered in the From field exists in another range.

Re–enter.

[APP–10206] The Document Number you entered in the To field exists in another range. Re–enter.

[APP–10207] Payables could not select number of set up checks from the selected payment

document.

[APP–10208] The Document Number you entered is greater than the last available document

number for the payment document. Re–enter.

[APP–10209] You are recording as Printed more payments than exist for the payment batch.

Re–enter the range.

[APP–10210] You have already used this range of documents. Re–enter.

[APP–10211] You cannot update, clear or delete a range of payment document numbers that has

already been confirmed.

[APP–10212] The Document Number you chose to restart the batch is greater than the last available

document number for the payment document. Re–enter.

[APP–10213] The Document Number you entered to restart the batch must be greater than the

highest document number already recorded for the batch. Re–enter.

[APP–10214] The Document Number you entered is greater than the last available document

number for the payment document. Re–enter.

[APP–10215] Days cannot be negative. Re–enter.

[APP–10216] Payables submitted your payment batch programs. The request numbers are &first to

&last. Check the status in the ”Concurrent Requests Summary.”

[APP–10217] This action will delete some or all of the payment batch. Continue?

[APP–10218] You entered a period name for Special Invoice Amount1 without entering a Special

Invoice Amount1. Enter Special Invoice Amount1.

[APP–10219] You entered an amount for Special Invoice Amount1 without entering a period name.

Enter a period name for Special Invoice Amount1.

[APP–10220] You entered a period name for Special Invoice Amount2 without entering an amount

for Special Invoice Amount2. Enter Special Invoice Amount2.

[APP–10221] You entered an amount for Special Invoice Amount2 without entering a period name.

Enter a period name for Special Invoice Amount2.

[APP–10222] The system option that requires the entry of a tax name for an invoice has been

enabled. Enter a tax name, disable the require tax entry system option in ”Payables Options,” or

contact the system administrator.

[APP–10223] You entered a special invoice amount that is greater than the control amount.

Re–enter the special invoice amount.

[APP–10224] You must enter a Change % that is between –100 and 100. Re–enter.

[APP–10225] When entering a recurring invoice template, you must use a Full (100%) distribution

set.

[APP–10226] For this period type, there are insufficient periods left to equal the total Number of

Periods you have defined for this recurring invoice. Re–enter the First period, define more periods

for the Period Type, or choose another Period Type.

[APP–10227] The Number of Periods you entered exceeds the number of periods defined for this

Period Type. Reduce the Number of Periods, define more periods for the Period Type, or enter

another Period Type.

[APP–10228] This invoice has an effective payment.

[APP–10229] This invoice is selected for payment in a payment batch.

[APP–10230] This invoice is already cancelled.

[APP–10231] You may not cancel this prepayment. See the User’s Guide or on–line help.

[APP–10232] This invoice is matched to a Finally Closed PO.

[APP–10233] Approval failed.

[APP–10234] This invoice has posting holds.

[APP–10235] This period overlaps a previously defined period. Change the Start Date or the End

Date.

[APP–10236] &NUM_CANCELLED invoices cancelled &NUM_NOT_CANCELLED invoices not

cancelled

[APP–10237] The total of all scheduled payments must equal the invoice amount. Adjust the Gross

Amount for one or more scheduled payments.

[APP–10238] You have already confirmed all documents for the batch. You cannot restart the batch

or cancel the remainder once you confirm all documents.

[APP–10239] You cannot choose Confirm if the payment batch has no payment documents or if you

have not specified a Status to record for each of the documents in the batch.

[APP–10240] You cannot record a Printed or Set Up range after a Spoiled range. Re–enter the

range.

[APP–10241] The First Discount Date must fall on or before the Second Discount Date. Re–enter.

[APP–10242] The Second Discount Date must fall on or before the Third Discount Date. Re–enter.

[APP–10243] The First Discount Amount must be greater than or equal to the Second Discount

Amount. Re–enter.

[APP–10244] The Second Discount Amount must be greater than or equal to the Third Discount

Amount. Re–enter.

[APP–10245] You cannot split a scheduled payment if the sum of the existing scheduled payments

is greater than or equal to the invoice amount. Reduce the gross amount for one or more scheduled

payments and choose Split.

[APP–10246] The scheduled payment you selected for full payment is on hold and therefore cannot

be paid. Remove the hold.

[APP–10247] You cannot delete a scheduled payment if it is paid or partially paid, or if the

scheduled payment is for a prepayment.

[APP–10248] Document numbers within this range have already been confirmed. Re–enter.

[APP–10249] You cannot restart the batch without entering a document number from which you

would like to restart. Continue?

[APP–10250] You can only apply a fully paid prepayment. Fully pay a prepayment from the Actions

window of the Invoices Workbench or the Payment Workbench.

[APP–10251] You can only apply a prepayment to an approved invoice. Submit Approval for this

invoice.

[APP–10252] You cannot Confirm a payment batch that does not have any payment documents.

[APP–10253] The payment batches you selected to perform actions on have already been cancelled.

You cannot perform actions for payments batches with a status of Cancelled.

[APP–10254] This update is not allowed for Oracle Projects expense reports.

[APP–10255] An invoice has been created for this expense report. You cannot update or delete an

expense report once an invoice has been created for the expense report.

[APP–10256] You cannot delete an expense report until you delete all expense items for the expense

report.

[APP–10257] This expense report already exists. Check your records for duplicates and re–enter this

expense report with a unique number if necessary.

[APP–10258] Enter a default GL Account for this employee.

[APP–10259] The total of the expense items must equal the expense report total. Adjust one or more

expense items or the expense report total.

[APP–10260] You cannot modify the Tax Name for an expense item with a type of Tax.

[APP–10261] You cannot Apply Advances for an expense report if there are no available

prepayments for the employee, or if the expense report total is negative.

[APP–10262] The low check number cannot be greater than the high check number. Re–enter.

[APP–10263] Enter a supplier number greater than &NUM.

[APP–10264] Enter an employee number greater than &NUM.

[APP–10265] Number Type cannot be Numeric because alphanumeric supplier numbers exist.

[APP–10266] You cannot change this period status.

[APP–10267] The number of periods entered is less than the number of periods for which an invoice

has already been created. Re–enter.

[APP–10268] This payment batch will be deleted. Continue?

[APP–10269] This purchase order line was cancelled at &CANCEL &UNIT.

[APP–10270] Encumbrance Accounting has been turned off.

[APP–10271] Insufficient Funds remain in your budget for this invoice or distribution. Payables

includes encumbered funds in its funds check.

[APP–10272] Payables was unable to perform funds check because this invoice or distribution has a

GL Account that does not exist.

[APP–10273] Payables was unable to perform funds check because this invoice or distribution has a

GL Account that is disabled.

[APP–10274] Payables was unable to perform funds check because this invoice or distribution has a

GL Account that does not allow detail posting or detail budget posting.

[APP–10275] Payables was unable to perform funds check because the calendar is incorrectly

defined. Correctly define the calendar used by this set of books in Oracle General Ledger.

[APP–10276] Payables was unable to perform funds check because it was unable to find a budget

for this GL Account in this period. Create a budget in Oracle General Ledger for this GL Account in

this period.

[APP–10277] This invoice or distribution failed funds check.

[APP–10278] This invoice or distribution passed funds check.

[APP–10279] Adjust the liability of this invoice?

[APP–10280] This invoice requires exchange rate information. Enter the exchange rate type, date,

and rate.

[APP–10281] The manual sequence type is prohibitted for this invoice.

[APP–10282] The recurring invoice template is expired. Enter a new template or change the

expiration date.

[APP–10283] The number you entered is greater than the number of periods remaining. Re–enter.

[APP–10284] Active date cannot be after the inactive date.

[APP–10285] When you define an amount due payment terms, the last terms line must be defined as

’0’ Amount Due.

[APP–10286] You cannot commit a payment term without entering scheduled payment lines for the

term.

[APP–10287] Period sequence numbers must be unique within a type and year. Enter a unique

value.

[APP–10288] Period name and year must be unique within a period type. Enter a unique value.

[APP–10289] The period sequence cannot exceed the number of periods allowed.

[APP–10290] The end date cannot be before the start date. Re–enter.

[APP–10291] You cannot maintain periods for which reports have already run.

[APP–10292] You cannot delete periods if there is a recurring invoice template that uses this Period

Type.

[APP–10293] You cannot delete periods if a Withholding Tax type tax name uses this Period Type.

[APP–10294] You cannot overlap an existing period within this period type.

[APP–10295] If you define a due Percent or a due Amount, you must enter either Days, Day of

Month and Months Ahead, or Fixed Date.

[APP–10296] If you enter due Day of Month or discount Day of Month, you must enter Months

Ahead.

[APP–10297] If you define a discount Percent, you must enter either discount Days or Day of

Month and Months Ahead.

[APP–10298] You cannot use percentage due amounts and specific due amounts in the same

payment terms line or payment terms.

[APP–10299] You must enter a Batch Name when the batch control option is on.

[APP–10300] Refresh Status 1

[APP–10301] No holds placed or released.

[APP–10302] Holds placed: &HOLDS Holds released: &RELEASES

[APP–10303] No invoices found for approval. Check parameters.

[APP–10304] Due to unposted distrbutions or payments, the period cannot be closed. Submit the

Preliminary Invoice Sweep report.

[APP–10305] The total Percent for all payment terms lines must equal 100.

[APP–10306] You can only enter overlapping effective date ranges if you enter unique contiguous

amount ranges for the same effective date range. Re–enter.

[APP–10307] You must enter both Amount Basis and Period Basis, or neither.

[APP–10308] If period basis is Period, Period Type must be entered.

[APP–10309] If you are creating withholding tax invoices, you must enter Tax Authority Supplier

for Withholding Tax type tax names.

[APP–10310] A Tax Group with this name already exists. Re–enter.

[APP–10311] The To amount must be greater than the From amount. Re–enter.

[APP–10312] This tax name is inactive. Re–enter.

[APP–10313] Duplicate Record is only available for new records.

[APP–10315] This option is invalid for this record.

[APP–10316] Pay &NUM_OF_RECS scheduled payment(s)?

[APP–10317] Pay &NUM_OF_RECS invoice(s) in full?

[APP–10318] Approve &NUM_OF_RECS invoice(s)?

[APP–10319] Approve related invoices for &NUM_OF_RECS memo(s)? Note: This action only

applies to debit and credit memos. All other invoice types will be ignored by this action.

[APP–10320] Cancel &NUM_OF_RECS invoice(s)?

[APP–10321] Release holds on &NUM_OF_RECS invoice(s)?

[APP–10322] Print &NUM_OF_RECS invoice(s)?

[APP–10323] Prorate &NUM_OF_RECS distribution(s)?

[APP–10324] Reverse &NUM_OF_RECS distribution(s)?

[APP–10325] Select invoices for &NUM_OF_RECS payment batch(es)?

[APP–10326] Build payments for &NUM_OF_RECS payment batch(es)?

[APP–10327] Modify &NUM_OF_RECS payment batch(es)?

[APP–10328] Print Preliminary Register for &NUM_OF_RECS payment batch(es)?

[APP–10329] Format payments for &NUM_OF_RECS payment batch(es)?

[APP–10330] Confirm &NUM_OF_RECS payment batch(es)?

[APP–10331] Print Final Register for &NUM_OF_RECS payment batch(es)?

[APP–10332] Print Separate Remittance Advice for &NUM_OF_RECS payment batch(es)?

[APP–10333] Cancel &NUM_OF_RECS payment batch(es)?

[APP–10334] Copy &NUM_OF_RECS payment batch(es)?

[APP–10335] Refresh Status for &NUM_OF_RECS payment batch(es)?

[APP–10336] Reissue &NUM_OF_RECS payment(s)?

[APP–10337] Format &NUM_OF_RECS payment(s)?

[APP–10338] Print Separate Remittance Advice for &NUM_OF_RECS payment(s)?

[APP–10339] Stop &NUM_OF_RECS payment(s)?

[APP–10340] Release Stop for &NUM_OF_RECS payment(s)?

[APP–10341] Void &NUM_OF_RECS payment(s)?

[APP–10342] Payment Terms are inactive. Re–enter or activate in ”Payment Terms.”

[APP–10343] Distribution Set is inactive. Re–enter or activate in ”Distribution Sets.”

[APP–10344] Ship to Location is inactive. Re–enter or activate.

[APP–10345] Bill to Location is inactive. Re–enter or activate.

[APP–10346] Pay Group is inactive. Re–enter or activate in ”QuickCodes.”

[APP–10347] FOB is inactive. Re–enter or activate in ”QuickCodes.”

[APP–10348] Freight Terms are inactive. Re–enter or activate in ”QuickCodes.”

[APP–10349] Supplier Type is inactive. Re–enter or activate in ”QuickCodes.”

[APP–10350] Minority Group is inactive. Re–enter or activate in ”QuickCodes.”

[APP–10351] The Qty Received Exception you entered is inactive. Re–enter.

[APP–10352] Supplier name already exists. Re–enter.

[APP–10353] There are invoices selected to pay for this supplier.

[APP–10354] This Supplier Number already exists. Re–enter.

[APP–10355] This Employee Name is already assigned to another supplier. Re–enter.

[APP–10356] You cannot assign an Offset Tax Name to a supplier type of Employee. Clear the

Offset Tax Name in the Tax region for this supplier.

[APP–10357] This Site name already exists for this supplier. Re–enter.

[APP–10358] You have more than one Tax Reporting Site for this federally reportable supplier.

[APP–10359] Invalid state abbreviations exist for this federally reportable supplier. Verify the

correct state abbreviation in ”Income Tax Regions.”

[APP–10360] No expired values found.

[APP–10361] The invoice currency for a Tax Authority type supplier and its sites must be the

functional currency. Re–enter.

[APP–10362] You cannot close the period because there are unconfirmed payment batches with

payment dates in this period. Confirm all payment batches or cancel them in the Payment

Workbench.

[APP–10363] You cannot re–open this period because this period may be Closed or Permanently

Closed in Oracle General Ledger.

[APP–10364] You have reached the maximum number of future periods allowed.

[APP–10365] You cannot change this period status to Future because you have reached the

maximum number of Future periods allowed as specified in ”Financials Option.” Contact your

system administrator.

[APP–10366] You cannot set the Allow Multiple Currencies option to No because you currently

have one or more multi–currency bank accounts.

[APP–10367] You cannot set up your Payables options without first setting up your Financials

options. Set up your Financials options in ”Financials Options.”

[APP–10368] You cannot allow the Future Dated payment method if you are using the Cash Basis

accounting method for your set of books.

[APP–10369] Approve &NUM_OF_RECS batch(es)?

[APP–10370] This Invoice was entered for a different site. Invoice Site: &INV_SITE Payment Site:

&PAY_SITE

[APP–10371] You do not have a tax reporting site for this federally reportable supplier. Define a Tax

Reporting Site in the Tax region for a supplier site.

[APP–10372] The payment document is locked by another user. Please select another payment

document.

[APP–10373] To Document Number accounts for more payment documents than those which are in

the payment batch. Please re–enter a lower To Document Number.

[APP–10374] You chose to initiate a supplier merge. This action is irreversible. Continue?

[APP–10375] Cannot enter the same invoice multiple times. Deselect invoice or choose another

[APP–10376] Single row representation for this Summary Form is not available.

[APP–10377] There is an error in the date range entered. Re–enter.

[APP–10378] You cannot navigate to the detail block without entering data in the master block.

[APP–10379] You cannot apply a prepayment for more than the amount remaining that is not on

hold. Reduce the amount to apply or remove one or more scheduled payment holds for

&invoice_num.

[APP–10380] This payment document is an invalid selection because it is in use by another payment

batch. Please select another payment document.

[APP–10381] WARNING: Supplier Site Address may be incomplete

[APP–10382] You cannot delete an invoice which is an automatically created Withholding Tax

Invoice. Cancel the invoice.

[APP–10383] You cannot delete an invoice which has automatically created withholding tax

distributions. Cancel the invoice.

[APP–10384] This invoice is subject to withholding tax.

[APP–10385] Withholding will be applied upon commit. Continue?

[APP–10386] View Projected Withholding

[APP–10387] Invoice: &Invoice, failed because: &Problem

[APP–10388] You can not delete records here. Make the Income Tax region inactive.

[APP–10389] OK

[APP–10390] This invoice has a Distribution Set. Choose OK to create distributions from the

Distribution Set and to proceed with matching. Choose Match Only to disregard the Distribution

Set and to proceed with matching. Choose Cancel if you do not want to match.

[APP–10391] Match Only

[APP–10392] Please choose at least one payment you want to reverse by checking the left hand side

checkbox.

[APP–10393] Enter a value less than zero.

[APP–10393] You cannot reconcile this payment with charges, errors or exchange rate information

unless the Oracle Payables System Option ’Allow Reconciliation Accounting’ is enabled.

[APP–10394] This recurring invoice number already exists. Re–enter.

[APP–10395] Enter a number less than or equal to &NUM.

[APP–10396] Control invoice total is not equal to actual invoice total.

[APP–10397] Control invoice count is not equal to actual invoice count.

[APP–10398] You are already at the first receipt.

[APP–10399] The calculated amount is &CALCAMOUNT &CURRENCY. This amount will be

copied into the ”&TARGETFIELD” field. The ”&DAILYAMOUNT” field will be cleared.

[APP–10400] Please wait until the Calculate Amount process completes before performing any

actions.

[APP–10401] Are you sure you want to cancel this expense report?

[APP–10402] Are you sure you want to continue?

[APP–10403] Are you sure you want to delete this receipt?

[APP–10404] Are you sure you want to save this expense report and modify it at a later time?

[APP–10405] Are you sure you want to submit this expense report?

[APP–10406] Continue editing this report

[APP–10407] This Cost Center is not valid. Please enter a valid Cost Center.

[APP–10408] Cost Center is missing. Please enter a Cost Center.

[APP–10409] Please enter all alphabetic characters in the &CUSTFIELD field as upper case.

[APP–10410] The &CUSTFIELD field should contain numbers and +, –, ., and , characters only.

[APP–10411] ...

[APP–10412] &CUSTFIELD is missing. Please enter a value for &CUSTFIELD.

[APP–10413] The Ending Date must be on or after Starting Date. Please re–enter the Ending Date.

[APP–10414] The value you entered ’&DAILY_AMOUNT’ is not allowed. Please enter a valid

number for Daily Rate.

[APP–10415] The value you entered ’&DAYS’ is not valid. Please enter a valid number for Days.

[APP–10416] Are you sure you want to delete this expense report?

[APP–10417] Yes

[APP–10418] Different Single Currency is required

[APP–10419] The Receipt Amount column is missing from your spreadsheet. Please contact your

system administrator.

[APP–10420] The expense spreadsheet you pasted cannot be read. Please re–paste your expense

spreadsheet.

[APP–10421] Duplicate values for &Field_name have been found. Please contact your system

administrator.

[APP–10422] This is not a valid action. You have not pasted your expense spreadsheet.

[APP–10423] Upload Expense Spreadsheet –– Spreadsheet Format Error. Contact your system

administrator.

[APP–10424] The header section of your expense spreadsheet contains an error(s). Press the

Continue button to review and correct any errors.<BR> <BR>

[APP–10425] The Currency Code &curr is not valid. Please enter a valid Currency Code.

[APP–10426] The Expense Type &exptype is not valid. Please enter a valid Expense Type.

[APP–10427] Multiple expense types (&exptype) are not allowed for one receipt.

[APP–10428] &RecCount receipt(s) uploaded. No errors found. Submit your expense report, or

press the Review button to review your expense report before submitting it.

[APP–10429] The Cost Center you entered is different than your default Cost Center. You must

enter an Overriding Approver.

[APP–10430] Expense Template is not valid. Please enter a valid Expense Template.

[APP–10431] Upload Expense Spreadsheet

[APP–10432] Upload Expense Spreadsheet

[APP–10433] <b>Instructions</b><br> <ul> <li>Download the

expense report spreadsheet. Save a copy to serve as a template for expense reports that you will

submit. <li>Open the expense report spreadsheet and track receipt information in the

spreadsheet. <li>Do not enter text in the colored or shaded areas of the spreadsheet.

<li>Save the expense report spreadsheet. <li>Highlight the entire report (Ctrl–A).

<li>Copy the report (Ctrl–C or Edit–Copy from the spreadsheet menu). <li>Click on the

Spreadsheet Upload Area and paste your report into this area (Ctrl–V or Edit–Paste from the

spreadsheet menu). <li>Press the Validate Receipts button. </ul>

[APP–10434] &RecCount receipt(s) uploaded, &ErrRecCount receipt(s) requires additional

information. Press the Continue button to review and enter the additional information that is

required.

[APP–10435] &RecCount receipt(s) processed, &ErrRecCount receipt(s) either contains errors or

requires additional information. Press the Continue button to review and correct any errors, and to

review and enter any additional information that is required.

[APP–10436] &RecCount receipt(s) processed, &ErrRecCount receipt(s) with errors. Press the

Continue button to review and correct any errors.

[APP–10437] Expense Type is missing. Please enter a valid Expense Type.

[APP–10438] Go to the Enter Receipts page and display receipt &RECEIPTNUM.

[APP–10439] An employee matching the search criteria you provided could not be found. Contact

your system administrator.

[APP–10440] The date you entered ’&END_DATE’ is not allowed. Please enter the Ending Date in

the format ’&PROPER_FORMAT.’

[APP–10441] You have the following errors:

[APP–10442] Expense Type is missing. Please enter an Expense Type.

[APP–10443] *Note: The original receipt is missing for this expense. Approving this expense

report indicates that you approve this expense item without an original receipt.

[APP–10444] The Cost Center you entered is different from the default Cost Center, but you did not

provide an Overriding Approver. Please enter an Overriding Approver.

[APP–10445] Invalid Find Approver method

[APP–10446] The default employee code combination id is NULL for the employee that submitted

this expense report.

[APP–10447] Expense report number &INVOICENUM for &REPORTTOTAL has been

saved.<BR> <BR> <font COLOR=#FF0000 +2> Saved expense reports are NOT

submitted for approval. To submit your expense report for approval, choose Modify Expense

Reports from the main menu to open your saved expense report. Once you open your saved expense

report, you can review, edit, and either resave, submit or cancel your expense report. </font>

[APP–10448] Expense report number &INVOICENUM for &REPORTTOTAL has been submitted.

[APP–10449] <li>Print this page from your browser, write your employee number on this

page, and attach all receipts. </li><br> <li>Place your receipts in an interoffice

envelope and send them to Accounts Payable. </li> <br><br> Your manager will

be notified requesting approval for this expense report. After your manager approves this expense

report, you will be notified. This expense report will be paid once your manager approves, and

Accounts Payable verifies receipts. <br><br>

[APP–10450] Expense Types (click to select)

[APP–10451] Starting Expense Date is missing. Please enter a Starting Expense Date.

[APP–10452] This field is required.

[APP–10453] There are no employees matching the search criteria you provided for Overriding

Approver. The search is based on the following format: Last Name, (Title) First Name. Use the

Wizard if you need assistance.

[APP–10454] Return to Previous Page

[APP–10455] Your expense report contains the following errors: <BR>

[APP–10456] Complete this receipt before performing this action.

[APP–10457] Justification is missing. Justification is required for this expense type.

[APP–10458] Last Expense Receipt Date is not valid. Please enter a valid Last Expense Receipt

Date.

[APP–10459] Last Expense Receipt Date is missing. Please enter a date for Last Expense Receipt

Date.

[APP–10460] Display all receipts that make up this amount.

[APP–10461] Send questions or comments to

[APP–10462] The amount of text entered exceeds the maximum amount. Any text entered above

this limit will be truncated to &MAXLEN characters.

[APP–10463] is not a positive number. Please enter a postive number.

[APP–10464] Receipt Currency is missing. Please enter a value for Receipt Currency.

[APP–10465] Wizard not installed with this version. Choose ”Create New Expense Report” from

the Main Menu to install a version with the Wizard.

[APP–10466] You must enter a number.

[APP–10467] At least one entered receipt is required to perform this action.

[APP–10468] Overriding Approver is missing. Please enter an Overriding Approver.

[APP–10469] Overriding Approver is missing. Overriding Approver is required because you

entered a Cost Center other than your default Cost Center. Please enter an Overriding Approver.

[APP–10470] The confirmation process is in progress. Do not perform any actions until this process

completes.

[APP–10471] Purpose is missing. Please enter a Purpose.

[APP–10472] Exchange Rate is zero or less than zero. Please enter an Exchange Rate that is greater

than zero.

[APP–10473] The value entered for ’&RATE’ is not valid. Daily Rate must be a number.

[APP–10474] Exchange Rate is not a valid number. Please enter a valid number for Exchange Rate.

[APP–10475] The value entered for ’&RECEIPT_AMOUNT’ is not valid. Please enter a valid

number for Receipt Amount.

[APP–10476] The calculated amount of Daily Rate and Days does not equal the amount for

&Receipt_Amount. Please re–enter the receipt dates and the Daily Rate.

[APP–10477] There are missing values for this receipt. Please complete this receipt or clear it to

continue.

[APP–10478] Receipt 01 of 02

[APP–10479] Receipt currency is the same as the reimbursement currency. Please select

Reimbursement for the receipt currency instead of Other.

[APP–10480] The following receipt(s) contains errors:

[APP–10481] Includes Foreign Currency Receipt(s)

[APP–10482] Receipt Currency is the same as the Reimbursement Currency. Select Reimbursement

instead of Other for the Receipt Currency.

[APP–10483] &START_DATE to &END_DATE (&DAYS Days)

[APP–10484] This expense report has already been deleted by another user.

[APP–10485] This expense report is currently locked. Please try again later.

[APP–10486] There are no saved expense reports to modify.

[APP–10487] Your expense report cannot be opened or deleted due to the following error(s):

<BR>

[APP–10488] This expense report has been submitted or deleted by another user and cannot be

opened.

[APP–10489] Return to Main Menu

[APP–10490] Return to Modify Expense Reports

[APP–10491] If the Receipt Currency is the same as the Reimbursement Currency, the Exchange

Rate you enter must be 1 or none.

[APP–10492] No

[APP–10493] You have selected a Receipt Currency that is the same as the Reimbursement

Currency. \nThe Conversion Rate must be 1 or none.

[APP–10494] This expense report has been updated, submitted, or deleted by another user, and

cannot be saved or submitted.

[APP–10495] This expense report is currently locked. Press the Cancel Report button and return to

the Main Menu.

[APP–10496] Saved Expense Report Confirmation

[APP–10497] &FIELD_NAME is missing. Please enter a value for &FIELD_NAME.

[APP–10498] Single currency is required.

[APP–10499] The Ending Date is before the Starting Date. Please re–enter the Ending Date.

[APP–10500] The value for ’&START_DATE’ is not valid. Starting Date must be in format

’&PROPER_FORMAT.’

[APP–10501] Submitted Expense Report Confirmation

[APP–10502] Oracle Web Employees Expense Entry

[APP–10503] Too many employees match the the name you entered for Overriding Approver. Enter

search criteria that can uniquely identify an employee. Use the Wizard for assistance.

[APP–10504] The value for ’&TOTAL_AMOUNT’ is not valid. Please enter a valid number for

Total.

[APP–10505] Total Amount &Total_Amount does not match our calculation.

[APP–10506] Total is missing. Please enter an amount for Total.

[APP–10507] The following receipt(s) contains no errors:

[APP–10508] The Calculate Amount process is in progress. Do not perform any actions until this

process completes.

[APP–10509] The confirmation process is in progress. Do not perform any other actions until this

process completes.

[APP–10510] Please wait until the application is fully loaded before performing any actions.

[APP–10511] The total amount you entered for this receipt (in the receipt currency) is:

[APP–10512] Are you entering the receipt amount as a daily rate that should be multiplied by the

number of days for the receipt, or are you entering the receipt amount as the total amount?

[APP–10513] Would you like to designate an Overriding Approver for your expense report, or use

the default approver? The default approver is your direct manager.

[APP–10514] To Calculate All, you must enter the Expense Date(s), and either Daily Amount or

Receipt Amount.

[APP–10515] For custom message

[APP–10516] Here is a summary of the amounts you entered for this receipt. Press the Next button

if these amounts are correct, or press the Back button to make corrections.

[APP–10517] Message not used.

[APP–10518] Select the Currency for this receipt. If you also enter the Conversion Rate, the total

amount in the Reimbursement Currency is automatically calculated. Otherwise, you must enter the

total amount in the Reimbursement Currency in the next Wizard window.

[APP–10519] If your receipts are all in the same currency, select the currency in which all of your

receipts are denominated. Select OTHER if the desired currency does not appear in this list.

Optionally enter a Conversion Rate for all receipts you enter.

[APP–10520] For custom message

[APP–10521] Enter the Cost Center that should receive the charge for this expense report. The

default Cost Center is the one associated with your employee information. You can enter another

Cost Center if the default is not the Cost Center that should receive the charge for this expense

report.

[APP–10522] For custom message

[APP–10523] Enter the expense date of the receipt. If this is a receipt for a range of days, the date

entered here will be used as the starting date. Click on the calendar date to enter the expense date,

or type the date in the Starting Date field if it is not displayed in the calendar.

[APP–10524] Enter the Ending Date of the receipt. Click on the calendar date to enter the date, or

type the date in the Ending Date field if it is not displayed in the calendar.

[APP–10525] Enter the Daily Rate for the receipt.

[APP–10526] Your default Cost Center is &costctr.

[APP–10527] Default approver

[APP–10528] Are all of your receipts in a single currency or in multiple currencies?

[APP–10529] For custom message

[APP–10530] Here is a summary of the currency information you entered for this receipt. Press the

Next button if this information is correct, or press the Back button to make corrections.

[APP–10531] Enter another receipt using Wizard

[APP–10532] Enter another receipt without using Wizard

[APP–10533] Return to Enter Receipts page for current receipt

[APP–10534] You have completed the Enter Receipts page. You now have three options: you can

enter another receipt using the Wizard, you can enter another receipt without using the Wizard, or

you can close the Wizard and return to the Enter Receipts page for the current receipt.

[APP–10535] Enter Receipts Wizard

[APP–10536] Select the Expense Type for this receipt.

[APP–10537] Optionally enter an Expense Group for this receipt. If you have a receipt with

multiple expense types, such as a hotel bill, you can enter each expense type individually and assign

an Expense Group to each individually entered type to easily reconcile the total amount of all the

expense types to the total receipt amount.

[APP–10538] Welcome to the Expense Report Wizard! The Expense Report Wizard assists you as

you enter your expense report by providing an explanation of what you need to enter for each field

as you enter it. Use the Wizard from start to finish to enter your expense report, or just to get started

– you can cancel the Wizard at any time. If you need help for any single field, just click on the field

label. Click on Next to proceed with the Wizard!

[APP–10539] Please enter an Overriding Approver from the following list of employees:

[APP–10540] Enter the first few letters of the Overriding Approver’s last name.

[APP–10541] You have selected the following employee as the Overrding Approver for this expense

report:

[APP–10542] Close Wizard and proceed

[APP–10543] Close Wizard

[APP–10544] You have completed the Start Report page. You now have two options: you can close

the Start Report Wizard and automatically proceed to the Enter Receipts page, or you can close the

Start Report Wizard without proceeding to the Enter Receipts page. If you choose the second

option, press the Enter Receipts button to proceed to the Enter Receipts page. Press the Wizard icon

on the toolbar of the Enter Receipts page to start the the Enter Receipts Wizard.

[APP–10545] For custom message

[APP–10546] Overriding Approver

[APP–10547] Briefly describe the Purpose of your expense(s).

[APP–10548] For custom message

[APP–10549] Enter the total amount of the receipt.

[APP–10550] Select the currency in which your expense report will be reimbursed. The payment

for your expense report will be in this currency.

[APP–10551] For custom message

[APP–10552] Enter the date of your most recent expense for this expense report. The default is

today’s date.

[APP–10553] For custom message

[APP–10554] Indicate if the original receipt for this expense is missing or available. If the original

receipt is missing, be certain to include a justification (previous Wizard window) for the expense.

[APP–10555] Enter a brief Justification for the expenses incurred for this receipt. Justification is

required for certain expense types.

[APP–10556] Enter the Conversion Rate from the Receipt Currency to the Reimbursement

Currency.

[APP–10557] Range of days

[APP–10558] Single day

[APP–10559] Is this receipt for a single day or for a range of days?

[APP–10560] Do you have any receipts in a currency other than your Reimbursement Currency?

Your Reimbursement Currency is:

[APP–10561] For custom message

[APP–10562] New Expense Report Wizard

[APP–10563] More than &maxrecord employees matched your query. Enter additional search

criteria to narrow the search for an employee for Overriding Approver.

[APP–10564] Select an Expense Template for your expense report. The template you select

determines what type of expenses you can enter for your expense report.

[APP–10565] For custom message

[APP–10566] Enter the total receipt amount in the reimbursement currency.

[APP–10567] There are no employees whose last name starts with the letters you entered as search

criteria. Re–enter your search criteria.

[APP–10568] Days is not valid. Please enter a valid number for Days.

[APP–10569] This transaction has been updated by another user. To review the change, press the

Cancel button to go back to the Open Credit Card Transactions page.

[APP–10570] The update process is in progress. Do not perform any actions until this process

completes.

[APP–10571] You entered a Tax–type line without entering a Tax Name. Enter a Tax Name.

[APP–10572] An Invoice that you selected can not be paid in full because it has already been

selected for payment by a Payment Batch.

[APP–10763] The Apply, Create Withholding combination specified is invalid.

[APP–10764] Discount Amount cannot be ’No’ if Apply Withholding is ’Approval’.

[APP–10765] You have not yet chosen a set of books. Please use the Choose Set of Books form to

do this first.

[APP–10766] There are overlaps in the amount ranges.

[APP–10767] There are gaps in the Amount Ranges. Modify the Amount Range value or Add in one

new record.

[APP–10768] The last Start Amount should be equal to the maximum End Amount in the Amount

Range. Modify the last Start Amount.

[APP–10769] The last End Amount should always be NULL. Modify the last End Amount.

[APP–10770] Only one End Amount with same Rate Type and Period should be NULL.

[APP–10771] Could not reserve record.

[APP–10772] Check Expired Values

[APP–10773] Create Positive Pay file(s) for &NUM_OF_RECS payment batch(es)?

[APP–10774] Incomplete bank information exists for this bank account. Enter the Branch Number

and Account Number for this bank account in ”Banks”.

[APP–10775] Tax Calculation Level

[APP–10776] Only Payment Batches with status Unstarted or New are allowed to be deleted.

[APP–10777] Please enter bank account name, bank account number, and bank branch if payment

method for the supplier or supplier site is Electronic Payments.

[APP–10778] The Control Total cannot be less than Released Total.

[APP–10779] Payment Batch total is over maximum outlay.

[APP–10780] Automatic Payment Programs

[APP–10781] Automatic Receipt Programs

[APP–10782] No conversion rate was found for this currency, type, and date.

[APP–10783] This check was already reconciled.

[APP–10784] You are trying to clear a check that was already cleared.

[APP–10785] The Cash Account for the check you are trying to clear has an invalid code

combination id. Please go into the Update Payment Distributions Form and fix the Cash code

combination id for the check you are clearing.

[APP–10786] No checks were found to reconcile.

[APP–10787] &PROCEDURE procedure raised unhandled exception &EVENT

[APP–10788] One of the ranges has to start from 0.

[APP–10789] The last Transaction_Amount(to) should always be NULL. Modify the last

Transaction_Amount(to).

[APP–10790] The last range must be open–ended and the others must not.

[APP–10791] This bank charge already exists.

[APP–10792] No bank charges/tolerance limit found.

[APP–10793] You cannot choose Other Banks/Branches in Receiving side while you choose All

Banks/Branches in Transferring side.

[APP–10794] &TOTAL advances exist for this employee. &AVAILABLE are available. To apply

or unapply advances, check the Apply Advances box before importing.

[APP–10795] Only one Primary Bank Account per currency is permitted.

[APP–10796] Bank Account Name already exists.

[APP–10797] This purchase order has been closed.

[APP–10798] VAT Registration Number is not unique.

[APP–10799] VAT Registration Number is invalid.

[APP–10800] Fiscal Code entered is not unique.

[APP–10801] Fiscal Code is not valid.

[APP–10802] You cannot reconcile this payment with charges, errors or exchange rate information

unless the Oracle Payables Option ”Allow Reconciliation Accounting” is enabled.

[APP–10803] Duplicate Bank Account assigned to Supplier.

[APP–10804] Duplicate Bank Account assigned to Supplier Site. It may be caused by the default

Bank Account from the Supplier level.

[APP–10805] You must define one Primary Bank Account for each currency. Vendor Name =

&VENDOR_NAME, Currency Code = &CURRENCY_CODE.

[APP–10806] You must define one Primary Bank Account for each currency for this site. Vendor

Site Id = &VENDOR_SITE_ID , Currency Code = &CURRENCY_CODE.

[APP–10807] Since you have chosen to use bank charges, the Transfer Priority field is required.

[APP–10808] WARNING: Bank Number must be entered

[APP–10809] WARNING: Bank Account Number is invalid.

[APP–10810] WARNING: Check Digit is invalid.

[APP–10811] WARNING: Check digit must be entered

[APP–10812] This EDI ID Number already exists.

[APP–10813] You cannot post to this account.

[APP–10814] The To Date cannot be less than the From Date. Re–enter.

[APP–10815] This invoice or distribution passed funds check with advisory warnings.

[APP–10816] You cannot delete or update Period Type while dependent Period Information exists.

[APP–10817] Invalid combination of Period, Year

[APP–10818] Invalid combination of End Date, Start Date

[APP–10819] Are you sure you want to create a 100% discount?

[APP–10820] Bank charge bearer must be entered.

[APP–10821] Parent Value is not allowed for this segment

[APP–10822] Account must be of type Liability

[APP–10823] WARNING: Bank Number is invalid

[APP–10824] WARNING: Bank Branch Number is invalid

[APP–10825] The hierarchy number you selected is a duplicate of another defaulting source. Please,

re–enter.

[APP–10826] The Payment Batch has been modified. Use the Done Button to submit the Payment

Batch Program.

[APP–10827] Please enter supplier site name.

[APP–10828] Not applied, cannot build invoice dist liability account

[APP–10829] Date:

[APP–10830] Description

[APP–10831] Page:

[APP–10832] Accounted Credit

[APP–10833] Accounted Debit

[APP–10834] Accounting Flex

[APP–10835] ACCOUNTS PAYABLE JOURNAL ENTRY AUDIT REPORT

[APP–10836] Bank Acccount :

[APP–10837] Code

[APP–10838] |––––––––––––––––Invoice––––––––––––––––––|

|––––––––––––––––––––Distribution––––––––––––––––––| Exception

[APP–10839] Supplier Name Invoice Number Currency Amount Num Amount Description GL

Date Code

[APP–10840] |––––––––––––––––Payment––––––––––––––––––| |––––––––––––––––Invoice

Payment–––––––––––––––| Exception

[APP–10841] Supplier Name Document Number Currency Amount Num Invoice Number

Amount GL Date Code

[APP–10842] Supplier Name Document Number Currency Amount Line Type GL Date

Exception Code

[APP–10843] Currency :

[APP–10844] DISABLED The Accounting Flexfield specified in this Distribution Line has been

disabled

[APP–10845] PERIOD This Distribution Line is in a General Ledger period which is not open or

future

[APP–10846] RATE This Distribution Line is in Foreign Currency and has no Exchange Rate

information

[APP–10847] Document Num

[APP–10848] Entered Credit

[APP–10849] Entered Debit

[APP–10850] Exception

[APP–10851] ACCOUNTS PAYABLE JOURNAL ENTRY EXCEPTION REPORT

[APP–10852] GL Date

[APP–10853] Grand Total :

[APP–10854] INACTIVE The Accounting Flexfield specified in this Distribution Line is not active

[APP–10855] INVALID This Distribution Line contains an invalid Accounting Flexfield

[APP–10856] Supplier Name Invoice Num GL Date Accounting Flex Entered Debit Entered

Credit Accounted Debit Accounted Credit

[APP–10857] Invoice Distributions with Exceptions

[APP–10858] Invoice Num

[APP–10859] Invoice Payments with Exceptions

[APP–10860] TRANSFER TO GENERAL LEDGER : POSTED INVOICES

[APP–10861] Total for

[APP–10862] Meaning

[APP–10863] These Items will not be transferred to the Oracle General ledger

[APP–10864] Payment Document :

[APP–10865] Supplier Name Document Num Pay Date Accounting Flex Entered Debit Entered

Credit Accounted Debit Accounted Credit

[APP–10866] PERIOD This Payment is in a General Ledger period which is not open or future

[APP–10867] RATE This Payment is in Foreign Currency and has no Exchange Rate information

[APP–10868] TRANSFER TO GENERAL LEDGER : POSTED PAYMENTS

[APP–10869] Sub Total :

[APP–10870] UNDIST Distribution on this Payment was not properly Flexbuilt

[APP–10871] Posting is not permitted to the Accounting Flexfield specified in this Distribution Line

[APP–10872] Reconciliation Payment Distributions with Exceptions

[APP–10873] TRANSFER TO GENERAL LEDGER : POSTED RECONCILIATION

DISTRIBUTIONS

[APP–10874] Total Number of Distribution Lines Containing Exceptions

[APP–10875] Total Number of Payments Containing Exceptions

[APP–10876] Supplier Name

[APP–10877] Amount

[APP–10878] Date

[APP–10879] Invoice

[APP–10880] Invoice Number

[APP–10881] No data exists for this report

[APP–10882] Document Line

[APP–10883] Number Vendor Name Invoice Num Type Amount Problem Ac counting Flex

Reason

[APP–10884] &COMPANY Final Payment Register Date: &CURDATE

[APP–10885] Undistributed Payments Report

[APP–10886] Currency

[APP–10887] As of

[APP–10888] For more information refer to Navigate Setup System Options

[APP–10889] An accrual set of books does not exist for this report

[APP–10890] Remaining

[APP–10891] Total rounding adjustments for report:

[APP–10892] TRIAL BALANCE

[APP–10893] Total for currency:

[APP–10894] Total for liability account:

[APP–10895] Total for report:

[APP–10896] Total for vendor:

[APP–10897] Invoice Import Exceptions Report &curdate Page:

[APP–10898] Employee Vendor Vendor Period Invoice

[APP–10899] Name Number Name Number Total End Date Number Exception Reason

[APP–10900] –––––––––––––––––––– ––––––––– –––––––––––––––––––– ––––––––––

––––––––––––––––– ––––––––– –––––––––––––– –––––––––––––––––––––––––

[APP–10901] Invoice Import Report &curdate Page:

[APP–10902] Source: &source

[APP–10903] Batch: &batch

[APP–10904] Employee Vendor Period Invoice Apply

[APP–10905] Name Number Number Total Description End Date Number Hold Advance

[APP–10906] –––––––––––––––––––– ––––––––– –––––––––––– –––––––––––––––––

–––––––––––––––––– –––––––– ––––––––– –––––––––––––– –––––––––– –––––––

[APP–10907] Total Invoices Created: &count

[APP–10908] Total Functional Currency Invoice Amount:&amount

[APP–10909] Invoice Import Prepayments Applied &curdate Page:

[APP–10910] Invoice Prepayment

[APP–10911] Invoice Prepayment Currency Amount Amount Amount

[APP–10912] Vendor Name Vendor Number Number Number Code Applied Remaining

Unapplied

[APP–10913] –––––––––––––––––––– –––––––––––––– –––––––––––––– ––––––––––––––

–––––––– ––––– ––––––––– –––––––––––––– ––––––––––––––

[APP–10914] &COMPANY Invoice Import Prepayment Date: &CURDATE Application

[APP–10915] Bank Account Name:

[APP–10916] &SOURCE:&error

[APP–10917] Error occurred while processing flexfield in &MODE mode

[APP–10918] This batch name already exists. Please use another

[APP–10919] Journal Import Funds Check Preprocessor failed

[APP–10920] No invoices exist to be imported

[APP–10921] Payment Batch program has completed

[APP–10922] This payment batch has an invalid status

[APP–10923] Payment Batch Name:

[APP–10924] /Payment Date:

[APP–10925] Payment Document Name:

[APP–10926] Error occurred while connecting to database and fetching arguments

[APP–10927] Unable to locate Purchasing system options

[APP–10928] Unable to locate Purchasing system options

[APP–10929] Error occurred while committing work after creating journal entries

[APP–10930] Unable to allocate sufficient memory using sfmmll

[APP–10931] Error occurred while selecting lines to be posted

[APP–10932] Error occurred while initializing posting status flags

[APP–10933] Error occurred while trying to insert future payment credit lines

[APP–10934] Error occurred while trying to insert future payment debit lines

[APP–10935] Wrong number of arguments received

[APP–10936] Unable to locate information for set of books id #

[APP–10937] Unable to locate information for set of books named %s

[APP–10938] Payables is missing from list of journal entry sources

[APP–10939] Payments is missing from list of journal entry categories

[APP–10940] Purchase Invoices is missing from list of journal entry categories

[APP–10941] Accounting method is not specified in Payables system options

[APP–10942] Secondary set of books is not specified in Payables system options

[APP–10943] Error occurred while determining a period’s default effective date

[APP–10944] Error occurred while fetching journal entry sources and categories

[APP–10945] Unable to determine output file name

[APP–10946] Error occurred while fetching Purchasing system options

[APP–10947] Error occurred while fetching set of books information

[APP–10948] Error occurred while fetching Payables system options

[APP–10949] A select statement necessary to determine undistributed payments failed.

[APP–10950] Error occurred while preparing Distributions for posting (Case I)

[APP–10951] Error occurred while preparing Distributions for posting (Case II)

[APP–10952] Error occurred while preparing Distributions for posting (Case III)

[APP–10953] End of Report

[APP–10954] No payment batch exists with this name

[APP–10955] Tax name is missing. Please enter a tax name.

[APP–10956] Please review the following new procurement card transactions you have incurred:

[APP–10957] Please review the following held procument card transactions you have incurred:

[APP–10958] Please review the following rejected procurement card transactions you have incurred:

[APP–10959] Accounts Payable Liability Accounting Flexfield:

[APP–10960] Line

[APP–10961] Error occurred while committing work after selecting rows to post

[APP–10962] Another tax is recommended based on tax defaulting rules. Do you wish to override

tax?

[APP–10963] Account is not valid. Please enter a valid Account.

[APP–10964] The sum of the distributions does not equal the transaction amount. You may not save

the changes unless the sum of the distributions is equal to the transaction amount.

[APP–10965] Please indicate whether the receipt amount includes tax.

[APP–10966] Enter the name of the tax included in the receipt amount.

[APP–10967] &CUSTFIELD contains an invalid value. Please enter a valid value for

&CUSTFIELD.

[APP–10968] This EDI Location value is already used in a bank record. Please re–enter.

[APP–10969] This EDI location value already exists for a supplier. Please re–enter.

[APP–10970] This payment schedule is for an electronic payment type but does not have a remit–to

bank account. If this is still the case when you come to build this payment the payment will be

placed on hold. It is advisable to populate the remit–to bank account now.

[APP–10971] The remit–to account for the selected invoice &INV_NUM is &INV_REMIT_TO.

This differs from the payment remit–to account, &PAY_REMIT_TO. Do you wish to proceed using

the Payments remit–to account?

[APP–10972] Invalid profile name &profile_name.

[APP–10973] Credit Card Transaction Verification

[APP–10974] Credit Card Transaction Verification

[APP–10975] This page cannot be generated at this time. Please try again later.

[APP–10976] The following error(s) was found:

[APP–10977] The following error occurred while updating the database:

[APP–10978] Back to Open Credit Card Transcations

[APP–10979] Negative amounts are not allowed. Please enter a positive number less than or equal

to the original transaction amount.

[APP–10980] Amount &amount is greater than the original amount &orig_amount. Reduce this

amount to be less than or equal to the orginal transaction amount.

[APP–10981] &amount is not a valid number. Please enter a valid positive number less than or

equal to the original transaction amount.

[APP–10982] The Total amount of all lines does not equal the original transaction amount. Correct

the amount so that the total amount of all lines equals the original amount of the transaction.

[APP–10983] This transaction cannot be found. Contact your system administrator.

[APP–10984] This record is being edited or updated by another user and is locked. Please try again

later.

[APP–10985] Database update failed due to error &error. Contact your system administrator.

[APP–10986] Additional values have been defaulted in the expense report you just uploaded.

[APP–10987] Instructions<br> <ul> <li>The first row in the table displays status

and accounting information for the transaction you selected. <li>Update this information as

necessary. <li>Optionally update the second row of the table to split the transaction between

two Statuses, Accounts, Cost Centers, Amounts, and/or Descriptions.<br> <br><font

color=#FF0000>Attention: The total Amount of both lines in this table must equal the original

amount of the transaction as displayed in the Amount field above the table.</font><br>

<br> <li>When you are finished verifying a transaction, press the Save and Return

button. <li>Press the Back button to return to Open Credit Card Transactions page without

saving your changes. </ul>

[APP–10988] Unable to retrieve printer information from the program definition. The profile value

for the printer will be used instead.

[APP–10989] To see your changes, press the Reload or Refresh button on your browser after the

Open Credit Card Transactions page displays.

[APP–10990] Status and Accounting Info

[APP–10991] For Split

[APP–10992] Records &FROM_ROW_TOKEN – &TO_ROW_TOKEN of

&TOTAL_ROW_TOKEN

[APP–10993] Account is missing. Please enter a value for Account.

[APP–10994] Please enter the complete address.

[APP–10995] Please enter Supplier name or Supplier Number

[APP–10996] Your user account has not been set up properly – Person not assigned to your user

name. Please notify your system administrator.

[APP–10997] Interest is due on this invoice. You should pay the invoice in a payment batch or with

a Quick Payment if you want interest to be calculated.

[APP–10998] You cannot perform this action because you may not have the Multiple Currencies

Payment flag set to ’No’ whilst having one or more payment documents whose format currency

differs from the account currency.

[APP–10999] You must enter a cash clearing account for documents with a Future Dated Payment

Format.

[APP–11000] Record must be entered or deleted first

[APP–11001] Invoices exist that belong to this batch, you cannot delete it.

[APP–11002] Invalid distribution. Total amount must equal receipt amount, and total percent must

be 100 %.

[APP–11003] From Postal Code (&FROM) must be before To Postal Code (&TO).

[APP–11004] Field must be entered

[APP–11005] Reversal GL date is before receipt or application GL date (&MIN_GLD)

[APP–11006] User not defined yet

[APP–11007] You must assign a document sequence for this document type when the profile option

’Sequential Numbering’ is set to ’Always Used’

[APP–11008] You cannot create new Invoicing Rules. You can have only 1 Invoicing Rule.

[APP–11009] Error in tokens passed by user exit (&LOC)

[APP–11010] Could not put value back to a field (&LOC)

[APP–11011] Customer Prospect Code must be either CUSTOMER or PROSPECT

[APP–11012] You may not have two records of the same type within a transmission format.

[APP–11013] Item not valid. Please re–enter.

[APP–11014] Rate Adjustment cannot be performed for the selected receipts a the receipts are not

of the same currency.

[APP–11015] You must have exactly 5 bucket lines for this aging bucket

[APP–11016] The Set Of Books used is different from the Receivables Set Of Books defined for this

Operating Unit. Either use the Receivables Set of Books or use a different Operating Unit.

[APP–11017] Recreation of Payment Schedules failed because the transaction has activity against it.

Please requery the transaction and try again. If the problem persists, please contact your System

Administrator.

[APP–11018] Days Past Due From must be less than or equal to Days Past Due To.

[APP–11024] &ROUTINE–&ERR_NUMBER &SQL_ERROR

[APP–11025] Duplicate telephone reference in table RA_CONTACT_PHONES_INTERFACE

[APP–11040] { &ERRLOCATION } &ERROR_MESSAGE &ERROR_CODE

[APP–11041] Your &FAILED process failed. Please submit &RESUBMIT.

[APP–11042] Your &FAILED process failed. Please submit &RESUBMIT, then &ALSO.

[APP–11043] Your &SUCCESSFUL was successful, but your &FAILED process failed. Please

resubmit &RESUBMIT.

[APP–11044] Your archive was successful, but your report failed. Please resubmit your Archive

Report, then Purge Only.

[APP–11045] Inserting into AR_ARCHIVE_PURGE_INTERIM

[APP–11046] No date retrieved. Exiting program.

[APP–11047] No period information available. Exiting program.

[APP–11048] Purging &TRANSACTIONS ID range: &IDLOW to &IDHIGH.

[APP–11049] Finished purging &TRANSACTIONS ID range: &IDLOW to &IDHIGH.

[APP–11050] Send

[APP–11051] Format

[APP–11053] Loaded &COUNT receipts into AR_PURGE_REC_AUX

[APP–11057] Request: &REQUESTID &STATUS

[APP–11063] Cannot get currency information

[APP–11064] Archive/Purge terminated. Archive tables are populated. Please save and then delete

the contents of AR_ARCHIVE_HEADER and AR_ARCHIVE_DETAIL, then resubmit

Archive/Purge.

[APP–11065] Loaded &COUNT transactions into AR_PURGE_TRX_AUX

[APP–11066] This function did not find all the required arguments.

[APP–11067] The postal code you have entered is invalid. Ensure that the postal codes are within

the range specified in the System Options form of Oracle Receivables.

[APP–11068] Territory Code: &TERRITORY is not defined. Ensure that every address has a

country code as defined in the form ”Define Territories”.

[APP–11069] You may not have more than five open accounting periods before a closed period.

[APP–11070] You must apply this receipt, &RECEIPT_NUMBER, to at least one invoice.

[APP–11071] You may not risk eliminate a receipt that is already risk eliminated or not remitted for

factoring.

[APP–11073] You may not undo risk eliminate on a receipt that has not been risk eliminated.

[APP–11074] Cannot update the receipt batch type. Clear the record and re–enter batch details.

[APP–11075] You can delete a batch only if the process status is Creation Started or Creation

Completed or PostBatch Waiting.

[APP–11077] You cannot create new records for a transaction with activity against it.

[APP–11078] You cannot insert new records after this transaction has been posted.

[APP–11079] There has been activity against this transaction. You cannot update it.

[APP–11080] This transaction has been posted. You can no longer update this field.

[APP–11081] This transaction has been printed. You can no longer update this field.

[APP–11083] Actions are not allowed. Profile option ’Allow actions in Enter Receipts form’ is

defined to ’No’.

[APP–11084] Cannot update chargeback associated with this receipt.

[APP–11086] This transaction type has an invalid creation sign.

[APP–11087] The application violates the creation sign constraint.

[APP–11088] This transaction type has an invalid creation sign.

[APP–11089] You cannot increase the balance of this transaction.

[APP–11090] The Natural Application Only field is empty for this transaction type.

[APP–11091] You cannot over apply this transaction.

[APP–11092] The Allow Overapplication field is empty for this transaction type.

[APP–11093] The Creation Sign for this transaction type is not set.

[APP–11094] Exchange rate of type &RATE_TYPE defaulted from profile option

&PROFILE_OPTION.

[APP–11095] Exchange rate defaulted from batch.

[APP–11098] Cannot assign bank account with the same name and overlapping date range.

[APP–11099] Address does not have a saved active Bill To business purpose. Bank Accounts,

Payment Methods and Credit Profiles can only be created for addresses with a saved Bill To

business Purpose.

[APP–11101] Address reference is already used by another customers address

[APP–11102] A primary bank account already exists for this currency and date range.

[APP–11103] Value &value is not defined for address component City.

[APP–11104] Error in submitting the concurrent request.

[APP–11109] Location already exists for this business purpose and customer.

[APP–11110] Warning: You have a duplicate contact name for this customer.

[APP–11111] Internal location is already assigned to another ship to address. Please choose a

different location.

[APP–11114] You cannot update the internal location of a ship to address when requisition lines

exist for the location.

[APP–11115] Invalid value &VALUE for parameter &PARAMETER. Please contact your System

Administrator

[APP–11119] Warning: Customer does not have a customer profile defined. Please define a

customer profile for this customer.

[APP–11120] Could not locate the site meaning.

[APP–11122] Procedure &PROCEDURE raised error : &ERROR_MSG. Please contact World

Wide Support.

[APP–11123] You can only assign one business purpose of each type to an address.

[APP–11124] You may only have one active Dunning business purpose for each customer.

[APP–11125] You may only have one active Legal business purpose for each customer.

[APP–11126] You may only have one active Statements business purpose for each customer.

[APP–11131] You cannot have more than one primary payment method for the same date range.

[APP–11132] Value &value is not defined for address component Postal Code.

[APP–11135] Cause : You have exceeded the maximum number of pending requests for the same

profile class. Action : Please wait for the pending requests to be processed.

[APP–11136] Value &value is not defined for address component Province.

[APP–11138] You are required to save changes before leaving the current record.

[APP–11141] Cannot merge same customers when the Delete After Merge option is set to ”Y”.

[APP–11142] A parameter to the form and the function exclusions are incompatible. Please contact

your System Administrator.

Cause: The initial region parameter has been excluded from your responsibility.

[APP–11143] Submitted request with ID: &reqid

[APP–11146] Value &value is not defined for address component State.

[APP–11147] Every From site does not have a corresponding To site.

[APP–11149] Error parsing Receivables Location Flexfield Structure. Please check the definition of

your Location Flexfield. The following structures are supported. STATE.COUNTY.CITY

STATE.CITY CITY PROVINCE PROVINCE.CITY COUNTRY. STATE

[APP–11150] The overall credit limit must be more than the order credit limit.

[APP–11151] The Dispute amount may not be less than the original amount due.

[APP–11158] The low Amount Past Due must be less than or equal to the high Amount Past Due.

[APP–11161] Days To must be more than Days From

[APP–11162] The low Correspondence Date must be less than or equal to the high Correspondence

Date.

[APP–11163] The low Credit Limit must be less than or equal to the high Credit Limit.

[APP–11165] The low Exceeded Credit must be less than or equal to the high Exceeded Credit.

[APP–11166] The low Follow–Up Action must be less than or equal to the high Follow–Up Action.

[APP–11167] The low Follow–Up Date must be less than the high Follow–Up Date.

[APP–11169] The low Customer Name must be less than or equal to the high Customer Name.

[APP–11170] The low Customer Number must be less than or equal to the high Customer Number.

[APP–11172] The low Amount Due Original must be less than or equal to the high Amount Due

Original.

[APP–11174] The low Remaining Amount must be less than or equal to the high Remaining

Amount.

[APP–11175] The low Remaining Percent must be less than or equal to the high Remaining Percent.

[APP–11176] The low Transactions Past Due must be less than or equal to the high Transactions

Past Due.

[APP–11177] Range for Remaining Amount OR Remaining Percent must be completed.

[APP–11178] Chargebacks are associated with this receipt. Reverse the chargebacks, before you

reverse the receipts.

[APP–11179] Deleting this receipt, &RECEIPT_NUMBER, will delete all invoices applied to this

receipt. Continue ?

[APP–11181] You may not delete a record referred to in another table.

[APP–11182] Deleting the only invoice applied by this receipt will change the status to Unapplied.

Do you want to continue?

[APP–11183] Unable to validate a GL date in an open/closed period.

[APP–11187] You cannot update the distribution because it is posted and could not be reversed. To

allow reversal of a posted distribution, ensure that either today’s date, transaction date, or the

transaction GL date fall in an Open or Future Enterable period.

[APP–11189] An exemption already exists for this tax code and effective date.

[APP–11190] The location you entered already exists for the given parent.

[APP–11192] Cannot insert receivable application

[APP–11193] This receipt number exists for the same customer and for the same amount.

[APP–11194] If Period is ’Specific Date’ then all dates must be entered.

[APP–11197] Cannot expand flexfield structure (&HANDLE),structure not initialized.

[APP–11198] Flexfield Structure: &FNAME not defined in System Parameters

[APP–11199] Cannot find flexfield qualifier &QUALIFIER for &FLEXCODE &STRUCTURE.

[APP–11200] Cannot get currency information

[APP–11203] GL date, &GL_DATE, is not in an open or future–enterable period.

[APP–11207] Invalid arguments for the procedure &PROCEDURE. Please contact World Wide

Support

[APP–11209] &MESSAGE_TEXT

[APP–11210] &SEGMENT must be the first segment in the Sales Tax Location Flexfield.

[APP–11211] Location Segment &SEGMENT not defined in Sales Tax Location Flexfield You

attempted to insert a row into AR_LOCATION_VALUES where the segment qualifier for the row

was: &SEGMENT. This segment is not part of your Sales Tax Location Flexfield.

[APP–11212] Mandatory parameter &PARAM passed as NULL

[APP–11215] No discounts allowed on this installment unless it is fully paid.

[APP–11217] There is no rate for this currency, rate date and rate type in the database.

[APP–11218] The corresponding record for AR set of book is missing in GL.

[APP–11219] Your system parameters are not defined for Oracle.

[APP–11220] Posting is not allowed for this account.

[APP–11221] You must save this transaction before attempting to make it complete.

[APP–11222] Cannot run Revenue Recognition for &DATE_LOW to &DATE_HIGH in closed GL

periods.

[APP–11224] The parameter &PARAMETER may not be null when &OBJECT is called.

[APP–11225] The location already has a rate assignment which is active in this postal code and date

range. Ensure that the effective dates do not overlap for the particular location and postal code

range.

[APP–11226] The parameter &PARAM is not valid.

[APP–11227] You can have at most one Freight transaction line at either the line level or the invoice

level, but not at both levels.

[APP–11228] Please define all periods in which revenue is to be recognized.

[APP–11229] Overlapping periods for the accounting rule and first GL date exist.

[APP–11231] You cannot delete or clear a previously saved application. Deselect the Apply

checkbox instead.

[APP–11233] Warning: The following QuickCash receipt has been applied to this transaction:

&APPLIED

[APP–11234] At least one of the selected receipts cannot be confirmed.

[APP–11235] At least one of the selected receipts cannot be unconfirmed.

[APP–11236] Warning: Changing the receipt type will erase your Receivable Activity and

Distribution Set Information. Do you want to continue?

[APP–11237] Warning: Changing the receipt type will erase your customer information. You might

be required to re–enter payment method and remittance bank information. Do you want to

continue?

[APP–11240] At least one of the selected receipts has applications. Receipts with applications

cannot be deleted.

[APP–11241] At least one of the selected receipts has been posted. Posted receipts cannot be

deleted.

[APP–11248] Discount taken is greater than the discount available (&DISC_AVAILABLE).

[APP–11250] Discount not allowed for On Account application. Clear discount amount field or

enter zero.

[APP–11251] Discount cannot be positive for a negative invoice. Enter negative discount amount,

zero or clear the field.

[APP–11252] Cannot take unearned discount. The Allow Unearned Discount field in the Define

System Options form has been set to No.

[APP–11254] Receivables Location Flexfield has not been installed. Define your Receivables

Location Flexfield structure and assign it to the Location Flexfield Structure field in the System

Options form.

[APP–11255] More than &MAX_ERRORS database errors have been logged by the sales tax

upload process. Most Recent Oracle Error:– SQLCODE: &SQLCODE ”&SQLERRM”. Fix the

errors before proceeding.

[APP–11257] This will submit &NUM_OF_REC batch(es) for Approval and Format. Do you want

to continue?

[APP–11263] Max Memory (in bytes) must be greater than 65534.

[APP–11267] You cannot delete a standard memo line. Use the end date to make the memo line

inactive.

[APP–11270] Failed to get next sequence number. Contact your System Administrator.

[APP–11271] Failed to get next sequence number for GROUPING_TRX_TYPE_ID. Contact your

System Administrator.

[APP–11272] You may not delete records here. Update Printed to Skip instead.

[APP–11273] You cannot delete a statement cycle that has been assigned to a customer profile.

[APP–11274] You may not delete a statement cycle after statements have been printed.

[APP–11275] You may not deactivate a batch source which has been assigned to the profile option

AR:Transaction Batch Source.

[APP–11276] You cannot delete this class as it is assigned to a payment method.

[APP–11278] Remittance banks exist for this payment method. Delete them before adding the

payment method.

[APP–11279] This combination of payment method and account already exists.

[APP–11280] You may not delete this remittance bank as it is used elsewhere.

[APP–11281] You may not delete this payment method as it is used elsewhere.

[APP–11283] Duplicate Cash Application Rule. Please choose another rule.

[APP–11285] You may not have two fields of the same type within a record.

[APP–11286] Location structure is used by other organizations; use another one.

[APP–11287] Duplicate lockbox number(&FIELD1)–bank number(&FIELD2) combination. Please

enter a unique combination.

[APP–11290] Approval limits for user &USER and currency &CURRENCY already exist.

[APP–11293] Please enter either a table name or a constant segment value.

[APP–11294] Please enter a due date, due days, or Day of Month and Months Ahead.

[APP–11299] Failed to get next sequence number for ORDERING_RULE_ID. Contact System

Administrator.

[APP–11300] Print Lead Days must be greater than 0 for installment payment terms.

[APP–11301] Derive date should be enabled when Oracle Inventory is installed.

[APP–11302] The Last Number must be at least &DB_LAST_BATCH_NUM.

[APP–11303] This account already exists. Please enter a different account.

[APP–11305] You may not change this period’s status. A &token1 period cannot be changed to

&token2.

[APP–11308] The Number Of Periods must show the actual number of periods.

[APP–11311] Warning: The Post to GL flag is different than the related Credit Memo flag.

[APP–11312] Warning: Postable flag is different on invoice and commitment types.

[APP–11313] The Invoice type receivable flag is different than the related Credit Memo flag.

[APP–11314] Warning: Receivable flag is different on invoice and commitment types.

[APP–11316] You must run Revenue Recognition program before you close this period.

[APP–11317] Receipts are required to have billing locations as per the Billing Location filed in

Define System Options.

[APP–11319] You have unposted QuickCash receipts. Use PostBatch to post them.

[APP–11322] You have an active dunning letter set with inactive letters.

[APP–11323] You may not inactivate this record when it is referenced in a profile.

[APP–11324] Warning: You have inactivated a collector who is assigned to a customer.

[APP–11325] Invalid date. Start date should be today’s date or future date.

[APP–11327] Only one Dispute or Pending Adjustment bucket may be specified.

[APP–11328] Warning: You have inactivated a dunning letter set assigned to a customer.

[APP–11329] The ending position must be greater than the starting position.

[APP–11331] You may not enter overlapping fields for the same transmission format.

[APP–11332] You must post all transactions in this period before you close it.

[APP–11336] The postal code range assigned to the city falls outside the range defined for the

county and state. Manually Update the postal code range and rates for the County and State in the

”Tax Locations and Rates” form.

[APP–11337] The Records held in the Sales Tax Interface table indicated a location flexfield

structure which has more segments in it than the structure that you have defined within the System

Options form of ”Oracle Receivables”.

[APP–11338] An invalid parent location id (&PARENT_LOCATION_ID) has been assigned to this

location id (&LOCATION_ID).

[APP–11339] You have attempted to reload the same sales tax data without first clearing out old

rows from ar_tax_interface. Before Rerunning the concurrent program ”Sales Tax Interface” ensure

that both the STATUS and LOCATION_SEGMENT_ID columns are NULL.

[APP–11340] The Structure of your Sales Tax Location Flexfield indicated that a segment qualifier

of: &EXPECTED was expected, but the value: &FOUND was found instead.

[APP–11341] You need to setup one and only one tax code of type LOCATION.

[APP–11342] The tax code (&TAX_CODE) is not active for the transaction date (&TRX_DATE).

[APP–11343] The tax code (&TAX_CODE) is not defined. Ensure that the tax code specified is

defined in the ”Tax Codes and Rates” form of Oracle Receivables.

[APP–11344] General Ledger Distribution Percents total more than 100.

[APP–11349] Invalid Item. An Item must be specified to view details.

[APP–11350] Unable to find a distinct sales tax rate for the transaction. Supply a postal code that

can be used to identify a unique sales tax rate.

[APP–11351] Transaction line has no amount value; cannot calculate Tax amount.

[APP–11352] Unable to find a tax code for the transaction. Ensure that you have defined an active

Tax Code for either the Customer Site, Customer or Inventory item and that Oracle Receivables

System Option enables the usage of a tax code at that level. If tax codes are not defined at any of

these levels, you need to manually enter a tax code.

[APP–11353] Database View: &VIEWNAME could not generate a tax line, when one was expected

for the invoice line internally identified by customer_trx_line_id ( &LINE ).

[APP–11354] The transaction currency has no precision; unable to calculate Tax. Ensure that the

currency defined for the transaction has a precision in the ”Define Currencies” form.

[APP–11355] Unable to locate a valid Sales Tax rate for transaction. Ensure that an active Sales Tax

rate exists for the Location.

[APP–11356] Tax View: &VIEWNAME not found The tax engine was unable to calculate a tax rate

because the database view: &VIEWNAME was not found.

[APP–11357] The tax code (&TAX_CODE) does not have a rate associated with it. Ensure that you

have not interfaced a tax code of type ’Group’ and Contact customer support for further assistance.

[APP–11358] Tax code (&TAX_CODE) of type LOCATION cannot be used in a VAT only

installation.

[APP–11359] The Country field must be the most senior member of the Sales Tax Location

Flexfield.

[APP–11360] Accounts for &GL_DATE must sum to the line amount or 100 percent.

[APP–11362] The total percent for Revenue and Offset accounts must be 100. The total percent for

AutoInvoice Clearing cannot be changed.

[APP–11363] You cannot approve this adjustment because it is not within your approval limits.

[APP–11364] You cannot approve this adjustment because the amount does not close the

transaction.

[APP–11365] You cannot approve this adjustment because it has been posted.

[APP–11366] You cannot approve this adjustment because Line Item will be negative.

[APP–11367] You cannot approve this adjustment because it does not allow over application.

[APP–11368] Warning: Pending adjustments exist for this transaction.

[APP–11369] Changing the Agreement will not affect the accounting on this transaction.

[APP–11370] You cannot approve this adjustment because it has been approved or rejected.

[APP–11371] The account assignments for charges line number &LINE_NUMBER are incomplete.

[APP–11372] The Charges account set for line &LINE_NUMBER is incomplete.

[APP–11373] The Commitment Start Date of &START_DATE must be on or before the

Commitment End Date of &END_DATE.

[APP–11374] The Commitment End Date of &END_DATE must be on or after

&ACTIVITY_DATE, the Transaction date of the latest transaction applied to this commitment.

[APP–11375] The Commitment Start Date of &START_DATE must be on or before

&ACTIVITY_DATE, the Transaction date of the earliest transaction applied to this commitment.

[APP–11376] The Agreement is invalid with the current Transaction Date.

[APP–11377] The Bank Account is not active for the current Transaction Date.

[APP–11378] The Bank Account is invalid with the current Transaction Date.

[APP–11379] The current Transaction Date cannot be before the transaction date of your

commitment.

[APP–11380] The current CM Date cannot be before the transaction date of the transaction you are

crediting.

[APP–11381] The Transaction Date must be between the Commitment’s start and end dates.

[APP–11382] The Currency is invalid with the current Transaction Date.

[APP–11383] Default Salesperson &SALESREP_NAME is invalid with the current Transaction

Date.

[APP–11384] Memo Line on line &LINE_NUMBER is invalid with the current Transaction Date.

[APP–11385] The Payment Method is invalid with the current Transaction Date.

[APP–11386] The Primary Salesperson is invalid with the current Transaction Date.

[APP–11387] The Reason is invalid with the current Transaction Date.

[APP–11388] Salesperson &SALESREP_NAME on line &LINE_NUMBER is invalid with the

current Transaction Date.

[APP–11389] The Carrier is invalid with the current Transaction Date.

[APP–11390] The Batch Source is invalid with the current Transaction Date.

[APP–11391] The Status is invalid with the current Transaction Date.

[APP–11392] Tax line &TAX_LINE_NUMBER on transaction line &LINE_NUMBER is invalid

with the current Transaction Date.

[APP–11393] The Term is invalid with the current Transaction Date.

[APP–11394] The Transaction Type is invalid with the current Transaction Date.

[APP–11395] Unit Of Measure on line &LINE_NUMBER is invalid with the current Transaction

Date.

[APP–11396] The Dispute Amount must be between zero and &BALANCE, the balance due of this

transaction.

[APP–11397] The Dispute Amount must be either zero or &BALANCE, the balance due of this

transaction.

[APP–11398] The freight account assignments for line &LINE_NUMBER are incomplete.

[APP–11399] The Freight account set for line &LINE_NUMBER is incomplete.

[APP–11401] The account assignments for line number &LINE_NUMBER are incomplete.

[APP–11405] The Suspense account set for line &LINE_NUMBER is incomplete.

[APP–11406] The tax account assignments for tax line &OTHER_LINE_NUMBER on line number

&LINE_NUMBER are incomplete.

[APP–11407] The Tax account set for tax line &OTHER_LINE_NUMBER on line

&LINE_NUMBER is incomplete.

[APP–11408] The Unbilled Receivable account set for line &LINE_NUMBER is incomplete.

[APP–11409] The Unearned Revenue account set for line &LINE_NUMBER is incomplete.

[APP–11410] WARNING: The bank fields have been changed because the old values are not valid

for the entered currency.

[APP–11411] You have chosen a Batch Source with automatic batch numbering. Batch Name will

be cleared.

[APP–11413] This transaction cannot be completed. There are &NUMBER_OF_ERRORS

completion errors.

[APP–11414] The Charges account assignments do not equal the line amount for line

&LINE_NUMBER.

[APP–11416] The Charges account set records do not equal 100% for line &LINE_NUMBER.

[APP–11418] The Credit amount exceeds commitment balance of &COMMITMENT_BALANCE.

[APP–11419] The Credit Memo Date must be on or after the credited transaction’s date of

&TRX_DATE.

[APP–11422] Updating the Default Tax field does not affect existing tax lines.

[APP–11424] Unable to derive a GL date in an open/closed period.

[APP–11425] GL date has been set to &NEW_GL_DATE.

[APP–11426] Transaction date has been set to &NEW_TRX_DATE.

[APP–11427] The combination of Batch Source and Batch Name is not unique in the system. nEnter

a unique combination.

[APP–11428] GL date is required

[APP–11429] The freight account assignment does not equal freight amount for line

&LINE_NUMBER

[APP–11430] The freight account set records do not equal 100% for line &LINE_NUMBER.

[APP–11431] The GL Date must be on or after the commitment’s GL date of &GL_DATE.

[APP–11432] The GL Date must be on or after the credited transaction’s GL date of &GL_DATE.

[APP–11433] The adjustment GL Date must be later than or equal to the transaction GL Date.

[APP–11435] Revenue sales credit not equal to line amount or 100% for line &LINE_NUMBER.

[APP–11436] The total freight credit must be same as the total freight amount.

[APP–11438] The total line credit must be same as the total line amount.

[APP–11446] The low Purchase Order must be less than or equal to the high Purchase Order.

[APP–11447] The low Reference Number must be less than or equal to the high Reference Number.

[APP–11449] The low Transaction Date must be less than or equal to the high Transaction Date.

[APP–11450] This Transaction Number already exists. Please enter a different value.

[APP–11451] The low Transaction Number must be less than or equal to the high Transaction

Number.

[APP–11452] The low Transaction Type must be less than or equal to the high Transaction Type.

[APP–11453] The Last GL Date must be between &MIN_DATE and &MAX_DATE.

[APP–11454] Limits have not been set for this user.

[APP–11455] The Revenue account assignments do not equal the line amount for line

&LINE_NUMBER.

[APP–11456] Adjustment amount cannot cause the remaining amount due of this line item to be a

negative number.

[APP–11457] You must enter the transaction line number.

[APP–11458] The Accounting Rule, First Date and Duration fields must be entered for line

&LINE_NUMBER.

[APP–11459] Line number &LINE_NUMBER has no tax.

[APP–11460] You can have at most one Freight line for each transaction line.

[APP–11461] There are no account assignments for charges line number &LINE_NUMBER.

[APP–11462] There are no Charges account set records for line &LINE_NUMBER/

[APP–11463] There are no freight account assignments for line &LINE_NUMBER.

[APP–11464] There are no Freight account set records for line &LINE_NUMBER.

[APP–11466] There are no account assignments for line number &LINE_NUMBER.

[APP–11467] No accounting period is defined for &DATE.

[APP–11468] There is no Receivable account assignment.

[APP–11469] There are no Receivable account set records.

[APP–11470] There are no revenue account set records for line &LINE_NUMBER.

[APP–11471] There are no Autoinvoice Clearing account set records for line &LINE_NUMBER.

[APP–11472] There are no account assignments for Tax line &OTHER_LINE_NUMBER on line

number &LINE_NUMBER.

[APP–11473] There are no Charges account set records for tax line &OTHER_LINE_NUMBER on

line &LINE_NUMBER.

[APP–11474] There are no Unbilled Receivable account set records for line &LINE_NUMBER.

[APP–11475] There are no Unearned Revenue account set records for line &LINE_NUMBER.

[APP–11476] The exchange date must be entered for foreign currency transactions.

[APP–11477] The exchange rate must be entered for foreign currency transactions.

[APP–11478] The exchange rate type must be entered for foreign currency transactions.

[APP–11479] Transaction Numbering is manual. You must enter a value.

[APP–11480] WARNING: The Payment Method has been changed because the old value is not

valid for the entered currency.

[APP–11481] The Purchase Order Date is after the Transaction Date.

[APP–11482] Updating the primary salesperson does not affect existing sales credit lines.

[APP–11483] For credit memos the quantity and unit price fields must both be entered, or both be

null.

[APP–11484] Do you want to rederive default values for the transaction ?

[APP–11490] The Revenue account set records do not equal 100% for line &LINE_NUMBER.

[APP–11491] The sales credits for line &LINE_NUMBER must equal the line amount

[APP–11492] A more recent credit memo has been applied to this transaction.

[APP–11493] The Suspense account set records do not equal 100% for line &LINE_NUMBER.

[APP–11495] The tax account assignments do not equal the tax amount for tax line

&OTHER_LINE_NUMBER on line &LINE_NUMBER.

[APP–11496] The tax account set records do not equal 100% for tax line

&OTHER_LINE_NUMBER on line &LINE_NUMBER.

[APP–11497] You must enter an unique value for the transaction flexfield.

[APP–11498] The Unbilled Receivable account set records do not equal 100% for line

&LIN_NUMBER.

[APP–11499] You cannot approve this adjustment because the user profile AR:Invoices with

Unconfirmed Receipts has not been set to ”Approve” or ”Approve and Credit”.

[APP–11500] The Unearned Revenue account set records do not equal 100% for line

&LINE_NUMBER.

[APP–11501] You are updating freight information at the header level.

[APP–11503] Invoice type adjustment must make the balance due zero.

[APP–11504] Invoice has pending adjustments.

[APP–11505] You do not have approval limits for this currency.

[APP–11506] You cannot change the application type if applications exist.

[APP–11507] You may not update this field once applications exist.

[APP–11508] Cannot increment the last batch number in batch source table. Contact the System

Administrator.

[APP–11509] Adjustments cannot be more than available invoiced line amount.

[APP–11510] Amount exceeded approval limit.

[APP–11511] You may not apply more than the receipt amount.

[APP–11517] Invalid date. Enter a GL date in an open or future enterable period.

[APP–11522] For a particular Tax Code, only one record may be active at any given time. In order

to activate a new record, the existing record must first be deactivated using the End Date of the

existing record.

[APP–11523] For a particular Tax Code, records must not have overlapping Effective dates. Only

one Location Code can be active for any given effective date range and the ”From” date must be

earlier than the ”To” date.

[APP–11524] Please contact WWS for cash basis post upgrade procedures.

[APP–11525] Invalid line type (LINE_TYPE)

[APP–11526] &GENERIC_TEXT

[APP–11527] Installments

[APP–11528] Reversed

[APP–11529] You cannot delete a posted record.

[APP–11530] The low Document Number must be less than or equal to the high Document Number.

[APP–11531] Please save your changes before navigating.

[APP–11532] A reversed receipt cannot be cleared.

[APP–11533] You may not delete batches that contain receipts.

[APP–11534] Exchange rate information needs to be entered.

[APP–11535] Please enter a positive exchange rate.

[APP–11536] The exchange rate cannot be zero.

[APP–11537] There is no rate for this currency, rate date and rate type in the database.

[APP–11538] Receipt applications validated

[APP–11539] ERROR Credit balance not sufficient for applied amount

[APP–11540] Customer identified by invoice numbers

[APP–11541] ERROR Customer number is invalid

[APP–11542] ERROR GL date cannot be determined from the source

[APP–11543] ERROR MICR number refers to more than one customer

[APP–11544] ERROR Bank origination number not defined for this lockbox

[APP–11545] ERROR Batch amount does not equal sum of receipt amounts

[APP–11546] ERROR Batch record count does not equal number of receipts

[APP–11547] ERROR Receipt may not be applied to this invoice type

[APP–11548] Unable to continue validating, check transmission errors

[APP–11549] ERROR Currency is not available for use

[APP–11550] Currency matches bank account’s currency

[APP–11551] ERROR Receipt’s currency must match invoice’s currency

[APP–11552] ERROR MICR and customer number do not refer to the same customer

[APP–11553] ERROR Receipt has more than one customer number

[APP–11554] Customer identified by customer number

[APP–11555] ERROR Deposit Date cannot be later than GL Date

[APP–11556] ERROR MICR number already exists as bank account name

[APP–11557] Duplicate lockbox batch name

[APP–11558] ERROR Duplicate invoice number for customer

[APP–11559] Duplicate Item Number for receipt

[APP–11560] Duplicate lockbox number

[APP–11561] Duplicate overflow sequence for this receipt

[APP–11562] ERROR Receipt number already exists for this customer and amount

[APP–11563] Record validated

[APP–11564] ERROR GL date is not in an open or future period

[APP–11565] Lockbox is either not defined or currently has a Inactive status.

[APP–11566] ERROR Batch has invalid receipts

[APP–11567] Batch with this name does not exist in this transmission

[APP–11568] ERROR Currency must match the bank account’s currency

[APP–11569] ERROR Installment number is invalid

[APP–11570] Receipt with this Item Number does not exist.

[APP–11571] Lockbox with this number does not exist in this transmission.

[APP–11572] ERROR Receipt has invalid billing location

[APP–11573] ERROR Receipt has invalid applications

[APP–11574] ERROR Payment method not valid for this bank account

[APP–11575] Record identifier is not in the requested transmission format.

[APP–11576] ERROR The invoice does not belong to the paying customer or any related customers

[APP–11577] Invoice numbers are valid for this customer

[APP–11578] ERROR Lockbox amount does not equal sum of receipt amounts

[APP–11579] ERROR Lockbox record count does not equal number of receipts

[APP–11580] ERROR Receipt has more than one MICR number

[APP–11581] Customer identified by MICR number

[APP–11582] Remittance amount may not be less than zero.

[APP–11583] New record

[APP–11584] Receipt is not a duplicate

[APP–11585] Lockbox batch name is missing.

[APP–11586] Receipt has no customer

[APP–11587] ERROR You have specified your GL Date Source to be the Deposit Date, however no

Deposit Date has been provided.

[APP–11588] ERROR Exchange rate is unavailable

[APP–11589] Overflow records for each receipt must begin with the same sequence number.

[APP–11590] ERROR Invoice number is missing for applied amount

[APP–11591] Receipt is missing item number.

[APP–11592] Lockbox number is missing.

[APP–11593] Overflow record with next sequence is missing.

[APP–11594] Bank origination number is missing from transmission.

[APP–11595] ERROR Billing location is required and the customer has not been assigned a primary

Bill–To site

[APP–11596] Receipt number is missing.

[APP–11597] Receipt is missing remittance amount.

[APP–11598] ERROR GL date must be entered when the GL Date Source has been defined as a

Constant Date

[APP–11599] Transmission has more than one bank origination number.

[APP–11600] Fill characters trimmed from data.

[APP–11601] ERROR Invoice has been selected for automatic receipt

[APP–11602] Associated receipt with customer’s primary billing location

[APP–11603] ERROR Receipt Date cannot be later than GL Date

[APP–11604] Payment method is valid

[APP–11605] Receipt is valid

[APP–11606] ERROR Sum of the applied amounts is greater than remittance amount

[APP–11607] Receipt transferred

[APP–11608] ERROR Transmission amount does not equal sum of receipt amounts

[APP–11609] ERROR Transmission record count does not equal number of records

[APP–11610] Transmission has more than one transmission header.

[APP–11611] Transmission has more than one transmission trailer.

[APP–11612] Billing location is valid

[APP–11613] The amount of your application has been changed to &AMOUNT.

[APP–11614] Enter an applied amount no greater than the available line amount (&AMOUNT).

[APP–11616] One or more of the receipts selected for reversal has already been reversed. Please

exclude reversed receipts from your selection.

[APP–11617] One or more of the receipts selected for reversal has a posted chargeback attached and

can only be reversed by debit memo reversal. Additionally, one or more of the receipts selected of

type MISC cannot be reversed by debit memo reversal. Please change your selection in order to

perform the two types of reversals separately.

[APP–11618] One or more of the receipts selected for reversal cannot be reversed by debit memo

reversal.

[APP–11619] The receipts selected for reversal must be reversed by debit memo reversal

[APP–11620] You are not permitted to select this receipt type.

[APP–11621] You cannot enter a negative receipt amount for cash receipts.

[APP–11623] AR_UPDATE_DUE_DATE profile is not set. Ask your System Administrator

[APP–11632] Could not get value from a form field (&LOC)

[APP–11633] You entered a minimum accountable unit value which is the same as or less than the

lowest denomination for this precision. Enter a minimum accountable unit value which is not less

than or equal to 1/power( 10, precision ). In this case, enter a minimum accountable unit greater

than &LOWEST_DENOMINATION.

[APP–11634] You entered a minimum accountable unit value which is not a multiple of the lowest

denomination for this precision. Enter a minimum accountable unit value which is a multiple of

1/power( 10, precision ). In this case, enter a minimum accountable unit which is a multiple of

&LOWEST_DENOMINATION.

[APP–11636] The Tax amounts must be more precise than your functional currency allows. Enter a

precision and minimum accountable unit that is less than or equal to that of the functional currency.

[APP–11637] Selected &ITEMS Item(s). &EXCEPTIONS existing Exception(s) will be overridden

with Tax Rate or Effective date range.

[APP–11638] Selected &ITEMS Item(s). &EXEMPTIONS existing Exemption(s) will be

overridden with Exemption details or Effective date range.

[APP–11639] The effective dates of the Tax Code(s) are not within the effective dates of the Tax

Group. Modify the effective dates of the Tax Group before modifying the effective dates of the Tax

Code(s).

[APP–11640] Please fix transaction &TRX_NUMBER, line number &LINE_NUMBER

&OTHER_LINE_NUMBER . Your changes cannot be saved until you fix this problem.

[APP–11641] The balance amount of the transaction has been credited. Please save your changes

and complete the credit memo.

[APP–11642] Your responsibility can not enter transactions of class &CLASS.

[APP–11643] The low Entered Amount must be less than or equal to the high Entered Amount.

[APP–11644] CM &Installments

[APP–11645] You must enter the tax line number.

[APP–11646] Trans Num

[APP–11647] RECEIPT

[APP–11648] Please provide values for mandatory columns of Profile Credit, Terms and Receipts

before creating / viewing Currency Rates and Limits.

[APP–11649] The low Days Late must be less than or equal to the high Days Late.

[APP–11650] Please choose Summary or Detail as the Consolidated Billing Invoice Format.

[APP–11651] You have paid the same invoice twice. Please correct.

[APP–11652] Choose Application Type ”Multiple” to apply this receipt to split term invoices.

[APP–11653] You cannot delete this adjustment. Please create an offsetting adjustment instead.

[APP–11654] The low Billing Number must be less than or equal to the high Billing Number.

[APP–11655] vvv

[APP–11656] Update all Tax Codes at Invoice Line

[APP–11713] There is no rate for this currency, rate date and rate type

[APP–11736] Account for Chargeback Adjustment activity is not defined

Cause:

No account is specified for the Chargeback Adjustment activity.

Action:

Navigate to the Define Receivables Activity screen, query the Chargeback Adjustment activity, and

specify an adjustment account.

[APP–11813] Error calling &func_name

[APP–11814] Failed to allocate memory for &var_name

[APP–11815] &var_name should be &value

[APP–11816] Invalid argument – &var_name

[APP–11817] Null &var_name

[APP–11818] Batch source is not defined

[APP–11819] Set of Book is not set up

[APP–11820] VARCHAR for &var_name is not long enough

[APP–11824] The given piece memory is not large enough to hold a single row

[APP–11825] Please increase the value for the profile option ’AutoInvoice: Maximum Memory (in

bytes)’

[APP–11831] Detail posting has been disabled for your Accounting Flexfield

[APP–11832] Invalid extra column name

[APP–11833] Invalid segment name – &segment

[APP–11834] You cannot create this &flexname because dynamic insertion has been disabled

[APP–11835] Zero row in the main cache is not allowed

[APP–11836] The value of &var_name is too large for this operating system

[APP–11837] You must supply an unique id for your &flexname

[APP–11838] Cross validation for your key flexfield failed

[APP–11839] You cannot supply a blank &flexname

[APP–11840] The supplied &flexname has been disabled

[APP–11841] The supplied &flexname has expired

[APP–11842] Invalid &flexname

[APP–11843] You cannot supply summary account for your Accounting Flexfield

[APP–11845] Invalid sold to customer id (ORIG_SYSTEM_SOLD_CUSTOMER_ID)

[APP–11846] Invalid bill to customer reference (ORIG_SYSTEM_BILL_CUSTOMER_REF)

[APP–11847] Invalid bill to customer id (ORIG_SYSTEM_BILL_CUSTOMER_ID)

[APP–11849] The Bill To address id must exist in Oracle Receivables, and it must be assigned to the

Bill To customer (ORIG_SYSTEM_BILL_ADDRESS_ID)

[APP–11850] The Bill To contact reference must exist in Oracle Receivables, and it must be

assigned to the Bill To customer (ORIG_SYSTEM_BILL_CONTACT_REF)

[APP–11851] The Bill To contact id must exist in Oracle Receivables, and it must be assigned to the

Bill To customer (ORIG_SYSTEM_BILL_CONTACT_ID)

[APP–11853] Invalid ship to customer id (ORIG_SYSTEM_SHIP_CUSTOMER_ID)

[APP–11855] The supplied ship to address id must exist in Oracle Receivables, and it must agree

with the supplied ship to customer (ORIG_SYSTEM_SHIP_ADDRESS_ID)

[APP–11857] The supplied ship to contact id must exist in Oracle Receivables, and it must agree

with the supplied ship to customer (ORIG_SYSTEM_SHIP_CONTACT_ID)

[APP–11858] Related transactions must have the same or related Bill To customers

[APP–11859] The bill to customer of your transaction must be the same or related to the one of the

commitment

[APP–11860] You must supply a sales credit percentage when your batch source indicates you

supply percentages

[APP–11861] Invalid salesrep number (SALESREP_NUMBER)

[APP–11862] Invalid salesrep id (SALESREP_ID)

[APP–11863] Invalid sales credit type id (SALES_CREDIT_TYPE_ID)

[APP–11864] Your sales credit assignment must be for a transaction of line type LINE

[APP–11865] Sum of sales credit does not equal line amount

[APP–11866] Invalid sales credit type name (SALES_CREDIT_TYPE_NAME)

[APP–11867] Total percentage of sales credit does not equal 100

[APP–11868] Invalid transaction type name (CUST_TRX_TYPE_NAME)

[APP–11869] Invalid transaction type id (CUST_TRX_TYPE_ID)

[APP–11871] Invalid reason code (REASON_CODE)

[APP–11873] Invalid primary salesrep id (PRIMARY_SALESREP_ID)

[APP–11874] Invalid invoicing rule name (INVOICING_RULE_NAME)

[APP–11875] Invalid invoicing rule id (INVOICING_RULE_ID)

[APP–11877] Invalid payment terms id (TERM_ID)

[APP–11878] Invalid unit of measure name (UOM_NAME)

[APP–11879] Invalid unit of measure code (UOM_CODE)

[APP–11881] Invalid agreement id (AGREEMENT_ID)

[APP–11882] Invalid accounting rule name (ACCOUNTING_RULE_NAME)

[APP–11883] Invalid accounting rule id (ACCOUNTING_RULE_ID)

[APP–11884] The supplied gl date cannot be prior to your invoice date

[APP–11886] Invalid printing option (PRINTING_OPTION)

[APP–11887] You cannot supply freight freight charges when the Allow Freight option for your

transaction type is No

[APP–11888] Invalid fob point (FOB_POINT)

[APP–11889] Invalid ship via (SHIP_VIA)

[APP–11890] The supplied gl date is in a closed period

[APP–11891] Invalid currency code (CURRENCY_CODE)

[APP–11892] Invalid conversion type (CONVERSION_TYPE)

[APP–11893] Invalid account class (ACCOUNT_CLASS)

[APP–11894] The valid account classes are: REV, FREIGHT, TAX and REC

[APP–11895] The valid account classes are: REV, FREIGHT, TAX, REC and UNEARN

[APP–11896] The valid account classes are: REV, FREIGHT, TAX, REC and UNBILL

[APP–11897] The total distribution amount for a transaction line must equal the transaction amount

[APP–11898] The total distribution percent for a transaction line must be 100 for each account class

[APP–11899] You can only supply one freight account for a transaction of line type FREIGHT

[APP–11900] You can supply at most one Receivables account for a transaction (an invoice, a debit

memo or a credit memo)

[APP–11902] The document created must have a non–negative total amount because the creation

sign for your transaction type is Positive

[APP–11903] The document created must have a non–positive total amount because the creation

sign for your transaction type is Negative

[APP–11904] The total amount of your credit memo cannot exceed the balance of the debit item it

is crediting

[APP–11905] You cannot apply a transaction with a negative amount to another transaction with a

negative balance and vice versa

[APP–11906] A credit memo created with a positive total amount cannot credit an invoice which is

against a commitment

[APP–11907] An invoice against a commitment cannot have a negative total amount

[APP–11908] The Receivables account of your credit transaction must be the same as that of the

transaction being credited, if the credit transaction has the Open Receivables Flag set to No

[APP–11910] Invalid reference line id (REFERENCE_LINE_ID)

[APP–11911] Invalid reference line attribute value (REFERENCE_LINE_ATTRIBUTE1–15)

[APP–11913] All enabled segments of Transaction Flexfield must have a value

[APP–11914] Duplicate Transaction Flexfield

[APP–11915] Your credit memo transaction can only credit an invoice or a debit memo line

[APP–11916] Your debit memo transaction cannot be against a commitment, or credit any other

transaction

[APP–11917] Invalid payment method name (RECEIPT_METHOD_NAME)

[APP–11918] Invalid payment method id (RECEIPT_METHOD_ID)

[APP–11919] Invalid customer bank account name (CUSTOMER_BANK_ACCOUNT_NAME)

[APP–11920] Invalid customer bank account id (CUSTOMER_BANK_ACCOUNT_ID)

[APP–11921] Invalid credit method for crediting an invoice line which uses an accounting rule

(CREDIT_METHOD_FOR_ACCT_RULE)

[APP–11922] Invalid credit method for installments (CREDIT_METHOD_FOR_INSTALLMENTS)

[APP–11923] Invalid tax code (TAX_CODE)

[APP–11924] Invalid memo line name (MEMO_LINE_NAME)

[APP–11925] Invalid memo line id (MEMO_LINE_ID)

[APP–11926] The entered amount does not have the correct currency precision

[APP–11927] The supplied accounted amount does not match the one computed by AutoInvoice

within the specified tolerance

[APP–11928] Invalid set of books id (SET_OF_BOOKS_ID)

[APP–11929] You cannot supply tax and related information when the Tax Calculation option for

your transaction type is No

[APP–11930] The supplied amount must match unit selling price times quantity when you do not

use AutoInvoice Clearing account

[APP–11931] You must supply an invoice number when your batch source indicates manual invoice

numbering; otherwise you must leave invoice number blank

[APP–11932] You cannot supply tax precedence number when you disable compound tax

[APP–11933] You cannot supply payment terms for your credit memo transaction

[APP–11934] You cannot supply invoicing and accounting rules for your on account credit memo

transaction

[APP–11935] You cannot supply values in the RELATED_BATCH_SOURCE_NAME,

RELATED_TRX_NUMBER and RELATED_CUSTOMER_TRX_ID fields for credit memo

transactions

[APP–11936] You must supply a reason code for your credit memo transaction

[APP–11937] The Open Receivable flag of your credit memo must match the flag of the transaction

you are crediting

[APP–11938] You must supply unit of measure for transactions with items

[APP–11939] You must supply payment terms for your non–credit transaction

[APP–11940] You cannot supply system items for your debit memo transaction

[APP–11941] You must supply related batch source name when you supply related invoice number

[APP–11942] You must supply conversion rate when you supply conversion type of type User

[APP–11943] You must not supply conversion rate when you supply conversion type of types other

than User

[APP–11944] You must supply an invoicing rule, but not GL date when you supply an accounting

rule

[APP–11945] You must supply an accounting rule duration when you supply an accounting rule of

type variable duration

[APP–11946] Invalid related document value (RELATED_TRX_NUMBER)

[APP–11947] Invalid related document id (RELATED_CUSTOMER_TRX_ID)

[APP–11948] Duplicate invoice number

[APP–11949] Duplicate document number

[APP–11950] You must supply document number

[APP–11951] You must either pass amounts for all the compound tax lines or not pass any amounts

at all

[APP–11954] You cannot supply the customer bank account when the supplied or defaulted payment

method is of type Manual

[APP–11955] The supplied payment method must have already been set up for the bill to customer

or site

[APP–11956] Your transaction currency must match one of the currencies which are associated with

the payment method

[APP–11957] When the payment method is of type Automatic, you must either supply a valid bank

account or ensure that a primary bank account for the currency code of the transaction has been set

up for the Bill To customer

[APP–11958] The GL date of your credit memo transaction cannot be prior to the GL date of the

invoice it is crediting

[APP–11959] CM date cannot precede the date of the transaction being credited

[APP–11960] The bill to customer of your credit memo transaction must be the same or related to

the one of the invoice it is crediting

[APP–11961] You cannot supply any account assignment for your credit memo transaction when the

system option ’Use Invoice Accounting for Credit Memos’ is Yes

[APP–11962] The valid values for credit method for accounting rule are: PRORATE, LIFO and

UNIT

[APP–11963] The valid values for credit method for installments are: LIFO, FIFO and PRORATE

[APP–11964] The line type of your credit memo transaction must match the line type of the invoice

line or debit memo line it is crediting

[APP–11965] The currency code of your credit memo transaction must match the currency code of

the invoice line or debit memo line it is crediting

[APP–11966] An invoice can only reference a commitment

[APP–11967] The supplied accounted amount does not have the correct currency precision

[APP–11968] The two linked transactions must have the same set of books id

[APP–11969] The two linked transactions must have the same currency code

[APP–11970] The transaction to which you link this transaction to must have the line type ’LINE’

[APP–11971] You must supply a value for the sales credit amount

[APP–11972] You must supply a value for the distribution amount

[APP–11973] You must supply a distribution percentage when your batch source indicates you

supply percentages, or when your transaction uses an accounting rule

[APP–11974] The valid account classes for this line type are: ’REV’, ’UNBILL’ and ’REC’

[APP–11975] The valid account classes for this line type are: ’REV’, ’UNEARN’ and ’REC’

[APP–11976] The valid account class for this line type is ’TAX’

[APP–11977] The valid account class for this line type is ’FREIGHT’

[APP–11979] The supplied unit of measure and the primary unit of measure of your system item

must share the same unit of measure class

[APP–11987] Conversion rate for the given date, currency code, set of books and conversion type

has not been defined

[APP–11988] You must supply either tax amount or tax rate when passing tax lines

[APP–11990] You cannot link a transaction whose line type is ’LINE’ or ’CHARGES’ to another

transaction

[APP–11991] You must link the transaction of line type ’TAX’ to a transaction of line type ’LINE’

[APP–11992] You must supply sales credit assignments for this transaction when you specify you

require salesperson

[APP–11993] You cannot supply any transactions in a non–functional currency if you have not set

up both realized gains account and realized losses account

[APP–11994] You must supply the same transaction code as the one this transaction is linked to

[APP–11996] You must supply the amount for this transaction

[APP–11997] Unable to adjust your gl date which is in a closed period to a non–closed period

because there is more than one subsequent period which is open

[APP–11998] Unable to adjust your gl date which is in a closed period to a non–closed period

[APP–11999] Unable to derive a gl date for your transaction. Please ensure that your transaction is

in a gl period which you have defined

[APP–12005] This customer reference has two different customer prospect codes

[APP–12006] There are rejected records in &BADFILE

[APP–12007] The Tax Code does not allow override of the amount includes tax flag.

[APP–12008] You cannot set the amount includes tax flag when using a Tax Group.

[APP–12009] Cannot enter adjustment for an invoice selected for automatic receipt

Cause:

You are trying to enter an adjustment against an invoice selected for automatic receipt

[APP–12010] Cannot change adjustment invoice is selected for automatic receipt

Cause:

You cannot modify adjustment because the invoice ha

[APP–12011] You cannot import manual tax lines with tax inclusive amounts.

[APP–12012] CUST_SHIP_VIA_CODE is not defined in ORG_FREIGHT

Cause:

The CUST_SHIP_VIA_CODE must be defined in the ORIG_FREIGHT table.

Action:

Enter a CUST_SHIP_VIA_CODE defined in ORG_FREIGHT or define a new one.

[APP–12013] CUSTOMER_CATEGORY_CODE is not defined in AR_LOOKUPS

Cause:

The CUSTOMER_CATEGORY must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

CUSTOMER_CATEGORY.

Action:

Enter a value defined in AR_LOOKUPS or define a new one using the Define QuickCodes form.

[APP–12014] CUSTOMER_CATEGORY_CODE is not enabled in AR_LOOKUPS

Cause:

The CUSTOMER_CATEGORY_CODE must be enabled.

Action:

Update the enabled flag in the Define QuickCodes form to enable this customer category.

[APP–12015] CUST_TAX_CODE is not defined in AR_VAT_TAX

Cause:

The tax code specified must be defined in AR_VAT_TAX

Action:

Use the Define VAT Rates form to enter a new tax code.

[APP–12016] CUST_TAX_REFERENCE cannot be null when CUST_TAX_CODE is ’EXEMPT’

[APP–12017] SITE_USE_TAX_CODE is not defined in AR_VAT_TAX

[APP–12018] SITE_USE_TAX_REFERENCE is required when SITE_USE_TAX_CODE is

’EXEMPT’

[APP–12019] You may have only one active Dunning site use for each customer

[APP–12020] Amount applied cannot be greater than the original line amount of &AMOUNT.

[APP–12021] A new location was created for a value in an address segment field

Cause:

A value specified in an address field that constitutes part of your sales tax location flexfield

structure was not defined in AR_LOCATION_VALUES. This value has been created in

AR_LOCATION_VALUES.

[APP–12022] A cash receipt with this number, date, amount and customer already exists.

[APP–12023] A miscellaneous receipt with this number, date and amount already exists.

[APP–12024] The Bank Account cannot be null. This Receipt Source is being used by

AutoLockBox.

[APP–12025] The customer reference specified is invalid

Cause:

The customer reference specified does not exist in the RA_CUSTOMERS table or the

RA_CUSTOMERS_INTERFACE table. The customer reference could also be in error in the

RA_CUSTOMERS_INTERFACE table.

Action:

Specify a different customer reference or rectify the errors reported in

RA_CUSTOMERS_INTERFACE.

[APP–12026] The address reference specified is invalid

Cause:

The address reference specified does not exist in the RA_ADDRESSES table or the

RA_CUSTOMERS_INTERFACE table (in the Insert mode). The address reference could also be in

error in the RA_CUSTOMERS_INTERFACE table.

Action:

Specify a different address reference or rectify the errors reported in

RA_CUSTOMERS_INTERFACE.

[APP–12027] The address reference specified is not valid for this customer

Cause:

The address reference specified is not valid for this customer reference.

Action:

Specify an address reference that is defined for this customer reference.

[APP–12028] Payment Method is not defined in AR_RECEIPT_METHODS

Cause:

The payment method name specified must exist in AR_RECEIPT_METHODS.

Action:

Use the Receipt Classes Window to define a new payment method or enter an existing one.

[APP–12029] A bank account does not exist for the specified customer

Cause:

To assign a payment method to a customer, the customer must have a bank account defined.

Action:

Assign a bank account to this customer.

[APP–12030] The end date specified cannot be before the start date

Cause:

You have specified an end date that is before the start date.

Action:

Enter an end date equal to or after the start date.

[APP–12031] The address specified must have an active BILL_TO site defined

Cause:

The address specified must have an active BILL_TO site defined. The address specified may be in

error in the RA_CUSTOMERS_INTERFACE table.

Action:

Specify an address with an active BILL_TO site or rectify the errors reported in the

RA_CUSTOMERS_INTERFACE table.

[APP–12032] Customer payment method already active between the dates specified

Cause:

This payment method is already assigned to this customer and is active between the dates specified.

Action:

Modify the dates for which this customer payment method is active.

[APP–12033] Customer site payment method already active between the dates specified

Cause:

This payment method is already assigned to this customer site and is active between the dates

specified.

Action:

Modify the dates for which this customer site payment method is active.

[APP–12034] Customer already has a primary payment method for specified dates

Cause:

This customer has a primary payment method defined for the dates specified.

Action:

Modify the dates for which this customer payment method is active.

[APP–12035] Customer site has a primary payment method on the dates specified

Cause:

This customer site has a primary payment method defined for the dates specified.

Action:

Modify the dates for which this customer site payment method is active.

[APP–12036] This customer payment method is already active in this date range

Cause:

This customer payment method is already defined to be active for the date range specified within

the interface table.

Action:

Modify the date range for which this payment method is active.

[APP–12037] Multiple primary payment methods defined

Cause:

There are multiple primary payment methods defined in the interface table for assignment to the

same customer or customer site

Action:

Define only one primary payment method for a customer or customer site.

[APP–12038] If you require automatic receipts to be confirmed, you must also choose the clearance

method of ”By Matching”.

[APP–12039] The bank account specified must be of type ’EXTERNAL’

Cause:

Customer banks accounts must be defined to be of type ’EXTERNAL’.

Action:

Specify a bank account defined to be ’EXTERNAL’.

[APP–12040] Customer bank account is already active between the dates specified

Cause:

The dates on which this customer bank account is active overlap with an existing assignment of this

bank account to this customer.

Action:

Assign a different bank account or alter the dates on which this customer bank account is active.

[APP–12041] Customer site bank account already active between these dates

Cause:

The dates on which this customer site bank account is active overlap with an existing assignment of

this bank account to this customer site.

Action:

Assign a different bank account or alter the dates on which this customer site bank account is active.

[APP–12042] This customer already has primary bank account for specified dates

Cause:

The dates for which this primary customer bank account is active overlap with an existing primary

customer bank account assignment.

Action:

Alter the dates for which this account is active or do not specify this as the primary account.

[APP–12043] Customer site can have only 1 primary bank account for the dates specified

Cause:

There is a primary customer site bank account already defined for this customer for the dates

specified.

Action:

Alter the dates for which this account is active or do not specify this as the primary account.

[APP–12044] Duplicate rows exist in Interface table for this Customer Bank and date range

Cause:

The assignment of this bank to this customer is defined already defined in the interface table to be

active for this date range.

Action:

Alter the date range for which this assignment is active.

[APP–12045] Duplicate primary customer banks defined within the interface table

Cause:

There are multiple records defined within the interface table to be the primary bank account for

customer or customer site. The dates for which these records are active overlap.

Action:

Alter the dates for which this primary account is an active.

[APP–12046] You must specify either the customer_trx_line_id or the request_id

Cause:

You have failed to specify either a customer_trx_line_id or a request_id when calling the credit

memo module.

Action:

Modify your call to the credit memo module to specify a either the customer_trx_line_id,

customer_trx_id and previous_customer_trx_line_id or the request_id of the credit memos that you

wish to process.

[APP–12047] If you require automatic receipts to be confirmed, you must also choose a remittance

method.

[APP–12050] Accounting rule information is not complete for line &line_number

[APP–12063] Unable to create payment schedules for this transaction

[APP–12064] Failed to set selected for receipt batch id (&TOKEN)

[APP–12065] Failed to mass process records (&TOKEN)

[APP–12066] The routine to approve your applications has failed (&TOKEN)

Cause:

Use Help Display Database Error to see the error message(s)

Action:

Contact your local system support representative

[APP–12067] Link list failure (&TOKEN)

[APP–12068] Failed to allocate memory (&TOKEN)

[APP–12069] Application amount: &AMT. Invoice number &INV

Cause:

Use Help Error to see review the error(s).

Action:

Contact your local support representative.

[APP–12070] Failed to reverse receivable application records

[APP–12071] Cannot update receivable application records when confirming (&TOKEN)

[APP–12072] Please complete the offset account assignments

[APP–12081] Bill to site must exist to create debit memo

[APP–12085] Cannot get debit trx number from form

[APP–12086] Cannot get remit to address

[APP–12087] Cannot create debit memo transaction number

[APP–12107] You have specified an invalid error level

Cause:

An invalid error level was passed to the credit memo module setup routine.

Action:

Pass a valid error level to the module.

[APP–12108] You have specified incorrect values for the memory buffers

Cause:

The arcdsu() routine was passed invalid values for the error or scratch memory buffers.

Action:

Modify the routine that calls arcdsu() to pass correct buffers.

[APP–12109] Failed to get the net revenue schedule for an invoice line

[APP–12110] Cash Receipt history function failed

[APP–12111] Currency references distribution amounts with invalid precision

[APP–12112] Currency references line amounts with invalid precision

[APP–12113] Currency references installment amounts with invalid precision

[APP–12114] Currency references salesrep amounts with invalid precision

[APP–12131] This is a duplicate branch name for this bank. Please enter another

Cause:

Bank name and bank branch name must be unique

Action:

Enter a new bank name or branch name

[APP–12142] Expansion of token: &TOKEN failed

Cause:

An oracle error occurred during the expansion of token: &TOKEN

Action:

Check the syntax of the template file

[APP–12143] Unable to open the file: &FILENAME

Cause:

The temporary file: &FILENAME could not be created.

Action:

Please check operating system privileges and space free on the disk

[APP–12144] Unable to write to the file: &FILENAME

[APP–12145] Token Expansion Completed

[APP–12146] Error returned while executing file: &FILENAME

[APP–12147] Flexfield PL/SQL Pre–Processor failed

[APP–12148] Expansion of file complete

[APP–12149] Expanding file: &FILENAME

[APP–12150] Unable to generate log file name

Cause:

Unable to determine the name of the log file for this concurrent request.

Action:

Check operating system file permissions.

[APP–12151] Unable to open the file: &FILENAME for flexfield expansion

[APP–12152] Memory error while processing line: &LINE, TOKEN: &TOKEN

[APP–12153] Unexpected End of file, while expecting PL/SQL function

Cause:

End of file was reached without any pl/sql function declared for token: &TOKEN

Action:

Update the token file, correcting the syntax error

[APP–12155] Flexfield PL/SQL Pre–Processor Parameters:–

[APP–12156] Oracle error occurred during processing of function for token: &TOKEN

Cause:

Oracle error during processing of the pl/sql function associated with token: &TOKEN.

Action:

Check the syntax of the token file Ensure that all database objects have been installed

[APP–12157] Expansion completed without any errors

[APP–12158] Running file: &FILENAME

[APP–12159] Starting Token Expansion

[APP–12160] Expanding token: &TOKEN

[APP–12165] GL date must be in an open or future–enterable period

Cause:

The GL date that you entered is not in an open or future–enterable period.

Action:

Enter a GL date that is in an open or future–enterable period. Or, change the status for the period

that your GL date is in to ’Future’ or ’Open’.

[APP–12167] Cannot determine a billing location for customer &CUSTOMER_NAME

Cause:

There are multiple billing locations for this customer.

Action:

Define one billing location as the primary location for this customer.

[APP–12168] The paying customer for this invoice will be &CUSTOMER_NAME

[APP–12170] Cannot create cash receipt history

[APP–12172] Cannot create debit memo line

[APP–12173] Cannot create debit memo

[APP–12174] Cannot create miscellaneous cash distributions

[APP–12175] Cannot create payment schedule

[APP–12176] Agreement is invalid with current transaction date

[APP–12177] Currency is invalid with current transaction date

[APP–12178] Customer bank is invalid with current transaction date

[APP–12180] Transaction level salesrep &SALESREP_NUMBER is invalid for transaction date

[APP–12181] Salesrep &SALESREP_NUMBER for line &LINE_NUMBER invalid for transaction

date

[APP–12182] Standard memo line for line &LINE_NUMBER invalid for transaction date

[APP–12183] Payment method is invalid with current transaction date

[APP–12184] Primary salesperson is invalid with current transaction date

[APP–12185] Ship via is invalid with current transaction date

[APP–12186] Source is invalid with current transaction date

[APP–12187] Tax line &TAX_LINE_NUM for line &LINE_NUMBER has invalid tax code for

transaction date

[APP–12188] Term is invalid with current transaction date

[APP–12189] Transaction type is invalid with current transaction date

[APP–12190] Unit of measure for line &LINE_NUMBER is invalid for transaction date

[APP–12192] This invoice is not available

Cause:

You entered an invoice which either does not exist or is not appropriate for the receipt.

Action:

Choose a different invoice or enter the customer information manually.

[APP–12203] You cannot apply more than the original freight amount

[APP–12204] You can not apply more than the original line amount

[APP–12205] You cannot apply more than the original tax amount

[APP–12212] &FIELD_NAME must be entered

[APP–12229] No data found

Cause:

The program to create the chargeback could not find the information it needed in the table

ar_memo_lines.

Action:

Contact your local support representative.

[APP–12230] There is no default for remit to address

[APP–12330] The currency code of your transaction must be the same as the currency code of the

commitment

[APP–12331] You must supply a freight account for your freight line if you have not set up

AutoAccounting for freight account

[APP–12332] You must supply a tax account for your tax line if you have not set up

AutoAccounting for tax account

[APP–12333] You must supply a receivables account for your document if you have not set up

AutoAccounting for receivables account

[APP–12334] You must supply a revenue account for your line if you have not set up

AutoAccounting for revenue account

[APP–12335] You must supply an unbilled account for your line if you have not defined an unbilled

account in AutoAccounting

[APP–12336] You must supply an unearned account for your line if you have not defined an

unearned account in AutoAccounting

[APP–12337] The GL date of your invoice against a commitment cannot be prior to the GL date of

the commitment itself

[APP–12338] The transaction date of your commitment invoice cannot be prior to the transaction

date of the commitment

[APP–12339] You cannot supply territory flexfield data because you have not set up your territory

flexfield

[APP–12340] You must supply a valid transaction code for this line

[APP–12341] You must define a period for this GL date

[APP–12344] You must set up AutoAccounting for AutoInvoice Clearing account if your batch

source allows AutoInvoice clearing

[APP–12346] Ensure that supplied rule start date will generate GL Dates that are in Open or Future

periods when the GL Date – Closed Period Rule is set to ’Reject’ in the Define Invoice Sources

form

[APP–12355] Cannot get cash receipt history

[APP–12359] Cannot get customer transaction type

[APP–12361] Cannot get memo line

[APP–12367] Standard receipt reversal failed

[APP–12375] Cannot update cash receipt history

[APP–12392] You may not use automatic payment method

Cause:

You may not use automatic payment method for customers who have more than one parent

customers.

[APP–12393] You may not use automatic payment method

Cause:

You may not use automatic method for customers who have reciprocal customer relationship.

[APP–12403] Fatal error Occurred During Processing of Sales Tax Error Message

[APP–12404] Internal error in AutoAccounting, no error message reported

Cause:

The Sales Tax system has made a call to AutoAccounting

[APP–12409] Unknown Data type passed to Sales Tax Data Cache

[APP–12411] Sales Tax Data Cache: Unable to locate oldest item in data cache

[APP–12413] Sales Tax Data Cache: Not Initialized

[APP–12414] Sales Tax Data Cache: Unable to locate start of cache

[APP–12425] Sales Tax: Missing Parameter &PARAMETER

[APP–12426] Sales Tax: Parameter: &PARAMETER has null value

[APP–12427] Unable to update parameter field: &PARAMETER

[APP–12428] Unable to update ’Receivables’ account for this invoice

Cause:

The update to the receivables account failed, with

[APP–12429] Functional Amount: Can not find information for currency ”&CURR”

Cause:

There is no information for currency ”&CURR” in the

[APP–12430] Functional Amount: Mandatory parameter passed as NULL

Cause:

You have passed a NULL value to a parameter that re

[APP–12432] Sales Tax: Unknown Tax Method read from system parameters

[APP–12433] Attempt to re–initialize AUTOACC Cache without first clearing it down

Cause:

The Software has made a call to AR AUTOACC STARTUP without having already made a call to

AR AUTOACC CLEANUP in the same session.

Action:

Ensure that a call to AR AUTOACC STARTUP is made during a startup trigger of this form and

that a corresponding call to AR AUTOACC CLEANUP is made during a post–form trigger.

[APP–12434] AUTOACC Userexit is not initialized

Cause:

The Software has made a call to AR AUTOACC without having already made a call to AR

AUTOACC STARTUP in the same session.

Action:

Ensure that a call to AR AUTOACC STARTUP is made during a startup trigger of this form and

that a corresponding call to AR AUTOACC CLEANUP is made during a post–form trigger.

[APP–12436] Sales Tax: Unable to Get Minimum Accountable Unit for Currency: &PARAMETER

[APP–12437] Sales Tax: Unable to Get Precision for currency: &PARAMETER

[APP–12438] Sales Tax: Unable to allocate memory for internal argument structure

[APP–12441] Sales Tax: Unable to get Profile: USER_ID

[APP–12442] Sales Tax: Unable to find System Parameters for this set of books

[APP–12443] Sales Tax: Unable to get Profile: ORGANIZATION_ID

[APP–12444] Unable to find one distinct sales tax rate for this transaction

Cause:

You have not supplied a postal code for this transasaction

[APP–12445] Transaction line has no amount value – unable to compute Sales Tax Rate and

Amount

[APP–12446] Unable to find a tax code for this transaction CAUSE: A default Tax Code was not

found for this transaction.

[APP–12447] Defined currency has no precision, unable to calculate Sales Tax

[APP–12448] Unable to locate a valid Sales Tax Rate for transaction

[APP–12449] You have specified invalid arguments for the user exit CHANGE_OK

Cause:

You have not specified the FORM or MODE arguments for the CHANGE_OK user exit.

Action:

Modify the call to the CHANGE_OK user exit to pass the correct parameters.

[APP–12483] General Ledger is not installed. Please commit here

[APP–12497] AR Lookup Type and Code not found ( &TYPE, &CODE )

Cause:

Your database does not contain seed data for ar_lookup

[APP–12498] BANK_NAME is mandatory when creating a new bank account

Cause:

When creating a bank account the associated bank branch must also be created. To create a bank

branch the BANK_NAME and BANK_BRANCH_NAME fields must be populated.

Action:

Enter a value into the BANK_NAME field.

[APP–12499] BANK_BRANCH_NAME is mandatory when creating a new bank account

Cause:

When creating a bank account the associated bank branch must also be created. To create a bank

branch the BANK_NAME and BANK_BRANCH_NAME fields must be populated.

Action:

Enter a value into the BANK_BRANCH_NAME field.

[APP–12500] BANK_ACCOUNT_CURRENCY_CODE is mandatory creating a new bank account

Cause:

The bank account does not exist. To create a bank account the

BANK_ACCOUNT_CURRENCY_CODE field must be populated.

Action:

Enter a value into the BANK_ACCOUNT_CURRENCY_CODE field.

[APP–12504] AUTO_REC_INCL_DISPUTED_FLAG mandatory when profile class is null

Cause:

A value to indicate whether disputed items are to be included when using automatic receipts must

be entered when no profile class is specified.

Action:

Enter a valid value into the AUTO_REC_INCL_DISPUTED_FLAG field.

[APP–12505] TAX_PRINTING_OPTION is mandatory when no profile class specified

Cause:

A value for the tax printing option must be specified when the profile class is null.

Action:

Enter a value into the TAX_PRINTING_OPTION field.

[APP–12506] GROUPING_RULE_NAME is mandatory when no profile class is specified

Cause:

Grouping rule name must be specified when no profile class is specified.

Action:

Enter a value into the GROUPING_RULE_NAME field.

[APP–12507] CHARGE_ON_FINANCE_CHARGES_FLAG has an invalid value

Cause:

Valid values for the CHARGE_ON_FINANCE_CHARGES_FLAG are ’Y’ and ’N’.

Action:

Enter a valid value.

[APP–12508] GROUPING_RULE_NAME has an invalid value

Cause:

The GROUPING_RULE_NAME is not defined in the database.

Action:

Use the Define Grouping Rules form to define a new grouping rule or enter an existing one.

[APP–12509] CURRENCY_CODE has an invalid value

Cause:

The currency code is not defined.

Action:

Use the Currencies Window to define a new currency or enter an existing one.

[APP–12510] CREDIT_BALANCE_STATEMENTS is mandatory when STATEMENTS is ”Yes”

Cause:

A value for credit balance statements must be entered when statements are to be sent.

Action:

Enter a valid value into the CREDIT_BALANCE_STATEMENTS field.

[APP–12511] CREDIT_BALANCE_STATEMENTS must be ”No” when STATEMENTS is ”No”

Cause:

Credit balance statements cannot be sent when statements are not to be sent.

Action:

Enter ’N’ into the CREDIT_BALANCE_STATEMENTS field.

[APP–12512] STATEMENT_CYCLE_NAME must be null when STATEMENTS is ”No”

Cause:

The statement cycle name must be null when statements are not to be sent.

Action:

Update the STATEMENT_CYCLE_NAME field to null.

[APP–12513] OVERRIDE_TERMS is mandatory when no profile class is specified

Cause:

A value for override terms must be specified when the profile class is null.

Action:

Enter a valid value into the OVERRIDE_TERMS field.

[APP–12514] CREDIT_BALANCE_STATEMENTS must be null when STATEMENTS is null

Cause:

Credit balance statements cannot be sent if statements are not being sent.

Action:

Do not enter a value in the CREDIT_BALANCE_STATEMENTS field.

[APP–12515] STATEMENT_CYCLE_NAME must be null when STATEMENTS is null

Cause:

When statements are not to be sent a statement cycle name is not applicable.

Action:

Do not enter a value into the STATEMENT_CYCLE_NAME.

[APP–12516] CHARGE_ON_FINANCE_CHARGE_FLAG must be null when

INTEREST_CHARGES is null

Cause:

When interest is not being charged, compound interest charge is not applicable.

Action:

Do not enter a value into the CHARGE_ON_FINANCE_CHARGE_FLAG.

[APP–12517] INTEREST_PERIOD_DAYS must be null when INTEREST_CHARGES is null

Cause:

When interest is not being charged the number of days in an interest period is not applicable.

Action:

Do not enter a value into the INTEREST_PERIOD_DAYS field.

[APP–12518] DISCOUNT_GRACE_DAYS must be null when DISCOUNT_TERMS is null

Cause:

When no discount terms have been specified the number of discount grace days is not applicable.

Action:

Do not enter a value into the DISCOUNT_GRACE_DAYS field.

[APP–12519] DISCOUNT_GRACE_DAYS must positive

Cause:

The discount grace days must be greater than zero.

Action:

Enter a valid discount grace days.

[APP–12520] DISCOUNT_GRACE_DAYS must be null when DISCOUNT_TERMS is ”No”

Cause:

When there are no discount terms, the number of discount grace days is not applicable.

Action:

Do not enter a value into DISCOUNT_GRACE_DAYS.

[APP–12521] DUNNING_LETTER_SET_NAME must be null when DUNNING_LETTERS is

”No”

Cause:

When dunning letters are not to be sent, the dunning letter set name is not applicable.

Action:

Do not enter a value into DUNNING_LETTER_SET_NAME.

[APP–12522] DUNNING_LETTER_SET_NAME must be null when DUNNING_LETTERS is null

Cause:

When dunning letters is not set, the dunning letter set name is not applicable.

Action:

Do not enter a value into the DUNNING_LETTER_SET_NAME field.

[APP–12523] CURRENCY_CODE is mandatory when a profile amount value is populated

Cause:

When a value has been specified in a profile amount field, the currency code field is mandatory.

Action:

Specify a valid CURRENCY_CODE.

[APP–12528] You have not designated this inventory item to appear on invoices

Cause:

This inventory item has Invoice Enabled flag set to No.

Action:

Set the Invoice Enabled flag in the Invoicing zone of the Define Items form to Yes for this inventory

item.

[APP–12529] Please correct the revenue account assignment for line &LINE_NUMBER

[APP–12530] TAX_PRINTING_OPTION has an invalid value

Cause:

TAX–PRINTING_OPTION must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

’TAX_PRINTING_OPTION’

Action:

Use the Define QuickCodes Form to define a new value of enter an existing one.

[APP–12531] The customer profile for this customer reference already exists

Cause:

A customer profile already exists for this customer.

Action:

Enter a different customer reference.

[APP–12532] The customer profile class for update does not exist

Cause:

The customer profile class is not defined.

Action:

Enter a customer profile that exists in the database.

[APP–12533] Both TRX_CREDIT_LIMIT and OVERALL_CREDIT_LIMIT must be populated

Cause:

If one of the TRX_CREDIT_LIMIT or OVERALL_CREDIT_LIMIT fields are populated then both

must be populated.

Action:

Enter a value into both the TRX_CREDIT_LIMIT and the OVERALL_CREDIT_LIMIT fields.

[APP–12535] Duplicate record within the interface table

Cause:

You have defined a duplicate record in the interface table.

Action:

Delete one of the duplicate records.

[APP–12536] Conflicting profile classes specified for this customer/site

Cause:

You have specified different profile classes for records relating to the same customer or the same

customer site.

Action:

Enter profile classes that are the same for a customer or customer site.

[APP–12539] TRX_CREDIT_LIMIT may not be greater than the OVERALL_CREDIT_LIMIT

Cause:

The credit limit for a transaction cannot be greater than a customer’s overall credit limit.

Action:

Enter a TRX_CREDIT_LIMIT limit less than or equal to the OVERALL_CREDIT_LIMIT.

[APP–12540] DUNNING_LETTER_SET_NAME must have a unique value

Cause:

The dunning letter set name specified must be a unique value in the

AR_DUNNING_LETTER_SETS table.

Action:

Enter a unique value.

[APP–12541] COLLECTOR_NAME must have a unique value

Cause:

The collector specified must be a unique value in the AR_COLLECTORS table.

Action:

Enter a unique value.

[APP–12542] STANDARD_TERM_NAME must have a unique value

Cause:

The term name specified must be a unique value defined in the RA_TERMS table.

Action:

Enter a unique value.

[APP–12543] STATEMENT_CYCLE_NAME must have a unique value

Cause:

The statement cycle name specified must be a unique value defined in the

AR_STATEMENT_CYCLES table.

Action:

Enter a unique value.

[APP–12544] SITE_SHIP_VIA_CODE not defined in ORG_FREIGHT

Cause:

The SITE_SHIP_VIA_CODE must be defined in the ORIG_FREIGHT table.

Action:

Enter a SITE_SHIP_VIA_CODE defined in ORG_FREIGHT or define a new one.

[APP–12547] BANK_ACCOUNT_NUM is mandatory when creating a new bank account

Cause:

The bank account specified does not exist. To create a bank account requires a bank account

number.

Action:

Enter a value into the BANK_ACCOUNT_NUM field.

[APP–12548] AUTO_REC_INCL_DISPUTE_FLAG has an invalid value

Cause:

Valid values for the AUTO_REC_INCL_DISPUTE_FLAG are ’Y’ and ’N’.

Action:

Enter a valid value.

[APP–12549] PAYMENT_GRACE_DAYS must be a positive value

Cause:

PAYMENT_GRACE_DAYS must be greater than zero.

Action:

Enter a valid value.

[APP–12554] Token: &TOKEN expanded to nothing, Invalid Flexfield

Cause:

The Flexfield structure is not valid, possible errors include:– 1) Structure Not defined/frozen 2)

Segment qualifiers not used

Action:

Check each of the install and upgrade steps and ensure that the flexfield is correctly frozen

[APP–12558] BANK_ACCOUNT_CURRENCY_CODE is not defined in FND_CURRENCIES

Cause:

The currency code specified must be defined in the FND_CURRENCIES table.

Action:

Use the Currencies Window to enter a new currency or specify an existing one.

[APP–12560] Customer record for insert must have validated profile record defined

Cause:

A new customer record marked for insert must have a valid customer profile record defined in the

RA_CUSTOMER_PROFILES_INTERFACE table.

Action:

Define a profile record for this customer in the RA_CUSTOMER_PROFILES_INTERFACE table

or ensure that the profile record defined passes validation successfully.

[APP–12562] CREDIT MEMO userexit is not initialized

Cause:

The software has made a call to AR AUTOACC without having already made a call to AR

AUTOACC STARTUP in the same session.

Action:

Ensure that a call to AR AUTOACC STARTUP is made during a startup trigger of this form and

that a corresponding call to AR AUTOACC CLEANUP is made during a post–form trigger.

[APP–12574] Quoted string too long for protection CAUSE:

Quoted Strings was too long ACTION:

Shorten the length of your string data.

[APP–12583] To Postal Code falls outside the range defined for the parent segment

Cause:

You have specified a city that has assigned to it a

[APP–12584] You must supply a charges account for your charges line if you have not set up

AutoAccounting for revenue account

[APP–12586] Please correct the charges account assignment

[APP–12588] The Last Period to Credit must be greater than 0 but less than the accounting rule

duration of the invoice line you are crediting

[APP–12589] Unit credit memos can only be applied to invoices that use rules

[APP–12590] You must supply a quantity to credit when passing Unit credit memos

[APP–12593] Quantity for Charges lines must be 1 or –1

[APP–12603] Check Debit Memo Reversal failed

[APP–12612] The valid account class for this line type is ’CHARGES’

[APP–12613] Credit memo charges lines can only be applied to debit memo charges lines

[APP–12614] Only debit memos and credit memos may have a line type of ’CHARGES’

[APP–12615] Invoicing and accounting rules are not allowed on line type ’CHARGES’

[APP–12616] Unit of measure is not allowed for line type ’CHARGES’

[APP–12620] Unable to find precision or minimum accounting unit for currency

[APP–12621] You have specified invalid values for one of the transaction ID parameters

[APP–12622] You have specified an invalid value for the trx_class_to_process parameter

[APP–12623] You have specified an invalid value for the check_rules_flag parameter

[APP–12624] You may not define rules when your Accounting Method is Cash Basis

[APP–12639] Primary flag should be ’Y’ or ’N’.

[APP–12640] Invalid demand class code.

[APP–12641] Bank and branch name already exists.

[APP–12642] Duplicate bank and branch name in interface table.

[APP–12643] Validation failed for the key location flexfield structure

[APP–12644] Bank number already exists.

[APP–12645] This invoice does not meet the customer minimum amount requirements

[APP–12646] This invoice does not meet the bank minimum amount requirements

[APP–12647] A receipt site cannot be derived from this invoice

[APP–12650] First GL Date must be the same as the rule’s first date

[APP–12651] Warning: The Postal Code is not in the defined range of system option

[APP–12652] The Postal Code is not in the defined range of system option

[APP–12653] Warning: The Postal Code is not in the defined range of &QUAL &VALUE

[APP–12654] The Postal Code is not in the defined range of &QUAL &VALUE

[APP–12656] The assignments for &GL_DATE do not total &AMOUNT

[APP–12657] Updating table &TABLE_NAME

[APP–12658] &NUM_ROWS row(s) updated

[APP–12659] Deleting table &TABLE_NAME

[APP–12660] &NUM_ROWS row(s) deleted

[APP–12661] Locking table &TABLE_NAME

[APP–12666] Quantity, unit_selling_price, and amount must be null or zero for tax–only and

freight–only lines

[APP–12674] Invoice Date must be between Commitment’s start and end dates

[APP–12675] You cannot supply a GL date if the Post To GL option for your transaction type is No

[APP–12677] Duplicate Location

[APP–12682] Invalid tax exempt reason code (TAX_EXEMPT_REASON_CODE)

[APP–12683] Invalid tax exempt reason code meaning

(TAX_EXEMPT_REASON_CODE_MEANING)

[APP–12684] Invalid tax exempt flag (TAX_EXEMPT_FLAG). If the system option Allow

Exemptions = No then valid values are S or R, otherwise the valid values are S, R or E

[APP–12685] You must supply a tax exempt reason for tax–exempt lines

[APP–12687] Tax code must be active, adhoc, and of type VAT or SALES TAX

[APP–12690] None of the transaction flexfield contexts you have provided for this request have

enabled segments

[APP–12691] Every row in ra_interface_lines must have a value in the column

interface_line_context

[APP–12692] Invalid tax exempt flag (TAX_EXEMPT_FLAG). If the profile option Tax: Allow

Override = No then S is the only valid value

[APP–12698] The Last GL Date must be between the first and last invoice GL Date

Cause:

You have entered a Last GL Date that is either before the first GL date of the invoice line that you

are crediting or after the last GL date of that invoice line. The Last GL date must be between these

two dates.

Action:

Enter a Last GL Date that is between the first GL date of the invoice line that you are crediting and

the last GL date of that invoice line.

[APP–12699] Duplicate bank number in interface table.

[APP–12704] The derived GL date of the receipt is not in open or future enterable period

[APP–12710] You cannot skip a location segment in the location flexfield

Cause:

You have skipped a segment in the location flexfield.

Action:

You may leave a segment blank only if the child segment below it is also blank.

[APP–12711] You need to set up one and only one active location tax code.

[APP–12712] The vendor tax engine did not provide a return code

Cause:

All sales tax lines that are calculated by an insta

[APP–12713] The vendor tax engine did not provide tax rate or tax amount

Cause:

The installed vendor of sales tax returned TAX_SUCC

[APP–12716] Tax precedence provided but system option does not allow compound tax.

[APP–12717] An unsupported event code ( &PARAMETER ) was passed to the tax engine

Cause:

This is an internal programming error and should no

[APP–12727] Request &request_id completed with error

[APP–12728] Request &request_id deleted

[APP–12729] Request &request_id has an unknown status

[APP–12730] Request &request_id could not be found

[APP–12731] arxdisc: Initialization of payment schedule data structure failed

[APP–12732] arxdisc: Discount module failed

[APP–12733] arxdisc: Specified payment schedule does not exist

[APP–12735] arxdisc: Discount module returned unknown status

[APP–12739] Invoice lines with the same document number have been separated by the grouping

process, causing duplicate document numbers

[APP–12740] Invoice lines with the same invoice number have been separated by the grouping

process, causing duplicate invoice numbers

[APP–12742] Enter last transaction number for automatic transaction numbering

[APP–12744] Get Userid Failed

[APP–12746] You have specified invalid arguments for the user exit &CPLACC

The user exit &CPLACC takes three parameters: CCID – the code combination ID for the new plug

account; INVRULE – –2 for UNEARN, –3 for UNBILL; PARENT_ID – the ID for the line against

which the new entries in RA_CUST_TRX_LINE_GL_DIST will be created.

[APP–12747] Bill_to_orig_address_ref should only be defined for Ship–to Addresses

[APP–12748] Bill_to_orig_address_ref is not a valid bill–to address

[APP–12753] Accounting rule duration must be a positive integer

[APP–12754] Tax Code &PARAMETER of type location can only be used in Sales Tax

Implementations CAUSE: You interfaced a tax code of type: LOCATION, which cannot be

interfaced

[APP–12755] Tax Code &PARAMETER_1 defined but not active for the transaction dated

&PARAMETER_2 CAUSE: The tax code: &PARAMETER_1 is not active on the transaction date

of:

[APP–13000] This date already exists. Please enter a new date.

[APP–13001] You cannot enter a date on or after the employee’s termination date.

[APP–13002] You cannot enter salary for an employee without a salary basis.

Cause:

Employee lacks a salary basis.

Action:

Assign a salary basis (Assignment Window, Salary Information Region).

[APP–13003] You cannot enter a date for which a salary change already exists.

[APP–13004] You cannot change the date on an approved salary proposal.

[APP–13005] You cannot change the amount on an approved salary proposal.

[APP–13006] You cannot enter a salary change for this record.

Cause:

This is the initial salary for the employee or the employee’s salary basis has changed.

[APP–13007] The next date must be later than the record’s current date.

[APP–13008] You must enter a salary date or a performance date.

[APP–13009] You must enter a new amount on a salary proposal.

[APP–13010] You must enter a rating for a performance review.

[APP–13011] A salary change was entered after the date of this proposal.

[APP–13012] The new amount is outside the adjusted salary range.

[APP–13016] This assignment is not eligible for the salary element.

[APP–13017] This name already exists. Please enter a new name.

[APP–13018] A salary basis with this input value and grade rate already exists.

[APP–13019] You cannot change a salary basis for which an element entry exists.

[APP–13020] You cannot delete a salary basis that an employee is assigned to.

[APP–13021] You must enter a name for a salary basis.

[APP–13022] You must choose a basis for the salary basis.

[APP–13023] You must name an input value for a salary basis.

[APP–13024] Please enter a grade rate.

[APP–13025] Please enter a basis for the grade rate.

[APP–13026] A salary basis is already defined for this element.

[APP–13027] The salary basis is invalid for this session date.

[APP–13028] Please enter a review date on which the Assignment is active.

[APP–13043] The status effective date must be the same as or later than the COBRA qualifying date

[APP–13045] You cannot delete a status of &COBRA_STATUS.

[APP–13051] Please enter the period start and end dates before electing this COBRA coverage.

[APP–13052] The date received must be the same or later than the COBRA qualifying date.

[APP–13053] The due date cannot be the same or later than the COBRA qualifying date

[APP–13054] The due date cannot be after the COBRA termination date

[APP–13060] For a status of Elected please enter the period start and end dates

[APP–13101] You must select a state before moving to the next zone.

[APP–13102] A job can have only one worker’s compensation code per state

Cause:

a job may have only one worker’s compensation code per state. A worker’s compensation code for

this job in each state.

Action:

correct the job field, or remove the existing record for this job.

[APP–13104] This combination of carrier, state and location already exists

[APP–13105] This worker’s compensation code is already defined for this fund.

[APP–13106] You cannot delete a fund if codes and rates exist for it.

[APP–13107] This coverage already exists

[APP–13108] There are no future changes to delete

[APP–13109] A future change to the benefit prohibits the entered change

[APP–13110] This person has not been terminated

Cause:

The person you are attempting to enrol in COBRA due to termination has not actually been

terminated.

Action:

Check that the person has been terminated as of the COBRA qualifying date

[APP–13111] This person has not had their hours reduced

Cause:

The person you are attempting to enrol in COBRA has not had their standard hours reduced.

Action:

Check that the person has had their standard hours reduced as of the COBRA qualifying date.

[APP–13112] No COBRA eligible benefit plans exist for this person

Cause:

As of the COBRA qualifying date no COBRA eligible benefit plans exist for this person.

Action:

Check the qualifying date and element entries for the person in question.

[APP–13113] You must enter the period dates for an elected coverage

Cause:

You attempted to elect COBRA coverage without entering coverage period start and end dates

Action:

Enter period start and end dates.

[APP–13115] Coverage start date must be on or after qualifying date

Cause:

The coverage start date you have entered is before the COBRA qualifying date.

Action:

Enter a coverage start date equal to or after the COBRA qualifying date.

[APP–13116] Coverage end date must be on or after the start date

[APP–13117] The period end date must be later than the period start date

[APP–13128] A job is using this code. You cannot delete it.

[APP–13129] This code is in use as an override for an employee. You cannot delete it.

[APP–13130] You must enter a Government Reporting Entity.

In order to view a balance of this dimension, you must enter a Tax Unit.

[APP–13131] You must enter a Jurisdiction

In order to view a balance of this dimension, you must enter a Jurisdiction.

[APP–13134] You must elect or reject the coverage first

Cause:

You attempted to terminate a coverage before electing or rejecting it

Action:

Either accept or reject the coverage first

[APP–13135] You must notify before electing or rejecting

Cause:

You must first notify before electing or rejecting the COBRA coverage

Action:

Notify the COBRA coverage

[APP–13136] You cannot elect and reject a COBRA coverage

Cause:

You attempted to elect or reject a COBRA coverage which had already been rejected or elected

Action:

Delete the offending elect or reject status first

[APP–13137] You must choose a termination reason

[APP–13139] This line has no errors or warnings.

[APP–13140] &1 element does not exist OR is not linked to payroll.

Action – [1] If element does not exist, contact your support representative. [2] If element has no

link to employee’s payroll, create a link. [3] If element has a link to the payroll and you still get an

error, contact your support representative.

[APP–13141] A COBRA enrollment already exists for this person, event and date

Cause:

You attempted to enter an enrollment for given person, qualifying event and qualifying date which

already exist.

Action:

Re–query the existing enrollment.

[APP–13143] This COBRA status already exists

Cause:

The status you attempted to enter already exists.

Action:

Enter a different status or re–query the exist status.

[APP–13144] Payments must start on or before COBRA termination

[APP–13145] A payment schedule with this due date already exists

[APP–13146] You must enter both period start and period end dates

[APP–13148] You cannot change the batch type after you have entered batch lines.

Action:

Delete the batch lines you have entered and then change the batch type.

[APP–13149] Please enter the batch type.

[APP–13150] You must enter batch header information

[APP–13152] System totals do not equal user totals.

Action:

Correct the user totals or correct the batch line entries.

[APP–13153] Users cannot change the status to Error or Warning. This is a system function.

[APP–13156] You cannot change the status of Transferred.

Cause:

The batch has transferred to the HRMS database. You can no longer add, change or delete data in it

using MIX windows.

[APP–13157] Batch Header is for a different Batch type

[APP–13158] You must enter the Units for the Absence Information

[APP–13159] Please save your changes before moving to the next screen.

[APP–13160] You are not allowed to delete this record.

[APP–13161] This accrual band will overlap with another.

[APP–13162] This input value is already being used by this plan.

[APP–13163] Each accrual plan must have a unique name.

[APP–13164] This plan name is invalid.

Cause:

you have selected a name for a plan which would result in duplicate element type names.

Action:

rename the accrual plan.

[APP–13165] A ceiling must be present for all band or no bands at all.

[APP–13166] Please enter the amount received.

[APP–13167] Please enter the date received.

[APP–13169] No input value &IV_NAME exists for this element.

[APP–13170] &VALUE does not exist.

[APP–13171] Systems batch totals do not match user defined totals

[APP–13172] No recurring entry exists to increase or decrease.

[APP–13174] No input value can accept this amount. Contact your System Administrator.

[APP–13175] A duplicate of this entry exists.

[APP–14000] Please enter a revision less than or equal to the current revision

Cause:

You cannot enter an acceptance revision number that is greater than the current revision of your

purchase order document.

Action:

No action is required.

[APP–14002] WARNING: You are accepting against a previous revision

Cause:

You are accepting against a previous revision of the Purchase Order document.

Action:

No action is necessary.

[APP–14004] You cannot unselect this line. Please unselect shipments first

Cause:

You have attempted to unselect a line which has selected shipments.

Action:

Unselect the shipments before unselecting the line.

[APP–14006] You must select the line before selecting a shipment

Cause:

You are trying to select shipments and you did not select the corresponding line.

Action:

Select the line first, then select the shipments you want to copy for this line.

[APP–14008] Unable to find Receipt Accruals accounting flexfield

Cause:

You did not provide a valid Receipt Accruals accounting flexfield in your purchasing options setup.

Action:

Use the Define Purchasing Options forms to specify the Accounting Flexfield you want to use for

your receipt accruals.

[APP–14010] Unable to find next period

Cause:

You are trying to create accrual entries for your uninvoiced receipts prior to defining your calendar

for your next period. You may not have defined accounting periods at all or this purchase order may

be referencing a date that your current calendar does not include.

Action:

To set up your calendars, use \ Navigate Setup Financials Calendars Types, \ Navigate Setup

Financials Calendars Periods and \ Navigate Setup Financials Books.

[APP–14012] Unable to find set of books

Cause:

You are trying to create accrual entries for your uninvoiced receipts prior to defining your set of

books.

Action:

Use \ Navigate Setup Financials Books to set up your set of books.

[APP–14014] Unable to find purchasing period

Cause:

You are trying to create accrual entries for your uninvoiced receipts prior to defining your calendar.

You may not have defined accounting periods at all or this purchase order may be referencing a date

that your current calendar does not include.

Action:

To set up your calendars, see \ Navigate Setup Financials Calendars Types, \ Navigate Setup

Financials Calendars Periods and \ Navigate Setup Financials Books.

[APP–14016] You cannot &action a document if it is &status

Cause:

You are attempting to perform an approval or control action on a document. You cannot complete

the action on a document with this status.

Action:

Determine the required approval or control action to be completed on the document.

[APP–14018] You must enter a due date if you require acceptance

Cause:

You have not entered an acceptance due date.

Action:

Enter an acceptance due date.

[APP–14020] This range overlaps another range for the same authorization group

Cause:

You entered an accounting flexfield range that overlaps with another accounting flexfield range for

the same authorization group.

Action:

Enter \ Row Erase to clear the current values, then enter new values that do not overlap any other

range.

[APP–14022] Autocreate completed successfully. Autocreated &NUM_REQ_LINES_PROCESSED

requisition lines.

[APP–14024] You cannot automatically autocreate a blanket release because at least one requisition

line: &REQ, &REQ_LINE has a one–time item on it. Please use the manual mode and select the

blanket purchase order source line against which you wish to create the release.

[APP–14026] You cannot inactivate an item category with active items

Cause:

You are attempting to inactivate an item category that contains active items.

Action:

Inactivate all items in the item category before inactivating the category.

[APP–14028] You must enter a value in all the required fields

Cause:

You tried to leave this zone without entering a value in all the required fields.

Action:

Enter a value in the required fields.

[APP–14030] &ROUTINE–&ERR_NUMBER: Error during commit

Cause:

Oracle Purchasing was unable to save your changes while executing the routine &ROUTINE.

Action:

Take note of both this error number and actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14032] You cannot use \ Screen Save here

Cause:

You are trying to save your changes in a zone where you cannot save your changes.

Action:

Navigate to the first zone of this form and save your changes.

[APP–14034] Concurrent program &CONC_NAME returned error

Cause:

&CONC_NAME encountered an internal error. Parameters: &PARAMETERS

Action:

Note both this error number and the actions you are trying to perform. Contact your system

administrator for assistance.

[APP–14036] Expiration date must be greater than or equal to the effective date

Cause:

You entered a date in the expiration date field that pre–dates the date you entered in the effective

date field.

Action:

Enter an expiration date that is greater than or equal to the effective date.

[APP–14038] Please enter a charge account

Cause:

You are trying to leave the accounting flexfield window without entering any information. You

must enter an accounting flexfield combination in this form.

Action:

Enter a valid accounting flexfield combination in the accounting flexfield window.

[APP–14040] Please enter a valid charge account

Cause:

Charge account is mandatory and you did not enter one.

Action:

Enter a charge account.

[APP–14042] Please enter a valid requisition number

Cause:

You did not enter a valid requisition number.

Action:

Use \ Field QuickPick to choose a valid requisition number.

[APP–14044] Please enter a numeric value

Cause:

You entered alphanumeric values into a field that requires numbers.

Action:

Enter only numbers into the field or use your Define Purchasing Options forms to change your

system options to accept Alphanumeric values.

[APP–14046] Please enter a percent value between zero (0) and one hundred (100)

Cause:

You are trying enter a value less than zero or greater than 100.

Action:

Enter a percent value between 0 and 100

[APP–14048] Please enter a valid purchase order number

Cause:

You did not enter a valid purchase order number.

Action:

Use \ Field QuickPick to choose a valid purchase order number.

[APP–14050] Please specify your search criteria

Cause:

You must provide some search criteria in this zone in order to limit your query retrieval.

Action:

Enter at least one search criterion in the Search Criteria zone.

[APP–14052] Please enter a unique value

Cause:

You entered a value that already exists for this field. You must enter a different value.

Action:

Enter a unique value for this field.

[APP–14054] Enter ’Yes’ before saving your request

Cause:

You are trying to save a request without specifying if you want Oracle Purchasing to process your

request.

Action:

Enter ’Yes’ if you want Oracle Purchasing to process your request.

Action:

Use the menu to navigate to another form without saving your request if you do not want Oracle

Purchasing to process your request.

[APP–14056] User Exit #PO &EXIT_NAME returned error

Cause:

#PO &EXIT_NAME encountered an internal error. Parameters: &PARAMETERS

Action:

Note this error number and the actions you are trying to perform. Contact your system administrator

for assistance.

[APP–14058] Too many arguments. Expected: &NUM_EXPECTED Actual: &NUM_ACTUAL

Cause:

A user exit or concurrent program was called with too many arguments. &NUM_EXPECTED were

expected, and &NUM_ACTUAL were received.

Action:

Note both this error number and the actions you are trying to perform. Contact your system

administrator for assistance.

Action:

Modify the calling form to provide the correct number of arguments.

[APP–14060] You cannot use \ Field Copy here

Cause:

You are trying to copy the previous row’s values into the current row. You cannot duplicate fields in

this zone.

Action:

Enter all the information for the row you want to insert.

[APP–14062] You cannot use \ Field Delete here

Cause:

You are trying to clear a field that does not allow update.

Action:

No action is required.

[APP–14064] Error getting form pathname

Cause:

Oracle Purchasing cannot find information to bring up your requested screen.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your

system administrator for assistance.

[APP–14066] The item cannot be purchased in the default destination organization

Cause:

You chose an item that is not stockable in the default destination organization and subinventory.

Action:

Choose a valid stocking default destination organization for your item.

[APP–14068] The item cannot be purchased in the source organization

Cause:

You chose an item that is not stockable in the source organization and subinventory.

Action:

Choose a valid stocking source organization for your item.

[APP–14070] Missing required argument: &ARG

Cause:

A user exit or concurrent program was called without a required argument.

Action:

Modify the calling form to provide the correct argument.

Action:

Note this error number and the actions you are trying to perform. Contact your system administrator

for assistance.

[APP–14072] You cannot change Accrue On Receipt to ’No.’

Cause:

You tried to change Accrue On Receipt to ”No” or clear the field when Inventory or Shop Floor

destined distributions exist for this shipment. All inventory goods are always accrued on receipt.

Action:

No action required.

[APP–14074] Please enter a currency exchange rate greater than zero (0)

Cause:

You entered a currency exchange rate that is less than or equal to zero.

Action:

You must enter a currency exchange rate that is greater than zero.

[APP–14076] This is a new value. Use \ Field QuickPick to see existing values

Cause:

You entered a new value for this field. You can review and enter existing values.

Action:

Use \ Field QuickPick to see existing values.

[APP–14078] Unable to find an accrual account

Cause:

An accrual account is mandatory and Account Generator could not find a valid accrual account.

Action:

Remove this record and review your Account Generator setup.

[APP–14080] Unable to find a budget account

Cause:

A budget account is mandatory and Account Generator could not find a valid budget account.

Action:

You must remove this record and review your Account Generator setup.

[APP–14082] Unable to find a charge account

Cause:

A charge account is mandatory and Account Generator could not find a valid charge account.

Action:

Remove this record and review your Account Generator setup.

[APP–14084] Cannot find control function for &ACTION on &DOC_SUBTYPE &DOC_TYPE

Cause:

Oracle Purchasing was unable to find a control function for the given combination of document type

and action type.

Action:

Define a control function for the given document and action combination using the Define Position

Control form.

[APP–14086] Unable to find the employee id for your user id

Cause:

You did not associate an employee with your user name

Action:

Use \ Navigate Setup Organization Personnel Employees Enter to define yourself as an employee.

Action:

Ask your System Administrator to associate your user name with your employee record. Use the \

Navigate Security User option of the System Administrator responsibility.

[APP–14088] Unable to find job for &EMP_NAME

Cause:

Oracle Purchasing was unable to find a jobassignment for this employee.

Action:

Assign a job to this employee using the Enter Employee form.

[APP–14090] No requisition lines were autocreated. Possible causes: 1) You tried to autocreate lines

onto a blanket release where the combination rules were not satisfied. 2) Some other error occurred

during the autocreate process.

[APP–14092] Unable to find position for &EMP_NAME

Cause:

Oracle Purchasing was unable to find a position assignment for this employee.

Action:

Assign a position to this employee using Define Employees form.

[APP–14094] No records meet your search criteria

Cause:

There are no records that match your search criteria.

Action:

Re–enter your search criteria with fewer or different parameters.

[APP–14096] No requisitions meet your search criteria

Cause:

There are no requisitions or requisition lines that match your search criteria.

Action:

Re–enter your search criteria with fewer or different parameters.

[APP–14098] Unable to find an invoice variance account

Cause:

A variance account is mandatory and Account Generator could not find a valid variance Account.

Action:

Remove this record and review your Account Generator setup.

[APP–14100] &ROUTINE–&ERR_NUMBER: Output field name &OUTFIELD is incorrect

Cause:

You have encountered an internal Oracle error.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14102] &ROUTINE–&ERR_NUMBER: Could not allocate memory

Cause:

You have encountered an internal Oracle error.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14104] &ROUTINE–&ERR_NUMBER: Incorrect number of parameters passed

Cause:

You have encountered an internal Oracle error.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14106] Your Concurrent Request ID is: &REQUEST

Cause:

Oracle Purchasing generated a Concurrent Request ID for your request.

Action:

Take note of this number. You can use the \ Navigate Other Requests option of your menu to verify

the status of your request at any time.

[APP–14108] You cannot use \ Query Count here

Cause:

You are trying to count the number of records that have been queried in a zone that does not allowed

the counting of queried records.

Action:

No action is required.

[APP–14110] You cannot use \ Query Enter here

Cause:

You are trying to query an inquiry zone. You do not need to use \ Query Enter in this zone to

retrieve the information you need.

Action:

No action is required.

[APP–14112] You cannot use \ Query Enter here

Cause:

You are trying to query an inquiry zone. You do not need to use \ Query Enter in this zone to

retrieve the information you need.

Action:

No action is required.

[APP–14114] You cannot use \ Query Run here

Cause:

You are trying to query all records in an inquiry zone. You do not need to use \ Query Run in this

zone to retrieve the information you need.

Action:

No action is required.

[APP–14116] Please enter a currency exchange rate date

Cause:

You have entered a rate type other than ’User’ without a rate date.

Action:

You must enter a rate date.

[APP–14118] Please enter a currency exchange rate

Cause:

You have entered a rate type of ’User’ without a currency exchange rate.

Action:

You must enter a currency exchange rate.

[APP–14120] Please enter a currency exchange rate type

Cause:

You have entered a currency code without a currency rate type.

Action:

You must enter a currency rate type.

[APP–14122] No records meet your search criteria

Cause:

There are no records that match your search criteria.

Action:

Re–enter your search criteria with fewer or different parameters.

[APP–14124] Line &REQ_LINE_NUM belongs to requisition &REQ_NUM. The status of

&REQ_NUM has changed while you were working due to the actions of another user. It will not be

autocreated at this time.

[APP–14126] You cannot use \ Row Copy here

Cause:

You are trying to copy the previous row into the current row.

Action:

Enter all information for the row you want to insert.

[APP–14128] You cannot use \ Row Delete here

Cause:

You are trying to delete data from an inquiry form.

Action:

Use the entry form corresponding to this inquiry form to delete the row from the database. If you

are unable to delete this information in the corresponding entry form, you may be required to

inactivate or cancel it.

[APP–14130] You cannot use \ Row Delete. Please inactivate the row instead

Cause:

You are trying to delete a row that you cannot delete for database integrity reasons. Other records in

Oracle Purchasing may reference this row.

Action:

Inactivate the row by entering an inactivate date.

[APP–14132] You cannot use \ Row Erase here

Cause:

You are trying to clear the row using \ Row Erase in a zone that you cannot erase.

Action:

No action required.

[APP–14134] Please use \ Row Delete to remove this record from the database

Cause:

You tried to clear a committed record.

Action:

Use \ Row Delete to remove the record instead. If you are unable to delete this information, you

may be required to inactivate or cancel it.

[APP–14136] You cannot use \ Row Insert here

Cause:

You are trying to insert a row using \ Row Insert in a form that you cannot update.

Action:

You cannot insert a row in a display–only zone or between two existing rows on a complete

purchase order or requisition.

[APP–14138] You cannot use \ Screen Erase here

Cause:

You cannot erase this screen using \ Screen Erase.

Action:

No action is required.

[APP–14140] Unable to get sequence number

Cause:

Oracle Purchasing is unable to get the next sequence number for the record you are creating.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your system

administrator for further assistance.

[APP–14142] &ROUTINE–&ERR_NUMBER: &SQL_ERR

Cause:

A SQL error has occurred in &ROUTINE. The SQL error is &LSQL_ERR.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your system

administrator for further assistance.

[APP–14144] &FILE–&ERR_NUMBER: Subroutine &SUBROUTINE returned error

Cause:

Subroutine &SUBROUTINE returned an internal error.

Action:

Note this error number and the actions you are trying to perform. Contact your system administrator

for assistance.

[APP–14146] &FILE–&ERR_NUMBER: Subroutine &SUBROUTINE returned error.

Cause:

Subroutine &SUBROUTINE returned an internal error. Returned error message is: &ERROR_MSG

Action:

Note this error number and the actions you are trying to perform. Contact your system administrator

for assistance.

[APP–14148] &ROUTINE–&ERR_NUMBER: Cannot read form information

Cause:

&ROUTINE is unable to retrieve information from a form field.

Action:

.Take note of both this error number and the actions you were trying to perform. Contact your

system administrator for further assistance.

[APP–14150] &FILE–&ERR_NUMBER: Unknown code: &CODE

Cause:

An unknown or incorrect code was encountered.

Action:

Note this error number and the actions you are trying to perform. Contact your system administrator

for assistance.

[APP–14152] Use \ Row Erase to clear this unsaved record

Cause:

You are trying to delete a row that has not been saved to the database.

Action:

Use \ Row Erase to clear the row.

[APP–14154] You cannot use \ Zone Erase in this zone

Cause:

You are trying to clear the zone using \ Zone Erase.

Action:

No action required.

[APP–14156] You cannot use the \ Query functions in this zone

Cause:

You are trying to query records in an inquiry zone. You do not need to query information here.

Action:

No action is required.

[APP–14158] You cannot use \ Row Next while in a ZOOM

Cause:

You attempted to use \ Row Next in a zoom.

Action:

Return to the previous form to see the next record.

[APP–14160] Document action not completed successfully

Cause:

You attempted to perform a document action that is incompatible with the document status.

Action:

No action required.

[APP–14162] You must enter an approval hierarchy when using position hierarchies

Cause:

Approval hierarchy is required if you areusing approval position hierarchies and you are

forwardingor submitting a document to another approver.

Action:

Enter an approval hierarchy.

[APP–14164] Please enter a forward from employee

Cause:

You attempted to perform an approval action without including a forward from employee. Oracle

Purchasing automatically defaults the employee submitting the document for approval as the

forward from employee.

Action:

You must enter a forward from employee. You can only select another forward from employee for

Requisitions.

[APP–14166] Please enter a forward to employee

Cause:

You do not have authority to approve this document or funds are not reserved for the document.

Action:

Please enter an employee to forward the document to.

[APP–14168] Cannot change approval hierarchy or forward to employee

Cause:

You cannot modify the approval hierarchy and forward to employee. Approval hierarchy and

forward to are not required.

Action:

No action required.

Cause:

You cannot modify the approval hierarchy and forward to employee. Approval hierarchy and

forward to employee is required.

Action:

Forward the document to the employee listed in the forward to employee field.

Cause:

You cannot modify the approval hierarchy and forward to employee. You are using approval

hierarches and a default approval hirarchy is not defined.

Action:

Use Navigate Setup Purchasing Document Controls to setup a default approval hierarchy.

Cause:

You cannot modify the approval hierarchy and forward to employee. You are using approval

hierarchies and the default approval hierarchy does not include both the forward to and forward

from employee.

Action:

Define a default approval hierarchy that includes the forward from and forward to employee.

Cause:

You cannot modify the approval hierarchy and forward to employee.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your approval hierarchy document

controls.

[APP–14170] Cannot change forward from or forward to employee

Cause:

You cannot modify the forward from or forward to employee. Forward from and forward to

employee is not required.

Action:

Continue processing the approval action.

Cause:

You cannot modify the forward from or forward to employee. Forward to employee is required.

Action:

Forward the document to the employee listed in the forward to employee field.

Cause:

You cannot modify the forward from or forward to employee. You are using approval hierarchies

and a default approval hierarchy is not defined.

Action:

Use Navigate Setup Purchasing Document Controls to setup a default approval hierarchy.

Cause:

You cannot modify the forward from or forward to employee. You are using approval hierarchies

and the default approval hierarchy does not include both the forward to and forward from employee.

Action:

Define a default approval hierarchy that includes the forward from employee.

Cause:

You cannot modify the forward from or forward to employee.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your forward to and from document

controls.

[APP–14172] Cannot change forward to employee

Cause:

You cannot modify the forward to employee. Forward from and forward to employee is not

required.

Action:

Continue processing the approval action.

Cause:

You cannot modify the forward to employee. Forward to employee is required.

Action:

Forward the document to the employee listed in the forward to employee field.

Cause:

You cannot modify the forward to employee. You are using approval hierarchies and a default

approval hierarchy is not defined.

Action:

Use Navigate Setup Purchasing Document Controls to setup a default approval hierarchy.

Cause:

You cannot modify the forward to employee. You are using approval hierarchies and the default

approval hierarchy does not include both the forward to and forward from employee.

Action:

Define a default approval hierarchy that includes both the forward from and forward to employee.

Cause:

You cannot modify the forward to employee.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your forward to and from document

controls.

[APP–14174] Cannot change approval hierarchy or forward from employee

Cause:

You cannot modify the forward from or approval hierarchy. Approval hierarchy is not required.

Action:

Continue processing the approval action.

Cause:

You cannot modify the forward from or approval hierarchy. Approval hierarchy is required.

Action:

Forward the document to the employee listed in the forward to employee field or select another

forward to employee.

Cause:

You cannot modify the forward from or approval hierarchy. You are using approval hierarchies and

a default approval hierarchy is not defined.

Action:

Use Navigate Setup Purchasing Document Controls to setup a default approval hierarchy.

Cause:

You cannot modify the forward from or approval hierarchy. You are using approval hierarchies and

the default approval hierarchy does not include the forward from employee.

Action:

Define a default approval hierarchy that includes the forward from employee.

Cause:

You cannot modify the forward from or approval hierarchy.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your approval document controls.

[APP–14176] Cannot change approval hierarchy

Cause:

You cannot modify the approval hierarchy. Approval hierarchy is not required.

Action:

Continue processing the approval action.

Cause:

You cannot modify the approval hierarchy. Approval hierarchy is required.

Action:

Forward the document to the employee listed in the forward to employee field or select another

forward to employee.

Cause:

You cannot modify the approval hierarchy. You are using approval hierarchies and a default

approval hierarchy is not defined.

Action:

Use Navigate Setup Purchasing Document Controls to setup a default approval hierarchy.

Cause:

You cannot modify the approval hierarchy. You are using approval hierarchies and the default

approval hierarchy does not include the forward from employee.

Action:

Define a default approval hierarchy that includes the forward from employee.

Cause:

You cannot modify the approval hierarchy.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your approval document controls.

[APP–14178] Cannot change forward from employee

Cause:

You cannot modify the forward from employee. You want to forward the document using the

forward from employee listed.

Action:

Continue processing the approval action. You can only modify the forward from employee for

Requisitions.

Cause:

You cannot modify the forward from employee. You want to modify the forward from employee.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your approval document controls.

You can only modify the forward from employee for Requisitions.

[APP–14180] The forward–to person is not an on–line user.

[APP–14182] Cannot change approval hierarchy, forward from, or forward to

Cause:

You cannot modify the approval hierarchy, forward from employee, or forward to employee.

Approval hierarchy and forward to employee are not required and forward from is defaulted.

Approval hierarchy, forward from employee, and forward to employee are all displayed.

Action:

Continue processing the approval action.

Cause:

You cannot modify the approval hierarchy, forward from employee, or forward to employee. You

are using approval hierarchies and a default approval hierarchy is not defined.

Action:

Use Navigate Setup Purchasing Document Controls to setup a default approval hierarchy.

Cause:

You cannot modify the approval hierarchy, forward from employee, or forward to employee. You

are using approval hierarchies and the default approval hierarchy does not include both the forward

from and forward to employee.

Action:

Define a default approval hierarchy that includes both the forward from and forward to employee.

Cause:

You cannot modify the approval hierarchy, forward from employee, or forward to employee.

Action:

Use Navigate Setup Purchasing Document Controls to redefine your approval document controls.

[APP–14184] The Forward–To person cannot approve requisitions on–line

Cause:

You provided the name of a person that is not an Oracle Purchasing user, and cannot approve

requisitions on–line.

Action:

Print your requisition immediately, or let designated buyers print all requisitions that require manual

signature approval.

Action:

Select an approver who can approve requisitions online.

[APP–14186] You have insufficient authority. Please enter a Forward–To person

Cause:

You do not have enough authorization to approve this requisition. Please forward it to the next

approver.

Action:

Select an approver with a higher authorization level.

Action:

If you need to change your authorization responsibility, contact your system administrator for

assistance.

[APP–14188] You have insufficient authority to reserve funds for requisition

Cause:

You must reserve funds for this requisition. Enter an approver in the Forward To field who can

reserve funds for the requisition.

Action:

Select an approver with a higher authorization level for funds reservation.

[APP–14190] Document account total exceeds account limit rule

Cause:

The current document includes an account whose total exceeds the account total on a control rule.

The current document type is not associated with a job or position in the Define Position Controls

form.

Action:

Reduce the total amount for the problem account on the document such that the relevant account

control rules have a higher amount limit.

Action:

Increase the total amount on the appropriate control rule(s) using the Define Control Groups form.

Action:

Verify that the approver’s position or job in the Define Position Controls form is associated with a

control rule for the document type.

[APP–14192] A document account does not exist on any rule

Cause:

One of the accounts used on the current document does not exist in any of the control rules. This

automatically excludes the account from being authorized.

Action:

Change the accounts on the document.

Action:

Include the accounts in a rule using the Define Control Groups form.

[APP–14194] Document approval failed one or more item category rule(s)

Cause:

Amount limit of category control rule is less than the amount for the category on the document.

Action:

Reduce the amount ordered for the category on the document.

Action:

Increase the limit on the category control rule using the Define Controls Groups form.

Cause:

One or more of the categories on the document is excluded using exclude control rules.

Action:

Change the category on the document or remove the category from the exclude rule(s) using the

Define Control Groups form.

[APP–14196] Document total exceeds document total limit rule

Cause:

The current document total exceeds the document total control rule limit.

Action:

Reduce the amount of the document to be less than the minimum control total limit rule.

Action:

Modify the control document total limit rule using the Define Control Groups form.

[APP–14198] Document approval failed one or more item rule(s)

Cause:

Amount limit of item control rule is less than the amount for the item on the document.

Action:

Reduce the amount ordered for the item on the document.

Action:

Increase the limit on the item control rule using the Define Controls Groups form.

Cause:

One or more of the items on the document is excluded using exclude control rules.

Action:

Change the item on the document or remove the item from the exclude rule(s) using the Define

Control Groups form.

[APP–14200] Document approval failed due to location limit failure

Cause:

Amount limit of location control rule is less than the amount for the ship–to location on the

document.

Action:

Reduce the amount ordered for the ship–to location on the document.

Action:

Increase the limit on the location control rule using the Define Controls Groups form.

Cause:

One or more of the ship–to locations on the document is excluded using exclude control rules.

Action:

Change the ship–to location on the document or remove the location from the exclude rule(s) using

the Define Control Groups form.

[APP–14202] You cannot reserve a document when encumbrance is turned off

Cause:

Encumbrance has been turned off at the system level. No funds reservation can be performed.

Action:

Turn encumbrance on at system level using the Define Financials Options form, or do not attempt

funds reservation if encumbrance remains turned off.

[APP–14204] You cannot inactivate a group with active employees

Cause:

You tried to inactivate a group with active employees.

Action:

Remove the active employees before inactivating the authorization group.

[APP–14206] Please enter a group limit greater than or equal to all range limits

Cause:

You attempted to define a group limit that is less than a range limit.

Action:

Enter a group limit that is greater than or equal to the largest range limit.

[APP–14208] Please enter a range limit less than or equal to the group limit.

Cause:

You attempted to define a range limit that is greater than the group limit.

Action:

Enter a range limit that is less than or equal to the group limit.

[APP–14210] Please enter an accounting flexfield

Cause:

You are attempting to navigate to the next zone without entering the accounting flex field.

Action:

Enter the accounting flex field.

[APP–14212] GL start date is greater than GL end date

Cause:

You tried to enter a GL start date that is greater than your GL end date.

Action:

Enter a GL start date that is less than your GL end date.

[APP–14214] Start period is greater than end period

Cause:

You tried to enter a start period that is greater than your end period.

Action:

Enter a start period that is less than your end period.

[APP–14216] Please enter a job

Cause:

You are not using approval hierarchies and did not enter a job. Control rule groups are associated

with jobs when you are not using approval hierarchies.

Action:

Enter a job.

[APP–14218] Please enter a position

Cause:

You are using approval hierarchies and did not enter a position. Control rule groups are associated

with positions when using approval hierarchies.

Action:

Enter a position.

[APP–14220] Please enter a start date that is less than the end date

Cause:

End date is greater than start date.

Action:

Enter a start date that less than or equal to the end date.

[APP–14222] Position &EMP_POSITION under superior &SUPER_POSITION not assigned

Cause:

An employee is not assigned to one or more of the positions listed in the message.

Action:

Assigned a position to the employee.

[APP–14224] You have not selected an order type or order source in Oracle Purchasing

Cause:

You have not selected an order type or an order source for internal requisitions in Oracle

Purchasing.

Action:

Choose an order type and order source from the Internal Requisitions zone of the Define Purchasing

Parameters form.

[APP–14226] Failed Requisition Numbers

Cause:

The following requisition numbers could not be processed because corresponding requisition line or

location information was missing.

Action:

Please check the requisition numbers again.

[APP–14228] &ROUTINE–&ERR_NUMBER: An invalid object type has been specified

Cause:

Oracle Purchasing is unable to read your database information.

Action:

Take note of both this error number and the actions you were trying to perform. Contact your

system administrator for assistance.

[APP–14230] The GL date is not in an open period.

Cause:

The GL date that you entered does not fall within an open period.

Action:

Choose a different GL date or open the period for this date.

[APP–14232] You cannot navigate to the next zone after entering an action

Cause:

You have entered a action that does not allow you to perform additional control actions on the

document entity.

Action:

No action required.

[APP–14234] You must enter an end date if you enter a start date

Cause:

You entered a start date without an end date.

Action:

Enter an end date.

[APP–14236] You do not have sufficient privileges to modify this release

[APP–14238] You must specify a purchase order line number in order to copy

Cause:

Oracle Purchasing requires a purchase order line number in to order to copy the requisition line

information.

Action:

Enter a purchase order line number.

[APP–14240] Items on &OBJECT line &LINE_NUM do not match

Cause:

You are trying to place different items on the same &OBJECT line. All requisition lines you are

placing on the same &OBJECT line must refer to the same item.

Action:

Revise your requisition selection. Do not place requisition lines for different items on the same

&OBJECT line. Use the explode option if you need to change a requisition line.

[APP–14242] Item revisions on &OBJECT line &LINE_NUM do not match

Cause:

You are trying to place requisition lines with different item revisions on the same &OBJECT line.

You should place these requisition lines on different &OBJECT lines.

Action:

Revise your requisition selection. Do not place requisition lines with different item revisions on the

same &OBJECT line. Use the explode option if you need to change a requisition line.

[APP–14244] Line &LINE_NUM has a different reason code

Cause:

You are trying to place requisition lines to &LINE_NUM line that has a different reason code.

Action:

Enter the number of a &LINE_NUM line that matches the reason code.

[APP–14246] &OBJECT line &LINE_NUM has been canceled

Cause:

You are trying to place requisition lines on a cancelled &OBJECT line. You cannot add requisition

lines to a &OBJECT line after you cancelled this &OBJECT line.

Action:

Enter the number of a &OBJECT line that is not cancelled.

[APP–14248] &OBJECT Line &LINE_NUM has been finally closed

Cause:

You are trying to place requisition lines on a cancelled &OBJECT line. You cannot add requisition

lines to a &OBJECT line after you finally closed this &OBJECT line.

Action:

Enter the number of a &OBJECT line that is not finally closed.

[APP–14250] Line types on &OBJECT line &LINE_NUM do not match

Cause:

You are trying to place requisition lines with different line types on the same &OBJECT line. You

should place these requisition lines on different &OBJECT lines.

Action:

Revise your requisition selection. Do not place requisition lines with different line types on the

same &OBJECT line. Use the explode option if you need to change a requisition line.

[APP–14252] Line &LINE_NUM has a different reason code

Cause:

You are trying to place requisition lines to &LINE_NUM line that has a different reason code.

Action:

Enter the number of a &LINE_NUM line that matches the reason code.

[APP–14254] A requisition line has not been placed on an RFQ

Cause:

One or more of the requisition lines you selected requires a quotation.

Action:

Reference quotation information in the new purchase order you are creating.

[APP–14256] Cannot find rate. Currency: &CURRENCY, Type: &RATE_TYPE, Date: &DATE

[APP–14258] No rate has been defined for this date

Cause:

The rate type that you have entered uses pre–defined rates. No rate has been defined for the current

rate type and rate date combination.

Action:

Enter a rate date for which a rate has been defined.

[APP–14260] &ROUTINE–&ERR_NUMBER: Control array is null

Cause:

You have encountered an internal Oracle error.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14262] &ROUTINE–&ERR_NUMBER: Quote array is null

Cause:

You have encountered an internal Oracle error.

Action:

Note this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14264] Line &REQ_LINE_NUM of requisition &REQ_HEADER_ID already on purchase

order

Cause:

You are trying to place a requisition line on a purchase order line. This line was placed on a

purchase order line by another buyer while you were working.

Action:

Revise your requisition selection. Omit this requisition line from your purchase order line.

[APP–14266] Line &REQ_LINE_NUM of requisition &REQ_HEADER_ID has been canceled

Cause:

Line &REQ_LINE_NUM of requisition &REQ_HEADER_ID was been cancelled while you were

working. You cannot place a cancelled requisition line on a purchase order.

Action:

Attempt to AutoCreate again with the same search criteria. Oracle Purchasing will not retrieve the

cancelled requisition line.

[APP–14268] Line &REQ_LINE_NUM of Requisition &REQ_HEADER_ID is finally closed

Cause:

Line &REQ_LINE_NUM of requisition &REQ_HEADER_ ID has been finally closed. You cannot

place a finally closed requisition line on a purchase order.

Action:

Attempt to AutoCreate again with the same search criteria. Oracle Purchasing will not retrieve the

finally closed requisition line to place on the purchase order.

[APP–14270] One or more of the lines you tried to place on &OBJECT was modified

Cause:

A buyer modified one or more of the requisition lines you tried to placed on a &OBJECT line. You

cannot place a requisition line modified by a buyer onto a &OBJECT line.

Action:

Revise your requisition selection. Place your available requisition lines onto your &OBJECT lines

as you need. Review requisition lines which buyers modified in the View Requisitions form if you

need to place the modified requisition lines onto &OBJECT lines.

[APP–14272] Please copy at least one requisition line on &OBJECT Line &LINE_NUM

Cause:

You are trying to place several requisition lines onto a purchase order line or RFQ line without

specifying the requisition information you want to copy onto the purchase orderline.

Action:

Revise your requisition selection. Copy requisition line information from one requisition line onto

the purchase order line or the RFQ line.

[APP–14274] Please use Copy once only for &OBJECT line &LINE_NUM

Cause:

You are trying to copy the information of two or more requisition lines onto one purchase order or

RFQ line. You can only copy the information of one requisition line onto a purchase order or RFQ

line.

Action:

Revise your requisition selection. Choose one requisition line to be the line information source for

the purchase order or RFQ line.

[APP–14276] &ROUTINE–&ERR_NUMBER: Unable to store this entry

Cause:

You have encountered an internal Oracle error.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14278] &ROUTINE–&ERR_NUMBER: Option not recognized

Cause:

You have encountered an internal Oracle error.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14280] Units of measure on &OBJECT line &LINE_NUM do not match

Cause:

You are trying to place requisition lines using different units of measure on the same &OBJECT

line. You should place these requisition lines on different &OBJECT lines.

Action:

Revise your requisition selection. Do not place requisition lines using different units of measure on

the same &OBJECT line. Use the Explode option if you need to change a requisition line.

[APP–14282] You cannot delete this quotation line.

Cause:

The quotation line is being referenced in the AutoSourceRules Form for the item specified on this

quotation line.

Action:

If you want to delete this quotation line, you must first delete the reference to the quotation line in

the AutoSourceRules Form.

[APP–14284] You cannot delete this quotation line

Cause:

This quotation is referenced on a requisition line.

Action:

If you want to delete the quotation line, remove the reference to the quotation from the requisition

lines.

[APP–14286] Please provide the correct document type Cause : You can create controls for

Document Types of Quotations and Request For Quotations alone

Action: Please correct the Document Type

[APP–14288] This document is either incomplete or you do not have access to it.

Cause:

You have tried to access a document that either 1) is incomplete or 2) is unavailable to you.

Action:

In case 1 above: You must take an action against the document before you can view the action

history. In case 2 above: Check the document security level and access level under the Define

Document Controls form. Check this security level against your status (e.g., are you an active

Purchasing agent if security level is Purchasing, or are you a supervisor of the document owner if

security level is hierarchy...)

[APP–14290] Funds were not released from at least one distribution

Cause:

Oracle Purchasing was not able to reverse the encumbrance on one or more distributions.

Action:

Verify that your budgets are correctly defined. Verify that you are not using an inactive accounting

flexfield.

[APP–14292] Funds were not reserved for at least one distribution

Cause:

Funds were not reserved for one or more distributions.

Action:

Verify your requisition or purchase order through the view approval forms. Verify that your budgets

are correctly defined.

[APP–14294] Please enter an approver to whom you want to forward documents.

[APP–14296] Please enter an approver from whom you want to forward documents.

[APP–14298] Error from &FDFUNC: &ERROR

Cause:

Oracle Purchasing has encountered an internal error.

Action:

Note this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14300] A unit of issue (&UNIT_OF_ISSUE) has been specified in the source organization.

Do you want to convert your order quantity and UOM from &ORDER_QUANTITY

&ORDER_UOM to &CONVERT_QUANTITY &UNIT_OF_ISSUE?

[APP–14302] Unable to find last price history for this item

Cause:

You are trying to review the last price history information for an item that either exists on unprinted

purchase orders or has never been purchased in Oracle Purchasing.

Action:

No action is necessary.

[APP–14304] Customer and site must both be entered

Cause:

You attempted to enter a customer without a entering site. Both customer and site must be entered.

Action:

Enter both customer and site.

[APP–14306] You cannot delete a record associated with a requisition line

Cause:

You attempted to delete a location that is referenced on a requisition line.

Action:

No action required.

[APP–14308] An entry for &FLD is already defined

Cause:

An entry for &FLD has already been defined.

Action:

Enter another value.

[APP–14310] Please enter the name of the buyer to whom you want to assign requisition lines.

[APP–14312] Unable to get the current date

Cause:

The concurrent process was unable to select the current date from system.dual.

Action:

Note this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14314] Please enter the name of the employee whose inbox you want to access.

[APP–14316] Cannot delete the notifications

Cause:

Oracle Purchasing is unable to delete your notifications from the database.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14318] Unable to delete the notifications

Cause:

Oracle Purchasing is unable to delete your notifications from the database.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14320] Unable to submit periodic concurrent request

Cause:

Oracle Purchasing is unable to submit a concurrent request.

Action:

Note this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14322] The notification is obsolete. Please re–query to view updated notifications.

[APP–14324] Unable to get the next run date

Cause:

Oracle Purchasing is unable to select the date from system.dual.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14326] Please enter a unique name for this note

Cause:

You are entering a new note or copying a note from an existing one. You provided a name for your

note that is already used by another note.

Action:

Enter a unique name for this note.

[APP–14328] You cannot import or reschedule requisitions while using encumbrance

Cause:

You attempted to import or reschedule requisitions while using encumbrance.

Action:

Import or reschedule the requisitions without using encumbrance.

[APP–14330] You cannot leave spaces in your alphanumeric segment value

Cause:

You entered a character value in a key flexfield segment without entering the entire alphanumeric

flexfield segment value.

Action:

Enter the entire alphanumeric value for the key flexfield segment.

[APP–14332] Please enter all required outside processing information

Cause:

The outside processing details for this document line are incomplete.

Action:

You must enter job/schedule, operation sequence, resource sequence, and a line if you have chosen a

schedule. If you do not enter these fields you must remove the distribution.

[APP–14334] This range overlaps one of the existing ranges

Cause:

You entered multiple accounting flexfield range values which overlap each other.

Action:

Enter accounting flexfield range values which do no overlap each other.

[APP–14336] Attempt to setup concurrent program failed

Cause:

This form launches a concurrent program to periodically delete outdated notifications. The launch

process failed.

Action:

Note this error number and contact your system administrator for assistance.

[APP–14338] Purchase order lines not automatically converted to this currency

Cause:

You are trying to change the currency of a purchase order header after creating purchase order lines

for this header. Oracle Purchasing does not automatically convert price on the purchase order lines

after you change the currency.

Action:

Update the price information on all purchase order lines to reflect your changes in the currency.

[APP–14340] You cannot approve a range of test purchase orders

Cause:

You are trying to submit a range of test purchase order for approval. Oracle Purchasing lets you

print test purchase orders if, for example, you want to test the form alignment in your printer.

Oracle Purchasing will not attempt to approve a test purchase order.

Action:

No action is required.

[APP–14342] This blanket purchase order has no lines

Cause:

You are trying to place requisition lines on a blanket purchase order that has no lines.

Action:

Add lines to the blanket purchase order before placing requisition lines on the blanket purchase

order.

[APP–14344] The cancel date is not in an open period

Cause:

You provided a cancel date that is not in an open purchasing period. Oracle Purchasing creates an

encumbrance reversal journal entry batch when you cancel a purchase order (if your use Funds

Control). If the cancel date is not in an open period, Oracle Purchasing cannot create this batch.

Action:

Provide a date that is in an open period, or re–open the period.

[APP–14346] A contract purchase order has no lines

Cause:

Only standard, planned, and blanket purchase orders have lines.

Action:

No action is required.

[APP–14348] You cannot copy onto a blanket purchase order

Cause:

You are trying to copy requisition information onto a blanket purchase order line. Blanket purchase

order lines already include complete item and price information. You cannot copy requisition

information on these lines.

Action:

No action is required. Oracle Purchasing automatically adds this requisition line quantity to the

purchase order line unless you return or omit this requisition line.

[APP–14350] You cannot copy onto an existing purchase order line

Cause:

You are trying to copy requisition information onto a purchase order line. Existing purchase order

lines already include complete item and price information. You do not need to copy this

information.

Action:

No action is required. Oracle Purchasing automatically adds this requisition line quantity to the

purchase order line unless you return or omit this requisition line.

[APP–14352] The amount limit (&AMOUNT) on the header is too precise

Cause:

You tried to select a currency code for which the amount limit in the Header Zone is too precise.

Action:

Change the amount limit so that the precision is valid for the new currency.

[APP–14354] The minimum release amount (&AMOUNT) on the header is too precise

Cause:

You tried to select a currency code for which the minimum release amount in the Header Zone is

too precise.

Action:

Change the minimum release amount so that the precision is valid for the new currency.

[APP–14356] Minimum release amount (&AMOUNT) on line &LINE_NUM is too precise

Cause:

You tried to select a currency code for which the minimum release amount in the Line Zone is too

precise.

Action:

Change the minimum release amount so that the precision is valid for the new currency.

[APP–14358] You cannot change currency information on an approved purchase order

Cause:

You are attempting to change the currency information an approved purchase order. You cannot

change the currency information on an approved purchased order

Action:

No action is required.

[APP–14360] You cannot change currency information on encumbered purchase order

Cause:

You are trying to change the currency information on an encumbered purchase order. You cannot

change the currency information on an encumbered purchase order

Action:

No action is necessary.

[APP–14362] The amount agreed (&AMOUNT) is too precise

Cause:

You tried to select a currency for which the amount agreed in the Purchase Agreement Header Zone

is too precise.

Action:

Go to the Purchase Agreement Header Zone and change the agreed amount precision so that the

amount is valid for the new currency.

[APP–14364] The amount agreed (&AMOUNT) on line &LINE_NUM is too precise

Cause:

You tried to select a currency for which the agreed amount in the Purchase Agreement Line Zone is

too precise.

Action:

Go to the Purchase Agreement Line Zone for the given line and change the amount precision so that

the amount is valid for the new currency.

[APP–14366] You cannot delete a distribution that has been delivered

Cause:

You are trying to delete a purchase order distribution line of a purchase order after you entered

deliveries against this distribution. You can no longer delete this purchase order distribution.

Action:

No action is required.

Action:

You may want to cancel or freeze the purchase order shipment associated with the distribution you

want to delete.

[APP–14368] You cannot delete a distribution that has been billed

Cause:

You are trying to delete a purchase order distribution line of a purchase order after you matched an

invoice distribution to this distribution. You can no longer delete this purchase order distribution.

Action:

No action is required.

Action:

You may want to cancel or freeze the purchase order shipment associated with the distribution you

want to delete.

[APP–14370] You cannot delete a distribution created from an on–line Requisition

Cause:

You are trying to delete a purchase order distribution line of a purchase order that has been created

from an on–line requisition. You cannot delete this purchase order distribution.

Action:

No action is required.

[APP–14372] End purchase order number is less than start purchase order number

Cause:

You are trying to specify a purchase order number range with an upper bound that is less than the

lower bound.

Action:

Adjust the range of purchase order numbers you entered so that the upper bound is greater than the

lower bound.

[APP–14374] The end release number must be greater than zero (0)

Cause:

You are trying to submit a range of releases for printing by providing a highest release number of

zero. Release numbers must be greater than zero.

Action:

Enter an end release number that is greater than zero.

[APP–14376] Please enter a GL Date within an open purchasing period

Cause:

You provided a GL date that is not within an open purchasing period.

Action:

Use the Control Purchasing Periods form to open the period corresponding to the date you entered.

Action:

Enter a date that is within an open period.

[APP–14378] Please enter a release date within effective and expiration dates

Cause:

You are trying to enter a date for your blanket purchase order release that is not within the effective

and expiration dates of the blanket agreement.

Action:

Enter a release date that is within the effective and expiration dates of the blanket agreement.

Action:

Change the effective date or the expiration date of your blanket agreement header to include the

release date of your purchase order release.

[APP–14380] Destination details for this document line are incomplete

Cause:

You tried to create an internal requisition line with incomplete destination details.

Action:

Enter deliver to person, deliver to location, and destination organization.

[APP–14382] Incorrect number of arguments passed

Cause:

Oracle Purchasing could not print your purchase order.

Action:

Note this error number and the action you are trying to perform. Contact your system administrator

for assistance.

[APP–14384] You cannot change category a pre–defined item category

Cause:

You are trying to change the category of a pre–defined item. You cannot change the category of a

pre–defined item.

Action:

No action is required.

[APP–14386] You cannot change a pre–defined item description

Cause:

You are trying to change the item description of a pre–defined item. You cannot change the

description for this item.

Action:

No action is required.

Action:

If you want to allow item description changes for this item, use the Define Items form to change this

system–level option.

[APP–14388] No blanket purchase order exists for this item

Cause:

You are trying to review the blanket purchase order information of an item that you have not

previously ordered on a blanket purchase order.

Action:

No action is required.

[APP–14390] You cannot change the description of a received or billed item

Cause:

You are trying to update the description of an item that you have already received or matched to an

invoice. You cannot update the description of an item that has been received or billed.

Action:

No action is required.

[APP–14392] You cannot update the item description when a release exists

Cause:

You are trying to update an item description which already exists on a release.

Action:

No action is required.

[APP–14394] The last accept date must be greater than the promised date

Cause:

You are trying to enter a last accept date that is earlier than the promised date. You cannot enter a

last accept date that is less than promised date.

Action:

Enter a later last accept date or an earlier promise date.

[APP–14396] Oracle Purchasing saves your changes when you leave this zone

Cause:

You are trying to save your changes in the Multisource or Explode ZOOM forms. You do not need

to save your changes here. Oracle Purchasing automatically saves your changes when you leave the

forms and return to the AutoCreate form.

Action:

No action is required.

[APP–14398] Line quantity (&LINE_QTY) and shipment quantities (&SHIPMENT_QTY) do not

match

Cause:

Your line quantity and shipment quantities do not match. You cannot approve a purchase order with

quantity mismatches.

Action:

Adjust your line or shipment quantities so they match.

[APP–14400] The need–by date must be greater than the promise date

Cause:

You entered a need–by date that is earlier than the promised date. You must enter a need–by date

that is later than or equal to the promised date.

Action:

Enter a later need–by date or an earlier promised date.

[APP–14402] You cannot create new distributions for encumbered shipments

Cause:

You are trying to create a new distribution for an encumbered shipment. You cannot create new

distributions on encumbered shipments.

Action:

No action is required.

[APP–14404] Changing the amount agreed may affect your notification controls

Cause:

You have created notification controls based upon the amount agreed of this purchase order.

Action:

Please review your amount based notification controls.

[APP–14406] Please enter an amount for your notification controls

Cause:

You have created a notification control without an amount.

Action:

Enter a notification control amount.

[APP–14408] Changing the expiration date may affect your notification controls

Cause:

You have created notification controls based uponthe expiration date of this purchase order.

Action:

Please review your date–based notification controls.

[APP–14410] Changing the unit price may affect your notification controls

You have created notification controls based upon the amount agreed for this purchase order. Please

review your amount–based notification controls.

Action:

You may want to revise the Amount on your Notification Controls.

[APP–14412] Changing the line quantity may affect your notification controls

Cause:

You have created notification controls based upon the amount agreed for this purchase order.

Action:

Please review your amount–based notification controls.

[APP–14414] Please enter an effective date for your notification controls

Cause:

You have created a notification control without an effective date.

Action:

Enter a notification control effective date.

[APP–14416] Changing the unit of measure may affect your notification controls

Cause:

You have created notification controls based upon the amount agreed for this purchase order.

Action:

Please review your amount–based notification controls.

[APP–14418] This form cannot be used when Oracle Purchasing is not installed.

Cause:

Oracle Purchasing is not installed.

Action:

Install Oracle Purchasing.

[APP–14420] This shipment has no distributions

Cause:

Your shipment has no distributions.

Action:

Please enter at least one distribution for your shipment.

[APP–14422] This purchase order has no matched invoices

Cause:

Your Accounts Payable department has not matched any invoice to this purchase order.

Action:

No action required.

[APP–14424] No purchase order lines were processed

Cause:

AutoCreate did not process any requisition or purchase order lines.

Action:

Modify your search criteria or options on each requisition line such that AutoCreate can match the

requisition lines successfully to purchase order lines.

[APP–14426] Enter a price limit greater than or equal to the unit price

Cause:

You entered a price limit for this blanket purchase order line that is less than the unit price. The

price limit must be greater than or equal to the unit price.

Action:

Enter a unit price that is less than or equal to the price limit.

Action:

Enter a price limit that is greater than or equal to the unit price.

[APP–14428] You can only copy new records

Cause:

You are trying to use \ Row Copy on a previously saved purchase order line, shipment, or

distribution. You can only use this function on new records.

Action:

Enter all information for your purchase order line, shipment, or distribution.

[APP–14430] You cannot enter price breaks for amount–based lines

Cause:

You attempted to go to the Price Breaks zone. Price Breaks are not available for Amount based

lines.

Action:

No action required.

[APP–14432] The unit price must be less than the price limit (&NE_PRICE)

Cause:

You are trying to enter a purchase order shipment unit price that is greater than the price limit of the

purchase agreement line. The price limit is the maximum price you can use for this item on the

purchase agreement.

Action:

Enter a unit price for the shipment line that is less than or equal to the price limit.

[APP–14434] Quantity Ordered cannot be less than Quantity Billed (&QTY_BILLED)

Cause:

You are trying to reduce the quantity ordered on a purchase order line. The purchase order line was

completely or partially matched with an invoice. You cannot change the quantity ordered to a value

smaller than the quantity billed against the line.

Action:

Use \ Navigate Purchases View Purchases to determine the quantity billed for this purchase order

line. Enter a quantity ordered larger than or equal to the quantity billed.

[APP–14436] The quantity ordered cannot be less than the quantity billed

Cause:

You are trying to reduce the quantity ordered on a purchase order shipment. The purchase order

shipment was completely or partially matched with an invoice. You cannot change the quantity

ordered to a value smaller than the quantity billed against the shipment.

Action:

Use the View Purchase Orders form to determine the quantity billed for this purchase order

shipment. Enter a quantity ordered larger than or equal to the quantity billed.

[APP–14438] The quantity ordered cannot be less than the quantity delivered

Cause:

You are trying to reduce the quantity ordered on a purchase order line. You completely or partially

delivered this purchase order line. You cannot change the quantity ordered to a value smaller than

the quantity delivered against the line.

Action:

Enter a quantity ordered larger than or equal to the quantity delivered.

[APP–14440] Quantity ordered cannot be less than quantity encumbered (&QTY_ENC)

Cause:

You are trying to reduce the quantity ordered on a purchase order line. The purchase order line was

completely or partially matched with an invoice. You cannot change the quantity ordered to a value

smaller than the quantity billed against the line.

Action:

Use the View Purchase Orders form to determine quantity billed for this purchase order line. Enter

a quantity ordered larger than or equal to the quantity billed.

[APP–14442] Quantity ordered cannot be less than quantity received (&QTY_RCVD)

Cause:

You are trying to reduce the quantity ordered on a purchase order line. The purchase order line was

completely or partially received. You cannot change the quantity ordered to a value smaller than

the quantity received against the line.

Action:

Use the View Purchase Orders form to determine the quantity received for this purchase order line.

Enter a quantity ordered larger than or equal to the quantity received.

[APP–14444] The Quantity ordered cannot be less than the quantity received

Cause:

You are trying to reduce the quantity ordered on a purchase order shipment. The purchase order

shipment was completely or partially received. You cannot change the quantity ordered to a value

smaller than the quantity received for the shipment.

Action:

Use the View Purchase Orders form to determine the quantity billed for this purchase order

shipment. Enter a quantity ordered larger than or equal to the quantity billed.

[APP–14446] Shipment quantity (&SHIP_QTY) and distribution quantities (&DIST_QTY) do not

match

Cause:

Your shipment and distribution quantities do not match. You cannot approve a purchase order that

does not have matching shipment and distribution quantities.

Action:

Adjust your shipment and distribution quantities so they match.

[APP–14448] Please choose a valid action to process the requisition lines

Cause:

You are trying to save your changes without specifying what type of action you want to perform.

Action:

Enter an action type in the Action field, then press \ Screen Save to commit your changes.

[APP–14450] There are no requisition lines associated with this shipment.

[APP–14452] Your ship–to location is invalid for this organization.

Cause:

The ship–to location is invalid for the ship–to organization.

Action:

You must enter a valid ship–to location.

[APP–14454] The shipment end date must be before the shipment start date.

Cause: You have specified a shipment start date that is later than your shipment end date.

Action: Enter a shipment start date that is earlier than your shipment end date.

[APP–14456] Please enter a reason for canceling or freezing this purchase order

Cause:

You are trying to cancel or freeze a purchase order without providing a justification for your action.

Since you may be cancelling or freezing purchase order information shared by other buyers, Oracle

Purchasing requires you to provide a reason for your action.

Action:

Enter or reason for cancelling or freezing this purchase order.

[APP–14458] The start release date must be before the end release date

Cause:

You have specified a release start date that is later than your release end date.

Action:

Enter a release start date that is earlier than your release end date.

[APP–14460] The start release number must be less than the end release number

Cause:

The lower bound of your release range must be smaller than the higher bound of your release range.

Action:

Enter a lower bound for your release range that is lower than the higher bound.

[APP–14462] The start release number must be greater than zero (0)

Cause:

You are trying to submit a range of releases for printing by providing a lowest release number of

zero. Release numbers must be greater than zero.

Action:

Enter a release number that is greater than zero.

[APP–14464] You cannot change the unit of measure on an encumbered line

Cause:

You are attempting to change the unit of measure on an encumbered purchase order line. You

cannot change the unit of measure once you have encumbered at least one shipment for the purchase

order line.

Action:

No action is required.

[APP–14466] Please cancel this previously approved release

Cause:

You are trying to delete a release that has been approved at least once.

Action:

Use the Control Purchase Orders form to cancel the purchase order release information you wanted

to delete.

[APP–14468] Please cancel this previously approved purchase order.

Cause:

You are trying to delete a purchase order that has been approved at least once.

Action:

Use the Control Purchase Orders form to cancel the purchase order.

[APP–14470] Please cancel this encumbered purchase order

Cause:

You are trying to delete a purchase order that has been approved at least once.

Action:

Use the Control Purchase Orders form to cancel the purchase order.

[APP–14472] Please enter a value between zero (0) and one hundred (100)

Cause:

You are trying to enter a quality code rating that is not between 0 and 100.

Action:

Enter a value between 0 and 100.

[APP–14474] A quotation exists for this RFQ and supplier

Cause:

You have already entered a quotation for this RFQ and supplier.

Action:

No action is required.

[APP–14476] Please save your quotation with an Active status

Cause:

You are attempting to approve a quotation that is not active. You must save your quotation with an

Active status before you can approve it.

Action:

Change your quotation Status to Active and save your changes.

[APP–14478] Please close this quotation

Cause:

You are trying to delete a quotation that is still open.

Action:

Please alter the quotation expiration date.

[APP–14480] Please enter quotation line information

Cause:

You are trying to navigate to the shipments zone before entering line information.

Action:

Enter line information before navigating to the shipments zone.

[APP–14482] You cannot delete this quotation line

Cause:

You are trying to delete a quotation line that has been used on a purchase order.

Action:

Inactivate every shipment for this line or close the quotation.

[APP–14484] Minimum quantity must be less than or equal to the maximum quantity

Cause:

The minimum quantity is greater than the maximum quantity.

Action:

Enter the quantities so that the minimum quantity is less than or equal to the maximum quantity.

[APP–14486] WARNING: You have not entered an expiration date

Cause:

You have not entered an expiration date.

Action:

No action is required.

[APP–14488] You cannot use \ Query Enter here

Cause:

You are trying to use \ Query Enter in an additional information zone.

Action:

Use \ Zone Prior to navigate to the previous zone and then use \ Query Enter.

[APP–14490] WARNING: You have chosen an expired RFQ

Cause:

You have a chosen a RFQ that has expired.

Action:

No action is required.

[APP–14492] You cannot use \ Screen Erase here

Cause:

You cannot erase this screen using \ Screen Erase.

Action:

No action is required.

[APP–14494] You cannot update the supplier information when a quotation exists

Cause:

You may not change the supplier name or site because a quotation already exists for this RFQ

number and supplier.

Action:

Add new suppliers from whom you require quotation information to the RFQ supplier list.

[APP–14496] You have entered a duplicate supplier site for this quotation list

Cause:

You have entered a duplicate supplier site in this supplier quotation list. You cannot enter a supplier

site more than once in a supplier quotation list.

Action:

Remove the duplicate site from the supplier quotation list.

[APP–14498] Please enter a supplier list name

Cause:

You tried to go to the next zone without entering a supplier list name.

Action:

Enter a supplier list name.

[APP–14500] You have not entered enough serial numbers

Cause:

You are using lot control and your lot quantity is greater than the number of serial numbers assigned

to it.

Action:

Increase your lot quantity.

Cause:

You are not using lot control and your transaction quantity is greater than the number of serial

numbers you have defined.

Action:

Create additional serial numbers.

[APP–14502] You have entered too many serial numbers

Cause:

You are using lot control and have assigned too many serial numbers to the lot quantity.

Action:

Reduce the number of serial numbers.

Cause:

You are not using lot control and you have defined more serial numbers than the transaction

quantity.

Action:

Increase your lot quantity.

[APP–14504] Cannot relieve funds reserved for requisition

Cause:

Oracle Purchasing is not able to reverse the encumbrance journal entry corresponding to your

cancelled requisition.

Action:

Verify that your budgets are correct. Verify that you are not using any inactive accounting

flexfields.

[APP–14506] You cannot change this field while requisition lines exist.

Cause:

You cannot change the value of this field. Oracle Purchasing uses this field to ensure that valid

requisition lines are displayed in the requisition lines zone.

Action:

You must remove the requisition lines if you want to change the field.

[APP–14508] Revision &REVISION is not valid for &ORG

Cause:

You have enter an invalid item revision for your source or destination organization.

Action:

Enter a valid item revision for your source and destination organizations.

Action:

Change your source or destination organization.

[APP–14510] Please enter a unique RFQ or Quotation subtype.

[APP–14512] You cannot delete document types installed with Oracle Purchasing. You can delete

only user–defined RFQ and Quotation types.

[APP–14514] You cannot update this document type

Cause:

You cannot update this document type.

Action:

No action required.

[APP–14516] You cannot delete a document type that has been used to create document.

[APP–14518] Please select a supplier list name

Cause:

You are trying to copy a supplier list onto this RFQ and have not specified a supplier list name.

Action:

Choose a supplier list name and press Apply to copy the suppliers onto this RFQ.

Action:

Press Cancel if you do not want to copy suppliers onto this RFQ.

[APP–14520] You cannot copy onto an existing RFQ line

Cause:

You tried to copy a requisition line onto an RFQ line that already exists.

Action:

Enter a larger number in the RFQ Line field.

[APP–14522] You cannot delete an RFQ that has been printed

Cause:

You are trying to delete an RFQ that has been printed.

Action:

No action is required.

[APP–14524] Please enter a numeric value

Cause:

You are trying to enter an alphanumeric value into a field that requires numeric values as a result of

your system option setup choices.

Action:

Enter a number for this Document or change your system numbering option.

[APP–14526] No RFQ lines were processed

Cause:

No Requisition or RFQ Lines were processed.

Action:

Change your search criteria, or select a different RFQ that allows requisition lines and RFQ lines to

be combined.

[APP–14528] WARNING: You have not entered a close date for this RFQ

Cause:

You have not entered a close date for this RFQ.

Action:

No action required.

[APP–14530] You cannot update a supplier for whom an RFQ has printed

Cause:

You are trying to update a supplier for whom an RFQ has printed.

Action:

No action is required.

[APP–14532] You cannot delete an RFQ you used to AutoCreate Quotations

Cause:

You are trying to delete an RFQ that was used to AutoCreate a quotation.

Action:

No action is required.

[APP–14534] You cannot update the supplier address in this form

Cause:

You are trying to update the supplier address information in an inquiry zone.

Action:

Please use the Define Suppliers forms if you want to change the supplier site address information.

[APP–14536] You cannot enter a duplicate supplier site in an RFQ supplier list

Cause:

You are trying to duplicate supplier sites in your RFQ supplier list.

Action:

No action is required.

[APP–14538] You already added this supplier and site to the RFQ supplier list

Cause:

You are trying to duplicate supplier sites in your RFQ supplier list. A supplier and site can be

referenced in the RFQ supplier list only once per RFQ.

Action:

Please choose a supplier and site that is not already in the RFQ supplier list.

[APP–14540] You cannot delete a supplier for whom an RFQ has printed

Cause:

You are trying to delete a supplier from the RFQ Supplier List and an RFQ has already been printed

for this supplier.

Action:

No action is required.

[APP–14542] Please enter a supplier list name

Cause:

You are trying to copy a supplier list and have not chosen a supplier list name.

Action:

Please choose a supplier list name. If you no longer wish to copy a supplier list, enter No in the

Copy Supplier List field.

[APP–14544] You cannot view the RFQ until it has been created

Cause:

You are trying to view a new RFQ which does not exist.

Action:

Select Add To RFQ and enter an existing RFQ number before attempting to view an RFQ.

[APP–14546] The approver is not on the approval path for the unapproved requisition

Cause:

You entered an approver who is not on the approval path you specified. The approver must be on the

approval path if USE_POSITIONS_FLAG is ’Y.’

Action:

Enter an approver who is on the approval path you specified.

Action:

Enter an approval path that the approver is on.

[APP–14548] Category or description is missing and cannot be determined

Cause:

You did not enter a item or item description.

Action:

Enter an item or item description.

[APP–14550] The requisition number is in use

Cause:

You entered a requisition number that is in use.

Action:

Enter a unique requisition number.

Cause:

The requisition number that was derived is in use.

Action:

Delete the requisition number.

[APP–14552] Approver is not an active employee.

Cause:

You entered an inactive employee as the approver. The approver must be an active employee if the

requisition is unapproved.

Action:

Enter an active employee as the approver.

Action:

Make the approver an active employee.

[APP–14554] Preparer is not an active employee

Cause:

You entered an inactive employee as the preparer.

Action:

Enter an active employee as the preparer.

Action:

Make the preparer an active employee.

[APP–14556] You have provided insufficient arguments to the Requisition Import program

Cause:

Requisition Import missing arguments.

Action:

Enter the following four arguments: Import Source, Import Batch ID, Group By, Last Requisition

Number

[APP–14558] Accrual account is invalid

Cause:

The accrual account that you entered or that was derived is invalid.

Action:

Enter a valid accrual account.

[APP–14560] An approval path is missing or invalid for the unapproved requisition

Cause:

You entered a missing or invalid approvalpath. A valid approval path is required if

USE_POSITIONS_FLAG is ’Y.’

Action:

Enter a valid approval path.

[APP–14562] Authorization status is missing or invalid

Cause:

You entered a missing or invalid authorization status.

Action:

Enter one of the following authorization statuses: APPROVED, INCOMPLETE, IN PROCESS,

PRE–APPROVED.

[APP–14564] Budget account is invalid

Cause:

The budget account that you entered or that was derived is invalid.

Action:

Enter a valid budget account.

[APP–14566] Category is invalid, or category is invalid for the item

Cause:

You entered an invalid category.

Action:

Enter a valid category.

Cause:

You entered a category that is invalid for the item that you entered.

Action:

Enter a valid category for the item.

[APP–14568] Charge account is invalid

Cause:

The charge account that you entered is invalid.

Action:

Enter a valid charge account.

[APP–14570] Currency selection is invalid

Cause:

You entered an invalid currency code.

Action:

Enter a valid currency code.

[APP–14572] Deliver–to location is invalid

Cause:

You entered a deliver–to location that is invalid for the destination organization.

Action:

Enter a valid deliver–to location for the destination organization.

Cause:

You have not associated a customer with the deliver–to location that you entered. You must

associate a customer with the deliver–to location if the source type is ’INVENTORY’.

Action:

Associate a customer with the deliver–to location that you entered using the Define Location

Associations form in Oracle Purchasing.

[APP–14574] Destination organization is invalid or Receiving Parameters are missing

Cause:

You entered an invalid destination organization.

Action:

Enter a valid destination organization.

[APP–14576] Destination subinventory is not valid

Cause:

You entered a destination subinventory that is invalid for the destination organization.

Action:

Enter a valid destination subinventory for the destination organization.

[APP–14578] Item is not stockable in the destination subinventory

Cause:

You entered an item that is not stockable in the destination subinventory.

Action:

Enter an item that is stockable in the destination subinventory.

Action:

Make the item stockable in the destination subinventory.

[APP–14580] Destination type is invalid

Cause:

You entered an invalid destination type.

Action:

Enter a valid destination type.

[APP–14582] GL date is not in a valid period

Cause:

GL date must be in a valid period if encumbrance is ON

[APP–14584] Hazard class is invalid

Cause:

You entered an invalid hazard class.

Action:

Enter a valid hazard class.

[APP–14586] GL date is not in a valid inventory calendar and open period

Cause:

GL date must be in a valid period inventory calendar and open period for a source type of

’INVENTORY’ if encumbrance is ON.

[APP–14588] Item is not valid for the destination organization

Cause:

You entered an item that is not valid for the destination organization. This is required for a

destination type of ’EXPENSE.’

Action:

Enter an item that is valid for the destination organization.

[APP–14590] Item is missing, invalid or not stock–enabled for the destination organization.

Cause:

You entered an item that is missing, invalid or not stock–enabled for the source organization. This is

required for a destination type of ’INVENTORY.’

Action:

Enter a valid item that is stock–enabled for the source organization.

[APP–14592] Please review item validity

Cause:

You entered an item that is invalid or it is not outside operation/purchasing enabled for the

destination organization. This is required for a destination type of ’SHOP FLOOR.’

Action:

Enter a valid item that is purchasing–enabled and an outside–processing item for the destination

organization.

[APP–14594] Please review item validity

Cause:

You entered an item that is invalid or it is not outside operation/purchasing enabled for the

purchasing organization. This is required for a destination type of ’SHOP FLOOR.’

Action:

Enter a valid item that is purchasing–enabled and an outside–processing item for the purchasing

organization.

[APP–14596] Item is invalid for the purchasing organization

Cause:

You entered an invalid item.

Action:

Enter an item that is valid for the purchasing organization.

[APP–14598] Item not allowed for amount–based line types

Cause:

You entered an item for an amount based line type. Items are not allowed for amount based line

types.

Action:

Delete the item that you entered.

[APP–14600] Revision is invalid for this item

Cause:

You entered an invalid item revision for the item that you specified.

Action:

Enter a valid item revision.

[APP–14602] Item is missing, invalid, or not internally orderable for the destination organization.

Cause:

You entered an item that is missing, invalid or not internal–order enabled for the destination

organization.

Action:

Enter an item that is valid and internal–order enabled for the destination organization.

[APP–14604] Item is missing, invalid, or not internally orderable for the purchasing organization.

Cause

The item is missing, invalid or not internal–order enabled for the purchasing organization. This is

required for a source type of ’INVENTORY’ Action

Enter a valid, internal–order–enabled item for the purchasing organization.

[APP–14606] Item is missing, invalid, or not stock–enabled for the source organization

Cause:

The item is missing, invalid or not stock–enabled for the source organization. The item is required

for a source type of ’INVENTORY’.

Action:

Enter a valid, stock–enabled item for the source organization.

[APP–14608] Item is invalid or not purchasing–enabled for the destination organization

Cause:

You entered an item that is invalid or not purchasing–enabled for the destination organization. This

is required for a source type of ’Supplier’

Action:

Enter a valid item that is purchasing–enabled for the destination organization.

[APP–14610] Item is invalid or not purchasing–enabled for the purchasing organization

Cause:

You entered an item that is invalid or not purchasing–enabled for the purchasing organization. This

is required for a source type of ’Supplier’

Action:

Enter a valid item that is purchasing–enabled for the purchasing organization.

[APP–14612] Line type is invalid

Cause:

You entered an invalid line type

Action:

Enter a valid line type.

[APP–14614] For MRP sourced internal requisitions, the source subinventory must be a

non–nettable subinventory for an intra organization transfer.

Cause:

You tried to perform an intra organization transfer from MRP. You can only do this if the source

subinventory is a non–nettable subinventory.

Action:

Make sure that the source subinventory is a non–nettable subinventory.

[APP–14616] Note is invalid

Cause:

The note that you referenced is invalid.

Action:

Enter a valid note.

[APP–14618] If Oracle Projects is installed and PROJECT_ACCOUNTING_CONTEXT is ’Y’,

then project, task, expenditure type and expenditure organization must be valid

Cause:

The project, task, expenditure type or expenditure organization that you entered is invalid. These

fields are required if the Oracle Projects context is ’Y’.

Action:

Enter a valid project, task, expenditure type and expenditure organization.

[APP–14620] The requestor is not an active employee

Cause:

You entered a requestor who is not a valid employee. Enter: Enter a requestor who is a valid

employee.

[APP–14622] Requisition type is missing or invalid

Cause:

You entered a missing or invalid requisition type.

Action:

Enter a valid requisition type. The requisition type must be one of: PURCHASE, INTERNAL.

Cause:

The requisition type that was derived is invalid.

Action:

Check the source type that you entered.

[APP–14624] Source organization is missing or invalid.

Cause:

The source organization is missing or invalid. The source organization is required if the source type

is ’INVENTORY’.

Action:

Enter a valid source type.

[APP–14626] Source type is invalid

Cause:

You entered an invalid source type.

Action:

Enter a valid source type.

[APP–14628] Source subinventory is not valid

Cause:

You entered a source subinventory that is invalid for the source organization.

Action:

Enter a valid source subinventory for the source organization.

[APP–14630] Item is not stockable in the source subinventory

Cause:

You entered an item that is not stockable in the source subinventory that you entered.

Action:

Enter an item that is valid in the source subinventory that you entered.

Action:

Make the item valid in the source subinventory that you entered.

[APP–14632] The suggested buyer is not a valid buyer or employee

Cause:

You entered an invalid buyer.

Action:

Enter a valid buyer.

[APP–14634] UN number is invalid

Cause:

You entered an invalid UN number.

Action:

Enter a valid UN number.

[APP–14636] The USSGL Transaction Code is invalid

Cause:

You entered an invalid USSGL Transaction Code.

Action:

Enter a valid USSGL transaction code.

[APP–14638] Variance account is invalid

Cause:

The variance account that you entered or that was derived is invalid.

Action:

Enter a valid variance account.

[APP–14640] For direct transfers, you cannot transfer an asset item from an expense subinventory to

an asset subinventory

[APP–14642] For intransit transfers, you cannot transfer an asset item out from an expense

subinventory

[APP–14644] For direct transfers, you cannot transfer items to a destination organization that has

tighter revision, lot or serial control than the source organization for that item

[APP–14646] For intransit transfers, you cannot transfer items to a destination organization that has

tighter revision control than the source organization for that item

[APP–14648] Item description problem

Cause:

The item description that you entered does not match the description of the item and update of the

item description is not allowed for the item.

Action:

Enter the correct item description.

[APP–14650] You cannot provide a revision without an item

Cause:

You entered an item revision without entering an item.

Action:

Enter a valid item and item revision.

[APP–14652] Destination type must be ’SHOP FLOOR’ for an outside operation line

Cause:

You entered an invalid line type. You must enter an outside–operation line type for a destination

type of ’SHOP FLOOR’.

Action:

Enter an outside operation line type.

Action:

Enter a destination type of ’SHOP FLOOR’.

[APP–14654] Item must be of type ’OUTSIDE OPERATION’ for an outside operation line

Cause:

You entered an invalid item for the line type that you entered. You must enter a outside–operation

item if you enter an outside–operation line type.

Action:

Enter an outside–operation item.

[APP–14656] Source type must be ’INVENTORY’ for an outside operation line

Cause:

You entered an invalid line type. You cannot enter an outside–operation line type if you enter a

source type of ’INVENTORY’.

Action:

Enter a line type which is not an outside–operation line type.

[APP–14658] Need–by date is missing or invalid for MRP or Inventory planned item

Cause:

You did not enter a need by date. A need by date is required if the item that you entered is either an

MRP or Inventory planned item.

Action:

Enter a need by date.

[APP–14660] Please review your foreign currency exchange rate, rate type and rate date

Cause:

Either the foreign currency exchange rate type is invalid, or the rate or rate date is missing.

Action:

Enter a valid currency rate type, rate and rate date.

[APP–14662] Unit of measure is invalid

Cause:

The Unit of Measure that you entered or that was derived is invalid.

Action:

Enter a valid Unit of Measure for the item.

Action:

Check the item that you entered.

[APP–14664] Inter–organization transfers are not defined for this combination of source and

destination organizations

[APP–14666] Preparer is not an on–line user

Cause:

The preparer must be an on–line user if the requisition is unapproved.

Action:

Make the preparer an on–line user.

Action:

Enter a preparer who is also an on–line user.

[APP–14668] Please enter a quantity greater than zero (0)

Cause:

You entered a quantity that was either missing or less than 0.

Action:

Enter a non–zero quantity.

[APP–14670] The source subinventory is not quantity–tracked

[APP–14672] The source subinventory is not a reservable subinventory. This is required if

reservations are ON in Order Entry.

[APP–14674] Some unit of measure conversions are not defined

Cause:

Some unit

[APP–14676] Please enter a unit price greater than or equal to zero (0)

Cause:

You entered a price that is either missing or less than 0.

Action:

Enter a price that is greater than or equal to 0.

[APP–14678] Must be a valid repetitive schedule or discrete job if WIP is installed

Cause:

The WIP entity that you entered must be a valid repetitive schedule or a valid discrete job.

Action:

Enter a valid repetitive schedule or a valid discrete job.

[APP–14680] The suggested rounded quantity is &PO_RND_ADVISORY1

Cause:

The quantity rounding routine has determined that a quantity of &PO_RND_ADVISORY1 would be

beneficial.

Action:

No action required.

[APP–14682] Unit of measure conversion failed

Cause:

Unit of measure conversion is not defined for the requisition line unit of measure and item unit of

issue.

Action:

Define the unit of measure conversion.

[APP–14684] A rounding factor has not been defined for this item

Cause:

A rounding factor has not been defined this item.

Action:

Define a rounding factor for the item.

[APP–14686] UOM Rounding User Exit failed

Cause:

The Unit of Measure Quantity Rounding routine was unable to place the rounded value into the

quantity field.

Action:

Note error number and the action you are attempting to perform. Contact your system administrator

for assistance.

[APP–14688] Please enter a valid date

Cause:

You entered an invalid date.

Action:

Enter a date that is a valid calendar date.

[APP–14690] You cannot add new lines to a complete requisition

Cause:

You are trying to change a saved requisition that has been submitted to the approval process. You

can no longer change this requisition.

Action:

Use the Enter Requisitions form to create a new requisition for the additional items you need.

[APP–14692] You cannot change a complete requisition

Cause:

You are trying to change a saved requisition that has been submitted to the approval process. You

can no longer change this requisition.

Action:

Use the Enter Requisitions form to create a new requisition for the additional items you need.

[APP–14694] This document is not updateable.

Cause: You have tried to update a document that is currently not updateable.

Action: No action required.

[APP–14696] Please enter an account for this distribution

Cause:

You have not entered an account into the accounting flexfield to which this distribution will be

charged.

Action:

Enter an account into the accounting flexfield.

[APP–14698] Concurrent process failed. Interface table not imported

Cause:

Oracle Purchasing could not submit the Requisitions Import process you requested to the Concurrent

Manager. There may be no Concurrent Manager presently running.

Action:

Note both your concurrent request ID and this error number. Contact your system administrator for

assistance.

[APP–14700] Destination location sourced from Inventory must be linked to customer

Cause:

Inventory sourced requisition lines require the destination location to be associated with an Order

Entry customer and site.

Action:

Associate the deliver to location with an Oracle Entry customer and site.

[APP–14702] The inventory source details are invalid for the item

Cause:

You attempted to create a requisition line with a source organization and subinventory that is not

allowed for the item entered. The item must be stockable in the source organization. The item must

be defined for the source subinventory.

Action:

Modify the source organization and subinventory to a combination that is valid for the item.

[APP–14704] You cannot source from an expense subinventory

Cause:

You selected a expense subinventory as your source subinventory, and your destination is an asset

subinventory. You cannot transfer an asset item from an expense subinventory to an asset

subinventory using internal requisitions. Intransit is also consider an asset, so you cannot source an

asset item from an expense subinventory if you are using intransit.

Action:

Choose an asset subinventory to complete your requisition or modify your item, organization

network, or subinventory setup options.

[APP–14706] Direct transfers not allowed between these organizations for this item

Cause:

You cannot transfer this item directly between the source and destination organization. You cannot

transfer an item that from an organization under looser item revision, lot or serial control, to an

organization with stricter control.

Action:

Choose a different source organization for your transfer or modify your organization setup and

controls to allow transfers between these two organizations.

[APP–14708] Cannot find primary destination subinventory

Cause:

You are trying to create a internal requisition for a direct inventory transfer, and you have not

specified a destination subinventory. You did not setup a primary subinventory for your item, so

you must specify a destination organization in this form if you want to transfer this item directly

between two organizations.

Action:

Choose an source organization that uses in–transit, or specify a destination subinventory in the

destination field.

[APP–14710] You may not enter identical destination and source organizations

Cause:

You tried to create an internal requisition using identical destination and source inventory

organizations.

Action:

Modify either your destination or source inventory information.

[APP–14712] Please enter the necessary line information .

Cause: You attempted to create a distribution without creating a parent line.

Action: Please enter all the required line information before attempting to create a distribution

for it.

[APP–14714] This line number does not exist for the selected requisition

Cause:

You are trying to review requisition line information for a requisition that does not have a line

matching your line number.

Action:

No action is required.

[APP–14716] You cannot un–cancel a canceled requisition line

Cause:

You are trying to un–cancel a requisition line. You cannot un–cancel requisition lines after you

cancel them.

Action:

Use the Enter Requisitions form to re–create the cancelled requisition line on a new requisition line.

[APP–14718] This line is not updateable.

Cause: You have tried to update a line that is not updateable.

Action: Please create new lines which are modified versions of the current line.

[APP–14720] You cannot source from the destination organization for planned items

Cause:

You tried to create an internal requisition using identical destination and source organizations.

Action:

Modify either your destination or source inventory information.

[APP–14722] There are multiple disposition messages for this item. Open the Define Item

Cross–References form to view them.

[APP–14724] The need–by date must be greater than or equal to requisition date

Cause:

You have entered a need–by date that is earlier than the requisition creation date. You cannot

request items for delivery in the past.

Action:

Enter a need–by date that is greater than or equal to the requisition creation date.

[APP–14726] The inventory source details do not include a source organization

Cause:

You tried to create an internal requisition line without a source organization.

Action:

Enter a source organization.

[APP–14728] There are no requisition lines for this purchase order line

Cause:

You are trying to review the requisition lines associated with a purchase order line, and you did not

create this purchase order line from an on–line requisition.

Action:

No action is required.

Action:

If you created this purchase order line from a paper requisition, you can review the requisition

number you entered by navigating to the distributions zone of the View Purchase Orders or Enter

Purchase Orders forms.

[APP–14730] Please enter a destination organization.

Cause: You attempted to enter outside processing information without providing a destination

organization.

Action: Please provide a destination organization.

[APP–14732] WARNING: Blanket purchase order &PO_NUM exists for this item

Cause:

A blanket purchase order already exists for this item.

Action:

You may want to review the details of the blanket purchase order instead of continuing with this

document.

[APP–14734] Unable to reschedule requisitions

Cause:

Submission of the requisition rescheduling process to the Concurrent Manager failed.

Action:

Note both this error number and the actions you were trying to perform. Contact your system

administrator for assistance.

[APP–14736] You cannot source from and deliver to the same subinventories.

Cause:

Your source organization and subinventory is identical to your destination organization and

subinventory.

Action:

Modify either your source or destination subinventories.

[APP–14738] You cannot un–cancel a canceled requisition

Cause:

You are trying to un–cancel a cancelled requisition.

Action:

Use the Enter Requisitions form to re–create the requisition.

[APP–14740] You cannot open a finally closed requisition

Cause:

You are trying to open a finally closed requisition. You cannot open a requisition after you have

finally closed the requisition.

Action:

Use the Enter Requisitions form to enter a new requisition.

[APP–14742] Item not valid for original line’s destination organization and subinventory

Cause:

The selected item is not valid for the original line’s destination organization and subinventory.

Action:

Select another item.

[APP–14744] You must cancel a complete requisition

Cause:

You are trying to delete a complete requisition. You cannot delete a complete requisition from the

database.

Action:

Use the Control Requisitions form to cancel your requisition.

[APP–14746] You must cancel lines on a complete requisition

Cause:

You are trying to delete lines from a complete requisition. You cannot delete a requisition line from

the database.

Action:

Use the Control Requisitions form to cancel your requisition lines.

[APP–14748] Express receiving failed

Cause:

You are trying to express receive incomplete shipments.

Action:

Enter the receipts individually for each purchase order line.

[APP–14750] Please enter a valid date range

Cause:

You tried to enter a date range with a lower bound that is later than your upper bound.

Action:

Enter a date range with a lower bound that is earlier than an upper bound.

[APP–14752] Cannot delete a control group that is assigned to a position or job

Cause:

You attempted to delete a control group that is assigned to a position or a job.

Action:

Unassign or inactivate the control group for all positions and jobs before attempting to delete the

control group.

[APP–14754] Both the source document and your purchase order are in foreign currency

&SELECTION_CURRENCY. The price will be copied to your purchase order as

&CURRENCY_PRICE; verify that this price is correct for the purchase order exchange rate.

[APP–14756] You have selected a price that is in foreign currency &SELECTION_CURRENCY

and your purchase order is in functional currency &PO_CURRENCY. The price will be converted to

functional currency using the source document’s rate information. OK to continue?

[APP–14758] You have selected a price that is in &SELECTION_CURRENCY and your purchase

order is in &PO_CURRENCY. It is not possible to convert from &SELECTION_CURRENCY to

&PO_CURRENCY. Do you want to:

[APP–14760] Split percentage total must be less than or equal to one hundred

Cause:

You attempt to increase the business split percentage for all suppliers to a value greater than 100

percent.

Action:

Enter split percentages for each supplier so the sum of all suppliers is less than or equal to 100

percent.

[APP–14762] Unable to get next automatic purchase order number

Cause:

Oracle Purchasing was unable to retrieve the next automatic purchase order number from the

database.

Action:

Note this error number and contact your system administrator for assistance.

[APP–14764] Unable to get next automatic quotation number

Cause:

Oracle Purchasing was unable to retrieve the next automatic RFQ number from the database.

Action:

Note this error number and contact your system administrator for assistance.

[APP–14766] Unable to get next automatic receipt number

Cause:

Oracle Purchasing was unable to retrieve the next automatic receipt number from the database.

Action:

Note this error number and contact your system administrator for assistance.

[APP–14768] Unable to get next automatic requisition number

Cause:

Oracle Purchasing was unable to retrieve the next automatic requisition number from the database

Action:

Note this error number and contact your system administrator for assistance.

[APP–14770] Unable to get next automatic RFQ number

Cause:

Oracle Purchasing was unable to retrieve the next automatic RFQ number from the database.

Action:

Note this error number and contact your system administrator for assistance.

[APP–14772] Only one row is allowed in the System Parameters form

Cause:

There is only one set of default values in the system. You cannot enter two sets of system

parameters.

Action:

No action required.

[APP–14774] Number type cannot be numeric. Alphanumeric numbers already exist

Cause:

You attempted to define the document number type as NUMERIC. This is not possible because

documents with alphanumeric numbers already exist.

Action:

Select the alphanumeric document number type using \ Field QuickPick or make all existing

document numbers numeric.

[APP–14776] Please copy only one shipment

Cause:

You are trying to copy more than one shipment.

Action:

If you want to copy this shipment, first enter ’No’ for the first shipment you selected and then enter

’Yes’ for this shipment.

[APP–14778] The quotation and purchase order currencies are different

Cause:

You have chosen a quotation shipment that has different currency information than the purchase

order header.

Action:

Choose ’No’ for Copy if you no longer want to copy the quotation information.

[APP–14780] You must specify an item or item category to source items

Cause:

You are trying to view item sourcing information and you have not entered an item number or an

item category.

Action:

Enter the item number or item class of the item you want to source.

[APP–14782] The quotation and requisition currencies are different

Cause:

You have chosen a quotation shipment that has different currency information than the requisition

line.

Action:

Choose ’No’ for Copy if you no longer want to copy the quotation information.

[APP–14784] The quotation and purchase order supplier sites are different

Cause:

You have chosen a quotation shipment that has a different supplier site than the purchase order

header.

Action:

Choose ’No’ for Copy if you no longer want to copy the quotation information

[APP–14786] The quotation and purchase order terms and conditions are different

Cause:

You have chosen a quotation shipment that has different terms and conditions than the purchase

order header.

Action:

Choose ’No’ for Copy if you no longer want to copy the quotation information

[APP–14788] Verify your system currency and set of books information

Cause:

The currency codes or set of books details are not setup properly in your system.

Action:

Verify that your system setup has been completed correctly.

[APP–14790] This supplier site has no contacts

Cause:

There are no contacts for this supplier site.

Action:

No action is required.

[APP–14792] This supplier has no sites

Cause:

There are no sites for this supplier.

Action:

No action is required.

[APP–14794] You cannot update the item category for a pre–defined item

Cause:

You tried to update the item category for a pre–defined item.

Action:

No action is required.

[APP–14796] This job or schedule has been closed

Cause:

You tried to receive outside processing items for a job or schedule that has been closed.

Action:

Open the corresponding job or schedule within Oracle Work In Process.

[APP–14798] Purchase order receipt date tolerance exceeded

Cause:

The receipt you are trying to transact exceeds the days early or late tolerance.

Action:

Return the shipment to the supplier if you think it is necessary.

Action:

Modify the receiving controls setup at the purchase order shipment, item, or organization level so

that you allow receipts exceed days early or late tolerance.

[APP–14800] The receiving and ship–to locations do not match

Cause:

The receiving location that you entered does not match the ship–to location you entered on the

purchase order.

Action:

Receive the goods at the same ship–to location you entered on the purchase order.

Action:

Return the shipment to the supplier if you think this is necessary.

Action:

Modify the receiving controls to allow you to receive goods at an alternate receiving location.

[APP–14802] A duplicate locator exists for another subinventory

Cause:

The locator that you specified for the subinventory is also specified for another subinventory within

the same organization.

Action:

Enter a different locator.

[APP–14804] Please enter a deliver–to location

Cause:

You are delivering goods to an expense destination without providing a deliver to location.

Action:

Enter a deliver to location.

[APP–14806] Lot number quantities do not match the transaction quantity

Cause:

The lot number quantity does not match the transaction quantity.

Action:

Change your lot or transaction quantity so that they are the same.

[APP–14808] Serial number quantities do not match the transaction quantity

Cause:

You did not enter the correct number of serial numbers for your transaction quantity

Action:

Adjust your transaction quantity or your serial numbers

[APP–14810] Please enter a transfer–to location

Cause:

You attempted to transfer goods from one receiving location to another without providing a transfer

to location.

Action:

Enter a transfer to location.

[APP–14812] Please enter a transaction date within an open accounting period

Cause:

You tried to enter a transaction date in a closed Purchasing accounting period.

Action:

Enter a transaction date that falls within an open Purchasing accounting period.

Action:

Open the closed Purchasing accounting period in which you’d like to perform this transaction.

[APP–14814] Quantity &QTY_A is greater than &QTY_B, quantity ordered plus tolerance

Cause:

Quantity you want to receive plus quantity already received is greater than quantity ordered plus the

over receipt tolerance.

Action:

Either reduce the quantity to receive, increase your quantity received tolerance, or change your

quantity received exception code.

[APP–14816] Please enter a valid locator combination

Cause:

You attempted to process the receiving transaction without a locator.

Action:

Enter a locator.

[APP–14818] Serial control requires an integral transaction quantity

Cause:

Transaction quantity does not convert to whole number of units in the primary unit of measure.

Action:

Enter another unit of measure or quantity.

[APP–14820] You cannot update receipt header with a missing receipt number

Cause:

You tried to update the receipt header information without specifying a receipt number for this

shipment.

Action:

Navigate to the lines block and specify a receipt number for this shipment.

[APP–14822] Supplier on this PO shipment does not match supplier on receipt

Cause:

This purchase order shipment has a different supplier than you specified on this receipt.

Action:

Create a separate receipt for this suplier, or omit the purchase order shipment from the current

receipt.

[APP–14824] You cannot enter a receipt date that is earlier than shipment date

Cause:

You enter a receipt date that is earlier than the shipped date.

Action:

Modify the receipt date to be greater than or equal to the shipped date on the shipment header.

[APP–14826] Please enter an expiration date

Cause:

This item requires a lot expiration date

Action:

Enter a lot expiration date

[APP–14828] Lot number is already used by another item

Cause:

This lot number is already used by another item. Your lot number uniqueness controls do not allow

you to assign this lot number to a different item

Action:

Remove this lot number

[APP–14830] You have not supplied enough data to match to a purchase order

Cause:

You tried to match an unordered receipt to a purchase order without providing enough information.

Action:

Please specify a valid purchase order number, line, release (if applicable), and shipment.

[APP–14832] The unordered item cannot be matched to this purchase order shipment

Cause:

The routing control on this purchase order is direct delivery. You can only match an unordered item

to a Purchase Order shipment that has standard receipt routing or no routing specified.

Action:

Match the unordered item to another Purchase Order or change the system level profile RCV:Allow

routing override to yes.

[APP–14834] Next automatic receipt number is not unique

Cause:

Your next automatic receipt number is not unique. You must enter a unique receipt number each

time you create a receipt, and your next automatic value already exists on another receipt.

Action:

Do not commit this transaction. Use Screen Erase to clear the transaction and then contact your

System Administrator to reset the Next Automatic Receipt Number using the Define Purchasing

Options form.

[APP–14836] You cannot update an existing receipt header

Cause:

You cannot update an existing receipt header.

Action:

Enter a new receipt header.

[APP–14838] You cannot clear or delete this record

Cause:

You attempted to clear or delete the receiving options record. You cannot delete a record from the

Receiving Parameters Form.

Action:

No action required.

[APP–14840] Please enter a number of days greater than or equal to zero (0)

Cause:

You tried to enter a negative number for number of days.

Action:

Enter a number for number of days that is greater than or equal to zero (0)

[APP–14842] A row exists for the receiving parameters in this organization

Cause:

You tried to enter more than one row of receiving parameters for this organization.

Action:

No action is required.

[APP–14844] Please enter a percentage that is greater than or equal to zero (0)

Cause:

You have entered a negative percentage.

Action:

Enter a percentage that is greater than or equal to zero (0)

[APP–14846] Serial number is already used in another organization

Cause:

This record contains serial numbers that are already used in another organization and this breaks the

uniqueness constraint across organizations. Your serial uniqueness controls do not allow this

Action:

Remove the duplicate serial numbers

[APP–14848] Serial number is already used by another unit of this item

Cause:

This record contains serial numbers that are already used by another unit of this item. Your serial

number uniqueness controls do not allow you to enter the same serial numbers again

Action:

Remove the duplicate serial numbers

[APP–14850] Serial number is already used in this organization

Cause:

This record contains serial numbers that are already used by another unit in this organization. Your

serial uniqueness controls do not allow you to enter the same serial numbers again

Action:

Remove the duplicate serial numbers

[APP–14852] Serial number is already used in the system

Cause:

This record contains serial numbers that are already used in the system. Your serial uniqueness

controls do not allow you to enter the same serial numbers again

Action:

Remove the duplicate serial numbers

[APP–14854] Your transaction date must be within an open accounting period

Cause:

You submitted a receiving transaction with a transaction date that does not fall within an open

accounting period.

Action:

Re–enter the transaction using a transaction date that falls within an open accounting period, or

open the accounting period for your transaction date.

[APP–14856] Invalid Auto–Transact Code

Cause: The transaction has an invalid auto–transact code. Explanation: Valid values are: SHIP,

RECEIVE, DELIVER

[APP–14858] Invalid Destination Type

Cause: The destination type on the transaction is invalid Explanation: Valid Values: EXPENSE,

INVENTORY, SHOP FLOOR

[APP–14860] You cannot receive against a &PO_TYPE purchase order

Cause:

You submitted a receiving transaction that corresponds to a purchase order type against which you

cannot receive.

Action:

If your transaction was created by a Receiving form, contact your system administrator for

assistance. If your transaction was loaded from an external system, please correct the source

transaction and re–load the interface table.

[APP–14862] Transaction quantity exceeds available quantity

Cause:

The transaction quantity exceeded the quantity available to be processed.

Action:

Enter the transaction using a smaller quantity.

[APP–14864] Invalid Receipt Source Type

Cause: Transaction has an invalid receipt source code Explanation: Valid values are:

VENDOR,INVENTORY, INTERNAL

[APP–14866] An invalid source document type was processed

Cause:

You submitted a receiving transaction that corresponds to source document type against which you

cannot receive.

Action:

If your transaction was created by a Receiving form, contact your system administrator for

assistance. If your transaction was loaded from an external system, please correct the source

transaction and re–load the interface table.

[APP–14868] Invalid transaction type

Cause:

The receiving transaction that you are processing has an invalid transaction type.

Action:

If the transaction was submitted by a Receiving form, contact your system administrator for

assistance. If your transaction was imported into the receiving interface tables manually, correct the

transaction type and re–submit the transaction for processing.

[APP–14870] You cannot return items from stores via Receiving & Inspection

Cause:

You attempted to return items to stores that were shipped in response to an internal order or as part

of an in–transit shipment. You can only return items to Receiving & Inspection if they were ordered

from a supplier.

Action:

If you need to return return items to the source organization or subinventory, you must issue a

subinventory transfer using Oracle Inventory.

[APP–14872] Interface transaction id or group id is missing

Cause:

You cannot process your receiving transaction due to interface transaction id or group id missing.

Action:

Contact your system administrator.

[APP–14874] Your transaction date is earlier than its parent transaction

Cause:

You tried to enter a transaction date that is earlier than the parent transaction date.

Action:

Enter a transaction date that is later than or equal to the parent transaction date.

[APP–14876] Please reduce your delivery quantity

Cause:

The sum of the delivery quantities in this zone exceeds the corresponding delivery quantity in the

transactions zone.

Action:

Reduce your deliver quantity such that the sum of the delivery quantities in this zone are less than or

equal to the corresponding delivery quantity in the transactions zone.

[APP–14878] Child transaction date pre–dates parent transaction date

Cause:

You tried to enter a child transaction date that is earlier than the corresponding parent transaction

date.

Action:

Enter a transaction date that is equal to or later than the transaction date of the corresponding parent

transaction.

[APP–14880] Express transaction failed

Cause:

Express transaction failed.

Action:

Enter the transactions individually.

Action:

Contact your system administrator for assistance.

[APP–14882] Please enter a transaction date that is not in the future

Cause:

You attempted to enter a transaction date that is in the future.

Action:

Enter a date less than or equal to current date.

[APP–14884] Please reduce your accept or reject quantity

Cause:

The sum of the individual accept and reject quantities in this zone exceeds the corresponding

inspect quantity in the transactions zone.

Action:

Reduce your accept or reject quantity.

[APP–14886] Please enter a quantity less than or equal to the available quantity

Cause:

The transaction quantity exceeds the quantity available to be processed.

Action:

Enter the transaction using a smaller quantity.

[APP–14888] Primary quantity &PRIMARY exceeds available subinventory quantity &SUB

Cause:

The transaction quantity &PRIMARY in primary unit of measure exceeds the available quantity

&SUB in the subinventory.

Action:

Enter a smaller quantity.

[APP–14890] &DOC_TYPE &DOC_NUMBER has been rejected by approver. Make the necessary

changes and resubmit for approval.

[APP–14892] Requisition &DOC_NUMBER has been rejected by buyer. Make the necessary

changes and resubmit for approval.

[APP–14894] &DOC_TYPE &DOC_NUMBER has not been completed. Open the entry form for

this document to complete it.

[APP–14896] &DOC_TYPE &DOC_NUMBER requires re–approval.

[APP–14897] VAT Registration Number is not unique.

[APP–14898] VAT Registration Number is invalid.

[APP–14899] Fiscal Code entered is not unique.

[APP–14900] Fiscal Code is not valid.

[APP–14999] No support for Lot and Serial functionality in this release.

[APP–15091] &BALANCE of this invoice was applied to commitment &COMMITMENT

[APP–15095] &STATUS &COUNT row(s) marked with: Accounting rule specified when

distribution records exist

[APP–15097] &STATUS Line level revenue account was specified when distribution records exist

[APP–15099] &STATUS GL date at the line does not match GL date at the header

[APP–15103] Transaction type must be an open receivable on invoice of a commitment

[APP–15105] Invoice type receivable flag is different from Credit Memo type flag

[APP–15106] Warning: Postable flag is different on invoice and commitment types

[APP–15108] Enter a date that is not in a closed period

[APP–15109] Control amount must be greater than actual amount

[APP–15110] Invoice batch source has no credit memo numbering source

[APP–15111] Please complete the revenue account for line &LINE_NUM &DESC

[APP–15112] You cannot update a record that has been processed

[APP–15113] Revenue accounts for this invoice line are not recalculated

Cause:

AutoAccounting link has been broken or revenue acco

[APP–15114] Recalculating the revenue accounts for &SREP

[APP–15115] Recalculating the revenue accounts for &SREP in line &LINE

[APP–15116] Invoice exceeds the balance of the commitment. Balance: &BALANCE

[APP–15117] No revenue account assignments are associated with this salesperson

[APP–15119] Please enter old customer name and new customer name

[APP–15120] Please enter customer name and customer number

[APP–15121] You cannot insert new records

[APP–15122] You cannot merge a customer with itself

[APP–15123] You cannot merge or move a site to itself

[APP–15124] A transaction must have at least one line

[APP–15125] Tax code already exists. Please enter a different value

[APP–15126] This function is disabled

[APP–15127] Credit Memos and Commitments cannot be recurred. Choose another

[APP–15128] Percent cannot exceed 100. Please enter a different value

[APP–15133] Credit memo type field is mandatory when class is invoice

[APP–15134] Rule name already exists. Please enter a different value

[APP–15135] Use \ Navigate Invoice Maintain Statuses to void invoice

[APP–15136] You cannot query records with this form

[APP–15139] Salesperson number already exists. Please enter a different value

[APP–15141] You cannot delete a customer contact telephone

[APP–15142] You cannot delete a customer business purpose

[APP–15143] You cannot delete a customer telephone

[APP–15144] Payment term name already exists. Please enter a different value

[APP–15145] You cannot delete a customer contact

[APP–15146] You cannot delete a customer address

[APP–15147] Please correct the freight account assignment

[APP–15148] Please correct the revenue account assignment

[APP–15149] High range must have a value. The default value is ALL

[APP–15150] Low range must have a value. The default value is ALL

[APP–15151] Use \ Screen Save to start invoice and credit memo printing routine

[APP–15152] Unable to run report

[APP–15153] There is no rate for this date and rate type

[APP–15154] Length cannot be less than zero

[APP–15155] You cannot query in this zone

[APP–15156] At last recurring invoice

[APP–15157] Warning: unposted GL distributions exist for this period

[APP–15158] You cannot close this period because it has unposted invoices

[APP–15159] Lookup type already exists. Please enter a different value

[APP–15160] You cannot update permanently closed periods

[APP–15161] You cannot update the status of a permanently closed period

[APP–15162] Warning: ending postal code cannot be less than starting postal code

[APP–15163] Starting postal code cannot be greater than ending postal code

[APP–15164] Warning: postal code is not in the specified state

[APP–15165] Days cannot be less than zero

[APP–15166] You must specify the corresponding month for the day

[APP–15167] You cannot update a posted invoice

[APP–15168] Percent cannot be less than zero

[APP–15169] Please enter all dates

[APP–15170] Please enter a valid type

[APP–15171] Warning: selling price is below cost

[APP–15172] Error generating batch name

[APP–15174] Customer reference has two different customer class codes defined

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same customer, are marked identically for insert or update but have different customer class codes

defined.

Action:

Update the customer class code of all records referencing this customer to be the same.

[APP–15176] This customer reference has two different parent customer references

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same customer, are marked identically for insert or update but have different parent customer

references.

Action:

Update the parent customer references of all records referencing this customer to be the same.

[APP–15177] This customer reference has two different customer numbers defined

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same customer, are marked identically for insert or update but have different customer numbers.

Action:

Update the customer numbers of all records referencing this customer to be the same.

[APP–15178] This customer reference has two different customer names defined

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same customer, are marked identically for insert or update but have different customer names.

Action:

Update the customer names of all records referencing this customer to be the same.

[APP–15179] SITE_USE_CODE is not defined in AR_LOOKUPS

Cause:

The SITE_USE_CODE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

SITE_USE_CODE.

Action:

Enter a SITE_USE_CODE defined in AR_LOOKUPS or use the Define QuickCodes form to define

a new one.

[APP–15180] COUNTRY is not defined in fnd_territories

Cause:

COUNTRY must be defined in fnd_territories.

Action:

Enter a COUNTRY defined in fnd_territories.

[APP–15181] STATE is not defined in AR_LOCATION_VALUES

Cause:

STATE must be defined in AR_LOCATION_VALUES.

Action:

Enter a STATE defined in AR_LOCATION_VALUES.

[APP–15182] CUSTOMER_PROFILE_CLASS_NAME has an invalid value

Cause:

The customer profile class name is not defined.

Action:

Use the Customer Profile Classes Window to define a new profile class or specify an existing one.

[APP–15183] CUSTOMER_CLASS_CODE is not defined in AR_LOOKUPS

Cause:

The CUSTOMER_CLASS_CODE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

’CUSTOMER CLASS’.

Action:

Use the Define Quickcodes form to define a new customer class or change the value to an existing

customer class.

[APP–15184] Error submitting concurrent request

[APP–15185] PRIMARY_SITE_USE_FLAG is mandatory when inserting an address

Cause:

The PRIMARY_SITE_USE_FLAG must be populated when inserting an address.

Action:

Enter a value into the PRIMARY_SITE_USE_FLAG field.

[APP–15186] SITE_USE_CODE is mandatory when inserting an address

Cause:

The SITE_USE_CODE field is mandatory when inserting an address.

Action:

Enter a value into the SITE_USE_CODE field.

[APP–15187] COUNTRY is mandatory when specifying an address

Cause:

The COUNTRY field is a mandatory field when specifying an address.

Action:

Enter a value into the COUNTRY field.

[APP–15188] ADDRESS1 is mandatory when specifying an address

Cause:

The ADDRESS1 field is a mandatory field when specifying an address.

Action:

Enter a value into the ADDRESS1 field.

[APP–15189] ORIG_SYSTEM_ADDRESS_REF is mandatory when specifying an address

Cause:

To identify an existing or new address requires an ORIG_SYSTEM_ADDRESS_REF.

Action:

Enter an ORIG_SYSTEM_ADDRESS_REF.

[APP–15190] Site use for this address reference already exists in the database

Cause:

When inserting an address and site use the site use for the address reference must not exist.

Action:

Specify an address and site use that do not exist.

[APP–15191] Customer reference for insert is already defined in RA_CUSTOMERS

Cause:

When inserting a customer the customer reference specified must not exist in RA_CUSTOMERS.

Action:

Specify a customer reference that does not exist.

[APP–15192] The address reference for update does not exist in RA_ADDRESSES

Cause:

When updating an address record the address reference specified must exist in RA_ADDRESSES.

Action:

Specify an address reference that exists in RA_ADDRESSES.

[APP–15193] The customer reference for update does not exist in RA_CUSTOMERS

Cause:

When updating a customer record the customer reference specified must exist in

RA_CUSTOMERS.

Action:

Specify a customer reference that exists in RA_CUSTOMERS.

[APP–15195] Error retrieving invoice distribution line numbers

[APP–15196] This type is non–postable

[APP–15198] You cannot enter a date prior to the invoice date

[APP–15201] You cannot clear a queried record

[APP–15205] This line has been saved. Use \ Row Delete to remove it

[APP–15206] Error retrieving manual–other batch source recorded

[APP–15207] Warning: salesperson information will be updated

[APP–15210] Data corrupted. Call support

[APP–15217] Error retrieving payment term line information

[APP–15222] Please enter an invoice number

[APP–15225] Invoices exist against this commitment; you cannot delete it

[APP–15226] This primary salesperson has no territory

[APP–15227] Press any key to continue

[APP–15228] Error retrieving line numbers for line salesperson

[APP–15229] Control count must be greater than actual count

[APP–15230] You cannot update status for this type

[APP–15231] Complete or erase necessary information before going to next record

[APP–15232] Due percent cannot be less than discount percent

[APP–15233] Please erase this field before going to the next field

[APP–15234] Please enter a payment term line for this payment term

[APP–15235] You cannot view variable duration rule schedule

[APP–15236] You cannot run RA posting when Cash Basis Accounting defined in AR

[APP–15237] &STATUS Neither negative dollar invoice nor zero dollar credit memo is allowed

[APP–15238] &STATUS Duplicate bill to site uses

[APP–15239] &STATUS Credit amount greater than balance due

[APP–15240] &STATUS Failed due to Oracle error

[APP–15242] &STATUS You cannot supply invoicing and accounting rules when you supply gl date

or on account credit memo

[APP–15243] &STATUS Invalid exchange rate data

[APP–15244] &STATUS &COUNT row(s) marked with: Same order twice within a batch

[APP–15245] &STATUS Invalid customer trx type id

[APP–15246] &STATUS Invalid bill to address reference

[APP–15247] &STATUS Invalid tax data

[APP–15248] &STATUS Invalid remit to data

[APP–15249] &STATUS Invalid batch source

[APP–15250] &STATUS Invalid previous number or previous order id

[APP–15251] &STATUS Invalid primary salesrep code

[APP–15252] &STATUS Invalid contact id

[APP–15253] &STATUS trx_number already used, or no auto–numbering and no trx_number

[APP–15254] &STATUS Invalid or null salesrep code

[APP–15255] &STATUS Line credits do not add up to revenue amount or 100 percent

[APP–15256] &STATUS Line and header credits not allowed

[APP–15257] &STATUS Header credits do not add up to revenue amount or 100 percent

[APP–15258] &STATUS Percent and Amount credits not allowed for the same order

[APP–15259] &STATUS Incorrect tax code, tax rate or tax amount

[APP–15261] &STATUS Either the deposit or guarantee referenced does not exist or the

commitment balance is negative

[APP–15262] &STATUS &COUNT row(s) marked with: Inconsistent accounting rule duration

[APP–15263] &STATUS Duplicate ship to site uses

[APP–15264] &STATUS Null line description

[APP–15265] &STATUS Invalid accounting rule duration for given accounting rule

[APP–15268] &STATUS &COUNT row(s) marked with: Same order line and shipment within a

batch

[APP–15269] &STATUS Invalid term id

[APP–15270] &STATUS &COUNT row(s) marked with: Inconsistent data with the same

orig_system_reference

[APP–15271] &STATUS Invalid previous order id or previous order line id

[APP–15272] &STATUS Invalid invoicing or accounting rules

[APP–15273] &STATUS Invalid ship to references

[APP–15274] &STATUS Non–matching lines and revenue data

[APP–15275] Field must be entered

[APP–15276] Adjustment made –– you cannot credit more than the tax remaining

[APP–15277] Code already exists for this type. Please enter a different value

[APP–15278] You are at the last line

[APP–15279] At first field

[APP–15280] Part number is not defined. Please enter a different value

[APP–15281] Part number already exists. Please enter a different value

[APP–15282] You cannot update the type because credit has been applied

[APP–15283] You cannot update type when amount is adjusted

[APP–15284] You cannot update type after amount has been applied

[APP–15285] You cannot update type after invoice is posted

[APP–15286] This payment term is used on an invoice; you cannot delete it

[APP–15287] Please enter a status for this customer

[APP–15288] Please enter a customer address

[APP–15289] Please enter a new customer or query an existing customer

[APP–15290] Amount due cannot be less than zero

[APP–15291] You cannot delete a customer general communications

[APP–15292] Please enter a valid customer name or number

[APP–15293] Please enter percent due or amount due

[APP–15294] Please enter a title for your saved report

[APP–15295] Please enter an invoice number

[APP–15296] Please enter a value; the default is ALL

[APP–15297] You can only enter two or four digits for the year

[APP–15298] Batch source name already exists. Please enter a different value

[APP–15299] You cannot use \ Row Copy here

[APP–15300] Invalid number. Please enter a different number

[APP–15301] You cannot delete. Update status to Inactive instead

[APP–15302] This customer is not defined. Please enter a different value

[APP–15303] You cannot use \ Row Insert here

[APP–15304] You cannot credit more than the original quantity

[APP–15305] Must be in range &low_value to &high_value

[APP–15306] You cannot credit more than the balance due on this invoice

[APP–15307] Please enter a due date, due days, or Day of Month and Months Ahead

[APP–15308] This is a new batch; there are no invoices to retrieve

[APP–15309] Error retrieving sales credit information

[APP–15310] Error retrieving accounting information

[APP–15311] Error retrieving invoice lines

[APP–15312] Please enter date in the format DD–MON–YY or DD–MON–YYYY

[APP–15313] This invoice does not exist. Please enter a different invoice

[APP–15314] Please enter at least one sales credit line for each invoice line

[APP–15315] Please enter at least one revenue assignment for each invoice line

[APP–15316] Please enter a quantity greater than zero

[APP–15317] This screen is for inquiry only. You cannot update a customer here

[APP–15318] This screen is for inquiry only. You cannot add a new customer here

[APP–15321] Use \ Screen Save to start concurrent process

[APP–15324] CUSTOMER_STATUS must have a value of ’A’ or ’I’

Cause:

The CUSTOMER_STATUS column of the RA_CUSTOMERS_INTERFACE table has two valid

values, ’I’ and ’A’.

Action:

Enter a valid value into the CUSTOMER_STATUS field.

[APP–15325] Please enter the last invoice number for auto–numbering

[APP–15336] The last batch number is needed for auto–numbering

[APP–15339] &STATUS Invalid code combination for unearned

[APP–15349] &STATUS Invalid code combination for unbilled

[APP–15350] &STATUS Invalid code combination for suspense

[APP–15351] &STATUS Not all AutoAccounting types are defined

[APP–15352] &STATUS Invalid agreement or category codes

[APP–15353] &STATUS Failure while trying to insert into gl distributions

[APP–15354] &STATUS Invalid code combination id (freight)

[APP–15355] &STATUS Invalid code combination id (tax)

[APP–15356] &STATUS Invalid code combination id (revenue)

[APP–15357] &STATUS Invalid receivable account

[APP–15358] You cannot use \ Zone Erase here

[APP–15359] Please complete the tax account for line &LINE_NUM &DESC

[APP–15360] Please complete the freight account assignment

[APP–15361] Please complete the receivable account assignment

[APP–15362] The tax code for this product has been removed from the tax form

[APP–15363] Error occurred updating tax rates

[APP–15364] The tax code EXEMPT has been removed from the tax form

[APP–15365] You cannot alter a credit memo

[APP–15366] Salesperson revenue amount does not equal line amount

[APP–15367] This invoice is for tax and/or shipping fees only

[APP–15368] Discount date must be greater than discount date of previous line

[APP–15369] You cannot use \ Query in this zone

[APP–15370] You cannot use \ Row Erase here

[APP–15371] A batch already exists with this batch name

[APP–15372] You entered a line number that does not exist. Please enter another

[APP–15373] An invoice exists with this invoice number

[APP–15374] At last recurring invoice

[APP–15375] Error retrieving salesperson name

[APP–15376] Error retrieving invoice amount

[APP–15377] Receipt or credit has been applied. Please credit by line

[APP–15378] You cannot credit more interest than the original interest amount

[APP–15379] Discount date must be equal to or later than the invoice date

[APP–15380] Credited freight amount exceeds outstanding freight amount

[APP–15381] Error retrieving payment schedule

[APP–15382] This payment term is used on an invoice; you cannot update it

[APP–15383] You cannot update the payment term on an existing invoice

[APP–15384] Total of relative amounts must sum to base amount

[APP–15385] You must specify a batch name when printing a batch of invoices

[APP–15386] INSERT_UPDATE_FLAG has an invalid value

Cause:

Valid values for the INSERT_UPDATE_FLAG are ’I’ and ’U’.

Action:

Enter a valid value into the INSERT_UPDATE_FLAG field.

[APP–15387] CUSTOMER_NUMBER is mandatory when auto–numbering is set to ”No”

Cause:

The system option ’Automatic Customer Numbering’ is set to ”No”. The CUSTOMER_NUMBER

column is mandatory.

Action:

Enter a value for CUSTOMER_NUMBER.

[APP–15388] CUSTOMER_NUMBER must be null when auto–numbering is set to ”Yes”

Cause:

The system option ’Automatic Customer Numbering’ is set to ”Yes”. The CUSTOMER_NUMBER

column must be null.

Action:

Update the CUSTOMER_NUMBER column to null.

[APP–15389] This customer reference has two different customer types defined

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same customer, are marked identically for insert or update but have different customer type values

defined.

Action:

Update the CUSTOMER_TYPE field of all records referencing this address to be the same.

[APP–15391] Concurrent request failed

[APP–15392] Customer Number already assigned to a different customer

Cause:

Customer numbers are unique within RA_CUSTOMERS. A new customer cannot have a customer

number that already exists within RA_CUSTOMERS.

Action:

Enter a different customer number.

[APP–15393] PRIMARY_SITE_USE_FLAG has an invalid value

Cause:

Valid values for PRIMARY_SITE_USE_FLAG are ’Y’ and ’N’.

Action:

Enter a valid value into the PRIMARY_SITE_USE_FLAG field.

[APP–15394] Please enter an invoice number for this source

[APP–15395] You cannot use \ Row Delete here

[APP–15396] CUSTOMER_TYPE is not defined in AR_LOOKUPS

Cause:

The CUSTOMER_TYPE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

CUSTOMER_TYPE.

Action:

Enter a value defined in AR_LOOKUPS.

[APP–15397] LOCATION is not updatable

Cause:

The LOCATION is not updatable through the customer interface.

Action:

Do not specify a value for LOCATION when the INSERT_UPDATE_FLAG is set to ’U’.

[APP–15398] PRIMARY_SITE_USE_FLAG is not updatable

Cause:

The PRIMARY_SITE_USE_FLAG is not updatable through the customer interface.

Action:

Do not specify a value for PRIMARY_SITE_USE_FLAG when the INSERT_UPDATE_FLAG is set

to ’U’.

[APP–15399] SITE_USE_CODE is not updatable

Cause:

The SITE_USE_CODE is not updatable through the customer interface.

Action:

Do not specify a value for SITE_USE_CODE when the INSERT_UPDATE_FLAG is set to ’U’.

[APP–15405] Telephone reference has two different addresses

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same telephone but have different address references.

Action:

Update the ORIG_SYSTEM_ADDRESS_REF field of all records referencing this telephone to be

the same.

[APP–15406] Please enter a batch name, no auto–numbering for this source

[APP–15407] Telephone reference has two different customers

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same telephone but have different customer references.

Action:

Update the ORIG_SYSTEM_CUSTOMER_REF field of all records referencing this telephone to be

the same.

[APP–15409] Telephone reference has two different area codes

Cause:

There are multiple records defined in theRA_CONTACT_PHONES_INTERFACE table that have

the same telephone reference but different area codes.

Action:

Update the TELEPHONE_AREA_CODE field of allrecords with this telephone reference to be the

same.

[APP–15410] Telephone reference has two different types

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same telephone but have different type values.

Action:

Update the TELEPHONE_TYPE field of all records referencing this telephone to be the same.

[APP–15411] Telephone reference has multiple extensions

Cause:

There are multiple records defined in theRA_CONTACT_PHONES_INTERFACE table that have

the sametelephone reference but have different extension numbers.

Action:

Update the TELEPHONE_EXTENSION field of all records referencing this telephone to be the

same.

[APP–15412] Telephone reference has two different phone numbers

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same telephone but have different phone numbers.

Action:

Update the TELEPHONE field of all records referencing this telephone to be the same.

[APP–15415] Contact reference has two different addresses

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE that reference

the same contact but have different address references.

Action:

Update the ORIG_SYSTEM_ADDRESS_REF field of all records referencing this contact to be the

same.

[APP–15416] Contact reference has two different customers

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE that reference

the same contact but have different customer references.

Action:

Update the ORIG_SYSTEM_CUSTOMER_REF field of all records referencing this contact to be

the same.

[APP–15417] Receipt has been applied to this invoice; you cannot update it

[APP–15418] Contact reference has two different job titles

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same contact but have different job titles.

Action:

Update the CONTACT_JOB_TITLE field of all records referencing this contact to be the same.

[APP–15419] Contact reference has two different titles

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same contact but have different titles.

Action:

Update the CONTACT_TITLE field of all records referencing this contact to be the same.

[APP–15420] Contact reference has two different last names

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same contact but have different last name values.

Action:

Update the CONTACT_LAST_NAME field of all records referencing this contact to be the same.

[APP–15421] Contact reference has two different first names

Cause:

There are multiple records defined in the RA_CONTACT_PHONES_INTERFACE table that

reference the same contact but have different first name values.

Action:

Update the CONTACT_FIRST_NAME field of all records referencing this contact to be the same.

[APP–15422] CONTACT_JOB_TITLE must be defined in AR_LOOKUPS

Cause:

CONTACT_JOB_TITLE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

’RESPONSIBILITY’ .

Action:

Use the Define QuickCodes Form to enter a new job title or enter an existing one.

[APP–15423] The address reference specified is not defined for this customer

Cause:

The address reference specified is not valid for the customer reference specified. The address

reference may be marked in error within the RA_CUSTOMERS_INTERFACE table.

Action:

Enter a valid address for the customer reference specified or rectify the errors reports in

RA_CUSTOMERS_INTERFACE.

[APP–15424] Contact reference for update is not defined in RA_CONTACTS

Cause:

When updating a contact record the contact reference specified must exist in RA_CONTACTS.

Action:

Specify a contact reference that exists in RA_CONTACTS.

[APP–15425] Contact reference for insert is already defined in RA_CONTACTS

Cause:

When inserting a contact the contact reference specified must not exist in RA_CONTACTS.

Action:

Enter a contact reference that does not exist.

[APP–15426] CONTACT_TITLE is not defined in AR_LOOKUPS

Cause:

The CONTACT_TITLE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

’CONTACT_TITLE’.

Action:

Use the Define Quickcodes form to define a new contact title or change the value to an existing

title.

[APP–15427] LAST_NAME is mandatory when specifying a contact

Cause:

The LAST_NAME field is mandatory when specifying a contact.

Action:

Enter a value into the LAST_NAME field.

[APP–15428] Enter a date that is not in a closed period

[APP–15429] ORIG_SYSTEM_CONTACT_REF mandatory for contact information

Cause:

To identify an existing or new contact requires an ORIG_SYSTEM_CONTACT_REF.

Action:

Enter an ORIG_SYSTEM_CONTACT_REF.

[APP–15430] Telephone reference for update does not exist in RA_PHONES

Cause:

When updating a telephone record the telephone reference specified must exist in RA_PHONES.

Action:

Specify a telephone reference that exists in RA_PHONES.

[APP–15431] Telephone reference for insert is already defined in RA_PHONES

Cause:

When inserting a telephone the reference must not exist in the database.

Action:

Specify a telephone reference that does not exist.

[APP–15432] TELEPHONE_TYPE is not defined in AR_LOOKUPS

Cause:

The TELEPHONE_TYPE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

’COMMUNICATION_TYPE’.

Action:

Use the Define Quickcodes form to define a new telephone type or change the value to an existing

type.

[APP–15433] TELEPHONE_TYPE is mandatory when specifying telephone information

Cause:

TELEPHONE_TYPE is mandatory when specifying telephone information.

Action:

Enter a value into the TELEPHONE_TYPE field.

[APP–15434] TELEPHONE is mandatory when specifying telephone information

Cause:

TELEPHONE is mandatory when specifying telephone information.

Action:

Enter a value into the TELEPHONE field.

[APP–15435] ORIG_SYSTEM_TELEPHONE_REF mandatory for telephone information

Cause:

To identify an existing or new telephone to the customer interface requires an

ORIG_SYSTEM_TELEPHONE_REFERENCE.

Action:

Enter an ORIG_SYSTEM_TELEPHONE_REF.

[APP–15436] Address reference has two different customers

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different customer reference

values defined.

Action:

Update the ORIG_SYSTEM_CUSTOMER_REF field of all records referencing this address to be

the same.

[APP–15437] Address reference has two identical site use codes

Cause:

There are multiple records defined in theRA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update and have same SITE_USE_CODE values

defined.

Action:

Update the SITE_USE_CODE field of allrecords referencing this address to be different.

[APP–15438] Address reference has two different countries

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different COUNTRY values

defined.

Action:

Update the COUNTRY field of all records referencing this address to be the same.

[APP–15439] No postal code was found, calculating tax from city data

[APP–15440] Address reference has two different counties

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different COUNTY values

defined.

Action:

Update the COUNTY field of all records referencing this address to be the same.

[APP–15441] Address reference has two different provinces

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different PROVINCE values

defined.

Action:

Update the PROVINCE field of all records referencing this address to be the same.

[APP–15442] Address reference has two different states

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different STATE values defined.

Action:

Update the STATE field of all records referencing this address to be the same.

[APP–15443] Address reference has two different postal codes

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different POSTAL_CODE values

defined.

Action:

Update the POSTAL_CODE field of all records referencing this address to be the same.

[APP–15444] Address reference has two different cities

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different ADDRESS4 values

defined.

Action:

Update the ADDRESS4 field of all records referencing this address to be the same.

[APP–15445] Address reference has two different ADDRESS4 values

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different ADDRESS4 values

defined.

Action:

Update the ADDRESS4 field of all records referencing this address to be the same.

[APP–15446] Address reference has two different ADDRESS3 values

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different ADDRESS3 values

defined.

Action:

Update the ADDRESS3 field of all records referencing this address to be the same.

[APP–15447] Address reference has two different ADDRESS2 values

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different ADDRESS2 values

defined.

Action:

Update the ADDRESS2 field of all records referencing this address to be the same.

[APP–15448] Address reference has two different ADDRESS1 values

Cause:

There are multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the

same address, are marked identically for insert or update but have different ADDRESS1 values

defined.

Action:

Update the ADDRESS1 field of all records referencing this address to be the same.

[APP–15449] This customer reference has two identical primary site uses defined

Cause:

A customer cannot have multiple primary site uses defined for the same site use code. There are

multiple records defined in the RA_CUSTOMERS_INTERFACE table that reference the same

customer, are marked for insert and have identical site uses marked as the primary.

Action:

Update the SITE_USE_CODE field or the PRIMARY_SITE_USE_FLAG so that there is only one

primary site use a customer and site use code.

[APP–15450] You cannot insert or update invoices against commitments

[APP–15451] Warning: customer name and site use are duplicate

[APP–15452] Invoice Type must be entered for this class

[APP–15453] Error generating transaction number from batch source

[APP–15454] Open Receivable must be Yes for this class

[APP–15455] You cannot have duplicate category or agreement combinations

[APP–15456] Please enter a corresponding discount percent

[APP–15458] Warning: cost is above standard price or selling price

[APP–15459] Warning: standard price is below cost

[APP–15460] Line validated

[APP–15461] Lines amount and salesperson revenue amount are not equal

[APP–15462] Could not retrieve status

[APP–15463] Warning: GL distributions exist for this period

[APP–15464] You cannot change the period status because it has unposted items

[APP–15465] Cannot re–open this period since all transactions have been posted

[APP–15466] You can not delete a batch source. Update status to Inactive

[APP–15467] You must enter a Tax Exempt Number if you select Yes for Tax Exempt

[APP–15469] Warning: Customer name already exists

[APP–15470] Last active date cannot be prior to first active date

[APP–15471] Start date cannot be later than end date

[APP–15472] You cannot create new lookup codes for this lookup type

[APP–15473] Please enter credit memo type for this invoice class

[APP–15474] This sequence number already exists. Please enter a different value

[APP–15478] You cannot add new lines

[APP–15479] You cannot insert a new record

[APP–15480] Please enter a code

[APP–15481] You cannot delete a customer class

[APP–15482] Please correct the receivable account assignment

[APP–15483] Use \ Screen Save before updating another invoice

[APP–15484] Will recalculate all revenue accounts when saving updated invoice

[APP–15485] Will recalculate receivable account when saving updated invoice

[APP–15486] Will recalculate freight account when saving updated invoice

[APP–15487] Please enter credit memo number; automatic numbering is not in effect

[APP–15488] Business purpose already exists. Please enter a different value

[APP–15489] Tax code already exists. Please enter a different value

[APP–15491] Due date must be greater than the due date of previous line

[APP–15492] Please enter a contact name before entering the communications zone

[APP–15493] End date is not in the selected GL period. Please select another date

[APP–15494] Start date is not in the selected GL period. Enter another date

[APP–15495] There are no other records to view

[APP–15496] Invalid accounting flexfield

[APP–15497] State/Country combination already exists

[APP–15500] Please enter customer profile class

[APP–15501] Use \ Screen Save or \ Zone Erase before leaving this zone

[APP–15505] Please use \ Screen Save to save your work

[APP–15506] The Number of Periods field must show the actual number of periods

[APP–15508] Please complete the sales credit distributions for this invoice line

[APP–15509] &STATUS Invalid account type when distribution records exist

[APP–15511] This transaction has been identified with some errors. Please refer to header level

interface status

[APP–15513] This transaction record has not been identified with any error. Please refer to other

records for this transaction for interface status

[APP–15514] DUNNING_LETTERS is mandatory when no profile class specified

Cause:

Dunning letters must be specified when the profile class is null.

Action:

Enter a value into the DUNNING_LETTERS field.

[APP–15515] INTEREST_CHARGES is mandatory when no profile class specified

Cause:

Interest charges must be specified when the profile class is null.

Action:

Enter a value into the INTEREST_CHARGES field.

[APP–15516] STATEMENTS is mandatory when no profile class specified

Cause:

Statements must be specified when the profile class is null.

Action:

Enter a value into the STATEMENTS field.

[APP–15517] CREDIT_BALANCE_STATEMENTS mandatory when no profile class specified

[APP–15519] DUNNING_LETTER_SET_NAME is mandatory when DUNNING_LETTERS is

”Yes”

Cause:

A dunning letter set name must be entered when dunning letters are to be sent.

Action:

Enter a value into the DUNNING_LETTER_SET_NAME field.

[APP–15520] CHARGE_ON_FINANCE_CHARGE_FLAG mandatory when

INTEREST_CHARGES is Yes

Cause:

When interest is to be charged the CHARGE_ON_FINANCE_CHARGE_FLAG must be populated.

Action:

Enter a value into the CHARGE_ON_FINANCE_CHARGE_FLAG field.

[APP–15530] INTEREST_PERIOD_DAYS is mandatory when INTEREST_CHARGES is ”Yes”

Cause:

A value must entered into the interest period days field when interest is being charged.

Action:

Enter a valid value into the INTEREST_PERIOD_DAYS field.

[APP–15532] COLLECTOR_NAME has an invalid value

Cause:

The collector name is not defined.

Action:

Define this collector in the Collectors Window or enter an existing collector name.

[APP–15533] CREDIT_CHECKING has an invalid value

Cause:

Valid values for the CREDIT_CHECKING field are ’Y’ and ’N’.

Action:

Enter a valid value into the CREDIT_CHECKING field.

[APP–15534] TOLERANCE has an invalid value

Cause:

Valid values for the TOLERANCE field are ’Y’ and ’N’.

Action:

Enter a valid value into the TOLERANCE field.

[APP–15535] DISCOUNT_TERMS has an invalid value

Cause:

Valid values for the DISCOUNT_TERMS field are ’Y’ and ’N’.

Action:

Enter a valid value into the DISCOUNT_TERMS field.

[APP–15536] DUNNING_LETTERS has an invalid value

Cause:

Valid values for the DUNNING_LETTERS field are ’Y’ and ’N’.

Action:

Enter a valid value into the DUNNING_LETTERS field.

[APP–15537] INTEREST_CHARGES has an invalid value

Cause:

Valid values for the INTEREST_CHARGES field are ’Y’ and ’N’.

Action:

Enter a valid value into the INTEREST_CHARGES field.

[APP–15538] STATEMENTS has an invalid value

Cause:

Valid values for the STATEMENTS field are ’Y’ and ’N’.

Action:

Enter a valid value into the STATEMENTS field.

[APP–15539] CREDIT_BALANCE_STATEMENTS has an invalid value

Cause:

Valid values for the CREDIT_BALANCE_STATEMENTS field are ’Y’ and ’N’.

Action:

Enter a valid value into the CREDIT_BALANCE_STATEMENTS field.

[APP–15540] CREDIT_HOLD has an invalid value

Cause:

Valid values for the CREDIT_HOLD field are ’Y’ and ’N’.

Action:

Enter a valid value into the CREDIT_HOLD field.

[APP–15541] CREDIT_RATING has an invalid value

Cause:

Credit rating must be defined in AR_LOOKUPS with a LOOKUP_TYPE of ’CREDIT_RATING’.

Action:

Use the Define Quickcodes form to define a new credit rating or change the value to an existing

one.

[APP–15542] RISK_CODE has an invalid value

Cause:

RISK_CODE must be defined in AR_LOOKUPS with a LOOKUP_TYPE of ’RISK_CODE’.

Action:

Use the Define Quickcodes form to define a new credit rating or change the value to an existing

one.

[APP–15543] STANDARD_TERM_NAME which contains the payment terms has an invalid value

Cause:

STANDARD_TERM_NAME must be defined in RA_TERMS.

Action:

Use the Payment Terms Window to create a new payment term.

[APP–15544] OVERRIDE_TERMS has an invalid value

Cause:

Valid value for the OVERRIDE_TERMS field are ’Y’ and ’N’.

Action:

Enter a valid value into the OVERRIDE_TERMS field.

[APP–15545] DUNNING_LETTER_SET_NAME has an invalid value

Cause:

DUNNING_LETTER_SET_NAME must be defined in AR_DUNNING_LETTER_SETS.

Action:

Use the Dunning Letter Sets Window to define a new dunning letter set or enter an existing one.

[APP–15546] STATEMENT_CYCLE_NAME has an invalid value

Cause:

STATEMENT_CYCLE_NAME must be defined in AR_STATEMENT_CYCLES.

Action:

Use the Statement Cycles Window to define a new statement cycle or enter an existing one.

[APP–15547] ACCOUNT_STATUS has an invalid value

Cause:

ACCOUNT_STATUS must be defined in AR_LOOKUPS with a LOOKUP_TYPE of

’ACCOUNT_STATUS’

Action:

Use the Define Quickcodes form to enter a new account status or enter an existing one.

[APP–15548] PERCENT_COLLECTABLE has an invalid value

Cause:

Valid values for the PERCENT_COLLECTABLE column are 0 to 100.

Action:

Enter a valid value.

[APP–15549] AUTOCASH_HIERARCHY_NAME which contains the AutoCash rule has an invalid

value

Cause:

AUTOCASH_HIERARCHY_NAME must be defined in AR_AUTOCASH_HIERARCHIES.

Action:

Use the AutoCash Rule Sets Window to define a new rule or enter an existing one.

[APP–15555] This is an invalid MODE

[APP–15557] Please complete your tax accounting flexfield

[APP–15572] You can only delete incomplete transactions

[APP–15587] This Transaction flexfield is not unique. Please update

[APP–15609] You cannot update imported invoices

[APP–15614] Your Allow Delete system option is set to No

[APP–15616] &STATUS Credit memo date before invoice date

[APP–15620] &STATUS Line level revenue account was not specified for all lines when

distribution records exist

[APP–15621] You cannot update an invoice that is marked for posting

[APP–15622] Commitment balance remaining: &BALANCE

[APP–15623] Please complete the discount information for this payment term

[APP–15624] You cannot use line level assignment for this invoice

[APP–15625] This type is referenced by another type; you cannot change it

[APP–15626] COLLECTOR_NAME is mandatory when no profile class specified

Cause:

A collector name must be specified when the profile class is null

Action:

Enter a value into the COLLECTOR_NAME field.

[APP–15627] TOLERANCE is mandatory when no profile class specified

Cause:

Tolerance must be specified when the profile class is null.

Action:

Enter a value into the TOLERANCE field.

[APP–15628] DISCOUNT_TERMS is mandatory when no profile class specified

Cause:

Discount terms must be specified when the profile class is null.

Action:

Enter a value into the DISCOUNT_TERMS field.

[APP–15630] Adjusting Balance Due to display full amount available to credit

[APP–15633] You may not update transactions with activity

[APP–15634] STATEMENT_CYCLE_NAME is mandatory when STATEMENTS is ”Yes”

Cause:

A statement cycle name must be entered when statements are to be sent for this customer.

Action:

Enter a valid value into the STATEMENT_CYCLE_NAME.

[APP–15635] LOCATION must be null when auto–numbering is set to ”Yes”

Cause:

The system option ’Automatic Site Numbering’ is set to ”Yes”. The LOCATION column must be

null.

Action:

Update the LOCATION column to null.

[APP–15636] LOCATION is mandatory when auto–numbering is set to ”No”

Cause:

The system option ’Automatic Site Numbering’ is set to ”No”. The LOCATION column is

mandatory.

Action:

Enter a value for LOCATION.

[APP–15646] Warning: You have duplicate contact names for this customer

[APP–15647] You may not use Screen Erase here

[APP–15649] Please delete using the Contact Roles screen

[APP–15651] Field is protected against update

[APP–15661] For each customer, you may only have one active ”Statements” type

[APP–15662] This customer already has a primary active &SITE_CODE address

[APP–15664] CREDIT_CHECKING is mandatory when profile class is null

Cause:

Credit checking must be specified when the profile class is null.

Action:

Enter a value into the CREDIT_CHECKING field.

[APP–15678] Error constructing WHERE clause for transaction flexfield uniqueness

[APP–15707] Please limit percent to four places after the decimal

[APP–15711] The invoice balance is 0. Please choose another

[APP–15719] Credited tax amount cannot exceed outstanding tax amount

[APP–15720] &STATUS GL DATE cannot be before the first period in your calendar

[APP–15731] You cannot credit this deposit because the commitment balance is zero

[APP–15732] Credit amount exceeds commitment balance of &AMOUNT.

[APP–15735] &STATUS You cannot credit more than revenue amount for the invoice

[APP–15736] &STATUS You cannot credit more than suspense amount for the invoice

[APP–15737] &STATUS The freight amounts must be the same on all lines

[APP–15740] These recurring invoices will not be applied to your commitment

[APP–15747] ERROR: The transaction has more than two decimal places

[APP–15804] This transaction has been identified with some errors. Please refer to salesperson

level interface status

[APP–15810] CHARGE_ON_FINANCE_CHARGE_FLAG must be null if INTEREST_CHARGES

is No

Cause:

Compound interest cannot be charged when interest is not being charged.

Action:

Do not enter a value into the CHARGE_ON_FINANCE_CHARGE_FLAG.

[APP–15811] INTEREST_PERIOD_DAYS must be null if INTEREST_CHARGES is ”No”

Cause:

When interest is not being charged the number of days in an interest period is not applicable.

Action:

Do not enter a value into the INTEREST_PERIOD_DAYS field.

[APP–15812] INTEREST_PERIOD_DAYS must be greater than zero

Cause:

The number of days in an interest period must be greater than zero.

Action:

Enter a valid value.

[APP–15813] Posting is not allowed for this account

[APP–15821] Some periods required by your accounting rules have not been defined

[APP–15828] Error setting up location flexfield data

[APP–15830] Error validating address information

[APP–15831] Too many segments defined for location flexfield

[APP–15833] No &PQUAL is defined for &CQUAL &CVALUE

[APP–15834] You must provide a value for address component &QUAL

[APP–15835] Value &VALUE is not defined for address component &QUAL

[APP–15836] &CQUAL &CVALUE is not defined for &PQUAL &PVALUE

[APP–15837] Oracle error &ERRNUM in location flexfield user exit

[APP–15838] More than one &QUAL found with value &VALUE

[APP–15839] More than one &CQUAL &CVALUE found in &PQUAL &PVALUE

[APP–15840] More than one &PQUAL found for &CQUAL &CVALUE – please specify &PQUAL

[APP–15841] Invalid value found for system parameter ADDRESS_VALIDATION

[APP–16000] Invalid input: &ENTITY1

[APP–16001] One or more of your actions failed. Please check the Action Log form for details.

[APP–16002] The action just created requires you to enter action details. Please enter them now.

[APP–16003] You must enter a quality action before choosing this button.

[APP–16004] You must enter a collection element before choosing this button.

[APP–16005] You must enter a collection plan name before choosing this button.

[APP–16006] You can not change a collection element on a collection plan if you have set values or

actions for it. You can erase the collection element and add a new one.

[APP–16007] You may only delete this action detail record by deleting the Related Action record.

[APP–16008] You cannot delete this collection element because it represents predefined reference

information.

[APP–16009] You cannot delete this collection element because it is used in a quality results report

name or chart name.

[APP–16010] You cannot delete this collection element because it is used on a collection plan.

[APP–16011] You cannot delete this collection element because it is used as a specification

characteristic.

[APP–16012] You cannot delete this collection plan because results have been collected.

[APP–16013] This collection plan cannot be deleted because it is used in a quality results report

name or chart name.

[APP–16014] You cannot add both Job Name and Production Line to the same collection plan.

[APP–16015] You cannot query records without a saved parent record.

[APP–16016] Transaction complete: records deleted.

[APP–16017] The range of Collection Numbers entered is not valid.

[APP–16018] You must enter a customer.

[APP–16019] You must add Item to the collection plan and enable it before you can add the action

’Assign item status’.

[APP–16020] You must add Job Name to the collection plan and enable it before you can add the

action ’Place the job on hold’.

[APP–16021] You must add Lot Number to the collection plan and enable it before you can add the

action ’Assign a control status to the lot’.

[APP–16022] You must add PO Line to the collection plan and enable it before you can add the

action ’Place the purchasing line on hold’.

[APP–16023] You must add Production Line to the this collection and enable it before you can add

the action ’Place the schedule on hold’.

[APP–16024] You must add Serial Number to the collection plan and enable it before you can add

the action ’Assign a control status to the serialized unit’.

[APP–16025] You must add From/To Intraoperation Step to the collection plan and enable it before

you can add the action ’Assign a shop floor status to the to intraoperation step’.

[APP–16026] You must add Supplier to the collection plan and enable it before you can add the

action ’Place the supplier on hold’.

[APP–16027] You must add From/To Operation Sequence to the collection plan and enable it before

you can add From/To Intraoperation Step.

[APP–16028] You must add Subinventory to the collection plan and enable it before you can add

Locator.

[APP–16029] You must add Item to the collection plan and enable it before you can add Lot

Number.

[APP–16030] You must add Job or Production Line to the collection plan and enable it before you

can add From/To Operation Sequence.

[APP–16031] You must add Purchase Order number to the collection plan and enable it before you

can add Purchase Order line.

[APP–16032] You must add Item to the collection plan and enable it before you can add Revision.

[APP–16033] You must add Item to the collection plan and enable it before you can add Serial

Number.

[APP–16034] You must add Sales Order number to the collection plan and enable it before you can

add Sales Order line.

[APP–16035] You must add Item to the collection plan and enable it before you can add

Subinventory.

[APP–16036] You must add Item to the collection plan and enable it before you can add Production

Line.

[APP–16037] The range of Effective Dates entered is not valid.

[APP–16038] You have chosen a specification that does not contain the collection element

&ENTITY1.

[APP–16039] A system error occurred while trying to create a record group. Please contact your

support representative.

[APP–16040] A system error occurred while trying to populate a record group. Please contact your

support representative.

[APP–16041] The number of user–defined collection elements for a collection plan has been

exceeded. Please contact your support representative.

[APP–16042] The function you pressed is not available in this window.

[APP–16043] Creation of the Global Quality Results View Failed. This is probably due to invalid

seed data. Please contact your support representative.

[APP–16044] Invalid collection element ID passed. Please contact your support representative.

[APP–16045] You must enter a valid date for this field.

[APP–16046] Invalid field name: &ENTITY1. Please contact your support representative.

[APP–16047] You must enter a valid number for this field.

[APP–16048] Invalid collection plan ID passed. Please contact your support representative.

[APP–16049] Serial numbers must end with a number.

[APP–16050] Inventory parameters have not been entered for this organization. In order to use this

form you must: Define your Inventory parameters. Define your Inventory flexfields.

[APP–16051] You must enter an item category.

[APP–16052] You must enter an item or category set.

[APP–16053] You must enter a revision because the item selected is under revision control.

[APP–16054] Locator already exists.

[APP–16055] The range of Log Numbers entered is not valid.

[APP–16056] The From value must be less than the To value.

[APP–16057] The Lower Reasonable Limit must be less than or equal to the Upper Reasonable

Limit.

[APP–16058] The Lower Specification Limit must be less than or equal to the Upper Specification

Limit.

[APP–16059] The Lower User–defined Limit must be less than or equal to the Upper User–defined

Limit.

[APP–16060] A collection element name or collection plan name cannot contain special characters

like single or double quotes, periods, commas, and ”!”, ”@”, ”#”, ”$”, ”%”, ”^”, ”&”, ”*”, ”(”, ”)”,

”–”, ”+”, ”=”, ”\”, ”|”, ”~”, ”{”, ”}”, ”[”, ”]”, ”:”, ”;”, ”>”, ”<”, ”?”, ”/”. Underscores (”_”)

can be used.

[APP–16061] Collection element names cannot be words reserved for column names in collection

plan results database views. This includes words like NAME, OCCURRENCE,

ORGANIZATION_ID, and CREATED_BY.

[APP–16062] A collection element with this name already exists. When Oracle Quality checks for

duplicate collection element names, the names are first converted to UPPERCASE and then

compared. The system checks that another collection element does not exist with this name in

uppercase, lowercase, or mixed case. For example, ’pH’, ’Ph’, and ’PH’ are considered the same.

[APP–16063] No results were found that matched these search conditions.

[APP–16064] No default action rules have been defined for this collection element. Use the Define

Collection Elements window to define default action rules for this collection element.

[APP–16065] No default values have been defined for this collection element. Use the Define

Collection Elements window to define values for this collection element.

[APP–16066] Values entered are too large to be supported. Please contact your support

representative.

[APP–16067] Creation of the Collection Plan View Failed. This is probably due to invalid seed

data. Please contact your support representative.

[APP–16068] You cannot assign values to a predefined reference collection element.

[APP–16069] The profile QA:Quality Category Set must be set in order to use Category Set or

Category.

[APP–16070] Prompts that begin with a hyphen are not displayed in the Enter, Update, and View

Quality Results windows.

[APP–16071] Plan must contain an enabled, mandatory collection element that is not dependent on

another collection element.

[APP–16072] This record already exists. You entered a duplicate value that must be unique for

every record.

[APP–16073] You cannot delete a referenced specification. This specification is referenced by other

specifications, including: &ENTITY1 &ENTITY2 &ENTITY3

[APP–16074] Cannot delete this element from this plan because it is used in a report and/or graph.

[APP–16075] Cannot delete this element from this plan because results have been collected.

[APP–16076] You must enter a unique combination of values for Item, Revision, Category Set,

Category, Supplier, and Customer. The combination you entered already exists on the following

specification: &ENTITY1

[APP–16077] No specification was found satisfying your search criteria.

[APP–16078] The range of Log Dates entered is not valid.

[APP–16079] You cannot delete this short code because it has been copied to a collection plan.

[APP–16080] Value must be greater than or equal to the Lower Reasonable Limit of &ENTITY1.

[APP–16081] Value must be less than or equal to the Upper Reasonable Limit of &ENTITY1.

[APP–16082] You must enter a supplier.

[APP–16083] Changing this operator deletes lists associated with this rule.

[APP–16084] The saved elements on this specification will be replaced with the referenced

elements. Continue?

[APP–16085] Changing the short code for this value may result in its having inconsistent codes

throughout the rest of the product

[APP–16086] By changing this data item, quality data will be deleted. Do you really want to do

this?

[APP–16087] No specification was found satisfying your search criteria. Using default

specifications.

[APP–16088] You must add Component Subinventory to the collection plan and enable it before

you can add Component Locator.

[APP–16089] You must add Component Item to the collection plan and enable it before you can add

Component Lot Number.

[APP–16090] You must add Component Item to the collection plan and enable it before you can add

Component Revision.

[APP–16091] You must add Component Item to the collection plan and enable it before you can add

Component Serial Number.

[APP–16092] You must add Component Item to the collection plan and enable it before you can add

Component Subinventory.

[APP–16093] You must add Item to the collection plan and enable it before you can add UOM.

[APP–16094] You must add Component Item to the collection plan and enable it before you can add

Component UOM.

[APP–16095] You must clear this record before changing the collection plan.

[APP–16096] &ENTITY1 is not a valid plan name. Choose a new plan name for each record, and

then requery to see the full set of columns.

[APP–16097] To see a list of values for this field, you must first enter a valid organization code.

[APP–16098] There are no action details for the action selected.

[APP–16100] You must enter a subgroup size between 2 and 25.

[APP–16101] There are not enough data points to create a graph with this subgroup size.

[APP–16102] You must enter control limits before creating a control chart.

[APP–16103] You must delete the control limits associated with this chart before changing the value

of this field.

[APP–16104] You must enter a subgroup size before computing new limits.

[APP–16106] You must enter a positive number of bars.

[APP–16107] No criteria to copy.

[APP–16108] Changing this action will delete all of its action details. Do you want to continue?

[APP–16109] Do you want to save your changes and create or update the views in the database?

[APP–16110] Views are not created.

[APP–16111] Concurrent requests are launching to create Enter Result View and Collection Import

View.

[APP–16112] You must enter a positive number of points.

[APP–16113] There is no output variable specified which matches the token ’&token’.

[APP–16114] The token ’&token’ in Actions does not match an output variable. Please check the

’Assign a Value’ action in the ’Collection Plans’ form.

[APP–16115] Failed to perform SQL statement: &final_stmt Please check the ’Assign a Value’

action in the ’Collection Plans’ form.

[APP–16116] The value of the collection element that token ’&token’ corresponds to is null. Your

Action ’Assign a Value’ may fail. Do you want to continue?

[APP–16117] Can not execute the SQL statement because of the following error: &oraerr Please

check the ’Assign a Value’ action in the ’Collection Plans’ form.

[APP–16118] There is more than one row returned for the SQL statement in the ’Assign a Value’

action. Please check the action definition in the ’Collection Plans’ form.

[APP–16119] There is no row selected for the ’Assign a Value’ action. The assigned collection

element will remain unchanged.

[APP–16120] Unable to compute the control limits or plot the chart, because the total number of

data points collected is less than the subgroup size you specified.

[APP–16121] X Bar

[APP–16122] X

[APP–16123] R

[APP–16124] S

[APP–16125] mR

[APP–16126] The collection element corresponding to the token that you specified in the ’Assign a

Value’ action is missing from the plan. Please check the ’Collection Plan’ form.

[APP–16127] he collection element you have assigned a value to with the ’Assign a Value’ action is

missing from the plan. Please check the ’Collection Plan’ form.

[APP–16128] View Collection Elements

[APP–16129] View Collection Elements Summary

[APP–16130] View Collection Plans

[APP–16131] View Collection Plans Summary

[APP–16132] Quality Results entered on the following plan(s) have been cleared: &PLANS1

[APP–16133] Enter Quality Results.

[APP–16134] You must enter results on the following mandatory collection plan(s): &PLANS1.

[APP–16135] Quality Results cannot be entered because no Collection Plans apply.

[APP–16136] Please complete required entries before attempting to Enter Quality Results.

[APP–16137] Warning! Quality Results entered on the following plan(s) will be deleted: &PLANS1.

Do you wish to continue?

[APP–16138] A Plan must have an independent, displayed, and enabled collection element before it

can be saved.

[APP–16139] Specification cannot be changed once results have been entered for this collection

plan.

[APP–16140] Please enter a valid SQL validation string.

[APP–16141] Cannot display plan because there are no enterable elements.

[APP–16142] There is no token in the text that matches the output variable &output.

[APP–16143] You must add Purchase Order Number to the collection plan and enable it before you

can add Purchase Order Release Number.

[APP–16152] You cannot add the Accept the Shipment or Reject the Shipment actions if this is not

an Inspection Transaction. Please delete these actions.

[APP–16155] The total quantity accepted or rejected cannot exceed the parent transaction quantity.

[APP–16156] The inspection transaction action failed. The failure message is :

[APP–16157] The inspection transaction failed. Please check your collection plan setup.

[APP–16158] You cannot enter quality results when the Destination Type is ’Multiple’.

[APP–16159] You must enter a transaction quantity greater than zero before entering Quality

results.

[APP–16160] You have mandatory Collection Plan(s) that can’t be collected under express process.

[APP–16161] Can’t find transaction block. Please inform system adminstrator.

[APP–16162] An error has occurred when trying to create transaction plan record group. Please

inform your system adminstrator.

[APP–16164] Failed to find a Quality Inspection Plan. Please check your Collection Plan setup.

[APP–16165] A collection plan associated with the Inspection Transaction requires mandatory data

collection.

[APP–16166] Background data collection is not permitted for an Inspection Transaction.

[APP–16167] Do you want to save the changes you have made?

[APP–16168] To enable an Inspection transaction you must add collection elements/actions that are

not on your plan. Do you want the missing items to be added to your definition?

[APP–16169] You must add Project Number to the collection plan and enable it before you can add

Task Number.

[APP–16170] More than one row matched the specified condition

[APP–16171] No row matched the specified condition

[APP–16172] Collection elements and/or Actions required for the PO Inspection transaction have

been deleted, disabled or made non–mandatory. Disable the PO Inspection Transaction?

[APP–16173] This plan already exists in the current organization or another organization. You

entered a duplicate value that must be unique for every record.

[APP–17000] An error occurred while trying to Match and Reserve the ATO Configuration

&IERROR

[APP–17002] An Approval step exists between Booking and Demand Interface

[APP–17004] An Approval step exists between Demand Interface and Manufacturing Release

[APP–17006] A Hold was found when trying to Demand Interface the ATO Line

[APP–17008] A Hold was found when trying to Manufacturing Release the ATO Line

[APP–17010] The following error(s) occurred when importing order: &IERROR

[APP–17012] The following line detail level validation errors occurred.

[APP–17014] The following header level validation errors occurred.

[APP–17016] The following line level validation errors occurred.

[APP–17018] The following price adjustment validation errors occurred.

[APP–17020] The following sales credit validation errors occurred.

[APP–17022] Order was not imported.

The order was not imported due to the following reason(s): &VALERROR:

[APP–17024] Unable to automatically save your changes

[APP–17026] Invalid service item, please re–enter

[APP–17028] The item specified for your query is invalid or does not exist in the organization you

specified. Enter a valid item name or other query criteria.

[APP–17030] You must specify a value for the profile option &PROFILE_OPTION

Oracle Order Entry requires that you specify a value for the profile option &PROFILE_OPTION.

You have not specified a value for the profile option.

[APP–17032] Order or line on hold at Receivables Interface

[APP–17034] Unable to retrieve Invoicing Rule, Accounting Rule or Accounting Rule Type for

order line

[APP–17036] ATO option line locked at time of processing, unable to interface ATO model line

[APP–17038] Oracle Order Entry was unable to explode bill of material for &ITEM; &REASON.

[APP–17040] Unable to find bill of material for &ITEM in validation organization

The bill of material for the item must be set up in the item validation organization designated by the

profile option, OE: Item Validation Organization.

[APP–17042] There are ATO lines in this order with schedule details that are linked. Cancel at the

individual line level.

[APP–17044] You have gone below the minimum required quantity for this option.

You are attempting to cancel a quantity which would result in the remaining quantity falling below

the minimum required quantity. You may not cancel this quantity.

[APP–17046] You must cancel at least 1 of the allowed quantity.

[APP–17048] There is no allowable cancel quantity on this line.

[APP–17050] You must commit your changes before navigating to/from a model or class.

You are navigating to or from a model or class when you have changes pending. If you made

changes to commit, or if you nulled out those changes without doing a row erase, you must first

commit, and then navigate to/from to model or class you choose.

[APP–17052] You must first remove the demand or reservations on this included item before you

can cancel it.

[APP–17054] You must choose the corresponding number of details to cancel. &explanation

[APP–17056] You must cancel an appropriate number of details. For Item: &ITEM Option Line:

&OPTION You must cancel &REQ You have selected &CAN

[APP–17058] This line’s RMA interface status is invalid, contact your System Administrator.

[APP–17060] You may not cancel the last option in this mandatory class.

You are attempting to cancel the last option of a mandatory class. You may not cancel this option.

[APP–17062] This line is being processed. Please make this change later.

[APP–17064] You may not cancel a mandatory class.

You have attempted to cancel a class that is not optional. You may not cancel this class.

[APP–17066] Please select an order to cancel.

[APP–17068] Order Security cannot determine the type of line you are cancelling.

[APP–17070] Cannot determine the supply ID for this internal sales order.

[APP–17072] You must select a quantity that is a multiple of the parent quantity.

[APP–17074] This order is already cancelled.

[APP–17076] You must cancel an amount less than or equal to the allowed cancel quantity.

[APP–17078] You must specify both a quantity and a reason to cancel.

[APP–17080] You cannot cancel this Return at this level.

There are lines in this return that have interfaced and cannot be cancelled. Navigate to the

individual lines zone and cancel those allowed separately.

[APP–17082] Scheduling failed due to an internal exception. Contact your support representative.

[APP–17084] Scheduling failed due to an internal exception. Contact your support representative.

[APP–17086] You must cancel an amount equal to the full allowed cancel quantity.

[APP–17088] A problem occurred during credit checking. &MESSAGE_EXP

[APP–17090] Tax could not be calculated for &COUNT order lines.

[APP–17092] Unable to automatically create option lines &REPORT

[APP–17094] Configuration created &REPORT

[APP–17096] The balance against commitment &COMMITMENT is &BALANCE

[APP–17098] Commitment &COMMITMENT is depleted. The commitment you chose has an

insufficient balance to allow you to apply it to this line. Choose another commitment or create a

new one in Oracle Receivables, and then apply it.

[APP–17100] The quantity entered is not a multiple of the parent quantity &QTY.

[APP–17102] You cannot use the Enter Configuration Options form to update option lines.

Use the Options zone of the Enter Orders form to add, delete, or modify configuration option lines.

[APP–17104] Selected quantity is out of range (greater than maximum)

[APP–17106] Selected quantity is out of range (less than minimum)

[APP–17108] You cannot add options when scheduling exists for the Model Please unschedule the

Model before adding options to it

[APP–17110] Source order has not been booked yet. You are trying to copy an unbooked regular

order to an RMA. You cannot return against an unbooked order. Book the source order using the

Enter Orders form or choose another order to copy from.

[APP–17112] Copy failed – &COPY_ERROR

[APP–17114] Copy orders succeeded with warnings. The source order bill–to location information

could not be copied to the new order because it is invalid. Navigate to the Enter Orders form.

Query up the new order and enter a valid bill–to location on the order header.

[APP–17116] Copy orders succeeded with warnings. The source order ship–to location information

could not be copied to the new order because it is invalid. Navigate to the Enter Orders form.

Query up the new order and enter a valid ship–to location on the order header.

[APP–17118] Copy orders succeeded with warnings. The source order location information could

not be copied to the new order because it is invalid. Navigate to the Enter Orders form. Query up

the new order and enter valid bill–to and ship–to locations on the order header.

[APP–17120] Copy orders succeeded with warnings. The source order bill–to and line ship–to

location information could not be copied to the new order and someof the new order lines because it

is invalid. Navigate to the Enter Orders form. Query up the new order and enter valid bill–to and

ship–to locations on the order header and order lines that are missing address information

[APP–17122] Copy orders succeeded with warnings. The source order and line ship–to location

information could not be copied to the new order and some of the new order lines because it is

invalid. Navigate to the Enter Orders form. Query up the new order and enter a valid ship–to

location on the order header and order lines that a re missing address information.

[APP–17124] Copy orders succeeded with warnings. The source order address and line ship–to

location information could not be copied to the new order and someof the new order lines because it

is invalid. Navigate to the Enter Orders form. Query up the new order and enter valid location

information on the order header and order lines that are missing address information.

[APP–17126] Copy orders succeeded with warnings. The source order line ship–to location

information could not be copied to some of the new order lines because it is invalid. Navigate to

the Enter Orders form. Query up the new order and enter valid ship–to locations on those order

lines that are missing address information.

[APP–17128] You need to set the OE: Default RMA Status profile option to create a return

[APP–17130] Please use the Copy Order feature to copy an order

[APP–17132] Please use Copy Orders form to copy a return

[APP–17134] You must specify at least one prerequisite for this action

[APP–17136] Oracle Order Entry has detected an internal exception Routine: &ROUTINE

Operation: &OPERATION Object: &OBJECT Message: &MESSAGE Contact your Oracle

Support Representative and provide complete details on how you reached this internal exception.

[APP–17138] Freight Charge locked at time of processing

[APP–17140] Unable to convert Freight Charge to Order currency

[APP–17142] Freight Charge not interfaced because no related order lines have interfaced

[APP–17144] Zero amount Freight Charge not interfaced

[APP–17146] A GSA violation hold has been applied against this line

[APP–17148] This price violates a GSA price (&GSA_PRICE)

[APP–17150] Hold applied against order based on &ATTRIBUTE

[APP–17152] &ATTRIBUTE hold applied against line &LINE_NUMBER

[APP–17154] No purchasing information was found for this line.

[APP–17156] Flexbuilder failed to create the COGS Account.

Flexbuilder could not create Cost of Goods Sold (COGS) Account segments for sales order lines

being processed by the Inventory Interface because your FlexBuilder assignment is incomplete.

Check your assignment in the Define FlexBuilder Parameter form for the ’Order Entry Inventory

Interface COGS Account’ function. Some or all of the parameters being used are failing to derive

COGS account segments, or you may not have indicated your Chart of Accounts Structure in the

Assign Function Parameters form.

Use the Test FlexBuilder Parameters form to ensure your assignment is set up correctly.

[APP–17158] No transaction account was found.

[APP–17160] Line locked at time of processing

[APP–17162] You must enter a selling price rounded to &ROUNDING decimal places.

[APP–17164] You have Non–Overridable Only discounting privileges. You can only choose

preexisting discounts to override the selling price. Use QuickPick from the Selling Price field to

change the price by a certain discount. Discounting privileges are set at the user, responsibility and

application levels using the OE: Discounting Privileges profile option.

[APP–17166] Order Number Source &SOURCE_NAME is missing a Sequence. There is no

Sequence defined for this Order Number Source in the Database. Please contact your Database

Administrator to create a sequence using the following Syntax: &SQL_STMT

[APP–17168] A preference for this source location already exists

[APP–17170] Unable to retrieve Quota Sales Credits for order or line

[APP–17172] Unable to retrieve corresponding Service Transaction lines for order line

[APP–17174] A hold prevents booking this order

[APP–17176] Unable to apply changes &REPORT

[APP–17178] Changes applied &REPORT

[APP–17180] Unable to copy configuration to shipment schedule line &REPORT

[APP–17182] Copied configuration to shipment schedule line &REPORT

[APP–17184] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&AGREEMENT_ID

An Agreement with an Agreement Id of &AGREEMENT_ID does not exist. The error occurred

when trying to execute the following SQL statement: SELECT NAME FROM SO_AGREEMENTS

WHERE AGREEMENT_ID = &AGREEMENT_ID Please contact your System Administrator.

The most probable cause of this error is an invalid value with Standard Value Rule defaulting.

Please check your Standard Value Rules.

[APP–17186] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&ATTRIBUTE_VALUE

&ATTRIBUTE_VALUE is not a valid &ATTRIBUTE Please contact your System Administrator.

The most probable cause of this error is an invalid value with Standard Value Rule defaulting.

Please check your Standard Value Rules.

[APP–17188] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&COMMITMENT_ID

A Commitment with a Customer Transaction Id of &COMMITMENT_ID does not exist. The error

occurred when trying to execute the following SQL statement: SELECT TRX_NUMBER FROM

RA_CUSTOMER_TRX WHERE CUSTOMER_TRX_ID = &COMMITMENT_ID Please contact

your System Administrator. The most probable cause of this error is an invalid value with Standard

Value Rule defaulting. Please check your Standard Value Rules.

[APP–17190] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&LOOKUP_CODE

The lookup code &LOOKUP_CODE is not a valid value for lookup type &LOOKUP_TYPE. The

error occurred when trying to execute the following SQL statement: SELECT meaning FROM

FND_COMMON_LOOKUPS WHERE APPLICATION_ID = &APPLICATION_ID AND

LOOKUP_TYPE = ’&LOOKUP_TYPE’ AND LOOKUP_CODE = ’&LOOKUP_CODE’ Please

contact your System Administrator. The most probable cause of this error is an invalid value with

Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17192] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&CONTACT_ID

A Contact with a contact id of &CONTACT_ID does not exist. The error occurred when trying to

execute the following SQL statement:

SELECT LAST_NAME || ’,’ || FIRST_NAME FROM RA_CONTACTS WHERE CONTACT_ID =

&CONTACT_ID

Please contact your System Administrator. The most probable cause of this error is an invalid value

with Standard Value Ruling defaulting. Please check your Standard Value Rules.

[APP–17194] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&CONVERSION_TYPE_CODE

A Conversion Type with a Conversion Type Code of &CONVERSION_TYPE_CODE does not

exist. The error occurred when trying to execute the following SQL statement: SELECT

USER_CONVERSION_TYPE FROM GL_DAILY_CONVERSION_TYPES WHERE

CONVERSION_TYPE = ’&CONVERSION_TYPE_CODE’ Please contact your System

Administrator. The most probable cause of this error is an invalid value with Standard Value Rule

defaulting. Please check your Standard Value Rules.

[APP–17196] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&CURRENCY_CODE

A Currency with a Currency Code of &CURRENCY_CODE does not exist. The error occurred

when trying to execute the following SQL statement: SELECT PRECISION FROM

FND_CURRENCIES WHERE CURRENCY_CODE = ’&CURRENCY_CODE’ Please contact

your System Administrator. The most probable cause of this error is an invalid value with Standard

Value Rule defaulting. Please check your Standard Value Rules.

[APP–17198] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&CUSTOMER_ID

A Customer with a Customer Id of &CUSTOMER_ID does not exist. The error occurred when

trying to execute the following SQL statement: SELECT CUSTOMER_NAME,

CUSTOMER_NUMBER, NVL( GSA_INDICATOR, ’N’ ) FROM RA_CUSTOMERS WHERE

CUSTOMER_ID = &CUSTOMER_ID Please contact your System Administrator.

[APP–17200] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&STATUS_CODE

An Entry Status with a Status Code of &STATUS_CODE does not exist. The error occurred when

trying to execute the following SQL statement: SELECT NAME FROM SO_RESULTS WHERE

RESULT_ID = &STATUS_CODE

[APP–17202] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&FREIGHT_CODE

A Freight Carrier with a Freight Code of &FREIGHT_CODE does not exist for an Organization

with an Organization Id of &ORGANIZATION_ID. The error occurred when trying to execute the

following SQL statement: SELECT FREIGHT_CODE FROM ORG_FREIGHT WHERE

ORGANIZATION_ID = &ORGANIZATION_ID AND FREIGHT_CODE = ’&FREIGHT_CODE’

Please contact your System Administrator. The most probable cause of this error is an invalid value

with Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17204] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&INVOICING_RULE_ID

An Invoicing Rule with a Rule Id of &INVOICING_RULE_ID does not exist. The error occurred

when trying to execute the following SQL statement: SELECT NAME FROM RA_RULES

WHERE RULE_ID = &INVOICING_RULE_ID Please contact your System Administrator. The

most probable cause of this error is an invalid value with Standard Value Rule defaulting. Please

check your Standard Value Rules.

[APP–17206] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&SITE_USE_ID

A Location with a Site Use Id of &SITE_USE_ID does not exist. The error occurred when trying to

execute the following SQL statement: SELECT LOCATION FROM RA_SITE_USES WHERE

SITE_USE_ID = &SITE_USE_ID Please contact your System Administrator. The most probable

cause of this error is an invalid value with Standard Value Rule defaulting. Please check your

Standard Value Rules.

[APP–17208] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&LOOKUP_CODE

The Lookup Code &LOOKUP_CODE is not a valid value for Lookup Type &LOOKUP_TYPE.

The error occurred when trying to execute the following SQL statement:

SELECT meaning FROM &LOOKUP_TABLE WHERE LOOKUP_TYPE = ’&LOOKUP_TYPE’

AND LOOKUP_CODE = ’&LOOKUP_CODE’

Please contact your System Administrator. The most probable cause of this error is an invalid value

with Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17210] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value = &TERMS_ID

Payment Terms with a Terms Id of &TERMS_ID do not exist. The error occurred when trying to

execute the following SQL statement: SELECT NAME FROM RA_TERMS WHERE TERM_ID

= &TERMS_ID Please contact your System Administrator. The most probable cause of this error

is an invalid value with Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17212] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&PRICE_LIST_ID

A Price List with a Price List Id of &PRICE_LIST_ID does not exist. The error occurred when

trying to execute the following SQL statement:

SELECT NAME, –ROUNDING_FACTOR FROM SO_PRICE_LISTS WHERE PRICE_LIST_ID

= &PRICE_LIST_ID

Please contact your System Administrator. The most probable cause of this error is an invalid value

with Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17214] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&SALESREP_ID

A Salesperson with a Salesrep Id of &SALESREP_ID does not exist. The error occurred when

trying to execute the following SQL statement:

SELECT NAME FROM RA_SALESREPS WHERE SALESREP_ID = &SALESREP_ID

Please contact your System Administrator. The most probable cause of this error is an invalid value

with Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17216] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value = &UOM_CODE

A Unit with a UOM Code of &UOM_CODE does not exist. The error occurred when trying to

execute the following SQL statement: SELECT UNIT_OF_MEASURE FROM

MTL_UNITS_OF_MEASURE WHERE UOM_CODE = ’&UOM_CODE’ Please contact your

System Administrator. The most probable cause of this error is an invalid value with Standard

Value Rule defaulting. Please check your Standard Value Rules.

[APP–17218] Query Error. Attribute = &BLOCK.&ATTRIBUTE, Invalid Value =

&ORGANIZATION_ID

A Warehouse with a Organization Id of &ORGANIZATION_ID does not exist. The error occurred

when trying to execute the following SQL statement: SELECT NAME FROM

HR_ORGANIZATION_UNITS WHERE ORGANIZATION_ID = &ORGANIZATION_ID Please

contact your System Administrator. The most probable cause of this error is an invalid value with

Standard Value Rule defaulting. Please check your Standard Value Rules.

[APP–17220] You cannot navigate to the Shipment Schedule zone. The order line cycle status, or

the cycle status of the configuration lines this line belongs to, does not allow creation of shipment

schedules.

[APP–17222] Cannot change ordered quantity in this zone, shipment schedules exist In order to

change the ordered quantity for this line, you must first navigate to the Shipment Schedule Lines

zone and either add, delete, or update the desired shipment schedule quantities. After doing so, you

can then save your changes and have the appropriate ordered quantity for the parent line updated.

[APP–17224] &ITEM has no primary unit of measure. Items must have a primary unit of measure

defined to be included on a sales order. The item you are trying to enter is missing a value for the

Primary Unit of Measure item attribute (Define Items form). Contact your Item Master

administrator to fix this problem.

[APP–17226] A shipment schedule cannot be part of a ship set

[APP–17228] Modify order–level price adjustments in the Order Price Adjustments zone

[APP–17230] Sales Credits are required to book return

[APP–17232] Tax exemption reason is required in order to book return

[APP–17234] Line &LINE_NUMBER, warehouse is invalid

[APP–17236] You cannot navigate to the Shipment Schedule zone. Scheduling exists on the line

item or on the configuration item to which this line belongs. Remove scheduling from the line item

or from the configuration items if you want to create shipment schedules.

[APP–17238] A Purchase Order Number is required for this order type.

[APP–17240] &ITEM and &UNIT not on &PRICE_LIST. Please enter price.

[APP–17242] The rounding factor has to be greater or equal to &PRECISION.

[APP–17244] ATP demand failed for this line.

[APP–17246] Order failed credit check.

[APP–17248] Line on hold at Pick Release

[APP–17250] Insufficient quantity to Pick Release.

[APP–17252] Order on hold at Pick Release

[APP–17254] Another line in set could not be released.

[APP–17256] Incomplete Ship Model Complete Configuration. Unable to Pick Release.

[APP–17258] Incomplete Ship Set. Unable to pick release.

[APP–17260] Order or line on hold at RMA Interface

[APP–17262] You Must use the Price Adjustments Zone to change price.

[APP–17264] Error rounding amount to Order currency precision

[APP–17266] Could not open connection to Order Entry Transaction Manager &SERVER. Verify

that the server name is in tnsnames.ora. Make sure the listener for the server is up and running.

Contact your System Manager and provide complete details on how you reached this internal

exception.

[APP–17268] Field &FIELD not found in fieldbuffer. Contact your Oracle Support Representative

and provide complete details on how you reached this internal exception.

[APP–17270] Could not read initialization parameter &ARG

[APP–17272] Internal Exception in network communications layer. In routine &ROUTINE with

error code &ERROR_CODE, transfer callback error &CALLBACK_CODE. Contact your Oracle

Support Representative and provide complete details on how you reached this internal exception.

[APP–17274] Internal Exception in network communications layer. In routine &ROUTINE with

error code &ERROR_CODE. Contact your Oracle Support Representative and provide complete

details on how you reached this internal exception.

[APP–17276] Could not write &FIELD to fieldbuffer with value &VAL. Contact your Oracle

Support Representative and provide complete details on how you reached this internal exception.

[APP–17278] OE Transaction Manager or client could not write initialization parameter &ARG.

Contact your Oracle Support Representative and provide complete details on how you reached this

internal exception.

[APP–17280] Please use the Schedule Group region to update the attributes of the model line.

The Schedule Group Attributes zone lets you update the shipping attributes for an entire ATO

Configuration, Ship Complete Configuration, or Ship Set, which must ship as a complete set.

To access the Schedule Group Attributes zone for an ATO Configuration, put your cursor on the

base model line and press [Next Zone] to get the navigation QuickPick. Choose the ’Update ATO

Configuration Attributes’ option directly, or by first choosing the ’Configuration...’ option if your

OE: Action QuickPick Method profile option is set to Dual.

[APP–17282] ATP Inquiry complete.

[APP–17284] &RESULT

[APP–17286] ATS Quickpick failed. Scheduling failed due to an internal exception. Contact your

support representative.

[APP–17288] ATS QUERY User exit failed.

[APP–17290] Scheduling failed. Scheduling failed due to an internal exception.Contact your

support representative.

[APP–17292] Scheduling failed. See explanation or go to View Schedule Results. &explanation

[APP–17294] Scheduling Complete. &EXPLANATION

[APP–17296] Enter a full quantity or navigate to the schedule details zone.

You cannot do a partial reservation on a line that has multiple details with different attributes. You

can either change the quantity to the full quantity, or navigate to the Schedule Details zone and

make the reservations on individual schedule detail lines.

[APP–17298] This is a configuration item, unable to update field. This is an ATO model line and a

configuration item has been linked to this line. There are some actions that you cannot perform once

the configuration item has been created. If you want to perform an action on this line, you must

first unschedule the line, which unlinks the configuration item, perform your action, and then relink

the item if necessary.

[APP–17300] Change of schedule date is not allowed with the selected action.

[APP–17302] Change of Demand Class is not allowed with the selected action.

[APP–17304] Order: &ORDER Line: &LINE Shipment: &SHIP Option: &OPT Item: &ITEM

Warehouse: &WH Quantity: &QTY Schedule Date: &DATE

[APP–17306] Order: &ORDER Line: &LINE Shipment: &SHIP Option: &OPT Item: &ITEM

Warehouse: &WH Quantity: &QTY Schedule Date: &DATE Available Quantity: &ATP_QTY ATP

Date: &ATP_DATE Group Available Date: &GROUP_DATE

[APP–17308] Order: &ORDER Line: &LINE Shipment: &SHIP Option: &OPT Item: &ITEM

Warehouse: &WH Quantity: &QTY Schedule Date: &DATE Available Quantity: &ATP_QTY ATP

Date: &ATP_DATE

[APP–17310] Error. &reason

[APP–17312] Schedule Success.

[APP–17314] The detail quantity should be greater than 0.

[APP–17316] The item is under lot control, enter a lot.

[APP–17318] The item is under revision control, enter a revision.

[APP–17320] Scheduling failed. Scheduling failed due to an internal exception. Contact your

support representative.

[APP–17322] One of the group attributes failed your scheduling attempt. You tried to perform a

scheduling action on a schedule group (ATO Configuration, Ship Complete Configuration, or Ship

Set) and since one of the group members failed it caused the entire group to fail. Use the Schedule

Group Attributes zone to update attributes and try to schedule again. The Schedule Group Attributes

zone lets you update the shipping attributes for an entire ATO Configuration, Ship Complete

Configuration, or Ship Set, which must ship as a complete set.

[APP–17324] Scheduling failed. The OE GROUP SCHEDULE User exit failed due to an internal

exception. Contact your support representative.

[APP–17326] The requested group action can only be performed on the ATO model line.

[APP–17328] Incomplete ATO configuration, unable to schedule the whole configuration.

[APP–17330] Incomplete ATO configuration within the shipset, unable to perform scheduling.

[APP–17332] Line is a part of an internal sales order. Deleting is not allowed.

[APP–17334] Line is a part of an internal sales order. Inserting is not allowed.

[APP–17336] Line is a part of an internal sales order. Updating is not allowed.

[APP–17338] Use the Schedule Group Attributes zone to update attributes. If you have multiple

warehouses, dates or demand classes within a schedule group, Oracle Order Entry is unable to

perform scheduling. The Schedule Group Attributes zone lets you update the shipping attributes for

an entire ATO Configuration, Ship Complete Configuration, or Ship Set, which must ship as a

complete set. To access the Schedule Group Attributes zone for a Ship Set, put your cursor on the

base model line and press [Next Zone] to get the navigation QuickPick. Choose the ’Update Ship

Set Attributes’ option directly, or by first choosing the ’Configuration...’ option if your OE: Action

QuickPick Method profile option is set to Dual.

[APP–17340] Warehouse is Invalid.

[APP–17342] Invalid action, item is not reservable.

[APP–17344] Invalid action, item is not transactable.

[APP–17346] Item is not reservable, Demand is already placed.

[APP–17348] Item is not reservable.

[APP–17350] Item is not transactable, can not place demand or reserve.

[APP–17352] Line has been fully Pick Released, unable to update field.

[APP–17354] Use the Schedule Group Attributes zone to update attributes. The Schedule Group

Attributes zone lets you update the shipping attributes for an entire ATO Configuration, Ship

Complete Configuration, or Ship Set, which must ship as a complete set. To access the Schedule

Group Attributes zone for an ATO Configuration, put your cursor on the base model line and press

[Next Zone] to get the navigation QuickPick. Choose the ’Update ATO Configuration Attributes’

option directly, or by first choosing the ’Configuration...’ option if your OE: Action QuickPick

Method profile option is set to Dual. To access the Schedule Group Attributes zone for a Ship

Complete Configuration, put your cursor on the base model line and press [Next Zone] to get the

navigation QuickPick. Choose the ’Update Ship Complete Configuration Attributes’ option

directly, or by first choosing the ’Configuration...’ option if your OE: Action QuickPick Method

profile option is set to Dual. To access the Schedule Group Attributes zone for a Ship Set, put your

cursor on the base model line and press [Next Zone] to get the navigation QuickPick. Choose the

’Update Ship Set Attributes’ option directly, or by first choosing the ’Configuration...’ option if your

OE: Action QuickPick Method profile option is set to Dual.

[APP–17356] Line has supply reserved details, unable to update field. This is an ATO model line

and a work order has been opened in Oracle Work in Process. There are some attributes that you

cannot update once the work order is open. If you want to perform an action on this line, you must

first detach the work order from the sales order using the Define Discrete Job form in Oracle Work

in Process.

[APP–17358] Use the Schedule Group Attributes zone to update attributes. The line is a part of an

ATO Configuration. The Schedule Group Attributes zone lets you update the shipping attributes for

an entire ATO Configuration, Ship Complete Configuration, or Ship Set, which must ship as a

complete set. To access the Schedule Group Attributes zone for an ATO Configuration, put your

cursor on the base model line and press [Next Zone] to get the navigation QuickPick. Choose the

’Update ATO Configuration Attributes’ option directly, or by first choosing the ’Configuration...’

option if your OE: Action QuickPick Method profile option is set to Dual.

[APP–17360] Change of Lot is not allowed with the selected action.

[APP–17362] An item is required on the line.

[APP–17364] A quantity is required on the line.

[APP–17366] A schedule date is required on the schedule detail to perform scheduling.

[APP–17368] A unit of measure is required on the line.

[APP–17370] A warehouse is required on the schedule detail to perform scheduling.

[APP–17372] Schedule error, multiple errors occurred. &explanation

[APP–17374] Use the Schedule Group Attributes zone to update attributes. If you have multiple

schedule dates within a Ship Set, Oracle Order Entry is unable to perform scheduling. The Schedule

Group Attributes zone lets you update the shipping attributes for an entire ATO Configuration, Ship

Complete Configuration, or Ship Set, which must ship as a complete set. To access the Schedule

Group Attributes zone for a Ship Set, put your cursor on the base model line and press [Next Zone]

to get the navigation QuickPick. Choose the ’Update Ship Set Attributes’ option directly, or by first

choosing the ’Configuration...’ option if your OE: Action QuickPick Method profile option is set to

Dual.

[APP–17376] Use the Schedule Group Attributes zone to update attributes. If you have multiple

warehouses within a Ship Set, Oracle Order Entry is unable to perform scheduling. The Schedule

Group Attributes zone lets you update the shipping attributes for an entire ATO Configuration, Ship

Complete Configuration, or Ship Set, which must ship as a complete set. To access the Schedule

Group Attributes zone for a Ship Set, put your cursor on the base model line and press [Next Zone]

to get the navigation QuickPick. Choose the ’Update Ship Set Attributes’ option directly, or by first

choosing the ’Configuration...’ option if your OE: Action QuickPick Method profile option is set to

Dual.

[APP–17378] Your action did not result in any scheduling requests. &explanation

[APP–17380] Your action did not result in any scheduling requests.

[APP–17382] No scheduling results are currently available.

Your most recent scheduling action either did not result in any requests or the results have been

deleted. Scheduling results are available immediately after the scheduling action and before

committing any other information to the database.

[APP–17384] Reserved quantity is not required with the selected action.

[APP–17386] ATP inquiry user exit failed due to an internal exception. Contact your support

representative.

[APP–17388] Scheduling failed. &explanation

[APP–17390] The OE SECURITY user exit failed due to an internal exception. Contact your

support representative.

[APP–17392] The OE STANDARD VALUE user exit failed due to an internal exception. Contact

your support representative.

[APP–17394] Order is Cancelled, no scheduling allowed

[APP–17396] OE_Order does not exist,

[APP–17398] Order is not booked, use the Enter Orders form to schedule it

[APP–17400] Scheduling not allowed on parent shipment lines.

[APP–17402] Partial scheduling success. See explanation or go to View Schedule Results.

&explanation

[APP–17404] Please commit new line quantity before attempting to schedule.

[APP–17406] ATO configuration reached Pick Release, unable to perform requested action

[APP–17408] Detail has been Pick Released, unable to update field.

[APP–17410] Reserved quantity should be less than or equal to the open quantity.

[APP–17412] Change of reserved quantity is not allowed with the selected action.

[APP–17414] Change of Revision is not allowed with the selected action.

[APP–17416] The SCHEDULE user exit failed due to an internal exception. Contact your support

representative.

[APP–17418] Change of ship set number is not allowed when changing scheduling attributes.

[APP–17420] Change of Ship To Location is not allowed with the selected action.

[APP–17422] Change of Subinventory is not allowed with the selected action.

[APP–17424] Line has Supply Reserved details, unable to update field. This is an ATO model line

and a work order has been opened in Oracle Work in Process. There are some attributes that you

cannot update once the work order is open. If you want to perform an action on this line, you must

first detach the work order from the sales order using the Define Discrete Job form in Oracle Work

in Process.

[APP–17426] Supply reserved detail, cannot perform scheduling.

[APP–17428] The OE SYNC user exit failed due to an internal exception. Contact your support

representative.

[APP–17430] Please commit change to unit before attempting to schedule.

[APP–17432] &MESSAGE &MESSAGE_EXP

[APP–17434] The action you selected resulted in no scheduling requests. &explanation

[APP–17436] Partial scheduling success. See explanation or go to View Schedule Results.

&explanation

[APP–17438] Change of warehouse is not allowed with selected action.

[APP–17440] A work order is open for this line, unable to schedule. See explanation.

This is an ATO model line and a work order has been opened in Oracle Work in Process. There are

some scheduling actions that you cannot perform once the work order is open. If you want to

perform an action on this line, you must first detach the work order from the sales order using the

Define Discrete Job form in Oracle Work in Process.

[APP–17442] You cannot cancel &OBJECT; &REASON

[APP–17444] You cannot delete &OBJECT; &REASON

[APP–17446] A security rule already exists with these conditions

[APP–17448] You cannot insert &OBJECT; &REASON

[APP–17450] You must enter a scope

[APP–17452] You cannot update &ATTRIBUTE; &REASON

[APP–17454] Corresponding Service Transaction lines locked at time of processing

[APP–17456] Rerouting is not allowed on picking lines with scheduled details.

[APP–17458] There are duplicate waybill numbers in the batch. Modify the pick slips.

[APP–17460] You cannot make changes. &REASON.

[APP–17462] You cannot delete records. &REASON.

[APP–17464] You cannot create a new record. &REASON.

[APP–17466] You cannot close this batch or pick slip. See explanation.

You have tried to close a batch (or pick slip) with a ’Partial’ ship action without entering the partial

shipped quantities for its picking lines. Navigate to the Lines zone and enter partial quantities for

those picking lines you are shipping and then close the batch (or pick slip).

[APP–17468] You cannot ship anything on this line. &REASON.

[APP–17470] You cannot view or change details. &REASON.

[APP–17472] Rerouting is not allowed on picking lines with shipped quantities.

[APP–17474] Unrecognized post–commit failure code &REASON.

[APP–17476] Process online for shipping failed in the &PROCESS

The process online request has failed in the &PROCESS process. Set the Process Online field to

No, then close the batch or pick slip you are processing. Run the Update Shipping Information

concurrent program and wait for it to complete successfully. Then run the Inventory Interface

concurrent program. Monitor the log files for errors.

[APP–17478] You are rerouting the line

[APP–17480] A rule with the profile option &PROFILE_OPTION has already been entered for this

object and attribute

[APP–17482] A rule with the sequence number &SEQUENCE already exists for this object and

attribute

[APP–17484] A standard value rule set by the name &RULE_SET already exists

[APP–17486] The source &SOURCE has already been selected for this object and attribute in this

rule set

[APP–17488] A rule with the value &VALUE has been entered for this object and attribute

[APP–17490] A non–override user–specified value allowed rule exists with a lower sequence

[APP–17492] The standard value rule set &RULE_SET for &OBJECT is too complex; cyclical

rules likely

[APP–17494] &RULE_SET contains a Profile Option source rule with no Profile Option

[APP–17496] &RULE_SET contains a Value source rule with no value

Cause:

You system administrator has defined a rule in the standard value rule set &RULE_SET for the

object &OBJECT and attribute &ATTRIBUTE that has a rule whose source is Value, but the rule

has no value specified

Action:

Contact your system administrator to correct the incorrectly defined rule.

[APP–17498] You must enter a profile option for a rule with the Profile Option source

[APP–17500] You have selected &CLASS without choosing any of its options

[APP–17502] You must specify at least one option for the mandatory class &CLASS

[APP–17504] The quantity for component &ITEM is outside the valid range (&LOW to &HIGH)

[APP–17506] This discount has already been applied to this line

[APP–17508] This salesperson already has line–level sales credit

[APP–17510] Duplicate line number

[APP–17512] This discount has already been applied to this order

[APP–17514] This salesperson already has order–level sales credit

[APP–17516] You must enter an integral service duration greater than 0

[APP–17518] Invalid configuration: &REPORT

[APP–17520] &OBJECT is incomplete: &REPORT

[APP–17522] Quantity must be a multiple of &COMPONENT between &LOW and &HIGH

Oracle Order Entry requires that the ordered quantity (or ordered minus cancelled quantity) of an

option line must be evenly divisible by the quantity of the option’s parent component line, and that

the quantity is within the range allowed by the bill of material. The option’s quantity does not

currently meet these requirements. You must change the quantity to be valid to commit.

[APP–17524] &OBJECT is incomplete: &REPORT

[APP–17526] Group component item &ITEM not found in group warehouse &WAREHOUSE

[APP–17528] Unbooked revenue sales credit total (&TOTAL) cannot exceed 100

Cause:

You are attempting so save sales credits for an unbooked order line whose revenue total exceeds

100. (Line–level revenue sales credit for a booked order must equal 0 or 100.)

[APP–17530] Unbooked revenue sales credit total (&TOTAL) cannot exceed 100

Cause:

You are attempting to save sales credits for an unbooked order whose revenue total exceeds 100.

(Order–level revenue sales credit for a booked order must equal 100.)

[APP–17532] Quantity must be a multiple of &COMPONENT greater than or equal to &LOW

Oracle Order Entry requires that the ordered quantity (or ordered minus cancelled quantity) of an

option line must be evenly divisible by the quantity of the option’s parent component line, and that

the quantity is greater than or equal to the minimum quantity on the bill of material. The option’s

quantity does not currently meet these requirements. You must change the quantity to be valid to

commit.

[APP–17534] Quantity must be greater than or equal to Cancelled

[APP–17536] Installation detail quantity total (&QUANTITY_TOTAL) must be less than or equal

to line open quantity (&OPEN_QUANTITY)

[APP–17538] Schedule detail quantity total (&QUANTITY_TOTAL) must equal Line open quantity

(&OPEN_QUANTITY)

[APP–17540] Shipment schedule quantity total (&QUANTITY_TOTAL) must equal Line open

quantity (&OPEN_QUANTITY), Update parent line open quantity?

[APP–17542] You must enter &ATTRIBUTE for a booked order

[APP–17544] You must enter AutoCreate Quantity and System Type for AutoCreate System

[APP–17546] The tax code attribute is missing on the order line and it is required. It is required

because the order’s ”Tax Status” value is ”Required” OR the ”Tax Calculation” value is ”Yes” on

the order type’s Receivables transaction type.

[APP–17548] You must enter &ATTRIBUTE; &REASON

[APP–17550] You must enter &ATTRIBUTE

[APP–17552] Cannot modify default quantity when bill attribute Basis is Option Class

[APP–17554] Line–level sales credit (&TOTAL) must equal 0 or 100

[APP–17556] Order–level sales credit total (&TOTAL) must equal 100%. Specify a Salesperson or

enter additional Sales Credits

[APP–17558] Price adjustment total (&TOTAL) cannot exceed 100

[APP–17560] Unable to retrieve picking lines

[APP–17562] Could not update order cycle.

Cause:

Error while trying to update the order cycle for the specified order line.

Action:

Please contact your Oracle Representative.

[APP–17564] Invalid action.

Cause:

The specified action was not a Oracle Work in Process link to order line, unlink from order line,

assembly completion, or return assembly from inventory.

Action:

Please contact your Oracle Representative.

[APP–17566] Action quantity is greater than the maximum allowed quantity.

Cause:

Action quantity (&ACT_QTY) is greater than the maximum allowed quantity (&MAX_QTY).

Action:

Lower the action quantity.

[APP–17568] Invalid order line.

Cause:

Oracle Order Entry could not find detail row for the specified sales order line.

Action:

Please contact your Oracle Representative.

Cause:

Order line has been pick released, making it ineligible for Oracle Work in Process to change.

Action:

Perform change through Oracle Order Entry.

[APP–17570] Order line unit of measure action quantity is not an integer.

Cause:

Oracle Order Entry requires that the action quantity for WIP links, unlinks, completions, and returns

be integers. The quantity for this record, after conversion to the sales order line’s unit of measure,

had a non–integer value (&ACT_QTY).

Action:

Enter an action quantity that is an integer value in the sales order line’s primary unit of measure.

[APP–17572] Quantity to interface is zero

[APP–17574] Expected Arrival Date is required for this internal sales order.

[APP–17576] The line has been undemanded – no actions allowed.

The ATO model was demanded and manufacturing released but was later undemanded. Therefore

no actions can be taken on this line from the ATO Configured Item window. Place demand for the

line in the Lines to Schedule window before navigating to the ATO Configured Item window.

[APP–17578] This name is already in use. Please choose another action for this cycle

[APP–17580] You must include a passing result in the results zone

[APP–17582] Update cycle user exit failed.

[APP–17584] Selecting into result column failed.

[APP–17586] Update cycle user exit failed.

[APP–17588] This hold source is holding no existing orders

[APP–17590] &ROUTINE: Unable to allocate memory for &OBJECT

[APP–17592] This name already in use. Please choose another

[APP–17594] Approval from date must be earlier or the same as approval to date

[APP–17596] Approval to date must be later or the same as approval from date

[APP–17598] Please choose a valid option

[APP–17600] Column–value combination is currently active for these effective dates

[APP–17602] Discount is applied. Please apply a different discount

[APP–17604] Error while creating order number sequence

[APP–17606] Expected receipt date cannot be earlier than the RMA date

[APP–17608] Quantity cannot be greater than original ordered quantity

[APP–17610] Unable to find cycle action

[APP–17612] Unable to retrieve order lines

[APP–17614] Price adjustments total cannot exceed 100 percent

[APP–17616] Quantity must be greater than zero

[APP–17618] Quota total must equal 100 percent

[APP–17620] Please select search criteria and navigate to the next zone

[APP–17622] You must specify an action before navigating to the next zone

[APP–17624] Your responsibility is not authorized to release this hold

[APP–17626] Cycle action already exists for effective from and to dates you entered

[APP–17628] Effective from date must equal or be later than hold effective from date

[APP–17630] Effective from date must not be later than hold effective to date

[APP–17632] Effective to date must equal or be earlier than hold effective to date

[APP–17634] Effective to date must not be earlier than hold effective from date

[APP–17636] To Query on a value, you must also enter the Parameter.

[APP–17638] Hold source of this type is currently active

[APP–17640] Hold until date must be later than the current date

[APP–17642] Unable to place hold because site is not a bill–to or ship–to site

[APP–17644] Unable to place this hold because site use is missing

[APP–17646] Cannot retrieve ID number for hold source sequence

[APP–17648] Failed to update hold comment

[APP–17650] Please specify a hold name and type

[APP–17652] Please use the Remove Holds form to remove holds

[APP–17654] At last zone

[APP–17656] Cannot delete records

[APP–17658] Cannot duplicate record

[APP–17660] Cannot erase record

[APP–17662] Cannot erase records

[APP–17664] Cannot insert record

[APP–17666] Cannot update record

[APP–17668] Your concurrent request ID is &REQUESTID

[APP–17670] Field is required

[APP–17672] This name is already in use. Please choose another

[APP–17674] Cannot copy records

[APP–17676] Cannot create new records

[APP–17678] Cannot delete record

[APP–17680] Cannot duplicate records

[APP–17682] Cannot insert records

[APP–17684] Cannot create new record

[APP–17686] &ROUTINE cannot get profile value for &PROFILE

[APP–17688] Query not allowed

[APP–17690] Row functions not allowed

[APP–17692] &ROUTINE routine failed

[APP–17694] Please save your changes using \ Screen Save

[APP–17696] Please adjust this price list or add an item group

[APP–17698] Please choose next option

[APP–17700] This date already exists for this item and unit. Please re–enter

[APP–17702] Discount with this name and price list is currently active

[APP–17704] Effective date:from must be the same or earlier than discounts zone date

[APP–17706] Effective to date must equal or be later than header effective to date

[APP–17708] Effective to date must equal or be earlier than header effective to date

[APP–17710] Discount already exists for this customer. Enter a unique discount

[APP–17712] Please erase amount before you enter price break lines

[APP–17714] Please erase percent before entering price break lines

[APP–17716] Please erase price field before entering price break lines

[APP–17718] You entered an amount in the price field. Default for fixed field is yes

[APP–17720] Please use GSA customers or site uses when defining your GSA discounts

[APP–17722] Discount violates your current GSA discount

[APP–17724] You must define a fixed price for GSA discounts

[APP–17726] GSA price is greater than or equal to the discount price you entered

[APP–17728] You must define your GSA discounts as type line item

[APP–17730] Item group dates must be within the price list start and end dates

[APP–17732] Please select an item on the price list you specified

[APP–17734] You have entered a header level discount amount or percent. If you want to enter a

line level discount amount or percent, you must delete the header level amount or percent.

[APP–17736] You have entered a header level discount percent. If you want to enter a line level

discount amount or percent, you must delete the header level percent.

[APP–17738] You have specified a negative amount

[APP–17740] You have specified a negative list price

[APP–17742] Unable to retrieve agreement name data

[APP–17744] Unable to retrieve agreement type lookup data

[APP–17746] Cannot retrieve item description

[APP–17748] Unable to retrieve lookup data

[APP–17750] Unable to retrieve order type data

[APP–17752] Cannot get item from price list

[APP–17754] Price list contains no rounding factor

[APP–17756] You have entered overlapping dates for the same item group

[APP–17758] Percent must be less than or equal to 100

[APP–17760] Warning! Your percent is equal to 0

[APP–17762] Starting and ending range overlap another price break line

[APP–17764] Price must be fixed for GSA discounts

[APP–17766] A pricing rule will override your specified list price and percent

[APP–17768] Use \ Screen Save to submit request

[APP–17770] Please specify a list price or percent

[APP–17772] You must specify a percent for this item

[APP–17774] Please specify a pricing rule or percent

[APP–17776] Please specify a pricing rule, list price, or percent

[APP–17778] Please specify a pricing rule or list price

[APP–17780] Ending range must be later or the same as starting range

[APP–17782] Starting range must be earlier or the same as ending range

[APP–17784] Please enter values in all the fields to the left of column &NUM.

[APP–17786] Warning! Amount is zero

[APP–17788] Warning! Your list price has a zero value

[APP–17790] Changes not allowed after Receivable Interface

[APP–17792] Changes not allowed after Receivable Interface

[APP–17794] You must enter an action

[APP–17796] Cannot define securty rules with the same sequence number as system rules.

[APP–17798] You must copy existing lines to create new records

[APP–17800] Please delete the order number before entering other search criteria

[APP–17802] Details required and detail quantity must equal line quantity.

[APP–17804] Detail shipped quantity does not equal line shipped quantity.

[APP–17806] You must enter a customer name before entering a ship to location

[APP–17808] You must specify a waybill number before shipping

[APP–17810] You must enter an amount if you have entered a freight charge name

[APP–17812] This location does not exist in this subinventory.

[APP–17814] Use the Pick Release Orders form to enter release criteria. Create a release rule for

frequently used release criteria.

[APP–17816] Error occurred while submitting concurrent request to create pick slips

[APP–17818] There are no outstanding lines to split.

[APP–17820] Pick slip is closed

[APP–17822] Use ”Split and Close” action to split and create new pick slips.

[APP–17824] Detail requested quantity total does not equal line requested quantity

[APP–17826] Scheduled ship date:from must be the same or earlier than ship date:to

[APP–17828] Numeric segment of a serial number cannot exceed 9 digits.

[APP–17830] Warning: this serial number has no numeric segment.

[APP–17832] Serial number range duplicates pick slip &PKSLP line &PKLN

[APP–17834] Shipping confirmation with this pick slip number and waybill exists

[APP–17836] Shipped quantity must be equal or less than ordered quantity

[APP–17838] Please use QuickPick

[APP–17840] Use \ Row Erase to clear this record

[APP–17842] You must enter a QuickCode type

[APP–17844] A printer has been chosen for this value of the profile level. Please select another

profile level value

[APP–17846] ATO model on manufacturing release hold

[APP–17848] Not all lines in ATO configuration available to release.

[APP–17850] Unable to release to manufacturing, locked by another program

[APP–17852] Order line on manufacturing release hold

[APP–17854] Some lines in ATO configuration not demanded.

[APP–17856] Order on manufacturing release hold.

[APP–17858] SQL error occurred.

The following SQL error occurred: &SQLERROR:

[APP–17859] Please enter Approval Name.

[APP–17860] You must choose the corresponding number of details to cancel.

[APP–17861] Nothing can be cancelled on this line.

[APP–17862] You cannot use the Full Checkbox to cancel an internally ordered line.

[APP–17863] You cannot use the Full Checkbox to cancel a return line.

[APP–17864] You cannot use the Full Checkbox to cancel a service line.

[APP–17865] You cannot cancel the full quantity because there are open pick slips for this line.

[APP–17866] Cancel Order

[APP–17867] Cancel Line(s)

[APP–17868] You have already specified a cancel quantity for this configuration. You can only

cancel quantities at one level within a configuration.

[APP–17869] Please enter a Cancel Quantity on the line you want to cancel.

[APP–17870] You must specify a quantity to cancel.

[APP–17871] The allowable cancel quantity has changed. Please requery and re–enter the quantity

you want to cancel.

[APP–17872] You must specify a reason to cancel.

[APP–17873] The Configurator is only available for Models.

[APP–17874] One or more Price Adjustments or Sales Credits was not copied to the new order

because they were not valid. Line Prices may have been adjusted or cleared. Other errors may have

been found when copying the order. To see a complete list of errors, navigate to Run Reports to run

the Process Exception Report for Program Name Copy Orders and Order Number

&ORDER_NUMBER.

[APP–17875] One or more fields on the new order or its lines were cleared because they were

inactive or invalid. Other errors may have been found when copying the order. To see a complete

list of errors, navigate to Run Reports to run the Process Exception Report for Program Name Copy

Orders and Order Number &ORDER_NUMBER.

[APP–17876] At least one line was not copied to the new order due to an invalid item or model.

Other errors may have been found when copying the order. To see a complete list of errors,

navigate to Run Reports to run the Process Exception Report for Copy Orders and Order Number

&ORDER_NUMBER.

[APP–17877] Sales Order does not exist.

[APP–17878] Copy failed. Unable to complete validation of the copied order. &VALID_ERROR

[APP–17879] Validating new order or return...

[APP–17880] Note Categories

[APP–17881] Notes

[APP–17882] Effective Dates

[APP–17883] Discounts already exist for this line. This fixed price discount will be treated as a

percentage discount and added to the existing discounts. Discounts already exist for this line. This

fixed price discount will be treated as a percentage discount and added to the existing discounts.

[APP–17884] Document #&DOCUMENT_ID

[APP–17885] All of the &TYPE you have selected are already released.

[APP–17886] All of the lines you have selected are already on hold.

[APP–17887] All of the lines you have selected are already released.

[APP–17888] All of the &TYPE you have selected are already on hold.

[APP–17889] All of the orders you have selected are already on hold.

[APP–17890] All of the orders you have selected are already released.

[APP–17891] All of the hold sources you have selected are already released.

[APP–17892] Please select one or more &TYPE to release from hold.

[APP–17893] Please identify whether the Hold Selection Criteria is for a Customer, Order, Site Use

or Item.

[APP–17894] Please enter Customer Name.

[APP–17895] Please enter Hold Name.

[APP–17896] Please enter Item.

[APP–17897] Please enter Order Number.

[APP–17898] Please enter a Release Reason.

[APP–17899] Please enter Site Use.

[APP–17900] Please enter &TYPE.

[APP–17901] No action has been taken on Holds which have already been released.

[APP–17902] Some of the &TYPE you have selected are already released. They will be ignored.

Continue?

[APP–17903] Some of the lines you have selected are already on hold. They will be ignored.

Continue?

[APP–17904] Some of the lines you have selected are already released. They will be ignored.

Continue?

[APP–17905] Some of the &TYPE you have selected are already on hold. They will be ignored.

Continue?

[APP–17906] Some of the orders you have selected are already on hold. They will be ignored.

Continue?

[APP–17907] Some of the orders you have selected are already released. They will be ignored.

Continue?

[APP–17908] Some of the hold sources you have selected are already released. They will be

ignored. Continue?

[APP–17909] Please enter the Transaction Type before entering other information for this

installation detail.

[APP–17910] Cancel

[APP–17911] Details

[APP–17912] Message Details

[APP–17913] This long text exceeds 32760 bytes. Refer to fnd_documents_long_text media_id = #

&DOCUMENT_ID

[APP–17914] This text exceeds 32760 bytes. Refer to so_notes document_id # &DOCUMENT_ID

[APP–17915] R10–OE*.inp–#FND STORELONG SO_NOTES NOTE NOTE_ID should update this

later.

[APP–17916] Please choose an existing Order before applying Notes.

[APP–17917] Please choose an existing Return before applying Notes.

[APP–17918] You cannot enter customer &CUSTOMER. No active addresses are defined for this

customer.

[APP–17919] This function is not available for Lines with Shipment Schedules.

[APP–17920] Please enter a value without %.

[APP–17921] You cannot adjust list prices lower than –100%.

[APP–17922] Please enter an adjustment percentage or amount.

[APP–17923] Please enter the name of the price list to copy from.

[APP–17924] You cannot copy to a price list that already exists. Enter a unique name for the new

price list you want to copy to.

[APP–17925] Please enter the name of a new price list to copy to.

[APP–17926] Item group dates must be within the price list effective dates.

[APP–17927] Multiple

[APP–17928] Please enter a price list.

[APP–17929] Please verify that the adjustment amount is correct for the new currency.

[APP–17930] You must enter Source Order Number. This field is required when copying an order.

[APP–17931] You must enter Source Order Type. This field is required when copying an order.

[APP–17932] You must enter Target Order Category. This field is required when copying an order.

[APP–17933] You must enter Target Order Type. This field is required when copying an order.

[APP–17934] Line Total

[APP–17935] List Price

[APP–17936] Original QTY

[APP–17937] You cannot change the Customer. Return is booked.

[APP–17938] Current Return quantity cannot be greater than the invoiced quantity and was adjusted

to match the invoiced quantity.

[APP–17939] You cannot change the Return Type. Return lines exist for this return.

[APP–17940] You cannot change the Price List because Discounts have been applied to this Return.

[APP–17941] You cannot change the Price List because Lines already exist for this Return.

[APP–17942] You cannot update the Price List because this Return Type does not allow changes to

Price Lists.

[APP–17943] Assemble to Order

[APP–17944] Scheduling failed. &explanation

[APP–17945] Partial scheduling success. &explanation

[APP–17946] Partial scheduling success. &explanation

[APP–17947] Please use the Group Attributes window to make this change. The Group Attributes

window lets you update the shipping attributes of an entire Ship Set, ATO Configuration or Ship

Complete Configuration, which must ship as a complete set. Save current changes and proceed to

the Group Attributes window?

[APP–17948] Ship Set

[APP–17949] Ship Complete

[APP–17951] Outstanding concurrent request exists for this cycle action. Please try this update

again later.

[APP–17952] At least one cycle action must be defined.

[APP–17953] You cannot change the passing result for this cycle action.

[APP–17954] You must include the Cycle Action ’Enter’ in the Order Cycle.

[APP–17955] Please add a prerequisite action and result for this cycle action.

[APP–17956] Please enter a later ’Effective To Date’, since this order cycle is assigned to at least

one Order Type that is active on the Cycle End Date.

[APP–17957] Your responsibility is not authorized to release this hold source.

[APP–17958] End date falls outside of the effective dates for this price list.

[APP–17959] GSA discounts must specify a fixed price. The discount you entered will be

converted to a fixed price.

[APP–17960] The list price will be treated as a zero price since the list price has not yet been

calculated for this rule–based price.

[APP–17961] You may not create price break lines for this detail.

[APP–17962] You must specify an item group before entering items.

[APP–17963] You must specify a price list before entering price list items.

[APP–17964] A list price, percent, or pricing rule must be entered.

[APP–17965] You may not enter a percent, amount, or sales price because price break lines exist for

this discount line.

[APP–17967] Entering an amount will override the specified pricing rule.

[APP–17968] Entering a percent will override the specified pricing rule.

[APP–17969] This query could take a long time. Do you wish to continue?

[APP–17970] This function not available currently.

[APP–17971] This function not available for lines with shipment schedule.

[APP–17972] ATO Options cannot have more than 1 detail.

[APP–17973] This function is only available for models.

[APP–17974] No Options exist for this line. Choose Details to see Line Schedule Details.

[APP–17975] No Shipments exist for this line. Choose Details to see Line Schedule Details.

[APP–17976] You cannot change the Customer. Return lines exist for this return.

[APP–17977] You cannot change Return for Repair after a Return Line is Completely Accepted.

[APP–17978] You cannot change Return for Repair after a Return is closed.

[APP–17979] You cannot change Return for Repair after a Return Line is closed.

[APP–17980] You cannot change the Return Type after a Return is booked.

[APP–17981] Some lines were not copied since the items are not in the new price list.

[APP–17982] (May be slow.)

[APP–17983] End date falls outside of the effective dates for this discount.

[APP–17984] Start date falls outside of the effective dates for this discount.

[APP–17985] Requery lines to see new sort.

[APP–17986] Start date falls outside of the effective dates for this price list.

[APP–17987] Please enter Approval Result.

[APP–17988] You cannot cancel this line because there are open pick slips against a parent class or

its included items in this configuration.

[APP–17989] Currency for new discount does not match currency from copied discount.

[APP–17990] For each configuration, you can only cancel one service line and only that service line

at a time.

[APP–17991] This model is on Configurator Validation Hold

[APP–17992] You cannot create Shipments for lines with Installation Details.

[APP–17993] You cannot create Shipments for lines that have Services attached.

[APP–17994] Cannot change Ship–to. Customer Item is not defined for new Ship–to.

[APP–17995] Order–level sales credit total (&TOTAL) must equal 100%.

[APP–17996] &NUMBER lines have been put on hold.

[APP–17997] &NUMBER orders have been put on hold.

[APP–17998] Hold Source created. Choose Hold All Orders to hold the order, or choose Lines to

hold lines on the order.

[APP–17999] Success.

[APP–18000] Required Parameters are missing.

[APP–18001] Invalid Action &ACTION .

[APP–18002] Application ID &APPLICATION_ID is not valid.

[APP–18003] Invalid Customer ID &CUSTOMER_ID .

[APP–18004] Valid Entity Codes are C,S,O and I.

[APP–18005] Invalid Header ID &HEADER_ID .

[APP–18006] Invalid Hold ID &HOLD_ID .

[APP–18007] &HOLD_NAME is not a valid hold name.

[APP–18008] Invalid Inventory Item ID &INVENTORY_ITEM_ID .

[APP–18009] Order Type &ORDER_TYPE and Order Number &ORDER_NUMBER is not valid.

[APP–18010] Invalid Reason Code &REASON_CODE .

[APP–18011] This responsibility is not authorized to perform this action.

[APP–18012] Responsibility ID &RESPONSIBILITY_ID is not valid.

[APP–18013] Invalid Site Use ID &SITE_USE_ID .

[APP–18014] Hold Source not found.

[APP–18015] REASON_CODE is a required parameter.

[APP–18016] Failed to Release the Hold.

[APP–18017] Failed to Remove the Hold.

[APP–18018] Order Entry Transaction Manager has detected an internal exception. This form will

not be able to perform any operations. You can use this form only for debugging purposes.

[APP–18019] Order Entry Transaction Manager has detected an internal exception. This form will

not be able to perform any operations, so the form will be closed.

[APP–18020] Remove ’%’ from your item range. You can enter the entire item, or just the first few

characters of the item, for the low or high end of the item range.

[APP–18201] Please choose the action text you want included in your new PCR

[APP–18202] Please enter text for the current action

[APP–18203] The current incident cannot be related to the product change request

[APP–18204] A product change request for the current incident has been created

[APP–18205] You cannot choose an unserviced product

[APP–18206] You cannot update the product from here. Use the Incident zone instead

Cause: You tried to change the product for the current incident. Changing the product from the

current zone is not allowed.

Action: Proceed to the Incident Details zone and choose the Complete Incident Details option.

This option transfers you to the Incident zone, where you can change the product.

[APP–18207] You cannot unrelate product change requests from incidents in this zone

Cause: You entered No in the Select field to unassociate this product change request with the

incident.

Action: Execute a new query in this zone to verify that this product change request is no longer

available for selection since it is already related to the current incident. Move to the Related PCRs

zone and enter Yes in the Delete field if you wish to unassociate this product change request with

the incident.

[APP–18208] You cannot relate product change requests with incidents in this zone

Cause: You entered No in the Delete field to associate this product change request with the

incident.

Action: Execute a new query in this zone to verify that this product change request is no longer

related to the current incident. Move to the Product Change Request Selection Criteria zone,

execute a query, and enter Yes in the Select field if you wish to associate this product change

request with the incident.

[APP–18290] You can define only one rule per attribute for a given rule set

[APP–18300] Please enter an availability date that equals or follows the current date

[APP–18301] Please enter the next highest, unused number

[APP–18302] Please enter text for your product change request action

[APP–18303] You cannot unrelate incidents from PCRs in this zone

Cause: You entered No in the Select field to unassociate this incident with the product change

request.

Action: Execute a new query in this zone to verify that this incident is no longer available for

selection since it is already related to the current product change request. Move to the Related

Incidents zone and enter Yes in the Delete field if you wish to unassociate this incident with the

product change request.

[APP–18304] You cannot relate incidents with PCRs in this zone

Cause: You entered No in the Delete field to associate this incident with the product change

request.

Action: Execute a new query in this zone to verify that this incident is no longer related to the

current product change request. Move to the Incident Selection Criteria zone, execute a query, and

enter Yes in the Select field if you wish to associate this incident with the product change request.

[APP–18305] Please return to the previous zone to query

[APP–18306] The default value for one or more PCR attributes has expired

Cause: The default value for one or more of the following product change request attributes is

no longer valid: o Request Type o Status o Severity o Urgency &APPLICATION automatically

leaves the attribute field blank for any attribute with an expired default value.

Action: Complete one of the following steps: 1) Use the Update Personal Profile Options form

to choose a different default value for the attribute or attributes with the expired value or values,

respectively. 2) Use the Define PCR Attribute Values form to update the End Date of the expired

default value so that it remains valid.

[APP–18307] The default value for one or more action attributes has expired

Cause: The default value for one or more of the following product change request action

attributes is no longer valid: o Type o Status Oracle Customer Service automatically leaves the

attribute field blank for any action attribute with an expired default value.

Action: Complete one of the following steps: 1) Use the Update Personal Profile Options form

to choose a different default value for the action attribute or attributes with the expired value or

values, respectively. 2) Use the Define PCR Action Attribute Values form to update the End Date

of the expired default value so that it remains valid.

[APP–18309] Please enter your selection criteria in the previous zone

[APP–18309] You cannot update the product from here. Use the PCR zone instead

Cause: You tried to change the product for the current product change request. Changing the

product from the current zone is not allowed.

Action: Proceed to the Product Change Request Details zone and choose the Complete PCR

Information option. This option transfers you to the Product Change Request (PCR) zone, where

you can change the product.

[APP–18311] You cannot proceed to subsequent fields since you entered No for Publish

[APP–18312] Please enter a different sequence number

[APP–18313] You are not authorized to create new product change requests

Cause: You have navigated to this form with the intention of entering a new product change

request or you have attempted to save the information you have entered for a new product change

request.

Action: You should contact your System Administrator to obtain authorization to create new

product change requests. Or, you should use this form only to query and review or query and

update existing product change requests.

[APP–18475] Entity being used by one or more templates so you cannot inactivate

[APP–18476] You cannot delete a template having CPs and/or contacts assigned to it

Cause: You tried to delete the current access control template while there are still customer

products and or support contacts assigned to it.

Action: You should inactivate the current access control template if you longer want to use it

by entering a date in the Effective To field. If you wish to remove the template altogether, you

should first delete all customer product and support contact assignments for the template. You can

then delete the template.

[APP–18477] You cannot enter a date since the contact is not selected for assignment

Cause: You tried to enter a start date or end date for a contact type that you have not selected to

automatically assign to access control templates.

Action: Leave the Start Date and End Date fields blank.

Action: Enter Yes in the Select field to automatically assign the current contact type to

templates, then enter appropriate start and end dates to control when automatic assignment should

occur.

[APP–18478] You cannot add assignments under the current option

[APP–18479] You cannot delete assignments but you can inactivate them

[APP–18480] You have already assigned the maximum number of contacts allowed

[APP–18481] Invalid number since it is less than number of contacts already assigned

[APP–18482] Access Code has to be alpha–numeric

[APP–18483] Enter a new access code that is less than &CURRENT_CODE

[APP–18500] AutoCreate Installed Base

[APP–18501] Depot Repair Control

[APP–18502] Service Termination

[APP–18515] Synchronization process cannot obtain lock on all details Oracle Order Entry is unable

to lock all details that needto be synchronized with the demand in Oracle Inventory.Another session

is currently locking one or more of thesedetails. Please try this operation again later.

[APP–18518] Invalid Original System Reference

[APP–18519] Line cancellable statuses have changed. Please erase changes and requery.

[APP–18520] No currency conversion information available.

[APP–18521] Line has been fully Cancelled; Unable to update field.

[APP–18522] Your requested cancel quantity must be a whole number.

[APP–18524] Option &OPTION already exists in this configuration.

[APP–18525] This name is already in use in another Organization. Please choose another name.

[APP–18526] &SET_NAME already exists. Choose another name, please.

[APP–18527] Oracle Order Entry has detected an internal exception

[APP–18528] OE Transaction Manager &SERVER could not connect to database &CONNECT.

Contact your System Manager and provide complete details on how you reached this internal

exception.

[APP–18530] Could not initialize Transaction Manager.

[APP–18531] OE Transaction Manager &SERVER could not load profile options. Contact your

Oracle Support Representative and provide complete details on how you reached this internal

exception.

[APP–18536] Error initializing connection to OE Transaction Manager. This version of the client

software does not match the server’s version. The client has version &CVER, the server has version

&SVER. Contact your System Manager and provide complete details on how you reached this

internal exception.

[APP–18541] Quantity must be less than 2,100,000,000.

[APP–18542] &SEQ_NUM already exists. Choose another number, please.

[APP–18543] Please enter a valid address.

[APP–18544] Included Item Detail is incomplete. &MESSAGE

[APP–18545] Invalid Order Cycle or Currency. The order was not copied because the Order Cycle

or the Currency on the order was inactive or invalid. Please review the order.

[APP–18565] &MESSAGE

[APP–18571] Reserved Quantity should be greater than or equal to the Released Quantity

(&RELEASED_QUANTITY)

[APP–18572] The shipping security failed. Oracle Order Entry was unable to execute the shipping

security for &object, &attribute.

[APP–18573] &ITEM and &UNIT not active in &PRICE_LIST1 &ITEM and &UNIT with these

pricing attributes is not active in primary price list &PRICE_LIST1

[APP–18574] &ITEM and &UNIT not active in &PRICE_LIST2 &ITEM and &UNIT with these

pricing attributes is not in primary price list &PRICE_LIST1 and not active in secondary price list

&PRICE_LIST2

[APP–18575] &ITEM and &UNIT not active in &PRICE_LIST1 &ITEM and &UNIT with these

pricing attributes is not active in primary price list &PRICE_LIST1. Please enter price.

[APP–18576] &ITEM and &UNIT not active in &PRICE_LIST2 &ITEM and &UNIT with these

pricing attributes is not in primary price list &PRICE_LIST1 and not active in secondary price list

&PRICE_LIST2. Please enter price.

[APP–18594] &ITEM and &UNIT is not in &PRICE_LIST1

[APP–18595] &ITEM and &UNIT not on &PRICE_LIST1. Please enter price.

[APP–18598] Quantity cannot be greater than the original invoice quantity

[APP–18599] Order Import did not return the header id successfully.

[APP–18600] INTERMEDIATE_SHIP_TO_LOC

No such location in RA_ADDRESSES/RA_SITE_USES, orSITE_USE_CODE is not ”SHIP_TO”,

or status flag check failedin RA_ADDRESSES/RA_SITE_USES.

[APP–18601] ITEM_NOT_ON_PR_LIST

THE ITEM DEFINED IS NOT ON THE ORDER PRICE LIST. @PARAGRAPGEND

[APP–18602] PROJECT_ID

No such project in MTL_PROJECT_Vview.

[APP–18603] Invalid value for field SOURCE TYPE CODE.

[APP–18604] TASK_ID

No such task in MTL_TASK_V view, orproject_id was null, or project_id wasinvalid.

[APP–18605] Invalid SOURCE TYPE CODE for this inventory item on this order cycle.

[APP–18606] There is a fixed currency conversion rate between the sales order currency and the

currency of the operating unit.

[APP–18607] You are not authorized to view or enter Orders or Returns. Contact your System

Administrator.

[APP–18608] Online Order Import failed. Cannot return order number/ header id.

[APP–18609] Volume discounts may no longer apply. Reprice shipment lines if needed.

[APP–18610] Existing Schedule details for line (&line_number) will be merged so that this line can

be purchased externally. Purchase these from external source anyway?

[APP–18611] You cannot create schedule details for externally sourced items.

[APP–18612] The Order is interfaced through Release Accounting.

[APP–18613] &Purchasing Information

[APP–18614] Multiple

[APP–18615] Configurator Validation Hold applied to line &LINE_NUMBER.

[APP–18616] Configurator Validation Hold was removed for line (&LINE_NUMBER)

[APP–18617] Control Level in inventory is set to Project

[APP–18618] Control Level in inventory is set to Task

[APP–18619] Invalid value for source type code.

[APP–18620] Invalid value for source type name.

[APP–18621] This Order Cycle allows the item to be purchased only from an external source.

[APP–18622] This Order Cycle allows the item to be satisfied only from an internal source.

[APP–18623] There is no receiving location associated with this ship–to location. Please define a

receiving location in the Location form, then associate the two locations in the Customer form

Address Business Purpose Detail window.

[APP–18624] Purchase Release

[APP–18625] This line was not copied because the destination order type can only process

externally sourced items; this item cannot be purchased from an external source.

[APP–18626] The person who entered the order, &USER, is not a valid buyer.

[APP–18627] The person who entered the order, &USER, is not a valid employee.

[APP–18628] You cannot update the Source Type of a line that has shipment schedules. Update the

individual shipment schedule lines instead.

[APP–18629] Agreement &AGREEMENT has been cleared from this order since it is not valid for

the new order type &ORDER_TYPE.

[APP–18630] You may copy regular sales orders and returns only. The source order is neither a

regular sales order nor a return.

[APP–18950] You have already defined responsibilities for this service group

Cause: You selected a service group which already has service responsibilities defined for it.

Action: Please choose a different service group.

[APP–18951] You have already assigned the current user to this service group

[APP–18952] Access Codes have to be numeric

Cause: You entered a value for the access code that was non numeric

Action: Enter an access code that is numeric The value for the code should only contain

characters that are numbers The access code can be a negative number Valid characters are – 1 2 3

4 5 6 7 8 9 and 0

[APP–19002] Please remove project/task references before deleting.

Cause:

Before deleting this schedule all project and task references to it must be deleted.

Action:

You can query up all projects with references to this schedule in the Enter Projects form. To find all

task references, contact your customer support representative.

[APP–19004] This distribution rule cannot be deleted or updated

Cause:

The distribution rule is currently being used by a project of this type.

Action:

Please change the project’s distribution rule or type before deleting/updating the rule here.

[APP–19005] Segment already has a rule assigned to it

Cause:

This segment has already been assigned a rule.

Action:

Please choose another segment to assign a rule to.

[APP–19006] The assignment start date must be after the resource start date

Cause:

The assignment start date must be on or after the start date of the non–labor resource.

Action:

Please assign a start date after the start date of the non–labor resource.

[APP–19007] The End Date of the assignment must be before the resource end date

Cause:

The assignment end date cannot be after the end date of the non–labor resource.

Action:

Please enter an assignment end date prior to that of the non–labor resource.

[APP–19021] Please define your system implementation before using this window

Cause:

Your system implementation options must be set up before you can use this window

Action:

Enter system implementation options in the Define Implementation Options window

[APP–19022] Employment start date for this employee is &S_DATE; enter later date

Cause:

The date you have entered is before the employment start date for this employee.

Action:

Please enter a date later than this employment start date.

[APP–19023] Employment end date for this employee is &T_DATE; enter earlier date

Cause:

The date you have entered is after this employee’s termination date.

Action:

Please enter a date that is before this termination date.

[APP–19024] Your logon is not set up to use Oracle Projects.

Cause:

Your logon is not set up to use Oracle Projects.

Action:

Please contact your System Administrator. Additional Information for System Administrator: An

employee has not been assigned to this user logon. Please enter an employee name after querying

up this user in the Define Application User form under the System Administrator responsibility.

[APP–19025] This user is not yet registered as an employee

Cause:

Your user logon has not been attached to an employee.

Action:

Please contact your System Administrator. Additional Information for System Administrator: An

employee has not been assigned to this User logon. Please enter an employee name after querying

up this User in the Define Application User under the Administrator Responsibility.

[APP–19026] You may need to recalculate revenue for affected expenditure items

Cause:

This change may result in different revenue figures for affected expenditure items.

Action:

If you want to see this change affect existing revenue figures, you should recalculate revenue for

those items.

[APP–19040] Please enter a SQL Select Statement

Cause:

You have not entered a SQL statement for this rule.

Action:

Please enter the SQL statement that you want the rule to use in the SQL Select Statement field.

[APP–19041] This rule has been assigned to a segment. Delete assignment first

Cause:

You cannot delete a rule that has been assigned to a segment.

Action:

Use the Assign Rules form to delete the assignment. Then delete the rule.

[APP–19042] Intermediate Values must be unique

Cause:

This Intermediate Value already exists for this lookup set.

Action:

Please change it to a unique value.

[APP–19043] Please enter a constant value

Cause:

You have not entered a constant value

Action:

Enter the constant that you want the rule to return in the Constant Value field

[APP–19044] Please enter a parameter name

Cause:

You have not entered a parameter to be returned by this rule

Action:

Use QuickPick to select a parameter into the Parameter Name field that will be used by this rule

[APP–19050] You cannot delete a job if Oracle Projects is installed

Cause:

You tried to delete a job using Oracle Projects

Action:

You can deactivate the job using effectivity dates

[APP–19051] You cannot delete a hierarchy used by Oracle Projects.

Cause:

If any of the Organizations in the hierarchy you are attempting to delete have been used in Oracle

Project Accounting, they may not be deleted.

[APP–19052] You cannot delete/update link in hierarchy used by Oracle Projects.

Cause:

You cannot delete or update any hierarchy links of the organization hierarchy under the start

organization specified for use by Oracle Projects.

[APP–19054] You cannot delete a hierarchy version used by Oracle Projects.

Cause:

You have requested the deletion of the Organization Hierarchy Version.

[APP–19070] Update not allowed. &FKEY_REF are charged to this &PRJ_OR_TSK

[APP–19071] This item is an adjustment. Actions cannot be applied to adjustments.

Cause:

You can perform an action only against original items, not on their adjustments. The item you are

attempting to perform an action on is an adjustment.

[APP–19072] Tasks cannot be billed until they are ready to accrue

Cause:

You cannot authorize a task for billing if it has not been authorized for revenue accrual.

Action:

If you want to authorize this task for billing, you must choose the ’Authorize revenue accrual and

release for billing’ option.

[APP–19073] You cannot change this project when navigating from Search Projects

Cause:

You tried to select a project other than the one you are viewing when navigating from Search

Projects

Action:

Choose another project in the Search Projects window or navigate to the Enter Projects window to

select a different project

[APP–19074] Project Type cannot be changed to Indirect because it has funding

Cause:

Project Type cannot be changed to Indirect since Funding has been allocated to it

Action:

You can back out the Funding and then attempt to change the Project to Indirect

[APP–19075] Organization cannot be changed since cost/revenue/invoices exist

Cause:

You cannot change the Project Organization since the Project has costed items, revenue, or invoices

billed against it.

[APP–19076] Project type cannot be changed due to costed items/revenues/invoices

Cause:

You cannot change the project type since costed items, revenue or invoices exist. You can change

the project type only if there are no processed transactions against the project.

[APP–19077] You cannot use this option when navigating from Search Projects

Cause:

You tried to use an option when navigating from Search Projects

Action:

You may enter the window directly in order to use this option.

[APP–19078] Project Customer cannot be removed; converted items exist.

Cause:

You may not remove the project customer because converted, revenue distributed expenditure items

exist. Oracle Projects does not allow customer changes for projects with converted items that are

revenue distributed.

[APP–19079] Paying project customers cannot be added; converted items exist.

Cause:

You may not add any paying project customer because converted, revenue distributed expenditure

items exist. Oracle Projects does not allow customer changes for projects with converted items that

are revenue distributed.

[APP–19080] You cannot add paying project customers; there is invoice activity.

Cause:

You cannot add paying project customers because there is invoice activity. Oracle Projects requires

that all project invoice history reflect the customer bill split. Adding a paying customer at this stage

would violate this rule.

[APP–19081] Billing contribution cannot be updated; converted items exist

Cause:

You may not update the billing contribution because converted expenditure items exist.

[APP–19082] Billing contribution cannot be updated; there is invoice activity

Cause:

Billing contribution may not be updated because there is invoice activity against this project.

Updating the billing contribution could cause data inconsistencies.

[APP–19083] Update not allowed; funding, draft revenue, or invoices exist

Cause:

Update is not allowed since related funding, draft revenue, or draft invoices exist.

[APP–19084] You cannot change the distribution rule; unearned revenue exists

Cause:

You cannot change the distribution rule because the project has Unearned Revenue.

[APP–19085] The expenditure item dates of the items to be transferred fall outside of the effective

dates of the destination project or task

Cause:

The expenditure item date is outside the effective dates of the project or task to which you are

transferring items.

Action:

If you wish to transfer this item to this project/task, you will need to change the effective dates of

the project/task.

[APP–19086] Billing contact not defined for each paying project client.

Cause:

Each paying client must have a billing contact in order to authorize this project for revenue accrual

or billing

Action:

Please enter billing contacts for each paying client of this project

[APP–19087] The billing allocation across project client(s) is incomplete

Cause:

The billing contributions for all customers of this project do not add up to 100%.

Action:

Please alter billing contributions or add customers to enable the billing contribution across this

project’s customers to sum to 100%.

[APP–19088] All mandatory class categories have not been classified.

Cause:

All mandatory class categories must be classified before this project can be authorized.

Action:

Please enter class code(s) for each mandatory class category.

[APP–19089] A project manager is not currently defined for this project

Cause:

A Project must have an active Project Manager in order to be authorized for distribution.

Action:

Please enter an active Project Manager for this project.

[APP–19090] Completion date must be later than all task completion dates

Cause:

A project completion date cannot be earlier than the completion date of any of its tasks

Action:

Change the completion date of all tasks to be earlier than this date or change the project completion

date to a later date

[APP–19091] Start date must be earlier than all task start dates

Cause:

A project cannot have a start date that is later than the start date of any of its tasks.

Action:

Change the task start dates to be later than this date or choose an earlier start date for the project.

[APP–19092] Cannot delete AutoAccounting code; expenditure items exist

Cause:

Costed expenditure items exist for this project. You cannot delete the AutoAccounting Code.

[APP–19093] Sum of dated billing events ($&EAMT) not equal to draft revenue budget

Cause:

For an Event billing Project, the sum of the billing events with completion dates must equal the

revenue budgeted for the project.

Action:

Change the events with completion dates so that the sum adds up to budgeted revenue.

[APP–19094] You must choose a job and/or billing title override

Action:

You must choose a job and/or billing title override for this employee.

[APP–19095] You do not have authorization to update information for this project

Cause:

Only project key members for this project or Cross–Project users can update project information.

Action:

In order to update information for this project, you must be added as a project key member, or you

must log in as a Cross–Project user.

[APP–19096] You do not have authorization to see details of this project or task

Cause:

Only project members or cross project users are authorized to see project or task details.

Action:

If you wish to see details, you must be defined as either a key member for this project a cross

project user.

[APP–19097] Only project members can authorize distribution

Cause:

Only project key members or Cross–Project users can authorize distribution for a project.

Action:

If you wish to authorize distribution for this project, you must be added as a project key member, or

you must log in as a Cross–Project user.

[APP–19098] There is no draft cost budget

Cause:

No draft cost budget exists.

Action:

Create a non–zero draft cost budget for this project before attempting to authorize distribution.

[APP–19099] You can use the customer QuickPick only if a project customer exists

Cause:

There are no customers set up for this project.

Action:

You need to set up project customers before you can use this QuickPick.

[APP–19100] This override requires an employee name or source organization

Cause:

You entered an override without entering an employee name or source organization.

Action:

You must enter either an employee name or a source organization.

[APP–19101] Only one billing contact can be entered for this customer/project

Cause:

You tried to define more than one billing contact for this project customer. Only one billing contact

can be defined for each project customer.

Action:

You can define other contact types using the Define Contact Types form.

[APP–19102] Only one default distribution rule is allowed for each project type

Cause:

A maximum of one default distribution rule is allowed for each project type.

[APP–19103] Resetting Expenditure items/Events for Revenue Distribution...

Cause:

This action causes associated Expenditure items and Events to be reset for Revenue Distribution.

[APP–19104] Warning: Update has caused a hold on revenue accrual for the Project

Cause:

Update has caused a hold on revenue accrual for this Project.

Action:

To remove the revenue accrual hold, you must re–authorize the project for revenue accrual.

[APP–19105] Task is not chargeable; project has no AutoAccounting class code

Cause:

Task set to ’Not Chargeable’ since this project does not have a class code required by

AutoAccounting.

Action:

If a class category and class code are required by AutoAccounting, you must define the appropriate

project information in the Classifications zone.

[APP–19106] You do not have authorization to transfer items to this project

Cause:

Only active project key members or Cross–Project users may transfer items into the target project.

Action:

Please transfer into a project for which you are a project key member or log in as a Cross–Project

user to transfer the item.

[APP–19107] You cannot edit the expenditure comment in this form.

Cause:

You can only modify expenditures in the Adjust Project Expenditures form.

Action:

Navigate to the Adjust Project Expenditures form to modify the expenditure.

[APP–19107] You may not request an Action; use Adjust Project Expenditures

Cause:

You can request an action only in the Adjust Project Expenditures form.

Action:

Navigate to the Adjust Project Expenditures form to perform the action you want to take.

[APP–19108] No items have been found which are eligible for transfer

Cause:

To be transferred to another task, an item may NOT be: already a member of the destination task,

already transferred to another task, a vendor invoice item, an adjustment item, a fully reversed

expenditure item, or a converted item

Action:

Please check for the above conditions.

[APP–19111] Chargeable status not allowed; no AutoAccounting code for project

Cause:

The project has no Autoaccounting class categories defined

Action:

Set up the required AutoAccounting class categories for the project in the Classification zone of the

Enter Projects window

[APP–19112] Total unprocessed writeoff may not exceed the Unbilled Receivables

Cause:

Your total unprocessed revenue writeoffs will exceed your unbilled receivables

Action:

To write off revenue you must increase your unbilled receivables by accruing more revenue or

reducing the invoiced amount

[APP–19113] Project does not exist in Compensation Rule Sets. Option unavailable.

Cause:

Your project does not exist in Compensation Rules.

Action:

You must set up your project in the Define Compensation Rules form in order to enter Labor Cost

Multipliers for tasks.

[APP–19114] You do not have authorization to modify revenue adjustment events

Cause:

To modify revenue adjustment events you must be a project key member or a cross–project user

[APP–19140] Please enter a unique agreement type and number for this customer

Cause:

An agreement already exists for this customer with the same agreement type and agreement number.

Action:

Please enter a unique agreement type and number combination for this customer.

[APP–19141] The revenue limit must be greater than or equal to amount allocated

Cause:

You cannot reduce the revenue limit amount to less than the amount already allocated

Action:

Update the revenue limit amount to an amount greater than the amount already allocated or reduce

the amount allocated to projects

[APP–19142] Total amount allocated cannot be less than amount accrued or billed

Cause:

Total amount allocated is less than amount already accrued and/or billed.

Action:

You must allocate enough funds to cover the revenue which has already been accrued and/or billed

against the allocated funding.

[APP–19143] This is a parent organization of an existing budget organization

Cause:

You cannot enter multiple budget items for organizations from the same branch of the organization

hierarchy. This would result in duplicate reporting of those organizations.

Action:

Enter an organization which does not fall in the same hierarchy as any organization already entered

as a budget item for this project/task.

[APP–19144] Transaction rolled back –– unable to update project information

Cause:

Could not update project information due to a lock on the relevant row in the Projects table.

Action:

Try again later. If error persists, ask your system administrator to resolve the problem.

[APP–19145] No update is allowed because a budget has been defined at a higher level

Cause:

A budget has been defined at a higher WBS level

Action:

If you wish to create a budget at this level, first clear the higher level budget

[APP–19146] Total percentage for each Revenue credit type for AR Transfer must be 100%

Cause:

You have made a modification to a credit receiver. As a result, the total percentage for one of the

Revenue credit types for Transfer to AR does not equal 100%.

Action:

Modify other active records of the same credit type to ensure that the total percentage for Transfer

to AR equals 100%.

[APP–19147] You cannot delete this credit receiver because draft invoices exist

Cause:

After invoices have been created for a project, credit receivers cannot be deleted for the project

Action:

You can deactivate this credit receiver by entering a date in the End Date field

[APP–19148] You cannot delete this credit receiver because draft revenue exists

Cause:

After revenue has been generated for the project, credit receivers cannot be deleted for the project

Action:

You can deactivate a credit receiver by entering a date in the End Date field

[APP–19149] This number already exists. Choose a unique budget line item number.

Cause:

You have attempted to create a budget item which has the same line number as an existing item.

Action:

Change the line item number.

[APP–19150] A budget already exists for this project and task

Cause:

The combination of project and task which you have entered already exists for this budget.

Action:

If modifications are required to the budget,

query the existing budget and modify it.

[APP–19151] Please enter a unique category or job for each budget line item

Cause:

You have attempted to enter a budget item which uses the same Expenditure Category/Type,

Revenue Category, or Job as a budget item which already exists.

Action:

Enter a unique combination or add your changes to the existing budget item.

[APP–19152] You have entered a duplicate credit type for an employee

Cause:

You have attempted to create a credit type for an employee when the same credit type already exists

in an active state.

Action:

You can either modify the existing record or deactivate it and enter a new record. Deactivate the

existing record by entering an end date.

[APP–19153] Allocated fixed fee must be greater than or equal to accrued

Cause:

The Fixed Fee allocated for this project or task is less than what has been accrued.

Action:

You must allocate enough funding to cover the fixed fee which has already been accrued against the

baseline budget. The fixed fee accrued against the baseline budget is shown in the Agreements

zone.

[APP–19154] You cannot delete an agreement after funds have been allocated for it

Cause:

You can only delete an agreement if no funds have been allocated from it. This rule applies even if

the funds have been reversed.

[APP–19155] Please enter a value other than zero

Cause:

When allocating funding to a direct project or task, the amount allocated cannot be zero.

Action:

Please enter either a positive or a negative value or erase the row.

[APP–19156] Warning: Receiver must be a designated salesrep

Cause:

Credit receivers for the credit type QuotaCredit must be designated as Sales Representatives in

Oracle Receivables.

Action:

Enter the credit receiver as a Sales Representative in Oracle Receivables.

[APP–19157] You must enter an expenditure category for this budget item

Cause:

If you have chosen an expenditure type for a budget item, an expenditure category must also be

entered.

Action:

If you choose the expenditure type using QuickPick, the appropriate category will automatically be

selected.

[APP–19158] Ready to Baseline is required for draft budgets

Cause:

Ready to Baseline is a required field for draft budgets.

Action:

Enter a value of Yes or No in the Ready To Baseline field. Enter Yes in the Ready To Baseline field

if you are ready to baseline the draft budget.

[APP–19159] You must be a project member to enter or modify the budget

Cause:

A budget can be queried or examined by any user, but modifications to budgets and their associated

budget items can only be made by project members or cross project users.

Action:

Contact a project member or cross project user to create you as a project member or ask them to

make the change.

[APP–19160] This budget is not ready to be baselined

Cause:

This budget is not ready to baseline since its ”Ready to Baseline” flag is set to No.

Action:

Set the flag to Yes for the Draft budget in the Enter Budgets form.

[APP–19161] Warning: You cannot modify Baseline or Original budgets

Cause:

Baseline budgets cannot be modified directly. Original budgets can never be modified.

Action:

If you wish to change the baseline budget, change the budget status from Baseline to Draft, ensure

funding is correct, and baseline this budget again. The new budget will replace your existing

baseline budget.

[APP–19162] You cannot update the customer after funds have been allocated

Cause:

After the customer’s funds have been allocated to projects, you cannot update the customer.

Action:

If you wish to change a customer’s funding on a project, or add a new customer, you must back out

the funds from the existing agreement and create a new agreement for the new customer to fund the

project.

[APP–19163] You cannot enter budget items for this budget

Cause:

You cannot enter budget items for this budget because amounts exist at the subbudget level.

Action:

Clear the amounts at the subbudget level before attempting to enter budget items.

[APP–19164] You must clear the project budget before entering a task budget

Cause:

You cannot enter a task level budget because project level amounts exist.

Action:

Clear the project level amounts before attempting to enter a task level budget.

[APP–19165] Project level funding is not allowed because task level funding exists

Cause:

You attempted to allocate funds at the task level when funds have already been allocated at the

project level. For each project, funding can only be allocated at either project or task level.

Action:

You must either fund at the project level or back out the existing project level funding and fund at

the task level.

[APP–19166] Credit receivers can be created only at the project level

Cause:

Funds have already been allocated to this project at the project level. Credit receivers can be

created only at the level at which funding has been allocated.

[APP–19167] You cannot update this amount

Cause:

You cannot update amounts at this level because amounts have been defined at the budget item level

Action:

Update amounts at the budget item level by choosing the appropriate cost breakdown code and

entering budget items in the Budget Item zone

[APP–19168] You cannot update this budget amount, because it consists of multiple amounts from

lower level tasks.

Cause:

You can update budget amounts only at the task level at which they were originally entered.

Action:

You may update budget amounts by drilling down to the task level at which they were originally

entered.

[APP–19169] You cannot allocate funds at the task level, because funds have already been allocated

at the project level.

Cause:

You attempted to allocate funds at the task level when funds have already been allocated at the

project level. You cannot allocate funds at both the task level and the project level for any given

project.

Action:

You can either allocate funds at the project level, or back out all project level allocations and

re–allocate funds at the task level.

[APP–19170] You can create credit receivers for this project only at the task level.

Cause:

You must allocate funds and create credit receivers for a project at the same level, either the task or

project level. Task level funding for this project already exists.

[APP–19171] You have allocated more funds than your revenue limit allows.

Cause:

When allocating funds to the current project, you have entered an amount greater than the Amount

Not Allocated shown at the top of the window.

Action:

The figures show a negative amount. Reverse the amount you entered by entering a corresponding

negative amount.

[APP–19172] A budget item organization from the same branch of the organization hierarchy

already exists.

Cause:

You cannot enter multiple budget item organizations from the same branch of the organization

hierarchy. This would result in duplicate reporting of those organizations.

Action:

Enter an organization that does not fall in the same hierarchy branch as any organization already

entered as a budget item organization for this project/task.

[APP–19173] You cannot update the Agreement Number because draft invoices referencing this

agreement number already exist.

[APP–19210] You cannot delete an expenditure group that contains expenditures with adjusted

expenditure items.

[APP–19211] You cannot delete an expenditure that contains adjusted expenditure items.

[APP–19212] You cannot approve draft revenue/invoices for a project with a status of Closed.

Cause:

If a project is closed, you cannot charge new transactions to it or approve revenue or invoices for it.

You can only run costing for uncosted transactions that have already been charged to the closed

project.

Action:

If you wish to approve revenue or invoices for a closed project, change the project status to Active.

[APP–19213] The Running Count does not equal the Control Count.

Cause:

The sum of all items entered does not equal your control total.

Action:

Ensure that all items have been entered with correct amounts and add up to the control total.

[APP–19215] A timecard for this employee and expenditure period already exists

Cause:

You cannot enter more than one timecard for an employee for a given expenditure period.

Action:

If you wish to make changes or additions to your existing timecard, query your existing timecard

and make the appropriate changes.

[APP–19216] You have entered duplicate expenditure items on a single timecard.

Cause:

You have entered expenditure items with the same project, task, expenditure type, employee, date,

and quantity information in a single timecard.

Action:

A timecard cannot contain duplicate expenditure items. Delete or revise one of the duplicate

expenditure items.

[APP–19217] This employee has no effective hourly cost rate.

Cause:

Either a cost rate has never been entered for this employee, or none of the employee’s cost rate are

effective as of the expenditure item date.

Action:

Ask your System Administrator to enter an hourly cost rate for this employee for the period covered

by the timecard in the Define Labor Cost Rates window.

[APP–19218] You cannot approve draft revenue/invoices for an inactive customer.

Cause:

You cannot approve draft revenue/invoices for an inactive customer.

Action:

Change the customer’s status to Active in the Oracle Receivables Customer Maintenance window.

You can then approve draft revenue/invoices for the customer in Oracle Projects.

[APP–19219] No approved expenditure item can be found for this adjustment.

Cause:

To adjust an approved expenditure item, you must identify the expenditure item by the following

information: expenditure item date, employee (if applicable), expenditure type, non–labor resource

(if applicable), and project and task. No approved expenditure item with the information entered

could be found.

Action:

Please verify that you have entered the correct information identifying the expenditure item to be

adjusted and revise, if necessary.

[APP–19221] You cannot delete expenditure items from approved expenditures

Cause:

You cannot revise or delete any expenditure item included in an approved expenditure.

Action:

To make adjustments to an approved expenditure, enter a new pre–approved expenditure batch with

expenditure items partially or fully reversing the items to be adjusted.

[APP–19222] You cannot delete pre–approved timecard information using this window

Cause:

You cannot delete pre–approved timecards using the Enter Timecards window.

Action:

You can make changes to pre–approved timecards using the Enter Pre–Approved Timecards

window. If the timecard is not approved, you can delete the timecard through the Enter

Pre–Approved Timecards window. If the timecard is approved, you can reverse it by entering a new

timecard with reversing items. If it is submitted, change the status back to Working and then delete

the timecard.

[APP–19223] You cannot delete this timecard item, because its labor cost has already been

distributed

Cause:

Since costs have been distributed, you may not delete this timecard item.

Action:

You need to enter pre–approved reversing entries to back out all items entered in the original

timecard.

[APP–19224] You cannot delete submitted or approved timecards

Cause:

You cannot delete timecards with a status of Submitted or Approved.

Action:

If the timecard has not yet been approved, use the Rework Routing Action to delete the timecard. If

it has been approved, contact your Expense Administrator regarding entering a pre–approved

expenditure to reverse all the expenditure items in the timecard.

[APP–19225] You may not delete expenditure items from a submitted expenditure batch

Cause:

You may not delete expenditure items from an expenditure batch once it has been submitted.

Action:

Change the expenditure batch status to Working and then delete expenditure items, as necessary.

[APP–19226] This employee has no effective employee assignment as of this expenditure item date

Cause:

This employee has no effective organization and job assignment as of this expenditure item date.

Action:

Enter an organization and job assignment for this employee for this expenditure item date in the

Assign Employees or Enter Employees window.

[APP–19227] You cannot release an expenditure batch that contains no expenditures

Cause:

You can release an expenditure batch only if contains expenditures.

Action:

Enter expenditures against this expenditure batch before attempting to release it.

[APP–19228] You cannot add an expenditure to a released or submitted expenditure batch

Cause:

You cannot add an expenditure to an expenditure batch with a status of Released or Submitted.

Action:

You will have to create a new expenditure batch to enter the expenditure.

[APP–19229] You cannot add a new expenditure item to an approved expenditure batch

Cause:

You cannot add a new expenditure item to an expenditure batch with a status of Approved.

Action:

Create a new expenditure batch to enter the expenditure item.

[APP–19230] You may not add information to a pre–approved timecard from this window.

Cause:

You may not add information to a pre–approved timecard using the Enter Timecards window.

Action:

You must use the Enter Pre–Approved Timecards window to revise pre–approved timecards.

[APP–19231] You cannot add expenditure items from this window

Cause:

You cannot add expenditure items using the Release Pre–Approved Expenditure window.

Action:

Add new expenditure items using the Enter Pre–Approved Expenditures window.

[APP–19232] You cannot add expenditure items to a submitted or approved timecard

Cause:

You cannot add expenditure items to a timecard with a status of Submitted or Approved.

Action:

If the timecard is submitted, change the status to Working and then add expenditure items. If it is

approved, you will need to make adjusting entries.

[APP–19233] You cannot add expenditure items to a submitted expenditure batch

Cause:

You cannot add expenditure items to an expenditure batch with a status of Submitted.

Action:

Change the expenditure batch status to Working and then add expenditure items.

[APP–19234] This employee has no active primary organization assignment as of this expenditure

item date

Cause:

This employee has no active primary organization assignment as of this expenditure item date.

Action:

An organization assignment must be entered for this employee as of this expenditure item date in

the Assign Employees window.

[APP–19235] A source timecard for Copy Timecard was not found

Cause:

There is no timecard for the previous expenditure period that you can copy.

Action:

You must enter a timecard for the previous expenditure period before you can copy it.

[APP–19236] You cannot revise expenditure items in a submitted or approved timecard.

Cause:

You cannot revise expenditure items in timecard with a status of Submitted or Approved.

Action:

If the timecard status is Submitted, change the status to Working and then revise the expenditure

items, as necessary. If the status is Approved, you cannot revise any expenditure items in the

timecard.

[APP–19237] You cannot revise expenditure items in a submitted expenditure group

Cause:

You cannot revise expenditure items in an expenditure group with a status of Submitted.

Action:

Change the expenditure batch status to Working before attempting to revise its expenditure items.

[APP–19238] You must submit the expenditure batch before releasing it

Cause:

You can release an expenditure batch only if it has a status of Submitted

Action:

Change the status of this expenditure batch to Submitted in a pre–approved expenditure entry form

before attempting to release it.

[APP–19239] The employee organization is not in the hierarchy

Cause:

The organization to which this employee is currently assigned is not in the Project Organization

Hierarchy.

Action:

Either reassign this employee to an organization in the hierarchy, or enter the employee’s

organization into the hierarchy.

[APP–19240] You cannot enter an expenditure ending date that occurs after the expenditure batch

ending date

Cause:

The Expenditure Ending Date must fall between the beginning and ending dates for the expenditure

batch.

Action:

Enter an Expenditure Ending Date that falls between the beginning and ending dates for the

expenditure batch.

[APP–19241] You cannot charge expenditure items to a closed project

Cause:

You cannot charge expenditure items to a project with a status of Closed.

Action:

If you wish to charge against this project for this date, you must change the project status to Active.

[APP–19242] The expenditure item date is not within the active dates of the project

Cause:

All expenditure items charged to a project must fall within the active dates of the project.

Action:

If you wish to charge against this project for this date, change the expenditure item date to a date

within the project start and end dates, or change the project’s start or end date to include the

expenditure item date.

[APP–19243] You must reverse the exact amount of the original item

[APP–19244] The Expenditure Control Total does not equal the Running Total

Cause:

The Expenditure Control Total does not equal the Running Total.

Action:

Verify that expenditure entries have been entered correctly.

[APP–19245] The Running Total does not equal the Control Total

Cause:

The Running Total does not equal the Control Total of the expenditure batch.

Action:

Recheck your entries. If the Control Total is incorrect, correct it before submitting the expenditure

batch.

[APP–19246] You cannot delete a submitted timecard

Cause:

You cannot delete a timecard with a status of Submitted.

Action:

Update your Working, Reworking, or Rejected Timecard, or contact your Expense Administrator

regarding adjusting your timecard.

[APP–19247] No timecards were processed

Cause:

The action you requested could not be executed for any timecards or associated Expenditure

Routing information satisfying the criteria.

Action:

If you are either Forwarding with Approval or Approving timecards, check your Authorization

Limit against the totals displayed for the timecards. Otherwise, contact your System Administrator.

[APP–19248] You may not revise the Expenditure Ending Date, because items for this expenditure

already exist.

[APP–19249] The expenditure item date is not within the expenditure period

Cause:

The expenditure item date must fall within the Expenditure Period.

[APP–19253] You may not delete this expenditure item, because its cost has already been

distributed

Cause:

You cannot delete expense report items once their costs have been distributed.

Action:

Contact your Expense Administrator to discuss entering a reversing entry through the Enter

Pre–Approved Expense Reports window.

[APP–19254] You cannot delete expenditure items from a submitted or approved expense report

Cause:

You may not delete expenditure items from an expense report with a status of Submitted or

Approved.

Action:

If the expense report has not yet been approved, use the Rework Routing Action to delete it. If it

has been approved, contact your Expense Administrator regarding entering a reversing entry

through the Enter Pre–Approved Expense Reports window.

[APP–19255] You cannot add expenditure items to a submitted or approved expense report

Cause:

You cannot add expenditure items to an expense report with a status of Submitted or Approved.

Action:

If the expense report is Submitted, change the status to Working and then add expenditure items, as

necessary. If it is Approved, you need to make adjusting entries.

[APP–19256] A source expense report for Copy Expense Report was not found

Cause:

There is no expense report for the previous period to copy.

Action:

You must enter an expense report for the previous period before you can copy it.

[APP–19257] You cannot revise expenditure items in a submitted or approved expense report

Cause:

You cannot revise expenditure items in an expense report with a status of Submitted or Approved.

Action:

If the expense report is Submitted, change the status to Working and then revise the expenditure

items, as necessary. If the status is Approved, you need to enter an adjusting entry in the Enter

Pre–Approved Expense Reports window.

[APP–19258] You cannot delete pre–approved expense reports using this window.

Cause:

You cannot delete pre–approved expense reports using this window.

Action:

Use the Enter Pre–Approved Expense Reports window to delete a pre–approved expense report.

[APP–19259] You cannot delete a submitted expense report

Cause:

You cannot delete an expense report with a status of Submitted.

Action:

Contact your Expense Administrator regarding adjusting your expense report using the Enter

Pre–Approved Expense Reports window.

[APP–19260] You may not add expenditure items to a pre–approved expense report from this

window

Cause:

You may not add expenditure items to a pre–approved expense report using the Enter Expense

Reports window.

Action:

Use the Pre–Approved Expense Reports window to revise pre–approved expense reports.

[APP–19261] The expenditure items from the selected expense report were not copied

Cause:

The process was unable to create new expense report items by copying expenditure items from a

selected expense report.

Action:

Contact your System Administrator.

[APP–19262] The expenditure items from the selected timecard were not copied

Cause:

The process was unable to create new timecard items by copying the expenditure items from the

selected timecard.

Action:

Contact your System Administrator.

[APP–19263] No expense reports were processed

Cause:

The Action you requested could not be executed for any expense reports or associated Expense

Report Routing information satisfying the criteria.

Action:

If you chose Forwarding with Approval or Approving, check your Authorization Limit against the

totals displayed for the Expense Report. Otherwise, contact your System Administrator.

[APP–19265] WARNING: An expense report for this employee and expenditure period already

exists

Cause:

An expense report for this employee and expenditure period already exists.

Action:

You can record multiple expense reports for the same period if you are routing expense reports to

different organizations. You can query your existing Expense Report(s) in View Expense Reports

and Enter Expense Reports to determine if an additional expense report for this period is

appropriate.

[APP–19267] A project–level expenditure transaction control has been violated

[APP–19268] A task–level expenditure transaction control has been violated

[APP–19269] The expenditure item date is not within the active dates of the task

[APP–19270] The task is not chargeable

[APP–19271] The specified project does not exist

[APP–19272] The specified task does not exist

[APP–19273] Project/Task validation error. Contact your support representative

[APP–19274] An Expenditure Transaction Control is already recorded for this date

[APP–19275] You may not delete adjusted expenditure items.

Cause:

Deleting this expenditure item will cause the corresponding reversing entries to point to a

non–existent expenditure item.

Action:

To delete this expenditure item, you must first delete this item’s reversing entries.

[APP–19277] This item requires a valid quantity

[APP–19278] Update not allowed. Please delete this adjustment and re–enter.

[APP–19310] You must enter an accrue through date to regenerate draft revenue

Cause:

An accrue through date is required for generating draft revenue.

Action:

All eligible expenditure items with a date before the accrue through date will accrue revenue. All

eligible events with a completion date before the accrue through date will also accrue revenue.

[APP–19311] You cannot cancel this invoice; cash has been applied against it

Cause:

You cannot cancel an invoice that has cash applied against it in Oracle Receivables.

Action:

You can undo the cash application in Oracle Receivables and then cancel the invoice.

[APP–19312] You cannot cancel this invoice; crediting invoices exist

Cause:

You cannot cancel an invoice if credit memos have been processed against it.

[APP–19313] You must enter the invoice date before releasing the invoice

Cause:

An invoice date is required before you can release an invoice.

Action:

Enter an invoice date before attempting to release the invoice.

[APP–19314] You must enter the AR Invoice Number before releasing the invoice

Cause:

An AR Invoice Number is required before you can release an invoice.

Action:

Enter the AR Invoice Number before releasing this invoice.

[APP–19315] Only an active project member or cross–project user can update draft invoices

[APP–19316] You cannot release an invoice that has not been approved or has already been released

Cause:

You cannot release an invoice with a status of Unapproved or Released.

Action:

If the invoice is Unapproved, it must be approved before you can release it. If it is Released, the

invoice is already in its final state and may not be updated.

[APP–19317] You must enter a bill through date to regenerate a draft invoice

Cause:

Bill through Date is a required field.

Action:

Enter a date through which to invoice items.

[APP–19318] Invoice item details only exist for payment schedule events

Cause:

Invoice item details only exist for payment schedule events. These are the only events that are

FIFO marked against expenditure items.

Action:

You can view details for invoices based on expenditure items or Schedule Payment events, and not

for any other event types.

[APP–19319] No invoice items were found for this invoice

Cause:

This invoice has no invoice items. This may be due to an error in invoice generation.

Action:

Regenerate the invoice after reviewing and trying to resolve the generation error. Call your

Customer Support Representative.

[APP–19320] No draft invoices pending or rejected

Cause:

There are no previous pending or rejected draft invoices. The Invoice Generation Program will

create an Invoice if there are any unprocessed eligible items or events.

[APP–19321] You cannot update the invoice date from this window.

Cause:

You cannot update the invoice date from this window.

Action:

Use the Release Invoices window to update the invoice date.

[APP–19322] Update not allowed – the invoice is not released or is already transferred

Cause:

You can update this invoice only if it has a status of Released.

Action:

If the invoice is not yet released, you can update this field after the invoice is released. If it has

been transferred, you may not update the record.

[APP–19323] You may not update the automatically generated Invoice Number

Cause:

You may not update the automatically generated Invoice Number.

Action:

If you wish to update invoice numbers, change the Implementation Options to allow manual invoice

numbering.

[APP–19324] You cannot update the invoice number from this window

Cause:

You can only update the invoice number using the Release Invoice window.

Action:

If your Implementation Option allows manual invoice numbers, you can update the invoice number

using the Release Invoice window.

[APP–19325] Update not allowed; the invoice is not released or is already transferred

Cause:

You can update this invoice only if it has a status of Released.

Action:

If the invoice is not yet released you can update this field after it is released. If it has been

transferred you may not update the record.

[APP–19326] You must enter a unique AR invoice number

Cause:

The AR Invoice Numbers must all be unique.

Action:

Please enter a unique AR Invoice Number.

[APP–19327] Write–off amount must be <= uncredited invoice amount : &BALANCE

Cause:

Write–off amount must not exceed the Uncredited Invoice Amount. You may only write off the

remaining invoice amount.

Action:

Reduce write–off amount to less than the Uncredited Invoice Amount.

[APP–19328] Write–off amount must not exceed the unpaid receivable.

Cause:

Write–off amount must not exceed the unpaid receivable amount. You may only write off an

amount that has not already been paid in Oracle Receivables.

Action:

If you wish to write off an amount greater than your existing unpaid receivable, you will have to

unapply cash in Oracle Receivables before doing the write–off.

[APP–19330] You cannot process draft revenue/invoices for an inactive customer.

Cause:

You cannot process draft revenue/invoices for inactive customers.

Action:

Use Oracle Receivables to change the customer status to active.

[APP–19331] You cannot have zero Project and Task level Funding.

Cause: You cannot have zero Project and Task level Funding.

Action: Use the Enter Agreements window to create either zero Project level Funding or zero

Task level Funding.

[APP–19332] Cannot delete Credit Receiver

Cause: Sales Credits for this Credit Receiver have been interfaced to AR

Action: You may turn off the Transfer To AR flag to prevent further credits from being

interfaced to AR.

[APP–19333] You cannot update this field for processed events

[APP–19334] Task funding with project level events is not allowed.

Cause: With task level funding, you may create only task level events.

Action: If you want to create project level events or have existing project level events, change

the funding to project level.

[APP–19335] &FIELD must be entered for this billing extension

[APP–19336] Delete not allowed. Automatic events have been generated

[APP–19337] This billing extension is already active at the project level

[APP–19338] This billing extension is already active at the task level

[APP–19339] You cannot update or delete a processed AUTOMATIC event

[APP–19340] You must specify at least one usage for this override schedule

[APP–19341] Update not allowed. Revenue–distributed items exist

[APP–19342] Date ranges between revisions must be continuous

[APP–19343] You cannot delete override schedules referenced by expenditure items

[APP–19344] Update not allowed. Override revisions exist

[APP–19345] A schedule is already in use for &TYPE

[APP–19346] Delete not allowed; revision date ranges must be continuous

[APP–19347] This Burden Cost Code is already defined for the revision

[APP–19400] Project number cannot be blank.

[APP–19401] Task number cannot be blank.

[APP–19402] Expenditure type cannot be blank

[APP–19403] Organization cannot be blank

[APP–19404] GL Date cannot be blank

[APP–19405] Direct cost cannot be blank

[APP–19407] A Burden schedule is not defined for the given expenditure combination.

[APP–19408] An appropriate cost base has not been defined.

[APP–19409] The burden schedule revision is not compiled.

[APP–19410] A compiled multiplier has not been defined for the revenue burden schedule.

[APP–19411] A compiled multiplier has not been defined for the invoice burden schedule.

[APP–19412] Cost base cannot be blank.

[APP–19413] This cost base and cost base type combination already exists.

[APP–19414] Cost base type cannot be blank

[APP–19415] Start date cannot be blank.

[APP–19417] This cost base has already been costed.

[APP–19418] There are expenditure types associated with this cost base.

[APP–19439] Cannot define a new assignment for a terminated employee.

Cause:

Start date for assignment was after the termination date of the employee.

Action:

Enter a start date for the assignment that is earlier than the termination date of the employee.

[APP–19440] You cannot create related items for a related item

[APP–19441] This adjustment action is not allowed on related items

[APP–19442] This field is not updatable for related item reversals

[APP–19443] You cannot delete a related item adjustment

[APP–19444] This adjustment action is not allowed on fully reversed items

[APP–19447] This period contains project–related supplier invoices in Oracle Payables that are not

interfaced to Oracle Projects. To identify the exceptions, run the Transaction Exception reports. Do

you want to close the period?

[APP–19449] You cannot close this period because it contains revenue distribution lines that are not

interfaced to GL. You must run the EXC: Transaction Exceptions reports to identify the transactions

that are preventing the period from being closed.

[APP–19450] Asset number conflicts with the Automatic Numbering in Oracle Assets.

[APP–19451] This asset has been capitalized. You may not update this field.

[APP–19452] Date Placed In Service is in a future Oracle Assets period. The asset may be rejected

during the interface process.

[APP–19453] The asset cannot be placed into service until the following attributes are entered:

&FIELDS_TO_COMPLETE

[APP–19454] Cannot obtain Oracle Assets installation information.

[APP–19455] Setup information is missing.

[APP–19456] System Error: A null lookup type parameter was passed to PAXSULKP.

[APP–19457] System Error: An invalid lookup type parameter was passed to PAXSULKP.

[APP–19458] Error occurred during auto–generation of Project Number.

[APP–19459] Revenue has not been distributed.

[APP–19460] The Resource List Assignment was not found.

[APP–19461] The Use Code was not found.

[APP–19462] No valid formats found for this resource.

[APP–19463] Error generating resource list ID

[APP–19464] Unclassified resource does not exist in PA_RESOURCES table.

[APP–19465] This window cannot be executed independently.

[APP–19466] The Project ID passed to this form is not valid.

[APP–19467] Cannot delete Resource Group because Resources exist.

[APP–19468] You cannot transfer an item between projects with different classes.

[APP–19469] You are not authorized to transfer items to this task.

[APP–19470] You cannot perform this action on an item which has not been approved.

[APP–19471] Your job submission failed. Check the View Requests form to get more information.

[APP–19472] You must query expenditure items in order to reverse them.

[APP–19473] A different resource list is used in the baselined budget. You cannot change the

resource list for a baselined budget.

[APP–19474] There is an error in the burdened cost budget calculation client extension. Error

number &&ERRNO: &ERRMSG.

[APP–19475] There is an error in the raw cost budget calculation client extension. Error number

&&ERRNO: &ERRMSG.

[APP–19476] There is an error in the revenue budget calculation client extension. Error number

&&ERRNO: &ERRMSG.

[APP–19477] You must create and baseline a cost budget for a project using cost as the revenue

accrual method, before the revenue budget can be created.

[APP–19478] System Error: Cannot find accumulation period type in PA_IMPLEMENTATIONS.

[APP–19479] System Error: Cannot find predefined cost budget type in PA_BUDGETS_TYPES.

[APP–19480] System Error: Cannot find predefined revenue budget type in

PA_BUDGETS_TYPES.

[APP–19481] System Error: Cannot find last accumulation period for project in PA_PERIODS.

[APP–19482] System Error: Cannot create parameter list for invoices.

[APP–19483] Adjustment aborted. Could not lock all items for update.

[APP–19484] The value is too large for this field.

[APP–19485] You cannot perform this action on an item which belongs to a contract project.

[APP–19486] Distribution rule cannot be changed since cost/revenue/invoices exist

Cause:

You cannot change the distribution rule because the project has costed items, revenue, or invoices.

[APP–20000] You must specify a valid, enabled activity in the ACTIVITY_ID column.

[APP–20001] Parameter &PARAM is missing in call to &PROGRAM

Action:

Please contact your Oracle representative.

[APP–20003] You must reference a valid activity

[APP–20006] You cannot delete this &ENTITY from this delete group

Cause:

You cannot delete this &ENTITY from this delete group. A deleted &ENTITY cannot be removed

from a delete group.

Action:

None.

[APP–20009] &ENTITY1 &ENTITY2 already exists. Please re–enter

Cause:

&ENTITY1 &ENTITY2 already exists.

Action:

Enter another value for &ENTITY1 or &ENTITY2.

[APP–20011] &ENTITY attribute value has been overriden by default value for Product Family

item

Cause:

Attribute dependency rule violation.

Action:

None.

[APP–20012] You cannot delete alternate &ENTITY. It is currently in use

Cause:

A bill of material, routing, or cost type currently references this alternate

Action:

You must delete all references to an alternate before you can delete it

[APP–20013] Cannot update the attribute

Cause:

Violation of attribute dependency rules for BOM Item Type = Product Family.

Action:

None.

[APP–20014] Error in BOM_PFI_PVT package: &MSG

[APP–20015] You cannot create a new revision with an alternate bill of material

Cause:

You cannot create a new revision with an alternate bill of material

Action:

You can create new item revisions: – using the Define Item Revisions form – using the Define Bill

of Material form to update an item’s primary bill of material – using the Define Engineering Change

Order form to create an ECO that updates an item’s primary bill of material.

[APP–20016] Item assignment to Product Family category set failed

Cause:

Category &CAT does not exist.

Action:

Please create the category before assigning members to the corresponding product family.

[APP–20017] &PROC :

&ENTITY not found

[APP–20018] You must specify a valid item as the assembly in the column ASSEMBLY_ITEM_ID.

[APP–20019] &ENTITY template attribute values have been overriden by default values for

Product Family item

Cause:

Attribute dependency rule violation. Optional action:

Use correct attribute values in your Product Family item template.

[APP–20021] You must specify a 1 or 2 in the column ASSEMBLY_TYPE.

[APP–20022] You must specify an existing assembly comment record for deletion.

[APP–20023] Valid primary does not exist

[APP–20024] You must specify a valid value for assigned units

[APP–20025] Planning percent may not be 0.

[APP–20026] A baseline already exists for this Line and Family. Saving this calculation will

overwrite the existing one.

[APP–20027] You must include a value in either the ASSEMBLY_ITEM_NUMBER column or the

ASSEMBLY_ITEM_ID column.

[APP–20030] You must specify valid item attributes for assembly items

[APP–20033] The BOM Configuration Item Delimiter profile value is invalid

Cause:

You must enter a one character value for your BOM Configuration Item Delimiter profile option.

Your profile value cannot equal your item flexfield segment separator.

Action:

Update the BOM Configuration Item Delimiter profile value.

[APP–20036] An internal error occurred while delinking your bill of material.

Cause:

Oracle Bills of Material detected an internal error while delinking your bill of material. &ERRMSG

Action:

Contact your Oracle support representative.

[APP–20039] Unable to find a new item number to use for configuration item

Cause:

Oracle Bills of Material’s Create Configuration Item program could not find a new item number.

Action:

Contact your Oracle support representative. Additional Information for support representative:

Please review the concurrent program log file.

[APP–20042] Unable to explode your bill of material

Cause:

Oracle Bills of Material was unable to explode your bill of material.

Action:

Contact your Oracle support representative. Additional information for support representative:

Review the concurrent program log file to determine where the explosion process failed.

[APP–20045] An insert error occurred while exploding your bill of material

Cause:

Oracle Bills of Material detected an insert error while exploding your bill of material.

Action:

Contact your Oracle support representative. Additional information for support representative:

Review the concurrent program log file to determine where the explosion process failed.

[APP–20048] An error occurred while exploding your bill of material

Cause:

Oracle Bills of Material detected missing data required for the bill of material explosion.

Action:

Contact your Oracle support representative. Additional information for your support representative:

One of the following errors occurred: 1) An explosion group id was passed to the explosion routine

which didn’t match any rows on the identified table. 2) The MTL_PARAMETERS table does not

have valid values set up in the CALENDAR_CODE and/or CALENDAR_EXCEPTION_SET_ID

columns for the ORGANIZATION_ID specified. 3) The REQUIREMENT_DATE on the row

processed is a date value which is not set up on the calendar identified in the MTL_PARAMETERS

table.

[APP–20051] An internal error occurred while exploding your bill of material

Cause:

Oracle Bills of Material was unable to explode your configuration item due to an update error.

Action:

Contact your support representative. Additional information for support representative: Review the

concurrent log file to determine where the explosion process failed.

[APP–20054] An internal error occurred while linking your bill of material.

Cause:

Oracle Bills of Material detected an internal error while linking your bill of material. &ERRMSG

Action:

Contact your Oracle support representative. Please review the concurrent log for additional

information.

[APP–20057] An internal error occurred while loading your bill of material

Cause:

Oracle Bills of Material detected an internal error while loading your bill of material. &ERRMSG

Action:

Contact your Oracle support representative. Additional information for support representative:

Review the concurrent program log file to determine where the load bill of material process failed.

[APP–20060] An internal error occurred in the duplicate configuration item name loop

Cause:

Oracle Bills of Material detected an internal error in the duplicate configuration item name loop.

Action:

Contact your Oracle support representative. Additional information for support representative:

Review the concurrent program log file to determine where the duplicate configuration item name

loop failed.

[APP–20063] Order Line in use

Cause:

AutoCreate Configuration found the order line being currently processed by another function.

Action:

Check to see if the row has been processed by the AutoCreate Configuration Concurrent Program or

try later.

[APP–20066] The derived date is outside the workday calendar date range.

Cause:

Oracle Bills of Material is unable to compute a requirement or release date because the date does

not exist for your workday calendar.

Action:

Define additional calendar dates for your workday calendar.

Action:

Reduce the quantity demanded for your item, so the requirement or release date is within your

workday calendar date range.

Action:

Adjust the fixed and variable lead times for your item so the requirement or release date is within

your workday calendar date range.

[APP–20069] An internal error occurred while processing your bill of material

Cause:

Oracle Bills of Material detected an internal error while processing your bill of material.

Action:

Contact your Oracle support representative. Additional information for support representative:

Review the concurrent program log file to determine where the bill of material process failed.

[APP–20072] You must specify a valid value in the column AUTOCHARGE_TYPE.

[APP–20075] You cannot copy this bill of material

Cause:

You cannot copy this bill of material. Copying the bill of material would cause component item

overlap for the default operation sequence ”1”.

Action:

Create a routing with operations for this item before you copy the bill of material. Associate each

component item with a routing operation when you copy the bill of material.

[APP–20078] The Bill header was created but components could not be copied

Cause:

You cannot copy components for this bill of material. Copying the components would cause

component item overlap for the default operation sequence ”1”.

Action:

Create a routing with operations for this item before you copy the bill of material. Associate each

component item with a routing operation when you copy the bill of material.

[APP–20081] A bill for the base model does not exist in this organization

Cause:

A manufacturing bill for the base model of this configuration bill does not exist in this organization.

Action:

You must define a manufacturing bill for your base model in this organization before you choose

option items for your configuration bill of material.

[APP–20084] You must define all bill component items for this organization

Cause:

Component items of your bill of material do not exist for your current organization.

Action:

Define all component items of your bill of material in your current organization.

[APP–20087] This &ENTITY already exists. Please enter another alternate to create an alternate

&ENTITY, or use Query Find to find an existing &ENTITY.

[APP–20090] This combination in the STANDARD_REMARKS_DESIGNATOR column and the

BILL_SEQUENCE_ID column already exists.

[APP–20093] Bill of material copied for this organization &ENTITY1 bill components copied of

&ENTITY2 total bill components &ENTITY3 bill of material comments copied of &ENTITY4

total bill comments &ENTITY5 reference designators were copied of &ENTITY6 total reference

designators &ENTITY7 substitute components copied of &ENTITY8 total substitute components

[APP–20096] You must specify a valid bill for this bill revision

[APP–20099] You must reference a valid bill in the column BILL_SEQUENCE_ID.

[APP–20102] You must specify a valid bill of material

[APP–20105] Alternate bills exist for this primary bill of material

[APP–20108] Other bills reference this bill as a common bill of material

[APP–20111] A repetitive schedule exists for this item

[APP–20114] A discrete job exists for this item

[APP–20117] Open sales orders exist for this item

[APP–20120] Outstanding demand exists for this item

[APP–20123] Configuration items exist for this model bill of material

[APP–20126] Another bill references this option class bill of material

[APP–20129] You must enter a calendar name to be copied &ENTITY.

[APP–20132] Please compile your calendar &ENTITY

Cause:

You have not compiled your calendar &ENTITY.

Action:

Compile calendar &ENTITY.

[APP–20135] Date should be between calendar start and end date

[APP–20138] &ENTITY1 already exists for calendar &ENTITY2. Please re–enter.

[APP–20141] Warning: This exception set is being used by &ENTITY organization(s)

[APP–20144] You cannot enter duplicate workday exception dates. Please re–enter

Cause:

You cannot have duplicate workday exception dates for your calendar or shift workday exceptions.

Action:

Enter another workday exception date.

[APP–20147] You cannot enter a date less than the current date for a new revision

Cause:

You cannot create a new revision with a revision date earlier than the current date.

Action:

Enter a revision date greater than or equal to the current date for your new revision.

[APP–20150] You cannot delete this location. Outside processing resources exist

Cause:

You cannot delete a location for a department with outside processing resources.

Action:

Remove outside processing resources from your department before deleting this location.

[APP–20153] You cannot delete a resource with assigned shifts

Cause:

You cannot delete your resource when shifts for this resource exist.

Action:

Delete the shifts for this resource before you delete your resource.

[APP–20156] You cannot delete this resource. An operation references &ENTITY

Cause:

You cannot delete resource &ENTITY. A routing operation references &ENTITY.

Action:

Disable resource &ENTITY.

[APP–20159] You cannot delete &ENTITY. A standard operation references &ENTITY

Cause:

You cannot delete resource &ENTITY. A standard operation references &ENTITY.

Action:

Disable resource &ENTITY.

[APP–20162] You cannot delete &ENTITY. A WIP job references &ENTITY

Cause:

You cannot delete resource &ENTITY. A WIP job contains operations that reference &ENTITY.

Action:

Disable resource &ENTITY.

[APP–20165] You cannot delete an effective routing revision

[APP–20168] You cannot delete multi–department resource &ENTITY

Cause:

You cannot delete multi–department resource &ENTITY from your department. Other departments

share this resource.

Action:

Delete &ENTITY from the sharing departments before you delete &ENTITY from this department.

[APP–20171] You cannot delete a resource shift with capacity modifications

Cause:

You cannot delete this shift for your resource. Capacity modifications exist for this shift.

Action:

Delete capacity modifications for this shift before you delete your resource shift.

[APP–20174] You cannot enter an autocharge of PO move or PO receipt

Cause:

You cannot enter an autocharge type of PO move or PO receipt for a resource with a negative usage

rate or amount.

Action:

Enter an autocharge type of WIP move or Manual for this resource.

[APP–20177] This capacity change already exists. Please re–enter

Cause:

You entered a capacity change that already exists.

Action:

Enter a unique capacity change.

[APP–20180] You cannot enter a negative usage rate or amount

Cause:

You cannot enter a negative usage rate or amount when the resource autocharge type is PO receipt

or PO move.

Action:

Enter a positive usage rate or amount for this resource.

[APP–20183] You cannot erase &ENTITY

Cause:

You cannot erase your &ENTITY. Values must exist for &ENTITY.

Action:

None.

[APP–20186] You cannot navigate to the &ENTITY zone

[APP–20189] You cannot assign shifts to a resource that is available 24 hours

Cause:

You cannot assign shifts to a resource that is available 24 hours.

Action:

None.

[APP–20192] You cannot define resource details for uncosted resources

Cause:

You cannot define resource details for your uncosted resource.

Action:

None.

[APP–20195] You cannot assign shifts to a shared resource

Cause:

You cannot assign shifts to a shared resource owned by another department.

Action:

Assign additional shifts to your shared resource for the owning department.

[APP–20198] You already share resource &ENTITY with other departments

Cause:

You cannot define &ENTITY as a non–shared resource for this department. Other departments

share &ENTITY.

Action:

Delete &ENTITY from the sharing departments before you define &ENTITY as a non–shared

resource for this department.

[APP–20201] You cannot view resource details for uncosted resources

Cause:

You cannot view resource details for your uncosted resource.

Action:

None.

[APP–20204] Unable to set locator control, defaulting to no locator control

[APP–20207] You must clear component records

[APP–20210] You must reference a valid item as the common item in the column

COMMON_ITEM_NUMBER.

[APP–20213] You must reference a valid common bill in the column

COMMON_BILL_SEQUENCE_ID.

[APP–20216] You must reference a valid common routing in the column

COMMON_ROUTING_SEQUENCE_ID.

[APP–20219] The parent item for this option is on an open sales order

[APP–20222] A pending ECO references this component

[APP–20225] You cannot delete comment &ENTITY. A bill uses this comment

Cause:

You cannot delete a comment referenced by a bill of material.

Action:

Before you delete your comment, delete the reference to your comment on the bill of material.

[APP–20228] You cannot enter additional data with a common &ENTITY assigned

Cause:

You cannot enter additional data when your bill of material or routing references a common bill of

material.

Action:

None.

[APP–20231] You must specify an existing bill as the common bill in the column

COMMON_BILL_SEQUENCE_ID.

[APP–20234] You must include a valid bill as the common bill

[APP–20237] You cannot assign components to a common bill of material

[APP–20240] Common bill has &ENTITY components missing from this organization

Cause:

You cannot reference a common bill of material that contains components not defined for your

organization.

Action:

Define all components to your common bill of material for your organization.

[APP–20243] The common bill information for this item is incomplete

Cause:

You must enter an organization and an item for your common bill of material.

Action:

Enter the organization and item for your common bill of material.

[APP–20246] You cannot assign operations to a common routing

[APP–20249] You must specify an existing organization as the common organization in the column

COMMON_ORG_CODE.

[APP–20252] This item does not exist or is invalid for organizations that reference this bill

Cause:

You entered a component item that either does not exist or has invalid ATO or PTO attributes in all

organizations with bills of material that reference your bill of material as a common.

Action:

Define this item with valid ATO and PTO attributes for all organizations with bills of material that

reference your bill of material as a common.

[APP–20255] You must include a valid routing as the common routing

[APP–20258] You must specify an existing routing as the common routing in the column

COMMON_ROUTING_SEQUENCE_ID.

[APP–20261] This combination of values in the columns COMPONENT_ITEM_ID,

EFFECTIVITY_DATE, OPERATION_SEQ and BILL_SEQUENCE_ID already exists.

[APP–20264] You must assign components with valid attribute combinations

[APP–20267] You must assign an existing item as a component in the column

COMPONENT_ITEM_NUMBER.

[APP–20270] You cannot set Check ATP to ”Yes” for this component

Cause:

You cannot set Check ATP to ”Yes” for a component quantity less than or equal to 0.

Action:

Enter a component quantity greater than 0.

Action:

Set Check ATP to ”No” for this component.

[APP–20273] Component item exists for this operation sequence and date range

Cause:

You cannot overlap the effective date range of identical component items for the same operation

sequence.

Action:

Change the effective date range or operation sequence of either component item.

[APP–20276] Each component must have a unique value in the column

COMPONENT_SEQUENCE_ID.

[APP–20279] You must reference an existing component in the COMPONENT_SEQUENCE_ID

column

[APP–20282] You must reference a valid component sequence in the column

COMPONENT_SEQUENCE_ID.

[APP–20285] You must create a revision for a new routing

Cause:

You must create a revision for a new routing.

Action:

Specify Create Revision as ”Yes” to define a new routing revision.

[APP–20288] Default not found. You must enter a change order number

Cause:

The default for your engineering change order number does not exist or is greater than ten

characters.

Action:

Define default engineering change order number information for each user and organization.

Action:

Reduce the number of characters in your engineering change order prefix or next number.

[APP–20291] You must associate a calendar with your current organization

Cause:

You must associate a workday calendar with each organization.

Action:

Associate a workday calendar with your current organization.

[APP–20294] You must define parameters for this organization in Oracle Inventory

Cause:

You have not defined parameters for your current organization in Oracle Inventory.

Action:

Define parameters for your current organization in Oracle Inventory.

[APP–20297] You must define parameters for Oracle Work in Process

Cause:

You must define parameters for Oracle Work in Process before you can proceed.

Action:

Please define the necessary parameters in the Define Work in Process Parameters form.

[APP–20300] You cannot delete this group. Deleted entities exist in the group

Cause:

You cannot delete this group because it contains deleted items, bills of material, or routings.

Action:

None.

[APP–20303] You cannot delete this group. Deleted sub–entities exist

Cause:

You cannot delete this group because it contains deleted component items or operations.

Action:

None.

[APP–20306] Please enter a valid value for &ENTITY

[APP–20309] Demand exists for this item (MTL_DEMAND)

[APP–20312] RMA’s exist for this item in the interface table (MTL_SO_RMA_INTERFACE)

[APP–20315] Pending cycle count entries exist for this item (MTL_CYCLE_COUNT_ENTRIES)

[APP–20318] Supply from PO’s or transfers exist for this item (MTL_SUPPLY)

[APP–20321] Unprocessed transactions exist for this item in the transaction interface.

(MTL_TRANSACTIONS_INTERFACE)

[APP–20324] Bill of Materials exist for this item (BOM_BILL_OF_MATERIALS)

[APP–20327] This item is a component in a Bill of Material

(BOM_INVENTORY_COMPONENTS)

[APP–20330] A routing exists for this item (BOM_OPERATIONAL_ROUTINGS)

[APP–20333] This item is a substitute component (BOM_SUBSTITUTE_COMPONENT)

[APP–20336] A forecast exists for this item (MRP_FORECAST_ITEMS)

[APP–20339] MRP plans exist for this item (MRP_SCHEDULE_ITEMS)

[APP–20342] Pending demand transactions exist for this item (MTL_DEMAND_INTERFACE)

[APP–20345] MRP plans exist for this item (MRP_SYSTEM_ITEMS)

[APP–20348] This item exists as a component on an ECO (ENG_REVISED_COMPONENTS)

[APP–20351] An ECO exists for this item (ENG_REVISED_ITEMS)

[APP–20354] WIP Jobs exist to produce this item (WIP_ENTITIES)

[APP–20357] WIP requirements exist for this item (WIP_REQUIREMENT_OPERATIONS)

[APP–20360] Purchase Order Lines exist for this item(PO_LINES)

[APP–20363] Receiving shipment lines exist for this item (RCV_SHIPMENT_LINES)

[APP–20366] Requisition lines exits for this item (PO_REQUISITION_LINES)

[APP–20369] Requisitions exit for this item (PO_REQUISITIONS_INTERFACE)

[APP–20372] ReqExpress template lines exist for this item (PO_REQEXPRESS_LINES)

[APP–20375] Inventory transactions exist for this item (MTL_MATERIAL_TRANSACTIONS)

[APP–20378] Purchasing Autosource rules exist for this item (PO_AUTOSOURCE_RULES)

[APP–20381] Purchase Orders exist for this item (PO_LINES)

[APP–20384] Receiving transactions are pending for this item

(RCV_TRANSACTIONS_INTERFACE)

[APP–20387] WIP jobs exist for this item (WIP_DISCRETE_JOBS)

[APP–20390] WIP jobs are pending for this item (WIP_JOB_SCHEDULE_INTERFACE)

[APP–20393] Resources exist for this item (BOM_RESOURCES)

[APP–20396] Invoice, credit memo, or commitment lines exist for this item

(RA_CUSTOMER_TRX_LINES)

[APP–20399] Cost adjustment details exist for this item (CST_STD_COST_ADJ_VALUES)

[APP–20402] Cost history exists for this item (CST_COST_TYPE_HISTORY)

[APP–20405] This item exists in an ABC compile (MTL_ABC_COMPILES)

[APP–20408] Inventory transactions exist for this item

(MTL_MATERIAL_TRANSACTIONS_TEMP)

[APP–20411] ABC Assignments exist for this item (MTL_ABC_ASSIGNMENTS)

[APP–20414] User defined demand exists for this item (MTL_USER_DEMAND)

[APP–20417] User defined supply exists for this item (MTL_USER_SUPPLY)

[APP–20420] This item is included in a Bill of Resource Set

(CRP_BILL_OF_RESOURCE_ITEMS)

[APP–20423] Sales Order Lines exist for this item (SO_LINES)

[APP–20426] Sales Order Details exist for this item (SO_LINE_DETAILS)

[APP–20429] Picking Lines exist for this item (SO_PICKING_LINES)

[APP–20432] Cost update adjustment history exists for this item (CST_STANDARD_COSTS)

[APP–20435] Item still exists in child organizations

[APP–20438] On hand inventory exists for this item (MTL_ONHAND_QUANTITIES)

[APP–20441] Physical Inventory Adjustments exist for this item

(MTL_PHYSICAL_ADJUSTMENTS)

[APP–20444] Physical Inventory Tags exist for this item (MTL_PHYSICAL_INVENTORY_TAGS)

[APP–20447] Replenishment lines exist for this item (MTL_REPLENISH_LINES)

[APP–20450] Pending replenishment lines exist for this item (MTL_REPLENISH_LINES_INT)

[APP–20453] You cannot update common information because demand exists for this bill

[APP–20456] You cannot delete class &ENTITY. A department uses this class

Cause:

You cannot delete a department class currently referenced by a department.

Action:

Delete all department references to this department class.

[APP–20459] You must reference a valid department in the column DEPARTMENT_CODE.

[APP–20462] You must specify a valid, enabled department in the column DEPARTMENT_ID.

[APP–20465] You must specify an active resource assigned to this operation’s department

[APP–20468] This &ENTITY is disabled

Cause:

You cannot reference this &ENTITY because it is disabled.

Action:

Choose another &ENTITY.

[APP–20471] You must include a unique value for the bill sequence in the column

BILL_SEQUENCE_ID.

[APP–20474] Please disable the duplicate component item/op seq for this bill

Cause:

Another component row exists with the same operation sequence and component item, without a

disable date.

Action:

You must add a disable date to the existing component before you can create a new component with

the same component item/operation sequence combination.

[APP–20477] This delete group name is already used for a different delete group type.

[APP–20480] This combination of values in the columns RESOURCE_SEQ_NUM and

OPERATION_SEQUENCE_ID already exists.

[APP–20483] A duplicate routing has been found.

[APP–20486] This combination of values in the columns SUBSTITUTE_COMPONENT_ID and

COMPONENT_SEQUENCE_ID already exists.

[APP–20489] This combination of values in the columns COMPONENT_SEQUENCE_ID and

COMPONENT_REFERENCE_DESIGNATOR already exists.

[APP–20492] You cannot assign an effective date that is greater than the disable date in the column

DISABLE_DATE.

[APP–20495] This item/alternate combination already exists in Engineering

Cause:

You cannot define your manufacturing bill of material using the same item/alternate combination

that already exists for an engineering bill of material.

Action:

Define your manufacturing bill of material using a unique item/alternate combination.

[APP–20498] You cannot enter an owning department. Shifts exist for this resource

Cause:

You cannot enter an owning department for a resource when shifts are assigned to that resource.

Action:

None.

[APP–20501] &ENTITY1 must be equal to &ENTITY2

Cause:

&ENTITY1 must be equal to &ENTITY2.

Action:

Enter the value of &ENTITY2 for &ENTITY1.

[APP–20504] An internal error occurred while creating your list of items

Cause:

Oracle Bills of Material detected an internal error while creating your list of items.

Action:

Contact your Oracle support representative.

[APP–20507] An internal error occurred while copying this &ENTITY

Cause:

Oracle Bills of Material detected an internal error while copying your &ENTITY.

Action:

Contact your Oracle support representative.

[APP–20510] You cannot change &ENTITY1 because &ENTITY2 exists.

[APP–20513] You must choose a workday exception set to compile your calendar

Cause:

You must choose a workday exception set in order to compile your calendar.

Action:

Define workday exception sets for your calendar, and choose a workday exception set when you

compile your calendar.

[APP–20516] Item &ITEM_NUMBER has no valid revision on &EFF_DATE

Cause:

On &EFF_DATE, your item has no valid revision.

Action:

Define a revision for your item on &EFF_DATE.

[APP–20517] The Link between &FROM_OP_SEQ_ID and &TO_OP_SEQ_ID already Exists.

[APP–20519] An effective date for revision &REVISION does not exist

Cause:

There is no effective date for revision &REVISION.

Action:

Enter another revision.

[APP–20522] This item or routing has no valid revision and effective date range

Cause:

This item or routing has no valid revision and effective date range.

Action:

Define a revision and effective date range for your item or routing.

[APP–20525] Item &ITEM_NUMBER has no valid routing revision on &EFF_DATE

Cause:

On &EFF_DATE, your item has no valid routing revision.

Action:

Define a routing revision for your item on &EFF_DATE.

[APP–20528] Unable to implode this component item.

Cause:

Oracle Bills of Material is unable to implode your component item.

Action:

Contact your Oracle support representative.

[APP–20531] Unable to implode this range of component items

Cause:

Oracle Bills of Material is unable to implode this range of component items.

Action:

Contact your Oracle support representative. Additional information for support representative:

Please review the log file for this concurrent program.

[APP–20534] You cannot assign an implemented component with overlapping effective date ranges

[APP–20537] You cannot assign an operation with overlapping effective date ranges

[APP–20540] &ENTITY1 must not be same as &ENTITY2

Cause:

You cannot enter the same value for &ENTITY1 and &ENTITY2.

Action:

Enter different values for &ENTITY1 and &ENTITY2.

[APP–20543] You must specify a valid standard instruction code in the column

OPERATION_DESCRIPTION_CODE.

[APP–20546] You cannot delete this instruction. An operation references &ENTITY

Cause:

A standard operation, a routing operation or a job currently references instruction &ENTITY.

Action:

Delete the standard operation, routing operation or job references to instruction &ENTITY before

deleting the instruction.

[APP–20549] &ENTITY must be a positive integer value

[APP–20552] You must include a valid alternate name in the column

ALTERNATE_BOM_DESIGNATOR.

[APP–20555] This component item is invalid. Please re–enter

Cause:

You cannot enter component items where the Check ATP or the ATP Components attribute is ”Yes”

on this bill of material.

Action:

Assign a component item where the Check ATP or ATP Component attribute is ”No”.

Action:

Change the parent item attributes: – Set ATP Components to ”Yes” or – Set Assemble to Order or

Pick Components to ”No” – Verify that the WIP Supply Type is not ”Phantom”

[APP–20558] You must define delete constraint &ENTITY as a SQL select statement

Cause:

You must define delete constraints as SQL select statements. &ENTITY is not a select statement.

Action:

Define your delete constraint as a SQL select statement.

[APP–20561] &ENTITY is not a valid date within the calendar.

[APP–20564] You must assign components with valid item attributes

[APP–20567] You must specify a valid operation sequence number for the component

[APP–20570] You must include a valid organization in the column ORGANIZATION_ID.

[APP–20573] You must include a valid alternate name in the column

ALTERNATE_ROUTING_DESIGNATOR.

[APP–20576] You must include a valid value in the column

STANDARD_REMARKS_DESIGNATOR.

[APP–20579] You must include a value in either the INVENTORY_ITEM column or the

INVENTORY_ITEM_ID column.

[APP–20582] You must specify a valid item in the column INVENTORY_ITEM_ID.

[APP–20585] Bill &ENTITY &ENTITY2 exceeds the maximum number of bill levels

Cause:

Bill &ENTITY1 &ENTITY2 exceeds the maximum number of bill levels defined for this

organization.

Action:

Reduce the number of levels in bill &ENTITY1 &ENTITY2.

[APP–20588] You must specify an existing location in the column LOCATION_NAME.

[APP–20591] You must specify a valid locator

[APP–20594] A loop may exist in this bill of material

Cause:

This bill of material either contains a parent item referenced as component or exceeds the maximum

number of bill of material levels.

Action:

Disable the component referencing a parent item.

Action:

Increase the maximum number of bill of material levels.

[APP–20597] Lead time calculation for &ENTITY failed

[APP–20600] Order details for the parent item specify no for &ENTITY

[APP–20603] The maximum number of bill of material levels must be in the range 1..60

Cause:

You cannot enter a value greater than 60 as the maximum number of bill of material levels.

Action:

Enter a value less than or equal to 60 as the maximum number of bill of material levels.

[APP–20606] A bill exceeds the maximum number of bill of material levels

Cause:

Oracle Bills of Material detected a bill that exceeds the maximum number of bill of material level.

Action:

Increase the parameter for the maximum number of bill of material levels or reduce the number of

levels in your bill structure.

[APP–20609] You cannot copy this bill. All items must exist for this organization

Cause:

You cannot copy a bill of material if all the component items do not exist for this organization.

Action:

Define all component items for this organization before copying this bill of material.

[APP–20612] Implementation failed for some Bills of Material

[APP–20615] You cannot set quantity related to yes when you add a component

Cause:

You cannot specify quantity related reference designators when you add a component to a bill

through a mass change order.

Action:

Specify ”No” for quantity related when you add a component to a bill through a mass change order.

[APP–20618] An internal error was detected

Cause:

Oracle Bills of Material detected an internal error when a function received a pointer to unallocated

memory.

Action:

Contact your Oracle support representative.

[APP–20621] The maximum number of bill of material levels must be in the range 1..60

Cause:

You cannot enter a value lower than 1 as the maximum number of bill of material levels.

Action:

Enter a value greater than or equal to 1 as the maximum number of bill of material levels.

[APP–20624] You must enter capacity units for this resource

Cause:

You must enter capacity units for multi–department resources.

Action:

Specify capacity units for this resource.

[APP–20627] You cannot specify a negative usage rate for this resource

[APP–20630] NONE is not a valid name for an Alternate.

[APP–20633] You cannot update Check ATP to ”Yes” for this component

Cause:

You cannot update the Check ATP component attribute if the Check ATP item attribute is set to

”No”.

Action:

Set the Check ATP item attribute to ”Yes” for this item.

[APP–20636] This &ENTITY1 is not a valid &ENTITY2. Please re–enter

Cause:

You must enter a valid &ENTITY2 for your capacity modification.

Action:

Enter a valid &ENTITY2 as the &ENTITY1 for your capacity modification.

[APP–20639] &ENTITY is not an existing message name. Please re–enter

Cause:

You must enter an existing message as your delete constraint failure message.

Action:

Define your message for Oracle Bills of Material in the Application Object Library message

dictionary. Enter your message name as your delete constraint failure message.

[APP–20642] You cannot define this resource as available 24 hours because either: Shifts exist for

this resource or A routing assigns more than 1 unit of this resource.

[APP–20645] You do not have the privilege required to define Currency as a Resource Type.

Request your system administrator for the privilege to update cost information.

[APP–20648] You cannot delete &ENTITY due to invalid data

Cause:

Oracle Bills of Material cannot delete &ENTITY due to invalid data.

Action:

Contact your support representative. Additional information for support representative: The table

BOM_DELETE_SQL_STATEMENTS does not contain SQL statements to delete &ENTITY.

[APP–20651] You cannot delete this &ENTITY1 from this organization

Cause:

You cannot delete this &ENTITY1 from your current organization. The &ENTITY1 exists in

organization &ENTITY2.

Action:

Change your current organization to the &ENTITY2 before deleting this &ENTITY1.

[APP–20654] You cannot delete cost for the frozen standard cost type

Cause:

You cannot delete your resource cost when the cost type is frozen.

Action:

Use Cost Update to update costs for the frozen standard cost type.

[APP–20657] &ENTITY1 do not exist for this &ENTITY2

Cause:

There are no &ENTITY1 for &ENTITY2. You can enter &ENTITY1 if: – &ENTITY2 has a delete

status of ”Error” – Your group type is ”Component” or ”Operation”

Action:

None.

[APP–20660] This operation’s department does not have a location. A charge type of PO Receipt

cannot be assigned if there is no location.

[APP–20663] You must enter an owning department or capacity units

Cause:

You must enter capacity units for non–shared resources or an owning department for shared

resources.

Action:

Specify capacity units for resources owned by this department and not shared with other

departments.

Action:

Enter an owning department for resources assigned to this department and owned by another

department.

[APP–20666] You can enter a negative usage rate only if the resource is not scheduled and the

charge type is neither PO Move or PO Receipt.

[APP–20669] An internal error was detected for this item or routing revision

Cause:

Oracle Bills of Material detected an incorrect sequence id for this item revision.

Action:

Contact your Oracle support representative. Additional information for support representative : The

sequence &SEQ_ID is invalid for this item.

[APP–20672] You cannot assign reference designators to planning bills

[APP–20675] You cannot assign reference designators to model, option class, or planning

components

[APP–20678] You cannot assign substitute components to planning bills

[APP–20681] You cannot assign substitute components to model, option class, or planning

components

[APP–20684] &ENTITY1 &ENTITY2 does not have a location specified. &ENTITY3 &ENTITY4

is an outside processing &ENTITY5.

[APP–20687] You must enter a valid standard instruction in the column

OPERATION_DESCRIPTION_CODE.

[APP–20690] You must include a value in the column COMPUTER_REFERENCE_DESIGNATOR.

[APP–20693] You must enter a resource sequence in the column RESOURCE_SEQ_NUM.

[APP–20696] You must include a value for the revision

[APP–20699] You must enter a routing revision in the column PROCESS_REVISION.

[APP–20702] You must specify a resource offset percent between 0 and 100 in the column

RESOURCE_OFFSET_PERCENT.

[APP–20705] You cannot assign an autocharge type of PO Move for this resource

Cause:

You cannot enter an Autocharge type of PO Move for more than one resource per operation.

Action:

Specify an Autocharge type of Manual, PO Receipt, or WIP Move for this resource.

[APP–20708] This bill of material contains a loop

Cause:

This bill of material contains the following loop: &ENTITY1

Action:

Disable the component that references a parent item.

[APP–20711] You must assign the days on and days off for this workday pattern

[APP–20714] This combination of values in the ROUTING_SEQUENCE_ID,

EFFECTIVITY_DATE, and OPERATION_SEQ columns already exists.

[APP–20717] You must specify an operation with valid attributes

[APP–20720] PTO model and option class bills must have optional ATO component items

[APP–20723] You cannot enter component yield for option class items

[APP–20726] This operation_description_code and operation_sequence_id combination already

exists

[APP–20729] You must specify a valid value in the following columns: BASIS_TYPE,

STANDARD_RATE_FLAG, SCHEDULE_FLAG and AUTOCHARGE_TYPE.

[APP–20732] You cannot have more than one Next scheduled resource for an operation

[APP–20735] You cannot have more than one Prior scheduled resource for an operation

[APP–20738] You cannot schedule this resource

[APP–20741] Each operation must have a unique value in the column

OPERATION_SEQUENCE_ID.

[APP–20744] You must reference a valid operation sequence in the column

OPERATION_SEQUENCE_ID.

[APP–20747] You must enter an operation sequence number in the column

OPERATION_SEQ_NUM.

[APP–20750] You must include a valid value for either the ORGANIZATION_CODE or

ORANIZATION_ID column.

[APP–20753] An internal error was detected

Cause:

An internal error was detected.

Action:

Contact your Oracle support representative. Additional information for support representative:

&ROUTINE failed to allocate memory. Please review the concurrent log file for more information.

[APP–20756] An internal error was detected

Cause:

Oracle Bills of Material detected an internal error when a function received invalid values as its

parameters.

Action:

Contact your Oracle support representative.

[APP–20759] You cannot rollup costs, define jobs or schedules in &ENTITY1

Cause:

You cannot rollup costs, define discrete jobs or repetitive schedules in an organization that shares

item costs with a master costing organization. Although Oracle Bills of Material lets you define

BOM parameters for this organization &ENTITY1, you cannot perform a cost rollup, open a

discrete job, define a repetitive schedule, or create configuration items in this organization.

Action:

Change to the master costing organization for &ENTITY1 to define your bills of material and

routings. Rollup costs, define discrete jobs, define repetitive schedules, and create configuration

items in your master costing organization.

[APP–20762] You cannot update a component referenced on pending ECO &ENTITY

[APP–20765] You must assign a supply type of phantom to this component

Cause:

You must assign a component supply type of phantom to model and option class items.

Action:

Change the component supply type for model and option class items.

[APP–20768] Only planning bills and optional components can have planning factors not equal to

100

[APP–20771] You cannot create additional details for planning bill components

[APP–20774] An internal error occurred in the program &ROUTINE

Cause:

Oracle Bills of Material detected &SQLERRM in &ROUTINE.

Action:

Contact your system administrator.

[APP–20777] Outside Processing resources with PO Receipt Charge Type exist for this department.

[APP–20780] &ENTITY1 does not exist for &ENTITY2

Cause:

&ENTITY1 does not exist for &ENTITY2.

Action:

None.

[APP–20783] You must specify a quantity of 1 for an ATO option class component that belongs to a

model, option class, or standard bill

[APP–20786] You cannot define &ENTITY quantities with related reference designators

Cause:

You cannot define &ENTITY component quantities and assign quantity related reference

designators.

Action:

Create whole number component quantities or define your reference designators as independent of

&ENTITY component quantities.

[APP–20789] You cannot define &ENTITY quantity related reference designators

Cause:

You cannot define quantity related reference designators for &ENTITY component quantities.

Action:

Create your reference designators as independent of component quantity.

[APP–20792] You cannot enter the character ’ for a revision. Please re–enter

Cause:

You cannot enter the character ’ for your revision label.

Action:

Enter another alphanumeric character for your revision label.

[APP–20795] Starting Value and Ending Value must be the same length

[APP–20798] You must define all departments and resources for this organization

Cause:

You cannot copy a routing with operations that reference departments and resources not defined for

your organization.

Action:

Define all departments and resources for your organization before copying this routing.

[APP–20801] The number of reference designators must equal the component quantity

[APP–20804] The number of reference designators must equal component quantity

Cause:

For quantity related reference designators, the number of reference designators must equal the

component quantity.

Action:

Change the number of reference designators to equal the component quantity.

[APP–20807] &ENTITY1 is required for &ENTITY2

[APP–20810] &ENTITY is not a valid name for this alternate. Please re–enter

Cause:

&ENTITY is not a valid name for this alternate.

Action:

Please enter another name for this alternate.

[APP–20813] You must include a valid value in either the RESOURCE_ID or RESOURCE_CODE

column.

[APP–20816] You must enter revisions and effectivity dates in ascending order

Cause:

A lower revision with a later effectivity date than your revision already exists.

Action:

Enter an effectivity date for your revision that is later than all other effectivity dates.

Cause:

A higher revision with an earlier effectivity date than your revision already exists.

Action:

Enter a revision that is higher than all other revisions.

[APP–20819] This routing has no effective revision for this date.

Cause:

This routing has no effective revision for the revision date entered.

Action:

Enter another revision date for this routing.

[APP–20822] You must assign revision labels in ascending order

[APP–20825] Routing copied for this organization &ENTITY1 operations copied of &ENTITY2

total operations. &ENTITY3 resources copied of &ENTITY4 total operation resources. &ENTITY5

operation instructions copied of &ENTITY6 total operation instructions.

[APP–20828] You must enter a routing with valid item attributes

[APP–20831] You must specify either a 1 or 2 ROUTING_TYPE column.

[APP–20834] Alternates exist for this primary routing

[APP–20837] Other routings reference this routing as a common routing

[APP–20840] A discrete job references this routing

[APP–20843] A repetitive schedule references this routing

[APP–20846] You must specify a valid routing for this routing revision

[APP–20849] You must enter a valid routing

[APP–20852] You must reference a valid routing sequence in the ROUTING_SEQUENCE_ID

column.

[APP–20855] An internal error was detected for this item or routing revision

Cause:

Oracle Bills of Material detected an error for this item or routing revision.

Action:

Contact your Oracle support representative. Additional information for support representative: An

invalid or insufficient number of arguments were passed to the revision user exit.

[APP–20858] You cannot update common information because sales exist for this bill

[APP–20861] Resource is not time–based. You cannot schedule a resource that is not time–based.

[APP–20864] You cannot overlap shifts. Please re–enter shift times

Cause:

Shift start time &ENTITY1 and stop time &ENTITY2 overlap with another shift.

Action:

Enter another shift start time or stop time.

[APP–20867] You must enter a shift number to be copied &ENTITY.

[APP–20869] Effective From date must be greater than or equal to current date and also less than

Disable Date.

[APP–20870] &ENTITY

Cause:

Oracle Bills of Material detected &ENTITY.

Action:

None.

[APP–20873] An internal error occurred while imploding your range of items

Cause:

Oracle Bills of Material detected an internal error while imploding your range of component items.

Action:

Contact your Oracle support representative.

[APP–20876] You must reference a valid operation code in the column OPERATION_CODE.

[APP–20879] You must reference a valid standard operation in the column

STANDARD_OPERATION_ID.

[APP–20882] You cannot delete this standard operation. A routing uses &ENTITY

Cause:

You cannot delete this standard operation. A routing references standard operation &ENTITY.

Action:

Delete routing references to standard operation &ENTITY before deleting &ENTITY.

[APP–20885] You must include a valid standard value in the

STANDARD_REMARKS_DESIGNATOR column

[APP–20888] You must specify a valid subinventory

[APP–20891] You must specify valid item attributes for substitute component items

[APP–20894] You must specify a standard, bom enabled item as the substitute component. You

cannot assign engineering items as substitutes on a manufacturing bill.

[APP–20897] You cannot assign the assembly or component item as a substitute component

[APP–20900] You must assign an existing item in the SUBSTITUTE_COMP_NUMBER column

[APP–20903] You must include a value in the SUBSTITUTE_ITEM_QUANTITY column

[APP–20906] The substitute item quantity cannot be zero

[APP–20909] You cannot enter a subinventory or locator when supply type is push

Cause:

You cannot enter a supply subinventory or locator for a component when the supply type is push.

Action:

Enter another supply type for this component.

Action:

Delete the supply subinventory and locator for this component.

[APP–20912] You must adjust resource usage rates based on the new UOM

Cause:

You modified the unit of measure for this resource.

Action:

You must adjust the resource usage rates in routing operations and standard operations that reference

this resource.

[APP–20915] You must specify the reciprocal of the value in the USAGE_RATE_OR_AMOUNT

column in the USAGE_RATE_OR_AMOUNT_INVERSE column

[APP–20918] An internal error occurred while verifying your bill of material

Cause:

Oracle Bills of Material detected an internal error while verifying your bill of material.

Action:

Contact your Oracle support representative.

[APP–20919] Date To should be greater than or equal to Date From

[APP–20920] A corresponding routing does not exist.

[APP–20921] Organization cannot be blank.

[APP–20922] Transaction Type must be Insert, Update or Delete

[APP–20923] Line is not updatable if processes, line operations, or standard events exist for this

routing.

[APP–20924] You must first save the delete group

[APP–20925] This item is already a member of a Product Family.

Action: Select a member which is not already a member of another Product Family or is not a

Product Family itself.

[APP–20926] A Product Family for this item already exists.

[APP–20927] You cannot insert records with this form.

[APP–20928] Effective To date must be greater than or equal to Effective From date.

[APP–20928] Effective To date must be greater than or equal to current date and must also be

greater than effective from date.

[APP–20929] Overlapping effectivity dates.

Cause: Effective From and Effective To dates for the planning factor cannot overlap. Only 1

planning percent can be effective at a given date.

Action: Enter effective from and to dates such that no date falls within the range of other

planning percentages.

[APP–20930] &ENTITY1 is required for &ENTITY2 form.

[APP–20931] You cannot assign values to non–updatable columns.

[APP–20932] You must specify an existing bill record for update.

[APP–20933] You must specify a delete group in the BOM_INTERFACE_DELETE_GROUPS table

for bills.

[APP–20934] You must specify a Delete Group with the proper Type.

[APP–20935] You must specify an existing component record for update.

[APP–20936] You must set Quantity Related to ”No” because the number of reference designators

does not equal the component quantity.

[APP–20937] You must specify a delete group in the BOM_INTERFACE_DELETE_GROUPS table

for components.

[APP–20938] You must specify an existing implemented substitute component record for update or

deletion.

[APP–20939] You must specify a component that exists in the organizations that refer to this bill as

a common bill.

[APP–20940] You must specify a substitute component that exists in the organizations that refer to

this bill as a common bill.

[APP–20941] You must assign an existing item as the NEW_SUB_COMP_NUMBER.

[APP–20942] You must specify an existing implemented reference designator record for update or

deletion.

[APP–20943] Events are associated with this process or line operation.

[APP–20944] This process or line operation is part of a network.

[APP–20945] &Forecast Entries

[APP–20946] &Standard Operations

[APP–20947] Flow &Routings

[APP–20948] &Kanban Planner Workbench

[APP–20949] Save as &Baseline

[APP–20950] &Next Set

[APP–20951] &Previous Set

[APP–20952] &View Baseline

[APP–20953] Master &Demand Schedule Entries

[APP–20954] Master Production Schedule &Entries

[APP–20955] Line Scheduling &Workbench

[APP–20956] This line does not exist.

[APP–20957] A line is required for Product Synchronizations.

[APP–20958] Only one routing per item per line may be used in mixed model map.

[APP–20959] Operation type is required.

[APP–20960] Operation code is required,

[APP–20961] Process or Line Operation does not exist.

[APP–20962] Only events can be associated with processes or line operations.

[APP–20963] You can insert, update and delete resources only for non–referenced events.

Resources cannot be associated with processes or line operations. They cannot be touched if the

event is referenced.

[APP–20964] Implementation Date, Change Notice, ECN Initiation Date, Creation Date and

Created By are not updatable.

[APP–20965] This operation does not exist.

[APP–20966] Operation Resources or Attachments exist. You cannot copy or reference standard

operations until existing assigned resources and attachments are deleted.

[APP–20967] You cannot update department code.

[APP–20968] This operation resource does not exist.

[APP–20969] A delete group name must be specified.

[APP–20970] At first record

[APP–20971] At last record

[APP–20972] You cannot access this form

Cause:

You do not have a license for Oracle Flow Manufacturing.

Action:

Obtain a license for Oracle Flow Manufacturing.

[APP–20973] Boost % cannot be –1.

[APP–20974] Demand Days cannot be zero.

[APP–20975] Line TAKT cannot be calculated because the total Demand is zero.

[APP–20976] The Capable to Promise flag can be set for only one routing per item per organization.

[APP–20977] This bill can not be copied because a component item either does not exist or has

invalid ATO or PTO attributes in an organization with bills of material that reference your bill of

material as a common.

[APP–20978] Hours Per Day cannot be zero.

[APP–20998] A Product Family for this item already exists. Action : Please perform a Query find to

see existing Product Families or enter an item for which a Product Family has not been defined.

[APP–21000] You have not chosen anything to transfer

Cause:

You have set all options to ’No’

Action:

Set one of these Options to ’Yes’ – Transfer Items – Transfer Bills – Transfer Routings

[APP–21002] Reference designator &ENTITY already exists. Please re–enter

Cause:

You cannot add &ENTITY as a reference designator for this component. This reference designator

already exists.

Action:

Enter another reference designator.

[APP–21004] This alternate bill already exists as an engineering bill

[APP–21006] Approver Name must be entered

[APP–21008] The combined length of Prefix and Next Number exceeds 10 characters

[APP–21010] You cannot revise components for a cancelled revised item

Cause:

You cannot change revised component information for cancelled revised items.

Action:

None.

[APP–21012] You cannot create a bill of material for this item

Cause:

You are trying to create a bill of material for an item which is not allowed to have bills.

Action:

Set item attribute ’BOM allowed’ to ’Yes’.

[APP–21014] You cannot delete this change type because it appears on an ECO or MCO

[APP–21016] You cannot delete or cancel the common bill &ENTITY

[APP–21018] You cannot delete this &Entity because it appears on an ECO

[APP–21020] You cannot update this item because the change type is accessed in an unimplemented

ECO or MCO

[APP–21022] You cannot view revised components

Cause:

You are not allowed to revise items of this type.

Action:

Contact your Manager/System Administrator to give you access to this item. This is done by setting

the values to ’Yes’ for the following Personal Profile Options : – Model Item Access – Planning

Item Access – Standard Item Access

[APP–21024] Unable to set locator control, defaulting to no locator control

[APP–21026] Change type &ENTITY already exists. Please re–enter...

[APP–21028] You cannot revise an item that references a common bill

Cause:

You cannot change an item that references a common bill.

Action:

Oracle Engineering allows you to revise the common bill.

[APP–21030] This item is missing from other organizations that refer to this bill

Cause:

You entered a component item that does not exist in all organizations that have engineering bills of

material referencing your bill of material as a common.

Action:

Define this item for all organization with engineering bills of material that reference your bill of

material as a common.

[APP–21032] Component Add or Change has a disable date less than the current date

Cause:

Add or change for component, &ITEM, could not be implemented because its disable date will be

less than the new effective date.

Action:

Redefine the change notice so that the Disable Date is some day in the future.

[APP–21034] Unable to add or change component &ITEM

Cause:

Implementation attempted to add Component, &ITEM, to operation &OP, which already exists on

the Bill of Material.

Action:

Cancel this portion of the engineering change order.

Cause:

Implementation attempted to change an existing Operation to number &OP. The new operation

number has already been specified for component, &ITEM.

Action:

Change the effectivity or disable dates of component &ITEM at operation &OP.

[APP–21036] Component item already exists for this operation sequence and date range

Cause:

A bill cannot have identical component items for the same operation sequence with overlapping

effective dates.

Action:

Change the effective date range or operation sequence of either component item.

[APP–21038] The new revision, &ENTITY1, is lower than the current revision, &ENTITY2

Cause:

New item revision, &ENTITY1, must be higher than the current revision, &ENTITY2.

Action:

Change the new item revision to a higher value.

[APP–21040] Default not found. You must enter a change order number

Cause:

The default for your engineering change order number does not exist or is greater than ten

characters.

Action:

Define default engineering change order number information for each user and organization.

Action:

Reduce the number of characters in your engineering change order prefix or next number.

[APP–21042] This &ENTITY is disabled

[APP–21044] You must set the approval status to Approved for this ECO

Cause:

The ECO has an ECO status of scheduled, or some revised items on this ECO have a revised item

status of scheduled.

Action:

Change the ECO status or revised item status to open, hold, released, or cancelled.

[APP–21046] You must enter a specific organization or all organization ECN number

[APP–21048] Enter a valid Employee Name

[APP–21050] An internal error occurred while transferring your data

Cause:

Oracle Engineering detected the following error, &TR_ERROR.

Action:

Contact your system administrator.

[APP–21052] An internal error occurred while copying this bill of material

Cause:

Oracle Engineering detected an internal error while attempting to copy this bill.

Action:

Contact your Oracle support representative.

[APP–21054] An internal error was detected during &ENTITY

Cause:

Oracle Engineering detected and internal error during &ENTITY.

Action:

Contact your local Oracle support representative.

[APP–21056] Component quantity of &ITEM must be an integer.

Cause:

You cannot enter a fractional component quantity for components to a pick to order bill.

Action:

Enter an integer for the component quantity on all components to a pick to order bill.

[APP–21058] You have already added this component to this operation sequence

Cause:

You cannot add a component to a operation sequence more than once.

Action:

Add this component to an another operation sequence

[APP–21060] This component item has already been revised on this date

Cause:

You cannot modify a component more than once for the same effective date.

Action:

Choose another effective date.

[APP–21062] You cannot see details for an implemented revised item

Cause:

You cannot review details for revised items you have already implemented.

Action:

None.

[APP–21064] &ECO &ITEM &ALT Implementation failed: &ERROR

[APP–21066] You cannot add a component item with these ATP item attributes

Cause:

You cannot add a component item where the Check ATP or the ATP Components item attribute is

”Yes”.

Action:

Assign a component item where the Check ATP or ATP Components item attribute is ”No”.

Action:

Change the parent item’s attributes: – Set ATP Components to ”Yes” or – Set Assemble to Order or

Pick Components to ”No” – Verify that the WIP Supply Type is not ”Phantom”

[APP–21068] There are no ECO’s revising this &ENTITY

Cause:

You have selected an item that does not appear in any ECO as a revised &ENTITY.

Action:

Enter an item for which an ECO exists where that item is a revised &ENTITY.

[APP–21070] Implementation failed for &ECO &ITEM &ALT: &ERROR

[APP–21072] &ENTITY is ’Yes’ for this component and ’No’ for the revised item

[APP–21074] &ITEM &ALT Implementation failed: &ERROR

[APP–21076] An internal error was detected and the data was not transferred

Cause:

Oracle Engineering detected an internal error. Oracle Engineering was not able to access enough

memory to transfer your engineering data.

Action:

Contact your System Administrator

[APP–21078] An alternate bill for this item already exists in manufacturing

Cause:

You cannot create an engineering bill of material for this item and alternate combination. You

already have defined an alternate bill in manufacturing for this item and alternate.

Action:

Choose another alternate or item to create an engineering bill of material.

[APP–21080] A primary bill for this item already exists in manufacturing

Cause:

You cannot define a primary engineering bill of material for this item. You have already defined the

primary bill for this item in manufacturing.

Action:

Define an alternate engineering bill of material for this item.

[APP–21082] You cannot add reference designators or substitute components to non–standard

components.

[APP–21084] &ENTITY1 is not equal to &ENTITY2

Cause:

&ENTITY1 is not equal to &ENTITY2.

Action:

Make &ENTITY1 equal to &ENTITY2.

[APP–21086] &ENTITY not found

[APP–21088] Program could not transfer item – &ENTITY

[APP–21090] Program could not transfer item – out of memory

Cause:

Program could not transfer this item due to lack of memory space.

Action:

Contact your System Administrator to rectify this problem.

[APP–21092] You cannot change or delete &ITEM for this bill

Cause:

You cannot change or delete &ITEM. This component has already been disabled from the bill.

Action:

Remove this revised component from your ECO.

[APP–21094] You cannot change or delete &ITEM for this bill

Cause:

You cannot delete or change &ITEM. This component has a future effective date for this bill of

material.

Action:

Implement the revised item after &ITEM is effective for this bill.

Action:

Remove revised component &ITEM for this revised item on your engineering change order.

Action:

Wait until the effectivity date has passed.

[APP–21096] You cannot change or delete &ITEM for this bill

Cause:

You cannot change or delete &ITEM. This component is not implemented for this bill.

Action:

Implement the revised item that adds this component to your bill, before you change or delete

&ITEM.

[APP–21098] You must enter an operation sequence of 1 for this item

Cause:

You must enter an operation sequence of 1 for all items that do not have a routing.

Action:

Enter an operation sequence of 1 for this item.

[APP–21100] You cannot enter a yield for option class items

[APP–21102] &ROUTINE: &SQLERRM

[APP–21104] ECO &ENTITY already created this revision.

Cause:

An ECO has already created this revision.

Action:

Enter another revision.

[APP–21106] Another process is trying to create this revision. Please re–enter

Cause:

Another process is attempting to create this revision.

Action:

Enter the next higher revision for this item.

[APP–21108] The effective date for this revised item is past due

Cause:

You have an unimplemented ECO for this item that is earlier than today.

Action:

Implement the ECO on this item or cancel the ECO.

[APP–21110] You cannot view revised component details for planning bills

[APP–21112] You cannot add reference designators or substitute components to planning bills.

[APP–21114] Another prefix has been defined as &ENTITY

Cause:

You have an existing prefix with the same name.

Action:

Enter an unique prefix name.

[APP–21116] This prefix already exists for user &ENTITY1 in organization &ENTITY2

Cause:

You have entered an existing prefix name.

Action:

Enter an unique prefix name.

[APP–21118] This prefix already exists for all users across all organizations

Cause:

You have entered an existing prefix name.

Action:

Enter an unique prefix name.

[APP–21120] This prefix already exists for all users in organization &ENTITY

Cause:

You have entered an existing prefix name.

Action:

Enter an unique prefix name.

[APP–21122] This prefix already exists for user &ENTITY across all organizations

Cause:

You have entered an existing prefix name.

Action:

Enter an unique prefix name.

[APP–21124] This organization &ENTITY1 already exists for user &ENTITY2

Cause:

You have entered an existing organization.

Action:

Enter an unique organization.

[APP–21126] This organization &ENTITY1 already exists for all users

Cause:

You have entered an existing organization.

Action:

Enter an unique organization.

[APP–21128] A primary engineering bill already exists for this item

Cause:

You cannot create a primary bill of material for this item.

Action:

Create an alternate engineering bill for this item.

[APP–21130] This component must have &ENTITY reference designators

Cause:

Components with quantity related reference designators must have the same number of designators

as the component quantity.

Action:

None.

[APP–21132] You cannot enter additional details for deleted revised component

[APP–21134] A lower revision for this part is pending on another ECO.

Cause:

You cannot implement revisions out of sequence.

Action:

Either implement or cancel the pending lower revision first..

[APP–21136] This item does not have a valid revision as of this date

Cause:

This item does not have a valid revision as of this date.

Action:

Enter another date that references a valid revision for this item.

[APP–21138] The substitute item cannot be a component or assembly item.

Cause:

You cannot enter the component or assembly item as the substitute component.

Action:

Enter another item as the substitute component.

[APP–21140] User name must be unique

[APP–21142] User name is required

[APP–21144] You cannot delete an item which has revised components

Cause:

You cannot delete an item that has revised components.

Action:

Delete all revised components before deleting the item.

[APP–21146] You cannot delete an ECO which has revised items

Cause:

You cannot delete an ECO that has revised items.

Action:

Delete all revised items on the ECO before deleting the ECO.

[APP–21148] You can insert, update or delete data for your user name only

[APP–21150] An internal error was detected when rescheduling your ECO

Cause:

Oracle Engineering detected and internal error when rescheduling your ECO.

Action:

Contact your system administrator.

[APP–21151] You must enter a valid value for ACD_TYPE

[APP–21152] The referenced component item has invalid Bom Item Type.

[APP–21153] The revised item’s latest revision is referenced in another ECO.

[APP–21154] You must specify a requestor name that is valid

[APP–21155] You must not change the Priority of the ECO when the ECO or any of its revised

items are scheduled.

[APP–21156] You must enter an existing Change Notice

[APP–21157] The Change Order Type you entered must have an Assembly Type compatible with

that of the revised item’s.

[APP–21158] You must enter an existing change order type

[APP–21159] You cannot change the ECO status when approval has been requested.

[APP–21160] You cannot access an ECO that is either implemented or canceled

[APP–21161] Implementation Date and Initiation Date cannot be updated.

[APP–21162] You cannot update the values for Implementation Date, Change Notice, Auto

Implement Date, Organization Id, Bill Sequence Id, Alternate BOM Designatory, or Revised Item

Id.

[APP–21163] The ECO record you are trying to update does not exist anymore.

[APP–21164] The referenced Change Order Type does not exist anymore.

[APP–21165] You cannot reschedule a revised item if approval has been requested for the ECO, or

if the Scheduled Date value is greater than the Disable Date value of any of its revised components

with ACD Type of 1 or 2.

[APP–21166] You must enter a valid organization that is going to be responsible for the ECO

[APP–21167] You cannot change the status of the revised item if an approval has been requested for

the ECO or if the ECO does not have Status Type set to 1.

[APP–21168] You must enter a valid organization

[APP–21169] You must enter a unique value for Bill Sequence Id

[APP–21170] You must enter values for Status Type and Approval Status Type.

[APP–21171] You cannot access the referenced Change Order Type.

[APP–21172] You do not have access to this revised item’s item type.

[APP–21173] The Revised Item you entered must have an assembly type compatible with that of the

Change Order Type.

[APP–21174] The approval status for the ECO must be ’Approved’

[APP–21175] A Scheduled Date value could not be found for this use up item and use up plan

combination.

[APP–21175] The substitute component must exist and must have valid attributes.

[APP–21176] You cannot delete an ECO while it still has revised items

[APP–21178] You must enter a Responsible Organization Id.

[APP–21179] The substitute component is for a common bill. The substitute component must exist

in all organizations that have the common bill.

[APP–21180] You must enter a unique revision for the ECO

[APP–21181] You cannot update the values for Change Notice, ACD Type, or Component Sequence

Id.

[APP–21182] You must enter a valid REVISION_ID value

[APP–21183] The row you want to lock has already been locked.

[APP–21184] The row you want to lock has already been deleted.

[APP–21185] Some columns in the row which you want to lock have already been changed.

[APP–21186] The row you want to update does not exist in the table.

[APP–21187] The Assembly Item Id was not found. You must enter valid values for Organization

Id, and Component Item Number.

[APP–21188] You must enter a valid value for REVISED_ITEM_SEQUENCE_ID

[APP–21189] The Substitute Component Id was not found. YOu must enter valid values for

Organization Id, and Substitute Component Number.

[APP–21190] You cannot delete a revised item if it is canceled, implemented, or if it has

unimplemented components.

[APP–21191] The Component Item Id was not found. You must enter valid values for Organization

Id, and Component Item Number.

[APP–21192] You must enter a unique value for REVISED_ITEM_SEQUENCE_ID

[APP–21193] You cannot enter a new item revision for an alternate bill.

[APP–21195] Revision value is required.

[APP–21196] You must specify a new revision for this item

[APP–21197] You cannot update the values for Change Notice, Organization Id, or Revision. to

update the Revision, please enter a value for New Revision.

[APP–21198] You must specify a valid use up item

[APP–21199] Disable Date for a component must be greater than current date.

[APP–21200] Product Family items cannot be added as components to a bill.

[APP–21201] Planning Factor must be 100 for the combination of attributes. Planning factor can be

other than 100 only if: Revised item is a Planning bill OR Revised item is a Model or Option Calss

bill and component is optional OR Revised Item is Model or Option Class bill and component is not

optional and revised components forecast control is set to Consume and Derive.

[APP–21202] The new item revision is being used in another ECO – you must enter a unique new

item revision

[APP–21203] Invalid value fo Supply Subinventory. Please verify the value against the values of

the profile option INV:Allow Expense To Asset Transer, and the value of the Restrict Subinventory

field.

[APP–21204] The new item revision must be greater than the current revision

[APP–21205] The component record you are trying to update or delete does not exist or may have

been deleted.

[APP–21206] You must enter an existing component item

[APP–21207] The component record you are trying to update has already been modified by another

user.

[APP–21208] The component item you are referencing is an invalid BOM item type

[APP–21209] Creation date, Created by, Change notice, and Reference Designator cannot be

updated.

[APP–21210] You must enter a valid value for ITEM_NUM

[APP–21211] The Approval Request Date must not be greater than the approval date.

[APP–21213] The assembly item used is either implemented or canceled. You cannot add, delete or

modify components whose assembly item is implemented or canceled.

[APP–21214] The revised item effective date must be greater than or equal to today’s date

[APP–21215] The reference designator record you are trying to update or delete does not exist or

may have been deleted.

[APP–21216] You must enter a value for Component Sequence Id.

[APP–21217] Use up item must be either the revised item or one of its implemented components.

[APP–21218] The component item does not have the BOM_ENABLED_FLAG set to yes

[APP–21219] The combination of Operation Sequence Number, Effectivity date, Bill Sequence Id,

and Component item id already exists. Please enter a different Operation Sequence Number.

[APP–21220] No Bill Sequence Id was found. You must enter a Bill Sequence Id value.

[APP–21221] The reference designator record you are trying to update has been changed by another

user.

[APP–21222] You must enter a valid Revision Id Value.

[APP–21223] You must assign an existing item as the substitute component.

[APP–21224] The Approval Status must be either Approved or Rejected.

[APP–21225] The ECO must be approved before it can be scheduled.

[APP–21226] No value was found for the Shceduled Date, You must enter a value for the

Scheduled Date.

[APP–21227] The revised item record you are trying to modify does not exist anymore.

[APP–21228] You have entered a component whose effective and disable dates overlap with the

existing dates for the same component

[APP–21229] You cannot schedlue an ECO if it has a Workflow Approval Process.

[APP–21230] The bill for this component is a common bill referenced by bills in other

organizations. There this component must exist and have the correct attributes in those other

organizations as well.

[APP–21231] The revised item does not have a current (implemented) revision.

[APP–21232] The component violates the bom matrix.

[APP–21233] You must not enter an Implementation Date value.

[APP–21234] The component you are adding already exists

[APP–21235] The component record you are trying to modify does not exist.

[APP–21236] You cannot add a component to a bill that is referencing another bill as a common.

[APP–21237] The revised item referenced by this component does not have a primary bill. ACD

type for the component should be add if the primary bill does not exist.

[APP–21238] You must not enter a Status Type value of Implemented.

[APP–21239] You must not enter a Status Type value of Cancelled when trying to create a revised

item for an ECO.

[APP–21240] You must not enter a Status Type value of Cancelled while creating a new ECO.

[APP–21244] The component must be optional for this comination of attributes

[APP–21248] You cannot have ATP CHECK set to yes for the existing combination of attributes

[APP–21250] Component cannot be required to ship or required for revenue if the assembly item is

an ATO item

[APP–21252] Minimum quantity must be less than or equal to component quantity

[APP–21254] Maximum quantity must be greater than or equal to component quantity

[APP–21256] The component yield factor must be equal to one for the combination of attributes you

have entered

[APP–21258] Component cannot have MUTUTALLY_EXCLUSIVE_OPTIONS set to yes for the

combination of attributes you have entered

[APP–21560] Component WIP_SUPPLY_TYPE must be Phantom for the combination of attributes

you have entered

[APP–21570] You must enter a value for ACD_TYPE

[APP–21572] You cannot add, change or diable reference designators or substitute components if

the parent component’s ACD_TYPE is set to disable in the ECO

[APP–21576] Reference Component Sequence Id does not exist

[APP–21580] Old component sequence Id does not exist

[APP–21582] You must enter a unique reference designator value

[APP–21586] You must enter a valid BILL_SEQUENCE_ID value

[APP–21594] You must assign an existing implemented item as the substitute component

[APP–21600] You must enter a substitute component that is not the same as the assembly item or

parent component.

[APP–21602] Substitute component quantity cannot be zero

[APP–21604] The substitute component you entered for the component already exists

[APP–21610] The Bill Sequence Id was not found. You must enter valid values for

ORGANIZATION ID, ASSEMBLY TEM ID and ALTERNATE BOM DESIGNATOR

[APP–21614] The Component Sequence Id was not found. You must enter valid values for

effectivity date, Operation seq num, component item id and bill sequence id.

[APP–21616] You must enter a valid supply locator for the organization you have chosen

[APP–21618] You must enter a valid revised item

[APP–21620] You must enter a valid Dispostion Type

[APP–21622] Early Scheduled Date must be less than or equal to the Scheduled Date

[APP–21624] You must enter a value of 1 or 2 for QUANTITY_RELATED

[APP–21626] You must enter a value of 1 or 2 for SO_BASIS

[APP–21628] You must enter a value of 1 or 2 for OPTIONAL

[APP–21630] You must enter a value of 1 or 2 for CHECK_ATP

[APP–21632] You must enter a value of 1 or 2 for MUTUALLY_EXCLUSIVE_OPTIONS

[APP–21634] You must enter a value of 1 or 2 for INCLUDE_IN_COST_ROLLUP

[APP–21636] You must enter a value of 1 or 2 for REQUIRED_TO_SHIP

[APP–21638] You must enter a value of 1 or 2 for REQUIRED_FOR_REVENUE

[APP–21640] You must enter a valid value for INCLUDE_ON_SHIP_DOCS

[APP–21642] You must enter a value of 1 or 2 for USE_UP

[APP–21644] You must enter a valid value for WIP_SUPPLY_TYPE

[APP–21648] You must enter a value of 1 or 2 for SHIPPING_ALLOWED

[APP–21652] You must enter a value of 1 or 2 for INCLUDE_ON_BILL_DOCS

[APP–21654] You must enter a valid value for USE_UP_PLAN_NAME

[APP–21656] You must enter a valid Supply Subinventory

[APP–21658] You must enter a value of 1 or 2 for PICK_COMPONENTS

[APP–21662] A Workflow Process was found for this ECO. You must not enter an Approval List

when a Workflow Process exists.

[APP–21664] You must enter a valid value for REQUESTOR_ID

[APP–21666] You must enter values for ORGANIZATION_ID and CHANGE_NOTICE

[APP–21668] You must enter a valid Approval Status value

[APP–21672] You must enter a valid Approval List value

[APP–21674] You must enter a Change Order Type value

[APP–21676] You must enter a valid Status Type value

[APP–21678] You must enter a valid value for REASON_CODE

[APP–21680] You must enter a valid value for PRIORITY_CODE

[APP–21682] The CHANGE_NOTICE value you have entered already exists

[APP–21684] You cannot create, update or delete an already implemented or canceled ECO

[APP–21690] The Approval Status you have entered is not valid for an ECO that has an Approval

List assigned to it

[APP–21692] You must update or delete an already existing record. The original referenced record

does not exist in the database.

[APP–21694] You must enter a value for CHANGE_NOTICE

[APP–21696] You must enter an Organization Id

[APP–21698] You must enter an ECO revision value

[APP–21700] You must enter a value for the ECO REVISION_ID

[APP–21702] The Approval Status you have entered is invalid since a Workflow Process exists for

this ECO

[APP–21704] You cannot update an ECO if it has been implemented or canceled, or if an approval

has been requested through a Workflow Process.

[APP–21706] You cannot delete an ECO that has requested approval through a Workflow Process

[APP–21710] You cannot change the approval list when approval has been requested

[APP–21712] You cannot entered a Cancellation Date or Cancellation Comments when the ECO is

not marked as canceled

[APP–21714] You must enter a Use Up Item since you have entered a Use Up Plan

[APP–21716] You must enter a Revised Item for this record

[APP–21718] You must enter a value for Revised Item Sequence Id.

[APP–21720] You cannot create, update or delete an already implemented or canceled revised item

[APP–21724] The revision you have entered for this revised item has already been implemented

[APP–21726] You must enter a valid value for MRP_ACTIVE

[APP–21728] You must enter a valid value for COMPONENT_QUANTITY

[APP–21730] The component is already Implemented. Modifications cannot be made to

implemented components.

[APP–21732] A required value from Reference Desingnator or Component Sequence Id or ACD

Type is empty. A record cannot be secured or created if any of these values is missing.

[APP–21734] ACD Type of the reference designator must be ADD if the ACD Type of the parent

component is ADD.

[APP–21736] Reference Designators and Substitute Components cannot be added if the bill is a

Planning Bill, or if the component is Model, Option Class, or Planning item.

[APP–21738] Update to Reference Designator record failed.

[APP–21740] The reference designator record could not be locked. The record values are invalid or

the record might have already been deleted.

[APP–21742] Querying of record failed. The record does not exist or may have been deleted.

[APP–21744] The revised component could not be secured. The record values may be invalid or the

record might have been deleted.

[APP–21746] Required for Revenue field has an invalid value. It can only have either 1 or 2.

[APP–21748] The revised item is referencing a common bill. Operations on these bill’s cannot be

performed.

[APP–21760] The component’s revised item has already been implemented

[APP–21762] You must enter a value for Component Sequence Id, Substitute Component Id, ACD

Type, and Substitute Item Quantity.

[APP–21764] You must enter a Substitute Component

[APP–21766] You must enter a parent Component

[APP–21770] You must set ACD Type to 1.

[APP–21771] The ECO revision record is refering to an change notice, that does not correspond to

the parent record. You may not enter a change notice value that does not correspond to the change

notice of the business object.

[APP–21772] The revised item record is referring to a change notice that does not match the value

of the parent record. You may not enter a change notice that does not belong to the same business

object.

[APP–21773] The revised component record is either referring to a change notice that does not

match the parent record or is referring to a revised item that does not belong to the same business

object. The component must use the change notice and the revised item values that match the

business object.

[APP–21774] The reference designator record is referring to a change notice that does not match the

parent record or is referring to a component record that does not belong to the same business object.

You may not enter values for component item and change notice that do not match the business

object.

[APP–21774] The substitute component record is referring to a change notice that does not match

the parent record or is referring to a component record that does not belong to the same business

object. You may not enter values for component item and change notice that do not match the

business object.

[APP–21775] The combination of component_sequence_id and component_item_id does not exist.

Please enter a value for the component_sequence_id and component_item_id that point to a valid

record.

[APP–22000] You cannot delete an active audit

Cause:

You have tried to delete an active audit.

Action:

Deactivate audits before trying to delete them.

[APP–22002] You cannot delete a predefined audit

Cause:

You have tried to delete a predefined audit. You can only delete audits that are not shipped as part

of Oracle Master Scheduling/MRP.

Action:

Do not try to delete predefined audits.

[APP–22004] The Information Audit has found invalid data

Cause:

One or more of the information audits has found data that are incorrect and require attention.

Action:

Determine which audits have failed and resolve the problems or contact your customer support

representative.

[APP–22006] A bill of resources for this assembly already exists. Query for details

Cause:

You have selected an assembly for which a bill of resources already exists.

Action:

Query the assembly and modify the existing bill of resources.

[APP–22008] A repetitive requirement for the bill of resource item already exists

Cause:

You cannot define multiple repetitive bill of resource requirements for the bill of resource item.

Action:

Delete this requirement or choose a different source item.

[APP–22010] A loop has been detected in the bill of materials for item &ITEM (Id=&ITEM_ID)

Cause:

The item &ITEM (Id=&ITEM_ID) is a component of itself.

Action:

Determine which items cause the loop, and remove the loop from the dependency structure.

[APP–22012] Run the bill of resources load

[APP–22014] You cannot access this form

Cause:

You have tried to use an Oracle Capacity form before defining capacity parameters for the current

organization.

Action:

Define capacity parameters for the current organization using the Define Capacity Planning

Parameters form in Oracle Capacity.

[APP–22016] Overlapping in date range occurs at Effective Date: &ENTITY

[APP–22018] Sourcing rule is already assigned and cannot be changed to planning inactive

[APP–22020] A loop has been detected in the bill of materials for item &ITEM (Id=&ITEM_ID)

Cause:

The item &ITEM (Id=&ITEM_ID) is a component of itself.

Action:

Determine which items cause the loop, and remove the loop from the dependency structure.

[APP–22022] You cannot delete a forecast set that contains forecasts

Cause:

You have tried to delete a forecast set that contains one or more forecasts.

Action:

Delete all the forecasts contained within the forecast set before deleting the forecast set itself.

[APP–22023] &ENTITY1 must be greater than or equal to &ENTITY2

Cause:

The current routine cannot successfully perform the specified comparison.

Action:

Contact your customer support representative.

[APP–22024] You cannot delete forecast overconsumption entries in disabled forecast sets.

Cause:

You cannot delete forecast overconsumption entries that belong to a disabled forecast set.

Action: If you need to delete forecast overconsumption entries for the current forecast set,

delete or modify its disable date first.

[APP–22026] You must select a forecast with a more detailed forecast level

Cause:

You have tried to load a forecast with a less detailed forecast level into a forecast with a more

detailed forecast level. This is not allowed. For example, you are not allowed to load a forecast

with a forecast level of Customer into a forecast with a forecast level of Ship–to.

Action:

Choose a forecast with a forecast level which is at the same level of detail, or more detailed, than

the forecast level of the forecast you are loading into.

[APP–22028] You cannot modify forecasts in disabled forecast sets. Clear your changes

Cause:

You have tried to create or modify a forecast in a disabled forecast set.

Action:

Clear your changes. If you need to create or modify forecasts for the current forecast set, delete or

modify it’s disable date first.

[APP–22030] Warning: You cannot create or modify entries for a forecast set

Cause:

You cannot create new forecast entries or modify existing forecast entries that belong to a forecast

set. The only forecast entries that can exist for a forecast set are those that were created as a result

of overconsumption. You can delete these entries, but you cannot modify them or create new ones.

Action:

In order to create or modify forecast entries, you must choose a forecast instead of a forecast set.

[APP–22032] The workday calendar has not been built

Cause:

The workday calendar has not been built.

Action:

Build the workday calendar before continuing.

[APP–22033] &ENTITY1 cannot be greater than &ENTITY2

Cause:

The current routine cannot successfully perform the specified comparison.

Action:

Contact your customer support representative.

[APP–22034] Cannot load &LOAD

Cause:

The current routine cannot load the specified entity.

Action:

Contact your customer support representative.

[APP–22038] Cannot reschedule or cancel &ORDER.

[APP–22040] Cannot select &ENTITY1 for &ENTITY2

Cause:

The current routine cannot select the specified entity.

Action:

Contact your customer support representative.

[APP–22042] Cannot update &ENTITY

Cause:

The current routine cannot update the specified entity.

Action:

Contact your customer support representative.

[APP–22044] Cannot update anchor date

Cause:

The current form cannot update the anchor date for the current organization because it is unable to

lock the mrp_parameters table.

Action:

Check if other users are locking this table in the Define Planning Parameters form, or contact your

system administrator.

[APP–22046] &ROUTINE: Cannot launch &PROCESS

Cause:

The current routine cannot launch the specified process.

Action:

Contact your customer support representative.

[APP–22048] &ROUTINE: Could not select &COLUMN

Cause:

The current routine cannot select the specified entity.

Action:

Contact your customer support representative.

[APP–22049] &ROUTINE: Unable to &ACTION field &FIELD

Cause:

The current routine cannot perform the specified action.

Action:

Contact your customer support representative.

[APP–22050] Date falls outside the boundaries of the workday calendar

Cause:

The current date is outside the range of valid workdays. The date is either before the start of the

workday calendar or after the end of the workday calendar.

Action:

Extend the boundaries of your workday calendar.

[APP–22052] &THE_DATE is outside the range of valid calendar dates

Cause:

The specified date is outside the range of valid workdays (&LOW_DATE to &HIGH_DATE). The

date is either before the start of the workday calendar or after the end of the workday calendar.

(Routine: &ROUTINE)

Action:

Extend the boundaries of your workday calendar.

[APP–22056] You cannot delete exception set &ENTITY

Cause:

You have tried to delete a planning exception set that is assigned to one or more items in the Define

Item form in Oracle Inventory.

Action:

Remove references to the current exception set in the Define Item form in Oracle Inventory and

rerun MRP before trying to delete it again.

[APP–22058] &ROUTINE: &TEXT

Cause:

The current routine cannot perform the specified action.

Action:

Contact your customer support representative.

[APP–22062] &ROUTINE: Insufficient arguments for &OPERATION

Cause:

The current routine cannot perform the specified operation because it has been passed an

insufficient number of arguments.

Action:

Contact your customer support representative.

[APP–22064] An internal error has occurred (&PROGFILE, &ERRNUMBER)

Cause:

The current routine encountered the specified internal error.

Action:

Contact your customer support representative.

[APP–22065] The Snapshot was unable to &ACTION lock file: &ERR_CODE

Cause:

The Snapshot was unable to perform the specified action to the lock file.

Action:

Contact your customer support representative.

[APP–22066] &ROUTINE: Invalid value of ’&VALUE’ for the argument ’&ARGUMENT’

Cause:

The current routine was passed an invalid value for the specified argument.

Action:

Contact your customer support representative.

[APP–22068] Forecast entries exist outside the range of valid workdays

Cause:

Forecast entries exist outside the range of valid workdays. The dates are either before the start of

the workday calendar or after the end of the workday calendar.

Action:

Extend the boundaries of your workday calendar.

[APP–22070] vltoch: Invalid mask &MASK (error type &NUM)

Cause:

the function vltoch() was passed an invalid mask string. The error type specified identifies what is

wrong with the mask: 1 – ’>’ must come before any digits 2 – Only one ’>’ allowed in mask 3

– ’(’ is embedded in # 4 – Only one set of ()’s allowed 5 – ’)’ does not match ’(’ 6 – ’(’ is embedded

in # 7 – Only one set of ()’s allowed 8 – ’)’ does not match ’(’ 9 – Parentheses do not match 10 –

invalid ’>’ character in the mask 11 – Invalid mask character (after decimal) 12 – Invalid mask

character (before decimal) 13 – Multibyte character in the character mask 14 – mask length should

be less than 99 characters.

[APP–22071] Profile &PROFILE has an invalid value of &VALUE

Cause:

The current routine encountered an invalid value for the specified profile option.

Action:

Assign a valid value to the specified profile option.

[APP–22072] Master schedule entries exist outside the range of valid workdays

Cause:

Master Demand Schedule and/or Master Production Schedules entries exist outside the range of

valid workdays. The dates are either before the start of the workday calendar or after the end of the

workday calendar.

Action:

Extend the boundaries of your workday calendar.

[APP–22074] You must enter time information using the HH:MM:SS format

Cause:

You have tried to enter a date using a format other than HH:MM:SS.

Action:

Enter the date using the HH:MM:SS format, where ’HH’ represents hours, ’MM’ represents

minutes, and ’SS’ represents seconds. For example, if you want the Planning Manager to run once

every 3 hours, 2 minutes and 15 seconds, enter: 03:02:15.

[APP–22075] An internal error has occurred (&PROGFILE, &ERRNUMBER, &ARG1, &ARG2)

Cause:

The current routine encountered the specified x

Action:

Contact your customer supportrepresentative.

[APP–22076] This item has already been added to this &SCHEDULE. Query for details

Cause:

You have tried to add an item to a forecast or master schedule to which the item has already been

added.

Action:

Query the existing item if you wish to create or modify entries for it.

[APP–22078] Warning: This item has order modifier associated with it

Cause:

You have modified the quantity for an item with order modifier ’&MODIFIER’ associated with it.

Action:

No action required.

[APP–22082] &ROUTINE: No rows selected from &TABLE

Cause:

The current routine cannot select any rows from the specified table.

Action:

Contact your customer support representative.

[APP–22084] Entity &ENTITY doesn’t exist

Cause:

The current routine cannot find the specified entity.

Action:

Contact your customer support representative.

[APP–22086] &ROUTINE: Cannot allocate memory for &VAR

Cause:

The current routine cannot allocate memory for the specified entity.

Action:

Contact your customer support representative.

[APP–22088] The planning processes have not been run for &COLUMN

Cause:

The planning processes have not yet been run for the current plan.

Action:

Run the planning processes to generate a material plan using the Launch Planning Processes form.

[APP–22090] &ROUTINE: Failed when called from &FUNCTION, &LOCATION

Cause:

The current routine failed when called from the specified function.

Action:

Check the concurrent manager for details.

[APP–22092] The &PROCESS1 has run more recently than the &PROCESS2

Cause:

A valid plan depends upon the planning processes running in the following order: Exploder,

Snapshot, Planner, CRP Planner. The current plan is invalid because the planning process

completion dates do not increase sequentially. For example, the Planner completion date may be

less than the Snapshot completion date. This can occur if one of the planning processes errors

before completing, or if the plan is currently being generated.

Action:

Check the concurrent manager for details.

[APP–22094] Request &REQUEST_ID completed prematurely

Cause:

The specified concurrent request completed prematurely. This concurrent program is dependent

upon the specified concurrent request either running or pending.

Action:

Contact your customer support representative.

[APP–22096] Request &REQUEST_ID was deleted

Cause:

The specified concurrent request has been deleted. All of the worker requests must complete

successfully for the material plan to be valid.

Action:

Examine the concurrent request log file for details.

[APP–22098] Request &REQUEST_ID is disabled

Cause:

The program to be executed by the specified concurrent request was disabled after the request was

submitted.

Action:

Re–enable the concurrent program using the Define Concurrent Program form in Application Object

Library.

[APP–22100] Request &REQUEST_ID failed

Cause:

The specified concurrent request exited with an error.

Action:

Examine the concurrent request log file for details.

[APP–22102] Request &REQUEST_ID is inactive

Cause:

The specified concurrent request is inactive. This request must be able to run for the concurrent

program to run successfully.

Action:

Re–launch this concurrent program.

[APP–22104] Request &REQUEST_ID is on hold

Cause:

The specified concurrent request has been placed on hold. This request must be able to run for the

concurrent program to run successfully.

Action:

Re–launch this concurrent program.

[APP–22106] Request &REQUEST_ID is pending

Cause:

The specified concurrent request is pending. This indicates a problem with the planning processes.

Action:

Contact your customer support representative.

[APP–22108] Request &REQUEST_ID is terminating

Cause:

The specified concurrent request has been terminated. This request must complete successfully for

the concurrent program to run properly.

Action:

Relaunch the concurrent program.

[APP–22110] This row was rejected due to a processing error for a previous row in the batch

[APP–22112] Running in debug mode

Debug: &DEBUG_TEXT:

[APP–22114] Warning: The Planning Manager is inactive

Cause:

The Planing Manager is not running. Forecast consumption and master schedule relief may not be

up to date.

Action:

Navigate to MRP Setup PlanningManager and start the Planning Manager

[APP–22116] The Planning Manager is already active

Cause:

Only one Planning Manager can be running or pending at any one time.

Action:

Terminate the current Planning Manager before launching the Planning Manager with a new

resubmission interval.

[APP–22120] The table &TABLE is currently locked

Cause:

The current process is unable to lock the specified table because it is already locked by another

process.

Action:

Terminate that process that is locking the table.

[APP–22122] MPS schedules cannot contain items that are not MPS planned

[APP–22124] Cannot load a repetitive schedule entry for a discretely planned item

[APP–22126] Transaction id does not exist or belongs to another organization or designator

[APP–22128] Duplicate initialization

Cause:

The current routine has already been initialized.

Action:

Contact your customer support representative.

[APP–22130] Cannot connect to database

Cause:

The current routine cannot connect to the database.

Action:

Contact your system administrator or customer support representative.

[APP–22132] Cannot get profile option &OPTION

Cause:

The current routine cannot retrieve a value for the specified profile option.

Action:

Contact your customer support representative.

[APP–22134] Cannot open file &FILE

Cause:

The current routine cannot open the specified file.

Action:

Contact your customer support representative.

[APP–22136] Cannot put profile option &OPTION

Cause:

The current routine cannot update the value of the specified profile.

Action:

Contact your customer support representative.

[APP–22138] &FUNCTION has been called

Cause:

The current routine is trying to call the specified function more than once.

Action:

Contact your customer support representative.

[APP–22140] Missing initialization (&FUNCTION)

Cause:

The current routine needs to be initialized.

Action:

Contact your customer support representative.

[APP–22142] ”&TOKEN=” argument needed

Cause:

The current routine cannot continue without a value for the specified token.

Action:

Contact your customer support representative.

[APP–22146] You cannot access this form

Cause:

You have tried to use an Oracle Master Scheduling/MRP or Oracle Capacity form before compiling

a workday calendar for the current organization.

Action:

Compile a workday calendar for the current organization using the Define Workday Calendar form

in Oracle Bills of Material. Make sure that the organization is associated with the appropriate

calendar and exception set in the Define Inventory Parameters form in Oracle Inventory.

[APP–22148] You cannot access this form

Cause:

You have tried to use an Oracle Master Scheduling/MRP form before defining planning parameters

for the current organization.

Action:

Define planning parameters for the current organization using the Define Planning Parameters form

in Oracle Master Scheduling/MRP.

[APP–22150] You have not defined a default discrete job class

Cause:

You have not defined a default discrete job class.

Action:

Use \ Navigate WIP Setup Parameters to define a default discrete class.

[APP–22152] You have not defined yourself as an employee

Cause:

You have not defined yourself as an employee.

Action:

Use \ Navigate Setup Organization Personnel Employees Enter to define yourself as an employee.

Ask your System Administrator to associate your user name with your employee record using the \

Navigate Security User option of the System Administrator responsibility.

[APP–22154] You cannot implement duplicate schedules

Cause:

You have tried to define a schedule that already exists. Duplicate schedules are defined as

schedules where the First Unit Completion Date and Line are the same.

Action:

Modify one of the duplicate schedules.

[APP–22156] This item has an invalid combination of make and buy attributes

Cause:

Either the item’s ’Make or Buy’ attribute is set to ’Make’ but it has the ’Build in WIP’ attribute set

to No, or the ’Make or Buy’ attribute is set to Buy, but the ’Purchasable’ attribute is set to No.

Action:

Update the ’Make or Buy’, ’Build in WIP’, or ’Purchasable’ item attributes in the Update Item

form. Run the Audit Information Report for a complete list of items with invalid attributes.

[APP–22158] The &PROCESS has not completed for this plan

Cause:

The specified process has not successfully completed. This could be because the process errored

last time it ran, or because the plan is currently being generated.

Action:

Check the concurrent manager for details.

[APP–22160] The &PROCESS has not been run for this plan

Cause:

The specified process has not yet run. This could be because a previous planning process errored, or

because the plan is currently being generated.

Action:

Check the concurrent manager for details.

[APP–22162] The Snapshot was unable to lock the &TABLE table

Cause:

The Snapshot was unable to lock the specified table. As a result, Oracle Master Scheduling/MRP

cannot guarantee that the data is a read–consistent snapshot.

Action:

Contact your system administrator or customer support representative.

[APP–22166] The Snapshot may have detected a loop in the dependency structure

Cause:

The snapshot may have detected a loop in the dependency structure while it was calculating low

level codes. This could be because of a loop that was introduced by manually adding a component

to a discrete job. For example, if you have an assembly A with a component B, and B has a

component C (ie A | B | C) and you create a discrete job for B, and manually add item A as a

component on that discrete job, then you have introduced a loop in the dependency structure.

Action:

The loop involves some of the items listed in the following output. Determine which items cause

the loop, and remove the loop from the dependency structure.

[APP–22168] The number of Snapshot workers is set to zero

Cause:

The profile option MRP:Snapshot Workers is set to zero. The Snapshot will run without locking

tables and therefore cannot guarantee a read–consistent snapshot.

Action:

Set the profile MRP:Snapshot Workers to a value greater than zero.

[APP–22170] Tables locked at &DATE_TIME

Cause:

The Snapshot will pause execution until the lock is released or until the wait time has passed.

Action:

Wait for the lock to be released or the wait time to pass.

[APP–22172] This assignment combination (assignment type, organization, item/category, source

type) already exists. Please select another

[APP–22174] This assignment set contains category set references that are different than the one in

the profile option. Please set the ’MRP:Sourcing Rule Category Set’ profile option properly.

[APP–22176] The CRP Inquiry manager is currently not available. Please set up or activate the CRP

Inquiry manager.

[APP–22178] The request sent to the CRP Inquiry Manager has timed out. The database could be

overloaded. Please try again at a later time.

[APP–24000] &MODULE: cannot initialize control structure.

[APP–24002] Another cost update process is currently running in your organization.

Cause:

Only one Standard Cost Update can run at a time in an organization.

Action:

Submit your Standard Cost Update program at a later time.

[APP–24004] The interorg cost copy failed because one or more entities used in the source

organization are not defined in the target organization.

Cause:

The interorg cost copy program requires that all entities used in the source organization are defined

in the target organization.

Action:

Review the list below to identify the missing entities and define them in the target organization.

[APP–24006] &MODULE: error processing in &FUNC

Cause:

An error is detected in function &FUNC while executing the module &MODULE.

Action:

Examine the request log file and contact your Oracle support representative if necessary.

[APP–24008] The functional currency for this organization is disabled

Cause:

The functional currency defined for this organization (&CURRENCY) is currently disabled.

Action:

Contact your system administrator.

[APP–24010] &MODULE has detected an internal data error

Cause:

&MODULE has detected an internal data error. This is an abnormal condition.

Action:

Contact your system administrator or Oracle Customer Support.

[APP–24012] You cannot update this field for the Frozen Standard cost type

Cause:

The Use Rollup Defaults field is not updatable for the Frozen cost type. Cost control information

for the Frozen cost type can not be defaulted from any other cost type.

Action:

No action is required.

[APP–24014] You cannot update this field for the Frozen Standard cost type

Cause:

The Use Default Controls field is not updatable for the Frozen cost type. Cost control information

for the Frozen cost type can not be defaulted from any other cost type.

Action:

No action is required.

[APP–24016] You cannot update the field because there are user defined costs

Cause:

You may not update Use Rollup Defaults field from No to Yes for items that have manually entered

costs for the cost type. Cost Rollup deletes all costs for items where Use Rollup Defaults is Yes.

Action:

Delete all the manually entered costs and then update Use Rollup Defaults field.

[APP–24018] You cannot update the field because there are user defined costs

Cause:

You may not update Use Default Controls field from No to Yes for items that have manually entered

costs for the cost type. Cost Rollup deletes all costs for items where Use Default Controls is Yes.

Action:

Delete all the manually entered costs and then update Use Default Controls field.

[APP–24020] You have not defined cost information for the default cost type

Cause:

This cost type uses default cost type that has no information for this item. By changing Use Rollup

Defaults to Yes, Cost Rollup needs to use the cost control information of the defaulted cost type.

Action:

None; Or, Define cost control information for the default cost type of this cost type.

[APP–24022] You have not defined cost information for the default cost type

Cause:

This cost type uses default cost type that has no information for this item. By changing Use Default

Controls to Yes, Cost Rollup needs to use the cost control information of the defaulted cost type.

Action:

None; Or, Define cost control information for the default cost type of this cost type.

[APP–24024] You cannot update the item controls or costs because the costs are defaulted.

Cause:

You cannot edit the item costs or the cost control information when the source of the items’s cost

controls are from another cost type. This defaulting occurs when you perform a cost rollup, with no

cost information for the items you roll up in the selected cost type. Cost rollup uses the default cost

type as the source of the cost controls. The controls are based on rollup, lot size, inventory asset,

and shrinkage. The cost rollup also defaults any manually entered costs from the default cost type,

such as material overhead, etc.

Action:

To edit the manually entered item costs or the cost control information you must first change Use

Default Controls from Yes to No. Changing the Use Default Controls does not delete any cost

information, however, when the Use Default Controls is no, the cost rollup no longer uses the cost

information from the default cost type.

[APP–24026] You cannot edit the &ACCOUNT account.

Cause:

You cannot edit the &ACCOUNT account because it is maintained in the master cost org.

Action:

Change your working organization to the master organization and re–enter your request.

[APP–24028] You have already defined &ENTITY for &FIELD_VALUE

Cause:

The value you have entered exists.

Action:

Use a different value for the field.

[APP–24030] Error occurred in the Costing Open Interface

Cause:

Problem occurs in costing open interface routine

Action:

Contact the Oracle Representative

[APP–24032] &NUM transaction(s) failed processing

Cause:

There are &NUM transaction(s) left unprocessed in the interface table.

Action:

Please review the error(s) for this transaction group in the View WIP Transaction Interface form.

[APP–24034] Please save changes before you go to previous or next record

Cause:

You have updated the lot size or shrinkage rate for the cost type. The form needs to know whether

the change needs to be saved and item costs need to be recomputed before you go to another cost

type.

Action:

You can either discard the change or save the change.

[APP–24036] You have specified an incorrect number of arguments for &ENTITY.

Cause:

You have not supplied all the arguments needed for &ENTITY that you are running.

Action:

Please read Oracle Cost Management Reference Manual for requirements on running &ENTITY.

[APP–24038] You have specified an invalid value for argument &ENTITY.

Cause:

You have entered an invalid value for the argument &ENTITY.

Action:

Please consult the Oracle Cost Management Reference Manual for the valid values for this program.

[APP–24040] Your cost organization network uses multiple &ENTITY

Cause:

Your cost organization network uses more than one &ENTITY.

Action:

Examine your cost organization network and make the appropriate changes.

[APP–24042] Invalid Material Sub Element

Cause:

Invalid Material Sub Element defined in open interface mtl_system_items_interface table

Action:

Correct the Material Sub Element

[APP–24044] Average Cost Org could not get Material Overhead

Cause:

An error is detected in Open Interface, Material Overhead is not allowed under Average Cost

Organization

Action:

Update Material Overhead Sub element with NULL value in mtl_system_items_interface

[APP–24046] Invalid Material Overhead Sub Element

Cause:

Invalid Material Overhead Sub Element in open interface mtl_system_items_interface table

Action:

Correct the Material Overhead Sub Element

[APP–24048] Option &ENTITY1 is not valid

Cause:

You have specified an invalid option &ENTITY1.

Action:

Please refer to the Oracle Cost Management Reference Manual for the options available for the

program you are running.

[APP–24050] Purge option &ENTITY is not valid

Cause:

You have specified an invalid purge option &ENTITY.

Action:

Please refer to the Oracle Cost Management Reference Manual for the valid purge options.

[APP–24052] Item cost details are not available for this inquiry

[APP–24054] Invalid transaction type

[APP–24056] You cannot enter any cost because the inventory asset flag is set to No

Cause:

The item is designated as an expense item for this cost type. So you cannot navigate to the Item

Costs zone to enter any cost for the item for this cost type.

Action:

To enter cost information for this item in this cost type change the asset flag to Yes.

[APP–24058] Item shrinkage factor must be less than 1

Cause:

Item shrinkage factor must be less than 1.

Action:

Enter a number that is less than 1.

[APP–24060] You cannot update costs when transactions exist for an item

Cause:

The item has been transacted and the item frozen cost is used to value the transaction and thus can

not be altered.

Action:

Perform Cost Update to update the frozen cost for the item. Cost Update creates accounting

adjustments to your inventory, intransit and WIP values.

[APP–24062] Unable to obtain a lock on table &TABLE

Cause:

The program is unable to obtain a lock on the table &TABLE.

Action:

Resubmit the program at a later time.

[APP–24064] Unable to obtain a lock on table CST_ITEM_COSTS

Cause:

The program is unable to obtain a lock on the table CST_ITEM_COSTS.

Action:

Resubmit the program at a later time.

[APP–24066] Unable to obtain a lock on table CST_ITEM_COST_DETAILS

Cause:

The program is unable to obtain a lock on the table CST_ITEM_COST_DETAILS.

Action:

Resubmit the program at a later time.

[APP–24068] Lot size must be greater than zero

Cause:

Manufacturing lot size must be greater than 0.

Action:

Enter a number that is greater than 0.

[APP–24070] You cannot edit the &ACCOUNT account.

Cause: The &ACCOUNT account is maintained in the master cost org.

Action: Change your working organization to the master organization.

[APP–24072] This function is only valid in master costing organization.

Cause:

This organization gets cost information from another master costing organization, so you cannot

update cost information in this organization.

Action:

Change to the master costing organization.

[APP–24074] A multi–org cost type must default to a multi–org cost type organization.

[APP–24076] The Report number of levels cannot be less than 0

Cause:

The report number of levels cannot be less than 0 and it cannot be greater than the explosion

number of levels.

[APP–24078] The repetitive line does not have schedule allocation

Cause:

There is no record in WIP_TXN_ALLOCATIONS table for this repetitive schedule. For any

repetitive schedule transactions, the quantity being transacted data is stored in this

WIP_TXN_ALLOCATIONS table.

Action:

Contact Oracle Support Representatives

[APP–24080] Record not found in WIP_PERIOD_BALANCE

Cause:

There is no record in WIP_PERIOD_BALANCES for the repetitive schedule or job.

Action:

Contact Oracle Support Representative

[APP–24082] You cannot delete cost for the frozen standard or non–updatable cost types

Action:

Update the Allow Update field to Yes for the cost type, or use Cost Update to update costs for the

frozen standard cost type.

[APP–24084] You cannot disable the default material sub–element for the organization

Cause:

You are attempting to disable the material sub–element that is defined as the default material

sub–element for this organization.

Action:

To disable this material sub–element you must first update the default material sub–element name

referenced on your organization parameters.

[APP–24086] Elemental cost history is not available

Cause:

Elemental cost history is not available for standard cost history prior to Release 10.

Action:

No action is required.

[APP–24088] You cannot insert or update.

[APP–24090] Unable to obtain a lock on table &TABLE

Cause:

The profile option for CST:Wait for Locks was set to No for the Cost Rollup. The program exited

since it was unable to obtain a lock on the table &TABLE without having to wait.

[APP–24092] &ROUTINE: cannot allocate memory for &VAR

Cause:

The program &ROUTINE can not allocate memory of size &VAR.

Action:

Contact Oracle Support Representative.

[APP–24094] No open accounting period is available

Cause:

No open accounting period corresponding to the transaction date is available in your organization.

Action:

Please open the appropriate accounting period in the Open Accounting Periods form.

[APP–24096] Item shrinkage is not allowed for buy items

Cause:

The item is designated as a buy item (Based On Rollup is set to No) for this cost type. Shrinkage

for a buy item is not allowed.

Action:

Update Based On Rollup to Yes and enter the shrinkage.

[APP–24098] Posting is not allowed for this account

[APP–24100] You may not choose a Single Level Rollup with the Consolidated Report

Cause:

The consolidated report requires that the Assembly structures be exploded to the maximum number

of levels. With the single level rollup the assembly structures are exploded to 1 level only, which is

not sufficient for a Consolidated Report.

[APP–24102] The report number of levels must not exceed the bill explosion levels

Cause:

For a single level cost rollup the bill explosion levels is set to 1. For a full cost rollup it is set to the

maximum number of levels defined in the Define Bills of Material Parameters form which is

&MAX_LEVELS.

Action:

The number of levels on the report cannot exceed the number of bill explosion levels. Please enter

a number less than or equal to the bill explosion levels for the report number of levels.

[APP–24104] The alternate designator &DESIG for the cost type &COST_TYPE is invalid.

Cause:

The default alternate bom designator &DESIG for the cost type &COST_TYPE is invalid for the

&ORG organization.

Action:

Define the alternate designator &DESIG for the &ORG organization.

[APP–24106] Please select a cost update session

Cause:

A specific cost update session is required for the functionality you are currently using.

Action:

Please type in a cost update date or use quickpick to select a cost update session.

[APP–24108] Error processing in &PROCEDURE

Cause:

&MODULE has detected an ORACLE error (ORA–&ERROR) while executing stored procedure

&PROCEDURE.

Action:

Contact your system administrator or your Oracle support representative.

[APP–24110] This function is only valid for a standard costing organization

Cause:

The selected function is valid for a standard costing organization only.

[APP–24112] Failed to submit concurrent request

Cause:

Unable to submit a concurrent request.

Action:

Contact your system administrator or Oracle support representative.

[APP–24114] You cannot directly debit or credit a summary account

[APP–24116] Currency code is missing for this foreign currency transaction.

Cause:

This transaction is missing the currency code. Whenever a transaction has a currency conversion

rate (foreign exchange rate) the currency code must be populated.

Action: Please populate the currency code for this transaction.

[APP–24118] Exchange rate is missing for this foreign currency transaction.

Cause:

When the interfaced transaction is in a currency code that is not the same as the currency code of

the organization, the currency exchange rate (CURRENCY_CONVERSION_RATE) must be

populated. Since the interface validation does not check against the Oracle General Ledger rate

table (GL_DAILY_TRANSLATION_RATES) this rate may be from any source. However, all

Oracle Purchasing transactions in a foreign currency will have a exchange rate.

Action:

Please populate the CURRENCY_CONVERSION_RATE in the interface table.

[APP–24120] Assembly is not costed. Please re–enter

[APP–24122] Cost type &ENTITY is not updatable

Cause:

You cannot change the cost controls, costs or rollup the item when the cost type does not allow

changes. You cannot directly change the Frozen cost type unless the item has never been transacted.

Under average costing, you use the Average Cost Update form to change your average costs.

Action:

If the cost type is not Frozen or Average, change the Allow Updates attribute from No to Yes in the

Define Cost Type form.

[APP–24124] Insufficient privilege to maintain cost information.

Cause:

You do not have the privilege required to access this form.

Action:

Request privilege to maintain cost information.

[APP–24126] Insufficient privilege to view cost information

Cause:

You do not have the privilege required to access this form.

Action:

Request your system administrator for the privilege to update cost information.

[APP–24127] This function is valid only in organizations that are enabled for projects

Cause: This organization is not enabled for the use of projects, so this function is not available.

[APP–24128] This function is only valid for manufacturing average costing

Cause: The selected function is only valid for a manufacturing average costing organization.

[APP–24129] Another actual cost worker is currently running in your organization.

Cause:

Only one Actual Cost Woker can run at a time in an organization.

Action:

Actual Cost Worker will run when the currently running worker has completed.

[APP–24130]

Cause: &MODULE already running for the current organization.

Action: Please run the &MODULE at a later time.

[APP–24131] The current Organization is not set–up for any type of cost collection. Either set the

Organization parameter ’cost_collection_enabled’ to 1 or define atleast one Capital project related

transaction type.

[APP–24132] Expenditure types association with cost elements are incomplete. Define ’IN’ and

’OUT’ expenditure types for all cost elements.

[APP–24133] Either project or the task fields for the current transaction is NULL. Enter the project

and task for the transaction.

[APP–24134] Either transfer project or the task fields for the current transaction is NULL. Enter the

transactions transfer project and task.

[APP–24135] Either source project or the task fields for the current transaction or job is NULL.

Enter the transactions source project and task.

[APP–24136] System failed to arrive at the first material sub–element for the current item. Either

define atleast one material sub–element for the item in the AVERAGE RATES COST TYPE or else

define the organization level default material sub–element.

[APP–24137] Expenditure type associated with the current sub–element is NULL. Associate a valid

expenditure type to the sub–element.

[APP–24138] ’Expenditure Organization Id’ associated with the current department is NULL.

Associate a valid ’Expenditure Organization Id’ with the department.

[APP–24139] Project Manufacturing transaction sources are missing. Create valid transaction

sources in Oracle Projects.

[APP–24140] Project Manufacturing system linkages are missing. Create valid system linkages in

Oracle Projects.

[APP–24141] Warning: The current transaction has zero actual cost and was not reported to Oracle

Projects.

[APP–24142] Could not arrive at Expenditure Week Ending Date. Verify the Expenditure Cycle

Start Day using the Define Implementation Options form in Oracle Projects.

[APP–24143] The costing of this WIP transaction failed.

[APP–24144] No capitalization accounts were obtained from the manufacturing subledger for this

transaction. Either the cost distributor failed or the setup may have changed since the transaction

was initiated and before the cost collector was run.

[APP–24145] The hook returned an account with the value NULL. Either the account was not set

up or the hook logic is incorrect

[APP–24146] The costing snapshot failed due to a database error. Please take the these error

messages to your database administrator.

[APP–24147] No conversion rate has been defined for the combination of foreign currency and

conversion rate type used in this transaction, or the defined conversion rate is not valid on the date

of this transaction.

[APP–25000] This assembly is not under lot or serial number control

Cause:

The assembly you are using is not under lot or serial control. You cannot navigate to a lot or serial

number page.

Action:

You can define the assembly to be under lot or serial number control in Oracle Inventory, if you

want to use lot or serial numbers.

[APP–25001] Assembly status does not allow transactions

Cause:

This assembly is not currently transactable.

Action:

You can change the Item Status in the Define Item form in Oracle Inventory or select another

assembly.

[APP–25002] Date must be less than or equal to most recent period close date (&ENTITY)

Cause:

You entered a cutoff date that does not fall in a closed accounting period.

Action:

Enter a date that falls before or on the most recent period close date. To find the most recent period

close date, you can navigate to the View Period Close Information form in Oracle Inventory.

[APP–25003] Cannot backflush components under lot and serial number control

Cause:

Oracle Work in Process does not support components under both lot and serial number control.

Action:

You can transact components under either lot number control only or serial number control only.

You can also transact components under neither control.

[APP–25004] Job/Schedule is cancelled, no transactions allowed

Cause:

You cannot perform transactions against this job or schedule.

Action:

You cannot change this job or schedule to a transactable status. You can close it if it is a discrete

job. Please select another job or schedule to perform transactions against.

[APP–25005] Unable to create ORDER BY clause

Cause:

An error occurred in the routine that builds the dynamic ORDER BY clause. This error may be due

to a lack of system memory.

Action:

Please use \Help Error to review previous messages for more information.

[APP–25006] Cannot delete this sales order because of quantity completed

Cause:

You cannot delete a sales order against which a net quantity of units has been completed.

Action:

If the completed units have not been shipped to the customer yet, you can return them from

inventory to work in process and then unlink the sales order.

[APP–25007] You cannot change the rate of the current schedule

Cause:

You cannot modify the daily rate of the current schedule.

Action:

You can create another schedule on the same line for the same assembly and cancel the current

schedule.

[APP–25008] You cannot receive this assembly into inventory

Cause:

You cannot receive an assembly into inventory if it is not stockable.

Action:

You can change the item attribute Stockable in the Define Items form in Oracle Inventory to Yes.

[APP–25009] You cannot unrelease the only open schedule on a line

Cause:

You cannot unrelease the only open schedule on a line, since there may be pending charges against

this assembly/line combination.

Action:

You can create a new unreleased schedule and cancel the existing schedule.

[APP–25010] You cannot cancel this job because you have linked sales orders

Cause:

You tried to cancel a job with sales orders linked to it.

Action:

Please navigate to the Sales Orders zone and unlink the sales orders attached to your job by using

Row Delete.

[APP–25011] You cannot update a disabled WIP accounting class

Cause:

You cannot update any information except the disable date when a WIP accounting class is disabled.

Action:

You can update the disable date to a future date, then make any other changes you want.

[APP–25012] Job/Schedule is closed, no transactions allowed

Cause:

You cannot perform transactions against a closed job.

Action:

You cannot change the status of this job to make it transactable. Please select another job or

schedule.

[APP–25013] You cannot close a job in a closed accounting period

Cause:

The period in which you are attempting to perform the job close transaction is closed.

Action:

You can change the transaction date for the close transaction to fall into an open accounting period.

[APP–25014] Close process failed, no transactions allowed

Cause:

You cannot perform transactions against this job or schedule because Oracle Work in Process failed

in closing it.

Action:

You cannot change this job to a transactable status. You should try to close it again. Please enter

another job or schedule to perform transactions against.

[APP–25015] Close process pending, no transactions allowed

Cause:

You cannot perform transactions against this job because Oracle Work in Process is in the process of

closing it.

Action:

Please select another job or schedule.

[APP–25016] You cannot delete a comment code currently in use

Cause:

You cannot delete a comment that is currently in use in a repetitive schedule or open discrete job.

Action:

You can remove the comment from the repetitive schedules and discrete jobs that currently use it. If

the schedules and jobs have statuses that do not allow updates, you can close the jobs and purge the

table wip_entity_comments.

[APP–25017] Job/Schedule is Complete – No Charges, no transactions allowed

Cause: You cannot perform transactions against this job or schedule.

Action: You can change the status of this job to Complete to perform transactions against it, if it

is a discrete job. You cannot change the status of a repetitive schedule with a status of Complete –

No Charges.

[APP–25018] Unable to load units into Queue of the first operation

Cause:

The SQL statement that loads the total job or schedule units into the queue of the first operation

upon release failed. This may be due to a problem with the scheduling process, or with system

memory.

Action:

Use \Help Error to review previous messages for more information. If this does not indicate a

problem, use the View WIP Operations form to examine the operations records for this job or

schedule. Reschedule via the define form if necessary.

[APP–25019] This date is not in the current accounting period

Cause:

The date you entered is not in the current accounting period.

Action:

Enter a date that is in the current accounting period. You can also change your accounting period

information in the Update Accounting Periods form.

[APP–25020] This transaction date is not in an open period

Cause:

The transaction date you entered is not in an open accounting period. You cannot perform

transactions in a closed accounting period.

Action:

Enter a transaction date that does fall in an open accounting period, or use the Open Accounting

Periods form to open the accounting period that contains your desired transaction date.

[APP–25021] You must define parameters for the Bills of Material module

Cause:

You must define parameters in Oracle Bills of Material before you can proceed in Work in Process.

Action:

Please define necessary parameters in the Define Bills of Material Parameters form.

[APP–25022] You must define parameters for the Inventory module

Cause:

You must define parameters in Oracle Inventory module before you can proceed in Work in Process.

Action:

Please define the necessary parameters in the Define Inventory Parameters form.

[APP–25023] You must define parameters for the Work in Process module

Cause:

You must define Work in Process parameters before you can proceed.

Action:

Please define the necessary parameters in the Define Work in Process Parameters form.

[APP–25024] You can only delete records with a status of Error

Cause:

You can only delete records with a status of Error.

Action:

You must wait until the transaction is processed before taking action. If it errors then you can delete

it. If not, then you must create a reversing transaction.

[APP–25025] You cannot delete this operation

Cause:

You can only delete an operation from a discrete job if: 1) there are no assemblies at the operation,

2) no assemblies have been completed at theoperation, 3) there are no pending move transactions in

the open move interface table, 4) no resources at the operation have been charged, and 5) there are

no pending resource transactions for resources at the operation.

Action:

You can move assemblies currently at the operation and any assemblies previously completed to the

previous operation in the routing. This will automatically reverse resource charges for WIP move

resources at the operation. You also need to undo any manual resource charges that might have

taken place. Finally, after pending move and resource transactions have been processed, you can

reverse them. When you delete an operation, Oracle Work in Process automatically deletes all

resources and instructions attached to it.

[APP–25026] You cannot delete this resource

Cause:

You can only delete a resource from a discrete job or repetitive schedule if the resource has not been

charged and there are no pending charges in the open resource interface table.

Action:

You must wait for any existing pending transactions to be processed and then enter reversing

transactions before you can delete the resource.

[APP–25027] Cannot use this count point at an operation with assembly pull components

Cause:

You cannot assign a ”direct charge” count point type to an operation that has assembly pull

components.

Action:

You can assign an ”autocharge” count point type to the operation, or you can change the supply type

of the components.

[APP–25028] Queue intraoperation step must be enabled

Cause:

You cannot delete or disable the queue intraoperation step.

Action:

Please enable the queue intraoperation step.

[APP–25029] Job/Schedule is on hold, no transactions allowed

Cause: You cannot currently perform transactions against this job or schedule.

Action: You can change this job or schedule to a status of Released or Complete to perform

transactions against it.

[APP–25030] This item is not under lot or serial number control

Cause:

You tried to navigate to the lot or serial number entry page.

Action:

You cannot enter lot or serial numbers when you transact an item that is not under lot or serial

number control.

[APP–25031] Item status does not allow transactions

Cause:

This item is not currently transactable.

Action:

You can change the Item Status attribute in the Define Item form in Oracle Inventory, or you can

use a different item for your transaction.

[APP–25032] Job/Schedule does not exist, no transactions allowed

Cause:

This job cannot be found in the discrete jobs table.

Action:

Please select another job.

[APP–25033] Item under lot and serial number control, no transactions allowed

Cause:

You cannot perform transactions against an item that is under both lot and serial number control.

Action:

You can change the controls on the item in Oracle Inventory or you can transact a different item.

[APP–25034] You must define start and stop times for the line

Cause:

You have attempted to define a production line without specifying start and stop times.

Action:

Define start and stop times for the production line in the Define Production Line form.

[APP–25035] You cannot lower the job/schedule quantity

Cause:

You cannot decrease the job/schedule quantity if there are no more assemblies in the Queue step of

the first operation.

Action:

You can cancel the job or schedule if you want to stop production on it and define another job or

schedule with the quantity you want.

[APP–25036] Mass load pending, no transactions allowed

Cause: You cannot perform transactions against a repetitive assembly through a schedule with

a Pending – Mass Loaded status.

Action: You can update this schedule to Released to perform transactions against it.

[APP–25037] Resource sequence already exists and has different resource code

Cause:

You entered a resource sequence that has already been matched to a resource code.

Action:

Please enter another resource sequence if you want to assign the current resource code to it.

[APP–25038] &ENTITY profile is missing

Cause:

You have not set one of your personal Work in Process profile options.

Action:

Please navigate to the Update Personal Profile Option form and assign a value to the appropriate

profile.

[APP–25039] Unable to find an open accounting period

Cause:

Oracle Work in Process was unable to find an open accounting period.

Action:

Please navigate to the Open Accounting Period form in Oracle Inventory to open a new period.

[APP–25040] Non–standard job has no assembly, no transactions allowed

Cause:

You cannot perform transactions against a non–standard job without an assembly.

Action:

Please select another job or schedule to perform transactions against.

[APP–25041] To define a job, you must first define a WIP accounting class

Cause:

There are no discrete or non–standard WIP accounting classes defined for the current organization.

Action:

Please navigate to the Define WIP Accounting Class form and create at least one accounting class.

To define a standard discrete job, you need only define a discrete accounting class. To define a

non–standard job, you can define either an expense non–standard class or an asset non–standard

class.

[APP–25042] Cannot delete this line because schedules have been defined on it

Cause:

You tried to delete a line with schedules defined on it.

Action:

You can delete a line only if you purge all schedules on that line.

[APP–25043] You cannot enter a future transaction date

Cause:

You attempted to enter a future date as a transaction date.

Action:

Please enter a past or current date for your transaction date.

[APP–25044] You cannot navigate to the detail zones for jobs with this status

Cause:

You cannot see details for a job with this status.

Action:

You can change ”Pending” or ”Failed” statuses by resubmitting the failed or pending process. You

can never see details for closed jobs.

[APP–25045] No query allowed on Specific component transaction type

Cause:

You cannot perform a query in the Items zone when the transaction type is Specific component.

Action:

You can select any other transaction type to perform a query in the Items zone.

[APP–25046] Job/Schedule has no routing, no transactions allowed

Cause:

You cannot perform move or resource transactions against a routingless job or schedule.

Action:

Please select another job or schedule to perform transactions against.

[APP–25047] You must enter more daily rate or processing days information

Cause:

You did not enter enough daily rate or processing days information.

Action:

Please enter two of the following: daily rate, processing days and total quantity.

[APP–25048] No valid schedule statuses exist, no transactions allowed

Cause:

You selected a repetitive assembly/line combination that does not have any valid schedules defined

for it.

Action:

You can select another line for your assembly or create one or more released schedules on your

current line.

[APP–25049] You cannot use the view for this component item

Cause:

You tried to navigate to the View Requirements page for a component that is not a requirement of

your job or schedule.

Action:

You can only navigate to the View Requirements page when the current line item is a requirement

for your job or schedule.

[APP–25050] Only one resource per operation can have Scheduled set to Next

Cause:

You cannot have more than one resource per operation scheduled as ’Next’.

Action:

Please select one resource only to be scheduled as ’Next’ before committing your changes.

[APP–25051] Only one resource per operation can have Scheduled set to Prior

Cause:

You cannot have more than one resource per operation scheduled as ’Prior’.

Action:

Please select one resource only to be scheduled as ’Prior’ before committing your changes.

[APP–25052] No valid schedule statuses on this line, choose another line

Cause:

You selected a repetitive assembly/line combination that does not have any valid schedules defined

for it.

Action:

You can select another line for your assembly or create one or more released schedules on your

current line.

[APP–25053] Transaction date precedes release date for the job/schedule

Cause:

You entered a date that precedes the release date for your job or schedule.

Action:

Please enter another date. You can find the release date of your job or schedule in the Define

Discrete Job, View Discrete Job, Define Repetitive Schedules or View Repetitive Schedules by

Assembly forms.

[APP–25054] You must enter both the start date and the completion date

Cause:

You did not enter enough information to define your job without a routing or routing reference.

Action:

You must enter both the start date and completion date when you define a job that has no routing or

routing reference.

[APP–25055] You must enter either the start date or the completion date

Cause:

You did not enter enough scheduling information to define or reschedule your discrete job.

Action:

Please enter either the start date or completion date for your job.

[APP–25056] You must enter either the start time or the completion time

Cause:

You did not enter enough scheduling information to reschedule your discrete job.

Action:

Please enter either the start time or completion time for your discrete job.

[APP–25057] Requirements load failed, no transactions allowed

Cause:

You cannot currently perform transactions against this job or schedule because Oracle Work in

Process was unable to load its requirements.

Action:

Please enter another job or schedule.

[APP–25058] Requirements pending, no transactions allowed

Cause:

You cannot currently perform transactions against this job or schedule because Oracle Work in

Process is in the process of loading its requirements.

Action:

Please select another job or schedule, or try performing transactions against this job or schedule

later.

[APP–25059] Routing load failed, no transactions allowed

Cause:

You cannot currently perform transactions against this job or schedule because Oracle Work in

Process was unable to load its routing.

Action:

Please select another job or schedule.

[APP–25060] Routing pending, no transactions allowed

Cause:

You cannot currently perform transactions against this job or schedule because Oracle Work in

Process is in the process of loading its routing.

Action:

Please select another job or schedule, or try performing transactions against this job or schedule

later.

[APP–25061] You cannot move assemblies within the same operation and step

Cause:

You tried to perform a shop floor move within a single operation and intraoperation step. You can

only move assemblies between distinct operations or between distinct steps of the same operation.

Action:

To perform a move from one operation to a different operation, make sure the From operation

sequence number is different from the To operation sequence number. To perform a move from one

intraoperation step to another intraoperation step in the same operation, make sure the From

intraoperation step is different from the To intraoperation step.

[APP–25062] Repetitive schedule has no routing, no transactions allowed

Cause:

You cannot perform transactions against this repetitive assembly because it doesn’t have a routing.

Action:

Please select another repetitive assembly/line combination.

[APP–25063] This schedule overlaps an existing schedule on the line

Cause:

You cannot have two schedules overlapping each other on the same line for the same repetitive

assembly.

Action:

You can modify the dates and/or times for the overlapping schedules.

[APP–25064] You cannot enter serial numbers for less than a single unit

Cause:

The shop floor move or completion transaction you are trying to perform requires that a partial

number of serially controlled components be backflushed.

Action:

Please modify the transaction quantity so you can enter a whole number of serial numbers for the

components to backflush.

[APP–25065] No quantity left to allocate against this SO/line/delivery

Cause:

The entire job quantity has already been allocated to one or more sales orders.

Action:

You cannot link any additional sales orders to your job.

[APP–25066] Status at this operation step disallows transactions

Cause:

You have assigned a status that prevents assemblies to be moved from this operation step.

Action:

Please navigate to the Update Shop Floor Statuses form and remove the shop floor status at this

operation step using \Row Delete.

[APP–25067] Status at To Move of last operation disallows transactions

Cause:

You assigned a status that prevents assemblies to be moved from the To Move step of the last

operation back into inventory.

Action:

Navigate to the Update Shop Floor Statuses form and remove the shop floor status at this operation

step using \Row Delete.

[APP–25068] You entered too many lot numbers

Cause:

You selected more lot numbers than needed for this transaction.

Action:

Please navigate to the lot number entry page and delete the unnecessary lot numbers.

[APP–25069] You entered too many serial numbers

Cause:

You selected more serial numbers than needed for this transaction.

Action:

Please navigate to the serial number entry page and delete the unnecessary serial numbers.

[APP–25070] Unable to calculate total units

Cause:

You have not entered enough information for Oracle Work in Process to calculate the total quantity.

Action:

Please enter the number of processing days and the daily rate for this schedule.

[APP–25071] To operation sequence number must be positive

Cause:

You entered a negative operation sequence number.

Action:

Please enter a positive integer for your operation sequence number.

[APP–25072] Please unlink the sales order to change the assembly

Cause:

When you linked the sales order to your job, Oracle Work in Process assigned the assembly

associated with it to your job. You cannot change the assembly until the sales order has been

unlinked.

Action:

Please use \Row Delete to unlink the sales order.

[APP–25073] Please unlink the sales order to change the demand class

Cause:

When you linked the sales order to your job, Oracle Work in Process assigned the demand class

associated with it to your job. You cannot change the demand class until the sales order has been

unlinked.

Action:

Please use \Row Delete to unlink the sales order.

[APP–25074] The job quantity must not be lower than the total quantity you have allocated to sales

orders.

[APP–25075] Job/Schedule is Unreleased, no transactions allowed

Cause: You cannot currently perform transactions against this job or schedule.

Action: You can change this job or schedule to a status of Released to perform transactions

against it.

[APP–25076] You cannot unrelease this job/schedule

Cause: You cannot unrelease a job or schedule that carries a net balance, or that has pending

transactions.

Action: You can reverse any transactions that resulted in charges against the job or schedule,

and you can resolve pending transactions. You can also cancel the existing job or schedule and

create a new job or schedule with a status of Unreleased.

[APP–25077] Please use disable date to delete this record

Cause:

You tried to delete a record manually.

Action:

Please enter a disable date equal to or greater than today’s date to delete this record.

[APP–25078] Only valid employees may transact moves into operations requiring outside resources

Cause:

You tried to transact moves into operations requiring outside resources but you are not a valid

employee yourself.

Action:

Please use the Enter Employee form to define yourself as an employee for this organization. You

must also associate your user name with your employee name in the Define Applications User form

under the System Administrator’s responsibility.

[APP–25079] Enter a valid locator before proceeding to lot number page

Cause:

You tried to navigate to the lot number entry page without entering a locator.

Action:

Please use Quickpick to select a locator before proceeding to the lot number entry page.

[APP–25080] Enter a valid locator before proceeding to serial number page

Cause:

You tried to navigate to the serial number entry page without entering a locator.

Action:

Please use Quickpick to select a locator before proceeding to the serial number entry page.

[APP–25081] Enter a valid subinventory before proceeding to lot number page

Cause:

You tried to navigate to the lot number entry page without entering a subinventory.

Action:

Please use Quickpick to select a subinventory before proceeding to the lot number entry page.

[APP–25082] Enter valid subinventory before proceeding to serial number page

Cause:

You tried to navigate to the serial number entry page without entering a subinventory.

Action:

Please use Quickpick to select a subinventory before proceeding to the serial number entry page.

[APP–25083] You must define a calendar for your organization

Cause:

You have not specified a value for the Calendar field in the Define Inventory Parameters form. A

value is required to perform scheduling in Work in Process.

Action:

Please navigate to the Define Inventory Parameters form and assign a value to the Calendar field.

[APP–25084] Operation dates fall outside defined calendar days

Cause:

Oracle Work in Process is unable to schedule your job or schedule because operation dates fall

outside defined calendar dates.

Action:

You can define additional calendar dates in Oracle Bills of Material or decrease your job or schedule

quantity.

[APP–25085] Bill revision does not exist as an item revision

Cause:

The revision of the common bill you are attempting to complete is not valid as a revision for the

assembly item itself. See ”Completing Assemblies from WIP into Inventory” in the WIP Material

Control Essay for more information.

Action:

You should update the revisions of the common bill to match those of the assembly itself in the

Define Item Revisions Form in Oracle Inventory.

[APP–25086] This assembly is invalid, please re–enter

Cause:

This assembly is invalid because 1) it does not exist in the item master, or 2) it is not buildable in

Work in Process, or 3) it is an engineering item and the WIP:See Engineering Items profile is set to

No.

Action:

You can 1) define this item in Oracle Inventory, or 2) set the buildable flag for this item in Oracle

Inventory to Yes and/or set the pick components flag for this item in Oracle Inventory to No, or 3)

set the WIP:See Engineering Items personal profile to Yes in the Update Personal Profile Options

form.

[APP–25087] This component is invalid, please re–enter

Cause:

This component is invalid because 1) it does not exist in the item master, or 2) it cannot be used on

a bill of materials, or 3) it is an engineering item and your WIP:See Engineering Items profile is set

to No.

Action:

You can 1) define this item in Oracle Inventory, or 2) change the Bom Allowed attribute in Oracle

Inventory to Yes, or 3) set the WIP:See Engineering Items personal profile to Yes in the Update

Personal Profile Options form.

[APP–25088] This component is not on the bill, please re–enter

Cause:

You cannot transact a component that is not on the bill when you perform a transaction other than

”Specific component”.

Action:

Please enter a component that exists on the bill for this job or schedule or choose the ”Specific

component” transaction type.

[APP–25089] Error in zooming to the Lot Number Entry page

Cause:

A process error occurred while zooming to the Lot Number Entry page.

Action:

Please contact your support representative.

[APP–25090] Error in zooming to the Serial Number Entry page

Cause:

A process error occurred while zooming to the Serial Number Entry page.

Action:

Please contact your support representative.

[APP–25091] Cannot assign shop floor status to a routingless job or schedule

Cause:

There are no operations to assign shop floor statuses to.

Action:

Please select a job or schedule with a routing.

[APP–25092] Invalid Reservation Type for transfer to new delivery

Cause:

Reservation Type (&RSV_TYPE) must be 2 or 3 for quantity transfers.

Action:

Please contact your Oracle Support representative.

[APP–25093] Invalid quantity (&MOVE_QTY) to transfer to new delivery

Cause:

The transfer quantity (&MOVE_QTY) is negative. OR The transfer quantity (&MOVE_QTY) is

greater than the allowed quantity (&ALLOWED_QTY) for the allocation record with

ALLOCATION_ID = &ALLOC_ID.

Action:

Please contact your Oracle Support representative.

[APP–25094] Bill loop detected

Cause:

There is a phantom in the assembly you just attempted to explode that either directly or indirectly

contains itself.

Action:

Please run a Verify Bill of Material process or report to determine where the loop is occurring. Use

the Define Bill of Material form to correct the problem.

[APP–25095] This item name is already in use as a discrete job name

Cause:

This item name already exists as a discrete job name.

Action:

Please navigate to the Define Discrete Job form and modify the name of the job with the same name

as your item.

[APP–25096] You cannot define new schedules for a disabled line

Cause:

You tried to define a new schedule on a line that is currently disabled.

Action:

You can update any existing schedules on the line in the Define Repetitive Schedules form. You can

also update the disable date of the line in the Define Production Line form.

[APP–25097] You cannot define new schedules for an item with these attributes

Cause:

You tried to define a schedule for an item with inappropriate inventory item attributes.

Action:

You can update the item attributes in the Define Item form. The Work In Process attribute ”Build in

WIP” should be set to Yes, and the Order Entry attribute ”Pick Components” should be set to No, if

you want to define new schedules for this item. You can also update any existing schedules for the

item.

[APP–25098] Warning: You have pull components that may remain unissued

Cause:

You are: 1) either scrapping assemblies at an operation with the backflush flag set to No and with

operation pull components, or 2) scrapping assemblies at an operation with assembly pull

components. At this point, Oracle Work in Process has not issued these components to your job or

schedule. However, you may have physically issued these components. In addition, Oracle Work in

Process cannot backflush all the component requirements because you have reduced the number of

assemblies in the job or schedule. Also, when you scrapped the assemblies, Oracle Work in Process

removed the standard cost of these assemblies through the operation, including the cost of the

components you have not yet issued.

Action:

Navigate to the WIP Material Transaction form and manually issue these components to your job or

schedule. This will update the job or schedule to correctly reflect the actual component quantities

and costs.

[APP–25099] Cannot define WIP parameters

Cause:

Your costing organization is different from your current organization.

Action:

To define WIP parameters, you must change the control level for the Costing Enabled and Inventory

Asset Value item attributes from Item level to Item/Org level in the Define Item Attribute Controls

form in Oracle Inventory. This change will require that costs be defined for all organizations that

point to other organizations for their costs. Please refer to the Cost Management topical essays in

the Oracle Inventory or Oracle Cost Management reference manuals.

[APP–25100] Transaction subinventory (&TXN_SUB) must match demand subinventory

(&SO_SUB)

Cause:

Under the WIP automated allocation algorithm, a transaction line was picked to fulfill a sales order

with a demand subinventory different from the transaction subinventory.

Action:

Please change the transaction subinventory to match the sales order demand subinventory or

override the allocation algorithm by explicitly entering a sales order for each transaction line.

[APP–25101] Transaction spans across multiple schedules with different bill revisions

Cause:

You are performing a completion or return from inventory transaction that overlaps several

schedules with different bill revisions.

Action:

You must perform a transaction for each bill revision. For example, if your transaction spans across

two schedules with bill revisions A and B, you must split the transaction into two transactions: one

for bill revision A and the other for bill revision B.

[APP–25102] This date is not defined in your organization’s workday calendar

Cause:

The date you have entered is not a valid date from your organization’s workday calendar.

Action:

You can either enter a valid date from your organization’s calendar or you may need to define the

workday calendar in the Define Workday Calendar form in Oracle Bills of Material.

[APP–25103] Non–standard job has no assembly, no move and completion transactions allowed

Cause:

You can perform neither move nor completion transactions against a non–standard job without an

assembly.

Action:

Please select another job to perform move or completion transactions against.

[APP–25104] An active schedule exists on the line with a different routing

Cause:

You tried to release a repetitive schedule whose routing is different than other released schedules on

the line

Action:

You can change the routing revision of the current schedule to match that of the other active

schedules on the line. Or you can update the operations of the schedule in the Update WIP

Operations form to also match the routing of the other active schedules on the line. You must

ensure that the operation sequences, departments, count point types, and backflush flags of all

operations for the current schedule are identical to that of the other active schedules on the line for

the assembly.

[APP–25105] Failed backflush transactions exist for TRANSACTION_HEADER_ID &TXN_ID

[APP–25106] You must define a deliver–to location for the PO Move resource

Cause:

You tried to move into an operation with a PO Move resource. The department of the next

operation or, if this is the last operation, this operation, has no location.

Action:

Assign a location to the department of the next operation or, if this is the last operation, this

operation, in the Define Departments form. This will be used as the deliver–to location on the

purchase order.

[APP–25107] A Hold was found on an ATO Line in order &ORDER_NUMBER and order type

&ORDER_TYPE

[APP–25108] You cannot complete assemblies if a sales order is linked to the job and you are

performing transactions online with the profile TP:Server Side Online Processing set to No.

[APP–25109] You cannot assign a shop floor status to a job with this status.

[APP–25110] You cannot assign a shop floor status to a disabled intraoperation step.

[APP–25111] You cannot assign a disabled shop floor status to an intraoperation step.

[APP–25112] You cannot change the status of this job to On Hold.

[APP–25113] The department is not assigned to the operation sequence number

[APP–25114] Backflush transaction(s) failed

[APP–25115] Operation does not exist in the routing

[APP–25116] You cannot delete this schedule group. There are discrete jobs that are using this

schedule group.

[APP–25117] Please enter a valid class or select a valid default class in the WIP Parameters

window.

[APP–25118] The sales order request failed. This block will be refreshed.

[APP–25119] This may be a long–running query. Continue?

[APP–25120] You cannot delete this resource or operation . This resource or a resource attached to

this operation is linked to a purchase order or a purchase requisition.

[APP–25121] Value for column &COLUMN is being ignored.

[APP–25122] Value for column &COLUMN is invalid.

[APP–25123] Invalid value for Load Type.

[APP–25124] Invalid value for Last Updated By. Check that you have chosen a valid user name.

[APP–25125] Invalid value for Created By. Check that you have chosen a valid user name.

[APP–25126] Invalid value for start quantity. Possible causes: 1. You must enter a value for start

quantity to create new jobs. 2. The start quantity must be greater than 0 for standard jobs. 3. The

start quantity must be greater than or equal to 0 for nonstandard jobs.

[APP–25127] Invalid value for Start Quantity. Possible causes: 1. You cannot lower the job quantity

below the quantity that has already been completed. 2. You cannot lower the quantity below the

quantity that has been allocated to sales orders.

[APP–25128] Invalid value for Net Quantity. Possible causes: 1. The net quantity must be greater

than or equal to 0. 2. The net quantity must be less than or equal to the start quantity. 3. The net

quantity must be 0 for nonstandard jobs without assemblies.

[APP–25129] Invalid value for Firm Planned. Possible causes: 1. The value you entered is not valid.

2. You have tried to firm plan a nonstandard job.

[APP–25130] Invalid value for Organization. Possible causes: 1. You must select a valid and

enabled organization. 2. The organization must have WIP and Inventory Parameters defined for it.

[APP–25131] Invalid or missing WIP Accounting Class. Possible causes: 1. You must specify a

class or define a default discrete class. 2. The class must exist and be enabled in this organization.

3. The class must have the correct class type for this job.

[APP–25132] Invalid value for Schedule Group. Make sure that the schedule group exists and is

enabled in this organization.

[APP–25133] Invalid value for Line. Make sure that the line exists and is enabled in this

organization.

[APP–25144] Build Sequence is invalid Possible causes: 1. You cannot enter a Build Sequence

without choosing a Schedule Group. 2. This Build Sequence is already being used in this Schedule

Group. 3. The Build Sequence must be greater than zero

[APP–25145] Invalid value for Supply Type. Possible causes: 1. You cannot use Operation Pull if

the job has no routing. 2. You cannot use Operation or Assembly Pull for nonstandard jobs without

assemblies.

[APP–25146] Demand Class is invalid. Make sure that the demand class exists and is enabled.

[APP–25147] You have entered a value for WIP_ENTITY_ID that is already being used.

[APP–25148] You cannot update this job. Possible causes: 1. You have chosen a job that does not

exist in this organization. 2. You cannot update jobs of this status.

[APP–25149] You can only have one record with this Group ID that updates this job.

[APP–25150] Alternate Routing is invalid. Choose a routing that exists for this assembly or routing

reference.

[APP–25151] Alternate Bill is invalid. Choose a bill that exists for this assembly or bill reference.

[APP–25152] Invalid Assembly. Possible causes: 1. The item does not exist in this organization. 2.

The item has attributes that are not allowed for an assembly.

[APP–25153] You cannot define schedules for this assembly/line. You must first create a repetitive

assembly/line association.

[APP–25154] Invalid routing reference. Possible causes: 1. The item does not exist in this

organization. 2. The item has attributes that do not allow it to be used as an assembly.

[APP–25155] Invalid Bill Reference Possible causes: 1. The item does not exist in this

organization. 2. The item has attributes that do not allow it to be used as an assembly.

[APP–25156] Invalid value for Project. Possible Causes: 1. No such project currently exists. 2.

Project References are not enabled in your organization.

[APP–25157] Invalid value for Task. Possible causes: 1. The Task you have entered does not belong

to this Project. 2. You have entered a Task without a Project. 3. If your Project Control Level is

task level, you must enter a Task for this Project.

[APP–25158] One or more of your scheduling dates is missing or invalid. Possible causes: 1. You

must select dates that are defined in your manufacturing calendar. 2. You must enter at least one

schedule date when creating jobs or schedules. 3. You must enter both dates for nonstandard jobs

without a routing reference.

[APP–25159] You must enter a value for Processing Days that is greater than 0.

[APP–25160] You entered a value for REPETITIVE_SCHEDULE_ID that is already in use.

[APP–25161] Daily Quantity must be greater than 0.

[APP–25162] Invalid value for Scheduling Method. Possible causes: 1. You must enter start and

completion dates to use manual scheduling. 2. The start date must be earlier than the completion

date when using manual scheduling. 3. You cannot use lead time scheduling for nonstandard jobs

without routing references.

[APP–25163] Completion subinventory is invalid. Possible causes: 1. Choose a subinventory that

exists in this organization. 2. Make sure the assembly can be transacted into this subinventory.

[APP–25164] Completion Locator cannot be specified without a Completion Subinventory.

[APP–25165] Duplicate value for Job Name. Possible causes: 1. A job with this name already exists

in this organization. 2. Job names must be unique. You cannot import jobs with the same name into

the same organization.

[APP–25166] Invalid Status. You can only define jobs as Unreleased, Released, or On Hold. You

can only update jobs to Unreleased, Released, Complete, On Hold, or Cancelled.

[APP–25167] One or more of your scheduling dates is invalid. You should enter only one

scheduling date if the assembly has a routing or if the line has a fixed lead time. You should enter a

start date and a completion date if your line is routing–based and your assembly has no routing.

[APP–25168] Invalid Bill Revision information. Possible Causes: 1. You have chosen an invalid

revision. 2. No valid revision exists on the revision date you have chosen.

[APP–25169] Invalid Routing Revision information. Possible Causes: 1. You have chosen an

invalid revision. 2. No valid revision exists on the revision date you have chosen.

[APP–25170] &Concurrent Request

[APP–25171] This Schedule Group, Build Sequence combination is already being used by another

job.

[APP–25172] Invalid or insufficient Locator information. Check that you have entered valid locator

information based on the organization, subinventory, and assembly that you have chosen.

[APP–25173] &ENTITY1 of &ENTITY2 records failed. You cannot resubmit a record to be mass

loaded unless the last attempt to process the record failed.

[APP–25175] Pending transactions for this job will not be affected. Only future transactions will be

affected by this change.

[APP–25176] Submit Request to purge data?

[APP–25177] Cannot Purge Headers. Foreign Key to table &TABLE exists.

[APP–25178] At least one of the include options must be selected.

[APP–25179] Rows: &NUMBER

[APP–25180] There is no information in the current record. You cannot proceed with the purge

activity.

[APP–25181] Not all transactions deleted: Some transactions scan multiple schedules, one of which

is not eligible for purge.

[APP–25182] WIP period balances for this Job/Schedule is non zero.

[APP–25183] Oracle Work in Process is unable to schedule your job or schedule because calculated

scheduling dates fall outside defined calendar dates. You can define additional calendar dates in

Oracle Bills of Material.

[APP–25184] You may not insert or delete operations because there are other active schedules on

this line with the same routing. You also may not update the Operation Code, Count Point,

Autocharge, or Backflush fields.

[APP–25185] The default WIP Accounting Class &class_code that you have chosen is disabled.

You should choose a different default WIP Accounting Class in the WIP Parameters form.

[APP–25186] You cannot perform this action on a new or changed record.

[APP–25187] Assembly pull is not a valid supply type because the operation is not autocharge.

[APP–25188] You can only update the status of this job.

[APP–25189] &ENTITY1 of &ENTITY2 records failed. Work in Process does not allow the status

changes you tried for those records.

[APP–25190] &ENTITY1 of &ENTITY2 records failed. You are not allowed to close jobs with

these statuses.

[APP–25191] &ENTITY1 of &ENTITY2 records failed. You cannot change the status of these jobs.

Either a concurrent program exists to close these jobs or the jobs did not have status Pending Close.

[APP–25192] &ENTITY1 of &ENTITY2 records failed. You are not allowed to unclose these jobs.

You can only unclose jobs that were closed in accounting periods that are still open. You cannot

unclose jobs that are linked to sales orders.

[APP–25193] You cannot create this job until you have completed departure planning.

[APP–25194] You must define a deliver–to location for the PO Move resource at the first operation

Cause:

You tried to release a job with a PO Move resource at the first operation. The department of the

next operation or, if this is the last operation, this operation, has no location.

Action:

Assign a location to the department of the next operation or, if this is the last operation, this

operation, in the Define Departments form. This will be used as the deliver–to location on the

purchase order.

[APP–25195] Only valid employees can release a job if the first operation requires outside resources

Cause:

You tried to release a job whose first operation requires outside resources but you are not a valid

employee yourself.

Action:

Please use the Employees form to define yourself as an employee for this organization. You must

also associate your user name with your employee name in the Define Applications User form under

the System Administrator’s responsibility.

[APP–25196] You cannot reschedule this job. Possible causes: 1. The job that is identified in this

interface record does not exist. 2. You can only reschedule jobs that have status Unreleased,

Released, Complete, or On Hold.

[APP–25197] Invalid Scheduling Level. The Scheduling Level must be set to Operation or

Resource.

[APP–25198] The start date must be less than the completion date.

[APP–25199] The operations in the interface table do not match the operations for the job you are

rescheduling.

[APP–25200] The resources in the interface table do not match the resources for the job you are

rescheduling.

[APP–25201] The Usage Rate or Amount must be greater than or equal to zero.

[APP–25202] This record cannot be processed because other records for this job have failed

validation.

[APP–25203] Cannot convert date format.

[APP–25204] You can only enter one completion transaction at a time for this average costing

organization.

[APP–25205] You cannot define repetitive items or schedules because the current organization is an

average costing organization.

[APP–25206] A No Move shop floor status exists between the From Operation and Intraoperation

Step and the To Operation and Intraoperation Step.

[APP–25207] You must define at least one WIP Accounting Class before using this module

[APP–25208] The estimated scheduling date does not exist in your manufacturing calendar.

[APP–25209] Invalid Interface Record. Be sure that you are inserting records with the correct values

for PROCESS_PHASE and PROCESS_STATUS.

[APP–25210] Total quantity must be greater than or equal to the quantity in queue of the first

operation.

[APP–25211] You have entered an invalid project or task for this transaction.

[APP–25212] Invalid Substitution Type – The Substitution Type entered at Operation Sequence

&ENTITY1 is invalid, please re–enter a valid Substitution Type – 1) Change, or 2) Delete or 3)

Add or 4) Lot/Serial.

[APP–25213] Invalid Completion Assembly – The Completion Assembly is invalid because either

1) it does not exist in the item master, or 2) it is not buildable in Work in Process, or 3) it is an

engineering item and the WIP:See Engineering Items profile is set to No.

[APP–25214] Invalid Substitution/Change at Operation Sequence &ENTITY1.

[APP–25215] Invalid Substitution/Delete at Operation Sequence &ENTITY2.

[APP–25216] Error occured in the Substitution Merge program, while Substituting components at

Operation Sequence &ENTITY1.

[APP–25217] Error occured while inserting costing information into the

WIP_COST_TXN_INTEFACE table.

[APP–25218] Error occured while performing the inventory validation for the material issues

associated with the Work Order–less Completion Transaction – &ENTITY1.

[APP–25219] Error occured while creating the Work Order–less Completion Entity &ENTITY1.

[APP–25220] The Work Order–less Completion Transaction failed as the Project/Task related

Locator couldnot be created dynamically.

[APP–25221] Error occured while generating the revisions for the material Issues associated with

the Work Order–less Completion Transaction whose transaction Interface ID is :&ENTITY1.

[APP–25222] Error occured while backflushing the components for the Work Order–less

Completions Transactions whose Transaction Interface ID is : &ENTITY1

[APP–25223] The transaction processor errored out while moving information from

MATERIAL_TRANSACTIONS_INTERFACE table to

MTL_MATERIAL_TRANSACTIONS_TEMP table for Work Order–less Completions.

[APP–25224] Cannot generate Auto–Fifo Lot numbers.

[APP–25225] An ATP rule cannot be found for some selected components.

[APP–25226] You have selected some components which are not Check ATP enabled.

[APP–25227] You need to save your changes before doing an ATP check.

[APP–25229] Invalid Substitution Item – The Substitution Item is invalid because either 1) it does

not exist in the item master, or 2) it is not buildable in Work in Process, or 3) it is an engineering

item and the WIP:See Engineering Items profile is set to No.

[APP–25230] Error occured while deleting the Work Order–less Completion Entity &ENTITY1.

[APP–25231] Invalid Flow Schedule Flag ’N’ for the Substitute Item at Operation Sequence

&ENTITY1

[APP–25232] Work Order–less Completions main program – wilctv errored out.

[APP–25233] Pre–Inventory Validation routine for the Material Issues associated with the Work

Order–less Completion transaction errored out.

[APP–25234] Post–Inventory Validation routine for the Material Issues associated with the Work

Order–less Completion transaction errored out.

[APP–25235] Clean up routine for the Work Order–less Completions errored out.

[APP–25236] Invalid Lot Serial Substitution at Operation Sequence &ENTITY1.

[APP–25237] Error occured while performing the post substitution merge operations.

[APP–25238] WIP Accounting Class &class_code defined in Project parameters is disabled.

[APP–25239] Flow Schedules

[APP–25240] You have selected an assembly whose only routing is a flow routing. Oracle Work in

Process does not currently support such routings. Please select a different assembly.

[APP–25241] The routing you have chosen for your assembly is a flow routing. Oracle Work in

Process does not currently support such routings. Please select a different routing.

[APP–25242] Please use clear block to clear the form.

[APP–25243] Changing this field will cause all dependent fields to be cleared. Are you sure?

[APP–25244] Could not default all fields for the assembly.

[APP–25245] Work in Process does not support Resource and Overhead transactions entered

manually for flow schedules – i.e., with PROCESS_PHASE = 1 in the

WIP_COST_TXN_INTERFACE table.

[APP–25246] Error occured while validating the Work Order–less Completion Entity &ENTITY1.

[APP–25247] Error occured while defaulting for the Work Order–less Completion Entity

&ENTITY1.

[APP–25248] The assembly chosen is under revision control but has no bill.

Cause: You cannot complete or return assemblies from the Move Transactions form for this

type of item.

Action: Use the Assembly Completions form instead.

[APP–25249] Changing the project and/or task information will cause all substitution information to

be deleted. Are you sure?

[APP–25250] The project and task references specified do not match the project/task references for

the locator.

[APP–25251] The backflush component &ENTITY1 for this Work Order–less Completion is under

Serial Control and its serial number is not provided. Work In Process cannot generate serial numbers

automatically.

[APP–25252] The backflush component &ENTITY1 for this Work Order–less Completion is under

Lot Control and its Lot number is not provided. Work In Process cannot generate Lot numbers

automatically as the Lot Selection Method is set to Manual Entry.

[APP–25253] The backflush component &ENTITY1 is under Lot Control. The Work Order–less

Completion/Return has this component in the bill with a negative/positive Quantity Per. Work in

Process cannot automatically generate a New Lot for this component.

[APP–25254] Material allocations exist for this schedule.

[APP–25255] &Transaction Summary

[APP–25256] The Substitute Component &ENTITY1 s, Transaction UOM &ENTITY2 is different

from its Primary UOM &ENTITY3. For Lot Serial Substitution the Transaction UOM should be the

same as Primary UOM.

[APP–25257] The WIP accounting class &class_code that you have chosen does not have an

enabled association with a Cost Group. This association is required in the case of an average costing

organization with project reference enabled.

[APP–25258] No default accounting class exists for specified assembly and/or project reference.

[APP–25259] Invalid Completion Locator for Project and Task.

[APP–25260] Schedule number

[APP–25261] WIP Accounting Class &class_code defined for Product line accounting is disabled.

[APP–25262] No resource/material requirement substitutions can be done for this job , because

status_type are not valid. The valid status_types are: 1) Unreleased, 3) Released, 4) Completed, 6)

Hold

[APP–25263] No resource/material requirement substitutions can be done for this job , because this

job is firmed and can not be changed

[APP–25264] Invalid Load OR Substitution Type – Substitution Type must be: 1) WIP_DELETE, or

2) WIP_ADD or 3) WIP_CHANGE; Load_Type must be : 1) WIP_RESOURCE or 2)

WIP_MTL_REQUIREMENT

[APP–25265] Invalid Last_Updated_By OR Created_By – They must be a valid user.

[APP–25266] This record failed because there are other failed records in this job.If any record in a

job fails, all records in this job will fail.

[APP–25267] When deleting resources, resource_seq_num AND resource_id_old in

WIP_JOB_DTLS_INTERFACE table can NOT be NULL.

[APP–25268] Resource can NOT be deleted or changed, because there is NOT such a combination

of wip_entity_id/organization_id/operation_seq_num/resource_seq_num/resource_id.

[APP–25269] Resource can NOT be deleted or changed, because

WIP_OPERATION_RESOURCES.applied_resource_units is not 0, which means this resource have

been applied.

[APP–25270] Resource can NOT be deleted or changed, because there are pending transactions

assoviated with this resource.

[APP–25271] When adding resources, you must specify resource_seq_num, resource_id_new, AND

usage_rate_or_amount.

[APP–25272] Resource can NOT be added or changed, because resource_id_new is invalid or

disabled.

[APP–25273] Resource can NOT be added, because resource_seq_num already exists, OR the

to–be–added resource_seq_num <= 0

[APP–25274] Resource can NOT be added or changed, because usage_rate_or_amount must be

>= 0.

[APP–25275] Resource can NOT be added or changed, because autocharge_type can NOT be

NULL

[APP–25276] When change resources, resource_id_old, resource_id_new, resource_seq_num and

usage_rate_or_amount can not be null

[APP–25277] When deleting material requirments, inventory_item_id must be specified.

[APP–25278] Materail requirements can NOT be deleted or changed, because it does not exist.

[APP–25279] Materail requirements can NOT be deleted or changed, because there are quantities

already issued

[APP–25280] Materail requirements can NOT be deleted or changed, because there are pending

transactions with this materail requirement

[APP–25281] When adding materail requirements, inventory_item_id AND quantity_per_assembly

MUST be specified

[APP–25282] Materail requirements can NOT be added or changed, because the same material

already exists in the specified job/operation

[APP–25283] Materail requirements can NOT be added or changed, because the new material is not

valid

[APP–25284] Materail requirements can NOT be added or changed, because defaulted

wip_supply_type is NULL

[APP–25285] When change material requirements, inventory_item_id_old, inventory_id_new and

quantity_per_assembly can not be null

[APP–26001] Pick Release Online failed. Release order in concurrent mode.

[APP–26002] No lines released. No exceptions reported. Release order concurrently.

[APP–26003] Pick Slips from different organizations cannot be processed online

[APP–26004] Error occurred while retrieving list of document set usages

[APP–26005] Currency formatting failed for this line

[APP–26006] A document set must contain at least one document

[APP–26007] Amount must be in format &FMT_MASK

[APP–26009] Currency formatting cannot be performed without a currency code

[APP–26010] You must commit your deletion before launching a new Pick Release.

[APP–26012] Launching Pick Release failed. Your request was deleted.

[APP–26013] Error occurred while submitting concurrent request to create exception reports.

[APP–26014] The Details window could not be released from semi–modality. Please contact your

Oracle representative.

[APP–26015] Shipping Transaction Manager is down. Please start it before proceeding.

[APP–26016] Cannot launch Pick Release Online without specifying an order number.

[APP–26017] Clearing will remove all serial number information for these line details.

[APP–26018] Please finish your work in the Details window and close it before saving here.

[APP–26020] You cannot ship &DETAILS_SHP_QTY for a line with a requested quantity of

&LINE_REQ_QTY. Please reduce the quantity shipped on the details.

[APP–26021] Quantity information for line &LINE does not match its details. Please check the

details entered.

[APP–26022] Please finish your work in the Serial Number window and close it before saving here.

[APP–26023] There are no open periods for this shipment to ship against.

[APP–26028] Quantity validation failed for a line detail(s). Please check Error Explanation to see

which line details are inconsistent with the picking lines.

[APP–26029] The quantities on the picking lines and details do not match for picking lines

&PICK_LINES of pick slip &PICK_SLIP. Please requery these lines and check the quantities.

[APP–26030] You are confirming a shipment in a past period.

[APP–26033] The Transaction Manager failed to execute &PROGRAM online. Please contact your

Oracle representative.

[APP–26034] Total shipped quantity (&DETAILS_SHP_QTY) on the line details does not match

the shipped quantity on the picking line (&LINE_SHP_QTY).

[APP–26035] There are duplicate serial numbers on the line details for picking lines &PICK_LINES

of pick slip &PICK_SLIP. Please choose unique serial numbers for these line details.

[APP–26036] Process online for shipping failed in the ’Inventory Interface’ process. The process

online request has failed in the ’Inventory Interface’ process. Run the Inventory Interface concurrent

program. Monitor the log files for errors.

[APP–26037] Process online for shipping failed in the ’Update Shipping’ process. The process

online request has failed in the ’Update Shipping’ process. Run the Update Shipping Information

concurrent program and wait for it to complete successfully. Then run the Inventory Interface

concurrent program. Monitor the log files for errors.

[APP–26038] The effective date can not be less than the current date.

[APP–26039] Please finish your work in the Details window and close it before proceeding.

[APP–26040] Total shipped quantity (&DETAIL_SHP_QTY) for the line detail does not match the

total requested quantity (&DETAIL_REQ_QTY) for the line detail.

[APP–26047] Expected Arrival Date cannot be before Shipped Date

[APP–26048] Transaction Out of Sequence. Pick slip is being closed by a transaction before this

one. Please correct the sequence of these transactions.

[APP–26049] This Serial Number is used by another transaction in the interface. Update the

transaction to make it unique.

[APP–26050] Cannot use this Serial Number because it is already used in the database

[APP–26051] Check Freight Charges for errors

[APP–26052] Invalid currency: currency must be the same as the delivery currency

[APP–26053] Invalid Item (either Id or segments)

[APP–26054] Invalid Inventory location ID (or segments) or not a valid Location from restricted list

for this warehouse/subinventory/item.

[APP–26055] Invalid lot for this item/warehouse/subinventory

[APP–26056] Packer ID or name not a recognized application user ID or name

[APP–26057] Invalid Pick Slip Number

[APP–26058] Invalid picking line detail id &ID

[APP–26059] Picker ID or name not a recognized application user ID or name

[APP–26060] Shipped Quantity must be a positive whole number

[APP–26061] Invalid revision for this item/warehouse

[APP–26062] Invalid subinventory for this item/warehouse

[APP–26063] Invalid Unit of Measure

[APP–26064] Weight must be a positive whole number

[APP–26065] Check Picking Line Details for errors

[APP–26066] Location Id is not valid for Items not under Location Control

[APP–26067] Lot Number is not valid for Items not under Lot Control

[APP–26068] Cannot Close–Ship because of missing inventory controls.

[APP–26069] Detail Records found without corresponding header record. Empty header record

added by Interface program. Please reassign this detail record or delete the transaction.

[APP–26070] Inventory Location is required

[APP–26071] Cannot find Locator Control Information for this Warehouse/Sub/Item combination

[APP–26072] Requires Lot number when under lot control

[APP–26073] Requires Revision when item under revision quantity control

[APP–26074] Requires Serial Number when item is under Serial Number Control

[APP–26075] Ship date must be supplied.

[APP–26076] Sub required and No Default Sub available

[APP–26077] Waybill must be supplied before closing the pick slip.

[APP–26078] Item and Warehouse must be the same as the Order Item and Warehouse

[APP–26079] Not allowed to Ship Confirm Orders from another Warehouse

[APP–26080] Overshipments are not allowed (Item = &ITEM).

[APP–26081] Not allowed to change inventory controls on a reservation

[APP–26082] Revision is not valid for Items not under Revision Control

[APP–26083] Error in Ship Confirm Close Module

[APP–26084] Serial Number not valid when Item not under Serial Number Control

[APP–26085] Transaction &TRANSACTION_ID : &ERROR_MSG

[APP–26086] Total shipped quantity (&SERIAL_QTY) in the Serial Number Entry form does not

match the shipped quantity (&DETAIL_QTY) for the picking line detail.

[APP–26087] Cannot specify partial shipped quantities for the picking line because there are

multiple picking line details. Please enter shipped quantities in Sales Order Issue window.

[APP–26088] This Find may take a long time. Specifying the Pick Slip Number, Batch Name, or

Order Number if you know it would make it much faster. Continue with this Find anyway?

[APP–26089] Process online for shipping failed in the Inventory Interface process. Please run the

Inventory Interface concurrent program and monitor the log files for errors.

[APP–26090] Process online for shipping failed in the Update Shipping Information process. Set

Process Online to No, then close the batch or pick slip you are processing. Run the Update Shipping

Information concurrent program and wait for it to complete successfully. Then run the Inventory

Interface concurrent program. Monitor the log files for errors.

[APP–26091] This module/function is not for Pick Slip Based shipping (Delivery based only).

[APP–26092] This module/function is not for Delivery Based shipping (Pick Slip based only).

[APP–26093] The Expected Arrival Date must be after the Ship Date.

[APP–26094] Split and Close did not create a new Pick Slip because all the picking lines were

shipped complete in the previous Pick Slip.

[APP–26095] Shipping Method Profile must be set before continuing.

[APP–26096] Invalid Carrier Code for this organization.

[APP–26097] Rerouting is not allowed for this line. This line has either been reserved or the shipped

quantity is greater than 0.

[APP–26098] The weight and volume UOMs must be specified.

[APP–26099] At least one parameter is incomplete (NULL).

[APP–26100] At least one parameter has an invalid value.

[APP–26101] The master containers are undefined. Please make sure that you have defined the

master containers and their maximum load quantities.

[APP–26102] The parameter source passed to WSH_WV_PVT.del_weight should be ’DPW’ or

’SC’.

[APP–26106] The load of these containers exceeds the maximum load! &Container_Seq_List

[APP–26107] It is possible that some items have been overpacked. Please validate the packed

quantity.

[APP–26108] The order number entered does not exist as an open order.

[APP–26109] There are more than one orders with this order number. Please specify order type first

or use List of Values

[APP–26110] Fail to setup pick release online. Disable pick release online button.

[APP–26111] Please remove freight charge references from this container.

[APP–26112] This delivery has been backordered.

[APP–26113] This delivery has been canceled.

[APP–26114] This delivery has been closed.

[APP–26115] Inventory details are required for delivery lines in this delivery.

[APP–26116] This delivery cannot be assigned to this departure because their freight carriers are

different.

[APP–26117] Duplicate delivery name: this must be unique across all organizations

[APP–26118] Only one delivery–level freight–charge can have an AETC value assigned.

[APP–26119] Freight charges on this delivery have been assigned to containers not included in this

delivery. Please assign missing containers to this delivery.

[APP–26120] Please unassign all delivery lines in this delivery.

[APP–26121] Please try this action again later. The data is being updated by another process.

[APP–26122] All delivery lines in this delivery must come from orders with the same currency code

and FOB point.

[APP–26123] Please try this action again later. The data is being updated by another process.

[APP–26124] This delivery has not been assigned to a departure.

[APP–26125] This delivery is not open.

[APP–26126] This delivery is not packed.

[APP–26127] This delivery is not planned.

[APP–26128] This delivery cannot be deleted here.

[APP–26129] This delivery has no delivery lines assigned.

[APP–26130] This delivery cannot be deleted or unplanned when it’s in Ship Confirm.

[APP–26131] Please assign a waybill to this delivery.

[APP–26132] Deliveries of internal orders must have an expected arrival date.

[APP–26133] Null Delivery Name

[APP–26134] This delivery is packed.

[APP–26135] At least one item is not packed.

[APP–26136] This delivery has &NUM_LINES delivery lines which have been pick released.

[APP–26137] This delivery is not open or planned.

[APP–26138] Please make sure that the ship sets in this delivery are complete.

[APP–26139] The ship set(s) in this delivery are not complete. Is it OK to ship parts of these ship

sets?

[APP–26140] Please make sure that the ship–together model(s) in this delivery are complete.

[APP–26141] The ship–together model(s) in this delivery are not complete. Is it OK to ship

incomplete models?

[APP–26142] This delivery has planned delivery lines which have not been pick released yet.

[APP–26143] This departure has been canceled.

[APP–26144] This departure has been closed.

[APP–26145] This departure has &NUM_DELIVERIES deliveries with a status other than packed,

closed, or cancelled.

[APP–26146] Please unassign all deliveries before deleting this departure.

[APP–26147] This departure has &NUM_DELIVERIES deliveries with a status other than ”open”

or ”planned”.

[APP–26148] Duplicate departure name: this must be unique across all organizations

[APP–26149] Please unassign all delivery lines from this departure before deleting it.

[APP–26150] This departure has at least one delivery line which is not assigned to any of its

deliveries.

[APP–26151] Please try this action again later. The data is being updated by another process.

[APP–26152] This departure is not open.

[APP–26153] This departure is not planned.

[APP–26154] This departure already has deliveries.

[APP–26155] Please specify the bill of lading.

[APP–26156] Please specify the freight carrier.

[APP–26157] There are no deliveries assigned to this departure.

[APP–26158] You cannot delete this departure here.

[APP–26159] There are no delivery lines assigned to this departure.

[APP–26160] Null Departure Name

[APP–26161] The planned departure date must be today or a future date.

[APP–26162] Some delivery lines in this departure have already been pick released.

[APP–26163] Some delivery lines in this departure have already been pick released.

[APP–26164] &ATTRIBUTE cannot be updated because some details in the order are assigned to a

delivery being planned.

[APP–26165] This delivery line has already been assigned to a delivery.

[APP–26166] This delivery line has already been assigned to a departure.

[APP–26167] All delivery lines assigned to a delivery must have the same customer and ship–to

address.

[APP–26168] This delivery line does not have the same freight carrier as in the target departure.

[APP–26169] This delivery line does not have the same FOB, currency code and freight terms as

the target delivery.

[APP–26170] Please remove freight charges referencing this delivery line.

[APP–26171] This delivery line has already been pick released.

[APP–26172] A delivery line with a quantity of 1 cannot be split.

[APP–26173] A delivery line with equal requested and shipped quantities cannot be split.

[APP–26174] Lines have already been assigned to this delivery/departure.

[APP–26175] The Item range is invalid (from value must be less than to value).

[APP–26176] Order Number range is invalid (From value must be less than To value).

[APP–26177] Production Line range is invalid (From value must be less than To value).

[APP–26178] Production Sequence range is invalid (From value must be less than To value).

[APP–26179] Schedule Date range is invalid (From value must be less than To value).

[APP–26180] Lines have not yet been assigned.

[APP–26181] Master–Detail relationship is ON, cannot assign

[APP–26182] Cannot lock the delivery lines.

[APP–26183] Customer Job range is invalid (From value must be less than To value).

[APP–26184] Deliveries have been created

[APP–26185] Delivery is not open, cannot (un)assign.

[APP–26186] This delivery attribute is not updatable

[APP–26187] Could not update delivery attributes from delivery lines.

[APP–26188] Sequence Number of a delivery must be unique within a departure.

[APP–26189] Attribute values are not unique to create a single delivery.

[APP–26190] Departure is not open, cannot (un)assign.

[APP–26191] Attribute values are not unique to create a single departure

[APP–26192] Departure does not have any deliveries assigned to it.

[APP–26193] Loading sequence of a delivery line must be unique within a delivery.

[APP–26194] Enter UOM codes to calculate the weight and volume.

[APP–26195] Please enter volume UOM code.

[APP–26196] Please enter weight UOM code.

[APP–26197] Departure Planning is not possible if OE: Included Item Freeze Method is ’Pick

Release’

[APP–26198] Invalid expected arrival date

[APP–26199] Invalid sequencing of departures

[APP–26200] Invalid planned departure date

[APP–26201] Invalid action for open delivery

[APP–26202] Invalid action for open departure

[APP–26203] Invalid action for planned delivery

[APP–26204] Invalid action for planned departure

[APP–26205] Lines have been released, cannot take action now

[APP–26206] Possible long running query. OK or Cancel

[APP–26207] Departure date and arrival date are mismatched (departure must be afer arrival).

[APP–26208] The order is closed

[APP–26209] Developer Error: could not build parameter list to call Pick Release Form

[APP–26210] No shipping parameters found for this organization (&ORGANIZATION_ID). Please

define these first.

[APP–26211] Do you want to plan the entire model?

[APP–26212] Do you want to plan the entire ship set?

[APP–26213] Please query the lines before taking any action

[APP–26214] Please regenerate loading sequence

[APP–26215] Vehicle information in master table not available

[APP–26216] This line’s &ATTRIBUTE cannot be updated because its details are assigned to a

delivery being planned.

[APP–26217] Warning: This line’s details are assigned to a delivery being planned.

[APP–26218] This line detail cannot be canceled.

[APP–26219] This line detail’s warehouse cannot be updated because it is assigned to a delivery or

departure.

[APP–26220] This line detail cannot be deleted.

[APP–26221] This delivery line is assigned to a delivery whose status is ’planned’.

[APP–26222] This line’s quantity cannot be updated because its details are assigned to a delivery

being planned.

[APP–26223] Serial Number is not valid for this combination of inventory controls.

[APP–26224] Warning: This line detail has been sequenced in a production.

[APP–26225] Cannot launch Pick Release Online without specifying either Order Number,

Departure or Delivery information.

[APP–26226] These items are not packed in containers: &UNPACKED_LIST

[APP–26227] Cancelled deliveries cannot be unassigned.

[APP–26228] This delivery line does not have the same freight carrier as in the target delivery.

[APP–26229] Submitted &SUBMITTED_DOCS out of &TOTAL_DOCS documents for this

document set.

[APP–26230] No Documents Submitted

[APP–26231] &ARGUMENT is a required argument for &DOCUMENT. Please supply a value to

Document Set Submission API or define a default value for this Concurrent Porgram parameter.

[APP–26232] Please enter at least one Release Sequence Priority.

[APP–26233] This line’s &ATTRIBUTE cannot be updated because an assigned departure is closed.

[APP–26234] This line’s &ATTRIBUTE cannot be updated because the line is assigned to a

delivery.

[APP–26235] Receivables Interface

[APP–26236] Inventory Interface

[APP–26237] Ship Confirm Open Interface

[APP–26238] Pick Release

[APP–26239] Pick Release

[APP–26240] RMA Interface

[APP–26241] Shipping Documents

[APP–26242] Shipping Interfaces

[APP–26243] Shipping Reports

[APP–26244] Shipping Reports and Documents

[APP–26245] Update Shipping

[APP–26246] &Document in your Document Set has an argument, &ARGUMENT, which is not

supported by the Document Set Submission API. Please rename the argument.

[APP–26247] Some of the packed containers do not meet their minimum fill requirements.

[APP–26248] Invalid Loading Order ’&LOAD_ORDER’ for the delivery.

[APP–26249] Load Sequence for the delivery lines have been generated. Please requery the lines to

see them.

[APP–26250] Loading Order of the delivery must be entered to generate loading sequences of

delivery lines.

[APP–26251] The Customer Job range is invalid (From value must be less than To value).

[APP–26252] All shipped items are packed.

[APP–26253] Freight Carrier cannot be NULL.

[APP–26254] Do you want to continue this action ?

[APP–26255] &LOAD_ITEM is already defined as containing &CONTAINER_ITEM.

[APP–26256] Load and Container Items must be different.

[APP–26257] At least one group by criteria must be selected.

[APP–26258] Please save your work before performing this action.

[APP–26259] Commit error! Can’t save your work.

[APP–26260] The container quantity is negative.

[APP–26261] Cannot pack the container into itself.

[APP–26262] This Locator already exists. Locators must be unique.

[APP–26263] Failed to calculate the container weight.

[APP–26264] Failed to query the delivery line entered from database.

[APP–26265] The inventory controls entered for this delivery line are invalid or do not exist.

[APP–26266] Cannot pack master containers into detail containers. Please check the relationship

defined in form ’Container–Load Relationships’.

[APP–26267] The lot number entered is expired.

[APP–26268] You are exceeding the maximum quantity that can be packed in this container.

[APP–26269] The number of serial numbers entered is greater than the shipped quantity.

[APP–26270] Failed to assign the delivery line to current delivery.

[APP–26271] Failed to populate delivery line information. Cannot assign the delivery line to current

delivery.

[APP–26272] Shipped Quantity is negative.

[APP–26273] Quantity Shipped is more than quantity requested.

[APP–26274] The Shipped quantity cannot be zero or NULL.

[APP–26275] The weight entered is negative.

[APP–26276] Failed to validate the quantity of the items packed into the containers.

[APP–26277] You cannot assign this Departure to the Delivery.

[APP–26278] You cannot delete this Delivery.

[APP–26279] Do you want to delete this Delivery ?

[APP–26280] An error occured in Weight–Volume Calculations.

[APP–26281] Please enter the Unit of Measure for Weight and/or Volume.

[APP–26282] Weight or Volume cannot be less than zero.

[APP–26283] The AETC information supplied is incomplete.

[APP–26284] AETC is not allowed here.

[APP–26285] You have entered a duplicate Ship To Address.

[APP–26286] You tried to perform an invalid action.

[APP–26287] You need to query a Delivery before you can perform this action.

[APP–26288] An Organization has not been chosen.

[APP–26289] Some Shipping Parameters have not been setup for this Organization.

[APP–26290] Date is outside of current inventory period

[APP–26291] Actual departure date cannot be a future date

[APP–26292] The parameters for printing this document set are invalid or not complete.

[APP–26293] Unable to completely backorder this delivery.

[APP–26294] You cannot modify the warehouse. It must be the same as the order line warehouse.

[APP–26295] You cannot add lines to a delivery that is already packed.

[APP–26296] Both Delivery ID and Name cannot be null: please input one.

[APP–26297] This container is not valid (or not valid in this warehouse for this delivery).

[APP–26298] Invalid customer.

[APP–26299] Invalid Delivery Status (only Open, Packed and Planned are permitted).

[APP–26300] Invalid Departure : cannot create this.

[APP–26301] Invalid Departure status (cannot assign to a closed or cancelled departure).

[APP–26302] Invalid Intermediate Ship To Address.

[APP–26303] Invalid Pooled Ship to Address.

[APP–26304] Invalid Ultimate Ship To Address.

[APP–26305] Both Container_id and Sequence cannot be null: please specify one.

[APP–26306] Please check Packed Containers for Error.

[APP–26307] Cannot process until previous transactions for this delivery complete.

[APP–26308] Please enter a unique delivery name that is not already in use.

[APP–26309] Please enter a unique departure name that is not already in use.

[APP–26310] The load does not meet the minimum fill required.

[APP–26311] Error occurred while processing delivery &DEL_NAME

[APP–26312] The vehicle is overfilled.

[APP–26313] The load’s volume exceeds the vehicle’s maximum volume.

[APP–26314] The load’s gross weight exceeds the vehicle’s maximum load weight.

[APP–26315] NO RATE

[APP–26316] The Requested quantity cannot be equal to the Shipped quantity.

[APP–26317] The Requested quantity cannot be one.

[APP–26319] Outstanding Invoice Value must have the highest priority (the lowest value), if it is

entered.

[APP–26320] Priority rankings must be unique.

[APP–26322] Assigning to a PLANNED departure will automatically plan this delivery. Do you

want to continue?

[APP–26323] The source type cannot be updated because this order line has been assigned to a

departure or a delivery.

[APP–26324] The source type cannot be updated because this order line has been released.

[APP–26325] Invalid parameters for Update Shipping. Please specify Departure or Delivery.

[APP–26326] Invalid Freight Charge Type (either ID or CODE)

[APP–26327] Invalid Delivery ID.

[APP–26328] The warehouse for this container is not valid (it must be the same as the Delivery to

which it is assigned).

[APP–26329] Cannot reassign this line to another delivery (current delivery must be open).

[APP–26330] Delivery Lines must be picked from the same warehouse as the delivery ships from.

[APP–26331] &MESSAGE_1 &MESSAGE_2 &MESSAGE_3 &MESSAGE_4

[APP–26332] &L_COUNT container types are overloaded by &LOAD_PERCENT percent. The

most overloaded container type has the sequence ’&L_SEQ_NUMBER’.

[APP–26333] &V_COUNT container types are overpacked by &VOLUME_AMOUNT

&VOLUME_UOM. The most overpacked container type has the sequence ’&V_SEQ_NUMBER’.

[APP–26334] &W_COUNT container types are overweight by &WEIGHT_AMOUNT

&WEIGHT_UOM. The most overweight container type has the sequence ’&W_SEQ_NUMBER’.

[APP–26335] &U_COUNT container types do not meet their minimum fill percentages. The least

filled container type has the sequence ’&U_SEQ_NUMBER’.

[APP–26336] This line is not interfaced because the Credit Memo Type is missing from the

Transaction Type (which is set up in Accounts Receivables and is associated with the Order Type).

[APP–26337] Price list &PRICE_LIST includes pricing for this item for multiple UOMs or pricing

attributes. This discount will apply to each listed price, regardless of UOM or pricing attributes.

Specify a percentage discount to ensure proportional discounts.

[APP–28000] You can use the Copy function only for new constraints

[APP–28001] QtySum and Sum functions can only be used to operate on numeric attributes

[APP–28002] Operators In and Not In require List function on the Right Hand Side of the constraint

clause

[APP–28002] This constraint name does not exist

[APP–28003] The value returned by the Left Hand Side of the constraint clause must be of the same

data type as the value returned by the Right Hand Side of the clause

[APP–28004] The number of Left parentheses must match the number of Right parentheses

[APP–28005] Optimization Expression is not valid

[APP–28006] You cannot delete an AutoSelection Range that has AutoSelection Items associated

with it

[APP–28007] You must enter a unique Attribute List Name

[APP–28008] You must enter a unique Attribute List Value

[APP–28009] An Internal Error occured in Routine &PACKAGE, Oracle Error –&ORA_ERROR,

&ORA_TEXT

[APP–28010] Internal error has occured. &TEXT

[APP–28011] AutoSelection Constraints can only be assigned to Models or Option Classes

[APP–28012] An operator must be specified for all clauses other than the first

[APP–28013] The Constraint name, Item or Configurator System Type, Organization and Constraint

Group entered is not a unique combination

[APP–28014] The Constraint is not assigned to an Item or Configurator System Type

[APP–28015] The evaluated AutoSelection Quantity assigned to Constraint &NAME is not an

integer

[APP–28016] No Items were found for the AutoSelection Constraint &NAME

[APP–28017] An error occured while evaluating the Optimization Expression &EXPRESSION

[APP–28018] Right Parenthesis missing in Optimization Expression.

[APP–28019] Optimization Expression contains a function with invalid number of arguments.

[APP–28020] Optimization Expression references clauses with datatypes, mismatched to operations

used.

[APP–28021] Optimization Expression Contains a clause name that does not exist.

[APP–28022] Optimization Expression contains a Clause with missing Right Bracket ( [ ) .

[APP–28023] Optimization Expression contains no clause or contains a Clause with missing Left

Bracket ( ] ) .

[APP–28024] Optimization Expression contains a clause with missing Right ( R ) or Left ( L )

Notation.

[APP–28025] Optimization Expression contains a clause with a missing comma.

[APP–28026] Optimization Expression contains a clause with missing colon.

[APP–28027] List Contains elements that are not embedded in quotes.

[APP–28028] List contains elements with missing comma.

[APP–28029] Number List cannot have quote.

[APP–28030] Number list contains Character.

[APP–28031] Invalid List.

[APP–28032] List elements have to be within parenthesis.

[APP–28033] Character Functions can only be used on Character Attributes.

[APP–28034] Literal List function requires an operator In or Not In.

[APP–28035] Autoselection Type of the constraint assignment cannot be modified if prior

autoselection ranges, items or user autoselection functions exist

[APP–28036] Constraints cannot be deleted when Assignments for them exist

[APP–28037] Constraint Type cannot be updated since Constraint Assignments exist

[APP–28038] An Autoselection constraint can only be assigned to an Initialization or Autoselection

constraint group

[APP–28039] Suggestion, Error, Overrideable Error and Warning constraints can only be assigned to

Before Autoselection or After Autoselection constraint group

[APP–28040] An Autoexclusion constraint can only be assigned to the Initialization constraint

group

[APP–28041] Left Hand Side function object attribute combination not supported

[APP–28042] Right Hand Side function object attribute combination not supported

[APP–28043] Comparison between the Left Hand Side and Right Hand Side of this clause is not

allowed. Please check their return data types

[APP–28044] The effectivity date of the autoselection range has to be later than the effectivity date

of the constraint assignment

[APP–28045] The effectivity date of the autoselection item has to be later than the effectivity date

of the autoselection range

[APP–28046] The disable date of the autoselection range has to be earlier than the disable date of

the constraint assignment

[APP–28047] The disable date of the autoselection item has to be earlier than the disable date of the

autoselection range

[APP–28048] Range is required.

[APP–28048] The autoselection from–to range contains non numeric values

[APP–28049] The value for to range has to be greater than the value for from range

[APP–28050] AutoSelection Items must be Standard Items or Models

[APP–28051] Value for the object is required before entering a value for the Attribute

[APP–28051] Warning: You are autoexcluding all options from a mandatory option class

[APP–28052] Disable date should be later than the Effectivity date

[APP–33001] Syntax error : line &1 position &2

Cause:

The formula contains some unexpected text which cannot be verified. The line number and position

of the text is given.

Action:

Correct the error in the formula and verify again.

[APP–33002] Syntax error : line &1 position &2

Cause:

The formula contains some unexpected text which cannot be verified. The line number and position

of the text is given.

Action:

Correct the error in the formula and verify again.

[APP–33003] Line &1: ’&2’ is of type &3 but has &4 type assigned into it.

Cause:

The data type of the expression on the right hand side of the assignment statement does not match

the data type of the variable on the left hand side of the assignment, probably because of an earlier

assignment to the variable of a different data type.

Action:

Ensure data types of assignments match, or that variable being set has not been set before to another

data type.

[APP–33004] Line &4: Item &1 is incorrect type: &2 expected, &3 actual.

Cause:

An unexpected data type was found during type testing. The line number, item and expected and

actual data types are given.

Action:

Check that the data type of the item is what you expect. Does the use of the item break FastFormula

rules. Possibly a conversion function such as to_char() is needed. Please consult the documentation

for further information.

[APP–33005] The local variable &1 was used before being initialized

Cause:

The variable named in the error message is being used before any value has been assigned to it, so it

has no meaningful value.

Action:

Please ensure variables have been assigned to before using them.

[APP–33006] The statement at line &1 has an invalid combination of data types

Cause:

A statement contains an invalid combination of data types, for example an expression which

contains sub–expressions of different data types.

Action:

Ensure data types within expressions match.

[APP–33008] Unknown function ’&1’ used in statement at line &2. The user specified a function in

his formula, the next name of which was not matched with any function in thefunction table.

Number: abs (n) Absolute value of n. floor(n) Integer value ofn. roundup(n[,m]) Round up n to m

decimal places; round_up ifm omitted, to 0 places. trunc(n[,m]) Truncate n to m decimal places;

truncate if momitted, to 0 places. round(n[,m]) Round n to m decimal places; if m is omitted to 0

places. least(n,n[,n]...) Return the lowest numberlisted. least_of greatest(n,n[,n]...) Return the

highest number listed. greatest_of Text: length(exp) Return length of exp. least(exp,exp[,exp]...)

Return the expression first least_of in alphabetical order. greatest(exp,exp[,exp]...) Return the

expression lastgreatest_of in alphabetical order. substr(exp,m[,n]) Return the substring of

exp,substring beginning at the mth character, n characterslong; if n is omitted, to end of exp. Date:

days_between(d1,d2) Days between dates d1 andd2. months_between(d1,d2) Months between dates

d1 andd2. years_between(d1,d2) Years between dates d1 andd2. least(d,d[,d],...) Returns earliest

date. least_of greatest(d,d[,d]...) Returns latestdate. greatest_of add_days(d,n) Add n days to dated.

add_months(d,n) Add n months to date d. add_years(d,n) Add n years to date d. Conversion:

to_char(n) Converts the numeric value nto_text into it’s text equivalent. to_date(exp) Converts the

text expression exp into adate.

[APP–33009] ’&1’ was named twice in INPUTS or RETURN statement at line &2

Cause:

A Local variable was named more than once as a parameter of an INPUTS or RETURN statement.

Action:

Please refer to variables once only in INPUTS and RETURN statements.

[APP–33010] Formula contains more than one INPUTS statement

Cause:

You have more than one INPUTS statement in your formula.

Action:

Use a single INPUTS statement containing all input variables.

[APP–33012] Line &1: ’&2’ is not a local variable: assignment is not allowed

Cause:

An illegal assignment was found caused by assignment to a variable that was not a local variable.

Action:

Please ensure that only local variables are assigned values.

[APP–33013] Line &2: Global ’&1’ illegally used in INPUTS or RETURN statement

Cause:

A global variable has been used in an INPUTS or RETURN statement.

Action:

Please use only local variables in INPUTS or RETURN statements.

[APP–33014] Line &2: DB Item ’&1’ illegally used in INPUTS or RETURN statement.

Cause:

A database item has been used in an INPUTS or RETURN statement.

Action:

Please use only local variables in INPUTS or RETURN statements.

[APP–33015] &1 is not a Local Variable – not allowed in INPUTS statement

Cause:

This error should not occur as there are now specific errors for global and database items used in

INPUTS and RETURN statements. Only Local Variables may be named in the INPUTS statement.

Action:

Please refer to your local support representative.

[APP–33016] &1 is Global variable: type declaration not allowed

Cause:

A type declaration has been made for a global variable.

Action:

Please do not make type declarations for global variables.

[APP–33017] &1 is Database Item: type declaration not allowed

Cause:

A type declaration has been made for a database item.

Action:

Please do not make type declarations for database items.

[APP–33018] The Item &1 is declared as being of conflicting types.

Cause:

An item has been declared twice but with conflicting data types.

Action:

Please only make type declarations once per variable, and only if necessary such as non–numeric

INPUT variables.

[APP–33019] Line &1: Item or Function name is too long: &2

Cause:

The Item or Function Name exceeds the maximum length allowed for names. At present this length

is set to 60.

Action:

Please use item names of 60 bytes or less.

[APP–33020] Formula is too large

Cause:

The formula is too large.

Action:

Please reduce the size of the formula until it verifies.

[APP–33023] Running formula &1.

Information message to tell user that named formula is being run.

[APP–33025] Initializing

Information message to tell the user that ffuevf is initializing.

[APP–33026] Parsing formula &1.

Information message to tell user that the formula is being parsed.

[APP–33027] Checking &1.

Information message to tell user that the formula is being checked.

[APP–33028] Generating PL–SQL.

Information message to tell user that PL–SQL is being generated.

[APP–33029] Formula &1 verified successfully.

Information message to tell the user that the formula has successfully been verified (compiled).

[APP–33030] Running formula &1

This information is displayed when formulas are run via AF.

[APP–33032] Translating ’&1’

This message does not indicate an error, but is for information only. When a QuickPaint report has

been written, and is being committed to the database, it is also translated into a formula. This

message indicates that the translation is taking place.

[APP–33039] The Value is in an incorrect format for the Type.

Cause:

For a global, you are trying to enter a Value which is inconsistent with the Type you have chosen.

Action:

Enter a value in the correct format for the type. For example, check a global of Number type

contains only numbers, or a global Date is in the format DD–MON–YYYY (so August 14 1992

would be 14–AUG–1992)

[APP–33052] The name ’&1’ is already used by a &2

Cause:

There is already a &2 called by the name that you have chosen.

Action:

Please choose another name.

[APP–33054] &VALUE_NAME name includes reserved words or characters. Re–enter

Cause:

You are trying to enter a name with words or characters the application reserves for its own use.

Action:

You cannot use reserved words or characters in a name. The name must contain only A–Z, a–z, 0–9

or underscore (_) characters. Also, you cannot start a name with a number.

[APP–33055] Line &1: Function ’&2’ has mixed token and non–token arguments.

Cause:

The function &2 was called with a mixture of tokenized and non–tokenized arguments.

Action:

Use the function &2 with either all tokenized or all all non–tokenized arguments

[APP–33061] Syntax error at line &1 position &2: Date format must be &3

Cause:

The date supplied is not the correct format (as indicated).

Action:

Format the date in the correct format shown.

[APP–33062] Line &1: Alias for &2 not allowed. Can only alias globals and DB items

Cause:

You have tried to alias a formula variable that was not a global or a database item

Action:

Only alias items whose name you cannot change such as database items or global variables.

[APP–33063] Alias &3 at line &2 of &1 is already used by another variable.

Cause:

You have specified an alias which has the same name as an existing variable.

Action:

Rename your alias to be different from existing variables.

[APP–33064] Line &1: Statements are ordered incorrectly.

Cause:

You have written an alias, default or input statement after a formula statement.

Action:

Alias and default statements must be first in your formula, followed by any input statement and

lastly the formula statements.

[APP–33065] Line &1: Only database items or input variables can be defaulted.

Cause:

You have specified an item to be defaulted which is not a database item or an input variable.

Action:

Use a database item or input variable in the default statement. If you want to change the value of a

local variable, simply assign a value to it. You can change global variable values using the Manage

Globals form.

[APP–33066] This formula contains no formula statements.

Cause:

You have written a formula which contains no statements, and as such, will not perform any useful

function.

Action:

Add some statements to the formula. Refer to FastFormula guide for more details.

[APP–33067] Error: Global variable &1 ends before end date of current formula.

Cause:

You are referencing a global variable whose end date is before the end date of the current formula.

Action:

Set the end date of the current formula to before the end date of the global variable, or extend the

global variable beyond the end date of the current formula.

[APP–33068] Global variables referenced in the formula have expired.

Cause:

The DateTrack operation selected for this formula causes the new date range for the formula to be

invalid because global variables which are referenced by the formula expire before the new formula

end date.

Action:

Investigate lifetime of global variables referenced within formula, and either extend their lifetime to

that of the formula or reduce the formula lifetime so it does not exceed that of referenced global

variables.

[APP–33069] Error at line &1 position &2: Empty string ’’ not allowed

Cause:

FastFormula does not allow empty strings.

Action:

Please use one or more characters in quotes to form a string.

[APP–33070] There are no more contexts available (maximum allowed is &1)

Cause:

The maximum number of allowed contexts has been reached.

Action:

Remove any old or unused contexts.

[APP–33071] The formula &1 has not been verified with this version.

Cause:

The formula has not been verified with the current version of FastFormula.

Action:

Reverify the formula before attempting to run it again.

[APP–33072] Database item ’&1’ cannot be found [&2,&3,&4]

Cause:

The named database item could not be found within the FastFormula dictionary [Formula Type

Id,Business Group Id, Legislation Code]

Action:

Please contact your local support representative.

[APP–33074] The variable ’&1’ matches a context name and must be changed.

Cause:

The variable ’&1’ has been used in the formula, but is also used as a context name on which a

database item has been based.

Action:

Please choose another name for variable ’&1’

[APP–33075] The item ’&1’ is referenced by one or more verified formulae.

Cause:

You have attempted to change or remove an item which is referenced by one ore more formulae.

Removal of this item will invalidate the verified formula and cannot be allowed.

Action:

Remove the verified formula before removing the item.

[APP–33076] Action will invalidate one or more compiled formula.

Cause:

An action has been requested which will invalidate one or more compiled formula.

Action:

Remove compiled formulae and retry. Then reverify all formulae.

[APP–33077] Error at line &1: Only local variables can be used for OUT parameters

Cause:

You have passed a variable other than a local variable to a function parameter which the function

expects to modify

Action:

Please use local variables only for function parameters which may be modified.

[APP–33099] Token too long: line &1 position &2

Cause:

A Name, or Text String exceeds its maximum permitted length.

Action:

Please reduce the length of the token.

[APP–33101] QuickPaint error detected (FF–&1)

[APP–33102] &1 parameter(s) passed to QUICKPAINT_GET instead of expected &2

Cause:

The userexit was called with the wrong number of parameters

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33104] Unable to access field QP_CONTEXT.QP_REPORT_ID

Cause:

There must be a field (usually a hidden field) called QP_REPORT_ID which holds the numeric

unique key for the report.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33105] Bad value (&1) in field QP_REPORT_ID

Cause:

The (hidden) field QP_REPORT_ID was accessed by the userexit, and found to have a value of zero

or less.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33106] Unable to write to field ’&1’

Cause:

One of the fields that receive a line of report text could not be accessed for writing. This would

normally indicate that the field field does not exist in the current block.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33107] No parameter list passed to QuickPaint user exit

Cause:

Application Foundation passes a parameter list, called ”argv”, to the QuickPaint user exit, but this

was found to be missing.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33108] &1 parameters expected, &2 found

Cause:

The wrong number of parameters was passed into a QuickPaint user exit.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33110] Negative or zero report identifier (value = &1)

Cause:

The report identifier is a number that acts as the unique identifier for each report in the table

FF_QP_REPORTS. It is generated from a sequence.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33111] QuickPaint report name missing

Cause:

A blank report name was passed to a QuickPaint user exit.

Action:

Please supply a name for an existing report.

[APP–33112] Bad NUMBER_OF_LINES parameter (value = &1 : should be 1 – &2)

Cause:

The NUMBER_OF_LINES parameter, which indicates the number of lines on the QuickPaint

screen, is outside the acceptable range.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33113] Unable to access field ’&1’

Cause:

There should be a field on the screen, holding QuickPaint text, with a name of the form LINEnn

(where nn is a two–digit number). If the parameter to the QUICKPAINT_BUILD exit indicates that

there will be e.g. 12 lines, then there should be fields called LINE01, LINE02, up to LINE12.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33114] QUICKPAINT_SAVE: bad formula_id (&1)

Cause:

The formula_id parameter to the QUICKPAINT_SAVE exit has a value that it is either a negative

number, or starts with a non–digit.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33115] QUICKPAINT_DELETE: No parameter list passed

Cause:

Application Foundation passes a parameter list, called ”argv”, to the QuickPaint user exit, but this

was found to be missing.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your loca support representative.

[APP–33116] QUICKPAINT_DELETE: &1 parameters expected, &2 found

Cause:

The wrong number of parameters was passed into a QuickPaint user exit.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33117] QUICKPAINT_DELETE: bad formula_id (&1)

Cause:

The formula_id parameter to the QUICKPAINT_DELETE exit has a value that is either a negative

number, or starts with a non–digit.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33118] A QuickPaint error occurred (in QUICKPAINT_DELETE trigger)

This is a cover message, giving the name of the userexit in which the error occurred. The real error

information follows in the subsequent message (usually displayed when carriage–return is pressed).

[APP–33119] Zero value for formula_id (as held in FF_QP_REPORTS)

Cause:

The FF_QP_REPORTS table has a column called FORMULA_ID, which is a foreign key into the

FF_FORMULAS table. When the QUICKPAINT_DELETE trigger is called, the value of

FORMULA_ID is passed in. This value, as passed in, was zero. It should have a positive numeric

value.

Action:

This is an error in the application calling FastFormula. If you are running an Oracle application

please refer to your local support representative.

[APP–33151] This Report Name Already Exists For A Formula Of The Same Type.

Cause:

A QuickPaint report name was entered which already exists.

Action:

Choose another report name.

[APP–33152] The Character ’ Is Not Allowed in the Report name.

Cause:

The character ’ was used in the name of the QuickPaint report.

Action:

Choose a report name which does not contain the ’ character.

[APP–33153] QUICKPAINT_SAVE: bad formula type id &1

Cause:

The Formula_type_id parameter to the QUICKPAINT_SAVE exit contains invalid characters. It

should only contain the digits 0–9 with an optional preceding ’–’ character.

Action:

Please refer to your local support representative.

[APP–33201] Empty formula supplied (Formula_Id=&1)

Cause:

A formula with length 0 was presented for execution. The length refers to the compiled (pl/sql)

formula, not the original formula text, as found in the FF_COMPILED_INFO table.

Action:

Please refer to your local support representative.

[APP–33202] No such formula (&1)

Cause:

The Application–ID, Formula Type, and Formula Name, used to identify the formula in the

FF_COMPILED_INFO table, do not correspond to any known formula.

Action:

Please refer to your local support representative.

[APP–33205] Formula &1: &2

Cause:

During the PL/SQL execution part, an Oracle error was detected.

Action:

Please refer to your system administrator.

[APP–33208] ORA&2 occurred at line &3 of formula &1

Cause:

Whilst executing PL/SQL, an Oracle error occurred. The line number and line position, are given

where available

Action:

Please refer to your system administrator.

[APP–33209] Unable to open file for reading (&1)

Cause:

Attempting to open a text file that contains data that is to be read in to memory.

Action:

Check that file exists and you have permission to read it.

[APP–33210] Unable to write to file (&1)

Cause:

An error occurred attempting to open a file for writing.

Action:

Please check you have permission to create or write to the file.

[APP–33211] Error writing to file (&1)

Cause:

An error occurred while attempting to write data into a file. The file has been successfully opened

for writing, but the fputs() function was unable to write.

Action:

Please refer to your system administrator.

[APP–33212] Unable to open file for reading (&1)

Cause:

An error occurred attempting to open a file for reading.

Action:

Check that the file exists and you have permission to read it.

[APP–33214] error while reading file (&1)

Cause:

An error was returned by the ftell() function.

Action:

Please refer to your system administrator.

[APP–33215] Attempt to convert NULL numeric (length=&1,item=&3)

Cause:

An attempt was made to convert an Oracleinternal number to a character representation of

thatnumber. The length provided with the Oracle number wasless than, or equal to, zero. This

normally occurs if aformula returns a NULL value through one of the numericvariables in its

RETURN statement. If a database item returns either a NULL, or no data was found for that

database item (which causes a NULL value), and the NULL gets put into a numeric variable, which

gets RETURNed, this error arises. This error occurs with either output data, or debug printing (e.g.

ffxprs())

Action:

Please refer to your local support representative.

[APP–33216] Variable &3 not initialized at line &2 of &1

Cause:

An attempt has been made to use a local variable before it was initialized. This is normally detected

by the verifier, but in certain cases this is not possible, and will result in this error. This problem

can be corrected by the altering the formula. Assign an initial value to the variable before it is

referenced in the formula.

Action:

Please refer to your system administrator.

[APP–33217] Divide by zero at line &2 of &1

Cause:

An attempt was made to divide a number by zero. Suppose that a formula has an input called

NUMBER_IN, and a line of the form NUMBER_OUT = 100 / NUMBER_IN. If NUMBER_IN was

passed a value of zero, then this error would result.

Action:

Please refer to your system administrator.

[APP–33218] Data &3 not found at line &2 of &1

Cause:

A SQL SELECT statement, obtained from the application dictionary, returned no rows when

executed.

Action:

Please refer to your local support representative.

[APP–33219] Too many rows returned for &3 at line &2 of &1

Cause:

The application dictionary has not been set up correctly. One of the SQL statements that it contains

would cause more than one row to be selected.

Action:

Please refer to your local support representative.

[APP–33220] Value exceeded allowable range (line &2 of &1)

Cause:

Caused by Oracle error 6502 occurring during the execution of the formula which is raised when an

arithmetic conversion error, or string truncation error occurs. This can also be caused by invalid

dates, e.g. 39–DEC–1991, 24–MAR–5000

Action:

Check your formula for possible invalid dates,numbers or strings greater than 255 characters in

length.

[APP–33221] Invalid number at line &2 of &1 (Object &3)

Cause:

An attempt was made to convert a character string to a number, but the character string did not

contain a valid numeric literal.

Action:

The formula may need altering, or there may be a problem with a value being returned from the

database.

[APP–33222] NULL value for &3 at line &2 of &1

Cause:

A SQL SELECT statement, obtained from the application dictionary, returned a column whose

value was NULL.

Action:

Please refer to your local support representative.

[APP–33223] Bad data type (&2) for Global Table Entry (&1)

Cause:

The global table has a row whose data type is not one of N (numeric), T (text) or D (date)

Action:

Please refer to your local support representative.

[APP–33224] Bad datatype (&1) in FF_FDI_USAGES (Item &2, Fmla &3)

Cause:

Only N,T or D permitted in the usage column of the FF_FDI_USAGES table. (These refer to

Numeric, Text or Date data).

Action:

Please refer to your local support representative.

[APP–33226] Item ’&1’ has &2 Fillers provided, but no placeholders for them

Cause:

In the Application Dictionary Route table, the route text for the database Item specified in Code 1

did not contain 1 or more matching placeholders for the User Where Clause Fillers associated with

the Database Item. For example, an B4 filler may have been provided, and when scanning the route

text for a placeholder in which to insert it, no matching placeholder was found.

Action:

Please refer to your local support representative.

[APP–33227] Item ’&1’ has &2 Column usages provided, but no placeholders for them

Cause:

Bad route or Route Column Usages in the Application Dictionary In the Application Dictionary

Route table, the route text for the database Item specified in Code 1 did not contain 1 or more

matching placeholders for the Route Column Usages associated with the Database Item.

Action:

Please refer to your local support representative.

[APP–33228] Placeholders in route text for &1 remain uncompleted.

Cause:

After replacement of the User Where Clause Fillers and the Route/ Context usages placeholders in

the Database Item’s Route text, some placeholders remain. This probably means that either

incorrect route text was entered, or the definition of the database item is incomplete.

Action:

Please refer to your local support representative.

[APP–33229] Global variable &1 has invalid data type (must be D, N or T)

Cause:

The data type for the item &1, as held in the Globals table, is invalid. It must be one of T (Text), D

(Date) or N (Number).

Action:

Change the data type for this global variable using the Define Globals form.

[APP–33230] The Item &1 is both a Global Variable and a Database Item

Cause:

The item named in &1 appears both in the FF_GLOBALS table, as a global variable and in the

FF_DATABASE_ITEMS table as a database item.

Action:

Remove or rename the global variable to a unique name.

[APP–33231] The DB Item &1 has an invalid data type: must be D, N or T

Cause:

The item named in &1 was found in the FF_DATABASE_ITEMS table to have an invalid data type.

The data type must be either N (Number), T (Text) or D (Date).

Action:

Please refer to your local support representative.

[APP–33232] &1 has null or not found allowed, but no default set specified.

Cause:

If a Database Item has null allowed, or not found allowed, then the item must also specify a default

set to be used to provide default values in the event of these occurring. The item named has one of

these conditions allowed, but the default set column in the FF_DATABASE_ITEMS table is null.

Action:

Please refer to your local support representative.

[APP–33234] Internal Error : (&1)

Cause:

Formula details could not be found for the formula id named.

Action:

Please refer to your local support representative.

[APP–33236] Bad data type (&1) for database item &2

Cause:

When reading values from the FF_DATABASE_ITEMS table, QuickPaint found a data type other

than ’N’, ’T’, or ’D’.

Action:

Please refer to your local support representative.

[APP–33238] UDF Error in formula &1 at line &2: &3

Cause:

An error occurred in the formula at the line indicated because of a UDF error. The UDF error

message is also shown.

Action:

Please correct the problem within the UDF, or refer to your system administrator.

[APP–33239] Internal Error: &1, &2

Cause:

An unexpected error has occurred whilst attempting to match context levels.

Action:

Please refer to your local support representative.

[APP–33302] The tester entered TYPED–ASSIGNING mode without its data type set up.

Cause:

The tester entered TYPED ASSIGNING mode without having it’s data type set up. This should

never happen, as this mode is only entered when the LHS of an assignment statement is entered, by

which time, if the RHS did not provide a type, an error should already have been detected.

Action:

Please refer to your local support representative.

[APP–33303] Bad data type non terminal node found in LHS of assignment statement

Cause:

While type testing, a non–terminal node was encountered at the LHS of an assignment statement,

and it had a different data type to the type that the tester expected. (At present there are no

nonterminals at the LHS of assignment statements, so this represents a double error condition.)

Action:

Please refer to your local support representative.

[APP–33304] Internal error : Code 1 is &1

Cause:

An unknown node type was encountered in the tree, which could not be found in the unflattening

table.

Action:

Please refer to your local support representative.

[APP–33305] Internal error : Code 1 is &1

Cause:

A bad action was received from tree walker: at present this means that the action was not one of

VISIT, LEAVE or BB. Code 1 is the actual action code received.

Action:

Please refer to your local support representative.

[APP–33306] Internal error : Code 1 is &1

Cause:

A bad tester current mode was encountered : the offending mode is displayed in &1.

Action:

Please refer to your local support representative.

[APP–33307] Internal error : Code 1 is &1

Cause:

An unrecognized action was encountered.

Action:

Please refer to your local support representative.

[APP–33309] Internal Error

Cause:

A match action taken from the Flattening table for this node type was found to be invalid.

Action:

Please refer to your local support representative.

[APP–33310] Internal Error – Code 1 is &1

Cause:

While searching the Unflattening table for the node type no match was found, i.e this is an

unrecognized node type.

Action:

Please refer to your local support representative.

[APP–33311] Internal Error – Code 1 is &1

Cause:

While performing unflattening, a node of unexpected type was found in the parse tree. The node

type is in Code 1.

Action:

Please refer to your local support representative.

[APP–33312] Internal Error – Code 1 is &1

Cause:

A node was found in the unflattening table, but the data type in the table for the node was not

recognized. Code 1 is the unknown data type.

Action:

Please refer to your local support representative.

[APP–33313] Internal Error – Code 1 is &1, Code 2 is &2

Cause:

Calling the tree walking function to go to the first child under an INPUTS node resulted in a bad

return code. Code 1 is the Node ID of the INPUTS statement, Code 2 is the return code from the

goto child function.

Action:

Please refer to your local support representative.

[APP–33314] Internal Error – Code 1 is &1

Cause:

Bad return code from tree walker attempting to goto an adjacent node. Return code is in Code 1.

Action:

Please refer to your local support representative.

[APP–33322] Internal Error – Code 1 is &1, COde 2 is &2

Cause:

While calling a tree walking function to go to the first child of an ASSIGNMENT node, a bad return

code was received. The code received is in Code 2, and the ASSIGNMENT node ID is in Code 1.

Action:

Please refer to your local support representative.

[APP–33323] Internal Error – Code 1 is &1, Code 2 is &2

Cause:

Bad return code from tree walker attempting to go to a child node. Code 1 contains the node ID of

the parent node Code 2 contains the return code.

Action:

Please refer to your local support representative.

[APP–33324] Internal Error – Code 1 is &1, Code 2 is &2

Cause:

Bad return code from tree walker while attempting to go from node to adjacent node. Code 1 is the

return code.

Action:

Please refer to your local support representative.

[APP–33330] Internal Error – Code 1 is &1

Cause:

A node was found in the Unflattening table, but the action associated with it indicated that this node

type should not be encountered at this time. Code 1 contains the node type.

Action:

Please refer to your local support representative.

[APP–33331] Internal Error – Code 1 is &1

Cause:

A bad return code was received from the quote stripping function. Code 1 contains the return code

received.

Action:

Please refer to your local support representative.

[APP–33332] Internal Error – Code 1 is &1

Cause:

A bad return code was received from the utility function which performs a normal format on a

node’s data. Code 1 contains the return code.

Action:

Please refer to your local support representative.

[APP–33333] Internal Error – Code 1 is &1

Cause:

The unflattening table entry for this node contained an unrecognized formatting action. Code 1

contains the action which caused the error.

Action:

Please refer to your local support representative.

[APP–33335] Internal Error – Code 1 is &1

Cause:

Bad return code from tree walker attempting to move between two nodes. Code 1 is the return

code.

Action:

Please refer to your local support representative.

[APP–33338] Internal Error – Code 1 is &1

Cause:

An internal error occurred in the character handling functions. Code &1 is an identifier of the point

in the code where the error was detected.

Action:

Please refer to your local support representative.

[APP–33340] Internal Error:

Cause:

An attempt was made to delete a symbol from the symbol list that did not exist ie it was a null

pointer.

Action:

Please refer to your local support representative.

[APP–33342] Internal Error:

Cause:

An attempt was made to set the branch details for an IF statement but the current symbol list was

NULL (empty).

Action:

Please refer to your local support representative.

[APP–33343] Internal Error:

Cause:

No IF symbol could be found when searching for one while setting the branch of an IF symbol.

This should not be possible, because if there was no IF symbol the search would not be performed in

the first place.

Action:

Please refer to your local support representative.

[APP–33344] Internal Error: &1

Cause:

An unknown branch type was encountered when attempting to set the IF symbol branch. The code

that was tried for the branch type is given.

Action:

Please refer to your local support representative.

[APP–33345] Internal Error:

Cause:

The symbol list pointer did not point to an IF symbol but should have done as an if branch is current

being processed.

Action:

Please refer to your local support representative.

[APP–33346] Internal Error:

Cause:

The symbol list was empty attempting to process IF branches.

Action:

Please refer to your local support representative.

[APP–33347] Internal Error:

Cause:

NULL symbol found when IF symbol expected.

Action:

Please refer to your local support representative.

[APP–33349] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

A variable name of unknown data type was requested. Code 1 is the item name, code 2 is the

variable type and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33350] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

A host variable was requested for an unknown data usage. Code 1 is the item name, code 2 is the

variable usage and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33351] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

The function ffgnns called by the tree walker has been passed a node type which the generator does

no know about. Code 1 is the visit or leave flag, code 2 is the node id and code 4 is the node type.

Action:

Please refer to your local support representative.

[APP–33352] Internal Error: Code 1=&1, Code 4=&4

Cause:

The visit_or_leave flag passed into the language strategy function given is not a valid operation.

Code 1 is the visit or leave flag and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33353] Internal Error: Code 4=&4

Cause:

A stack pop was attempted from the function given when the stack was empty. Code 4 is the

function number.

Action:

Please refer to your local support representative.

[APP–33354] Internal Error: Code 1=&1

Cause:

The stack was not empty after supposed successful execution of all previous elements, meaning

some text was not written. Code 1 is the stack text.

Action:

Please refer to your local support representative.

[APP–33355] Internal Error: Code 1=&1, Code 4=&4

Cause:

An append to stack text was made when the stack was empty. A push must be done before a stack

append can be done. Code 1 is the text and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33356] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

An attempt was made to pop the text of an empty stack. The parameter number, parameter

delimiter and calling function are given. Code 1 is the parameter number, code 2 is the parameter

delimiter and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33357] Internal Error: Code 1=&1, Code 2=&2, Code 3=&3, Code 4=&4

Cause:

The parameter number requested to be returned from the stack was not present or the delimiter

specified was not that used when the parameters were put onto the stack. Code 1 is the parameter

number, code 2 is the parameter delimiter, code 3 is the stack text and code 4 is the function

number.

Action:

Please refer to your local support representative.

[APP–33358] Internal Error: Code 4=&4

Cause:

When attempting to count the parameters on the stack, the stack was empty. Code 4 is the function

number.

Action:

Please refer to your local support representative.

[APP–33359] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

No parameters were found on the stack. Code 1 is the parameter delimiter, code 2 is the stack text

and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33360] Internal Error: Code 1=&1, Code 4=&4

Cause:

A request for a temporary variable causes the maximum allowed number of temporary variables to

be exceeded. Code 1 is the maximum allowed number of temporary variables and code 4 is the

function number.

Action:

Please refer to your local support representative.

[APP–33361] Internal Error: Code 1=&1, Code 4=&4

Cause:

A temporary variable of unknown type was requested by the calling function. Code 1 is the

requested variable’s type and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33362] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

A zero length string resulted when trying to convert the current node’s line number into text format.

Code 1 is the line number, code 2 is the node id and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33363] Internal Error: Code 1=&1, Code 4=&4

Cause:

The text pointer associated with the given node number is NULL. Code 1 is the node id and code 4

is the function number.

Action:

Please refer to your local support representative.

[APP–33364] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

A host variable of unknown type was requested based on the name given. Code 1 is the variable

type, code 2 is the variable name and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33365] Internal Error: Code 1=&1, Code 2=&2, Code 4=&4

Cause:

The maximum number of host variables allowed has been exceeded. Code 1 is the maximum

number of host variables, code 2 is the name of the variable and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33368] Verified formula is too long. Max len=&1, Current len=&2

Cause:

The code generated from your formula has exceeded the maximum size allowed.

Action:

Please reduce the size of your formula.

[APP–33370] Internal Error: Code 1=&1, Code 4=&4

Cause:

The number passed into ffguit was not properly converted into a string. The string length of the

result was zero. Code 1 is the number and code 4 is the function number.

Action:

Please refer to your local support representative.

[APP–33401] Unable to allocate memory

Cause:

Insufficient memory for FastFormula parser.

Action:

Please refer to your system administrator.

[APP–33402] Unable to allocate memory: Code 1 &1 Code 2 &2

Cause:

Insufficient memory for FastFormula parser. Code 1 is the return code (FFSTR_XXX) from the tree

function. Code 2 is the point at which the error was encountered.

Action:

Please refer to your system administrator.

[APP–33403] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory for allocating bind descriptor.

Action:

Please refer to your system administrator.

[APP–33404] Unable to allocate memory: Code 1 &1 Code 2 &2

Cause:

Insufficient memory during execution of a formula.

Action:

Please refer to your system administrator.

[APP–33405] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory during testing phase.

Action:

Please refer to your system administrator.

[APP–33409] Unable to allocate memory

Cause:

Insufficient memory

Action:

Please refer to your system administrator.

[APP–33410] Unable to allocate memory

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33411] Unable to allocate memory

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33412] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33413] Unable to allocate memory for SQLDA size &1 (&2)

Cause:

A SQLDA could not be allocated due to insufficient memory.

Action:

Please refer to your system administrator.

[APP–33414] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33415] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 3 &3 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33416] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 3 &3 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33419] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33420] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33421] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33422] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33423] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33424] Unable to allocate memory: Code 1 &1 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33425] Unable to allocate memory: Code 1 &1 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33426] Unable to allocate memory: Code 1 &1 Code 2 &2 Code 3 &3 Code 4 &4

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33427] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33431] Unable to allocate memory

Cause:

There is too much text in the QuickPaint report that has been painted. There is not enough available

memory to hold it all.

Action:

Reduce the size of your QuickPaint report.

[APP–33432] Unable to allocate memory

Cause:

The QuickPaint report is converted into a formula. The text of the formula that is generated is held

in memory while it is being created, but ran out of memory.

Action:

Please reduce the size of your QuickPaint report.

[APP–33433] Unable to allocate memory: Code 1 &1

Cause:

The QuickPaint report is converted into a formula. The text of the formula that is generated is held

in memory while it is being created, but ran out of memory.

Action:

Please refer to your system administrator.

[APP–33434] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33435] Unable to allocate memory

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33438] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33439] Unable to allocate memory: Code 1 &1 Code 2 &2

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33440] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33441] Unable to allocate memory

Cause:

QuickPaint attempts to build an internal list of Database Items (which it use to validate items named

in a QuickPaint report). It was unable to find enough memory to build this list.

Action:

Please refer to your system administrator.

[APP–33442] Unable to allocate memory

Cause:

QuickPaint attempts to build an internal list of Database Items (which it use to validate items named

in a QuickPaint report). It was unable to find enough memory to build this list.

Action:

Please refer to your system administrator.

[APP–33443] Unable to allocate memory

Cause:

QuickPaint failed to find memory for the lexical analyzer input buffer.

Action:

Please refer to your system administrator.

[APP–33444] Unable to allocate memory

Cause:

QuickPaint failed to find memory to store the QuickPaint report.

Action:

Please refer to your system administrator.

[APP–33445] Unable to allocate memory

Cause:

QuickPaint failed to find memory for the to store the formula text associated with the QuickPaint

report.

Action:

Please refer to your system administrator.

[APP–33446] Unable to allocate memory: Code 1 &1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33447] Unable to allocate memory: Code 1 &1 Code 2 &2

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33448] Unable to allocate memory: Code 1=&1

Cause:

Insufficient memory.

Action:

Please refer to your system administrator.

[APP–33449] Internal Error: &1, &2

Cause:

An internal error has occurred allocating memory.

Action:

Please refer to your system administrator or local support representative.

[APP–33502] Oracle Error ORA&0 occurred while reading FF_GLOBALS (stage &1)

Cause:

Error occurred during Global Table Build module

Action:

Please refer to your system administrator.

[APP–33504] Oracle error ORA&0 occurred at the &1 stage

Cause:

An Oracle error occurred parsing or executing the PL/SQL for the formula.

Action:

Please refer to your system administrator.

[APP–33505] Oracle error ORA&0 occurred while reading FDI_USAGES (&1)

Cause:

An Oracle error occurred accessing the FF_FDI_USAGES table.

Action:

Please refer to your system administrator.

[APP–33508] Oracle error &0 performing fetch: Code 1 = &1: Item is &3

Cause:

An Oracle error occurred in the function fftbfc().

Action:

Please refer to your system administrator.

[APP–33509] Oracle warning : character data truncated (&1)

Cause:

A character string was truncated when fetched from the database.

Action:

Please refer to your system administrator.

[APP–33510] Oracle warning : rollback occurred (&1)

Cause:

An unexpected rollback has occurred.

Action:

Please refer to your system administrator.

[APP–33511] Oracle warning : data not query–consistent (&1)

Cause:

The current data is no longer read–consistent.

Action:

Please refer to your system administrator.

[APP–33512] Oracle error ORA&0 occurred (stage &1, length=&3)

Cause:

An Oracle error occurred in the long field functions.

Action:

Please refer to your system administrator.

[APP–33513] Error ORA&0 closing cursor for &1

Cause:

An Oracle error occurred while closing a cursor.

Action:

Please refer to your system administrator.

[APP–33514] Oracle error &0 while accessing FF_GLOBALS table for &1

Cause:

An Oracle error occurred while accessing the FF_GLOBALS table.

Action:

Please refer to your system administrator.

[APP–33515] ORA&0 occurred while accessing FF_DATABASE_ITEMS for &1

Cause:

An Oracle error occurred while accessing the FF_DATABASE_ITEMS table.

Action:

Please refer to your system administrator.

[APP–33518] Oracle Warning Occurred (&1:&2)

Cause:

One of Oracle’s warning flags was set (sqlca.sqlwarn). Use the Pro*C guide to determine the

meaning of each flag. The first parameter in brackets in the error message shows the warning flags.

The second shows the direction (dm = database –> memory, md = memory –> database)

Action:

Please refer to your system administrator.

[APP–33519] Name &1 : &2

Cause:

The named pl/sql could not be parsed. This is normally due to (a) a table or column, referred to by

SQL in the Application Dictionary, no longer exists or has been renamed, or (b) invalid SQL has

been entered into the Application Dictionary, or (c) the formula is so big that it has generated more

pl/sql than can be handled by the pl/sql parser.

Action:

Please refer to your system administrator.

[APP–33520] ORA&0 occurred while parsing SQL

Cause:

An Oracle error occurred in the long field functions.

Action:

Please refer to your system administrator.

[APP–33521] ORA&0 occurred while parsing SQL

Cause:

An Oracle error occurred in the long field functions.

Action:

Please refer to your system administrator.

[APP–33522] Oracle error ORA&0 occurred (stage &1, length=&3)

Cause:

An Oracle error occurred in the long field functions.

Action:

Please refer to your system administrator.

[APP–33523] Oracle Error &0 verifying &1. &2

Cause:

An Oracle error occurred in the function ffscmp().

Action:

Please refer to your system administrator.

[APP–33530] Oracle error ORA&0 deleting from FF_FORMULAS (FORMULA_ID=&1)

Cause:

An Oracle error has occurred deleting from the FF_FORMULAS table.

Action:

Please refer to your system administrator.

[APP–33531] Oracle error ORA&0 inserting into FF_FORMULAS

Cause:

QuickPaint converts its text into a formula, which it then attempts to write into the FF_FORMULAS

table. In this case, an Oracle error occurred writing to the table.

Action:

Please refer to your system administrator.

[APP–33532] Oracle error ORA&0 fetching FF_FORMULAS_S.NEXTVAL

Cause:

An Oracle error occurred accessing the sequence FF_FORMULAS_S.

Action:

Please refer to your system administrator.

[APP–33534] Oracle error ORA&0 deleting from FF_COMPILED_INFO (FORMULA_ID=&1)

Cause:

An Oracle error has occurred deleting from the FF_COMPILED_INFO table.

Action:

Please refer to your system administrator.

[APP–33535] Oracle error ORA&0 deleting from FF_FDI_USAGES (FORMULA_ID=&1)

Cause:

An Oracle error occurred deleting from the FF_FDI_USAGES table.

Action:

Please refer to your system administrator.

[APP–33536] Oracle error ORA&0 reading FF_FORMULAS (typeid=&1,name=&3)

Cause:

An Oracle error occurred accessing the FF_FORMULAS table.

Action:

Please refer to your system administrator.

[APP–33537] Oracle error ORA&0 updating FF_QP_REPORTS (qp_report_id=&1)

Cause:

An Oracle error occurred accessing the FF_QP_REPORTS table.

Action:

Please refer to your system administrator.

[APP–33538] Internal Error: Code 1=&1: ORA&0

Cause:

An Oracle error occurred in the function ffgadu().

Action:

Please refer to your system administrator.

[APP–33540] &2

Cause:

An unexpected Oracle error has occurred.

Action:

Please refer to your system administrator.

[APP–33564] Oracle error ORA&0 occurred whilst accessing FF_FORMULAS table

Cause:

An Oracle error occurred accessing the FF_FORMULAS table.

Action:

Please refer to your system administrator.

[APP–33569] Oracle error ORA&0 accessing FF_UDFS table

Cause:

An Oracle error occurred accessing the FF_UDFS table.

Action:

Please refer to your system administrator.

[APP–33570] Oracle error ORA&0 occurred whilst accessing FF_UDFS

Cause:

An Oracle error occurred accessing the tables FF_FTYPE_CONTEXT_USAGES,

FF_UDF_CONTEXT_USAGES and FF_UDFS.

Action:

Please refer to your system administrator.

[APP–33572] Oracle error ORA&0 occurred while accessing FF_UDF_PARAMETERS

Cause:

An oracle error occurred while accessing the FF_UDF_PARAMETERS table.

Action:

Please refer to your system administrator.

[APP–33574] Oracle error ORA&0 opening cursor on FF_DATABASE_ITEMS

Cause:

An Oracle error occurred accessing the FF_DATABASE_ITEMS table.

Action:

Please refer to your system administrator.

[APP–33575] Oracle error ORA&d fetching from FF_DATABASE_ITEMS

Cause:

An Oracle error occurred accessing the FF_DATABASE_ITEMS table.

Action:

Please refer to your system administrator.

[APP–33576] Internal Error: ORA &0

Cause:

An Oracle error occurred inserting into the FF_FDI_USAGES table.

Action:

Please refer to your system administrator.

[APP–33578] Internal error: &1, &3, &0, &2

Cause:

An oracle error occurred in &1 accessing &3.

Action:

Please refer to your system administrator.

[APP–33580] &1: &2

Cause:

An oracle occurred in &1

Action:

Please refer to your system administrator or local support representative.

[APP–33581] Internal Error: ORA &0

Cause: An Oracle error occurred selecting from the FF_CONTEXTS table.

Action: Please refer to your system administrator.

[APP–33602] Output count (=&2) invalid for formula &1

Cause:

The ’FFARG’ structure (created by ffxcrs()) has an ’ffargocn’ which is greater than zero (the actual

value is given in the error message). However, ’ffargodt’ which points to the descriptions of each of

the outputs is NULL.

Action:

Please refer to your local support representative.

[APP–33603] Formula &1 has surplus input DATAELEMENTs (&2)

Cause:

The input or uidcol dataelement structure passed into ffxers() contains references that are

unnecessary for the current formula. These surplus inputs are normally ignored, but if the

in_surplus element of the FF_OPTIONS structure is set to 1, these extra inputs are rejected. The

name of the surplus input is given in brackets at the end of the error message.

Action:

Please refer to your local support representative.

[APP–33604] Incorrect datatype (’&3’:’&4’) for &2 in formula &1

Cause:

The data type of the variable declared using ffxdrs differs from the data type for the variable as used

in the formula.

Action:

Please refer to your local support representative.

[APP–33605] Bad data type (’&3’) found in input/uidcol (&2) for formula (&1)

Cause:

Permissible data type are ’N’, ’T’, and ’D’ (Numeric, Text, Date). This was picked up when

examining the DATALIST passed into ffxers()

Action:

This is a problem with the application calling FastFormula. If running an Oracle application you

should refer to your local support representative.

[APP–33606] Formula &1 has duplicate DATAELEMENTS for elements &2

Cause:

One of the DATAELEMENT structures in the DATALIST for INPUT or UID has the same name as

one of the other structures.

Action:

Please refer to your local support representative.

[APP–33607] FFARG structure has ffarguct=&2 but ffargudt=NULL (Formula &1)

Cause:

The FFARG structure has an element ’ffarguct’ that indicates the number of UIDs referenced by the

formula. However ’ffargudt’ (which points to an array of structures that describe the UIDs) is

NULL. It should be either (1) ffarguct=0, ffargudt=NULL, or (2) ffarguct>0 and ffargudt !=

NULL

Action:

Please refer to your local customer representative.

[APP–33608] FF_ARGS has icount=&2 but idata=NULL (formula &1)

Cause:

The FFARG structure indicates one or more INPUT variables, but the INPUT data area is NULL.

Action:

Please refer to your local support representative.

[APP–33609] Output ’&2’ unknown in formula &1

Cause:

The OUTPUT structure has an element which names which is not part of the formula.

Action:

Please refer to your local support representative.

[APP–33610] Formula &1 (element ’&2’) has mismatched data type (’&3’:’&4’)

Cause:

The data type given in the output element named in the error message does not match the type that

the formula verifier believes the variable is defined as. All formula variables are numeric, unless

the (TEXT) or (DATE) overrides are used. The 2 letters at the end of the error message (’x’:’y’)

refer to the type named by the application programmer, and the type that the formula verifier

detected (N=numeric, T=Text, D=Date).

Action:

Please refer to your local support representative.

[APP–33611] Output element (’&2’) is not an output type (’&3’) in formula &1

Cause:

Output element &2 is not an output type in the formula The formula verifier has recorded the output

element as having a type other than ’O’ (Output only), or ’B’ (Both output & input). If the type is

’I’ then this element should appear in the INPUT data list instead. Similarly, if the type is ’U’, the

element should be in the UID data list, not the OUTPUT data list.

Action:

Please refer to your local support representative.

[APP–33612] Output element ’&2’ has bad data type ’&3’ in formula &1

Cause:

Each DATANODE structure in the OUTPUT list, has a data type which must be one of ’T’ (Text),

’D’ (Date), ’R’ (Real [double–precision] number), ’A’ (Ascii number), ’O’ (Oracle internal format

number)

Action:

Please refer to your local support representative.

[APP–33613] Output data list has NULL dldata, but dlcount = &2 (formula &1)

Cause:

The OUTPUT data list provided can only have a NULL data pointer if it has a data element count of

zero.

Action:

Please refer to your local support representative.

[APP–33615] Uidcol (&2) missing from formula &1

Cause:

The uidcol DATALIST pointed to by the FFARG parameter passed to ffxers, does not contain a

DATAELEMENT describing this missing UID. The formula uses a UID, so ffxdrs() should be

called to set up the address and other details of this UID.

Action:

Please refer to your local support representative.

[APP–33624] ffxdrs: null data pointer for formula &1 (var &2)

Cause:

An NULL pointer was passed to ffxdrs() as a data area for a formula value.

Action:

Please refer to your local support representative.

[APP–33625] Too few parameters to ffxxit (&1 supplied instead of &2)

Cause:

Insufficient parameters passed to execute formula user exit.

Action:

Please refer to your local support representative.

[APP–33626] Element &2 should be a UIDCOL (formula &1)

Cause:

Unexpected type found where UIDCOL type expected.

Action:

Please refer to your local support representative.

[APP–33627] Element &2 should be INPUT type (formula &1)

Cause:

Unexpected type found where INPUT type expected.

Action:

Please refer to your local support representative.

[APP–33628] Datatype missing from ”&1” line (trigger for &2)

Cause:

The formula has been invoked from an Application Foundation #USR trigger step. The syntax of

the #USR trigger step is wrong for one of the lines, either INPUT=, UIDCOL=, or OUTPUT= as

indicated in the message. The correct syntax is e.g.

HOURS_WORKED(N)=:BLOCK1.HRS_WORK\n

Action:

Please refer to your local support representative.

[APP–33629] Unexpected end of ”&1” line (trigger for &2)

Cause:

A formula was invoked via Application Foundation. It was invoked using a #USR trigger step. One

of the INPUT=, or UIDCOL=, or OUTPUT= lines appears to have been truncated.

Action:

Please refer to your local support representative.

[APP–33630] No ’)’ found after data type in ”&1” line (trigger for &2)

Cause:

The data type letter (N,T or D) should be enclosed in brackets e.g.

HOURS_WORKED(N)=:BLOCK1.HRS_WORK\n

Action:

Please refer to your local support representative.

[APP–33631] Invalid data type ”&1” in &2 line (trigger for &3)

Cause:

Only N, T, or D are allowed for the data type, depending on whether the data is of type Numeric,

Text or Date.

Action:

Please refer to your local support representative.

[APP–33632] Missing ’=’ before value in &1 line (trigger for &2)

Cause:

The data type part e.g. (N) should be separated from the value part by an equal (=) sign. No white

space is permitted before the equal sign.

Action:

Please refer to your local support representative.

[APP–33633] ’)’ found before ’(’ in ”&1” line (trigger for &2)

Cause:

The data type, which is enclosed in brackets, was found to have its ’(’ bracket missing. E.g.

HOURS(N)=:B1.HOURS\n would generate this error condition.

Action:

Please refer to your local support representative.

[APP–33634] Data type missing from ”&1” line (trigger for &2)

Cause:

Between the variable name, and it’s value, there should be a data type enclosed in brackets. E.g.

SALARY(N)=1500 is correct, but SALARY=1500 is incorrect and would cause this error condition.

Action:

Please refer to your local support representative.

[APP–33640] Internal Error: &1

Cause:

Incorrect number of parameters passed to test formula user exit.

Action:

Please refer to your local support representative.

[APP–33642] Internal Error: &0

Cause:

An Oracle error occurred accessing the FF_HARNESS table.

Action:

Please refer to your system administrator.

[APP–33644] Internal Error: &1

Cause:

An unknown data type was found in the test formula user exit.

Action:

Please refer to your local support representative.

[APP–33646] Internal Error &0. &2

Cause:

An Oracle error occurred in the test formula user exit.

Action:

Please refer to your local support representative.

[APP–33647] Internal Error: &1

Cause:

The number of parameters passed to user exit ffuevf was incorrect. The actual number of

parameters passed is given.

Action:

Please refer to your local support representative.

[APP–33648] Internal error

Cause:

Number of memory allocations does not match number of free operations.

Action:

Please refer to your local support representative.

[APP–33651] Number couldn’t be converted (&2 in formula &1)

Cause:

A number (FF_NUMASC) was passed into ffxdrs(). At runtime, this number is converted to

Oracle’s internal number format, but the conversion failed. Probable cause is passing a double to

ffxdrs(), but using the FF_NUMASC parameter instead of FF_NUMREAL.

Action:

Please refer to your local support representative.

[APP–33654] ffxchr() invoked at the wrong time

Cause:

ffxchr() should be called just BEFORE ffxdei(). ffxfrs() will not affect the statistics. The statistics

are reset to zero by ffxdei().

Action:

Please refer to your local support representative.

[APP–33655] Null address passed to ffxchr() at parameter 1

Cause:

The address of an integer variable should be given to ffxchr. E.g. return_code = ffxchr (&ratio,

&number_of_caches); Leaving out the ’&’ before ’ratio’ will often cause this error.

Action:

Please refer to your local support representative.

[APP–33657] Null parameter 2 passed to ffxchr()

Cause:

ffxchr() expects 2 parameters, both of which are pointers to integers. E.g. int ratio=0,

cache_size=0; return_code = ffxchr (&ratio, &cache_size);

Action:

Please refer to your local support representative.

[APP–33660] ffsdcf: formula id not present

Cause:

Formula identifier not provided by caller.

Action:

Please refer to your local support representative.

[APP–33661] ffsdcf: Session effective date was not found in FND_SESSIONS table

Cause:

Missing session date in FND_SESSIONS table.

Action:

Please refer to your local support representative.

[APP–33662] ffsdcf: formula could not be found for given formula ids

Cause:

The formula could not be found.

Action:

Please refer to your local support representative.

[APP–33663] ffsdcf: Invalid DateTrack mode

Cause:

An invalid DateTrack mode was detected in ffsdcf(),

Action:

Please refer to your local support representative.

[APP–33664] ffsdcf: stage &1 ORA&0

Cause:

An Oracle error occurred in ffsdcf.

Action:

Please refer to your system administrator.

[APP–33665] Internal Error: &1

Cause:

The number of parameters passed to the Delete Compiled Formula user exit was incorrect.

Action:

Please refer to your local support representative.

[APP–33666] Internal Error

Cause:

The DateTrack mode was not passed into the delete compiled formula user exit. DateTrack mode is

a mandatory parameter.

Action:

Please refer to your local support representative.

[APP–33667] ffxcrs: parameter 1 has NULL address

Cause:

The first parameter of the ffxcrs() call should be an address E.g. FF_ARGS *F; ... F = (FF_ARGS

*) NULL; rc = ffxcrs (&F, ...);

Action:

Please refer to your local support representative.

[APP–33668] ffxcrs: parameter 1 has non–null pointer

Cause:

The first parameter of the ffxcrs() call should be the address of a pointer, and the pointer should be

initialized to NULL. Failure to initialize the pointer to NULL (as in the example below), will cause

this error message. FFARG *F; ... F = (FFARG *) NULL; /* Don’t forget the initialization */ rc =

ffxcrs (&F, ...);

Action:

Please refer to your local support representative.

[APP–33669] Internal Error

Cause:

An error occurred while reading the profile for session effective date.

Action:

Please refer to your local support representative.

[APP–33671] Output (&1) has wrong type (’&2’) in formula &3

Cause:

ffxdrs() has been called for an item and ffxdrs() was told that this item is an OUTPUT. However, its

usage in the actual formula text indicates that it has some other use (e.g. INPUT, UIDCOL,

GLOBAL).

Action:

Alter the parameter passed to ffxdrs (FF_OUTPUT) to the correct type (FF_INPUT/FF_UIDCOL).

Please refer to your local support representative.

[APP–33672] Missing output ’&2’ in formula &1

Cause:

When a formula returns an input (e.g. ”inputs are x ... return x”) then separate input and output

datanodes are required. This means that there must be two calls to ffxdrs (1. ffxdrs

(...FF_INPUT...) and 2. ffxdrs (...FF_OUTPUT...)). This error arises when ffxdrs is called to set up

the INPUT half, but not the OUTPUT half.

Action:

Call ffxdrs (...FF_OUTPUT...). Please refer to your local support representative.

[APP–33673] Duplicate declaration of ’&2’ in formula &1

Cause:

This error is concerned with variables that are both INPUT and OUTPUT (e.g. ”INPUTS ARE

FRED ... FRED=FRED + 1... RETURN FRED”) If ffxdrs(...FF_INPUT...) is called twice, instead

of once for input and once for output, then this error arises.

Action:

Prevent ffxdrs (...FF_INPUT...) being called more than once for the named input variable. Please

refer to your local support representative.

[APP–33677] Item &2 has wrong usage (should be ’&3’) in formula &1

Cause:

The call to ffxdrs() declares the wrong usage for a formula item. For example, if a formula has an

input called ABC (”INPUTS ARE ABC”), but the ffxdrs() call says that ABC is something other

than an input (e.g. ffxdrs (...”ABC”....FF_UIDCOL...)) then this error arises. The actual usage

(’&3’) is given in the error text, and should be one of the following : ’I’ (Input), ’U’ (Uidcol), ’O’

(Output), ’G’ (Global), ’B’ (Both Input and Output), ’D’ (Database Item).

Action:

Please refer to your local support representative.

[APP–33678] Empty name encountered in formula &1

Cause:

This error occurs if ffxcrs() is called to set up space for inputs, UIDs and outputs, but ffxdrs() is not

called to fill in the names. E.g. ffxcrs (..., 1, 2, 5, ...) says that there is one UID, 2 inputs and 5

outputs. This totals 8 elements, so ffxdrs() must be called 8 times, after ffxcrs() but before ffxers().

Action:

Please refer to your local support representative.

[APP–33681] No such formula (&1)

Cause:

A compiled version of this formula cannot be found.

Action:

Check that the formula has been compiled before attempting to run it.

[APP–33682] No such formula (&1)

Cause:

A compiled version of this formula cannot be found.

Action:

Check that the formula has been compiled before attempting to run it.

[APP–33683] FastFormula execution engine not initialized.

Cause:

An attempt was made to use FastFormula before it had been properly initialized.

Action:

Call ffxcrs() before any other FastFormula function. ffx...() was called before ffxcrs() or ffxini()

[APP–33684] Validation start date or end date missing from ffsdcf() call.

Cause:

Either NULL or empty string were passed for validation start date or validation end date.

Action:

Ensure that the validation start dates are passed properly and are not NULL.

[APP–33687] Internal error

Cause:

The ’context_level’ parameter passed to ffadnc was NULL.

Action:

Please refer to your local support representative.

[APP–33688] Internal Error: &1

Cause:

The user exit CONTEXT_LEVEL was not passed a valid field name when called from a form.

Action:

Please refer to your local support representative.

Cause:

An internal error has occurred because an item name was missing where one was expected.

Action:

Please refer to your local support representative.

[APP–33694] Internal Error (&1,&2)

Cause:

The pl/sql described contains too many bind variables (&1) to fit into the SQLDA (&2)

Action:

Please refer to your local support representative.

[APP–33695] FastFormula execution engine not initialized.

Cause: An attempt was made to use FastFormula before it had properly been initialized.

Action: Call init_formula before calling run_formula.

[APP–33701] Memory error: &1

Cause:

Error allocating memory.

Action:

Please refer to your system administrator.

[APP–33702] File error: Failed to open file &1

Cause:

The named file could not be opened.

Action:

Please refer to your system administrator.

[APP–33703] File error: Failed to read from file &1

Cause:

An error occurred reading from named file.

Action:

Please refer to your system administrator.

[APP–33704] Oracle error: &0 at stage &1

This error message is generated whenever a PRO*C operation fails. This is typically either a failure

to read from the database or open a cursor or fetch from an open cursor. The position in the source

where this occurs is indicated by variable 1. Note that rows not found is a case which is handled

separately.

[APP–33705] Database error: No rows retrieved from table &1

This error message is generated whenever no rows are retrieved from a database table and some

rows are expected.

[APP–33706] File error: File &1 contains no test run names

This error message is generated when the file specifying test runs to be performed contains no test

run names. Note that the file need not necessarily be empty; it may simply contain comments ie.

lines whose first character is ’#’.

[APP–33707] Test run &1 does not exist or has no test steps

This error message is generated whenever the PRO*C query to retrieve the test step details of the

specified test run returns no rows. If the test runs were specified by file, then this could be due to

there being no test run of that name on the database, or the test run may be empty. If the test runs

are taken by default from the database, only the latter can be the cause.

[APP–33708] Error in reading system time for timer &1

This message is generated whenever the call to time(), within a start or stop timer test step fails.

[APP–33709] Attempted to start timer &1 which is still in use

This message is generated when an attempt is made to start a timer which has already been started

and is still going.

[APP–33710] Attempted to stop timer &1 which is not in use

This message is generated when an attempt is made to stop a timer which has not been started.

[APP–33711] Negative elapse time returned for timer &1

This message is generated when the elapse time returned for a timer pair is negative. This could be

caused by the system date being prior to 01/01/70, since the value returned by system call time() is

the number of seconds since 01/01/70.

[APP–33712] Load long data – filename expected in file &1

This message is generated from the load long test step. A load long command file is specified,

which should contain pairs of SQL command strings and the filenames of their corresponding load

long data. If no corresponding filename is found for a SQL command, then this message is

generated.

[APP–33713] Null &2 specified in load long file &1

Cause:

This message is generated whenever a null SQL command string or loadlong data filename is

specified in a load long file, as part of a load long test step.

Action:

Check test step or load long file.

[APP–33714] Oracle error &0 occurred when running SQL command &1 in file &3

This error message is generated from a RUN_SQL test step. For such a test step, a file containing

any number of SQL command scripts is run against the database. If failure of the test step is not to

be ignored then this message is produced, giving sufficient details to identify which SQL string

failed.

[APP–33715] End–of–file encountered when reading SQL command in file &1

This message is generated from a RUN_SQL test step. It is produced when eof is encountered

before the ’/’ terminator of the current SQL command string being read from the file identified by

&1.

[APP–33716] Regression test aborted: results of test step unexpected

When the abort option is set, if the actual results of a test step do not match the expected ones, then

the regression test harness aborts, with this message. Note that this error message is not generated

by any internal test harness error.

[APP–33717] Invalid usage &1 for data element encountered

A data element may be used as input, output, both or uid (I, O, B or U) If the usage of the element

as retrieved is not on this set, then this error message is generated.

[APP–33718] Invalid type &1 encountered for data element

A data element can be of type: ASCII number, Oracle number, real number, date or text (A, O, R, D,

T). If the element type retrieved from the database is not in this set, then this message is generated.

[APP–33719] Oracle error &0 encountered when accessing FF_FORMULA_TYPES table

This error message is generated whenever an error is encountered on accessing the table

FF_FORMULA_TYPES, in order to validate that the application shortname and formula type name

of the test formula to be compiled is already known to the Formula Facility. The most likely error is

that a row is not found ie. there is not an entry in FF_FORMULA_TYPES for the application

shortname, formula type name pair associated with the test formula. If the test formula details are

correct, then the appropriate row can be inserted into FF_FORMULA_TYPES using a RUN_SQL

test step prior to compilation.

[APP–33720] SQL command &2 in file &1 exceeds the maximum length of 512 characters

This error message is generated when a single SQL command (terminated by a ”/” as the first

character on a new line) within a RUN_SQL script file exceeds the maximum length of 512

characters.

[APP–33721] Oracle error &0 occurred when inserting into FND_SESSIONS table.

This error message is generated whenever an Oracle failure occurs on insertion of a row into the

FND_SESSIONS table. This is only attempted by the date–effective version of the regression test

harness.

[APP–33722] Oracle error &0 encountered at stage &1 in compilation test step.

This error message is generated by an Oracle error in the procedure frtlfo(), which is responsible for

loading formula text into FF_FORMULAS and cleaning up FF_FDI_USAGES and

FF_COMPILED_INFO prior to compilation, possibly date–effectively. The stage number indicates

where in the source code, the error occurred.

[APP–33723] Call to ffxgem() failed.

The function ffxgem() is called by frtchr (check test step results) to retrieve the actual Formula

Facility and/or Oracle error message generated when the Boolean result or error code returned by

performing the test step is not as expected. This error is generated when that call fails.

[APP–33724] Error encountered in forming full filename for file &1

This error is generated by the harness utility procedure, frufop(). Using the filename specified from

the command line, and the base pathname derived from environment variables FF_TOP and

FR_TESTDIR, it creates the full pathname using the AF function sficpn(). The failure of this

function results in the above error message; this could be caused by either the base pathname or

filename being null.

[APP–33725] Error encountered in generating base pathname.

This error message is generated when the call to sficpn() in frciap() fails. The likely cause is that

the environment variable FF_TOP is not set up.

[APP–33726] Failed to read system time for run formula timer.

This error message is generated by a run formula test step, when the call to getcpu() fails. This call

is made before and after the execution of the test step, to establish how long it took, but only when

the Time Formula Runs option is on. This option is switched on or off within a test run by the

corresponding test steps. Note that this should not be confused with Stop and Start Timer test steps.

[APP–33727] A negative cpu time was calculated for the formula run.

This error message is generated by a run formula test step, when the Time Run Formula option is

on, and the calculated cpu time for a single run of the formula is negative.

[APP–33751] Internal Error Code 1 &1 Code 2 &2

Cause:

Error found while constructing parse tree. The Code returned was &1, and the point in the YACC

code where the failure was detected was &2.

Action:

Please refer to your local support representative.

[APP–33753] Internal Error – Code 1 is &1

Cause:

The tree walker was invoked with an invalid mode. Code 1 contains the mode.

Action:

Please refer to your local support representative.

[APP–33754] Internal Error

Cause:

The top node in the subtree that the tree walker was invoked on had no children.

Action:

Please refer to your local support representative.

[APP–33755] Internal Error – Code 1 is &1

Cause:

While executing a tree walker function to go to the parent of a node, a bad return code was

received. Code 1 contains the return code.

Action:

Please refer to your local support representative.

[APP–33756] Internal Error

Cause:

While executing a tree walker function to go from a node to it’s parent a bad return code was

received. Code 1 contains the return code.

Action:

Please refer to your local support representative.

[APP–33757] Internal Error – Code 1 is &1

Cause:

While executing a tree walker function to go to the child of a node, a bad return code was received.

Code 1 contains the return code.

Action:

Please refer to your local support representative.

[APP–33758] Internal Error

Cause:

Internal error in tree dumping routine.

Action:

Please refer to your local support representative.

[APP–33759] Illegal data type combination in line &1: &2 not allowed.

Cause:

While performing unflattening, an invalid combination of node type and data type was encountered,

that has no valid flattened node type.

Action:

Please refer to your local support representative.

[APP–33760] Internal Error: Code 1 = &1

Cause:

Internal error attempting to delete a Database Item Group from a node where it did not exist.

Action:

Please refer to your local support representative.

[APP–33761] Internal Error: Code 1 is &1

Cause:

Internal error searching for named database item in the DB ELEMENT list in memory.

Action:

Please refer to your local support representative.

[APP–33762] Internal Error

Cause:

The function fftbfp() which prints the function table details was passed a NULL function table

pointer.

Action:

Please refer to your local support representative.

[APP–33763] Internal Error

Cause:

The definition text for a UDF could not be found.

Action:

Please refer to your local support representative.

[APP–33764] Internal Error

Cause:

The function add_parm() was passed a parameter list pointer that was NULL.

Action:

Please refer to your local support representative.

[APP–33765] Internal Error: Code 1 &1

Cause:

The hash table pointer passed into the function was NULL.

Action:

Please refer to your local support representative.

[APP–33766] Internal Error: Code 1 &1

Cause:

The symbol descriptor was NULL. The function being called is given as Code 1

Action:

Please refer to your local support representative.

[APP–33768] Internal Error: Code 1 &1

Cause:

An unexpected node type was encountered in fftcmn().

Action:

Please refer to your local support representative.

[APP–33771] Internal Error: Code 1=&1 Code 2=&2

Cause:

An internal error occurred in the type tester in fftctm(). The function was passed a null parameter

pointer.

Action:

Please refer to your local support representative.

[APP–33781] Internal Error: &1

Cause:

A null symbol name was passed to the symbol table utility functions.

Action:

Please refer to your local support representative.

[APP–33782] Internal Error: &1 &2

Cause:

A symbol that should have been found in the symbol table could not be found

Action:

Please refer to your local support representative.

[APP–33783] Internal Error: &1

Cause:

A generated name was empty where one was expected.

Action:

Please refer to your local support representative.

[APP–33785] Internal Error: Bad Route Text length (&3) [&2, &1]

Cause:

The route text fetched for the item and route ID shown was either empty or too long. The actual

length is shown.

Action:

Please contact your local support representative.

[APP–33786] Internal Error: &1

Cause:

A bad control code was passed to fftbfa.

Action:

Please refer to your local support representative.

[APP–33787] Internal Error: &1 &2

Cause:

A null pointer was detected internally.

Action:

Please refer to your local support representative.

[APP–33788] Internal Error: &1

Cause:

A SQL element could not be found for the route id shown.

Action:

Please contact your local support representative.

[APP–33789] An alias symbol &1 has been found where an alias is not allowed

Cause:

An alias symbol has been found. The most common cause is an alias of a function which is the

same as the function name.

Action:

If the name corresponds to a function, check whether its alias has the same name. If it does, rename

the alias to be different. If the name is not a function, please contact your local support

representative.

[APP–33790] Procedure calls (&1) are not supported by FastFormula

Cause:

A procedure has been detected whilst loading function definitions from the FF_FUNCTIONS table

(procedures have null data types). Procedures are not supported by FastFormula in this release.

Action:

If the procedure has been defined as part of user data, please remove the procedure or replace it with

a function. If the procedure has not been defined as part of user data, please refer to your local

support representative.

[APP–33791] Formula calls (&1) are not supported by FastFormula

Cause:

A Formula has been detected whilst loading function definitions from the FF_FUNCTIONS table

(procedures have null data types). Called Formulas are not supported by FastFormula in this

release.

Action:

If the Formula has been defined as part of user data, please remove the formula or replace it with a

function. If the Formula has not been defined as part of user data, please refer to your local support

representative.

[APP–33792] Internal Error [&1, &2]

Cause:

An internal error has occurred whilst loading function information. A function has OUT or IN/OUT

parameters which have been specified as Optional or Variable Argument, neither of which is legal.

Action:

Please contact your local support representative.

[APP–33801] Internal Error (&1,&2)

Cause:

The length of the compiled formula was zero, or the buffer pointer was NULL.

Action:

Please refer to your local support representative.

[APP–33802] Internal error (&1,&2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33803] Internal error (&1,&2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33804] Internal error (&1,&2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33805] Internal error (&1,&2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33806] Internal error (&1, &2)

Cause:

The memory version of the FDIU has become out of step with the table FF_FDI_USAGES.

Action:

Please refer to your local support representative.

[APP–33807] Internal error (&1)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33808] Internal error (&1,&2,&3)

Cause:

Invalid parameter value to ffxlfe().

Action:

Please refer to your local support representative.

[APP–33810] Internal error (&1)

Cause:

After doing a DESCRIBE BIND VARIABLES, bdp–>F was negative. A new bind descriptor

was allocated, but the redescribe still thought that the bind descriptor supplied was too small.

Action:

Please refer to your local support representative.

[APP–33812] Internal error (&1,&2)

Cause:

One of the names that appeared in the SQLDA after a describe of the bind variables, has a name

whose length is zero. The first number in brackets after the message is the position in the SQLDA

(starting from zero), and the second number is the total size of SQLDA entries.

Action:

Please refer to your local support representative.

[APP–33813] Internal Error (&1)

Cause:

A variable name appeared in the formula compiled text that was not in the FF_FDI_USAGES table.

The 4 parameters in brackets refer to variable name, SQLDA position, total entries in SQLDA and

formula ID.

Action:

Please refer to your local support representative.

[APP–33815] Internal Error (&1,&2,&3)

Cause:

An error occurred accessing the FF_FDI_USAGES table. A row with an invalid usage was

encountered. The 3 parameters refer to (Formula_id,Item_name,Usage)

Action:

Please refer to your local support representative.

[APP–33816] Internal Error (&1,&2)

Cause:

ffxlge() could not locate the global in the core global table.

Action:

Check that the global variable has not been deleted. If still present, this is an internal error and

should be referred to your local support representative.

[APP–33817] Internal Error (&1)

Cause:

Global table is being searched before it has been built

Action:

Please refer to your local support representative.

[APP–33818] Internal Error (&1)

Cause:

ffxfgv() was invoked with a null parameter for this formula

Action:

Please refer to your local support representative.

[APP–33819] Internal Error (&1,&2)

Cause:

The structure passed into ffxfgv() contains an invalid data type : one of ’N’, ’T’ or ’D’ was

expected.

Action:

Please refer to your local support representative.

[APP–33820] Internal Error (&1,&2)

Cause:

Attempt to allocate &2 bytes is incorrect.

Action:

Please refer to your local support representative.

[APP–33821] Internal Error (&1,&2)

Cause:

ffxsii was called with the wrong usage type. It should be one of FDE_INPUT, FDE_UIDCOL or

FDE_GLOBAL.

Action:

Please refer to your local support representative.

[APP–33822] Internal Error (&1)

Cause:

A null DATAELEMENT pointer was passed in ffxsii().

Action:

Please refer to your local support representative.

[APP–33823] Internal Error (&1,&2,&3)

Cause:

The element does not have an indicator variable associated.

Action:

Please refer to your local support representative.

[APP–33824] Internal Error (&1,&2,&3,&4)

Cause:

An element named in the FDIU does not have a corresponding entry in the SQLDA. Either the

EXEC SQL DESCRIBE BIND VARIABLES part is not picking up all the bind variables, or the

FDIU table contains spurious entries (that unfortunately just happens to be referenced by the user).

Formula Id = &1, Output element name = &2 Position in FDIU table = &3 Value of v_sqlda for this

element in the FDIU = &4

Action:

Please refer to your local support representative.

[APP–33825] Internal Error (&1,&2,&3,&4)

Cause:

The SQLDA’s pointer to the host variable is NULL. &1 = Formula_id &2 = Output element name

&3 = Location in FDIU &4 = Location in SQLDA

Action:

Please refer to your local support representative.

[APP–33826] Internal Error (&1,&2)

Cause:

&1 = Formula Identifier &2 = Current Execution State (ffxces) The execution state should be in

AT_START_STATE but was not.

Action:

Please refer to your local support representative.

[APP–33827] Internal Error (&1,&2)

Cause:

Formula &1, dataelement &2 ffxsii has been called to setup a global, but the FDIU table says that it

is not of type global.

Action:

Please refer to your local support representative.

[APP–33828] Internal Error (&1,&2,&3,&4)

Cause:

&1 = Formula ID &2 = Variable name &3 = Position into FDIU table (array index) &4 = Position

into SQLDA (array index: –1 means entry not in SQLDA) The variable has appeared in the original

formula text and the FDIU, but does not show up as a bind variable in the PL/SQL and so has no

entry in the SQLDA. Since data space is only allocated for those variables that show up in the

SQLDA, the input/uid being presented has nowhere to go.

Action:

Reverify the formula and run again. If the problem persists, refer to your local support

representative.

[APP–33831] Internal Error (&1)

Cause:

Attempt to close a cursor, number &1. The number supplied is out of range.

Action:

Please refer to your local support representative.

[APP–33832] Internal Error (&1, &2)

Cause:

Attempt to declare cursor outside the range available.

Action:

Please refer to your local support representative.

[APP–33833] Internal Error (&1)

Cause:

A formula cache was given to the ffxfes() function to be freed, but either its nxt or prv pointer was

not null. The cache is still linked into a chain.

Action:

Please refer to your local support representative.

[APP–33834] Internal Error (&1,&2)

Cause:

Attempt to use a cursor whose cursor number is out of range.

Action:

Please refer to your local support representative.

[APP–33835] Internal Error (&1, &2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33836] Internal Error (&1, &2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33837] Internal Error (&1, &2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33838] Internal Error

Cause:

A NULL parameter passed into ffxahf()

Action:

Please refer to your local support representative.

[APP–33839] Internal Error (&1)

Cause:

Attempt to add a cache to the free list while it is still connected to surrounding caches.

Action:

Please refer to your local support representative.

[APP–33840] Internal Error (&1)

Cause:

Attempt to add a free cache to the free list, when it is already on the free list.

Action:

Please refer to your local support representative.

[APP–33841] Internal Error (&1)

Cause:

Infinite loop detected in the free list.

Action:

Please refer to your local support representative.

[APP–33842] Internal Error

Cause:

Null cache pointer passed to ffxahm()

Action:

Please refer to your local support representative.

[APP–33843] Internal Error

Cause:

Attempt made to add a cache to the MRU when the cache is already being used.

Action:

Please refer to your local support representative.

[APP–33844] Internal Error

Cause:

MRU cache and Free cache lists start at the same place.

Action:

Please refer to your local support representative.

[APP–33845] Internal Error (&1)

Cause:

A cache has been lost from the MRU and Free lists.

Action:

Please refer to your local support representative.

[APP–33846] Internal Error (&1, &2)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33847] Internal Error

Cause:

Infinite loop detected.

Action:

Please refer to your local support representative.

[APP–33848] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33849] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33850] Internal Error (&1)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33851] Internal Error (&1)

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33852] Internal Error

Cause:

Null pointer passed to ffxffc

Action:

Please refer to your local support representative.

[APP–33853] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33854] Internal Error

Cause:

Either ffx000 or ffx000–>env are missing.

Action:

Please refer to your local support representative.

[APP–33855] Internal Error (&1, &2)

Cause:

ffx000–>dcs reports a different size from ffxdcs()

Action:

Please refer to your local support representative.

[APP–33856] Internal Error

Cause:

Infinite loop in the Free list detected during logging.

Action:

Please refer to your local support representative.

[APP–33857] Internal Error

Cause:

Null pointer passed to ffxucm()

Action:

Please refer to your local support representative.

[APP–33858] Internal Error

Cause:

Infinite loop detected in MRU list by ffxucm()

Action:

Please refer to your local support representative.

[APP–33859] Internal Error (&1)

Cause:

A cache was supposed to be unlinked from the MRU but it wasn’t on the MRU in the first place.

Action:

Please refer to your local support representative.

[APP–33860] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33861] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33862] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33863] Internal Error (&1)

Cause:

Attempt to evict a cache from MRU but not enough caches on MRU. If the total number of caches

equals one, this error results. A minimum of 2 caches is required.

Action:

Please refer to your local support representative.

[APP–33864] Internal Error (&1)

Cause:

Attempt to evict a cache occupied by the current (active) formula.

Action:

Please refer to your local support representative.

[APP–33865] Internal Error (&1)

Cause:

ffxvec called before ffx000 set up.

Action:

Please refer to your local support representative.

[APP–33866] Internal Error (&1)

Cause:

ffxvec called before ffx000–>env set up.

Action:

Please refer to your local support representative.

[APP–33867] Internal Error

Cause:

An internal error has occurred.

Action:

Please refer to your local support representative.

[APP–33868] Internal Error (&1:&2:&3)

Cause:

The indicator variable that shows the status of a formula output is normally either –1 (not used), 0

(variable referred to, but not set), >= 1 (variable set, indicates the return position). If the

indicator variable is less than –1, then this error will arise.

Action:

Please refer to your local support representative.

[APP–33869] Internal Error

Cause:

ffxcoc received a NULL Penv pointer

Action:

Please refer to your local support representative.

[APP–33870] Internal Error: &1, &2

Cause:

An unknown item cache usage (&2) was detected in function &1.

Action:

Please contact your local support representative.

[APP–33871] Internal Error: &1, &2, &3

Cause:

An item was being referenced which had a different declaration to the internal representation of the

item.

Action:

Please refer to your local support representative.

[APP–33872] Internal Error: &1, &2, &3

Cause:

The context mask for the referenced item was different to the context mask stored internally for the

item.

Action:

Please refer to your local support representative.

[APP–33873] Internal Error: &1

Cause:

A type mismatch was detected when comparing date or text values

Action:

Please refer to your local support representative.

[APP–33874] Internal Error: &1, &2

Cause:

An internal error was detected due to an unknown internal data type.

Action:

Please refer to your local support representative.

[APP–33875] Internal Error: &1

Cause:

An internal error was detected due to an unknown host variable class.

Action:

Please refer to your local support representative.

[APP–33876] Internal Error: &1, &2

Cause:

An internal error occurred due to a NULL context dependency mask being fetched from

FF_FDI_USAGES for a database item or context named

Action:

Please refer to your local support representative.

[APP–33877] Null CONTEXT_ID for item &ITEM_NAME for formula &FMLA_NAME

Action: Please refer to your local support representative.

[APP–33878] Internal error.

Cause: An unknown PLSQL exception &ERROR was raised.

Action: Please refer to your local support representative.

[APP–33879] The item named &NAME does not exist in your formula.

Action: Please check the variable and context names in your formula.

[APP–33901] Internal Error (&1)

Cause:

An error occurred in fful2m() due to an attempt to select more than one item.

Action:

Please refer to your local support representative.

[APP–33902] Internal Error

Cause:

Selection criteria passed to ffuldm() is either too restrictive (no rows found) or not selective enough

(more than one row found).

Action:

Please refer to your local support representative.

[APP–33903] Internal Error

Cause:

The SQL statement passed to ffulmd() contained more than one bind variable.

Action:

Please refer to your local support representative.

[APP–33904] Internal Error (&1)

Cause:

The address of the data (longtext) area was passed into the function as NULL.

Action:

Please refer to your local support representative.

[APP–33905] Internal Error (&1)

Cause:

The WHENEVER SQLWARNING condition was invoked, but the general warning flag was not set.

Action:

Please refer to your local support representative.

[APP–33906] Internal Error (&1)

Cause:

The sqlca.sqlwarn[2] flag was set (see the Pro*C manual). A null value was used in calculating a

SUM, AVG, MIN, MAX etc.

Action:

Please refer to your local support representative.

[APP–33907] Internal Error (&1)

Cause:

sqlca.sqlwarn[3] flag set to ’W’ (see Pro*C manual) A SQL statement had more (or less) columns

named in the SELECT statement than appear in the INTO clause.

Action:

Please refer to your local support representative.

[APP–33908] Internal Error (&1)

Cause:

An UPDATE or DELETE statement was executed without a WHERE clause.

Action:

Please refer to your local support representative.

[APP–33909] Internal Error (&1)

Cause:

sqlca.sqlwarn[5] was set to ’W’ (see Pro*C manual). This should never happen since sqlwarn[5] is

’not used’.

Action:

Please refer to your local support representative.

[APP–33912] Cannot create path name for log directory.

Cause:

An error occurred building the directory name for the log directory.

Action:

Please refer to your system administrator.

[APP–33913] Cannot build filename &1&2

Cause:

An error occurred building a file name from it’s component parts.

Action:

Please refer to your system administrator.

[APP–33914] Cannot add filename &1 to path &2.

Cause:

An error occurred building the full path name of a file.

Action:

Please refer to your system administrator.

[APP–33915] Cannot create file &1.

Cause:

An error occurred creating a file.

Action:

Please refer to your system administrator.

[APP–33916] Internal Error (&1)

Cause:

An error occurred allocating memory for a long field.

Action:

Please refer to your system administrator.

[APP–33917] Internal Error (&1, &2)

Cause:

ffultest : fetched data differs from inserted data. &1 = number of bytes inserted : position of

null–terminator &2 = number of mismatched bytes : position of first incorrect byte : position of last

incorrect byte

Action:

Please refer to your local support representative.

[APP–33918] Internal Error (&1, &2)

Cause:

ffultest : ffulfs returned an invalid file size. &1 = size returned by ffulfs() &2 = name of file

Action:

Please refer to your local support representative.

[APP–33919] Internal Error (ORA&0)

Cause:

An Oracle error occurred deleting any spurious rows from the FFULTEST_TEMP table. This is a

temporary table have a number column (IDCOL) and a long column (LONGCOL), which is set up

in the FastFormula Regression Tester. The number in brackets is the Oracle error.

Action:

Please refer to your local support representative.

[APP–33920] Internal Error

Cause:

Null parameter passed to ffqblt().

Action:

Please refer to your local support representative.

[APP–33921] Internal Error: &1, &2

Cause:

The bind variable &1 could not be bound because its name is different from the expected bind name

Action:

Please refer to your local support representative.

[APP–33951] Internal Error

Cause:

The ffqdcf() function was passed a null parameter (parameter 1).

Action:

Please refer to your local support representative.

[APP–33952] Internal Error

Cause:

Parameter 2, as passed to ffqdcf(), was null.

Action:

Please refer to your local support representative.

[APP–33953] Internal Error

Cause:

Parameter 3 of the ffqdcf() function was null.

Action:

Please refer to your local support representative.

[APP–33954] Internal Error (&1)

Cause:

When reading the report from the database into memory, a fixed chunk of memory is made

available to receive the report. The report was bigger than the space available to hold it, and has

overwritten memory beyond the end of the buffer. This is a QuickPaint internal error.

Action:

Please refer to your local support representative.

[APP–33955] Internal Error (&1,&2,&3,&4)

Cause:

Function ffqdcf() returned a type that was not known about. &1 = function type returned &2 =

Column to jump to &3 = Position in input text (should point to a ’$’ character) &4 = first 10

characters of the input text passed to ffqdcf().

Action:

Please refer to your local support representative.

[APP–33956] Internal Error (&1)

Cause:

Null pointer passed to ffqcdt ()

Action:

Please refer to your local support representative.

[APP–33957] Internal Error (&1,&2)

Cause:

ffqddt() returned an unknown data type (&1) for item &2.

Action:

Please refer to your local support representative.

[APP–33958] Internal Error (&1)

Cause:

A NULL pointer was passed as a parameter to ffqddt()

Action:

Please refer to your local support representative.

[APP–33959] Internal Error (&1)

Cause:

At position &1 in the internal database item list, the pointer to the database item name was found to

be NULL.

Action:

Please refer to your local support representative.

[APP–33961] Internal Error (&1)

Cause:

Null parameter passed to ffqpqr()

Action:

Please refer to your local support representative.

[APP–33962] Internal Error (&1)

Cause:

Null parameter(s) passed to stage 2 parsing function

Action:

Please refer to your local support representative.

[APP–33963] Internal Error (&1,&2)

Cause:

Bad value for either previous token, or current token

Action:

Please refer to your local support representative.

[APP–33964] Internal Error (&1,&2,&3,&4)

Cause:

Bad value taken from action/copytype matrix

Action:

Please refer to your local support representative.

[APP–33965] Internal Error (&1)

Cause:

Bad action – something other than APPEND and REPLACE was found

Action:

Please refer to your local support representative.

[APP–33966] Internal Error

Cause:

Null QP parameter passed to ffqbf2()

Action:

Please refer to your local support representative.

[APP–33967] Internal Error (&1,&2)

Cause:

After reading a QuickPaint report from the database, the attempt to unpack it into separate lines

failed. One of the lines (line_number &2, starting from 1), had too many characters before reaching

a newline or null–terminator (&1 characters)

Action:

Please refer to your local support representative.

[APP–33968] Internal Error (&1, &2)

Cause:

Bad copy type encountered (out of range). &1 = copy type number &2 = action number

Action:

Please refer to your local support representative.

[APP–33980] Failed to generate package &1

Cause:

A Compilation error has been detected while attempting to generate package &1

Action:

Please refer to your system administrator.

[APP–33981] ORA&0 occurred while attempting to compile package &1.

Cause:

An Oracle error occurred while attempting to compile the package with name &1.

Action:

Please refer to your system administrator.

[APP–33982] ORA&0 occurred while attempting to drop package.

Cause:

An Oracle error occurred while attempting to drop a package. The command being executed was

&1. The Oracle Error was &0.

Action:

Please refer to your system administrator.

[APP–33983] Parameter type mismatch for function ’&1’ at line &2

The user has a specified a function whose name has been recognised but whose parameter types do

not match any known version of the function. Please check that the types of any variables or literals

passed to the function are of the appropriate types for the function definition.

[APP–33992] Assertion failed at location &LOCATION Cause : An internal assertion test has

failed. Action : Please refer to your local support representative.

[APP–34001] Starting verify: &FFCOUNT formula instances to process.

[APP–34002] &FTYPE_NAME:&FMLA_NAME:&EFFSTART verified OK

[APP–34004] &FTYPE_NAME:&FMLA_NAME:&EFFSTART FAILED

[APP–34005] No formulas selected: exiting

[APP–34006] Unexpected SQL error &SQLCODE: statement &SQLSTATE

[APP–34010] This program performs the bulk compilation of a set of formulas in an Oracle account.

Where a formula has more than one version, all the different versions will be compiled. SQL

wildcard characters (%% and _) may be used to specify the set of formulas. Use apostrophes around

parameters containing spaces. The program produces PL/SQL packages which are dropped if they

fail to compile. The –K option allows the packages that fail to compile to be kept for error analysis.

For example, to compile all formulas of all Formula Types, which begin with ’NI’, the command

would be <BULKCOMPILE> joe/bloggs 0 Y %% NI%% The same command but keeping all

packages would be <BULKCOMPILE> joe/bloggs 0 Y –K %% NI%%

[APP–34101] Current Zone is not DateTracked.

DateTrack History was selected for a non–DateTracked Zone. DateTrack History is only available

for zones which are DateTracked ie zones which have an Effective Start Date and Effective End

Date.

[APP–34102] No DateTracked instances exist on the database

There are no committed instances of the current record on the database. DateTrack History only

displays instances that have been committed to the database.

[APP–34111] DateTrack History is not available for the current security access.

If the DATETRACK:DATE_SECURITY profile is set to ”PRESENT” or null, then no history

information can be displayed.

[APP–34114] Record cannot be extended as it already ends on &1.

Cause:

You have selected ’Remove all scheduled changes’ or ’Remove next change’, but the record cannot

be extended in time further because it already ends at the latest possible date, which has been

determined by the parent record’s end date.

Action:

You need take no action because the record already ends on the date you require, and there are no

subsequent changes to the record.

[APP–34207] Current rowid has NULL rowid

Normally caused when the DateTrack userexit is called for a record that is in INSERT mode on the

screen (i.e. has no rowid yet)

[APP–34209] Oracle error ORA&0 accessing DT_CODE table

The error code table could not be accessed when an error occurred. Possible reasons are (a) user not

connected to Oracle (b) table has been renamed (c) table has been dropped (d) user has no synonym

DT_CODE in his account (e) user has no SELECT access to the table

[APP–34210] Table &1 has no ENDDATE column

Every DateTracked table must have an ENDDATE column

[APP–34502] Memory Allocation Error (&1)

sqlald() failed attempting to allocate a SQLDA descriptor. The number of column requested is

given in brackets after the message.

[APP–34503] Unable to allocate memory

A 64k byte block of memory was requested via Application Foundation’s fdugvb function. This

returned NULL.

[APP–34504] Insufficient memory (&1 bytes)

A memory allocation call to AF’s fdugbf() failed.

[APP–34505] Insufficient memory (&1 bytes)

Unable to allocate memory calling AF’s fdugbf() function.

[APP–34507] Unable to allocate memory

Called sqlald() to allocate a 2 column descriptor.

[APP–34508] Unable to allocate memory

Attempt to allocate memory for a small descriptor failed.

[APP–34601] Oracle error ORA&0 occurred while accessing table &1

During either PREPARE, DECLARE or DESCRIBE an Oracle error occurred.

[APP–34602] Oracle warning (&1) occurred on table &2

[APP–34603] Oracle error ORA&0 accessing &1 table

Attempting to fetch one row from the SQL*Forms base table.

[APP–34604] Oracle warning while accessing &1 table (&2)

[APP–34605] Oracle error ORA&0 occurred writing to &1

Attempt to copy a row in the table (named in error message).

[APP–34606] Oracle warning occurred writing to &1 (&2)

Attempting to copy a row within the SQL*Forms base table.

[APP–34609] Oracle error ORA&0 (&3)

Oracle error occurred during the prepare, declare, describe stage.

[APP–34611] Oracle error ORA&0 occurred (&4.&1=&3)

While fetching the count of rows, having a Primary Key(&1) with a value (&3), from base table &4,

an Oracle error occurred.

[APP–34612] Oracle warning occurred (&1) on table &2

The contents of sqlca.sqlwarn[] is printed in brackets. The first code is always ’W’, and one other

between sqlwarn&1 and sqlwarn[7] will also be set to ’W’, indicating the nature of the error (see

Pro*C manual).

[APP–34613] Oracle error ORA&0 occurred

While dtdb20() was preparing some SQL an Oracle error was detected.

[APP–34615] Oracle error ORA&0 (&1)

Oracle error occurred while deleting rows

[APP–34616] Oracle warning (&1) while deleting from &2

[APP–34617] &2

[APP–34701] Name of base table unavailable for current block

DateTrack PRE–BLOCK trigger not being called.

[APP–34702] Name of base table unavailable for current block

DateTrack PRE–BLOCK trigger not being called.

[APP–34703] Name of Primary Key column unavailable for &1

In order to select from the base table, the name of that table’s primary key/UID column must be

available.

[APP–34704] Session Effective Date unavailable

A previous trigger should have set up the value of the current Session Effective Date.

[APP–34705] Two digit year used where four–digit year expected (&1)

A date of the format DD–MON–YYYY is expected.

[APP–34706] Wrong date format (&1) : should be DD–MON–YYYY

A date whose length is greater than 11 characters was encountered.

[APP–34716] There are commits outstanding

The ChangeDate window cannot be called when there are outstanding commits. Commit your

changes before calling the ChangeDate window.

[APP–34717] Date security does not allow the effective date to be changed

The DATETRACK:DATE_SECURITY profile is set to PRESENT. The effective date cannot be

changed.

[APP–34719] You may not use an effective date earlier than today.

The DATETRACK:DATE_SECURITY profile is set to FUTURE and does not allow any changes of

date less than SYSDATE

[APP–34720] You may not use an effective date later than today.

The DATETRACK:DATE_SECURITY profile is set to PAST and does not allow any changes of

date greater than SYSDATE.

[APP–34802] Rowid exceeds maximum length

A rowid of more than 18 characters was obtained for current record being processed by SQL*Forms.

[APP–34803] No data found in &1 table for current record

The record being processed by SQL*Forms has a rowid, which is used in the DateTrack user exit to

select the row. When the select takes place if no data is selected, then this error occurs.

[APP–34901] Internal Error (&1)

EXEC SQL DESCRIBE SELECT LIST indicated initially that the descriptor provided was not big

enough to hold the SELECT LIST. A new descriptor had been allocated (successfully) of the

required size, but the DESCRIBE still indicates that the descriptor is too small.

[APP–34902] Error &1 occurred, but no message found in DT_CODE table

There should be an entry in the DT_CODE table for every error that can occur within the DateTrack

system. However an error has occurred for which there is no entry in the DT_CODE table.

[APP–34903] Internal Error (&1)

A descriptor has been created of exactly the right size (given that the exact number of bind variables

is known). However the DESCRIBE function found more than the expected number of bind

variables.

[APP–34904] Internal Error (&1)

An unknown bind variable has turned up in the SQL.

[APP–34905] Internal Error (&1)

Having generated the SQL to be executed, the precise number of SELECT columns is known. A

descriptor of the appropriate size is created. However, the EXEC SQL DESCRIBE felt that the

provided descriptor wasn’t big enough.

[APP–34906] Internal Error (&1;&2)

Only one column should appear in the select descriptor (”COUNT(*)”). However some other

column has slipped in (name in brackets after error message along with name of the base table)

[APP–34910] Internal Error (&1)

The mode parameter was passed with an invalid value into dtdbtr(). Use DT29_ALL or

DT30_FUTURE_ONLY.

[APP–34911] Internal Error (’&1’)

Parameter 2 of dtdbtr(), which should have a rowid value, contained an invalid rowid.

[APP–34912] Internal Error

dtuidc has no value, is empty, or has address of NULL

[APP–34913] Internal Error

dtuidv is NULL, or empty.

[APP–34914] Internal Error

Name of base table (dtbtab) unavailable.

[APP–34915] Internal Error

Session effective date unavailable. This error will occur if dtdbtr() is called with a mode of

DT30_FUTURE_ONLY and there is no value in dtsedt.

[APP–34916] Internal Error

The global variable dtuidv is either null or empty.

[APP–34928] Internal error (&1)

Internal errors encountered in dthedp(), as a result of a call to AF menu or window code, are

reported with this error message. The stage number in brackets serves to identify the problem area.

Clearly, this error should not occur.

[APP–34939] Internal error

This internal error is generated when no default display name is derived for a virtual column. This

should never occur. The default name is derived form the first real column encountered in the

definition which is neither EFFECTIVE_END_DATE nor EFFECTIVE_START_DATE.

[APP–34948] Internal error

This error is reported when the value of a real column constituting a foreign key virtual column is

found to be null in dthrld(). This should not occur since such a condition is filtered out before

calling dthrld()

[APP–34950] Title Prompt is missing for the &VIEW view

Cause:

The DateTrack History window title is missing for the &VIEW view.

Action:

Contact your Oracle support representative quoting this error message. Please provide the name of

the view (&VIEW) and the value of your language profile.

[APP–34951] Missing date prompts for language &LANGUAGE

Cause:

The DateTrack History prompts for the Start Date and/or End date fields are missing for the current

language.

Action:

Contact your Oracle support representative quoting this error message. Please provide the value of

your language profile.

[APP–34952] Cannot access the database table &TABLE

Cause:

DateTrack History attempted to reference the database table called &TABLE.

Action:

Ensure the current user is given access to this table. Otherwise disallow the user from using

datetrack history, by setting the Datetrack:Date_security profile to ’PRESENT’.

[APP–34954] DateTrack History is unavailable for this zone

[APP–34955] Code generated by Oracle FastFormula – do not edit. Formula Name: &2

[APP–35003] Birth date cannot be specified in the future.

Cause:

You entered a birth date that is greater than TODAY

Action:

Re–enter the birth date

[APP–35007] The Intended Return Date must be after the Earliest MPP Start Date

Cause:

You specified the Intended Return date as being BEFORE the Earliest MPP Start Date.

Action:

Ensure the Intended Return date is after the Earliest MPP Start date.

[APP–35008] If you pay SMP as a lump sum, you may have to reclaim some overpayment if the

woman’s circumstances change after payment is made.

[APP–35010] The due date specified is more than 9 months from today.

[APP–35011] This person has been recorded as having had an actual birth within 9 months of the

specified due date. Check the entered due date.

[APP–35018] There is a maternity leave record for this woman. Do you wish to update the

maternity leave end date to the return date specified ?

[APP–35020] There is already a medical evidence record for this person from this source on this

date.

[APP–35021] You cannot enter the evidence date in advance.

[APP–35022] The evidence received date must be after the evidence date.

[APP–35023] You cannot enter the evidence received date in advance.

[APP–35024] Average earnings cannot be calculated automatically unless you have installed Oracle

Payroll. You must enter the figure yourself.

[APP–35025] Oracle Payroll is unable to calculate the earnings of directors because it has no way to

distinguish between voted fees and fees drawn in anticipation of voting. Please enter the average

earnings figure for directors yourself.

[APP–35026] This is a new employee whose earnings have not yet been processed. Oracle Payroll

cannot derive the average earnings for new employees who have not yet received any pay on which

to base a calculation. Please enter the average earnings figure yourself, based upon the employee’s

contracted weekly earnings.

[APP–35027] The medical evidence was received late. Please enter the reason for the late evidence

and state whether or not you accept it.

[APP–35029] Oracle SSP is attempting to insert an entry for SSP/SMP, but cannot determine a

payroll period in which to put it. This means that there is no payroll period for the person’s primary

assignment payroll which is; a) open: open the payroll period. b) defined as having a cut–off date

which is later than the effective date: change effective date. c) after the start of the maternity pay

period (SMP only): create more payroll periods for the payroll. d) before the woman’s final close

date (SMP only): delay the woman’s final close date. e) before the person’s last standard process

date (SSP only): delay the person’s last standard process date. e) before the person’s last standard

process date (SSP only): delay the person’s last standard process date. f) after the date the entry was

earned (the end of the week for which it is a payment). This is not a requirement if the entry is for

SMP paid as a lump sum or if the date earned is after the last standard process date: create more

payroll periods for the payroll. Please resolve this problem before continuing with the SSP/SMP

transaction.

[APP–35031] You have entered a maternity leave start date which is too early. Maternity leave is

not permitted until the Qualifying Week.

[APP–35032] You have attempted to create maternity leave for a person for whom you have no

maternity record.

[APP–35034] The absence start date may not be before the sickness start date.

[APP–35035] The absence end date may not be after the sickness end date.

[APP–35036] The absence notification date may not be before the sickness start date.

[APP–35037] You cannot insert or delete a sickness absence if there are later sickness absences

recorded. Nor may you change sickness start/end dates if this will affect the linking of periods of

incapacity for work. To proceed with this change, you must first remove all the later sickness

absences.

[APP–35046] There is no withholding reason which corresponds to the reason ’&REASON’ for the

element type selected. Contact your Oracle Applications Support Desk.

[APP–35048] There is no SSP qualifying pattern for this person. You must define one for the person

or for the business group to which they belong.

[APP–35054] The MPP start date must be a Sunday.

[APP–35056] The absence notification date cannot be in the future.

[APP–35060] You entered an invalid maternity_id.

[APP–35061] The linked absence specified does not exist.

[APP–35062] You must enter either both sickness end date and absence end date, or neither. If

entered, sickness end date may not be earlier than the absence end date.

[APP–35063] You cannot enter both maternity and sickness attributes for a single absence.

[APP–35064] The absence start date must be before the absence end date.

[APP–35067] The sickness start date cannot be after the notification date.

[APP–35077] No Statutory Sick Pay element exists on &EFFECTIVE_DATE. Either the element

has not been set up correctly or the date passed in was not set correctly. Contact your Oracle

Applications Support desk.

[APP–35078] No Statutory Sick Pay correction element exists on &EFFECTIVE_DATE. Either the

element has not been set up correctly or the date passed in was not set correctly.

[APP–35079] There is no SSP rate specified on &EFFECTIVE_DATE. Either the SSP element was

not correctly set up or the effective date passed was not set correctly.

[APP–35080] Oracle SSP is trying to create an entry for SSP/SMP, but cannot find a payroll for the

primary assignment as at &DATE_EARNED. The primary assignment must be on a payroll if the

person is to be able to receive SSP/SMP entries.

[APP–35216] This absence overlaps another absence of category sickness

[APP–35217] Only one absence of sickness category is allowed with open end dates

[APP–35219] You cannot delete an absence when a PIW is defined for it

[APP–36066] The sickness start date may not be after the absence start date.

[APP–36067] The date you enter must be a Sunday

[APP–36068] The date must be a Saturday.

[APP–36069] You must enter the time in the 24 hour format (eg 22:15).

[APP–36070] The element &ELEMENT_NAME has not been set up correctly. One of the

Developer Descriptive Flexfield segments does not have a value. Contact your Oracle Applications

Support representative.

[APP–36071] The element &ELEMENT_NAME has been set up incorrectly. Either some of its

input values have been incorrectly named or they do not exist. Please consult your Oracle

Applications Support desk.

[APP–36072] You have entered values in fields which are inappropriate for the absence type. Check

the sickness–related fields.

[APP–36073] You have indicated a pregnancy–related illness for a person for whom you have no

record of maternity.

[APP–42211] Maximum number (&PARAMETER) of different tax codes exceeded for Transaction

[APP–42214] For each customer, you may only have one active Legal site

[APP–42215] Number of returned columns (&PARAMETER) is incorrect CAUSE: The SQL

Statement that has been used to drive the tax engine returns

[APP–42216] Clearing Days must be greater than or equal to zero

[APP–42217] Address language is not installed

[APP–42218] Address reference has different languages

[APP–42219] Accounting Effect

[APP–42220] Actual

[APP–42221] Amount

[APP–42222] Applied

[APP–42223] Applied Line Items

[APP–42224] Apply

[APP–42225] Application violates invoice/credit memo type definition.

[APP–42226] AutoCash

[APP–42227] Bank Account Number

[APP–42228] Bank Name

[APP–42229] Batch Date

[APP–42230] Batch Name

[APP–42231] Batch Source

[APP–42232] Batch Status

[APP–42233] This batch has already been processed.

[APP–42234] Error applying to invoices – applications reversed.

[APP–42235] Cannot apply receipt.

[APP–42236] Cannot apply receipt – error getting invoice information.

[APP–42237] Error in creating application.

[APP–42238] Unable to create cash receipt.

[APP–42239] Unable to get interim cash receipts.

[APP–42240] Unable to get interim cash receipt lines.

[APP–42241] Cannot get invoice information.

[APP–42242] Can not update cash receipt record.

[APP–42243] Code

[APP–42244] Comments

[APP–42245] Control

[APP–42246] Count

[APP–42247] Currency

[APP–42248] Customer

[APP–42249] Date

[APP–42250] Deposit Date

[APP–42251] Difference

[APP–42252] Discounts

[APP–42253] Due Date

[APP–42254] Earned

[APP–42255] Error in customer information.

[APP–42256] Error applying to invoice

[APP–42257] Error in clearing account.

[APP–42258] Error in clearing past due items.

[APP–42259] Error in database commit.

[APP–42260] Error in discount information – receipt not applied.

[APP–42261] Error fetching invoices.

[APP–42262] Error putting receipt on account.

[APP–42263] Freight

[APP–42264] from previous receipts

[APP–42265] GL Date

[APP–42266] Insufficient receipt – all applications for cash receipt are reversed

[APP–42267] Insufficient receipt – following items not paid:

[APP–42268] Item

[APP–42269] Meaning

[APP–42270] Name

[APP–42271] This is not a valid batch for this program.

[APP–42272] NO MATCH

[APP–42273] There are no open invoices.

[APP–42274] Partial receipt is not allowed.

[APP–42275] None of the AutoCash rules matched successfully

[APP–42276] Number

[APP–42277] On Account

[APP–42278] Page

[APP–42279] Percentage

[APP–42280] Period

[APP–42281] Post QuickCash Execution Report

[APP–42282] Receipt

[APP–42283] Receivables Charges

[APP–42284] Distribution of Applied Receipt

[APP–42285] Receipt Status Summary

[APP–42286] Remaining

[APP–42287] Rule

[APP–42288] AutoCash Rule Legend

[APP–42289] Status

[APP–42290] Tax

[APP–42291] Total

[APP–42292] Totals

[APP–42293] Total applications

[APP–42294] Total Effect

[APP–42295] Total Receipts in batch

[APP–42296] Type

[APP–42297] Unapplied

[APP–42298] Unearned

[APP–42299] Unidentified

[APP–42300] This location already exists for another address of this customer. Cause : The EDI

Location should be unique for a customer Action : Clear the field or enter a unique value

[APP–42301] Update of this column is not allowed. Reason : Printed/Posted/Applied Transaction(s)

exists for one of the sites (Ship To / Bill To) of this address. Action : Please create a new address.

Requery the address to undo the changes.

[APP–42302] Cannot merge this site. Reason : The address location of the To Address is different

than the From Address. Action : Select a To Address with the same location as From Address.

[APP–42303] Amount Class Value

[APP–42304] Audit Report

[APP–42305] Collector Name

[APP–42306] Compound Interest

[APP–42307] Credit Checking

[APP–42308] Credit Class

[APP–42309] Credit Class Value

[APP–42310] Credit Balance Statements

[APP–42311] Currency

[APP–42312] Currency Code

[APP–42313] Current Value

[APP–42314] Customer Name

[APP–42315] Customized Profile Option

[APP–42316] Date

[APP–42317] Descriptive Flexfield

[APP–42318] Discount Terms

[APP–42319] Discount Grace Days

[APP–42320] Dunning Letters

[APP–42321] Dunning Letter Set

[APP–42322] Exceptions Report

[APP–42323] Grouping Rule

[APP–42324] Include Disputed Items

[APP–42325] Interest Charges

[APP–42326] Interest Period

[APP–42327] Interest Rate

[APP–42328] Location

[APP–42329] Maximum Interest Charge

[APP–42330] Minimum Dunning Amount

[APP–42331] Minimum Dunning Invoice Amount

[APP–42332] Minimum Finance Charge Balance Amount

[APP–42333] Minimum Finance Charge Invoice Amount

[APP–42334] Minimum Receipt Amount

[APP–42335] Minimum Statement Amount

[APP–42336] Number

[APP–42337] Number of Profiles Updated

[APP–42338] Overall Credit Limit

[APP–42339] Override Terms

[APP–42340] Page

[APP–42341] Payment Grace Days

[APP–42342] Payment Rule

[APP–42343] Previous Value

[APP–42344] Profile Class

[APP–42345] Profile Option Updated

[APP–42346] Standard Terms

[APP–42347] Statements

[APP–42348] Statement Cycle

[APP–42349] Tax Printing Option

[APP–42350] Update Customer Profiles

[APP–42351] Tolerance

[APP–42352] Transaction Credit Limit

[APP–42353] Updated Value

[APP–42354] UPDATE ALL PROFILES

[APP–42355] Update Option

[APP–42356] UPDATE ALL UNCUSTOMIZED PROFILES

[APP–42357] UPDATE ALL PROFILE AMOUNTS

[APP–42358] UPDATE ALL UNCUSTOMIZED PROFILE AMOUNTS

[APP–42359] Record Statuses Page:

[APP–42360] Error

[APP–42361] Number Applied Amount Invoice Number Installment Customer Number Invoice

Type Currency

[APP–42362] –––––– –––––––––––––––– –––––––––––––––––––– –––––––––––

–––––––––––––––––––––––––––––– –––––––––––––––––––– –––––––––––––––

[APP–42363] Unable to read the SQL*Loader bad file

[APP–42364] Record –––––––––––––––––––––––––––––––––––––– QuickCash Batch

––––––––––––––––––––––––––––––––––

[APP–42365] Error Identifier Deposit

[APP–42366] Number Lockbox Batch Name | Batch Name Count Amount Currency Date GL

Date

[APP–42367] –––––– ––––––––––––––––––––––––– –– ––––––––––––––––––––––––– ––––––

–––––––––––––––– ––––––––––––––– ––––––––––– –––––––––––

[APP–42368] Receipt Batch Source: &BATCH_SOURCE

[APP–42369] Control File: &INPUT

[APP–42370] Complete Batches Only: &INPUT

[APP–42371] Concurrent Request Id: &CONC_REQUEST

[APP–42372] Count Status

[APP–42373] Data File: &INPUT

[APP–42374] Deposit Date: &DEPOSIT_DATE Bank Origination Number:

&BANK_ORIG_NUMBER

[APP–42375] Deposit Time: &DEPOSIT_TIME Destination Account: &DEST_ACCOUNT

[APP–42376] Record Identifier: &REC_TYPE Deposit Date: &DEPOSIT_DATE GL Date:

&GL_DATE

[APP–42377] Item Number: &ITEM_NUM Receipt Date: &REC_DATE Payment Method:

&REC_METHOD

[APP–42378] Receipt Number: &RECEIPT_NUM Remittance Amount: &REMIT_AMT

[APP–42379] Overflow Sequence: &OVF_SEQUENCE Overflow Indicator: &OVF_INDICATOR

[APP–42380] MICR Number: &MICR_NUM

[APP–42381] Customer Number: &CUST_NUM Customer Identified: &CUST_IDENTIFIED

[APP–42382] Billing Location: &LOCATION

[APP–42383] Billing Location Identified: &LOC_IDENTIFIED

[APP–42384] Bank Origination Number: &BANK_ORIG_NUMBER Destination Account:

&DEST_ACCOUNT

[APP–42385] Currency: &CURRENCY

[APP–42386] Exchange Rate Type: &EXCHANGE_RATE_TYPE Exchange Rate:

&EXCHANGE_RATE

[APP–42387] Transmission Record Count: &TRANS_COUNT Transmission Amount:

&TRANS_AMT

[APP–42388] Lockbox Number: &LOCKBOX_NUMBER Lockbox Amount: &LOCKBOX_AMT

[APP–42389] Lockbox Batch Count: &LB_BATCH_COUNT Lockbox Receipt Count:

&LB_RECEIPT_COUNT

[APP–42390] Lockbox Batch Name: &BATCH_NAME Batch Amount: &BATCH_AMT

[APP–42391] Batch Receipt Count: &BATCH_COUNT

[APP–42392] There are discarded records in &DISFILE

[APP–42393] Unable to read the SQL*Loader discard file

[APP–42394] ***** END OF REPORT: ARLPLB *****

[APP–42395] *********

[APP–42396] Error occurred in Lockbox Processing

[APP–42397] Error occurred in Batch Posting

[APP–42398] Error occurred during validation

[APP–42399] GL Date: &INPUT

[APP–42400] Number of records successfully imported: &IMPORTED_RECORDS

[APP–42401] Receipts with valid customer numbers: &CUST_NUM Receipts with invalid

customer numbers: &INVALID_CUST_NUM

[APP–42402] Receipts with customers: &CUST_ID Receipts with no customers: &NO_CUST

[APP–42403] Receipts with valid billing locations: &LOC_OK Receipts with invalid billing

locations: &INVALID_LOC

[APP–42404] Receipts with no duplicates: &DUP_REC Receipts with duplicates: &NO_DUP

[APP–42405] Receipts with valid payment methods: &MTHD_OK Receipts with invalid payment

methods: &INVALID_MTHD

[APP–42406] Receipts with valid currency: &CURR_OK Receipts with invalid currency:

&INVALID_CURR

[APP–42407] Receipts with valid applications: &APP_OK Receipts with invalid applications:

&INVALID_APP

[APP–42408] Loaded data from &DATAFILE

[APP–42409] Lockbox: &INPUT

[APP–42410] Unable to find lockbox definition for this transmission

[APP–42411] Lockbox Number: &LOCKBOX_NUMBER Record Identifier: &REC_IDENTIFIER

[APP–42412] New Transmission: &INPUT

[APP–42413] The batch size is unknown for lockbox &LOCKBOX

[APP–42414] No data found

[APP–42415] The source of the GL date is unknown for lockbox &LOCKBOX

[APP–42416] There is no record for this transmission request

[APP–42417] Original Concurrent Request: &INPUT

[APP–42418] Page:

[APP–42419] Pay Unrelated Invoices: &INPUT

[APP–42420] Program Parameters

[APP–42421] Record

[APP–42422] ––––––

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

–––––––––––––––––––––––––––––––––––––––––––

[APP–42423] Report Format: &INPUT

[APP–42424] &SET_OF_BOOKS Lockbox Execution Report Report Date: &CURR_DATE

[APP–42425] The rejected records must be reviewed before the validation begins

[APP–42426] Submit Import: &INPUT

[APP–42427] Submit PostBatch: &INPUT

[APP–42428] Submit Validation: &INPUT

[APP–42429] ––––––

[APP–42430] Transmission Record Count: &REC_COUNT Transmission Amount: &TRANS_AMT

[APP–42431] Transmission Format: &INPUT

[APP–42432] Transmission Name: &INPUT

[APP–42433] Records Transferred This Run: &RUN_COUNT Amount Transferred This Run:

&RUN_AMT

[APP–42434] Records Transferred To Date: &TO_DATE_COUNT Amount Transferred To Date:

&TO_DATE_AMT

[APP–42435] The validation process is unable to continue with existing errors

[APP–42436] UNIDENTIFIED

[APP–42437] ************

[APP–42438] If bad file named in control file, check the output of the bad file

[APP–42439] If discard file named in control file, check the output of the discard file

[APP–42440] ERROR Invalid matching number

[APP–42441] Addresses Inserted =

[APP–42442] RA_CUSTOMER_RELATIONSHIPS

[APP–42443] –––––––––––––––––––––––––––

[APP–42444] RA_CUSTOMER_PROFILES_INTERFACE AR_CUSTOMER_PROFILES

AR_CUSTOMER_PROFILE_AMOUNTS

[APP–42445] –––––––––––––––––––––––––––––– ––––––––––––––––––––––––––

––––––––––––––––––––––––––––––––

[APP–42446] Accounts Inserted =

[APP–42447] Addresses Updated =

[APP–42448] Branches Inserted =

[APP–42449] Customer Banks Inserted =

[APP–42450] Contacts Inserted =

[APP–42451] Contacts Updated =

[APP–42452] Customers Inserted =

[APP–42453] Customers Updated =

[APP–42454] Exception Records in RA_CONTACT_PHONES_INTERFACE

[APP–42455] Exception Records in RA_CUSTOMERS_INTERFACE

[APP–42456] Exception Records in RA_CUSTOMER_BANKS_INTERFACE

[APP–42457] Exception Records in RA_CUST_PAY_METHOD_INTERFACE

[APP–42458] Exception Records in RA_CUSTOMER_PROFILES_INTERFACE

[APP–42459] Exception Records =

[APP–42460] RA_CUSTOMERS_INTERFACE RA_CUSTOMERS RA_ADDRESSES

RA_SITE_USES

[APP–42461] –––––––––––––––––––––––––––– –––––––––––––––––––––––––––––––––

[APP–42462] RA_CUSTOMER_BANKS_INTERFACE AP_BANK_BRANCHES

AP_BANK_ACCOUNTS AP_BANK_ACCOUNT_USES

[APP–42463] ––––––––––––––––––––––––––– –––––––––––––––––––––––––––

––––––––––––––––––––––––––– –––––––––––––––––––––––––––––––

[APP–42464] Customer Reference Address Reference Site Use Error Message

[APP–42465] ––––––––––––––––––––––––––– ––––––––––––––––––––––––––– –––––––––––

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

[APP–42466] Customer Reference Address Reference Error Message

[APP–42467] ––––––––––––––––––––––––––––––– –––––––––––––––––––––––––––––

–––––––––––––––––––––––––––––––––––––––

[APP–42468] Customer Reference Address Reference Currency Error Message

[APP–42469] ––––––––––––––––––––––––––– ––––––––––––––––––––––––––– –––––––––––

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

[APP–42470] Contact Reference Telephone Reference Error Message

[APP–42471] ––––––––––––––––––––––––––– –––––––––––––––––––––––––––

––––––––––––––––––––––––––– –––––––––––––––––––––––––––

[APP–42472] ––––––––––––––––––––––––––––––– –––––––––––––––––––––––––––––––

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

[APP–42473] Customer Reference Address Reference Payment Method Name Start Date Error

Message

[APP–42474] –––––––––––––––––– ––––––––––––––––– ––––––––––––––––––– ––––––––––

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

[APP–42475] Customer Reference Address Reference Bank Account Name Start Date Error

Message

[APP–42476] –––––––––––––––––––– –––––––––––––––––––– ––––––––––––––––––––

–––––––––– ––––––––––––––––––––––––––––––––––––––––––––––––––––––––

[APP–42477] RA_CONTACT_PHONES_INTERFACE RA_CONTACTS RA_PHONES

[APP–42478] ––––––––––––––––––––––––––– –––––––––––––––––––––––––––

–––––––––––––––––––––––––––

[APP–42479] RA_CUST_PAY_METHOD_INTERFACE AR_CUST_RECEIPT_METHODS

[APP–42480] Inserted Records =

[APP–42481] Phones Inserted =

[APP–42482] Phones Updated =

[APP–42483] Payment Methods Inserted =

[APP–42484] Profile Amounts Inserted =

[APP–42485] Profile Amounts Updated =

[APP–42486] Profiles Inserted =

[APP–42487] Profiles Updated =

[APP–42488] Request Id =

[APP–42489] Summary of Transfer

[APP–42490] Site Uses Inserted =

[APP–42491] Site Uses Updated = N/A

[APP–42492] Customer Interface Transfer Report

[APP–42493] Total Accounts =

[APP–42494] Total Addresses =

[APP–42495] Total Branches =

[APP–42496] Total Customer Banks =

[APP–42497] Total Contacts =

[APP–42498] Total Customers =

[APP–42499] Total Phones =

[APP–42500] Total Payment Methods =

[APP–42501] Total Profile Amounts =

[APP–42502] Total Profiles =

[APP–42503] Total Records =

[APP–42504] Total Site Uses =

[APP–42505] Updated Records =

[APP–42506] User Id =

[APP–42507] Warning Records in RA_CUSTOMERS_INTERFACE

[APP–42508] Relations Inserted =

[APP–42509] Relations Updated = N/A

[APP–42510] Total Relations =

[APP–42511] (Nil)

[APP–42512] Action Date From &FROM_DATE To &TO_DATE

[APP–42513] Apply

[APP–42514] Apply Date

[APP–42515] As of

[APP–42516] BALANCE DUE

[APP–42517] Balance due From &LOW_AMT to &HIGH_AMT

[APP–42518] Batch

[APP–42519] Call Date From &FROM_DATE To &TO_DATE

[APP–42520] &F_TRX_TYPE_INITCAP Confirmation

[APP–42521] This is not a request for payment

[APP–42522] 100% of Credit Memo applied to &F_PREVIOUS_TYPE_NAME

&F_PREVIOUS_CUSTOMER_TRX_N1

[APP–42523] Date

[APP–42524] Days Past Due From &FROM_DATE To &TO_DATE

[APP–42525] Debit

[APP–42526] Description

[APP–42527] ERROR

[APP–42528] GL Date

[APP–42529] GL Date From &FROM_DATE To &TO_DATE

[APP–42530] ** & F_PERCENT_DUE_ROUNDED% OF &F_TRX_TYPE_NAME TOTAL DUE

IN THIS INSTALLMENT **

[APP–42531] Invoice

[APP–42532] Invoice Date From &FROM_DATE To &TO_DATE

[APP–42533] n/a

[APP–42534] N/A

[APP–42535] None

[APP–42536] No Limit

[APP–42537] Number

[APP–42538] Number adjusted

[APP–42539] Order by

[APP–42540] Purchase Order

[APP–42541] Precedence

[APP–42542] Receipt

[APP–42543] , Sales Order Number : &SALES_ORDER_NUMBER

[APP–42544] Sales Tax @ &TAX_RATE

[APP–42545] Shipping and Handling

[APP–42546] Sum For

[APP–42547] Tax

[APP–42548] Tax Summary by Tax Code

[APP–42549] Tax Summary by Tax Name

[APP–42550] Trx Number

[APP–42551] Unavailable

[APP–42552] Unid Receipt

[APP–42553] Tax &TAX_CODE &EURO_TAXABLE_AMOUNT@ &TAX_RATE

[APP–42554] Years

[APP–42555] This change impacts your other Balancing Segment definitions.

[APP–42556] You cannot insert Account Segments without an Account Default.

[APP–42557] You cannot insert an Aging Bucket Line without an Aging Bucket.

[APP–42558] You cannot insert an AutoCash rule without an AutoCash Hierarchy.

[APP–42559] You cannot insert Distribution Set Lines without a Distribution Set.

[APP–42560] You cannot insert a Dunning Letter Set Line without a Dunning Letter Set.

[APP–42561] You cannot insert a Payment Method without a Receipt Class.

[APP–42562] You cannot insert a Payment Schedule without a Payment Term.

[APP–42563] You cannot insert a QuickCode without a Lookup Type.

[APP–42564] You cannot insert a Receipt Method Account without a Receipt Class.

[APP–42565] You cannot insert a Schedule without a Rule.

[APP–42566] You cannot insert a Territory without a Salesperson.

[APP–42567] You cannot insert a Cycle Date without a Statement Cycle.

[APP–42568] You cannot Insert a Term Line Discount without a Payment Term.

[APP–42569] You cannot insert a Transmission Format without a Transmission Record.

[APP–42570] You cannot insert a Transmission Record without a Transmission.

[APP–42571] Key is not valid in this context.

[APP–42572] You must enter the Attribute Name and the Description.

[APP–42573] You must enter an Account Name, an Account Number, a Description and a Currency.

[APP–42574] You cannot delete Line Ordering Rules when there are dependent rules.

[APP–42575] You cannot delete Payment Terms when there are dependent Discounts.

[APP–42576] You cannot delete the Grouping Rules when there dependent records.

[APP–42577] You cannot delete Grouping Transactions Types while there are dependencies.

[APP–42578] Editing is not allowed in this context.

[APP–42579] You cannot query in this Block.

[APP–42580] You cannot update the Payment Terms when there are dependent Discounts.

[APP–42581] You must Query the Account Segments in the context of the Account Defaults.

[APP–42582] You must query the Aging Bucket Lines in the context of an Aging Bucket.

[APP–42583] You must Query an AutoCash rule in the context of an AutoCash Hierarchy.

[APP–42584] You must query the Distribution Set Lines in the context of the Distribution Set.

[APP–42585] You must Query the Dunning Letter Set Lines in the context of a Dunning Letter Set.

[APP–42586] You must query a Payment Method in the context of a Receipt Class.

[APP–42587] You must Query the Payment Schedule in the context of a Payment Term.

[APP–42588] You must query the QuickCodes in the context of the Lookup Type.

[APP–42589] You must Query a Receipt Method Account in the context of a Receipt Class.

[APP–42590] You must query a Schedule in the context of a Rule.

[APP–42591] You must query a Territory in the context of a Salesperson.

[APP–42592] You must query a Cycle Date in the context of a Statement Cycle.

[APP–42593] You must query the Term Line Discounts in the context of the Payment Term.

[APP–42594] You must query a Transmission Format in the context of a Transmission Record.

[APP–42595] You must query a Transmission Record in the context of a Transmission.

[APP–42596] The Start Date cannot be after the End Date.

[APP–42597] You must supply account assignments or account sets for account class

&ACCOUNT_CLASS.

[APP–42598] The Open Receivable flag &CM_OPEN_REC_FLAG of your credit memo must

match the flag &INV_OPEN_REC_FLAG of the transaction you are crediting.

[APP–42599] The valid account classes are: REV, UNEARN. The account class of

&ACCOUNT_CLASS is invalid.

[APP–42600] You cannot supply Unbilled account sets Bill In Advance transactions.

[APP–42601] The valid account classes are: REV, UNBILL. The account class of

&ACCOUNT_CLASS is invalid.

[APP–42602] You cannot supply Unearned account sets Bill In Arrears transactions.

[APP–42603] The valid account class for this line type is CHARGES. The account class of

&ACCOUNT_CLASS is invalid.

[APP–42604] The account class for freight account assignment and account set records must be

FREIGHT, not &ACCOUNT_CLASS.

[APP–42605] Invalid Account Class (ACCOUNT_CLASS: &ACCOUNT_CLASS)

[APP–42606] The account class for tax account assignment and account set records must be TAX,

not &ACCOUNT_CLASS.

[APP–42607] Accounting duration cannot be specified on tax and freight lines.

(ACCOUNTING_RULE_DURATION: &ACCOUNTING_RULE_DURATION )

[APP–42608] Accounting rules cannot be used on tax and freight lines.

(ACCOUNTING_RULE_ID: &ACCOUNTING_RULE_ID )

[APP–42609] The tax rate may not be specified for tax lines that are not ad hoc.

[APP–42610] The distribution amount must not be specified for transactions that use invoicing

rules. (AMOUNT: &AMOUNT)

[APP–42611] The accounting flexfield is invalid. Additional information: &GENERIC_TEXT

[APP–42612] All lines on transactions with rules must have accounting rules specified. Otherwise,

accounting rules are not allowed.

[APP–42613] The accounting rule duration &ACCOUNTING_RULE_DURATION must be positive

for invoices with rules and be null for invoices without rules.

[APP–42614] The bill–to site must exist in Oracle Receivables, and it must be assigned to the

Bill–to customer. (BILL_TO_SITE_USE_ID: &BILL_TO_SITE_USE_ID )

[APP–42615] The Bill–to contact id must exist and must be assigned to the Bill–to customer.

(BILL_TO_CONTACT_ID: &BILL_TO_CONTACT_ID )

[APP–42616] Invalid Bill–to customer id. (BILL_TO_CUSTOMER_ID:

&BILL_TO_CUSTOMER_ID)

[APP–42617] Only debit memos and credit memos may have a line types of CHARGES. ( CLASS:

&CLASS )

[APP–42618] The Last Period to Credit &LAST_PERIOD_TO_CREDIT must be greater than 0 but

less than the accounting rule duration &INV_ACCOUNTING_RULE_DURATION of the invoice

line you are crediting.

[APP–42619] An invoice against a commitment cannot have a negative total amount. (Total

amount: &TOTAL_AMOUNT)

[APP–42620] No foreign currency code is allowed if realized gain and realized losses accounts are

not set up. The currency code &CURRENCY_CODE is invalid.

[APP–42621] The transaction currency must match one of the currencies associated with the

customer bank account.( BANK_ACCOUNT_ID: &BANK_ACCOUNT_ID )

[APP–42622] Your transaction currency must match one of the currencies associated with the

receipt method unless multi currency is allowed for a bank account associated with the receipt. (

RECEIPT_METHOD_ID: &RECEIPT_METHOD_ID )

[APP–42623] For lines without rules or the lines using the Bill in Advance rule, the GL Date must

be in an open or a future–enterable period. (GL_DATE: &GL_DATE )

[APP–42624] For Bill in Arrears transactions, the GL Date &GL_DATE must not be in an closed

period.

[APP–42625] A credit memo created with a positive total amount cannot credit an invoice which is

against a commitment. (Total amount: &TOTAL_AMOUNT)

[APP–42626] The inventory item flexfield is invalid. Additional information: &GENERIC_TEXT

[APP–42627] The line type for transaction lines must be LINE or CHARGES. ( LINE_TYPE:

&LINE_TYPE )

[APP–42628] Sales Credit lines can only be associated with transaction lines, not tax or freight

lines.(SALESREP_ID: &SALESREP_ID, LINE_TYPE: &LINE_TYPE )

[APP–42629] The supplied Ship–to site must exist and must agree with the supplied Ship–to

customer. ( SHIP_TO_SITE_USE_ID: &SHIP_TO_SITE_USE_ID

[APP–42630] The supplied Ship–to contact id must exist and must agree with the supplied Ship–to

customer. ( SHIP_TO_CONTACT_ID: &SHIP_TO_CONTACT_ID )

[APP–42631] Invalid Ship–to customer id. (SHIP_TO_CUSTOMER_ID:

&SHIP_TO_CUSTOMER_ID)

[APP–42632] Invalid sold to customer id. (SOLD_TO_CUSTOMER_ID:

&SOLD_TO_CUSTOMER_ID)

[APP–42633] The territory flexfield &TERRITORY_ID is invalid. Additional information:

&FLEX_ERROR_TEXT

[APP–42634] The total distribution percent of &PERCENT must be 100% for account class

&ACCOUNT_CLASS.

[APP–42635] The child invoice transaction date &TRX_DATE must be between commitment start

date and end date.

[APP–42636] Invalid Transaction Status &INVALID_VALUE .

[APP–42637] Batch does not exist (BATCH_ID: &BATCH_ID ).

[APP–42638] You cannot supply customer bank accounts when the supplied or defaulted payment

method is of type Manual. (RECEIPT_METHOD_ID: &RECEIPT_METHOD_ID)

[APP–42639] When the payment method is of type Automatic, you must either supply a valid bank

account or ensure that a primary bank account for the currency code of the transaction has been set

up for the Bill–to customer. (RECEIPT_METHOD_ID: &RECEIPT_METHOD_ID)

[APP–42640] You cannot delete transactions that have activity.

[APP–42641] You cannot delete chargebacks.

[APP–42642] You cannot delete debit memo reversals.

[APP–42643] You cannot add new lines when your accounting method is cash basis.

[APP–42644] You cannot update chargebacks.

[APP–42645] You cannot update column &COLUMN_NAME. (Value: &VALUE).

[APP–42646] You cannot update debit memo reversals.

[APP–42647] You cannot update posted transactions.

[APP–42648] You cannot update printed transactions.

[APP–42649] You cannot update transactions on which you have run the Revenue Recognition

Program.

[APP–42650] Charges lines must have quantities of 1 or –1. The quantity &QUANTITY you

provided is invalid.

[APP–42651] The credit_method_for_rules must be null if invoicing rule is not used, or if the

current transaction is not a regular CM. The credit_method_for_rules you provided is

&CREDIT_METHOD_FOR_RULES.

[APP–42652] Credit memo charges lines can only be applied to debit memo charges lines. Either

the line type &CREDITED_TRANS_LINE_TYPE or the transaction type

&CREDITED_TRANS_CLASS is invalid.

[APP–42653] The currency code &CM_CURRENCY of the credit memo must match the currency

code &INV_CURRENCY of the invoice the credit memo is crediting.

[APP–42654] You cannot supply account assignments for regular credit memos when the system

option ’Use Invoice Accounting for Credit Memos’ is Yes

[APP–42655] The GL Date &CM_GL_DATE of the credit memo must not be prior to the GL Date

&INV_GL_DATE of the invoice the credit memo is crediting.

[APP–42656] The line type of &CM_LINE_TYPE on your credit memo must match the line type of

&INV_LINE_TYPE on the transaction line that it is crediting.

[APP–42657] The transaction date &CM_TRX_DATE of the credit memo must not be prior to the

transaction date &INV_TRX_DATE the invoice the credit memo is crediting.

[APP–42658] The Receivables account of your credit transaction must be the same as that of the

transaction being credited, if the credit transaction has the Open Receivables Flag set to No

[APP–42659] The Receivables account of your credit transaction must be the same as that of the

transaction being credited, if the credit transaction has the Open Receivables Flag set to No ( CM

account: &CODE_COMBINATION_ID , Invoice Account: &INV_CODE_COMBINATION_ID )

[APP–42660] The Bill–to customer of your transaction must be the same or related to the one of the

commitment. ( BILL_TO_CUSTOMER_ID: &BILL_TO_CUSTOMER_ID )

[APP–42661] Distribution does not exist. (CUST_TRX_LINE_GL_DIST_ID:

&CUST_TRX_LINE_GL_DIST_ID).

[APP–42662] There are duplicate tax line numbers for transaction line &LINE_NUMBER.

[APP–42663] If exchange_rate_type is ’User’, the exchange_rate cannot be null.

[APP–42664] Exchange rate, rate type, and exchange date must be null for base currency

transactions.

[APP–42665] If exchange_rate_type is not ’User’, the exchange_rate cannot be specified. The

exchange rate type you provided is &EXCHANGE_RATE_TYPE.

[APP–42666] The extended amount &EXTENDED_AMOUNT must have the correct precision and

minimum accountable unit for the specified currency &CURRENCY_CODE.

[APP–42667] The total distribution amount of &DIST_AMOUNT for this freight line must equal

the freight amount of &FREIGHT_AMOUNT.

[APP–42668] You cannot supply freight charges when the Allow Freight option for your transaction

type is No.

[APP–42669] The invoice GL Date &INV_GL_DATE must not be prior to the commitment GL

Date &COMMITMENT_GL_DATE.

[APP–42670] The entered amount: &VALUE for the column &NAME does not have the correct

currency precision.

[APP–42671] Invalid account class. (ACCOUNT_CLASS: &ACCOUNT_CLASS)

[APP–42672] If an invoicing rule is used, the account_set_flag must be Y. Otherwise, it must be N.

The account_set_flag of &ACCOUNT_SET_FLAG you provided is invalid.

[APP–42673] The Open Receivable flag must be Y for child invoices that reference commitments.

The Open Receivable flag &OPEN_RECEIVABLE_FLAG is invalid.

[APP–42674] Invalid accounting rule id. (ACCOUNTING_RULE_ID: &INVALID_VALUE)

[APP–42675] Invalid agreement id. (AGREEMENT_ID): &INVALID_VALUE)

[APP–42676] Invalid customer bank account id. (BANK_ACCOUNT_ID:

&BANK_ACCOUNT_ID)

[APP–42677] Invalid Batch Status &INVALID_VALUE .

[APP–42678] Invalid customer bank account id. (CUSTOMER_BANK_ACCOUNT_ID:

&INVALID_VALUE)

[APP–42679] The valid values for Credit Method For Installments are: LIFO, FIFO and PRORATE.

The value &CREDIT_METHOD_FOR_INSTALLMENTS that you provided is invalid.

[APP–42680] If invoicing rules are used, the Credit Method for Rules must be either ’PRORATE’,

’LIFO’, or ’UNIT’. The Credit Method for Rules &CREDIT_METHOD_FOR_RULES is invalid.

[APP–42681] A regular credit memo can only point to an invoice, debit memo, or commitment.The

transaction your credit memo is crediting is a transaction of class &CREDITED_TRANS_CLASS.

[APP–42682] Invalid conversion type. (EXCHANGE_RATE_TYPE: &INVALID_VALUE)

[APP–42683] Invalid currency code. (INVOICE_CURRENCY_CODE: &INVALID_VALUE)

[APP–42684] Quantity, unit_selling_price, and amount must be null or zero for tax–only and

freight–only lines. The memo line type of this line is &MEMO_LINE_TYPE.

[APP–42685] Invalid tax exempt reason code. (TAX_EXEMPT_REASON_CODE:

&INVALID_VALUE)

[APP–42686] If the system option Allow Exemptions is No then valid values for tax exempt flag are

S or R, otherwise the valid values are S, R or E.(TAX_EXEMPT_FLAG: &INVALID_VALUE)

[APP–42687] Invalid fob point. (FOB_POINT): &INVALID_VALUE)

[APP–42688] The GL_Date of this distribution line, &GL_DATE, must be the same as the

Receivable GL Date, &REC_GL_DATE

[APP–42689] The transaction line specified on this distribution of class &ACCOUNT_CLASS does

not exist.

[APP–42690] The valid invoicing rule ids are –2, –3, or null. The invoicing rule id

&INVOICING_RULE_ID is invalid.

[APP–42691] Invalid line type. (LINE_TYPE: &LINE_TYPE)

[APP–42692] Invalid memo line id. (MEMO_LINE_ID: &INVALID_VALUE)

[APP–42693] Invalid printing option. (PRINTING_OPTION: &INVALID_VALUE)

[APP–42694] Invalid primary salesrep id. (PRIMARY_SALESREP_ID: &INVALID_VALUE)

[APP–42695] Invalid reason code. (REASON_CODE: &INVALID_VALUE)

[APP–42696] Invalid receipt method id. (RECEIPT_METHOD_ID: &INVALID_VALUE)

[APP–42697] Invalid salesrep id. (SALESREP_ID: &SALESREP_ID)

[APP–42698] The set of books id must match the set of books id specified in ar_system_parameters.

(SET_OF_BOOKS_ID: &SET_OF_BOOKS_ID )

[APP–42699] Invalid ship via. (SHIP_VIA: &INVALID_VALUE)

[APP–42700] Invalid batch source ( BATCH_SOURCE_ID: &BATCH_SOURCE_ID )

[APP–42701] The tax code you provided is not active, or it is not an adhoc tax code for tax–only

line. ( VAT_TAX_ID: &VAT_TAX_ID )

[APP–42702] Invalid payment terms id. (TERM_ID: &INVALID_VALUE)

[APP–42703] Invalid Transaction Code (TRANSACTION_CODE: &TRANSACTION_CODE)

[APP–42704] Invalid transaction type id. (TRANSACTION_TYPE_ID: &INVALID_VALUE)

[APP–42705] Invalid unit of measure code. (UOM_CODE: &INVALID_VALUE)

[APP–42706] The currency code &INV_CURRENCY of the commitment invoice must match the

currency code &COMMITMENT_CURRENCY of the commitment.

[APP–42707] An invoice’s commitment must be either a Deposit or a Guarantee. Your invoice

references a transaction whose class is &COMMITMENT_CLASS.

[APP–42708] For on–account credit memos, the invoicing rule id must be null.

(INVOICING_RULE_ID: &INVOICING_RULE_ID )

[APP–42709] If the system parameter ’Accounting Method’ is CASH, the invoicing rule id must be

null. The invoicing rule id &INVOICING_RULE_ID is not allowed.

[APP–42710] The total distribution amount of &DIST_AMOUNT must equal the line amount of

&LINE_AMOUNT.

[APP–42711] Line does not exist. (CUSTOMER_TRX_LINE_ID :

&CUSTOMER_TRX_LINE_ID).

[APP–42712] Invalid Line Transaction Flexfield.

[APP–42713] Either the memo_line_id or the inventory_item_id may be specified, but not both.

(INVENTORY_ITEM_ID: &INVENTORY_ITEM_ID MEMO_LINE_ID: &MEMO_LINE_ID)

[APP–42714] The document created must have a non–negative total amount because the creation

sign for your transaction type is Positive. (Total amount: &TOTAL_AMOUNT)

[APP–42715] The primary key &COLUMN must be null when inserting new records. (Value:

&VALUE).

[APP–42716] You must supply a value for the distribution amount.

[APP–42717] You must supply the amount for a freight–only or tax–only line.The memo line type

of this line is &MEMO_LINE_TYPE.

[APP–42718] The specified commitment does not exist. (INITIAL_CUSTOMER_TRX_ID:

&INITIAL_CUSTOMER_TRX_ID)

[APP–42719] You must supply the amount for this transaction line.

[APP–42720] You must supply the GL Date for this account assignment or account set line.

[APP–42721] The accounting period for the last GL Date is not defined.

(ACCOUNTING_RULE_ID: &ACCOUNTING_RULE_ID RULE_START_DATE:

&RULE_START_DATE)

[APP–42722] You must supply the percent for all account assignment and account set records of

Account Class &ACCOUNT_CLASS.

[APP–42723] Accounting periods must be defined for the GL Date &GL_DATE.

[APP–42724] The specified credited transaction does not exist.

(PREVIOUS_CUSTOMER_TRX_ID: &PREVIOUS_CUSTOMER_TRX_ID)

[APP–42725] This transaction line credits an invoice line that does not exist. (

PREVIOUS_CUSTOMER_TRX_LINE_ID: &PREVIOUS_CUSTOMER_TRX_LINE_ID )

[APP–42726] You must supply a quantity to credit when creating Unit credit memos.

[APP–42727] The receipt method must have already been set up for the Bill–to customer or site. (

BILL_TO_CUSTOMER_ID: &BILL_TO_CUSTOMER_ID )

[APP–42728] The receivable gl date must be specified.

[APP–42729] You must supply a value for the sales credit amount.

[APP–42730] You must supply a percentage for the sales credit.

[APP–42731] If a line is tax exempt, a tax exempt reason must be specified.

[APP–42732] The Tax Rate columns must be specified.

[APP–42733] The transaction line which this distribution line points to does not exist.

[APP–42734] You must supply a unit of measure for transaction lines that use standard items.

[APP–42735] If either the non–revenue amount or the non–revenue percent is specified, then both

must be specified. (NON_REVENUE_PERCENT: &NON_REVENUE_PERCENT,

NON_REVENUE_AMOUNT: &NON_REVENUE_AMOUNT)

[APP–42736] You supplied &FREIGHT_COUNT distributions for this freight line. You must supply

one and only one freight account for each freight line.

[APP–42737] You supplied &REC_DIST_COUNT Receivable distributions for your transaction.

Each transaction must have one and only one Receivable account.

[APP–42738] The document created must have a non–positive total amount because the creation

sign for your transaction type is Negative. (Total amount: &TOTAL_AMOUNT)

[APP–42739] The Bill–to customer of your credit memo must be the same or related to the one of

the invoice it is crediting. ( BILL_TO_CUSTOMER_ID: &BILL_TO_CUSTOMER_ID )

[APP–42740] This transaction line credits the wrong transaction.

(PREVIOUS_CUSTOMER_TRX_ID: &CREDITED_TRANS_ID)

[APP–42741] The supplied amount, &EXTENDED_AMOUNT, must match unit selling price times

quantity of &QUANTITY_TIMES_PRICE when AutoInvoice Clearing is disabled.

[APP–42742] Related transactions must have the same or related Bill–to customers

(BILL_TO_CUSTOMER_ID: &BILL_TO_CUSTOMER_ID)

[APP–42743] Credit memos cannot have related transactions. ( RELATED_CUSTOMER_TRX_ID:

&RELATED_CUSTOMER_TRX_ID )

[APP–42744] The specified related transaction does not exist. (RELATED_CUSTOMER_TRX_ID:

&RELATED_CUSTOMER_TRX_ID)

[APP–42745] Invoicing and accounting rules cannot be used on charges lines.

(INVOICING_RULE_ID: &INVOICING_RULE_ID ACCOUNTING_RULE_ID:

&ACCOUNTING_RULE_ID )

[APP–42746] Sales credits have been specified for CHARGES line &LINE_NUMBER. CHARGES

lines cannot have sales credits.

[APP–42747] Sales Credit does not exist. (CUST_TRX_LINE_SALESREP_ID :

&CUST_TRX_LINE_SALESREP_ID).

[APP–42748] The rule start date must be the same as the accounting rule’s first date.

[APP–42749] For Bill in Advance transactions, the supplied rule start date &RULE_START_DATE

must be in a open or future–enterable period.

[APP–42750] For Bill in Arrears transactions, the rule start date &RULE_START_DATE must

result in the last GL Date &LAST_GL_DATE in an open, future–enterable or never opened period.

[APP–42751] The total distribution amount of &DIST_AMOUNT for this tax line must equal the

tax amount of &TAX_AMOUNT.

[APP–42752] You cannot supply tax and related information when the Tax Calculation option for

your transaction type is No

[APP–42753] You cannot supply payment terms for credit memo transactions. (TERM_ID:

&TERM_ID )

[APP–42754] Terms are required for all transaction except for credit memos.

[APP–42755] You can have at most one Freight transaction line at either the line level or the invoice

level, but not at both levels.

[APP–42756] Transaction does not exist. (CUSTOMER_TRX_ID: &CUSTOMER_TRX_ID).

[APP–42757] The child invoice transaction date &INV_TRX_DATE must not be prior to the

commitment transaction date &COMMITMENT_TRX_DATE.

[APP–42758] The supplied unit of measure &UOM_CODE and the primary unit of measure

&ITEM_UOM_CODE of your system item must share the same unit of measure class.

[APP–42759] You may not specify a unit of measure for Charges lines. ( UOM_CODE:

&UOM_CODE )

[APP–42760] Your selection is not a valid option for this tax code. Please choose either ”Yes” or

”No” for ”Amount Includes Tax.”

[APP–42761] You have assigned the same sequence to more than one default in the tax hierarchy.

Each default must have a distinct sequence in the tax hierarchy. Please re–enter.

[APP–42762] Transaction line number &LINENO does not match its Revenue account tax code

&GL_TAX_CODE.

[APP–42763] Tax Group &TAX_CODE cannot be used on a tax line, Use a singular tax code. A tax

group was incorrectly assigned to a tax line by your tax–defaulting source. Oracle Receivables is

unable to calculate the necessary tax when a tax group is used on a tax line. Ensure that a singular

tax code is available for the tax line.

[APP–42764] Multiple inclusive taxes cannot be defined within overlapping time periods with the

same criteria.

[APP–42765] Unable to calculate multiple inclusive taxes.

[APP–42766] Validation of tax code(s) from Revenue Account failed. Would you like the system to

correct the tax code automatically?

[APP–42767] Please check your set of books and period set up.

[APP–42768] Value for amount exceeds permissible limits. Please reenter.

[APP–42769] Starting Module: Sales Tax Rate Assignments

[APP–42770] Completed Module: Sales Tax Rate Assignments. &TOTALLINES processed,

&BADLINES in error

[APP–42771] Tax Cache had &SIZE elements, &HITS hits, &MISSES misses and &DROPS drops

[APP–42772] Sales Tax: Starting AutoAccounting

[APP–42773] Sales Tax: AutoAccounting Finished

[APP–42774] Number already exists, please enter unique number.

[APP–42775] A bank and branch with this bank number and branch number already exists

[APP–42776] Adjustment

[APP–42777] Adjustments Count

[APP–42778] Adjustments Total

[APP–42779] Adjustment Activity

[APP–42780] Adjustment Type

[APP–42781] Adjusted Amount

[APP–42782] Approval Limits

[APP–42783] Approved

[APP–42784] AutoAdjustment Audit Report

[APP–42785] Balance Due

[APP–42786] Created By

[APP–42787] Currency

[APP–42788] Customer Name

[APP–42789] Customer Number

[APP–42790] Date

[APP–42791] Adjustment Account

[APP–42792] Due Date

[APP–42793] END OF REPORT –– AutoAdjustment Audit Report

[APP–42794] GL Date

[APP–42795] Invoice

[APP–42796] Transaction Type

[APP–42797] Number

[APP–42798] Page

[APP–42799] Pending

[APP–42800] AutoAdjustment Preview Report

[APP–42801] Remaining Amount

[APP–42802] Remaining Percent

[APP–42803] Report Parameters

[APP–42804] Status

[APP–42805] Total Pages

[APP–42806] Total Approved Adjustments Count

[APP–42807] Total Approved Adjustments

[APP–42808] Total Pending Adjustments Count

[APP–42809] Total Pending Adjustments

[APP–42810] Type

[APP–42811] to

[APP–42812] applied to

[APP–42813] on account

[APP–42814] unapplied

[APP–42815] unidentified

[APP–42816] Match Receipts By

[APP–42817] Remainder Rule Set

[APP–42818] 10 Periods Prior

[APP–42819] 11 Periods Prior

[APP–42820] 1 Period Prior

[APP–42821] 2 Periods Prior

[APP–42822] 3 Periods Prior

[APP–42823] 4 Periods Prior

[APP–42824] 5 Periods Prior

[APP–42825] 6 Periods Prior

[APP–42826] 7 Periods Prior

[APP–42827] 8 Periods Prior

[APP–42828] 9 Periods Prior

[APP–42829] Amount Collected

[APP–42830] Average Invoice

[APP–42831] Over Split Amount

[APP–42832] Under Split Amount

[APP–42833] Credit Memos Created

[APP–42834] Conventional DSO

[APP–42835] Creation Date

[APP–42836] Current Sales

[APP–42837] DSO Calculation Days

[APP–42838] Gross Receivables

[APP–42839] Indicator

[APP–42840] Invoice Amount

[APP–42841] Over Split Amount

[APP–42842] Under Split Amount

[APP–42843] Over Split Amount

[APP–42844] Under Split Amount

[APP–42845] Net Receivables

[APP–42846] Number of Invoices

[APP–42847] Open Credit Memos

[APP–42848] Open Receipts

[APP–42849] Page

[APP–42850] ( % Collected)

[APP–42851] Payment Pattern

[APP–42852] Report Date

[APP–42853] Rolling Ten Periods

[APP–42854] Inv. Split Amount

[APP–42855] Collection Effectiveness Indicators

[APP–42856] Total

[APP–42857] Total

[APP–42858] Adjustments Created

[APP–42859] chargeback

[APP–42860] credit memo

[APP–42861] deposit

[APP–42862] debit memo

[APP–42863] guarantee

[APP–42864] invoice

[APP–42865] Erroneous Batch – Please Delete!!

[APP–42866] .

[APP–42867] .

[APP–42868] .

[APP–42869] .

[APP–42870] .

[APP–42871] .

[APP–42872] .

[APP–42873] .

[APP–42874] .

[APP–42875] .

[APP–42876] .

[APP–42877] .

[APP–42878] .

[APP–42879] .

[APP–42880] .

[APP–42881] .

[APP–42882] .

[APP–42883] .

[APP–42884] at new rate.

[APP–42885] at new rate.

[APP–42886] at new rate.

[APP–42887] at new rate.

[APP–42888] at new rate.

[APP–42889] at old rate.

[APP–42890] at old rate.

[APP–42891] at old rate.

[APP–42892] at old rate.

[APP–42893] at old rate.

[APP–42894] .

[APP–42895] bank charge

[APP–42896] .

[APP–42897] .

[APP–42898] .

[APP–42899] bank charge

[APP–42900] .

[APP–42901] .

[APP–42902] .

[APP–42903] Credit ADJ for adjustment on

[APP–42904] Credit AR for adjustment on

[APP–42905] Debit ADJ for adjustment on

[APP–42906] Debit AR for adjustment on

[APP–42907] Gain/Loss: Rounding adjustment

[APP–42908] AR(CM) account for credit memo

[APP–42909] AR account for credit memo

[APP–42910] Gain/Loss: G/L account for credit memo

[APP–42911] Gain/Loss: AR account for credit memo

[APP–42912] AR account for

[APP–42913] Freight of

[APP–42914] account for

[APP–42915] Tax of

[APP–42916] DISC account for discount taken: Receipt

[APP–42917] AR account for discount taken: Receipt

[APP–42918] DISC account for earned discount taken: Receipt

[APP–42919] AR account for earned discount taken: Receipt

[APP–42920] Distribution for receipt

[APP–42921] Gain/Loss: G/L account for receipt

[APP–42922] Gain/Loss: AR account for receipt

[APP–42923] Receipt

[APP–42924] Distribution for receipt

[APP–42925] Receipt

[APP–42926] Reverse Gain/Loss: G/L account for receipt

[APP–42927] Reverse Gain/Loss: AR account for receipt

[APP–42928] Reverse receipt

[APP–42929] Reverse distribution for receipt

[APP–42930] Reverse receipt

[APP–42931] Receipt

[APP–42932] Receipt

[APP–42933] Gain/Loss: G/L account for receipt

[APP–42934] Gain/Loss: AR account for receipt

[APP–42935] Reverse: Receipt

[APP–42936] Reverse: Receipt

[APP–42937] Receipt

[APP–42938] DISC account for unearned discount taken: Receipt

[APP–42939] AR account for unearned discount taken: Receipt

[APP–42940] Preliminary

[APP–42941] Original

[APP–43000] Invalid Item Definition Level in &TABLE table. Ensure that the &COLUMN column

in the &TABLE table contains a valid Item Definition Level. Valid values are: 1, 2, 3, ( in the

ITEM_DEFINITION_LEVEL column ) or ’CUSTOMER’, ’ADDRESS CATEGORY’, and

’ADDRESS’ ( in the ITEM_DEFINITION_LEVEL_DESC column ).

[APP–43001] No Item Definition Level specified in the &TABLE table. Ensure that the Item

Definition Level information is specified in the &TABLE table.

[APP–43002] Inactive Customer in &TABLE table. Ensure that the &COLUMN column in the

&TABLE table contains an active Customer.

[APP–43003] No Customer information specified in the &TABLE table. Ensure that the Customer

information is specified in the &TABLE table.

[APP–43004] Invalid Customer in &TABLE table. Ensure that the &COLUMN column in the

&TABLE table contains a valid Customer.

[APP–43005] Multiple Customers with the same specified criteria in the RA_CUSTOMERS table.

Ensure that the Customer information specified in the &TABLE table refers to only one existing

Customer.

[APP–43006] Inactive Address in &TABLE table. Ensure that the &COLUMN column(s) in the

&TABLE table contain(s) an active Address.

[APP–43007] No Address information specified in the &TABLE table. Ensure that the Address

information is specified in the &TABLE table.

[APP–43008] Invalid Address in &TABLE table. Ensure that the &COLUMN column(s) in the

&TABLE table contain(s) a valid Address. If the Address_Id is not provided, you must ensure that

all the address columns match character by character. An extra balnk space will cause two records

to mismatch.

[APP–43009] Multiple Addresses with the same specified criteria in the RA_ADDRESSES table.

Ensure that the Address information specified in the &TABLE table refers to only one existing

Address.

[APP–43010] Disabled Address Category in &TABLE table. Ensure that the &COLUMN column in

the &TABLE table contains an enabled Address Category.

[APP–43011] Inactive Address Category in &TABLE table. Ensure that the &COLUMN column in

the &TABLE table contains an active Address Category.

[APP–43012] No Address Category information specified in the &TABLE table. Ensure that the

Address Category information is specified in the &TABLE table.

[APP–43013] Invalid Address Category in &TABLE table. Ensure that the &COLUMN in the

&TABLE table contains a valid Address Category.

[APP–43014] Invalid Container Item in &TABLE table. Ensure that the &COLUMN column(s) in

&TABLE table contain(s) a valid Container Item.

[APP–43015] Inactive Commodity Code in &TABLE table. Ensure that the &COLUMN column in

the &TABLE table contains an active Commodity Code.

[APP–43016] No Commodity Code information specified in the &TABLE table. Ensure that the

Commodity Code information is specified in the &TABLE table.

[APP–43017] Invalid Commodity Code in &TABLE table. Ensure that the &COLUMN column in

the &TABLE table contains a valid Commodity Code.

[APP–43018] Multiple Commodity Codes with the same specified criteria in the

MTL_COMMODITY_CODES table. Ensure that the Commodity Code information specified in the

&TABLE table refers to only one existing Commodity Code.

[APP–43019] Inactive Model Customer Item in &TABLE table. Ensure that the &COLUMN

column in the &TABLE table contains an active Model Customer Item.

[APP–43020] Invalid Model Customer Item in &TABLE table. Ensure that the &COLUMN

column in the &TABLE table contains a valid Model Customer Item.

[APP–43021] Multiple Model Customer Items with the same specified criteria in the

MTL_CUSTOMER_ITEMS table. Ensure that the Model Customer Item information specified in

the &TABLE table refers to only one existing Model Customer Item.

[APP–43022] Demand Tolerance is out of range in the &TABLE table. Valid numeric values are

between 0 and 999.99, inclusive.

[APP–43023] Minimum Fill Percentage (MIN_FILL_PERCENTAGE) column in &TABLE table is

out of range. Valid numeric range is from 0 to 100, inclusive.

[APP–43024] Invalid Departure Planning Flags in &TABLE table. Valid values are: ’1’ ( meaning

Yes ) and ’2’ ( meaning No ). The following rule may have been violated: &RULE.

[APP–43025] Record was not inserted into destination table. Could not insert record from the

&TABLE table into destination table.

[APP–43026] Record was not deleted from &TABLE table.

[APP–43027] Inactive Item Master Organization in &TABLE table. Ensure that the &COLUMN

column in the &TABLE table contains an active Item Master Organization.

[APP–43028] Invalid Item Master Organization in &TABLE table. Ensure that the &COLUMN

column in the &TABLE table contains a valid Item Master Organization.

[APP–43029] Multiple Item Master Organizations with the same specified criteria in the

MTL_ORGANIZATION_UNITS table. Ensure that the Master Organization information specified

in the &TABLE table refers to only one existing Master Organization.

[APP–43030] No Inventory Item information specified in the &TABLE table. Ensure that the

Inventory Item information is specified in the &TABLE table.

[APP–43031] Invalid Inventory Item in &TABLE table. Ensure that the &COLUMN column(s) in

the &TABLE table contain(s) a valid Inventory Item.

[APP–43032] Invalid Inactive Flag (INACTIVE_FLAG) value in &TABLE table. Valid values are:

’1’ ( meaning Yes ) or ’2’ ( meaning No ).

[APP–43033] No Concurrent Program information specified in the &TABLE table. Ensure that the

Concurrent Program information has been populated in the &TABLE table. Please, contact your

support representative.

[APP–43034] Record with the same unique key combination already exists in the

MTL_CUSTOMER_ITEMS table. Ensure that the following columns, in the &TABLE table,

contain a unique ( non–existent in the MTL_CUSTOMER_ITEMS table ) combination:

CUSTOMER_ITEM_NUMBER, CUSTOMER_ID, CUSTOMER_CATEGORY_CODE,

ADDRESS_ID, and ITEM_DEFINITION_LEVEL.

[APP–43035] Record with the same unique key combination already exists in the

MTL_CUSTOMER_ITEM_XREFS table. Ensure that the following columns, in the &TABLE

table, represent a unique combination in the MTL_CUSTOMER_ITEM_XREFS table:

&COLUMN1, &COLUMN2, COLUMN3.

[APP–43036] Missing required column(s) in &TABLE table. Ensure that information for all the

required columns in the destination table ( MTL_CUSTOMER_ITEMS or

MTL_CUSTOMER_ITEM_XREFS ) is provided in the appropriate interface table.

[APP–43037] No Customer Item found in the MTL_CUSTOMER_ITEMS table with the specified

criteria.

[APP–43038] No Customer Item Cross Reference found in the MTL_CUSTOMER_ITEM_XREFS

table with the specified criteria.

[APP–43039] Inactive Customer Item found in MTL_CUSTOMER_ITEMS table.

[APP–43040] Inactive Customer Item Cross Reference found in MTL_CUSTOMER_ITEM_XREFS

table.

[APP–43041] Returned attribute value is NULL. Successful Customer Item and Customer Item

Cross Reference fetch.

[APP–43042] Required parameters are missing. Ensure that all the required parameters are being

passed to the API call.

[APP–43043] Invalid column name specified in the Attribute_Name parameter. Ensure that the

value passed to this parameter is a valid column name in the MTL_CUSTOMER_ITEMS table or

one of the following values: Inventory_Item_Id, Master_Organization_Id, or Preference_Number.

[APP–43044] Mismatch between API parameter Attribute_Name and the

MTL_CUSTOMER_ITEMS columns.

[APP–43045] No Item Master Organization defined in the &TABLE table. Ensure that a valid Item

Master Organization is specified in one of the following columns: &COLUMN1, &COLUMN2,

&COLUMN3 .

[APP–43046] Warning: Records with validation errors. &ERROR_COUNT record(s) in the

&TABLE table failed validation. Please correct the errors in &TABLE table and re–submit the

concurrent program.

[APP–43047] No seeded data in Oracle Applications for Item Definition Level. Contact your

support representative. Error found while processing records in the &TABLE table.

[APP–43048] Multiple Item Definition Level codes found in MFG_LOOKUPS. Contact your

support representative. Error found while processing records in the &TABLE table.

[APP–43049] No Master Container has been defined in the &TABLE table. Ensure that a valid

Master Container is specified for the Detail Container. Detail Containers cannot be specified

without a valid Master Container.

[APP–43050] A Model Customer Item with a lower Item Definition Level than the Customer Item’s

Definition Level has been specified in the &TABLE. Ensure that a Model Customer Item with an

Item Definition Level greater than or equal to the Customer Item’s Definition Level is specified in

the &COLUMN column.

[APP–43051] Required Customer Item information is missing from the &TABLE table. Provide a

value for the CUSTOMER_ITEM_ID or the CUSTOMER_ITEM_NUMBER column.

[APP–43052] Invalid Customer Item specified in the &TABLE table. Ensure that a valid Customer

Item is specified in the &COLUMN column.

[APP–43053] Multiple Customer Item records have been found in the MTL_CUSTOMER_ITEMS

table with the same specified criteria. Ensure that unique criteria for a Customer Item is specified in

the &TABLE table.

[APP–43056] A default shipping subinventory already exists for this item.

[APP–43059] A shipping locator already exists for this item and subinventory.

[APP–44005] Ending Automatic Address Export. File Name for Export was ’&FNAME’ in path

’&PATHNAME’.

[APP–44010] &ROUTINE–&ERR_NUMBER: &SQL_ERR. Please take note of both this error and

the actions you were trying to perform. Contact your system administrator for assistance.

[APP–44014] Ending Automatic Commodity Code Export. File name for export was ’&FNAME’ in

path ’&PATH_NAME’

[APP–44019] Concurrent Request Failure, Request ID: ’&REQ_ID’. Error file path is:

’&FURTHER_INFO’

[APP–44023] Address records do not exist for this customer. Do you wish to create new records?

[APP–44024] Export document detail record does not exist for this commodity code. Do you wish

to create a new record?

[APP–44025] Trading partner group record does not exist for this trading partner group. Do you

wish to create a new record?

[APP–44026] Customer item records do not exist for this customer. Do you wish to create new

records?

[APP–44030] Ending Customer Item Export. File name for export was &FNAME in path

’&PATHNAME’.

[APP–44040] Error in Transfer. Value for debugging are Type = ’&TYPE’. Table = ’&TAB’. File

= ’&OUTPUT_FILE’. Description = ’&DESCRIPTION’. Field Value = ’&FIELD_VALUE’.

[APP–44047] External Company Cross–Reference Code

[APP–44052] Generate Bar Code Label Flag

[APP–44060] The entry in the &FIELD equals or exceeds 24. Please check your entry and enter

value less than 24.

[APP–44061] The entry in &FIELD equals or exceeds 60. Please check your entry and enter value

less than 60.

[APP–44062] An invalid Organization has been entered. Please check your entry and try again.

[APP–44088] Organization ’&ORG_CODE’ has multiple cross references setup in the EDI Code

Conversion Values form. A single cross reference is required to export item information to CARaS.

[APP–44091] Detail Container Type ’&CONTAINER_TYPE’ has multiple cross references setup in

the EDI Code Conversion Values form. A single cross reference is required to export item

information to CARaS.

[APP–44092] Master Container Type ’&CONTAINER_TYPE’ has multiple cross references setup

in the EDI Code Conversion Values form. A single cross reference is required to export item

information to CARaS.

[APP–44093] Converted UOM Code ’&C_UOM_CODE’ has multiple cross references setup in the

EDI Code Conversion Values form. A single cross reference is required to export item information

to CARaS.

[APP–44094] Inner Pack UOM Code ’&I_UOM_CODE’ has multiple cross references setup in the

EDI Code Conversion Values form. A single cross reference is required to export item information

to CARaS.

[APP–44095] Primary UOM Code ’&P_UOM_CODE’ has multiple cross references setup in the

EDI Code Conversion Values form. A single cross reference is required to export item information

to CARaS.

[APP–44096] Standard Pack UOM Code ’&S_UOM_CODE’ has multiple cross references setup in

the EDI Code Conversion Values form. A single cross reference is required to export item

information to CARaS.

[APP–44097] Standard Pack Dim UOM Code ’&SD_UOM_CODE’ has multiple cross references

setup in the EDI Code Conversion Values form. A single cross reference is required to export item

information to CARaS.

[APP–44098] Ending Manual Address Export. File Name for Export was ’&FNAME’ in path

’&PATHNAME’.

[APP–44101] Ending Manual Commodity Code Export. File name for export was ’&FNAME’ in

path ’&PATH_NAME’

[APP–44104] Ending Manual Customer Item Export. File Name for Export was ’&FNAME’ in path

’&PATHNAME’

[APP–44115] Container Load data for Container ’&CONTAINER’ and item ’&ITEMNUMBER’ in

the Shipping Container Load details form, is required to export item information to CARaS.

[APP–44116] Trading partner group extensions for group ’&GROUPCODE’ in the Automotive

Trading Partners Extensions form are required to export item information to CARaS.

[APP–44119] Container Load data between Master Container ’&CONTAINER’ and Item

’&ITEMNUMBER’ in the Shipping Container Load form is required to export item information to

CARaS.

[APP–44120] Container Load data between Master Container ’&MCONT’ and Detail Container

’&DETCONT’ for Customer item ’&CITEM’ in the Shipping Container Load form to export item

information to CARaS.

[APP–44123] Cross reference for Organization ’&ORG_CODE’ is required to be setup in the EDI

Code Conversion Values form, to export item to CARaS.

[APP–44125] Converted Inner Pack Unit of Measure Code ’&CIP_UOM’ for Customer Item

’&CITEM’ must be exactly 2 characters in the Automotive Customer items form, to export item

information to CARaS.

[APP–44126] Converted Standard Pack Dimension Unit of Measure ’&CSPD_UOM’ for Customer

Item ’&CITEM’ must be exactly 2 characters in the Automotive Customer Items form, to export

item information to CARaS.

[APP–44127] Converted Unit of Measure Code ’&CON_UOM’ for Customer Item ’&CITEM’ must

be exactly 2 characters in the Automotive Customer Items form, to export item information to

CARaS.

[APP–44128] State ’&STATE’ for Customer ’&CUST_NAME’ and Address ’&ADDR_1’ in the

Receivables Customers form, must be exactly 2 characters, to export address information to

CARaS..

[APP–44129] Translator Code ’&TRANSLATOR_CODE’ for the Trading Partner Group

’&TP_GROUP’ in EDI Trading Partner Definition form must be exactly 2 characters, to export

trading partner information to CARaS.

[APP–44130] External Company ’&EXT_COMPANY’ must be exactly 3 characters for

Organization ’&ORGCODE’ in the EDI Code conversions form, to export item information to

CARaS.

[APP–44132] Customer Item Number ’&CUSTITEM’ for the customer ’&CUSTOMER’ in the

Inventory Customer Items form must be numeric because the part number data type in the

Automotive Trading Partner form is of type ’D’.

[APP–44134] Organization code ’&ORG_CODE’ in the EDI Code Conversion Values form needs

to be cross–referenced to an external company code, to export address cross–reference information

to CARaS.

[APP–44135] Organization Code ’&ORG_CODE’ in the EDI Code Conversion Values form is

required to be cross–referenced to an external Company code to export the item information to

CARaS.

[APP–44136] Organization ’&ORG_CODE’ needs to be cross referenced in the EDI Code

Conversion Values form to export item information to CARaS.

[APP–44137] Customer Item ’&CUSTITEM’ needs to be cross referenced with an Inventory Item

in the Inventory Customer Item Cross Reference form to export item information to CARaS.

[APP–44141] Detail container type ’&D_CONT_TYPE’ needs to be cross referenced in the EDI

Code Conversion Values form to export item information to CARaS.

[APP–44143] Reference 2 (Destination Abbreviation) for Trading Partner ’&TP_CODE’ and

Trading Partner Group ’&GROUP_CODE’ in the EDI Trading Partner form is required to export

item information to CARaS.

[APP–44145] EDI Location for Customer ’&CUST_NAME’ and Address ’&ADDR_1’ in the

Receivables Customers form, is required to export address information to CARaS.

[APP–44146] Master container type ’&M_CONT_TYPE’ needs to be cross referenced in the EDI

Code Conversion Values form to export the item to CARaS.

[APP–44154] Translator code for Trading Partner ’&TP_CODE’ and Trading Partner Group

’&GROUP_CODE’ in the EDI Trading Partner form is required to export item information to

CARaS.

[APP–44155] Converted UOM Code ’&C_UOM_CODE’ needs to be cross referenced in the EDI

Code Conversion Values form to export item information to CARaS.

[APP–44156] Inner Pack UOM Code ’&I_UOM_CODE’ needs to be cross referenced in the EDI

Code Conversion Values form to export item information to CARaS.

[APP–44157] Primary UOM Code ’&P_UOM_CODE’ needs to be cross referenced in the EDI Code

Conversion Values form to export item information to CARaS.

[APP–44158] Standard Pack UOM Code ’&S_UOM_CODE’ needs to be cross referenced in the

EDI Code Conversion Values form to export item information to CARaS.

[APP–44159] Standard Pack Dim UOM Code ’&SD_UOM_CODE’ needs to be cross referenced in

the EDI Code Conversion Values form to export item information to CARaS.

[APP–44160] Automotive Address extension information for Customer ’&CUST_NAME’ and

Address ’&ADDR_1’ in the Automotive Address Extension form, is required to export address

cross–reference information to CARaS.

[APP–44170] Detail Container Quantity for Customer ’&CUSTNAME’ and Customer item

Customer Item ’&CUSTITEM’ in the Shipping Container Load form needs to be between 0 and

9999999, to export item information to CARaS.

[APP–44171] Detail Container Weight for Customer ’&CUSTNAME’ and Customer Item

’&CUSTITEM’ in the Inventory items form needs to be between 0 and 9999.99, to export item

information to CARaS.

[APP–44180] Master Container Quantity for Customer ’&CUSTNAME’ and Customer Item

’&CUSTITEM’ in the Shipping Container Load form needs to be between 0 and 9999999, to export

item information to CARaS.

[APP–44181] Master Container Weight for Customer ’&CUSTNAME’ and Customer Item

’&CUSTITEM’ in the Inventory items form needs to be between 0 and 9999.99, to export item

information to CARaS.

[APP–44182] Minimum Fill Percentage for Customer ’&CUSTNAME’ and Customer Item

’&CUSTITEM’ in the Inventory Customer Items form needs to be between 0 and 99, to export item

information to CARaS.

[APP–44195] Max Load Quantity for Master and Detail Containers for Customer ’&CUSTNAME’

and Customer Item ’&CUSTITEM in the Shipping Container Load form needs to be between 0 and

999999, to export item information to CARaS.

[APP–44197] Unit Weight for Customer ’&CUSTNAME’ and Customer Item ’&CUSTITEM’ in

the Inventory Items form needs to be between 0 and 99999.99999, to export item information to

CARaS.

[APP–44209] City ’&CITY’ for Customer ’&CUST_NAME’ and Address ’&ADDR_1’ in the

Receivables Customers form, needs to be 30 characters or less, to export address information to

CARaS.

[APP–44215] Customer Category Code &CATCODE in the Inventory Item form should be 5

characters or less, to export item information to CARaS.

[APP–44216] WARNING : Customer Item Description in Inventory Customer Item form is too long

for Customer ’&CUSTNAME’ and Customer Item ’&CUSTITEM’. It has been truncated to 30

characters. Original Customer Item : &ORIG_CUSTITEMDESC Value exported :

&NEW_CUSTITEMDESC

[APP–44218] Commodity Code ’&CCODE’ in the Inventory Commodity Code form needs to be 16

characters or less to export commodity code information to CARaS.

[APP–44219] Item Number length for Item ’&INVITEM’ in the Inventory Item form should be

&PART_LENGTH characters or less, to export item information to CARaS.

[APP–44220] Country ’&COUNTRY’ for Customer ’&CUST_NAME’ and Address ’&ADDR_1’ in

the Receivables Customers form, needs to be 10 characters or less, to export address information to

CARaS.

[APP–44221] Detail Container Type ’&DET_CONT’ in EDI Code Conversion Values form for

Customer ’&CUSTNAME’ and Customer Item ’&CUSTITEM’ needs to be 5 characters or less to

export item information to CARaS.

[APP–44235] EDI Location ’&EDI_LOCN’ for Customer ’&CUST_NAME’ and Address

’&ADDR_1’ in the Receivables Customers form, needs to be 15 characters or less, to export address

cross–reference information to CARaS.

[APP–44237] Master Container Type ’&MAST_CONT’ for Customer ’&CUSTNAME’ and

Customer Item ’&CUSTITEM’ in the EDI Code Conversion Values form needs to be 5 characters or

less to export item information to CARaS.

[APP–44239] Postal Code ’&POSTAL_CODE’ for Customer ’&CUST_NAME’ and Address

’&ADDR_1’ in the Receivables Customers form, needs to be 15 characters or less, to export address

information to CARaS.

[APP–44240] Inventory Item Number &INVITEM for Customer &CUSTNAME in Inventory Items

form needs to be 30 characters or less to export item information to CARaS.

[APP–44242] Returnable Container Part Number for Customer ’&CUSTNAME’ and Inventory Item

’&INVITEM’ in the Inventory Items form needs to be 30 characters or less to export item

information to CARaS.

[APP–44246] EDI Location Code for Customer ’&CUSTNAME’ and Group ’&GROUPCODE’ in

the Receivables Addresses form needs to be 5 characters or less to export item information to

CARaS.

[APP–44248] Reference 2(Destination Abbreviation) ’&TP_REF_EXT2’ for Trading Partner

’&TP_CODE’ in Group ’&TP_GROUP_CODE’ in the EDI Trading Partner Definition form, needs

to be 5 characters or less, to export address information to CARaS.

[APP–44251] There are multiple Automotive Address extension records for Customer

’&CUST_NAME’ and Address ’&ADDR_1’ in the Automotive Address Extensions form. A single

address extension record is required to export information to CARaS.

[APP–44254] Master container ’&CONTAINER_PART_NUMBER’ and Load Item

’&LOAD_PART_NUMBER’ for Customer Item ’&CUSTOMER_ITEM_NUMBER’ has multiple

relationships setup. A single relationship is required to export to CARaS.

[APP–44255] Master container ’&CONTAINER_PART_NUMBER’ and Load Item

’&LOAD_PART_NUMBER’ for Customer Item ’&CUSTOMER_ITEM_NUMBER’ has multiple

relationships setup. A single relationship is required to export to CARaS.

[APP–44270] Ending Automatic Trading Partner Export. File name for export was ’&FNAME’ in

path ’&PATHNAME’.

[APP–44277] Unknown Error in Transfer. Value for debugging are Package Name =

’&PACKAGE_NAME’. Location = ’&LOCATION’. Oracle Error = ’&ORACLE_ERROR’.

Type = ’&TYPE’. Table = ’&TAB’. File = ’&OUTPUT_FILE’. Description =

’&DESCRIPTION’. Field Value = ’&FIELD_VALUE’.

[APP–44287] EDI Cross reference information has not been setup for this Unit Of Measure. Please

setup this Cross reference.

[APP–44289] Ending Automatic Address Cross–reference Export. File Name for Export was

’&FNAME’ in path ’&PATHNAME’.

[APP–44293] Addr

Auto

Ext Cus No/Add Name

[APP–44294] Customer No/Item Number

[APP–44297] Converted Standard Pack Unit of Measure Code ’&CSP_UOM’ for Customer Item

’&CITEM’ must be exactly 2 characters in the Automotive Customer Items form, to export item

information to CARaS.

[APP–44301] Commodity Code has been left blank and is a required field. Please enter a valid

value in this field.

[APP–44302] Customer Name has been left blank and is a required field. Please enter a valid value

in this field.

[APP–44303] Trading Partner Group Code has been left blank and is a required field. Please enter a

valid value in this field.

[APP–44304] The customer ’&CUSTOMER_NAME’ is not part of any group. Please add this

customer to a group.

[APP–44501] Concurrent program &CONC_NAME returned error. Parameters: &PARAMETERS.

Contact your system administrator for assistance.

[APP–44502] Too many arguments. Expected: &NUM_EXPECTED Actual: &NUM_ACTUAL.

Contact your system administrator for assistance.

[APP–44503] Missing required argument: &ARG. Please note the error and the actions you are

trying to perform. Please contact your system administrator for assistance.

[APP–44505] You have provided insufficient arguments to the Release Accounting Demand

Processor program. Please provide the following four arguments: External Customer Name,

External Destination Name, Transmission Name, Archive Flag.

[APP–44506] You have provided an external ship–to address without an external customer name.

Please resubmit the concurrent request with a valid external customer name.

[APP–44600] &ROUTINE–&ERR_NUMBER. Please take note of both this error number and the

actions you were trying to perform. Contact your system administrator for further assistance.

[APP–44601] &ROUTINE–&ERR_NUMBER: &SQL_ERR. Please take note of both this error and

the actions you were trying to perform. Contact your system administrator for assistance.

[APP–44602] For transmission &TRANSMISSION_NAME, unable to validate customer

&CUSTOMER_EXT without a valid external address. A valid external address must be included in

the transmission.

[APP–44603] Line records in table &TABLE_NAME with order number &ORDER_NUMBER,

order type &ORDER_TYPE in transmission &TRANSMISSION_NAME could not be locked.

Please run the Release Management Demand Processor program again.

[APP–44604] Records in table &TABLE_NAME for order number &ORDER_NUMBER, order

type &ORDER_TYPE could not be locked. Please run the Release Management Demand Processor

program again.

[APP–44605] Records in table &TABLE_NAME with forecast &FORECAST_DESIGNATOR

could not be locked. Please run the Release Management Demand Processor program again.

[APP–44606] Duplicate requirements exist for customer &CUSTOMER, address &ADDRESS,

customer item &CUSTOMER_ITEM, on &PLANNED_DATE in transmission

&TRANSMISSION_NAME.

[APP–44607] For transmission &TRANSMISSION_NAME, unable to resolve the EDI cross

reference address for external customer &CUSTOMER_EXT, and &DEST_TYPE external address

&DESTINATION_EXT. Please verify your EDI trading partner cross references.

[APP–44608] Unable to resolve the EDI cross reference for &EXT_NAME external value

&EXT_VALUE for transmission &TRANSMISSION_NAME. Please verify your EDI trading

partner cross references.

[APP–44609] For transmission &TRANSMISSION_NAME, external customer

&CUSTOMER_EXT does not have a valid forecast designator. Please create a forecast designator

for this customer and assign it to the Release Management source list.

[APP–44610] For transmission &TRANSMISSION_NAME, order number &ORDER_NUMBER,

order type &ORDER_TYPE does not exist for external customer &CUSTOMER_EXT.

[APP–44611] For transmission &TRANSMISSION_NAME, customer &CUSTOMER, ship–to

&SHIP_TO_EXT, order type name &ORDER_TYPE_NAME, and order number

&ORDER_NUMBER, a blank customer_item_ext was passed with an ato_model_method other

than 3.

[APP–44612] Customer item &CUSTOMER_ITEM for customer &CUSTOMER and address

&ADDRESS is invalid in transmission &TRANSMISSION_NAME. Please create your customer

items for each customer and/or address.

[APP–44613] Unable to resolve default model for order number &ORDER_NUMBER, order type

&ORDER_TYPE in transmission &TRANSMISSION_NAME. Customer item

&CUSTOMER_ITEM for customer &CUSTOMER does not have a valid default model.

[APP–44614] Transmission &TRANSMISSION_NAME in table &TABLE_NAME cound not be

locked. Please run the Release Management Demand Processor program again.

[APP–44615] Multiple forecasts exist in the Release Management source list for customer

&CUSTOMER, ship to address &ADDRESS1, bill to address &ADDRESS2. Please assign only

one forecast to this source list for the listed values.

[APP–44616] Demand Management was unable to change or delete line number &LINE_NUMBER

on order number &ORDER_NUMBER, order type &ORDER_TYPE. This line has been

manufacturing or pick released.

[APP–44617] Exceptions occurred while importing order number &ORDER_NUMBER and order

type &ORDER_TYPE for transmission &TRANSMISSION_NAME. Please review the following

text generated during the OE Import process and review the request log of Process Demand:

&OE_IMPORT_ERROR_TEXT

[APP–44618] Warnings exist for order number &ORDER_NUMBER, order type &ORDER_TYPE,

transmission &TRANSMISSION_NAME. Please review the following text generated during the

OE Import process and review the request log of Process Demand: &OE_IMPORT_ERROR_TEXT

[APP–44619] Exceptions occurred while interfacing lines for order number &ORDER_NUMBER,

order type &ORDER_TYPE, and transmission &TRANSMISSION_NAME. Please review the

following text generated during the OE Import process and review the request log of Process

Demand: &OE_IMPORT_ERROR_TEXT

[APP–44620] Warnings exist for lines on order number &ORDER_NUMBER, order type

&ORDER_TYPE, transmission &TRANSMISSION_NAME. Please review the following text

generated during the OE Import process and review the request log of Process Demand:

&OE_IMPORT_ERROR_TEXT

[APP–44621] Demand Management was unable to change or delete the quantity for requirement

&REQUIREMENT_EXT on order number &ORDER_NUMBER, order type &ORDER_TYPE.

The remaining quantity cannot be cancelled as this order line has been manufacturing released,

partially pick released or ship confirmed.

[APP–44622] Demand Management was unable to change or delete order line &LINE_NUMBER

for order number &ORDER_NUMBER and order type &ORDER_TYPE. This line is sequenced

and has already been assigned to a delivery or has included items which have been assigned to a

delivery.

[APP–44624] Demand Management was unable to change order line &LINE_NUMBER for order

number &ORDER_NUMBER, order type &ORDER_TYPE. This line has already been assigned to

a delivery, manufacturing released or partially pick released.

[APP–44625] Demand Processor failed to lock required records in Oracle Order Entry for order

number &ORDER_NUMBER, order type &ORDER_TYPE. Please run the Release Management

Demand Processor program again

[APP–44626] Demand Management was unable to resolve default model for order number

&ORDER_NUMBER, order type &ORDER_TYPE in transmission &TRANSMISSION_NAME.

[APP–44627] For transmission &TRANSMISSION_NAME, Demand Management was unable to

add, change, or delete order lines on the closed order number &ORDER_NUMBER, order type

&ORDER_TYPE. Please assign an open sales order to the appropriate customer items.

[APP–44628] For transmission &TRANSMISSION_NAME, requirements for customer item

&CUSTOMER_ITEM and Schedule Ship Date &PLANNED_SHIP_DATE exceed the assigned

demand tolerances. Please verify the assigned tolerance against this percentage change of

&PCT_DELTA

[APP–44629] Transmission ’&TRANSMISSIONNAME’ already exists in the

RLA_DEMAND_INTERFACE table.

[APP–44630] No data found in file ’&FILENAME’.

[APP–44631] Successfully loaded &RECORDCOUNT record(s) from file ’&FILENAME’ in

’&DIRECTORY’

[APP–44632] File not found. ’&FILENAME’ not found in ’&DIRECTORY’.

[APP–44633] Cannot read file ’&FILENAME’ in ’&DIRECTORY’. Please verify the file is in the

correct directory and has the appropriate access priviledges

[APP–44634] For transmission &TRANSMISSION_NAME, Demand Management was unable to

add, change, or delete order lines on order number &ORDER_NUMBER, order type

&ORDER_TYPE. The order has not been booked. Please assign a booked sales order to the

appropriate customer items.

[APP–44635] For transmission &TRANSMISSION_NAME, unable to resolve the EDI cross

reference customer for external customer &CUSTOMER_EXT, and external address

&DESTINATION_EXT. Please verify your EDI trading partner cross references.

[APP–44636] Unable to process forecast for organization &ORGANIZATION_ID and

forecast_designator &FORECAST_DESIGNATOR. MRP API failure.

[APP–44637] Unable to process forecast for organization &ORGANIZATION_ID and

forecast_designator &FORECAST_DESIGNATOR. The following message text was provided:

&MESSAGE_TEXT

[APP–44638] For order number &ORDER_NUMBER, order type &ORDER_TYPE, item number

&ITEM_NO and planned shipment date &PLANNED_SHIPMENT_DATE, the quantity of the new

requirement &NEW_QTY is less than the summed quantity of past due requirements. The quantity

of the new line must be equal to or greater than the total quantity of previously linked requirements.

[APP–44639] For transmission &TRANSMISSION_NAME, customer &CUSTOMER, ship–to

&SHIP_TO_EXT, order type name &ORDER_TYPE_NAME, and order number

&ORDER_NUMBER, the header level Purchase Order Number does not match the line level

Purchase Order Number.

[APP–44640]

For Customer &Customer_id and Transmission Name &Transmission_Name and ShipSiteId

&ship_id and BillSiteID &Bill_id the Transaction Set Purpose Code

&TRANSACTION_SET_PURPOSE_CODE is invalid.

[APP–44641] Demand Management was unable to change or delete order line &LINE_NUMBER

for order number &ORDER_NUMBER and order type &ORDER_TYPE. This line has already

been departure planned.

[APP–44642] You are changing order line &LINE_NUMBER for order number

&ORDER_NUMBER and order type &ORDER_TYPE. This line has already been assigned to a

delivery or has included items which have been assigned to a delivery.

[APP–44643] External Ship To should be specified for External Customer Name

&CUSTOMER_EXT.

[APP–44644] For transmission &TRANSMISSION_NAME and order type &ORDER_TYPE, an

invalid order number &ORDER_NUMBER has been specified.

[APP–44645] Unable to resolve the quantity for the default model of order number

&ORDER_NUMBER, order type &ORDER_TYPE, and customer item &CUSTOMER_ITEM, in

transmission &TRANSMISSION_NAME.

[APP–44646] Demand Management was unable to change or delete order line &LINE_NUMBER

for order number &ORDER_NUMBER and order type &ORDER_TYPE. This line has included

items which have been departure planned.

[APP–44647] Demand Management was unable to change or delete order line &LINE_NUMBER

for order number &ORDER_NUMBER and order type &ORDER_TYPE. This line has included

items which have been pick released.

[APP–44648] No records available to be processed for transmission ’&TRANSMISSIONNAME’

[APP–44650] There were some errors in Loading the records from file(s). Please review Demand

Management Exception Report for the Exceptions.

[APP–44651] &FILE_COUNT File(s) were loaded Successfully. Please review Demand

Management Exception Report If there were more Files.

[APP–44652] There were no files available to Load.

[APP–44653] &REC_COUNT record(s) have been deleted from Interfrace Table.

[APP–44660] For order number &ORDER_NUMBER and order type &ORDER_TYPE, the

quantity of the new requirement is greater than the summed quantity of past due requirements. The

new lines have been linked to the past due requirements.

[APP–44661] An internal error occured when trying to open ’&FILENAME’ in ’&DIRECTORY’.

Please contact your system administrator.

[APP–44662] Invalid filehandle for ’&FILENAME’ in ’&DIRECTORY’ is being used. Please

contact your system administrator.

[APP–44663] Unable to open ’&FILENAME’ in ’&DIRECTORY’ with existing file permissions.

Please verify the file is being opened in the correct mode and has the appropriate access privileges.

[APP–44664] Cannot write to file ’&FILENAME’ in ’&DIRECTORY’. Please verify the file is in

the correct directory and has the appropriate access privileges.

[APP–44665] For order number &ORDER_NUMBER, order type &ORDER_TYPE, item number

&ITEM_NO and planned shipment date &PLANNED_SHIPMENT_DATE, the quantity of the new

requirement &NEW_QTY is equal to the summed quantity of past due requirements. Hence a new

line will not be inserted for this requirement.

[APP–44666] For order number &ORDER_NUMBER, order type &ORDER_TYPE, item number

&ITEM_NO and planned shipment date &PLANNED_SHIPMENT_DATE, the quantity of the new

requirement &NEW_QTY is greater than the summed quantity of past due requirements. Hence a

new line will be inserted for the difference.

[APP–44667] For the transmission &TRANSMISSION_NAME, the customer_item

&CUSTOMER_ITEM is not enabled in the organization &ORGANIZATION_CODE.

[APP–44668] For Transmission ’&TRANSMISSION_NAME’, there are &NUM records that are

neither Firm (disposition S), nor Forecast (disposition F).

[APP–45007] Cannot acquire serial port for dialing.

[APP–45010] The profile value for the Modem Serial Port is not found. Please select the default

serial port in the Personal Profiles window before proceeding.

[APP–45012] The OSM: Freight Carrier profile value is inconsistent with the OSM: Freight Carrier

Source and the OSM: Collateral Organization profile values. Please have your system administrator

correct these values.

[APP–45018] KEY user exit failed to create &KEY key.

[APP–45045] You must define at least one organization to be able to run Oracle Sales and

Marketing.

[APP–45048] Merge records exist for this batch. Do you want to delete them and create new ones?

[APP–45049] The file name extension must be ”.doc”. A valid filename would be letter.doc

[APP–45080] You do not have access to this window. To gain access to it, please ask your system

administrator to link your Employee Name to your Application Object Library User Name.

[APP–45081] Oracle Order Entry rejected fulfillment request &REQ_ID. All lines must include an

item number.

[APP–45085] Use your word processor to merge file &FILE_NAME with letter &LETTER_NAME.

[APP–45092] Aborting Program. Too many errors.

[APP–45099] fdpscr: Error calling Order Import: &ERROR

[APP–45105] Order Import not called due to loading errors.

[APP–45112] Skipped request &REQUEST due to errors.

[APP–45160] Error! Cannot run in Restart mode. Please rerun in Total or New mode.

[APP–45161] Error! Submit child process failed. Command = &COMMAND &ERRBUF

[APP–45171] Error! Cannot process account (Account Code = &NUM).

[APP–45172] Error! Cannot process lead (Lead Number = &NUM).

[APP–45196] Incorrect arguments passed to &ROUTINE.

[APP–45197] Cannot allocate memory in &ROUTINE for &REASON.

[APP–45198] Cannot close file &FILE_NAME in &ROUTINE.

[APP–45199] Cannot create file path for &OBJECT in &ROUTINE.

[APP–45200] Cannot read from file &FILE_NAME in &ROUTINE.

[APP–45201] Cannot write to file &FILE_NAME in &ROUTINE.

[APP–45205] &ROUTINE encountered an error returning from &BADROUTINE.

[APP–45206] &ROUTINE encountered a warning when returning from &BADROUTINE.

[APP–45207] SQL Error occurred

[APP–45208] SQL Error occurred. Please evaluate the Column, Operator, and Value fields.

[APP–45209] Wrong number of arguments passed. This program requires &NUM arguments.

[APP–45212] The phone number you entered does not match any phone format you have set up, or

you have not yet specified the country associated with this number. Do you wish to continue?

[APP–45213] Cannot create Parameter List &LIST_NAME

[APP–45216] You cannot define an inventory kit in OSM.

[APP–45219] The Order Source setup for the Oracle Order Entry Interface is either not specified or

invalid.

[APP–45220] The Order Type setup for the Oracle Order Entry Interface is either not specified or

invalid.

[APP–45242] You have not been allowed to change a customer relationship from prospect to

customer.

[APP–45243] You cannot set the relationship to be ’Existing Customer’

[APP–45259] Cannot find the &WORD_PROCESSOR word processor. Please contact your system

administrator

[APP–45268] Program aborted due to error(s).

[APP–45270] A word processor does not exists for the letter with Code &LETTER_CODE

[APP–45274] Cannot open letter &FILE_NAME. The Letter with this name does not exist or you

do not have read access. Contact your system administrator to verify that the Letter Location Path

specified in the Word Processor Form is correct and that you have read access to the file system.

[APP–45275] Cannot create letter &FILE_NAME. The Letter Location Path is incorrect or you do

not have write access. Contact your system administrator to verify that the Letter Location Path

specified in the Word Processor Form is correct and that you have write access to the file system.

[APP–45281] There is a time conflict with another &Item1. Do you want to save this &Item2

anyway?

[APP–45286] Cannot open merge file.

[APP–45287] An error occurred while interacting with Schedule+. This could be either due to

incorrect installation or incorrect access persmissions. The changes you have made have not been

propagated to Schedule+. Please ensure a Post Office and a Schedule file have been set up for you

correctly, and your password is correctly saved and is automatically entered when Schedule+ is

started.

[APP–45288] You have selected &WPNAME to create and edit this letter but &WPNAME has not

been properly installed on your PC. Please install or reinstall &WPNAME.

[APP–45289] Unable to lock all resources necessary to complete this transaction. Please retry later.

[APP–45290] The header file associated with this template could not be found. The letter will be

saved, but you will not be able to merge this letter with your data unless you specify the header file

manually. This can be done in Microsoft Word by selecting Tools:Mail Merge:Get Data:Header

Options:Open and locate the header file ’evnthead.doc’. Select ’comma’ as field delimiter and

’enter’ as record delimiter. Please notify your system administrator to link this header file to the

template.

[APP–45291] The Microsoft Word template &TNAME cannot be found. Please contact your

system administrator to verify that the file has been installed in the default template directory of

Microsoft Word.

[APP–45328] Cannot write to a log file.

[APP–45330] An error occurred when trying to save the profile values.

[APP–45331] The client number you have entered is bigger than the maximum client number

allowed. Please enter a number less than or equal to &MAX_CLIENT_NUMBER.

[APP–45332] Contact Merge not allowed here. You must be in the Contact block in find accounts

form to be able to merge contacts.

[APP–45333] Error while parsing the query statement.

[APP–45334] Query raised oracle error ORA–&ERR_NUM while execution.

[APP–45335] The rule selected to identify duplicates in this list does not have fields defined to

identify the duplicates. ”Remove Duplicate” process terminated. Define the fields in this rule or

associate a different rule with this list before starting ”Remove Duplicate” process.

[APP–45336] The priority list selected for this list does not have source names defined. ”Remove

Duplicate” process terminated. Define the source names in this priority list or associate a different

priority with this list before starting ”Remove Duplicate” process.

[APP–45337] Internal error occured while removing duplicates. Please contact your system

administrator.

[APP–45338] Do you want to remove the list source name?

[APP–45339] Do you want to change the source of the list entries in this list to &SOURCE_NAME?

[APP–45340] Address validation failed for this list entry. To ignore this entry and carry on with the

others click on the ”Continue” button.

[APP–45341] Could not transfer the list entry into Customer/Contact database. Please verify the list

entry data or contact your system administrator.

[APP–45400] The company number must be unique.

[APP–45401] The imported address (city: &CITY, county: &COUNTY, province: &PROVINCE,

state: &STATE, postal code: &POSTAL_CODE, country: &COUNTRY) must be valid.

[APP–45402] The win probability/sales stage combination must be valid.

[APP–45403] A decision date is required for opportunities or opportunity lines of status: Upside,

Forecast, Won, or Lost.

[APP–45404] Only one of the obstacle columns (obstacle or obstacle code) should be populated.

[APP–45405] Only one of the competitor columns (competitor or competitor code or competitor id)

should be populated.

[APP–45406] At least one of the credit columns (revenue amount or percent, or quota credit amount

or percent) must exist for every sales credit record.

[APP–45407] Only one of the revenue columns (revenue amount or revenue percent) should be

populated.

[APP–45408] Only one of the quota credit columns (quota credit amount or quota credit percent)

should be populated.

[APP–45409] A sales credit record must consist of either an employee or a partner, but not both.

[APP–45410] In order to find a matching contact, the activity record must also include a company

and an address.

[APP–45411] The &ROW original system reference must be unique.

[APP–45412] An unexpected error has occured during processing of the &ROW information.

[APP–45413] The &ROW information could not be processed due to errors during validation.

[APP–45414] The &ROW information could not be processed due to errors during the conversion

from values to identifiers.

[APP–45415] The column(s), &COLUMN, has an invalid value(s), &VALUE. Please insure that

the entered identifier or combination of identfiers exist in the database.

[APP–45416] The column(s), &COLUMN, must exist. The missing column is either required by

the database or required based on the data that is being imported.

[APP–45417] The API cannot convert the value, &VALUE, of the column, &COLUMN, to an

associated identifier.

[APP–45418] This quote has a changed opportunity, please validate whether you want to update the

quote line(s) with expected purchase(s) of the changed opportunity.

[APP–45419] This quote status transition does not follow the defined rules.

[APP–45420] The price list for this quote is cleared. The prices in the quote lines are invalid. Do

you wish to clear all the quote lines?

[APP–45421] The price list of this quote is changed. The prices in the quote lines may be invalid.

Do you wish to automatically re–price the quote lines?

[APP–45422] The opportunity number of this quote is changed. The quote lines may not

correspond to the new opportunity’s expected purchases. Do you wish to automatically update and

price the quote lines?

[APP–45423] Please choose the Order button to change the quote status to be Order Reviewed.

[APP–45424] Please choose the Order button to change to the quote status to be Ordered.

[APP–45425] Order validation failed: Please set the profile OSM: Quote Order Entered State.

[APP–45426] Order validation failed: You have chosen a payment type without specifying a

payment amount. Please enter a payment amount.

[APP–45427] Order validation failed: You have chosen the payment type to be Check without

specifying a check number. Please enter a check number.

[APP–45428] Order validation failed: You have chosen the payment type to be Credit Card without

specifying a credit card code. Please enter a credit card code.

[APP–45429] Successful order validation. Do you want to save this quote with status Order

Reviewed?

[APP–45430] Order validation failed: You have chosen the payment type to be Credit Card without

specifying a card holder name. Please enter a card holder name.

[APP–45431] Order validation failed: You have chosen the payment type to be Credit Card without

specifying a card number. Please enter a credit card number.

[APP–45432] Order validation failed: You have chosen the payment type to be Credit Card without

specifying a card expiration date. Please enter a card expiration date.

[APP–45433] Order validation failed: The currency for the quote does not match the functional

currency, as specified in the Oracle Order Entry profile OE: Set of Books. Please use a price list

that has the functional currency.

[APP–45434] Order validation failed: The current date does not fall between the effect start and

end date of the order type as specified in the OSM: Quote Order Type profile. Contact your system

administrator to re–set the order type in the profile.

[APP–45435] Order validation failed: Please enter an agreement.

[APP–45436] Order validation failed: The current date does not fall between the effective start and

end date of your chosen agreement. Please choose another agreement that is currently effective or

contact your system administrator to change the effective dates of your chosen agreement.

[APP–45437] Order validation failed: Please enter a purchase order number.

[APP–45438] Order validation failed: Please enter a company and account code.

[APP–45439] Order validation failed: Please enter a ship to contact person.

[APP–45440] Order validation failed: Please enter a bill to contact person.

[APP–45441] Order validation failed: The comany does not have an active status. You cannot

order for a inactive company.

[APP–45442] Order validation failed: The company account code does not have an active status.

You cannot order for an inactive account.

[APP–45443] Order validation failed: The ship to location does not have an active status. An order

cannot be shipped to an inactive site.

[APP–45444] Order vaildation failed: The bill to location does not have an active status. An order

cannot be billed to an inactive site.

[APP–45445] Order validation failed: Please enter a sales channel.

[APP–45446] Order validation failed: Please enter a price list.

[APP–45447] Order validation failed: The current date does not fall between the effective start and

end date of your chosen price list. Please choose another price list that is currently effective or

contact your system administrator to change the effective dates of your already chosen price list.

[APP–45448] Order validation failed: The currency of the quote does not match the currency of the

price list. Please choose another price list with a matching currency or change the currency of the

quote.

[APP–45449] Order validation failed: Please enter an invoicing rule.

[APP–45450] Order validation failed: Please enter an accounting rule.

[APP–45451] Order validation failed: Please enter a payment term.

[APP–45452] Order validation failed: The invoicing rule does not have an active status. Please

choose an active invoicing rule.

[APP–45453] Order vaildation failed: The accounting rule does not have an active status. Please

choose an active accounting rule.

[APP–45454] Order validation failed: The current date does not fall between the effective start and

end date of your chosen payment term. Please choose another payment term or contact your system

administrator to change the effective dates of your already chosen payment term.

[APP–45455] Order validation failed: Please enter an employee for the quote.

[APP–45456] Order validation failed: The employee does not have an active status as a sales

representative. Please choose another employee or contact your system administrator to change the

employee sales representative status to be active.

[APP–45457] Order validation failed: The current date does not fall between the effective start and

end date of the employee as a sales representative. Please choose another employee or contact your

system administrator to change the effective dates of the employee as sales representative.

[APP–45458] Order validation failed: Please enter a tax status.

[APP–45459] Order validation failed: Please enter a tax exempt reason.

[APP–45460] Order validation failed: The current date has passed the expiration date of the quote.

[APP–45461] Order validation failed: Please enter a line number for the quote line.

[APP–45462] Order validation failed: Please enter an item for the quote line.

[APP–45463] Order validation failed: Please enter a list price for the quote line.

[APP–45464] Order validation failed: Please enter a quantity for the quote line.

[APP–45465] Order validation failed: Please enter an UOM for the quote line.

[APP–45466] Order validation failed: There is not a valid discount that exists in Oracle Order Entry

to account for the difference in list and quote price. Please price the quote line again by clearing

and re–entering the same UOM value.

[APP–45467] Order validation failed: The discount for this quote line no longer exists in Oracle

Order Entry discounts. Please price the quote line again by clearing and re–entering the same UOM

value.

[APP–45468] Order validation failed: The current date does not fall between the effective start and

end date of the discount in this quote line. Please price the quote line again by clearing and

re–entering the same UOM value.

[APP–45469] Order validation failed: The discount for this quote no longer exists in Oracle Order

Entry discounts. Please choose another discount.

[APP–45470] Order validation failed: The current date does not fall between the effective start and

end date of the discount in this quote. Please choose another discount or contact your system

administrator to change the effective dates of your chosen discount.

[APP–45471] A quote has to be validated before the quote status can be changed to Ordered. Please

choose the Order button and validate order.

[APP–45472] The previous validation is no longer valid. Validating and summitting orders has to

be done on the same day. Please choose the Order button and validate order again.

[APP–45473] This quote &ORIGINAL_REFERENCE has been ordered already. The order number

is &ORDER_NUMBER. Please use Oracle Order Entry to make changes in the order.

[APP–45474] Order validation failed: An error occurred when defaulting tax code. Please check

and activate Oracle Receivables System Option: Use Tax Code at Customer Site.

[APP–45475] Please save the quote before printing it.

[APP–45476] No sales tax is calculated for this quote.

[APP–45477] An error has occurred when calculating tax. This quote is saved without tax.

[APP–45478] The prices of this quote item will expire on &EXPIRATION_DATE. Do you wish to

overwrite the quote header’s expiration date with this earlier date?

[APP–45479] The order submission has failed. This quote is not ordered.

[APP–45480] The system has made a request to submit this sales quote for order fulfillment. You

can use Request ID &REQUEST_ID to check the status.

[APP–45481] You don’t have access to this group/member forecast.

[APP–45482] An error has occured during Forecast Freeze.

[APP–45483] Some of the forecast records are locked by another user. Forecast Freeze cannot be

completed at this time.

[APP–45484] Please enter a value for Forecast Freeze Period.

[APP–45485] Please enter a value for Next Forecast Freeze Period.

[APP–45486] Forecast Freeze has been completed successfully.

[APP–45487] An error has occured while updating the profile ’OSM: Forecast Current Freeze

Period.’

[APP–45489] Sales forecasts accumulation process has failed with error code = &ERROR_CODE.

[APP–45491] Sales forecasts export–to–MRP process has failed with error code =

&ERROR_CODE.

[APP–45492] Are you sure you want to delete sales forecasts from the interface table?

[APP–45493] Are you sure you want to overwrite these existing forecasts in the interface table?

[APP–45494] Please select a forecast designator.

[APP–45495] There is no correct profile of ’OSM: Product Organization’.

[APP–45496] Please select a forecast period or a freeze period.

[APP–45497] Are you sure you want to export these sales forecasts from the interface table to MRP

System?

[APP–45498] No sales forecast designator found in the interface table.

[APP–45499] The value &NEW_AMOUNT does not fall between the allowed range of revenue

&LOWER_BOUND_AMOUNT and &UPPER_BOUND_AMOUNT with respect to the current

quantity &ORIGINAL_QUANTITY. Do you wish the system to update the quantity to

&NEW_QUANTITY?

[APP–45500] The value &NEW_QUANTITY does not fall between the allowed range of quantity

&LOWER_BOUND_QUANTITY and &UPPER_BOUND_QUANTITY with respect to the current

amount &ORIGINAL_AMOUNT. Do you wish the system to update the amount to

&NEW_AMOUNT?

[APP–45501] There is no price for this inventory item, Amount–Quantity correspondence checking

cannot be performed for this record.

[APP–45502] This new sales quota has product interest category conflicting with another sales

quota.

[APP–45503] Competitor and product already exist for this Opportunity.

[APP–46482] Some of this Prospect’s address is invalid. Changing this Prospect to a Customer will

make those addresses Inactive.

[APP–46483] Prospects Address is invalid. Cannot change the Prospect to a Customer.

[APP–47000] Depreciation has detected undistributed depreciable assets.

Cause:

Depreciation has detected assets that are depreciable but have not been distributed.

Action:

Please distribute the assets listed in the log file and rerun depreciation.

[APP–47001] Method has not been set up for the Subcomponent Life calculated.

[APP–47003] Submitted Requests &MASSCHG_ID, &AUDIT_ID

[APP–47004] You must enter a life for assets with a life–based method.

[APP–47006] You must enter an asset number or an asset category for each rate.

[APP–47007] &TYPE adjustments not allowed on CIP assets

[APP–47008] You must enter a Basic and Adjusted Rate for flat–rate methods.

[APP–47009] Error: Unable to get book_class and set_of_books_id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47010] Error: Failed to get Prorate Date and Depreciation Start Date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47011] Error: Failed to process the add_to_asset function call

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47012] Error: Failed to update the FA_TRANSACTION_HEADERS table for a Capitalized

asset

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47013] Error: Failed to terminate a record in FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47014] Error: Cannot expense change

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47015] Error: Unable to select period counter

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47019] Error in GL_CODE_COMBINATIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47020] Query the information for this book before making cost changes.

[APP–47021] Error: An invalid code combination ID was generated for row ID &row

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47022] Mass Addition ID: &Mass_addition_id ==> ** FAILED **

[APP–47023] You must use a units of production depreciation method for this book.

[APP–47026] You cannot enter a revaluation ceiling of zero.

[APP–47027] Error: Could not update Used_Flag for asset’s Production

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47028] Opening cursor for Production

[APP–47029] Fetching rows from Production

[APP–47030] Closing cursor for Production

[APP–47031] Error: Unable to get expense account from FA_CATEGORY_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47032] You must enter values for production capacity and units.

[APP–47034] You cannot amortize a prorate convention adjustment.

[APP–47035] You cannot change to a production method after you run depreciation.

[APP–47037] Cannot process Asset Number: &ASSET_NO Start Date: &START_DT End Date:

&END_DT

[APP–47038] Error: An inactive distribution has a nonzero &ACCOUNT balance: &ID_BALANCE

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47039] Error: Sum of the FA_DEPRN_DETAIL rows does not add to the

FA_DEPRN_SUMMARY row for the &ACCOUNT account. Values: &VALUES

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47040] Error: Amount inserted into FA_ADJUSTMENTS is not the requested amount

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47041] Error: Cannot back out depreciation across fiscal years

[APP–47042] Error: Unable to create &TABLE table. &SQLSTMT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47043] Error: Purge action on &TABLE table failed. &SQLSTMT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47044] Error: Failed to set archive status

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47045] Purge not allowed for &BOOK_TYPE.

[APP–47047] You cannot set Depreciate to No for units of production assets.

[APP–47048] Query Financial Info User Exit

[APP–47049] FlexBuilder: Failed to delete from &TABLE

[APP–47050] FlexBuilder : Failed to insert into &TABLE

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47051] Sign of revaluation reserve must be the same as sign of the cost.

[APP–47052] Data Error in FA_DISTRIBUTION_HISTORY

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47053] Data Error in FA_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47054] Get period range for the specified fiscal year

[APP–47055] Error: Failed to get archive status

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47058] Error: The Depreciation_Running_Flag is not set for this book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47059] Error: Unable to get the CIP cost account from FA_CATEGORY_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47060] Error: Unable to fetch records into cursor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47061] Error: Could not find prorate date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47062] Error: Could not load financial information structure

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47063] Error: Transaction Status invalid

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47064] You can only adjust depreciation for a book during the first period of the fiscal year

and before you enter any transactions.

[APP–47065] Please enter a date that is before the end of the current open period.

[APP–47067] You have to purge data for &FISCAL_YR before this year.

[APP–47068] You have to restore data for &FISCAL_YR before this year.

[APP–47069] The Fiscal Year has not been closed for the Corporate Book.

[APP–47071] The control book must have the same associated corporate book as the adjusted book.

[APP–47072] Error: could not fetch the status of the last request.

[APP–47073] Error: Invalid Request Status fetched

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47074] Error: Could not submit concurrent request

[APP–47075] Error: &MODULE – Unable to get category combination id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47076] Error: Failed to update depreciation detail for the ACE book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47077] Error: Unable to get information from FA_METHODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47078] Error: Unable to get information from FA_CALENDAR_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47079] The Adjusted Book must be a TAX book.

[APP–47080] Data Error in FA_DEPRN_METHODS. Contact System Administrator

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47081] Error: Failed to update ACE Book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47082] Error: Failed to update depreciation summary for the ACE book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47083] Failed to get upper cutoff date for Date Placed in Service

Cause:

ACE Book is not set up properly.

Action:

Set up an ACE book and ensure that the open period is the last period of the fiscal year before 1990.

[APP–47084] This table–based method is not defined for this life

[APP–47085] Error: Could not find Production amount for asset

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47086] Error: called Query Financial Information with no asset_id specified

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47088] Asset Number: &ASSET_NO does not exist in the system

[APP–47089] Error: Unable to update FlexBuilder parameters table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47090] FlexBuilder : Failed to compile the rules for function : &FUNCTION

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47092] This asset does not use a units of production depreciation method

[APP–47093] Production for the date range specified exists

You cannot enter production for a date if production information has already been entered for a date

range that includes that date.

[APP–47094] You cannot modify or delete this production because it has already been used to

calculate depreciation.

[APP–47095] Unable to calculate the subcomponent life for non–life–based method.

[APP–47099] Error: invalid mode specified

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47100] Please delete the last row only, save the deletion, and save any consecutive deletions

separately.

[APP–47101] Error fetching cursor C1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47102] Error: code combination ID passed into faxinaj() was zero

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47103] Error: An invalid selection mode was passed into faxinaj()

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47104] Error closing cursor C1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47105] Error selecting the reserve adjustments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47106] You cannot change the Method from TABLE or FLAT to PRODUCTION or

CALCULATED. Please clear the Rates and re–enter the Method.

[APP–47111] You must enter a Life Extension Factor if you are revaluing fully reserved assets.

[APP–47112] Please leave the End Year field blank for the last rate for a rule.

[APP–47113] Your first bonus rate must begin with year 1.

[APP–47114] Enter at least one asset category or number for the revaluation.

[APP–47116] This category has already been entered for this revaluation.

[APP–47117] This asset has already been entered for this revaluation.

[APP–47119] Error opening cursor DS1

[APP–47120] ERROR occurred in fadpaa routine. Asset_ID = &ASSET_ID : Dist_ID = &DIST_ID

[APP–47121] Selecting count of distribution_history records

[APP–47122] Finding the prorate period

[APP–47123] Error allocating array in &ROUTINE

[APP–47124] Updating new adjusted cost in FA_BOOKS

[APP–47125] &ROUTINE : The following asset requires adjustment but has no distribution history

records:

Asset number:

&ASSET_NUM

Asset ID:

&ASSET_ID

Book type:

&BOOK_TYPE

[APP–47126] ppadep–>faxcde, asset_id = &ASSET_ID : t_dist_total_deprn = &TOTAL

[APP–47127] Selecting transaction header

ccp_start_date:

&CPP_DATE

cp_start_date:

&CP_DATE

[APP–47130] Error: Unable to find adjustment amount for back out

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47131] Error: Unable to get current fiscal year

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47132] Error: Unable to insert as select for depreciation detail

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47133] Error: Unable to insert into fa_deprn_summary

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47134] Error: Getting adjustments for period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47135] Error: Unable to get last deprn detail record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47137] Error: Updating a deprn_detail value

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47138] Error: Selecting updated deprn_detail values

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47139] check_reserve: WARNING:

The following asset should have been fully reserved in an earlier period. Instead, it has been fully

depreciated in this period.

Asset Number:

&ASSET_NUM

Asset ID:

&ASSET_ID

Book Type:

&BOOK_TYPE

[APP–47140] Error calling fadidd: no distributions found

[APP–47141] &ROUTINE : The following asset is depreciable but has no distribution history

records:

Asset number:

&ASSET_NUM

Asset ID:

&ASSET_ID

Book type:

&BOOK_TYPE

[APP–47143] Error: Selecting deprn info (first attempt)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47144] Error: Unable to insert into FA_ADJUSTMENTS (distributions)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47146] Error: Unable to insert as select into FA_ADJUSTMENTS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47148] Error: Selecting depreciation summary records

[APP–47151] Error : PREPAREing cursor &CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47152] Error: Unable to insert into FA_ADJUSTMENTS (invoices)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47153] Flexbuilder failed to generate a new code combination

Cause:

The code combination for the generated segment values does not exist and cannot be created

because it would contain invalid segment values.

Action:

Check the account segment value you are using to generate a new code combination.

[APP–47154] Error: Unable to insert into FA_DEPRN_DETAIL table (flushing array fetch)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47156] FAMADEL–E: Error in checking FA_DELETED_MASS_ADDITIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47157] Error: Deleting from FA_MASS_ADDITIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47158] The program will rollback all the changes since the last commit

[APP–47159] This asset category has not been defined for this depreciation book.

[APP–47160] Error: Cannot select currency information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47161] Error: Unable to select number per fiscal year from FA_CALENDAR_TYPES table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47162] Distribution_source_book is null for this book

[APP–47163] Error: Unable to get new depreciation period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47164] Error: Unable to insert a new fa_deprn_periods record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47165] Error: Unable to retrieve limit from FA_CEILINGS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47166] Error getting the previously calculated depreciation reserve

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47167] Usage : FAFBUPG userid 0 Y [book type code]

[APP–47168] Error re–allocating memory in &ROUTINE

[APP–47169] This asset has no Distribution History information

[APP–47170] Unable to retrieve candidate assets

[APP–47171] Cost Initial Journal Entry terminated with error

[APP–47172] fadcje – Updating FA_ADDITIONS for candidate assets

[APP–47173] Error: Cannot select payables information from FA_ASSET_INVOICES

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47174] Cache: &COLUMN does not exist in table &TABLE

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47175] Cache: Error retrieving row from FA_CEILINGS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47176] Cache: Error retrieving row from FA_CALENDAR_TYPES table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47177] Error: Invalid value for argument &ARG_NAME passed to user exit

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47178] Cost Adjustments are not allowed on this asset

[APP–47179] Selecting count of distribution_history records

[APP–47180] Error: FETCHing cursor &CURSOR

[APP–47181] Please wait for request &REQUEST_ID in book &BOOK to complete.

[APP–47182] Failed to resubmit the concurrent request for &RESUB_TIME.

[APP–47183] A mass transaction is pending for this book. Please complete it and try again. Failed

to obtain lock on FA_BOOK_CONTROLS row for book &BOOK.

[APP–47184] Depreciation for book &BOOK has failed. Please rerun depreciation.

[APP–47185] Error: Depreciation request status &STATUS is not known.

[APP–47186] PREPAREing &CACHE_NAME statement

[APP–47187] DECLAREing cursor for &CACHE_NAME

[APP–47188] DESCRIBEing bind variables for &CACHE_NAME

[APP–47189] DESCRIBEing select list for &CACHE_NAME

[APP–47190] OPENing cursor for &CACHE_NAME

[APP–47191] FETCHing cursor for &CACHE_NAME

[APP–47192] CLOSEing cursor for &CACHE_NAME

[APP–47193] Error: selection mode specified is undefined for CLOSE CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47195] This category has already been set up for this book.

[APP–47199] You cannot clear a record that has already been saved.

[APP–47200] Error: Unable to select currency code or precision for currency code.

[APP–47203] Cannot process this transaction for book of class &CLASS.

[APP–47206] For the last year of life the rate for each period must be 1 to fully depreciate the asset.

[APP–47207] Error counting the number of distributions in ACTIVE mode

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47211] You cannot change this book to a different Book Class.

[APP–47212] You must be on the last record to create a new record.

[APP–47213] To create another set of default depreciation rules for a different date placed in service

range, you must enter a To Date Placed In Service for the most recent record and create the new

record.

[APP–47216] Only the last row can have a null ’To Date Placed in Service’

[APP–47217] To create another set of default depreciation rules, please enter a To Date Placed In

Service for this record and then insert a New Record.

[APP–47219] You cannot use Zone Erase in this zone

[APP–47221] Error getting the old_reserve from the Reserve Adjustments form

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47222] Error: Failure inserting FA_ADJUSTMENTS row

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47223] Error: Failure opening cursor FISCAL_YEAR_CR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47224] Tax Reserve Adjustment User Exit

[APP–47225] You cannot transfer lines between assets added in the current period and assets added

in prior periods.

[APP–47226] Error: The table had more columns than expected

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47227] You must set up the category with default depreciation rules for at least one date

range.

[APP–47229] Error: Unable to get the CIP cost account from FA_CATEGORY_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47230] Set up the retirement convention for this retirement date.

[APP–47231] Error executing set rollback segment statement

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47232] Error PREPAREing Set Rollback Segment statement

[APP–47233] Error recalculating depreciation reserve

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47234] Error: Failure declaring cursor FISCAL_YEAR_CR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47235] You cannot perform a Reserve Adjustment on a fully retired asset.

[APP–47236] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47237] Error: Unable to insert a new FA_ASSET_HISTORY record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47238] Error: Unable to open cursor DH_CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47239] Error: Unable to determine if the asset was added in a prior period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47240] Error: Unable to determine if the asset is retired

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47241] Error: Unable to update the expense account for the new category

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47242] Error: Unable to fetch rows using DH_CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47243] Error: Unable to get adjustments for this asset

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47244] Error: Unable to retrieve system control information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47245] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47246] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47247] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47248] Error: Unable to select last depreciation date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47249] Error: Unable to select latest summary row – 2

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47250] Error: Unable to select projection start date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47251] Error: malloc() failed to allocate dynamic memory

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47252] Unable to get the Accounting Flexfield structure for this book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47253] Error: Unable to count the number of distributions for this asset

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47254] Error: You have not set up your System Controls

Cause:

You have not set up the System Controls for your system. You cannot use Oracle Assets until you

set them up.

Action:

Please use the System Controls form to set up your system controls.

[APP–47255] You cannot move to the Adjust Asset Cost zone for SPLIT transactions

Cause:

You tried to enter the Adjust Asset Cost zone for split invoice transactions.

Action:

If you want to add this mass addition to an existing asset, enter No in the Split field.

[APP–47256] Error: The add–to–asset transaction for asset &ASSET_NUMBER would result in a

reversal in the sign of the cost of the asset

[APP–47258] Error: Unable to determine whether to calculate depreciation

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47259] You have already budgeted this Account and Category.

[APP–47264] Getting the status of the Depreciation concurrent request

[APP–47265] Depreciation for the book you specified is &STATUS

[APP–47266] Error: Unable to perform rounding for summary table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47267] There are unprocessed retirements for this book

[APP–47268] Error: Depreciation Status for this book is not ”Submitted”

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47269] Rolling back all the changes since the last commit

[APP–47270] Error executing an IMMEDIATE SQL statement

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47273] You can perform only one transaction at a time.

[APP–47274] You cannot change the cost from positive to negative, or vice versa.

[APP–47275] You cannot make a cost adjustment to a CIP asset.

[APP–47276] Error: Unable to get segment delimiter

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47278] Error: Unable to get CIP account numbers

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47279] You cannot make a change if revaluation is running or completed

[APP–47280] Data Error in FA_MASS_REVALUATIONS. Contact System Administrator

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47282] Error &FA_TREE_ERROR_NUMBER in tree handling functions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47283] Error: Unable to update Adjusted Cost in the FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47285] Error: Unable to declare cursor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47286] Error: Unable to close cursor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47287] Data Error in FA_MASS_REVALUATION_RULES

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47289] Please enter only positive units in the transfer In field.

[APP–47290] Units assigned must not exceed units available.

[APP–47291] Units transferred must not exceed units available.

[APP–47294] Please finish assigning all Units to Assign to accounts and locations before saving.

[APP–47296] Please enter a non–zero value for units.

[APP–47298] Please enter a negative value in the Unit Change field for only one distribution.

[APP–47302] You must enter a zero transfer cost for a source line with a zero cost.

[APP–47303] Please add this asset to a book before you transfer it.

[APP–47305] Please enter a transfer cost that is between zero and the source line cost.

[APP–47306] You must assign the asset to a cost center before transferring.

[APP–47309] You cannot split an invoice line item which has zero units

Cause:

You attempted to split an invoice line item with zero units.

Action:

No action necessary.

[APP–47310] Error: Lookup in FA_SYSTEM_CONTROLS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47312] You cannot transfer lines to or from this asset because it has previously had an

amortized adjustment.

[APP–47314] Error: Error in routine &ROUTINE

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47315] Error: Unable to get Unique Id

Cause:

You have a database problem.

Action:

Contact you system administrator.

[APP–47316] Error: Unable to get user id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47317] Error: Split user exit passed incorrect number of arguments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47318] You cannot split an invoice which has only one unit

Cause:

You attempted to split an invoice line item with only one unit.

Action:

No action necessary.

[APP–47319] Error: SQL error detected in main program.

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47320] Error: Failure on STORELONG user exit

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47321] This category combination has not been defined.

[APP–47322] Error: Failed to get username

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47326] Error: Unable to set up the Accounting Flexfield

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47327] Error: Unable to set up &PROGRAM program

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47328] Error: Unable to execute SQL statement

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47329] Unable to execute SQL statement.

[APP–47332] Error: Failed to get request id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47333] You cannot perform this transaction because the asset is fully retired. Choose a book

in which you have not yet retired the asset, or reinstate the asset, and then perform the transaction.

If you wish to cancel or undo the retirement, please query it first.

[APP–47334] You entered other transactions for this asset after this date.

[APP–47335] Please run the Gain/Loss Program before performing this transaction.

[APP–47336] Error: Failure on QUERYLONG user exit

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47339] You can perform only one prior period transaction in each period.

[APP–47350] You cannot add a CIP asset to this category and book because they do not have CIP

accounts set up.

[APP–47353] Unable to allocate memory.

[APP–47354] Message is not defined in dictionary

[APP–47358] You cannot query in this form.

[APP–47362] Error: Invalid Rate Source Rule

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47364] The Depreciation Method and Life you entered are not set up in the Depreciation

Rates window.

[APP–47365] Depreciation method and rate are not set up.

[APP–47369] Error: Invalid Rate Source Rule – must be FLAT or TABLE

Cause:

You have a database problem. This method has a depreciation basis rule of NBV and the rate source

rule is not FLAT or TABLE.

Action:

Contact your system administrator.

[APP–47370] You must enter an account of type Asset.

[APP–47371] You must enter an expense account.

[APP–47372] Error: Failed to find &ITEM

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47373] You have made no changes that you need to commit.

[APP–47376] Error: Invalid Calculation Basis Rule

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47377] Error: Unable to find Associated Corporate Book for this book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47380] Unable to get the flexfield structure. Verify that the flexfield is set up.

[APP–47383] You cannot enter a future Date Placed In Service.

[APP–47384] Error: GETGLOBAL user exit failure

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47385] Error: Unable to get value from field &FIELD_NAME

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47386] Error: Unable to get segment number from GL_ACCOUNT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47387] Error: Unable to open output file

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47388] Error: Unable to get request id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47389] Error: Unable to get User Id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47390] Error: Unable to write to output file

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47393] You cannot perform this transaction because the asset is fully reserved.

[APP–47395] Error: Unable to get active column

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47396] Error: Unable to connect to the database

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47397] Error: Unable to create a multi flex code

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47398] Please enter values for all the required fields before you proceed.

[APP–47399] Submitting your report to the Concurrent Manager

[APP–47400] You cannot date your transaction in a future period.

[APP–47401] You cannot perform transactions on any assets in a book for which depreciation is

running.

[APP–47403] Error: Unable to select system date (sysdate)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47404] Error: Unable to get unique ID for &TOKEN.

[APP–47405] Error: Unable to commit to the database

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47407] Units retired cannot exceed current units.

[APP–47408] You cannot partially retire CIP assets.

[APP–47411] Error: &ACTION on &TABLE table failed.

[APP–47412] Error: &PROGRAM did not get enough arguments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47413] &MODULE: Fail to &PROCESS asset &ASSET

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47416] Distribution lines are out of balance

Cause:

The sum of the distributed units is not equal to the total units of the asset that you entered on the

Depreciation Books form.

Action:

Use the Transfers form to change the distributions so that the distributed units matches the total

units of the asset.

[APP–47418] You cannot retire this asset because an adjustment is pending

Cause:

Oracle Assets does not allow you to perform an expensed adjustment followed by a retirement in a

single period.

Action:

Perform your retirement in a later period.

[APP–47419] Some retirement transactions are pending. Please run the Calculate Gains and Losses

program. If you wish to cancel or undo the retirement, please query it first.

[APP–47420] Trade In Asset Number cannot be the asset you are retiring.

[APP–47423] This asset is not assigned to any depreciation books

Cause:

You tried to retire an asset that you have never assigned to a depreciation book.

Action:

To remove the asset from Oracle Assets, find it on the Additions form and then use \ Row Delete.

[APP–47424] Please enter a Straight–line Method and Life

Cause:

You depreciated this asset using a non–straight–line method. Oracle Assets calculates your gains

and losses for tax purposes, and these calculations require you to assign a straight–line method and

life to assets in your tax books.

Action:

Enter a straight–line method and life for this asset.

[APP–47425] &MODULE: Failed to get &INFO information for asset &ASSET

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47426] &MODULE: Fail to &ACTION &TYPE adjustments for asset &ASSET

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47427] Please enter a transaction date in the current fiscal year.

[APP–47430] You can only retire by cost in tax books.

[APP–47431] Cost retired cannot exceed current cost nor equal zero.

[APP–47434] You must post your mass additions before you can retire this asset.

[APP–47440] You already reinstated this asset

[APP–47442] You must define a Prorate Period for this Date Placed In Service.

[APP–47444] Submitted requests: &PROJ_ID, &REP_ID

[APP–47445] This asset is already in this book.

[APP–47446] Please clear this block before you enter the previous block.

[APP–47448] You may want to start your projection in or after the current period. Prior period

projection results may differ from your historical results.

[APP–47449] Error: Unable to insert the Projection results

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47450] Error: Unable to insert the Projection results on second attempt

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47451] Error: Unable to get period names

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47452] Error: Unable to get prorate information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47453] Error: Unable to insert projection results

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47454] Error: Unable to open cursor to get asset information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47455] Error: Unable to open cursor to get period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47456] Error: Unable to get period name

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47457] Error: Unable to get asset information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47458] Error: Unable to get book information from FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47459] Error: Unable to get depreciation start date information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47460] Error: Unable to get the first period in the projection

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47461] Error: Unable to get the last period in the projection

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47462] Error: Unable to verify period number

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47463] Error: Unable to close the cursor used to select period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47464] Error: Unable to Commit rows to FA_PROJ_INTERIM table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47465] Error: Unable to create Depreciation Projections interim table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47466] Error: Unable to Drop the previous projection interim table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47467] Error: Unable to get assets

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47473] Please define your calendar for the projection duration

Cause:

You tried to project into future periods for which you have not yet defined calendar periods.

Action:

Define your fiscal years for the duration of your projection and then define calendar periods for the

duration of your projection.

[APP–47478] This Asset Number does not exist

[APP–47479] To cancel, use the Menu to choose another form

[APP–47480] Please enter an account number

[APP–47487] Please enter a number of periods that is greater than zero.

[APP–47495] Invalid asset life

Cause:

You entered a negative value for Years.

Cause:

You entered a value for Months that is not between zero and eleven.

Cause:

You did not enter a value for Years or Months.

Action:

Enter a value for Years that is not negative and enter a value for Months that is between zero and

eleven.

[APP–47496] Please enter Time in the format HH:MM:SS (i.e. 14:58:04)

Cause:

You entered time in an incorrect format.

Action:

Enter a value for time using the format HH:MM:SS, where HH is a two digit number for hours from

zero to 23, MM is a two digit number for minutes from zero to 59, and SS is a two digit number for

seconds from zero to 59.

[APP–47499] Error: Unable to submit Concurrent Process.

[APP–47504] Please enter a value for Years that is greater than zero.

[APP–47509] Please enter all the rates for this method.

[APP–47510] Please enter a value for Months that is between 0 and 11.

[APP–47512] The sum of the annual rates for a period must equal 1.

[APP–47522] Error: Unable to check: &ACTION for asset: &ASSET

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47523] Asset Number: &ASSET_NO not processed. Other transactions exist

Cause:

This asset was not processed because there are other transactions on it after the given date.

Action:

No action necessary.

[APP–47524] From and To fields are identical for all selection criteria.

[APP–47525] Units for Asset: &ASSET are out of balance

Cause:

The units for this asset are out of balance.

Action:

Use the Transfers form to balance the units.

[APP–47527] Please enter a Date in the current period.

[APP–47528] Please enter both the From and To fields, or neither.

[APP–47529] Asset Number: &ASSET_NO processed

[APP–47530] You can perform a mass transfer only once.

[APP–47531] Error: Unable to update transaction type code to Addition/Void

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47532] Asset Number: &ASSET_NO Unable to process

Cause:

You did not set up the asset category in your tax book, or you did not define a prorate period for this

date placed in service.

Action:

Use the Asset Categories form to make sure that you have set up the asset category in your tax book.

Action:

Use the Calendars form to make sure you have defined a prorate period for the asset’s date placed in

service.

[APP–47533] Asset Number: &ASSET_NO not processed

Cause:

The Asset was not processed by Mass Transfer.

Action:

No action necessary.

[APP–47534] Error: Unable to update FA_MASS_CHANGES with request id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47535] Error: Unable to get username

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47538] Error: Unable to update old FA_BOOKS records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47539] Error: Could not rollback transactions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47540] Error: Unable to get request id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47541] Error: Could not select date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47542] Error: Unable to define main select statement

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47543] Error: Aborted &ERROR_COUNT transactions with errors

[APP–47544] Error: Unable to get transaction header ID for Mass Change

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47545] Processed &ASSET_COUNT transactions successfully

[APP–47546] Error: Unable to create new FA_BOOKS records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47547] Error: Unable to get company code or sysdate

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47548] No depreciation books are set up to allow mass changes

Cause:

You cannot use Mass Change because the Allow Mass Changes field in the Book Controls form is

set to No for all depreciation books.

Action:

Find the book in which you want to perform a mass change in the Book Controls form and change

the value of the Allow Mass Changes field to Yes.

[APP–47549] Error: Could not test/check for post–dated transactions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47550] Error: Could not test/check for post–submit transactions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47553] Error: Unable to fetch transactions for main select statements

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47555] You can only reverse capitalize assets added in the current period.

[APP–47556] Mass Change program encountered over 100 errors. Program aborted

Cause:

Mass Change program was aborted because the program detected more than 100 transaction errors.

Action:

Contact your system administrator.

[APP–47557] Assets have changed since you previewed your mass changes

Cause:

You have manually changed one or more of your assets since you ran the Preview Mass Change

program. The Mass Change program will skip those assets which have changed.

Action:

Re–run the Preview Mass Changes program to reflect the current state of your assets. Or, manually

change those assets which are skipped by the Mass Change Program.

[APP–47558] Please enter at least one change criterion.

[APP–47560] Error: Could not commit FA_MASS_CHANGES update

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47561] Error: Failed to create an unique transaction header id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47562] Error: Could not insert into FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47563] No mass additions are ready to post into this book

Cause:

No mass additions have the status POST for this book. You can give a status POST when you have

entered all necessary information.

Action:

Use the Create Mass Additions form (in Oracle Payables) to create new mass additions. Use the

Prepare Mass Additions form to examine the mass additions and add any missing information.

Change the status to POST by entering POST in the Queue name field for mass additions which are

ready to become assets.

[APP–47564] You cannot undo a split if you already posted part of the split mass additions.

[APP–47565] Error: Unable to determine if the asset was added in current period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47566] Enter all required fields before posting this Mass Addition

Cause:

You tried to post a mass addition before first entering all required fields on the Prepare Mass

Additions form.

Action:

Make sure that you have entered a value in the following required fields: Asset Type, Description,

Location, Expense Account, Units, Cost, Date Placed In Service, Depreciate, and Split.

[APP–47567] Error: Unable to insert records in FA_MASS_ADDITIONS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47568] Error: Unable to get mass addition id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47569] No mass additions are in the DELETE queue for this book

Cause:

You tried to run the Mass Additions Delete program with no mass additions to delete for the book

that you entered.

Action:

No action necessary.

[APP–47576] Please enter a destination asset or clear the Adjust Asset Cost Zone

Cause:

You did not enter a destination asset for this mass addition.

Action:

Assign a destination asset to this mass addition in the Destination Asset zone.

[APP–47577] This Asset Number does not exist

Cause:

The asset number you entered does not exist.

Action:

Verify that the asset number is correct.

[APP–47578] Invalid CIP asset category

Cause:

The specified asset category is incompatible with a CIP asset.

Action:

Change either the asset type or the asset category.

[APP–47579] You must enter the category and description before reclassifying an existing asset to

that of the mass addition.

[APP–47580] Error: Invalid asset type

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47581] Error: Invalid data retrieved from database

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47582] Error: Invalid posting status for mass addition

Cause:

You cannot post a merged child or split parent. If you merge a mass addition, you can post only the

merged parent. Or, if you split a mass addition, you can post only the split child.

Action:

Set the posting status of the merged parent or the split child to POST.

[APP–47583] Error: Invalid queue name for mass addition

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47584] This asset is not assigned in the same book as the mass addition

Cause:

The asset is not in the same corporate book as the mass addition.

Action:

Assign the mass addition to an asset in the corporate book.

[APP–47585] You cannot assign an expensed mass addition to an asset.

[APP–47586] You cannot assign this mass addition to other assets

Cause:

This invoice is either split or merged into other invoice lines. You cannot assign this invoice to other

assets.

Action:

Undo the split or merge if you want to assign this invoice to an asset directly.

[APP–47587] This invoice line is already assigned to the parent asset

Cause:

This invoice line is already assigned to a parent asset and you cannot add it to another existing asset.

Action:

To add this invoice line to another asset, first clear the Parent Asset Number field.

[APP–47589] Warning: Invalid units. Mass addition created with 1 unit

Cause:

The invoice line from which you created a mass addition has units greater than the limit of 9999,

null units, or fractional units. Therefore, Oracle Assets cannot use the invoice units for the Mass

Addition. The mass addition was created with one unit.

Action: Use The Prepare Mass Additions form to enter a value for units between 1 and 9999.

[APP–47590] Payables Units: [Payables Units]

[APP–47591] Cost adjustments are not allowed on this asset

Cause:

You tried to adjust the cost of an asset that is either fully retired, fully reserved, or has a pending

retirement.

Action:

No action is needed if the asset is fully retired or fully reserved. If the asset has a pending

retirement, submit the Calculate Gain/Loss program to process the retirement. When the concurrent

process finishes, make your cost adjustment.

[APP–47594] The asset’s category is not eligible for ITC in this book. Please make the category

eligible for ITC in the Asset Categories form and the book eligible for ITC in the Book Controls

form.

[APP–47595] You cannot assign ITC to an asset that has a cost ceiling.

[APP–47596] Function not currently available

[APP–47601] Error: Lookup in PO_VENDORS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47602] Error: Oracle Assets

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47603] Error: TRXHEADER date_effective

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47604] Error: Unable to generate a TRANSACTION_HEADER_ID

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47605] Error: UPDATE_HEADER in the Books form

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47606] Error: update instead of insert

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47608] Error: Unable to update books record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47609] Error: Unable to update distributions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47610] Error: Unable to update transfer details record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47611] Error: Unable to use NEWFRM

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47612] Error: Unable to select the CAPITALIZE_FLAG

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47613] Error: GL_PERIOD_FULLY_RESERVED

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47614] Error: Unable to insert into the FA_DEPRN_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47615] Error: Unable to insert into FA_DEPRN_SUMMARY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47616] Error: Unable to run Amortized_User_Exit

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47617] Error: Unable to run Expensed_User_Exit

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47618] Error: Unable to save because retirements are pending

[APP–47619] Error: Unable to update the adjustment required status

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47620] Error: Unable to get book control information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47621] Error: Unable to get book information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47622] Error: Unable to get period name from FA_DEPRN_SUMMARY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47623] Error: Unable to get the location structure

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47624] Error: Unable to obtain Unique ID

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47625] Error: Unable to insert a book record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47626] Error: Unable to delete retirement record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47627] Error: Unable to find book control record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47628] Error: Could not find routine faufpp

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47629] Error: Unable to find the form path

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47630] Error: Unable to calculate Recoverable Cost

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47631] Error: Unable to generate year of life

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47632] Unable to generate depreciation start date. Please verify that your calendars and

prorate conventions are set up for this date placed in service.

[APP–47633] Error: Unable to compute cost retired

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47634] Error: Unable to calculate the GL period adjustment

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47635] Error: Unable to calculate rate adjustment factor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47636] Error: Unable to delete book record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47637] Error: Unable to delete distributions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47638] Error: Unable to get information about the asset

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47639] Error: Lookup in FA_EMPLOYEES

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47640] Error: Unable to update FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47641] Error: Unable to update FA_DEPRN_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47642] Depreciation is already &STATUS for this book (ID &REQUEST)

Cause:

You tried to start depreciation on a book while Depreciation is &STATUS for the book. You can

only depreciate a book for one period at a time.

Action:

Wait until the current depreciation process (Request &REQUEST) is finished, and then you can run

depreciation again. Use the View Requests form to monitor the progress of the current depreciation

process.

[APP–47643] Error: Unable to update adjustment required status in FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47644] Error: Unable to update depreciation period records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47645] Error: Unable to update period fully reserved in FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47646] Error: Unable to validate deprn_running_flag in FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47647] Error: Missing record in the FA_DEPRN_SUMMARY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47648] Exceeded max number of fiscal years (&FA_DEPRN_MAX_FISCAL_YEARS)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47649] Error: Unable to set depreciation status in FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47650] Error: Unable to select source book from FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47651] Error: Unable to select retirement status from FA_RETIREMENTS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47652] Error: Unable to select prorate period number

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47653] Error: Unable to select transaction header records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47654] Error: Unable to select sysdate from dual

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47655] Error: Unable to reset deprn running flag in FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47656] Error: Unable to reset retirement pending flag in FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47657] Error: Unable to select most current depreciation detail record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47658] Error: Unable to select distribution history records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47659] Error: Unable to select depreciation information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47660] Error: Unable to select records from FA_DISTRIBUTION_HISTORY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47661] Error: Unable to insert into FA_DEPRN_DETAIL table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47662] Error: Unable to insert records into FA_DEPRN_SUMMARY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47663] Error: Unable to find number of periods per fiscal year

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47664] Error: Unable to get current period counter

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47665] Error: Unable to select prorate period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47666] Error: Unable to update cost change flag in FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47667] Error: Unable to update period_reserved flag

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47668] Error: Unable to find depreciation amount for back out

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47669] Error: Unable to determine whether it is the end of the fiscal year

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47670] Error: Unable to validate depreciation period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47671] Error: Unable to fetch distribution history records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47672] Error: Unable to insert values into FA_ADJUSTMENTS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47673] Error: Unable to reset control flag in FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47674] Submitted requests: &RET_ID, &DEPRN_ID, &REP_ID

[APP–47675] Error: reset_rp_flag – Unable to reset retirement pending flag

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47676] Error: Unable to set deprn_running_flag in FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47677] Error: Unable to get previous period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47678] Error: fadidd – Unable to insert into FA_DEPRN_DETAIL table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47679] Error: nrp_det_deprn – Unable to insert into FA_DEPRN_DETAIL table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47680] Error: Unable to open cursor for FA_CALENDAR_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47681] Error: Unable to reset cost change flag in FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47682] Error: faddep – Failure in calling depreciation routine

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47683] Error: faddep – Failure in fetching book information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47684] Error: do_sum_deprn – Unable to create records for FA_DEPRN_SUMMARY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47685] Error: Unable to get information from FA_CALENDAR_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47686] Error: Unable to get current period counter

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47687] Error: Unable to select from FA_RATES table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47688] Error: fadcje – Failure in Cost Journal Entry routine

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47689] Error: Unable to close cursor for calendar periods (FA_CALENDAR_PERIODS)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47690] The book you specified has conc_process_status: &MEANING

[APP–47691] Error: Cannot verify retirement status from FA_RETIREMENTS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47692] Error: do_det_deprn – Unable to create records in FA_DEPRN_DETAIL

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47693] Error: faddep – SQL error in main select

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47695] Error: Unable to insert into FA_DEPRN_DETAIL table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47696] Error: Unable to insert into FA_DEPRN_SUMMARY table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47697] Error: Unable to insert into FA_DEPRN_DETAIL and FA_DEPRN_SUMMARY

tables

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47698] Error: Unable to validate input parameters

Cause:

Unable to validate depreciation book and period information.

Action:

Confirm the following: (1) You entered a valid depreciation book (2) The depreciation period is

valid, and immediately follows the last depreciation run period. Otherwise, contact your system

administrator.

[APP–47700] You cannot enter overlapping dates, or the same year of life for the same date range

for more than one record.

[APP–47701] Please enter a date in the current period or a prior period.

[APP–47708] A ceiling must have ceiling Amounts.

[APP–47711] This field is protected against update.

[APP–47712] This category is not eligible for ITC. Change the ITC Allowed field to Yes for the

book in the Book Controls form to make this category eligible.

[APP–47714] ITC can only be assigned to tax books.

[APP–47719] The Adjusted Rate cannot exceed 100%.

[APP–47720] Error: Lookup in FA_CATEGORIES table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47721] Error: Lookup in FA_CATEGORY_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47722] You cannot delete an index that is assigned to a category. Delete this index for the

category and book in the Asset Categories form.

[APP–47723] You cannot change the Category Type and Capitalize fields because this category is

already in use.

[APP–47733] Error: &MODULE – Unable to get segment number of GL_ACCOUNT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47734] Error: Unable to insert a row to FA_CAPITAL_BUDGET table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47735] Error: &MODULE – Unable to set Segment Number for &FLEX flexfield

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47736] Error: Unable to get &FLEX Code Combination Id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47738] Error: Unsupported cache mode: &FA_CACHE_MODE

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47740] Please enter an amount for all periods.

[APP–47741] Please enter Yes or No for each option

[APP–47742] Please choose at least one of the options in this form.

[APP–47743] Error: &MODULE – Unable to get active columns for &FLEX

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47744] Error: &MODULE – Unable to get &FLEX combination id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47745] You already uploaded data into this budget book

Cause:

You must delete the existing budget from this book before you can upload new data.

Action:

Use this form to enter Yes in the Delete Budget From This Book field.

[APP–47747] Error: Unable to setup flexfield

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47748] Budget line is not processed

[APP–47749] The date placed in service you entered does not fall into a prorate period that you

defined. Please set up fiscal years, calendars, and conventions.

[APP–47750] CIP assets must have a zero cost.

[APP–47751] Year–to–date depreciation cannot exceed life–to–date depreciation.

[APP–47752] Please enter a non–zero value for Cost

[APP–47753] You have entered budget amounts for all periods.

[APP–47754] The Life–To–Date Depreciation must be less than or equal to the current cost.

[APP–47758] You must enter a positive Salvage Value for positive cost assets.

[APP–47759] Life–to–date depreciation and year–to–date depreciation must be the same.

[APP–47761] The salvage value cannot be greater than the net book value.

[APP–47763] You must enter a zero Salvage Value for credit assets.

[APP–47766] You can assign ITC to assets that use a life–based depreciation method only.

[APP–47767] Error: Invalid rate adjustment factor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47768] Life–To–Date Depreciation cannot be greater than the Recoverable Cost.

[APP–47769] This book does not exist or has a date ineffective on or before today.

[APP–47770] You cannot enter a negative cost for an asset that has ITC.

[APP–47771] Error: Lookup in FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47772] The Date Placed In Service must be on or after the Oldest Date Placed In Service you

specify in the System Controls form.

[APP–47773] Asset is already in this book. Use \ Query Enter to find it

Cause:

The asset you tried to add has already been added to this book.

Action:

If you want to update the asset, use \ Query Enter to find it.

[APP–47774] Please enter a Date Placed In Service that falls in the current or a prior period.

[APP–47776] This Asset Category is not defined in this depreciation book.

[APP–47777] This Book is not set up for this Asset Category.

[APP–47778] You cannot expense an adjustment to an asset for which you have already Amortized

an adjustment. Please Amortize this adjustment.

[APP–47779] The prorate calendar and prorate convention are not set up for this date.

[APP–47780] You can use either a depreciation cost ceiling or ITC for an asset, but not both.

[APP–47782] You cannot amortize changes before you depreciate the asset.

[APP–47786] This asset is already assigned to a corporate book.

[APP–47789] You must enter a negative life–to–date and year–to–date depreciation if you enter a

negative cost.

[APP–47790] You must enter a positive life–to–date and year–to–date depreciation if you enter a

positive cost.

[APP–47792] Amortized adjustments are not allowed for this book.

[APP–47795] The Last Depreciation Run Date must be before today’s date.

[APP–47805] You have not defined any bonus rates for this bonus rule.

[APP–47806] You have not defined a Rule Name for the entered rates. Please enter a valid Rule

Name.

[APP–47807] Error: Unable to get CIP account numbers

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47808] You must define a prorate period for this prorate convention.

[APP–47809] You cannot make more than one adjustment in a single transaction.

[APP–47811] Error: Unable to insert transaction header

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47812] Error: Unable to get period name.

[APP–47813] Error: Unable to get transaction date entered.

[APP–47814] You can not ”undelete” this row

Cause:

You attempted to ”undelete” a row you had deleted during the current transaction.

Action:

Use \ Row Erase to cancel.

[APP–47815] Error: Unable to update existing book record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47816] Error: Unable to update existing transaction header.

[APP–47817] You cannot delete this line item

Cause:

You attempted to delete a line item whose cost you have updated.

Action:

Either return the cost to its original value or commit the change and then delete the row.

[APP–47818] Error: Unable to get data for database inserts

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47819] Error: Unable to insert adjustment record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47820] Error: Unable to insert asset invoice

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47821] Error: Unable to insert book record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47822] Error: Unable to insert invoice transaction

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47823] Error: Unable to select depreciation method flag

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47824] Error: Unable to select period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47825] You cannot adjust a line item that you have already deleted

[APP–47826] You cannot delete a line item you have just inserted

Cause:

You attempted to delete an invoice line you just inserted.

Action:

Use \ Row Erase to remove the line item.

[APP–47827] You cannot delete this line item

Cause:

You attempted to delete a row you had previously undeleted during the current transaction.

Action:

Use \ Row Erase to cancel.

[APP–47828] Error: Unable to select information from FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47829] Error: Unable to select information from FA_BOOKS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47830] Error: Unable to select calendar information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47831] Error: Unable to select depreciation period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47832] Unable to select from FA_DEPRN_SUMMARY and FA_DEPRN_PERIODS tables

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47833] Error: Unable to select depreciation method

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47834] Error: Unable to select salvage value

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47835] Error: Unable to select transaction header id

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47836] Error: Unable to insert new adjusted cost

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47837] Error: Unable to insert new rate adjustment factor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47838] Error: Unable to select information from FA_ADDITIONS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47839] Error: Unable to select adjustment records

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47840] Error: Unable to select date placed in service

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47841] Error: Unable to select depreciation method

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47842] Error: Unable to select depreciation start date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47843] Error: Unable to select asset life (in months)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47844] Error: Unable to select prorate date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47845] Error: Unable to select recoverable cost

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47846] Error: Unable to select book information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47847] Error: Unable to select bonus rule

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47848] Error: Unable to select depreciation book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47849] Error: Unable to select asset category

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47850] Error: Unable to select ceiling name

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47851] Error: Unable to select asset cost

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47852] Error: Failure in amortize user exit main module

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47853] Error: Unable to insert records into FA_ADJUSTMENTS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47854] Error: Failure calling faxnbv routine

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47855] Error: Unable to select adjusted rate

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47856] Error: Unable to select asset number

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47857] Error: Unable to select asset type

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47858] You did not depreciate assets during this fiscal year. Please perform your depreciation

adjustment in a later fiscal year.

[APP–47859] You cannot perform reserve adjustments in this book. Allow reserve adjustments

when you set up a book.

[APP–47860] Error: Unable to build depreciation structure module

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47861] Error: Unable to calculate depreciation expense

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47862] Error: Unable to calculate new rate adjustment factor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47863] You cannot reclassify capitalized assets as expensed items.

[APP–47864] This Tag Number is already used. Please enter another.

[APP–47869] You cannot reclassify expensed items as capitalized assets.

[APP–47875] Please delete the lease before changing the category.

[APP–47876] You must delete the leasehold improvements before you can delete the lease.

[APP–47877] Please delete the leasehold improvements before changing the category.

[APP–47878] You can only delete assets added in the current period.

[APP–47883] This Asset Number is reserved for automatic asset numbering.

[APP–47886] Failed to find Period Name

Cause:

Calendar periods have not been set up correctly for this book.

Action:

Use the Calendars form to correctly set up the calendar periods.

[APP–47887] Invalid ACE Period

Cause:

ACE period is not the last period in a fiscal year.

Action:

Use a different ACE Book, or ensure that the current period is the last period of a fiscal year.

[APP–47888] This Asset Number is already in use. Please enter another.

[APP–47890] Depreciation method &METHOD is not defined for life &LIFE

[APP–47891] Error retrieving information from FA_CALENDAR_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47892] Error retrieving information from FA_DEPRN_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47893] You cannot enter production for a CIP asset

[APP–47894] Invalid Book class, you cannot post Budget books.

[APP–47895] Error: Unable to retrieve current Mass Change status.

[APP–47896] Error: Unable to retrieve Mass Transaction status(es).

[APP–47897] Mass Change status is &CURRENT, should be &RUNNING

[APP–47898] Error: Unable to update Mass Change status.

[APP–47899] Mass Change Program completed with failure.

[APP–47900] Error: Unable to lock FA_BOOKS row for update.

[APP–47901] Error: Asset has transactions after Mass Change submission date.

[APP–47902] Error: Unable to update old Addition transaction.

[APP–47904] You cannot alter the record while Preview/Run is in process.

[APP–47905] One or more of the selected assets is Production in a Tax book.

Cause:

One or more of the selected assets is Production method in one or more associated Tax Books.

Action:

Make sure all selected assets that are to be changed to non–Production have non–Production

methods in all associated Tax Books.

[APP–47906] One or more selected assets are not production in corporate book

Cause:

One or more of the selected assets are not production in the Associated Corporate book.

Action:

Please make sure that all select assets that are to be changed to Production method are Production

method in the Associated Corporate book.

[APP–47907] Depreciation has been run on one or more selected assets

Cause:

Depreciation has been run on one or more of the selected assets. You cannot change these assets to

a Production method.

Action:

Please choose a different To Method.

[APP–47908] At least one of the child requests failed

Cause:

At least one of the child requests spawned to run depreciation failed.

Action:

Check the depreciation log files to find out what caused the request to fail. If only one request

failed, change FA: Number of Parallel Requests profile option value by one to process failed assets

in parallel. Then resubmit.

Action:

Contact your system administrator.

[APP–47909] Error getting period_counter_fully_reserved from Reserve Adjustments form

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47910] Error: Incorrect dynamic table &TABLE used. Existing and expected (Record count,

Checksum) are &CHECKSUM

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47911] The number of rows inserted or deleted does not match with those fetched

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47914] You cannot make a reserve adjustment on a CIP asset

[APP–47915] Error: This asset has been revalued

[APP–47916] Error checking whether or not this is a revalued asset

[APP–47917] Depreciation not run for period in associated CORPORATE book

Depreciation must have completed in the Distribution Source Book for this TAX book before you

can calculate deferred deprecation.

[APP–47919] You cannot post depreciation to this book class

[APP–47920] Illegal cache mode sent to fazinje()

The function faxinje() has received an invalid cache mode from the calling function.

[APP–47921] Error: Unable to open &CURSOR cursor

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47922] Error: Failed to get checksum

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47923] Error: Failed to get fiscal year corresponding to a period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47924] Error: Date Placed In Service is not valid for this book.

[APP–47925] You must specify a life for this Depreciation Method.

[APP–47926] You must specify a production capacity for this Depreciation Method.

[APP–47927] You must specify a rate for this Depreciation Method.

[APP–47928] Cannot copy from non–production method to production in tax book

You cannot copy assets which do not use a units of production method in the corporate book to use a

units of production method in the tax book

[APP–47929] There is no life associated with the Parent Asset.

[APP–47930] Depreciation has never been run on this CORPORATE book

Depreciation must be calculated at least once for this CORPORATE book in order to calculate

deferred depreciation with the chosen TAX book.

[APP–47933] Depreciation has never been run on this TAX book

Depreciation must be run at least once for this TAX book in order to calculate deferred depreciation

with the associated CORPORATE book.

[APP–47934] Number of rows inserted does not equal number of rows in cache

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47935] Error: Unable to calculate the adjusted cost

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47936] Error: Failed to insert new financial information into FA_BOOKS for cost

adjustments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47937] Error: Failed to insert into FA_INVOICE_TRANSACTIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47938] Error: Failed to Update FA_MASS_ADDITIONS table with new asset_number

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47939] Parent asset does not belong to the same book as the mass addition

[APP–47940] Error: Rate_adjustment_factor calculated is out of range

[APP–47941] Journal categories must be unique for each transaction type within a book.

[APP–47942] The cost change flag is set for asset &ASSETNUM

[APP–47944] You cannot transfer lines between expensed and non–expensed assets.

[APP–47945] Distribution: &dist in Book: &book could not be processed.

[APP–47946] Selecting distribution information.

[APP–47947] Selecting book information.

[APP–47948] Selecting asset history information

[APP–47949] Checking status of retirement transaction.

[APP–47952] Unable to remove COST CLEARING adjustment.

[APP–47953] Accounting period &PERIOD for book &BOOK is unavailable for posting.

[APP–47954] Error in updating FA_DEPRN_PERIODS.

[APP–47955] Cannot upgrade book &BOOK : Rolling back transactions...

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47956] Error: Cannot get default date placed in service for this mass addition

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47957] Error: Cannot select mass_addition_id from fa_mass_additions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47958] Error: Inserting into FA_DELETED_MASS_ADDITIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47959] Error: Updating FA_DELETED_MASS_ADDITIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47960] Error: Unable to get detail flags from old book controls table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47961] FlexBuilder : Invalid Account Type : &ACCOUNT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47962] Error: Getting tax reserve adjustments for period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47963] Error: Tried to update more than one fa_books record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47964] Error: Selecting deprn info (second attempt)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47965] Error: Unable to insert records into FA_DEPRN_SUMMARY table (flushing array

fetch)

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47966] Error: Inserting into FA_MASS_ADDITIONS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47967] Error: Cannot set request_id in FA_SYSTEM_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47968] Error: Unable to get current period information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47969] Error : COMMITting cursor &CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47970] Error: Unable to get most recent distribution period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47971] Error: Unable to insert values for depreciation detail

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47972] Error: Unable to select most recent summary period

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47973] Error: Getting ytd deprn

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47974] Error: Invalid mode &MODE_NAME passed to user exit

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47975] Error getting the period_adjusted from the Reserve Adjustments form

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47976] Error: OPENing cursor &CURSOR

[APP–47977] Error: DECLAREing cursor &CURSOR

[APP–47978] Error: CLOSEing cursor &CURSOR

[APP–47979] Error: Unable to select period name from FA_CALENDAR_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47980] Error: Could not insert a new FA_BOOKS record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47981] Error: Failure checking if the asset is retired

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47982] Error: Failure to insert first FA_ADJUSTMENTS row

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47983] Cache: Error retrieving row from FA_BONUS_RATES table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47984] Cache: Error retrieving row from FA_CALENDAR_PERIODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47985] Cache: Error retrieving row from FA_METHODS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47986] Error: malloc() failed to allocate dynamic memory

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47987] Unable to build dpr_struct

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47988] Error getting the new_reserve from the Reserve Adjustments form

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47989] Error getting the fiscal year from the Reserve Adjustments form

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47990] Error: Failure fetching cursor FISCAL_YEAR_CR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47991] Error: Could not update FA_BOOKS record

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47992] Error: Unable to declare cursor DH_CURSOR2

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47993] Error: Unable to open cursor DH_CURSOR2

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47994] Error: Unable to fetch cursor DH_CURSOR2

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47995] Error: Unable to get the asset cost account from FA_CATEGORY_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47996] Error: Unable to get the reserve account from FA_CATEGORY_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47997] Error: Unable to get the expense account from FA_CATEGORY_BOOKS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47998] Error: Unable to insert into FA_DISTRIBUTION_HISTORY

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–47999] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48000] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48001] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48002] Error: Unable to insert into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48003] Error: Unable to get depreciation reserve

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48004] Error: Unable to insert into FA_TRANSACTION_HEADERS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48005] Error: Unable to determine if the category exists for this book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48006] Error: Unable to invalidate old FA_ASSET_HISTORY row

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48007] Error: Unable to determine if this book is a corporate book

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48008] Error: Unable to declare cursor DH_CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48009] Error: Unable to update FA_DISTRIBUTION_HISTORY

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48010] Error: Unable to select first depreciation date

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48011] Error: &MODULE – Flexfield Code for &FLEX doesn’t exist

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48012] Error: Unable to update deprn periods table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48013] Error: Fatal error in main routine

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48014] Unable to determine if asset uses flat–rate depreciation method

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48015] Error: Unable to get the date for this transaction

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48017] Error: Unable to select latest summary row – 1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48018] Transactions have been made for this Book in the Current Period You can only adjust

depreciation for a book with no transactions in the current period.

[APP–48023] Data Error in FA_METHODS. Contact System Administrator

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48024] You have not defined default values for this category and book.

[APP–48025] An unbalanced transaction was taking place &CLEAR_AMT &INSERT_AMT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48026] Error: amount cleared &CLEARED does not equal amount inserted &INSERTED;

cannot create balanced journal entries

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48027] Error: Called Query Fin Info with no book specified

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48028] Error getting the summary level adjustments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48029] Error: Invalid Request Phase fetched. Contact System Administrator

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48030] Error executing Rollback

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48031] Data Error in FA_BOOK_CONTROLS. Contact System Administrator

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48032] Data Error in FA_CATEGORY_BOOK_DEFAULTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48033] &BOOK_TYPE cannot be purged for the fiscal year &FISCAL_YR. You cannot

purge a fiscal year not already archived, the current fiscal year, or fiscal years out of chronological

order.

[APP–48034] Archive table &TABLE does not exist

You cannot purge a fiscal year unless the temporary archive tables from that year exist.

[APP–48035] Error: Failed to update FA_BOOK_CONTROLS table

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48036] Error: An invalid mode was specified to fauqadd()

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48037] Error getting the distribution level adjustments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48038] Error: The row to be updated or deleted does not exist

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48039] Invalid purge action specified

Cause:

You have chosen an action that is not allowed for this status.

Action:

Please choose an allowed action.

[APP–48040] Error: Unable to create &INDEX index. &SQLSTMT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48041] Error: Unable to get the status of database object &OBJECT. &SQLSTMT

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48042] Error: Checksum failed for &TABLE table. (Record count, checksum) for main and

archive tables is &CHECKSUM

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48044] Cannot copy capacity adjustment because asset does not use production method in the

tax book

You can only copy capacity adjustments from the corporate book if the asset also uses a units of

production method in the tax book.

[APP–48045] Error: Failed to update the FA_TRANSACTION_HEADERS table for a CIP asset

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48046] Error: Failed to process the insert_mc function call

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48047] Error: The Depreciate Flag for this mass addition is not valid

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48048] Error: Failed to update FA_MASS_ADDITIONS for posted mass additions

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48049] Error: Cannot find Merged Children’s Fixed Assets Cost

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48050] Mass Additions Post does not process Merged Child and Split Parent mass addition

lines

[APP–48051] Error: Failed to Update FA_MASS_ADDITIONS for this mass addition’s

subcomponents

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48052] Error: Failed to execute the Reclassification program

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48053] Error: Failed to select date information from FA_TRANSACTION_HEADERS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48054] Error: Invalid depreciation method for this book.

[APP–48055] Error: Failed to Update FA_ADDITIONS table with new category information

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48056] Error: Failed to get the Adjustment type

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48057] Error: Failed to insert into FA_ASSET_INVOICES

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48058] Error: Cannot find financial information for asset to which to add mass addition line

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48059] Error: Failed to get category segments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48060] Error fetching cursor DS1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48061] Error selecting the cost adjustments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48062] Error selecting the revaluation adjustments

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48063] Fatal error: out of bounds on insert into FA_ADJUSTMENTS cache

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48064] Error opening cursor C1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48065] Error: selection mode specified is undefined for OPEN CURSOR

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48066] Error: Illegal value (&VALUE) for &VARIABLE

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48067] Error: Unable to find Period_Counter of the period in which the transfer occurred

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48068] Error on array INSERT into FA_ADJUSTMENTS

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48069] Error closing cursor DS1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48070] Error declaring cursor C1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48071] Error declaring cursor DS1

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48072] Please assign this asset to an employee, location, and general ledger depreciation

expense account in the corporate book.

[APP–48073] You cannot use a production depreciation method in this book.

[APP–48075] Error: Insert into Depreciation Detail failed

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48076] Closing Cursor FAMTDH.

[APP–48077] Error in updating fa_distribution_history.

[APP–48078] Error in inserting into fa_distribution_history.

[APP–48079] Error in inserting old distribution information into fa_transfer_details.

[APP–48080] Error in inserting new distribution information into fa_transfer_details.

[APP–48081] Error: This asset has no distributions.

[APP–48082] Error in selecting sysdate.

[APP–48083] Error in selecting mass tax adjustment information.

[APP–48084] Could not find total number of distributions affected by transfer

[APP–48085] Declaring Cursor Interco_cursor.

[APP–48086] Opening Cursor Interco_cursor.

[APP–48087] Fetching Cursor Interco_cursor.

[APP–48088] Closing Cursor Interco_cursor.

[APP–48089] Error: New distributions have unbalanced units.

[APP–48090] Distribution has an invalid transaction header ID

[APP–48091] This asset’s parent asset does not belong to this book.

[APP–48092] Error in selecting depreciation information from fa_deprn_summary.

[APP–48093] Error in selecting asset’s cost from fa_books.

[APP–48094] Selecting Mass Transfer information.

[APP–48095] Updating Mass Transfer information.

[APP–48096] Selecting accounting period information from fa_deprn_periods.

[APP–48097] Declaring Cursor C1.

[APP–48098] Opening Cursor C1.

[APP–48099] Fetching Cursor C1.

[APP–48100] Selecting asset’s cost from fa_books.

[APP–48101] Cannot rollback.

[APP–48102] Closing Cursor C1.

[APP–48103] Checking whether or not this transfer occurred in a prior period.

[APP–48104] Checking that the units are balanced.

[APP–48105] Getting the lastest transaction date for the asset.

[APP–48106] Checking the validity of the transaction date.

[APP–48107] Declaring Cursor FAMTDH.

[APP–48108] Opening Cursor FAMTDH.

[APP–48109] Fetching Cursor FAMTDH.

[APP–48110] Error in selecting account information.

[APP–48111] Error in selecting invoice information.

[APP–48112] Cannot commit record.

[APP–48113] Asset ID &ASSET –> ** FAILED **

[APP–48114] You cannot revalue assets in an expensed category.

[APP–48115] You cannot reverse capitalize assets for which you have already entered transactions.

[APP–48116] You have not uploaded a budget for this book.

[APP–48117] You must delete the budget assets before uploading

Cause:

You are attempting to upload a new budget for a budget book with existing budget assets.

Action:

Please enter Yes in the Delete Existing Budget field before uploading a new budget.

[APP–48118] Error declaring cursor CLEAR

[APP–48119] Error opening cursor CLEAR

[APP–48120] Error fetching cursor CLEAR

[APP–48121] No active books row exists for asset

[APP–48122] Error declaring cursor RET_CR

[APP–48123] Error opening cursor RET_CR

[APP–48124] Error fetching cursor RET_CR

[APP–48125] You cannot create a distribution with zero units

[APP–48126] Undefined selection mode

[APP–48127] Undefined flush flag

[APP–48128] Asset has not been added to a corporate book.

[APP–48133] Error selecting the category/book information

[APP–48134] The asset category is not set up correctly

Cause:

The asset category is not set up for thisbudget book’s associated corporate book.

Action:

Please set up the category for the corporate book or assign the budget to another category.

[APP–48135] The revaluation reserve account for category &CATDESC has not been defined in

&BOOK

[APP–48136] Error: Failure checking if the asset has had an amortized adjustment

[APP–48137] You cannot assign or delete ITC to or from this depreciated asset.

[APP–48138] Error: Cannot change a depreciated asset’s method to/from production

[APP–48139] Error: Asset is production in a TAX book, cannot change to non–production

depreciation method

[APP–48140] Error: Asset non–production in corporate book, cannot change to production

[APP–48141] Error: Asset is not in associated corporate book

[APP–48142] Status &STATUS unknown

Cause:

The mass transaction has an unknown status.

Action:

Please resubmit the mass transaction.

[APP–48143] Error: Unable to fix Mass Change status

[APP–48144] Error checking whether Mass Change changes only the UOM

[APP–48145] Error performing a Unit of Measure Change

[APP–48146] Error: Failed to update tax book’s Unit of Measure

Cause:

You have a database problem.

Action:

Contact your system administrator.

[APP–48148] Error: Failure checking cost of asset in the Control, Corporate, and Adjusted Books

[APP–48149] Error inserting into FA_TRANSACTION_HEADERS

[APP–48152] Asset number &NUMBER

[APP–48155] Sequence has errors

[APP–48156] Sequence type is not Automatic

[APP–48157] Failed to fetch next sequence value

[APP–48158] Failed to update GL_JE_HEADERS with document sequencing information

[APP–48159] Error: Invalid value for argument &ARG_NAME passed to user exit.

[APP–48160] Error: Invalid mode &MODE_NAME passed to user exit.

[APP–48161] Error: Life extension factor is not part of the revaluation rules.

[APP–48162] Error: Investment Tax Credit ceiling does not exist.

[APP–48163] Error inserting discount lines

[APP–48164] Error: &FORMAT is not the correct date format

[APP–48165] &USER_EXIT User Exit ended with error.

[APP–48166] Asset ID &ASSET –> ** NOT PROCESSED **

[APP–48167] New method &METHOD with &NEW_LIFE life created; ignore previous message

Oracle Assets created the new method. Ignore the previous error message.

[APP–48168] Illegal transaction type sent to fampvt()

The program attempted to process an illegal transaction type. This illegal value was found in

th–>type_code: &MODE.

[APP–48169] You cannot delete this record because it is already in use.

[APP–48170] This record already exists. Please query to review it.

[APP–48171] From Date must be on or before To Date.

[APP–48172] The To Date can only be blank for the last record which is then effective indefinitely.

[APP–48173] The date ranges cannot overlap.

[APP–48174] The To Date you entered was later than the end of the fiscal year. Oracle Assets has

changed it to be the last day of the fiscal year. Accept this To Date or enter a different date in the

fiscal year.

[APP–48175] Please save your changes first.

[APP–48176] You can only insert a new record as the last record.

[APP–48177] Delete this record?

[APP–48178] Error: FEEDER SYSTEM NAME: &FEEDER_SYSTEM_NAME

[APP–48179] Error: Incorrect Add to Asset ID: &ADD_TO_ASSET

[APP–48180] Error: Employee ID: &ASSIGNED_TO does not exist.

[APP–48181] Error: The Date Placed In Service &DPIS must be greater than the Oldest Date

Placed In Service in FA_SYSTEM_CONTROLS.

[APP–48183] Error: Depreciate flag &DEPRECIATE_FLAG must be YES or NO.

[APP–48184] Error: Invalid location for &LOCATION_ID.

[APP–48186] Error: Parent Asset ID for &PARENT_ASSET either does not exist in FA_BOOKS or

is inactive.

[APP–48187] Error: Invalid Payables Code Combination ID for &PAYABLES_ID.

[APP–48189] Error: Invalid Expense Code Combination ID for &EXPENSE_ID.

[APP–48195] Error: Invalid PO Vendor ID for &PO_VENDOR_ID.

[APP–48197] Error: Incorrect Unit of Measure for &UNIT_OF_MEASURE.

[APP–48198] Error: The Salvage Value for &SALVAGE_VALUE cannot be less than the fixed

asset Cost.

[APP–48199] Error: Invalid split merged code for &SPLIT_MERGED_CODE

[APP–48200] Error: Category ID for &CATEGORY_ID is either disabled or invalid.

[APP–48201] Error: Incorrect Asset Type and Category combination for &CATEGORY_ID.

[APP–48202] Error: Mass Additions does not post with incorrect data.

[APP–48203] Error: Asset units for &ASSET_UNITS cannot be zero.

[APP–48204] If you want to delete this record, you must delete the entire prorate convention.

[APP–48205] More than one record exists for this prorate convention. To delete this row, please

requery all the prorate dates for this convention first.

[APP–48206] You cannot delete any part of this transaction because it is already Completed.

[APP–48207] You cannot change any part of a transaction with a status of Running or Completed.

[APP–48208] &ELEMENT has the value of &VALUE.

[APP–48209] You can only delete or clear the most recent record.

[APP–48210] You cannot delete or clear the last remaining set of depreciation rules for a category

and a book.

[APP–48211] You cannot change the Fiscal Year. Please clear or delete this record and re–enter the

prorate convention.

[APP–48212] You can only enter rates for table and flat–rate methods.

[APP–48213] You have entered an asset with an invalid asset type. Valid asset types are

CAPITALIZED, CIP, or EXPENSED.

[APP–48214] The Fiscal Year has not been closed for &BOOK.

[APP–48215] Data error in &TABLE. Contact your system administrator.

[APP–48216] Request &REQUEST_ID completed with status &REQUEST_STATUS

[APP–48217] Request &REQUEST_ID is &REQUEST_PHASE

[APP–48218] Concurrent Request &REQUEST_ID submitted.

[APP–48219] You cannot update this field because the record is already in use.

[APP–48220] Mass Depreciation Adjustment completed in error. Please commit the status change.

[APP–48221] Error: Oracle Assets. Database problem. Contact your system administrator.

[APP–48222] You can only enter production information in the open period or for future dates.

[APP–48223] From Date must be greater than or equal to the prorate date.

[APP–48224] From and To dates must be within the same calendar period.

[APP–48225] The asset must use a units of production depreciation method.

[APP–48226] The asset type must be capitalized.

[APP–48227] Total production for the asset must be greater than or equal to zero.

[APP–48228] You cannot update mass additions in the &QUEUE_NAME queue.

[APP–48229] You cannot post a mass addition that does not have a value for the required hidden

field &FIELD_NAME Null.

[APP–48230] The oldest Date Placed In Service must be the same as or before all assets already

placed in service.

[APP–48231] Perform this mass transaction?

[APP–48232] Another transaction is already being performed on this asset. Please try again later.

[APP–48233] This fiscal year already exists, or the dates conflict with an existing fiscal year.

[APP–48234] Please enter dates without gaps that do not overlap.

[APP–48235] You can clear the last row only.

[APP–48236] Error: Unable to calculate recoverable cost.

[APP–48237] Reinstate this asset?

[APP–48238] Undo this reinstatement?

[APP–48239] Undo this retirement?

[APP–48240] The units in FA_ASSET_HISTORY and FA_DISTRIBUTION_HISTORY are

different.

[APP–48241] You cannot perform transactions on this asset because it is assigned to a budget book.

[APP–48242] Please choose a set of books before navigating to another block.

[APP–48243] Error: SQL error detected in &Procedure_name.

[APP–48244] You can undo a split only for the split parent mass addition line.

[APP–48245] Undo this split?

[APP–48246] To see the effect of this transaction, please re–execute your query.

[APP–48247] A transaction window is already open. Please complete your transaction and close it

before opening a new window or doing a split or undo split on a mass addition.

[APP–48248] You must specify the asset to add the mass addition to.

[APP–48249] You cannot assign this mass addition to other assets because it has already been split

or merged.

[APP–48250] Un–Splitting Mass Addition...

[APP–48251] Splitting Mass Addition...

[APP–48252] Working...

[APP–48253] You cannot split this mass addition. Verify that this is a multi–unit mass addition and

that you have not already split it.

[APP–48254] You cannot remove this mass addition from an asset because it has not yet been added

to an asset.

[APP–48255] Please enter a value that is greater than zero.

[APP–48256] Please complete or clear the current transactions before performing a Split or Undo

Split.

[APP–48257] Undo the cost adjustment for this mass addition?

[APP–48258] Split this mass addition?

[APP–48259] You cannot change the Depreciate flag for this category and book because you cannot

depreciate an Expensed asset.

[APP–48260] Module &PROGRAM ended with error

[APP–48261] Program &PROGRAM completed successfully

[APP–48262] You cannot change this flag either because this category is already in use, or because

it already has default values set up. Note that you cannot depreciate assets in non–Capitalized

categories.

[APP–48263] Please enter the required fields before navigating to another block.

[APP–48264] Detaching the lease information for this asset also removes lease information from

subcomponents. Continue?

[APP–48265] Transaction committed for asset number &ASSET_NO. Reference number:

&REF_NO

[APP–48266] Transaction saved for asset number &ASSET_NO. Reference numbers:

&REF_NO1, &REF_NO2

[APP–48267] Remove this asset from the system?

[APP–48268] Mass addition successfully split into &FIXED_ASSETS_UNITS mass additions.

[APP–48269] Invoice cost must equal asset cost.

[APP–48270] Please enter both the book and asset type in the Find window before you execute the

query.

[APP–48271] &BLOCK_NAME has some pending transactions. Please complete them before

splitting or unsplitting a mass addition.

[APP–48272] Submitted Request: &REQUEST

[APP–48273] &ITEM must be entered.

[APP–48274] You can change the end date placed in service for any row except the last.

[APP–48275] If you choose to use STL for Retirements, please enter the Method and Life.

[APP–48276] You must enter both Before and After fields, or neither field.

[APP–48277] Mass Change status change to &MASSCHG_STATUS. Please save this change.

[APP–48278] Concurrent Request &REQUEST_ID submitted.

[APP–48279] Please Calculate Gains and Losses before performing this transaction.

[APP–48280] Changing status to &REVAL_STATUS. Please save this change.

[APP–48281] Mass Change &REQUEST_ID: &REQUEST_STATUS with phase

&REQUEST_PHASE

[APP–48282] You cannot transfer this line if the transfer amount is greater than the original line

amount.

[APP–48283] Unable to generate asset id.

[APP–48285] &VALUE already exists. Please enter a new value.

[APP–48286] You have not defined default values for the category.

[APP–48287] Cannot find the last period for this book.

[APP–48288] You cannot retire assets you added in the current period.

[APP–48289] Unknown error. Please contact your system administrator.

[APP–48290] The calendar range must coincide with an existing fiscal year range.

[APP–48291] Run depreciation? Once the program closes the period, you cannot reopen it.

[APP–48292] &OBJECT is not defined.

[APP–48293] Change the asset number?

[APP–48294] You already have reached the end of this fiscal year calendar.

[APP–48295] You already have entered rates for every period in this method.

[APP–48296] Error: A unit change on this asset has not been completed. Please use the

Assignments form to distribute the units correctly.

[APP–48297] Waiting for request &REQUEST_ID to complete. Will try again at &RESUB_TIME

[APP–48298] Depreciation is running on book &BOOK. Please try this transaction later.

[APP–48299] There is no detail information for this transaction type.

[APP–48300] Please enter only a negative number of units in the Unit Change field.

[APP–48301] Unknown server side error. Please contact your system administrator.

[APP–48302] &TAG_NUMBER already exists. Please use another.

[APP–48303] You must enter a transfer amount if you want to transfer this source line.

[APP–48304] From Year must be before To Year.

[APP–48305] You cannot enter more periods for this fiscal year than there are days in this fiscal

year. Please enter a fewer number of periods.

[APP–48306] Please enter the book and either the reference or asset number in the Find window

before you execute the query.

[APP–48307] Please enter all the required fields in all windows for this transaction.

[APP–48308] Please enter a date for which the calendar periods are set up.

[APP–48309] You must enter a Category and Description if you choose the New Category and

Description check box.

[APP–48310] You must enter a Description, Category, Location, and Expense Account before you

place this mass addition in the POST queue.

[APP–48311] You cannot unsplit the split Child of a Merge. Unsplitting the split Parent of the

Merge also unsplits the children. Please unsplit the Parent only.

[APP–48312] This mass addition line is marked to be added to an existing asset. If you want to

merge this line into another, you must Remove it from the existing asset before performing the

merge.

[APP–48313] You cannot create identical distribution lines.

[APP–48314] Unable to get Application Information using procedure

FND_INSTALLATION.GET_APP_INFO.

[APP–48315] You cannot delete the last rate row.

[APP–48316] Please enter a year greater than 1000.

[APP–48317] The employee to which this distribution line is assigned is no longer valid.

[APP–48318] Category and subcategory values may not be longer than 15 characters.

[APP–48319] You cannot delete master record when matching detail records exist.

[APP–48320] This category is set up to use a depreciation limit. Please enter either a percent value

or depreciation limit amount.

[APP–48321] You must enter a valid budget book.

[APP–48322] Do you want to save the changes you have made?

[APP–48324] You cannot change the calendar type when periods are already defined.

[APP–48326] A line to be posted as a non–CAPITALIZED asset cannot have existing depreciation

or revaluation reserves. For Mass_Addition_Id = &MASS_ADDITION_ID, ensure that the

following columns are null or zero: DEPRN_RESERVE, YTD_DEPRN,

FULLY_RSVD_REVALS_COUNTER, REVAL_AMORTIZATION_BASIS, REVAL_RESERVE,

YTD_REVAL_DEPRN_EXPENSE

[APP–48327] The date placed in service for &DPIS cannot be NULL.

[APP–48328] The Location for &LOCATION cannot be NULL.

[APP–48329] Parent Asset ID for &PARENT_ASSET either does not exist in FA_BOOKS or is

inactive.

[APP–48330] The Payables CCID cannot be NULL for &PAYABLES_ID.

[APP–48331] The Expense CCID cannot be NULL for &EXPENSE_CCID.

[APP–48332] Asset cost cannot be NULL for &ASSET_COST.

[APP–48333] Asset units cannot be NULL for &ASSET_UNITS.

[APP–48334] Payables cost cannot be NULL for &INVOICE_COST.

[APP–48335] Payables units cannot be NULL for &INVOICE_UNITS.

[APP–48336] Please complete the Oracle Assets setup steps before using the system.

[APP–48337] Concurrent request &REQUEST_ID for &PROCESS submitted.

[APP–48338] You cannot perform this transaction on an asset whose normal life is complete but not

yet fully reserved.

[APP–48339] An asset’s recoverable cost cannot be greater than its cost. Please enter a recoverable

cost less than or equal to this asset’s cost.

[APP–48340] You cannot set the recoverable cost to zero.

[APP–48341] The cost’s magnitude cannot be less than the special depreciation limit for this

category.

[APP–48342] If the cost is positive, the recoverable cost must also be positive. If the cost is

negative, the recoverable cost must be negative.

[APP–48343] If the cost is positive, the revaluation ceiling must also be positive. If the cost is

negative, the revaluation ceiling must be negative.

[APP–48344] There are no rows in table SYS_DUAL.

[APP–48345] Error querying default information for percent salvage value or depreciation limit.

[APP–48346] The salvage value must be less than the cost when using depreciation limits.

[APP–48347] Error: Invalid asset number

[APP–48348] The cost cannot be less than the net book value for a non–depreciating asset.

[APP–48349] You cannot enter both a depreciation expense ceiling and a depreciation limit.

Uncheck the Use Depreciation Limit check box if you want to use a depreciation expense ceiling.

[APP–48351] This trade–in asset does not exist in Oracle Assets. Please enter an existing asset.

[APP–48352] The Depreciation Amount cannot be greater than the net book value of the asset.

[APP–48353] The reversed depreciation amount cannot be greater than the accumulated

depreciation.

[APP–48354] Please commit or clear your changes before proceeding.

[APP–48355] Please define the category in the Categories form first.

[APP–48356] Retirement values may not be longer than 15 characters.

[APP–48357] The fiscal year name for the calendar and each book must be the same.

[APP–48358] Before

[APP–48359] After

[APP–48360] The number of Units for this merged mass addition must be greater than the sum of all

the child units.

[APP–48361] You cannot clear records here.

[APP–48362] You cannot clear this block.

[APP–48363] The Start Date cannot be before the Lease Date.

[APP–48364] Error: Unable to generate Payment Schedule Id.

[APP–48365] Please recalculate before proceeding.

[APP–48366] You must leave either the Present Value field or the Amount field for one of the Lease

Payments blank before you choose the Calculate button.

[APP–48367] Please enter the first day of the month for the Lease Date and the Start Date

[APP–48368] Frequency cannot be Balloon Payment or Bargain Purchase when the Number of

Payments is more than one.

[APP–48369] You cannot delete a Payment Schedule that is attached to a lease.

[APP–48370] You cannot update a Payment Schedule that is attached to a lease.

[APP–48371] You must enter a valid tablename.

[APP–48372] You cannot enter more than 25 parameter rows.

[APP–48373] Concurrent Program Name already exists. Please enter a new value.

[APP–48374] The Currency does not match with the Payment Schedule. Please clear the Payment

Schedule field to change the Currency.

[APP–48375] Cannot find the Payment Schedule you selected.

[APP–48376] This asset has not been assigned to a category.

[APP–48377] Please commit or clear the distributions before changing the distribution set.

[APP–48378] Either the expense account or location in the Assignments Window is null. Please

enter valid values for these fields.

[APP–48379] Please ensure that all the units are distributed.

[APP–48380] Please use the Assignments window to change the number of units.

[APP–48381] &Check All

[APP–48382] &Uncheck All

[APP–48383] &Post All

[APP–48384] &Hold All

[APP–48385] &Delete All

[APP–48386] &Merge All

[APP–48387] &Unmerge All

[APP–48388] &Copy Definition

[APP–48389] The present value of the payment schedule you selected has changed. Please reselect

the payment schedule to see the change.

[APP–48390] This asset is assigned to a lease with a different currency.

[APP–48391] This option is only applicable to merged parent mass additions for which the Sum

Units checkbox has been checked.

[APP–48392] &MSG1

[APP–48393] Program exited with errors : &MSG1 &MSG2

[APP–48394] Program exited with errors: &MSG1 &MSG2 &MSG3

[APP–48395] Program exited with errors: &MSG1 &MSG2 &MSG3 &MSG4

[APP–48396] Program exited with errors: &MSG1 &MSG2 &MSG3 &MSG4 &MSG5

[APP–48397] Program exited with errors: &MSG1 &MSG2 &MSG3 &MSG4 &MSG5 &MSG6

[APP–48398] Program exited with errors: &MSG1 &MSG2 &MSG3 &MSG4 &MSG5 &MSG6

&MSG7

[APP–48399] Error: function &CALLING_FN returned failure

[APP–48400] &ORACLE_ERR

[APP–48401] Fixed Asset Debug Messages: &MSG1 &MSG2 &MSG3 &MSG4 &MSG5 &MSG6

&MSG7 &MSG8 &MSG9 &MSG10

[APP–48402] Report names can include only alphanumeric characters.

[APP–48403] Error in PRE–INSERT Trigger . Please contact your System Administrator.

[APP–48404] Unable to insert records. Please contact your System Administrator.

[APP–48405] Please enter a positive, non zero, whole number for Extended Life in Years.

[APP–48406] The amortization start date must be after the period the asset began depreciating.

[APP–48407] Please use the System Controls form to specify your company name, asset numbering

scheme, and key flexfield structures before using this form.

[APP–48408] Oracle Assets cannot copy adjustments dated in prior periods.

[APP–48409] Property Type values may not be longer than 10 characters.

[APP–48410] Please close the Assignments window before performing this action.

[APP–48411] There is a data error in table FA_MASS_TAX_ADJUSTMENTS. Please contact your

system administrator.

[APP–48412] Do you want to save the amortization schedule?

[APP–48413] Invalid value &VALUE passed as parameter &PARAM

[APP–48414] Start date must come before the End Date.

[APP–48415] Purge function will permanently remove records from the database. Do you want to

continue?

[APP–48416] Purging is not allowed in this mode.

[APP–48417] Not all records have been reconciled. Do you want to continue with purge?

[APP–48418] From Cost must be less than or equal to To Cost.

[APP–48419] Please enter an ASSET NUMBER, TAG NUMBER, or SERIAL NUMBER before

proceeding.

[APP–48420] Error selecting beginning balances.

[APP–48421] Error selecting ending balances.

[APP–48422] Error selecting adjustment account segments.

[APP–48423] Unable to get segment numbers corresponding to this book’s accounting flexfield

structure.

[APP–48424] Unable to get concatenated segments for code combination &CCID in flexfield

&FLEX_CODE.

[APP–48425] Error deleting from &TABLE.

[APP–48426] Error inserting into &TABLE.

[APP–48427] Error fetching columns for structure &STRUCT_ID of flexfield &FLEX_CODE.

[APP–48428] Error generating dynamic SQL statements for structure &STRUCT_ID of flexfield

&FLEX_CODE.

[APP–48429] Unhandled exception generating segments for structure &STRUCT_ID of flexfield

&FLEX_CODE.

[APP–48430] Error populating reserve ledger table.

[APP–48431] Error selecting FA_BOOKS information for asset_id &ASSET_ID.

[APP–48432] Error querying balances for asset_id &ASSET_ID.

[APP–48433] Error determining the start and end periods of this What–If Analysis.

[APP–48434] Unhandled exception while performing expensed adjustment for asset_id

&ASSET_ID.

[APP–48435] Unhandled exception while performing amortized adjustment for asset_id

&ASSET_ID.

[APP–48436] Unhandled exception while running what–if depreciation on asset_id &ASSET_ID.

[APP–48437] Error in allocating depreciation expense for asset_id &ASSET_ID across the periods

specified for this What–If Analysis.

[APP–48438] Error calling What–If Engine in Normal mode for asset_id &ASSET_ID.

[APP–48439] Error calling What–If Engine in Expensed/Amortized mode for asset_id

&ASSET_ID.

[APP–48440] Error committing analysis for asset_id &ASSET_ID to interface table.

[APP–48441] Error selecting assets satisfying query criteria for this What–If Analysis.

[APP–48442] Error checking transaction dates for asset_id &ASSET_ID.

[APP–48443] Asset &ASSET_NUM satisfies the query criteria for this What–If Analysis but will

not be analyzed because a transaction is still pending.

[APP–48444] Asset &ASSET_NUM satisfies the query criteria for this Expensed What–If Analysis

but will not be analyzed because an amortized adjustment has already occurred.

[APP–48445] Error encountered while checking if depreciation has run on asset_id &ASSET_ID.

[APP–48446] Asset &ASSET_NUM satisfied the query criteria for this What–If Analysis but will

not be analyzed because depreciation has not run on it yet.

[APP–48447] Error obtaining asset information for asset_id &ASSET_ID.

[APP–48448] Error obtaining current depreciation information for asset_id &ASSET_ID.

[APP–48449] Error obtaining distribution information for asset_id &ASSET_ID.

[APP–48450] Error calculating What–If depreciation for asset_id &ASSET_ID before commit.

[APP–48451] Unhandled exception encountered while calling main What–If function.

[APP–48452] No assets meet the query criteria entered for this What–If Analysis.

[APP–48453] The ending asset number must be alphabetically greater than the beginning asset

number.

[APP–48454] Category &CAT does not exist.

[APP–48455] Category &CAT is not enabled, not depreciable or not set up for this book.

[APP–48456] Depreciation method &METHOD does not exist.

[APP–48457] Prorate convention &CONV does not exist.

[APP–48458] Please enter a value between 0 and 100.

[APP–48459] You can only enter a life for life–based methods.

[APP–48460] One or more of the following required parameters is missing or invalid: BOOK,

START PERIOD, NUMBER OF PERIODS, AMORTIZE FLAG, FULLY RESERVED ASSETS

FLAG

[APP–48461] Error: Unable to generate warranty_id.

[APP–48462] You must enter both a start and end date, or leave both fields blank.

[APP–48463] Date placed in service does not fall within the warranty period.

[APP–48464] Location &LOC does not exist.

[APP–48465] Unable to get the concurrent request status using procedure

FND_CONCURRENT.GET_REQUEST_STATUS.

[APP–48466] Period name must be ten or fewer characters in length.

[APP–48467] The start and end dates are not within an existing fiscal year.

[APP–48468] You must delete the existing budget before you can upload or create a new budget.

[APP–48469] No dates have been specified for this fiscal year name.

[APP–48470] You cannot save while the Show Merged Distributions option is selected. Please

deselect it or use the Cancel button.

[APP–48471] Please close the Lease Payments window before performing this action.

[APP–48491] Lease Start_Date should coincide with the beginning of a period.

[APP–48492] You must update at least one asset assignment before saving this transaction.

[APP–48493] This Distribution Set Name already exists. Please enter a new value.

[APP–48494] The number of distribution units does not equal the total number of units.

[APP–48495] You must enter a life for a life–based method.

[APP–48496] The lease must use the same currency as the book to which it is assigned.

[APP–48497] Period name must be unique.

[APP–48498] You entered other transactions for this asset after this date or tried to amortize an

adjustment in the period the asset was added.

[APP–48499] In order to complete this transaction first run depreciation for this period in all the

Reporting books.

[APP–48500] In order to complete this transaction ensure that the Primary book and it’s Reporting

books are in the same period.

[APP–48501] In order to complete this transaction first run dpreciation for the associated Tax books

and it’s Reporting books.

[APP–48502] In order to complete this transaction first run depreciation in the Primary book.

[APP–48503] Trigger &TRIGGER failure. Unable to delete information from table &TABLE.

Error: &ERROR

[APP–48504] Trigger &TRIGGER failure. Unable to insert information from table &TABLE.

Error: &ERROR.

[APP–48505] Trigger &TRIGGER failure. Unable to select information from table &TABLE.

Error: &ERROR.

[APP–48506] Trigger &TRIGGER failure. Unable to update information in table &TABLE. Error:

&ERROR.

[APP–48507] Trigger &TRIGGER failure. Unable to determine transaction type. Book Type

Code=&BOOK_TYPE_CODE. Asset Id=&ASSEST_ID. Invoice Transaction

Id=&INVOICE_TRANSACTION_ID. Error: &ERROR.

[APP–48508] Unable to retrieve prior period exchange rate information. Error: &ERROR.

[APP–48509] Unable to retrieve current period exchange rate information. Error: &ERROR.

[APP–48510] Trigger &TRIGGER failure. Exchange rate is missing for this transaction. Asset

Id=&ASSET_ID. Book Type Code=&BOOK_TYPE_CODE. Set of Books

Id=&SET_OF_BOOKS_ID. Transaction Header ID=&TRANSACTION_ID. Error: &ERROR.

[APP–48511] Trigger &TRIGGER failure. Unable to retrieve book information. Asset

Id=&ASSET_ID. Error: &ERROR.

[APP–48512] Trigger &TRIGGER failure. Unable to determine if the asset was added in the

current period. Error: &ERROR.

[APP–48513] Unable to retrieve the depreciation status of book &BOOK_TYPE_CODE. Error:

&ERROR.

[APP–48514] Trigger &TRIGGER failure. Unable to retrieve invoice exchange rate information

from Oracle Payables. Invoice Id=&INVOICE_ID. Distribution Line

Number=&DISTRIBUTION_LINE_NUMBER. Error: &ERROR.

[APP–48515] Trigger &TRIGGER failure. Unable to retrieve invoice transaction information.

Book Type Code=&BOOK_TYPE_CODE. Asset Id=&ASSET_ID. Invoice Transaction

Id=&INVOICE_TRANSACTION_ID. Error: &ERROR.

[APP–48516] Trigger &TRIGGER failure. Unable to determine transaction date entered for this

asset. Asset Id=&ASSET_ID. Book Type Code=&BOOK_TYPE_CODE. Error: &ERROR.

[APP–48517] Trigger &TRIGGER failure. Unable to sum the cost of all the merged children for

this mass addition. Mass Addition Id=&MASS_ADDITION_ID. Parent Mass Addition

Id=&PARENT_MASS_ADDITION_ID. Set of Books Id=&SET_OF_BOOKS_ID. Error:

&ERROR.

[APP–48518] Trigger & TRIGGER failure. Unable to retrieve the cost of the parent mass addition.

Parent Mass Addition Id=&PARENT_MASS_ADDITION_ID. Set of Books

Id=&SET_OF_BOOKS_ID. Error: &ERROR.

[APP–48519] Unable to retrieve book information Asset Id = &ASSET_ID Book Type Code =

&BOOK_TYPE_CODE Transaction Header Id = &TRANSACTION_HEADER_ID Error:

&ERROR

[APP–48520] Unable to retrieve the multiple reporting currency flag the book

&BOOK_TYPE_CODE. Error: &ERROR.

[APP–48521] Trigger &TRIGGER failure. Exchange rate is missing for this mass addition line.

Mass Addition Id=&MASS_ADDITION_ID.

[APP–50000] You may only include one overtime category at a time

[APP–50001] You must enter GRE details for the assignment

[APP–50002] Invalid Government Reporting Entity

[APP–50003] Invalid Business Group for Government Reporting Entity

[APP–50004] Timecard Approver must be a current employee

[APP–50005] Invalid Business Group for Timecard Approver

[APP–50006] Timecard Required must be Yes(Y) or No(N)

[APP–50007] Invalid Work Schedule

[APP–50008] Spouse’s salary must be a number between 0.00 and 10000000.00, with two decimal

places

[APP–50009] Legal Representative must be Yes(Y) or No(N)

[APP–50010] Invalid Workers Compensation Override Code

[APP–50011] Invalid Reporting Establishment

[APP–50012] Invalid Business Group for Reporting Establishment

[APP–50013] You can enter a value for Workers Compensation Override Code only when updating

an assignment.

[APP–50014] The input_value_id for the input was not found

The input_value_id for the input value as not found.

[APP–50015] The jurisdiction entered is not adequate for the taxes adjusted.

The jurisdiction entered is not adequate for the taxes adjusted.

[APP–50019] Earnings in the category Regular must have the tax rule All

[APP–50020] The value entered for tax rule ( &code ) is invalid

[APP–50021] Oracle Human Resources could not retrieve a value for the Business Group profile

option. Please ensure it is set properly for your responsibility.

[APP–50022] Oracle Human Resources could not retrieve a value for the User Type profile option.

Please ensure it is set properly for your responsibility.

[APP–50023] You must choose a record before you can continue.

[APP–50024] You must save your work before you can continue.

[APP–50030] Fast Formula not found

[APP–50031] Report format not found.

[APP–50032] Defined balance not found.

[APP–50033] Jurisdiction code not found

[APP–50034] This report has already been run. Please roll back report before rerunning.

[APP–50035] Invalid report type requested.

[APP–50036] Submission to concurrent request failed.

[APP–50037] No valid employees for reporting exist.

[APP–50303] Merge Accounting successfully completed

[APP–50304] This source has not been copied to this target

Cause:

You entered a source sub that has not been copied

to the target you specified.

Action:

Enter a source that has been copied to this target.

Action:

Enter the target that you used to merge this source.

Action:

Merge these third parties before running this program.

[APP–50305] Cannot find specified API. Possible causes: 1. Package &PACKAGE does not exist. 2.

Module &MODULE does not exist in package &PACKAGE. 3. Either &PACKAGE or &MODULE

is an invalid name. Please enter a correct API specification.

[APP–50306] Package &PACKAGE is invalid. Please contact your system administrator.

[APP–50307] Cannot get information for remote object &OBJECT. Please contact your system

administrator.

[APP–50308] Specified object &OBJECT cannot be an API. Possible causes: 1. &OBJECT is a

function, but APIs must be procedures. 2. &OBJECT has no parameters, but APIs must have

parameters. Please specify a valid API.

[APP–50309] Program error: Overloaded APIs (such as &API) are not supported. Please contact

your support representative.

[APP–50310] Program error: API argument name &ARGUMENT has the wrong format. Please

contact your support representative.

[APP–50311] Program error: API argument &ARGUMENT is of unsupported type &TYPE. Please

contact your support representative.

[APP–50312] Seed data error: Mapping information for API parameter &PARAMETER is invalid.

Please contact your support representative.

[APP–50313] Mapping function package &PACKAGE does not exist or is in an invalid state. Please

contact your system administrator.

[APP–50314] Seed data error: Mapping function &FUNCTION does not exist. Please contact your

support representative.

[APP–50315] Program or seed data error: Bad mapping function name &OBJECT. Please contact

your support representative.

[APP–50316] Seed data error: Mapping function &FUNCTION is a procedure when it should be a

function. Please contact your support representative.

[APP–50317] Seed data error: The return type of mapping function &FUNCTION does not match

the type of the mapped API parameter &PARAMETER. Please contact your support representative.

[APP–50318] Seed data error: Cannot process overloaded mapping functions such as &OBJECT.

Please contact your support representative.

[APP–50319] Seed data error: Mapping function &FUNCTION has argument &ARGUMENT of

unsupported type &TYPE. Please contact your support representative.

[APP–50320] Seed data error: Argument &ARGUMENT cannot be used consistently. Please contact

your support representative.

[APP–50321] Program error: Number of required arguments (&TOTAL) exceeds the maximum

number permissible (&MAXIMUM). Please contact your support representative.

[APP–50322] Program error: Compilation of object &OBJECT failed. Please contact your system

administrator.

[APP–50323] Program error: Generated code size exceeds maximum buffer size. Please contact

your support representative.

[APP–50324] Generated package: &PACKAGE

[APP–50325] Generated view: &VIEW

[APP–50326] Program error: Could not find row in &TABLE whose &COLUMN value is

&VALUE. Please contact your support representative.

[APP–50327] Bad &TYPE value (&VALUE) for parameter &PARAMETER found in table

&TABLE when attempting to call the API. Please correct the value and try again.

[APP–50328] Seed data error: Seed data for parameter &ARGUMENT was found. Parameter

&ARGUMENT may not appear in the seed data. Please contact your support representative.

[APP–50329] Progam error: The header status indicates that this batch is already processing. Please

contact your support representative.

[APP–51000] Invalid position

This position does not exist at all, or is not completely within the assignment’s date range.

[APP–51001] This vacancy does not exist

[APP–51002] Cannot submit report

Possible causes could be that the report does not exist, The concurrent request manager is not

working.

[APP–51003] Assignment must have a valid pay period at actual termination date

[APP–51005] Person type must be a type of EMP at actual termination date

[APP–51006] Payroll must have a valid pay period at actual termination date

[APP–51007] Actual termination date must exist before setting final process date

[APP–51008] Person type must be a type of EX_EMP at final process date

[APP–51009] This position is not in the same business group as the assignment.

[APP–51010] Formula return &RET_NAME exceeds size limit of &LIM_SIZE characters.

[APP–51011] Person does not exist at specified date

[APP–51012] Cannot rehire a person who is not a type of EX_EMP

[APP–51013] This person does not have a previous period of service

[APP–51014] Cannot rehire a person unless a final processing date exists for their previous period

of service

[APP–51015] The rehire date must be later than the final processing date of the previous period of

service

[APP–51017] Assignment Number must be null for applicant assignments

[APP–51018] Hierarchy Level must be greater than 0.

The Hierarchy level specified must be greater than 0.

[APP–51019] Primary Key Constraint Error

Combination of Entity Name and Pattern Purpose is not unique.

[APP–51020] Unique Key Constraint Error.

Combination of Entity Name and Pattern Purpose is not unique.

[APP–51021] Unique Key Constraint Error.

Combination of Pattern Purpose and Hierarchy Level is not unique.

[APP–51022] Invalid primary key specified.

The Primary key specified is invalid.

[APP–51023] The Pattern Bit Specified is not unique.

Pattern Bit specifed is not unique.

[APP–51024] Multiplier must be positive whole number.

Multiplier must be greater than 0.

[APP–51026] This record is locked by another user.

The Object specified is currently locked. Try again later.

[APP–51027] API Error. Invalid Object Version Number.

Invalid Object Version Number. Re–query and try again.

[APP–51028] Employment category is not valid

[APP–51029] Choose a date on which the assignment includes a payroll

[APP–51030] There is a gap in the continuity of Primary Addresses.

[APP–51030] There is a gap in the continuity of Primary/Main Addresses.

[APP–51031] Employee is a supervisor, changing hire will invalidate this.

[APP–51032] Employees previous Employment,has not been closed for more than a day.

[APP–51033] Future dated salary administration records exist

[APP–51034] Retropay encountered an Incomplete Assignment Action

Retropay is unable to process any Assignment Action with a status that is not complete. The

effective date for the incomplete action is &EFFECTIVE_DATE.

[APP–51036] The assignment must be an applicant assignment as of the effective date.

When attempting to update an applicant assignment the assignment type should be of type ’A’

(Applicant). An error occurs when the update of an employee assignment is attempted with

assignment type of ’A’.

[APP–51037] This action MAY affect the value of balances. Do you wish to continue?

By deleting a balance feed, or taking action which may result in balance feeds being deleted, you

may affect the value of balances which have already been fed by this input value.

[APP–51038] The usage may not start before the calendar starts.

You may not assign someone to a calendar for a period of time before the calendar has come into

being. Please choose a date later than &CALENDAR_START_DATE.

[APP–51039] A Workers Compensation override rate for this state and carrier is being referenced

[APP–51040] The applicant assignment position doesn’t match it’s vacancy position.

The position_id for the assignment should match the position_id of the assignment’s vacancy but

only if the position_id for the vacancy is not null.

[APP–51041] The applicant assignment location doesn’t match it’s vacancy location.

When the vacancy_id for an assignment is not null and the location_id for this vacancy in

PER_VACANCIES is also not null. Then the location_id of the vacancy should match the

location_id of the assignment.

[APP–51042] The applicant assignment organization doesn’t match it’s vacancy organization.

When the assignment vacancy_id is not null and the organization_id for this vacancy is not null then

the vacancy organization_id should match the assignment organization_id.

[APP–51043] The Payroll specified does not exist.

[APP–51044] The Balance Dimension does not exist.

[APP–51045] Initial Balance Upload does not Support this Balance Dimension.

[APP–51046] The Tax Unit does not exist.

[APP–51047] The ORIGINAL_ENTRY_ID context must be specified.

[APP–51048] The Original Element Entry does not exist.

[APP–51049] The Balance does not exist.

[APP–51050] Balance does not have an initial balance feed.

[APP–51051] Balance does not have an element link for its initial balance feed.

[APP–51052] Assignment must be an employee assignment.

[APP–51053] Assignment has already been processed before the upload date.

[APP–51054] The position definition flexfield structure is invalid

[APP–51055] The assignment position and organization combination is invalid.

The position and organization combination for the assignment should match the position and

organization combination in PER_POSITIONS.

[APP–51056] The assignment position and job combination is invalid

The position and job combination for the assignment should match the position and job combination

in PER_POSITIONS.

[APP–51057] The job for the assignment position and job combination cannot be null

The POSITION_ID and JOB_ID combination for the assignment should match the position

combination in PER_POSITIONS. Hence the assignment JOB_ID cannot be a null value.

[APP–51058] An error occurred in hrentmnt.validate_adjust_entry. Contact your Oracle Support

Representative.

The cursor csr_ele_info in the pl/sql package, hrentmnt.validate_adjust_entry returned no rows

(unexpectedly). The parameters of the procedure were: p_mode = $P_MODE p_assignment_id =

$P_ASSIGNMENT_ID p_element_entry_id = $P_ELEMENT_ENTRY_ID p_start_or_end_date =

$P_START_OR_END_DATE p_old_date = $P_OLD_DATE p_new_date = $P_NEW_DATE

p_effective_start_date = $P_EFFECTIVE_START_DATE p_effective_end_date =

$P_EFFECTIVE_END_DATE p_entries_changed = $P_ENTRIES_CHANGED

[APP–51059] The absence duration in days/hours must be entered.

The absence duration in days or hours must be entered. Enter a duration value in the duration field

to proceed.

[APP–51060] The calendar start position must be between 1 and $MAXIMUM

The pattern consists of $MAXIMUM distinct parts. You may not enter a number which does not

correspond to one of the parts.

[APP–51061] The start position must be positive

The start position must be greater than zero.

[APP–51062] The calendar starts on the wrong weekday.

The pattern definition specifies that any calendar using it must start on a $WEEKDAY. If you have

specified a pattern start position greater than 1 then the system will go back from the start time to

work out the day on which the first pattern bit would fall.

[APP–51063] The calendar starts at the wrong time.

The pattern definition specifies that any calendar which uses it must start at $START_TIME. If you

have specified a pattern start position greater than 1 then the system will take into account the offset

to work out the time at which bit 1 of the pattern would start.

[APP–51064] The calendar name must be unique

[APP–51065] The calendar_id must be unique.

The system–generated key for HR_CALENDARS is not unique. Contact your system administrator.

The sequence in use was HR_CALENDARS_S.

[APP–51066] The pattern is not valid.

You must choose a valid pattern on which to base your calendar.

[APP–51067] The primary key value is invalid.

The specified identifier of the $ENTITY_NAME does not correspond to a record which exists on

$START_DATE. Enter a valid identifier.

[APP–51068] The calendar is not valid.

The calendar you specified does not exist. Please enter a valid calendar.

[APP–51069] The entity and purpose may not be combined.

You may not attach a calendar to the entity selected for the purpose you specified. Please choose a

different combination.

[APP–51070] The start date must precede or equal the end date.

[APP–51071] The pattern is not appropriate for SSP.

The pattern on which the calendar is based is not appropriate for an SSP qualifying pattern. Choose

a calendar based on a pattern which comprises only qualifying and non qualifying days.

[APP–51072] There is already a calendar for this entity and purpose at this time.

At any given time, there may be only one calendar attached to an entity for a given purpose. Check

the start and end dates you have selected.

[APP–51073] SSP qualifying patterns must be whole days.

The pattern is defined as being potentailly used for an SSP qualifying pattern. You chose a pattern

construction which consisted of a time period which was not a whole multiple of a day. This is not

allowed for SSP qualifying patterns.

[APP–51074] Not a valid availability.

The availability must be one of the pre–defined values which you set up in the lookups screen.

Choose a valid one (a list of values may be available if you are using Oracle Forms), or set up the

new one in the lookups screen.

[APP–51075] Patterns may be broken down to only one further level.

Patterns may consist of other patterns, but only if the component pattern is not itself further broken

down into patterns. Choose a different pattern.

[APP–51076] Not a valid pattern

You must choose a valid pattern for the pattern purpose.

[APP–51077] The pattern purpose must be unique for the pattern.

[APP–51078] The pattern purpose is not valid.

The pattern purpose must be one of the pattern purpose lookup values.

[APP–51079] Not a valid SSP qualifying pattern.

In order to be used as an SSP qualifying pattern, a pattern must: 1. Be composed only of whole

days or multiples of whole days. 2. Be required to start at 00:00 hours. 3. Be composed only of

’qualifying’ and ’non qualifying’ days. 4. Be guaranteed to have at least one day in every seven as

a qualifying day.

[APP–51080] The time must be specified in the format HH24:MI.

For example, 22:37.

[APP–51081] The pattern name must be unique.

[APP–51082] This grade does not exist.

[APP–51083] This grade does not exist for your current Business Group.

[APP–51084] The valid grade’s start date must be earlier than or equal to its end date.

[APP–51085] The start date you enter must be between the grade’s start and end dates.

[APP–51086] The valid grade’s start date must be later than or equal to the start date of the job.

[APP–51087] The valid grade’s start date must be later than or equal to the start date of the position.

[APP–51088] Enter a valid grade for either job or position, not for both.

[APP–51089] Enter a valid grade for either job or position.

[APP–51090] This job does not exist.

[APP–51091] This job does not exist in your current Business Group.

[APP–51092] A valid grade already exists for this job and grade combination.

[APP–51093] This position does not exist.

[APP–51094] This position does not exist in your current Business Group.

[APP–51095] A valid grade already exists for this position and grade combination.

[APP–51096] The valid grade’s end date must be later than or equal to its start date.

[APP–51097] The end date you enter must be between the grade’s start and end dates.

[APP–51098] The valid grade’s end date must be earlier than or equal to the end date of the job.

[APP–51099] The valid grade’s end date must be earlier than or equal to the end date of the

position.

[APP–51100] Prior employment SSP weeks must be an integer greater than zero.

[APP–51101] SSP1L details must be fully entered.

If you enter prior employment SSP details, you must complete both the weeks paid and the paid to

date fields.

[APP–51102] The SSP paid to date must be before the hire date.

The prior employment SSP paid to date refers to the last date SSP was paid to an employee with the

employer he had before this period of service began.

[APP–51103] This Assignment was not moved to the target position.

Cause:

This assignment has a future change pending.Mass Moves does not muove such assignments.

Action:

Use the assignment or application form toassociate this assignment with target position.

[APP–51104] This assignment was not moved/updated.

Cause:

You must change an assignment’s organization,position, location, standard conditions, GRE/Legal

Entity or grade.

Action:

Define a new mass move changing at least oneof these attributes.

[APP–51105] The Defined Balance specified does not exist.

[APP–51106] Currency required for monetary Element Type

Currency code must not be null for an Element Type that has an Input Value with Money Unit Of

Measure.

[APP–51108] You cannot clear saved components in this region.

Saved components cannot be cleared in components region.

[APP–51109] A job requirement already exists for this job and analysis criteria.

[APP–51110] A job requirement already exists for this position and analysis criteria.

[APP–51111] The analysis criteria does not exist.

[APP–51112] Enter a job or position, but not both.

[APP–51113] Essential must be ’Y’ or ’N’.

[APP–51114] This special information type does not exist.

[APP–51115] This special information type is not enabled.

[APP–51116] This task flow name already exists.

[APP–51117] To use multiple components, clear the changes in the change amount field.

[APP–51118] Error was encountered when processing assignment &ASGNO

[APP–51119] Error was encountered when processing Element Type &ETNAME

[APP–51120] Error was encountered when processing formula &FMLANAME

[APP–51121] Error was encountered when processing Skip formula &FMLANAME

[APP–51122] A Task Flow name is required. Please enter a valid value.

[APP–51123] You cannot copy a Task Flow that you haven’t saved.

[APP–51124] No manager exists in this assignment’s source organization.

Cause:

The manager assignment has been moved from the source organization, leaving no manager.

Action:

None, this is a warning only.

[APP–51126] This assignment change has altered at least one salary element entry.

[APP–51128] This position change has altered at least one valid grade.

Cause:

Deactivating the source position has resultedin deactivating the valid grades for this position.

Action:

None, this is a warning only.

[APP–51129] Assignments associated to a vacancy are not moved to the target position.

Cause:

This assignment has an associated vacancy.Assignments with vacancies will not move to the target

position.

Action:

Use the assignments form to associate withthe target position.

[APP–51131] You can only perform a word processor mail merge from Microsoft Windows.

[APP–51132] Link does not exist for element &ELEMENT

Link for the element does not exist.

[APP–51133] The location is not a valid work location for the assignment.

The location is not a valid work location for the assignment.

[APP–51134] The total tax withheld is not equal to the difference between the gross and net

earnings.

The total taxes withheld is not equal to the difference between gross and net earnings.

[APP–51135] Cannot determine the assignment_id and/or business_group_id.

Cannot determine the assignment_id and/or business_group_id.

[APP–51136] Could not determine the consolidation_set_id.

Could not determine the consolidation_set_id.

[APP–51139] You have already created an address for this person and address type which overlaps

this date range.

[APP–51140] An earnings element must be specified.

An earnings element must be specified since the gross earnings are non–zero.

[APP–51141] SIT withheld entered for a state that does not have SIT tax.

SIT Withheld entered for a state that does not have an SIT tax.

[APP–51142] SDI_EE withheld entered for a state that does not have SDI_EE tax.

SDI_EE tax withheld for a state that does not have SDI_EE tax.

[APP–51143] The employee cannot supervise themself.

The employee for the assignment cannot be the same as the supervisor. As a supervisor cannot

supervise themself.

[APP–51145] The supervisor’s business group should match the employee’s business group.

The supervisor should be in the same business group as the business group on the employee

assignment.

[APP–51147] The date probation end must be after the earliest effective start date for the

assignment.

[APP–51148] The default code combination does not exist for the date effective period of the

assignment.

The specified default code combination does exist in the table GL_CODE_COMBINATIONS or

exists but is not active for the date effective period of the assignment.

[APP–51149] The performance review period frequency doesn’t exist.

[APP–51151] This type of probation unit does not exist.

[APP–51152] Invalid money format.

[APP–51153] Invalid number or integer format.

[APP–51154] Invalid Time format.

[APP–51155] Invalid date format.

[APP–51157] Invalid Pay_Name format.

[APP–51158] Invalid NACHA format.

[APP–51159] Invalid value format.

[APP–51160] The set of books does not exist.

[APP–51161] The set of books cannot be updated for an assignment.

[APP–51162] The source type does not exist.

[APP–51163] The perf review period frequency and perf review period must both be not null for the

assignment.

[APP–51164] The salary review period frequency does not exist.

[APP–51165] The salary review period frequency and salary review period combination should both

be set or both be not set.

[APP–51166] The probation unit and probation period combination must both be set or both be not

set.

[APP–51167] The probation period is out of the range 0 to 99.99.

[APP–51168] The pay basis you have entered for this assignment does not exist.

[APP–51169] Enter the same Business Group for pay basis and assignment.

[APP–51170] The Payment Type specified is not for Magnetic Tape.

[APP–51171] You cannot update this assignment as a pay proposal exists for it with a change date

after its effective start date.

[APP–51172] The job you have entered for this assignment does not exist.

[APP–51173] Enter the same Business Group for job and assignment.

[APP–51175] You can define a set of books only for an employee assignment.

[APP–51176] You can define a pay basis only for an employee assignment.

[APP–51177] You can define a default code combination only for an employee assignment.

[APP–51178] You can define a performance review frequency only for an employee assignment.

[APP–51179] You can define a performance review period only for an employee assignment.

[APP–51180] You can define a salary review period only for an employee assignment.

[APP–51181] You can define a salary review period frequency only for an employee assignment.

[APP–51182] You may not update a salary proposal entry in this mode.

Cause:

You attempted to update an attribute, other than an entry value, of a salary proposal element entry in

a prohibited datetrack mode.

Action:

Choose either ’UPDATE_CHANGE_INSERT’ or ’CORRECTION’ as the datetrack update mode.

[APP–51183] The business group you specified for this application does not exist.

[APP–51184] The application id already exists.

[APP–51185] Select one of these system person types for the applicant you are creating: APL,

EMP_APL, APL_EX_APL, EX_EMP_APL

The system person type must be one of the following values for people who are applicants : APL,

EMP_APL APL_EX_APL, EX_EMP_APL

[APP–51186] Enter either Y or N for Successful.

[APP–51187] The applicant and the application must be in the same business group.

[APP–51188] The date received must be earlier than the end date.

[APP–51189] The date received must be earlier than or equal to the projected hire date.

[APP–51190] An application for this person with the same date received already exists.

An application for this person with the same date received already exists.

[APP–51192] The projected hire date must be later than or equal to the date received.

[APP–51194] The applicant does not exist in the system on the date received.

There must be an instance of the applicants’ person record that starts on the date received.

[APP–51195] The Zip code is incorrect for this address.

[APP–51198] You cannot define an applicant assignment as a primary assignment.

[APP–51200] You must enter a value for applicant number.

[APP–51201] The applicant number is system generated and cannot be modified.

[APP–51203] You can define a period of service only for an employee assignment.

[APP–51204] Total time in state(s) exceeds 100%.

[APP–51206] Select an ’ACTIVE’ assignment status type for this assignment.

[APP–51207] Enter the same Business Group for assignment status type and assignment.

[APP–51208] You cannot terminate this assignment Future Element Entries Exist.

[APP–51210] The application does not exist with a date received which is the same as the effective

start date of the assignment.

[APP–51211] You cannot enter application details when creating an employee assignment.

[APP–51212] You must enter application details when creating an applicant assignment.

[APP–51213] You cannot delete existing application details when creating an employee assignment.

[APP–51214] Enter the same Business Group for the application and assignment.

[APP–51215] The location should be active for the assignment.

[APP–51216] You can define a recruiter only for an applicant assignment.

[APP–51217] You can define an employment category only for an employee assignment.

[APP–51218] Give the applicant assignment a system status of ’ACTIVE_APL’ when you create it.

[APP–51219] You cannot enter source organization details when creating an employee assignment.

[APP–51220] You cannot change source organization details when modifying an employee

assignment.

[APP–51221] You cannot enter vacancy details when creating an employee assignment.

[APP–51222] You cannot change vacancy details when modifying an employee assignment.

[APP–51223] You can only define a recruitment activity for an applicant assignment.

[APP–51224] You can only define ’Person referred by’ for an applicant assignment.

[APP–51225] You can only define a special ceiling step for an employee assignment.

[APP–51226] You can only define a payroll for an employee assignment.

[APP–51227] You can only define a soft coded keyflex for an employee assignment.

[APP–51228] You have entered an invalid change reason for an employee assignment.

[APP–51229] You have entered an invalid change reason for an applicant assignment.

[APP–51230] You can only set an internal address line for an employee assignment.

[APP–51231] There is no applicant assignment associated with this person on the date you

specified.

[APP–51232] The assignment status type for an applicant assignment should be ACTIVE_APL or

OFFER.

[APP–51233] You must enter the first line of the address to complete the address.

[APP–51234] You cannot change the end date of the application except to make it null.

[APP–51235] You entered an end date for the application earlier than the date received.

[APP–51236] You set an end date for the application earlier than future changes already made to the

applicant’s assignment record. Change the end date or delete the future changes.

[APP–51237] You set an end date for the application earlier than future changes already made to the

applicant’s personal record. Change the end date or delete the future change.

[APP–51238] You entered a termination reason that is not on the list of valid values.

[APP–51239] You cannot update this employee number as it is generated automatically.

[APP–51240] You cannot enter this employee number manually; it is generated automatically.

[APP–51241] You cannot enter this employee number manually; it is generated by the system from

the National Identifier number.

[APP–51242] You must enter a value for the employee’s National Identifier as the employee number

generation method is based on this number.

[APP–51243] You entered a value that is not on the list of valid values for I–9.

[APP–51245] You entered a value that is not on the list of valid values for visa types.

[APP–51246] You entered a value that is not on the list of valid values for veteran status.

[APP–51247] You entered a value that is not on the list of valid values for student flag.

[APP–51248] You entered a value that is not on the list of valid values for the registered disabled

flag.

[APP–51249] You entered a value that is not on the list of valid values for vendor id.

[APP–51250] You can only enter a value for vendor id if the system person type is EMP,

EMP_APL, EX_EMP or EX_EMP_APL.

[APP–51251] You specified an invalid value for ’expense check send to address.’

[APP–51252] Enter an enabled people group.

[APP–51254] A salary proposal cannot be created for an applicant.

[APP–51256] You entered an Employee Data Verified date earlier than the start date.

[APP–51259] Please enter a review date, before entering the next performance review date.

[APP–51261] Please enter ’Y’ or ’N’ for the Multiple_Components field.

[APP–51262] The first salary proposal for the assignmnet cannot have multiple components.

[APP–51263] This event is not valid for this assignment.

[APP–51266] The Performance rating must not be entered, if the review date is not entered.

[APP–51268] The record is protected against update.

[APP–51269] You cannot approve a salary proposal, if the salary amount is not entered.

[APP–51270] You cannot unapprove a proposal which has already being approved.

[APP–51271] The assignment is not eligible for the element.

You may not grant the element &ELEMENT_NAME to assignment number

&ASSIGNMENT_NUMBER on &SESSION_DATE. The assignment is not eligible for the element

on that date. Eligibility is determined by the element link. In order to be eligible, the link criteria

must be met by the assignment at all times during the life of an element entry.

[APP–51272] The value you entered for Additional Pension Years is outside the valid range of 0 to

99.

[APP–51273] The value you entered for Additional Pension Months is outside the valid range of 1

to 11.

[APP–51274] You must enter Y or N for the NI Multiple Assignments flag.

[APP–51275] You cannot modify an applicant assignment with an initial terminated status.

[APP–51276] You have entered a city that is invalid.

[APP–51277] The organization should be an HR organization for all assignments other than the

first.

[APP–51278] Please enter ’Y’ or ’N’ for the approved flag.

[APP–51279] Invalid combination of city, county and state

[APP–51280] The recruiter you enter must exist on the effective date of the assignment.

[APP–51281] Enter the same recruiter for applicant assignment and vacancy.

[APP–51282] Zip code is incorrect for the city, county and state entered for this address.

[APP–51283] The address must be US style

[APP–51284] Enter the same Business Group for recruiter and applicant assignment.

[APP–51285] You entered a value that is not on the list of valid values for new hire.

[APP–51286] You cannot enter a value for New Hire Exception Reason if you enter ’Exclude’ in the

New Hire field.

[APP–51287] The value you entered for New Hire Exception Reason is not on the list of valid

values.

[APP–51288] Enter either Y or N in the Child Support Obligation field.

[APP–51289] You have entered the same name for applicant and recruiter.

[APP–51290] The recruiter must be an employee.

[APP–51291] Enter the same grade for applicant assignment and vacancy.

[APP–51292] The review date cannot be before the assignment date. Please enter a valid review

date.

[APP–51293] Enter the same job for applicant assignment and vacancy.

[APP–51294] Enter a person type for an applicant assignment which is either ’APL’,

’APL_EX_APL’, ’EMP_APL’ or ’EX_EMP_APL’.

[APP–51295] QuickPay cannot process entries that require ’separate check’ or ’tax separately’

processing. To run QuickPay for this assignment you must deselect these earnings types.

To include these earnings types you should include the employee in an assignment set and submit

the batch Payroll Process for this one employee. The batch process will manage both standard and

separate processing.

[APP–51296] Enter the same people group for applicant assignment and vacancy.

[APP–51297] The vacancy you enter must exist on the start date of the assignment.

[APP–51300] Enter the same Business Group for vacancy and assignment.

[APP–51302] The ’person referred by’ does not exist on the database at the start of the assignment.

[APP–51303] Enter the same Business Group for ’person referred by’ and assignment.

[APP–51304] The ’person referred by’ cannot be same person as the applicant.

[APP–51305] The ’person referred by’ must be an employee.

[APP–51306] The recruitment activity does not exist at the start of the assignment.

[APP–51307] Enter the same Business Group for recruitment activity and assignment.

[APP–51308] The source organization does not exist at the start of the assignment.

[APP–51309] Enter the same Business Group for source organization and assignment.

[APP–51310] The proposal_id is not valid. Please enter a valid proposal_id.

[APP–51311] You cannot insert or update a salary component,if the associated salary proposal has

already been approved.

[APP–51312] Salary component cannot be created for this salary proposal.

[APP–51313] The reason for a salary component must be unique.

[APP–51315] You cannot delete a salary component, if the associated proposal has already been

approved.

[APP–51316] The set of books must exist as a financials system parameter for the assignment

Business Group.

[APP–51317] The business_group_id is not valid. Please enter a valid business_group_id.

[APP–51318] A component reason must be enterd,before approving the salary component.

[APP–51319] The component_id is invalid. Please enter a valid component_id.

[APP–51320] Enter the same Business Group for period of service and assignment.

[APP–51322] The effective date for all DateTracked operations must not include a time component.

[APP–51323] Do not enter an end date when you first create a primary assignment.

[APP–51324] Cannot make an adjustment to a non–recurring element entry

[APP–51325] The source type must be the same as the type of the assignment recruitment activity.

[APP–51326] This salary proposal has one or more components. Please delete the components

before deleting the overall proposal.

[APP–51327] SDI withheld in a state that is not currently the primary work state.

[APP–51328] The SUI state for this assignment does not have employee SUI taxes.

[APP–51329] Enter a person type for an employee assignment which is either ’EMP’ or

’EMP_APL’.

[APP–51330] The target position already exists outside the target organization.

Cause:

Two organizations may not have the sameposition definiton. You have attempted to create a new

position when an identical position already exists to another organization.

Action:

Make the position unique.

[APP–51331] Assignments were not moved from the source position to the target position.

Cause:

The mass move effective date is outside the date range of the target position.

Action:

Update the target position effective dates to encompass the mass move effective date, or alter the

mass move effective date.

[APP–51332] This combination of categories already exist. Please clear the form and query for this

combination.

[APP–51333] Vacancies associated with the source position did not move to the target position.

Cause:

Automatic moving of vacancies is not enabled.

Action:

Use the Requisition and Vacancy form toassociate with the target position.

[APP–51334] Job Evaluations associated with the source position did not moved to the target

position.

Cause:

Automatic moving of job evaluations is notenabled.

Action:

Use the Position form to associate the target position with the job evaluation.

[APP–51335] The target position has a future end date.

Action:

None, this is a warning only.

[APP–51336] Your initial amount cannot exceed your maximum amount. Please adjust the

amounts.

[APP–51337] A value for the key flex segment cannot be entered.

[APP–51346] The supervisor should be an employee.

[APP–51348] The object version number is invalid.

[APP–51349] The date of a salary proposal cannot be updated.

[APP–51350] No personal payment method external account structure exists for the organisational

method you selected.

[APP–51351] The personal payment method you selected does not exist.

[APP–51356] Timeout while writing to dbms_pipe. You must run monitor the trace pipe using

PYUPIP if trace is enabled.

[APP–51357] The location does not exist

[APP–51358] The job is not valid for the current date

[APP–51359] The organization is not valid for the current date

[APP–51360] The successor position can not be the current position

[APP–51361] The relief position can not be the current position

[APP–51362] The current date effective must be earlier than the date end

[APP–51363] The position frequency is invalid

[APP–51365] Combination of probation period and probation units is invalid.

[APP–51366] Probation units is invalid

[APP–51367] Combination of time start and time finish is invalid.

[APP–51368] Time finish must be later than time start

[APP–51369] The position definition doesn’t exist

[APP–51370] Replacement required must be Y or N

[APP–51371] The organization does not exist

[APP–51372] The combination of working hours and frequency is invalid

[APP–51373] You cannot approve a proposal before approving all the components.

[APP–51374] A validation error has occurred during the approval process.

[APP–51375] You can only define an applicant assignment where the effective start date of the

assignment is between the date received and date end of the application.

[APP–51376] Your session date has to be between the Start Date and End date

[APP–51377] You cannot enter values into non Magnetic Tape Personal Payment segments. They

must always be null.

[APP–51378] You are not authorized to see more details on this person

[APP–51379] The Contact Type you have entered for this Contact Relationship does not exist.

[APP–51380] Target position is required if selected to move.

[APP–51381] Target job is required if selected to move.

[APP–51382] New requirement and delete flag cannot both be set.

[APP–51383] Applicants cannot be assigned a GRE/Legal Entity.

[APP–51384] There are no positions in the source organization.

[APP–51385] The Beneficiary Flag must be set to ’Y’ or ’N’

[APP–51386] The Bondholder Flag must be set to ’Y’ or ’N’

[APP–51387] The Dependant Flag must be set to ’Y’ or ’N’

[APP–51388] The Primary Contact Flag must be set to ’Y or ’N’

[APP–51389] The Person ID that you have entered does not exist

[APP–51392] Assignments exist for this period of service. Delete these assignments before deleting

the period of service.

[APP–51393] WF_SESSION cookie does not exist. The workflow user cannot be established.

[APP–51394] Sorry, the resume details for this candidate are not available. The number of pages

for the candidate’s resume has been entered incorrectly.

[APP–51394] Sorry, the resume details for this candidate are not available. The number of resume

pages has been entered incorrectly.

[APP–51395] Your Business Group was not found in PER_BUSINESS_GROUPS.

[APP–51396] Your person ID was not found in PER_PEOPLE. Please contact your system

administrator.

[APP–51397] Your candidate was not found in the database.

[APP–51398] Invalid location. Please update the location and save again. Save processing will

continue without this information.

[APP–51398] Invalid location. Please update the location and save again. Save processing will

continue without this information.

[APP–51399] Invalid job code. Please update the job code and save again. Save processing will

continue without this information.

[APP–51400] The question has an invalid html type defined.

[APP–51401] You are not authorized to see this information.

[APP–51402] The hire date cannot be changed in UPDATE.

[APP–51403] Question not found.

[APP–51404] Question length error.

[APP–51405] The competence_id is either invalid or not effective from the date that you have

entered.

[APP–51406] Enter selection criteria to display a list matching values.

[APP–51406] Enter selection criteria to find a list matching values.

[APP–51411] Sorry, the resume details for this candidate are not available. A resume reference code

and resume number of pages have not been specified by the hiring manager.

[APP–51411] Sorry, the resume details for this candidate are not available. A resume reference code

and the number of pages for the resume have not been specified by the hiring manager on the

candidate’s offer profile.

[APP–51412] Sorry, the resume details for this candidate are not available. A resume reference code

has not been specified by hiring manager in the Offer Profile.

[APP–51412] Sorry, the resume details for this candidate are not available. A resume reference code

has not been specified by the hiring manager on the candidate’s offer profile.

[APP–51413] Sorry, the resume details for this candidate are not available. The number of pages

for the resume has not been specified by the hiring manager on the candidate’s offer profile.

[APP–51413] Sorry, the resume details for this candidate are not available. The number of resume

pages has not been specified by the hiring manager in Offer Profile.

[APP–51414] Sorry, the resume details for this candidate are not available. The hiring manager

does not exist. Please contact the HR department.

[APP–51414] Sorry, the resume details for this candidate are not available. The hiring manager dose

not exist. Please contact the HR department.

[APP–51415] Pay value is a restricted name. You can not change the input value name to pay value

after it has been saved.

[APP–51416] Bank Name must not exceed 30 characters.

[APP–51417] The bank name you entered is not a predefined GB bank.

[APP–51418] Bank Branch must not exceed 35 characters.

[APP–51419] Sort Code must be 6 digits long.

[APP–51420] Sort Code must be a positive number.

[APP–51421] Account Number must be 8 digits long.

[APP–51422] Account Number must be a positive number.

[APP–51423] Account Name must not exceed 18 characters.

[APP–51424] Account Name must be in upper case.

[APP–51425] Account Type must not exceed 1 digit.

[APP–51426] Account Type must be in the range of 0 to 5.

[APP–51427] Building Society Account Number must not exceed 18 characters.

[APP–51428] Building Society Account Number must be in upper case.

[APP–51429] Bank Branch Location must not exceed 20 characters.

[APP–51430] The bank branch location you entered is not a predefined location.

[APP–51432] Enter Y if the competence requires certification, otherwise enter N

[APP–51433] The evaluation method you entered is invalid. Enter a valid one.

[APP–51434] The renewable period unit you entered is invalid. Enter a valid one.

[APP–51435] Enter both renewable period unit and renewable period frequency, otherwise leave

both fields blank

[APP–51436] A competence with this name already exists. Enter a new name.

[APP–51437] A general proficiency scale cannot be entered because specific proficiency levels

exist for the competence.

[APP–51438] A specific proficiency level cannot be entered because a general proficiency scale has

been entered for the competence.

[APP–51439] This competence has proficiency levels – these will be deleted.

[APP–51440] You cannot delete a competence that is used in a competence element.

[APP–51441] Enter a name for the competence.

[APP–51442] Only rating scales of type ’Proficiency’ can be assigned to competences

[APP–51443] Cannot update rating scale as levels exists in competence element

[APP–51444] The lookup type you have entered is invalid. Enter one of the following: Proficiency,

Performance, Weighting.

[APP–51449] This rating scale name already exists in this Business Group.

[APP–51450] The lookup type you have entered is invalid. Enter one of the following : Y, N

[APP–51451] A default already exists for this type. You cannot have more then one default for a

type.

[APP–51452] This rating scale does not exist in the current business group

[APP–51453] The rating scale is not in the same business group as the competence

[APP–51454] You cannot update a salary component amount or percentage, if the component is

already approved.

[APP–51455] This record has already been changed by another user.Please execute a query on this

record to see the changes.

[APP–51456] Error while calculating effective_end_date

[APP–51457] There is no object version number for this external account.

[APP–51458] Account Name must not exceed 60 characters.

[APP–51459] Account Type must not exceed 80 characters.

[APP–51460] The account type you entered is not a predefined US account type.

[APP–51461] Acount Number must not exceed 60 characters.

[APP–51462] Transit Code must not exceed 9 digits.

[APP–51463] Bank Name must not exceed 60 characters.

[APP–51464] Bank Branch must not exceed 60 characters.

[APP–51465] There is no Tax Information specified for this assignment in this location.

There is no Tax Information specified for this assignment in this location.

[APP–51470] This rating scale is not in the same business group as the rating level.

[APP–51471] This rating scale does not exist in the current business group.

[APP–51472] This competence does not exist in the current business group.

[APP–51473] This competence is not in the same business group as the rating level.

[APP–51474] A rating level with this name already exists. Enter a new name.

[APP–51475] Enter a name for the rating level.

[APP–51476] Enter a step value for this level.

[APP–51477] A rating level with this step value already exists. Enter a new one.

[APP–51479] A rating level cannot be deleted if either i. it is referenced by a competence which is

already used in a personal competence profile, competence requirement, or an assessment OR ii. it

is referenced itself in a personal competence profile, competence requirement, or an assessment A

rating level cannot be inserted if it is referenced by a competence which is already used in a

personal competence profile, competence requirement, or an assessment

[APP–51480] You cannot add/delete a level that is used as a general rating scale for a competence.

[APP–51481] You cannot add/delete a level that is used in a rating scale for an assessment type.

[APP–51482] A level should either be for a rating scale or a competence.

[APP–51483] Enter an integer value for step value.

[APP–51485] The name of the Establishment and the Location must be unique.

[APP–51486] An Establishment cannot be deleted if it is referenced by Establishment Attendances

[APP–51487] The name of the Establishment must be entered.

[APP–51488] The location must be entered.

[APP–51489] The attended end date must be later or equal to the attended start date.

[APP–51490] The establishment trying to be referenced does not exist.

[APP–51491] This business group does not exist.

[APP–51492] The primary key must be entered and must be unique

[APP–51493] The business group, person id, establishment, establishment id and attended start date

must be unique.

[APP–51494] The Person must be entered

[APP–51495] The establishment must be entered or an establishment must be referenced

[APP–51496] The attended end date must be later or equal to the attended start date.

[APP–51497] The attendance dates overlap with other attendance dates at the same establishment

[APP–51498] The assessment type must have a name. Enter a unique name.

[APP–51499] This assessment type name is already in use for this business group. Enter a new

name.

[APP–51500] You have entered an incorrect display assessment comment. Enter either ’Y’ or ’N’.

[APP–51502] The assessment classification is incorrect. Enter a valid value.

[APP–51503] The business group for the person is not the same as the business group for the

establishment attendance

[APP–51504] You have entered an incorrect weighting scale id for this business group. Enter a

correct one.

[APP–51505] If you enter a weighting scale comment, you must also enter a weighting scale. Either

enter a weighting scale or remove the comment.

[APP–51506] The assessment classification is not of a type that has a rating scale. Either change

the assessment classification or remove the rating scale

[APP–51507] The rating scale entered does not exist for this business group. Enter a correct one.

[APP–51508] A rating scale is required for this assessment classification. Either change the

assessment classification or add a rating scale.

[APP–51509] If you enter a rating scale comment you must also enter a rating scale. Either enter a

rating scale or delete the comment.

[APP–51510] If you enter a weighting scale id, you must also enter a weighting classification.

Either enter a weighting classification or remove the weighting scale id.

[APP–51511] The attendance type does not exists as a lookup

[APP–51512] If you enter a weighting_classification you must also have a weighting scale. Either

remove the weighting classification or enter a weighting scale

[APP–51513] You have entered an incorrect weighting classification. Enter a correct one.

[APP–51514] The weighting classification should be the same as the assessment classification.

Enter the correct value.

[APP–51515] You have entered an incorrect formula for the line score. Enter a correct one.

[APP–51516] You have entered an incorrect formula for the total score. Enter a correct one.

[APP–51529] Invalid phone type

Cause:

The value you have entered does not exist, is not date effective, or is disabled in the lookup table.

[APP–51530] Only one active home phone number is allowed.

Action:

Delete or end date existing home phone, or use secondary home phone type.

[APP–51531] Only one active work phone number is allowed.

Action:

Delete or end date existing work phone, or use secondary work phone type.

[APP–51532] Value for parent id was not found in parent table.

[APP–51535] The primary key for the qualification type must be entered and must be unique

[APP–51536] The name for a qualification type must be unique.

[APP–51537] This qualification type cannot be deleted as it is referenced by a qualification and

subject grouping

[APP–51571] Enter a name for the rating scale.

[APP–51572] You cannot delete a rating scale that is used in a competence.

[APP–51573] You cannot delete a rating scale that is used in an assessment type.

[APP–51574] You cannot delete a rating scale which has levels used in competence element.

[APP–51576] This type of assessment is being used so the rating scale cannot be changed.

[APP–51577] This type of assessment is being used so therefore the weighting scale cannot be

changed.

[APP–51578] This type of assessment is being used, therefore the assessment classification cannot

be changed.

[APP–51579] This assessment type is being used by at least one assessment so it cannot be

removed.

[APP–51580] The establishment attendance can not be deleted as the attendance is referenced by a

qualification record.

[APP–51581] The attendance start date must be entered

[APP–51582] You cannot change assessment type after you have entered information about the

assessment for this person. Delete the information, then change the assessment type.

[APP–51583] You have entered an incorrect assessment type. Enter a correct one.

[APP–51584] The assessment template that has been selected is not in use for the assessment date

that has been entered.

[APP–51584] The assessment template that has been selected is not in use for the assessment date

that has been entered.

[APP–51585] You have entered an incorrect value for the status flag.

[APP–51586] The assessee entered does not exist. Enter one that does

[APP–51587] You have entered an incorrect assessee for this assessment date. Enter a correct one.

[APP–51588] The assessor entered does not exist. Enter one that does

[APP–51589] You have entered an incorrect assessor for this assessment date. Enter a correct one

[APP–51590] You have entered an end date for the assessment but not a start date. Either remove

the end date or add a start date.

[APP–51591] The Assessment Period End Date has to be later than or equal too the Assessment

Period Start Date

[APP–51592] You have entered an incorrect assessment group. Enter a correct one.

[APP–51593] This assessment type, assessor, assessee and assessment group already exist for this

assessment date. Either abandon the information, or change it.

[APP–51594] This assessment group name is already in use for this business group. Enter a new

name.

[APP–51595] The assessment group must have a name. Enter a unique name.

[APP–51596] The attendance dates are outside of a qualification start date that references the

establishment attendance.

[APP–51597] There are assessments which reference this assessment group. Remove these

references first before removing the assessment group.

[APP–51598] Enter the start date for this competence.

[APP–51599] Competence end date has to be later than start date.

[APP–51600] You cannot delete this person. Special Information exist.

[APP–51603] Invalid Analysis criteria id

[APP–51603] The analysis criteria id that you entered does not exist.

[APP–51610] This question name already exists.

[APP–51611] This question is referenced in PER_PROPOSAL_QUESTION_MEMBERS table. No

delete action can proceed.

[APP–51612] The business_group_id is invalid.

[APP–51615] The proficiency_level_id is invalid.

[APP–51616] The high_proficiency_level_id is invalid.

[APP–51620] The job_id is invalid.

[APP–51621] The person_id is invalid.

[APP–51622] The position_id is is invalid.

[APP–51623] The organization_id is invalid.

[APP–51628] The assessment_id is invalid.

[APP–51631] The rating_level_id is invalid.

[APP–51632] The weighting_level_id is invalid.

[APP–51633] The parent_competence_element_id is invalid.

[APP–51634] The competence_element_id is invalid.

[APP–51635] Please enter ’Y’ or ’N’ for the Mandatory field.

[APP–51636] The certification_method you entered is invalid.

[APP–51637] You cannot enter a certification_method without a certification_date and vice versa.

[APP–51638] The competence dates are outside the competence type dates.

[APP–51639] The source_of_proficiency_level you entered is invalid.

[APP–51641] The competence_element_type you entered is invalid.

[APP–51642] It is not possible to verify the rating levels for the competence element because the

competence has not been entered.

[APP–51644] The step_value of the high_proficiency_level must be greater than or equal to the

step_value of the proficiency_level.

[APP–51645] One of the assessment_id or assessment_type_id must be entered.

[APP–51646] The use of a rating or weighting level on this assessment is invalid, the corresponding

assessment type does not allow it.

[APP–51647] The effective_date_from must be before the effective_date_to.

[APP–51648] The dates of the competence_element you entered overlaps with an existing

competence record.

[APP–51649] The dates of the competence_element for this job which you have entered overlaps

with an existing competence record.

[APP–51650] The dates of the competence_element for this position which you have entered

overlaps with an existing competence record.

[APP–51651] The dates of the competence_element for this organization which you have entered

overlaps with an existing competence record.

[APP–51653] You cannot enter a normal_elapse_duration without a normal_elapse_duration_unit

and vice versa.

[APP–51654] The normal_elapse_duration_unit you entered is invalid.

[APP–51655] One of the organization_id, position_id, job_id, enterprise_id must be entered.

[APP–51656] Only one of the organization_id, position_id, job_id, or enterprise_id must be entered.

[APP–51657] One or more parameters were incorrectly entered for the Requirement competence

element.

[APP–51658] One or more parameters were incorrectly entered for the Assessment competence

element.

[APP–51659] One or more parameters were incorrectly entered for the Assessment_Group

competence element.

[APP–51660] The parent_competence_element must be of type Assessment_Group, if the type of

the competence_element is Assessment_Competence.

[APP–51662] Only one of the assessment_type_id or parent_competence_element_id must be

entered for a competence_element of type Assessment_Competence.

[APP–51663] One or more parameters were incorrectly entered for the Assessment_Competence

competence element.

[APP–51664] One or more parameters were incorrectly entered for the Competence_Usage

competence element.

[APP–51665] Only one of the qualification_id or activity_version_id must be entered for a

competence_element of type Delivery.

[APP–51666] One or more parameters were incorrectly entered for the Delivery competence

element.

[APP–51667] Only one of the qualification_id or activity_version_id must be entered for a

competence_element of type Prerequisite.

[APP–51668] One or more parameters were incorrectly entered for the Prerequisite competence

element.

[APP–51669] One or more parameters were incorrectly entered for the Path competence_element.

[APP–51670] One or more parameters were incorrectly entered for the Personal

competence_element. You must enter a competence and an effective_date_from for a Personal

competence_element record.

[APP–51672] One or more parameters were incorrectly entered for the Proposal

competence_element.

[APP–51673] One or more parameters were incorrectly entered for the Set competence_element.

[APP–51674] The foreign key combination for a competence_element must be unique.

[APP–51675] You cannot delete a personal competence element.

[APP–51677] You cannot delete a competence_element if it is used by other competence_element

records.

[APP–51678] You cannot delete a competence_element of type Competence_Usage, if its assciated

competence is used by other competence_element records.

[APP–51679] You cannot de–select this competence since it is being used by an Assessment based

on the current template

[APP–51681] The values entered are not valid half Kana characters.

[APP–51681] This field only accepts one byte character

[APP–51682] Invalid value is entered for PER_INFORMATION1

[APP–51683] Invalid value is entered for PER_INFORMATION2

[APP–51684] Invalid value is entered for PER_INFORMATION3

[APP–51685] Invalid value is entered for PER_INFORMATION4

[APP–51686] Invalid value is entered for PER_INFORMATION5

[APP–51687] Invalid value is entered for PER_INFORMATION6

[APP–51688] Invalid value is entered for PER_INFORMATION7

[APP–51689] Invalid value is entered for PER_INFORMATION8

[APP–51690] Invalid value is entered for PER_INFORMATION9

[APP–51692] This field can only contain single byte characters

[APP–51693] District Code does not exist

[APP–51694] Address Line1 does not exit

[APP–51695] Both District Code and Address Line1 are null

[APP–51696] Address Line1 Kana does not exist

[APP–51697] Region 2 is not null when Address Line 2 is null

[APP–51698] Region 3 is not null when Address Line 3 is null

[APP–51699] Invalid postal code is entered

[APP–51701] The activity_version is invalid.

[APP–51705] at least one of segment10–30 is not null

[APP–51713] Invalid date format for graduation date

[APP–51714] Invalid highest educational level

[APP–51716] The element_entry_id is invalid.

[APP–51717] This salary proposal must have the same start date as the new salary basis for the

employee.

[APP–51718] The salary basis for this employee has changes that take effect at a date in the future.

You must delete future changes of salary basis before you can enter this salary proposal.

[APP–51722] The new salary basis uses a different element input value to hold the salary for this

employee. If you continue, the system will automatically end the existing salary entry.

[APP–51724] Assignment &ASSIGNID skipped because of previous incomplete actions.

[APP–51725] Assignment &ASSIGNID skipped because it is used in future actions.

[APP–51726] You cannot enter the high_proficiency_level without entering the proficiency_level.

[APP–51727] The rating_level_id or weighting_level_id is invalid.

[APP–51731] The effective date is outside payroll time periods.

[APP–51734] <P>A system error has occurred. You will be notified when your System

Administrator has corrected the problem.</P><P>Click on the button below to return to

the Employee Direct Access Menu.</P>

[APP–51734] <P>A system error has occurred. You will be notified when your System

Administrator has corrected the problem.</P><P>Click the button below to return to the

Employee Direct Access Menu.</P>

[APP–51735] <P>You are at the wrong step for changing your details.<P>Do one of the

following:

[APP–51736] <P>You have already completed all steps for this task.</P><P>Click

on the button below to return to the Employee Direct Access Menu.</P>

[APP–51737] Click on the button below to continue at the correct step.

[APP–51738] Click on the button below to return to the Employee Direct Access Menu.

[APP–51739] Non single byte character is entered

[APP–51740] Invalid value for segment30 is entered

[APP–51741] This flex structure does not exist

[APP–51748] The assessment_type_id is invalid.

[APP–51749] The Error type you have specified is incorrect

[APP–51749] The error type you have specified is incorrect

[APP–51750] The transaction you have selected has already been started. Please choose another.

[APP–51751] The parameter specified does not exist

[APP–51752] The transaction specified does not exist

[APP–51753] You are not the creator of this transaction which is restricted. Therefore you can not

create this transaction step.

[APP–51754] No Function has been specified for the toolbar frame.

[APP–51754] No function has been specified for the toolbar frame.

[APP–51755] No Function has been specified for the workspace frame.

[APP–51755] No function has been specified for the workspace frame.

[APP–51756] The HR_ACTION_CODE lookup code supplied must be one of the following:

SHOW_DETAILS, HIDE_DETAILS, REST,NEXT, PREVIOUS, COMMIT, ROLLBACK.

[APP–51756] The HR_ACTION_CODE lookup code supplied should only be one of the

following(SHOW_DETAILS, HIDE_DETAILS, REST,NEXT, PREVIOUS, COMMIT,

ROLLBACK).

[APP–51758] No codes in lookup HR_ACTION_BUTTONS.

[APP–51758] There are no codes in lookup HR_ACTION_BUTTONS.

[APP–51759] One or more of the action buttons is defined with a state not in the set

{ON,OFF,WORKFLOW}.

[APP–51759] The state of one or more of the action buttons is not a member of the set

{ON,OFF,WORKFLOW}.

[APP–51761] No details are found for the given activity identifier.

[APP–51762] The header level is out of the range of that specified in HTML

[APP–51762] The header level is out of the range specified in HTML.

[APP–51763] There is no root activity for the given item.

[APP–51764] There is no activity in a NOTIFIED: state for the given item.

[APP–51765] There is no function name for the activity.

[APP–51766] There was no name for the previous activity.

[APP–51767] Effective date must exceed target organization’s start date.

[APP–51768] An icon is defined with a state not in the set {ON,OFF}.

[APP–51770] You cannot make this change because a future placement for a different grade to the

current entry already exists.

[APP–51771] City is not in the state.

[APP–51773] This question is referenced in PER_ASSIGN_PROPOSAL_ANSWERS table. You

canot delete this question.

[APP–51774] Display Order is invalid

[APP–51776] A Web user can not have more than one ICX_HR_PERSON_ID attribute.

[APP–51776] Web User can not have more than one ICX_HR_PERSON_ID attribute.

[APP–51779] Assignment id is valid but Assignment type is not ’ACCEPTED’.

[APP–51780] This combination of categories already exist. Please clear the form and query with a

session date after &1

[APP–51781] PRORATION RULE CANNOT BE N/A FOR A SUPPORT CATEGORY.

[APP–51782] The annualized hours cannot be less than zero or more than 8766 hours.

[APP–51783] You must enter a value for the annualized hours field.

[APP–51784] The assessment needs to have a date. Enter a date for the assessment.

[APP–51785] Invalid district_code aginst per_jp_address_lookups is entered.

[APP–51786] Invalid address_line1 against per_jp_address_lookups is entered.

[APP–51787] Query on per_jp_address_lookups returned more than one row.

[APP–51788] Query on per_jp_address_lookups returned more than one row.

[APP–51789] Both district_code and address_line1 can not be null.

[APP–51790] Invalid address_line1_kana aginst per_jp_address_lookups is entered.

[APP–51796] Invalid school_id against per_jp_school_lookups is entered.

[APP–51797] Invalid school_name against per_jp_school_lookups is entered.

[APP–51798] Invalid school_name_kana against per_jp_school_lookups is entered.

[APP–51799] Invalid major against per_jp_school_lookups is entered.

[APP–51800] Invalid major_kana against per_jp_school_lookups is entered.

[APP–51801] The date of birth was in an incorrect format. It has been set to empty. Please enter a

date in a correct format.

[APP–51801] The format of the date of birth was incorrect. The incorrect date has been erased.

Please enter a date in a correct format.

[APP–51802] Either you did not check a primary contact or you have checked more than one

primary contact. You must have one primary contact.

[APP–51802] You either do not check a primary contact or you have more than one primary

contacts checked.

[APP–51806] The assessee is does not belong to the current business group. Enter onne that does

[APP–51807] The Effective date you entered is too early. The Effective date has been reset to the

earliest date allowed.

[APP–51807] The effective date you entered is too early. It has been reset to the earliest date

allowed.

[APP–51808] The assessor does not exist in the current business group. Enter one that does.

[APP–51809] This competence is used in a competence element. The dates you have entered are

outside the competence element dates.

[APP–51810] Completed payroll actions exist.

[APP–51811] Contiguous periods of service exist.

[APP–51812] This assessment is being referenced by competence elements. Remove the

competence elements before removing the assessment.

[APP–51813] The qualification record being referenced does not exist.

[APP–51814] The Primary Key for the Subject Taken record is incorrect. It should be null on insert

and non updatable on update.

[APP–51815] This subject already exists for this qualification with the same subject status.

[APP–51816] The subject start date must be before the subject end date.

[APP–51817] The start and end dates for the subject are outside of the dates for the qualification.

[APP–51818] The lookup value for subject major is invalid.

[APP–51819] The subject status does not exist as a lookup.

[APP–51820] This subject does not exist as a lookup.

[APP–51821] The start date or the end date for this subject overlaps with the identical subject for

the same qualification.

[APP–51830] The appraisal this assessment should belong to doesn’t exist. Attach it to another

appraisal.

[APP–51833] The person or the establishment attendance must be entered but not both.

[APP–51834] This person does not exist as of the system date.

[APP–51835] The value of the qualification status is invalid.

[APP–51836] The qualification awarded date is invalid. The awarded date must be greater than or

equal to the start date and greater than or equal to the end date.

[APP–51838] Job codes have already been assigned for this state.

[APP–51840] A fee has been entered without the currency having been entered or the fee currency

has been entered without the fee having been entered.

[APP–51841] The start and end dates for the qualification are outside of the start and end dates of

the establishment attendance.

[APP–51842] The qualification start and end dates do not bound the subjects taken records, either

change the dates of the related subjects taken or change the start and end dates of the qualification.

[APP–51844] The projected completion date is earlier than the start date of the qualification. The

projected completion date can not be entered unless the start date has been entered.

[APP–51845] The tuition method value is invalid and doesn’t exist in the lookup

PER_TUITION_METHODS

[APP–51847] This qualification record already exists within the date range specified. A

qualification record must be unique and not bounded by an identical qualification’s start and end

dates.

[APP–51848] The business group for the establishment attendance being referenced is different to

the business group for the qualification.

[APP–51849] The business group for the person referenced is different to the business group for the

qualification.

[APP–51850] The establishment attendance being referenced is invalid and does not exist in the

PER_ESTABLISHMENT_ATTENDANCES table.

[APP–51851] The qualification type being referenced is invalid and does not exist in the

PER_QUALIFICATION_TYPES table.

[APP–51852] The business group being referenced is invalid and does not exist in the

HR_ORGANIZATION_UNITS table.

[APP–51853] The start date for the qualification is after the end date for the qualification.

[APP–51854] The primary key for the qualification is invalid. It should be null on insert and should

be non–updatable on update.

[APP–51855] This currency code is invalid as it does not exist in the fnd_currencies table.

[APP–51856] FTE availability must be a number between 0.00 and 100.00, with two decimal

places.

[APP–51857] This record can not be deleted as it is referenced by some subjects taken.

[APP–51859] The template end date is before the start date.

[APP–51860] At least one assessment of this type has an assessment date later than the date that this

type is valid until. Change the date that the type is valid until.

[APP–51861] At least one assessment of this type has an assessment date earlier than the date that

this type is valid from. Change the date that this type is valid from.

[APP–51862] Either you did not check a main address or you have checked more than one main

address. You must have one main address.

[APP–51862] You either do not check a primary address or you have more than one primary

addresses checked.

[APP–51863] The start date for the Establishment Attendance is not in a valid date format.

[APP–51864] You must enter selection criteria before entering a record here.

[APP–51865] Please select a position before pressing the Find button.

[APP–51866] The competence element type must be ’PERSONAL’ when updating a persons

competence profile.

[APP–51867] The person already has this competence at some time during the period you have

specified.

[APP–51868] The Qualification Projected Completion Date is in an invalid date format.

[APP–51869] The License Expiry Date is in an invalid date format.

[APP–51870] Position status is invalid.

[APP–51871] The training completed amount is not in a valid numeric format.

[APP–51872] The total training amount value is not in a valid numeric format.

[APP–51873] The start date for the subject is invalid.

[APP–51874] The end date for the subject is invalid.

[APP–51875] Commit your Establishment Attendance before moving.

[APP–51876] For each copy transaction you can only select one of the core competencies,

organization,job or position.

[APP–51877] Please select one of the core competencies, organization, job or position before

pressing the copy button.

[APP–51878] The date from field must be entered for copying process.

[APP–51879] Save the assessment template before adding competences.

[APP–51880] The value of the category is invalid, this value does not exist as a lookup.

[APP–51881] The person must have a current primary address for them to be entered on a payroll.

[APP–51882] The person’s address must have a county for them to be entered on a payroll.

[APP–51883] The appraisal template is invalid for your business group.

[APP–51884] The appraisal template does not exist as of the effective date.

[APP–51887] You must enter an appraisee for the appraisal.

[APP–51888] You must enter an appraiser for the appraisal.

[APP–51889] This person does not exist.

[APP–51890] This person does not exist in the appraisal’s business group.

[APP–51891] This person does not exist as of your effective date.

[APP–51892] The appraisal type you have entered is invalid. Enter a valid one.

[APP–51893] The appraisal status you have entered is invalid. Enter a valid one.

[APP–51894] You must enter the start date for this appraisal.

[APP–51895] You must enter the end date for this appraisal.

[APP–51896] The appraisal period start date must be earlier than or equal to the appraisal period

end date.

[APP–51896] The appraisal start date must be earlier than or equal to appraisal end date.

[APP–51897] The appraisal end date must be later than or equal to appraisal start date.

[APP–51898] The overall rating level you entered does not exist.

[APP–51899] The overall rating level does not exist in the appraisal’s business group.

[APP–51900] The overall rating level must be for the rating scale defined for the appraisal template.

[APP–51902] You cannot delete an appraisal that has an overall rating set.

[APP–51903] You cannot delete an appraisal that is used in proposal answers.

[APP–51903] You cannot delete an appraisal where questionnaire answers exist

[APP–51904] You cannot delete an appraisal that is used in objectives.

[APP–51905] You cannot delete an appraisal that is used in an assessment.

[APP–51906] You cannot delete an appraisal that is used in a performance rating.

[APP–51907] You must enter a name for the appraisal template.

[APP–51908] A template with this name already exists. Enter a new name.

[APP–51909] The date from has to be earlier than or equal to date to.

[APP–51910] The date to has to be later than or equal to date from.

[APP–51911] This template is used in an appraisal. The dates you have entered are outside the

appraisal dates.

[APP–51912] The assessment type you have entered does not exist.

[APP–51913] The assessment type is invalid for your business group.

[APP–51914] The assessment type is outside the start date and end date of the appraisal template.

[APP–51915] The questionnaire template you have entered does not exist.

[APP–51916] The questionnaire template must be of type ’APPRAISAL’.

[APP–51917] You cannot update the questionnaire template as this template is used in proposal

answers.

[APP–51918] You must enter an appraisal for the performance rating.

[APP–51919] The appraisal you have entered for this performance rating does not exist.

[APP–51920] You must enter an objective for the performance rating.

[APP–51921] The objective you have entered for this performance rating does not exist.

[APP–51922] The objective must be in the performance rating’s business group.

[APP–51924] The objective you have entered already exists for this appraisal. Enter a new

objective.

[APP–51925] The rating level you have entered for this performance rating does not exist.

[APP–51926] The rating level must be in the performance rating’s business group.

[APP–51927] The rating level must be for the rating scale defined in the appraisal template.

[APP–51928] The rating scale you have entered does not exist.

[APP–51929] The rating scale should be in the appraisal template’s business group.

[APP–51930] You can only assign rating scale’s of type PERFORMANCE to appraisal templates.

[APP–51931] You cannot update this rating scale as this appraisal template is used in an appraisal

which has the overall rating set.

[APP–51932] You cannot update this rating scale as this appraisal template is used in a performance

rating.

[APP–51933] You cannot delete this appraisal template as it is used in an appraisal.

[APP–51936] The Establishment Attendance is invalid, please select a valid Establishment

Attendance from the LOV.

[APP–51937] Save your location or display another before continuing

[APP–51938] The system cannot find the program unit being called. This could be because the

application API pre–processor has not been run. Contact your system administrator quoting the

following details: Error ORA–06508 in API module &MODULE_NAME at hook &HOOK_TYPE.

[APP–51939] An internal commit or full rollback has occurred inside this API user hook. These

commands are not permitted as they interfere with other logic. Contact your system administrator to

resolve this action and to remove the commit or rollback statement. Quote: API module

&MODULE_NAME at hook &HOOK_TYPE.

[APP–51940] ORA–06502: PL/SQL: numeric or value error. Check whether you are attempting to

create API hook package source code greater than 32K in size. If so, reduce the number of

procedures which need to be called for this API module. The module will not execute until this

problem is resolved.

[APP–51941] A call package procedure cannot have any PL/SQL overloaded versions. Code to

carry out this hook call has not been created.

[APP–51942] A package function cannot be called. Only package procedures can be called. Code to

carry out this hook call has not been created.

[APP–51943] The &PARAMETER parameter to the call procedure must have the same datatype as

the value available at the hook. Code to carry out this hook call has not been created.

[APP–51944] At least one OUT or IN/OUT parameter has been specified on the call procedure. You

can only use IN parameters. Code to carry out this hook call has not been created.

[APP–51945] There is a parameter to the call procedure which is not available at this hook. Check

your call procedure parameters. Code to carry out this hook call has not been created.

[APP–51946] A legislation package function cannot have any PL/SQL overloaded versions. This

API module will not execute until this problem has been resolved.

[APP–51947] The &PARAMETER parameter to the legislation function must have the same

datatype as the value available at the hook. This API module will not execute until this problem has

been resolved.

[APP–51948] All the parameters to the legislation function must be IN parameters. OUT or IN/OUT

parameters are not allowed. This API module will not execute until this problem has been resolved.

[APP–51949] There is a parameter to the legislation function which is not available at this hook.

This API module will not execute until this problem has been resolved.

[APP–51950] The call_package does not exist in the database. Code to carry out this hook call has

not been created.

[APP–51951] The call_procedure does not exist in the call_package. Code to carry out this hook

call has not been created.

[APP–51952] Remote objects cannot be called from API User Hooks. Code to carry out this hook

call has not been created.

[APP–51953] The call_package code in the database is invalid. Code to carry out this hook call has

not been created.

[APP–51954] An error has occurred while attempting to parse the name of the call package and call

procedure. Check the package and procedure names. Code to carry out this hook call has not been

created.

[APP–51955] The legislation_package does not exist in the database. This API module will not

execute until this problem has been resolved.

[APP–51956] The legislation_function does not exist in the legislation_package. This API module

will not execute until this problem has been resolved.

[APP–51957] Remote objects cannot be called to find out the legislation code. This API module

will not execute until this problem has been resolved.

[APP–51958] The legislation_package code in the database is invalid. This API module will not

execute until this problem has been resolved.

[APP–51959] An error has occurred while attempting to parse the name of the legislation package

and legislation function. Check the package and function names. This API module will not execute

until this problem has been resolved.

[APP–51960] The hook package header source code cannot be found in the database. Either the

package header has not been loaded into the database or the hook package name specified in the

HR_API_HOOKS table is incorrect. This API module will not execute until this problem has been

resolved.

[APP–51961] The hook procedure does not exist in the hook package. This API module will not

execute until this problem has been resolved.

[APP–51962] Remote objects cannot used for API hook package procedures. This API module will

not execute until this problem has been resolved.

[APP–51963] The hook package code in the database is invalid. This API module will not execute

until this problem has been resolved.

[APP–51964] An error has occurred while attempting to parse the name of the hook package and

hook procedure. Check the package and procedure names. This API module will not execute until

this problem has been resolved.

[APP–51965] The legislation function can only be a function. It cannot be a procedure. This API

module will not execute until this problem has been resolved.

[APP–51966] The legislation function must return a varchar2 value. This API module will not

execute until this problem has been resolved.

[APP–51967] The legislation specific code cannot be called from this hook. The legislation package

function has not been specified in the HR_API_HOOKS table, and the business_group_id value is

not available at this hook. This API module will not execute until this problem has been resolved.

[APP–51968] In a hook package procedure all the parameter datatypes must be VARCHAR2,

NUMBER, DATE, BOOLEAN or LONG. This API module will not execute until this problem has

been resolved.

[APP–51969] In a hook package procedure all the parameters must be IN parameters. OUT or

IN/OUT parameters are not allowed. This API module will not execute until this problem has been

resolved.

[APP–51970] You cannot define default values for parameters to a hook package procedure. Ensure

no defaults are defined. This API module will not execute until this problem has been resolved.

[APP–51971] A hook package procedure cannot have any PL/SQL overloaded versions. This API

module will not execute until this problem has been resolved.

[APP–51972] The hook package procedure can only be a procedure. It cannot be a function. This

API module will not execute until this problem has been resolved.

[APP–51973] You can book an Employee on an event only once

Cause:

For an event, you are trying to book an Employee more than once.

Action:

As this Employee is already booked for this event, either delete the information you have already

entered or change the Employee

[APP–51974] You can book an Applicant on an event only once

Cause:

For an event, you are trying to book an Applicant more than once.

Action:

As this Applicant is already booked for this event, either delete the information you have already

entered or change the Applicant

[APP–51975] Maximum value must be greater than or equal to minimum value.

[APP–51976] Minimum value must be less than or equal to maximum value.

[APP–51977] Mid value must be less than or equal to maximum.

[APP–51978] Assignment’s payroll has changed. You can only advance assignments which do not

change payroll between the start date of the payment period and the end date of the one period after

the last advanced period. Correct advance dates or review changes to assignment.

[APP–51979] The paragraph with this number has more than 2000 characters. Please shorten the

text or divide the text into two paragraphs.

[APP–51980] Requery for the correct details to be displayed.

[APP–51981] Payment date is too early. You have entered an advance payment date that is earlier

than 2 pay periods before the start of the advance period. Correct dates entered.

[APP–51982] Too many periods advanced. Correct advance dates.

[APP–51984] Save your qualification first before entering subject details.

[APP–51985] Parameters Available at each API User Hook

[APP–51986] API User Hook Pre–Processor All Module Error Report

[APP–51987] API User Hook Pre–Processor One Module Error Report

[APP–51988] Created on

[APP–51989] Module Name

[APP–51990] Module Type

[APP–51991] Hook

[APP–51992] Hook Package

[APP–51993] You entered an invalid date format. This has been replaced with the system date.

[APP–51995] The person has not been entered. A person must be entered prior to insertion.

[APP–51996] The person can not be updated. Once a succession planning record has been saved for

a person he/she can not be updated.

[APP–51997] This person does not exist as of the system date.

[APP–51998] The position has not been entered. A position must be entered in order to insert a

succession planning record.

[APP–51999] The position can not be updated. Once a succession planning position has been

entered it can not be updated.

[APP–52000] This position does not exist as of the system date.

[APP–52001] The timescale value does not exist as a lookup.

[APP–52002] The start date must be entered. A succession plan must have a start date.

[APP–52003] The start date is greater than the end date. The start date must be less than or equal to

the end date for a succession plan record.

[APP–52004] The available for promotion field does not exist as a lookup value.

[APP–52005] The succession plan record overlaps with another succession plan record for the same

person and the same position.

[APP–52006] The succession plan records primary key is invalid. The primary key should be null

on insert and non–updateable on update.

[APP–52007] A person has not been chosen from the current person list.

[APP–52008] A person has not been selected from the LOV.

[APP–52009] The person can not be derived from the persons name. Please reselect person from

LOV.

[APP–52010] The position cannot be derived from the value selected from the list. Please select a

position from the list.

[APP–52011] The start date is not in a valid date format.

[APP–52012] The end date is not in a valid date format.

[APP–52013] Mix rollback complete. &ASGN_COUNT assignments processed.

[APP–52014] The element entry created by this batch line has run results.

[APP–52015] The batch you have selected no longer exists.

[APP–52016] You cannot delete this Advance Pay record because it has already been processed. To

delete the record you must first roll back the process.

[APP–52017] This job does not exist.

[APP–52018] This business group does not exist.

[APP–52019] This job already exists within the business group.

[APP–52020] The record could not be reserved as another user is making a change based on this

record. The selected DateTrack option cannot be used and has been changed to Correction. If this

option is unacceptable clear this record and try again later.

[APP–52021] Start date must be entered.

[APP–52022] The person can not be updated.

[APP–52023] The position can not be updated.

[APP–52024] The position does not exist as of the system date.

[APP–52025] The job can not be updated.

[APP–52026] The job can not be updated.

[APP–52027] The country name is not valid.

[APP–52028] The value for the work duration is invalid and does not exist in the lookup

PER_TIME_SCALES.

[APP–52029] the value for the work schedule is invalid. The value must exist in the lookup

PER_WORK_SCHEDULE.

[APP–52030] The value for work hours is invalid. The value must exist in the lookup

PER_WORK_HOURS.

[APP–52031] The value for the FTE capacity is invalid. The value must exist in the lookup

PER_FTE_CAPACITY.

[APP–52032] The value for the relocation preference is invalid. The value must exist in the lookup

PER_RELOCATION_PREFERENCES.

[APP–52033] The length of service value is invalid. The value should exist in the lookup

PER_LENGTHS_OF_SERVICE.

[APP–52034] The value for the location is invalid. The location must exist in the HR_LOCATIONS

table.

[APP–52035] The position, job or person has not been set. A deployment factor must be related to a

person, job or position.

[APP–52036] Attributes have been set that are not consistent with Person related deployment

factors. The following attributes should be null when dealing with Person related deployment

factors : RELOCATION_REQUIRED, PASSPORT_REQUIRED, LOCATION1, LOCATION2,

LOCATION3, OTHER_REQUIREMENTS, SERVICE_MINIMUM.

[APP–52037] Attributes have been set that are not consistent with Job/Position related deployment

factors. The following attributes should be null when dealing with Job/Position related deployment

factors : VISIT_INTERNATIONALLY, ONLY_CURRENT_LOCATION, NO_COUNTRY1,

NO_COUNTRY2, NO_COUNTRY3, COMMENTS, EARLIEST_AVAILABLE_DATE,

AVAILABLE_FOR_TRANSFER, RELOCATION_PREFERENCE.

[APP–52038] <<Datatype not recognised>>

[APP–52039] The business group for the job is different to the business group for the deployment

factor.

[APP–52040] The business group for the position is different to the business group for the

deployment factor.

[APP–52041] The Primary key for deployment factors is incorrect. It should be null on insert and

non–updateable on update.

[APP–52042] The business group for the person is not the same as the business group for the

deployment factor.

[APP–52043] The deployment factor clashed with another deployment factor for the same job,

position and person.

[APP–52044] The value for available for transfer attribute is invalid. The value should fall within

the YES_NO lookup.

[APP–52045] The value for the current location is invalid. The value should exist in the lookup

YES_NO.

[APP–52046] The value for passport required is invalid. The value should exist in the YES_NO

lookup.

[APP–52047] The valus for relocate domestically is invalid. The value should exist in the YES_NO

lookup.

[APP–52048] The value for relocate interantionally is invalid. The value should exist in the lookup

YES_NO.

[APP–52049] The value for relocation required is invalid. The value should exist in the YES_NO

lookup.

[APP–52050] the value for travel required is invalid. The value should be in the YES_NO lookup.

[APP–52051] the value for visit interantionally is invalid. The value should exist in the lookup

YES_NO.

[APP–52052] The value for work any country is invalid. the value should exist in the lookup

YES_NO.

[APP–52053] The value for work any location is invalid. the value should exist in the lookup

YES_NO.

[APP–52054] This appraisal does not exist.

[APP–52055] This appraisal is not in the same business group as the objective.

[APP–52056] You must enter the owning person.

[APP–52057] This person does not exist.

[APP–52058] This person does not exist in your business group.

[APP–52059] This person does not exist as of your effective date.

[APP–52060] The owning person should be the appraisee as defined in the appraisal.

[APP–52061] You cannot delete this objective as it is used in performance ratings.

[APP–52062] You must enter a name for the objective.

[APP–52063] You must enter a start date for the objective.

[APP–52064] You must enter a table name.

[APP–52065] This table does not exist.

[APP–52066] You must enter a column name.

[APP–52067] This column does not exist for the table specified.

[APP–52068] You must enter a value for the participant column.

[APP–52069] There is no such record for the value entered for ’participation in’ field.

[APP–52070] The value entered for the ’participation in’ field does not exist in your business group.

[APP–52071] This person does not exist.

[APP–52072] This person does not exist in your business group.

[APP–52073] This person does not exist as of your effective date.

[APP–52074] The same person cannot be the appraisor and the appraisee.

[APP–52075] You must enter a person.

[APP–52076] You must provide a last name.

[APP–52077] The employee’s eligibility for Advance Pay is not valid over the period you have

selected. Check element link and payroll transfer details, then specify Advance Pay criteria again

for the assignment.

[APP–52078] Legislative features for Advance Pay may not have been correctly installed. Check

predefined balances, element types and input values.

[APP–52079] The system cannot match the number of pay period deferments to the total number of

Advance Pay periods. Check element link and payroll transfer details, then specify Advance Pay

criteria again for the assignment.

[APP–52080] The Create Batches process has failed to insert a set of batch lines into the temporary

batch table. See your System Administrator about this.

[APP–52081] The Create Batches process failed when inserting a new batch header record into the

temporary batch tables. See your System Administrator about this.

[APP–52082] Assignment Set is a required parameter. To include the whole payroll, define the

assignment set to be equal to or larger than the payroll.

[APP–52083] You must enter a valid background check status.

[APP–52084] The MIX transfer has failed for this process. To see what action to take, view the

messages for the failed batch in the Batch Lines window.

[APP–52085] The payroll you have entered for the assignment set does not match the payroll you

have entered for the Advance Pay process.

[APP–52086] The Business Group you have entered for the assignment set does not match the

Business Group you have entered for the Advance Pay process.

[APP–52087] The batch header name you have entered is not unique. Please update with a unique

name.

[APP–52088] Commit your deployment factor record to the database or save your changes before

moving.

[APP–52089] Could not open file &FILENAME for reading.

[APP–52090] The business group and person id combination is invalid.

[APP–52091] The analysis criteria id that you have entered not exist in the system.

[APP–52092] The Person ID that you have entered does not exist.

[APP–52093] The id flex num and analysis criteria id combination is invalid.

[APP–52094] The date_from and date_to combination is invalid.

[APP–52095] Date_from is not null if date_to has value.

[APP–52096] Person type must be either APL or APL_EX_APL.

[APP–52097] The applicant that you have entered does not exist in the system.

[APP–52098] The assignment specified by person id is invalid.

[APP–52099] The assignment specified by assignment id does not exist.

[APP–52100] The assignment type specified by assignment id is not ’ACCEPTED’.

[APP–52101] The combination of person id and assignment id is invalid.

[APP–52102] Do you want your batch lines to be created?

[APP–52103] Pay period does not exist. The dates that you have entered do not correspond to the

existing pay period. Define time periods for the assignment’s payroll starting from at least one

period before the advance period and ending at least one period after the advance period.

[APP–52104] Incorrect date entered. You have either entered a start of advance period date later

than the end of advance period or a payment date later than the start of advance period date. Correct

advance dates.

[APP–52105] Assignment does not exist or it has no payroll. Assignment must be valid and have a

payroll at least between the start date of the payment period and the end date of the one period after

the last advanced period. Correct advance dates or review assignment information.

[APP–52106] Save this record or display another before continuing.

[APP–52107] You have not entered sufficient criteria, please enter some criteria.

[APP–52108] The assignment must not already have a status type of TERM_ASSIGN on or after the

actual termination date.

[APP–52109] No competencies exist for the enterprise, organization, job, position or vacancy you

selected.

[APP–52111] You must enter a valid Blood Type.

[APP–52112] You must enter a valid Student Status.

[APP–52113] You must enter a valid Work Schedule.

[APP–52114] You must enter a valid Rehire Recommendation.

[APP–52115] You must enter a valid On Military Service Status.

[APP–52116] You must enter a valid Resume Exists Status.

[APP–52117] You must enter a valid Second Passport Exists Status.

[APP–52118] The Module Name parameter was not entered in upper case.

[APP–52119] The combination of Module Type and Module Name is not unique in the table.

[APP–52120] Module Package must be entered in upper case.

[APP–52121] The Module Type has been set to an invalid value.

[APP–52122] The Data Within Business Group parameter has been given an invalid value.

[APP–52123] The Legislation Code has been given an invalid value.

[APP–52124] Module Package must be set when Module Type is BP.

[APP–52125] Module Package must be NULL when Module Type is RH.

[APP–52126] This Organization/Job/Position/Competence does not exists. Use List of Values to

select valid names.

[APP–52127] The API Hook Type parameter has been given an invalid value.

[APP–52128] There already exists an API Hook of that type defined for the API Module.

[APP–52129] The API Hook cannot be associated with the parent API Module because there is a

mismatch between their types.

[APP–52130] The combination of Hook Package and Hook Procedure must be unique within the

table.

[APP–52131] Legislation Package must be NULL when the parent Module has a Data Within

Business Group value of N.

[APP–52132] Legislation Function must be NULL when the parent Module has a Data Within

Business Group value of N.

[APP–52133] Legislation Package and Legislation Function must be both not null or both null.

[APP–52134] The API Hook ID must reference a hook on the HR_API_HOOKS table.

[APP–52135] The API Hook Call Type parameter has been given an invalid value.

[APP–52136] The Enabled Flag value must be YES or NO.

[APP–52137] The Call Package value is invalid for that particular Hook Call Type.

[APP–52138] The Call Procedure value is invalid for that particular Hook Call Type.

[APP–52139] Check that the values for CALL_PACKAGE, CALL_PROCEDURE,

LEGISLATION_CODE and API_HOOK_ID form a unique combination in the HR_HOOK_CALLS

table.

[APP–52140] The Status value is invalid.

[APP–52141] Status must be set to N on insert.

[APP–52142] The Encoded Error value must be NULL during insert.

[APP–52143] Encoded Error should be null if Status is set to ’V’ or ’N’.

[APP–52144] Preprocessor Date should be null during insert.

[APP–52145] Sequence must be greater than or equal to 1000 and less than or equal to 1999 when

Legislation Code is not null.

[APP–52146] Sequence number must be less than 1000 or greater than 1999 when Legislation Code

is null.

[APP–52147] Warning: Advance Pay has detected no amount to advance from this pay period

[APP–52148] Warning : Advance Pay has processed the relevant advance periods for this payment.

There is a zero amount for this assignment.

[APP–52149] Deleting this entry invalidates any future Advance Pay runs for the assignment. Are

you sure you want to delete this entry?

[APP–52150] Legislation Groups or Legislation Vertical Markets cannot insert rows where

Legislation Code is null.

[APP–52151] Cannot cost this assignment because the run that has been reversed has not been

costed for this assignment.

[APP–52152] The system person type must be EMP.

[APP–52152] This combination of balances is invalid for the load date

[APP–52153] You cannot save this update as element entries exist.

[APP–52154] The API Module ID does not reference a Module on the HR_API_MODULES table.

[APP–52155] Cannot delete this Module because it is referenced by a child row in the

HR_API_HOOKS table.

[APP–52158] The Assessment Period Start Date has an incorrect format.

[APP–52159] The Assessment Period End Date has an incorrect format.

[APP–52160] The Assessment Date has an incorrect format.

[APP–52161] No reviewers have yet been defined.

[APP–52162] No assessments match the specified criteria.

[APP–52163] There are no instructions available.

[APP–52164] The Assessee is required.

[APP–52165] The Assessment Date is required.

[APP–52166] A valid Assessment Template must be selected.

[APP–52167] A valid Status must be selected.

[APP–52168] You must include both the appraisal period start and end dates

[APP–52169] You cannot leave the appraisal period start and end dates blank

[APP–52170] You cannot leave the objective start date blank

[APP–52171] You cannot leave the status field blank

[APP–52172] You cannot leave the type field blank

[APP–52173] Validation Errors

[APP–52174] Use the List of Values button to choose a person from the appropriate list

[APP–52175] You must include an appraisal template

[APP–52176] You have not selected a reviewer. Use the List of Values to choose a reviewer, or

press finish to conclude

[APP–52177] Select OK if you want to notify the named person

[APP–52178] Select OK if you wish to cancel data entry for the new objective. (Objective name

and start date cannot be left blank)

[APP–52179] You are already entering a new objective

[APP–52180] Click OK if you have saved your data and you want to view the original appraisal list.

This list has not been updated to reflect any changes you may have made.

[APP–52181] Appraisal Main Menu

[APP–52182] Create an Appraisal

[APP–52183] Appraisal Details

[APP–52184] Header Details

[APP–52185] Comments

[APP–52186] Objectives

[APP–52187] Questionnaire

[APP–52188] Reviewers

[APP–52189] <!DOCTYPE HTML PUBLIC ”–//W3C//DTD HTML 3.2//EN”>

<HTML> <HEAD> <TITLE></TITLE> <META NAME=”Author”

CONTENT=””> <META NAME=”GENERATOR” CONTENT=”Mozilla/3.01Gold (WinNT;

I) [Netscape]”> </HEAD> <BODY> <TABLE> <TR VALIGN=TOP>

<TD VALIGN=TOP>1</TD> <TD VALIGN=TOP>Select the person from the

whole database, or from your working list. Note: You cannot click on any tab other than Instructions

until you have completed the header details and clicked the Continue button. </TD>

</TR> <TR> <TD VALIGN=TOP>2</TD> <TD>Enter header details

for the appraisal: <UL> <LI>include the dates covered by the appraisal, and the date

you perform the appraisal. </LI> <LI>select the questionnaire to include in the appraisal

from the Appraisal Template field. </LI> <LI>select the status of the appraisal, such as

completed or on–going, and the type of appraisal. If your enterprise does not use status and

appraisal types, you can leave these fields blank. </LI> </UL> </TD>

</TR> <TR> <TD VALIGN=TOP>3</TD> <TD>Press the Continue

button.</TD> </TR> <TR> <TD VALIGN=TOP>4</TD>

<TD>Select the appropriate tab to enter further information:</TD> </TR>

</TABLE> </BODY> </HTML>

[APP–52190] Send for Review

[APP–52191] Choose an Appraisal

[APP–52192] There are no appraisals for you to review

[APP–52193] No appraisals meet the criteria entered

[APP–52194] Appraisal Details not found

[APP–52195] Cannot decode the lookup type

[APP–52196] Performance Rating details not found

[APP–52197] Rating level details not found

[APP–52198] Appraisal template details not found

[APP–52199] There are no objectives declared for this appraisal

[APP–52200] A questionnaire does not exist for the appraisal template which this appraisal is using

[APP–52201] No reviewers have yet been notified

[APP–52202] You can only view the information in this mode; you cannot update it

[APP–52203] Check the date format for the Appraisal Period Start Date

[APP–52204] Check the date format for the Appraisal Period End Date

[APP–52205] Appraisal Period End Date must be greater than the Appraisal Period Start Date

[APP–52206] Check the date format for the Appraisal Date

[APP–52207] You must include the objective start date

[APP–52208] Check the date format for the Objective Start Date

[APP–52209] Check the date format for the Objective Target Date

[APP–52210] Check the date format for the Objective Achievement Date

[APP–52211] The Objective Start Date cannot be equal to or greater than the Objective target Date

[APP–52212] The Objective Start Date cannot be equal to or greater than the Objective

Achievement Date

[APP–52213] Bad frame data: likely cause is an incorrect call in the frameset definition

[APP–52214] No person details retrieved

[APP–52215] Bad date format encountered while trying to convert date

[APP–52216] Could not decode lookup for STATUS

[APP–52217] You may not apply for the same vacancy more than once. The existing application

must be ended before reapplying.

[APP–52218] Manage Categories and Questions

[APP–52219] Define Questionnaire

[APP–52220] Assemble Questionnaire

[APP–52221] Define Answer Layout

[APP–52222] Please select a questionnaire and click the Show Categories button

[APP–52223] Select the New button to define the questionnaire. Alternatively, enter part of the

questionnaire name or description and click the Find button

[APP–52224] No questionnaires were retrieved which match the criteria

[APP–52225] Select the New button to define a new question and its answer layout. Alternatively,

enter part of the qustion name or text for which you want to define the layout as it will appear on

the web page and click the find button to retrieve existing ones

[APP–52226] Add questions to this category

[APP–52227] Workflow was unable to send the notification

[APP–52228] Notification succeeded

[APP–52229] Workflow cannot process your notification request: the person is not known to

workflow. Contact your system administrator

[APP–52230] Work Telephone must be null. Telephone numbers are now stored on the

PER_PHONES table.

[APP–52231] Assemble Questionnaire

[APP–52232] Payroll has been run. Changing location will affect the tax record.

[APP–52233] Tax percentage records exist. Change to location will override future tax percentage

records.

[APP–52234] Payroll has already been run.

[APP–52235] Can not delete. Payroll has been run.

[APP–52236] Total percentage time in cities can not exceed the percentage time in county.

[APP–52237] Total percentage time in counties can not exceed the percentage time in state.

[APP–52238] This action changes the W4 Federal Allowances.

[APP–52239] This action changes the W4 State Allowances.

[APP–52240] School District can not be assigned to both city and county.

[APP–52241] No tax percentage record exists for the state : &state.

[APP–52242] No tax percentage record exists for the county : &county.

[APP–52243] No tax percentage record exists for the city : &city.

[APP–52244] You can only have one address of each type at any time.

[APP–52245] The alias name cannot be the same as the function name.

[APP–52246] The appraisal template does not exist

[APP–52247] You must enter a start date for the appraisal template if an end date exists.

[APP–52248] A person, job or position must be set prior to using the deployment factors webpage.

[APP–52249] The earliest available date is not in a valid date format.

[APP–52250] This person does not exist as of the system date.

[APP–52251] The competence_id is invalid.

[APP–52252] You entered an invalid enterprise_id. The enterprise_id must be null or the same as

the business_group_id.

[APP–52253] The end date for the Establishment Attendance is not in a valid date format.

[APP–52254] The Qualification Awarded Date is in an invalid date format.

[APP–52255] The fee for the qualification is not in a valid numeric format.

[APP–52256] You must enter an appraisal template for this appraisal.

[APP–52257] The Assessment Template data is not available.

[APP–52258] The Assessment Data is not available.

[APP–52259] From: &FORWARDER. Review Type: &REVIEW_OBJECT. For: &REVIEWEE

[APP–52260] Please review the &REVIEW_OBJECT for &REVIEWEE. Select the link to perform

the review now. &REVIEW_OBJECT_URL

[APP–52261] Click here to perform the task now

[APP–52262] This competence already exists within the competence category

[APP–52263] This competence already exists within the assessment.

[APP–52264] The competence already exists within this assessment template

[APP–52265] The competence type already exists in this assessment template

[APP–52266] The competence already exists on this date for the specified Enterprise, Organization,

Jon or Position.

[APP–52267] The competence already exists for this Activity.

[APP–52268] The competence already exists for this person on the specified date.

[APP–52269] Inconsistent data: cannot populate rating levels with the rating scale id supplied

[APP–52270] Cannot derive the business group for the person id supplied

[APP–52270] The nuber of grace days is less than the minimum amount of grace days.

[APP–52271] The primary key is invalid. The primary key must be null on insert and

non–updateable on update.

[APP–52272] The cobra enrollment event being referenced does not exist.

[APP–52273] The dependent being covered by the cobra event is outside of the cobra event

coverage dates.

[APP–52274] The contact being referenced does not exist.

[APP–52275] This dependent is already being covered by a different cobra event.

[APP–52276] This dependent has already been covered with the exact same dates.

[APP–52277] Dependents exist which are invalidated by the date change to the cobra enrollment

event. Please change the dates of the dependent coverage and then change the enrollment dates.

[APP–52278] This event clashed with another event for the same assignment. Cobra events must be

unique within a time frame.

[APP–52279] The coverage for cobra events must not exceed 36 months. Change the dates of the

event coverage so that an assignments linked cobra events do not exceed 36 months.

[APP–52280] You cannot end this assignment as future tax record exists

[APP–52281] You cannot delete the assignment as future tax record exists

[APP–52282] You cannot perform this operation as at least one future change in location exists. To

corrects future change(s) datetrack and set the location to &current_location_id

[APP–52285] <!DOCTYPE HTML PUBLIC ”–//W3C//DTD HTML 3.2//EN”>

<HTML> <HEAD> <TITLE></TITLE> <META NAME=”Author ”

CONTENT=””> <META NAME=”GENERATOR” CONTENT=”Mozilla/3.01Gold (WinNT;

I) [Netscape]”> </HEAD> <BODY> <TABLE> <TR VALIGN=TOP>

<TD VALIGN=TOP>1</TD> <TD VALIGN=TOP>Select the person from the

database, or from your working list. Note:You cannot click on any tab other than Instructions until

you have completed the header details and clicked the Continue button </TD> </TR>

<TR> <TD VALIGN=TOP>2</TD> <TD>Enter header details for the

assessment: <UL> <LI> include the date the assessment is performed on.</LI>

<LI>optionally include the dates which indicate the period the assessment refers

too.</LI> <LI>select the template to base the assessment on</LI>

<LI>optionally, select the status of the assessment, such as completed or

on–going.</LI> </UL> </TD> </TR> <TR> <TD

VALIGN=TOP>3</TD> <TD>Press the Continue button.</TD> </TR>

<TR> <TD VALIGN=TOP>4</TD> <TD>Select the appropriate tab to enter

further information:</TD> </TR> </TABLE>

[APP–52286] You can only view the information in this mode.

[APP–52287] You cannot change any part of the assessment, but you can add a comment in the

Reviewer comment box

[APP–52288] The dates of the competence_element for this business which you have entere

overlaps an existing competence record.

[APP–52288] The dates of the competence_element for this business which you have entered

overlaps with an existing competence record.

[APP–52289] You cannot make your change as of the current date because none of the DateTrack

options are available. This occurs when DateTrack functionality does not allow certain options, and

further restrictions have been imposed on this record.

[APP–52290] Error while creating default tax records. Contact your System Administrator.

[APP–52291] Error while getting the defaulting tax rules date. Contact your System Administrator.

[APP–52292] Future dated assignment records exist for this employee. This action confilcts with the

future dated records. Datetrack ahead to final record and resolve the confilct.

[APP–52293] Can not delete when a state is assigned to a work location.

[APP–52294] Can not delete when a county is assigned to a work location.

[APP–52295] Can not delete when a city is assigned to a work location.

[APP–52296] Can not delete when a state is assigned to a primary resident address.

[APP–52297] Can not delete when a county is assigned to a primary resident address.

[APP–52298] Can not delete when a city is assigned to a primary resident address.

[APP–52299] Future dated location records exist for this employee. This action conflicts with the

future dated records. Datetrack ahead to final record and resolve the conflict.

[APP–52300] School district is assigned for the given date range.

[APP–52301] Nothing to save

[APP–52302] You must include a unique name for the objective

[APP–52303] The Appraisal Date must be greater than the Appraisal Period Start Date

[APP–52304] &COUNT competencies have been created or modified. Do you want to save these

changes?

[APP–52305] The group initiator does not exist on the system.

[APP–52306] The group initiator does not exist in the current business group.

[APP–52307] The group initiator does not exist on the date the group is being created.

[APP–52308] You must enter both an initiator and the date to create a group.

[APP–52309] <!DOCTYPE HTML PUBLIC ”–//W3C//DTD HTML 3.2//EN”>

<HTML> <HEAD> <TITLE></TITLE> <META NAME=”Author ”

CONTENT=””> <META NAME=”GENERATOR” CONTENT=”Mozilla/3.01Gold (WinNT;

I) [Netscape]”> </HEAD> <BODY> <TABLE> <TR VALIGN=TOP>

<TD VALIGN=TOP>1</TD> <TD VALIGN=TOP>Select the assessee from the

database, or from your working list. </TD> </TR> <TR> <TD

VALIGN=TOP>2</TD> <TD> Select the assessors from the database, or from your

working list. </TD> </TR> <TR> <TD VALIGN=TOP>3</TD>

<TD>Enter header details for the assessment.<UL> <UL> <LI> include the

date the assessment is performed on.</LI> <LI>optionally include the dates which

indicate the period the assessment refers too.</LI> <LI>select the template to base the

assessment on</LI> <LI>optionally, select the status of the assessment, such as

completed or on–going.</LI> </UL> </TD> </TR> <TR> <TD

VALIGN=TOP>4</TD> <TD>Press the Continue button.</TD> </TR>

Note:You cannot click on any tab other than Instructions until you have completed the header detail

s and clicked the Continue button </TABLE>

[APP–52310] An error has occurred with the notification process. Contact both the sender of this

message and your system administrator.

[APP–52311] The group has been processed. Enter a new group or press cancel to return to the

main menu

[APP–52312] You cannot declare a person more than once in the group

[APP–52313] You must include at least one person in the group

[APP–52314] Data inconsitency: probably workflow (web) usernames do not exist for hr person id

Workflow monitor could not create local_user_roles / an item_key for the process

[APP–52315] Workflow error: workflow has not retrieved the specific URLs for the notifications as

the item_key was null

[APP–52316] <!DOCTYPE HTML PUBLIC ”–//W3C//DTD HTML 3.2//EN”>

<HTML> <HEAD> <TITLE></TITLE> <META NAME=”Author”

CONTENT=””> <META NAME=”GENERATOR” CONTENT=”Mozilla/3.01Gold (WinNT;

I) [Netscape]”> </HEAD> <BODY> <TABLE> <TR VALIGN=TOP>

<TD VALIGN=TOP>1</TD> <TD VALIGN=TOP>Select the person from the

whole database, or from your working list. Note: You cannot click on any tab other than Instructions

until you have completed the header details and clicked the Continue button. </TD>

</TR> <TR> <TD VALIGN=TOP>2</TD> <TD>Enter header details

for the appraisal: <UL> <LI>Add Appraisers to the list – if you wish to remove the

appraiser from the list, select remove from the drop down box. </LI> <LI>include the

dates covered by the appraisal, and the date you perform the appraisal. </LI> <LI>select

the questionnaire to include in the appraisal from the Appraisal Template field. </LI>

<LI>select the status of the appraisal, such as completed or on–going, and the type of

appraisal. If your enterprise does not use status and appraisal types, you can leave these fields blank.

</LI> </UL> </TD> </TR> <TR> <TD

VALIGN=TOP>3</TD> <TD>Press the Continue button.</TD> </TR>

<TR> <TD VALIGN=TOP>4</TD> <TD>Select the appropriate tab to enter

further information:</TD> </TR> </TABLE> </BODY> </HTML>

[APP–52317] Click OK if you have saved your data and you want to view the original assessment

list. This list has not been updated to reflect any changes you may have made.

[APP–52318] Create a 360&#176 Appraisal

[APP–52319] Unable to retrieve details for a specific notification. Probable cause: workflow engine

/ notification process has failed

[APP–52320] Package Name and Procedure Name are required fields.

[APP–52321] The package name you entered does not exist in the database.

[APP–52322] The procedure name you enter must exist within the specified package.

[APP–52323] The procedure name you enter may only be a packaged procedure, and not a function.

[APP–52324] The procedure name you enter may only be a packaged procedure which is not

overloaded.

[APP–52325] The parameter type requires this parameter to be included.

[APP–52326] Parameter details must be retrieved prior to running the API.

[APP–52327] The datatype of the value you enter must match the parameter’s datatype.

[APP–52328] To view the source code, call the API procedure first.

[APP–52329] You have overlapped a RetroPay process and a RetroPay by Action process. This is

invalid. You can only overlap equivalent–time processes, that is, two RetroPay processes or two

RetroPay by Action processes.

[APP–52330] The RetroPay set you specified contains missing or incorrect RetroPay rules. Check

that details of balance, element and input values are correctly entered on the RetroPay Set form.

[APP–52331] Select OK if you do not wish to save this assessment and would like to return to the

appraisal.

[APP–52332] Select OK if you have saved your data and wish to return to the appraisal.

[APP–52333] Select OK if you have saved your data and wish to goto the assessment.

[APP–52334] You need to set up your Assessment Templates before using the assessment web

pages. Please contact your system administator.

[APP–52335] You need to set up your Appraisal Templates before using the assessment web pages.

Please contact your system administrator.

[APP–52336] The &TAXNAME tax rules fields must have a valid value before you can navigate to

the &SCREENNAME screen.

[APP–52337] Error in getting work details. Contact your local support representative.

[APP–52338] The competence date(s) you have entered are outside the business group, job,

position or organization dates.

[APP–52339] The competence element date(s) are outside the valid dates for that competence.

[APP–52340] The activity version is not effective for the date you hav chosen.

[APP–52341] The competence date(s) you have entered are outside the person’s effective date(s)

[APP–52342] The grade is not valid for the effective date(s) you have entered.

[APP–52360] The assignment does not exist as of the effective date.

[APP–52361] You specified an invalid person_id.

[APP–52362] You specified an invalid person_type_id.

[APP–52363] You can only specify a Datetrack Update mode of ’CORRECTION’.

[APP–52364] You must specify a Datetrack Delete Mode of ’DELETE’ or ’ZAP’.

[APP–52365] No person exists with this Person Id.

[APP–52366] You specified an invalid person type.

[APP–52367] This Location is not valid for this Inventory Organization.

[APP–52368] There are no people who match the criteria you have entered.

[APP–52369] Check the Core Competencies or Primary Assignment boxes, or select a vacancy from

which to copy competencies.

[APP–52370] The system cannot launch the main display for the current career management task: –

try to solve by selecting the desired career management option from the main menu – enter suitable

query criteria – select the appropriate record returned If this still fails contact your system

administrator

[APP–52371] The menu option you have selected has not been set up correctly. Contact your

system administrator.

[APP–52372] You have entered an invalid grade.

[APP–52373] When entering competence requirements for an enterprise or an organization the

grade must be null.

[APP–52374] The Qualification Start Date is in an invalid date format.

[APP–52375] The Qualification End Date is in an invalid date format.

[APP–52376] There already exists a record for this person with this person type id on this date.

[APP–52377] You cannot create an application for an ex–applicant. Either reverse the termination

of the closed application or change the person type to include an active type, for example, applicant

and ex–applicant.

[APP–52378] You have entered a future hire date. You will not be able to view this person until that

date.

[APP–52379] The related person resides with designator flag must be set to ’Y’ or ’N’.

[APP–52380] The reason you have entered for the start of this contact relationship does not exist on

the effective date.

[APP–52381] The reason you have entered for the end of this contact relationship does not exist on

the effective date.

[APP–52382] The labour union member flag must be set to ’Y’ or ’N’.

[APP–52383] You have entered an invalid bargaining unit code.

[APP–52384] The end date of the relationship cannot exist without a start date.

[APP–52930] The rating scale you have selected is not of type Performance.

[APP–52950] The process &PROCESS_NAME in the &ITEM_TYPE item type does not contain

the Top Node Selector Activity. Each top level task flow process must contain this activity.

[APP–52951] You can only have one Top Node Selector Activity for the process

&PROCESS_NAME in the &ITEM_TYPE item type.

[APP–52952] The Top Node Selector Activity for the process &PROCESS_NAME in the

&ITEM_TYPE item type does not transition to a Top Node window.

[APP–52953] The Top Node Selector Activity for the process &PROCESS_NAME in the

&ITEM_TYPE item type must transition to one Top Node window only.

[APP–52954] The Top Node Selector Activity for the process &PROCESS_NAME in the

&ITEM_TYPE item type transitions to an Activity that is not defined as a Top Node window.

[APP–52955] The task flow &FROM_FORM_ACTIVITY window for the process

&PROCESS_NAME in the &ITEM_TYPE item type must only transition to the

&TO_FORM_ACTIVITY window once.

[APP–52956] The task flow &FROM_FORM_ACTIVITY window for the process

&PROCESS_NAME in the &ITEM_TYPE item type must transition to the

&TO_FORM_ACTIVITY window.

[APP–52957] There is no Task flow Navigation Unit defined for the &ACTIVITY_NAME window.

You must define a navigation unit for this window before using it in the process

&PROCESS_NAME in the &ITEM_TYPE item type.

[APP–52958] The process &PROCESS_NAME in the &ITEM_TYPE item type cannot be found.

Either the process is not defined within this item type, or it is not runnable.

[APP–52959] The task flow &FROM_FORM_ACTIVITY window for the process

&PROCESS_NAME in the &ITEM_TYPE item type must transition to the specified Top Node

&TO_FORM_ACTIVITY window.

[APP–52960] Please save your changes before converting Task flows.

[APP–52961] Adoption date must be later than the date of birth

[APP–52962] Date of receipt of death certificate must be later than the date of death

[APP–52963] Date of death must be later than the date of birth

[APP–52964] &COLUMN must be greater than or equal to 0.

[APP–52965] &COLUMN must be between &MINIMUM and &MAXIMUM

[APP–52966] The &COLUMN value does not exist as a lookup for lookup type &LOOKUP_TYPE.

[APP–52967] The assignment must have a salary basis.

[APP–52968] The assignment must have a payroll.

[APP–52969] The business group of tax record must match the business group of the assignment.

[APP–52970] The &COLUMN can only be ’Y’ or ’N’.

[APP–52971] Invalid datetrack delete mode. Only ZAP is allowed for tax records.

[APP–52972] Enter a period start date.

[APP–52973] Enter a period end date.

[APP–52974] Warning: Payment has not been made for the assignment you have selected to reverse

– you may still rollback this assignment’s payroll. Do you wish to proceed with the reversal?

[APP–52975] Assignment action interlock rule failure. You cannot mark this process for retry as

there has been subsequent post–run processing for this payroll. To remedy this you can mark the

subsequent process for retry. Marking for retry deletes the results of the subsequent process and

enables you to retry the first process. Please note an exception to this procedure. If the subsequent

process is a payments process (magnetic transfer, cheque, or cash) you can only delete it in order to

retry the preceding process.

[APP–52976] Involuntary Deduction Name must be less than 13 characters

[APP–52977] You cannot update this assignment with these details. To correct the original problem

please query this assignment and reapply your change.

[APP–54000] Process failed to start.

[APP–54001] Cannot start process. Corresponding product is not installed.

[APP–54002] Responsibility context: &AZWCURTYPE – &AZWCURCTXT Desired context:

&AZWDESTYPE – &AZWDESCTXT Must use a responsibility whose profile value equals the

desired context. Either switch to a different responsibility, or create a responsibility that has the

desired context associated to the profile option : GL – Set of Books.

[APP–54003] You are at the first step of the process. Can not go to the previous step.

[APP–54004] Responsibility context: &AZWCURTYPE – &AZWCURCTXT Desired context:

&AZWDESTYPE – &AZWDESCTXT Must use a responsibility whose profile value equals the

desired context. Either switch to a different responsibility, or create a responsibility that has the

desired context associated to the profile option : MO – Operating Unit.

[APP–54005] Responsibility context: &AZWCURTYPE – &AZWCURCTXT Desired context:

&AZWDESTYPE – &AZWDESCTXT Must use a responsibility whose profile value equals the

desired context. Either switch to a different responsibility, or create a responsibility that has the

desired context associated to the profile option : HR: Security Profile.

[APP–54006] Responsibility context: &AZWCURTYPE – &AZWCURCTXT Desired context:

&AZWDESTYPE – &AZWDESCTXT Must use a responsibility whose profile value equals the

desired context. Either switch to a different responsibility, or create a responsibility that has the

desired context associated to the profile option : OE: Item Validation Organization.

[APP–55000] Custom API failure:

[APP–55001] The application ID given will be ignored. The list of objects to be extracted will be

used.

[APP–55002] The application short name given will be ignored. The application ID will be used

instead.

[APP–55003] The application short name given is invalid.

[APP–55004] The primary Flow Page Region for Flow Page with key ’&KEY’ is invalid. Please

reassign a primary Flow Page Region to this Flow Page.

[APP–55005] The primary Flow Page for Flow with key ’&KEY’ is invalid. Please reassign a

primary Flow Page to this Flow.

[APP–55006] Please enter the regions to assign the object attribute to, or press Cancel to return

without selecting any regions.

[APP–55007] Attribute record with key ’&KEY’ is created.

[APP–55008] Attribute with key ’&KEY’ deleted.

[APP–55009] Attribute does not exist.

[APP–55010] Attribute already exists.

[APP–55011] Attribute Navigation

[APP–55012] Attribute with key ’&KEY’ not created.

[APP–55013] Attribute with key ’&KEY’ not deleted.

[APP–55014] Attribute with key ’&KEY’ not downloaded.

[APP–55015] Attribute with key ’&KEY’ not updated.

[APP–55016] Attribute with key ’&KEY’ updated.

[APP–55017] An error occurred while updating Attribute record.

[APP–55018] Attribute Value

[APP–55019] Value error occurred while processing fields for attribute with key ’&KEY’. Make

sure that all data fields are of the correct data type and within the length constraints.

[APP–55020] Attribute with key ’&KEY’ not downloaded.

[APP–55021] You cannot delete the Primary Flow Page Region of a Flow Page.

[APP–55022] Please provide a value for &COLUMN.

[APP–55023] Attribute datatype cannot be changed while there are instance attribute value

assignments.

[APP–55024] You cannot delete the Primary Flow Page Region of a Flow Page.

[APP–55025] You cannot delete the Primary Page of a Flow.

[APP–55026] This Attribute record cannot be deleted because it is referenced by another Object

Attribute record.

[APP–55027] This Attribute record cannot be deleted because it is referenced by another Region

Item record.

[APP–55028] This Foreign Key record cannot be deleted because it is referenced by another Foreign

Key Column record.

[APP–55029] This Foreign Key record cannot be deleted because it is referenced by another Flow

Region Relationship record.

[APP–55030] This Flow record cannot be deleted because it is referenced by another Flow Page

record.

[APP–55031] This Object Attribute record cannot be deleted because it is referenced by another

Region Item record.

[APP–55032] This Object Attribute record cannot be deleted because it is referenced by another

Object Attribute Navigator record.

[APP–55033] This Object Attribute record cannot be deleted because it is referenced another Flow

Page Region Item record.

[APP–55034] This Object record cannot be deleted because it is referenced by another Foreign Key

record.

[APP–55035] This Object record cannot be deleted because it is referenced by another Object

Attribute record.

[APP–55036] This Object record cannot be deleted because it is referenced by another Region

record.

[APP–55037] This Object Attribute record cannot be deleted because it is referenced by another

Unique Key record.

[APP–55038] This Flow Page Region record cannot be deleted because it is referenced by another

Flow Page Region Item record.

[APP–55039] This Flow Page Region record cannot be deleted because it is referenced by another

Flow Region Relationship record.

[APP–55040] This Flow Page record cannot be deleted because it is referenced by another Flow

Page Region record.

[APP–55041] This Region record cannot be deleted because it is referenced by another Object

Attribute Navigation record.

[APP–55042] This Region record cannot be deleted because it is referenced by another Flow Page

Region record.

[APP–55043] This Region record cannot be deleted because it is referenced by another Region Item

record.

[APP–55044] This Flow Region Relationship record cannot be deleted because it is referenced by

another Flow Page Region Item record.

[APP–55045] This Unique Key Column record cannot be deleted because it is referenced by another

Foreign Key Column record.

[APP–55046] This Unique Key record cannot be deleted because it is referenced by another Foreign

Key record.

[APP–55047] This Unique Key record cannot be deleted because it is referenced by another Unique

Key Column record.

[APP–55048] You may not edit this value.

[APP–55049] You cannot change the data type of this object attribute. Please delete the records

from the &FORM form first.

[APP–55050] Data Type for this Attribute is being used within Oracle Bill of Materials – cannot be

changed.

[APP–55051] Data Type cannot be changed if there is an existing Default Value.

[APP–55052] Please delete the foreign key columns first.

[APP–55053] Cannot deselect Primary Region. Please delete the record in Flow Page Relations

form first.

[APP–55054] DBMS Database update failure

[APP–55055] Please enter a unique value.

[APP–55056] There is nothing in the input file to be loaded to the database.

[APP–55057] File &PATH/&FILE is empty.

[APP–55058] End of Core Modules – AK Loader file Download Session.

[APP–55058] End of Core Modules – AK Loader file Upload Session.

[APP–55059] Please enter an attribute name.

[APP–55060] Please enter the number of characters for displaying the label.

[APP–55061] Please enter the number of characters for displaying the value.

[APP–55062] You must enter a value length for VARCHAR2 or NUMBER data types.

[APP–55063] AK_EXCLUDED_ITEMS

[APP–55064] Excluded Item with key ’&KEY’ created.

[APP–55065] Excluded Item does not exist in AK_EXCLUDED_ITEMS.

[APP–55066] Excluded Item already exists.

[APP–55067] Excluded Item with key ’&KEY’ not created.

[APP–55068] Excluded Item with key ’&KEY’ not downloaded.

[APP–55069] Value error occurred while processing fields for Excluded Item with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55070] Foreign Key Column with key ’&KEY’ created.

[APP–55071] Foreign Key Column with key ’&KEY’ deleted.

[APP–55072] Foreign Key Column does not exist in AK_FOREIGN_KEY_COLUMNS table.

[APP–55073] Foreign Key Column already exists in AK_FOREIGN_KEY_COLUMNS table.

[APP–55074] Foreign Key Column with key ’&KEY’ not created.

[APP–55075] Foreign Key Column with key ’&KEY’ not deleted.

[APP–55076] Foreign Key Column with key ’&KEY’ not downloaded.

[APP–55077] Foreign Key Column with key ’&KEY’ not updated.

[APP–55078] Foreign Key Column with key ’&KEY’ updated.

[APP–55079] An error occurred while updating Foreign Key Column record.

[APP–55080] Value error occurred while processing fields for Foreign Key Column with key

’&KEY’. Make sure that all data fields are of the correct data type and within the length

constraints.

[APP–55081] Cannot delete this foreign key. Please delete the LOV foreign key ’&K_VALUE’ on

the Object Attributes form first.

[APP–55082] Cannot delete this foreign key. Please delete the relationship ’&K_VALUE’ on the

Flow Page Relations form first.

[APP–55083] Cannot delete this foreign key. Please delete the LOV foreign key ’&K_VALUE’ on

the Region Items form first.

[APP–55084] Flow with key ’&KEY’ created.

[APP–55085] Flow with key ’&KEY’ deleted.

[APP–55086] Flow does not exist in AK_FLOWS table.

[APP–55087] Flow already exists in AK_FLOWS table.

[APP–55088] Flow with key ’&KEY’ not created.

[APP–55089] Flow with key ’&KEY’ not deleted.

[APP–55090] Flow with key ’&KEY’ not downloaded.

[APP–55091] Flow with key ’&KEY’ not updated.

[APP–55092] Flow Page

[APP–55093] Flow Page with key ’&KEY’ created.

[APP–55094] Flow Page with key ’&KEY’ deleted.

[APP–55095] Flow Page does not exist in AK_FLOW_PAGES table.

[APP–55096] Flow Page already exists in AK_FLOW_PAGES table.

[APP–55097] Flow Page with key ’&KEY’ not created.

[APP–55098] Flow Page with key ’&KEY’ not deleted.

[APP–55099] Flow Page with key ’&KEY’ not downloaded.

[APP–55100] Flow Page with key ’&KEY’ not updated.

[APP–55101] Flow Page Region

[APP–55102] Flow Page Relations

[APP–55103] Flow Page with key ’&KEY’ updated.

[APP–55104] An error occurred while updating Flow Page record.

[APP–55105] Value error occurred while processing fields for Flow Page with key ’&KEY’. Make

sure that all data fields are of the correct data type and within the length constraint.

[APP–55106] Value error occurred while processing fields for Flow Primary Key with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55107] Flow with key ’&KEY’ updated.

[APP–55108] An error occurred while updating Flow record.

[APP–55109] Value error occurred while processing fields for Flow with key ’&KEY’. Make sure

that all data fields are of the correct data type and within the length constraint.

[APP–55110] Foreign Key

[APP–55111] Foreign Key Column

[APP–55112] Foreign Key with key ’&KEY’ created.

[APP–55113] Foreign Key with key ’&KEY’ deleted.

[APP–55114] Foreign Key does not exist in AK_FOREIGN_KEYS table.

[APP–55115] Foreign Key already exists in AK_FOREIGN_KEYS table.

[APP–55116] Foreign Key with key ’&KEY’ not created.

[APP–55117] Foreign Key with key ’&KEY’ not deleted.

[APP–55118] Foreign Key with key ’&KEY’ not downloaded.

[APP–55119] Foregin Key with key ’&KEY’ not updated.

[APP–55120] Foreign Key with key ’&KEY’ updated.

[APP–55121] An error occurred while updating Foreign Key record.

[APP–55122] Value error occurred while processing fields for Foreign Key with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55123] An error occurred while retrieving the next token from the input file. Please check

your input file.

[APP–55124] An error occurred while writing the standard header information to the loader file.

[APP–55125] Header information is missing from Loader file.

[APP–55126] Value entered is not consistent with data type &DATA_TYPE.

[APP–55127] An error occurred while inserting an attribute record.

[APP–55128] An error occurred while inserting a Foreign Key record.

[APP–55129] An error occurred while inserting a Flow record.

[APP–55130] An error occurred while inserting a Flow Page record.

[APP–55131] An error occurred while insertng an Object Attribute record.

[APP–55132] An error occurred while inserting an Object record.

[APP–55133] An error occurred while inserting a record into Object Primary Key table.

[APP–55134] An error occurred while inserting a Region record.

[APP–55135] An error occurred while inserting a Region Item record.

[APP–55136] Assign Attribute Values

[APP–55137] Attribute with key ’&KEY’ referenced by the following record does not exist in

AK_ATTRIBUTES table.

[APP–55138] Business Object parameter ’&INVALID’ is invalid. It must be FLOW, REGION,

OBJECT, or ATTRIBUTE.

[APP–55139] Column &COLUMN does not exist in object &OBJECT.

[APP–55140] The value in &COLUMN is invalid.

[APP–55141] Invalid file handle error. Please contact your Oracle Representative.

[APP–55142] Attemp to open a file failed with an invalid mode &MODE.

[APP–55144] An invalid file operation error occurred on file &PATH/&FILE. The program may be

trying to write to or read from a file that does not exist.

[APP–55145] Path &PATH does not exist or is not accessible by PL/SQL.

[APP–55146] Foreign Key with key ’&KEY’ referenced by the following message does not exist in

AK_FOREIGN_KEYS table.

[APP–55147] Foreign Key with key ’&KEY’ referenced by the following message does not exist in

AK_FOREIGN_KEYS table.

[APP–55148] Flow Page with key ’&KEY’ referenced by the following message does not exist in

AK_FLOW_PAGES table.

[APP–55149] Flow with key ’&KEY’ referenced by the following message does not exist in

AK_FLOWS table.

[APP–55150] The foreign key provided does not define the relationship between the two regions.

Please select another foreign key.

[APP–55151] Foreign key sequence number &SEQUENCE must corespond to a column in the

referenced primary key.

[APP–55152] Fatal Error: There are no regions remaining to format.

[APP–55153] Region &REGION_NAME cannot be formatted. Please choose another Region.

[APP–55154] There is an invliad element in the list at element number &ELEMENT_NUM.

[APP–55155] Lov Foreign Key with key ’&KEY’ referenced by the following message does not

exist in AK_FOREIGN_KEYS table.

[APP–55156] Lov Attribute with key ’&KEY’ referenced by the following message does not exist

in AK_REGION_ITEMS table.

[APP–55157] Lov Region with key ’&KEY’ referenced by the following message does not exist in

AK_REGIONS table.

[APP–55158] Object Attribute with key ’&KEY’ referenced by the following message does not

exist in AK_OBJECT_ATTRIBUTES table.

[APP–55159] Object with key ’&KEY’ referenced by the following message does not exist in

AK_OBJECTS table.

[APP–55160] Flow Page Region with key ’&KEY’ referenced by the following message does not

exist in AK_FLOW_PAGE_REGIONS table.

[APP–55161] Query failure; return value = &RETURN_VALUE.

[APP–55162] Fatal Error: Region &REGION_APPL_CODE not defined for query.

[APP–55163] Region with key ’&KEY’ referenced by the following message does not exist in

AK_REGIONS table.

[APP–55164] Region Item with key ’&KEY’ referenced by the following message does not exist in

AK_REGION_ITEMS table.

[APP–55165] Flow Page Relation with key ’&KEY’ referenced by the following message does not

exist in AK_FLOW_REGION_RELATIONS table.

[APP–55166] Cannot mix 3rd Normal and 4th Normal in Data Source Type and Data Storage Type.

[APP–55167] Invalid startup region. The parameters for calling this form are incorrect.

[APP–55168] Target flow page region must be different from the current flow page region.

[APP–55169] Target Page with key ’&KEY’ referenced by the following message does not exist in

AK_FLOW_PAGES table.

[APP–55170] Either the region with ’&KEY’ does not exist, or it is not a region for the object with

key ’&OBJECT’.

[APP–55171] Either the Target URL Attribute ’&KEY’ does not exist, or it is not of data type

’URL’.

[APP–55172] Unique Key with key ’&KEY’ referenced by the following message does not exist in

AK_UNIQUE_KEYS table.

[APP–55173] View with name ’&KEY’ referenced by the following message does not exist in

ALL_VIEWS nor in FND_VIEWS table.

[APP–55174] Invalid write mode. It must be ’A’ (append) or ’W’ (overwrite).

[APP–55175] attribute

[APP–55176] region

[APP–55177] region item

[APP–55178] &NUMLINES lines processed.

[APP–55180] LOV Region

[APP–55181] Data Type cannot be changed if there is an existing List Attribute.

[APP–55182] The LOV region ’&KEY’ that is referenced by this record does not exist in

AK_REGIONS table.

[APP–55183] You have changed this label from ’&OLD_LABEL’ to ’&NEW_LABEL’. Do you

want to change the labels from ’&OLD_LABEL’ to ’&NEW_LABEL’ for all related Object

Attributes and Region Items?

[APP–55184] You have changed this label from ’&OLD_LABEL’ to ’&NEW_LABEL’. Do you

want to change the labels from ’&OLD_LABEL’ to ’&NEW_LABEL’ for all related Region Items?

[APP–55185] Attribute Name

[APP–55186] Flow Name

[APP–55187] Inverse Relationship

[APP–55188] Long Label

[APP–55189] Object Name

[APP–55190] Page Name

[APP–55191] Region Name

[APP–55192] Relationship

[APP–55193] Relationship Description

[APP–55194] &COLUMN must be null.

[APP–55195] Attribute Navigation with key ’&KEY’ created.

[APP–55196] Object Attribute Navigation with key ’&KEY’ deleted.

[APP–55197] Attribute Navigation does not exist in AK_OBJECT_ATTRIBUTE_NAVIGATION

record.

[APP–55198] Attribute Navigation record already exists in

AK_OBJECT_ATTRIBUTE_NAVIGATION table.

[APP–55199] Attribute Navigation with key ’&KEY’ not created.

[APP–55200] Attribute Navigation with key ’&KEY’ not deleted.

[APP–55201] Attribute Navigation with key ’&KEY’ not downloaded.

[APP–55202] Attribute Navigation with key ’&KEY’ not updated.

[APP–55203] Attribute Navigation with key ’&KEY’ updated.

[APP–55204] An error occurred while updating an Attribute Navigation record.

[APP–55205] Value error occurred while processing fields for Attribute Navigation with key

’&KEY’. Make sure that all data fields are of the correct data type and within the length

constraints.

[APP–55206] New Flow Application Name and New Flow Code already exists. Please change name

or code.

[APP–55207] New Region Application Name and New Region ID already exists. Please change

name or ID.

[APP–55208] A page’s Primary Region cannot be updated.

[APP–55209] There is no intrapage relation connecting this page region with its parent page region.

Please provide the name of a valid foreign key connecting these two regions and the API will create

the relation for you.

[APP–55210] No items exist for Region &REGION_APPL.

[APP–55211] No primary key fields are defined for Region &REGION_APPL.

[APP–55212] Please specify a Target Page or a Target URL Attribute.

[APP–55213] There is no Flow Region Relation connecting this Page Region Link with the Target

Page whose key is ’&KEY’.

[APP–55214] Please specify an application ID, application short name, or a list of flows, regions,

objects, or attributes to be extracted to the file.

[APP–55215] Object

[APP–55216] Object Attributes

[APP–55217] Object Attribute with key ’&KEY’ created.

[APP–55218] Object Attribute with key ’&KEY’ deleted.

[APP–55219] Object Attribute with key ’&KEY’ does not exist in AK_OBJECT_ATTRIBUTES.

[APP–55220] Object Attribute already exists in AK_OBJECT_ATTRIBUTES table.

[APP–55221] Object Attribute with key ’&KEY’ not created.

[APP–55222] Object Attribute with key ’&KEY’ not deleted.

[APP–55223] Object Attribute with key ’&KEY’ not downloaded.

[APP–55224] Object Attribute with key ’&KEY’ not updated.

[APP–55225] Object Attribute with key ’&KEY’ updated.

[APP–55226] An error occurred while updating an Object Attribute record.

[APP–55227] Value error occurred with processing fields for Object Attribute with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55228] Object with key ’&KEY’ created.

[APP–55229] Object with key ’&KEY’ deleted.

[APP–55230] Object does not exist in AK_OBJECTS.

[APP–55231] &OBJECT already exists.

[APP–55232] Object with key ’&KEY’ not created.

[APP–55233] Object with key ’&KEY’ not deleted.

[APP–55234] Object with key ’&KEY’ not downloaded.

[APP–55235] Object with key ’&KEY’ not updated.

[APP–55236] Object primary key table

[APP–55237] Value error occurred while processing primary key table of objects. Make sure that

all data fields are of the correct datat type and within the length constraints.

[APP–55238] Object with key ’&KEY’ updated.

[APP–55239] An error occurred while updating an Object record.

[APP–55240] Value error occured while processing fields for Object with key ’&KEY’. Make sure

that all data fields are of the correct data type and within the length constraints.

[APP–55241] One of the Value fields must be provided.

[APP–55242] Order Sequence must be unique within the Region.

[APP–55243] Discard current values?

[APP–55244] Flow Page Region with key ’&KEY’ created.

[APP–55245] Flow Page Region with key ’&KEY’ deleted.

[APP–55246] Flow Page Region already exists in AK_FLOW_PAGE_REGIONS table.

[APP–55247] Page Region Links

[APP–55248] Flow Page Region with key ’&KEY’ updated.

[APP–55249] No parent Page Region is allowed for the primary Page Region of a Page.

[APP–55250] In line &LINENUM – Encountered symbol &TOKEN while expecting

&EXPECTED.

[APP–55251] Page Region with key ’&KEY’ does not exist in AK_FLOW_PAGE_REGIONS table.

[APP–55252] Flow Page Region with key ’&KEY’ not created.

[APP–55253] Flow Page Region with key ’&KEY’ not deleted.

[APP–55254] Flow Page Region with key ’&KEY’ not downloaded.

[APP–55255] Flow Page Region with key ’&KEY’ not updated.

[APP–55256] An error occurred while updating Flow Page Region record.

[APP–55257] Value error occurred while processing fields for Page Region with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55258] Flow Page Region Item with key ’&KEY’ created.

[APP–55259] Flow Page Region Item with key ’&KEY’ deleted.

[APP–55260] Flow Page Region Item does not exist in AK_FLOW_PAGE_REGION_ITEMS table.

[APP–55261] Flow Page Region Item already exists in AK_FLOW_PAGE_REGION_ITEMS table.

[APP–55262] Flow Page Region Item with key ’&KEY’ not created.

[APP–55263] Flow Page Region Item with key ’&KEY’ not deleted.

[APP–55264] Page Region Item with key ’&KEY’ not downloaded.

[APP–55265] Flow Page Region Item with key ’&KEY’ not updated.

[APP–55266] Flow Page Region Item with key ’&KEY’ updated.

[APP–55267] An error occurred while updating Flow Page Region Item record.

[APP–55268] Value error occurred while processing fields for Page Region Item with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55269] Lockname too long: unable to generate lock handle. Please contact your Oracle

Representative.

[APP–55270] Reassign the primary page before deleting this page.

[APP–55271] New object attribute has been created. Refresh the screen now to show the new data?

[APP–55272] Regions

[APP–55273] You have changed an attribute value. This has changed the list of available regions.

Please select a valid region from the poplist.

[APP–55274] Region with key ’&KEY’ created.

[APP–55275] Region with key ’&KEY’ deleted.

[APP–55276] Region does not exist in AK_REGIONS table.

[APP–55277] Region already exists in AK_REGIONS table.

[APP–55278] Region Items

[APP–55279] Region with key ”&KEY’ not created.

[APP–55280] Region with key ’&KEY’ not deleted.

[APP–55281] Region with key ’&KEY’ not downloaded.

[APP–55282] Region with key ’&KEY’ not updated.

[APP–55283] Value error occurred while processing fields for Region Primary Key table. Make

sure that all data fields are of the correct data type and within the length constraints.

[APP–55284] Region with key ’&KEY’ updated.

[APP–55285] An error occurred while updating a Region record.

[APP–55286] Value error occurred while processing fields for Region with key ’&KEY’. Make sure

that all data fields are of the correct data type and within the length constraints.

[APP–55287] Region Item with key ’&KEY’ created.

[APP–55288] Region Item with key ’&KEY’ deleted.

[APP–55289] Region Item does not exist in AK_REGION_ITEMS table.

[APP–55290] Region Item already exists in AK_REGION_ITEMS table.

[APP–55291] Region Item with key ’&KEY’ not created.

[APP–55292] Region Item with key ’&KEY’ not deleted.

[APP–55293] Region Item with key ’&KEY’ not downloaded.

[APP–55294] Region Item with key ’&KEY’ not updated.

[APP–55295] Region Item with key ’&KEY’ updated.

[APP–55296] An error occurred while updating a Region Item record.

[APP–55297] Value error occurred while processing fields for Region Item with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55298] Flow Region Relationship with key ’&KEY’ created.

[APP–55299] Flow Region Relationship with key ’&KEY’ deleted.

[APP–55300] Flow Region Relationship does not exist in AK_FLOW_REGION_RELATIONS

table.

[APP–55301] Flow Region Relationship already exists in AK_FLOW_REGION_RELATIONS

table.

[APP–55302] Flow Region Relationship with key ’&KEY’ not created.

[APP–55303] Flow Region Relationship with key ’&KEY’ not deleted.

[APP–55304] Flow Region Relationship with key ’&KEY’ not downloaded.

[APP–55305] Flow Region Relationship with key ’&KEY’ not updated.

[APP–55306] Flow Region Relationship with key ’&KEY’ updated.

[APP–55307] Value error occurred while processing fields for Flow Region Relations with key

’&KEY’. Make sure that all data fields are of the correct data type and within the length

constraints.

[APP–55308] Data in the underlying table has been changed. Requery?

[APP–55309] This Attribute has been made Required because it is required in the database.

[APP–55310] &LABEL is a required field. Please make an entry in this field.

[APP–55311] AK_RESP_SECURITY_ATTRIBUTES

[APP–55312] Security Attribute already exists.

[APP–55313] Security Attribute does not exist in AK_RESP_SECURITY_ATTRIBUTES.

[APP–55314] Securing Attribute already exists.

[APP–55315] Securing Attribute with key ’&KEY’ not created.

[APP–55316] Securing Attribute with key ’&KEY’ not downloaded.

[APP–55317] Value error occurred while processing fields for Securing Attribute with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55318] Please save this &TABLE first.

[APP–55319] You must select an item first.

[APP–55320] Start of Core Modules – AK Loader file Download Session.

[APP–55321] Start of Core Modules – AK Loader file Upload Session.

[APP–55322] Only either a Target Page or a Target URL Attribute can be in a Flow Page Region

Item. Please delete one of them.

[APP–55323] Unique Key Column with key ’&KEY’ created.

[APP–55324] Unique Key Column with key ’&KEY’ deleted.

[APP–55325] Unique Key Column does not exist in AK_UNIQUE_KEY_COLUMNS table.

[APP–55326] Unique Key Column already exists in AK_UNIQUE_KEY_COLUMNS table.

[APP–55327] Unique Key Column with key ’&KEY’ not created.

[APP–55328] Unique Key Column with key ’&KEY’ not deleted.

[APP–55329] Unique Key Column with key ’&KEY’ not downloaded.

[APP–55330] Unique Key Column with key ’&KEY’ not updated.

[APP–55331] Unique Key Column with key ’&KEY’ updated.

[APP–55332] An error occurred while updating Unique Key Column record.

[APP–55333] Value error occurred while processing fields for Unique Key Column with key

’&KEY’. Make sure that all data fields are of the correct data type and within the length

constraints.

[APP–55334] Encountered end of file when expecting more text from the file.

[APP–55335] Display sequence # must be unique within a region.

[APP–55336] Unique Key

[APP–55337] Unique Key Column

[APP–55338] Unique Key with key ’&KEY’ created.

[APP–55339] Unique Key with key ’&KEY’ deleted.

[APP–55340] Unique Key does not exist in AK_UNIQUE_KEYS table.

[APP–55341] Unique Key already exists in AK_UNIQUE_KEYS table.

[APP–55342] Unique Key with key ’&KEY’ not created.

[APP–55343] Unique Key with key ’&KEY’ not deleted.

[APP–55344] Unique Key with key ”&KEY’ not downloaded.

[APP–55345] Unique Key with key ’&KEY’ not updated.

[APP–55346] Unique Key Column with key ’&KEY’ updated.

[APP–55347] An error occurred while updating Unique Key record.

[APP–55348] Value error occurred while processing fields for Unique Key with key ’&KEY’.

Make sure that all data fields are of the correct data type and within the length constraints.

[APP–55349] Unique Key Sequence number must be unique. Sequence number &SEQUENCE

already exists within this Unique Key ’&KEY’, please use another number.

[APP–55350] An error occurred while updating &OBJECT record.

[APP–55351] Database update failure

[APP–55352] ***** Second pass for reading file &FILE. Please investigate and resolve all errors

below:

[APP–55353] Value eror occurred while processing fields for &OBJECT with key ’&KEY’. Make

sure that all data fields are of the correct data type and within the length constraints.

[APP–55354] Value in &COLUMN must be ’Y’ or ’N’.

[APP–55355] Value length cannot exceed &VALUE_LENGTH characters.

[APP–55356] Save changes?

[APP–55357] This Loader flat file version is not compatible with the Loader program. Please obtain

the correct version of flat file before running Upload.

[APP–55358] Fatal Error: Region &REGION_APPL not associated with object name &OBJECT.

[APP–55359] Database Object

[APP–55360] The parent region must be distinct from the child region.

[APP–55361] Flow ID

[APP–55362] Flow Name

[APP–55363] Flow Pages

[APP–55364] Flow Page Regions

[APP–55365] Flow Region Relationship

[APP–55366] Foreign Keys

[APP–55367] Foreign Key Name

[APP–55368] page

[APP–55369] region

[APP–55370] relation

[APP–55371] Page

[APP–55372] Page ID

[APP–55373] Primary Key Name

[APP–55374] Region Attributes

[APP–55375] Region ID

[APP–55376] Region Name

[APP–55377] You cannot delete a region which has children. Delete the child regions first before

deleting the parent.

[APP–55378] You cannot delete the &ENTITY1 of a &ENTITY2

[APP–55379] This &ENTITY is referenced in other tables. Please delete the record in the

&ENTITY2 form first.

[APP–55380] A &ENTITY has already been selected for this &ENTITY2. Deselect the current

&ENTITY before selecting a new one.

[APP–55381] A &ENTITY with this name already exists. Please select another.

[APP–55382] An &ENTITY with this name already exists. Please select another.

[APP–55383] Field &ENTITY must be entered

[APP–55384] A primary page must be assigned to the flow

[APP–55385] A primary region must be assigned to the page

[APP–56000] &ERROR Unexpected error in the trigger &TRIGGER_NAME

[APP–56001] &ERROR Unexpected error in the PL/SQL package &PACKAGE_NAME

[APP–56002] Program error: &ERROR Failed to insert a record in the table &TABLE_NAME.

Please contact your system administrator.

[APP–56003] &ERROR Failed to delete a record in the table &TABLE_NAME

[APP–56004] Program error in &LOCATION. &ERROR Please contact your system administrator

or support representative.

[APP–56005] The job successfully completed.

[APP–56006] Program error: &MESSAGE Please contact your support representative.

[APP–56007] No value is defined for the lookup code &LOOKUP_CODE and the lookup_type

&LOOKUP_TYPE

[APP–56008] Program error: data integrity violation in &LOCATION. Please contact your support

representative.

[APP–56009] This entry already exists.

[APP–56010] &MESGBUF

[APP–56100] Rules successfully deleted

[APP–56102] System error in deleting the rule lines: &ERROR

[APP–56103] System error in deleting the rule: &ERROR

[APP–56104] System error when validating the rule delete: &ERROR

[APP–56110] System error when saving the setup for the event type &EVENT_TYPE: &ERROR

[APP–56111] System error when updating the saved setup for the event type &EVENT_TYPE:

&ERROR

[APP–56112] System error when saving the setup: &ERROR

[APP–56120] Loading successfully completed

[APP–56121] System error when validating: &ERROR

[APP–56122] System error when inserting rules: &ROWS inserted instead of 1

[APP–56123] System error when inserting rules: &ERROR

[APP–56124] System error: The rowid &ROWID is invalid in table &TABLE_NAME

[APP–56125] System error when during access of sequence ax_conditions_s: &ERROR

[APP–56126] System error when updating the translator program info: &ERROR

[APP–56127] Invalid rule name.

Cause:

&RULE_NAME is not a valid rule name or this set has been purged

Action:

please select another rule name

[APP–56130] System error when restoring the category code for the event type &EVENT_TYPE:

&ERROR

[APP–56131] System error when restoring the category codes: &ERROR

[APP–56140] Purge successfully completed

[APP–56141] System error when purging &TABLE_NAME: &ERROR

[APP–56142] System error during purge validation: &ERROR

[APP–56147] The rule name &RULE_NAME is already in use.

[APP–56148] Dynamically generated MRC rulesets cannot be unloaded.

[APP–56149] Unload completed with warnings. The following query chains are shared with others

translator programs: &SHARED_QC

[APP–56150] Unload successfully completed

[APP–56151] System error: &ERROR This error occurred during insert of rule for the following

record:

Table : &TABLE_NAME

Column: &COLUMN_NAME

Value : &VALUE

[APP–56152] System error: unable to get the posting set of books id Please make sure the translator

program has been built successfully

[APP–56153] System error: unable to get the rule sequence id

[APP–56154] System error during insert of rule: &ERROR

[APP–56155] System error when validating unload: &ERROR

[APP–56156] System error when saving the category &EVENT_TYPE: &ERROR

[APP–56157] System error when trying to get the category name for &CATEGORY_NAME:

&ERROR

[APP–56158] System error when trying to get the category code for &CATEGORY_CODE:

&ERROR

[APP–56159] The following query chains are missing: &MISSING_QC

[APP–56160] System error when trying to get the saved category name for the event type

&EVENT_TYPE: &ERROR

[APP–56190] Invalid Concurrent Program.

Cause:

the setup has been defined through the Setup Subledger form.

Action:

please use the Setup Subledger form to update the setup.

[APP–56200] System error: Can’t submit tracer

[APP–56300] Merge Accounting cannot be run when failed events exist

Cause:

Previous transactions generated events that failed to be translated.

Action:

Run Posting Manager and analyze event translation errors.

[APP–56301] Merge Accounting cannot be run when merge is incomplete

Cause:

The merge among these third parties is not complete.

Action:

Merge completely the third parties and run this program again.

[APP–56302] Invalid third parties

Cause:

You entered third parties that have not been merged.

Action:

Enter third parties that have been merged.

Action:

Merge these third parties before running this program.

[APP–56350] Cannot find period info for Period : &PERIOD_NAME Application : &APPL_ID Set

of books: &SOB_ID

[APP–56351] The date &PDATE in not included in the period &START_DATE – &END_DATE

[APP–56352] The report has been submitted with an invalid parameter. REPORT_TYPE:

&REPORT_TYPE

[APP–56353] This report cannot be run for this application (&APPLID).

[APP–56400] Transfer to GL successfully completed

[APP–56401] System error: The profile option &PROFILE is not defined

[APP–56402] System error when selecting the source and category name: &ERROR

[APP–56403] System error when selecting the next sequence batch id: &ERROR

[APP–56404] System error when selecting the user source name: &ERROR

[APP–56405] System error when selecting the category name: &ERROR

[APP–56406] System error when selecting the conversion_type: &ERROR

[APP–56407] Invalid option. Please check for the available options for this program

[APP–56408] No data in subledger to transfer to GL

[APP–56409] System error in transfer to GL: &ERROR

[APP–56410] Failed to get the currency_code &ERROR

[APP–56411] System error: The mandatory variable is NULL: &VARIABLE

[APP–56412] System error: A failure occured during the insert in gl_interface: &ERROR

[APP–56413] System error: A failure occured when updating the source journal in ax_sle_lines:

&ERROR

[APP–56414] System error: A failure occured when updating the source journal in ax_sle_headers:

&ERROR

[APP–56450] A failure occurred when inserting into ax_balances. &ERROR

[APP–56451] A failure occured when deleting from ax_balances. &ERROR

[APP–56452] A failure occured when updating ax_balances. &ERROR

[APP–56453] Ax_calculate_balances unexpectantly failed. &ERROR &PROCEDURE

[APP–56454] Accounting Period: &PERIOD is not declared.

[APP–56455] System error: application id error (temporary message: do not translate)

[APP–56456] Set of Books: &SOB is not defined

[APP–56457] A PL/SQL table error: &ERROR occured in: &PROCEDURE

[APP–56458] Table ax_period_history has not been initialized for: &PERIOD.

[APP–56459] Table ax_period_history dosn’t have a period historical number: &PERIOD

[APP–56460] Table ax_period_history doesn’t have a closing status: &PERIOD

[APP–56461] System error: unexpected closing status (temporary message: do not translate)

[APP–56462] The profile option: &PROFILE is incorrectly set.

[APP–56463] Code combination id is missing for sle_header_id: &SHI (temporary message: do not

translate)

[APP–56464] Code combination id unidentified: &SHI &CCID (temporary message: do not

translate)

[APP–56465] System error: control_account_undefined (temporary message: do not translate)

[APP–56466] System error: no_control_account_sle (temporary message: do not translate)

[APP–56467] Program completed without error

[APP–56468] Invalid set of books. Action :

Please check set of books ID or set of books short name.

set of books ID : &SOBID

set of books name : &SOBSHORTNAME

[APP–56469] Invalid application. Action :

Please check application ID or application short name.

application ID : &APPLICATIONID

short name : &APPLSHORTNAME

[APP–56470] Invalid third party. Action :

Please check third party ID or name.

third party ID : &THIRDPARTYID

name : &THIRDPTYNAME

[APP–56471] Invalid third party sub identifier. Action :

Please check sub ID or sub name.

sub ID : &SUBID

sub name : &SUBNAME

[APP–56472] Invalid fiscal year. Action :

Please provide a valid year.

[APP–56473] Invalid control account. Action :

Please check the code combination ID or concatenated segment values.

code combination ID : &CCID

segment values : &CONCATSEQ

[APP–56474] Please provide only a debit or credit balance.

[APP–56475] Program error: No valid balance segment value found for code combination ID

&CCID Please contact your system administrator or support representative.

[APP–56476] Program error: No valid account segment value found for code combination ID

&CCID. Please contact your system administrator or support representative.

[APP–56477] Internal error: Invalid parameters.

[APP–56478] Only one initial period can be specified per application and set of books. A different

initial balance period exists for application ID: &APPLID and set of books ID: &SOBID.

Action:

Provide the same fiscal year as previous initial balances, or

change the period name of previous initial balances to this period name.

[APP–56479] Subledger transactions exist prior to the provided fiscal year for

application ID: &APPLID

set of books ID: &SOBID.

Action:

Create an initial balance in a fiscal year of the date

of the earliest transaction.

[APP–56480] One or more subledger lines are missing third party ID or sub ID for code

combination ID: &CCID in period &PERIODNAME.

[APP–56481] Balance synchronization completed without errors.

[APP–56482] The transaction balance cannot be created in a period prior to the initial balances for

application ID: &APPLID and set of books ID: &SOBID.

[APP–56500] No sequence is assigned for the category name &CATEGORY_NAME on

&EFFECTIVE_DATE

[APP–56501] Default category: could not find document number for event

[APP–56502] Rules error: &CALLING_PLACE: mandatory column &COLUMN is null

[APP–56503] Failed to get the category name for the category code &CATEGORY_CODE

[APP–56504] An error occured when fetching the table &TABLE_NAME (&TABLE_ALIAS):

&ERROR &WHERE_CLAUSE

[APP–56505] Failed to submit the AX Compiler

[APP–56506] You have not provided the required arguments for this program. Usage: AXSCMP

<Posting Set of Books ID> [<Trace Level>]

[APP–56507] Successfully completed.

[APP–56508] Invalid rules.

Cause:

Invalid or disabled event types or translation schemes exist

Action:

Please verify the status of event types and translation schemes.

[APP–56509] Please inform your system administrator or support representative that: obsolete rules

are present in the system; a more recent set of rules needs to be installed.

[APP–56510] No event types are defined for this translation program.

Action:

make sure that your translation program definition is complete.

[APP–56511] Program error: Unable to remove temporary files. Please contact your system

administrator.

[APP–56512] Program error: Generic parsing failure. Please contact your system administrator or

support representative.

[APP–56513] Program error: unable to open temporary file for writing. Please contact your system

administrator.

[APP–56514] Program error: cannot write to file. Possible cause: file system is full. Please contact

your system administrator.

[APP–56515] Program error: unable to open file for reading. Please contact your system

administrator.

[APP–56516] Program error: cannot read from file. Please contact your system administrator.

[APP–56517] Program error: out of memory. Please contact your system administrator.

[APP–56520] Program error: error generating database objects. Please contact your support

representative.

[APP–56600] The event table is locked. Please try later

[APP–56601] Internal error: The application_id &APPLICATION_ID is invalid.

[APP–56602] Illegal operation.

Cause:

you cannot change the vendor site of a posted invoice.

[APP–56700] An error occured when updating gl_period_statuses: &ERROR

[APP–56701] There is no currency &CURRENCY_CODE

[APP–56702] No value is defined for the profile option &PROFILE

[APP–56703] The profile option value for &PROFILE should be of type NUMBER

[APP–56704] Invalid Subledger: the current application, set of books is not a valid AX Subledger.

Cause:

incorrect setup

Action:

revise the profile options and the AX Setup.

[APP–56705] The status of the setup has been altered since submission.

Action:

please freeze the setup again.

[APP–56706] Compiler failure

Action:

Please review the Log and Report of request &REQUEST.

[APP–56707] Setup successfully frozen.

[APP–56708] At least one Subledger must be defined.

[APP–56709] The primary Posting Set of books is not defined for the following Subledger:

Application: &APPLICATION Main Set of Books: &MAIN_SOB

[APP–56710] The rule set is missing for the following Posting Set of Books: Application:

&APPLICATION Main Set of Books: &MAIN_SOB Posting Set of Books: &POST_SOB

[APP–56711] One or more Inventory Organization are not defined for the following Subledger:

Application: &APPLICATION Main Set of Books: &MAIN_SOB

[APP–56712] The definition of the Posting Sets of Books for the following Subledger is not

consistent with Multiple Reporting Currency setup: Application: &APPLICATION Main Set of

Books: &MAIN_SOB

[APP–56715] The following Primary Posting Set of Books is not used for all the Operating Units:

Application: &APPLICATION Main Set of Books: &MAIN_SOB Posting Set of Books:

&MAIN_SOB

[APP–56717] Invalid configuration. Encumbrance accounting is defined for Set of Books &SOB

having more that one Operating Unit.

[APP–56718] Invalid status. The status found is &STATUS_FOUND . It should be &STATUS_EXP

[APP–56719] Invalid configuration. Different rulesets are selected for the same MRC reporting set

of books Application &APPLICATION Reporting set of books &SOB

[APP–56720] Invalid configuration. The same posting set of books is involved in an MRC and a

non–MRC configuration Application &APPLICATION Reporting set of books &SOB

[APP–56721] Invalid configuration. The same set of books is used in at least two relationships and

has been selected as a primary set of books for one and a posting set of books for another one.

Application &APPLICATION Set of books &SOB

[APP–56722] Invalid configuration. A reporting set of books cannot be selected as a primary set of

books. Application &APPLICATION Set of books &SOB

[APP–56723] Invalid configuration. Different rulesets are selected for the same posting set of books

Application &APPLICATION Reporting set of books &SOB

[APP–56724] No translation program has been successfully created.

Action:

Please review the compiler logfiles.

[APP–56725] The setup is partially frozen.

Cause:

&TP_SUCCESS translation programs have been created

&TP_FAILURE translation programs have not been created.

Action:

Please review the compiler logfiles.

[APP–56726] The setup is incomplete.

Cause:

The translation scheme &TRANS_SCHEME has not been setup.

Action:

Please assign a valid category and re–submit the freeze.

[APP–56727] The setup submission has been cancelled.

[APP–56728] The freeze program is still running.

[APP–56800] Invalid parameters. The AX Posting manager has been submitted with invalid

parameters.

[APP–56801] Invalid parameters. An inconsistency has been detected in the AX posting parameters.

Please check.

[APP–56802] System error when initializing the Posting Manager process.

[APP–56803] An error occured when during the translation

[APP–56804] An error occured when starting during the AP Posting.

[APP–56805] Failed to submit AP Posting.

[APP–56806] Failed to submit GL Posting.

[APP–56807] Failed to submit EasyLink Posting.

[APP–56808] An error occured during the transfer to GL: &ERROR

[APP–56809] An error occured when executing the Easylink Filter: &ERROR

[APP–56810] The easylink job didn’t complete successfully.

[APP–56811] The GL posting didn’t complete successfully.

[APP–56812] An invalid mark value has been found.

[APP–56813] The job AX Posting Manager successfully completed.

[APP–56814] Failed to submit the Event Translation Job: &ERROR.

[APP–56815] Program error: Failed to submit Revenue Recognition program Please contact your

system administrator.

[APP–56816] Revenue Recognition failure

Action:

Please review the Log and Report of request &REQUEST.

[APP–56817] Unfrozen setup.

Cause:

the setup is not completed or has been unfrozen

Action:

please freeze AX setup and resubmit posting

[APP–56820] No data found in ax_sle_headers for journal_sequence_id : &JOURNAL_ID

sle_header_id : &HEADER_ID

[APP–56821] No application_column name found for the set of books &SOB_ID

[APP–56822] No data found in ax_sle_lines for journal_sequence_id : &JOURNAL_ID

sle_header_id : &HEADER_ID company: : &COMPANY

[APP–56823] Failed to insert the adjustement row: &ERROR

[APP–56824] Failed to get the intercompany flag for the set of books &SOB_ID

[APP–56825] The header is not properly adjusted for the current journal_sequence_id :

&JOURNAL_ID sle_header_id : &HEADER_ID

[APP–56826] No adjustment CCID has been defined for the following Company : &COMPANY Set

of books: &SOB_ID Application : &APPL_ID Cr Dr Code : &CR_DR_CODE

[APP–56830] An error occured when fetching the base query from &TABLE_NAME

(&TABLE_ALIAS): &ERROR &WHERE_CLAUSE

[APP–56831] An error occured when fetching from &TABLE_NAME (&TABLE_ALIAS):

&ERROR

[APP–56832] An error occured during event translation: &ERROR

[APP–56833] Failed to submit the AX Event Report

[APP–56834] The category associated with this event is DEFAULT. Automatic numbering should be

activated.

[APP–56835] Encumbrance error: &&DATE is not an open GL period (&STATUS)

[APP–56836] &&DATE is not in an open GL period

[APP–56837] Distribution plan &PLAN returned no accounting key flexfield ID.

Action:

Revise the definition of the plan in the translation scheme corresponding to this event type.

[APP–56838] An unexpected failure occured during the event translation Internal location failure:

&LOCATION &ERROR

[APP–56839] Unexpected error when calling the AX compiled packaged. &ERROR The

ax_posting_manager_pkg PL/SQL package may have to be re–validated.

[APP–56840] The AX compiled program &PGM_NAME has not been found Try to restart the

concurrent managers.

[APP–56841] Encumbrances are ON and some events are in failure.

[APP–56842] No period defined for this event: Set of books :

&SOB_ID Effective date :

&DATE

[APP–56843] Event date and accounting date do not match.

[APP–56844] Distribution plan &PLAN returns inconsistent rows. Possible cause:

rows returned by this plan must have common elements. Please contact your support representative.

[APP–56845] No open period found in General Ledger. Set of books:

&SOB Effective date:

&DATE

Action: open a General Ledger period including or later than the effective date for this set of

books.

[APP–56846] Program error: Oracle Payables and Global Accounting Engine are not transferring

consistent data. Please contact your support representative.

[APP–56900] This will commit all pending changes and create this Translator Program. Continue?

[APP–56901] You cannot create duplicate records here.

[APP–56902] Concurrent request &REQUEST_NUMBER submitted to perform this task.

[APP–56903] This date is not in an open period. Please enter an effective date from an open period.

[APP–56904] You cannot change a completed journal entry after it is saved. Do you want to

continue?

[APP–56905] This journal entry cannot be completed as it has no lines. The pending changes have

not been commited.

[APP–56906] The total of the entered credits must equal the total of the entered debits. Modify the

lines so that this journal entry is balanced.

[APP–56907] A line must have either a debit or a credit value.

[APP–56908] Warning: duplicates of accounting flexfield and third party found. Line &LINE_NUM

is one of the duplicated rows.

[APP–56909] Due to currency translation rounding, the total of the accounted credits and debits are

not equal. To rectify this, the accounted credit value of line &LINE_NUM was increased by

&AMOUNT.

[APP–56910] Due to currency translation rounding, the total of the accounted credits and debits are

not equal. To rectify this, the accounted credit value of line &LINE_NUM was decreased by

&AMOUNT.

[APP–56911] Due to currency translation rounding, the total of the accounted credits and debits are

not equal. To rectify this, the accounted debit value of line &LINE_NUM was increased by

&AMOUNT.

[APP–56912] Due to currency translation rounding, the total of the accounted credits and debits are

not equal. To rectify this, the accounted debit value of line &LINE_NUM was decreased by

&AMOUNT.

[APP–56913] Posting Manager program submitted.

[APP–56914] This action will prevent posting transacations. Do you want to continue?

[APP–56915] The Freeze AX Setup concurrent program could be running and locking the setup. Do

you want to continue?

[APP–56916] There is no drilldown available for the event type &EVENT_TYPE

[APP–56917] This value ( &REFERENCE ) exceeds the maximum number of columns involved in

a primary key

[APP–56918] This accounting line has been translated with an obsolete accounting rule. There is no

drill down available.

[APP–56919] The value for the transaction id ( &REFERENCE ) is NULL

[APP–56920] Please query some accounting lines before drill down

[APP–56921] No value is retrieved for profile option &PROFILE. Please ensure it is set properly for

the responsibility.

[APP–56922] No conversion rate has been defined for the given currency, conversion date, and

conversion type.

[APP–56923] You cannot create more than one line with the same line number.

Action:

Please enter a unique line number.

[APP–56924] You cannot change categories when the setup is frozen. The setup can be unfrozen

using the Setup Window.

[APP–58000] The organization is not project enabled. Locator cannot have project references.

[APP–58001] The project and task references are invalid for the given locator. The control level for

the organization is ”Task”. Both project and task must be specified.

[APP–58002] The project references specified in the transaction (&TXN_PRJ_REF) do not match

the project references for the locator (&LOC_PRJ_REF).

[APP–58003] Project references must be entered for the given locator.

Cause: Possible Reasons: 1. If control level for the organization is ”Project”, project must be

entered for the locator. 2. If control level for the organization is ”Task”, project and task must be

entered for the locator.

[APP–58004] Project references are not allowed for the locator for this transaction.

Cause:

The transaction does not have project references.

Action:

Remove the project references in the locator.

[APP–58005] Task AutoAssignment rule not found

[APP–58006] Cannot create this locator since the corresponding physical locator is already defined

for another subinventory (&SUBINV).

[APP–58007] The locator is not valid for this transaction.

Cause:

The project specified in the transaction (&TXN_PRJ_REF) and the project specified in the locator

(&LOC_PRJ_REF) reference different planning groups.

[APP–58008] The locator is not valid for this transaction.

Cause:

The project specified in the transaction (&TXN_PRJ_REF) and the project specified in the locator

(&LOC_PRJ_REF) reference different cost groups.

[APP–58500] A project with this name already exists. Please select another.

[APP–58501] A project with this number already exists. Please select another.

[APP–58502] Please enter a seiban number and seiban name before navigating to the parameters

form

[APP–58503] &SEGMENT of the Stock Locator flexfield is already in use. Project Manufacturing

features require &SEGMENT of this segment.

Action:

Please contact your Oracle Support representative.

[APP–58504] You cannot access this form

Cause: This Organization is not Project Enabled

Action: Choose a Project Enabled Organization

[APP–58505] Cost Group cannot be updated for project &project_number.

Cause:

Transactions have already been recorded against this project.

[APP–60001] The Oracle Receiveables concurrent request for contra charging failed. As a result, a

transaction may exist in the Oracle Payables interface tables for supplier &SUPPLIER at site

&SITE for an amount of &AMOUNT. Please go into the Payables interface form and remove this

record.

[APP–60002] The Customer and Supplier selected do not have the same name.

[APP–60003] The Customer and Supplier Sites selected do not have the same VAT Registration ID.

[APP–60004] The Customer and Supplier selected do not have the same Tax Identifier.

[APP–60005] Contra charging is not possible if the supplier or customer balance is zero.

[APP–60007] You may not delete EFT Media that contain payment batches.

[APP–60008] Please enter a breakdown for your breakdown amounts.

[APP–60009] Only one Segment Name may be active at any time. If you wish to change which

segment you are using set the inactive date to today or less and save changes. You will then be able

to create records for a different Segment Name.

[APP–60009] There is no batch source for the interest invoice process. As a result you will not be

able to submit a batch transfer. Check the interest invoice setup.

[APP–60010] Duplicate VAT Number – This VAT number already exists for a reporter.

[APP–60011] For Receipt Acknowledgment reprinting, only Receipt Acknowledgment Numbers

From and To must be entered.

[APP–60012] You are not permitted to update the Receipt Acknowledgement Global Flexfields.

Your changes to the Global Flexfield have been discarded.

[APP–60013] Vendor Site EFT Information not complete for Vendor &vendor_name

[APP–60014] For Receipt Acknowledgment creation, Receipt Acknowledgment Numbers From and

To must be NULL.

[APP–60110] Please enter an Effective From date that is the same as or later than the current date.

[APP–60111] Please enter an Effective To date that is the same as or later than the Effective From

date.

[APP–60112] Please ensure that both the Effective From and Effective To dates are in the same

calendar year.

[APP–60113] Please enter an Effective From date that does not overlap with an existing exemption

letter range.

[APP–60114] Please enter an Effective To date that does not overlap with an existing exemption

letter date range.

[APP–60115] Please change the date range so that it does not overlap with any existing date ranges.

[APP–60116] When entering a new exemption letter, ensure that the Print flag is set to Yes.

[APP–60117] When entering a new exemption letter, ensure that the Issue flag is set to Yes.

[APP–60118] The Issue flag can only be set to Yes when the Print flag is also Yes.

[APP–60119] Save or clear this newly created row before moving to another record.

[APP–60120] Please enter at least a vendor name and vendor number before continuing.

[APP–60121] Function not currently available

Cause: You pressed a function key that is not currentlyavailable.

[APP–60122] Enter a book name before continuing.

[APP–60123] The territory code for the record that you entered already exists. Query the record

with the territory code. If the details are incorrect, you can delete the record and re–enter it.

[APP–60126] Payment amount does not match declaration total. Cause : The total of the declaration

line amounts do notequal the payment amount which you are declaring.Action : Amend the

decalaration record amounts to enable the total of these amounts to equal the payment amount.

[APP–60127] The bank account of this payment run has no default EFT parameters assigned to it.

Use the Create EFT Parameters window to set up default parameters for the bank account.

[APP–60128] No payment records will be returned. Cause : The selection criteria which you have

entered in this zone will not return any payment records in the nextzone. Action : Either change the

selection criteria in this zone,i.e. reduce the declaration limit, or select anotherpayment run for

declaration.

[APP–60129] Enter an unplanned depreciation amount that is not greater than the net book value of

the asset.

[APP–60130] Please enter a valid Unplanned Depreciation Amount. The Unplanned Depreciation

Amount must not increase thevalue of the Asset to greater than its Current Cost.

[APP–60140] Save the tax record.

[APP–60141] New Records cannot be created in zoom.

[APP–60142] The end date cannot be earlier than the start date

[APP–60143] A declaration has already been made for this period

[APP–60144] Standard Localization Error Standard Localization Error

[APP–60145] A start date must &date_msg

[APP–60146] No VAT transaction type exists. Enter a VAT transaction type.

[APP–60147] Undefined period

[APP–60148] This declaration was &status. No other action is allowed.

[APP–60149] &message_type: &message_text (&module_id at position &pos)

[APP–60150] Cannot find a VAT Rule

[APP–60151] Warning:&prog Pos : &pos Values : &val

[APP–60152] This VAT number is invalid, check the ’format’ and ’check digit’ formula The VAT

number format is BE999999988BE –country code9999999 –official vat registration number88

–check digitThe formula for the calculating the check digit is asfollows:The VAT registration

number must be 7 digits long. Thecheck digit is the remainder of dividing the VATregistration

number by 97. The check must be 2 digitslong. ie 2 will be 02. If the remainder is 0 then it willbe

97.

[APP–60153] Save your current movement, or use Edit and then Clear Record to erase changes to

this movement.

[APP–60154] You must select an action before you can save your work.

[APP–60155] This VAT number already exists for a reporter.

[APP–60156] Duplication – This set of books has already been assigned to a reporter There can be

only one reporter with this set of books.Please amend the other reporter or select another set

ofbooks.

[APP–60157] Cannot create an allocation

[APP–60158] Non existent, inactive or disabled &attribute on &object (&value &PK)

[APP–60159] Missing &attribute on &object (&PK)

[APP–60160] Multiple tax lines are not allowed

[APP–60161] Correct format for the bank account number : 999–9999999–99

[APP–60162] Bank account failed modulus 97 control

[APP–60163] This is a valid, unposted transaction

[APP–60164] The &field1 should be &sign1 The &field1 should be &sign1 to match the sign of

theinvoice value

[APP–60165] For this movement type, the value of &field must be &sign because the sign on the

weight, additional unit of measure, and statistical value must match.

[APP–60166] Tax Reg. Number must begin with a VAT Member State Code

[APP–60167] Your bank account has an invalid payment method. For foreign payments, you can

enter a payment method code (for example, CHC) in the Bank Account Number field. Ensure that

the payment method code is entered correctly and that your payment codes were set up in the

Belgian Localizations application.

[APP–60168] Missing Financial Institution Code for your Belgian Bank

[APP–60169] Missing or Invalid Foreign Cost Center Code for your Belgian Bank

[APP–60170] Missing Bank Identification for this Bank Account

[APP–60171] Payment Currency must be BEF for this Belgian Pay Group

[APP–60172] A &object with this &characteristics already exists for this period

[APP–60173] A &object with this &characteristics already exists

[APP–60174] A &object with this &characteristics already exists

[APP–62000] Error while searching for book related information.

[APP–62001] Currency details not defined for given book type code.

[APP–62002] Price index value not defined for this period.

[APP–62003] Depreciation period details not defined for given book type code and for current

financial year.

[APP–62004] Depreciation period not open for this depreciation book.

[APP–62005] Start and/or end dates are not defined for current fiscal year.

[APP–62006] Price index not defined for given book type code and current asset category.

[APP–62007] Price index value not defined for current price index and current acquisition date.

[APP–62008] Price index value not defined for current price index and current half period date.

[APP–62009] Only one asset group can be checked.

[APP–62010] Error while selecting previous depreciation period. Periods might not be defined

sequentially.

[APP–62011] Adjusted cost for previous period is not available.

[APP–62012] Price index value not defined for previous period.

[APP–62013] Depreciation period details not defined for given book type code and for previous

financial year.

[APP–62014] Cannot find the balancing segment for this AFF structure.

[APP–62015] Book details not defined for given set of books id.

[APP–62016] Additional information not available for the specified set of books.

[APP–62017] Currency details not defined for given set of books id.

[APP–62018] Cannot retrieve the inflation adjustment gain and loss account for the specified set of

books.

[APP–62019] Cannot get or define the inflation adjustment gain and loss account for the current

balancing segment.

[APP–62020] Model already exists with this name.

[APP–62021] Invalid Option : Model is not selected.

[APP–62022] Period details not defined for given set of books id and for current chart of accounts

id.

[APP–62023] Price index value not available.

[APP–62024] This fiscal classification code–tax category association is still active.

[APP–62025] This combination of ship–from, ship–to and fiscal classification code–tax exists and is

active.

[APP–62026] This combination of ship–from location, ship–to location, item and tax category exists

and is active.

[APP–62027] This Tax Category already exists.

[APP–62028] This Tax Group exists and is active.

[APP–62029] This tax category for the same ship–from and ship–to location is still active.

[APP–62030] &ENTITY Already Exists.

[APP–62031] Amount cannot be entered when Percent Distribution Exists.

[APP–62032] Profile JLBR Interest Debit Memo Batch Source cannot be null.

[APP–62033] Amount fields will be cleared. Continue?.

[APP–62034] Percentage fields will be cleared. Continue?.

[APP–62035] Concurrent Program has not finished yet.

[APP–62036] Name already exists.

[APP–62037] You have included this Bank Account Number more than once for creating

Occurrence Remittance Batch.

[APP–62038] You have already selected all the Bank Accounts of this Bank/Branch for creating

Occurrence Remittance Batch.

[APP–62039] An existing record with the same File control has a different Generation date,

Processing date or Bank Number.

[APP–62040] You can define only one Bank Instruction Code for this Instruction Type.

[APP–62041] Invalid Bank Instructions Combination.

[APP–62042] Company Code for the Bank Account of the Collection Document is different than the

Company Code you have entered.

[APP–62043] Final Customer Number is less than Initial Customer Number.

[APP–62044] Max. Document Amount is less than Min. Document Amount.

[APP–62045] Min. Document Amount is more than Max. Document Amount.

[APP–62046] Min. Document Amount is more than Min. Remittance Amount.

[APP–62047] Final Due Date is less than Initial Due Date !.

[APP–62048] Invalid GL Date.

[APP–62049] Max. Remittance Amount is less than Min. Remittance Amount.

[APP–62050] Min. Remittance Amount is more than Max. Remittance Amount.

[APP–62051] Min. Remittance Amount is less than Min. Document Amount.

[APP–62052] Final Transaction Amount is less than Initial Transaction Amount.

[APP–62053] Final Transaction Date is less than Initial Transaction Date !.

[APP–62054] Final Transaction Number is less than Initial Transaction Number.

[APP–62055] You can not enter an occurrence of type Call–Off Protest for selected Collection

Document.

[APP–62056] You can not enter new occurrences for selected Collection Document.

[APP–62057] Output format is not specified for this Bank Transfer Batch.

[APP–62058] You can define only one Bank Occurrence Code for a Standard Occurrence Code.

[APP–62059] Percentages Total should be 100.

[APP–62060] Percentages Total Exceeded 100.

[APP–62061] Percent Distribution cannot be entered when Amounts Exist.

[APP–62062] Either Percentage Field OR one of the Amounts is Required.

[APP–62063] Payment Method ID and Bank Account ID exist.

[APP–62064] Profile JLBR Interest Debit Receipt Method cannot be null.

[APP–62065] Remittance Code should be 2 in Bank Returns.

[APP–62066] Please choose media as FIle/Report for Remittance Occurrence.

[APP–62067] Trade Note already exists.

[APP–62068] Profile JLBR Interest Debit Memo Transaction Type cannot be null.

[APP–62069] Starting Collection Document and Trade Note Association ...

[APP–62070] Profile JLBR Calendar Name cannot be null.

[APP–62071] The consolidated invoice cannot be cancelled. There is a payment for its shipping

invoice.

[APP–62072] The consolidated invoice cannot be cancelled. You should unmatch its invoices first.

[APP–62073] You cannot match a cancelled consolidated invoice.

[APP–62074] You cannot modify this field because a Printed &ENTITY Report already exists.

[APP–62075] Operation Fiscal Code required when ICMS Amount is not null.

[APP–62076] Inscription number for CGC or CPF must be entered.

[APP–62077] Inscription digit for CGC or CPF must be entered.

[APP–62078] Invalid CGC or CPF inscription. Please re–enter.

[APP–62079] Inscription branch for CGC must be entered.

[APP–62080] The current date was anticipated and/or postponed.

[APP–62081] Profile JLBR Automatically Change Date cannot be null.

[APP–62082] Inactive Date must be equal or greater than today’s Date.

[APP–62083] CNAB code already exists for another currency. Re–enter.

[APP–62084] Collection Document and Trade Note associated.

[APP–62085] Collection Document and Trade Note Disassociated.

[APP–62086] Collection Document or Trade Note not associated.

[APP–62087] Consolidated Invoice Number is a Display Only item. Replacing with database value.

[APP–62088] Date cannot be greater than consolidated invoice date.

[APP–62089] Duplicated Message Link is not allowed.

[APP–62090] You must enter Tax Planned Margin when Tributary Substitution is checked.

[APP–62091] You must enter Tax Recoverable Rate for checked Taxes.

[APP–62092] Entry not Valid.

[APP–62093] &ENTITY1 must be equal or greater than &ENTITY2.

[APP–62094] Inconsistent Date, out of Calendar interval.

[APP–62095] Interest Formula must be entered.

[APP–62096] Interest Grace Days must be entered.

[APP–62097] Interest Period must be entered.

[APP–62098] Interest Rate/Amount must be entered. Rate must be between 0 and 100.

[APP–62099] Interest Type must be entered.

[APP–62100] Enter a valid Director Number, the current Director Number will be cleared.

[APP–62101] Invalid End Date, it cannot be less than Start Date.

[APP–62102] Invalid Grace Days.

[APP–62103] Enter a Valid Inscription Number for the selected Inscription Type. the current

Inscription number will be cleared.

[APP–62104] Invalid Interest Amount .

[APP–62105] Invalid Interest Period.

[APP–62106] Invalid Interest Type.

[APP–62107] Invalid Penalty Amount.

[APP–62108] Invalid Penalty Rate.

[APP–62109] Attribute disabled. Use the Global Descriptive Flexfield to enter tax information for

the item.

[APP–62110] The Tax Location Flexfield Classification is required for the Latin Tax Method. Be

sure you are selecting a classification that exists in the Location Flexfield Structure.

[APP–62111] The Location Flexfield Structure is not populated. Please select a structure you want

the Latin Tax method to consider with at least one segment equal to the Tax Location Flexfield

Classification.

[APP–62112] The combination of Lookup Type amd Lookup Code already exists.

[APP–62113] Field must be entered.

[APP–62114] This date is a non–workday date. Would you like to change it?.

[APP–62115] You cannot delete a consolidated invoice. You can perform its cancellation.

[APP–62116] You cannot update this field since Recalculation of Payment Schedules is not allowed

because you have associated them with a Collection Document.

[APP–62117] Interest Formula should be Null when Interest Type is Null.

[APP–62118] Interest Period should be Null when Interest Type is Null.

[APP–62119] Interest Rate/Amount should be Null when Interest Type is Null.

[APP–62120] Interest Grace Days should be Null when Interest Type is Null.

[APP–62121] Penalty Rate/Amount should be Null when Penalty Type is Null.

[APP–62122] The Start date or End date cannot fall within an existing range.

[APP–62123] Profile JLBR Payment Action cannot be null.

[APP–62124] Profile JLBR Payment Location cannot be null.

[APP–62125] Penalty Rate/Amount must be entered. Rate must be between 0 and 100.

[APP–62126] Penalty Type must be entered.

[APP–62127] End Date cannot fall in a existent Period.

[APP–62128] Start Date cannot fall in an existent Period.

[APP–62129] You cannot modify any tax information that has been automatically generated.

[APP–62130] You cannot modify the Fiscal Classification Code for Inventory Items.

[APP–62131] You cannot modify the PO total plus IPI tax amount.

[APP–62132] Exempt Reason will be cleared. Continue?

[APP–62133] ICMS Non–Incidence and ICMS Tax Name will be cleared. Continue?

[APP–62134] ICMS Exempt and ICMS Tax Name will be cleared. Continue?

[APP–62135] ICMS Exempt and ICMS Non–Incidence will be cleared. Continue?

[APP–62136] ICMS Recoverable Rate will be cleared. Continue?

[APP–62137] ICMS Rate Reduced Base will be cleared. Continue?

[APP–62138] IPI Exempt will be cleared. Continue?

[APP–62139] IPI Recoverable Rate will be cleared. Continue?

[APP–62140] IPI Rate Reduced Base will be cleared. Continue?

[APP–62141] IPI Tax Name will be cleared. Continue?

[APP–62142] Tax Name Planned Margin will be cleared. Continue?

[APP–62143] To see the latest tax information you need to save the changes first. Do you want to

save the changes you have made ?

[APP–62144] Reason for the exempted ICMS tax not entered. Continue?

[APP–62145] Reason for the exempted IPI tax not entered. Continue?

[APP–62146] Fiscal Classification Code already exists.

[APP–62147] The combination of Establishment Type, Contributor Type and Transaction Nature

already exists.

[APP–62148] The combination of Ship–From state, Ship–To state and Fiscal Classification Code

already exists.

[APP–62149] The combination of Ship–From state, Ship–To state and Item already exists.

[APP–62150] The combination of Ship–From state and Ship–To state already exists.

[APP–62151] Enter a two–character state.

[APP–62152] This Tax Rule already exists.

[APP–62153] Tax Location Segment Qualifier could not be populated. Check Locations Structure.

[APP–62154] Summary of shipping invoices amount must be equal to consolidated invoice amount.

[APP–62155] Tax code is required whenever using Latin Tax Method. Please enter a tax code.

[APP–62156] Do you want to override the shipping invoices Pay Group with the Pay Group

&PAYGROUP from the consolidated invoice ?

[APP–62157] Withholding Due Date is less than Period Date.

[APP–62158] Amount Applied cannot be different from Main Amount Segment plus Received

Interest Segment.

[APP–62159] You should enter the Interest Difference Action Segment when there is difference

between the Calculated and Received Interest.

[APP–62160] Write Off Reason Segment should be entered when interest is written off.

[APP–62161] Interest Amount must be greater than or equal to Zero.

[APP–62162] Main Amount must be greater than zero.

[APP–62163] This is an overdue invoice. Interest needs to be computed. Please, open the global

flexfield for Interest Calculation.

[APP–62164] Period Balance must be Re–calculated.

[APP–62165] An identical association of the current Tax Rule, Fiscal Classification and Exception

already exists.

[APP–62166] An identical association of the current Tax Rule, Ship–From and Ship–To Locations,

Fiscal Classification and Exception already exists.

[APP–62167] An identical association of the current Tax Rule, Ship–From and Ship–To Locations,

Inventory Item and Exception already exists.

[APP–62168] An identical association of the current Tax Rule, Ship–From and Ship–To Locations,

and Exceptions already exists.

[APP–62169] An identical association of the current Tax Rule, Inventory Item and Exception

already exists.

[APP–62170] An identical association of the current Tax Rule, Customer and Exception already

exists.

[APP–62171] An identical assocaition of the current Tax Rule, Organization and Exception already

exists.

[APP–62172] An identical association of the current Tax Rule, Memo Line and Exception already

exists.

[APP–62173] An identical association of the current Tax Rule, Ship–To / Bill To Location and

Exception already exists.

[APP–62174] If you check Tributary Substitution, you need to enter a Tax Category to Compound

Base. This tax category will be used to compound the base amount for tax calculation.

[APP–62175] Manual Receipt can only be updated to Registry.

[APP–62176] Registry can only be updated to Legal Department

[APP–62177] You cannot update this Bearer note or Trade note.

[APP–62178] Sum of Main Amount and Received Interest cannot exceed UnApplied Amount.

[APP–62179] The inflation adjustment process was already executed for the current period.

[APP–62180] You must perform inflation adjustment for this period before closing it.

[APP–62181] Please, enter value for the required segment in the descriptive flexfield.

[APP–62182] You cannot update this value.

[APP–62183] Shipping Date should be after or same as Issue date. Do you want to overwrite

Shipping date with Issue Date?

[APP–62184] You cannot update Status to Void.

[APP–62185] You must supply a Fiscal Classification Code for transaction line.

[APP–62186] Invalid Fiscal Classification Code for transaction line.

[APP–62187] You must supply a Transaction Nature for transaction line.

[APP–62188] Invalid Transaction Nature for transaction line.

[APP–62189] Tax Base Amount for transaction line must be a numeric value.

[APP–62190] Tax Base Rate for transaction line must be a numeric value.

[APP–62191] The valid Interest Types are: ’A’ (for amount) and ’R’ (for rate).

[APP–62192] The Interest Rate must be a numeric value between 0 and 100.

[APP–62193] The Interest Amount must be a numeric positive value.

[APP–62194] The Interest Period of days must be a numeric positive value.

[APP–62195] The valid Interest Formulas are: ’C’ (for compound) and ’S’ (for simple).

[APP–62196] The Grace Days must be a numeric positive value.

[APP–62197] The valid Penalty Types are: ’A’ (for amount) and ’R’ (for rate).

[APP–62198] The Penalty Rate must be a numeric value between 0 and 100.

[APP–62199] The Penalty Amount must be a numeric positive value.

[APP–62200] Freight Accessory Expense for transaction must be a numeric value.

[APP–62201] Insurance Accessory Expense for transaction must be a numeric value.

[APP–62202] Other Accessory Expense for transaction must be a numeric value.

[APP–62203] Volume Quantity for transaction must be a numeric value.

[APP–62204] Volume Number for transaction must be a numeric value.

[APP–62205] Total Gross Weight for transaction must be a numeric value.

[APP–62206] Total Net Weight for transaction must be a numeric value.

[APP–62207] You must supply a Operation Fiscal Code for transaction line.

[APP–62208] Invalid Operation Fiscal Code for transaction line.

[APP–62209] You must supply an Item Origin for transaction line if you have defined an item or a

memo line.

[APP–62210] Invalid Item Origin for transaction line.

[APP–62211] You must supply an Item Fiscal Type for transaction line if you have defined an item

or a memo line.

[APP–62212] Invalid Item Fiscal Type for transaction line.

[APP–62213] You must supply a Federal Tributary Situation for transaction line if you have defined

an item or a memo line.

[APP–62214] Invalid Federal Tributary Situation for transaction line.

[APP–62215] You must supply a State Tributary Situation for transaction line if you have defined an

item or a memo line.

[APP–62216] Invalid State Tributary Situation for transaction line.

[APP–62217] Historical journal entries have been already created for this period.

[APP–62218] Operation Fiscal Code already exists.

[APP–62219] Calendar Name already exists.

[APP–62220] Inactive Date will be cleared. Continue?

[APP–62221] Due Date must be equal or greater than Document Date.

[APP–62222] Discount Date must be equal or greater than Document Date.

[APP–62223] Penalty Fee Date must be equal or greater than Document Date.

[APP–62224] Arrears Date must be equal or greater than Document Date.

[APP–62225] Do you want to override the shipping invoices Pay Group with the Pay Group from

the consolidated invoice?

[APP–62226] Trade Note Amount does not match with Invoice. Do you want to correct it with the

Invoice Amount?

[APP–62227] This rule is associated to a legal message: you cannot delete it.

[APP–62228] Invalid Fiscal Classification Code for the sales order line.

[APP–62229] You must supply a Fiscal Classification Code for the sales order line.

[APP–62230] You can not reverse a Bank Transfer Remittance Batch with selected status.

[APP–62231] Concurrent program completed with error. You may want to re–query to refresh Bank

Transfer Remittance Batches Status values.

[APP–62232] Void/Reverse could not complete. You may want to re–query to refresh Bank Transfer

Remittance Batches Status values.

[APP–62233] Invalid Branch and/or Account Number for the specified Due Date range.

[APP–62234] You cannot update Status of this Void Invoice.

[APP–62235] You must print all invoices before changing the Printing Invoice Immediately flag to

Yes.

[APP–62236] Occurrence Remittance Batch is not created for the specified Due Date range. No

Occurrence exists in this Due Date range.

[APP–62237] Factoring date is greater than the due date

[APP–62238] Concurrent program did not successfully finish

[APP–62239] Credit amount cannot be a negative value

[APP–62240] You cannot enter protest occurrence for a protested collection document

[APP–62241] You are at the last remittance batch. Do you want to create a new remittance batch?

[APP–62242] The inflation journal entry source is not defined

[APP–62243] The adjustment journal entry category is not defined

[APP–62244] You cannot work on this record because it is currently being used by another user.

Please try again later.

[APP–62245] You can not delete this code if it is in use

[APP–62246] You must enter information into the Base Rate and/or Tax Code fields. You cannot

leave both of these fields blank.

[APP–62247] You can only apply IPI Tax Recovery if the IPI Tax Apply check box is checked.

Continue?

[APP–62248] The IPI Tax Recoverable and Recoverable Rate will be cleared. Continue?

[APP–62249] Could not get the currecy precision. Review the currency definition.

[APP–62250] You cannot update Tax Inclusive field when this tax category is in use

[APP–62251] Record cannot be deleted. This consolidated invoice is already canceled or at least

one shipping invoice is associated with this consolidated invoice

[APP–66000] This record is not user maintainable.

[APP–66001] A record already exists for this &FIELD_PROPERTY range.

[APP–66100] Quantity on hand: &QOH ATP: &ATP

[APP–66101] Backorder Exists For This Item/Deliver–To Location. Would you like to continue?

[APP–66102] Please fill in the End Date before create a new certificate.

[APP–66103] This is not a valid certificate number.

[APP–66104] The amount entered for allocation cannot exceed the amount available for allocation.

[APP–66105] Unable to obtain BAL_CHG_SOURCE_ID Sequence Number for this allocation.

[APP–66106] Unable to update Balancing Charge Source record.

[APP–66107] Unable to create a new FA_BOOKS record.

[APP–66108] Retired since it must be between the current date and the default date.

[APP–66109] Unable to obtain details for this asset.

[APP–66110] Call to Assets Expense Code failed.

[APP–66111] Unable to initialize Flex structures.

[APP–66112] Please select an asset before continuing.

[APP–66113] Unable to obtain the last open date for the current book.

[APP–66114] Unable to obtain transaction header date for this allocation.

[APP–66115] Unable to create a new transaction header record.

[APP–66116] Unable to obtain transaction header id for this allocation.

[APP–66117] Print Australia Reports

[APP–66118] You cannot clear this record.

[APP–66119] No more records for this type.

[APP–66120] Please enter either a table name or a constant for this segment.

[APP–66200] This book has been used. If this record is changed, there may cause problem with the

issued Uniform Invoices assigned the numbers in this book.

[APP–66201] Print Unified Invoice/Sales Receipt

[APP–66202] This number is not valid based on the current combination of date and format.

[APP–66203] Cannot find a matching Unified Invoice Number based on this combination of Format

and Date.

[APP–66204] Print Taiwan Reports

[APP–66300] Print Korea Reports

[APP–66400] Print Thailand Reports

[APP–66500] Print China Reports

[APP–66600] No Tax Parameter information found. Please define your Tax Parameters.

[APP–66601] Your invoice contains two or more different group taxes. You may only have one

group tax per invoice.

[APP–66602] Group tax rate does not equal to sum of distribution tax rates.

[APP–66603] Cannot find invoice information.

[APP–66604] No tax distributions found for &MTD_TAX_NAME tax.

[APP–66605] No Tax Credit Name defined for the segment value you entered. You can either

supply a Tax Credit Name or assign a Tax Credit Name in the Define Tax Credit Segment Ranges

form.

[APP–66606] Each Base Tax Rule with the Rebate flag checked, requires a pair of credit and debit

taxes.

[APP–66607] No rebate information found for Tax Credit Name: &TAX_CREDIT_NAME. Please

make sure that the Tax Credit Name has rebate information defined.

[APP–66608] Changing this field may cause an inconsistency in data. Would you like to proceed

anyway?

[APP–66609] The sum of the distribution tax rate is not equal to the group tax rate. Would you like

to proceed anyway?

[APP–66610] The sum of distribution tax rate cannot exceed the group tax rate.

[APP–66611] A Base Tax Rule with the Rebate flag checked, does not have a pair of credit and

debit taxes. Would you like to proceed anyway?

[APP–66612] &TAX_NAME tax has an inactive date in the Define Tax Names form.

[APP–66613] Please delete credit and debit taxes for this &TAX_NAME tax before updating.

[APP–66614] Cannot use past date.

[APP–66615] An invoice exists with an invoice date that is in this date range.

[APP–66616] Warning: Ineffective date is not the same as the inactive date of this tax in the Define

Tax Names form. Would you like to proceed anyway?

[APP–66617] Your General Ledger set of books does not match the Payables set of books.

[APP–66700] A company with this name already exists.

[APP–66701] Print Singapore Reports.

[APP–68000] Submitted request &request to create balances from &period1 to &period2. You have

closed one or more accounting periods.Customer/Vendor balances for the period(s) which youclosed

will now be calculated.

[APP–68001] The start and end date must belong to the same calendar year.

[APP–68002] Date range may not include an existing range for this supplier within its scope.

[APP–68003] Effective date may not fall within an existing effective date range for this supplier.

[APP–68004] Please save or clear changes before continuing.

[APP–68005] Please enter a VAT Country Code in the Define Financials Options form

[APP–68006] View EFT Details.

[APP–68007] You cannot delete a transferred interest invoice batch.

[APP–68008] You cannot submit the batch transfer request because no batch source exists for

interest invoice. Check your interest invoice setup.

[APP–68010] You may only delete overdue invoices or late payments.

[APP–68011] You may not save unless the balance is zero and the credit and debit totals are not

zero.

[APP–68012] Sequence JG_ZZ_RECON_ID_S does not exist. The sequence JG_ZZ_RECON_ID_S

does not exist and is required by this form. Please contact your System Administrator.

[APP–68013] You cannot delete this record because the batch has been transferred to Oracle

Receivables.

[APP–68014] You cannot save this batch because it was not transferred to Oracle Receivables. Press

the Generate Invoices button on this window and then run Autoinvoice.

[APP–68015] Line transaction flexfield is not set up correctly for interest invoice.

[APP–68016] Exchange Rate is null for customer &customer_name

[APP–68017] Enabled date ranges must be continuous for code &CODE.

[APP–68018] Code &CODE must have one and only one enabled Rate with a null End Date.

[APP–68019] Enabled date ranges should not overlap for code &CODE.

[APP–68020] You cannot use System Formats screen when no VAT Member country is defined.

[APP–68021] In the VAT Registers the start date must chronologically precede, or be the same as,

the end date.

[APP–68022] Submitted request &request to delete balances from &period You have re–opened a

closed accounting period. Any customer/vendor balances for this period and any following periods

will be deleted.

[APP–68023] The amount type must be Functional or Foreign.

[APP–68024] Select records for reconciliation so that the sum of the debits is equal to the sum of

the credits.

[APP–68025] Please enter a valid ID.

[APP–68026] You may not enter details here because additional EFT information is not required at

this level for EFT payment formats supported for your country. Your country is defined by the VAT

Member State Code you select in Financial Options form of Oracle Payables.

[APP–68027] Enter a Currency Code and Currency Type.

[APP–68028] Interest Invoice Transaction Type is not set up correctly.

[APP–68029] Interest Invoice Batch Source is not set up correctly.

[APP–68030] Interest Invoice Memo Line is not set up correctly.

[APP–68031] You cannot change the Number of Days for this line because either the batch was

transferred to Oracle Receivables or the line has a line type of Fee.

[APP–68032] Your interest invoice information has now been transferred to AutoInvoice. To create

your interest invoices in Oracle Receivables run AutoInvoice from the Standard Reports Submission

window.

[APP–68033] Please enter at least one Reversal field

[APP–68034] Transactions have been reconciled with Reconciliation ID &RECON_ID

[APP–68035] It is advisable to restrict the Accounts for Reconciliation to increase Performance.

[APP–72000] Non single byte characters are used in either segment4(school_name_kana) or

segment6(major_kana).

[APP–72001] Date format should be either dd–mon–yyyy or dd–mon–yy.

[APP–72002] Invalid school type is entered.

[APP–72003] Invalid value is entered in either segment10 or segment30. It should be either Y or N.

[APP–72004] Flex structure has not been set up.

[APP–72005] Invalid value is entered in segment2(school_id).

[APP–72006] Invalid value is entered in segment3(shool_name).

[APP–72007] Invalid value is entered in segment4(shool_name_kana).

[APP–72008] Invalid value is entered in segment5(major).

[APP–72009] Invalid value is entered in segment6(major_kana).

[APP–72010] Segment11 to segment29 must be null.

[APP–72011] Invalid school_id is entered.

[APP–72012] Invalid school_name is entered.

[APP–72013] Invalid major is entered.

[APP–72014] Invalid combination of school_name and major is entered.

[APP–72015] Both school_id and school_name can not be null.

[APP–72016] Invalid school_name_kana is entered.

[APP–72017] Invalid major_kana is entered.

[APP–72018] Special information type with this business group and flex number with enabled flag

being Y does not exist

[APP–72019] The flex structure with this flex number, id_flex_code = PEA, id_flex_structure_name

= educational background, and enabled flag =Y does not exist.

[APP–72020] Id flex number for educational background could not obtain.

[APP–72021] Invalid charactor was found where half kana charactors were expected.

[APP–72022] Invalid value was found in Per_Information1.

[APP–72024] Invalid charactor was found where half kana charactors were expected.

[APP–72025] Address_line2 cannot not be null when Address_line2_kana is not null.

[APP–72026] Address_line3 should not be null when Address_line3_kana is not null.

[APP–72027] Postal Code is invalid.

[APP–72028] District Code is invalid.

[APP–72029] Address_line1 is invalid.

[APP–72030] There are duplicated district codes.

[APP–72031] Both district_code and address_line1 cannot be null.

[APP–72032] Address_line1_kana is invalid.

[APP–72042] Bank segment1 is invalid.

[APP–72043] Bank segment2 is invalid.

[APP–72044] Bank segment3 is invalid.

[APP–72045] Bank segment4 is invalid.

[APP–72046] Bank segment5 is invalid.

[APP–72047] Bank segment6 is invalid.

[APP–72048] Bank segment7 is invalid.

[APP–72049] Bank segment8 is invalid.

[APP–72050] Bank segment9 is invalid.

[APP–72051] SCL segment1 is invalid.

[APP–72052] SCL segment2 is invalid.

[APP–72053] SCL segment3 is invalid.

[APP–72054] SCL segment4 is invalid.

[APP–72055] SCL segment5 is invalid.

[APP–72056] SCL segment6 is invalid.

[APP–72057] SCL segment7 is invalid.

[APP–72058] SCL segment8 is invalid.

[APP–72059] SCL segment9 is invalid.

[APP–72060] SCL segment10 is invalid.

[APP–72061] SCL segment11 is invalid.

[APP–72062] SCL segment12 is invalid.

[APP–72063] SCL segment13 is invalid.

[APP–72064] Failed to find Effective_date.

[APP–72723] Invalid value was found in Per_Information2.

[APP–72724] The dates of the competence_element for this business group which you have entered

overlaps with an existing competence record.

[APP–72725] This element has a future end date already set.

The link you have created will only exist to that date.

: Oracle Error Messages And Codes Manual

Oracle%20Error%20Messages%20and%20Codes%20Manual

Navigation menu

Versions of this User Manual:

Views

Navigation