Mail Sender to Abap Proxy Receiver with Attachements

Hi All,
Scenario: I need to create a ticket in Solman from a mail. I intend to do the scenario as Mail sender to Abap Proxy receiver asynchronous.
I have configured my sender mail adapter and am able to get the mails in XI. The attachements also appear in Inbound payload as MailAttachement-1, MailAttachement-2 etc. I have checked use mail packege and keep attachements in sender adapter.
Transport Protocol: IMAP4
Message Protocol: XIPAYLOAD
Queries:
1. My Inbound Data Type is the mail Package -- ximail30_xsd. Here in sxmb_moni I can see the mail attributes like from, to and the mail body in content. But How can I read the attachements in my message mapping.
2. How can I pass these attachements to Abap Proxy ( I do not need to alter attachments only pass to proxy ). These attachements have to be attached to the Solman ticket in SOLMAN server.
Appreciate your kind response to my above queries.
Thanks.
Regards,
Siddhesh S.Tawate
PS: I have tried using PayloadSwapBean in adapter module but still the content at source remains same.

Hi,
Please find below the part of code that might help you. I have given code only responsible for attachements part of the ticket.
loop at lt_attach into l_attachment.
        count = count + 1.
        if count = 1.
          first_line = 1.
        endif.
        l_type = l_attachment->GET_CONTENT_TYPE( ).
        split l_type at '"' into l_type
                                 file_name
                                 l_name.
        l_name = file_name.
        split file_name at '.' into file_name
                                    file_type.
        l_xstring = l_attachment->GET_BINARY_DATA( ).
        strlen = xstrlen( l_xstring ).
        Compute int = ( strlen div 255 ).
        Compute rem = ( strlen mod 255 ).
        if rem <> 0.
          int = int + 1.
        endif.
        count1 = int.
        if count = 1.
          last_line = count1.
        else.
          if int = 1.
            first_line = last_line.
          else.
            last_line = first_line + count1.
          endif.
        endif.
        wa_APPX_HEADERS-APPXNO = count.
        wa_APPX_HEADERS-DESCR = l_name.
        wa_APPX_HEADERS-FILETYP = file_type.
        wa_APPX_HEADERS-FILENAM = l_name.
        wa_APPX_HEADERS-FILEFM_UL = 'BIN'.
        wa_APPX_HEADERS-FIRSTL = first_line.
        wa_APPX_HEADERS-LASTL = last_line.
        wa_APPX_HEADERS-FILELEN = strlen.
        wa_APPX_HEADERS-LAST_USR = sy-uname.
        GET TIME STAMP FIELD wa_appx_headers-TIMESTAMP.
        append wa_APPX_HEADERS to it_APPX_HEADERS.
        while count1 <> 0.
          count1 = count1 - 1.
          if count1 <> 0.
            wa_APPX_LINES_bin-LINE = l_xstring+0(255).
            shift l_xstring left by 255 places in BYTE MODE.
          ELSE.
            wa_APPX_LINES_bin-LINE = l_xstring.
          endif.
          append wa_APPX_LINES_bin to it_APPX_LINES_bin.
          clear: wa_APPX_LINES_bin, wa_APPX_LINES.
        endwhile.
        first_line = last_line + 1.
        clear: strlen, count1, file_name, file_type, l_type, int, rem, l_xstring, l_attachment.
      endloop.
CALL FUNCTION 'BAPI_NOTIFICATION_CREATE'
        EXPORTING
          NOTIF_EXT                = wa_NOTIF_EXT
        NOTIF_CRM                = wa_NOTIF_CRM
  IBASE_DATA               =
     IMPORTING
       NUMBER                   = Refnum
       NUMB                     = Numb
       REFNUM                   = Ticket_No
       SYSID                    = SYSID
        TABLES
          NOTIF_PARTNERS           = it_NOTIF_PARTNERS
        NOTIF_NOTES              = it_NOTIF_N_EXT
          NOTIF_SAP_DATA           = it_NOTIF_SAP_DATA
        NOTIF_TEXT_HEADERS       = it_NOTIF_TEXT_HEADERS
        NOTIF_TEXT_LINES         = it_NOTIF_TEXT_LINES
        APPX_HEADERS             = it_APPX_HEADERS
        APPX_LINES               = it_APPX_LINES
        APPX_LINES_BIN           = it_APPX_LINES_BIN
         RETURN                   = RETURN
