SAP Production Order Technically Complete (TECO): Set and Reverse in CO02
SAP CO02 technically complete TECO production order reverse how to
Also searched as
- how to reset TECO status production order SAP
- SAP production order TECO vs CLSD
- difference technically complete and business complete SAP
- SAP production order cannot post goods movement TECO
Short answer
TECO (technically complete) stops further goods movements and confirmations on a production order and removes open reservations and capacity requirements. Set it in CO02 under Functions > Restrict Processing > Technically Complete, and reverse it with Reset Technically Complete when the order still needs postings. CLSD, the business close, is a separate step that comes after settlement.
Applies to: SAP ECC 6.0 and SAP S/4HANA, discrete production orders and process orders. Behaviour of reversing TECO depends on release and order status.
How to set and reset TECO in CO02
- 1Open CO02 (Change Production Order) and enter the order number. For many orders use COHV mass processing and the TECO mass function instead.
- 2Check the status first through Goto > Header > Status, or the Status field. You want REL, PCNF or CNF, and no open goods movements you still intend to post.
- 3Choose Functions > Restrict Processing > Technically Complete. Save the order. The system sets the TECO status.
- 4To reverse, open CO02 for the same order and choose Functions > Restrict Processing > Reset Technically Complete, then save.
- 5If the reset is not offered, check whether the order has been business-closed (CLSD), archived or flagged for deletion. Those cannot be reset the same way.
- 6After resetting, post the missing confirmation in CO11N or goods movement in MIGO against the order, then set TECO again.
- 7Run the settlement (KO88 for a single order or CO88 for collective) and variance calculation before moving to business close.
- 8Use the Business Completion function in CO02 (Functions > Complete) only after settlement, so the order reaches CLSD.
What TECO does and what it does not do
Setting TECO is a statement that nothing more will happen on the order from a production point of view. Open reservations for components not yet issued are deleted, open capacity requirements are removed, and the order no longer appears in MRP as future supply for the remaining open quantity. Further goods issues, goods receipts and confirmations against the order are blocked.
TECO does not settle costs, does not calculate variances by itself, and does not stop the order from being changed in some master data aspects. Cost still sits on the order until you run variance calculation and settlement. This is why finance often asks for TECO as a trigger: it tells cost accounting that the quantities are final so WIP can be released and variances posted at period close.
TECO versus business completion (CLSD)
CLSD, set through the business completion function, is the final status. It is only allowed once costs are settled, and it prevents further settlement or changes from the controlling side. Think of TECO as the production signal and CLSD as the finance signal. An order can be TECO for weeks while accountants finish settling and then be moved to CLSD at period close.
A common practice is to run COHV regularly to set TECO on orders whose last confirmation is older than a policy threshold, for example orders that are fully delivered (status DLV) and have no postings for a set number of days. Keep the policy in the shop-floor procedure, not only in the job, so planners know why an order they still wanted to use has been closed.
Reversing TECO safely
Resetting TECO is allowed from the same CO02 function, but it is not free of consequences. When you reset, the reservations for components that were deleted are not restored automatically in every release. Check the order components list after the reset and add missing items or reschedule the order so material requirements are recreated. In some releases, you must re-release the order.
Authorisation is controlled through the order-related authorisation object (for example C_AFKO_AWK for order types and plants). Restrict the reset function to a small group of supervisors because a reset order can accept new postings after cost accounting has already treated it as final.
-- Review status history for an order in SE16N Table JEST (OBJNR = 'OR' + order number, INACT = space) Table TJ02T (status text, SPRAS = EN) Table AFKO (order header, AUFNR = order number)
When the reset or the TECO is not possible
If CO02 refuses to set TECO, the order often has open goods movements or an incomplete confirmation, or it is locked by another user or a collective job. Check SM12 for locks and the order status for flags such as a pending confirmation. If it refuses to reset, look for the business close status or a deletion flag and involve your controller.
Partially delivered orders with open reservations are the classic case. If the quantity delivered is below the order quantity and you set TECO, the missing quantity disappears from MRP supply. Make sure planning knows to create a replacement order for the shortfall.
Common pitfalls
- !Setting TECO on a partially delivered order removes the open quantity from MRP, so shortages show up later with no planned supply.
- !Assuming TECO settles costs. It does not; run variance calculation and KO88 or CO88 afterwards.
- !Resetting TECO without checking that deleted component reservations and capacity requirements were recreated.
- !Mass TECO through COHV without a clear age and status policy, which catches orders planners still wanted.
- !Confusing TECO with the deletion flag. A deletion flag marks the order for archiving; TECO leaves it fully visible.
How an ERP-grounded AI assistant handles this
An assistant grounded in your SAP data (ERPray, read-only by default) can list orders that are TECO but still carry open cost, or orders delivered long ago that are still not TECO, by reading AFKO, AUFK and JEST and showing the query. It can tell a controller which orders block period close. The reset and TECO actions themselves stay in CO02 or COHV, behind your normal authorisations and a human approval step.
Frequently asked questions
What is the difference between TECO and CLSD?
TECO means technically complete: no more goods movements or confirmations, and open reservations and capacity are removed. CLSD means business closed and is set after settlement. TECO is the production signal and can be reset; CLSD is the finance signal and normally cannot be undone without special handling.
Can I post a goods receipt to an order with TECO status?
No. Technically complete orders block further goods movements and confirmations. Reset TECO in CO02 under Functions > Restrict Processing > Reset Technically Complete, post the missing movement or confirmation, then set TECO again.
Does TECO delete the order or its history?
No. The order remains fully visible with all confirmations, goods movements and costs. Only the deletion flag and later archiving remove it from active tables. TECO only restricts further processing and releases open reservations and capacity requirements.
How do I set TECO on many orders at once?
Use COHV, the mass processing transaction for production orders. Select orders by plant, status and date, then run the Technically Complete mass function. Always test the selection on a small list first, because orders with open quantities will lose their remaining supply from MRP.
Related
SAP CO11N Confirmation Errors and How to Fix Them
CO11N (time ticket confirmation for production/process orders) throws several distinct errors: deviation from the standard value is too large, goods movement not possible for a component, or the order/operation status does not allow confirmation. Each has a specific cause in order status, routing tolerance settings, or component availability, not a single generic fix.
How-toSAP MD01N (MRP Live) vs MD01: How to Run MRP Correctly
MD01N is MRP Live: the same planning logic as classic MD01, but executed inside the SAP HANA database instead of looping through materials in ABAP. Run it from MD01N by entering the plant, choosing a processing key (net change or regeneration), setting the purchase requisition and scheduling parameters, and executing in the background for large scopes.
Error fixSAP KI 235: G/L Account Requires an Assignment to a CO Object
KI 235 means a primary cost or revenue element exists (or should exist) on a P&L account, but the posting you are entering has no valid Controlling object - cost center, order, WBS element or profitability segment - to receive it. Add the account assignment on the posting, or set a default cost center via OKB9 so future postings resolve automatically.
How-toSAP SE16N vs SQVI: Table Browser vs Ad Hoc Query
SE16N is a single-table browser: fast filtering, formatted display, and export from one table at a time, with an optional edit function for authorized users. SQVI (Quick Viewer) builds ad hoc queries that join multiple tables without writing ABAP, and can be saved as a reusable report. Use SE16N for a quick look at one table; use SQVI when you need data joined across two or more tables.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ECC and S/4HANA?
Talk to engineers who work inside SAP ECC and S/4HANA every week, and who build private AI that answers these questions from your own ERP data.