Changing field length of a standard field in standard table VBEP

Hi,
Please advice the possibility and the possible repercussions of changing field lengths in a standard table. Table in concern is VBEP.
Thanks & Rgds,
Pradeep

No you cannot change the field length
thanks
G. Lakshmipathi

Similar Messages

Risks of changing the field length of data structure of a Cluster Table

Hello,
We are on ECC 604 and had implemented HR & Travel Management. Reporting on these applications is done in BI. We use ESS and & Mobile Travel for time, travel expenses, etc and use PCLn clusters.
There is business need to change the length of a field from 20 to 40 for the data structure PTK** of cluster table PCL1.
We are exploring various options to avoid core modifications.
We are also assessing the risks associated with changing the field length.
I am asking you for your opinion about the risks associated with changing the field length of a data structure of cluster table.
Thanks & Regards,
Manoj K Pingali

Recently, we came across the same situation where we had to change the length of a field. Let me explain you what precautions we had taken during that time.
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.
Thanks.
Anurag

Changing the length of a key field in a table

Hi,
I want to increase the length of the field from 2 to 4 in a standard SAP table and deliver it to the customers. This field is a key field in table. This field from this table is also used in view and view clusters.
What is the implication of changing the length to the customers. The customers would have already data in this field and they should not loose any data. Will the existing data for customers remain at length 2 or do they have to do some conversion?
Regards,
Srini.
Edited by: Srinivasa Raghavachar on Feb 7, 2008 12:45 PM

