P06_S_MV_CR_LIVRADOM_1001 SAP (Meal Tickets - Meal Voucher: LIVRADOM 1001 Structure) Structure details
Description: Meal Tickets - Meal Voucher: LIVRADOM 1001 Structure
Related tables to P06_S_MV_CR_LIVRADOM_1001
Access table P06_S_MV_CR_LIVRADOM_1001
Structure field list including key, data, relationships and ABAP select examples
P06_S_MV_CR_LIVRADOM_1001 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 "Meal Tickets - Meal Voucher: LIVRADOM 1001 Structure" 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_P06_S_MV_CR_LIVRADOM_1001 TYPE P06_S_MV_CR_LIVRADOM_1001.
The P06_S_MV_CR_LIVRADOM_1001 table consists of various fields, each holding specific information or linking keys about Meal Tickets - Meal Voucher: LIVRADOM 1001 Structure data available in SAP. These include CUFCD (Meal Tickets - Meal Voucher: Client number to invoice (Sdx)), PONUM (Meal Tickets - Meal Voucher: PO number), DISCD (Meal Tickets - Meal Voucher: Delivery code), CRNUM (Meal Tickets - Meal Voucher: No. of vouchers for employee).. 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 P06_S_MV_CR_LIVRADOM_1001 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 |
| CUSCD | Meal Tickets - Meal Voucher: Primary client number (Sodexo) | P06_MV_CR_CUSTOMER_CODE | NUMC | 8 | NUM8 | ||||
| CUFCD | Meal Tickets - Meal Voucher: Client number to invoice (Sdx) | P06_MV_CR_CUST_FACTU_CODE | NUMC | 8 | NUM8 | ||||
| PONUM | Meal Tickets - Meal Voucher: PO number | P06_MV_CR_PO_NUMBER | CHAR | 16 | CHAR16 | ||||
| DISCD | Meal Tickets - Meal Voucher: Delivery code | P06_MV_CR_DISTRIBUTION_CD | CHAR | 16 | CHAR16 | ||||
| CRNUM | Meal Tickets - Meal Voucher: No. of vouchers for employee | P06_MV_CR_NUMBER_OF_CRS | NUMC | 2 | NUM2 | ||||
| FACIV | Meal Tickets - Meal Voucher: Face value | P06_MV_CR_FACIAL_VALUE | NUMC | 5 | NUM5 | ||||
| EENUM | Meal Tickets - Meal Voucher: Employee's personnel number | P06_MV_CR_EMPLOYEE_NUMBER | CHAR | 11 | CHAR11 | ||||
| EEPAT | Meal Tickets - Meal Voucher: Employee's family name | P06_MV_CR_EE_PATRONYME | CHAR | 30 | CHAR30 | ||||
| PERZN | Meal Tickets - Meal Voucher: Custom field | P06_MV_CR_PERSONALIZ_ZONE | NUMC | 5 | NUM5 | ||||
| PARTV | Meal Tickets - Meal Voucher: Employer's contribution | P06_MV_CR_ER_PARTICIPATION | NUMC | 5 | NUM5 | ||||
| EENAM | Meal Tickets - Meal Voucher: Employee's Last and First Names | P06_MV_CR_EMPLOYEE_NAME | CHAR | 36 | CHAR36 | ||||
| ADDR1 | Meal Tickets - Meal Voucher: Address 1 | P06_MV_CR_ADDR1 | CHAR | 36 | CHAR36 | ||||
| ADDR2 | Meal Tickets - Meal Voucher: Address 2 | P06_MV_CR_ADDR2 | CHAR | 36 | CHAR36 | ||||
| ADDCP | Meal Tickets - Meal Voucher: Address postal code | P06_MV_CR_ADDR_CP | NUMC | 5 | NUM5 | ||||
| ADDCT | Meal Tickets - Meal Voucher: Address - Town/City | P06_MV_CR_ADDR_CITY | CHAR | 36 | CHAR36 |
| Key field | Non-key field |
How do I retrieve data from SAP structure P06_S_MV_CR_LIVRADOM_1001 using ABAP code?
As P06_S_MV_CR_LIVRADOM_1001 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 P06_S_MV_CR_LIVRADOM_1001 as there is no data to select.How to access SAP table P06_S_MV_CR_LIVRADOM_1001
Within an ECC or HANA version of SAP you can also view further information about P06_S_MV_CR_LIVRADOM_1001 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