Previous  Next          Contents  Index  Glossary  Library

Voucher Definition in Oracle Payables

The company wants to use General Ledger, Oracle Payables, and Oracle Receivables for the accounting period 1996, assigning to all passive invoices, credit memos, and custom bills manually entered in Oracle Financials a single sequence of voucher numbers. In order to benefit from the functionality which reduces the number of transactions necessary to enter EU Invoices and Payables Self Invoices, the company decides to assign two further different sequences to these documents. The company has two offices entering invoices. To easily identify which office has carried out each entry, the company decides to have a double sequence of documents, identical but characteristic of each office.

The company decides to define the following new documents:

1. Passive invoices - office A

2. Passive invoices - office B

3. EU invoices - office A

4. EU invoices - office B

5. Self invoices - office A

6. Self invoices - office B

7. Non-VAT passive documents - office A

8. Non-VAT passive documents - office B

9. Payments - office A

10. Payments - office B

The company decides to define the following vouchers:

FATPAS_96_
For all passive invoices, credit memos, and custom bills manually entered (Documents 1 and 2)
CEEFAT_96_
For all EU VAT passive invoices and credit memos manually entered (Documents 3 and 4)
AUTFAT_96_
For all suppliers self invoices (Documents 5 and 6)
NONIVA_96_
For all non-VAT passive documents (bills of costs, fuel cards, extra-EU invoices) (Documents 7 and 8)
PAGAM_96_
For all payments (Documents 9 and 10)
Voucher Definition and Oracle Payables Hints

Always choose a sequence name that easily identifies the entry type (taking into account the maximum printable size, which is 14 characters for vouchers). In addition, choose a name that is easy to update every year.

Before you start to define the structure, you must set the Sequence Numbering profile option to Always Used using the System Administrator responsibility.

The next transactions must be carried out using the same responsibility.

Use the standard functionality in the Define Document Categories window to define documents according to the following scheme:

Application
Code
Name
Description
Table
Oracle Payables
Passive invoices = A
Passive invoices A
Passive invoices entry A
AP_INVOICES
Oracle Payables
Payment B with check
Payments with check
Customers bank check payments entries - office B
AP_CHECKS

Use the standard functionality in the Define Documents Sequences window to define sequences according to the following scheme:

Name
Application
Start Date
End Date
Type
Initial Value
Message
FATPAS_96
Oracle Payables
01-JAN-98
31-DEC-98
Gapless

Yes
PAGAM_96
Oracle Payables
01-JAN-98
31-DEC-98
Gapless

Yes

Use the standard functionality in the Assign Document Sequences window to assign documents to sequences according to the following scheme:

Document Flexfield
Start Date
End Date
Sequence Name
Application = Oracle Payables
01-JAN-98
31-DEC-98
CGM_96
Set of Books =Reference Set of Books



Category = Passive invoices - A



Method = manual



Application = Oracle Payables
01-JAN-98
31-DEC-98
NOCGM_96
Set of Books =Reference Set of Books



Category = Passive invoices - B



Method = manual



Application = Oracle Payables
01-JAN-98
31-DEC-98
NOCGM_96
Set of Books =Reference Set of Books



Category = Payments B with check



Method = manual





         Previous  Next          Contents  Index  Glossary  Library