MCJVBEB SAP (Reference Structure for MCJVBE for LIS Function Modules) Structure details
Description: Reference Structure for MCJVBE for LIS Function Modules
Structure field list including key, data, relationships and ABAP select examples
MCJVBEB 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 "Reference Structure for MCJVBE for LIS Function Modules" 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_MCJVBEB TYPE MCJVBEB.
The MCJVBEB table consists of various fields, each holding specific information or linking keys about Reference Structure for MCJVBE for LIS Function Modules data available in SAP. These include SUPKZ (Statistics update indicator (post in/post out)), MANDT (Client), VBELN (IS-M/SD: Billing Document), POSNR (IS-M: Billing Item).. 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 MCJVBEB 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 |
SUPKZ | Statistics update indicator (post in/post out) | SUPKZ | CHAR | 1 | SUPKZ | ||||
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
VBELN | IS-M/SD: Billing Document | ISPVBELN | CHAR | 10 | Assigned to domain | ALPHA | ISPVBELN | VF | MJF0 |
POSNR | IS-M: Billing Item | ISPPOSNR | NUMC | 6 | Assigned to domain | ISPPOSNR | |||
VAUSGB | Issue | VAUSGB | CHAR | 10 | Assigned to domain | ALPHA | VAUSGB | JD8 | MJD4 |
DRERZTAT | Actual Publication Delivered | DRERZTAT | CHAR | 8 | Assigned to domain | ALPHA | DRERZ | JDC | MJD1 |
PVATAT | Actual edition delivered | PVATAT | CHAR | 8 | Assigned to domain | ALPHA | PVA | JDD | MJD2 |
ERSCHDAT | Publication Date | ERSCHDAT | DATS | 8 | DATUM | JD9 | |||
JAHRGANG | Year number of issue | JAHRGANG | NUMC | 4 | JAHRGANG | ||||
NRIMJAHR | Issue number (in year) | NRIMJAHR | CHAR | 4 | ALPHA | JNRIMJAHR | |||
HEFTNUMMER | Copy Number of Issue | HEFTNUM_VA | CHAR | 9 | HEFTNUMMER | ||||
NETWR_E | Net Value of (Simulated) Billing Schedule Line | JMC_NETWRE | CURR | 15(2) | WERTV8 | ||||
BRTWR_E | Gross Value of (Simulated) Billing Schedule Line | JMC_BRTWRE | CURR | 15(2) | WERTV8 | ||||
SKFBP_E | Amount for (Simulated) Bill.Sched.Line Qualifying for Disct | JMC_SKFBPE | CURR | 13(2) | WERTV7 | ||||
WAVWR_E | Cost of (simulated) billing schedule line | JMC_WAVWRE | CURR | 13(2) | WERTV7 | ||||
KZWI1_E | Subtotal 1 from pricing procedure for condition | KZWI1 | CURR | 13(2) | WERTV7 | ||||
KZWI2_E | Subtotal 2 from pricing procedure for condition | KZWI2 | CURR | 13(2) | WERTV7 | ||||
KZWI3_E | Subtotal 3 from pricing procedure for condition | KZWI3 | CURR | 13(2) | WERTV7 | ||||
KZWI4_E | Subtotal 4 from pricing procedure for condition | KZWI4 | CURR | 13(2) | WERTV7 | ||||
KZWI5_E | Subtotal 5 from pricing procedure for condition | KZWI5 | CURR | 13(2) | WERTV7 | ||||
KZWI6_E | Subtotal 6 from pricing procedure for condition | KZWI6 | CURR | 13(2) | WERTV7 | ||||
DUMMYUSR | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY |
Key field | Non-key field |
How do I retrieve data from SAP structure MCJVBEB using ABAP code?
As MCJVBEB 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 MCJVBEB as there is no data to select.How to access SAP table MCJVBEB
Within an ECC or HANA version of SAP you can also view further information about MCJVBEB 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