PROCESSIT 7.4 R1
For Oracle Fusion Middleware 11g

Custom Validation

©2025 Copyright ReadSoft AG (publ). All rights reserved. The contents of this document are subject to change without notice. ReadSoft is a registered trademark of ReadSoft AB. Other product and company names herein may be the trademarks or registered trademarks of their respective owners.
Questions or comments about this document may be emailed to documentation@readsoft.com.

ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20
ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13
info@readsoft.com | www.readsoft.com

Custom ValidationCustomizationSupport for Custom ValidationsInterface validation process flow procedureReturn codesCustom Validation - Synchronization

Custom Validation

Customization

This customization is managed in the Customization Workbench.

Support for Custom Validations

You can add your own custom validations for the invoice data inserted into Payable Interface. The custom validations are carried out prior to importing invoices to Accounts Payable.

To enable custom validation, login as user setup and open the Customization Workbench and find the interface named VALIDATE_AP_INTERFACE with description Validate the invoice inserted into payable interface tables. You can supply custom code or use the seeded code. To enable the customization, select the source code for the interface and click Enable.

After data has been inserted into the payable interface, the plsql package xxd4_validation in the apps schema in the Oracle E-Business Suite database is invoked.

The xxd4_validation package contains the procedure validate_ap_interface that acts as a router. It calls the procedure validate_ap_interface in the package xxd4_validation_custom.

You must create the package xxd4_validation_custom and the methods in it according the signature in the package xxd4_validation. This way, the xxd4_validation package can be overridden when new callout options are introduced without removing the custom code.

The call to xxd4_validation is performed to be backward compatible with the first version of this interface. You can also add a new source code that invokes the xxd4_validation_custom or even add the custom plsql code directly here.

Interface validation process flow procedure

  1. Insert data into payable interface.
  2. Invoke Custom validation.
  3. In case of error returned go to 4, else go to 6.
  4. Send notification to administrative super user who corrects data Modify Invoice.
  5. If super user replied Retry go to 6. If super user replied Stop flow go to 11.
  6. Run import.
  7. In case of rejections go to 8, else go to 10.
  8. Send notification to administrative super user who corrects data Modify Invoice.
  9. If super user replied Retry go to 2. If super user replied Stop flow go to 11.
  10. Remaining workflow processed.
  11. Stop flow.

Return codes

Status code OK=Continue importing
--             ERROR=Correct errors
--             EXCEPTION=Unexpected exception

You must create the plsql package xxd4_validation_custom with this procedure:

PROCEDURE validate_ap_interface(
    p_ap_invoice_id number,
    P_processit_invoice_id number,
    p_status_code OUT VARCHAR2,
    p_status_desc OUT VARCHAR2)
AS

Custom Validation - Synchronization

If synchronization is enabled, any changes made to the invoice in AP interface from either the custom validation plsql package or from PROCESSIT payable correction form are copied back to the PROCESSIT invoice table.

To enable synchronization for custom validations, set the configuration parameter Synchronize changes in payable interface to Yes.

The synchronization is not aware of custom mapping and can therefore not be used if custom mappings are used.