WVLB_LB_COUPLE SAP (Definition of Component for a Load Building Combination) Structure details
Description: Definition of Component for a Load Building Combination
Related tables to WVLB_LB_COUPLE
Access table WVLB_LB_COUPLE
Structure field list including key, data, relationships and ABAP select examples
WVLB_LB_COUPLE 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 "Definition of Component for a Load Building Combination" 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_WVLB_LB_COUPLE TYPE WVLB_LB_COUPLE.
The WVLB_LB_COUPLE table consists of various fields, each holding specific information or linking keys about Definition of Component for a Load Building Combination data available in SAP. These include LIFNR (Vendor Account Number), EKORG (Purchasing Organization), LTSNR (Vendor Subrange), WERKS (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 (Deep)
SAP WVLB_LB_COUPLE 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 |
| LBPRF | Internal number of load building combination | WVLBLBPRFINT | INT4 | 10 | SYST_LONG | ||||
| LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | Assigned to domain | LTSNR | |||
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| VENDOR_EKORZ | Reference Purchasing Organization | WEKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| PLANT_EKORZ | Reference Purchasing Organization | WEKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| BOPNR | Restriction Profile for PO-Based Load Building | BOPNR | CHAR | 4 | CHAR4 | ||||
| DESIRE_VENSL | Vendor service level | VENSL | DEC | 4(1) | DEC3_1 | ||||
| FABKL | Factory calendar key | FABKL | CHAR | 2 | Assigned to domain | WFCID | |||
| KUNNR | Customer number of plant | KUNNR_WK | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| GTERM | Scheduling according to purchasing info record or agreement | GTERM | CHAR | 1 | XFELD | ||||
| TODAY_0 | General date field | WVLBDATE | DATS | 8 | DATUM | ||||
| TODAY_1 | General date field | WVLBDATE | DATS | 8 | DATUM | ||||
| TODAY_2 | General date field | WVLBDATE | DATS | 8 | DATUM | ||||
| FKDAY_T0 | Factory calendar day | FKDAY | DEC | 5 | FKDAY | ||||
| FKDAY_T1 | Factory calendar day | FKDAY | DEC | 5 | FKDAY | ||||
| FKDAY_T2 | Factory calendar day | FKDAY | DEC | 5 | FKDAY | ||||
| CUR_VENSL_T0 | Vendor service level | VENSL | DEC | 4(1) | DEC3_1 | ||||
| CUR_VENSL_T1 | Vendor service level | VENSL | DEC | 4(1) | DEC3_1 | ||||
| CUR_VENSL_T2 | Vendor service level | VENSL | DEC | 4(1) | DEC3_1 | ||||
| PO_DATE | General date field | WVLBDATE | DATS | 8 | DATUM | ||||
| DELIVERY_DATE | General date field | WVLBDATE | DATS | 8 | DATUM | ||||
| KKOWK | Indicator: Conditions at plant level | KKOWK | CHAR | 1 | KKOWK | ||||
| RESULT_ENTRY | Entry in results list of automatic load building | WVLBLISTENTRY | CHAR | 1 | CHAR1_X | ||||
| LFRHY | Planning cycle | LFRHY | CHAR | 3 | Assigned to domain | MRPPP | |||
| PLIFZ | Planned Delivery Time in Days | PLIFZ | DEC | 3 | DEC3 | ||||
| SOURCETIME | Runtime in Hours, Minutes and Seconds | WVLBSOURCETIME | TIMS | 6 | T | ||||
| NUM_R_MATNR | Number of Materials Read | WVLBNUMRMATNR | NUMC | 10 | NUM10 | ||||
| NUM_R_EKPO | Number of Purchase Order Items Read | WVLBNUMREKPO | NUMC | 10 | NUM10 | ||||
| NUM_R_EBAN | Number of Purchase Requisition Items Read | WVLBNUMREBAN | NUMC | 10 | NUM10 | ||||
| NUM_W_EKPO | Number of Purchase Order Items Changed and Created | WVLBNUMWEKPO | NUMC | 10 | NUM10 | ||||
| NUM_W_EBAN | Number of Purchase Requisition Items Changed | WVLBNUMWEBAN | NUMC | 10 | NUM10 | ||||
| NUM_W_WBO2 | Number of Entries in Result List (Table WBO2) | WVLBNUMWWBO2 | NUMC | 10 | NUM10 |
| Key field | Non-key field |
How do I retrieve data from SAP structure WVLB_LB_COUPLE using ABAP code?
As WVLB_LB_COUPLE 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 WVLB_LB_COUPLE as there is no data to select.How to access SAP table WVLB_LB_COUPLE
Within an ECC or HANA version of SAP you can also view further information about WVLB_LB_COUPLE 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