Business ScenarioAP Process Flow:The AP Process Flow starts once the needs for any material or service are identified at theproduction departmant or any other department.

Production Department will raise the Purchase Requisition(PR) through Procurement /Commertial Team. The commertial team or procurement team will get bids or quotes from different vendors and finalize the vendor. Once the vendor is finalized, they will issue a Purchase Order(PO) to the vendor. Vendor will deliver the Goods/Services to our warehouse/factory. The warehouse person will enter the reciept of goods in Goods Recieved Notes(GRN), In case of services it is Service Reciept Note(SRN). 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. Payment will be made to the vendor based on the payment terms.

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. Concepts: OrgID(Business Unit), OrganizationID

ODC: Oracle Document CaptureOFR: OracleForms Recognition Input AgentIPM: Image Processing Management Input AgentInput UCM: Universal Content Management SOA/ BPELEBS-DBEBSTiff FileStep1TIFF, XML, TXT files

Step 2Step 3Step 4Step 3Step 1.1Image + Content(XML)CompositesWeb ServicesStep 5Step 6WEBCENTER IMAGING

ODC: Oracle Document CaptureIPM: Image Processing Management Step 1.1Step 1.1) This covers the activities involved in commiting image directly to IPM

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 profile1. Document is scanned using scan profile2. 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 input agent.6. No XML file generated in this case.

ODC: Oracle Document CaptureOFR: OracleForms Recognition Tiff FileStep1Step 1) This covers the below activities with in Oracle Document Capture (ODC).

1. Document is scanned using scan profile2. 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: OracleForms Recognition Input AgentInput AgentTIFF, XML, TXT files

Step 2Step 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.C. TXT: This contains the metadata that will be filled in IPM application.5. All these 3 files will be exported in IPMs Input agent directory.6. IPM has a listener pointed to this folder which wills pick-up the seeding file defined in mask under inputs entity in IPM.

OFR: OracleForms Recognition Input AgentInput AgentTIFF, XML, TXT files

Step 2Step 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.C. TXT: This contains the metadata that will be filled in IPM application.5. All these 3 files will be exported in IPMs Input agent directory.6. IPM has a listener pointed to this folder which wills pick-up the seeding file defined in mask under inputs entity in IPM.

Input AgentInput AgentInput Step 3Step 3Step 3) This covers the details which happen once the files are added in Input agent and inputs gets activated.

1. In IPM admin section under Manage Inputs we must have defined the masks. These masks are generally pointing to seeding file. In our case it is TXT file.2. 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 with application fields. The XML and TIFF files are referred from seeding file (i.e. TXT).

IPM: Image Processing Management Input Step 4Step 4) This covers the details happened between inputs and IPM application.

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

IPM: Image Processing Management UCM: Universal Content Management Image + Content(XML)Communication between Imaging (IPM) & WebCenter Content(UCM)

1.It passes below entities to content server2. TIFF images along with the metadata which has been received as imaging application 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 configured and auto-increment number. While creating the web-url, IPM also adds the application ID as the prefix.3. It also passes the supporting content which is XML file content. 4. The document ID generated in Content server is also saved in the Imaging application. This is a unique reference number for the document.

IPM: Image Processing Management SOA/ BPELCompositesStep 5Communication between Imaging & SOA server

This is based on the workflow configuration madein IPM. This works like a trigger, as soon as new entry is made in the IPM, this is triggered. Below events happens using SOA server connection.

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

1.The first composite in all cases is Document Routing.2.From here it calls Invoice Import composite.3.This composite is responsible for many important tasksA.This does basic validations like Org_id. In case this is incorrect it will directly sent it Invoiceprocessing without ingesting any data in EBSB.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 'Account Distribution' and allow user to do the coding(Approve).4. Then it will invoke Invoice validation and import composite. This composite will do the detailed validations and will add the invoice data in Open interface table(AP_Invoices_Interface) of EBS. Later on from there it will be sent to Invoice Master/Base table(AP_Invoices_All) using concurrent job. This composite will send status of validation back to Invoice Import.5. Based on the validation status it will do further activities.6.If the status is N then it will invoke invoice processing.7.If the status is Y then it will wait for EBS response and then proceed to next step.8. The EBS response will be processed in Post Invoice Import composite that creates holds.9. Invoice Synchronization composite is used to attach Image in EBS.

SOA/ BPELSOA/ BPEL activities:

Document RoutingInvoice ImportAccount DistributionNOYesInvoice ProcessingNO-POPOInvoice Validation and ImportEBS- Interface TablePost Invoice ImportDetailed ValidationNO

YesStatus (Y)YESResponseEntry to Base tableAP_INVOICES_ALLBasic ValidationLike Org-Id