SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

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

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.

Download:

Status	Object	Meaning	Set by	Effect
CRTD	Order	Created	Saving a new order	Order can be planned but goods issue and confirmation are not allowed
REL	Order	Released	Release of the order	Allows goods issue, confirmation and printing of shop papers
PREL	Order	Partially released	Release of selected operations	Only released operations can be confirmed
PCNF	Order	Partially confirmed	Confirming some operations or part of the work	Order is in progress, still open for confirmation
CNF	Order	Confirmed	Final confirmation of all operations	Order is ready for technical completion
TECO	Order	Technically completed	Planner or technician completes the order	Stops further execution and can trigger final cost calculation inputs
CLSD	Order	Closed	Business completion after settlement	No more postings or changes, settlement is done
DLFL	Order	Deletion flag	User marks order for deletion	Order is a candidate for archiving, no new postings
DLT	Order	Deletion indicator	Archiving preparation	Order is ready for archiving or deletion
PRT	Order	Printed	Shop papers printed	Information only
NMAT	Order	Material availability not checked	Order creation with availability check on	Informs planner a check is still pending
SETC	Order	Settlement rule created	Creating or generating the settlement rule	Order can be settled
GMPS	Order	Goods movement posted	Posting a goods movement to the order	Material consumption exists on the order
DLV	Order	Delivered	Final goods receipt for the order object	Used by orders that produce material
OSNO	Notification	Outstanding notification	Creating a notification	Notification is open and not yet being worked
NOPR	Notification	Notification in process	Starting processing or linking an order	Work is under way
NOCO	Notification	Notification completed	Completing the notification	No more changes except by reactivation
ORAS	Notification	Order assigned	Creating an order from the notification	Notification is linked to an order
DLFL	Notification	Deletion flag	User marks notification for deletion	Candidate for archiving
MOFN	Notification	Notification has outstanding tasks	Open tasks exist on the notification	Information for the planner

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.

Order backlog cleanup plan

Optional: share how many TECO and open orders you carry and we will suggest a closing rule.

Optional. The tool and every export work without this. No spam.

How to use the status list

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

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.

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

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.

Frequently Asked Questions

What does TECO mean in SAP PM?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools