SAP BC : attachments not sent anymore to supplier

Hi All,
We are using SAP Business connector to send Bid invitations to our suppliers. since a few weeks
They don't receive the attachements anymore.
When i look in the lofiles i ca nsee this :
003616  [B2BCORE.0064.0002] HTTP Get HTTP://EBP.SAP.INTRANET.PROD:80/sap/ebp/zsapbc/173/DV3820%2003%2006%202008%201mondeparfait%20DD.pdf?attcget&ClId=4869649AEA66326CE10000000A2BDB22
003617  [B2BCORE.0064.0014] Opening Socket http://EBP.SAP.INTRANET.PROD:80/sap/ebp/zsapbc/173/DV3820%2003%2006%202008%201mondeparfait%20DD.pdf?attcget&ClId=4869649AEA66326CE10000000A2BDB22  proxy=gw-int.prod:80
003618  [B2BCORE.0038.0002] --> GET http://EBP.SAP.INTRANET.PROD:80/sap/ebp/zsapbc/173/DV3820%2003%2006%202008%201mondeparfait%20DD.pdf?attcget&ClId=4869649AEA66326CE10000000A2BDB22 HTTP/1.0
003619  [B2BCORE.0038.0002] --> User-Agent: Mozilla/4.0 [en] (WinNT; I)
00361A  [B2BCORE.0038.0002] --> Accept: image/gif, /
00361B  [B2BCORE.0038.0002] --> Host: EBP.SAP.INTRANET.PROD:80
00361C  [B2BCORE.0038.0002] --> Proxy-Authorization: Basic YWJ1c2luZXNzY29ubmVjdG9yOmFidXNpbjA0
00361D  [B2BCORE.0038.0002] --> Content-type: application/x-www-form-urlencoded
00361E  [B2BCORE.0040.0001] HTTP/1.1 503
00361F  [B2BCORE.0038.0002] <-- Cache-Control: no-cache
003620  [B2BCORE.0038.0002] <-- Pragma: no-cache
003621  [B2BCORE.0038.0002] <-- Content-Type: text/html; charset=utf-8
003622  [B2BCORE.0038.0002] <-- Proxy-Connection: close
003623  [B2BCORE.0038.0002] <-- Connection: close
003624  [B2BCORE.0038.0002] <-- Content-Length: 3036
003625  [B2BSERV.0048.9999] [B2BCORE.0064.9324] Server Error: 503 Service Unavailable
003626  [B2BCORE.0049.0006] Loop : index=3 depth=6
003627  [B2BCORE.0049.0008] Sequence : index=2 depth=5
003628  [B2BSERV.0056.0003] Unable to send mail. Illegal address
Has anyone an idea where the problem is?
I know XI but BC is really different...
Thanks,
Laurent TOUILLAUD

Hi,
Normally 503 error is returned when the server which you are sending the request is unavailable to process you request.
So the problem should be with the target server which you are connecting to send mail.
Thanks
SaNv...

