Boolean data element in ABAP Dictionary

Dear friends,
Is it possible to have a Boolean variable defined in the domain without having the value range ???
Regards,
Vivek K

Hi Vivek,
If you are speaking of a boolean VARIABLE .. it has a default value range.
However, I do not know what is meant by boolean variable in a DOMAIN.
Anyway, as far as I can think of a default value range should be associated with it.
Regards,
Sameer

Similar Messages

Changing Field Label length for Data Element using ABAP code.

Hi Experts,
We have a scenario where we have to update the maximum length of the various Field Labels (Short, Medium, Long..) for a Data Element using ABAP code.
Does anyone know how to do this ? Is there a Function Module available for this purpose ?
Appreciate your valuable inputs.

Hi ,
Use the view
DD03M
Give
TABNAME as table name,
DDLANGUAGE = EN / sy-langu
and order by position. (for correct sequencing)
You will get description of the fields (short,medium, long etc). You will also get the length and other details.

Data Class in ABAP dictionary

hi,
recently we moved the tables from tablespace PSAPBTAD to user defined tablespace & since than we have poor performance in PROD - have any one had this issue before ? any idea on data class and tablespace ?
thanks

I doubt data class affects performance. It definitely affect upgrades and support packs so you'll want to confirm that every table you reorged is assigned the data class associated with its current tablespace, otherwise you can lose data.
It could be a lot of things affecting the performance. Maybe the reorg tool added too many small extents to the tables which is a problem only if you're not on SAN and if the tablespaces are DTMS. But I'd start with disk stats. Take a look and see if you've got hot spots, it's the first thing I'd check.
Oh, and how about database statistics, did you re-calc after the reorgs? It's essential.

Problem when define Value range for data element

Dear
When I define a new data element in ABAP Dictionary, for example, ZDATA_ELEMENT_TEST.
I use domain ZDOMAIN_TEST.
(Data type is DEC, the length is 10, and decimals is 2 with sign.)
Now, I want to restrict that, user can ONLY input the value from 10 to 100.
From ABAP course and the Internet, I switch to "Value Range" tab, and define 10 for Lower Limit, 100 for Upper Limit in Intervals section.
And write the simple program.
PARAMETERS test TYPE ZDATA_ELEMENT_TEST.
WRITE: test.
And run it.
Line: -
But, there is a problem.
When I input 200 for test, the program still run and display 200 to screen without any error report or notification. The ABAP runtime system doesn't check the input value.
I want to config for the domain that can satisfies, if the user input the wrong value (e.g: 200 in the previous case), the program will auto raise the error report, or exception, or sth like that.
Any help is welcome.

Hi Hanni,
Welcome to forum.
Try to attach key word VALUE CHECK to your PARAMETER statement.
I.e:
PARAMETERS test TYPE ZDATA_ELEMENT_TEST VALUE CHECK.
Note: The addition VALUE CHECK cannot be used together with the additions AS CHECKBOX, RADIOBUTTON, or NO-DISPLAY.
Regards,

Procedure for creating transparent table, data element and domain

Hi,
Can anybody let me know the procedure for creating transparent table, data element and domain.
Thanks,
Mahathi

