Technical Insight of AP Invoice With Imaging

Download as pdf or txt
Download as pdf or txt
You are on page 1of 9

AP Invoice with Imaging – A Technical Insight

Fusion Applications

White Paper -

Technical Insight of AP Invoice with Imaging

Author: Vijaya Gudipati, FAST-Payables


Version: 1.0
August 2011

Fusion Payables 1
Overview

A scanned invoice is an invoice that is processed through the Oracle Fusion Payables integrated imaging
solution.

The integrated imaging solution uses:

 Oracle Document Capture to receive the scanned invoice image.


 Oracle Forms Recognition to scan the image and capture invoice header information.
 Oracle Imaging and Process Management to take the processed image and convert it into a BPEL
task for routing to the proper accounts payable specialist for completion. Oracle Imaging and Process
Management provides the repository to store the image, along with the captured attributes.

Scanning Invoice Attributes

You can configure Oracle Forms Recognition to capture the following invoice header attributes:

 Purchase order number


 Supplier
 Invoice number
 Invoice amount
 Invoice date
 Customer taxpayer ID

Routing Scanned Invoices

A BPEL process flow assigns the scanned images to Payables users based on routing rules to complete
invoice entry. When an accounts payable user signs in to Payables, a list of assigned images are presented
in the Invoices work area for invoice entry.

BPEL Routing Process

A new instance of the BPEL process is generated when an invoice image is saved successfully in IPM,

which will then be routed based on the configured rules.

FinApInvTransactionsImageTransferComposite is SOA BPEL Composite which consists of Business

rules, bpel design flow and wsdl flow process.

 Action Rules

 Business Process Management (BPM) Worklist

 Parameters or Key Attributes

 Test Run

Fusion Payables 2
 Action Rules:

Fusion Payables provides a sample approval rule for image routing based on the invoice
amount.

ImageAssignmentRuleset defines if the Payload attribute invoiceAmount <1000 then


router route the imaged invoices to AP_SPEC_OPERATIONS.

Else if invoiceAmount > 1000 then process will route to AP_SUPV_OPERATIONS.

 Business Process Management (BPM) Worklist

A default image routing rule based on the invoice amount assigned to individual users will be

seeded as part of the provisioning process. Implementers will need to modify these routing rules

using the BPM (Business Process Management) Worklist application to achieve the desired

specialization within the Payables department.

BPM Worklist list out all tasks where user can check whether task is assigned, completed,

withdrawn, expired, suspended or Errored.

Fusion Payables 3
 Parameters or Key Attributes
Invoice Header Key Attributes are taken from the BPEL payload parameters/attributes set.

 Image Number (unique number)

 Assigned Date ( Queue Date in Invoice workbench)

 PO Number (Identifying PO in Invoice workbench)

 Supplier

 Invoice Number

 Invoice Date

 Invoice Amount

 Customer Taxpayer ID (Taxpayer ID in Invoice workbench) (optional)

 Business Unit (optional)

 Test Run from Enterprise Manager Console

 Test Run Web Service

Fusion Payables 4
 Enter the Input Arguments to Test the SOA Composite and Submit the Test.

Fusion Payables 5
 Response shows that Composite Instance was generated. Click Launch Flow Trace to view

the Flow Trace of the instance.

 ImageTransferProcess Instance provides information about to which user the invoice got

assigned.

Fusion Payables 6
 BPM Worklist show list of details of assignment.

 Invoice Workbench of the Assigned User show the scanned invoice in Overview dashboard.

 Create Invoice show the image as attachment to the invoice.

Fusion Payables 7
Technical Summary
 Application Modules (AM)

 Entity Objects (EO)

 View Objects (VO)

 View Links (VL)

 Database Tables

Application Entity Objects (EO) View Objects (VO) View Links


Modules (AM)
FndAttachedDocumentsEO AttachmentsVO FndAttachedDoc
FndDocumentsEO DocumentTypesVO umentsVO.xml
FndDocumentCategoriesEO FndDocCategoriesVO
AttachmentsUIAM
FndDocumentEntitiesEO FndAttachedDocumentsVO

InvoiceTransactionAM FndAttachedDocumentsEO APIpmImageVO

InvoiceHeaderEO InvoiceHeaderVO

FinApInvTransactonsModel.jpr > InvoiceHomePF.jsff and InvoiceEditPF.jsff

 Executable: APIpmImage1Iterator
 Invoice TransactionAMDataControl
o APIpmImageVO

Data Model: (View Objects created from Tables)

 AttachmentsVO
 FND_ATTACHED_DOCUMENTS
 FND_DOCUMENTS_VL
 FND_DOCUMENT_ENTITES_VL
 FND_DOCUMENT_CATEGORIES_VL
 FndAttachedDocumentsVO
 FND_ATTACHED_DOCUMENTS

Fusion Payables 8
 FndDocumentsVO
 FND_DOCUMENTS_VL
 InvoiceHeaderVO
 AP_INVOICES_ALL
 APIpmImageVO
 FND_ATTACHED_DOCUMENTS

ViewLink: InvoiceHeaderVOToAttachmentsVO.xml

View Objects involved AttachementsVO and InvoiceHeaderVO

Query where clause: FND_ATTACHED_DOCUMENTS.PK1.VALUE = AP_INVOICES_ALL.INVOICE_ID

Sample Data:
select Attached_document_id,document_id,category_name,pk1_value,entity_name,created_by
from FND_ATTACHED_DOCUMENTS
WHERE PK1_VALUE = '100000133182952' ( Enter Invoice_id)

select document_id,Title, Created_by,Datatype_code,Description, Url from fnd_documents_vl


where document_id = <<enter doc id from above query>>

Fusion Payables 9

You might also like