Please observe how first and last line of attachement is calculated. That is what created problem for me initially.
Hope this helps.
Regards,
Siddhesh S.Tawate

Similar Messages

  • ABAP Proxy Receiver Asynchronous EOIO

    Hi,
    Is it possible to Guaranteeing the Sequence of Asynchronous Messages for ABAP Proxy Receiver(EOIO)?
    If yes, how can I configure?
    Thanks,
    Kiara.

    Hi Stefan,
    Thank you.
    One quick question.
    In case if I  use JMS>PI>RFC(Async) then also no need of maintaining EOIO for RFC Receiver Async?
    On JMS sender we are maintaining EOIO.
    Reason for this request is currently we are using JMS>PI>RFC Async. We are using EOIO on JMS sender, but some times sequence of messages is missing.
    Can you please let us know the cause of this issue.
    Thanks,
    Kiara.

  • Receive mail with PDF attachment into XI and send to ABAP proxy

    Hi,
    I have a scenario where I need to receive a mail into XI that has a PDF attachment. This attachment needs to be retained as ultimately I need to send the message into CRM via an ABAP proxy and read the attachment and load against a business partner.
    However, as I am only on SP13 I do not have the parameters such "Keep Attachments" available to use.
    So I have two questions:
    1. How do I receive the mail into XI with the PDF attachment ?
    2. How do I read the attachment in an ABAP proxy ?
    Any guidance in either question would be appreciated.
    Cheers
    Colin.

    hi,
    you say that there's no keep attachment
    indicator but does the XI store the attachment or not?
    maybe it stores all attachmens
    (I work with sp16 and I don't remember how it worked with sp13)
    but try maybe it accepts attachments by default
    then it would be quite easy
    if you use then use the attachement in abap proxy
    (like I said you won't have to use any java)
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Sender Abap Proxy -- Receiver JDBC , catch communication channel exceptions

    Hi All,
    I have a sender abap proxy and a receiver jdbc asynchronous interface.
    Now under some circumstances when I send some junk data for an update query(which satisfies metadata requirement but wrong primary key) it shows chequered flag in both XI and r/3.
    But in communication channel it shows error.
    Queries:
    1. How do I handle this.
    2. Since this is triggered from Abap wht will be subrc when method ends in this particular case.
    3. Is there any possibility of program goin into dump?
    Regards,
    Prem

    You can catch the exception in cx_ai_system_fault.
    http://help.sap.com/saphelp_nw70/helpdata/en/75/a55c3cff8ca92be10000000a114084/content.htm
    DATA:
    lo_mes TYPE REF TO
         [Client proxy class],
    l_sys_exc TYPE REF TO
            cx_ai_system_fault,
    l_app_exc TYPE REF TO
            cx_ai_application_fault.
    CREATE OBJECT lo_mes.
    TRY.
    CALL METHOD
      lo_mes->EXECUTE_SYNCHRONOUS
        EXPORTING
          OUTPUT    = ls_request
        IMPORTING
          INPUT     = ls_response.
    CATCH cx_ai_system_fault
                INTO l_sys_exc.
    * handle system error
        EXIT.
    CATCH cx_fault_1
                INTO l_app_exc.
    * handle application error 1
    CATCH cx_fault_n
                INTO l_app_exc.
    * handle application error n
    CATCH cx_ai_application_fault
                INTO l_app_exc.
    * handle other
    * application errors
    ENDTRY.
    Thanks,
    Beena.

  • File/FTP to ABAP Proxy (file as attachment)

    I have the following scenario: File/FTP -> XI -> ABAP Proxy but not the normal case. What I need is the picked file as attachment and the file name. I hope this is possible.
    I have found the following blogs:
    /people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
    /people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
    I have no idea where I have to start. How I should define the sender and receiver message interface? How I have to configure the sender file/ftp adapter?
    I'm using PI 7.1 SP 7.

    At the moment I have the following problem. I always get an error during mapping the request message. This is the error message:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Mapping der Request-Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MT_SCANFILE_to_MT_SAP_SCANFILE_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>
      <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.ParserE</SAP:P3>
      <SAP:P4>xception: XMLParser: No data allowed here: (hex) ~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Während des Anwendungs-Mappings com/sap/xi/tf/_MT_SCANFILE_to_MT_SAP_SCANFILE_ ist eine RuntimeException aufgetreten. com.sap.aii.utilxi.misc.api.BaseRuntimeException:Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) ~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    And if I use transaction sxmb_moni I see that the payload MainDocument is my pdf document and I can read it.
    MG%PDF-1.3
    %âãÏÓ
    2 0 obj
    /WinAnsiEncoding
    endobj
    3 0 obj
    <<
    %Devtype POST2    Font COURIER  normal Lang DE
    /Type /Font
    /Subtype /Type1
    /BaseFont /Courier
    /Name /F001
    /Encoding 2 0 R
    >>
    endobj
    4 0 obj
    <<
    /Length 5 0 R
    u2026.
    I believe there is still an error at my communication channel configuration of the ftp sender adapter.

  • IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

    Dear all,
    I have idoc to abap proxy  -
    R3 to SRM scenario.
    I am getting the error Receiver service cannot be converted to ale logical system.
    I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
    i am using receiver XI adapter
    with XI 3.0 as protocol
    and http destination with /sap/xi/engine?type = receiver
    i can see the data in the moni of receiver SRM system but it shows a red flag
    pls help

    Hi kiran,
    i have checked all the RFC destinations ... seems OK
    problem is in SRM moni .. sender service and sender interface are not visible.
    trace ::::
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = SR5</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
      <Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = DD2FF717DAE395F186DF001560A1C7CB</Trace>
      <Trace level="1" type="T">PLNAME = RECEIVER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
      <Trace level="1" type="T">Queue name : XBTR0003</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SR5</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
      <Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
    - <!--  ************************************
      -->
    - <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    - <asx:values>
      <CX_ERROR href="#o3314" />
      </asx:values>
    - <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
    - <cls:CX_SY_NO_HANDLER id="o3314">
    - <CX_ROOT>
      <TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
      <PREVIOUS href="#o3313" />
      <KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
    - <INTERNAL_SOURCE_POS>
      <PROGID>496</PROGID>
      <CONTID>1564</CONTID>
      </INTERNAL_SOURCE_POS>
      </CX_ROOT>
      <CX_NO_CHECK />
    - <CX_SY_NO_HANDLER>
      <CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
      </CX_SY_NO_HANDLER>
      </cls:CX_SY_NO_HANDLER>
    - <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
    - <CX_ROOT>
      <TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
      <PREVIOUS />
      <KERNEL_ERRID />
    - <INTERNAL_SOURCE_POS>
      <PROGID>496</PROGID>
      <CONTID>1738</CONTID>
      </INTERNAL_SOURCE_POS>
      </CX_ROOT>
      <CX_DYNAMIC_CHECK />
      <CX_AI_APPLICATION_FAULT />
    - <CX_BBPX1_STD_MESSAGE_FAULT>
      <AUTOMATIC_RETRY />
      <CONTROLLER />
      <NO_RETRY />
    - <STANDARD>
      <CONTROLLER />
      <FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
      <FAULT_URL />
      <FAULT_DETAIL />
      </STANDARD>
      </CX_BBPX1_STD_MESSAGE_FAULT>
      </cls:CX_BBPX1_STD_MESSAGE_FAULT>
      </asx:heap>
      </asx:abap>
      </Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
    pls help 
    points will be awarded

  • File to ABAP Proxy (problem with inbound queues in R3)

    Hi,
    In File-XI-ABAP proxy scenario, XI is successfully picking up file and sending it to R3.
    But in R3, an inbound queue is created in SMQ2 transaction code and I solved the same to automatically process the Queue by registering that in SMQR transaction code. But even though the inbound queue doesn't appear in SMQ2 (which means that it is processed successfully) it doesn't call the method EXECUTE_ASYNCHRONOUS. Can anyone help me whether I need to do any settings to run that method?
    Also can anyone help me, after the inbound queue is successfully processed in SMQ2 transaction, what would be the next step to watch what exactly that queue has done?

    Hi,
    Please check the program code for Server ABAP proxy.
    This will show you the trigerring of Proxy on inbound side.
    ABAP Proxy inbound program - sales order creation - Community Profiles - Wiki
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
    For Queues, you can go to SMQR and check for the register queue. Select and double click on it. If anything is stuck up then you can see in it. Even same with SMQ2
    Thanks
    swarup

  • HTTP to ABAP Proxy - Problem with "Current User" parameter

    Hi experts,
    We have a HTTP to ABAP proxy sceario, where I used an HTTP Destination to connect to the proxy.
    We're trying to use the option "Current User" in that destination in order to login to ECC with the same user that in PI adapter plain.
    The user exists i both systems, PI and ECC, with the same password.
    Checking that parameter we get the following error:
    <SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.UNAUTHORIZED</SAP:Code><SAP:P1>401 </SAP:P1><SAP:P2>Unauthorized</SAP:P2><SAP:P3>(See attachment HTMLError for details)</SAP:P3></SAP:Error>
    We think that PI is not getting the password.
    Does aybody know how to do this?
    Thanks and regards,
    LUIS B.

    Hi Chirumamilla,
    If we put user and password in SM59 (unchecking "Current User") the commuication works without problems.
    We don't want to leave a user set there, beacuse we are looking to access to PI with different users and login to ECC with the same user.
    Thanks,

  • Http to Abap Proxy communication with multiple queues generation in Recevr

    Dear SDNs,
    I need some help in the following scenario, appreciate your suggestions and help .
    I am receiving the messages from sender to PI on http posting, from PI  I am sending the message to SAP system using receiver xi communication channel ( receiver is abap proxy).
    Sender will send the messages in QOS=EOIO, QUEueID=XXXt_100 etc  parameters, when large volumes cases, it is getting delayed to process it using a single queue.
    We are thinking to dynamically  generate multiple queues in PI and send the same queue ids to receiver SAP system to process all the messages quickly in SAP System also.
    Help /Clarifications needed:
    1. XI receiver communication channel in  pi  does not provide any options to generate dynamic queue id based on payload content (using dynamic configuration) and sent it to SAP.
    2. Module Tab in receiver communication channel also got disabled to add  custom adapter modules, can we add custome adapter module on xi receiver channel to generate dynamic queue id ?
    Really appreciate your immediate help and suggestions.
    Thanks.
    Suraj.

    Dear Praveen,
    Thanks lot for the immediate reply, we need to use EOIO, as the messages need to be processed in the same order we send and receive, there is no flexibility in QOS=EOIO, Appreciate if there is any other thoughts?
    Thanks In Advance.
    Suraj.

  • XI 3.0 SP14 Synchronous SOAP- XI- ABAP Proxy - fails with "System Error"

    Hi All,
    The synchronous response message fails at the stage "Receiver Identification".
    It seems that the synchronous response XML has no "sender" attribute, so obviously the receiver determination fails.
    In the message monitor I can see the correct payload coming from the ABAP proxy, so that part looks OK.
    I have the same scenario working perfectly on another system landscape, so there might be a configuration side to it.
    Thanks is advance,
    Ofer
    Message was edited by: Ofer Even-Tsur

    Hi,
    for the error information SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
    looks like xi is not able to find a reciever of best case. Open up the scenario in COnfiguration, open up the modify(add spaces) and activate reciever determination / reciever communication channel.
    cheers,
    naveen

  • Is CC possible in Mails sending through ABAP?

    Hello All,
    My requirement is to send the requirement to MAIL reciepients ..We all know well about this from past ...
    But.Can You please  let me know is this possible Like putting some one in CC???
    Regards
    sas

    Hi,
    Please check the sample code.Its working fine. You can check the sample code by change the email IDs.
    REPORT  ztest_subha_mail.
    DATA: l_send_request TYPE REF TO cl_bcs,         " Send request
          l_body      TYPE bcsy_text,                " Mail body
          l_success   TYPE bcsy_text,                " Atchmnt for success
          l_error     TYPE bcsy_text,                " Atchmnt for error
          wa_text     TYPE soli,                     " Work area for attach
          l_document  TYPE REF TO cl_document_bcs,   " Mail body
          l_sender    TYPE REF TO if_sender_bcs,     " Sender address
          l_recipient TYPE REF TO if_recipient_bcs,  " Recipient
          l_size      TYPE sood-objlen,              " Size of Attachment
          l_lines     TYPE i,                        " Lines count
          l_email     TYPE ad_smtpadr,               " Email ID
          l_address   TYPE bcsy_resv,
          wa_address  TYPE bcss_resv,
          l_extension TYPE soodk-objtp VALUE 'RAW'.  " TXT format
    Prepare mail bidy
    APPEND 'Send multiple file as attachment of a Email commit.' TO l_body.
    APPEND space TO l_body.
    Preparing contents of attachment with Change Log
    Header line
    wa_text-line+0   = 'First column'.
    wa_text-line+20  = 'Second column'.
    wa_text-line+40  = 'Third column'.
    wa_text-line+60  = 'Fourth column'.
    wa_text-line+80  = 'Fifth column'.
    wa_text-line+100 = 'Sixth column'.
    wa_text-line+120 = 'Seventh column'.
    wa_text-line+140 = 'Eighth column'.
    APPEND wa_text TO l_success.
    APPEND wa_text TO l_error.
    CLEAR : wa_text.
    Populate the data part
    wa_text-line+0   = '111111111'.
    wa_text-line+20  = '222222222'.
    wa_text-line+40  = '333333333'.
    wa_text-line+60  = '333333333'.
    wa_text-line+80  = '444444444'.
    wa_text-line+100 = '555555555'.
    wa_text-line+120 = '666666666'.
    wa_text-line+140 = '777777777'.
    APPEND wa_text TO l_success.
    CLEAR : wa_text.
    wa_text-line+0   = 'aaaaaaaaa'.
    wa_text-line+20  = 'bbbbbbbbb'.
    wa_text-line+40  = 'ccccccccc'.
    wa_text-line+60  = 'ddddddddd'.
    wa_text-line+80  = 'eeeeeeeee'.
    wa_text-line+100 = 'fffffffff'.
    wa_text-line+120 = 'ggggggggg'.
    wa_text-line+140 = 'hhhhhhhhh'.
    APPEND wa_text TO l_error.
    CLEAR : wa_text.
    Creates persistent send request
    l_send_request = cl_bcs=>create_persistent( ).
    Craete document for mail body
    l_document = cl_document_bcs=>create_document(
                 i_type    = 'RAW'
                 i_text    = l_body  " Mail body
                 i_subject = 'Mail send as attachment' ).
    Attachment for success records
    l_lines = LINES( l_success ).
    l_size = l_lines * 255.
    Add attchment
    CALL METHOD l_document->add_attachment
      EXPORTING
        i_attachment_type    = l_extension
        i_attachment_subject = 'Success'
        i_attachment_size    = l_size
        i_att_content_text   = l_success. " Attachment for success record
    Attachment for error records
    l_lines = LINES( l_error ).
    l_size = l_lines * 255.
    Add attchment
    CALL METHOD l_document->add_attachment
      EXPORTING
        i_attachment_type    = l_extension
        i_attachment_subject = 'Error'
        i_attachment_size    = l_size
        i_att_content_text   = l_error. " Attachment for error record
    Add the document to send request
    CALL METHOD l_send_request->set_document( l_document ).
    Sender addess
    l_sender = cl_sapuser_bcs=>create( sy-uname ).
    CALL METHOD l_send_request->set_sender
      EXPORTING
        i_sender = l_sender.
    Recipient address
    l_email = 'TO'.        " NEED TO CHANGE
    l_recipient = cl_cam_address_bcs=>create_internet_address( l_email ).
    Add recipient address to send request
    CALL METHOD l_send_request->add_recipient
      EXPORTING
        i_recipient  = l_recipient
        i_express    = 'X'
        i_copy       = ' '
        i_blind_copy = ' '
        i_no_forward = ' '.
    l_email = 'CC'.      " NEED TO CHANGE
    l_recipient = cl_cam_address_bcs=>create_internet_address( l_email ).
    Add recipient address to send request
    CALL METHOD l_send_request->add_recipient
      EXPORTING
        i_recipient  = l_recipient
        i_express    = 'X'
        i_copy       = 'X'
        i_blind_copy = ' '
        i_no_forward = ' '.
    Trigger E-Mail immediately
    l_send_request->set_send_immediately( 'X' ).
    Send mail
    CALL METHOD l_send_request->send( ).
    COMMIT WORK.
    Also you can do the same thing using the FM SO_NEW_DOCUMENT_ATT_SEND_API1
    Here when you trying to create the Receipient list there for CC you need to check the field SOMLRECI1-COPY.
    Thanks
    Subhankar
    Edited by: Subhankar Garani on Mar 4, 2010 6:46 AM

  • Call proxy service from other proxy service with attachment

    Hi!
    I have got an email sending proxy service I would like to call this from an other proxy service and I want to send attachment in email. I can send email with attachment if i call this proxy as a webservice (e.g. from soapUI)
    But if i want to call this email proxy service from other proxy service, the attachment in email is empty. I put a log action (expression: $attachments) in the beginning of email proxy service, and I saw this in the log file:
    +<con:attachments xmlns:con="http://www.bea.com/wli/sb/context"/>+
    So the attachment is really empty...
    I use service callout. I put an insert action in request action of service callout:
    In Variable:
    attachments
    XPath:
    +.+
    Location:
    as first child of
    Expression:
    +<con:attachment xmlns:con="http://www.bea.com/wli/sb/context">+
    +     <con:Content-Type>application/octet-stream</con:Content-Type>+
    +     <con:Content-Disposition>attachment; filename="{$v_fileName}"</con:Content-Disposition>+
    +     <con:Content-Transfer-Encoding>base64</con:Content-Transfer-Encoding>     +
    +     <con:body>{$attachments/ctx:attachment/ctx:body/*}</con:body>+
    +</con:attachment>+
    Why cannot I call this email proxy service from other proxy service for sending email with attachment?
    I tried to solve this other. I called an email sending business service from this proxy service. But in this case I cannot set the body of email. If I put just one Transport Header action in publish action, I could send the email (with empty body). But If I put a replace action in publish action as well then the OSB didn't send the email and I couldn't find any error message in log file... How could I set the body of email in publish action?
    Thanks!
    Viktor

    You should be able to get the current user id from the SPListItemEventProperties object. From here you should be able to create a Claim. For example get the user by using
    user = SPWeb.Users.GetByID(properties.CurrentUserId)
    SPClaim claim = SPClaimProviderManager.CreateUserClaim(user.email, SPOriginalIssuerType.TrustedProvider, issuerIdentifier);
    https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.claims.spclaimprovidermanager.createuserclaim(v=office.14).aspx
    Blog | SharePoint Field Notes Dev Tools |
    SPFastDeploy | SPRemoteAPIExplorer

  • Mac Mail sends but does not receive

    Hi
    Big problem!
    Just upgraded to Lion - and this problem was on Snow Leopard too - I tried to upgrade to sort this out!
    Mail sends emails but does not recieve.
    I own the server where it is trying to connect to - the emails are there - I can see them through webmail.
    I have set up different email accounts on Mail and exactly the same for all domains and email accounts.
    I have re-installed Mail - exactly the same happens.
    I have used Thunderbird and it works!
    So it has to be a Mail problem. Server is fine, OS is fine, other email is fine. Mail is the problem.
    I think it has to do with keychain? Not sure though... I have tried literally hundreds of things but nothing works and I am at my wits end and run out of ideas!
    Any suggestions would be warmly received!!
    Thanks in advance
    Rob

    Hi,
    I have the same problem with my incoming mail.  I talked to the folks at Frontier (my ISP). They verified that a
    test message I had sent was received.  All account info appeared to be ok.  I click on "get mail"  and I do not
    receive any new incoming messages.  All connections succeed Using Connection Doctor, although the connection to smtp.frontiernet.net spins quite awhile before succeeding.
    While I was composing this reply, I decided to try to send a test message to my wife's account.  It came
    through ok.  I think I might have to contact Frontier again on this.  When I set her account up they gave me a
    different Incoming Mail Server name to use:  pop3.frontier.com, whereas mine is: pop3.frontiernet.net.  I believe
    new accounts are being assigned to: pop3.frontier.com.
    Also, when I'm showing all inboxes,  Mine all have a symbol after them that looks like a lazy z.  I am not familiar
    with this symbol, but since I'm having trouble, I suspect it is telling me something. Help on this??

  • E-mail sending from PL/SQL fails with SMTP error 550 must check for new....

    We have a issue like this. We have a e-mail program (PL/SQL stored procedure which is called from a 10g R2 form) which sends e-mails using UTL_SMTP. It was working but suddenly from day-before-yesterday stopped working. Mail admin says he did not change any mail server paras.
    The DB is in Linux so is the mail server. We finally did a code change. Now the mail goes to SMTP server but the mail does not go out of it (to a gmail address). We did a trace of the SMTP log and found out that it throws *550 [email protected] must check for new mail first* .
    Here is the SMTP server log:
    [192.168.0.6:25]
    Wed 2012-04-25 18:52:46: --> 220 suninsurance.com.fj ESMTP MDaemon 12.5.4; Wed, 25 Apr 2012 18:52:46 +1200
    Wed 2012-04-25 18:52:46: <-- HELO 192.168.0.6
    Wed 2012-04-25 18:52:46: --> 250 suninsurance.com.fj Hello 192.168.0.6, pleased to meet you
    Wed 2012-04-25 18:52:46: <-- MAIL FROM:[email protected]
    Wed 2012-04-25 18:52:46: --> 250 <[email protected]>, Sender ok
    Wed 2012-04-25 18:52:46: <-- RCPT TO:[email protected]
    Wed 2012-04-25 18:52:46: --> 550 [email protected] must check for new mail first
    Wed 2012-04-25 19:02:45: Connection timed out!
    Wed 2012-04-25 19:02:45: SMTP session terminated (Bytes in/out: 96/256)
    Wed 2012-04-25 19:02:46: ----------
    Wed 2012-04-25 19:20:11: Session 17159; child 1What could be the problem here? Any help would be greatly appreciated.

    Finally figured out the problem and fixed it. Now it is working.
    *"must check for new mail first"* means that before sending mail you have to check your mails (i.e. download) your mails first from the mail server, because the normal setting is for SMTP servers is that you can send mail only if you received a mail. So, when you receive a mail (i.e. check mail), your IP is recorded in the SMTP server log. Now if you send a mail, only mails with the IPs which has received any mail will be allowed to send mails outside.
    In order to only a send a mail without receiving any mail first you have to use SMTP authentication.
    I.e. After
    c := utl_smtp.open_connection(p_smtp_host, p_smtp_port);      
    utl_smtp.EHLO(c, p_smtp_host);  You have to give UID/PWD for the SMTP server like this:
    utl_smtp.command( c, 'AUTH LOGIN');
    utl_smtp.command( c, utl_raw.cast_to_varchar2( utl_encode.base64_encode( utl_raw.cast_to_raw( p_un))) );
    utl_smtp.command( c, utl_raw.cast_to_varchar2( utl_encode.base64_encode( utl_raw.cast_to_raw( p_pwd))) );However, when we sent like this we got a another SMTP error:
    554 Message is not RFC compliant; missing "Date" header To solve this do this: Go to Setup -> Default Domain & Servers, Servers, uncheck ...refuse
    messages which are not RFC compliant. That will allow MDaemon to accept  the malformed messages without date headers..Doing this solved the problem. Now we can send mails to outside mail boxes (like Gmail). In Gmail, when we checked the inbox there was no mail. It had gone the Spam folder. This is also important since you have to check the spam folder since Gmail will think it is spam. Once the mail is flagged as "not spam" it will start coming to your inbox.

  • Most email I send using warpdriveonline is received with the body blank. Haven't seen this problem in I.E. Not sure if it is the browser.

    I am using webmail from USA Cable, which uses warpdriveonline. They are still researching my problem but think it might be browser related. Most but not all email I send is received with the body blank. It is also blank in my sent mail.

    Carole,
    If it talks about your password it is probably a scam.
    Take a look in your purchase history and see if there has really been a purchase.
    Also you can refer to this document:  Identifying fraudulent "phishing" email

Maybe you are looking for