Document not sent error

Hi all,
I am using the FM SO_NEW_DOCUMENT_ATT_SEND_API1 to send the file to external address. It worked fine on dev and after transporting to Q, the same prog is failing and giving the error as DOCUMENT NOT SENT.
I tried to debug the FM also to understand but no clue yet.
Any help would really be appreciate
regards
AG

Hi,
I guess basis settings are missing in your quality server.
Please check the below link and ask your basis consultant to configure the external mail server.
[http://www.sap-img.com/basis/basis-faq.htm]
Regards,
Naresh.

Similar Messages

  • Document Not sent error while sending pdf attchments in smartforms

    Hi All,
    I am trying to send the smartforms output in the PDF format as an attachment via email but it seems to be not working for me.
    here is the piece if code i'm trying to use
    Convert smartform OTF Table data to PDF
      CALL FUNCTION 'CONVERT_OTF'
           EXPORTING
                format                = 'PDF'
                max_linewidth = 132
           IMPORTING
                bin_filesize          = pdf_size
           TABLES
                otf                   = w_job_info-otfdata
                lines                 = pdf_table
           EXCEPTIONS
                err_max_linewidth     = 1
                err_format            = 2
                err_conv_not_possible = 3
                OTHERS                = 4.
    ENDIF.
    IF P_PDF = 'X'.
      CALL FUNCTION 'DOWNLOAD'
       EXPORTING
         BIN_FILESIZE                  = pdf_size
         FILENAME                      = 'C:
    SSFPDF.PDF '
         FILETYPE                      = 'BIN'
        TABLES
          DATA_TAB                      = pdf_table
      EXCEPTIONS
        INVALID_FILESIZE              = 1
        INVALID_TABLE_WIDTH           = 2
        INVALID_TYPE                  = 3
        NO_BATCH                      = 4
        UNKNOWN_ERROR                 = 5
        GUI_REFUSE_FILETRANSFER       = 6
        CUSTOMER_ERROR                = 7
        OTHERS                        = 8
      IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDIF.
    IF P_EML = 'X'.
    Convert PDF from 132 to 255.
    LOOP AT pdf_table.
    Replacing space by ~
    TRANSLATE pdf_table USING ' ~'.
    CONCATENATE w_buffer pdf_table INTO w_buffer.
    ENDLOOP.
    Replacing ~ by space
    TRANSLATE w_buffer USING '~ '.
    DO.
    i_record = w_buffer.
    Appending 255 characters as a record
    APPEND i_record.
    SHIFT w_buffer LEFT BY 255 PLACES.
    IF w_buffer IS INITIAL.
    EXIT.
    ENDIF.
    ENDDO.
    Object with PDF.
    i_objbin[] = i_record[].
    Refresh: i_reclist,
    i_objtxt,
    i_objbin,
    i_objpack.
    clear w_objhead.
    Object with PDF.
    i_objbin[] = i_record[].
    DESCRIBE TABLE i_objbin LINES v_lines_bin.
    Object with main text of the mail.
    i_objtxt = 'Find attached the output of the smart form.'.
    APPEND i_objtxt.
    i_objtxt = 'Regards,'.
    APPEND i_objtxt.
    i_objtxt = 'J.Jayanthi'.
    APPEND i_objtxt.
    DESCRIBE TABLE i_objtxt LINES v_lines_txt.
    Document information.
    w_doc_chng-obj_name = 'Smartform'.
    w_doc_chng-expiry_dat = sy-datum + 10.
    w_doc_chng-obj_descr = 'Smart form output'.
    w_doc_chng-sensitivty = 'F'. "Functional object
    w_doc_chng-doc_size = v_lines_txt * 255.
    CLEAR i_objpack-transf_bin.
    i_objpack-head_start = 1.
    i_objpack-head_num = 0.
    i_objpack-body_start = 1.
    i_objpack-body_num = v_lines_txt.
    i_objpack-doc_type = 'RAW'.
    APPEND i_objpack.
    Packing as PDF.
    i_objpack-transf_bin = 'X'.
    i_objpack-head_start = 1.
    i_objpack-head_num = 1.
    i_objpack-body_start = 1.
    i_objpack-body_num = v_lines_bin.
    i_objpack-doc_type = 'PDF'.
    i_objpack-obj_name = 'Smartform'.
    CONCATENATE 'Smartform_output' '.pdf'
    INTO i_objpack-obj_descr.
    i_objpack-doc_size = v_lines_bin * 255.
    APPEND i_objpack.
    Document information.
    CLEAR i_reclist.
    e-mail receivers.
    i_reclist-receiver = '[email protected]'.
    i_reclist-express = 'X'.
    i_reclist-rec_type = 'U'.
    append i_reclist.
    Sending mail.
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        document_data = w_doc_chng
        put_in_outbox = 'X'
      TABLES
        packing_list = i_objpack
        object_header = w_objhead
        contents_hex = i_objbin
        contents_txt = i_objtxt
        receivers = i_reclist
      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.
    the return code is 2. Can u pls identify the mistake that i am doing? Pls suggest the solution to make this work.
    Thanks in advance,
    Rashmi

    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

  • Getting "messages not sent" error from Yahoo e-mail outbox folder

    I tried forwarding two e-mails with attachments that somehow got stuck in my outbox.  I continually get the "x messages not sent" error message but when I click on the error and go to the outbox, I am unable to delete the messages or perform any other action because it says the messages are in the progress of being sent.  Any thoughts on how to clear this error?

    RegisMcGarry wrote:
    I tried forwarding two e-mails with attachments that somehow got stuck in my outbox.  I continually get the "x messages not sent" error message but when I click on the error and go to the outbox, I am unable to delete the messages or perform any other action because it says the messages are in the progress of being sent.  Any thoughts on how to clear this error?
    Simple delete the yahoo mail from the native email app. then go to the google play store and download the stand alone YMail app and you need only to enter your yahoo mail user name and password and it will work perfectly.
    Good Luck

  • Request IDoc : Application document not posted  ERROR

    Hi All,
    When I am executing Info Package in BW PROD the system is showing error
    Transfer (IDocs and TRFC): Errors occurred
    Request IDoc : Application document not posted
    I searched the forums but no such kind of error regarding this senario.This problem is for all IP in BW PROD.
    Can anyone help in this issue.
    Thanks,
    Mayur

    In SCC4 the following
    in we21
    Please do not make any changes to these parameters by urself ,ask ur basis team to check it and change it accordingly ....

  • Document not found error in sourcing

    Friends,
    We are implementing SRM 5.0 in ECS. I have created a shopping cart. It is approved and is purchaser's worklist. When we go to sourcing(BBPSOCO01) and add it to my workarea and then click "create purchase order", I get a message "Document 1000000341 does not exist ". if I click on the create PO again a Purchase order is created but is in held status. I get the same error in this PO also.The message doesn't even have any number. Please any help will be appreciated.

    Hi
    <b>Please go through the following SAP OSS Notes as well -></b>
    <u>Note 1008491 - BBPSOCO01:Problems with large follow on Docs
    Note 979476 - Calling transaction BBPSOCO01 takes a very long time
    Note 858153 - Short dump could occur after implementing note 851605
    Note 851605 - PO references updated incorrectly in the back-end
    Note 954435 - Short dumps during creation of purchase order
    Note 1045347 - "Error in system;" when using Requirements link in BBPSOCO02
    Note 904550 - Obsolete vendor in document preview of the sourcing cockpit</u>
    Hope this will help.
    Regards
    - Atul

  • "Document not found "  Error message

    Hi Experts:
    In CRM 4.0 - WinClient, we are getting error message CRM_ORDER000 "Document not found".
    The error occurs when the agent creates two sales orders for the same client. She does not save the first order with Saving bottom (F ), but presses directly the quick link to create a new sales order.
    A pop-upp apears with the question: Do you want to save transaction Telesales? The agent confirms this. Later she is not able to save the second order because of the error message  CRM_ORDER000 "Document not found".
    We have found note 856954 but we have already the relevant support package.
    Any idea what this could be?
    Best regards,
    Cristina

    Hello,
    have you find the problem's cause ?
    I have the same problem ....
    Thank you.

  • FM SO_NEW_DOCUMENT_SEND_API1 error message- document not sent

    Hi Team
    just want to know what could have gone wrong when i executed the sample program attached in the documentation of FM SO_NEW_DOCUMENT_SEND_API1. this is my error message: document could not be sent to any of the recipients!
    Could you please suggest me what is the exact problem ? ASAP.
    Thanks in Advance.
    Puneet.

    FORM docu_send_email USING pv_otfdata TYPE tsfotf pv_emailid TYPE any pv_formname TYPE any. DATA: lv_filesize TYPE i, lv_buffer TYPE string, lv_attachment TYPE i, lv_testo TYPE i. DATA: li_pdfdata TYPE STANDARD TABLE OF tline, li_mess_att TYPE STANDARD TABLE OF solisti1, li_mtab_pdf TYPE STANDARD TABLE OF tline, li_objpack TYPE STANDARD TABLE OF sopcklsti1, li_objtxt TYPE STANDARD TABLE OF solisti1, li_objbin TYPE STANDARD TABLE OF solisti1, li_reclist TYPE STANDARD TABLE OF somlreci1, li_objhead TYPE soli_tab. DATA: lwa_pdfdata TYPE tline, lwa_objpack TYPE sopcklsti1, lwa_mess_att TYPE solisti1, lwa_objtxt TYPE solisti1, lwa_objbin TYPE solisti1, lwa_reclist TYPE somlreci1, lwa_doc_chng TYPE sodocchgi1. CONSTANTS: lc_u TYPE char1 VALUE 'U', lc_0 TYPE char1 VALUE '0', lc_1 TYPE char1 VALUE '1', lc_pdf TYPE char3 VALUE 'PDF', lc_raw TYPE char3 VALUE 'RAW', lc_ordform TYPE char15 VALUE 'ZORDCONFIRM_01', lc_attachment TYPE char10 VALUE 'ATTACHMENT'. CALL FUNCTION 'CONVERT_OTF' EXPORTING format = lc_pdf max_linewidth = 132 IMPORTING bin_filesize = lv_filesize TABLES otf = pv_otfdata lines = li_pdfdata EXCEPTIONS err_max_linewidth = 1 err_format = 2 err_conv_not_possible = 3 err_bad_otf = 4 OTHERS = 5. IF sy-subrc 0. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. LOOP AT li_pdfdata INTO lwa_pdfdata. TRANSLATE lwa_pdfdata USING ' '. CONCATENATE lv_buffer lwa_pdfdata INTO lv_buffer. CLEAR lwa_pdfdata. ENDLOOP. TRANSLATE lv_buffer USING ' '. DO. lwa_mess_att = lv_buffer. APPEND lwa_mess_att TO li_mess_att. CLEAR lwa_mess_att. SHIFT lv_buffer LEFT BY 255 PLACES. IF lv_buffer IS INITIAL. EXIT. ENDIF. ENDDO. * Object with PDF. REFRESH li_objbin. li_objbin] = li_mess_att[. DESCRIBE TABLE li_objbin LINES lv_attachment. * Object with main text of the mail. lwa_objtxt = space. APPEND lwa_objtxt TO li_objtxt. CLEAR lwa_objtxt. DESCRIBE TABLE li_objtxt LINES lv_testo. * Create the document which is to be sent lwa_doc_chng-obj_name = text-008. lwa_doc_chng-obj_descr = text-008. lwa_doc_chng-sensitivty = lc_0. lwa_doc_chng-obj_prio = lc_1. lwa_doc_chng-doc_size = lv_testo * 225. * Pack to main body. CLEAR lwa_objpack-transf_bin. * header lwa_objpack-head_start = 1. * The document needs no header (head_num = 0) lwa_objpack-head_num = 0. * body lwa_objpack-body_start = 1. lwa_objpack-body_num = lv_testo. lwa_objpack-doc_type = lc_raw. APPEND lwa_objpack TO li_objpack. CLEAR lwa_objpack. * Create the attachment. * Fill the fields of the packing_list for the attachment: lwa_objpack-transf_bin = gc_x . * header lwa_objpack-head_start = 1. lwa_objpack-head_num = 1. * body lwa_objpack-body_start = 1. lwa_objpack-body_num = lv_attachment. lwa_objpack-doc_type = lc_pdf. lwa_objpack-obj_name = lc_attachment. lwa_objpack-obj_descr = text-008. lwa_objpack-doc_size = lv_attachment * 255. APPEND lwa_objpack TO li_objpack. CLEAR lwa_objpack. lwa_reclist-receiver = pv_emailid. lwa_reclist-rec_type = lc_u. lwa_reclist-notif_del = gc_x. lwa_reclist-notif_ndel = gc_x. APPEND lwa_reclist TO li_reclist. IF li_reclist IS NOT INITIAL. CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1' EXPORTING document_data = lwa_doc_chng put_in_outbox = gc_x TABLES packing_list = li_objpack object_header = li_objhead contents_bin = li_objbin contents_txt = li_objtxt receivers = li_reclist 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. IF sy-subrc 0. * MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno * WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. ENDIF. ENDIF. ENDFORM. " DOCU_SEND_EMAIL

  • "Message Not Sent" Error When sending picture via text message

    I have a Droid 2 and I am unable to send a text with a picture.  I use the phone in the field and need to send images of land with a text message but so far am unable to do so.  I have checked my options settings in My Verizon and do not see anything that may be preventing from doing this function.  It is not a signal strength problem.  Also this is not an intermittent problem.  It just will not send a text with a picture 100% of the time.  Not having a problem with regular texting.  Can anyone help.  Thanks

    Thank you community!
    Hello dash9,
    The community gave great options.  I know the picture messaging is important to your job.  If the community suggestion did not assist I would like to help.  Are you able to send pictures when you are not in the field?  When you are unable to send a picture are you able to access the internet?  Have you successfully sent a mms in this area before?  Please advise me of this information so I may further assist.  Thank you. 

  • Windows 7 (64bit) & Office 2010 (32bit) Excel 'Document not saved' over WAN to network drive

    Hi All
    We are currently in the process of upgrading all PC's on our WAN to windows 7 across multiple locations
    I know this has been asked numerous times but nothing is working for me.
    We are experiencing the dreaded 'Document not saved' error at only some locations (5 or 6 out of 200 for all users, these sites generally have slow network connections) when trying to save to a network share back at our HQ. it creates a .tmp file and leaves
    the original document intact but without the changes, changing the name of the document in save as doesn't work. saving locally and copying to the share works. We can save locally and to other onsite network shares. It constantly happens so the document can
    never be saved to that network share.
    Always worked on XP SP3 with Office 2010.
    the files in question are around 4mb. smaller excel files with no contenct do work.
    I have tried literally everything listed on all forums and nothing seems to resolve it...I've tried
    - the hotfix - doesn't apply to my enviroment and the offending KB aren't installed.
    - the network resiliency, pivot table network resiliency and Enable simply copy for UNC registry keys
    - disabling offline folders, windows search and indexing
    - disabling SMB2 on the client
    - turning off QOS on the IP4 settings.
    - trusted documents.
    event log gives
    Log Name:      OAlerts
    Source:        Microsoft Office 14 Alerts
    Date:          28/03/2014 18:47:23
    Event ID:      300
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Description:
    Microsoft Excel
    Document not saved.
    P1: 100490
    P2: 14.0.7015.1000
    P3: xsmh
    P4: 0x80070040
    and numerous other things.
    My guess is me the issue points to Excel loosing connection to the network share when saving and then the .tmp becoming corrupt.
    Does any one have any ideas? Is there a way to sure the connection when saving? is there a way to force it to stay connected?
    any help highly appreciated.
    Thanks

    Hello, We've been having this same issue, and I think we have a work-around.
    If we change HKLM\System\CurrentControlSet\services\LanmanWorkstation\Parameters\RequireSecuritySignature from "0" to "1" we still get the error message but the tmp file is NOT created. If the user tries to save again, it is then successful.

  • Extended Payment Order with status 51 Application document not posted in IHC

    Dear Gurus,
    We are make an extended payment order (PAYEXT), through the transaction F110, and then when we want to see the IDOC (by Tx. WE02) we have the following error in the Inbound IDOC´s:
    IDoc: 0000000002179110 Status: Application document not posted
    Error Message: A transaction type could not be (uniquely) determined - IHC 0308
    We enter a payment method and payment method supplement in the proposal on F110.
    I don´t know whats the reason of the error. I hope you can help me please.
    Kind Regards,

    Hi Jayj,
    Thanks for your response. Sorry for the delay in responding you
    I make the following steps to get the error:
    1. I´ve created the invoice through FB60, on the company CO05.
    2. IThen I pay the invoice by F110, (I´m attaching the log of the payment).
    3. When I want to check by WE02 the IDOC the system generate the error message: a transaction type could not be determine. (I´m attaching the error message)
    Please I hope you can help me.
    Thanks a lot and kind regards,
    Ivan R. Menacho

  • Text not sent

    So after the Gingerbread update I have been having text issuews with the stock app and handcent.  Every few days I will get a text message not sent error after trying to send a text.  The only way it will start sending texts again is if I reboot and then I get the error again a few days later.  It is really annoying.  I've tried clearing stock cache.  any suggestions?  Also, is verizon planning on releaseing an update to fix the gingerbread bugs?

    Hugh7911, thank you for your community and thanks to everyone who helped. 
    One thing I have noticed with Handcent is that it gives an option to send a delivery report, but the stock text messaging app does not. The phone may be trying to send a delivery report when it doesn't support it. Go into Handcent, press the Menu button, More, Undelivered. Delete any undelivered messages then power cycle the phone. Try sending a text message from the default text messaging app and see if that resolves the errors. 

  • Not sent txts

    For the last 3 days sometimes when I send a txt I get an error message that says that the txt wasn't sent so I resend and some of those times the other person tells me I am sending the same txt twice????? Anyone else having this problem or know what is happening? I took my battery out last night but I had 3 not sent errors in the last few hours. Thanks
    Maddie

    Which TEXT app are you using?  Try HANDCENT  ... it's one of the better free text apps out there.  Not sure why you would be getting that error though.  Maybe a network connection issue when you click on SEND ?

  • 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

  • Accounting Document not posted for Cancelled Invoice -error in FI interface

    Hi,
    When I create a billing document then an accounting document gets created automatically in the background and then when I cancel the billing document no accounting document gets generated and the field Posting Status in header Detail of Billing document updated as "Errors in Financials Interface.
    I tried to release it for Posting via VFX3 but failed due to below error message in Log:
    "Incorrect doc.no.: 4900000005. Select document number between 3000000000 and 3099999999"
    I have checked the Number range assignments to the Invoice type and Accounting type.
    The number range is same for both Invoice type (Y0F2) and Cancelled Invoice type (Y0S1).
    The Accounting document type (RV) is also same for both the cases. But it is working fine for Y0F2 (Acounting document generated and cleared automatically). But not working fine for Cancelled Invoice (Y0S1).
    Can anybody please help me find out a solution to the issue.
    Thanks, Ram.

    Hi,
    The error message F5151 refers to the number range of the FI document.
    Please have a look at the note 1259505: FAQ: New cancellation procedure in SD, which covers this issue in detail.
    Question 5:
    Q5. What is the FI document type, generated by the cancellation ?
    In the old cancellation procedure, the FI document type is always
    determined in SD, and passed to FI (the same when a normal invoice  -
    not a cancellation -  is transferred to accounting).
    In transaction VOFA there is the field 'Document type' (TVFK-BLART).
    If this field is filled, then the FI document will have the document
    type maintained here.
    If TVFK-BLART is empty, then the FI document will get the default
    document type 'RV'.
    If the new cancellation procedure is performed, the FI document type is
    always determined in FI, based on the document type of the FI document
    to be reversed.
    In transaction OBA7 the FI document type has assigned the field 'Reverse
    document type' (T003-STBLA).
    If it is filled, then the FI cancellation document will get the document
    type maintained here.
    If T003-STBLA is empty, then the FI document cancellation will get the
    same document type as the cancelled FI document.
    Notice that an unexpected FI document type can cause the error message
    F5 151.
    Example:
    F2 invoice 90000001 was released, creating an accounting document with
    document type 'RV'.
    This F2 invoice is reversed by the S1 billing document 70000001.
    In customizing of SD there is:
    Billing Type    Document Type
    F2              RV
    S1
    In customizing of FI there is:
    Document Type    Number range   Reverse Document Type
    RV               00             AB
    AB               01             AB
    The FI number ranges (object RF_BELEG) are:
    No  From number    To number   Ext
    00  0090000000     0099999999  X
    01  0100000000     0199999999
    Different situations can occur, due to these customizing settings of the
    FI document type, caused by the type of cancellation.
    If the new cancellation is used:
    The FI document type 'RV' has 'Reverse Document Type' = 'AB'.
    Document type 'AB' has number range '01' set as internal.
    So the FI document will have its own number included in
    100000000-199999999.
    There is no issue.
    If the old cancellation is used:
    The cancellation billing type S1 has no 'Document type' maintained, so
    the FI document will get document type 'RV'. It has number range '00',
    set as external number range.
    So the FI document should get the same number of S1 billing document.
    But the S1 billing document has number 70000001, not included in the
    interval of number range '01'.
    This will cause error F5 151.
    I hope this information helps you.

  • File not found error when tried to open Document ID settings page

    Hi
    when i open sitesettings>site collection administratin >Document
    ID settings
    it shows
    file not found error
    adil

    Hi,
    first we need to figure out the error. change the web.config so that you can see the error on browser
    1) Obtain the complete call stack instead of the default error page:
    <SafeMode MaxControls="200" CallStack="false"/>
    to
    <SChangeafeMode MaxControls="200" CallStack="true"/>
    2) CustomeErrors mode value (in the system.web section) is set to Off:
    <customErrors mode="On">
    to
    <customErrors mode="Off">
    Change these value in "c:\inetpub\wssroot"  CA dirctory web.config and
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\web.config .
    now again try to do the action. you will get the error on screen.
    Whenever you see a reply and if you think is helpful,Vote As Helpful! And whenever you see a reply being an answer to the question of the thread, click Mark As Answer

