COOIS — Production Order Information System List
COOIS is the multi-purpose list transaction for production orders. It does not pull one fixed data set: the list type chosen on the selection screen (order headers, component overview, operation overview, capacity requirements, trigger points, or confirmations) determines which underlying tables drive the output and which fields even exist on screen. Most confusion comes from picking the wrong list type for the question being asked.
This page covers COOIS, the order information system used to list and drill into production orders across header, component, operation, and confirmation data. It focuses on why the same transaction produces wildly different output depending on the list type selected, and how to diagnose empty or wrong results without assuming a data extraction bug.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,161 words
Purpose
COOIS is a selection and list report over production order data. It does not have a single output structure. A dropdown or radio selection on the entry screen (component overview, operation overview, order headers, capacity requirements, trigger points, confirmations, and similar variants) picks a different underlying join and a different field catalog. The one structural fact that explains most confusion: a saved layout or a habit built on one list type does not carry over to another, because the fields simply do not exist in the other list's source tables. A consultant who expects to see reservation quantities in an 'order headers' list, or expects operation control keys in a 'component overview' list, is asking a question the chosen list type cannot answer. Getting the diagnosis right starts with confirming which list type was actually run before touching filters or authorizations.
When it is used
COOIS is the first stop for any question about a batch of production orders rather than one order: which orders are still open past their finish date, which orders have components not yet withdrawn, which operations are not yet confirmed, which orders are missing a goods receipt. CO03 and CO02 answer questions about a single order; COOIS answers questions about a population of orders. It is also the tool used before a period-end close to find orders stuck in a status that blocks settlement, and during a shortage investigation to find every order still waiting on a component. On S/4HANA, some of this is now covered by Fiori manufacturing overview apps, but COOIS remains the fallback when the Fiori app's filters do not go deep enough or when the exact field needed only exists in the classic list.
How to use it in practice
- Decide the question first: header status, component shortage, operation progress, or confirmation gaps, since this decides the list type.
- On the entry screen, select the correct list type from the selection profile or radio button group before entering any filter values.
- Enter plant and order type as a minimum; an unrestricted date range across all plants is the most common cause of a timeout.
- Restrict by order status (released, technically complete, confirmed) if the question is about orders in a specific stage.
- Run the list, then use the layout variant to add or remove columns rather than assuming the default layout is complete.
- Drill into a single line to jump to CO03 or CO02 for the underlying order when a line looks wrong.
Key data objects
- AFKO - order header data: order number, scheduled dates, basic dates, order type, production version.
- AFPO - order item data: material, target quantity, confirmed quantity, goods receipt information tied to the order.
- AFVC and AFVGD - operation and operation detail data: control keys, work center, activity type, capacity requirements.
- RESB - component reservations: material, required quantity, withdrawn quantity, requirement date per component line.
- AFRU - confirmation records: confirmed quantities, confirmation dates, personnel or work center that posted the confirmation.
- COOIS itself writes nothing; it is a read-only list transaction and does not update any of these tables.
How to prove it in the data
To confirm what a COOIS run actually returned, go to SE16 or SE16N and pull the source table that matches the list type used: AFKO joined to AFPO on order number for a header or item question, RESB filtered on order number for a component shortage question, AFRU filtered on order number for a confirmation question. Filter by the same plant, order type, and status range entered on the COOIS selection screen. If a row is missing from COOIS but present in the raw table, the selection screen filter or the layout variant is excluding it, not a data problem.
ECC vs S/4HANA
COOIS runs largely unchanged on S/4HANA and still sits on the same classic order tables in most implementations. Some manufacturing overview and monitoring needs are covered by newer Fiori apps built on CDS views, which can be faster for dashboard-style questions but usually offer fewer selection combinations than COOIS. Consultants working an S/4HANA incident still reach for COOIS when the Fiori app does not expose the specific list type or field needed, particularly for component or operation-level detail.
Common pitfalls and how to diagnose them
- Wrong list type selected: the user expects component or capacity fields but ran the order headers list, or vice versa. Fix is to re-run with the correct list type, not to search for a missing field in the layout.
- Status filter too narrow: default selection often excludes technically complete or closed orders. A user reporting orders as missing is frequently just excluding TECO or CLSD status without realizing it.
- Date field misunderstanding: basic dates, scheduled dates, and confirmation dates are different fields on different tables. Filtering on the wrong date field returns an empty or wrong list even though the order clearly exists.
- Saved layout hiding data: a personal layout variant with columns removed makes data look absent. Reset to the default layout before concluding data is missing.
- Authorization scoping: plant or order type authorization restricts the list silently, returning zero rows with no error message. Check the user's plant authorization before assuming the selection is wrong.
- Performance on wide selections: running across all plants with a long date range and no order type restriction causes timeouts or very long runtimes; this is a selection design problem, not a system defect.
- Confirmation and component overview mismatch: a component line shown as open in COOIS component overview may already be consumed if a backflush happened at a later operation; cross-check against RESB withdrawn quantity before assuming an availability problem.
Whose problem this is
COOIS is a functional PP transaction; it belongs to the production planning or shop floor control consultant. A handover to that owner should include the list type used, the exact selection screen filters (plant, order type, status range, date field), and the order numbers where the result looked wrong, so the diagnosis can be reproduced without guessing at what was run.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cooisERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.