JEST
transaction S/4HANA status: ActiveIndividual Object Status
What the badges mean
- S/4HANA status: Active
- Active and unchanged in S/4HANA.
- S/4HANA status: Deprecated
- Still readable today, but no longer SAP's strategic path — plan around it.
- S/4HANA status: Replaced
- Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
- S/4HANA status: Migrating to IBP
- Planning scope is moving from APO toward IBP.
- S/4HANA status: Active (StRM) · Replaced (EWM)
- Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
- S/4HANA status: Replaced · Compat View
- Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
- S/4HANA status: Active · Proxy View
- Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
- master
- Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
- Linked type codes
CLNT — the client key; filter it explicitly and carry it through every join.
NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.
DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.
CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.
LANG — a language key in a text table — one row per language.
Fields
4 fields · 3 key
The join key is all 3 key fields together — matching on any single one fans out. See composite keys in the quirks guide.
4 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | |
| Primary key | OBJNR | Object Number | CHAR | 22 | |
| Primary key | STAT | Object Status | CHAR | 5 | |
| INACT | Indicator: Status Is Inactive | CHAR | 1 |
Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading JEST on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
3 parameters not filled: <catalog>, <schema>, <MANDT>
-- ============================================================
-- Table : JEST Individual Object Status
-- Purpose: Column-selected read of JEST — auto-generated from field metadata
-- Grain : One row per OBJNR + STAT
-- Notes : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
j.MANDT AS "Client",
j.OBJNR AS "Object Number",
j.STAT AS "Object Status",
j.INACT AS "Indicator: Status Is Inactive"
FROM <catalog>.<schema>.jest j
WHERE
j.MANDT = '<MANDT>'
ORDER BY j.OBJNR;Verified August 2026
Relationships
Diagram of 1-hop neighbors — join details below.
Join details
ON aufk.OBJNR = jest.OBJNR
Transaction Codes That Use This Table
No t-code mappings populated for this table yet.