You are on page 1of 7

3/4/13

Document

Document and Payment Validations in Oracle Fusion Payments [ID 1468078.1]


Modified: Oct 7, 2012 Type: BULLETIN Status: PUBLISHED Priority: 1

In this Document Purpose Scope Details 1. Validations 1.1 Definition 1.2 Types of Validations 1.3 Setting Up Validations 1.4 Document Validations 1.5 Payment Validations 1.6 Validation Points

Applies to:
Oracle Fusion Payments - Version 11.1.1.5.1 to 11.1.4.0.0 [Release 1.0] Oracle Fusion Payments Cloud Service Information in this document applies to any platform.

Purpose
This document is to provide information concerning Document and Payment validations, both of which are performed during payment processing in Fusion Payments.

Scope
The Scope of this document is to show the detailed information on Document Validations and Payment Validations. SEPA formats, Validations are out of scope in this document. SEPA is targeted to introduce in later versions of Fusion. This document is intended for functional and technical users of Oracle Fusion Payables and Fusion Payments.

Details 1. Validations
1.1 Definition Oracle Fusion Payments provides seeded validations which are similar in EBS R12 except ISO20022 formats (SEPA which are enhancements to future versions of Fusion). Validations are associated with the supported payment formats by default. Validations are implemented using a flexible framework that enables you to assign new validation rules. Seeded validations can be assigned in one the following places: Create Payment Method task - funds capture Create Payment Method task - funds disbursement Create/Update Format 1.2 Types of Validations There are 2 types of Validations: Pre-defined Validations: Payments provides a seeded library of various "country-specific" validations that are required for country-specific requirements, and "standard" validations available to everyone, such as "validate supplier bank account assignments", etc. It is comprised of a code and multiple sub-validations that are required for the specific country, a validation point, and additional specifications regarding the payment formats and/or payment methods to which the validations are applicable. Country-specific validations are seeded by Oracle Fusion Payments and cannot be modified. User-defined Validations: Users can create validations using various seeded attributes. For example, a user can define a validation that requires that payment amounts should not be below $10, etc..

1.3 Setting Up Validations Validations ensure that funds capture and funds disbursement transactions are valid, in addition to being correctly formatted before they are printed or submitted to payment systems. In FSM > View Validations, you can view seeded validations.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

1/7

3/4/13

Document

For each validation, User can view the parameters of the validation and the formats and payment methods to which it is assigned. can assign pre-defined or user-defined validations to a format of type Disbursement Payment Instruction or to a funds disbursement payment method. can assign pre-defined validations to a format of a type say Funds Capture Settlement Batch.

1.4 Document Validations The payment methods is a required attribute on a Document payable to indicate how the first-party payer will make the payment. All document validations are based on the payment method of the document. This validation process may result in failures when documents payable do not pass the

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

2/7

3/4/13

All document validations are based on the payment method of the document. This validation process may result in failures when documents payable do not pass the validation checks. The view that supports this setup is IBY_PAYMENT_METHODS_VL, based on tables IBY_PAYMENT_METHODS_B and IBY_PAYMENT_METHODS_TL.

Document

FSM > Manage Payment Method

Setup and Maintence > Manage Payment Method > Query for existing payment method or Create new/custom payment method:

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

3/7

3/4/13

Document

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

4/7

3/4/13

Document

1.5 Payment Validations These validations are based on the payment format assigned to the payment profile of the document. Go to Manage Formats task and query up the "German International EFT Format" (below), you can see that several Pre-Defined Validations have been assigned to this format say: German International EFT Internal Bank Validation, German International EFT Payee validation, German International EFT Payer Validation and German International EFT Payment validation. No User defined validation available.

If user would like to add pre-defined validation to format, click '+'. Add values for Country and Payment Method, if needed. Use these same steps to build a new User-Defined/Pre-Defined Validation for an existing Payment Method/Payment Format on the Manage Payment Methods/Manage Formats page.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

5/7

3/4/13

Document

Click '+' to add user-defined Validations to 'German International EFT Format'

Inactivating existing User-Defined Validations If you need to inactivate an existing User-Defined Validation for a Payment Method or Payment Format, simply provide the end-date.

1.6 Validation Points Validations occur at the following points in the payment process: Document Level in the Source Product: The validation is executed early in the process while the documents are created in the source product. Example of a validation run at the document level in the source product: Assign validations to the payment method on the invoice. Document Level in Oracle Payments: The validation is automatically executed late in the process by the Build Payments program as the documents are grouped into payments. Example: Assign validations to the payment format. Payment Level: The validation is automatically executed late in the process by the Build Payments program as the documents are grouped into payments. This occurs when the validation is set on a field, such as the payment amount. Example: Assign validations to the payment amount on the payment. Payment File Level in Oracle Payments: The validation is automatically executed late in the process by the Create Payment File as the payments are grouped into payment files. This occurs when the validation is set on a field, such as the payment file total amount. Example: Assign validations to the total payment amount on the payment file.

The vast majority of seeded validation sets are linked to formats. The link between validation sets and payment methods/formats is stored in the IBY_VAL_ASSIGNMENTS table, which stores the link between a validation set and a payment entity. Column VALIDATION_SET_CODE is a unique name of the validation set used for querying. Example: Check Column VAL_ASSIGNMENT_ENTITY_TYPE is type of payment entity to which this validation set is linked. This will be FORMAT or METHOD. Example: FORMAT Column ASSIGNMENT_ENTITY_ID is an actual entity to which this validation set is linked. Example: the entity is the Standard check format - IBYDC_STD1.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

6/7

3/4/13

Document

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=nvrn6rshi_106

7/7