Business Scenario

AP Process Flow:
The AP Process Flow starts once the needs for any material or service are identified at
the
production departmant or any other department.
1. Production Department will raise the Purchase Requisition(PR) through
Procurement /Commertial Team.
2. The commertial team or procurement team will get bids or quotes from different
vendors and finalize the vendor.
3. Once the vendor is finalized, they will issue a Purchase Order(PO) to the vendor.
4. Vendor will deliver the Goods/Services to our warehouse/factory.
5. The warehouse person will enter the reciept of goods in Goods Recieved
Notes(GRN), In case of services it is Service Reciept Note(SRN).
6. Simultaneously, Vendors will send the invoice copy to Account Payable(AP) Team
then, AP team will do a 3-way match between Invoice, PO and GRN/SRN and
process the invoice.
7. Payment will be made to the vendor based on the payment terms.

Concepts: OrgID(Business Unit), OrganizationID

For instance let us say you are having Inventory Store.
You have Inventory Stores in two different countries like India and USA
You have installed Oracle Apps single instance and entered all the suppliers information,customers data,tax
rules etc.
And your business requirement is like this, all the rules and the data corresponding to indian store shouldnt
be applicable/available to american store and vice versa.
So to meet the above requirements you will define two operating units one for india and one for USA.
Now each operating unit will have an ID known as ORG ID.
And we use ORG ID to secure our business data.
Now to do transactions for indian operations you need to define one responsibility and attach indian ORG ID
to this responsibility.By this an indian will not see any data/rules applicable to USA.
Similarly you will define another responsibility for USA and attach USA's ORG ID to this responsibility so
that an american will not see any data/rules corresponding to India.
This is the concept of ORG ID.
Now let us see what is Organization ID.
Within India you have got various branches in different parts of the country in different states like AP,UP,MP
etc.
And the business requirement is like this in AP you will maintain stock of Rice,UP for Wheat and MP for
Maize.
To meet this business requirement you will define 3 Inventory Organizations under Indian Operating Unit to
maintain the respective stocks of the states..
Each Inventory Organization will have an Organization ID.
This is the outline of the differences between ORG ID and Organization ID.

ODC: Oracle
Document
Capture

Tiff File
Step1

IPM: Image
Processing
Management

Step 4

Composites
SOA/ BPEL

Step 6

TIFF, XML, TXT files

Step 2

WEBCENTER IMAGING

Step 1.1

Step 5

OFR: Oracle
Forms
Recognition

Step 3

Input

Image + Content(XML)
UCM: Universal
Content
Management

Web Services
EBS

Input Agent
Agent
Input

EBS-DB

ODC: Oracle
Document
Capture
Step 1.1
IPM: Image
Processing
Management

Step 1.1) This covers the activities involved in commiting image direc

This approach is used for committing the image directly to IPM server with bare
minimum metadata. This is simplest and quickest way to push the image in IPM.
Document is scanned using scan profile
1.
Document is scanned using scan profile
2.
Based on 'File Cabinet' it assignes the file name.
3.
Image is indexed and commit using indexing profile.
4.
Based on the commit profile, it commits the image to IPM.
5.
Only TIFF and TXT file is generated in this case that is feed into IPM through
6.
No XML file generated in this case.

ODC: Oracle
Document
Capture

Tiff File
Step1

OFR: Oracle
Forms
Recognition

Step 1) This covers the below activities with in Oracle

Document Capture (ODC).
1.
Document is scanned using scan profile
2.
Based on 'File Cabinet' it assignes the file name.
3.
Image is indexed and commit using indexing profile.
4.
Based on the commit profile, it commits the image to OFR.
5.
The data is passed using file name of TIFF. Generally file name
contains different
values in the file name separated by _
(underscore).Mostly it has values like
BatchName, ScanDate,
ScanDocumentID.

OFR: Oracle
Forms
Recognition

TIFF, XML, TXT files

Step 2
Input Agent
Agent
Input

Step 2) This covers the activities with in Oracle Forms

Recognition(OFR).
1.
Data is extracted from image using series of operations like Optical
character
Recognition (OCR), Classification, Extraction and
Export.
2.
This creates the 3 files (Tiff, XML and TXT) which are fed to the IPM
input agent.
3.
Input agent directory is a standard ingestion method for adding
content to IPM.
4.
OFR does the processing like OCR, classification, extraction, export
and pulls the data from image. It creates 3 files in the output directory
configured in the OFR export
location.
A.
TIFF: This contains the document image. It may be a multipage. This is
the same file
that has been given as an input to OFR by ODC.
B.
XML: This contains the data extracted from the document image. The
xml elements
are controlled from INI file and scripts in OFR.

OFR: Oracle
Forms
Recognition

TIFF, XML, TXT files