hi,
The database table can be adjusted to the changed definition in the ABAP Dictionary in three different
ways:
By deleting the database table and creating it again. The table on the database is deleted, the inactive
table is activated in the ABAP Dictionary, and the table is created again on the database. Data
existing in the table is lost.
By changing the database catalog (ALTER TABLE). The definition of the table on the database is
simply changed. Existing data is retained. However, indexes on the table might have to be built again.
By converting the table. This is the most time-consuming way to adjust a structure.
If the table does not contain any data, it is deleted in the database and created again with its new
structure. If data exists in the table, there is an attempt to adjust the structure with ALTER TABLE. If the
database system used is not able to do so, the structure is adjusted by converting the table.
Field 1     Field 2,    Field 3
NUMC,6 CHAR 8    CHAR, 60
Field 1    Field 2       Field 3
NUMC,6 CHAR, 8     CHAR,30
The following example shows the steps necessary during conversion.
Starting situation: Table TAB was changed in the ABAP Dictionary. The length of field 3 was reduced
from 60 to 30 places.
The ABAP Dictionary therefore has an active (field 3 has a length of 60 places) and an inactive (field 3
still has 30 places) version of the table.
The active version of the table was created in the database, which means that field 3 currently has 60
places in the database. A secondary index with the ID A11, which was also created in the database, is
defined for the table in the ABAP Dictionary.
The table already contains data.
Step 1: The table is locked against further structure changes. If the conversion terminates due to an
error, the table remains locked. This lock mechanism prevents further structure changes from being
made before the conversion has been completed correctly. Data could be lost in such a case.
Step 2: The table in the database is renamed. All the indexes on the table are deleted. The name of the
new (temporary) table is defined by the prefix QCM and the table name. The name of the temporary
Step 3: The inactive version of the table is activated in the ABAP Dictionary. The table is created on the
database with its new structure and with the primary index. The structure of the database table is the
same as the structure in the ABAP Dictinary after this step. The database table, however, does not
contain any data.
The system also tries to set a database lock for the table being converted. If the lock is set, application
programs cannot write to the table during the conversion.
The conversion is continued, however, even if the database lock cannot be set. In such a case
application programs can write to the table. Since in such a case not all of the data might have been
loaded back into the table, the table data might be inconsistent.
You should therefore always make sure that no applications access the table being converted
during the conversion process.
Step 4: The data is loaded back from the temporary table (QCM table) to the new table (with MOVECORRESPONDING).
The data exists in the database table and in the temporary table after this step.
When you reduce the size of fields, for example, the extra places are truncated when you reload the
data.
Since the data exists in both the original table and temporary table during the conversion, the storage
requirements increase during the process. You should therefore verify that sufficient space is available in
the corresponding tablespace before converting large tables.
There is a database commit after 16 MB when you copy the data from the QCM table to the original
table. A conversion process therefore needs 16 MB resources in the rollback segment. The existing
database lock is released with the Commit and then requested again before the next data area to be
converted is edited.
When you reduce the size of keys, only one record can be reloaded if there are several records whose
key cannot be distinguished. It is not possible to say which record this will be. In such a case you should
clean up the data of the table before converting.
Step 5: The secondary indexes defined in the ABAP Dictionary for the table are created again.
Step 6: The temporary table (QCM table) is deleted.
Step 7: The lock set at the beginning of the conversion is deleted.
If the conversion terminates, the table remains locked and a restart log is written.
Caution: The data of a table is not consistent during conversion. Programs therefore should not access
the table during conversion. Otherwise a program could for example use incorrect data when reading the
table since not all the records were copied back from the temporary table. Conversions therefore
should not run during production! You must at least deactivate all the applications that use tables to
be converted.
You must clean up terminated conversions. Programs that access the table might otherwise run
incorrectly. In this case you must find out why the conversion terminated (for example overflow of the
corresponding tablespace) and correct it. Then continue the terminated conversion.
Since the data exists in both the original table and temporary table during conversion, the storage
requirements increase during conversion. If the tablespace overflows when you reload the data from the
temporary table, the conversion will terminate. In this case you must extend the tablespace and start the
conversion in the database utility again.
If you shorten the key of a table (for example when you remove or shorten the field length of key fields),
you cannot distinguish between the new keys of existing records of the table. When you reload the data
from the temporary table, only one of these records can be loaded back into the table. It is not possible
to say which record this will be. If you want to copy certain records, you have to clean up the table
before the conversion.
During a conversion, the data is copied back to the database table from the temporary table with the
ABAP statement MOVE-CORRESPONDING. Therefore only those type changes that can be executed
with MOVE-CORRESPONDING are allowed. All other type changes cause the conversion to be
terminated when the data is loaded back into the original table. In this case you have to recreate the old
state prior to conversion. Using database tools, you have to delete the table, rename the QCM table to
its old name, reconstruct the runtime object (in the database utility), set the table structure in the
Dictionary back to its old state and then activate the table.
If a conversion terminates, the lock entry for the table set in the first step is retained. The table can no
longer be edited with the maintenance tools of the ABAP Dictionary (Transaction SE11).
A terminated conversion can be analyzed with the database utility (Transaction SE14) and then
resumed. The database utility provides an analysis tool with which you can find the cause of the error
and the current state of all the tables involved in the conversion.
You can usually find the precise reason for termination in the object log. If the object log does not
provide any information about the cause of the error, you have to analyze the syslog or the short dumps.
If there is a terminated conversion, two options are displayed as pushbuttons in the database utility:
After correcting the error, you can resume the conversion where it terminated with the Continue
adjustment option.
There is also the Unlock table option. This option only deletes the existing lock entry for the table .
You should never choose Unlock table for a terminated conversion if the data only exists in the
temporary table, i.e. if the conversion terminated in steps 3 or 4. table for table TAB is therefore QCMTAB.
Hope this is helpful,Do reward.

Field Length of the text field on the screen

Hello Experts,,
I have field with its label on the screen. Now the label text is picked up from data dictionary as defined.
Data element       J_3ARQDA                       Active
Short Description: Requested delivery date
Length           Field   Label
Short             10       RqDlv.date
Medium         16       Req.deliv.date
Long              20      Requested deliv.date
Heading         5        Dldat
Now the text in different laguage say russian is quite bigger in length as compared to english ones. Now on the sales order screen i have the text 'Dldat', but the russian user needs a bigger word than just 'Dldat'.
Approach : I changed the heading length to some '25' from '5' to accomedate the russian text in DDIC for data element. But if i have to adjust the same on the screen with new text length i have to extend the screen border as well.
Is this right approach ? If not how do we actually accomedate the other language texts on the screen with out altering the screen borders ( length and breadth).

Hi Radhika,
I tried doing that with a couple of invoices but I dont see the Long text printed on the check after the automatic payment run. Can you please suggest me if I am missing on anything. I inserted a long text and a '*" before this to have it printed on the check which does not seem to work. Can you please suggest me alternative solution.
   Thanks in advance.
