LOBM_BATCH_CHANGE_REQUEST_SYNC SAP (BatchChangeRequest_sync) Structure details
Description: BatchChangeRequest_sync
Related tables to LOBM_BATCH_CHANGE_REQUEST_SYNC
Access table LOBM_BATCH_CHANGE_REQUEST_SYNC
Structure field list including key, data, relationships and ABAP select examples
LOBM_BATCH_CHANGE_REQUEST_SYNC 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 "BatchChangeRequest_sync" 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_LOBM_BATCH_CHANGE_REQUEST_SYNC TYPE LOBM_BATCH_CHANGE_REQUEST_SYNC.
The LOBM_BATCH_CHANGE_REQUEST_SYNC table consists of various fields, each holding specific information or linking keys about BatchChangeRequest_sync data available in SAP. These include BATCH_CHANGE_REQUEST_SYNC (), CONTROLLER (), MESSAGE_HEADER (), CONTROLLER ().. 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 LOBM_BATCH_CHANGE_REQUEST_SYNC 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 |
| CONTROLLER | 0 | ||||||||
| BATCH_CHANGE_REQUEST_SYNC | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| MESSAGE_HEADER | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| BASIC_BUSINESS_DOCUMENT_MESSA | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| ID | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| SCHEME_ID | 0 | ||||||||
| SCHEME_AGENCY_ID | 0 | ||||||||
| SCHEME_AGENCY_SCHEME_AGENCY_ID | An AgencyIdentificationCode is a code representation of the | SAPPLSEF_AGENCY_IDENTIFICATION | CHAR | 3 | |||||
| VALUE | Unique identifier of a business document in a (technical) me | SAPPLSEF_BUS_DOC_MSGID_CONTENT | CHAR | 35 | |||||
| UUID | Universally Unique Identifier (without attributes) | SAPPLSEF_ATTRIBUTEIND_UUID | CHAR | 36 | |||||
| REFERENCE_ID | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| SCHEME_ID | 0 | ||||||||
| SCHEME_AGENCY_ID | 0 | ||||||||
| SCHEME_AGENCY_SCHEME_AGENCY_ID | An AgencyIdentificationCode is a code representation of the | SAPPLSEF_AGENCY_IDENTIFICATION | CHAR | 3 | |||||
| VALUE | Unique identifier of a business document in a (technical) me | SAPPLSEF_BUS_DOC_MSGID_CONTENT | CHAR | 35 | |||||
| REFERENCE_UUID | Universally Unique Identifier (without attributes) | SAPPLSEF_ATTRIBUTEIND_UUID | CHAR | 36 | |||||
| BATCH | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| ID | Unique identifier for a batch in the context of a material n | SAPPLSEF_BATCH_ID | CHAR | 10 | |||||
| MATERIAL_INTERNAL_ID | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| SCHEME_ID | 0 | ||||||||
| SCHEME_AGENCY_ID | 0 | ||||||||
| VALUE | Proxy Data Element (Generated) | SAPPLSEF_PRODUCT_INTERNAL_ID_C | CHAR | 60 | |||||
| PRODUCTION_DATE | Proxy Data Element (Generated) | SAPPLSEF_DATE | DATS | 8 | |||||
| AVAILABILITY_DATE | Proxy Data Element (Generated) | SAPPLSEF_DATE | DATS | 8 | |||||
| LAST_GOODS_RECEIPT_DATE | Proxy Data Element (Generated) | SAPPLSEF_DATE | DATS | 8 | |||||
| NEXT_QUALITY_INSPECTION_DATE | Proxy Data Element (Generated) | SAPPLSEF_DATE | DATS | 8 | |||||
| EXPIRATION_DATE | Proxy Data Element (Generated) | SAPPLSEF_DATE | DATS | 8 | |||||
| ORIGIN_COUNTRY_CODE | Proxy Data Element (Generated) | SAPPLSEF_COUNTRY_CODE | CHAR | 3 | |||||
| ORIGIN_REGION_CODE | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| LIST_ID | 0 | ||||||||
| LIST_VERSION_ID | 0 | ||||||||
| LIST_AGENCY_ID | 0 | ||||||||
| LIST_AGENCY_SCHEME_ID | 0 | ||||||||
| LIST_AGENCY_SCHEME_AGENCY_ID | An AgencyIdentificationCode is a code representation of the | SAPPLSEF_AGENCY_IDENTIFICATION | CHAR | 3 | |||||
| VALUE | Proxy Data Element (Generated) | SAPPLSEF_REGION_CODE_CONTENT | CHAR | 6 | |||||
| RESTRICTED_USE_INDICATOR | Indicator is the representation of a situation that has exac | SAPPLSEF_INDICATOR | CHAR | 5 | |||||
| AUTOMATIC_CLASSIFICATION_INDI | Indicator is the representation of a situation that has exac | SAPPLSEF_INDICATOR | CHAR | 5 | |||||
| PROPERTY_VALUATION | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure LOBM_BATCH_CHANGE_REQUEST_SYNC using ABAP code?
As LOBM_BATCH_CHANGE_REQUEST_SYNC 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 LOBM_BATCH_CHANGE_REQUEST_SYNC as there is no data to select.How to access SAP table LOBM_BATCH_CHANGE_REQUEST_SYNC
Within an ECC or HANA version of SAP you can also view further information about LOBM_BATCH_CHANGE_REQUEST_SYNC 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