WSPO_ENTRY SAP (SAP Retail Store PO: Fields for Initial Screen) Structure details
Description: SAP Retail Store PO: Fields for Initial Screen
Structure field list including key, data, relationships and ABAP select examples
WSPO_ENTRY 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 Retail Store PO: Fields for Initial Screen" 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_WSPO_ENTRY TYPE WSPO_ENTRY.
The WSPO_ENTRY table consists of various fields, each holding specific information or linking keys about SAP Retail Store PO: Fields for Initial Screen data available in SAP. These include VNDR_ID (SAP Retail Store: Vendor or Plant Number), VNDR_TYPE (SAP Retail Store: Indicator Vendor or Plant), VENDOR_NO (Account Number of Vendor or Creditor), PLANT (Plant).. 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 WSPO_ENTRY 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 |
| VNDR_ID | SAP Retail Store: Vendor or Plant Number | WSRS_VENDOR_SITE_ID | CHAR | 10 | |||||
| VNDR_TYPE | SAP Retail Store: Indicator Vendor or Plant | WSRS_VENDOR_SITE_TYPE | CHAR | 1 | WSRS_VENDOR_SITE_TYPE | ||||
| VENDOR_NO | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| PLANT | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| VNDR_TYPE_D | SAP Retail Store: Description 20 Characters | WSRS_DESCR_20 | CHAR | 20 | |||||
| VNDR_TYPE_INP | SAP Retail Store: Indicator Vendor or Plant | WSRS_VENDOR_SITE_TYPE | CHAR | 1 | WSRS_VENDOR_SITE_TYPE | ||||
| NAME_1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
| CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| MAT_KEY_VNDR | Long material number for SAP Retail Store | WSRS_MAT_KEY | CHAR | 40 | WSRS_MAT_KEY | ||||
| MATERIAL_VNDR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| MATID | SAP Retail Store: Material ID Type | MATID | CHAR | 4 | ART_ID | ||||
| DOC_TYPE | Purchasing Document Type | ESART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
| DOC_DATE | Purchasing Document Date | EBDAT | DATS | 8 | DATUM | ||||
| DOC_DATE_CHAR | SAP Retail Store: Output Format of a Date | WSRS_DATE_CHAR | CHAR | 10 | |||||
| MAT_KEY_DOC | Long material number for SAP Retail Store | WSRS_MAT_KEY | CHAR | 40 | WSRS_MAT_KEY | ||||
| MATERIAL_DOC | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| RET_ITEM_ALL | SAP Retail Store PO: Indicator Only/No Returns Items | WSPO_RET_ITEM_ALL | CHAR | 1 | |||||
| PO_NUMBER | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| STATUS | SAP Retail Store PO: Document Status | WSPO_DOC_STATUS | CHAR | 1 | |||||
| MAT_KEY_VNDR_TYPED_IN | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| MAT_KEY_DOC_TYPED_IN | Checkbox | XFELD | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure WSPO_ENTRY using ABAP code?
As WSPO_ENTRY 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 WSPO_ENTRY as there is no data to select.How to access SAP table WSPO_ENTRY
Within an ECC or HANA version of SAP you can also view further information about WSPO_ENTRY 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