Scribd
Upload
936 views

Setup For Oracle Payables and Cash Management

1) The document outlines the steps to setup document sequencing for invoices, payments, and bank statements in Oracle Payables and Cash Management, including defining document sequences, categories, and assignments. 2) Key steps include defining document sequences to generate numbers, categories to define document types, and assignments to link sequences and categories for a given application, set of books, and entry method. 3) The profile option "Sequential Numbering" must be set to activate document sequencing at the desired enforcement level.

Uploaded by

rcp.general
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
936 views

Setup For Oracle Payables and Cash Management

1) The document outlines the steps to setup document sequencing for invoices, payments, and bank statements in Oracle Payables and Cash Management, including defining document sequences, categories, and assignments. 2) Key steps include defining document sequences to generate numbers, categories to define document types, and assignments to link sequences and categories for a given application, set of books, and entry method. 3) The profile option "Sequential Numbering" must be set to activate document sequencing at the desired enforcement level.

Uploaded by

rcp.general
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Document Sequencing: Setup generated when the document

for Oracle Payables and Cash transaction is committed to the database.


If the document is subsequently deleted,
Management
the document sequence data remains for
Joan Currence
audit purposes. This data is stored in
Oracle Support
audit tables in each application.
Abstract
In the sysadmin responsibility the
following steps are performed.
This paper provides an overview of the
• Define a document sequence
steps to setup and use document
sequencing for Invoices and Payments • Define a document category if
within Oracle Payables as well as Bank necessary.
Statements within Oracle Cash • Assign the document sequence to a
Management. document category.
• Enable the ‘Sequential Numbering’
Scope profile option.

I. Document Sequencing Overview In the Payables responsibility, you can


II. Defining Document Sequences optionally enable Document Category
III. Defining Document Categories Override in the Payables Options
IV. Defining Document Assignments window in either the Invoice or Payment
V. Activating Document Sequencing region. This allows users access to any
VI. Troubleshooting custom defined document categories.

In the Cash Management responsibility


I. Document Sequencing Overview defining a document category is not an
optional step since the category is based
Document sequencing provides a upon the bank name.
method of numbering documents
uniquely from numbers generated within
the application. The number is
II. Defining Document Sequences assigning document numbers to. It also
specifies what table the transaction
The first step in setting up document information will be written to. This step
sequencing is to define a sequence. The is optional for Oracle Payables
sequence determines how the document transactions because Payables seeds
numbers are to be generated and to what categories for all payment and invoice
application the sequence will belong. types. These seeded categories are what

There are 3 different methods for


generating the document number:
Automatic – sequential number
generated automatically. These numbers
are not guaranteed to be gapless.
Gapless – same as automatic except
that it ensures that the document was
successfully generated before issuing a
number so that no gaps exist due to
incomplete or failed document creation.
(The recommendation is to use this
method only if absolutely necessary due
to performance issues).
Manual – instead of being
automatically generated by the system, will default into the Payables
the number is entered manually by the transactions.
user. No number ordering or uniqueness In Cash Management there are no seeded
is enforced. categories. Thus, this is a required step.
The category for Cash Management
bank statements is defined using the
Navigate:Application:Document:Sequences bank account name as the code. A
separate category would need to be
defined for every bank account for
which you want to use document
sequencing. The table used to store the
information is
CE_STATEMENT_HEADERS.

Navigate:Application:Document:Categories

III. Defining Document Categories

The second step is to define a document


category. A document category defines
what type of transactions you will be
IV. Defining Document Assignments V. Activating Document Sequencing

The last setup step is creating the Once document sequence is complete,
document assignment. The sequence you need to specify the profile option,
assignment ties together the document Sequential Numbering. This activates
sequence and the document category. document sequencing specifying both
There are several items specified on the what level of the applications to activate,
document assignment that are used by and what level of enforcement will be
the application as selection criteria when used. This profile option can be set at
searching for a document assignment for either the site or the application level.
that transaction. The combination of When set, there are 3 levels of
these values must be unique for active enforcement,
assignments. When the application Always Used - requires assignments for
searches for a sequence assignment for a all documents.
transaction, it should return only one Not Used – will not check for any
row. assignments.
Application – the application the Partially Used – will check for
document is generated from. assignments on all documents and will
Category – from step 2, it specifies the issue a warning if not found.
document type.
Navigate:Profile:System
Set of Books* – specifies the chart of
accounts document is generated from.
Method* – specifies how the document
is generated.
There are 2 methods.
Automatic, for transactions
entered through a concurrent process,
(ie. Invoice Import, Payment Batch).
Manual, for transactions entered
in the system manually through a form.
Begin Date – specifies the date that the
sequence assignment begins to be active. Payables Options to consider:
End Date – if specified, is the last date Invoice Region
that the sequence assignment is active. – Allow Document Category Override
Payment Region
*These optional fields are enabled via – Allow Document Category Override
the descriptive flexfield Document These options allow the user to override
Flexfield. the default category assigned to the
document by Payables.
Navigate:Application:Document:Assignments For Invoices, this allows the user to
choose a custom invoice category rather
than the default category that comes
seeded with the application.
For payments, this allows the user to
choose a custom category or populate
the category in the payment document.
This can be useful when document because you have your profile option set
sequencing was setup after the payment to ‘Partially Used’. Use the same steps
document was created. If document to troubleshoot. If document numbering
sequencing was not setup at the time that is not needed for the transaction, the
the payment document was entered, the message can be ignored.
document category would not get
populated.
Q: Why does an Automatic
numbering method not guarantee a
VI. Troubleshooting gapless number?

The most common errors result from A: If the record insert fails for any
problems with the sequence assignment. reason, Oracle does a rollback. The
sequence select does not roll back
• APP-1702 An assignment does not because other users may have
exist for these parameters and one is successfully committed transactions
mandatory. using the numbers read into memory
This error results from the profile option from the sequence select.
being set to ‘Always Used’and the For performance reasons, Oracle uses
application is not able to find and caching with a default cache value of 20.
assignment that matches the criteria for This means that when a transaction is
the transaction being entered. entered, 20 numbers are selected from
To resolve this issue, check the the sequence and read into memory. The
following: next time a number is requested from the
- Does the application creating the sequence, it can be read from memory
transaction, match the application on rather than disk
the document assignment?
- Does the document category match
the document category of the
assignment? About the Author
- Does the assignment set of books
match the set of books on the Joan Currence has worked with Oracle
transactions? Support Applications for the past four
- How was the transaction entered? years.
Manually or automatically? Does
this match the method on the
assignment?
- What is the GL date on the
transaction? Does it fall within the
begin and end dates of the
assignment?

• APP- 1728 An assignment does not


exist for these parameters.
This message is a warning, not an error.
It occurs for the same reasons as the
error message above, but is a warning

You might also like