AGGREGATED_RECORDS1 SAP (Proxy Structure (Generated)) Structure details
Description: Proxy Structure (Generated)
Related tables to AGGREGATED_RECORDS1
Access table AGGREGATED_RECORDS1
Structure field list including key, data, relationships and ABAP select examples
AGGREGATED_RECORDS1 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 "Proxy Structure (Generated)" 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_AGGREGATED_RECORDS1 TYPE AGGREGATED_RECORDS1.
The AGGREGATED_RECORDS1 table consists of various fields, each holding specific information or linking keys about Proxy Structure (Generated) data available in SAP. These include BEGIN_TS (XSD Time (UTC): yyyy-mm-ddThh:mm:ssZ [ext.]), CALL_COUNT (), END_TS (XSD Time (UTC): yyyy-mm-ddThh:mm:ssZ [ext.]), PERIOD ().. 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 (Deep)
SAP AGGREGATED_RECORDS1 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 |
| CONTROLLER | 0 | ||||||||
| BEGIN_TS | XSD Time (UTC): yyyy-mm-ddThh:mm:ssZ [ext.] | XSDDATETIME_Z | DEC | 15 | XSDDATETIME_Z | ||||
| CALL_COUNT | 0 | ||||||||
| END_TS | XSD Time (UTC): yyyy-mm-ddThh:mm:ssZ [ext.] | XSDDATETIME_Z | DEC | 15 | XSDDATETIME_Z | ||||
| PERIOD | 0 | ||||||||
| STATUS | 0 | ||||||||
| COMPANY_ID | 0 | ||||||||
| SYSTEM_ID | 0 | ||||||||
| OPERATION_INFO | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| SERVICE_COMPONENT | 0 | ||||||||
| SERVICE_INTERFACE | 0 | ||||||||
| SERVICE_INTERFACE_NAMESPACE | 0 | ||||||||
| SERVICE_INTERNAL_NAME | 0 | ||||||||
| SERVICE_OPERATION | 0 | ||||||||
| CALLER_INFO | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| CALLER_INFO_APPLICATION | 0 | ||||||||
| CALLER_INFO_COMPANY | 0 | ||||||||
| CALLER_INFO_COMPONENT | 0 | ||||||||
| CALLER_INFO_SYSTEM | 0 | ||||||||
| CALLER_INFO_TYPE | 0 | ||||||||
| CALLER_INFO_USER_CODE | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure AGGREGATED_RECORDS1 using ABAP code?
As AGGREGATED_RECORDS1 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 AGGREGATED_RECORDS1 as there is no data to select.How to access SAP table AGGREGATED_RECORDS1
Within an ECC or HANA version of SAP you can also view further information about AGGREGATED_RECORDS1 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