Adjusting data element

Hello Friends,
Can any one tell me how to adjust data elements in ' without modification assistant in spau tcode.
Thanks,
Vibha

Hi   ,
select the obect thne see the display ... it will show the   obect status   and go fot eh version when it was   changed    if you do want to modify the skip ... if you want modification then change ....so
for not changing   it is skip   ..
for chaning it is changing ..
Girish

Similar Messages

Creation of field without data element

Hi all,
i want to create a field SLNO without data element, i.e. by assigning direct data type NUMC.
by doing so while activating it is giving the below message.
"The table must be adjusted by unloading and reloading
it in the database. This function has a long runtime and should
not be performed while the table is being used for production."
"If you want to start the adjustment nevertheless,
select a processing type and choose 'Adjust'.
Otherwise choose 'Terminate'."
pls let me know which is better i.e. by assingning direct data type, or else can i create a data element with type as 'NUMC'.
Regards,
venkat

hi venkat,
when creating the db table in se 11 ,if u want to use predefined data type ie char,numc,date etc ... With in se14,in fields tab, click predefined type button which is placed in the first row along with cut ,delete icons.
When u click predefinedtype button, the field named data type will be enabled and its there ready for editing.Choose the data type u need and data length etc.
If u r creating the db for the first time, there is no need for , adjusting the db table using se14.
But if u r trying to edit a db ,that is already been created , then make neccessary changes in the db and go to se14. There give ur edited db name, and click "activate and adjust database " button...Ensure that "save data " option button is selected.
Note:
If u r making any structural changes in already existing db ,then use se14 to adjust ,save and activate the db.
Hope the content is usefull
please change the problem status if its resolved .Thank you.
thanks
rajeshwari
Edited by: Rajeshwari padmanaban on Jan 16, 2009 11:24 AM

How to change data element in table?

Hello all:
I just need to change data element for a field in some Z table. I know I can do it through SE11 but I just want to make sure if there is anything I should be aware of? Are there any other steps I should perform apart from making changes through SE11? Any information you could provide would be great.
Thanks.
Mithun

Hi Mithun,
Yes, you can change the table using SE11. After saving, check for errors and activate. Using Menu, Utilities
-> click on Database Utility and then click on 'activate and adjust database'.
Hope this helps.
Thanks,
Srinivasa
Message was edited by:
Srinivasa Bhanuprasad Moningi

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.

Changing field lable of KVGR1 data element.

Hi Guys,
I am changing field lable of KVGR1 data element. No. of depedent objects are also changed but some of the objects were end up with warning "Enahancement category for table missing". Since all this objects SAP Standard do I have to genarate key for every single one with warning to adjust the enhancement type.
Cheers
S Kumar

Hi Amit,
I have already changed the Field labels and Description of KVGR1 data element using SSCR key.
Is it a good idea to revert it back. The dependent tables and structures are activated with warnings. Which is Enhancement category.
Cheers
S Kumar

Data element status showing Modified / Active

Hi Gurus,
created one custom field using EEW in WEB UI, that filed length and type is NUMC,2, my requirement is need to change the length from 2 to 3.So i am not able to change the length from WEB UI ,doing changes manually from SE11. i have chaged the particular Data element length to 3 and activated Data element the Data element status showing Modified /Active instead of Active.
i have checked SE09 .showing inactive objects. please help me on this how to come out from this problem.how to activate Data element.
Thanks & Regards,
Sunil B

Hi Sanly yan,
i have done table Adjustment in se14.
Thanks & Regards,
Sunil B

Data element length modification

Hi friends,
We are working on a requirement that requires a change to an existing data element/field.
This field has been used in various tables/structures/programs and FM's. Essentially, Change to this field requires us to modify lot of programs.
I am just wondering if there are any alternative approaches. Need your help to evaluate.
1. The change required is to increase a length of the field to accommodate higher numbers.
2. Instead of modifying all programs, Are there any alternative approaches?
Thank you
Kris

Make sure to take the following precautions before doing any change
1. Apply the where use list of that table/ Field and check whether it has been used in some program and FM or not. If yes then check one more thing that check the TYPE of another variables on which system has populating data (move, write or in FM parameters). if you will not consider this then you can land you in big trouble. (Conversion dump)
2. Ask the basis to take a dump of the production, quality and data for the safer side if something does not go right.
Now, you can do the changes in your development system and then adjust the database and see the impact of it.
Hopefully, you will not come across any difficult situation in this changes.

Change in data element

dear all ,
I have changed my data element of a field in a table , previously that was N 5 length , now i have changed to P decimal 3 ..if i move this to qas server , this table already in qas with datas,, when i try to moving that to qas i cannot move the request to qas but i can see the changes in table i mean data element changed to P in qas , but when i try to see contents in se11 , i am getting TABLE IS NOT FOUND IN DATABASE , and i tried to adjust thro SE14 , ther was error log and i tried to unlock the table but it showing 'data will be lost ' . what should i do to rectify that .
Thanks

