ISU_BI_BILL_S_JVL_VER SAP (YAP Data at Contract Level) Structure details
Description: YAP Data at Contract Level
Related tables to ISU_BI_BILL_S_JVL_VER
Access table ISU_BI_BILL_S_JVL_VER
Structure field list including key, data, relationships and ABAP select examples
ISU_BI_BILL_S_JVL_VER 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 "YAP Data at Contract Level" 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_ISU_BI_BILL_S_JVL_VER TYPE ISU_BI_BILL_S_JVL_VER.
The ISU_BI_BILL_S_JVL_VER table consists of various fields, each holding specific information or linking keys about YAP Data at Contract Level data available in SAP. These include MANDT (Client), OPBEL (Budget billing plan), VERTRAG (Reference Specifications from Contract), SPARTE (Division).. 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 ISU_BI_BILL_S_JVL_VER 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 |
WA_JVL_VER | 0 | ||||||||
MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
OPBEL | Budget billing plan | ABPLANNR | CHAR | 12 | ALPHA | OPBEL_KK | OP1 | EABP | |
VERTRAG | Reference Specifications from Contract | VTREF_KK | CHAR | 20 | ALPHA | VTREF_KK | VTZ | ||
SPARTE | Division | SPART_KK | CHAR | 2 | SPART | SPA | |||
BUKRS | Company Code | BUKRS | CHAR | 4 | BUKRS | BUK | C_T001 | ||
WAERS | Currency Key | WAERS | CUKY | 5 | WAERS | FWS | |||
JVLBASIS | Base amount of yearly advance payment | JVLBASIS | CURR | 13(2) | WRTV7 | ||||
JVLBETR | Yearly advance payment amount | JVLBETR | CURR | 13(2) | WRTV7 | ||||
JVLBETRTAX | Tax amount of the YAP amount | JVLBETRTAX | CURR | 13(2) | WRTV7 | ||||
JVLBONUS | Yearly advance payment bonus | JVLBONUS | CURR | 13(2) | WRTV7 | ||||
JVLBONUSTAX | Tax amount of the YAP bonus | JVLBONUSTAX | CURR | 13(2) | WRTV7 | ||||
MWSKZ | Tax on sales/purchases code | MWSKZ | CHAR | 2 | MWSKZ | ||||
FAEDN | YAP Due Date | FAEDN_JVL | DATS | 8 | DATUM | ||||
ZINSZ | Interest Calculation Rule | IRULE | CHAR | 10 | ALPHA | RRGL | |||
JVLSTATUS | Yearly advance payment status | JVLSTATUS | CHAR | 1 | JVLSTATUS | ||||
JVLTE | Participation in yearly advance payment procedure | JVLTE | NUMC | 1 | JVLTE | ||||
AKTIV | Yearly advance payment active | JVL_AKTIV | CHAR | 1 | JVL_AKTIV | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
FDATE | Lock valid from | FDATE_KK | DATS | 8 | DATUM | ||||
TDATE | Lock valid to | TDATE_KK | DATS | 8 | DATUM | ||||
BON_HVORG | Internal Main Transaction of YAP Bonus | BON_HVORG | CHAR | 4 | HVORG_KK | ||||
BON_TVORG | Internal Sub-Transaction of YAP Bonus at Time of Creation | BON_TVORG | CHAR | 4 | TVORG_KK |
Key field | Non-key field |
How do I retrieve data from SAP structure ISU_BI_BILL_S_JVL_VER using ABAP code?
As ISU_BI_BILL_S_JVL_VER 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 ISU_BI_BILL_S_JVL_VER as there is no data to select.How to access SAP table ISU_BI_BILL_S_JVL_VER
Within an ECC or HANA version of SAP you can also view further information about ISU_BI_BILL_S_JVL_VER 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