Skip to main content
Kofax

MarkView Expense Management - Expense Report stuck in MarkView SQLFLOW/MarkView Initialize node within the Oracle Workflow

Summary

4021

Applies To

  • ERP System: Oracle
  • MarkView Version: All versions

Behavior

  • Any of the following issues may occur with MarkView Expense Management for Oracle.
    • Problem 1:
      After the employee submits an Expense Report, then withdraws, updates & resubmits it, the workflow does not move from the SQL*Flow Initialize stage.
    • Problem 2:
      1. Employee: submits iExpense
      2. Employee faxes in receipts
      3. Manager rejects iExpense
      4. Employee resubmits iExpense
      5. Employee faxes in revised receipts
      6. At this point, the iExpense should move back to the Manager for re-approval but it does not. Instead, in MarkView it remains in OIE Awaiting Approval and in the Oracle Workflow it remains in SQL*Flow Initialize.
    • Problem 3:
      Expense Reports remain in "Kofax SQLFLOW_Initialize" activity in Oracle Workflow.

Known Causes

  • The known causes for each of the problems described is given below:
    • Problem 1:
      The problem is caused by an incorrect "ResubmittedQueue" rule parameter for the "OIE Workflow Flag Changed" rule on the "OIE Awaiting Receipt Images" queue in the "OIE Expense Reports" workflow. It is set to "OIE Awaiting Approval" but needs to be set to "OIE Awaiting Receipt Images".
    • Problem 2:
      The problem is caused by an incorrect "ResubmittedQueue" rule parameter for the "OIE Workflow Flag Changed" rule on the "OIE Rejected Expense Reports" queue in the "OIE Expense Reports" workflow. It is set to "OIE Awaiting Approval" but needs to be set to "OIE Awaiting Receipt Images".
    • Problem 3:
      This can occur if the modes of certain OIE events are not set for synchronous processing. Incorrectly set OIE event modes can affect any version of MarkView Expense Management for Oracle Applications versions.

Resolution

  • The following steps need to be taken to resolve each of the issues described:
    • Resolution for problem 1:
      Run the attached fix_17620.sql which will correct this "ResubmittedQueue" rule parameter from "OIE Awaiting Approval" to "OIE Awaiting Receipt Images". It will prevent this issue from occurring again.
    • Resolution for problem 2:
      Run the attached fix_17620b.sql to correct this issue.
  • The above fixes will only resolve future Expense Reports in the Workflow. To workaround the existing items stalled in SQL*Flow Initialize, simply resubmit the expense report which has a status of withdrawn then run the following in the MarkView schema:
    For pre-6.x releases of MarkView Expense Management:
    exec MVOA_OIE_Expense_Reports.ContinueOracleWorkflow(ReportHeaderId => &StalledReportHeaderId);
    e.g. : exec MVOA_OIE_Expense_Reports.ContinueOracleWorkflow(ReportHeaderId => 39223);

    For 6.x and later releases of MarkView Expense Management:
    exec MVERP_Expense_Report.ReleaseExpenseReport(ReportHeaderId => &StalledReportHeaderId);
    e.g. : exec MVERP_Expense_Report.ReleaseExpenseReport(ReportHeaderId => 39223);
    • Resolution for problem 3:
      The following update statement sets the appropriate events to Synchronous:
      update sf_event_type et
      set et.event_mode = 'S'
      where et.event_name in ('OIEDuplicateWorkItem','OIEReceiptsAttached','OIEReportDeleted',
      'OIERetryReceiptMatch','OIEWorkflowFlagChanged');
      commit;

Notes.

It is the recommended policy of Kofax, Inc. that all system changes be applied in the customer's test environment and tested thoroughly before being migrated to a production environment.

These are workarounds and potential fixes that can be used resolve the issues described above. They are not official Product Development patches.

Keywords: iExpense, OIE, synch, asynch