NELBP SAP (Main Criterion in Vendor Evaluation with Update Indicator) Structure details
Description: Main Criterion in Vendor Evaluation with Update Indicator
Structure field list including key, data, relationships and ABAP select examples
NELBP 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 "Main Criterion in Vendor Evaluation with Update Indicator" 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_NELBP TYPE NELBP.
The NELBP table consists of various fields, each holding specific information or linking keys about Main Criterion in Vendor Evaluation with Update Indicator data available in SAP. These include MANDT (Client), EKORG (Purchasing Organization), LIFNR (Vendor Account Number), HKRIT (Key for evaluation criterion).. 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 NELBP 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 | |||
EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
HKRIT | Key for evaluation criterion | HKRIT | CHAR | 2 | T147G | HKRIT | |||
BEURT | Score | BEWER1 | DEC | 3 | BEWER | ||||
LEBEW | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
LEBDT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
SPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
TXTSL | Text key | TXTSL | CHAR | 5 | CHAR5 | ||||
KRT01 | Score for subcriterion 01 | KRT01 | DEC | 3 | BEWER | ||||
KRT02 | Score for subcriterion 02 | KRT02 | DEC | 3 | BEWER | ||||
KRT03 | Score for subcriterion 03 | KRT03 | DEC | 3 | BEWER | ||||
KRT04 | Score for subcriterion 04 | KRT04 | DEC | 3 | BEWER | ||||
KRT05 | Score for subcriterion 05 | KRT05 | DEC | 3 | BEWER | ||||
KRT06 | Score for subcriterion 06 | KRT06 | DEC | 3 | BEWER | ||||
KRT07 | Score for subcriterion 07 | KRT07 | DEC | 3 | BEWER | ||||
KRT08 | Score for subcriterion 08 | KRT08 | DEC | 3 | BEWER | ||||
KRT09 | Score for subcriterion 09 | KRT09 | DEC | 3 | BEWER | ||||
KRT10 | Score for subcriterion 10 | KRT10 | DEC | 3 | BEWER | ||||
KRT11 | Score for subcriterion 11 | KRT11 | DEC | 3 | BEWER | ||||
KRT12 | Score for subcriterion 12 | KRT12 | DEC | 3 | BEWER | ||||
KRT13 | Score for subcriterion 13 | KRT13 | DEC | 3 | BEWER | ||||
KRT14 | Score for subcriterion 14 | KRT14 | DEC | 3 | BEWER | ||||
KRT15 | Score for subcriterion 15 | KRT15 | DEC | 3 | BEWER | ||||
KRT16 | Score for subcriterion 16 | KRT16 | DEC | 3 | BEWER | ||||
KRT17 | Score for subcriterion 17 | KRT17 | DEC | 3 | BEWER | ||||
KRT18 | Score for subcriterion 18 | KRT18 | DEC | 3 | BEWER | ||||
KRT19 | Score for subcriterion 19 | KRT19 | DEC | 3 | BEWER | ||||
KRT20 | Score for subcriterion 20 | KRT20 | DEC | 3 | BEWER | ||||
UPDKZ | Update indicator for vendor evaluation | UPDT | CHAR | 1 | UPDKZ |
Key field | Non-key field |
How do I retrieve data from SAP structure NELBP using ABAP code?
As NELBP 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 NELBP as there is no data to select.How to access SAP table NELBP
Within an ECC or HANA version of SAP you can also view further information about NELBP 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