VNLCO SAP () Structure details
Description:
Structure field list including key, data, relationships and ABAP select examples
VNLCO 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 "" 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_VNLCO TYPE VNLCO.
The VNLCO table consists of various fields, each holding specific information or linking keys about data available in SAP. These include MANDT (Client), LNRLS (IS-H: Service Sequence Number), LNRKO (IS-HCO: Sequence Number of Account Assignment), UBVON (IS-HCO: Start of Transfer).. 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 VNLCO 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| LNRLS | IS-H: Service Sequence Number | LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
| LNRKO | IS-HCO: Sequence Number of Account Assignment | ISH_LNRKO | NUMC | 5 | ISH_LNRKO | ||||
| UBVON | IS-HCO: Start of Transfer | ISH_UBVON | DATS | 8 | RI_DATUM | ||||
| UBBIS | IS-HCO: End of Transfer | ISH_UBBIS | DATS | 8 | RI_DATUM | ||||
| UMENG | IS-HCO: Transferred Service Quantity | ISH_UMENG | NUMC | 4 | LEISMENGE | ||||
| LSTAR | IS-HCO: Activity Type | ISH_LSTAR | CHAR | 6 | ISH_LSTAR | ||||
| LMENG | IS-HCO: Activity Quantity | ISH_LMENG | QUAN | 15(3) | MENGV8 | ||||
| LEINH | Activity Unit | LEINH | UNIT | 3 | T006 | CUNIT | MEINS | ||
| ORGID | Identification Key of Organizational Unit | ORGID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OGE | |
| ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ANPOE | IS-H: Nursing Organizational Unit Requesting the Service | ANPOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ERBOE | IS-H: Organizational Unit that Performs the Service | ERBOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| SKOST | IS-HCO: Sender | ISH_SKOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | ||
| EKOST | IS-HCO: Receiver (Cost Center) | ISH_EKOST | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | ||
| EAUFN | IS-HCO: Receiver (Order) | ISH_EAUFN | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ||
| KOKRS | Controlling Area | KOKRS | CHAR | 4 | Assigned to domain | CACCD | CAC | ||
| BELNR | Document Number | CO_BELNR | CHAR | 10 | Assigned to domain | ALPHA | CO_BELNR | BLN | |
| STOBL | Document Number | CO_BELNR | CHAR | 10 | Assigned to domain | ALPHA | CO_BELNR | BLN | |
| STORN | IS-H: Cancellation Indicator | RI_STORN | CHAR | 1 | XFELD | ||||
| BLDAT | Document Date | CO_BLDAT | DATS | 8 | DATUM | ||||
| BUDAT | Posting Date | CO_BUDAT | DATS | 8 | DATUM | ||||
| UBDAT | Date Document Was Created | CO_CPUDT | DATS | 8 | DATUM | ||||
| USNAM | User name | USNAM | CHAR | 12 | Assigned to domain | XUBNAME | USR | ||
| TCODE | IS-HCO: Transaction Code of Transfer | ISH_UTCODE | CHAR | 20 | Assigned to domain | TCODE | |||
| VORGN | IS-HCO: Business Transaction | ISH_VORGN | CHAR | 4 | ISH_VORGN | ||||
| PERIO | IS-H: Posting period | ISH_POPER | NUMC | 3 | POPER | ||||
| GJAHR | IS-H: Fiscal Year | ISH_BDATJ | NUMC | 4 | GJAHR | GJAHR | |||
| BZLST | Sequence Number of Reference Service | ISH_BZLST | CHAR | 10 | ALPHA | LNRLS | |||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure VNLCO using ABAP code?
As VNLCO 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 VNLCO as there is no data to select.How to access SAP table VNLCO
Within an ECC or HANA version of SAP you can also view further information about VNLCO 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