Extended ECM seat counting traps for SAP integrations

Extended ECM is built to live inside other applications, and the application it most often lives inside is SAP. That tight integration is exactly what makes Extended ECM seat counting so easy to get wrong, because an audit can count the entire population of the connected application as Extended ECM users.

The product earns its value by putting content management directly into the business application, so the people who touch content are the people already working in SAP. The trap is that an audit may treat every one of those people as a chargeable Extended ECM seat, even those whose contact with content is incidental, indirect, or routed through the integration rather than direct use of the content platform.

Why SAP integration inflates the seat count

When Extended ECM is integrated with SAP, content actions are surfaced inside SAP transactions. A user completing a business process in SAP may cause a document to be stored, retrieved, or linked without ever opening an Extended ECM interface directly. Because the integration authenticates and acts in the content platform, an audit can attribute that activity to the SAP user and count them as an Extended ECM seat. Multiply that across an SAP user base and the seat count can balloon far beyond the people who actually work with the content platform as a tool.

This is the indirect access problem in an ECM setting. The question is whether a person who interacts with content only through another application, in the course of work they are already licensed for there, is a direct Extended ECM user at all. How integration driven activity is attributed is closely related to how Documentum API and integration users are counted.

The specific seat traps

Counting the whole SAP population

The broadest trap is treating every SAP user with any path to content as an Extended ECM seat. The defensible count is the population that genuinely uses the content platform, not everyone the integration could in theory touch.

Integration service identities

The connector between SAP and Extended ECM runs through service identities. As with any integration, those credentials are infrastructure, not users, and should not be counted as seats.

Metric mismatch with the content platform

Extended ECM and the underlying content platform may carry different metrics, and an audit can apply the wrong one to integration users. Understanding the distinctions matters, which is why we set them out in Extended ECM versus Documentum licensing differences and in Content Suite license metrics and where audits overcharge.

Defending the count under the four Rs

Respond. In the seven day notice window we control the channel so an export of the SAP user base does not become the agreed Extended ECM seat count. The breadth of the integration makes this first step especially important.

Reconstruct. We build the effective license position independently by separating direct content platform users from people whose only contact with content is incidental and routed through SAP. We map the integration service identities out of the population and align each remaining user to the correct metric. The documentation approach mirrors how to document Documentum named users for a rebuttal.

Rebut. We challenge the indirect attribution directly: a person working in SAP under their SAP license, who only triggers a content action as a byproduct, is not a direct Extended ECM seat. Each contested seat is supported by evidence of how the person actually interacts with content.

Resolve. We settle on the corrected seat count and, where it serves you, convert forward into an OpenPass agreement that defines how integration users are treated so the indirect access question cannot reopen at renewal.

Why the correction matters

The leverage here is unusually large because the inflation is structural. When the seat count is drawn from an entire SAP population, the gap between that figure and the genuine content platform user base can be enormous, and the remedy multiplies the gap through list price, back maintenance, and audit cost recovery. The same discipline that reduced our anonymised Documentum insurance finding, case file E-01, from $7.2M to $1.6M, a 78 percent reduction, applies to Extended ECM: count the people who actually use the content platform, not everyone the integration can reach.

The indirect access question at the heart of the trap

Extended ECM seat counting is really a particular form of the indirect access problem, the question of whether someone who reaches a product only through another application is a user of that product at all. In the SAP context the question is sharp because the whole point of the integration is to let people work with content without leaving SAP. The better they are served by the integration, the less they look like direct content platform users, and yet the audit may count them most aggressively precisely because their activity touches content.

The defensible position turns on the nature of the interaction. A person who opens the content platform, navigates it, and works with documents as a tool is a direct user. A person who completes an SAP transaction that happens to file or retrieve a document as a byproduct is exercising their SAP license, and the content action is incidental to work they are already entitled to do. Drawing that line carefully, user by user, is what separates a genuine content platform population from an inflated one.

Evidence is again decisive. To contest an indirect seat, you show how the person actually interacts with content: whether they ever use a content platform interface directly, whether their activity is confined to SAP transactions, and how the integration attributes that activity. Where the record shows only incidental, integration mediated contact, the case that the person is not a direct Extended ECM seat is strong and grounded in fact rather than assertion.

Because the inflation in these integrations is structural rather than incidental, the correction is often the largest single item in an Extended ECM finding. Settling the indirect access question on the buyer terms, and writing the treatment of integration users into a forward agreement, removes both the immediate charge and the risk that the same population is recounted at the next renewal.

Where to go next

For the broader method behind an ECM finding, read our complete OpenText audit defense playbook for 2026 and our ECM and Documentum audit defense track. If your Extended ECM seat count was drawn from your SAP user base, open a case and we will rebuild the count to genuine content platform users.