Oracle U.S. Federal Financials provides an automatic numbering system of payment instructions where payment instructions containing different types of payments are numbered in separate sequences. The types of payment represent the purpose of the payment, such as travel expenses and payroll payments.
The Payment Instruction Sequence Assignments window enables users to optionally select automatic numbering for a payment reason within an operating unit and to define how each payment reason should be numbered. A unique numbering sequence can be defined using these values:
Initial value
Final value
Prefix, an optional value
Suffix, an optional value
Range of dates for the sequence
The sequence number is assigned when the payment instruction is created in Oracle Payments and displayed in Reference Assigned by Administrator field on the payment instruction.
To guarantee unique payment instruction numbers within an operating unit, you can only define one unique assignment per Payment Reason. You cannot define two active sequence assignments for one Payment Reason. To define a unique assignment for one Payment Reason, these conditions must exist:
Payment reasons differ
The prefix and suffix combination differ
Example A as shown in the following table, is a valid scenario with uniqueness guaranteed because the Payment Reasons and prefix-suffix combinations differ. As a result, the Initial Value and Final Value do not have to differ. The same holds true for the start date and end date.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Travel | 1 | 1000 | T- | -2002 | 01-JAN-2002 | |
| Travel-FED | 1 | 1000 | TF- | -2003 | 01-JAN-2002 |
Example B as shown in the following table, is an invalid scenario with uniqueness not guaranteed by cancelling (inserting an end date for the record) the initial assignment, then reusing the Payment Reason or prefix-suffix combination.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Travel | 1 | 1000 | T- | -2002 | 01-JAN-2002 | 31-JAN-2002 |
| Travel | 1 | 1000 | T- | -2002 | 01-JAN-2003 |
Example C as shown in the following table, is an invalid scenario because uniqueness is not guaranteed since the Payment Reasons do not differ.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Travel | 1 | 1000 | T- | -2002 | 01-JAN-2002 | |
| Travel | 1 | 1000 | TF- | -2003 | 01-JAN-2002 |
A prefix and suffix can never be reused. To guarantee unique payment instruction numbers within an operating unit, you must never reuse a prefix and suffix combination per Payment Reason assignment. To define a unique assignment depicting the proper use of a prefix and suffix combination, the Payment Reasons must be different. The Prefix-suffix combinations must differ, and never be reused.
Example D as shown in the following table, is a valid scenario because uniqueness is guaranteed by different Payment Reasons and prefix-suffix combinations. In particular, each record has a different suffix.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Allotments | 1 | 1000 | P- | -2002 | 01-JAN-2002 | |
| Salary | 1 | 1000 | PF- | -2003 | 01-JAN-2002 |
Example E as shown in the following table, is an invalid scenario because uniqueness is not guaranteed due to the prefix-suffix combinations not being different.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Allotments | 1 | 1000 | P- | -2003 | 01-JAN-2002 | |
| Salary | 1 | 1000 | P- | -2--3 | 01-JAN-2002 |
Example F as shown in the following table, is invalid. Even though numbers generated in this case would be unique, this would be very confusing. The purpose of the prefix and the suffix is to distinguish between different types of payments, and this setup does not accomplish this. For a given range of dates, the assignment of the prefix and the suffix is valid for one payment reason only.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Travel | 1 | 1000 | T | 2003 | 01-JAN-2002 | 31-DEC-2002 |
| Tax | 1001 | 2000 | T | 2003 | 01-JAN-2003 | 31-DEC-2003 |
Example G as shown in the following table, is invalid. The numbers generated by these assignments would not be unique. In addition, you would not be able to tell the two types of payments apart.
| Payment Reason | Initial Value | Final Value | Prefix | Suffix | Start Date | End Date |
|---|---|---|---|---|---|---|
| Travel | 1 | 1000 | T | 2003 | 01-JAN-2003 | 31-DEC-2003 |
| Tax | 1 | 1000 | T | 2003 | 01-JAN-2003 | 31-DEC-2003 |
Before setting up automatic sequence numbering of payment instructions, you must:
Define the FV: Enable Automatic Numbering profile option to enable automatic sequence numbering.
Define any additional payment reasons in the Oracle Payment Codes window.
Related Topics
Defining Lookup Codes, Oracle Purchasing User's Guide
Customizing the Layout of a Folder, Oracle Applications User's Guide
To assign automatic sequence numbering to payment instructions, navigate to the Payment Instruction Sequence Assignments window.
The following table describes selected fields on the Payment Instruction Sequence Assignments window.
| Field Name | Description |
|---|---|
| Operating Unit | Operating unit of the record.
Note: The list of values include operating units assigned to the MO: Security profile. |
| Payment Reason | Payment reason |
| Initial | Beginning sequence value |
| Final | Ending sequence value |
| Prefix | Prefix sequence value
Note: There can only be one prefix-suffix combination per Pay Reason irrespective of different organizations. Note: Users can add a separator between the prefix and the sequence number. For example, if the sequence number is T-00001, the user enters the prefix as T-. |
| Suffix | Suffix sequence value
Note: Users can add a separator between the suffix and the sequence number. For example, if the sequence number is 00001-2003, the user enters the prefix as -2003. |
| Start Date | Automatic numbering sequence begin date
Tip: Leave the End field blank. |
| End Date | Automatic numbering sequence end date
Note: It is recommended that users not enter an end date. |