Beruflich Dokumente
Kultur Dokumente
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.
ODC: Oracle
Document
Capture
Tiff File
Step1
IPM: Image
Processing
Management
Step 4
Composites
SOA/ BPEL
Step 6
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
OFR: Oracle
Forms
Recognition
OFR: Oracle
Forms
Recognition
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
3.
4.
IPM: Image
Communication between Imaging & SOA server
Processing
Management
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
4.
5.
6.
7.
8.
9.
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