Possible solution for exception process for barcode mismatches.
You'll need to setup a virtual e-form in OnBase, an import process and a simple Workflow to handle the exceptions, and on the SAP side the External table will have to be extracted.
SAP:
- Extract data from the External table and save as a CSV file
- Setup an SAP process to extract data
- Extract should occur once a day possibly more depending on workload
OnBase:
- Virtual E-form should be created and have the keyword: SAP ArchiveLink Barcode. You can include other keywords (such as Repository ID, Processor ID) on the virtual e-form, but only SAP ArchiveLink Barcode would be used to match. Any others would be informational only.
- Setup a scheduled task to load the extracted External table data into the virtual e-form.
- For the Workflow, use a folder so associated documents show up in the Work Folder, and also setup a 'Complete' AdHoc task so that when SAP has been updated, the e-form is pushed out of the Workflow.
- End user goes into SAP, finds the incorrect business object, updates the object with the correct barcode value and saves it.
- Once SAP has been updated, end user goes into OnBase and marks the e-form 'Complete', and moves to the next entry.
- With the corrected barcode, the external/internal table match should occur and your exception should be fixed.
