CRMT_CD_DOCFLOW_DATA_HDR SAP (Transportation Cross-Docking Document Flow Data (Header)) Structure details
Description: Transportation Cross-Docking Document Flow Data (Header)
Related tables to CRMT_CD_DOCFLOW_DATA_HDR
Access table CRMT_CD_DOCFLOW_DATA_HDR
Structure field list including key, data, relationships and ABAP select examples
CRMT_CD_DOCFLOW_DATA_HDR 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 "Transportation Cross-Docking Document Flow Data (Header)" 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_CRMT_CD_DOCFLOW_DATA_HDR TYPE CRMT_CD_DOCFLOW_DATA_HDR.
The CRMT_CD_DOCFLOW_DATA_HDR table consists of various fields, each holding specific information or linking keys about Transportation Cross-Docking Document Flow Data (Header) data available in SAP. These include DELIVERY (Delivery), PREC_DELIVERY (Transportation Cross-Docking: Preceding Delivery), DLV_TYPE (Delivery Type), DLV_CATEGORY (SD document category).. 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 CRMT_CD_DOCFLOW_DATA_HDR 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 |
CD_PROCESS | Transportation Cross-Docking Process Number | CRMT_CD_PROCESS | CHAR | 10 | ALPHA | VBELN | |||
DELIVERY | Delivery | VBELN_VL | CHAR | 10 | ALPHA | VBELN | VL | ||
PREC_DELIVERY | Transportation Cross-Docking: Preceding Delivery | CRMT_CD_PREC_DLV | CHAR | 10 | ALPHA | VBELN | |||
DLV_TYPE | Delivery Type | LFART | CHAR | 4 | Assigned to domain | LFART | ALT | ||
DLV_CATEGORY | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
OBJTYPE | Object Type | SWO_OBJTYP | CHAR | 10 | Assigned to domain | OJ_NAME | OBJ | ||
PREC_DLV_TYPE | Transportation Cross-Docking: Preceding Delivery Type | CRMT_CD_PREC_DLV_TYPE | CHAR | 4 | Assigned to domain | LFART | |||
PREC_DLV_CATEG | Transportation Cross-Docking: Preceding Delivery Category | CRMT_CD_PREC_DLV_CATEGORY | CHAR | 1 | VBTYP | ||||
SUPPLYING_PLANT | Transportation Cross-Docking: Source Plant | CRMT_CD_SOURCE_PLANT | CHAR | 4 | Assigned to domain | WERKS | |||
SUPPLYING_PLANT_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
SUPPLYING_VENDOR | Transportation Cross-Docking: Vendor for Source Plant | CRMT_CD_SOURCE_VENDOR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
RECEIVING_PLANT | Transportation Cross-Docking: Target Warehouse | CRMT_CD_TARGET_PLANT | CHAR | 4 | Assigned to domain | WERKS | |||
RECEIVING_PLANT_NAME | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
RECEIVING_CUSTOMER | Transportation Cross-Docking:Cust. Assigned to Tgt Warehouse | CRMT_CD_TARGET_CUSTOMER | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
DELIVERY_DATE | Delivery date | LFDAT | DATS | 8 | DATUM | ||||
DELIVERY_TIME | Time of delivery | LFUHR | TIMS | 6 | LFUHR | ||||
TIMEZONE_DELIV | Time Zone of Sending Location | CRMT_SEND_TIMEZONE | CHAR | 6 | Assigned to domain | TZNZONE | |||
ARRIVAL_DATE | Transportation Cross-Docking: Arrival Date for Delivery | CRMT_CD_ARRIVAL_DATE | DATS | 8 | DATS | ||||
TIMEZONE_ARRDATE | Time zone of recipient location | TSEGZONREC | CHAR | 6 | Assigned to domain | TZNZONE | |||
MATMOV_DATE | Goods Issue Date | WADAT | DATS | 8 | DATUM | ||||
MATMOV_TIME | Time of Goods Issue (Local, Relating to a Plant) | WAUHR | TIMS | 6 | TIME_PLANT | ||||
SHIP_TO | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
SHIP_TO_ADDR | One-line short form of formatted address | AD_LINE_S | CHAR | 80 | CHAR80 | ||||
SHIP_TO_NAME | Name of Ship-To Party | CRMT_SHIP_TO_NAME | CHAR | 35 | CRM_SHIP_TO_NAME | ||||
SALES_ORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | VSTEL | VST | |||
GEOROUTE | Description of Geographical Route | CRMT_ROUTE_ID | CHAR | 10 | CHAR10 | ||||
GEOROUTE_IND | Indicator for Change to Route | CRMT_ROUTE_IND | CHAR | 1 | CHAR1 | ||||
CR_DATE | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
CR_TIME | Time, at Which Record Was Added | ERZEIT | TIMS | 6 | UHRZT | ||||
GOODS_MOVE_STATUS | Total goods movement status | WBSTK | CHAR | 1 | STATV | ||||
MATMOV_UTC | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
DELIVERY_UTC | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
DONE | Logical Variable | CRMT_BOOLEAN | CHAR | 1 | CRM_BOOLEAN |
Key field | Non-key field |
How do I retrieve data from SAP structure CRMT_CD_DOCFLOW_DATA_HDR using ABAP code?
As CRMT_CD_DOCFLOW_DATA_HDR 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 CRMT_CD_DOCFLOW_DATA_HDR as there is no data to select.How to access SAP table CRMT_CD_DOCFLOW_DATA_HDR
Within an ECC or HANA version of SAP you can also view further information about CRMT_CD_DOCFLOW_DATA_HDR 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