Ramya

GL Account Field length

Hi,
My client wants to change the account field length in the doc entry. Standard account field is length is 16 or 17 digits. Its length has to be reduced to 10 digits.
How can i do this ? Can I do this in the configuration (or) customisation ? If it is customisation what are the tables I need to touch ?
Awaiting for the reply
Thanks,
Krishna

Use Transaction code OB13 to maintain maiximum length of GL account length as 10 apart from this you can also write validation so that if any gl account with more that 10 digits is entered system gives error.
Regads,
Manish Jain
Assign points if it serves your purpose.

EEWB field length modification error

Hi,
In our system, an EEWB project is already exist for custom fields in Quotation's product item (CI_EEW_CUSTOMER_I).
I want to change the field length of those custom fields. Thus, I run the wizard of this EEWB project and change some of the field length.
After the wizard and some of the tables are converted, following error occurs:
Task CRM_BTX_ADD_NEW_FIELDS CD3100
deleting of existing BAdI Implementation "ZEEW_CUSTOMER_I01" failed
Moreover, the EEWB icon is changed to red & broken.
How can I continue and make it back to normal?

Hi
The error is coming because EEWB does changes in the ABAP dictionary objects. Now you are not able to delete the field properly thats why you are getting the error
Once you delete the field then only you can process.
check your customizing in transaction EEWC.
Look at note 649336 to set up the customizing.
Regards
Manohar

CATT - vendor/customer master address field length over

Dear all,
when use CATT to record vendor/customer master,the address some fields length are over recorded field length(ex. ADDR1_DATA-NAME4,ADDR1_DATA-STR_SUPPL3...etc)
is there any config in CATT to solve this kind of problem?

When you are doing your LSMW batch input recording, on selection screen (where you specify the sales org, distribution channel, division, account group, etc) please put a flag on "Use central address management" checkbox (SAPMF02D 0100 > USE_ZAV).
In this case you should be able to see and fill the desired fields.

What is the best way to declare field length 500 in internal table?

Hi all,
what is the best way to declare field length 500(constant value allways) in internal table?
I am trying to send data from internal table to file format, and I have a field in internal table with 500 length (constant value always). So how do I can declare and append this field value to table?
Thanks
Murali

Hi. Please see the following example program, notice how I am filling the field with the constant value.
report zrich_0001.
*       CLASS lcl_main DEFINITION
class lcl_main definition.
public section.
    types: begin of ttab,
            fld1(500) type c,
           end of ttab.
    data: itab type table of ttab.
    data: xtab type ttab.
    methods: constructor,
             write_itab.
endclass.
*       CLASS lcl_main IMPLEMENTATION
class lcl_main implementation.
method constructor.
<b>
    xtab-fld1 =
      'This is one part of the total string which needs to be really' &
      ' long and this is a constant and we need to move it to a work' &
         ' area and then append it to the internal table which has a' &
          ' field with a length of five hundred characters'.
    append xtab to itab.</b>
endmethod.
method write_itab.
    loop at itab into xtab.
      write:/ xtab-fld1.
    endloop.
endmethod.
endclass.
data: o_main type ref to lcl_main.
start-of-selection.
create object o_main.
call method o_main->write_itab.
Regards,
Rich Heilman

Regardig Field Length in ALV

I am trying to set the field length in ALV
so i wrote
<fs_fcat>-outputlen = 15.
and in layout...
wa_layout-colwidth_optimize = space . tried by commenting this statment also
But it doesnt show any effect
" in fact field length is depend on field lable and on its content..."
so plz help me some buddy.....
Edited by: anurodh_t on Sep 29, 2010 3:58 PM

Hello,
Try updating the description fields of the Fieldcat records prior to defining the outputlen field. Depending on the way you are implementing your ALV, try updating the following fields:
scrtext_l
scrtext_m
scrtext_s
or
seltext_l
seltext_m
seltext_s
Best regards,
Mário Espinheira

Field Lengths in Smartforms

Hi All,
How can we make the field lengths of all the fields to be displayed in smartforms of the same length so that they are aligned properly.
Eg: V_field1 is of length 8,
V_field2 is of length 2.
Both are of the type Z table.
How can this be done in smartforms to display both of same length.
Thanks,
Saher

