BDOC_TRACK SAP (Information on BDOCs During Load from CRM System/Back End) Table details
Description: Information on BDOCs During Load from CRM System/Back End
Table field list including key, data, relationships and ABAP select examples
BDOC_TRACK is a standard SAP Table which is used to store Information on BDOCs During Load from CRM System/Back End data and is available within R/3 SAP systems depending on the version and release level.
The BDOC_TRACK table consists of various fields, each holding specific information or linking keys about Information on BDOCs During Load from CRM System/Back End data available in SAP. These include UPLOAD_ID (Unique Reference Number), BLOCKNO (Block Number Data Transfer), LOAD_TYPE (Internal Adapter: Type of Load), RUNTIMEINF (Runtime Information for a BDoc in the Back End).. 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: L - Table for storing temporary data, is delivered emptyDisplay/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP BDOC_TRACK table 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 | |||
UPLOAD_ID | Unique Reference Number | REF_ID | CHAR | 32 | CHAR32 | ||||
BLOCKNO | Block Number Data Transfer | CRMBLOCKNO | CHAR | 10 | CRMBLOCKNO | ||||
LOAD_TYPE | Internal Adapter: Type of Load | LOAD_TYPE | CHAR | 1 | LOAD_TYPE | ||||
RUNTIMEINF | Runtime Information for a BDoc in the Back End | RUNTIMEINF | CHAR | 32 | CHAR32 | ||||
CONSUMER | User of R/3 Adaptor Functionality | CONSUMER | CHAR | 10 | CRMCONSUM | CONSUMER | |||
LOG_SYSTEM | Logical system | LOGSYS | CHAR | 10 | TBDLS | ALPHA | LOGSYS | ||
OBJNAME | Object Name | CRMOBJNAME | CHAR | 15 | CRMOBJECT | CHAR15 | |||
LOADSTART | Load Started By Trigger Function Module | LOADSTART | CHAR | 1 | CHAR1 | ||||
EXIT1_INT | Internal Exit for Load Trigger Function Module (Exit No. 1) | EXIT1_INT | CHAR | 1 | CHAR1 | ||||
PROCESSED1 | Indicator: Trigger Module Internal Exit Executed (No.1) | PROCESSED1 | CHAR | 1 | CHAR1 | ||||
CONTROL1 | Indicator: Internal Trigger Exit Controls the Load (No. 1) | CONTROL1 | CHAR | 1 | CHAR1 | ||||
EXIT2_EXT | External Exit for Load Trigger Function Module (Exit No. 2) | EXIT2_EXT | CHAR | 1 | CHAR1 | ||||
PROCESSED2 | Indicator: Trigger Module External Exit Executed (No. 2) | PROCESSED2 | CHAR | 1 | CHAR1 | ||||
CONTROL2 | Indicator: External Trigger Exit Controls the Load (No. 2) | CONTROL2 | CHAR | 1 | CHAR1 | ||||
MODULFOUND | Extraction Mod. or Inbound Module Determined During Load | MODULFOUND | CHAR | 1 | CHAR1 | ||||
EXFMNOTNOK | Module for Data Extraction Incorrectly Processed | EXFMNOTNOK | CHAR | 1 | CHAR1 | ||||
XMLFORMAT | Indicator:XML Data Format Exists During Load to R/3 Back End | XMLFORMAT | CHAR | 1 | CHAR1 | ||||
XMLPARSED | Indicator: Data Exists in BAPIMTCS Structure (XML Parsed) | XMLPARSED | CHAR | 1 | CHAR1 | ||||
NOACTEVENT | During Load to R/3 Back End: No Event Determined | NOACTEVENT | CHAR | 1 | CHAR1 | ||||
SENDSTART | Indicator: Function Module CRS_SEND_TO_SERVER Started | SENDSTART | CHAR | 1 | CHAR1 | ||||
LASTBLOCK | Indicator for Last Block During Initial Download | LASTBLOCK | CHAR | 1 | CHAR1 | ||||
EXTRACTOK | Indicator: Data Extracted During Load | EXTRACTOK | CHAR | 1 | CHAR1 | ||||
DNL_PARAMS | Indicator: Load Parameters Determined (CRS_READ_DNL_PARAMS) | DNL_PARAMS | CHAR | 1 | CHAR1 | ||||
CRMUCSYS | System Is a Unicode System | CRMUCSYS | CHAR | 1 | XFELD | ||||
EXIT3_INT | Indicator: Internal Exit of CRS_SEND_TO_SERVER (Exit No.3) | EXIT3_INT | CHAR | 1 | CHAR1 | ||||
PROCESSED3 | Indictor: Internal Exit of CRS_SEND_TO_SERVER Executed (3) | PROCESSED3 | CHAR | 1 | CHAR1 | ||||
CONTROL3 | Indicator: Internal CRS_SEND_TO_SERVER Exit Controls Load(3) | CONTROL3 | CHAR | 1 | CHAR1 | ||||
EXTRACT3 | Data Extract Available After Int. CRS_SEND_TO_SERVER Exit | EXTRACT3 | CHAR | 1 | CHAR1 | ||||
FILTERSYNC | Indicator: Synchronous Filtering During Load | FILTERSYNC | CHAR | 1 | CHAR1 | ||||
FILTEROK | Indictator: Filtering Performed Successfully During Load | FILTEROK | CHAR | 1 | CHAR1 | ||||
FILTEREXTR | Indicator: Data Extract Available After Filtering | FILTEREXTR | CHAR | 1 | CHAR1 | ||||
EXIT4_EXT | Indicator: External Exit of CRS_SEND_TO_SERVER (Exit No.4) | EXIT4_EXT | CHAR | 1 | CHAR1 | ||||
PROCESSED4 | Indicator: External Exit of CRS_SEND_TO_SERVER Executed (4) | PROCESSED4 | CHAR | 1 | CHAR1 | ||||
NOTSEND4 | Indicator: Send No More Data After Internal Exit (4) | NOTSEND4 | CHAR | 1 | CHAR1 | ||||
EXTRACT4 | Data Extract Available After Ext. CRS_SEND_TO_SERVER Exit | EXTRACT4 | CHAR | 1 | CHAR1 | ||||
SENDDATA | Indicator: Data Sent During Load | SENDDATA | CHAR | 1 | CHAR1 | ||||
ENDSEND | Indicator: CRS_SEND_TO_SERVER Completely Processed | ENDSEND | CHAR | 1 | CHAR1 | ||||
OPERATION | Function | MSGFN | CHAR | 3 | MSGFN | ||||
ACTSTATINF | Additional Information on Status | ADDTEXT_ST | CHAR | 30 | CHAR30 | ||||
LSTSTATINF | Additional Information on Status | ADDTEXT_ST | CHAR | 30 | CHAR30 | ||||
OBJECTTYPE | Obj. Type | CRMOBJTYPE | CHAR | 4 | CHAR_LG_04 | ||||
OBJKEY | Object Key | CRMOBJKEY | CHAR | 32 | SYSUUID_C | ||||
CREDATE | Date on Which the Record was Created | CREATEDATE | DATS | 8 | DATUM | ||||
CRETIME | Time Created | CREATIME | TIMS | 6 | SYTIME | ||||
CHANGDATE | Last Changed On | CHANGDATE | DATS | 8 | DATUM | ||||
CHANGTIME | Time of Last Change | CHANGTIME | TIMS | 6 | SYTIME |
Key field | Non-key field |
How do I retrieve data from SAP table BDOC_TRACK using ABAP code
The following ABAP code Example will allow you to do a basic selection on BDOC_TRACK to SELECT all data from the tableDATA: WA_BDOC_TRACK TYPE BDOC_TRACK.
SELECT SINGLE *
FROM BDOC_TRACK
INTO CORRESPONDING FIELDS OF WA_BDOC_TRACK
WHERE...
How to access SAP table BDOC_TRACK
Within an ECC or HANA version of SAP you can also view further information about BDOC_TRACK 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