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.

Similar Messages

Increase maktx data element Length in makt table

Dear Expert,
Please guide me or provide me a solution.....
There is a requirement in my company from MM consultant, he wants me to increase the length of maktx field from 40 to 100.
Please tell me is it possible? if possible then what is the solution and impact?
Please i am waiting for a reply........
Regards
Shelly Malik

Hi
@Matt
You can see similar type of requirement posted today : [Change The length of field MAKTX |Change The length of field MAKTX;.
Regards
Vinod
Edited by: Vinod Kumar on Jun 25, 2010 11:21 AM

Data Element Length - Restriction / Best Practice

Many databases in the market currently allows table/column names to be 128 characters long. Our developers are suggesting that 30-35 characters is the limit one should strive for.
One thought is that Business Objects cannot handle queries bigger than 64K u2013 is this true? If a query has several filters or results fields that are very long will that be a problem?
Also, is there some potential usage issue / best practice by which using a shorter name would be advantageous in Business Objects?
Our tool stack is SQL Server 2005 / Informatica 8.1.1 / Business Objects XI R2

Hi Jennifer,
I am not sure if the 64K limit is true. However, given that this is the query string that BO is passing to your SQL Server, it would be a limit
The following query is 2k, so you can imagine that a 64k one would be difficult to read
SELECT
     A_Long_Table_Name.TestField1,
     A_Long_Table_Name.TestField12,
     A_Long_Table_Name.TestField22,
     A_Long_Table_Name.TestField32,
     A_Long_Table_Name.TestField42,
     A_Long_Table_Name.TestField52,
     A_Long_Table_Name.TestField62,
     A_Long_Table_Name.TestField72,
     Another_Long_Table_Name.TestField1,
     Another_Long_Table_Name.TestField12,
     Another_Long_Table_Name.TestField13,
     Another_Long_Table_Name.TestField14,
     Another_Long_Table_Name.TestField15,
     Another_Long_Table_Name.TestField16,
     Another_Long_Table_Name.TestField17
FROM
     A_Long_Table_Name,
     Another_Long_Table_Name
WHERE
     A_Long_Table_Name.TestField1 =      Another_Long_Table_Name.TestField1
UNION ALL
SELECT
     A_Long_Table_Name2.TestField1,
     A_Long_Table_Name2.TestField12,
     A_Long_Table_Name2.TestField22,
     A_Long_Table_Name2.TestField32,
     A_Long_Table_Name2.TestField42,
     A_Long_Table_Name2.TestField52,
     A_Long_Table_Name2.TestField62,
     A_Long_Table_Name2.TestField72,
     Another_Long_Table_Name.TestField1,
     Another_Long_Table_Name.TestField12,
     Another_Long_Table_Name.TestField13,
     Another_Long_Table_Name.TestField14,
     Another_Long_Table_Name.TestField15,
     Another_Long_Table_Name.TestField16,
     Another_Long_Table_Name.TestField17
FROM
     A_Long_Table_Name2,
     Another_Long_Table_Name
WHERE
     A_Long_Table_Name2.TestField1 =      Another_Long_Table_Name.TestField1
On the object names, I do not believe you will recieve any noticable difference in performance. It is better to keep the names of columns and tables legible, and your DBAs suggestion of 30-35 is about right.
Regards
Alan

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

Why CHAR DATA ELMNT LENGTH allowed is different in SAP and BI?

Hi All
Why the Character Data Element Length of Text is different in SAP R3 and BI though the product belong to SAP??
Any ideas to solve this issue to get long text or any workaround in Query??
how do I find the table to fetch using FM READ_TEXT?

Hi,
Work Around for more than 60 char length:
Check Blogs:
/people/marc.bernard/blog/2009/08/07/the-60-character-restriction-for-bw-data-models
Reason for 60Char restiction-Exact reason not known.
- Performance is probably an issue.
- You don't really need longer InfoObjects, they just thought it is enough.
- Longer texts would have been fine but still not necessary.
Hope it helps.
Thanks and Regards,
MuraliManohar.

Internal length ( dd03l-intlen ) of data element

Hi Experts,
I have created structure using data elements.
intlen updated in table dd03l is double than Whatever length I defined for data elements.
e.g.
I defined custom data element ZDEPOT of domain type WERKS of type char 4.
but it's length in table DD03L-INTLEN is 8 char.
Please let me know what is the connection of data element and DD03L-INTLEN
and how we can control it as per the length of domain.
Thanks,
Yogesh.

Hmm, everything I can find in table DD03L with the domain WERKS shows up with INTLEN of 4 and INTTYPE of C. Our custom data elements and structures appear to all have INTLEN values that match our LENG values. Have you saved and activated your custom data element and your structure?
- April King

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 Element Sales Org in CRM and ECC differ in length...

Hi Experts,
The standard data element for Sales Org in ECC and CRM differ in Length.
Similarly the Purchasing Org.
I need to export the Sales Org from CRM to ECC. But there is an error due to the length mismatch.
Why is there this difference? How can my requirement be met ?
Any ideas/pointers would be of great help.
Points Assured.
Thanks in Advance.
Arun.

use offset like vbeln+0(5).

Data element-reward point guranteed

Hi all,
         i am in a peculiar problem.I have to go through a hell lots (50+) of ztable and find the domian used and corresponding data element.
going thorugh SE11 and finding the things are going to take lots of time.
i have a report program , sending it to you, it displays details of info of listed table.
just run the report.
but the thing is , it rerieves the data type, instead of data element and domain.
somehow if i get those two things(domian & data element instead of data type of each field) , my work will be easier.
i will simply run this report and download the content of the priniting internal table int an excel ****.
can you just do some modification in this report to print DATA ELEMENT AND DOMAINS OF RESPECTIVE.
here it is ,
REPORT ZANID_TEST message-id zz NO STANDARD PAGE HEADING
       LINE-SIZE 178 LINE-COUNT 65.
TABLES: DD03L, DD04T, DD02T, DD02L.
SELECT-OPTIONS: TABNAME FOR DD02L-TABNAME.
*SELTEXT E 'SAP Table Name(s)'
DATA: BEGIN OF TAB OCCURS 500,
     TABNAME LIKE DD03L-TABNAME,
     POSITION LIKE DD03L-POSITION,
     FIELDNAME LIKE DD03L-FIELDNAME,
     STXT LIKE DD04T-DDTEXT,
     KEYFLAG LIKE DD03L-KEYFLAG,
     DATATYPE LIKE DD03L-DATATYPE,
     LENG     LIKE DD03L-LENG,
     DECIMALS LIKE DD03L-DECIMALS,
     CHECKTABLE LIKE DD03L-CHECKTABLE,
     REFTABLE LIKE DD03L-REFTABLE,
     REFFIELD LIKE DD03L-REFFIELD,
     END OF TAB.
DATA: LINE-COUNT TYPE I.
SELECT * FROM DD03L WHERE TABNAME IN TABNAME.
MOVE-CORRESPONDING DD03L TO TAB.
IF TAB-FIELDNAME CS '.inc'.
ELSE.
    SELECT * FROM DD04T WHERE ROLLNAME   = DD03L-ROLLNAME
                          AND DDLANGUAGE = SYST-LANGU
                          AND AS4LOCAL   = 'A'.
    ENDSELECT.
    IF SYST-SUBRC = 0.
      TAB-STXT = DD04T-DDTEXT.
    ENDIF.
    APPEND TAB.
ENDIF.
ENDSELECT.
DESCRIBE TABLE TAB LINES LINE-COUNT.
IF LINE-COUNT EQ 0.
MESSAGE E009 WITH 'Table Not Found'.
ENDIF.
SORT TAB BY TABNAME POSITION.
LOOP AT TAB.
ON CHANGE OF TAB-TABNAME.
    NEW-PAGE.                          "Page Break for New Table
ENDON.
WRITE: / TAB-FIELDNAME, 20 TAB-STXT,
           81 TAB-KEYFLAG, 85 TAB-DATATYPE,
           90 TAB-LENG, 100 TAB-DECIMALS,
           110 TAB-CHECKTABLE,
           121 TAB-REFTABLE,
           132 TAB-REFFIELD.
ENDLOOP.
TOP-OF-PAGE.
FORMAT INTENSIFIED OFF.
WRITE: / SY-REPID,
           'Run by', SY-UNAME(8), 'on', SY-DATUM, SY-UZEIT,
           'System', SY-SYSID(4), 'Client', SY-MANDT.
WRITE: / SY-TITLE CENTERED.
FORMAT INTENSIFIED ON.
*include zconinc3.
FORMAT INTENSIFIED OFF.
CLEAR DD02T.
SELECT * FROM DD02T WHERE TABNAME EQ TAB-TABNAME
                      AND DDLANGUAGE EQ SYST-LANGU
                      AND AS4LOCAL   EQ 'A'.
ENDSELECT.
CLEAR DD02L.
SELECT * FROM DD02L WHERE TABNAME EQ TAB-TABNAME
                      AND AS4LOCAL   EQ 'A'.
ENDSELECT.
WRITE: / 'Table Name   ', TAB-TABNAME,
         'Type=', DD02L-TABCLASS,
          DD02T-DDTEXT.
WRITE: / 'Field',       20 'Description',
         81 'Key',        75 'Type',
         90 'Length', 100 'Decimals',
         110 'Check Table',
         121 'REF Table',
         132 'REF Field'.
FORMAT INTENSIFIED ON.

Here you go:
REPORT ZANID_TEST message-id zz NO STANDARD PAGE HEADING
LINE-SIZE 255 LINE-COUNT 65.
TABLES: DD03L, DD04T, DD02T, DD02L.
SELECT-OPTIONS: TABNAME FOR DD02L-TABNAME.
*SELTEXT E 'SAP Table Name(s)'
DATA: BEGIN OF TAB OCCURS 500,
TABNAME LIKE DD03L-TABNAME,
POSITION LIKE DD03L-POSITION,
FIELDNAME LIKE DD03L-FIELDNAME,
STXT LIKE DD04T-DDTEXT,
KEYFLAG LIKE DD03L-KEYFLAG,
DATATYPE LIKE DD03L-DATATYPE,
LENG LIKE DD03L-LENG,
DECIMALS LIKE DD03L-DECIMALS,
CHECKTABLE LIKE DD03L-CHECKTABLE,
REFTABLE LIKE DD03L-REFTABLE,
REFFIELD LIKE DD03L-REFFIELD,
rollname like dd03l-rollname,
domname like dd04l-domname,
END OF TAB.
DATA: LINE-COUNT TYPE I.
SELECT * FROM DD03L WHERE TABNAME IN TABNAME.
MOVE-CORRESPONDING DD03L TO TAB.
select single domname from dd04l into tab-domname
    where rollname = dd03l-rollname.
IF TAB-FIELDNAME CS '.inc'.
ELSE.
    SELECT * FROM DD04T WHERE ROLLNAME = DD03L-ROLLNAME
    AND DDLANGUAGE = SYST-LANGU
    AND AS4LOCAL = 'A'.
    ENDSELECT.
    IF SYST-SUBRC = 0.
      TAB-STXT = DD04T-DDTEXT.
    ENDIF.
    APPEND TAB.
ENDIF.
ENDSELECT.
DESCRIBE TABLE TAB LINES LINE-COUNT.
IF LINE-COUNT EQ 0.
MESSAGE E009 WITH 'Table Not Found'.
ENDIF.
SORT TAB BY TABNAME POSITION.
LOOP AT TAB.
ON CHANGE OF TAB-TABNAME.
    NEW-PAGE. "Page Break for New Table
ENDON.
WRITE: / TAB-FIELDNAME, 20 TAB-STXT,
81 TAB-KEYFLAG, 85 TAB-DATATYPE,
90 TAB-LENG, 100 TAB-DECIMALS,
110 TAB-CHECKTABLE,
tab-rollname,
tab-domname.
ENDLOOP.
TOP-OF-PAGE.
FORMAT INTENSIFIED OFF.
WRITE: / SY-REPID,
'Run by', SY-UNAME(8), 'on', SY-DATUM, SY-UZEIT,
'System', SY-SYSID(4), 'Client', SY-MANDT.
WRITE: / SY-TITLE CENTERED.
FORMAT INTENSIFIED ON.
*include zconinc3.
FORMAT INTENSIFIED OFF.
CLEAR DD02T.
SELECT * FROM DD02T WHERE TABNAME EQ TAB-TABNAME
AND DDLANGUAGE EQ SYST-LANGU
AND AS4LOCAL EQ 'A'.
ENDSELECT.
CLEAR DD02L.
SELECT * FROM DD02L WHERE TABNAME EQ TAB-TABNAME
AND AS4LOCAL EQ 'A'.
ENDSELECT.
WRITE: / 'Table Name ', TAB-TABNAME,
'Type=', DD02L-TABCLASS,
DD02T-DDTEXT.
WRITE: / 'Field', 20 'Description',
81 'Key', 75 'Type',
90 'Length', 100 'Decimals',
110 'Check Table',
141 'Data Element',
172 'Domain'.
FORMAT INTENSIFIED ON.
Message was edited by: Erik Verbeeck

Changing size of standard data element.

Hello here,
I need some clarification.
I have standard data element TIDNR - Technical identification number (Used in PM tables).
It has Data Type - CHAR and Length 25.
Is it possible to increase his length to 35?
Maybe, it is possible to create new data element ZTIDNR and make reference to TIDNR?
Or easily is to add some user field to equipment time segment?
Thank You in advance.
Edited by: andriy.hulyk on Nov 1, 2011 3:23 PM
Edited by: andriy.hulyk on Nov 1, 2011 3:24 PM

Hi andriy,
always be careful.
Check what the where-used-list says: It's not only the use in programs and database tables, all input/output fields are also affected and must be changed manually (which is a modification).
You may create an own translation table: If i.e. you allow only 96 characters as defined ind [CDC display code|http://en.wikipedia.org/wiki/CDC_display_code] , this can be reduced to 8 characters in 6 bytes or 33 chars in the original data element. Some bit&byte operations required for the conversion. If you define your own code with, say only A-Z, 0-9 and space and some more you can reduce to 5 bits having 8 characters in 5 bytes and so forth.
If you are on unicode with 2 bytes per char, possibilties are even more...
Yes, it's kind of a challenge - but at least an idea.
Regards,
Clemens

Data Element for No.Containers(GR Quantity tab)- QANZGEB

Hi All,
We are planning to reduce the decimal length from 3 to 1 in Data Element for No.Containers(GR Quantity tab)- QANZGEB field , while doing GR in ECC 6.0 , So that if we receive 1000 containers , we can enter.
We want to Know , what will be the implication in the system, do you recommend or what is the other alternative and what step we need to take after the modification.
Thanks & Regards,

Hi,
did you finally try it ? I would need also...
thanks

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

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

A problem when using a data element in BAPI

Hi there,
I build a function module, and want to use it as a BAPI. But when I add the function module as a method of a BAPI object, it gives me the following error: data type xxxxx cannot be used for methods.
I guess the problem happens because of the type of data element I used for the input parameter of the function module. Thus I tried many other data elements, but I keep getting the same error. I am really out of the game. Could anyone tell me which data element I should use for the input parameter of the function module? The function module has only one input parameter, which should be a string with length less than 100.
Thank you so much!!
Sincerely,
Bing

The function module has only one input parameter, which should be a string with length less than 256. (I tried many predefined data element like RPLM_STRING, but when I tried to add the function module as a method of BAPI, the SAP always gave me the error: data type xxxxx cannot be used for methods)
It only has one output parameter: RETURN (associated type: BAPIRETURN)
I am really not familiar with ABAP program, let alone BAPIs. Any suggestions would be very helpful to me. I sincerely appreciate your help.
Bing

Getting error while using the data element in ztable

though i specified the length as 20 in dataelement when i am entering the dataelement i am getting this error
while i used help i got the following information
Number of positions < minimum number (1) for data type CHAR
Message no. DO253
Diagnosis
A minimum length is required for the specified data type.
This minimum length is not reached by the specified number of positions.
Procedure
Increase the number of positions or select a more appropriate data type with the possible entries help F4.

This is strange, you shouldn't even be able to activate the dataelement type char with a length of 0. Revisit your data element and make sure that the length shows to be greater than 0 and reactivate your data element to make sure the newest version is active. In case you are referencing a domain in your data element do the same with the domain after validating that everything is correct (you can also use the check function). Then go back to your table and reenter the data element before activating your table.
Hope that helps,
Michael

Data element length modification

Similar Messages

Maybe you are looking for