BBPS_PDEXT_SUSASN_HEADER_D SAP (Shipping Notification Header Data) Structure details
Description: Shipping Notification Header Data
Related tables to BBPS_PDEXT_SUSASN_HEADER_D
Access table BBPS_PDEXT_SUSASN_HEADER_D
Structure field list including key, data, relationships and ABAP select examples
BBPS_PDEXT_SUSASN_HEADER_D 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 "Shipping Notification Header 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_BBPS_PDEXT_SUSASN_HEADER_D TYPE BBPS_PDEXT_SUSASN_HEADER_D.
The BBPS_PDEXT_SUSASN_HEADER_D table consists of various fields, each holding specific information or linking keys about Shipping Notification Header Data data available in SAP. These include GUID (Globally Unique identifier), DESCRIPTION (Name of SRM Document), POSTING_DATE (Document Date (Posting Date of Log. Business Transaction)), REF_DOC_NO (Number of the Reference Document).. 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 BBPS_PDEXT_SUSASN_HEADER_D 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 |
GUID | Globally Unique identifier | BBP_GUID | RAW | 16 | SYSUUID | ||||
DESCRIPTION | Name of SRM Document | BBP_DOCNAME | CHAR | 40 | TEXT40 | ||||
POSTING_DATE | Document Date (Posting Date of Log. Business Transaction) | BBP_POSTING_DATE | DATS | 8 | DATUM | ||||
REF_DOC_NO | Number of the Reference Document | BBP_REF_DOC | CHAR | 16 | CHAR16 | ||||
SUSASN_TRANSTYPE | SUS ASN Transportation Type | BBP_SUSASN_TRANS_TYPE | CHAR | 4 | CHAR4 | ||||
SUSASN_TRANSID | SUS ASN Transportation ID | BBP_SUSASN_TRANS_ID | CHAR | 20 | CHAR20 | ||||
SUSASN_BILL_LAD | SUS Bill of Lading | BBP_SUSASN_BILL_OF_LADING | CHAR | 35 | CHAR35 | ||||
INCOTERM_KEY | Incoterm Key | BBP_INCOTERM_KEY | CHAR | 3 | Assigned to domain | BBP_INCOTERM_KEY | |||
INCOTERM_LOC | Incoterm Location | BBP_INCOTERM_LOCATION | CHAR | 28 | BBP_INCOTERM_LOCATION | ||||
PMNTTRMS | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
SK_COUNTRY | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
SK_SCENARIO1 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
SK_SCENARIO2 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
SK_SCENARIO3 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
SK_SCENARIO4 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
SK_SCENARIO5 | Key of a Scenario for Field Extension | BBP_CUF_SCENARIO_KEY | CHAR | 3 | BBP_CUF_SCENARIO_KEY | ||||
DUMMY_EEW_PDHSS_SUSASN | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
.INCLU--AP | 0 | ||||||||
BBP_ICC_EXC_NUM | Excise Document Number | BBP_ICC_EXNUM_IN | CHAR | 10 | BBP_ICC_EXNUM_IN_D | ||||
BBP_ICC_EXC_DATE | Excise Document Date | BBP_ICC_EXDATE_IN | DATS | 8 | BBP_ICC_EXDAT_DATE_D | ||||
BBP_ICC_EXC_TXT | Text Information for Country Versions | BBP_ICC_TEXT | CHAR | 60 | BBP_ICC_TXT_D | ||||
BBP_ICC_EXC_PARK | General Flag | FLAG | CHAR | 1 | FLAG | ||||
DUMMY_EEW_PDHSC_SUSASN | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
COPY_OF_GUID | GUID Object is a Copy of | BBP_COPY_OF_GUID | RAW | 16 | SYSUUID | ||||
PROCESS_TYPE | Business Transaction Type | CRMT_PROCESS_TYPE_DB | CHAR | 4 | Assigned to domain | CRM_PROCESS_TYPE | |||
OBJECT_ID | Transaction Number | CRMT_OBJECT_ID_DB | CHAR | 10 | ALPHA | CRM_OBJECT_ID | |||
REF_OBJECT_ID | Reference Transaction Number | BBP_REF_OBJECT_ID | CHAR | 10 | BBP_OBJECT_ID | ||||
DESCR_LANGUAGE | Language Key of Description | CRMT_PROCESS_DESCRIPTION_LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
EXT_HEADER | Creation Date of PO in External System (SRM/MM) | BBP_EXT_CREATE_DATE | DATS | 8 | DATE | ||||
LOGICAL_SYSTEM | Logical System | CRMT_LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
EXT_CREATE_DATE | Creation Date of PO in External System (SRM/MM) | BBP_EXT_CREATE_DATE | DATS | 8 | DATE | ||||
IR_IND | Invoice Receipt Indicator | REPOS | CHAR | 1 | XFELD | ||||
CO_CODE | Company Code in FI System | BBP_CO_CODE | CHAR | 4 | Assigned to domain | BUKRS | |||
LOGSYS_FI | Logical System of FI System | BBP_LOGSYS_FI | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | BBP_BACKEND_DESTINATION_F4 | |
BE_LOG_SYSTEM | Logical System of Logistics Backend | BE_LOG_SYSTEM | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
BE_OBJECT_TYPE | Follow-On Document Object Type in Back-End System | BE_OBJECT_TYPE | CHAR | 10 | Assigned to domain | OJ_NAME | |||
BE_OBJECT_ID | Follow-On Document Object ID in Back-End System | BE_OBJECT_ID | CHAR | 20 | BBP_BE_OBJECT_ID | ||||
BE_REFOBJ_TYPE | Reference Object Type in Back-End System | BE_REFOBJ_TYPE | CHAR | 10 | Assigned to domain | OJ_NAME | |||
BE_REFOBJ | Reference Object in Back-End System | BE_REFOBJ | CHAR | 20 | BBP_BE_OBJECT_ID | ||||
BE_REFOBJ_ITEM | Reference Object Item in Back-End System | BE_REFOBJ_ITEM | CHAR | 10 | BBP_REF_ITEM | ||||
BE_PUR_GROUP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
BE_PUR_ORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
DUMMY_EEW_PD_HD_SWD_SUSASN | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
DUMMY_EEW_PD_HD_CSD_SUSASN | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
CREATED_BY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
CREATED_AT | Transaction was Created at this Time | CRMT_CREATED_AT | DEC | 15 | TSTPS | BCOS_TSTMP | |||
CHANGED_BY | Name of Person Responsible for Changing Object | BBP_CHNAM | CHAR | 12 | USNAM | ||||
CHANGED_AT | Time of Last Change to the Transaction | CRMT_CHANGED_AT | DEC | 15 | TSTPS | BCOS_TSTMP | |||
SRC_GUID | Reference Document GUID | BBP_SRC_H_GUID | RAW | 16 | SYSUUID | ||||
SRC_OBJECT_TYPE | Object Type of Reference Document | BBP_SRC_H_OBJ_TYP | CHAR | 10 | Assigned to domain | OJ_NAME | |||
TZONE | Time Zone for Date and Time Fields of Procurement Document | BBP_TZONE | CHAR | 6 | BBP_TZONE | ||||
GROSS_WEIGHT | Gross Weight | BBP_GROSS_WEIGHT | QUAN | 15 | BBP_GROSS_WEIGHT | ||||
GROSSWEIGHT_UNIT | Unit of Weight | BBP_WEIGHT_UNIT | UNIT | 3 | BBP_WEIGHT_UNIT | ||||
NET_WEIGHT | Net Weight | BBP_NET_WEIGHT | QUAN | 15 | BBP_NET_WEIGHT | ||||
NETWEIGHT_UNIT | Unit of Weight | BBP_WEIGHT_UNIT | UNIT | 3 | BBP_WEIGHT_UNIT | ||||
VOLUME_VAL | Volumes, Pack Size | BBP_VOLUME | QUAN | 15 | BBP_VOLUME | ||||
VOLUME_UNIT | Volume Unit | BBP_VOLUME_UNIT | UNIT | 3 | BBP_VOLUME_UNIT | ||||
CURRENCY_ISO | ISO Currency Code | BBP_ISOCD | CHAR | 3 | ISOCD | ||||
LANGU_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
GROSS_AMOUNT_EXT | Amount | BBP_BAPI_AMOUNT | DEC | 23(4) | BAPICURR | ||||
REF_OBJECT_ID_EXT | Business Transaction Document ID | BBP_BTD_ID | CHAR | 35 | BBP_BTD_ID | ||||
ACCEPT_STAT_CODE | Acceptance Status | BBP_ACCEPT_STAT_CODE | CHAR | 1 | BBP_ACCEPT_STAT_CODE | ||||
ACTION_CODE | Control: Creating, Changing, and Deleting Objects | BBP_ACTION_CODE | CHAR | 2 | BBP_ACTION_CODE | ||||
DELIV_DATE | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
DELIV_TIME | Delivery Time of the Item | BBP_DELIV_TIME | TIMS | 6 | TIME |
Key field | Non-key field |
How do I retrieve data from SAP structure BBPS_PDEXT_SUSASN_HEADER_D using ABAP code?
As BBPS_PDEXT_SUSASN_HEADER_D 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 BBPS_PDEXT_SUSASN_HEADER_D as there is no data to select.How to access SAP table BBPS_PDEXT_SUSASN_HEADER_D
Within an ECC or HANA version of SAP you can also view further information about BBPS_PDEXT_SUSASN_HEADER_D 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