Closing System Messages

Hi To All,
There are system messages appear in most of the screens..For those system messages we should click Ok Button or Cancel Button to close that message..But i want to close that system message through source code not by clicking the buttons...How to do it.....

Hi,
You can use this code..
Select Case pVal.FormTypeEx
Case "0"
If pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_ACTIVATE And pVal.FormType = "0" And pVal.ItemUID = "" And pVal.BeforeAction = False Then
objApp.SendKeys("")                      
End If
But you must be sure, that you auto click enter in system message on proper form - store in global variable identification, that the system mesage should be auto clicked and after click set the variable back to nothing. Otherwise you will auto click all system messages...
regards:
SANDY

Similar Messages

  • Trying to reinstall Acrobat Pro X from disc onto win 8.1 system. (Previous installation got corrupted) Continually getting message 'Acrobat has detected another process which has not yet completed-'. Have now closed system both cold (full shutdown) and wa

    Trying to reinstall Acrobat Pro X from disc onto win 8.1 system. (Previous installation got corrupted) Continually getting message ‘Acrobat has detected another process which has not yet completed…’. Have now closed system both cold (full shutdown) and warm (restart) over 10 times. Every time I go to reinstall I get message.

    I would run http://labs.adobe.com/downloads/acrobatcleaner.html and delete any Acrobat folders that have been created, then try again. Be sure to log in as the administrator and disable anti-virus when you have problems like this.

  • In r12 What is use of Purge log and Closed system alerts

    Hi
    In r12 What is use Concurrent reqest "Purge logs and Closed system alerts "
    is there any diffrence with "Purge Concurrent Request and/or Manager Data Program"
    we have to purge cm logs and data.
    '

    In r12 What is use Concurrent reqest "Purge logs and Closed system alerts "The concurrent program "Purge Debug Log and System Alerts" (Short name: FNDLGPRG) is the recommended way to purge messages. This program purges all messages up to the specified date, except messages for active transactions (new or open alerts, active ICX sessions, concurrent requests, and so on). This program is by default scheduled to run daily and purge messages older than 7 days. Internally this concurrent program invokes the FND_LOG_ADMIN APIs, which are described later in this document.
    Oracle® Applications Supportability Guide Release 12
    http://download.oracle.com/docs/cd/B40089_09/current/acrobat/120fndsupp.pdf
    is there any diffrence with "Purge Concurrent Request and/or Manager Data Program" This concurrent program is used to purge concurrent requests log/out file, and/or CM log files.
    we have to purge cm logs and data.Use "Purge Concurrent Request and/or Manager Data" concurrent program.

  • Newly Entered Posting Date - System Message in 2007

    Hi,
    I also have the same questions as I found in the below thread
    What G/L Accounts are Updated Accordingly when the Posting Date is Changed?
    What are the G/L accounts updated when you say u2018yesu2019? Is this update is for the new fiscal year G/L accounts?
    My Client recently upgraded from 2005A to 2007A and the new posting period starts from 01/08/09 to 31/0710
    When the posting date is changed to July 09 (Which is the previous posting period) in A/P or A/R Invoices, the following message appears
    Newly Entered Posting Date Relates to Another Posting Period. Do you want to update G/L accounts accordingly? Yes No
    Also the message keeps coming every time when posting for previous posting period. How to stop this system message?
    Thanks in advance
    Mohan

    Dear Mohan,
    The system message 'Newly entered posting date relates to another
    posting period, do you want to update G/L accounts accordingly' does not
    prevent the document from being added, it is just an alert message.
    The business background of this alert is that it may be possible that
    user has the changes done already to the G/L Account Determination in a
    new year. Therefore an alert is initiated to avoid any wrong postings to
    another period. I.e. this does not mean the system will somehow alter
    the G/L accounts after the alert was displayed and the message is for
    user information only.
    We had investigated the issue and found the following observations
    -Posting period for 01/08/2008 created
    -Create any transaction in previous posting period. (31/07/2008)
    -The system gives this message
    -If there is no posting period created for 2008, there will not be any
    message
    So whenever you enter any transaction in previous posting period other
    than the latest the system gives this message.Because system will update
    the accounts for that period.
    From the functional perspective, this transation can be added, and once
    it has been added to the previous fiscal year you need to perform the
    year-end closing again. It is a standard system behaviour.
    If you press yes the system will update the accounts involved for that
    period and the new account balance will be update accordingly.
    You can test it in a test environment.
    Please refer to note 800291 for more information.
    Kind regards,
    Apple

  • How to pop up a system message for a specific user when She/He log on SAP

    Hi Friends,
    As we know SM02 setting will pop up a system message to all users in specific client in a specific period when the user log on SAP system; and we can do the same thing via using function module SM02_ADD_MESSAGE.
    But now we want to pop up a message to a specific user ID when somebody log on SAP via this ID, instead of all user IDs in the client. Please do we have any similar traction / function module / class method to to do this job??
    Thanks in advance.
    Joe

    Below code can be used to send a pop up message to all users who are logged on to the
    system.
    DATA: MESSAGE(128) VALUE 'Test message'.
    DATA: OPCODE TYPE X VALUE 2.
    DATA: BEGIN OF USR_TABL OCCURS 10.
    INCLUDE STRUCTURE UINFO.
    DATA: END OF USR_TABL.
    CALL 'ThUsrInfo' ID 'OPCODE' FIELD OPCODE
    ID 'TAB' FIELD USR_TABL-SYS.
    LOOP AT USR_TABL.
    CALL FUNCTION 'TH_POPUP'
    EXPORTING
    CLIENT = SY-MANDT
    USER = USR_TABL-BNAME
    MESSAGE = MESSAGE
    EXCEPTIONS
    USER_NOT_FOUND = 1.
    ENDLOOP.
    In the above code just pass the desired user ID instead of All user ID's
    Edited by: harsh bhalla on Mar 26, 2009 2:14 PM

  • Unable to Log-in *SAP System Message : Error while reading a Dynpro*

    Hi,
    We are facing issues while logging-in through SAP logon 710.
    The system throws an error dialog box with the below message:
    SAP System Message : Error while reading a Dynpro
    At the OS level Java process  server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

    Hi Please find the contents of std_server.out below.
    stdout/stderr redirect
    node name   : server0
    pid         : 4124
    system name : KEC
    system nr.  : 01
    started at  : Mon Jul 27 15:44:57 2009
    [Thr 5656] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
    Loading: LogManager ... 250 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 47 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 0 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 93 ms.
    Loading: LockingManager ... 32 ms.
    Loading: ConfigurationManager ... 1032 ms.
    Loading: LicensingManager ... 0 ms.
    Loading: CacheManager ... 93 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service runtimeinfo started. (16 ms).
      Service cross started. (31 ms).
      Service file started. (31 ms).
      Service memory started. (31 ms).
      Service timeout started. (16 ms).
      Service trex.service started. (32 ms).
      Service userstore started. (0 ms).
      Service jmx_notification started. (15 ms).
      Service p4 started. (62 ms).
      Service classpath_resolver started. (16 ms).
      Service deploy started. (3722 ms).
      Service MigrationService started. (31 ms).
      Service bimmrdeployer started. (0 ms).
      Service log_configurator started. (5177 ms).
      Service locking started. (0 ms).
      Service http started. (126 ms).
      Service naming started. (157 ms).
      Service failover started. (16 ms).
      Service appclient started. (31 ms).
      Service javamail started. (47 ms).
      Service ts started. (47 ms).
      Service jmsconnector started. (47 ms).
      Service licensing started. (15 ms).
      Service connector started. (93 ms).
      Service iiop started. (94 ms).
      Service configuration started. (16 ms).
      Service webservices started. (265 ms).
      Service dbpool started. (1204 ms).
      Service UT started. (0 ms).
    Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
    Jul 27, 2009 3:45:09 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro                                       
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro                                       
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro                                       
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro                                       
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

  • System message at the time of login & need  post installation

    Hallo Everybody
    I just install the SAP IDES ECC 5.0 (SQL database), I also running some transaction, but from 2 days i receive the message at the time of logging
    System message
    Validity of certificate from list with PSE type >system PSE < ends in 1 day. for more information see the SAP system log (transaction SM21)
    but i also check the tran. SM21 but i can't find something that indicate what exact erroe and dignosis.
    So please suggest me the solution.
    Also  what  tran. are need to run (Post installation) after the installation. beacause i install IDES on standalone machine (Require Post installation proc.)
    System Desc.
    SID=ERP
    instance no=00
    host=sapsrv
    database SQL 2005

    check these links for the PSE error:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/0e/fb993af7700577e10000000a11402f/frameset.htm
    PSE certification validity end
    post-processing steps are in the installation guide.

  • SAP System Message: Syntx error or generation error in a screen

    dear sap basis gurus,
    i am currently having problems signing on to our DEV server. i get this error message:
    <SID>: SAP System Message
    Syntx error or generation error in a screen.
    it won't let me log on.
    there were no changes made on the server (i.e., profile parameters) lately. it was working really fine after our support package level upgrade about 5 months ago.
    have you encountered this problem before? please help me as there we have two imminent go-lives.
    thank you very much in advance.
    best regards,
    albert

    hello nick, ashok,
    thank you very much for your responses.
    i have already resolved this issue by just freeing up some space from our disks. not one of them was full though.
    i hope i would no longer encounter the error message.
    again, thank you.
    best regards,
    albert

  • Unique id For System Message

    Dear all,
       Any one can please tell me the unique id for System Message.  Also i want to know the unique id for 'yes' and 'No' in System Message. Its very urgent
    Thanks in advance
    with Regards
    G.shankar

    System message has formtype = 0. The Yes and No button has no ids for sap, but when you want to press one of this button, use sendkeys as SBO_Application.SendKeys("") or tab for No (default is Yes).
    For accesing to correct system message, use some global variable and there before showing system msgbox set some value and compare it after showing.
    hope it helps

  • Problem with GlassFish and Sun Java System Message Queue

    Hi,
    I used application server PE.8 and I upgraded to Sun Java System Application Server Platform Edition 9.0 Update 1 Patch 1, and I changed all my CLASSPATH and everything. My system is working fine, but the Sun Java System Message Queue that I used before is still showing the queues and physical queues of the previous application server, not the new one. Do you know if there is way to change that and link it to the new version?
    thanks

    Use an ESB like ServiceMix to bridge JMS providers
    http://servicemix.org/
    Or write your own MessageListener to consume from one JMS and publish on another one. Be careful with queues to avoid loosing the ordering - so you probably want to use a single MessageListener per subscription/queue - or to take advantage of Tibco's exclusive queues to ensure ordering is preserved. If ordering doesn't matter then don't worry too much about it and maybe have a pool of consumers to improve throughput
    James
    http://logicblaze.com/

  • Bapi_po_create1 is giving same system messages  multiple time in the joblog

    Hi Experts,
    Bapi_po_create1 is giving same system messages multiple times in the job log when we ran the program in the background
    can u plz suggest how to prevent these multiple appearances of same messages.
    I am pasting the code below whn i ran this program in backgorund job log is having the messages.
    Date       Time     Message text                                                                 Message class Message no. Message type
    08/06/2009 08:11:53 Job started                                                                       00           516          S
    08/06/2009 08:11:53 Step 001 started (program ZZZTEST, variant &0000000000008, user ID BREDDY)        00           550          S
    08/06/2009 08:11:54 Commitment plan contains no account assignment data                              MECP          020          S
    08/06/2009 08:11:54 Commitment plan contains no account assignment data                              MECP          020          S
    08/06/2009 08:11:54 Status "Initial Block" of material 20111 does not allow external procurement      ME           053          E
    08/06/2009 08:11:54 Status "Initial Block" of material 20111 does not allow external procurement      ME           053          E
    08/06/2009 08:11:54 Source not included in list despite source list requirement                       06           722          E
    08/06/2009 08:11:55 Pricing/euro: Attention: Euro Customizing not maintained                          VH           777          S
    08/06/2009 08:11:55 Pricing/euro: Attention: Euro Customizing not maintained                          VH           777          S
    08/06/2009 08:11:55 Status "Initial Block" of material 20111 does not allow external procurement      ME           053          E
    08/06/2009 08:11:55 Purchase order still contains faulty items                                       MEPO          000          E
    08/06/2009 08:11:55 Job finished                                                                      00           517          S
    Edited by: bhavani prasad kotharu on Aug 6, 2009 3:09 PM

    HERE IS THE CODE OF THE PROGRAM, WE R JUST PASSING SOME PO DATA TO THE BAPI_PO_CREATE1,ON RUNNING THIS PROGRAM IN BACKGROUND SAME SYSTEM MESSAGES ARE APPEARED MULTIPLE TIMES,----
    REPORT zzztest.
    DATA :    lwa_bapimepoheader TYPE bapimepoheader
             ,lwa_bapimepoheaderx TYPE bapimepoheaderx
             ,li_bapimepoitem TYPE STANDARD TABLE OF bapimepoitem
             ,lwa_bapimepoitem TYPE  bapimepoitem
             ,li_bapimepoitemx TYPE STANDARD TABLE OF bapimepoitemx
             ,lwa_bapimepoitemx TYPE bapimepoitemx
             ,li_conditions TYPE STANDARD TABLE OF komv
             ,li_return TYPE STANDARD TABLE OF bapiret2
             , n TYPE c
    PARAMETERS: p1 TYPE c AS CHECKBOX.
    IF p1 = 'X'.
      lwa_bapimepoheader-doc_type = 'NB'.
      lwa_bapimepoheader-purch_org = 'NA00'.
      lwa_bapimepoheader-pur_group = 'C02'.
      lwa_bapimepoheaderx-doc_type = 'X'.
      lwa_bapimepoheaderx-purch_org = 'X'.
      lwa_bapimepoheaderx-pur_group = 'X'.
      lwa_bapimepoitem-po_item = '10'.
      lwa_bapimepoitem-material = '000000000000020111'.
      lwa_bapimepoitem-plant = 'CA01'.
      lwa_bapimepoitem-vend_mat = '1000'.
      lwa_bapimepoitem-quantity = '10'.
      lwa_bapimepoitem-orderpr_un = 'M'.
      lwa_bapimepoitem-no_more_gr = 'K'.
      lwa_bapimepoitem-agreement = '4600000095'.
      lwa_bapimepoitem-agmt_item = '10'.
      lwa_bapimepoitem-pricedate = 'X'.
      lwa_bapimepoitem-price_date = '20071030'.
      lwa_bapimepoitem-no_rounding = 'X'.
      APPEND lwa_bapimepoitem TO li_bapimepoitem.
      lwa_bapimepoitemx-po_item = '10'.
      lwa_bapimepoitemx-po_itemx = 'X'.
      lwa_bapimepoitemx-po_itemx = 'X'.
      lwa_bapimepoitemx-material = 'X'.
      lwa_bapimepoitemx-plant = 'X'.
      lwa_bapimepoitemx-quantity = 'X'.
      lwa_bapimepoitemx-po_unit = 'X'.
      lwa_bapimepoitemx-orderpr_un = 'X'.
      lwa_bapimepoitemx-acctasscat = 'X'.
      lwa_bapimepoitemx-agreement = 'X'.
      lwa_bapimepoitemx-agmt_item = 'X'.
      lwa_bapimepoitemx-pricedate = 'X'.
      lwa_bapimepoitemx-price_date = 'X'.
      lwa_bapimepoitemx-preq_no = 'X'.
      lwa_bapimepoitemx-preq_item = 'X'.
      lwa_bapimepoitemx-no_rounding = 'X'.
      APPEND lwa_bapimepoitemx TO li_bapimepoitemx.
    DATA: lo_msg_handler  TYPE REF TO cl_message_handler_mm.
      CALL METHOD cl_message_handler_mm=>get_handler
        IMPORTING
          ex_handler = lo_msg_handler.
      lo_msg_handler->remove_all( ).
      lo_msg_handler->cleanup( ).
      CALL FUNCTION 'BAPI_PO_CREATE1' "in background task
           EXPORTING
             poheader   = lwa_bapimepoheader
             poheaderx  = lwa_bapimepoheaderx
             testrun    = 'X'
           NO_MESSAGING = c_x
           NO_MESSAGE_REQ = c_x
             no_authority = 'X'
           IMPORTING
             expheader  = lwa_bapimepoheader
           TABLES
             return     = li_return
             poitem     = li_bapimepoitem
             poitemx    = li_bapimepoitemx
             conditions = li_conditions.
    ENDIF.
    Edited by: bhavani prasad kotharu on Aug 6, 2009 3:38 PM

  • SAP Business One 8.8 System Messages

    In SAP Business One 8.8 when you have entered a document with a later posting then today if you then enter a document with todayu2019s date you receive the System Message "There is a document of this type with a later posting date". If you select the option 'Block Documents with eelier posting date' you know longer receive this message however we still need to the option to do this.
    I have a number of clients that would like to have the ability to turn this message on or off

    Hi Gordon,
    Yes I know you can select u2018OKu2019 and move on with the entering of a marketing document, however this is an extra click and when you are entering a large number of documents a day this can become painfully and that is the feedback from the customers, is there a reason why this could not be an option in the company settings? I know this will not happen overnight and this is why I posted the question of the development collaboration forum.
    Kind regards,
    Johnathon

  • How can I clean up queue one-time on Sun Java system messaging 6.3

    Hi,
    <address>Our Email server have a problem, When I run _./imsimta qm directory tcp_local_, There are about 5 Millions of messages in the queue.</address>
    Now our Email server send messages very slowly, how can I clean up queue one-time?
    the command _./imsimta qclean_ is very slowly.
    What can I do to prevent this problem?
    our Email server version is :
    Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)
    libimta.so 6.3-6.03 (built 17:12:37, Mar 14 2008; 32bit)
    SunOS email-1 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V890
    Thank you !

    If you have more than 100,000 messages in the queue, then look at the MAX_MESSAGES parameter in [the job_controller.cnf file|http://wikis.sun.com/display/CommSuite/Job+Controller+Configuration+File]. If the parameter is not specified, it defaults to 100000. If you have more than that number of messages in the channel queues, it will take a long time for new/legitimate messages to be sent because job_controller is only considering the first 100,000 messages in the queue.
    If you get into the "imsimta qm" command do do "sum -database", it will show a summary of what job_controller has in its internal cache and therefore what job_controller is working on. If you compare that to "sum -directory" you will probably see a difference.
    If these are all legitimate messages, you need to increase MAX_MESSAGES, cnbuild, and restart job_controller.
    If they are not, then preventing this in the future will require determining how they got into your queue and correcting that.
    As for removing them, the "imsimta qm" commands allow you to select messages by various criteria and then you can "return" or "delete" them. But yes, that will take a long time if there are many messages because it is a single threaded process and it needs to open and examine each message. You may be able to accomplish the task more quickly with a shell script that works on individual channel queue subdirectories and then run multiple copies of that script in parallel. After you have cleaned out the queue, restart job_controller.
    Also, you might want to consider [the subdirs channel keyword|http://msg.wikidoc.info/index.php/Subdirs_and_nosubdirs_Channel_Options].

  • Error in local message system; message 009999000035 not complete

    Hello All.
    I have configured Service desk in SolMan 7.0 which has patch level 14 and also configured in Satellite systems. I am using SM_...._BACK RFC connection in BCOS_CUST table. The user used by SM_...._BACK have the following roles in SolMan
    SAP_SUPPDESK_CREATE,SAP_SV_FDB_NOTIF_BC_ADMIN
    and SAP_SV_FDB_NOTIF_BC_CREATE.
    However, when I try to create support message (Help --> Create support message) in satellite system, i am getting Error in local message system; message 009999000035 not complete.
    I have also checked for Product_ID parameter which is not existing.
    One important thing is, I can create support message in satellite system if I give SAP_ALL in that RFC user using in SM_...._BACK connection in SolMan.
    So, this shows clearly that it is an issue with role/authorization.
    Please suggest me !!
    Thanks in advance.
    Regards,
    Satish.

    Hmm not really. Profiles for the roles are also generated?
    Those roles/profiles should be sufficient to create support messages.
    Even though you assigned SAP_ALL and it worked afterwards I cannot imagine you got an auth. problem here anymore.
    When assigning SAP_ALL did you really assign SAP_ALL to the RFC user or did you assign another user (who got SAP_ALL auth.) to the RFC connection?
    The user who was logged on to the satellite system when the support messages have been created (with and without SAP_ALL assigned to the RFC user) has always been the same?
    Just to make sure: did you set NO_USER_CHECK = X in Sol Man tx: DNO_CUST04?

  • Error in local system;message is not complete--- in Solman 4.0

    Hello Solman Gurus,
             After importing SP 13 in Solution Manager 4.0 , whenever i am trying from help--> create support message ; i am getting "ERROR IN LOCAL SYSTEM; MESSAGE <MSG NO> IS NOT COMPLETE "
    i have seen these threads
    ERROR when Trying to create support message in satellite system
    ERROR when Trying to Create Support Message in Satillite system
    create support message
    but they are saying about Satelliate system not solman
    Please help if you could
    regards
    Naveen

    Naveen,
      Check if the UserId that is creating the message in SolMan via Help->Create Support Message has roles SAP_SUPPDESK_CREATE and SAP_SV_FDB_NOTIF_BC_ADMIN (the profiles of the roles must be generated, all the authorization objects should be green).
      I have SolMan 4.0 SP 13 too, when I delete these authorizations from my userid, I have the same error.
    Let me know if you still have the error.
    Regards,
    Raquel.

Maybe you are looking for