Maybe you are looking for

  • LG l1953S sleep issues when mac mini is in stand-by . No cable connected...

    Hi .. Yesterday i started in the fabulous world of MAC with my brand new MAC MINI . The problem that i have is that when the MAC mini is in stand-by the monitor is not in sleep state , and i get in the monitor screen " check cable " . So i have to di

  • Table name changed in Reports 3.0

    My DBA asked me to change the table name from SA_AWARDS to SAFETY_AWARDS. I had already developed a report using table name SA_AWARDS. When I change the table name in my report to SAFETY_AWARDS, I get compilation errors. How can I fix it ? Thanks. Su

  • How can I restore part of a library from vault?

    Hi All, I have a backup-restore problem here. I have a vault that was current *before my vacation*. I have since added several hundred pictures and done some keywording and photo editing. Then I accidentally deleted a project (I thought I was deletin

  • Dreamweaver and DNS issue

    Ok folks. I am looking for some major help with what seems like it would be a simple solution. But it has proved to be a very difficult one. Here is the story- I have a website. I use dreamweaver to upload (FTP) everything. My host recently did some

  • To remove Acknowledgement status in Async scenario.

    Hi All, I have a async scenario where in Sender is Business System and Receiver is a Business Component(Business Service). Sender - FTP Receiver - Http I tested using the given payload in RWB. The message reached successfully and target confirms it.