cancel
Showing results for 
Search instead for 
Did you mean: 

VIM 7.5 ECC – MRKO Posting Does Not Finalize DP Workflow (BUS_OBJTYPE / BUS_OBJKEY Missing)

03-27-2026 6:28 PM
Maria_Boal Newcomer
514 views 1 comments
0 Likes
SAP Managed Tags
Subscribe

Hello everyone,

I’m currently working on an issue in SAP ECC with OpenText VIM 7.5, related to MRKO posting and VIM Document Processing (DP) workflow finalization, and I’m looking for guidance or best practices from anyone who has faced a similar scenario.

System Context

  • SAP ECC
  • OpenText VIM 7.5
  • Invoice processing uses VIM DP with workflow
  • Posting is done via MRKO (consignment settlement) rather than MIRO

Current Design

  • The VIM workflow starts correctly.
  • The posting step uses a custom copy of /OPT/VIM_52_BAPI_DOCLINES_PO.
  • Inside this copy, MRKO is executed via SUBMIT.
  • MRKO successfully creates the FI document (BELNR / BUKRS / GJAHR).

Issue / Symptoms

After the FI document is created:

  • The workflow remains active in SWIA and is not completed.
  • VIM Analytics loses the workflow association.
  • In the workflow container, BUS_OBJTYPE and BUS_OBJKEY are empty.

Root Cause (Analysis So Far)

From our investigation, the problem does not seem to be MRKO itself, but how it is executed:

  • MRKO is triggered outside of VIM’s standard DP posting framework.
  • As a result, DP is never finalized.
  • VIM is not informed of the created FI document.
  • BOR linkage is missing, so the workflow cannot bind to the posted document and close properly.

Has anyone come across this situation when using MRKO with VIM DP? What is the recommended or supported way to correctly finalize DP and close the workflow in this scenario? Are there specific VIM classes or methods that should be used to link the FI document back to the DP document? Any advice or experience would be greatly appreciated.

Thank you!

0 Likes

Accepted Solutions (0)

Answers (1)

Answers (1)

Lakshmipathi
Active Contributor
0 Likes

SAP/OpenText do not support bypassing VIM’s posting framework. If you need MRKO, you must wrap it inside VIM’s posting classes so the DP document is updated and workflow closed. Otherwise, you will always end up with active workflows and broken analytics.
Having said that, the fix is not in MRKO itself, but in ensuring VIM’s DP finalization logic runs after MRKO. You need to call the VIM posting APIs to update BUS_OBJTYPE/KEY and close the workflow.