Step 2
Input Agent
Agent
Input

Step 2) This covers the activities with in Oracle Forms

Recognition(OFR).
1.
Data is extracted from image using series of operations like Optical
character
Recognition (OCR), Classification, Extraction and
Export.
2.
This creates the 3 files (Tiff, XML and TXT) which are fed to the IPM
input agent.
3.
Input agent directory is a standard ingestion method for adding
content to IPM.
4.
OFR does the processing like OCR, classification, extraction, export
and pulls the data from image. It creates 3 files in the output directory
configured in the OFR export
location.
A.
TIFF: This contains the document image. It may be a multipage. This is
the same file
that has been given as an input to OFR by ODC.
B.
XML: This contains the data extracted from the document image. The
xml elements
are controlled from INI file and scripts in OFR.

Input Agent
Agent
Input

Input

Step 3

Step 3) This covers the details which happen once the files are added
and inputs gets activated.
1.
2.

In IPM admin section under Manage Inputs we must have defined the mas
masks are generally pointing to seeding file. In our case it is TXT file.
Based on the input mask, Input agent will pick-up only the seeding file
(in our case it is TXT). This file will have the metadata which will be mapped
application fields. The XML and TIFF files are referred from seeding file (i.e.

IPM: Image
Processing
Management

Step 4

Input

Step 4) This covers the details happened between inputs and IPM
1.

2.
3.

TIFF file is pushed in UCM and the unique IPM URL is created using configur
made in IPM schema. This URL becomes a web viewable URL to show ima
AXF paradigm. In this stage DocumentID is created which is used as a uniq
accessing the document.
Based on the mapping, data will be read from TXT file and new record is cre
IPM.
The XML file is used as a supporting content which is passed while invoking
instance.

IPM: Image
Processing
Management

Image + Content(XML)
UCM: Universal
Content
Management

Communication between Imaging (IPM) & WebCenter Conten

1.
2.

3.
4.

It passes below entities to content server

TIFF images along with the metadata which has been received as imaging app
fields. While doing this the web URL. This URL is a combination of multiple
parameters which are defined in configuration table present in IPM schema.
Content server creates an unique Document ID based on the prefix configure
auto-increment number. While creating the web-url, IPM also adds the applic
ID as the prefix.
It also passes the supporting content which is XML file content.
The document ID generated in Content server is also saved in the Imaging ap
This is a unique reference number for the document.

IPM: Image
Communication between Imaging & SOA server

Processing
Management

This is based on the workflow configuration made

in IPM. This works like a trigger,
as soon as new entry is made in the
Step 5
IPM, this is triggered. Below events
happens using SOA server connection.
1.
2.
3.
4.
5.
6.

Composites
SOA/ BPEL

Once new entry is made in the IPM, prior to this data has been already pushed
server & related data is also available in the imaging application, this uses
the workflow configuration.
Workflow configuration has details like SOA server connection, composite name
its revision, mapping of the fields.
Using above details it invokes composite web service exposed by SOA server.
Using parameter mapping it creates the input SOAP XML. Few important fields li
document ID, document URL are also passed. These values are used in future c
This SOAP XML will also have the supporting contents present in XML file sent to
imaging in OFR flow.
Once the SOA composite is invoked from imaging, there is no further action line
imaging. There are no events that happen in imaging which pull or push the da
entities. However metadata is updated in imaging application using value of do
BPEL.

SOA/ BPEL

SOA/ BPEL activities:

1.
2.
3.

4.

5.
6.
7.
8.
9.

The first composite in all cases is Document Routing.

From here it calls Invoice Import composite.
This composite is responsible for many important tasks
A.
This does basic validations like Org_id. In case this is incorrect it will direct
processing without ingesting any data in EBS
B.
It will check the type of invoice.
C.
If it is PO then it will go to next step. If it is non-PO then it will call 'Accoun
and allow user to do the coding(Approve).
Then it will invoke Invoice validation and import composite. This composite
detailed validations and will add the invoice data in Open interface table(AP_Inv
of EBS. Later on from there it will be sent to Invoice Master/Base table(AP_Invoi
using concurrent job.
This composite will send status of validation back to Invoice Import.
Based on the validation status it will do further activities.
If the status is N then it will invoke invoice processing.
If the status is Y then it will wait for EBS response and then proceed to next step
The EBS response will be processed in Post Invoice Import composite that cre
Invoice Synchronization composite is used to attach Image in EBS.

Document Routing

Status (Y)

Invoice Import
NO-PO

Yes

Basic Validation
Like Org-Id
NO

PO
Account
Distribution

Invoice
Processing
Detailed Validation

YES

Invoice Validation
and Import

NO

Yes
EBS- Interface Table
Response
Post Invoice Import

Entry to Base table

AP_INVOICES_ALL