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

Similar Messages

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

How to change filed length for Infotypes IT0197

Hello Gurus,
I have a requirement from my client regarding IT0197 (malaysia specific)
In the above infotype there is a field called SOCSO number. Currently the filed length defined is 20 characters in SE11.
But on the screen level, if we see it is allowing only 9 characters.
My question is we need to extend this from 9 characters to 12 characters on screen level.
Can we do this w/o access key. I heard we can do this with help of config. Please assist.... its bit urgent.
regds,
babu

Hi.
Can you share how you were able to change the screen field length?
We need to do the same thing at our company, but our ABAPer is not sure how.
Can you share the steps please?
Thanks.

Change field length

Using Oracle Database 9.2.0.5 on Oracle Enterprise Linux and Oracle Report Builder 10.1.2.0.2 on Microsoft Windows XP Professional SP2.
I have changed the length of a varchar2 column in my database from 4 to 8 and need to update the fields that correspond to that column in my reports.
How is this done?

The layout width of the field seems to be more than substantial to hold the 6 characters that should be displayed of which only 5 currently are.
The problem is in the Column property of the field the width attribute is only 5 when the corresponding database column is 8. The width attribute is a non-editable value when the field is a database item.
How do I refresh or force the field to update to the new length of 8?

Change field length via Admin Personalization?

As part of our ESS/MSS config, I have a requirement where I have to change the allowable number of characters for a number of input fields. Using Administrative Personalization, I can change the display field width, but I can't change the number of allowable characters.
Is this possible with configuration, or do I have to open up the code and change that (most likely dictionary changes)?
We're trying to shorten the field, so making this change should not cause any issues...but I need to know how to do it.

Hi,
I believe this is not possible using the webdynpro personalization, I suggest you to modify the ESS application as you have also mentioned.
Regards,
Ervin

Forms not updating field lengths

All,
I've been changing field lengths in forms all day in OIM 9.1, and it never updates the actual column lengths when the form is activated. I've reverted to directly updating the column sizes in the database to get things working. Am I missing something here, or are field length changes in OIM completely useless?
S

We faced recently a similiar problem, but regarding export/import operations.
We changed the forms in our dev environment, and sizes updated correctly in the database. But when exporting and importing the forms into the QA environment, although field size in the form definition was updated, the field size in the database table didn't.
The workaround we found was to manually change field sizes in the form definition.
Hope this help!

Infotype 0032 - Internal Data extend field length

Dear All,
We have a requirement to store employee's office location in SAP infotype through inbound interface from Active Directory. It seems infotype 0032 - Internal data is design to store such information under Work Center fields - Building number (6 char length), Room number (6 char length) & Telephone number but these fields are too small, Can I make these fields long? How? Some of EE's location is very long, so I am looking at around 30 Char so it does not chop-off the office location. Same with Phone number too, should be able to store international numbers with country codes e.g. 61-3- 7890-1234.
Please guide. Thank you.

Thank you for your reply.
Looking into above related threads, I am confused about the ways it could be done. It is obvious SAP has delivered above fields so small and it is necessary for us to make it longer. what is the right way - modify these standard fields (w/ getting access key to change) or create custom fields with same label description - Building number, Room number, Tel. number; which sounds redundant.
And if suggested creating custom fields to standard infotype then how to achieve thru PM01 or shown in above link - Append structure and ETC. I am a functional analyst not techincal person.

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

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.

How to create an infotype with one of its field length eq 1000.??

hi ,
i need to create a infotype where one of the field length is 1000 characters how do i achieve this. if i give more than 255 in the PS structure it will not allow. then how do i get a text field of 1000 chars in the screen ( which is an input field)

You can use those function calls even inside a PA Infotype.. they just invoke the text ediotr table control.. I gave you the reference of the PD infotype 1002 just for an idea. I don't think you will able to meet your 1000 char reqt without using the text editor.
~Suresh

Idoc segment field length changes

Hi friends,,
I am new to idoc.
My requirement is in my segment
i am having 5 fields and also this segment is already realeased one.
i wnat to change the field length from 10 to 20 . how to do this ?
actually what i did is
1. i cancel the release for that segment.
2. in that field inside the dataelement i changed the field length from 10 to 20.
3. data elemnt get chaged from 10 to 20 but Export length for that field in Idoc segment still retain the 10 only
can you plz how to resolve this
deva

Hi,
The way you used is right. ( cancel release or create a new segment )
After you cancel release, try delete that field, and insert a new one.
If it isn't valid still, create a new segment instead.
Regards
Sam

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

How to display dates on which the field of an infotype is changed

there are two fields in an infotype and both the fields are changed on different dates then how to display those dates on which the two fields are changed

Hi ankit,
If you want the change log for one infotype with one two fields, then write one custom program with following logic. If you want the log for multiple infotypes for multiple fileds then you have to use that program 'RPUAUD00'. Read the documentation of the program to check how to use it.
select * from pa0000 into table it_pa0000
where pernr = v_pernr.
sort it_pa0000 by begda descending.
loop at it_pa0000 into wa_pa0000.
write your own logic to compare the previous record PERSG with current record PERSG.
if this doesnt match then get the Changed DATE from AEDTM field.
wa_pa0000-AEDTM = changed date.
Else.
continue with loop.
exit.
endloop.
regards,
Shrinivas

Custom IDOC type Segment-field length change

Hello,
We have a custom segment developed for triggering Outbouds. I'm tring to change the Field length of a deta element used for one of the fields in the segment.
But after chaning the data element and activating it also, the changes are not effecting in WE31/ in the structure of the segment.
Process I'm following:
we31 <segment>
......cancel release
Change data element and activate
....set release.
Please suggest if something else can be done
Thanks,
Lucky.

> @Sarvesh: The IDOC segment has been released. I also re-imported the IDOC into XI - is that what you mean by 'reloaded'?
No, re-importing in XI is different from reloading the metadata into ABAP stack of XI using IDX2 transaction. So if you have not done this, then this could be the main reason of truncating the length.
Regards,
Sarvesh

Field length was changed in R/3 was this effect in BW

Hi ,
Field length of one Field was incresed in the data source.
the same data source/table is used for extracting the data from R/3 to BW.
will it effect these changes in BW side.
Thanks
Ram

Hi Ram,
It Affects 100%.for the Data.
If the field in the data source is suppose 15 and if the Info Object In BW is 12 the there are chances of missing 3 characters which might be crucial for the client.
<i>But there will not be any effect on Transfer Rules mapping or data load</i>.
Regards,
RK.

Changing field length in infotype 105

Similar Messages

Maybe you are looking for