Hi
Database table and its components
A database table is the central data structure of the ABAP/4 data dictionary.
The structure of the objects of application development are mapped in tables on the underlying relational database.
The attributes of these objects correspond to fields of the table.
A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization.
A field has a unique name and attributes; for example it can be a key field.
A table has one or more key fields, called the primary key.
The values of these key fields uniquely identify a table entry.
You must specify a reference table for fields containing a currency (data type CURR) or quantity (data type QUAN). It must contain a field (reference field) with the format for currency keys (data type CUKY) or the format for units (data type UNIT). The field is only assigned to the reference field at program runtime.
The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).
A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.
A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.
A field is not an independent object. It is table-dependent and can only be maintained within a table.
You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.
The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.
Two Level Domain Example
A domain defines a field technically and therefore it may
be used at different business levels.
A data element describes the meaning of a domain in a certain business context.
A domain, however, is used for the technical definition of a table field (for example field type and length).
Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.
Definitions of Table in Database
In SAP R/3 tables are defined as
A) Transparent tables: All of the fields of a dictionary table correspond to a field in the real database table.
B) Pooled tables: Different tables which are not linked to each other with a common key are combined into a TABLE POOL. Several logical tables thus exist as a single real database table.
C) Cluster tables: Several tables linked by a common key may sometimes be combined by the data dictionary and made to exist on the database schema as a single table.
SAP is evolving R/3 tables in transparent tables.
Elaboration on each of the definitions
A transparent table is automatically created on the database when it is activated in the ABAP Dictionary. At this time the database-independent description of the table in the ABAP Dictionary is translated into the language of the database system used.
The database table has the same name as the table in the ABAP Dictionary. The fields also have the same name in both the database and the ABAP Dictionary. The data types in the ABAP Dictionary are converted to the corresponding data types of the database system.
The order of the fields in the ABAP Dictionary can differ from the order of the fields on the database. This permits you to insert new fields without having to convert the table. When a new field is added, the adjustment is made by changing the database catalog (ALTER TABLE). The new field is added to the database table, whatever the position of the new field in the ABAP Dictionary.
Tables can also reside on the database as Pooled tables or cluster tables
Pooled Tables: Different tables which are not linked to each other with a common key can be combined into a Table Pool. The tables contained within this pool are called Pooled Tables. A table pool is stored in the database a simple table. The table's data sets contain, in separate fields, the actual key for the data set to be stored, the name of the pooled table and the contents of the data set to be stored.
Using this schema, several logical tables are combined into a single real database table. Although the data structure of each set is lost during the write to the table pool, it is restored during the read by the ABAP/4 Data Dictionary. The ABAP/4 Data Dictionary utilizes its meta-data to accomplish this.
Since information must be prepared (defined) within the ABAP/4 Data Dictionary when it is read or written to (or accessed), this process itself defines these as not transparent tables
Cluster Tables: Occasionally, several tables may be linked by a common key. The ABAP/4 Data Dictionary can also combine these tables into a single table. Each data set of the real table within the database contains a key and in a single data field, several data sets of the subsequent table for this key.
As mentioned above, these table types require special data handling, therefore they are not transparent tables.
Technical Settings in Dictionary
The data class logically defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.
The most important data classes are master data, transaction data, organizational data and system data.
Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.
Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.
Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.
System data is data that the R/3 System itself needs. The program sources are an example.
Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.
The size category describes the expected storage requirements for the table on the database.
An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.
You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.
Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.
Modifications to the entries of a table can be recorded and stored using logging.
To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.
Parameter 'rec/client' can have the following settings:
rec/client = ALL All clients should be logged.
rec/client = 000[...] Only the specified clients should be logged.
rec/client = OFF Logging is not enabled on this system.
The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).
Logging creates a 'bottleneck' in the system:
Additional write access for each modification to tables being logged.
This can result in lock situations although the users are accessing different application tables!
Create transparent table
Go to transaction SE11. Enter name of table you want to create (beginning with Y or Z) and click on create pushbutton
Enter the delivery class and the table maintenance criteria
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems .
The display/maintenance indicator specifies whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).
Enter the name of the table field and the data element. The
System automatically populates the technical details for
existing data elements.
So far as possible it is advisable to use existing data elements which befit the business requirements.
However, we may create data elements if need be. The same is shown in the next slide.
To create a data element simply double click on it.
Alternately create a data element by simply choosing the
data type radio button on SE11 initial screen.
Create data element
The system prompts you to create a new data element.
Choose the Yes pushbutton.
Under the data type tab enter the domain name which
determines the technical characteristics of the field.
Further characteristics tab: Allows you to specify a search help assigned to the data element.
It also allows you to specify a parameter id which helps you populate a field from SAP memory.
Field label: Can be assigned as prefixed text to a screen field referring to the ABAP Dictionary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
Create domain
If the domain does not exist in the data dictionary the
system prompts you to create one.
Give the technical characteristics under the definition
tab. Value range allows you value restriction at domain
level.
Value range tab:
As explained in the section Consistency through input checks one can restrict the possible values for a field at domain level itself by either entering fixed values or by specifying a value table under the tab Value range.
Currency/Quantity fields in a table
A currency or a quantity field must be assigned a reference field from a reference table containing applicable qty unit or currency unit.
Field of the reference table, containing the applicable quantity unit or currency
A field containing currency amounts (data type CURR) must be assigned a reference field including the currency key (data type CUKY).
A field containing quantity specifications (data type QUAN) must be assigned a reference field including the associated quantity unit (data type UNIT).
Create transparent table continue
Maintain the technical settings of the table by clicking on the tab

