SAP ABAP Data Element DDJAVAONLY (Write access only with JAVA)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷
SDTB (Package) ABAP/4 Dictionary: Tables
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD⤷
SDTB (Package) ABAP/4 Dictionary: Tables
Basic Data
| Data Element | DDJAVAONLY |
| Short Description | Write access only with JAVA |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DDBOOL | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 8 | JavaOnly |
| Medium | 8 | JavaOnly |
| Long | 20 | WriteWithJavaOnly |
| Heading | 17 | WriteWithJavaOnly |
Documentation
Definition
Using the indicator "Write access with Java only" you can define that contents of the table may only be changed from within Java.
If you have changes (INSERT, UPDATE) in table content through ABAP programs, there is basically no guarantee that this data can be read correctly from within Java. However, if the data written by ABAP is ASCII data, it can also be read from the Java side.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20041230 |
| SAP Release Created in | 700 |
