INCL_EEW_PD_SEARCH_HDR_SWF_BID SAP (SAP Int. Enh.(IBUs...) in Bid Invitatn Header:Search Res.) Structure details
Description: SAP Int. Enh.(IBUs...) in Bid Invitatn Header:Search Res.
Related tables to INCL_EEW_PD_SEARCH_HDR_SWF_BID
Access table INCL_EEW_PD_SEARCH_HDR_SWF_BID
Structure field list including key, data, relationships and ABAP select examples
INCL_EEW_PD_SEARCH_HDR_SWF_BID 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 "SAP Int. Enh.(IBUs...) in Bid Invitatn Header:Search Res." 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_INCL_EEW_PD_SEARCH_HDR_SWF_BID TYPE INCL_EEW_PD_SEARCH_HDR_SWF_BID.
The INCL_EEW_PD_SEARCH_HDR_SWF_BID table consists of various fields, each holding specific information or linking keys about SAP Int. Enh.(IBUs...) in Bid Invitatn Header:Search Res. data available in SAP. These include PS_US01 (User-Specified Status 01), PS_US02 (User-Specified Status 02), PS_US03 (User-Specified Status 03), PS_US04 (User-Specified Status 04).. 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 INCL_EEW_PD_SEARCH_HDR_SWF_BID 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 |
DUMMY_EEW_PD_SEARCH_HSS_BID | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
.INCLU--AP | 0 | ||||||||
PS_US01 | User-Specified Status 01 | /SAPPSSRM/_US_01 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US02 | User-Specified Status 02 | /SAPPSSRM/_US_02 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US03 | User-Specified Status 03 | /SAPPSSRM/_US_03 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US04 | User-Specified Status 04 | /SAPPSSRM/_US_04 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US05 | User-Specified Status 05 | /SAPPSSRM/_US_05 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US06 | User-Specified Status 06 | /SAPPSSRM/_US_06 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US07 | User-Specified Status 07 | /SAPPSSRM/_US_07 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US08 | User-Specified Status 08 | /SAPPSSRM/_US_08 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US09 | User-Specified Status 09 | /SAPPSSRM/_US_09 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US10 | User-Specified Status 10 | /SAPPSSRM/_US_10 | CHAR | 5 | Assigned to domain | J_ESTAT | /SAPPSSRM/H_US | ||
PS_US01_TXT | User-Specified Status 01 Description | /SAPPSSRM/_US_TXT_01 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US02_TXT | User-Specified Status 02 Description | /SAPPSSRM/_US_TXT_02 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US03_TXT | User-Specified Status 03 Description | /SAPPSSRM/_US_TXT_03 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US04_TXT | User-Specified Status 04 Description | /SAPPSSRM/_US_TXT_04 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US05_TXT | User-Specified Status 05 Description | /SAPPSSRM/_US_TXT_05 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US06_TXT | User-Specified Status 06 Description | /SAPPSSRM/_US_TXT_06 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US07_TXT | User-Specified Status 07 Description | /SAPPSSRM/_US_TXT_07 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US08_TXT | User-Specified Status 08 Description | /SAPPSSRM/_US_TXT_08 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US09_TXT | User-Specified Status 09 Description | /SAPPSSRM/_US_TXT_09 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
PS_US10_TXT | User-Specified Status 10 Description | /SAPPSSRM/_US_TXT_10 | CHAR | 30 | TEXT30 | /SAPPSSRM/H_TJ30 | |||
.INCLU--AP | 0 | ||||||||
PS_IPT | Public Sector Item Type | /SAPPSSRM/_IPT | CHAR | 10 | Assigned to domain | /SAPPSSRM/_IPT | |||
EXLIN | Configurable Line Item Number | /SAPSRM/EXLIN | CHAR | 40 | /SAPSRM/EXLIN |
Key field | Non-key field |
How do I retrieve data from SAP structure INCL_EEW_PD_SEARCH_HDR_SWF_BID using ABAP code?
As INCL_EEW_PD_SEARCH_HDR_SWF_BID 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 INCL_EEW_PD_SEARCH_HDR_SWF_BID as there is no data to select.How to access SAP table INCL_EEW_PD_SEARCH_HDR_SWF_BID
Within an ECC or HANA version of SAP you can also view further information about INCL_EEW_PD_SEARCH_HDR_SWF_BID 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