# SAP PM Order and Notification Status Codes (CRTD, REL, TECO, CLSD, OSNO)

> Source: https://netray.co/tools/sap-pm-status-codes-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A lookup of SAP PM system statuses with what each means, what sets it and what it blocks.

## Category

sap

## Erp

SAP ECC / S/4HANA

## Audience

- SAP PM consultant
- Maintenance planner
- ABAP developer

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Status

**Key:** code

**Type:** text

#### Object

**Key:** object

**Type:** text

#### Meaning

**Key:** meaning

**Type:** text

#### Set by

**Key:** set_by

**Type:** text

#### Effect

**Key:** effect

**Type:** text

**Rows:**

**Code:** CRTD

**Object:** Order

**Meaning:** Created

**Set by:** Saving a new order

**Effect:** Order can be planned but goods issue and confirmation are not allowed

**Code:** REL

**Object:** Order

**Meaning:** Released

**Set by:** Release of the order

**Effect:** Allows goods issue, confirmation and printing of shop papers

**Code:** PREL

**Object:** Order

**Meaning:** Partially released

**Set by:** Release of selected operations

**Effect:** Only released operations can be confirmed

**Code:** PCNF

**Object:** Order

**Meaning:** Partially confirmed

**Set by:** Confirming some operations or part of the work

**Effect:** Order is in progress, still open for confirmation

**Code:** CNF

**Object:** Order

**Meaning:** Confirmed

**Set by:** Final confirmation of all operations

**Effect:** Order is ready for technical completion

**Code:** TECO

**Object:** Order

**Meaning:** Technically completed

**Set by:** Planner or technician completes the order

**Effect:** Stops further execution and can trigger final cost calculation inputs

**Code:** CLSD

**Object:** Order

**Meaning:** Closed

**Set by:** Business completion after settlement

**Effect:** No more postings or changes, settlement is done

**Code:** DLFL

**Object:** Order

**Meaning:** Deletion flag

**Set by:** User marks order for deletion

**Effect:** Order is a candidate for archiving, no new postings

**Code:** DLT

**Object:** Order

**Meaning:** Deletion indicator

**Set by:** Archiving preparation

**Effect:** Order is ready for archiving or deletion

**Code:** PRT

**Object:** Order

**Meaning:** Printed

**Set by:** Shop papers printed

**Effect:** Information only

**Code:** NMAT

**Object:** Order

**Meaning:** Material availability not checked

**Set by:** Order creation with availability check on

**Effect:** Informs planner a check is still pending

**Code:** SETC

**Object:** Order

**Meaning:** Settlement rule created

**Set by:** Creating or generating the settlement rule

**Effect:** Order can be settled

**Code:** GMPS

**Object:** Order

**Meaning:** Goods movement posted

**Set by:** Posting a goods movement to the order

**Effect:** Material consumption exists on the order

**Code:** DLV

**Object:** Order

**Meaning:** Delivered

**Set by:** Final goods receipt for the order object

**Effect:** Used by orders that produce material

**Code:** OSNO

**Object:** Notification

**Meaning:** Outstanding notification

**Set by:** Creating a notification

**Effect:** Notification is open and not yet being worked

**Code:** NOPR

**Object:** Notification

**Meaning:** Notification in process

**Set by:** Starting processing or linking an order

**Effect:** Work is under way

**Code:** NOCO

**Object:** Notification

**Meaning:** Notification completed

**Set by:** Completing the notification

**Effect:** No more changes except by reactivation

**Code:** ORAS

**Object:** Notification

**Meaning:** Order assigned

**Set by:** Creating an order from the notification

**Effect:** Notification is linked to an order

**Code:** DLFL

**Object:** Notification

**Meaning:** Deletion flag

**Set by:** User marks notification for deletion

**Effect:** Candidate for archiving

**Code:** MOFN

**Object:** Notification

**Meaning:** Notification has outstanding tasks

**Set by:** Open tasks exist on the notification

**Effect:** Information for the planner

**Notes:** Statuses are stored in table JEST with the object number OBJNR, and texts in TJ02T. Some statuses also depend on your order type customizing and on any user status profile assigned to the object. The internal code for TECO is I0045 and for CLSD is I0046.

## Content

**Intro:** Every SAP maintenance order and notification carries one or more system statuses. Knowing exactly what REL, TECO or CLSD allow or block saves hours of debugging when a goods issue or settlement is refused.

**Sections:**

#### How to use the status list

**Body:** Search a four letter code or a phrase from an error message such as not released or technically completed. The Object column separates order statuses from notification statuses, because DLFL appears on both. The Effect column tells you what the status allows. If a user cannot post a goods issue, check whether the order is still CRTD; if settlement fails, check whether it has the SETC status and whether TECO was set first.

#### The normal order lifecycle

**Body:** A typical corrective order goes CRTD, REL, PCNF, CNF, TECO and finally CLSD. Release is the gate for execution. TECO ends work and typically locks further confirmation, and CLSD is the final business closure after settlement. Many plants skip CLSD for months, leaving a pile of TECO orders open, which hurts cost reporting and makes selection lists noisy. Agree a clear rule for who sets CLSD and when, and automate it in a scheduled run.

**Bullets:**

- REL is required for confirmation and goods issue
- TECO is not the same as closed: costs can still settle
- CLSD should follow settlement, not precede it

#### Using statuses in reports and user status profiles

**Body:** In ABAP and SQL, filter out finished work with a NOT EXISTS against JEST for TECO and CLSD, as in the open order query tool. Always check INACT is blank, because deactivated status rows stay in the table. If your plant needs steps SAP does not model, such as waiting for permit or waiting for parts, use a user status profile assigned to the order type. User statuses are stored in the same JEST table but with codes that start with E and a profile name from JSTO.

**Cta:** If your planners track waiting-for-parts or permit states in spreadsheets, we can help design a user status profile and a read-only dashboard over it.

**Faq:**

#### What does TECO mean in SAP PM?

**Answer:** TECO is technically completed. It marks that the physical work is finished and stops further operations or confirmations. It does not close the order commercially: costs can still be settled, and the order is later set to closed once settlement is done.

#### Can I reverse TECO?

**Answer:** Yes, in most configurations you can reset the technical completion status through the order change transaction before the order is closed, which allows more postings. Once the order is CLSD, you normally need to reset the closed status first, subject to authorization.

#### Why can't I confirm a maintenance order?

**Answer:** The usual reasons are that the order is still CRTD and not released, that it is already TECO or CLSD, or that the operation has a control key that does not allow confirmation. Check the status line of the order and the operation control key.

#### Where do I find the status text for I0045?

**Answer:** System status texts are in table TJ02T. The internal code I0045 corresponds to TECO and I0046 to CLSD. In a report, join JEST to TJ02T on STAT = ISTAT and the language key to show the text instead of the internal code.

## Search terms

sap pm order status, sap teco status meaning, sap crtd rel pcnf cnf, sap notification status osno nopr noco, sap system status list, jest status i0045, sap pm order status flow, sap pm user status

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