logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.48.3

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland

Status

Algorithm v2.48.3

Tool profile

SAP NetWeaver 750

SAP NetWeaver 750 appears on both unmodified and modified documents in our corpus. The name alone is never the verdict; each file is judged on its own structure.

Back to all statistics
Forensic verdict

Mixed signal

Based on this tool’s share of the HTPBE? corpus.

Modification rate
82%+33pp above baseline
Corpus baseline: 49%
Corpus share
0.12%
Share of all analyzed appearances
Modification rate
82%
+33pp above baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How SAP NetWeaver 750 shows up in HTPBE? corpus

SAP NetWeaver 750 is one of the PDF-handling tools surfaced in the HTPBE? corpus. SAP NetWeaver 750 appears predominantly as the Producer (100% of its occurrences) — i.e. on documents whose original Creator was a different application and that subsequently passed through SAP NetWeaver 750 on the way out.

HTPBE? reads the SAP NetWeaver 750 name as one input among many and weighs it together with the rest of the file’s structure – the tool itself is never the accusation.

On documents where SAP NetWeaver 750 acts as Creator, 0% carry modification markers; on documents where it acts as Producer, 82% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against SAP NetWeaver 750 or its users.

The signal
HTPBE? reads the SAP NetWeaver 750 name as one input among many and weighs it together with the rest of the file’s structure – the tool itself is never the accusation.

Reading guide

How to read this page

Every PDF stores two software labels: the Creator, which names the application that first produced the document, and the Producer, which names the software that last wrote the file out. This page counts the files HTPBE? has analysed where SAP NetWeaver 750 fills one of those labels, and shows how often those files carry modification markers, which PDF versions they use and which other tools sit next to them.

A tool name tells you where a file passed through, not whether anyone changed its content. A Creator and Producer that agree usually point to a single pass; a Producer that differs from the Creator means the file was written out again by another program, which has many ordinary explanations such as compression, merging or a print-to-PDF step.

Caveats

  • The figures cover 33 files. Larger than a handful, but still a sample of what was submitted, not of all PDFs in the world.
  • The statistics describe files HTPBE? analysed. They are not a judgement of the quality or trustworthiness of SAP NetWeaver 750.
  • Submitted files lean towards documents that someone wanted checked, so rates here can sit higher than in everyday document flows.
  • Metadata can be rewritten by anyone, so a producer name on its own is never treated as proof either way.
Read a PDF’s metadata for freeAll tool statisticsCreator vs Producer explainedPDF metadata fields referenceCheck PDFs through the API

Role in the workflow

How SAP NetWeaver 750 shows up in metadata

Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.

CAs Creator · 0%
As Producer · 100%P
CAs Creator
  • Share of appearances
    0%
  • Modification rate
    0%
PAs Producer
  • Share of appearances
    100%
  • Modification rate
    82%
  • Avg file size
    51 KB

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the final file, which is not always the same software.

A higher modification rate as Producer than as Creator usually means the tool is acting as a re-saver on documents that originated elsewhere. A higher rate as Creator points to fragile workflows around the original authoring app.

Distributions

What ships alongside SAP NetWeaver 750

The PDF versions SAP NetWeaver 750 writes when acting as Producer, and the other tools that appear in the same documents.

PDF versions written

Most output is PDF 1.7 (48% of files where SAP NetWeaver 750 is the Producer).

PDF 1.748.5%
PDF 1.627.3%
PDF 1.324.2%

Common Creators when SAP NetWeaver 750 is the Producer

Form X_65_80 EN sits upstream in 94% of cases — read this row as “what kinds of documents end up routed through SAP NetWeaver 750.”

Form X_65_80 EN93.5%
Form ZPYXXFO_ZTP_PAYSLIP_CA EN3.2%
SAPPY3.2%

Related profiles

Tools you’ll see next to SAP NetWeaver 750

Other tools that frequently share metadata with SAP NetWeaver 750 in the same documents. Each card links to its own forensic profile.

C88% co-occurrence
Form X_65_80 EN
Corpus share0.10%
Mod rate79%
C3% co-occurrence
Form ZPYXXFO_ZTP_PAYSLIP_CA EN
Corpus share<0.01%
Mod rate100%
C3% co-occurrence
SAPPY
Corpus share<0.01%
Mod rate100%

Long tail

Notable observations

Smaller cuts of the SAP NetWeaver 750 corpus – useful context, but treat each row as a single data point rather than a strong signal.

Embedded files
3%

Of files have attachments inside

Avg pages per document
1.0
Oldest observed
03.03.2026 — 8 months ago

FAQ

SAP NetWeaver 750 in PDF metadata: common questions

What is SAP NetWeaver 750?

SAP NetWeaver 750 is a PDF-handling tool that writes its name into the Creator or Producer field of the PDFs it generates or re-saves.

Why does SAP NetWeaver 750 appear in the metadata of a PDF?

A PDF can record the software that created it (Creator) and the software that last wrote the file out (Producer). When SAP NetWeaver 750 generated the file, or re-saved it, it can leave its name in one of those fields. The field is filled in by software, not checked by anyone, so it is a hint about the file’s history rather than a guarantee.

Does SAP NetWeaver 750 in the metadata mean the PDF was edited?

No. A producer name alone proves nothing about whether a document was changed. Many SAP NetWeaver 750 files are original output, and a file that was edited can name any tool at all. What matters is the whole picture: how the file is built, how its dates and structure line up, and whether the Creator and Producer fit together.

How should I read the SAP NetWeaver 750 statistics?

The figures describe the 33 files in the HTPBE? corpus that list SAP NetWeaver 750 as Creator or Producer. The modification rate is the share of those files that carry modification markers. It is a base rate for this particular set of files, not a property of SAP NetWeaver 750 and not a prediction for any single document.

Can I compare SAP NetWeaver 750 with other tools using these numbers?

Only loosely. The corpus consists of PDFs people chose to submit for checking, which skews towards documents someone had a reason to doubt. A tool popular for legitimate bulk output can still show a high rate here, and a rarely seen tool can show an extreme rate from a handful of files. These pages are not a quality ranking of the tools themselves.

How do I check a PDF that lists SAP NetWeaver 750?

Upload it to HTPBE? for a modification check, or open it in the free PDF Metadata Viewer to see the Creator, Producer and dates stored in the file. The same check is available through the HTPBE? API.

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.

Start Free – Close the Structural Fraud GapSee Pricing
Read API Docs →