Mail Triggering Issue

Hi Folks,
             I am facing a problem in mail generation program.Program is working fine if i send to individual Mail IDs but if I send to multiple Mail IDs its been reaching only to few Mail IDs and its not able to deliver other Mail IDs.
Valuable Inputs are rewarded.

hi ,
can u check the Error of that mail status in SCOT.
regards
Prabhu

Similar Messages

  • Manual mail triggering issues in SOST

    Hi ,
    In standard notification type (M1) ACTION BOX " Send confirmation of Receipt", i executed the Email with user's mail id. Mail was generated.But its waiting for long time in SOST(send request) and i need to manually trigger it in SOST to send it users. Usually, mail would be sent to user without the manual triggering in SOST. But its not happening in my case. I think, some settings to be done for it.
    Can you please let me know how to sort out this issue.
    Thanks in Advance.

    Hi,
    First, your question is out of topic in this forum.
    Secondly, the answer is that you need a periodic job using report RSCONN01 to send your mails automatically.
    Regards,
    Olivier

  • DOCUMENT_NOT_SENT error in Mail Triggerring

    Hello All,
    I got a requirement wherein i have to covert a program output to spool and from spool i should convert that into a PDF attachment and trigger a mail to Outlook...
    I could do the above one [everything is going fine, right spoolid i chosen and the data is compressed and packed in right way]
    But when i try to trigger that as mail using FM SO_DOCUMENT_SEND_API1..
    I am getting error as DOCUMENT_NOT_SENT [My NEW_OBJECT_ID in FM SO_DOCUMENT_SEND_API1 is blank will it make FM SX_SEND_DISPATCHER to fail?? Hence results in no mail triggering] ...
    To find out the problem i have even checked SCOT and SOST transaction, But no log was found....
    Also i made a background schedule of my program and saw the results in SM37 [Here also i could not see any error and i could see my desired output]..
    I have even enabled  PUT_IN_OUTBOX  as  'X' and COMMIT_WORK  as  'X'.....
    My coding is as follows:
      CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
        EXPORTING
          DOCUMENT_DATA              = LA_DOC "W_DOC_DATA
          PUT_IN_OUTBOX              = 'X'
          COMMIT_WORK                = 'X'
        IMPORTING
          NEW_OBJECT_ID              = OBJID
        TABLES
          PACKING_LIST               = IT_PACKING_LIST
          OBJECT_HEADER              = HEADLIST
          CONTENTS_BIN               = IT_ATTACHMENT
          CONTENTS_TXT               = IT_MAILBODY[]
          RECEIVERS                  = T_RECEIVERS[]
        EXCEPTIONS
          TOO_MANY_RECEIVERS         = 1
          DOCUMENT_NOT_SENT          = 2
          DOCUMENT_TYPE_NOT_EXIST    = 3
          OPERATION_NO_AUTHORIZATION = 4
          PARAMETER_ERROR            = 5
          X_ERROR                    = 6
          ENQUEUE_ERROR              = 7
          OTHERS                     = 8.
    Waiting for your replies.....

    Hi Jayanthi,
    I want to send email to internet address and not to SAP user. Like for example can I send the attachment to my yahoo id??
    If I change to
    i_reclist-receiver = give sap user id
    i_reclist-express = 'X'.
    i_reclist-rec_type = 'B'.
    this will surely work but it comes to my SAP Office Inbox but I need to send it to any address on the internet. Is it possible?
    Please do reply.
    Thanks in advance,
    Rashmi

  • Transport Mail Database issues crashing Transport service

    We are experiencing frequent issues on Hub servers (as often as once a week) where Transport Mail DB issues crash the Transport service.  Had an MS specialist in the other day who could not exactly figure out the root cause.  The pattern usually is as follows:
    1. Event ID 486 - This event refers to a failure to move a log file (associated with Transport Mail DB queues) because it is being used by another process.  What that process could be is unknown.
    2. Event ID 413 - Unable to create a new logfile because the database cannot write to the log drive.
    3. Event ID 492 - The logfile sequence in <dir> has been halted
    4. Event ID 17019 - A database operation has encountered a I/O error. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamLogWriteFailException: Failure writing to log file (-510)
    Also followed by events 7001,1022,1002, and 1003.
    Haven't been able to determine what is causing Event ID 486.  Not aware of any process that would be tying up the access to the log file.  These queue files are stored on a local disk, not a SAN. 
    Any ideas as to what could be causing this?  Running E2K7SP1 Rollup 2 currently on all Exchange systems.

    Hi,
    I suggest that you use the following method to check which process access the log file indicated in the event 486:
    Using Process Explorer
    http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
    Then, we did the following:
    1. Launch Process Explorer
    2. Click Find, Find Handle or DLL
    3. Enter the log name indicated in the event 486 and click Search
    In addition, please also check whether any events such as 150004 occur before the Transport service crashes. If you notice the event, I also suggest that you refer to the following article:
    http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx
    Mike
     

  • In which community is it best to discuss mail.app issues?

    In which community is it best to discuss mail.app issues?

    You should ask in the forum for the version of OSX you are using:
    OS X Yosemite
    OS X Mavericks
    OS X Mountain Lion
    Mac OS X v10.7 Lion
    Mac OS X v10.6 Snow Leopard

  • Outgoing Mail server issues

    ooutgoing mail server issues. Rebooted phone, changed password, changed port everything and still no luck !!

    Its something to do with my phone it's self. The exact details in another phone works !! Just can't figure it out.

  • Mail app issues

    This is more of a Mail app issue, and I've posted the question on that board, but I thought I'd post it here because I'm hoping some admins might have dealt with a similar issues:
    Is anyone having success with clients on Network Homes using Leopard's Mail.app and an IMAP server?
    Things used to work on the same client machines under Tiger, but after upgrading them to Leopard, Mail.app flat out refuses to work.
    Users with portable homes seem to have better luck.
    Some symptoms:
    after working fine for 15-20 seconds, preview pane gets stuck on a "Loading" message. Double-clicking the same email opens it just fine in a separate window.
    auto-fill of addresses in the To: field doesn't work. (The little circle on the right just keeps spinning.)
    Mail.app does not pull any new incoming messages.
    Mail.app refuses to quit cleanly. Force-quitting is the only way to make it quit
    Mail.app randomly needs to "Quit or Quit and Rebuild" the database.
    Thanks.

    Thanks to Dan Peterka in this thread:
    http://discussions.apple.com/message.jspa?messageID=7912204
    Disabling Sophos On-Access Scanning resolves the issue.

  • How to find the mails triggered by which user from SOST or other transac.

    Hi Experts,
    How to find out mails triggered from SAP system by which user from SOST or some other means of mail triggering from SAP.
    Regards,
    IFF

    Hi Buddy,
    Make the question clear. You can check in SCOT transaction.
    Cheers,
    Sanil

  • Mail send issue - Workflow Triggered from Error Message

    hi
    i am learning workflow and doing some practical sessions using tutorials found on the internet. I have successfully enabled a workflow triggering options from the error message. The workflow will simply send an email and there is nothing else in that workflow definition. When i get the error message i open up the error message window and trigger the workflow option which is enabled. I get a message that the workflow has been started but i dont get the email immediately. I see the emails only after a long time. Infact the emails sent yesterday is only visible today.
    i checked in SOST and i dont see the messages at all. If its available in SOST then the system would have picked up and send to the inbox. But i dont see the mails queued in SOST. But if i wait for a day i can see the emails in my inbox. Any idea what is wrong.
    ~Suresh
    Message was edited by:
            Suresh Reddy

    Hi Suresh
    Good on you that you are actually going through the SAP Help and trying the harder but better way unlike many others...your input regarding your problem is also quite well explained....Keep it up!
    Coming to your problem,
    <b>1.>>I see the emails only after a long time. Infact the emails sent yesterday is >>only visible today.</b>
    RSCONN01 is the program that sends email out of SAP, make sure this scheduled to run frequently otherwise you can manually run this from SE/SA38.
    <b>2. i checked in SOST and i dont see the messages at all. If its available in SOST then the system would have picked up and send to the inbox</b>
    When you run SOST make sure you tick all the checkboxes - Waiting, Errors, Sent and Transmitted. If you are on ECC, then these are available on the Send Status tab...
    Good Luck
    Ravi

  • Issue while mail triggering using function module SO_NEW_DOCUMENT_SEND_API1

    Hi all,
    I have requirement to send mails from BADI.For that i used following function modules-SO_NEW_DOCUMENT_SEND_API1
    and
    SO_NEW_DOCUMENT_ATT_SEND_API1,
    Both of these two function module requires to use COMMIT WORK statement.
    But if we use COMMIT WORK statement in BADI a run time error is occuring as its not allowed in BADI.
    Can anybody provide solution for this  or provide another function module.
    Thank you.

    commit work not allowed in BADI.It gives runtime error
    Information on commit work.
    becos for commit work. sy-subrc will allways sets to zero.
    you can better use commitwork and wait. it sets sy-subrc.
    To avoid runtime error / dump you can check the sy-subrc value. if its not equal to zero. just
    Roll back work.
    Plz look at the piece of code below
    commit work and wait.
    if sy-subrc eq 0.
    exit.
    else.
    rollback work.
    wa_error-msg = "Failed to update the status in the database "
    append wa_error to it_error.
    exit.
    endif.
    Also check the badi signature. there you have a internal table to store the error messages.
    if commit work fails then add the appropriate error message to the internal table .
    Hope this gives you some idea on commit work.
    But as everyone says, commit work is not required for that function module . i too agree with that.
    if you try to update any database after you successfully send the file . then i think commit work statement is necessary for you.
    Thanks,
    Uma

  • Mail sent issue in CLM work flow

    Hi Expert,
    we are facing an issue CLM workflow mails.
    Once all approvers done in contract document the status mail need to be triggered to the owner of the Document.
    But intead of that it is sending to other person who is nowhere related to the document .
    Please guide me on this .
    Thanks,
    Pavan.

    Hi Expert,
    we are facing an issue CLM workflow mails.
    Once all approvers done in contract document the status mail need to be triggered to the owner of the Document.
    But intead of that it is sending to other person who is nowhere related to the document .
    Please guide me on this .
    Thanks,
    Pavan.

  • Mail Trigerred Issue

    Hi ,
          Mail was not sent to the respective group for a workflow process . i.e. Mail is not getting triggered and sent to the approval group  . Experts pls suggest me how to resolve this issue  .
    Thanks in Advance,
    Deepika T

    resolved

  • Workflow triggering Issue

    Hi Experts,
         When i look into this problem from outside,Its really strange.Actually user has created a PO and a workflow was triggered to the approver.The problem is 'PO creator gets an error message that ' Approvers not maintained ' eventhough that corresponding PO has released after approved by approver.So why PO creator gets error message as 'Approvers not maintained' instead of releasing confirmation'. Please throw some lights to solve this workflow error.Thanks in advance.

    Hi Kavi,
      As yiu said Initiator is getting error message "No approver maintained" after all the approval. That means all the maintained approvers in PO release strategy have approved the PO and finally there will be no more approver so the initiator is getting message. 2 Points:
    1.) Check the PO release streatgy. After final approval PO release status should changed to Released completly.
    2.) The workflow step which sends error message to initiator should have condition. If last approver is not final approver of PO then only send mail.
    Hope point 2 will solve your issue.
    CHeers,
    Prakash

  • E-mail Trigerring issue

    Hi Experts,
                      For a contract work-flow , Email trigerring was not happeneing .  when a contract moves from 1 phase to other , Email was getting triggered . but suddenly the email is not getting generated . Can any one pls suggest me ..
    Thanks in advance
    Tayi

    Here are a few things worth checking.
    1. Check processed messages:  to see if the messages are leaving the system and not reaching their intended recipients.
    2. Check queued messages :  to see if the messages are being generated and simply have not left the system yet.
    3. Ensure, that the approver collaborator is not silent
    4. Ensure, that document phase has workflow associated with it.
    5. Ensure, that the correct mail message template ( Workflow Approval Request ) is properly configured to send emails to buyers.
    Then we will have a better idea of what the issue may be...

  • 10.9.1 Mail - Scrolling issues between Message & Mailbox views

    Just in the past week I am seeing something strange with scrolling in both the Message panel and the Mailbox list of all Mail in either my inbox or sent.
    At times I can only scroll within the Message window between all the Messages in a conversation. But then can not scroll through the list of all Mail and Conversations. Then other times it reverses and the Message window is frozen and can only scroll through the lists. Also for the first time when I scroll too far down I can see white space above with the Message or in the List, whichever I am able to scroll through at that time. I have quit mail, quit and restarted the computer, all to no avail. The whole thing is random and can not replicate this behavior. Help?
    OS 10.9.1
    Mail 7.1 (1827)

    I should add that these Print formatting issues do *NOT* show on every Mail 7.1 message in Mavericks 10.9.1.
    So far, I've not been able to ferret out just what it is about a Message that cause Print formatting to screw up.  Things I believe I've ELIMINATED include:
    1)  Newly created Messages vs. old Messages.
    2)  Messages with or without attachements
    3)  Messages with or without signatures
    4)  Messages which include prior Messages in a Reply or Forward string, or not (i.e., single, original Messages)
    5)  Mesages with multiple recipients or not or with CC: recipients in the Header or not.
    However this problem is by no means "random".  Any Message that shows one of the Three Problems I've detailed above will exhibit that Problem every single time you try to Print it.  Any Message which Prints cleanly, will continue to Print cleanly every time as well.  So there is SOMETHING about the data in the failing Messages which is triggering this problem.
    One new behavior I've noted is that for some Messages a new notice appears on screen -- briefly -- the first time you try to Print them.  It appears so briefly that I may have the exact text wrong, but it is something like "Generating Print Content".  I'm beginning to  suspect the Printing problems show ONLY on Messages that need to go through that "extra step" the first time you try to Print them.  But I don't know what that Message implies -- i.e., is there a new, "printable" file being generated by Mail specific to that Message which might persist across different Print attempts?  If so, the error may be due to how THAT file is created.
    This new notice only seems to appear the FIRST time you try to Print a Message -- and evidently not on every Message (or pehaps it is so brief on some Messages that I just don't see it).
    --Bob

Maybe you are looking for