T683S table — Item Category Determination Table

T683S stores the item category determination rules maintained through the VOV4 configuration transaction. One row represents a single combination of sales document type, item category group (carried from the material master onto the order item), item usage, and higher-level item category, resolving to a default item category value. This value is written into VBAP-PSTYV when a sales document item is created without reference to a preceding document. The table also carries an indicator for whether the determined item category can be overridden manually on the document. It does not store transactional data itself; it is pure configuration consulted at document-save time by the item category determination logic inside standard sales order processing.

T683S is small and fully client-dependent, so MANDT plus AUART is enough to pull a readable slice for a single sales document type. There is no meaningful selectivity problem here; the table has at most a few hundred rows per client. The risk is not performance but misreading blank key values: many configurations include a fallback row with an empty item category group or empty usage that acts as a catch-all for everything not matched by a more specific row. Always sort results so that fully specified rows are checked before the blank-key fallback, otherwise the wrong rule looks like the one that fired.

To confirm why a given order line got item category TAN instead of an expected value, take the order's AUART from VBAK, the MTPOS and usage indicator actually stored on that VBAP row, and the PSTYV of the higher-level item if one exists, then look up T683S for the matching AUART with those exact values, falling back to the blank-MTPOS or blank-usage row if no specific match exists. The row found should return the PSTYV seen on the order; if it does not, the value was set by another mechanism, not by determination.

T683S is retained in S/4HANA as a standard customizing table maintained through the same VOV4 activity; it has not been replaced by a CDS compatibility view because it is configuration, not master or transactional data subject to the usual simplification list treatment. The determination logic that reads it during sales document processing is unchanged in shape, though surrounding logic such as advanced ATP or newer pricing procedures can influence which item category path is actually exercised for a given scenario.

The SD or order-management functional consultant owns the T683S configuration, maintained via VOV4 as part of sales document customizing. Where the input MTPOS comes from the material master, the MM or master-data team owns getting that item category group set correctly on the material; basis is not normally involved since this is pure customizing.

T683 defines the item categories themselves that T683S can point to as a result. VBAK and VBAP carry the sales document type and the determined item category respectively once an order is saved. Copy control transactions govern item category behavior for documents created with reference, overriding what T683S would otherwise determine. The material master sales view is where the item category group used as input is maintained.