SE14 conversion

I was trying to convert Fact table in Se14.During Conversion it got failed in the 5 th step.
I got dump
Database error text........: "ORA-14400: inserted partition key does not map to any partition"
Currently the data is avialbale in the temprorary table.How to restore the data back to the cube.
If I do continue adjustment even though it is having errors , the data will get lost.
Please help
Regards,
Anita

Hi,
I have read this Note 885441.It suggests to execute program SMIGR_CREATE_DDL .Will it affect the data if i execute this program on temporary table
Reagrds,
Anita
Values of a partition key do not map to a partition (Oracle)
            R3load aborts during data load because values of the partitioning key do not map to any partition. This is noted in the ORA-14400 error.
Cause
            Package dimension in f-fact table is higher or equal to 'high value' of the last partition. This error occurs if data has been exported from the F fact table (i.e. cube) AFTER the <TABART>.SQL files have been created. In other words, the <TABART>.SQL file has been created, data has been loaded to the cube and then the export of F-fact table data has taken place.
Solution
           Recreate <TABART>. SQL files using program SMIGR_CREATE_DDL and restart data export.
Header Data

Similar Messages

Se14- conversion error, unlock table

Hi.
I have added a new append to MCHA. I modified this append and afterwards I went to se14 in order to adjust and activate the table.
But, I have a conversion error. Now, append structure is partially active and only temporary table for MCHA exists. I can not fix the conversion problem. Data on MCHA are not important, it is the development system and it contains few data. What happens if I select "Unloc Table" in se14?
Thanks

