Change length of Info object

Hello,
I have an infoobject with NUMC as data type and length 3. I need to change the length to 4 and keep the data type same. This infoobject is included in 6 or more ODS and cubes and is also a navigational attribute of another info object.
The infoobject already has MD loaded in it via a flat file. it can also be loaded directly through R/3, but the team has decided not to pursue that option.
My question is: Can I change the length to 4 without emptying the cubes and ODS? If so, how will it affect my MD? Is there any way to change the transactional data in the cube to 4 digits..by padding it with zero?
The only option that I see in front of me is to delete all the data in the infoobject. pad the data in the flat file so that it is 4 digits instead of 3 (I think I should be fine even if i don't do this). Delete all the ODS and cubes that contain this info object. Also delete all the data in the other info object that has this info object as a navigational attribute. Reload all the ODS and cubes and info object after the changes have been done.
Any other suggestions?
Thanks
Sam

Thanks Arun,
I reopened the post because the Q about the transport was related to the same post. I did not want to have 2 threads open for the same thing.
It does seem that when I transported it to BWQ, the tranfer structure was activated, but the infoobject has not been activated and gives me an error. It states that the tables need to be converted. So i guess I have to make the changes manually in QA.
Thanks
Sam

Similar Messages

Tracking the changes to a Info-object or info-cube.

Hi Gurus,
I want to track a Info-object changes.Put it this way.
When the info-object is been created the length is 10 chars,But then its changed to 20 and then 40 .i don't these changes are until somebody told me.how do i track the changes to length or any other properties of the info-object ?
What about info-cube?Is there any way to track the changes done with respect to time on a info-cube?

hi Nrupal,
if the log not deleted, you can try
RSD1 - your infoobject - click icon 'logs' (blue !),
choose 'activating in dictionary', try as well saving/activating, give date range
for mass check last change, can use table RSDIOBJ
for infocube try RSDCUBE, logs, choose 'mass activator', try also 'save/activate'
to display last change, infocube right click 'display',
menu extras - info - content/change
or SE16 table RSDCUBE
the log can be accessed in infoobject or infocube maintainance also,
or try SLG1
hope this helps.

To change Sequence of info-Objects in Filter dispaly for a 7.0 report

Hi
I have a 7.0 Bex Query.
When I run the report .Click on 'Filter' , I get all the available info Objects for drill down in alphabetic Order .
I know that we can change the Order through 'Query Properties' and tab 'Navigational state'. But it is for that temporary view.
Is there any way to fix the Order/ sequence parmanantly? I dont want to fix it every time I open the report.
Thanks for your inputs.
Nandita..

Hi,
I am assuming you are talking about the order of free characteristics.
By default when you execute the report, they are arranged in an alphabetical order evn though you have arranged them in some other order in the query designer. In 7.0, this can be fixed in WAD.
Go to WAD 7.0 (release 2004s), open the web template created on your query. Then after you open, on the left you can see web items.Under that select 'Navigation Pane' and drag it to layout. Once you bring it in layout, then on the left side under Web item properties look for 'Internal display'.
In 'Internal display' look for in the field navifation pane content select free charcteristics. Then just uncheck the check box named 'Alphabetical Sorting of'. By default it will be On, you just make it Off.
Hope this helps.
Thanks,
rahul

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

Issue with Info Object Transport after changing Data Type

Hi Experts,
We have a DSO which is running past 5 years. And recently(3 days back) we added new fields into that DSO. Delta loaded for last three days and new info object (Say XXX) data populated into DSO.
Now the problem is, We identified that, info object data type is not correct. We used data type NUMC instead of CHAR.So Character information is missing for that field.
Example:
Data from ECC: ABC123
Data Loaded to DSO: 123 (Missed character ABC)
So we deleted data from DSO and changed the info object data type in Development system.
And also I have deleted only last three days delta records from DSO and transported my info object to Production. But its giving error as: Info object contains data in DSO".
But that info object field is empty in DSO. I have already deleted last three days delta.
Do I need to Delete all 5 years data from DSO to change the data type of recently added new info object ?
Please give me your solutions and ideas to solve this issue.
Thank you,
Best Regards,
Santhosh

Hi Raman,
Thank you for your answer.
When I changed the data type of info object in Dev, I deleted the content of DSO. And same thing transported to QA as well. Before importing changed info object, I just deleted the content of DSO from QA. So transport done successfully QA.
But in Production we have a history of past 5 years. So I cant delete all contents of DSO.
So just deleted only the delta request's which contains data for that info object(3 days back, we moved that info object(NUMC data type) to production,So last 3 days delta only loaded for that info object). And tried to transport it. But it was failed. I am sure we need to drop all data from DSO, if I am interested to go with same info object.
I have some comments on your first approach,
1. If we delete info objects from Dev DSO and transport to Production will give transport failure, Why because, my previous transports errors clearly saying that info object contains data in DSO . So it wont allow to remove that info object from DSO.
2.We are using same info object technical name in BO Data federator also. So if we change add new info objects again we need to make changes with BO as well. I am thinking this point as my last option if i cant find any other solution.
Thank you.
Best Regards.

Info Object lengths Desperately needed.

Dear Gurus,
Please dont think this question as a simple question. I desperately need your inputs.
What are the lengths of info objects according to SAP name space and Customer name spaces. I can see some Info objects starting with 0 having as long as 11 characters. And when i try to create one i am able to give only 9 characters. And when I searched in RSD1 for object lengths there i can see some as long as 14 characters eg: /BA1/C35DATDOC
Please tell me clearly what is the maximum length an info object can have.   I tried to read the documentation from the following link. but I am not able to understand things clearly.
http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?_CLASS=IWB_EXTHLP&TMP_IWB_TASK=DISPLAY&_LOIO=53EC2C37B995184890C6D8BA5B668A86&_SLOIO=E3E60138FEDE083DE10000009B38F8CF&RELEASE=700&LANGUAGE=EN&_SEQNUM=14&_SCLASS=IWB_STRUCT
Kindly help me
Regards
Mohan
Message was edited by:
        mohan kumar

Hi Mohan,
SAP-delivery (Business Content) namespace:
·        Objects beginning with 0
·        Generated objects in the DDIC beginning with /BI0/
Customer namespace:
·        Objects beginning with A-Z
·        Generated objects in the DDIC beginning with /BIC/
Partner-specific namespace and customer-specific namespace:
·        Object begins with /XYZ/ (example)
Special SAP namespaces for generated objects:
·        The prefixes 1, 2, 3, 4, 6, 7, 8 are required in BW for DataSources and InfoSources in special SAP applications.
·        The prefix 9A is required for the SAP APO application.
When you create your own objects, therefore, give them technical names that start with a letter.
The maximum permitted length for a name varies from object to object. Typically, 9 to 11 letters can be used.

Upgrade to SCM7.0 DP info objects (Characteristics) long/short text issue

Hi All,
We have upgraded from SCM4x to SCM7.0. The info objects characteristics customized long and short text is not updated in SCM 7.0.
Example: Info object 9ALOCNO standard long/short text is APO location. But in SCM4x they have changed to Plant. After upgrade this text is set to APO location, not the plant. Like this many chars text have been changed to SAP standard.
When I try to change text of info object creates transport request.
Is this standard behavour when we upgrade?
Please share your thoughts and let me know for more information.
Thanks,
Sreeni

Sreeni,
With every upgrade the customization is lost. We will have to make a list of all customized objects and make the change again in the upgraded system.
Hope this helps.
Thanks
Mani

Exception aggregation for info object

Hi all,
I have problem using exception aggregation for info object (zabarb) :
The data :
wbs element      zabarb
        1                    100
        1                    100
In query i want to show the data wbs element: 1; zarbarb:100
But in fact i got in query wbs element 1; zabarb :200
I've tried to change info object exception aggregation : average all value with reference char. wbs_element, but still the result in query is 200.
I hope someone can help me.
Thanks.

Hi,
Make these Changes to the Info Object
Aggregation--MAximum
Exception Agg-Summation
Agg Ref Char- wbs_element
Thry this..........
Rgds
SVU

Info Object: Change of Data Type (NUMC to CHAR)

We have a scenario wherein one of the Info objects is defined currently as NUMC. Due to the change in the Source system, the info object is now defined with data type as CHAR. The info object in consideration is the "Cost element".
As the current info object contains data, it will not be possible to change the data type from NUM to CHAR.
Is there any pre-defined way of doing this data type change without loss of data (in the info object as well as the info cube(s) where the info object is used)?
Regards
Bala

Hi Balakrishana,
Try this:
Insted of changing the definition of infoobject(NUMC to CHAR), why cant you change the data itself from CHAR to NUMC...?? If length is same.
You can write a simple routine in transfer rules and you can convert.
Hope it Helps
Srini

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 reduce the length of the info object that's being used?

Hi All,
I have created info objects and used them in a DSO. Now I want to reduce the length of the info objects but i'm unable to do it. When I reduced the length and tried activating the Info object, it's giving me error and the info object is not getting activated. Please guide me how I can reduce the length and activate the Info Object.
Thanks
Hima Bindu

Reducing the length of an infoobject is not that easy
Cleanest way -
Drop all transaction data for that infoobject
Drop all data in the DSO and cubes.
Reduce the length and then activate and transport all the infoobject and there dependence objects.

Loss Authorization after changing info object

Hi
tHIS is authorization issue
I have DP Planning book and in this planning book I have used Zinfoobject .
This is working fine since go live . Recently I have added new atribute in this zinfoobject .
After that user is not accessible to DP pLANNING Area.
SAYS THAT 'NO Authorization.
Can anybody suggest me

Hi,
Is this Info Object is Std. one?
I assume this info object is created by manually.If you want to change the data type of info object then you need to delete master data of this info object.After that you can change the data type of info object.
But this is the vrey risky steps,so i would suggest try it ones in dev. or sand box server,then go further.
Regards
Sujay

Change Info Object Master/Text data in PROD to Time dependant

Hello Experts,
I have an Info Object used in ODS and Cube. Both ODS and Cube has data in it. The Info Object has Text data.
I need to change Info Object Text data as Time dependant.
What are best way to make this change? If I make change to Info Object, how it's going to effect Cube and ODS.
Please advise.
Thanks
Padma
Padma Reddy

Bhanu,
Yes I am selectiong the check box to make IO as time dependant.
May be I am over complicationg this. Here is my understanding, correct me if I am wrong.
The IO is used in cube. It belongs to Dimension1. This dimension table is nothing but dim id's and SID's. So the Dimension table is built based on the exist SID values.
When I make change to IO, the data and SID's will change. Doesn't it cause some data inconsistancy ? And also the IO text table will have multiple rows with the same data but with different validity periods.
As I said I may be thinking too foolish or technical.
Please advise.
Thanks
Padma

What happens to data, when Info object property is changed to have ALPHA

Hi experts,
I have a trivial question,
What happens to existing data, when I change the info Object property to have an ALPHA convesion routine ? Specifically I need to know, will it remove any similar looking entries ??
thanks in advance
D Bret

Check this:
Re: Alpha conversion for an existing infoobjects
Re: ALPHA conversion routine - how to change an existing InfoObject
Alpha conversion
TCODE: RSMDCNVEXIT in BW and What is Alpha Conversion?
Hope it helps..

BW Info Object update problem

Hi All,
We are implementing BW. The Vendor and Document date info objects are not mapped directly to SAP R/3. Hence the data is not updating directly fromR/3 for these info objects. So I have written a small transfer routine to update the info object. But it is not getting updated with this routine. I am not sure where the problem is. Any ideas why?
The following is the code of transfer routine. There are two infosources: communicaoin structure and Transfer structure. I wrote the routine in transfer structure. This routine is written for the info object Vendor.
PROGRAM CONVERSION_ROUTINE.
Type pools used by conversion program
TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
Declaration of transfer structure (selected fields only)
TYPES: BEGIN OF TRANSFER_STRUCTURE ,
InfoObject SL_ACTIV: CHAR - 000004
ACTIV(000004) TYPE C,
InfoObject SL_AWORG: CHAR - 000010
AWORG(000010) TYPE C,
InfoObject SL_AWTYP: CHAR - 000005
AWTYP(000005) TYPE C,
InfoObject 0ACDOC_NO_F: CHAR - 000010
BELNR(000010) TYPE C,
InfoObject 0PSTNG_DATE: DATS - 000008
BUDAT(000008) TYPE D,
InfoObject 0ITEM_NUM: NUMC - 000003
BUZEI(000003) TYPE N,
InfoObject 0CHRT_ACCTS: CHAR - 000004
CHARTACCTS(000004) TYPE C,
InfoObject 0CREATEDON: DATS - 000008
CPUDT(000008) TYPE D,
InfoObject SL_CPUTM: TIMS - 000006
CPUTM(000006) TYPE T,
InfoObject 0CREDIT: CURR - 000017
CREDIT(000009) TYPE P,
InfoObject 0CURRENCY: CUKY - 000005
CURRUNIT(000005) TYPE C,
InfoObject 0CURTYPE: CHAR - 000002
CURTYPE(000002) TYPE C,
InfoObject 0DEBIT: CURR - 000017
DEBIT(000009) TYPE P,
InfoObject SL_DOCCT: CHAR - 000001
DOCCT(000001) TYPE C,
InfoObject SL_DOCLN: CHAR - 000006
DOCLN(000006) TYPE C,
InfoObject SL_DOCNR: CHAR - 000010
DOCNR(000010) TYPE C,
InfoObject SL_DOCTY: CHAR - 000002
DOCTY(000002) TYPE C,
InfoObject 0FISCPER: NUMC - 000007
FISCPER(000007) TYPE N,
InfoObject 0FISCVARNT: CHAR - 000002
FISCVAR(000002) TYPE C,
InfoObject SL_LINET: CHAR - 000005
LINETYPE(000005) TYPE C,
InfoObject SL_LOGSYS: CHAR - 000010
LOGSYS(000010) TYPE C,
InfoObject SL_POPER: NUMC - 000003
POPER(000003) TYPE N,
InfoObject 0QUANTITY: QUAN - 000015
QUANTITY(000008) TYPE P,
InfoObject 0UNIT: UNIT - 000003
QUANUNIT(000003) TYPE C,
InfoObject 0GL_ACCOUNT: CHAR - 000010
RACCT(000010) TYPE C,
InfoObject 0COMP_CODE: CHAR - 000004
RBUKRS(000004) TYPE C,
InfoObject 0COSTCENTER: CHAR - 000010
RCNTR(000010) TYPE C,
InfoObject SL_REFACT: CHAR - 000004
REFACTIV(000004) TYPE C,
InfoObject SL_RFDCCT: CHAR - 000001
REFDOCCT(000001) TYPE C,
InfoObject SL_RFDCLN: NUMC - 000006
REFDOCLN(000006) TYPE N,
InfoObject SL_RFDCNR: CHAR - 000010
    REFDOCNR(000010) TYPE C,
InfoObject SL_REFRYR: NUMC - 000004
REFRYEAR(000004) TYPE N,
InfoObject SPL_CUR1: CUKY - 000005
RTCUR(000005) TYPE C,
InfoObject 0VERSION: CHAR - 000003
RVERS(000003) TYPE C,
InfoObject SPL_CUR2: CUKY - 000005
RWCUR(000005) TYPE C,
InfoObject 0FISCYEAR: NUMC - 000004
RYEAR(000004) TYPE N,
InfoObject 0CO_AREA: CHAR - 000004
RZZKOKRS(000004) TYPE C,
InfoObject 0PROFIT_CTR: CHAR - 000010
RZZPRCTR(000010) TYPE C,
InfoObject 0PACCOUNT: CHAR - 000010
SACCT(000010) TYPE C,
InfoObject 0PCOMP_CODE: CHAR - 000004
SBUKRS(000004) TYPE C,
InfoObject 0PART_CCTR: CHAR - 000010
SCNTR(000010) TYPE C,
InfoObject 0POSTXT: CHAR - 000050
SGTXT(000050) TYPE C,
InfoObject SL_PPRCTR: CHAR - 000010
SZZPRCTR(000010) TYPE C,
InfoObject SL_TMSTMP: DEC - 000015
TIMESTAMP(000008) TYPE P,
InfoObject 0SALES: CURR - 000017
TURNOVER(000009) TYPE P,
InfoObject 0RECORDMODE: CHAR - 000001
UPMOD(000001) TYPE C,
InfoObject 0USER_NAME: CHAR - 000012
USNAM(000012) TYPE C,
InfoObject 0VTYPE: NUMC - 000003
VALUETYPE(000003) TYPE N,
InfoObject 0VALUATION: NUMC - 000001
VALUTYP(000001) TYPE N,
InfoObject SL_WSDAT: DATS - 000008
WSDAT(000008) TYPE D,
InfoObject SL_SPLTMD: CHAR - 000001
XSPLITMOD(000001) TYPE C,
InfoObject 0ASSET_MAIN: CHAR - 000012
ZZANLN1(000012) TYPE C,
InfoObject 0ASSET: CHAR - 000004
ZZANLN2(000004) TYPE C,
InfoObject 0DEBITOR: CHAR - 000010
ZZKUNNR(000010) TYPE C,
InfoObject SL_ZZLFNR: CHAR - 000010
ZZLIFNR(000010) TYPE C,
InfoObject SL_ZRPRCR: CHAR - 000010
ZZREPPRCTR(000010) TYPE C,
InfoObject SL_ZTCDE: CHAR - 000020
ZZTCODE(000020) TYPE C,
InfoObject 0REF_DOC_NO: CHAR - 000016
ZZXBLNR(000016) TYPE C,
END OF TRANSFER_STRUCTURE .
Global code used by conversion rules
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
$$ end of global - insert your declaration only before this line   -
      FORM COMPUTE_CREDITOR
Compute value of InfoObject 0CREDITOR
in communication structure /BIC/CSSPL_LINE
Technical properties:
    field name      = CREDITOR
    data element    = /BI0/OICREDITOR
    data type       = CHAR
    length          = 000010
    decimals        = 000000
    ABAP type       = C
    ABAP length     = 000010
    reference field =
Parameters:
--> RECORD_NO       Record number
--> TRAN_STRUCTURE Transfer structure
<-- RESULT          Return value of InfoObject
<-> G_T_ERRORLOG    Error log
<-- RETURNCODE      Return code (to skip one record)
<-- ABORT           Abort code (to skip whole data package)
FORM COMPUTE_CREDITOR
USING    RECORD_NO LIKE SY-TABIX
           TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
           G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BI0/OICREDITOR
           G_T_ERRORLOG TYPE rssm_t_errorlog_int
           RETURNCODE LIKE SY-SUBRC
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
$$ begin of routine - insert your code only below this line        -
DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
SELECT SINGLE CREDITOR FROM /BIC/AAPOSLVEN00
                INTO RESULT
                WHERE /BIC/SL_RFDCNR = TRAN_STRUCTURE-REFDOCNR.
   IF SY-SUBRC NE 0.
       CLEAR RESULT.
    ENDIF.
returncode <> 0 means skip this record
RETURNCODE = 0.
abort <> 0 means skip whole data package !!!
ABORT = 0.
$$ end of routine - insert your code only before this line         -
ENDFORM.
      FORM INVERT_CREDITOR
      Inversion of selection criteria for InfoObject 0CREDITOR
      This subroutine needs to be implemented only for SAP RemoteCubes
      (for better performance) and for the Report/Report Interface
      (drill through).
--> I_RT_CHAVL_CS       Ranges table for current InfoObject
--> I_THX_SELECTION_CS Selection criteria for all other InfoObjects
<-- C_T_SELECTION       Selection criteria for fields of
                          transfer structure
<-- E_EXACT             Flag: Inversion was exact
FORM INVERT_CREDITOR
USING    I_RT_CHAVL_CS      TYPE RSARC_RT_CHAVL
           I_THX_SELECTION_CS TYPE RSARC_THX_SELCS
CHANGING C_T_SELECTION      TYPE SBIWA_T_SELECT
           E_EXACT            TYPE RS_BOOL.
$$ begin of inverse routine - insert your code only below this line-
DATA:
    L_S_SELECTION LIKE LINE OF C_T_SELECTION.
An empty selection means all values
CLEAR C_T_SELECTION.
L_S_SELECTION-FIELDNM = 'REFDOCNR'.
Selection of all values may be not exact
E_EXACT = RS_C_FALSE.
$$ end of inverse routine - insert your code only before this line -
ENDFORM.
Thanks for the great help,
Sobhan.

Hi manoj,
Welcome to SDN!!
Check this blog:
/people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
Bye
Dinesh

Change length of Info object

Similar Messages

Maybe you are looking for