Hi,
Use like below
Eg: V_field1+(08)
V_field2+0(2).
Regards
Jana

How to change the length of a JTextField?

Hello,
I am trying to shorten the length of a JTextField with the following code :
// up to this point, getColumns() returns a value of 35.
jTextField1.setColumns(20);
(jTextField1.getParent()).invalidate();
(jTextField1.getParent()).validate();
When I ran this code, it does not change the length of the text field at all.
I wonder if I am writing my code correctly or is there a better/more correct
way to do this?
Thank you for your help.
Akino.

Packing a frame works:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class ShortText implements ActionListener {
    JTextField txtF;
    JFrame frame;
    public ShortText() {
     frame = new JFrame();
     frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
     txtF = new JTextField(30);
     JButton btn = new JButton("Shorten");
     btn.addActionListener(this);
     frame.add(txtF, BorderLayout.NORTH);
     frame.add(btn, BorderLayout.SOUTH);
     frame.pack();
     frame.setVisible(true);
    public static void main(String[] args) {
     new ShortText();
    public void actionPerformed(ActionEvent e) {
     System.out.println("Old Columns: " + txtF.getColumns());
     txtF.setColumns(20);
     frame.pack();
     System.out.println("New Columns: " + txtF.getColumns());
}

How to change the field length in standard sap program.

Hi All,
How to change the field length in standard sap program.
Urgent
Example:
Text1 type c length 75,
To change :
Text1 type c length 150,
Point will be rewarded..
Thank you,
Vikram.C

If the only solution is to change the sap standard program, simply change the program, it will prompt for an access key. This key can be retrieved in the SAP support portal (service.sap.com) at keys and requests, sccr keys, register object.
Sometimes these actions are outsourced to a competence center, so maybe youre not entitled to do this, in any case ask a resident senior developer for support.
regards, Rob

Changing field length in infotype 105

Good morning
We wish to use both IT105 subtype 0010 and IT105 subtype 9000 to handle external email accounts.
Subtype 9000 has field name USRID with length 30 xhars.
Subtype 0010 has field name USRID_LONG with length 240 chars.
1. Can I and if so, how do I, change the length of subtype 9000 to 240 chars?
2. If not then could I have both subtype 9000 and 0010 pointing to USRID_LONG - if so how do I do it and what are the consequences?
Many thanks
DCoutts

Hi,
1.Its not possible to change the character Length of standard Field.
2.Tick the checkbox in table V_T591C for Long ID.
Manoj

Unable to change the length of field in idoc segment

Dear all,
My requirement is to change the length of a field(Z field) in a segment (Z Segment). I tried the following but in vain
1)Tried to Cancel the release and then change the length of the domain. Unfortunately it is givin an error saying "Error while resetting release of segment ZC9DEMARA01".
I also tried cancelling hte release of extension and then cancelled the release of segment
2) Created a new version, but in new version the earlier fields are diabled. So I am unable to edit.
I have gone through some of the links available in SDN but I could not solve as I am unable to cancel the release in the first step.
[Idoc segment field length changes]
Could you please help me.
Thanks in advance!
regards,
Aravind

Hello Aravind,
I Have created one Segment type with some fields, changed the field length also its working.
just try to cancel the release and change the length of the filed and do it set release again.
Try it .
Thanks,
santhosh

How to change search help for standard field in me51n.

hi frnds,
I want to change search help option for 'Advice code' field under Additional DFPS tab in me51n. But i dont know how to change or add search help for standard field. so plz help..
best regards,
sudip biswas

Hi Abhi,
Try using any one option:
Create a Search Help in SE11.
Now Goto SE11 -> Enter Ztable -> Select that field -> Click Search Help and try to assign the created Search help to that field in your Ztable explicitly
OR
Create a Zdata element in SE11.
In Data Element, under Further Characteristics tab, enter Name Parameters of Search Help.
Assign this data element to that field in ur Ztable.
OR
Create a Zdomain and maintain a Value Table or Fixed Values for it.
Assign this domain to that field in ur Ztable.

Changing field length of a standard field in standard table VBEP

Similar Messages

Maybe you are looking for