SAP MDST_LOAD_API_HIST Interface for 'Load API' (History Data) Table data and field list

MDST_LOAD_API_HIST 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 "Interface for 'Load API' (History Data)" 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_MDST_LOAD_API_HIST TYPE MDST_LOAD_API_HIST.

The MDST_LOAD_API_HIST table consists of various fields, each holding specific information or linking keys about Interface for 'Load API' (History Data) data available in SAP. These include CLIENT (Client), SYNC_LOAD_GUID (Unique ID for Synchronization History), COUNTER (2 byte integer (signed)), SYNC_OBJ_SOURCE (Source Synchronization Object)... 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. .

MDST_LOAD_API_HIST structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced

SAP MDST_LOAD_API_HIST structure 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 MDST_LOAD_API_HIST 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
CLIENT	Client	MANDT	CLNT	3	Assigned to domain		MANDT
SYNC_LOAD_GUID	Unique ID for Synchronization History	MDST_SYNC_LOAD_GUID	RAW	16			SYSUUID
COUNTER	2 byte integer (signed)	INT2	INT2	5			INT2
SYNC_OBJ_SOURCE	Source Synchronization Object	MDS_CTRL_OBJ_SOURCE	CHAR	10	Assigned to domain		MDS_CTRL_OBJECT
SYNC_OBJ_TARGET	Target Synchronization Object	MDS_CTRL_OBJ_TARGET	CHAR	10	Assigned to domain		MDS_CTRL_OBJECT
SYNC_TIMESTAMP	UTC Time Stamp in Short Form (YYYYMMDDhhmmss)	TIMESTAMP	DEC	15			TZNTSTMPS
USER_NAME	User Name	SYUNAME	CHAR	12			SYCHAR12
BLOCK_SIZE	Block Size for Mass Synchronization	MDST_BLOCK_SIZE	INT4	10			INT4_NOS9
QUEUE_NAME	Name of tRFC Queue	TRFCQNAM	CHAR	24			TRFCQNAM
MAX_PROCESSES	Number of Parallel Processes	MDST_SYNC_PROCESSES	INT2	5			INT2
SEL_KIND	Type of Data Selection	MDST_SYNC_KIND	CHAR	1			MDS_SYNC_KIND
TEST_RUN	Test Run Indicator	MDST_SYNC_TEST_RUN	CHAR	1			BOOLEAN
SYNC_STATUS	Mass Synchronization Status	MDST_SYNC_STATUS	CHAR	1			MDS_SYNC_STATUS
SYNC_PROGRESS	Mass Synchronization Processing Progress	MDST_SYNC_PROGRESS	CHAR	1			MDS_SYNC_PROGRESS
BUSINESS_PROCESS	PPO Order: Business Process	MDST_PPO_BUSINESS_PROCESS	CHAR	10			CHAR10
BACK_GRND_PROC	FM Processing Type (Foreground, Background)	MDST_SYNC_PROC_KIND	CHAR	1			XFELD
SEL_OPT				0

Key field

Non-key field

< MDST_LOAD_API_F4_FIELDNAME - Internal Structure for F4 Help MDST_LOAD_API_HIST_DATA - Interface for 'Load API' (History Data) (Data Part) >

How do I retrieve data from SAP structure MDST_LOAD_API_HIST using ABAP code?

As MDST_LOAD_API_HIST 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 MDST_LOAD_API_HIST as there is no data to select.

How to access SAP table MDST_LOAD_API_HIST

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

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