# SAP Document Info Record Template for DMS and Engineering Documents

> Source: https://netray.co/tools/sap-document-info-record-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Capture the key fields of a document info record before entering it in CV01N, with links to material, BOM and change number.

## Category

engineering-plm

## Erp

SAP S/4HANA

## Audience

- Document controller
- PLM engineer
- SAP DMS consultant

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company or plant

**Key:** company

**Type:** text

**Default:** Acme Pumps Ltd, Plant 1000

#### Document type

**Key:** doc_type

**Type:** text

**Default:** DRW

#### Document number

**Key:** doc_number

**Type:** text

**Default:** DRW-0048213

#### Document part

**Key:** doc_part

**Type:** text

**Default:** 000

#### Document version

**Key:** doc_version

**Type:** text

**Default:** 01

#### Description

**Key:** title

**Type:** text

**Default:** Pump body machining drawing

#### Document status

**Key:** status

**Type:** select

**Options:**

- In work
- In review
- Released
- Obsolete

**Default:** In work

#### Linked material

**Key:** material

**Type:** text

**Default:** PUMP-BODY-100

#### Change number

**Key:** change_no

**Type:** text

**Default:** ECN-2026-0142

#### Original file

**Key:** file_name

**Type:** text

**Default:** pump_body_100_revB.pdf

#### Responsible person

**Key:** author

**Type:** text

**Default:** A. Engineer

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-19

#### Remarks

**Key:** remarks

**Type:** textarea

**Default:** Revised bore tolerance. Supersedes previous version once the change number is released.

**Blocks:**

#### Document Info Record Request

**Body:** Organization: {{company}}
Prepared by: {{author}}
Date: {{date}}

#### Document key

**Table:**

**Columns:**

- Field
- Value

**Rows:**

**0:** Document type

**1:** {{doc_type}}

**0:** Document number

**1:** {{doc_number}}

**0:** Document part

**1:** {{doc_part}}

**0:** Document version

**1:** {{doc_version}}

#### Header data

**Table:**

**Columns:**

- Field
- Value

**Rows:**

**0:** Description

**1:** {{title}}

**0:** Status

**1:** {{status}}

**0:** Responsible person

**1:** {{author}}

**0:** Change number

**1:** {{change_no}}

#### Original application file

**Body:** File name: {{file_name}}
Storage: content server or vault as defined for the document type
The file must be checked in before the status is set to Released.

#### Object links

**Table:**

**Columns:**

- Linked object
- Object key
- Purpose

**Rows:**

**0:** Material

**1:** {{material}}

**2:** Drawing for the part

**0:** BOM or routing

**2:** Where the document is referenced

**0:** Change master

**1:** {{change_no}}

**2:** Revision control

#### Remarks

**Body:** {{remarks}}

#### Approvals

**Signatures:**

- Author
- Reviewer
- Document controller

**Notes:** This is a planning form. A document info record is created in SAP in CV01N (change CV02N, display CV03N), and the available fields, document types, status values and storage categories depend on your configuration. Confirm the key format with your DMS administrator.

## Content

**Intro:** A document info record, often called a DIR, is the SAP object that represents a drawing, specification or other controlled file. Use this template to collect the data you need before entering it, then export it as a request form or checklist for your document control team.

**Sections:**

#### How to use the template

**Body:** Fill in the document key, the description and the status, then name the original file and the objects it should link to. The preview becomes a clean document you can export as PDF or Word and hand to document control, or attach to a change record. Use it when engineers request new documents or new versions so that the information arrives complete and in the same format each time.

**Bullets:**

- Always give the part and version explicitly
- Name the file before check-in so naming rules are applied
- Add a change number whenever a controlled structure is affected

#### The key of a document info record

**Body:** In SAP document management, a document is identified by four fields: document type, document number, document part and document version. The type groups documents by purpose, such as drawings or specifications, and controls number ranges, status flow and storage settings. Part is used to split a document into sections. Version marks revisions. Together they form the key you see in CV01N, CV02N and CV03N. Choosing a clear numbering pattern at the start saves a great deal of confusion later.

**Bullets:**

- Document type: defined in configuration, customer specific except for standard examples
- Document number: internal or external numbering depending on type
- Part and version: support splitting and revisions

#### Links, status and files

**Body:** A DIR gains value when it is linked. Documents can be linked to material masters, BOM items, equipment and other objects, so users find the right drawing from the part they are working on. Status values control who can change or release a document, and the original application file is stored in a content repository or vault. Many sites require the status to move through an approval before it is visible to production. Record the intended link targets in the template so nothing is left standing alone.

#### Common mistakes

**Body:** Common problems are documents created without a link, so nobody finds them; files stored outside the repository on a shared drive; versions created in place of a controlled revision with a change number; and statuses set to released before the file is attached. Another problem is each engineer inventing their own numbering. A standard request form removes most of these and gives the document controller what they need on the first try.

**Cta:** If you manage thousands of drawings across SAP and file shares, we can discuss tooling that cross-checks DIR links and files on your own infrastructure. This template does not require it.

**Faq:**

#### Which transactions handle document info records?

**Answer:** CV01N creates a document info record, CV02N changes it and CV03N displays it. Related functions for searching and checking in files are available from the document management menu, depending on your release and configuration.

#### What is a document type in SAP?

**Answer:** A document type classifies documents, for example drawings or specifications, and controls numbering, status network, storage and workflow. Types are defined in configuration, so the list is specific to your company. DRW is commonly seen as a drawing type but you must check yours.

#### Why do documents need a version?

**Answer:** Versions let you keep earlier revisions while working on a new one, and with a change number you can show which version applied when. Overwriting a file without versioning loses that history.

#### Can one document link to many materials?

**Answer:** Yes. A single document, such as a standard specification, can be linked to many materials, BOMs or other objects. Check the allowed object links for your document type.

## Search terms

sap document info record template, sap dms document info record, cv01n create document, sap document type version part, sap drawing document info record, dir sap fields, sap document management form, sap document status template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json