Diff B/w ABAP Dictionary and Data Dictionary

What is the difference between ABAP Dictionary and Data Dictionary........

Hi,
Both are the same.
Please check this online document perhaps it may help.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCDWBDIC/BCDWBDIC.pdf
Regards,
Ferry Lianto

ABAP Dictionary type FLTP is not allowed for screen element

Hi Experts
I tried to open VBFA in se16 and i got the message in the status bar like this , what does it mean. please explain.
"ABAP Dictionary type FLTP is not allowed for screen element"

Hi,
This is from help
ABAP Dictionary type FLTP is not allowed for screen element
Message no. 37048
Diagnosis
The format of the ABAP Dictionary field is only for use within the ABAP
program and cannot be used in the Screen Painter.
Procedure
The field cannot be used in screens. If you want to output the
information in the field or assign a value to the field from the screen,
you must use an intermediate field with an appropriate format.
Reward points
Regards

Data class and Delivery class in ABAP Dictionary

Hi all,
I want to know the exact information about Data class and Delivery class in ABAP Dictionary
Moderator message : Search for available information. Thread locked.
Edited by: Vinod Kumar on Aug 3, 2011 1:35 PM

As your name Suggests, there were exactly 21 rajapandian already who wanted exact information about Data class and Delivery class. Fortunately some has found the information by own and some were dumped by SAP Police.
Cheers
Amit

Difference between Data Dictionay and ABAP/4 dictionary

Hi all,
can any body please say me the difference between Data Dictionay and ABAP/4 dictionary
Ranjith

Check this PDF:
http://www.sappoint.com/faq/faqabdic.pdf#search=%22Data%20Dictionary%20and%20ABAP%2F4%20dictionary%22
Regards,
Prakash.

How to find which data elements are used in ABAP program ?

I wish to find out which data elements are used in some programs .
Is there any DD table which stores this information ?
I know we can go to program and look in fields, but do SAP stores this information somewhere ?

Dear Kaushal,
Please check the table TRDIR.
Regards,
Abir
Don't forget to award points *

ABAP Dictionary structure for use in ABAP Mapping

Hello, I'm creating an ABAP mapping class which requires me to use standard ABAP dictionary (table) structures (ex.MARA, KNA1 etc) for the mapping as the data coming into the mapping is in that format. I'm creating the ABAP class in the PI server and do not have table structures (MARA, KNA1 etc) in the dictionary in the PI server. What is the efficient way to create these structures (as Z elements) in the PI server's dictionary?
I have the XSD of these table structures. Can I import those XSDs into the ABAP dictionary in PI servers? If yes, how can it be done? Please help!

Yes you can import it as an external definition data and create the data type based on this XSD. Go through the link below for more information on the steps to import and how to use it.
http://help.sap.com/saphelp_nwpi71/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/frameset.htm

What are the basic objects in abap dictionary ?

Try to provide the details if anyone knows about it.

