SAP B121 OutputDev. Table data and field list

B121 is a standard SAP Table which is used to store OutputDev. data in SAP systems, such as SAP R/3, S/4HANA, depending on the version and release level.

The B121 table consists of various fields, each holding specific information or linking keys about OutputDev. data available in SAP. These include KAPPL (Application), KSCHL (Output Type), OUTPUT_DEV (Spool: Output device), KNUMH (Number of output condition record)... See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .

B121 table Technical Details:

Delivery Class: A - Application table (master and transaction data)
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced


SAP B121 table fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the B121 table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
MANDTClient MANDTCLNT3T000MANDT
KAPPLApplication KAPPLCHAR2T681AKAPPLKAP
KSCHLOutput Type NA_KSCHLCHAR4T685KSCHLNACCSH_NA_KSCHL
OUTPUT_DEVSpool: Output device RSPOPNAMECHAR4TSP03SPDEVRSPOPNAME
KNUMHNumber of output condition record NNUMHCHAR10KNUMB

Key field Non-key field



How do I retrieve data from SAP table B121 using ABAP code

The following ABAP code Example will allow you to do a basic selection on B121 to SELECT all data from the table
DATA: WA_B121 TYPE B121.

SELECT SINGLE *
FROM B121
INTO CORRESPONDING FIELDS OF WA_B121
WHERE...

How to access SAP table B121

Within an ECC or HANA version of SAP you can also view further information about B121 and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).