ISU_BI_COLL_BILL_S_CDOC_LOCKS SAP (Lock on Contract Account: Collective Bill) Structure details
Description: Lock on Contract Account: Collective Bill
Related tables to ISU_BI_COLL_BILL_S_CDOC_LOCKS
Access table ISU_BI_COLL_BILL_S_CDOC_LOCKS
Structure field list including key, data, relationships and ABAP select examples
ISU_BI_COLL_BILL_S_CDOC_LOCKS 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 "Lock on Contract Account: Collective Bill" 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_COLL_BILL_S_CDOC_LOCKS TYPE ISU_BI_COLL_BILL_S_CDOC_LOCKS.
The ISU_BI_COLL_BILL_S_CDOC_LOCKS table consists of various fields, each holding specific information or linking keys about Lock on Contract Account: Collective Bill data available in SAP. These include CLIENT (Client), LOOBJ1 (Lock object), LOTYP (Lock Object Category), PROID (Process Code (Example: Dunning, Payment)).. 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_COLL_BILL_S_CDOC_LOCKS 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_CDOC_LOCKS | 0 | ||||||||
CLIENT | Client | MANDT | CLNT | 3 | MANDT | ||||
LOOBJ1 | Lock object | LOOBJ_KK | CHAR | 32 | CHAR32 | ||||
LOTYP | Lock Object Category | LOTYP_KK | CHAR | 2 | LOTYP_KK | ||||
PROID | Process Code (Example: Dunning, Payment) | PROID_KK | CHAR | 2 | PROID_KK | ||||
LOCKR | Lock Reason | LOCKR_KK | CHAR | 1 | LOCKR_KK | ||||
FDATE | Lock valid from | FDATE_KK | DATS | 8 | DATUM | ||||
TDATE | Lock valid to | TDATE_KK | DATS | 8 | DATUM | ||||
GPART | Business Partner Number | GPART_KK | CHAR | 10 | ALPHA | BU_PARTNER | BPA | ||
VKONT | Contract Account Number | VKONT_KK | CHAR | 12 | ALPHA | VKONT_KK | KTO | FKKVKP_F4 | |
COND_LOOBJ | Lock object | LOOBJ_KK | CHAR | 32 | CHAR32 | ||||
ACTKEY | Activity key for conditional business locks | ACTKEY_KK | CHAR | 2 | ACTKEY_KK | ||||
UNAME | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
ADATUM | Date of Last Change | UDATUM | DATS | 8 | SYDATS | ||||
AZEIT | Time | UZEIT | TIMS | 6 | UZEIT | ||||
PROTECTED | Processing lock write-protected | PROTECTED_KK | CHAR | 1 | PROTECTED_KK | ||||
LAUFD | Date ID | LAUFD_KK | DATS | 8 | DATUM | ||||
LAUFI | Additional Identification Characteristic | LAUFI_KK | CHAR | 6 | LAUFI_KK |
Key field | Non-key field |
How do I retrieve data from SAP structure ISU_BI_COLL_BILL_S_CDOC_LOCKS using ABAP code?
As ISU_BI_COLL_BILL_S_CDOC_LOCKS 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_COLL_BILL_S_CDOC_LOCKS as there is no data to select.How to access SAP table ISU_BI_COLL_BILL_S_CDOC_LOCKS
Within an ECC or HANA version of SAP you can also view further information about ISU_BI_COLL_BILL_S_CDOC_LOCKS 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