The DDIC is nothing but the ABAP Dictionary. The ABAP Dictionary centrally describes and manages all the data definitions used in the system.
Data types
Data types are the actual type definitions in the ABAP Dictionary. They allow you to define elementary types, reference types, and complex types that are visible globally in the system. The data types of database tables are a subset of all possible types, namely flat structures.
Data Elements
Data elements in the ABAP Dictionary describe individual fields. They are the smallest indivisible units of the complex types described below, and are used to specify the types of columns in the database. Data elements can be elementary types or reference types.
Structures
A structure is a sequence of any other data types from the ABAP Dictionary, that is, data elements, structures, table types, or database tables. When you create a structure in the ABAP Dictionary, each component must have a name and a data type. In an ABAP program, you can use the TYPE addition to refer directly to a structure.
If you define a local data type in a program by referring to a structure as follows:
TYPES <t> TYPE <structure>.
Table Types
Table types are construction blueprints for internal tables that are stored in the ABAP Dictionary.
When you create a table type in the ABAP Dictionary, you specify the line type, access type, and key. The line type can be any data type from the ABAP Dictionary, that is, a data element, a structure, a table type, or the type of a database table. You can also enter a predefined Dictionary type directly as the line type, in the same way that you can with a domain.
Type Groups
Before Release 4.5A, it was not possible to define standalone types in the ABAP Dictionary to which you could refer using a TYPE addition in an ABAP program. It was only possible to refer SAP AG BC - ABAP Programming
Data Types in the ABAP Dictionary to flat structures. Structures in programs corresponded to the structures of database tables or structures in the ABAP Dictionary. In ABAP programs, you could only refer to database tables and structures in the ABAP Dictionary using LIKE. It was, however, possible to refer to individual components of the Dictionary type. Complex local data types such as internal tables or deep structures had no equivalent in the ABAP Dictionary. The solution to this from Release 3.0 onwards was to use type groups. Type groups were based on the include technique, and allowed you to store any type definitions globally in the Dictionary by defining them using TYPES statements.
Views:
There are 4 types views are avilable in SAP.
Database View - To club more than one table
Projection View - To hide fields in one table
Maintanance View - To maintain database records in table
Help View - To provide help for a fields (Same functionality as Search help. This is outdated)
View are improves perfromance in the following aspects
1. If you want to use more than two table in 'JOIN' condition better to use Views . It will improves performance of a program
2. If you want to use mutiple FOR ALL ENTRIES clause, better to club all SELECT statement in a view.
Lock Objects:
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
You have to use these function module in your program.
Search Helps:
These are two types.
Elementary n Collective.
1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
2) Collective search helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.
3)An elementary search help defines the standard flow of an input help.
4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.
5)A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.
6)Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in a collective search help, they are expanded to the level of the elementary search helps when the input help is called.
See the below link to understand this completely:
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
Rewards if useful

Strange behaviour of data element object

Dear Gurus,
I have incremented the field length of a z table's field from 5 (type DEC) to 8 by increasing the corresponding domain length . But the internal tables that refer to this field still refer to the old value 5, though the table is accepting values for this field with 8 length through 'Create Entries' in SE11.
The problem seems to be in the runtime object of the corresponding data element which shows
database length = 5
abap length = 5
BUT dictionary length = 8.
Could anyone pls help diagnose this strange behaviour as even if I create new domains with new data elements for this table field ,it gives the SAME RUNTIME OBJECT STATUS as mentioned above.
Rewards are awaiting the right answer.
Thanks in advance.
Shweta.

Hi,
For these kind of problems, you can use the Database utility tool (SE14), give the table name press enter, click Adjust and Activate Database table also select save data radiobutton. After this Re-Run the Program, it works fine, also cross-check in the Debugging screen.
Cheers...
Santosh.
Mark Usefull Answers.

Where is stocked the description of different object in ABAP Dictionary ?

Hi,
Please, Can any one tell me where is stocked the description of different object in ABAP Dictionary like: Domain (Description, value range u2026), View, Data Type...?
Best regards
Mustapha

Hi,
Check these tables:
DD01T                          R/3 DD: domain texts
DD02T                          R/3 DD: SAP table texts
DD03T                          DD: Texts for fields (language dependent)
DD04T                          R/3 DD: Data element texts
DD06T                          R/3 DD: texts on SQL tables
DD07T                          DD: Texts for Domain Fixed Values (Languag
DD08T                          Texts on the relationship definitions
DD12T                          Text Table for DD12L (Short Descriptions o
DD15T                          R/3 DD: texts on SAP objects
DD20T                          AS400-T_MCOBJECT: MC Object Texts
DD23T                          AS400_L-MCID: Matchcode ID Texts
DD25T                          Short Texts for Views and Lock Objects
DD29T                          AS400_L-SELCOND: Selection Condition Texts
DD30T                          Search help texts
DD40T                          Text on table types
DD90T                          R/3-DD: Text for External Index
Regards,
Joy.

Type of X equals which data elements or data type

Hi ABAP Experts,
I declareted variable type of X in my program.
(Example TYPES: BEGIN OF T_XML_LINE,
         DATA(1024) TYPE X,
       END OF T_XML_LINE.)
But I want to create structure with SE11 Tcode in my program. But I dont know Type of X equals which data elements or data type and length.
Thanks for help.

Hi,
You can use the below data type in data dictionary
RAW:   Uninterpreted byte string, maximum length of 255 in tables
LRAW: Uninterpreted byte string of any length, but has to be declared with a minimum length of 256
RAWSTRING: Uninterpreted byte string of variable length
Regards
Praveen

Boolean data element in ABAP Dictionary

Similar Messages

Maybe you are looking for