Wednesday, February 27, 2013

How To: Send a custom static value from Oracle Document Capture through Oracle Forms Recognition

Disclaimer: This article assumes some knowledge of Oracle Document Capture (ODC) and Oracle Forms Recognition (OFR). Also, dependency on the Oracle AP Solution Accelerator is expected as well.

This blog will provide an example of how to use the provided scan macro to set static values without any customizations to the macro.

This sample will use an ODC variable named 'Organization' to map to the OFR existing 'CompanyCode' header. Finally it will be exported in the OFR export .xml as the 'orgID' element.

Let's take a look at the process:

1.     Start by opening ODC as an admin user

2.     Open the macro management window by clicking System --> ManageMacros
a.      We'll assume the use of an ISIS-driver based scanner for this scenario
b.     Select the category of "Scan for ISIS"

3.     Using the AP Accelerator, there will be an existing macro named "OFR-Scan-ISIS-Macro"
a.      Select this macro, but do not open it
b.     Click on the 'Setup' button

4.     The setup configuration window will appear at this time

5.     Notice the "Default Values" field
a.      This is where we will place our static value
b.     NOTE: The 'Organization' variable must be an existing variable for the related file cabinet
                                                             i.      The file cabinet is associated with the scan profile, which leverages the macro opposed to the macro itself
6.     Enter the following into the Default Values: Organization=204
a.      Note that multiple values may be entered by comma separating the entries

7.     Now, the custom variable must be added to the output; this is done via filename naming syntax
a.      Open the File Cabinets
                                                             i.      The default accelerator file cabinet is "Invoices - OFR"
b.     Select the commit profile for your file cabinet
                                                             i.      The default accelerator commit profile is "OFR Commit"
                                                           ii.      It is a "Commit Text File" driver, which allows for the following configuration options
c.      Click the "Config..." button next to the commit driver
d.     In addition to the default configurations, add the following on the "Document File Naming" tab

e.      Make sure that the Organization is set in the "Selected Fields"
                                                             i.      For our example, we're using the third position
1.     This is needed for OFR input configuration
2.     Also make sure your field delimiter is changed from <space> to '_' as this is what OFR will be expecting by default
8.     At this point, an item run through the scan profile attached to the macro & file cabinet will output with the expected format
a.      e.g., 649_D6F37E2C17AE494D8DA87B991A25186F_204_04122012.tif

9.     Now the OFR configurations will take place
a.      This will consist of updating the .ini file to ensure the input and output options are mapped as expected

10. Configure the Import variable mapping
a.      Open OFR's project .ini file
b.     Locate the block of keys starting with: IMP_VL_
                                                             i.      Note that these are the values that are exposed by default
                                                           ii.      Tokenized values can be assigned to each of the IMP_VL_ keys
                                                        iii.      Again, the delimiter is the '_' field.
1.     Gotcha: You must make sure that no '_' are existing in the values or that could affect the tokenizing and parsing process
c.      Locate the IMP_VL_CompanyCode key
                                                             i.      This is the exposed key for the OFR Company Code variable
                                                           ii.      Update this entry to the following: IMP_VL_CompanyCode=COMPONENT3
1.     Recall that we used position #3 for the ODC Organization
d.     This completes the import mapping

11. Configure the Export variable mapping (.XML)
a.      Again, open the OFR's project .ini file (if not already open)
b.     Locate the block of keys starting with: EXP_VL
                                                             i.      These are the default exposed output variables
                                                           ii.      Values mapped to these keys are exported as xml elements
c.      Locate the EXP_VL_XMLHCCompanyCode key
                                                             i.      This is the exposed key for exporting the Header Company Code
                                                           ii.      Update this entry to the following:
                                                        iii.      This will map the OFR Header Company Code to the output XML <orgID> value
12. Configure the Export variable mapping (.txt)
a.      And, again, open the OFR's project .ini file (if not already open)
b.     Locate the block of keys starting with: CSV_VL
                                                             i.      These are the default exposed configurations for create supplemental output files
                                                           ii.      There is a specific line format syntax that is configured to output the values
c.      Locate the CSV_VL_01_FormatLine1 key
                                                             i.      This is the exposed key to set the output syntax for this specific 'CSV' configuration
1.     Tip: CSV configurations do not require the output to be in csv format
                                                           ii.      Using the exposed variable, <%CCO>, will allow for the addition of the Header Company Code into the output.
d.     An example:

This wraps up the walkthrough. Thanks for reading!

Wednesday, February 13, 2013

Tip of the Day: Metadata-only Content Without Configuration

Just a quick tip pulled directly out of the product docs:


You can check in a metadata placeholder without specifying a primary file by entering an invalid path in the Primary File field. For example, entering the word placeholder into the Primary File field creates a content item within Content Server with the specified metadata, but no indexed primary file. Placeholders are useful for initiating workflows or making metadata available for searching and discussion.


 If you are checking in a placeholder using Internet Explorer version 6.0 on the Windows XP operating system with Service Pack 2 installed, the path used in the Primary File field must be valid, but end with an invalid file. In the following example, c:/ is a valid drive, but placeholder is not a valid file:


If you do not specify a valid drive, an error message is displayed. Pretty clever way of forcing a meta-only content item without the configurations in place!

It's always worth reading the docs!


Friday, February 1, 2013

While You Were Sleeping -- New Oracle WebCenter-Imaging Patches

In the middle of the night, while you were sleeping, Oracle has released a couple of new patch sets for the WebCenter-Imaging product, version  They are as follows with some details as to what they fix:

  • 16244026: IPM/AXF Patchset 10
    • Bug 16243790 - AXF EBS R12 adapter doesn't differentiate between balance segments and other types of segments.  This change also requires 16245122.
    • Bug 16051792 -The GetDocumentPermissions service is being called too many times (part 3 of a multi-part fix).
    • Bug 14822845 - When using the URL Tool, ExecuteSearch, the link generated by the eMail button on the search results screen givs the wrong results when executed.  This also affects Image Searching from PeopleSoft as this utilizies this URL tool.
    • Bug 14137629 - When creating a text annotation, the font is too small.  The default font will now be Arial, point size 12.
  • 16245122: EBS Patchset 3
    • Bug 16243790 - AXF EBS R12 adapter doesn't differentiate between balance segments and other types of segments.

Also, they have released the following patch for version

  • 16262772: IPM/AXF Patchset 15
    • Bug 10271381 - Error on import application where it fails to import.
    • Bug 10644977 - An issue in AXF where the Auto Task mode fails when using the Enumeration Picker.
    • Bug 11663155 - Basic viewer can fail when attempting to render an image via URL without the size of the image in the URL.
    • Bug 11780032 - A SQL Syntax Error Exception is being recored sometimes when attempting to search by a Date field.
    • Bug 11893266 - The Goto Page Number box is empty when attempting to view 2 pdfs both of which are over 10 pages long and you are on the last page of the second one.
    • Bug 11934578 - Remove warning when attempting to work on a AXF project in JDeveloper.
    • Bug 11934646 - Remove the requirement of an Account Code when using EBS12 for Account Distribution
    • Bug 11934679 - Change the Segment Editor to initilize segments with default values.
    • Bug 11934687 - Chagne the Segment lookup to respect Segment Dependency models.

Have a good day!