Hi peter,
what do you mean. Possible to upload stuff via excel? If so here is a link
http://wiki.scn.sap.com/wiki/display/ABAP/ABAP+code+snippet+to+upload+Excel+file+into+an+internal+table+and+display+it+in+alv+format
But I'm pretty sure you know that...I think I just do not got the question
~Florian

Data element was activated (error in the dependencies)

Hello Friends,
We had released some TR yesterday to move to Quality and this was not moved successfully and in the TR logs I found the following message. Not sure what to do...request if some has encountered similar situation to give their feedback.
We had similar problem 2 days ago with another TR failing for the same reasons for another Data element...both are mentioned below...
We have adjusted the table in SE14 also but still the same. In development box we do not have any issues everything is active.
We have also regenerated the table maintenance also.
Following objects not activated/deleted or activated/deleted w. warning:
Table YAR_CN_BS_ACT could not be activated
(E- Nametab for table YAR_CN_BS_ACT cannot be generated )
Data Element ZLINE was activated (error in the dependencies)
Data Element ZZSERIAL was activated (error in the dependencies)
Following objects not activated/deleted or activated/deleted w. warning:
Table YAR_CN_GAAP_AREA could not be activated
(E- Nametab for table YAR_CN_GAAP_AREA cannot be generated )
Data Element ZZDES was activated (error in the dependencies)

Ramesh,
When you transport a custom object, you need to make available other dependent custom objects for that object in the target system, means that when you transport a custom table you need to take all custom domains, data elements also in the TR if they are not already existing in the target system.....
Pls check that in your respective TRs, do you have data elements ZLINE, ZZSERIAL also....same for ZZDES...., Also include their domains if they are custom. Now, to remove this error, create a new TR and include all these custom data elements in it and transport to Quality. After that re-import your erroneous transports in Quality with help of basis.
BR,
Diwakar

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

Releation between fields and data element

Dear Abapers,
What is the relation between the fields and data element, while cretion of fields system will ask the data element, can we have one data element to more than one fields. Can you plese explain me.
Regards

Hi,
data elements are structures defined in SAP Dictionary.
Fields you meen in a table? or in programs? in both places you create in reference to SAP Dictionary.
data element char20. TEXT20
Programs data: l_text type char20.
Tables ... field ZTEXT type CHAR20...TEXT20

Adding data element to segment in we31 in ECC 6.0

hi all,
I have added field name ( data element ) to segment in we31 in 4.6 C by going Edit u2013> cancel release, then F6 to goto change mode to add our field.
Now I have to add the same field ( data element ) to segment While adding it is giving system error as " Error while resetting the release of segment ZE1XXXXXX_01"
Kindly let me know what to do ?
Thanks in advance

Problem solved with the help of my collegue.
It is just using "Segment --> Add version".
As the old version is already released so we can
"Edit --> Cancel release".
Thanks,

Adding new data elements to Org Modeler.

We are trying to add 4 fields to the org Modeler. However it is nowhere to be found like in the orgchart.
Org Modeler 3.0 SP2
PA0001, PA0008, HRP1005 and HRP1008. (also linking to the texts in T001P, so we will require a table inner join)

Hi Wade,
In order to get the fields in OrgModeler scenarios you need to make sure that your hierarchy data element in the Source OrgChart contains all fields that you want. For this I recommend creating a NakisaRFC function for the additional data, creating a data element for it and then creating a linked data element to link together the new data element and the existing hierarchy data element. There is no data center in OrgModeler so you will need to do this manually.
Best regards,
Luke

What is domain and dataelement.....diff b/w domain and data element

dear all
what is domain?
what is data element?
In one domain how many data elements are possible to used?
with out data element how can u create a table? explain briefly.

To clarify it little further the Data element and Domains are used in combination where similiar type of data fields are to be used with some more additional characteristics to each Data element.
For example consider creating a table which contains Employee details. The Columns Name1 and Name2 are to be of type char and length 40. There are 2 ways to do this,
1. You can assign the fields Name1 and Name2 directly to CHAR40(as the data element) in SE11. But this will make both the fields to have same characteristics with no difference among them.
2. The other way is to assign the columns Name1 and Name2 to seperate Data elements say DE_NAME1 and DE_NAME2. This method has tha advantage of adding further charectristics and labels to the data element. Hence in this case you can add a label "Name1" for the data element DE_NAME1 and "Name2" for data element DE_NAME2. And both these data element will point to the same domain CHAR40, hence length and type is same.
Hope this helps.
Thanks,
Prasath N

Doubt in data element creation

Hi,
I have doubt in data element creation ie, there is 2 options elementary type
(domain and built-in-type) and reference type (name of the reference type &
ref to predefined type). if there is built in type here then what is the use of
built-in-type in initial screen of the table and also explain me about the use of
reference type.
with regards,
nanjunda sharma

Hi!
With the use of the built-in type, you have to set always in every different data element the exact type.
With the use of the domains (pre-defined types) you just have to enter the domain name into the data element. If you have to modify the type, you can maintain it in the domain (only once) but the built in types have to modifyed in every data element (which means more work).
Domains have a little more options also, than the built in types.
Regards
Tamá

Adjusting data element

Similar Messages

Maybe you are looking for