Increasing the length of Char type Info-object ( impact )?

Hi,
We are on BW3.5 version and we have a custom defined Info-object ZP_REPORT(say )whose length is 3 now as all the three digit series will be used up in near future we have a requirement to increase the length of the characteristic.
This Info-object is used Navigation attribute of 0Material. And also this info-object is used as Navigational characteristic in few Info-cubes.
Can any one please let me know what would be the impact of increasing the length?
1)Do I need to delete the master data from this ZP_REPORT?
2)DO I need to delete the master data from 0MATERIAL?
3)Will there be any impact on Info-Cubes?
Thanks in advance.
Regards
Ajay

Hi Ajay,
It is always big challenge to change the existing info object lengh or type or anything that have gone live already..........
But if we will be very careful at the time of changing length and transport, we can do it succefully......
Lets come to your scenario... In my understanding
i) Your scenario is going to change the info object length that info object is only available for attribute. It is not at all used anywhere in the dimenstion table. So your cube will not be affected.... If problem will come your master data only will be affected.... Verify more than one time your info object is not at all used in any cubes. (Go to infoobject change mode check in where used list)
ii) Before changing the length in development, data should be available in development cube as well as master data.. Because you can verify it in development itself whether the data will be deleted or not at the time of changing the length and activate the info object.
iii) At the time of transport transport only the particular info object. Dont sent any other info objects. That might have related with any cube.
iv) For safety purpose check whether your info cube is having which type of load. Either Full load or Delta. Most of the cubes will be having delta. If it is full, then we dont have more worry on that.
v) Finally if possible, create one backup cube and back master data and load data from your existing cube to that cube. If the data will be more that 2 GB it is not a simple task to take a backup..... This is only for safty purpose......
Please let me know your status...............
Best Regards,
Vivek

