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

Similar Messages

  • Error when connecting(DBCO) from R/3 database to external database (mssql)

    Hello,
    We are having issue while connecting from SAP R/3 quality server to
    external SQL (development) Database(Radar server).
    We have created the Database connection (RADAR_DEV) in both development
    and quality r/3 server. Both of these servers connect to one target
    machine which is no -sap mssql (radar development) server for fetching
    the data.The program (Ztest) uses native sql statement and the
    dbconnection name RADAR_DEV to connect to Non-sap mssql server.
    The same program works in development environemnt but it is not working
    in quality thougth the DB connection and program is same.
    Getting the below short dump in quality server
    Runtime Error          DBIF_DSQL2_OBJ_UNKNOWN                            
    Exception              CX_SY_NATIVE_SQL_ERROR                            
           Occurred on     03.03.2008 at   16:54:17                                                                               
    Information on where terminated                                                                               
    The termination occurred in the ABAP program "ZRADAR_EXTRACT" in               
    "START-OF-SELECTION".                                                         
    The main program was "ZRADAR_EXTRACT ".                                                                               
    The termination occurred in line 57 of the source code of the (Include)        
    program "ZRADAR_EXTRACT"                                                      
    of the source code of program "ZRADAR_EXTRACT" (when calling the editor 570).                                                                               
    Source code extract

    Hi Jun,
    Drop the table RFCKEYSS. To do this, logon to the original system, run the database utility (transaction se14) and use the button 'Delete database table'.
    After that, repeat the phase PARDIST_SHD.
    With SUM 1.0 SP 7 and higher, the table is dropped directly before phase PARDIST_SHD. If the error appears again, manual action is necessary.
    This is what the notes says to do.
    Have you tried this ?
    Regards,

  • How to use LSMW to upload database table directly from flat file extract

    Hi Guru's,
    I am new to LSMW tool. I have searched the fourm before posting this thread for my issue but i didn't find any good posts for the same.
    my requirement is : I will have a flat ( tab -delimited ) or Excel file with number of records downloaded using the databrowser for some of standard tables from one SAP systesm  . I wanted to upload the records using the LSMW  to the same tables  in some other SAP systesm . Please help me to How to upload the same using the LSMW.
    Thanks & Regards,
    Praveen.

    Hi Praveen,
    There is a risk trying to migrate data directly into standard tables because this can generate database inconsistences or wrong inserted data according to what is customized in the target system. I do not recommend migrate like this. 
    With LSMW you use objects like direct input programs, idocs, bapis and recorded batch input. Try to create a project and use an standard object for your data. Also, check in SXDA transaction (Goto-->DX programs) if there is a standard program for your data.
    Anyway, if you want to upload data directly to tables, read below thread:
    ["UPLOAD  CSV  FILE";
    [how to upload .csv file into a custom table;
    Regards,
    Roger

  • How to retrieve deleted entries of a database table

    Hi,
    I accedentally deleted database table from se14.
    how to retreive the table of entries.
    regards ,
    Rajesh

    you did not assigned any point to any one i guess... its not how we thanks to an answer on sdn community. (whether it had helped u solve ur problem or a concrete answer with not possible)
    But i am pretty much sure you can restore from ur latest backup and you could get your table along with data. in case u are not still gatting it. then probably you need to restore DB strcuture first (i know in AIX OS you can make a copy of DB structure using MKSYS command ) which will create structure of database and then you can restore the same backup which we are talking about using restore procedure.
    Mandeep

  • Database conversion on very lg tables when extending lenght of InfoObject

    Hello Gurus,
    We need to extend the lenght of an InfoObject which is contained in a number of DSOs. These DSOs are very large (altogether about 1billion records). When we transport the change to the InfoObject SAP forces us to run a database conversion (in SE14) on all the underlying tables of the DSOs (Change Log and Active Tables) which contain the InfoObject we're changing. However, this is taking a very long time as SAP is doing a large number of SQL SELECT statements etc on the data in these tablese. However, the InfoObject doesn't have an ALPHA conversion on it and all we want is to change the DDIC definition - we do not want SAP to start copying data, renaming tables, selecting data etc. Has anyone else come across this and does anyone know if there's a way to do this without having to do the database conversion in this way - i.e. where it doesn't access the data.....?
    Thanks in advance,
    Joachim

    This is going to seem a plum of a question in this forum, but i've had to register to gain access relating to the problem i have... Well, not exactly a problem but an unneccessary addition !
    I had to format my hard drive and had to install XP Pro Service pack 1A instead of the original service pack 1. Java plugin has been removed from the service pack, and because i needed to access web pages containing java code, i downloaded the java plugin... I thought !
    I now have a program called Java web start, which opens with options for notepad, Draw 4, Military Game and swingset 2...
    I want to un-install the program, and install only the plug in - so could someone plant me a Hyperlink to somewhere i can download ONLY the plug-in, and not the actual program...
    I've looked at some of the demo's... but haven't even grasped the concept of what the program is actually for... so there isn't much chance of me using it for the purpose it was intended, because as i've said, i haven't got a clue what it's all about !

  • Inconsistencies on pool tables when import patches

    Hello Experts.
    I installed the enhacements packages of EA-PS and SAP_APPL (version 603) on my system SAP ECC 6.0 Unicode 64 bits. This process terminated correctly.
    Then, when i'm importing another patch of SAP_BASIS or another component with the spam, the system return me the following error in the check_requirements phase:
    " 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
    Pools/Clusters    GLSP
                             GLTP"
    In the se14, for both, there is not inconsistencies on the database objects but on the runtime objects, the
    length of the vardata field is a half of the value of this field of the runtime object.
    For correct this inconsistencies, i execute the reports RADPOCNV (ABAP Dictionary: Table Pool Conversion) and RATPONTC (Adaption of VARDATA field for table pools).
    Now this tables are totally consistent but when i import again the SAP_BASIS patch or another patch, the inconsistence error still appears.
    ¿How could i resolve this inconsistencies?
    Thanks in advance.

    http://ora-24006.ora-code.com/

  • ACS 5.3 Authorization problem with using Identity Groups in Access Policy Rule

    Hello guys, I am found a problem which I can't solve regarding authorization with using Identity Groups in Access Policy rule.
    ACS version: 5.3.0.40.6 (internal build B.839)
    I have very simple RADIUS Authorization rule which authorize user on behalf of right Identity Group.
    Requested Identity Group exist
    Testing user is created in Internal Users and has assigned requested Identity Group
    Radius Access Policy: 
    Authentication against Identity Store Sequence, where authorization server is external RSA SecurID device and additional attributes retrieval is configured from Internal Users.
    Authorization is very simple – One Rule with only one Condition which is: Identity Group - in - Requested_Testing_Rule. Then Default rule is set to Deny.
    When I will try login with my testing user then authentication against RSA SecurID is OK, but authorization will be denied by Default rule – It looks like my Rule with Identity Group is totally omitted.
    I am managing several other ACS servers (version 5.3 but with older patches) where similar rules are working without problem.
    What I am tested:
    Remove testing user and create his account again.
    Rename Identity Group
    Use another Identity Group
    Remove Access Policy rule and create it again
    Use Compound Condition: System:Identity Group
    Use Compound Condition: System:UserID instead of Identity Group in Rule (it is working without problem)
    Do you have any idea where problem can be?

    OK guys, it started working yesterday without any configuration change. Maybe it was some database inconsistence wich was solved by ACS itself.

  • How to delete the short dump list in st22

    Hi all,
              i want to clear the runtime error list in ST22.
    How to clear the list of short dump in ST22.
    is there any T.code kindly suggest
    thanks in advance
    Sundar.c

    Dear Sundar,
    By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
    Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
    The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
    1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
    ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
    2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
    3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
    4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
    Hope this information resolves your error and also more useful in the feature.
    Thanks
    Kishore

  • 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.

  • Error while updating patch

    Hi All,
    I'm updating the patch SAPKE60009 and i'm getting this error and i checked the two objects. They are in consistent state only. But still getting the same error.
    Please suggest me.
    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       PPOIX ~ 002
                       PPOPX ~ 002
    Regards,
    Ganesh.

    hello Ganesh,
    Try to adjust and activate the table using SE14 in sap for which your getting error.
    As well as you can go in SE14 and cleick on "DB request" and select "terminated" and "created with import"
    links and check whethere any inconsistencies you see.
    If yes delete them and try to re-import the support package again

  • SAINT Error in Phase CHECK_REQUIREMENTS

    Hi.Experts,
    In a new SAP component installation with "t-cd:SAINT", an error occurred.
    ERROR MESSAGE
    =============================================
    Phase CHECK_REQUIREMENTS: Explanation of Errors
    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.
    =============================================
    I have already checked 4 things of below
    1.SE14－－＞BSEG
    I can see the message below  on the screen.
    Request:"Adjust"　Error in step2 -see object log and analysis
    2.SPAU
    The contents related to BSEG are already modified (Green)
    3.SPDD
    The contents related to BSEG are already modified (Green)
    4.SE10
    There is no modifiable request related BSEG.
    Could someone tell me about how to deal this error?
    Best Regards,
    Naomi

    Hi Naomi
    Could you check this SAP Note about your issue
    1839881 - SPAM/SAINT error during CHECK_REQUIREMENTS regarding open conversion request still existing
    BR
    SS

  • Upgrade to ECC6.0 problem

    Hi all,
    Currently, I'm upgrading R/3 4.7 ext 2.00 to ECC 6.0.
    In the Final Step before complete the SAPup needed me
    to revise this
    UPGRADEPHASE XPRAS_UPG
    1PEPU203X> Messages extracted from log file "SAPR700ZE1.UG1" <
      Long text:
        Cause
          During the upgrade, a message relevant for postprocessing was written
          to a log file. This message is not dealt with until the end of the
          entire upgrade. The upgrade continues.
        System Response
          The upgrade stops in phase CHK_POSTUP. To create the reference to the
          original log file, this message is generated by R3up.
        What to do
          Note the messages following this message and proceed according to the
          instructions.
    A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
    UPGRADEPHASE JOB_RDDNTPUR
    1PEPU203X> Messages extracted from log file "RDDNTPUR.UG1" <
      Long text: see above
    3PETG447 Table and runtime object "RFIDPTFCATAG" exist without DDIC reference ("Transp. table")
      Long text:
        Cause
          A runtime object was found for a table which is unknown in the ABAP
          Dictionary. The table contains data, which is why, as a precaution, the
          runtime object was not deleted.
          Since there is a runtime object, this means the table was once created
          in the ABAP Dictionary. The fact that the table can no longer be found
          in the ABAP Dictionary could be due to the following reasons:
          It is a customer-specific table which was created when the correction
          system was switched off.
          Depending on the history of your system, there may also be SAP tables
          which were not deleted completely, or for which only the runtime object
          was delivered without the related definition in the ABAP Dictionary.
        System Response
        What to do
          RESET N1
          Customer-specific tables
          If it is a customer-specific table, and you still need the data, try to
          restore the table in the ABAP Dictionary. Note the specified table type
          when you do this (transparent table, pool table, and so on).
          The table may still, for example, be contained in the version database.
          You can access version management through the menu "Utilities" in the
          in the ABAP Dictionary (transaction SE11). You may also still have a
          copy of the system that still contains the table definition. You can
          also display the runtime object and create the table according to the
          field names, types and lengths specified in the definition. You can
          display the runtime object in the menu "Extras" of the database utility
          (transaction SE14).
          Tables in the SAP namespace
          Search for notes on these tables in OSS using the key words RDDNTPUR
          and TG447.
    3PETG447 Table and runtime object "RFIDPTFIELDAG" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "RFIDPTPOSTAG" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "RFIDPTPOSTAG_T" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "RFIDPTPRENTCLC" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "RFIDPTPRENTVAL" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "RFIDPTPRPERTYP" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "T811MESS" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TFARSIMONTH" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TISLMONTH" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TIVBE44" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TIVBECTYP" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TIVBECTYPT" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TIVBEKOFI" exist without DDIC reference ("Transp. table")
      Long text: see above
    3PETG447 Table and runtime object "TIVBEOBJ" exist without DDIC reference ("Transp. table")
      Long text: see above
    Any help would be appreciate.
    Rapheephan

    Dear Rapheephan
    I search AGS Global message as same as your problem.
    this is rely from AGS.
    but there is still no confirmation to solve this problem by this rely
    Please re-review SAP Note 69455 specifically section 3. Upgrade behavior
    and section 4. Combination with Add-ons for resolution.
    This section explains your error messages and how it can be remedied
    post upgrade. As stated in the note:
    3.  Upgrade behaviour
    During system upgrade the addon ST-A/PI gets lost just like standard
    coding ("passive deletion"). No restrictions on upgrade target
    releases or similar. Choose "Passive deletion" whenever the upgrade
    asks you about ST-A/PI. You do not need the files of ST-A/PI for the
    target release during the upgrade. You do not need to update an old
    ST-A/PI prior to an upgrade.
    4.  Combination with other add-ons
    After upgrade you may find messages like 'Table /SSF/.. exists
    without DDIC reference' concerning service tool tables in the
    CHK_POSTUP phase or in DB02. These are harmless and most easily
    solved by implementing ST-A/PI on the new release. Then run report
    RTCCTOOL and follow the recommendation 'Procedure after upgrade'
    (takes 2 clicks from inside the tool).
    Combination with other add-ons
    All combinations of ST-A/PI with all other addons are released. No
    conflicts with any other support package or addon.
    To prevent any possibility of conflicts or interference with
    productive transactions, ST-A/PI objects are in independent separate
    namespaces /SSF/+/SSA/ (transaction codes ST12-ST14 and report
    source RTCCTOOL are the only exception to this rule).
    Best Regards
    JangHyun.

  • Error in upgrade from 4.6 to ecc 6.0

    Hi all,
    We are upgrading from SAP 4.6 c to ecc 6.0 anr we are getting the following messages
    UPGRADEPHASE XPRAS_UPG
    1PEPU203X> Messages extracted from log file "SAPR700WG4.ORD" < Long text:
    Cause
    During the upgrade, a message relevant for postprocessing was writte to a log file. This message is not dealt with until the end of the entire upgrade. The upgrade continues.
    System Response
    The upgrade stops in phase CHK_POSTUP. To create the reference to the original log file, this message is generated by R3up.
    What to do
    Note the messages following this message and proceed according to the instructions.
    A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_CONFIRM" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_UPDATE" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZWORKORDER_UPDATE" must still be migrated
    1PEPU203X> Messages extracted from log file "SAPR700ZG1.ORD" < Long text: see above
    A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
    UPGRADEPHASE JOB_RDDNTPUR
    1PEPU203X> Messages extracted from log file "RDDNTPUR.ORD" < Long text: see above
    3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
    Long text:
    Cause
    A runtime object was found for a table which is unknown in the ABAP Dictionary. The table contains data, which is why, as a precaution, the runtime object was not deleted. Since there is a runtime object, this means the table was once create in the ABAP Dictionary. The fact that the table can no longer be found in the ABAP Dictionary could be due to the following reasons:
    It is a customer-specific table which was created when the correction system was switched off.
    Depending on the history of your system, there may also be SAP tables which were not deleted completely, or for which only the runtime object was delivered without the related definition in the ABAP Dictionary
    System Response
    What to do
    RESET N1
    Customer-specific tables
    If it is a customer-specific table, and you still need the data, try to restore the table in the ABAP    Dictionary.
    Note the specified table type
    when you do this (transparent table, pool table, and so on). The table may still, for example, be contained in the version database.
    You can access version management through the menu "Utilities" in the  in the ABAP Dictionary (transaction SE11).
    You may also still have a copy of the system that still contains the table definition. You can also display the runtime object and create the table according to the field names, types and lengths specified in the definition. You can display the runtime object in the menu "Extras" of the database utility (transaction SE14).
    Tables in the SAP namespace
    Search for notes on these tables in OSS using the key words RDDNTPUR and TG447.
    3PETG447 Table and runtime object "STGLTRAN" exist without DDIC reference ("Transp. table")
    Long text: see above
    3PETG447 Table and runtime object "STSLEVNTSV" exist without DDIC reference ("Transp. table")
    Long text: see above
    3PETG447 Table and runtime object "STSLTOBJSV" exist without DDIC reference ("Transp. table")
    Long text: see above
    3PETG447 Table and runtime object "STSLTRANSV" exist without DDIC reference ("Transp. table")
    Long text: see above
    3PETG447 Table and runtime object "TIBAN_ACTIVE" exist without DDIC reference ("Transp. table")
    Long text: see above
    3PETG447 Table and runtime object "ZPH_RESS_STATUS" exist without DDIC reference ("Transp. table")
    Long text: see above
    Please suggest what to be done in these cases.
    Thanks

    Hi,
    I think you have some BADIs or other enhancements donne in 4.6, whn tried to migrate to 6.0 causes this. Pls check whether all these objects are available/changed in 6.0.
    Regards.
    Renjith Michael.

  • 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

Maybe you are looking for