Short dump will happen because duration time unit is wrong.

Hello,
I maintained breakdown duration time unit as "TST" which is created in CUNI. System can not convert it to "S", so system will dump when I tried to access this maintenance order. So I want to change this time unit "TST" to "S" or "h". I tried to make this change in SE16 table VIQMEL, but failed. Could anybody tell me how to make this change?
Thank you.

Dear Stephen,
have you changed all unit measurement? VIQMEL is table for notification header and you said that you cannot access maintenance order. so, i think you should check table AUFK, AFKO and also AFIH. for unit measurement in order
Rgds
Edited by: Johan Lief on Apr 27, 2010 5:49 AM

Similar Messages

  • On my itouch 4th gen, I use imessage and message many people, but sometimes when i send a message the send bar on top will go almost all the way and stop. This will happen for some time and then work later. is there anything to avoid the freezinginsending

    On my itouch 4th gen, I use imessage and message many people, but sometimes when i send a message the send bar on top will go almost all the way and stop. This will happen for some time and then work later. is there anything to avoid the freezing problem while it sends

    See:
    iOS: Troubleshooting Messages
    However, I suspect it is just a tempery network problem beyond your control

  • Short dump Error-ABAP/4 Run time Error

    Hi Expert,
    Dump:ABAP/4 Processor:MESSAGE_TYPE_X Why this error came,I would like to Investigation on Perticular error,Please Some body give me an Exact answer,so that i closed the ticket.
    Regards,
    Raju.

    Hi Suresh,
    What is the actual issue?
    When did you get this error.
    To know about this type of error, check below link...
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=dump%3aABAP%2F4Processor%3A+MESSAGE_TYPE_X&adv=false&sortby=cm_rnd_rankvalue
    Also check this:
    Note 1016317 - SP13:PC: Start type 'Date & time' gets scheduled wrong
    "Process chain scheduling results in dump- ABAP/4 processor: MESSAGE_TYPE_X"
    Solution:
    In the short dump analysis, the process fails at function module
    RSS2_PSA_NEW_OLD_DS
    call function 'RSDS_DATASOURCE_SINGLE_GET'
    Regards,
    KK.

  • Changing Critical Duration time unit

    Hi,
    The Warehouse monitor in LL01 executes well with job run daily.
    Now the user's request is to change the critical duration time from Day to Hrs .
    Will there be any impact on changing the duration time?
    Regards,
    Vengat

    Nope. There are no issues in doing that.

  • What will happen when the time come?

    I have upgrade eligibility so when the time come iphone will be available on the list of phones that I'm eligible for upgrade? Is the iphone just gonna appear on the list of phones to purchase on the website?

    Login into MY Verizon....go to your upgrade line, and you will see i buy iphone button... 

  • Getting short dumps while reading bulky data from excel sheet

    Hi all,
    We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
    SQL 2000) into a unicode based system recently. We are facing two peculiar
    problems for last few days.
    *Problem 1 - *Whenever we want to upload the data from excel sheet, the
    system throws a dump after reading about 400 entries, while last week the
    same system used to read about 8000 entries in a single go.
    *Problem 2 - *Also, whenever we realease a transport requst from development
    containing a lot of changes, the request will reach the quality system but
    without the changes. but if i ll try to import the changes into quality
    system after generating more than one request containing small small
    changes, they get reflected in QAS immediately. Is there any size
    constraint in transporting a request fro DEV->QAS->PRD.
    Please suggest some ways.
    I am pasting the dump (that I am getting while data uploading from Excel).
    ~~~~~~~~~~~~~~~~~~
    Runtime errors
    MESSAGE_TYPE_X*
    Occurred on
    22.02.2008 at
    13:21:02*
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    Short text of error message:
    Control Framework : Error processing control
    Technical information about the message:
    Diagnosis
    An error occurred when the system tried to process the commands
    from the Automation Queue on the presentation server.
    There are several possible reasons for this:
    - The installation of the SAP GUI on the presentation server is
    faulty or obsolete.
    - There is an error in the application program
    - There is an error in the SAPGUI or an integrated control
    Procedure
    1. Make sure that you have imported the appropriate Support
    Package, the current kernel, and GUI patch for the release of your
    System
    2. Check whether the error occurs locally on one or a few PCs, or
    generally on all PCs. Note whether the error only occurs for some
    users, for example because of a specific Customizing setting.
    If it only occurs locally, this suggests an installation problem
    with the PC. Check the installation; if necessary, reinstall the
    software. In the dump, search for the SY-MSGLI field, since it may
    point to the cause of the error.
    3. Activate the Automation Trace (in accordance with SAP Note
    158985).
    4.Start the transaction and continue until the screen immediately
    before the dump.
    5. From the System -> Utilities menu, choose Autom. Queue,
    Synchronous Processing.
    The status bar of the GUI displays the text:
    "Automation synchron flush mode on"
    6. If you now proceed with the application, the short dump will
    display the ABAP call that caused the error; the Automation Trace
    will contain the error on the presentation server.
    7. If necessary, load the short dump and trace files on to
    sapservX, so that SAP can analyze them.
    Message classe...... "CNDP"
    Number.............. 006
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPLOLEA" or "LOLEAU02"
    "AC_SYSTEM_FLUSH"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
    To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
    To obtain this, call the system log with Transaction SM21
    and select the "Print" function to print out the relevant
    part.
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, you can either use the "PRINT" command in the editor or
    print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "nhbho930"
    Network address.......... "192.168.0.30"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "NHBHO930"
    Database type............ "MSSQL"
    Database name............ "DEV"
    Database owner........... "dev"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 17 2007 00:18:58"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "SQL_Server_8.00 "
    Patch level.............. "196"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    User, transaction...
    Client.............. 300
    User................ "NHBABAP"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "SAPLOLEA"
    Screen.............. "SAPMSDYP 0010"
    Screen line......... 0
    Information on where terminated
    The termination occurred in the ABAP program "SAPLOLEA" in
    "AC_SYSTEM_FLUSH".
    The main program was "ZBDC_CONTRACT ".
    The termination occurred in line 29 of the source code of the (Include)
    program "LOLEAU02"
    of the source code of program "LOLEAU02" (when calling the editor 290).
    ~~~~~~~~~~~~~~~~~~~~~
    Thank you all.
    Cheers.
    Mitra __.____._

    for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
    You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone).

  • SAP Short Dumps and PCI Compliance

    We've run into an issue with our PCI Compliance audit around being able to see unencrypted credit cards in short dump messages in SAP.  Has anyone run into this issue?
    Only work around I've got at this point is to restrict all access to short dumps and require many documented signoffs before turning on and off access to a short dump.  This is pretty cumbersome, and still leaves a hole in my overall security.
    We've managed to purge restricted CC data from our XI logging, and done everything right with encryption, but this short dump issue just doesn't seem to have a solution.
    Can anyone help?  We're on 6.0.
    Thanks!

    Hi David,
    This is an interesting situation you have described. ABAP short-dumps or run-time errors as they are also known as, are unhandled exceptions during program execution. The conditions that cause such exceptions is unknown or cannot be handled at run-time. To help analyze what went wrong with the said program during execution, it is necessary for the dump to contain all possible information including data values passed between programs when the error occurs. Encryption of restricted data values is a program step in itself. If the dump were to occur after this step then of course it would contain encrypted CC info. Unfortunately in your case it exposes restricted CC info because the dump occurs BEFORE this step.
    I don't believe there is a way to prevent this from happening -- for the same reason that the program logic does not know at run-time how to "handle" the exception. If occurrences of such dumps is fairly common in your system, you may want to investigate the likely causes -- for example, missing or incorrect customization. Analyzing the short dumps will probably give you a clue. Your customization team may be able to identify a pre-condition that causes this unhandled exception. If this exception can then be handled (via a program change) that returns a meaningful error instead of a short dump you would be able to close the security hole. This however entails modification to SAP standard code. I don't usually recommend such changes, but given the sensitive nature of your data it may be worth consideration.
    I personally advocate restricted access to ST22. The steps you have undertaken to enforce this may be cumbersome despite efforts to keep it simple. I suppose that's the price we pay in administering the system. If you have not already done so, you may also want to ensure that short-dumps that contain restricted CC info are not saved (using the "Keep" feature in ST22) for easy retrieval at a later point in time or they are saved, it be available only to 'restricted eyes'. Short-dumps are normally saved in the system for 7 or 14 days (not sure of exact # of days). The bigger challenge in my opinion is: How do you prevent the restricted info from being viewed by the user who during the course of program/transaction execution encounters the said short dump? No amount of security controls around ST22 will mitigate this risk. The only option that remains is program change (as mentioned above). But to get there you first need to know what causes the exception.
    Regards.
    Ashutosh

  • Short Dump while copying Org structure from ERP to CRM

    Hello Experts:
    We are trying to copy the Org structure from ECC to CRM.
    We have a standard transaction 'CRMC_R3_ORG_GENERATE' to copy the the org structure from ECC or the IMG path:
    SPRO->CRM->Master Data->Organization Management->Data Transfer->Coppy ECC Sales Structure
    We have a multiple assignment scenario where each sales groups are assigned to multiple sales offices and likewise,each sales office is assigned to multiple sales org unit in ECC.
    This can be achieved by turning on the enhanced version.
    In our current business,even though the sales offices and groups are created,but are not having relavance in the business,hence while running in the sandbox system, we ran the program to copy the structures in the standard mode(default) and we could copy it without issues and create the org units for every entity in CRM based on how the number ranges are defined.
    What happens when enhanced version switch is turned on ::
    While we turn the mode to enhanced version, The system automatically::
    - enhances the Function tab page in the ppoma_crm  transaction to include a grid table, in which you maintain multiple assignments of organizational units
    - generates an extra dialog box to the Organization tab page in business transactions for you to select the relevant assignment path for the organizational unit
    - adapts the consistency check in business transactions to take into account organizational units that have been multiple assigned
    Risk factor :
    Once you have switched to the enhanced backend integration version of the organizational model you cannot return to the standard backend integration version. The system will also automatically make changes to the organizational model version in CRM Mobile Sales.
    Also this structure will happen across all the clients in the system,so unfortunately cannot try in a sandbox client also of the new environment.
    We are building our development box,so while running the above step in standard mode,the program gives a short dump due to long execution time even though we have the same amount of data as in our prototype system.
    Also, we increased the idle time value to a very high value.
    When I approached SAP OSS,I was told that it is due to the multiple assignment scenario,hence we need to switch to enhanced version in CRM before we run the copy program ( CRMC_ORG_R3_GENERATE )
    I am not quite sure if the mismatch of the scenarios between CRM and ECC could be causing this short dump as we could run it in standard mode in our prototype/sandbox environment without issues even  with the same data volume as in the new development system .
    I am looking for help from all the experts if they have come across similar issue and your recommendations/feedback if this can be corrected.
    Appreciate your guidance/recommendation on this issue.
    thanks!!

    In CRM Best Practices Building block C05 is the step by step description how to replicate Org. structure and some of employee's master data.
    Follow link - http://help.sap.com/bp_crmv12007/CRM_DE/BBLibrary/html/C05_EN_DE.htm

  • Short Dump due to TIME_OUT Error

    Hi,
         We have a situation here, where the monthly data from R/3 is extracted to ODS (Full upload) and subsequently getting uploaded to infocube (Delta). Usually the ODS to infocube updation takes long hours of time (say 8 hours), because of complexity of the update rules over the cube and this was working fine for the past months.
    But on 1st of this month when I extracted R/3 data went fine upto ODS, but failed in the further process (i.e., ODS to Infocube) resulting in a short dump. Extract is shown below
    Short dump in the Warehouse
    Diagnosis
    The data update was not completed. A short dump has probably been logged in BW providing information about the error.
    System response
    "Caller 70" is missing.
    Further analysis:
    Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
    You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
    So I want to try out with another option, Since we know the data coming to ODS on a  monthly basis, instead of pushing the data to infocube in delta mode, can I upload the data using full update (but of course weekly wise) to cube ?.
    What will be the complications?.
    Please guide with your ideas…
    Thanks in advance,
    Arun.

    System response
    "Caller 70" is missing.
    Further analysis:
    Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
    You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
    Did you follow this recommendation?  Did you check the short dump? 
    If it is really a time_out issue, the short dump will tell you so, but there can also be other causes for caller 70 missing.
    It is a time_out you can either increase your time out setting, or decrease the package size in your infopackages;
    kr,
    Tom

  • ODS activation, short dump COMPUTE_INT_PLUS_OVERFLOW. How to solve?

    Hello Gurus,
    We are on BW 3.1.
    We have an issue - ODS activation failed due to a short dump.
    Runtime Error          COMPUTE_INT_PLUS_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    In the current program "SAPLRSSM_PROCESS",
    using + or 'ADD' to add the values 2137304138 and 12410267 resulted in a
    value greater than 2147483647 or samller than -2147483648. This
    leads to a whole number overflow.
    Could you please guide me to solve this?
    Please let me know if you need more details.
    Thanks,
    raj

    This dump is happening because of the overflow of the size assigned for the variable.
    This dump can be avoided by changing the declaration of the variable definition.
    DATA: variable_name type p decimals 0.  
                              OR
    DATA: varibale_name(25) type n decimals 0
    Try this. This will resolve your dump.
    regards,
    brijesh

  • In SMARTFORMS when openee a Text Node,   Giving a Short Dump

    Hi
    I am getting Short Dump in SMARTFORMS Transaction, when ever I opened a Text Node and made some changes in it.
    With out opening a Text Node I can able to change and activate the SmartForm.
    But if I open a Text Node I can able to make changes in the Text Node but later if i click on any other Node, it is giving a Short Dump.
    But all other systems in my office are working fine.
    I have tried the Utilities->Settings-> and changed the editor also. 
    I have also Installed the SAPGUI once again for this Issue. But still I am getting the same problem.
    Can anyone Please help me on this Issue.
    I am sending the error enalysis of the Short Dump.
    Error analysis
        Short text of error message:
        Control Framework : Error processing control
        Long text of error message:
         Diagnosis
             An error occurred when the system tried to process the commands
             from the Automation Queue on the presentation server.
             There are several possible reasons for this:
             - The installation of the SAP GUI on the presentation server is
             faulty or obsolete.
             - There is an error in the application program
             - There is an error in the SAPGUI or an integrated control
         Procedure
             1. Make sure that you have imported the appropriate Support
             Package, the current kernel, and GUI patch for the release of your
             system
             2. Check whether the error occurs locally on one or a few PCs, or
             generally on all PCs. Note whether the error only occurs for some
             users, for example because of a specific Customizing setting.
             If it only occurs locally, this suggests an installation problem
             with the PC. Check the installation; if necessary, reinstall the
             software. In the dump, search for the SY-MSGLI field, since it may
             point to the cause of the error.
             3. Activate the Automation Trace (in accordance with SAP Note
             158985).
             4.Start the transaction and continue until the screen immediately
             before the dump.
             5. From the System -> Utilities menu, choose Autom. Queue,
             Synchronous Processing.
             The status bar of the GUI displays the text:
                "Automation synchron flush mode on"
             6. If you now proceed with the application, the short dump will
             display the ABAP call that caused the error; the Automation Trace
             will contain the error on the presentation server.
             7. If necessary, load the short dump and trace files on to
             sapservX, so that SAP can analyze them.
        Technical information about the message:
        Message class....... "CNDP"
        Number.............. 006
    Thanks in Advance.

    Hi
    I think dump is because of SAP GUI. If you are ECC 6.0 then install SAP GUI 710 with patch level  2 or more and check
    Regards
    Shiva

  • ABAP short dump error while creating an invoice

    Hi All,
    We are creating a delivery(Unit is EA) for the material for which the Unit Conversion is maintained as 1CS = 48 EA. So while creating a delivery If I maintain the delivered quantity is less than 24, I am not able to create an invoice.It's throwing an ABAP short dump error BCD zerodivide run time error.
    If I deliver greater than or equal to 24, then the invoice is created without any issue
    I have checked if there is any  CMIR record but no record is maintained.
    Can anyone help me out on this?
    Regards,
    Manjunath

    Hi Manju,
         Can you post the dump screen shot, which should contain the source code for that dump.
    Regards,
    Krishna

  • 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

  • Short Dump Error DYNPRO_SEND_IN_BACKGROUND

    hello Experts
    I am facing one problem while query execution as a short dump is coming with run time error DYNPRO_SEND_IN_BACKGROUND.
    On the same time, the other query based on same Info provider is running perfectly without giving any error.
    Plz help on this , I checked the forums but does not get any output.
    Thanks in advance
    Neha

    Hi Neha,
    Check the below SAP Note.
    Note 1010525 - ABAP dump in precalculation server with system messages
    Veerendra.

  • Regarding Short dump while data extraction

    Hi All,
    We are trying to extract data from DB Connect. When we try to pull the data by giving selections, we are getting short dump.
    Name of Run time error.
    PERFORM_CONFLICT_TAB_TYPE
    Exception Name
    CX_SY_DYN_CALL_ILLEGAL_TYPE
    What could be the reason for this error.

    Hi Jayanth,
    Check these ...
    Perform_conflict_tab_type error
    Oracle to BW Load Runtime error CX_SY_DYN_CALL_ILLEGAL_TYPE
    Raja

Maybe you are looking for