Similar Messages

  • SUS - MM Scenario: notification mail not sent to all Supplier Users

    Hi,
    we're in a SUS-MM scenario and we publish Purchasing documents (PO and/or SAR) to SUS portal.
    The notification mail for new published documents are sent only to the e-mail address of the Supplier (imported from SAP to SUS) which is in the SAP Supplier Master data. But if the Admin supplier creates other users for the supplier (F1 / F2 / F3), the notification mail for new published PO/SAR are not sent to the mail address of F1 / F2 / F3 users. Is it the standard behavior or is there some missing customizing setting missing?
    Our customer wants that notification mail are sent to all the mail addresses of the Supplier Users.
    Has someone had this kind of requirement? and, if it is not achievable via standard customizing, which could be the right solution to meet this requirement?
    Thanks in advance

    Hi,
    This is a standard SAP process which SAP has provided,
    The other way is to develop a custom program,
    1) Select the Supplier.
    2) Check the available contact persons of the Supplier.
    3) When a document is created in ECC (Hope you are in MM-SUS), select the list of contact persons for Supplier. (I assume need a RFC FM to develop to SUS)
    4) Send a e-mail to all users linked with this Supplier.
    You can find the linked Contact persons in BP transaction and Table BUT000.
    Please change the Status of the Issue once your problem solved, other will get benefitted. If possible post the soulution.
    Thank you,
    Anil

  • APEX_MAIL - e-mail not sent anymore

    Hi,
    I created an evaluation application on apex.oracle.com. I created a page based on a procedure where a user can fill in e-mail addresses. The procedure should then send an e-mail to each e-mail address. This has worked for some time. I use APEX_MAIL.SEND to send the e-mails, and i can see them in the APEX_MAIL_QUEUE table. So far so good. But then even if i run APEX_MAIL.PUSH_QUEUE the e-mails are not sent. There are no errors in the MAIL_SEND_ERROR column.
    In the APEX_MAIL_LOG table I can see 10 e-mails, 8 of them were sent successfully (the 2 others had syntax issues in MAIL_TO, I was experimenting how strict "comma separated" was meant :-) )
    But the past 2 days I haven't been able to get any mail out. It just stacks in the queue table. I ran push_queue, without effect, and then deleted all rows in the queue to be sure the first row in the table contained a valid e-mail with existing and different mail_to and mail_from. But it has no use...
    I searched the forum but none of the existing posts solved this. Since I use apex.oracle.com I have no access to a lot of the settings, but as I said I have been able to get 10 mails out, so I suppose settings for SMTP server etc. are correct.
    Can anyone help me? Thanks,
    Jan

    I (Oracle) use(s) the latest version of apex I suppose? It's version 2.2.1.00.04
    I can't test the mailserver using PHP, as I don't know it's name/address, it's maintained by Oracle.
    My web application uses an evaluation workspace provided by Oracle, I don't have any control over "external" settings and configuration like the mail server. It is strange however that the first 10 e-mails got through (moved from APEX_MAIL_QUEUE to APEX_MAIL_LOG).
    Anyone knows about a limitation of the number of e-mails allowed by Oracle? Or anyone else uses one of these evaluation workspaces and is (un)able to send e-mail? I can't get ant mail out since november 30th.
    Thanks

  • Some POs are not sent to supplier via email

    Hello all,
    During the PO ordering to supplier via email, some POs are not sent to the supplier.
    the document output status is in incorrectly processed in the table PPFTTRIGG.
    Pls help me with any standard job is available to execute this incorrectly processed PO outputs.
    Regards
    Madhan

    Hello Maddan,
    If some of your action status have errors occured during processing, you cannot re-process PO edition: you have first to identify what was the error.
    So, get the application keys (PO number) from table PPFTTRIGG for which status is "2". Then, check in transactional what is exactly the error for each PO concerned.
    Regards.
    Laurent.

  • Few POs are not sent to supplier via email

    Hello all,
    During the PO ordering to supplier via email, some POs are not sent to the supplier may be due to object lock (temporary isue).
    The document output status (2) is in incorrectly processed in the table PPFTTRIGG.
    Pls help me with the parameter to be filled in the report "RSPPFPROCESS" so that i can create a variant and schedule daily.
    Regards
    Madhan

    Hello Maddan,
    If some of your action status have errors occured during processing, you cannot re-process PO edition: you have first to identify what was the error.
    So, get the application keys (PO number) from table PPFTTRIGG for which status is "2". Then, check in transactional what is exactly the error for each PO concerned.
    Regards.
    Laurent.

  • How to remove 1797 emails. stuck in inbox.  but not showing anymore - and i have the same problem wit the sent.  please help

    how to remove 1797 emails. stuck in inbox.  but not showing anymore - and i have the same problem wit the sent.  please help

    This is a user supported frum, so making threats really doesn't help, besides which it's not like any of us can really make a dent in Toshiba's bottom line despite how many people we think we can influence. Unless those people were standing in line to buy a Toshiba product cash in hand, and you pulled them out, it really doesn't add up for them.
    At this point it would probably be better for you to use the 800 number. Have all your e-mails ready to forward, if needed, to whoever you end up talking to. Don;t let them off the hook. An hour on the phone is much better than weeks passing e-mails through a support site. Also contest the charge with your bank or credit card.

  • My sent mail will not open anymore

    I have removed a lot of sent messages(8000>3000) and my sent folder will not open anymore.
    For a couple of times I opened my Thunderbird but no respons.
    The cursor is still turning cirkels.
    What can you suggest?
    Thanx in advance
    Kees

    If it is an IMAP account you might have to wait for an update/synchronization of your actions on the server.

  • NSP (SAP NW2004s ABAP AS 7.00 SP8) does not start anymore

    Hi all,
    I installed SAP NW2004s ABAP Trial Version SP8 and was able to work
    with it. Since today I get a timeout error when starting the Application Server.
    I tried to start the MaxDB instance with the SAP MMC but I do not know
    the user and/or password for the MaxDB User (I did not change the
    "Standard-User" provided during installation; unfortunately I do not remeber
    the credentials)
    Any ideas:
    - why the application server does not start anymore ?
    - what the credentials of the SAP DB Administrator are ?
    Thank you in advance for your help,
    Axel

    Hi Axel,
    this is a 90 day trial, though maybe you're already used it three month?
    the database used to run under control, control (usr, password), btu that changes from time to time....
    Regards,
    Benny

  • Sent an email and its missing from my mail.. It was not sent it and it is not in my Mac anymore. I invested a lot of time on them and I just lost them?

    I have lost two email in one week, after sent them. I just invested a lot of time in write them, and after select send it, the email just disappeared from my Mac and it was not sent it to nobody..

    Uninstalling and reinstalling iTunes has no affect on the media on the computer or the account it is linked to.
    If the media was purchased under another iTunes account, then it is permanently tied to that account.
    Using mulitple iDevices with one computer

  • Error : OBJECT NOT SENT

    Hi Experts,
    I am new to ABAP..
    I am facing one dump with the message "OBJECT NOT SENT"  working with User Exit only in Production Server.
    Kindly help.

    Hi ..
    Here it is...
    ABAP runtime errors    RAISE_EXCEPTION
           Occurred on     07.02.2007 at 10:55:17
    >> Short dump has not been completely stored. It is too big.
    Exception condition "OBJECT_NOT_SENT" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    A RAISE statement in the program "SAPLSOA2 " raised the exception
    condition "OBJECT_NOT_SENT".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    Object was not sent
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "RAISE_EXCEPTION"
    "SAPLSOA2 " or "LSOA2U01 "
    "SO_OBJECT_SEND"
    or
    "SAPLSOA2 " "OBJECT_NOT_SENT"
    or
    "SAPMV45A " "OBJECT_NOT_SENT"
    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.............. "46C"
    Application server....... "secerpa2"
    Network address.......... "10.20.1.151"
    Operating system......... "Windows NT"
    Release.................. "5.0"
    Hardware type............ "3x Intel 80686"
    Database server.......... "SECERPP1"
    Database type............ "ORACLE"
    Database name............ "PK1"
    Database owner........... "SAPR3"
    Character set............ "English_United State"
    SAP kernel............... "46D"
    Created on............... "Jul 25 2006 15:00:57"
    Created in............... "NT 4.0 1381 Service Pack 5 x86 MS VC++ 12.00"
    Database version......... "OCI_805_SHARE__OCI_7_API "
    Patch level.............. "2265"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
    8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
    SAP database version..... "46D"
    Operating system......... "Windows NT 4.0, Windows NT 5.0, Windows NT 5.1,
    Windows NT 5.2, , System build information:,
    , LCHN : 844749"
    User, transaction...
    Client.............. 200
    User................ "SG005"
    Language key........ "E"
    Transaction......... "VA22 "
    Program............. "SAPLSOA2 "
    Screen.............. "SAPMV45A 4001"
    Screen line......... 61
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLSOA2 " in
    "SO_OBJECT_SEND".
    The main program was "SAPMV45A ".
    The termination occurred in line 1264
    of the source code of program "LSOA2U01 " (when calling the editor 12640).
    Source code extract
    012340     PERFORM SOOD_UPDATE(SAPFSSO0) USING OBJECT_ID
    012350                                CHANGING OBJECT_HD
    012360                                         RCODE.
    012370
    012380
    012390
    012400
    012410   ************************************************************************
    012420   *  Only now it is possible to invoke some sap object with the method
    012430   * "RECEIVE" since the office object SOFM exist on the data base only
    012440   * after the SOFM_INSARR abaove (at least for sure)
    012450   ************************************************************************
    012460     IF OBJECT_RECEIVER_SIZE > 0.
    012470       PERFORM INVOKE_OBJECTS TABLES OBJECT_TABLE
    012480                              USING  OFFICE_OBJECT.
    012490   *   * for object which could not receive this document set status
    012500       PERFORM SET_OBJECT_FAILED TABLES OBJECT_TABLE
    012510                                        RECEIVER_TABLE.
    012520     ENDIF.
    012530   *----
    012540   * 14A.fill receiver list for export                                    *
    012550   *----
    012560   * move all receiver who are noz in receiver table because of an error
    012570   * into receiver table for retransfer
    012580     PERFORM PREPARE_RECLIST_FOR_RETURN TABLES RECEIVERS
    012590                                               RECEIVER_TABLE
    012600                                        USING  SENT_TO_ALL
    012610                                               F_RESUB_SENT.
    012620     IF F_OBJECT_NOT_SEND = ON AND
    012630        F_RESUB_SENT = OFF.
          RAISE OBJECT_NOT_SENT.
    012650     ENDIF.
    012660   *----
    012670   * only if realy at least one recipient go the object make the binding  *
    012680   * in case an binding could not be done the corresponding won't appear  *
    012690   * anymore in the table APPLICATION_OBJECT                              *
    012700   * binding will be done only for new documents
    012710   * 40C: If not object is given it will be look whether some obejcts are
    012720   * published by application
    012730   *----
    012740   *  IF SIZE-APPL_OBJECT LE 0.                               "note 313853
    012750   *    PERFORM LOOK_FOR_PUBLISHED_OBJECTS TABLES APPLICATION_OBJECT
    012760   *                                       USING  SIZE-APPL_OBJECT.
    012770   *  ENDIF.
    012780     IF SIZE-APPL_OBJECT GT 0              AND
    012790        ( SEND_PROC = NEW_OBJ_NO_FILE OR           " new document
    012800          SEND_PROC = NEW_OBJ_WI_FILE    ).
    012810       PERFORM BIND_OBJECTS TABLES APPLICATION_OBJECT
    012820                            USING  OFFICE_OBJECT_KEY
    012830                                   ALL_BINDING_DONE.
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 1
    SY-TABIX 1                             SY-DBCNT 1
    SY-FDPOS 2550                          SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1
    Chosen variables
    Name.......................... Contents.1........2........3....+....4
    OBJECT_TABLE
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120                                ##        ####
                                   22222222
                                   0000000
    OFFICE_OBJECT
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   22222222222
                                   00000000000
    ERO2                           ERO2
                                   4543222222222222222222222222222222222222
                                   52F2000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    SYST                           ########################d###############
                                   0000000000000000000000006000000000000000
                                   1000000010001000000010004000000000000000
    ... +  40                      ####ö     ##############################4###
                                   0000F00000000000000000000000000000003000
                                   1000690010000000100000000000000000004D00
    ... +  80                      ################ÿ#######################
                                   0000000000000000F00000000000000000000000
                                   0000000000000000F00000000000000000000000
    ... + 120                      ########################################
                                   00000000
                                   0000000
    OBJECT_TABLE[]                 Table[initial]
                                   0000FFFD
                                   0000FFFF
    RECEIVER_TABLE[]               ############################ ###########
                                   0000000000000000000000000000210000000000
                                   00000000000000000000000041300C0000001000
    ... +  40                      ############d###ÿÿÿÿ4########### â÷I####
                                   0000000000006000FFFF3000000000002EF40000
                                   4000400040004000FFFF4D007000430002790000
    ... +  80                      ############################Ì!##
                                   0000000000000000000000000000C200
                                   0000000000000000000000000000C100
    RECEIVER_TABLE                                   SR007
                                   2222222222222222225533322222222222222222
                                   0000000000000000003200700000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   22222222
                                   0000000
    EWSP                           EWSP
                                   4555222222222222222222222222222222222222
                                   5730000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    RSJOBINFO                                                      00000000
                                   2222222222222222222222222222222233333333
                                   0000000000000000000000000000000000000000
    ... +  40                      000000
                                   3333332222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80                      ####
                                   0000
                                   0000
    RECEIVERS[]                    #############################2##########
                                   0000000000000000000000000000930000000000
                                   0000000000000000000000004000021000001000
    ... +  40                      ################ÿÿÿÿ´###########°8÷I####
                                   0000000000000000FFFFB00000000000B3F40000
                                   1000100010001000FFFF4E007000430008790000
    ... +  80                      ############################²!##
                                   0000000000000000000000000000B200
                                   00000000000000000000000000002100
    RECEIVERS                        00000000#000000
                                   2233333333033333322222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80                         00000000000000B   SR007
                                   2223333333333333342225533322222222222222
                                   0000000000000000020003200700000000000000
    ... + 120
                                   22222222
                                   0000000
    SENT_TO_ALL
                                   2
                                   0
    F_RESUB_SENT
                                   2
                                   0
    GF_ACC                         2
                                   3
                                   2
    F_OBJECT_NOT_SEND              X
                                   5
                                   8
    ON                             X
                                   5
                                   8
    SPACE
                                   2
                                   0
    OFF
                                   2
                                   0
    MTRP                           MRP
                                   4552222222222222222222222222222222222222
                                   D200000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    MRKX                           MRKX
                                   4545222222222222222222222222222222222222
                                   D2B8000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    SIZE-APPL_OBJECT               1
                                   0000
                                   1000
    SEND_PROC                      A
                                   4
                                   1
    NEW_OBJ_NO_FILE                A
                                   4
                                   1
    NEW_OBJ_WI_FILE                B
                                   4
                                   2
    SCREEN                         MESSTXT8
                                   4455555322222222222222222222222222222222
                                   D533484800000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120                                              00001200000#####
                                   22222222
                                   0000000
    ATTA                           ATTA
                                   4554222222222222222222222222222222222222
                                   1441000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    Active calls / events
    No.... Type........ Name..........................
           Programm
           Include                                  Line
         1 FUNCTION     SO_OBJECT_SEND
           SAPLSOA2
           LSOA2U01                                  1264
         2 FORM         USEREXIT_SAVE_DOCUMENT
           SAPMV45A
           MV45AFZZ                                  1171
         3 FORM         BELEG_SICHERN
           SAPMV45A
           MV45AF0B_BELEG_SICHERN                    1115
         4 FORM         FCODE_SICH
           SAPMV45A
           MV45AF0F_FCODE_SICH                         18
         5 FORM         FCODE_BEARBEITEN
           SAPLV00F
           LV00FF0F                                    91
         6 FUNCTION     SCREEN_SEQUENCE_CONTROL
           SAPLV00F
           LV00FU02                                    58
         7 FORM         FCODE_BEARBEITEN
           SAPMV45A
           MV45AF0F_FCODE_BEARBEITEN                  109
         8 MODULE (PAI) FCODE_BEARBEITEN
           SAPMV45A
           MV45AI0F_FCODE_BEARBEITEN                   10
    Internal notes
    The termination occurred in the function "ab_jfune" of the SAP
    Basis System, specifically in line 1403 of the module
    "//bas/46D/src/krn/runt/abfunc.c#18".
    The internal operation just processed is "FUNE".
    The internal session was started at 20070207104801.
    Active calls in SAP kernel
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=3424)
    When      : 2/7/2007 10:55:18.262
    Threads   : 2
    Computer Name       : SECERPA2
    User Name           : sapservicePK1
    Number of Processors: 3
    Processor Type: x86 Family 6 Model 10 Stepping 1
    Windows Version     : 5.0 Current Build: 2195
    Stack Dump for Thread Id 510
    eax=00000000 ebx=03158da0 ecx=00400000 edx=00000000 esi=77f94086 edi=00000840
    eip=77f94091 esp=03158d84 ebp=03158da8 iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000297
    function :
             77f87106 58               pop     eax
             77f87107 e9f3800000       jmp     77f8f1ff
             77f8710c 8bc8             mov     ecx,eax
             77f8710e 81e1ff000000     and     ecx,0xff
             77f87114 0f84b3c40000     je      77f935cd
             77f8711a 0fbe8128e0f877   movsx  eax,byte ptr ds:88099d34=0f
             77f87121 e9a7b0ffff       jmp     77f821cd
             77f87126 b848000000       mov     eax,0x48
             77f8712b 8d542404         lea     edx,[esp+0x4]          ss:4b59ec67=????????
             77f8712f cd2e             int     2e
             77f87131 c22800           ret     0x28
             77f87134 ff742410         push    dword ptr    ss:4b59ec67=????????
             77f87138 6a00             push    0x0
             77f8713a 6a00             push    0x0
             77f8713c ff742418         push    dword ptr    ss:4b59ec67=????????
             77f87140 ff742418         push    dword ptr    ss:4b59ec67=????????
             77f87144 ff742418         push    dword ptr    ss:4b59ec67=????????
             77f87148 e8b8800000       call    77f8f205
             77f8714d c21000           ret     0x10
             77f87150 55               push    ebp
             77f87151 8bec             mov     ebp,esp
             77f87153 51               push    ecx
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    053ffcb0 00c310ac 00000a30 00000000 00000007 03325ae0 ntdll!
    List of ABAP programs affected
    Type
    Program
    Gen. date  time
    LoadSize
    Prg
    SAPMV45A
    20.10.2005 17:39:06
    1901568
    Prg
    SAPMSSYD
    14.08.2000 15:39:21
    16384
    Prg
    SAPFSYSCALLS
    21.12.1999 19:32:31
    7168
    Prg
    SAPFV45C
    01.02.2006 18:21:05
    549888
    Prg
    SAPFV45K
    12.12.2004 11:00:10
    623616
    Prg
    SAPFV45E
    12.12.2004 11:00:10
    732160
    Prg
    SAPFV45P
    12.12.2004 11:00:10
    1343488
    Prg
    SAPFV45S
    12.12.2004 11:00:10
    765952
    Prg
    SAPLAIEV
    26.06.2002 23:34:53
    14336
    Prg
    CL_OS_TRANSACTION_END_NOTIFIER
    20.06.2004 17:53:14
    8192
    Prg
    SAPLSYST
    26.06.2002 23:13:17
    38912
    Prg
    SAPLSBDC
    26.06.2002 23:38:38
    66560
    Prg
    SAPLNDAC
    14.10.1999 23:32:54
    7168
    Prg
    SAPLBUOP
    12.12.2004 10:53:50
    69632
    Prg
    SAPLITSR
    20.06.2004 18:07:30
    87040
    Typ
    TPS01
    20.02.1998 09:19:57
    2048
    Prg
    SAPLASTAT_TRIG
    01.04.2003 19:09:20
    12288
    Typ
    T180
    20.02.1998 09:17:43
    2048
    Prg
    SAPLV00F
    13.12.2004 10:28:00
    68608
    Typ
    T185V
    10.11.1999 17:45:26
    4096
    Prg
    SAPLV86E
    12.12.2004 10:57:15
    329728
    Prg
    SAPLVFSP
    11.12.2004 16:23:47
    251904
    Prg
    SAPLDLOG
    04.01.2000 19:06:44
    7168
    Prg
    SAPLVTXC
    26.06.2002 23:35:28
    24576
    Prg
    SAPLV45T
    12.12.2004 11:55:08
    137216
    Typ
    STXDRNAME
    26.02.1999 14:48:42
    2048
    Prg
    SAPLSTXD
    20.06.2004 17:53:32
    407552
    Prg
    SAPCNVE
    04.01.2000 19:06:37
    7168
    Prg
    SAPLLANG
    04.01.2000 19:06:49
    9216
    Prg
    SAPLV01Z
    12.12.2004 10:59:08
    205824
    Prg
    SAPLCLFM
    12.12.2004 10:58:14
    677888
    Prg
    SAPLCUOB
    11.12.2004 15:53:45
    34816
    Prg
    SAPLCLSE
    11.12.2004 16:43:02
    177152
    Prg
    SAPLCTMS
    12.12.2004 10:58:25
    940032
    Prg
    SAPLCTCV
    12.12.2004 10:58:25
    192512
    Prg
    SAPLCTCF
    01.04.2003 20:49:26
    24576
    Prg
    SAPLV01P
    12.12.2004 10:57:28
    163840
    Prg
    SAPFV45L
    12.12.2004 11:00:10
    450560
    Prg
    SAPLV45A
    12.12.2004 11:00:10
    871424
    Typ
    TPAER
    15.04.1998 00:15:36
    2048
    Typ
    VBMUE
    12.04.1999 16:17:03
    1024
    Prg
    SAPLSUSE
    20.06.2004 17:33:55
    44032
    Typ
    TCDCOUPLES
    10.04.2002 10:24:49
    2048
    Prg
    SAPLJ1AZ
    11.12.2004 16:44:41
    29696
    Typ
    TWPA
    03.05.1999 19:52:52
    5120
    Prg
    SAPLVEHS
    12.12.2004 11:00:10
    105472
    Prg
    SAPLPSCONV
    26.06.2002 23:57:31
    11264
    Prg
    SAPLSUNI
    20.06.2004 17:33:13
    138240
    Typ
    TFDIR
    29.07.1998 19:49:08
    2048
    Prg
    SAPLCJPN
    12.12.2004 10:58:11
    310272
    Prg
    SAPLSCNT
    26.06.2002 23:35:28
    28672
    Prg
    SAPLSVSM
    26.06.2002 23:35:28
    25600
    Prg
    SAPLSGUI
    26.06.2002 23:35:28
    33792
    Prg
    SAPLSTTM
    26.06.2002 23:38:39
    84992
    Prg
    CL_DATAPROVIDER===============
    26.06.2002 23:35:25
    51200
    Typ
    OBJ_RECORD
    14.02.1998 08:30:43
    2048
    Prg
    SAPLSTUP
    20.06.2004 17:52:24
    95232
    Prg
    SAPLCNDP
    26.06.2002 23:35:27
    181248
    Prg
    SAPFGUICNTL
    01.04.2003 18:42:31
    20480
    Prg
    SAPLOLEA
    26.06.2002 23:33:43
    81920
    Prg
    SAPLSFES
    20.06.2004 17:33:13
    141312
    Prg
    SAPLGRFC
    26.06.2002 23:33:43
    16384
    Prg
    SAPSHDTV
    01.04.2003 19:09:39
    36864
    Typ
    SHDSTU
    14.12.1998 23:15:34
    1024
    Typ
    SHDSTCIU
    14.12.1998 23:15:34
    1024
    Prg
    CL_GUI_PROPS_CONSUMER=========
    01.04.2003 18:26:40
    26624
    Prg
    CL_DYNAMIC_GUI_EXTENSIONS=====
    11.02.2000 14:36:06
    55296
    Prg
    CL_GUI_DATAMANAGER============
    01.04.2003 18:43:20
    82944
    Typ
    VBAKKOM
    10.04.2002 09:50:02
    22528
    Prg
    /1BCDWBEN/SAPLVEN0000
    01.04.2003 20:55:35
    145408
    Prg
    SAPLSENA
    04.01.2000 19:06:53
    28672
    Prg
    SAPLV45K
    12.12.2004 11:00:10
    110592
    Prg
    SAPLV45I
    12.12.2004 11:00:17
    476160
    Typ
    VBAK
    23.11.2002 15:53:28
    15360
    Prg
    SAPLV21F
    12.12.2004 11:00:10
    142336
    Typ
    TVAK
    26.03.1999 15:09:05
    13312
    Typ
    TVAKT
    14.02.1998 14:38:43
    2048
    Typ
    TVKO
    06.05.1998 02:22:47
    4096
    Prg
    SAPLSZA0
    05.01.2007 15:17:56
    2089984
    Typ
    TSAD3T
    14.02.1998 17:01:10
    2048
    Typ
    ADCNTRYQU
    04.01.2000 18:08:16
    1024
    Typ
    ADRSTATUS
    29.01.1997 19:04:23
    1024
    Typ
    ADRC
    10.03.1999 18:47:25
    11264
    Typ
    ADRCT
    28.08.1997 08:35:27
    2048
    Typ
    ADRG
    03.07.1996 22:44:47
    1024
    Prg
    SAPLSZAD
    05.01.2007 15:17:50
    23552
    Prg
    SAPLSADR
    20.06.2004 17:53:59
    203776
    Typ
    T005
    14.10.1999 22:02:32
    7168
    Typ
    T001
    12.03.1999 15:15:31
    9216
    Typ
    TVTW
    27.05.1992 18:19:33
    1024
    Typ
    TSPA
    10.06.1992 12:18:00
    1024
    Typ
    TVBUR
    25.07.1996 16:33:30
    2048
    Typ
    TVKGR
    14.07.1993 02:32:49
    1024
    Typ
    TVTA
    03.09.1997 03:28:25
    3072
    Typ
    VBKD
    08.04.2002 15:08:30
    10240
    Prg
    SAPLV05I
    12.12.2004 10:57:14
    486400
    Prg
    SAPLSZA13
    26.06.2002 23:39:42
    12288
    Prg
    SAPLV05E
    12.12.2004 10:57:15
    405504
    Typ
    TPAR
    27.08.1994 21:59:27
    2048
    Prg
    SAPLV08D
    11.12.2004 15:57:13
    20480
    Typ
    KNA1
    03.04.2003 18:05:27
    16384
    Prg
    SAPLV09D
    12.12.2004 10:57:17
    168960
    Typ
    ADR2
    25.01.1999 13:08:51
    3072
    Typ
    ADRT
    14.02.1998 05:38:23
    2048
    Prg
    SAPLSZA8
    20.06.2004 17:34:25
    73728
    Typ
    VBADR
    11.12.2004 15:51:24
    5120
    Prg
    SAPLVS01
    03.04.2003 18:05:31
    179200
    Typ
    TPAKD
    26.10.1994 17:32:29
    1024
    Prg
    SAPLXV09
    04.01.2000 19:06:57
    13312
    Prg
    SAPLWY14
    11.12.2004 15:57:26
    23552
    Typ
    KNVK
    01.04.1998 02:08:10
    9216
    Typ
    ADRP
    14.04.1998 11:18:32
    6144
    Typ
    ADRGP
    03.07.1996 22:44:47
    1024
    Typ
    ADCP
    23.04.1998 14:45:51
    2048
    Prg
    SAPLHRMR
    16.08.2000 17:00:24
    26624
    Prg
    SAPLHRAC
    08.04.2002 15:01:41
    55296
    Prg
    SAPLSXCH
    20.06.2004 17:53:46
    80896
    Typ
    V_EXT_ACT
    14.10.1999 22:16:55
    2048
    Typ
    ACT_IMP
    25.01.1999 12:55:20
    1024
    Prg
    CL_HRPAD00AUTH_CHECK_STD======
    16.08.2000 17:03:23
    111616
    Typ
    P0001
    16.08.2000 17:00:14
    6144
    Typ
    T77S0
    08.03.1992 17:36:54
    1024
    Prg
    SAPLHRIPA02CENTRAL_PERSON
    09.12.1999 20:12:54
    25600
    Typ
    PA0105
    03.09.1997 03:22:10
    4096
    Prg
    SAPLHRPAPAXX_T777D_READ
    12.04.1999 17:50:35
    15360
    Typ
    T777D
    25.03.1999 15:43:54
    5120
    Prg
    SAPLSEQ0
    20.06.2004 17:33:45
    87040
    Typ
    PS0001
    13.09.1996 17:21:13
    4096
    Prg
    SAPLSDIF
    20.06.2004 17:11:50
    256000
    Prg
    SAPLSDNT
    01.04.2003 18:57:26
    188416
    Typ
    T522T
    28.08.1997 09:05:45
    2048
    Typ
    T500P
    03.09.1997 03:24:54
    3072
    Prg
    SAPLHRPAPAXX_T582S_READ
    12.04.1999 17:50:35
    10240
    Typ
    T582S
    14.02.1998 11:43:07
    2048
    Prg
    SAPLVADR
    11.12.2004 16:45:16
    67584
    Prg
    SAPLV09A
    12.12.2004 10:59:08
    493568
    Prg
    SAPLV46B
    12.12.2004 11:00:10
    67584
    Prg
    SAPLSWUG
    20.06.2004 17:52:24
    265216
    Typ
    SWOTOBJID
    04.05.1995 15:20:52
    2048
    Typ
    SWHACTOR
    04.04.1995 16:18:07
    1024
    Prg
    CL_GOS_MANAGER================
    26.06.2002 23:35:25
    24576
    Prg
    CL_GOS_VIEW_MANAGER===========
    26.06.2002 23:35:25
    29696
    Typ
    SGOS_MVOBJ
    01.12.1999 08:16:05
    2048
    Prg
    SAPLSUU1
    20.06.2004 17:53:44
    181248
    Typ
    USR02
    26.06.2002 23:13:21
    5120
    Typ
    USREFUS
    01.04.2003 18:41:15
    1024
    Typ
    BORIDENT
    28.08.1997 08:38:50
    1024
    Prg
    CL_GOS_TOOLBOX_MODEL==========
    20.06.2004 17:53:55
    39936
    Typ
    SGOS_MODL
    08.02.2000 16:42:30
    3072
    Prg
    SAPLBDLS
    14.08.2000 15:20:53
    13312
    Typ
    T000
    11.09.1997 10:17:18
    3072
    Prg
    CL_GOS_PUBLICATION============
    26.06.2002 23:35:25
    24576
    Prg
    CL_GUI_OBJECT=================
    26.06.2002 23:35:25
    1024
    Prg
    CL_GUI_CFW====================
    01.04.2003 19:10:31
    196608
    Typ
    TOLE
    29.07.1998 19:56:01
    2048
    Prg
    SAPLSGOSHIST
    26.06.2002 23:40:40
    56320
    Prg
    SAPFSGOS
    26.06.2002 23:40:32
    13312
    Typ
    SGOSHIST
    14.10.1999 22:09:01
    2048
    Prg
    SAPLURFC
    04.01.2000 19:08:13
    14336
    Prg
    CL_GOS_STARTER================
    26.06.2002 23:35:25
    21504
    Prg
    CL_GUI_CONTROL================
    26.06.2002 23:40:31
    117760
    Prg
    CL_GUI_TOOLBAR================
    26.06.2002 23:35:25
    72704
    Prg
    CL_GUI_GOS_CONTAINER==========
    26.06.2002 23:35:25
    38912
    Typ
    CFW_LINK
    01.12.1999 12:16:48
    2048
    Prg
    CL_GUI_CONTAINER==============
    26.06.2002 23:35:25
    58368
    Prg
    SAPLCNTH
    26.06.2002 23:40:20
    26624
    Prg
    SAPLSCONTROLINFO
    04.01.2000 19:06:52
    13312
    Prg
    SAPLSCONTROLSTATUSCHECK
    04.01.2000 19:06:52
    10240
    Typ
    USR05
    09.07.1997 23:46:52
    1024
    Typ
    CNTLWARN
    25.01.1999 13:09:44
    2048
    Prg
    SAPLICON
    14.08.2000 15:39:37
    25600
    Prg
    %_CICON
    14.08.2000 15:39:36
    55296
    Typ
    KUAGV
    01.03.1999 13:28:45
    9216
    Typ
    KNVV
    30.11.1999 10:18:28
    9216
    Typ
    KUPAV
    19.02.2001 12:29:12
    7168
    Prg
    SAPLSUSM
    01.04.2003 18:26:37
    35840
    Typ
    USR21
    10.03.1999 18:32:06
    2048
    Prg
    SAPLSUGS
    04.01.2000 19:06:54
    15360
    Prg
    SAPLSUG2
    04.01.2000 19:06:54
    37888
    Typ
    CVERS
    26.04.1999 17:21:32
    2048
    Typ
    SVERS
    30.07.1992 18:39:23
    1024
    Typ
    UVERS
    16.07.1997 14:46:33
    3072
    Typ
    V_ADDR_USR
    27.08.1999 18:32:38
    15360
    Typ
    TSADCORR
    20.06.2004 17:32:36
    1024
    Typ
    T005T
    14.02.1998 10:26:48
    2048
    Typ
    TSAD3
    16.07.1997 14:46:19
    2048
    Prg
    CL_EXITHANDLER================
    20.06.2004 17:33:43
    13312
    Prg
    CL_ABAP_TYPEDESCR=============
    04.01.2000 19:06:00
    17408
    Prg
    CL_ABAP_ELEMDESCR=============
    04.01.2000 19:06:00
    13312
    Prg
    CL_ABAP_DATADESCR=============
    04.01.2000 19:06:00
    11264
    Prg
    CL_ABAP_REFDESCR==============
    04.01.2000 19:06:00
    14336
    Prg
    CL_ABAP_STRUCTDESCR===========
    04.01.2000 19:06:00
    16384
    Prg
    CL_ABAP_COMPLEXDESCR==========
    04.01.2000 19:06:00
    11264
    Prg
    CL_ABAP_TABLEDESCR============
    04.01.2000 19:06:00
    16384
    Prg
    CL_ABAP_CLASSDESCR============
    04.01.2000 19:06:00
    23552
    Prg
    CL_ABAP_OBJECTDESCR===========
    04.01.2000 19:06:00
    28672
    Prg
    CL_ABAP_INTFDESCR=============
    04.01.2000 19:06:00
    21504
    Prg
    IF_EX_ADDR_PRINTFORM_SHORT====
    01.04.2003 18:43:42
    7168
    Typ
    SXS_INTER
    30.11.1998 15:55:16
    1024
    Prg
    SAPLSEXV
    20.06.2004 17:11:44
    157696
    Prg
    CL_EX_ADDR_PRINTFORM_SHORT====
    01.04.2003 18:43:42
    15360
    Prg
    CL_EXIT_MASTER================
    01.02.2000 09:29:10
    10240
    Typ
    V_EXT_IMP
    14.10.1999 22:16:55
    2048
    Prg
    SAPLSCP5
    20.06.2004 17:11:41
    23552
    Typ
    T683V
    24.02.1999 03:31:49
    2048
    Typ
    KUWEV
    01.12.1999 15:13:15
    11264
    Typ
    KURGV
    23.04.1998 14:51:01
    7168
    Typ
    KNVA
    10.07.1993 03:46:26
    5120
    Prg
    SAPLV52E
    12.12.2004 11:55:16
    506880
    Typ
    KNEX
    15.04.1998 00:23:05
    4096

  • CO54: Message is not sent to any destination: Commit Work is getting failed

    Hello,
    While processing the Messages from XFP to SAP Update is getting terminated due to the use of Commit Work. SAP Note 147467 - Update termination when sending process messages has been referred which is for 4.6C, but we are in ECC6.0.
    While processing the message in second iteration Commit Work triggres and Update happens in the data base.
    Following Issue is only concerned with Nested HUs
    T-Code used CO54
    Following are the analysis:
    it looks like u201CCreate and Post a Physical Inventory Docu201D is failing in the initial processing because the inventory doc is created when the Transfer Order to the PSA (or the TO from the PSA) is not yet completed (quant is still locked somehow).
    CO54, process message category=ZHU_CONS: HU to be consumed is a nested pallet (unpacking/ repacking and TOs to/from) and qty to consume is greater that HU qty in SAP (creation of a physical inventory doc is required).
    1. The error occurs while clearing the inventory posting for the physical inventory document.
    2. The surprising factor is the u201CProcess Messageu201D is not processed correctly for the first time.
    3. Indeed it is successfully processed without any error if you do process it second time.
    Error Log from C054 T-Code.
    02.08.2010                                         Dynamic List Display                                                1
    Type
    Message text
    LTxt
    Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
    Message to be sent to destination:
    ZHGI ZPP_0285_XFP_GOODSISSUE Individual Processing Is Active
    => Message will be sent to destination (check log for destination)
    Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
    Message destination ZPP_0285_XFP_GOODSISSUE triggered COMMIT WORK
    Input parameters OK, passed to source field structure
    Step 0: Now checking if scenario with HU
    Step 2: Scenario with HU, Now checking if HU nested
    Step 3: HU nested, checking if HU in repack area
    Step 4: HU not in repack area, moving it to repack area
    HU moved to repack area, TO number 0000000873
    Step 5: Depacking nested HU...
    Nested HU depacked, HU pallet n°: 00176127111000461994
    Steps 6-7: Moving back HUs to supply storage type / bin...
    HU 00376127111000462001 moved back to original area with TO number 0000000875
    Steps 6-7: Moving back HUs to supply storage type / bin...
    No need to move back HU 00176127111000461994 (not in table LEIN)
    Step 8: Checking if HU fully used and quantity matches HU system quantity
    HU not fully used but picked quantity > HU quantity: inventory necessary
    Step 9: Inventory needed, creating physical inventory document...
    Physical inventory document 0000000126 created
    Step 10: Adding weighted quantity on inventory document...
    Weighted quantity entered in document 0000000126
    Step 11: Posting rectification in inventory document 0000000126...
    Physical inventory document 0000000126 rectified
    Error: rectification for doc 0000000126 not updated in DB!
    => Destination ZHGI ZPP_0285_XFP_GOODSISSUE can currently not process the message
    => Message is not sent to any destination
    The errors in SM13 for this contain the program SAPLZPP_0285_HUINV_ENH (creating/changing the HUM physical inventory doc). WM Function module L_LK01_VERARBEITEN is also involved.
    From SM13, it displays the following piece of code in include LL03TF2M (read the LEIN table=Storage Units table):
    WHEN CON_LK01_NACH.
           IF (LEIN-LGTYP = LK01-NLTYP AND         
                 LEIN-LGPLA = LK01-NLPLA) OR
                  NOT P_LEDUM IS INITIAL.
           ELSE.
    Das ist der Fall einer TA-Quittierung wo Von-Hu = Nach-HU ist und sofort die WA-Buchung erfolgt. Dann steht die HU noch auf dem Von-Platz, daher darf hier kein Fehler kommen, sondern es wird ein. Flag gesetzt, daß verhindert daß die LE fortgeschrieben wird.
             FLG_NO_LE_UPDATE = CON_X.
            MESSAGE A558 WITH P_LENUM.
           ENDIF.
    Translation in English of the German text via Google:
    "This is the case where confirmation of a TO source-HU = destination-HU, and now the WA (Good Issue?)- made book. Then, the HU is still on the From-space may therefore come here not a mistake, but it sets a flag that prevents that the LE is updated."
    Thanks and Regards,
    Prabhjot Singh
    Edited by: Prabhjot  Singh on Aug 2, 2010 4:39 PM

    Hope you have carried out following things in Production ( Please refer to SAP help before actually doing it in production).
    1. Transport the predefined characteristics from the SAP reference client (000) to your logon client.
    2. Adopt Predefined Message Categories - In this step, you copy the process message categories supplied by SAP from internal tables as Customizing settings in your plants.

  • How to extract data from custom made Idoc that is not sent

    Hi experts,
    Could you please advise if there is a way how to extract data from custom made idoc (it collects a lot of data from different SAP tables)? Please note that this idoc is not sent as target system is not fully maintained.
    As by now, we would like to verify - what data is extracted now.
    Any help, would be appreciated!

    Hi,
    The fields that are given for each segment have their length given in EDSAPPL table. How you have to map is explained in below example.
    Suppose for segment1, EDSAPPL has 3 fields so below are entries
    SEGMENT          FIELDNAME           LENGTH
    SEGMENT1         FIELD1                   4
    SEGMENT1         FIELD2                   2
    SEGMENT1         FIELD3                   2
    Data in EDID4 would be as follows
    IDOC           SEGMENT                          APPLICATION DATA
    12345         SEGMENT1                        XYZ R Y
    When you are extracting data from these tables into your internal table, mapping has to be as follows:
    FIELD1 = APPLICATIONDATA+0(4)        to read first 4 characters of this field, because the first 4 characters in this field would belong to FIELD1
    Similarly,
    FIELD2 = APPLICATIONDATA+4(2).
    FIELD3 = APPLICATIONDATA+6(2).  
    FIELD1 would have XYZ, FIELD2 = R, FIELD3 = Y
    This would remain true in all cases. So all you need to do is identify which fields you want to extract, and simply code as above to extract the data from this table.
    Hope this was helpful in explaining how to derive the data.

  • Web-dynpro application -ERROR: ICF service node "/sap/bc/webdynpro/sap/zqm_cto_arr_general1" does not exist (see SAP Note 1109215) (termination: ERROR_MESSAGE_STATE)

    i have created my web-dynpro application in development. and sent to quality . whenever i will execute my dynpro in quality  i got one message
    ERROR: ICF service node "/sap/bc/webdynpro/sap/zqm_cto_arr_general1" does not exist (see SAP Note 1109215) (termination: ERROR_MESSAGE_STATE)
    whenever i saw  sicf  transaction my web-dynpro is not seen . my dynpro application name is more then 15 character. what i will do . please give me valuable suggestion.....

    Hi Ashok,
                   for your requirement the application is not exist in particular place. It means, the webdynpro application is saved at different package or different location.
                  Please change the webdynpro component name and save it in particular request in package, then transport it to quality ..(development server )
    then go to SICF  t.code .. sap->bc->webdynpro->sap->find  out your application and activate the service of your webdynpro application.
    Now test it ... this solution might helpful to you .
    Regards,
    Naveen M

  • Attaching files as Attachments, not INLINE attachments

    I'm sending images to a client who's on Lotus Notes (7.02). We have discovered an issue with inline attachments in Lotus, where attachments can only be drag and dropped out of Lotus if the attachment was NOT sent as an inline attachment.
    This was tested in Thunderbird by changing the mail.contentdispositiontype preference as per this article:
    http://kb.mozillazine.org/Sendattachments_as_realattachments
    In any event, the client is not able to switch from Lotus to OS X mail or any other client– as this is a large organization.
    The issue is easily fixed on my end by using Thunderbird– but that's not the path that I'd like to take–I'd like to know how to address this in OS X Mail.
    I've already clicked on windows friendly, send at end of message, and tried right clicking and setting the attachment to 'show as icon'– all in an attempt to get OS X Mail to send 'real' attachments, as opposed to inline.
    Does anyone know of a .plist file, or a hidden preference that can be enabled to address this?
    Thanks!

    exactly the same with on of my clients (Lotus, blocker, large org...). I have filed an problem case on this.
    http://www.ietf.org/rfc/rfc2183.txt
    http://www.iana.org/assignments/mail-cont-disp
    My understanding is Apple Mail has no outgoing option (GUI) to set the "Mail Content Disposition Value" to "attachment" (RFC2183 2.2) to have an "user controlled display" as opposed to "inline" (RFC2183 2.1) and "displayed automatically" on the side of the recipient.
    In short the Summary (RFC2183 4.):
    +"Content-Disposition takes one of two values, `inline' and `attachment'. `Inline' indicates that the entity should be immediately displayed to the user, whereas `attachment' means that the user should take additional action to view the entity."+
    I also suggest we should also have a preference for incoming mail to not display content at all as "inline" regardless of the Content-Disposition Value if we want to.
    Btw. I am also missing the option (MDN) to request a notification that a message is delivered/read.
    http://www.ietf.org/rfc/rfc3798.txt

  • Attachments not showing as attachments in mail

    Why are my attachments not showing up as attachments when recieved. They are sent from Mail as windows "friendly" - but never the less always show up inlaid in the mail. The recipient then have to ctrl clik on the documents, save them on the harddrive before being able to fx print.
    very annoying indeed - please can anyone help on this :-)

    thanks for quick responce - but the problem lies with the recievers of MY mails - where the attachments is only inlaid and not showing as an attachment. The reciever then have problems opening attachments in i.e. Photoshop, and they cannot print the attachments directly from the mail..

Maybe you are looking for