US food manufacturer SAP indirect access. Eighty nine percent exposure reduction.

A leading US food manufacturer received an SAP indirect access claim large enough to require board attention. The number came from SAP's measurement of documents created in the system by the company's surrounding applications.

Indirect access is the licensing question that catches manufacturers hardest. Warehouse systems, plant equipment, EDI links to retailers and supplier portals all write into SAP continuously, and none of them is a person with a named user licence.

The claim fell by 89 percent. Not through a contractual argument, and not through a settlement purchase. The count was simply rebuilt to include only what the licence model actually charges for.

See the SAP advisory practice, the SAP audit defense service, and the SAP digital access licensing notes.

What SAP actually charges for

Under the digital access model, SAP charges for the initial creation of a document in SAP by something other than a licensed human user. That sentence contains three separate limits, and each one removes volume from a raw count.

Initial creation. The document counts once, when it is created. Later updates to the same document are not separate chargeable events.

Documents, not line items. A sales order with two hundred lines is one document. Counting lines rather than documents inflates a manufacturing estate enormously.

By an external system. A document raised by a properly licensed SAP user is covered by that user's licence, even when a system helped create it.

What was counted	What is actually chargeable	Effect on the claim
Every document the integrations touched	Only documents the integrations created	Removed updates and reads
Every line item on every document	One count per document	Largest single reduction on a manufacturing estate
Documents raised by licensed SAP users	Only documents raised by external systems	Removed a substantial internal volume
Document types outside the chargeable nine	Only the nine defined document types	Removed categories that were never in scope

The nine document types

SAP defines a specific set of chargeable document types, and anything outside that set does not belong in a digital access claim.

They cover sales orders, invoices, purchase orders, service and maintenance documents, manufacturing documents, quality management documents, time management documents, material documents and financial documents.

For a food manufacturer, manufacturing and material documents dominate the volume, which is precisely why the line item distinction mattered so much here. Production activity generates a very high line count against a much smaller document count.

Mapping the integration landscape

You cannot argue a digital access claim without knowing what writes into your SAP system. Most organizations discover their own integration landscape during the audit, which is far too late.

We rebuilt it from the middleware logs, the interface inventory, and the system documentation the integration team already maintained for operational reasons.

That exercise answered the question SAP could not: for each interface, does it create documents, update them, or only read them. Only the first category generates a charge.

Where the exposure actually came from

Split by cause, the claim resolved into four correctable components rather than one large number.

• Updates counted as creations. Status changes flowing back from warehouse and logistics systems, each counted as a new document.
• Line items counted as documents. The single largest component, given the production volumes involved.
• Internally created documents. Raised by licensed users working through an interface, and therefore already covered.
• Out of scope types. Records that are not among the nine chargeable document types.

See the SAP audit defense framework for the full method.

The response

Acknowledge, scope, evidence, close. The order matters more than the speed.

1. Acknowledge without data. Confirm receipt, agree a timeline, and send nothing else.
2. Scope in writing. Which systems, which entities, which periods, agreed before any extract is produced.
3. Evidence interface by interface. Answer with the integration map and the creation logic for each one.
4. Close the corrected position. Then document the counting rule so it holds at the next measurement.

Where the common advice on SAP indirect access is wrong

The common advice is to treat an indirect access claim as a contractual dispute and to argue about what the agreement permits. We disagree, because that argument is slow, expensive and usually unnecessary. In every claim we have rebuilt, the decisive issue was not what the contract said but what the number counted. Updates counted as creations, line items counted as documents, and internally raised documents counted as external ones will between them inflate a claim several times over before anyone reaches a question of interpretation. Fix the arithmetic first. If a genuine contractual disagreement remains after that, it will be a much smaller one, and you will be arguing it from a position built on your own evidence rather than the vendor's.

The eleven moves

These are the moves that removed the claim. The first four did nearly all of it.

1. Separate creation from update. Only initial creation is chargeable.
2. Count documents, not line items. On a manufacturing estate this is usually the largest correction available.
3. Exclude documents raised by licensed users. Their licence already covers the activity.
4. Restrict the count to the nine chargeable document types. Anything else is out of scope.
5. Map every interface that writes to SAP. With its creation logic documented.
6. Use your own middleware logs. They are better evidence than any extract produced under time pressure.
7. Scope the audit in writing before producing data.
8. Answer interface by interface. Not claim total against claim total.
9. Keep the renewal conversation separate. An audit framed as a migration discussion is a commercial exercise.
10. Document the counting rule. So the next measurement starts correct.
11. Re measure annually for yourself. Integration landscapes change faster than licence positions.

What to do next

If indirect access is a live question for you, start here.

1. Draw the integration map: every system that writes into SAP, and whether it creates, updates or only reads.
2. Separate document creation from document update in your own logs before anyone asks you to.
3. Count documents rather than line items, and check which side your current reporting uses.
4. Identify documents raised by licensed users through an interface, and exclude them from any external count.
5. Check every category against the nine chargeable document types and drop anything outside them.
6. Write the counting rule down and apply it at every annual measurement from now on.

How we engage

• SAP audit scoping. Six week engagement. SAP advisory practice.
• SAP audit response. Audit response engagement. SAP audit defense service.
• SAP renewal negotiation. Renewal negotiation alongside the audit cycle. SAP contract negotiation service.
• SAP digital access advisory. Document counting rules, integration mapping, and the conversion question. SAP digital access licensing.
• Vendor Shield. Vendor Shield.
• Run the calculator. The audit defense readiness checklist.