Hi all,
Regarding data, I lost them, but I did not mind since it is test development, and we are doing the first steps to implant MM module. So data was not revelant for us.
Archana,
Our problem was caused by a bad conversion data, in the end I unlock the table. Afterwards table mcha was at the dictionary but not in the database, and se14 only showed option "create database". We used this functionality to create it again, and it worked. It created the table, in inactive status, I fixed the append structure and activated the table. Then I went to db02 to perform consistency check, here I knew that indexes and table views were lost and I had to create them again.
On the other hand, if you want to maintain your data, I think you have several options:
- contact system team in order to restore them from backup or
- before unlocking the table, you can save temporary tables created for adjustment (tables like QCMMCHA ...) that contains data, or
- correct the conversion problem and continue adjustment (in my case I couldn't fix the problem, I tried to modify the append that caused the problem but I could not activate again)
Hope this helps you.

Dependent tables automatic conversion during transport (SE14?)

Hello all,
I have changed the length of our custom ZATLAPC1 attribute of 0MATERIAL from 2 to 3 (data type = NUMC).
When I tried to activate this attribute in the development system - it asked me to go SE14 transaction and convert /BI0/PMATERIAL and /BIC/SZATLAPC1 tables.
So that helped.
But when I transported this change to the test system - the transport failed saying structures changed at field level.
I could only open the system for changes, went to SE14 to convert tables and activate infoobject.
This solution is not really elegant to transport this change to production in order to do manual changes there.
Any one can help me if there is a better option? Is there any possibility the transport will convert dependent tables automatically?

Hi,
when activating your IObj in DEV the system has complained asking you to convert the underlying tables. You should accept this prompt; you will then be directed directly to SE14 where you manually adjust the tables. Then you would have gone back to your RSD1 screen and activate it again. The system would have prompted successively the same for each table to be converted.
If you go by yourself in SE14 (out of RSD1), the "adjustment" won't be "transported automatically".
Usually the transport does that automatically for simple changes. In your case it would have worked if ZATLAPC1 wouldn't have been an attr of your 0MATERIAL I guess; at least in my case, the transport has nearly always taken care of this conversion automatically.
hope this shed some light...
Olivier.

Error in CHECK_REQUIREMENTS phase (Open ABAP Dictionary Conversions)

Hi Gurus,
When were are trying to update SPAM/SAINT to version 7.00/0033 from 7.00/0029
we're encountering 'Open Conversions in the ABAP Dictionary' in CHECK_REQUIREMENTS phase, refraining to proceed further.
It was due to 2 indexes in a table.
When i checked(using SE14), those two indexes were not appearing in dictionary, hence we've removed them at the ORACLE level, reset the queue and tried to update again, and got the same error .
Table PAT03 - has the following
Patch - 'SAPKD70033'
Status - '?'
and the table PAT02 has 2 enties of those two indexes.
with Patch - 'OPEN_TBATG'
How to proceed further,pls provide us a solution.
Regards
Prabumanoharan

Hai,
Goto SE14 - select "Indexes" and "Activate". But you should have tried this before deleting the Indexes from the Oracle level.
or try restarting the update.
Regards,
Yoganand.V

IDES ERP 2005 / open ABAP dictionary conversion during SPAM Update

Dear all,
First of all, I'm currently busy implementing a educational enviroment for our company, we are using IDES MySAP ERP 2005 SR1 MSSQL.
At the moment we are trying to upgrade the SPAM version from version 20 to 22.
However, during the requirement checks the following error occurred :
<b>Open conversions in the data dictionary</b>
<i>Phase CHECK_REQUIREMENTS: Explanation of Errors
Some open conversion requests still exist in the ABAP Data Dictionary
for the following ABAP Dictionary objects. To avoid inconsistencies and
loss of data, you must process these conversions first.
Proceed as follows:
- Open a new session.
- Start the Database Utility (transaction SE14).
- Correct the inconsistencies for the specified objects.
- Repeat the import phase. If no more inconsistencies are found, the
import continues.
Phase CHECK_REQUIREMENTS: Open ABAP Dictionary Conversions
Object Type       Object Name
Table Index       LXE_WRK_4 ~ STA
                   SC2T327F363DFA4T ~ ESI
                   SC2T327F363DFA4T ~ KYS
</i>
It seems that the indexes mentioned above are missing or doesn't exist!!!! i've tried looking for a sap note or a solution on SDN. However, haven't found a solution at all, or I'm looking at the wrong spot.
Is there a note or can somebody provide me what's in the indexes, so i can create it in our IDES system.
Regards,
Yam-Lang Lee

Hi Kiran,
Thank you very much. I managed to create the first index.
However not the indexes on table SC2T327F363DFA4T. Can't find any information for the indexes for this table. Did found note 959811. There it state that de indexes were deleted. But still stuck in the check_requirements of the SPAM Update!
Greetings,
Yammie

Patching ST_PI, open conversions in ABAP dictionary

Hello
during a patching of ST-21 2008 the tool stops at CHECK_REQUIREMENTS phase with the screen:
open conversions in ABAP dictionary
Some open conversion requests still exist in the ABAP Dictionary for the
following ABAP Dictionary objects. To avoid inconsistencies and loss of
data, you must process these conversions first.
Proceed as follows:
- Open a new session.
- Start the Database Utility (transaction SE14).
- Correct the inconsistencies for the specified objects.
- Repeat the import phase. If no more inconsistencies are found, the
import continues.
INDEX GLPCA-Z01
Now , no index exists in dictionary and database but in the past probably it existed and was cancelled . Anyway the table GLPCA is consistent in database and like runtime object.
I've activated it again but the problem is always the same
any idea?
thanks
Nicola

- start transaction SE14
- use the menue to "DB Requests - Created with import"
Check if there are any outstanding conversions.
Markus

Open conversions in data dictionary

Dear experts,
We have been trying to install an ST-PI package in an SAP system.However,it gives a warning saying "Open conversions in data dictionary". It says - Some open conversion requests still exists for the following ABAP data dictionary objects.To avoid inconsistencies and data losses you must process these conversions first.
Further it asks us to run the transaction SE14 which points towards the table GLPCA and says Index Z1 does not exist.
What can be the cause behind this?I do not have an ABAP background.So,hoping if you could help me out.
Regards,
Minuj
Edited by: minuj sarma on Feb 22, 2008 2:12 PM

hi sagar,
Go to transaction SE14 and choose the following options in the menu
DB requests --> Terminated
Reward points if usefull,
Thanks,
Kalyan.

Database utility SE14 purpose

Hello folks,
I have read a few forums on the functionality or SE14, but and unable to understand the exact occasion on when to use this TCode.
Its been said that SE14 is automatically executed while moving the transports.
We had an issue while moving the transport to production while one of the transparent table was locked in the database.
Due to this there was an inconsistency between the SAP Application table and the Database table and the ALTER TABLE function failed.
So, my question is does SE14 adjust the DB table by using table conversion.
Regards,
[V]

Hello,
Take a look of these three links. The last one explains the conversion process done:
The Database Utility - BC - ABAP Dictionary - SAP Library
Adjusting Database Structures - BC - ABAP Dictionary - SAP Library
Conversion Process - BC - ABAP Dictionary - SAP Library
Thanks and Regards,
Mariano

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
     submit zrppt500
     using selection-set 'AUTO3'
     with res_no eq lo_rsnum
     with sreserv in preserv
     to sap-spool destination p_dest
     immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
     Start of change for ECC6
     message e398(00) with 'Could not find access sequence'
     'for condition type:'
     p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
     End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
     VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

Problem about InfoObject locked by conversion

Hi Experts:
   Now I am doing BW Upgrade Project and one task is to check all infoobjects consistency (RSUPGRCHECK).
And one infoobject 0MATERIAL is inconsistent.
1. I have used RSD1 to repair it, but it failed
2. When I tried to activate manually, but it popup with message that it is locked by conversion.
3. I tried to use SE14 to delete /BI0/PMATERIAL data, but the option for "activate and delete data" is greyed out.
   This is my situation now, any one could give me some suggestion?
   Thank you so much,
   Louis Lu

Hi,
I RSA1, click on Tab Find, type ur IO name, then down, check on the box All Object Types. It vll show u where all u used that IO, then delete them accordingly.
or
goto T-code RSDMD, type ur IO name, and delete manually.
or
Goto T-code SLG1, In object type RSDMD, in sub object type
MD_DEL, then type ur user name, then execute.,,u vll c what all data u have loaded so far, delete what is pertaining to ur IO
try to delete the content as u are unable to perform the same with SE14... and then try repairing the same.. and perform ur steps..
Thanks

Convert the Tables in se14 for cube

I have the requirement to convert the table for the cube since we have changed the Group and Legal Costs stored in BW as currencies to 6 decimal places. The two objects changed to floating point numbers . Now I am asked to covert the tables for the cube how should i go about this
first I will go to se14 and give the cube name like /BIC/FZINV_C09 Then what should i do to convert the tables or should i follow some thing else in se14 please clarify me soon. i am asked to do this as per tech document.
Conversion of all the tables used in Info cubes & ODS objects, in Development Systems
soniya

Hi Dinesh and Anil, You both are genius, but please help me what it means by changing the data for legal and group cost directly in data base should i go to se11 and type /bic/fzcobmc01 and select databasetable and now change under "field tab" the data type to floating point and length 16. and also should i change the values by going display table values do i change them manually all 100 values since dinesh pointed the right thing so here is my approach
soniya
proceed as below
1. change the key figures data type and decimal places AND CTIVATE THE KEY FIGURE
2.

Database inconsistence in SE14

Hi
I hope one of you i5 exports can provide some advise.
We changed a table in development where we changed the length of a field. On development it went fine.
On the QA system the transport as such did not produce any errors but after the import the table was inconsistent (both the database object and the runtime object).
From se14 we tried to to a "activate and adjust database" but just got an error at the end saying it was not possible du to "a pending operation". After a while we tried at again and it finished without any errors but we still have a inconsistent database object (the field is not extended in the db).
What do you recommend to do in this case? Is a "force conversion" what has to be done?
Best regards
Flemming Grand

Hi Flemming,
to me it sounds, that the needed ALTER TABLE crashed - most likely because of locks on the table and the nametab is updated now.
For that, SAP created something special called "Recreate Nametab" in SE14 for DDIC only. But, I do not know, if unexperienced people should use this tool ? At least you need to activate in SE11 after that - and you should get rid of the lock on the table first in order to not run into the same issue ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

Encounters Open Conversions when performing Application ServiceTools import

Hi,
I am trying to apply Application Servicetools for R/3 46C - 01L_R3_46C into our Production system and I encounter Open Conversions in the ABAP Dictionary. Apparently, An index exists in the database but not in ABAP Dictionary and stop me from progressing.
It advises me to proceed as follows:
Open a new session
Start the Database Utility (txn SE14)
Correct the inconsistencies for the specific objects
Repeat the import phase. If no more inconsistencies are found, the import continues
My question is:
1. Do I perform 'Activate and adjust database' in txn SE14 for this case?
2. Is there any risk or issues if I were to delete this index at the Oracle level?
This is a Production system and I am unable to simulate in other servers. Your help will be greatly appreciated.
Thanks,
Annie

Reply from SAP and I confirm the transport works successfully after performing the below steps.
"Please check table LIKP in SE14, are both Database object check and
Runtime Object check are consistent? If so this entry can be deleted by:SE14->menu DB Request/created with import->select the entry and delete.
Then continue with SAINT, let me know if there's still a problem"

Characteristic 0EMPLOYEE is blocked by conversion

Hi Gurus.
I added 2 Attributes to 0EMPLOYEE infoobject and made them navigational. Now, when I try to activate 0EMPLOYEE it times out and I get this message when I come and try to enter edit mode for 0EMPLOYEE:
Characteristic 0EMPLOYEE is blocked by conversion
Message no. R7476
Diagnosis
The conversion of master data tables from characteristic 0EMPLOYEE is not completed.
System Response
Characteristic 0EMPLOYEE can not be changed until this conversion has been successfully carried out.
Procedure
Activate characteristic 0EMPLOYEE. The block will be removed following a successful activation.

Hi Dinah,
Yes, I was able to fix this.
You need to do the following. In BW, go to tcode SE14 (ABAP Dictionary: Database Utility). Enter the table name that is causing the problem in the Obj. name field. In my case that was the SID table, e.g. /BIC/YEMPLOYEE. You can display all the infoobject tables by typing in EMPLOYEE (your InfoObject name) and F4 for lookup.
Once you type in the correct table name, click on Edit button. On another screen, click on Delete data radio button. Then do an Activate and adjust database. If that does not fix it ..also ..come back and click on Delete database table button.
Hope this helps.
Thanks

Characteristic 0TCTUSERNM is blocked by conversion

Dear All,
I am trying to activate the infoobject 0TCTUSERNM but it is giving error as below,
Characteristic 0TCTUSERNM is blocked by conversion
Message no. R7476
Diagnosis
The conversion of master data tables from characteristic 0TCTUSERNM is not completed.
System Response
Characteristic 0TCTUSERNM can not be changed until this conversion has been successfully carried out.
Procedure
Activate characteristic 0TCTUSERNM. The block will be removed following a successful activation.
When I activate the infoobject, it is giving short dump.
Does anyone have faced such issues?
I tried force conversion in SE14 and also tried to activate and adjust tables in SE14 for this infoobject. It didn't helped.
Any pointers to solve the issue will be helpful.
Regards,
Niraj

Hi,
I tried both the options suggested by you. Deleted the table from SE14 and adjust and activate. The issue did not resolved.
i tried activation in background and job was getting cancelled.
To solve the issue I went to infoobject> Extras>Remove conversion lock
it gace a warning and then activated manually.
Thanks for all the suggestions.
Regards,
Niraj

SE14 conversion

Similar Messages

Maybe you are looking for