JVTLIEFBAR SAP (IS-M/SD: Delivery/Home Delivery/Pickup Viability Sets) Table details
Description: IS-M/SD: Delivery/Home Delivery/Pickup Viability Sets
Table field list including key, data, relationships and ABAP select examples
JVTLIEFBAR is a standard SAP Table which is used to store IS-M/SD: Delivery/Home Delivery/Pickup Viability Sets data and is available within R/3 SAP systems depending on the version and release level.
The JVTLIEFBAR table consists of various fields, each holding specific information or linking keys about IS-M/SD: Delivery/Home Delivery/Pickup Viability Sets data available in SAP. These include LIEFBARNR (Sequence number for delivery/home delivery viability set), GUELTIGAB (Valid-From Date), GUELTIGBIS (Valid-To Date), GBISBEEND (Valid to Date After Closed Delivery Via. Sets are Released).. 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: A - Application table (master and transaction data)Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP JVTLIEFBAR table 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 | |||
LIEFBARNR | Sequence number for delivery/home delivery viability set | LIEFBARNR | CHAR | 9 | LIEFBARNR | ||||
GUELTIGAB | Valid-From Date | GUELTIGVON | DATS | 8 | DATUM | JSA | |||
GUELTIGBIS | Valid-To Date | GUELTIGBIS | DATS | 8 | DATUM | JSB | |||
GBISBEEND | Valid to Date After Closed Delivery Via. Sets are Released | GBISBEEND | DATS | 8 | DATUM | ||||
XAUFTRREL | IS-M: Use of delivery viability set possible in order | XAUFTRREL | CHAR | 1 | XFELD | ||||
LOESCH_KZ | Deletion Flag for Master Data in Media Sales & Distribution | LOEVM_ISP | CHAR | 1 | XFELD | ||||
DRUERZART | Publication Type | DRUERZART | CHAR | 1 | TJD17 | DRUERZART | |||
DRERZ | Publication | DRERZ | CHAR | 8 | JDTDRER | ALPHA | DRERZ | JD1 | MJD1 |
PVA | Edition | PVA | CHAR | 8 | JDTPVA | ALPHA | PVA | JD2 | |
BEZUGSTYP | Mix Type | BEZUGSTYP_JE_PVA | CHAR | 2 | JDTBEZTYP | BEZUGSTYP_JE_PVA | JD3 | MJD7 | |
VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
LIEFERART | Delivery Type | LIEFERART | CHAR | 2 | TJV01 | LIEFERART | JLA | ||
GEOEIN | Number of Geographical Unit | GEOEIN | CHAR | 10 | JSTGEOEINH | ALPHA | GEOEIN | GEO | |
BEZIRK | Carrier Route | BEZIRK | CHAR | 10 | JVTBEZIRK | ALPHA | BEZIRK | BEZ | MJVC |
ABHOLSTELL | IS-M/SD: Customer Pickup Point | ABHOLSTELL | CHAR | 10 | JGTGPNR | ALPHA | GPNR | ||
BEZRUNDE | IS-M: Delivery Round | BEZRUNDE | CHAR | 10 | JVTRUNDE | ALPHA | BEZRUNDE | JBR | |
DRUCKEREI | Plant | JWERK | CHAR | 4 | T001W | WERKS | WRK | ||
AENDNRBIS | Change Number for To-Date of Structural Change | AENDNRBIS | CHAR | 9 | JSTAENDER | ALPHA | AENDNR | ||
AENDNRBISD | Date of Change Number Used to Change To-Date | AENDNRBISD | CHAR | 1 | AENDNRARTD | ||||
AENDNRAB | Change Number for From-Date of Structure Change | AENDNRAB | CHAR | 9 | JSTAENDER | ALPHA | AENDNR | ||
AENDNRABD | Date of Change Number Used to Change From-Date | AENDNRABD | CHAR | 1 | AENDNRARTD | ||||
AENDNRINIT | Initiating Change Number | AENDNRINIT | CHAR | 9 | JSTAENDER | ALPHA | AENDNR | ||
AENDLFDNRI | Sequence Number of Initiating Change Number | AENDLFDNRI | NUMC | 4 | AENDLFDNR | ||||
AENDNRAKT | Change Number in Process | AENDNRAKT | CHAR | 9 | JSTAENDER | ALPHA | AENDNR | ||
AENDLFDNRA | Sequence Number of Currently Operative Change Number | AENDLFDNRA | NUMC | 4 | AENDLFDNR | ||||
XAENDER | Structure information being changed on other change number | XAENDER | CHAR | 1 | XFELD | ||||
XSTRUAKTIV | Structure information inactive | XSTRUAKTIV | CHAR | 1 | XSTRUAKTIV | ||||
FCCODE | Function Control Code for Structure Changes | FCCODE | CHAR | 2 | FCCODE | ||||
DBCODEFREI | DB Code for Structural Changes | DBCODE | CHAR | 1 | DBCODE | ||||
ERFUSER | Created By | ERFUSER | CHAR | 12 | USNAM | ||||
ERFDATE | Created On | ERFDATE | DATS | 8 | DATUM | ||||
ERFTIME | Time Created | ERFTIME | TIMS | 6 | UZEIT | ||||
AENUSER | Last Changed By | AENUSER | CHAR | 12 | USNAM | ||||
AENDATE | Date of Last Change | AENDATE | DATS | 8 | DATUM | ||||
AENTIME | Time of Last Change | AENTIME | TIMS | 6 | UZEIT |
Key field | Non-key field |
How do I retrieve data from SAP table JVTLIEFBAR using ABAP code
The following ABAP code Example will allow you to do a basic selection on JVTLIEFBAR to SELECT all data from the tableDATA: WA_JVTLIEFBAR TYPE JVTLIEFBAR.
SELECT SINGLE *
FROM JVTLIEFBAR
INTO CORRESPONDING FIELDS OF WA_JVTLIEFBAR
WHERE...
How to access SAP table JVTLIEFBAR
Within an ECC or HANA version of SAP you can also view further information about JVTLIEFBAR 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