AENRB SAP (Change Master Document Table) Structure details
Dictionary Type: Structure
Description: Change Master Document Table
Description: Change Master Document Table
Structure field list including key, data, relationships and ABAP select examples
AENRB is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Change Master Document Table" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_AENRB TYPE AENRB.
The AENRB table consists of various fields, each holding specific information or linking keys about Change Master Document Table data available in SAP. These include MANDT (Client), AENNR (Change Number), AENST (Status of change number), AENBE (Authorization group for change master 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. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP AENRB structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
| AENST | Status of change number | AENST | NUMC | 2 | T419S | AENST | |||
| AENBE | Authorization group for change master record | CC_AENBE | CHAR | 4 | CC_BEGRU | ||||
| DATUV | Valid-From Date | CC_CCDAT | DATS | 8 | CC_DATUM | ||||
| TECHV | Technical status from | CC_TECHV | CHAR | 12 | CC_TECHS | ||||
| ANDAT | Date record created on | CC_ANDAT | DATS | 8 | CC_DATUM | ||||
| ANNAM | User who created record | CC_ANNAM | CHAR | 12 | CC_USNAM | ||||
| AEDAT | Date of Last Change | CC_AEDAT | DATS | 8 | CC_DATUM | ||||
| AENAM | Name of person who changed object | CC_AENAM | CHAR | 12 | CC_USNAM | ||||
| AETXT | Change Number Description | CC_AETXT | CHAR | 40 | CC_TEXT40 | ||||
| LTXSP | Language: The long text was stored in this language | CC_LTXSP | LANG | 1 | T002 | ISOLA | SPRAS | ||
| AEGRU | Reason for change | CC_AEGRU | CHAR | 40 | CC_TEXT40 | ||||
| CCART | Change type | CC_CCART | NUMC | 3 | Assigned to domain | CC_CCART | AENR_CCART | ||
| CCSTM | Maximum partial status keys in engineering change management | CCSTM_D | NUMC | 8 | CC_NUMC8 | ||||
| DYDAT | Indicator: change number with dynamic date | CC_DYDAT | CHAR | 1 | CC_XFELD | ||||
| CONT1 | Digital signature (process improvement) | CC_DSIGN | CHAR | 1 | CC_DSIGN | ||||
| AEFUN | Change number function | CC_AEFUN | CHAR | 1 | CC_AEFUN | ||||
| UESTR | Indicator: Overriding possible | CC_UESTR | CHAR | 1 | CC_XFELD | ||||
| RLKEY | Release Key for Change Master Record | CC_RLKEY | NUMC | 2 | TCC10 | CC_RLKEY | CC_RLKEY | ||
| LVORM | Deletion Flag for Change Number (Reorganization) | CC_LOEKZ | CHAR | 1 | CC_XFELD | ||||
| CLINT | Internal class number describing effectivity type | CC_CLINT | NUMC | 10 | Assigned to domain | CC_CLINT | |||
| AERNG | ECM: rank of change number | CC_AERNG | NUMC | 2 | CC_NUMC2 | ||||
| RLDAT | Date when the release key was changed | CC_RLDAT | DATS | 8 | CC_DATUM | ||||
| RLTIM | Time when the release key was changed | CC_RLTIM | TIMS | 6 | CC_UZEIT | ||||
| TEREL | Indicator: Technical release occurs | CC_TEREL | CHAR | 1 | CC_XFELD | ||||
| NACHT | Indicator: Change Package Created After Release | CC_NACHT | CHAR | 1 | CC_CHAR1 | ||||
| INDAT | Effective Date of Statutory Regulation | CC_INDAT | DATS | 8 | CC_DATUM | ||||
| AUDAT | End Date for Transitional Period (Prescribed by Law) | CC_AUDAT | DATS | 8 | CC_DATUM | ||||
| FLUSE | Change number has been used for data maintenance | CC_FLUSE | CHAR | 1 | CC_XFELD | ||||
| AEDIF | ECM: differentiate effectivity types | CC_AEDIF | NUMC | 10 | CC_NUMC10 | ||||
| ERLED | Indicator for basic change | CC_AEERL | CHAR | 1 | CC_XFELD | ||||
| DBART | Change Type | CCART | NUMC | 3 | Assigned to domain | CCART | AENR_CCART | ||
| DBDAT | Valid-From Date | CC_DATUV | DATS | 8 | DATUM | ||||
| DBSTS | Status Profile | CC_J_STSMA | CHAR | 8 | CC_J_STSMA | ||||
| EFFTYP | Effectivity Type | CC_EFFT | CHAR | 10 | CC_CHAR10 | ||||
| OBJNR | Object no. | CC_J_OBJNR | CHAR | 22 | CC_J_OBJNR | ONR | |||
| VBKZ | Update indicator | CC_VBKZ | CHAR | 1 | CC_VERBUCHER | ||||
| LTXVB | Update indicator | CC_VBKZ | CHAR | 1 | CC_VERBUCHER |
| Key field | Non-key field |
How do I retrieve data from SAP structure AENRB using ABAP code?
As AENRB is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on AENRB as there is no data to select.How to access SAP table AENRB
Within an ECC or HANA version of SAP you can also view further information about AENRB and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects