WISP_KEYS_SAP_M02 SAP (Retail Planning: Plng Char. from Field Catalogs for App. 02) Structure details
Description: Retail Planning: Plng Char. from Field Catalogs for App. 02
Related tables to WISP_KEYS_SAP_M02
Access table WISP_KEYS_SAP_M02
Structure field list including key, data, relationships and ABAP select examples
WISP_KEYS_SAP_M02 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 "Retail Planning: Plng Char. from Field Catalogs for App. 02" 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_WISP_KEYS_SAP_M02 TYPE WISP_KEYS_SAP_M02.
The WISP_KEYS_SAP_M02 table consists of various fields, each holding specific information or linking keys about Retail Planning: Plng Char. from Field Catalogs for App. 02 data available in SAP. These include KNUMA (Agreement (various conditions grouped together)), DATBI (End date of validity period of an arrangement), WAERS (Purchase order currency), LMEIN (Base Unit of Measure).. 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: Not classified
SAP WISP_KEYS_SAP_M02 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 |
BOLIF | Condition granter | BOGEW | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | |
KNUMA | Agreement (various conditions grouped together) | KNUMA | CHAR | 10 | KONA | ALPHA | KNUMA | VMBO | |
DATBI | End date of validity period of an arrangement | MC_DATBI | DATS | 8 | DATUM | ||||
WAERS | Purchase order currency | BSTWA | CUKY | 5 | TCURC | WAERS | |||
LMEIN | Base Unit of Measure | LAGME | UNIT | 3 | T006 | CUNIT | MEINS | ||
LNRZB | Agency business: Payee | W_LIFZE | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
MWSKZ | Agency business: Tax code (input tax) | MWSKZ_LF | CHAR | 2 | T007A | MWSKZ | |||
LANDL | Supplying Country | LANDL | CHAR | 3 | T005 | LAND1 | |||
LFTYP | Agency business: Billing category | WFTYP | CHAR | 2 | WFTYP | ||||
NPLNR | Network Number for Account Assignment | NPLNR | CHAR | 12 | AUFK | ALPHA | AUFNR | NET | |
SAKTO | G/L Account Number | SAKNR | CHAR | 10 | SKA1 | ALPHA | SAKNR | SAK | C_SAKNR |
KAPPL | Application | KAPPL | CHAR | 2 | Assigned to domain | KAPPL | KAP | ||
DATUM | Date | DATUM | DATS | 8 | DATUM | ||||
KOTABNR | Condition table | KOTABNR | NUMC | 3 | Assigned to domain | KOTABNR | KON | ||
VARKEY | Variable key 100 bytes | VAKEY | CHAR | 100 | VAKEY | ||||
KVEWE | Usage of the condition table | KVEWE | CHAR | 1 | Assigned to domain | KVEWE | KVW | ||
BLTYP | Document category for document index updates | BLTYP | CHAR | 2 | BLTYP | ||||
LIFEX | External Identification of Delivery Note | LIFEX | CHAR | 35 | TEXT35 | ||||
LGTOR | Door for Warehouse Number | LGTOR | CHAR | 3 | T30B | LGTOR | |||
TRATY | Means-of-Transport Type | TRATY | CHAR | 4 | TVTY | TRATY | |||
TRAID | Means of Transport ID | TRAID | CHAR | 20 | TRAID | ||||
BOLNR | Bill of lading | BOLNR | CHAR | 35 | CHAR35 | ||||
MFRGR | Material freight group | MFRGR | CHAR | 8 | TMFG | MFRGR | |||
VGBEL | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
KONZS | Group key | KONZS | CHAR | 10 | KONZS | ||||
LLIEF | Supplying Vendor | LLIEF | CHAR | 10 | LFA1 | ALPHA | LIFNR | LLI | |
RESWK | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | T001W | WERKS | |||
LIFRE | Different Invoicing Party | LIFRE | CHAR | 10 | LFA1 | ALPHA | LIFNR | LRE | |
INFNR | Number of Purchasing Info Record | INFNR | CHAR | 10 | EINA | ALPHA | INFNR | INF | MEIN_C |
KUNRE | Bill-to party | KUNRE | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
MWSK2 | Agency business: Tax code (output tax) | MWSKZ_RB | CHAR | 2 | T007A | MWSKZ | |||
EBELN | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
SUBMI | Collective Number | SUBMI | CHAR | 10 | CHAR10 | ||||
ESOKZ | Purchasing info record category | ESOKZ | CHAR | 1 | ESOKZ | ESO | |||
PSTYP | Item Category in Purchasing Document | PSTYP | CHAR | 1 | T163 | PSTYP | |||
EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | EKPO | EBELP | BSP | ||
SRVPOS | Activity Number | ASNUM | CHAR | 18 | Assigned to domain | ALPHA | ASNUM | ASN | |
LBNUM | Short Description of Service Type | LBNUM | CHAR | 3 | CHAR3 | LBR | |||
AUSGB | Edition of Service Type | AUSGB | NUMC | 4 | NUMC4 | AGB | |||
STLVPOS | Standard Service Catalog Item | STLVPOS | CHAR | 18 | CHAR18 | ||||
ASTYP | Service Category | ASTYP | CHAR | 4 | Assigned to domain | ASTYP | ASY | ||
PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER |
Key field | Non-key field |
How do I retrieve data from SAP structure WISP_KEYS_SAP_M02 using ABAP code?
As WISP_KEYS_SAP_M02 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 WISP_KEYS_SAP_M02 as there is no data to select.How to access SAP table WISP_KEYS_SAP_M02
Within an ECC or HANA version of SAP you can also view further information about WISP_KEYS_SAP_M02 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