Similar Messages

  • How to increase the length of the Info object

    Hi All
         Any one have idea about how to increse the length of the Info object Char(beyond 60). Can you please explain me in detail we are using BI7.0.
    Thanks
    Vani

    Hello Vani,
    You cannot increase the length of an info-object beyond 60 chars.However if you want to store a characteristics data with more than length 60, then you may create separate info-objects
    for example: if you need to store 'notes' which might have length more  than 60,
    then you may create info-objects like notes 1/3 ---store first 60 chars.
    notes 2/3 --- store next 60 characters and so on.
    Thanx
    Priyanka

  • How to increase the length of the char which has master data!

    Hi,
    I am uploading hierarchy from flat file!
    i am using basic char texts as hierarchy texts  and my basic char has length  15 )
    Because the first 15 characters of the hierarchy short text are same, and it s total length being 15, while uploading it is giving me error saying same record values cannot be used more than once!
    ( i am using nodename as hierarchy texts  and my basic char has length  15 )
    when i try to increase the length of the char by deleting entries in it, the delete option is grayed out!
    Any suggestions?
    Thanks,
    Ravi

    Hi,
    Check it out that object where-used list, whether that object is used in any other cubes or ODS or any target......
    If it is used then delete all the data from all the targets and also object data itself.
    Then it is possible to increase the length.
    One more thing is if you want to change in Production system directly ,may be you have the display authorization only.
    You have to change it in to development system and trasport it to production system.
    Regards,
    Venkat

  • Increasing the length of Infoobject from 60 to 240 characters

    Hi...
    I want to increase the length of the infoobject from 60 to 240 characters, because that particular field in R/3 has texts with length 200 characters.
    I want to create 4 infoobjects each of length 60, breakup the texts coming from R/3, in transfer rules, by writing the transfer routine for each infoobject stating, first 60 char of the r/3 field into the first infoobject and so on.
    Did anyone write such routine? If so, can u provide me with the code?
    Thanks a lot.
    Sai.

    Hi Sai,
    I usually prepare data before load cutting long texts into parts (in case of flat files I use Access for it, for DB Connect – create a view).
    But for future usage it would be usefull to do it in a routine.
    The task seemed to be very easy, but some important nuances have appeared.
    Note: I always prefer to keep parts of the long description in the long texts of separate chars. The reasons for this: Possibility to use time-dependent texts and texts with lowercase letters without problems with SIDs.
    So, I use one main object with child objects (which keep parts of the text) as attributes. The long text of the main object keeps the first 60 (or 59) symbols of the long description. In this case I create either main or child IOs not as CHAR 60, but as another type depending on the key field of the incoming description (for example, for  a material description it may be its code). In the codes below I use 0ADDR_LINE1 - 0ADDR_LINE4 standard IOs for description parts – in order not to create 4 objects of CHAR 60 which I will not use.
    So, here is a result.
    For simplicity I assume that I have only 4 IOs like 0ADDR_LINEx and one IO as a main char.
    <b>1.     Case of load from flat files</b>
    - Create a flexible infosource.
    - Put there the main char and  0ADDR_LINE1, 0ADDR_LINE2, 0ADDR_LINE3, 0ADDR_LINE4.
    - After assigning a source system the transfer structure is created automatically.
    - Since in the comm structure (which the system uses as a template for creation TS and TRs) the 0ADDR_LINE1 char has a length 60, we need to increase the length of this object upto 240 symbols in the TS.
    - Main char and 0ADDR_LINE1 wil have 1:1 mapping in transfer rules.
    - Mapping of the other chars depends on type of routine we use
    - In case of a start routine, all other chars are to be mapped as 1:1 also. Its important, because in the start routine (which works BEFORE the work of routines for particular chars) we create values for them and 1:1 mapping is placed these values into IOs. If these IOs are not mapped, then regardless of existing data for them in the data package, they’ll not be updated at all.
    The start routine code:
    FIELD-SYMBOLS <fs> TYPE TRANSFER_STRUCTURE.
    LOOP AT DATAPAK ASSIGNING <fs>.
      <fs>-ADDR_LINE2 = <fs>-ADDR_LINE1+60(60).
      <fs>-ADDR_LINE3 = <fs>-ADDR_LINE1+120(60).
      <fs>-ADDR_LINE4 = <fs>-ADDR_LINE1+180(60).
      MODIFY DATAPAK FROM <fs>.
    ENDLOOP.
    * abort <> 0 means skip whole data package !!!
      ABORT = 0.
    As an alternative it’s possible to create routines for ADDR_LINE2, ADDR_LINE3 and ADDR_LINE4.
    The code is very simple:
      RESULT =   TRAN_STRUCTURE-ADDR_LINE1+180(60).
    * returncode <> 0 means skip this record
      RETURNCODE = 0.
    * abort <> 0 means skip whole data package !!!
      ABORT = 0.
    This is for ADDR_LINE4. For the other IOs the offset will be 60 and 120.
    <b>2.     Case of loading from R/3 or 3rd parties systems.</b>
    Routines for ADDR_LINE2, ADDR_LINE3 and ADDR_LINE4 is a straightforward solution. In case of a start routine, the source system should supply besides the long description 3 additional dummy fields with length 60. And mapping will be 1:1 for all fields.
    The rest is simple – inserting main and child IOs as data targets, creating update rules for them with proper mapping to incoming from a comm structure ADDR_LINEx values. Value of main IO should be set as a key field for all IOs.
    Best regards,
    Eugene
    Message was edited by: Eugene Khusainov

  • How to increase the length of a message in message class

    Hi Friends,
    Is there any way to increase the length of a message in a message class as the maximum length is 72 chars.
    My requirement is I cannot use the Long text option.
    Thank You

    HI,
      We cannot change the message length in the message class
    but you can do one thing ,
    while giving the message in your msg class write till which you are allowed to and then you put '&'
    eg : this is message &
    now goto text elements and create a text element suppose T00
    and write the remaining text in that text element.
    and when you want to display the message do it like
    message i00(zmsg_class) with text-T00.
    it ll work.
    *****Reward if useful,
    Thanks & Regards,
    Sunny Suren .C.

  • How to increase the length of charcteristics

    Hi all
    I want to concatenate four characteristics into one, but the problem is that when i m doing the same, the length of my concatenated (resulted) char is excceded 60 char. Is there any other way to do the concatenation or can i increase the length of resulted characteristics by any means.
    Regards
    Ritesh

    Hi Ritesh,
       You can not increase size of infoobject more than 60 chars.
       Have a look, it may helps
    /people/sap.user72/blog/2006/05/27/long-texts-in-sap-bw-modeling
    Srini

  • How to Increase the Length of Condition table in OV20

    While creating a condition table in T.code OV20 if fields length is more that 50 bytes table is not getting generated.it gives error as Too Many Fields Selected(More than 50 Bytes).
    Actually i need to create a tabel with Basic Material(WRKST) which has length of 48 bytes.
    Is there a solution on how to increase the length so that error is avoided.
    There is no such error occuring while crating condition table in V/03

    Hi,
         You can try to use the type string:
    form like zscr_data_hdr-form,
    werks like zscr_data_hdr-werks,
    matnr like zscr_data_hdr-matnr,
    verid like zscr_data_hdr-verid,
    lot like zscr_data_hdr-lot,
    lot_qty like zscr_data_hdr-lot_qty,
    udate like zscr_data_hdr-udate,
    utime like zscr_data_hdr-utime,
    zuser like zscr_data_hdr-zuser,
    processed like zscr_data_hdr-processed,
    defect like zscr_defect_data-defect,
    vornr like zscr_route_data-vornr,
    fieldxx type string,
    dayst like zscr_data_hdr-dayst,
    end of t_data.
    So you can save you informations of every fld<n> concatenating their values into fieldxx.
    Regards

  • How to increase the length of internal table dynamically

    How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
    The requirement code :
    types: begin of t_data,
             form          like zscr_data_hdr-form,
             werks         like zscr_data_hdr-werks,
             matnr         like zscr_data_hdr-matnr,
             verid         like zscr_data_hdr-verid,
             lot           like zscr_data_hdr-lot,
             lot_qty       like zscr_data_hdr-lot_qty,
             udate         like zscr_data_hdr-udate,
             utime         like zscr_data_hdr-utime,
             zuser         like zscr_data_hdr-zuser,
             processed     like zscr_data_hdr-processed,
             defect        like zscr_defect_data-defect,
             vornr         like zscr_route_data-vornr,
             fld1          like zscr_defect_data-defect_val,
             fld2          like zscr_defect_data-defect_val,
             fld3          like zscr_defect_data-defect_val,
             fld4          like zscr_defect_data-defect_val,
             fld5          like zscr_defect_data-defect_val,
             fld6          like zscr_defect_data-defect_val,
             fld7          like zscr_defect_data-defect_val,
             fld8          like zscr_defect_data-defect_val,
             fld9          like zscr_defect_data-defect_val,
             fld10         like zscr_defect_data-defect_val,
             fld11         like zscr_defect_data-defect_val,
             fld12         like zscr_defect_data-defect_val,
             fld13         like zscr_defect_data-defect_val,
             fld14         like zscr_defect_data-defect_val,
             fld15         like zscr_defect_data-defect_val,
             fld16         like zscr_defect_data-defect_val,
             fld17         like zscr_defect_data-defect_val,
             fld18         like zscr_defect_data-defect_val,
             fld19         like zscr_defect_data-defect_val,
             fld20         like zscr_defect_data-defect_val,
             fld21         like zscr_defect_data-defect_val,
             fld22         like zscr_defect_data-defect_val,
             fld23         like zscr_defect_data-defect_val,
             fld24         like zscr_defect_data-defect_val,
             fld25         like zscr_defect_data-defect_val,
             fld26         like zscr_defect_data-defect_val,
             fld27         like zscr_defect_data-defect_val,
             fld28         like zscr_defect_data-defect_val,
             fld29         like zscr_defect_data-defect_val,
             fld30         like zscr_defect_data-defect_val,
             fld31         like zscr_defect_data-defect_val,
             fld32         like zscr_defect_data-defect_val,
             fld33         like zscr_defect_data-defect_val,
             fld34         like zscr_defect_data-defect_val,
             fld35         like zscr_defect_data-defect_val,
             fld36         like zscr_defect_data-defect_val,
             fld37         like zscr_defect_data-defect_val,
             fld38         like zscr_defect_data-defect_val,
             fld39         like zscr_defect_data-defect_val,
             fld40         like zscr_defect_data-defect_val,
             fld41         like zscr_defect_data-defect_val,
             fld42         like zscr_defect_data-defect_val,
             fld43         like zscr_defect_data-defect_val,
             fld44         like zscr_defect_data-defect_val,
             fld45         like zscr_defect_data-defect_val,
             fld46         like zscr_defect_data-defect_val,
             fld47         like zscr_defect_data-defect_val,
             fld48         like zscr_defect_data-defect_val,
             fld49         like zscr_defect_data-defect_val,
             fld50         like zscr_defect_data-defect_val,
             fld51         like zscr_defect_data-defect_val,
             fld52         like zscr_defect_data-defect_val,
             fld53         like zscr_defect_data-defect_val,
             fld54         like zscr_defect_data-defect_val,
             fld55         like zscr_defect_data-defect_val,
             fld56         like zscr_defect_data-defect_val,
             fld57         like zscr_defect_data-defect_val,
             fld58         like zscr_defect_data-defect_val,
             fld59         like zscr_defect_data-defect_val,
             fld60         like zscr_defect_data-defect_val,
             fld61         like zscr_defect_data-defect_val,
             fld62         like zscr_defect_data-defect_val,
             fld63         like zscr_defect_data-defect_val,
             fld64         like zscr_defect_data-defect_val,
             fld65         like zscr_defect_data-defect_val,
             fld66         like zscr_defect_data-defect_val,
             fld67         like zscr_defect_data-defect_val,
             fld68         like zscr_defect_data-defect_val,
             fld69         like zscr_defect_data-defect_val,
             fld70         like zscr_defect_data-defect_val,
             fld71         like zscr_defect_data-defect_val,
             fld72         like zscr_defect_data-defect_val,
             fld73         like zscr_defect_data-defect_val,
             fld74         like zscr_defect_data-defect_val,
             fld75         like zscr_defect_data-defect_val,
             fld76         like zscr_defect_data-defect_val,
             fld77         like zscr_defect_data-defect_val,
             fld78         like zscr_defect_data-defect_val,
             fld79         like zscr_defect_data-defect_val,
             fld80         like zscr_defect_data-defect_val,
             fld81         like zscr_defect_data-defect_val,
             fld82         like zscr_defect_data-defect_val,
             fld83         like zscr_defect_data-defect_val,
             fld84         like zscr_defect_data-defect_val,
             fld85         like zscr_defect_data-defect_val,
             fld86         like zscr_defect_data-defect_val,
             fld87         like zscr_defect_data-defect_val,
             fld88         like zscr_defect_data-defect_val,
             fld89         like zscr_defect_data-defect_val,
             fld90         like zscr_defect_data-defect_val,
             fld91         like zscr_defect_data-defect_val,
             fld92         like zscr_defect_data-defect_val,
             fld93         like zscr_defect_data-defect_val,
             fld94         like zscr_defect_data-defect_val,
             fld95         like zscr_defect_data-defect_val,
             fld96         like zscr_defect_data-defect_val,
             fld97         like zscr_defect_data-defect_val,
             fld98         like zscr_defect_data-defect_val,
             fld99         like zscr_defect_data-defect_val,
             fld100         like zscr_defect_data-defect_val,
             fld101         like zscr_defect_data-defect_val,
             fld102         like zscr_defect_data-defect_val,
             fld103         like zscr_defect_data-defect_val,
             fld104         like zscr_defect_data-defect_val,
             fld105         like zscr_defect_data-defect_val,
             fld106         like zscr_defect_data-defect_val,
             fld107         like zscr_defect_data-defect_val,
             fld108         like zscr_defect_data-defect_val,
             fld109         like zscr_defect_data-defect_val,
             fld110         like zscr_defect_data-defect_val,
             fld111         like zscr_defect_data-defect_val,
             fld112         like zscr_defect_data-defect_val,
             fld113         like zscr_defect_data-defect_val,
             fld114         like zscr_defect_data-defect_val,
             fld115         like zscr_defect_data-defect_val,
             fld116         like zscr_defect_data-defect_val,
             fld117         like zscr_defect_data-defect_val,
             fld118         like zscr_defect_data-defect_val,
             fld119         like zscr_defect_data-defect_val,
             fld120         like zscr_defect_data-defect_val,
             fld121         like zscr_defect_data-defect_val,
             fld122         like zscr_defect_data-defect_val,
             fld123         like zscr_defect_data-defect_val,
             fld124         like zscr_defect_data-defect_val,
             fld125         like zscr_defect_data-defect_val,
             fld126         like zscr_defect_data-defect_val,
             fld127         like zscr_defect_data-defect_val,
             fld128         like zscr_defect_data-defect_val,
             fld129         like zscr_defect_data-defect_val,
             fld130         like zscr_defect_data-defect_val,
             fld131         like zscr_defect_data-defect_val,
             fld132         like zscr_defect_data-defect_val,
             fld133         like zscr_defect_data-defect_val,
             fld134         like zscr_defect_data-defect_val,
             fld135         like zscr_defect_data-defect_val,
             dayst         like zscr_data_hdr-dayst,
           end of t_data.
    In this fld1 to fld135 are defined in internal table.
    But if the number of fields are more than 135 then the program is going to short dump.
    Some times fld1 to fid170 or more fields will be there in my internal table.
    Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

    Hi
    You can try to use the type string:
    form like zscr_data_hdr-form,
    werks like zscr_data_hdr-werks,
    matnr like zscr_data_hdr-matnr,
    verid like zscr_data_hdr-verid,
    lot like zscr_data_hdr-lot,
    lot_qty like zscr_data_hdr-lot_qty,
    udate like zscr_data_hdr-udate,
    utime like zscr_data_hdr-utime,
    zuser like zscr_data_hdr-zuser,
    processed like zscr_data_hdr-processed,
    defect like zscr_defect_data-defect,
    vornr like zscr_route_data-vornr,
    fieldxx type string,
    dayst like zscr_data_hdr-dayst,
    end of t_data.
    So you can save you informations of every fld<n> concatenating their values into fieldxx.
    Max

  • If we can increase the length of the Short Text field in a purchase order?

    Hi Experts,
    Please suggest if we can increase the length of the Short Text field in a purchase order?
    If yes, How? and what will be the impact?
    Thanks
    Gavar

    Dear Arpit,
    You can use PO Text field for long description of the material.
    Regards,
    Manish Jain

  • To increase the length of a vanilla column

    Hello Everyone,
    I have a situation, where I have to increase a length of a vanilla column in siebel.
    I have to increase the length of a base column CORP_STOCK_SYMBOL of a vanilla table S_ORG_EXT. From the tools level I can't do this as it does not allow me to.
    If I can make the change from the backend, it won't reflect the same in the tools(Logical Level). But in the DB level you can see that the length has altered. But when u try to update a value and then open the application it throws an SQL error. What I am thinking is, though the length is altered at the physical level, in logical level it has not changed therefore i guess the SQL error is popping.
    Or can I alter the S_COLUMN table itself? If it is done, I fear the problem while migrating this to different environment.
    Please let me know the solution for this if any of you people have encountered the similar situation.

    If you insist on increasing the length of the column, I would get Oracle involved.
    Another option might be to use a different column or create a new column.

  • How do I increase the length in data file

    I have been getting this error, can anyone tell me why I'm getting the error below and help me fix the the error( increase the length of data file.
    This is my Control file
    LOAD DATA
    INFILE Job.dat
    APPEND INTO TABLE job
    FIELDS TERMINATED BY x'09'
    (PositionID, jobID, title, code, family)
    This is my data in my data file
    PositionID JobID Title Code family
    50003490 1 NULL 001610 NULL
    50004865 1 NULL 001615 NULL
    ERROR
    SQL*Loader: Release 10.2.0.1.0 - Production on Fri Jul 13 10:17:33 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Control File: Position1.ctl
    Data File: Job.dat
    Bad File: Job.bad
    Discard File: none specified
    (Allow all discards)
    Number to load: ALL
    Number to skip: 0
    Errors allowed: 50
    Bind array: 64 rows, maximum of 256000 bytes
    Continuation: none specified
    Path used: Conventional
    Table JOB, loaded from every logical record.
    Insert option in effect for this table: APPEND
    Column Name Position Len Term Encl Datatype
    POSITIONID FIRST * WHT CHARACTER
    JOBID NEXT * WHT CHARACTER
    TITLE NEXT * WHT CHARACTER
    CODE NEXT * WHT CHARACTER
    FAMILY NEXT * WHT CHARACTER
    Record 1: Rejected - Error on table JOB, column POSITIONID.
    Field in data file exceeds maximum length
    Record 2: Rejected - Error on table JOB, column POSITIONID.
    Field in data file exceeds maximum length
    Record 3: Rejected - Error on table JOB, column POSITIONID.
    Field in data file exceeds maximum length
    Record 4: Rejected - Error on table JOB, column POSITIONID.

    this is the structure of my table
    create table job (PositionID number(20) not null,
    jobID number(20) not null, title nvarchar2(255), code nvarchar2(255), family nvarchar2(255),
    constraint job primary key (PositionID, jobID))
    organization index
    Tablespace Position
    pctthreshold 20
    overflow tablespace users;
    comment on table job is 'This table defines the job(s) associated with the position. There can be multiple jobs allowed although the preferred business rule is for one job per position.';
    alter table job add constraint FKjob373174 foreign key (PositionID) references Position;

  • How to increase the length of the subject line in email using FM

    Hi
    we have maintained 50 characters for the subject line initially, but some subjects are having more than 50 characters. how can we increase the length of the subject line in email.
    urgent.
    points will be rewarded generousely.

    Hi Rana,
    In this case, you have to create a user defined field of required length under Journal Transactions Header to fill the data.
    Regards,
    Vijay Kumar
    SAP Business One Forums Team

  • How to increase the length of a columnin existing publication item

    We need to urgently increase the length of three columns in one of the tables that is sent offline as a publication item. I have searched everywhere to see if there is a procedure to see this. I only found process to add/drop columns but not modify to JUST increase the length.
    Can we just alter the tables on the server and republish the application? Will that cause any data loss on the client end?
    Any help is greatly appreciated.
    Thanks
    Sireesha

    I totally forgot about this method. Metalink had it in the headlines today and remembered your question.
    This should work for you.
    Applies to:
    Oracle Lite - Version: 10.2.0.1.0 to 10.2.0.2.0
    Information in this document applies to any platform.
    Goal
    The Goal of this Document is to show the right steps when it is necessary to increase the Column Size for a table
    which is used for the Synchronization with Oracle Lite 10GR2
    BECAREFULL, it is not supported to change the Column Size or make any Schema Evolution on the Primary key
    as The Synchronization Algorithm is based on Primary key
    Solution
    Create table test_sec (col1 number(10); varchar2(10));
    alter table test_sec add primary key (col1));
    Create Publication: PUB_TEST_SEC
    Create Publication: PI_TEST_SEC: select COL1, COL2 from scott.TEST_SEC fast
    Refresh, server wins, weight = 1 and add it to the Publicatio PUB_TEST_SEC
    Synchronize this PUB_TEST_SEC
    On the Server: increase the col2 WHICH IS NOT A PK, from 10 to 15
    alter Table scott.TEST_SEC modify (col2 (varchar2(15));
    To get the new Column Size on the olite DB, you need to alter the Publication item too using for example this code:
    import java.sql.*;
    import java.io.*;
    import oracle.lite.sync.Consolidator;
    import oracle.lite.sync.ConsolidatorManager;
    import oracle.mobile.admin.*;
    public class PublicationChange {
    public static void main(String argv[]) throws Throwable
    DriverManager.registerDriver ((Driver)Class.forName ("oracle.jdbc.driver.OracleDriver").newInstance());
    ConsolidatorManager consolidatorManager = new ConsolidatorManager();
    consolidatorManager.openConnection("mobileadmin","manager","JDBC:ORACLE:thin:@suppolite1.fr.oracle.com:1521:PROD");
    System.out.println("Connected");
    try
    /*You need to put a Select Statment lightly different from the Publication item,
    if you will use the same select statment, it won't take in Account
    if you used: select * from owner.table to create the Publication Item
    you need to use: select * from owner.table for the alterPublicationItem API
    consolidatorManager.alterPublicationItem("PI_TEST_SEC","SELECT * FROM SCOTT.TEST_SEC");
    System.out.println("Pub Item recreated");
    catch (Throwable e) {
    e.printStackTrace();
    try
    consolidatorManager.closeConnection();
    System.out.println("The installation is done!");
    } catch (Throwable e) {
    Compile and run this java code.
    Synchronize
    Check your table Description on Oracle Lite Database to verify that this Schema Evolution has worked as expected.

  • How to increase the length of the identifier?

    I want to create a table with a column name as:
    "domainnameregistrationassistance"
    oracle 9i does not allow me to do this.
    as the identifier length is fixed to 30 characters.
    how do i increase the length of the identifier?
    any help on this will be great!

    Don't forget that there is a comment space for each table
    and column, so calling the column DNR_ASSIST doesnt
    revent you from doing ...
    COMMENT ON TABLE M_SCHEMA.DNR_ASSIST IS '
    Domain Name Registration Assistance';

  • How to increase the length of message in status bar

    Hi all,
    I need to show an error message in the status bar of the ABAP editor when an error occurs in the program. But the error message is not fully getting displayed, it is getting truncated. Is there any way to increase the length of the message in the status bar.

    You can display upto 73 charcters ,if you need more than this then create one text element .
    here you can have 132 charcters.
    parameters p_matnr like mara-matnr.
    start-of-selection.
    message s999(z01) with text-005.
    Create message class with & & & & & & ( Message short text ).
    This way you can show maximum 132 charcters.
    Thanks
    Seshu

Maybe you are looking for

  • Z10 won't display text messages, can't receive

    I performed a security wipe yesterday because my contacts were a complete mess, numbers were associated incorrectly, and I have no idea how that occured. After the security wipe, and when I highlight and click text messages, the Blackberry hub only d

  • Cant create iCloud photo album in Yosemite

    I have imported some photos in iPhoto. I tried to create an iCloud album but it won't let me.  Is this a bug in Yosemite?

  • Installation problems with Lotus Symphony

    Intallation fails with no error reason.  I had Lotus Symphony working on my older iMac.  The software did not work after system migration to the new machine. Attempts to re-install have failed.

  • BLOB - Internal or External?

    Hey guys - I was curious if anyone could tell me when to use BFILE vs. internal storage. I will be storing microsoft word documents in my BLOB column (size could eclipse 2MB, but probably no more). Is it necessary to store these documents externally

  • Blue screen after update

    I recently updated my iPad (4th gen)  and when it was time to install the screen went blue and then shut down. I've tried to restart it by holding the lock and home button and connecting it to my laptop but nothing has worked.