AFAB_UPDATE_RELEVANT SAP (Fields relevant to update from AFAB (sim. vers.)) Structure details
Description: Fields relevant to update from AFAB (sim. vers.)
Related tables to AFAB_UPDATE_RELEVANT
Access table AFAB_UPDATE_RELEVANT
Structure field list including key, data, relationships and ABAP select examples
AFAB_UPDATE_RELEVANT 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 "Fields relevant to update from AFAB (sim. vers.)" 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_AFAB_UPDATE_RELEVANT TYPE AFAB_UPDATE_RELEVANT.
The AFAB_UPDATE_RELEVANT table consists of various fields, each holding specific information or linking keys about Fields relevant to update from AFAB (sim. vers.) data available in SAP. These include AOBAR (Type of relationship), MIMAX (Indicates whether maximum time interval will be considered), ZEINH (Unit for the time interval between relationships), DAUER (Time interval between relationships).. 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: Not classified
SAP AFAB_UPDATE_RELEVANT 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 | Assigned to domain | MANDT | |||
AOBAR | Type of relationship | AOBAR | CHAR | 2 | AOBAR | AOBAR | |||
MIMAX | Indicates whether maximum time interval will be considered | DAUMIMAX | CHAR | 1 | XFELD | ||||
ZEINH | Unit for the time interval between relationships | AOBDAUEH | UNIT | 3 | T006 | CUNIT | MEINS | ||
DAUER | Time interval between relationships | AOBDAUER | QUAN | 5(1) | AOBDAUER | ||||
DAUKZ | Indicator for the duration of the relationship | AOBDAUKZ | CHAR | 1 | AOBDAUKZ | ||||
VORNC | Indicator: maintained after successor | VORG_NACH | CHAR | 1 | XFELD | ||||
NCVOR | Indicates whether data after predecessor is maintained | NACH_VORG | CHAR | 1 | XFELD | ||||
LOEKZ | Indicates whether an object is logically deleted. | LOLOE | CHAR | 1 | XFELD | ||||
KALID | Factory Calendar | WFCID | CHAR | 2 | TFACD | WFCID | FCI | ||
PRZNT | % used to calc. time interval between predecessor/successor | AOB_PRZNT | NUMC | 3 | AOB_PRZNT | ||||
PROVG | Key for defining time intervals in a relationship | AOB_PROVG | CHAR | 1 | AOB_PROVG | ||||
ARBID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
FSABD | Earliest start date for the relationship | FSABD | DATS | 8 | DATUM | ||||
FSABZ | Earliest start time for the relationship | FSABZ | TIMS | 6 | ATIME | ||||
SSABD | Latest start date of the relationship | SSABD | DATS | 8 | DATUM | ||||
SSABZ | Latest start time of the relationship | SSABZ | TIMS | 6 | ATIME | ||||
FEABD | Earliest finish date for the relationship | FEABD | DATS | 8 | DATUM | ||||
FEABZ | Earliest finish time for the relationship | FEABZ | TIMS | 6 | ATIME | ||||
SEABD | Latest finish date of the relationship | SEABD | DATS | 8 | DATUM | ||||
SEABZ | Latest finish time of the relationship | SEABZ | TIMS | 6 | ATIME | ||||
DAUTM | Relationship duration (in seconds) as result of scheduling | DAUTM | INT4 | 10 | CX_DAUERS | ||||
AUCRE | Ind.: Relationship automatically generated | CN_AUCRE | CHAR | 1 | XFELD | ||||
DAUERMAX | Maximum time interval for relationship | AOBDAUERM | QUAN | 5(1) | AOBDAUER |
Key field | Non-key field |
How do I retrieve data from SAP structure AFAB_UPDATE_RELEVANT using ABAP code?
As AFAB_UPDATE_RELEVANT 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 AFAB_UPDATE_RELEVANT as there is no data to select.How to access SAP table AFAB_UPDATE_RELEVANT
Within an ECC or HANA version of SAP you can also view further information about AFAB_UPDATE_RELEVANT 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