Sending Details.  URGENT ! ! !

Hi,
I have a programming problem which I need urgent help with....
1.) I firstly have a HTML file which a user will fill out 3 fields on and submit.
2.) A servlet will get these parameters, validate some information and update a database.
Problem Part Needs to send on these details to another servlet which will be located on a seperate server.
Is there a way of doing a submit like function without an actual submit, as this will all be done away from the user.
Was initially going to use:
ctx = getServletContext();
rd = ctx.getRequestDispatcher("https://localhost:8443/servlet/FileName");But found out you can only do this with files in the same immediate location!
3.) Next servlet will accept in the same details as 2, and do some more functions and database updating. Before again sendin on some details to another servlet! (so same problem as in 2).
4.) Accepts in details from 3 and updaes database!
So does anbody have any ideas how this can be done??
Any help greatly appreciated.
Aidan.

Here some simple code
URL url = new URL("http://pc015:8080/hrm/reportholidaylist"+sessid);
            HttpURLConnection con = (HttpURLConnection)url.openConnection();
            con.setDoInput(true);
            con.setDoOutput(true);
            OutputStream out = con.getOutputStream();
            PrintWriter pw = new PrintWriter(out);
            pw.println(start);
            pw.println(end);
            pw.flush();
            con.connect();
            BufferedReader br = new BufferedReader(new InputStreamReader(con.getInputStream()));
            String res = br.readLine();

Similar Messages

  • Sending Details -- URGENT HELP REQUIRED! ! !

    Hi,
    I have a programming problem which I need urgent help with....
    1.) I firstly have a HTML file which a user will fill out 3 fields on and submit.
    2.) A servlet will get these parameters, validate some information and update a database.
    Problem Part Needs to send on these details to another servlet which will be located on a seperate server.
    Is there a way of doing a submit like function without an actual submit, as this will all be done away from the user.
    Was initially going to use:
    ctx = getServletContext();
    rd = ctx.getRequestDispatcher("https://localhost:8443/servlet/FileName");But found out you can only do this with files in the same immediate location!
    3.) Next servlet will accept in the same details as 2, and do some more functions and database updating. Before again sendin on some details to another servlet! (so same problem as in 2).
    4.) Accepts in details from 3 and updaes database!
    So does anbody have any ideas how this can be done??
    Any help greatly appreciated.
    DBM.

    Whats so wrong with posting in more than one forum? I
    need to get this done in the next few hours and im not
    exaclt the most qualified java developer in the
    world!!
    sorry if its such a crime! :o(Should be obvious. You post exact question in forum A and B. Person A answers you on forum A. Person B, not knowing you were already answered because he's looking at the post on forum B, answers you on forum B, thus having wasted his time.

  • Payment details - Urgent

    Hi
    Can some provide me the information what transaction happens and what tables gets updated once bank send details about he payment made to the vendors
    Thank you

    Hi,
    Once you receive a manual or electronic bank statement from the bank, you usually execute T Codes FF67 / FEBC / FF_5 to import bank statement into your system.  The tables that get hit (as far as the bank statement is concerned) are FEBCL, FEBEP, FEBKO, FEBPI, ...
    As the postings are happening, the tables that get hit are pretty standard ones for accounting (vendor) documents - BKPF, BSEG, BSIK, BSAK.  You may want to check standard programs SAPMF40K and RFEBKA00.

  • Can u send an URGENT text message on the Droid Charge???

    I been trying to figure out how to send an urgent text message. I've had the phone since lst November and seems all I can do is send regualr text messages. How can u send an urgent text message so that it grabs the recipients attention to respond as soon as possible. Like for example, that person ur sending the message to is in a situation where they cant recieve phone calls, so u gotta text them instead and its an urgent matter, so ur wanna to send an urgent text message that grabd their attention immediately.  So does anyone know how u go about sending an urgent text message? Please get back to me. Thanks -Brian

    don't know aside from calling someone.  if they are unable to receive phone calls, then they are probably unable to receive texts.  you could sending them an e-mail - perhaps they have a data signal?

  • Please send detail steps for uploading legacy data

    Hi friends,
    please send detail steps for uploading legacy data
    Thanking u in advance,
    Diwa.

    HI U CAN USE LSMW TO UPLOAD LEGACY DATA
    LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
    Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
    The LSMW comprises the following main steps:
    Read data (legacy data in spreadsheet tables and/or sequential files).
    Convert data (from the source into the target format).
    Import data (to the database used by the R/3 application.
    But, before these steps, you need to perform following steps :
    Define source structure : structure of data in the source file.
    Define target structure : structure of SAP that receives data.
    Field mapping: Mapping between the source and target structure with conversions, if any.
    Specify file: location of the source file
    Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
    How is the decision made which method should be followed? What is the procedure followed for this analysis?
    All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready  tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
    SO Bottom line is make choice of these methods based of real time requirements.
    These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
    Try to go through the some material on these four methods, and implement them.  You will then have a fair idea about when to use which.
    LSMW Steps For Data Migration
    How to develop a lsmw for data migration for va01 or xk01 transaction?
    You can create lsmw for data migration as follows (using session method):
    Example for xk01 (create vendor)
    Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
    1. TCode : LSMW.
    2. Enter Project name, sub project name and object name.
        Execute.
    3. Maintain object attributes.
        Execute
        select Batch Input recording
        goto->Recording overview
        create
        recording name.
        enter transaction code.
        start recording
        do recording as per ur choice.
        save + back.
        enter recording name in lsmw screen.
        save + back
    Now there will be 14 steps.
    2. MAINTAIN SOURCE STRUCTURES.
        Here you have  to enter the name of internal table.
        display change
        create
        save + back
    3. MAINTAIN SOURCE FIELDS.
        display change
        select structure
        source_fields->copy fields.
        a dialogue window will come .
        select -> from data file
        apply source fields
        enter No. of fields
        length of fields
        attach file
        save + back
    4. MAINTAIN STRUCTURE RELATIONS
        display change
        save + back
    5. MAINTAN FIELD MAPPING & CONVERSION RULE
        display change
        click on source field, select exact field from structue and enter
        repeat these steps for all fields.
        save+back
    6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
        execute
        save + back
    7. SPECIFY FILES.
        display change
        click on legacy data
        attah flat file
        give description
        select tabulatore
        enter
        save + back
    8. ASSIGN FILE
        execute
        display  change
        save + back
    9. IMPORT DATA.
        execute
        display  change
        save + back
    10. DISPLAY IMPORTED DATA
          enter ok, it willl show records only.
          back
    11. CONVERT DATA
          execute
          display  change
          save + back
    12. DISPLAY CONVERTED DATA
          execute
          display  change
          save + back
    13. CREATE BATCH INPUT SESSION
          tick keep batch input folder
          F8
          back
    14. RUN BATCH INPUT SESSION.
          sm35 will come
          Object name will be shown here
          select object & process

  • Changing Sender Details in Sending mails from SAP

    Hi All,
           I am getting request from legacy system to send mail from along with document. So i am creating the document and attaching   that to send request then the system automatically taking the user login eamil ID as sender Email ID.But My requirement is i have to change the sender email ID as the what ever the email ID i got from legacy system.
    In this i am using class :: CL_SAPUSER_BCS
    Please help me if any implemented this earlier.
    Thanks
    Anil d

    I am using object oriented approach and this is my modified code
    Intially SAP using the following code
        Sender details; Usually user name
         WA_SENDER0 = CL_SAPUSER_BCS=>CREATE( SY-UNAME ).
         call method WA_SENDREQ->SET_SENDER
           exporting
             I_SENDER = WA_SENDER0.
    but i hv commented this one and added my code.then also i can't able to send mails from this class.
    V_SENDER = 'abc.yahoo.com'.
    data: SENDER type ref to CL_CAM_ADDRESS_BCS.
    SENDER = CL_CAM_ADDRESS_BCS=>CREATE_INTERNET_ADDRESS( V_SENDER ).
    call method WA_SENDREQ->SET_SENDER
    exporting
    I_SENDER = SENDER.
    Thanks

  • Send details on fallowing exits:

    send details on ENHANCE MENT NO : IWO10004  AND  ENHANCE MENT NO   :  QQMA0014

    Hi,
    see the below links also,
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9913a954-0d01-0010-8391-8a3076440b6e
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    Regards
    Chilla..

  • Vendor master bank details urgent.........

    Hi Exps,
    In the vendor master under general data, option payment transactions the window opens for bank details.
    Here which bank details i have to maintain? is my company bank details or vendor bank details?
    for bank interface we have to maintain every vendor swift code or only our swift code to assign? if so where we have maintain this?
    Kindly give the answers asap please.. this is very urgent.

    Hi,
    In the option for nak details you have to mantain the bank details of vendor not your bank... you rhouse bank will maintained in company code data tab...
    so for the bank interface you have to give vendor house bank swift code... by which bankers will be able to send through Electronic system...
    If helpful assign points...
    cheers
    PK

  • Error in sending Idoc ::  Urgent

    HI
    we are trying to send Idoc DELINS and ORDERS to SUS system. when sending the idoc the following error occurs in SUS
    StandaredMessageFault
    An error occured within XI interface: An exception with the type CX_GDT_CONVERSION occured but was neithered handled locally nor declared in a RAISING clause Program: SAPLBBP_BD_MAPPING_SAPXML1; Include : ; Line
    How ever the same works fine in Dev and QAS servers
    Regards,
    Anand

    Hi
    <u>Please provide SRM-SUS and XI Version details.</u>
    <b>Please go through the SAP OSS Notes, which will help -></b>
    Note 782755 - Control indicator is not transferred from MM to SUS
    <u>Related Notes</u>
    Note 1062864 - Control indicator is not transferred from MM to SUS
    Note 313925 - Example exit for EDI outbound processing (e.g. purchase order
    <b>Other OSS Notes -></b>
    Note 885825 XML inbound: Dump in QuoteItemReferenceVersionID
    Note 825169 XML: Bid currency in bid invitation
    Note 819953 SRM 4.0 of SAP XML output of partner address data
    Note 723680 Corrections in the mapping of SAP XML messages
    Note 723594 - SRM 4.0 XML confirmation mapping error
    Do let me know.
    Regards
    - Atul

  • When I export an email as a PDF it only displays the sender details not the content

    I normally export any email I wish to save as a PDF, for some reason a tax receipt I've just received, when exported as PDF, displays only as the sender's details, i.e. name, address, date sent etc.
    I've tried saving as RTF and converting but when it converts to PDF it moves the formatting around so figures aren't in one column anymore. Has anyone experienced this and solved it? Thanks.

    I normally export any email I wish to save as a PDF, for some reason a tax receipt I've just received, when exported as PDF, displays only as the sender's details, i.e. name, address, date sent etc.
    I'm seeing the same, when I try to export as PDF. It looks like Mail were formatting and scaling the mail like formatted in the Browser Window and all content is on the following pages of the document. So a simple Mail will be spread across several PDF pages.
    I get better results when opening the mail in a separate window (⌘O) and then using the "Print" button in the toolbar of the window. Then I can access the settings for the paper size and ensure it is A4 and the paper handling settings and enable "Scale to fit".
    Then click the "PDF" button to save to a PDF file.

  • Send mail (Urgent)

    HI guys,
    Please look at the coding below..
    l_wa_recieve-receiver = '[email protected]'. " this is the distribution list id "with number of mail ids inside it
    l_wa_recieve-rec_type = 'C'. "shared dis list
    APPEND l_wa_recieve TO l_it_recieve.
    CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
    EXPORTING
    document_data = "ERROR'
    document_type = 'DLI'
    put_in_outbox = c_x
    commit_work = c_x
    TABLES
    object_content = l_it_content "this table contains the body of email
    receivers = l_it_recieve " this is above
    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.
    Can you just tell me whether it works fine.. And if it is correct how much time will it take to get email in my respective email address..
    I have run this FM by just giving my mail id (not distribution list just giving doctype = 'RAW instead of DLI)
    The FM ran sucessfully without any errors , But I didnot receive any mail in my mail Inbox..
    Can you please help me how to sort it out getting mail in less time..
    Points will be rewarded
    regards,
    nazeer

    Hi Nazeer,
                   This will work fine.but If u are not getting mail just go through this documentation.This will help u find out the error.
    Functionality
    This function module enables you to send a new document, which has not yet been created, internally and externally. During the send process the document is created, along with the attributes and content that are to be transferred.
    Import parameters
    DOCUMENT_TYPE
    Default = 'RAW'.
    Document class. All classes are possible except for folders ('FOL') and distributions lists ('DLI').
    PUT_IN_OUTBOX
    Default = ' '.
    If this flag is activated ('X'), the newly created document is also placed in the outbox of the active user when it is sent.
    DOCUMENT_DATA
    This structure must contain the attributes of the document to be sent.
    OBJ_NAME
    Name of document.
    OBJ_DESCR
    Title (short description) of document.
    OBJ_LANGU
    Language of document.
    OBJ_SORT
    Sort field of document. You can search for this term using attribute search.
    OBJ_EXPDAT
    Expiry date of document. The document itself cannot expire, but each time the document is entered in a folder, this date is used as the default for the expiry date of the entry (field EXPIRY_DAT).
    SENSITIVTY
    Document sensitivity.
    A private document can have the following levels of sensitivity:
    'O' : Standard, normal sensitivity
    'F' : Functional, can be forwarded functionally
    'P' : Confidential, not visible to substitutes
    For documents in shared folders, only sensitivity level 'O' is permitted.
    OBJ_PRIO
    Recipient priority. The document itself does not have a priority level, but each time the document is entered in a folder, this value is used as the default for recipient priority for the entry (field PRIORITY).
    NO_CHANGE
    If this flag is activated ('X'), documents in shared folders can only be changed by the author. The author can change documents in private folders after they have been sent.
    PRIORITY
    Recipient priority for the folder entry. This value gives the priority, which was assigned to the document by the owner, after receipt.
    EXPIRY_DAT
    Expiry date of the folder entry. When the expiry date has been reached or passed, the entry is placed in private trash and can be retrieved from there if needed, up until the next time the trash is emptied. A new folder entry is initially given the expiry date of the document from field OBJ_EXPDT.
    PROC_TYPE
    If this field does not contain the default value (default is ' '), the document can be processed.
    The following entries are permitted:
    'D' : Dialog module
    'F' : Function module
    'R' : Report
    'S' : Report with transfer of values to global memory
    'T' : Transaction
    'U' : Transaction with transfer of values to global memory
    PROC_NAME
    Processing element. You must enter the name of the dialog module, function module, report or transaction in accordance with the entry in the field PROC_TYPE.
    PROC_SYST
    Name of sytem in which the document is to be processed. If no system is specified or '*' is entered, processing is possible in all systems.
    PROC_CLINT
    Client in which the document is to be processed. If no client is specified or '*' is entered, processing is possible in all clients.
    SKIP_SCREN
    If this flag is activated ('X'), the first screen is skipped during processing.
    TO_DO_OUT
    If this flag is activated ('X'), the document cannot be processed from the SAPoffice interface. You must use the API function module SO_DOCUMENT_SET_STATUS_API1.
    FREE_DEL
    If this flag is activated ('X'), you can delete the document from external folders using the API.
    DOC_SIZE
    Size of the document in bytes. For PC documents, the size of the relevant file should be entered, for RAW  and SCR documents the size is the "length of the last line" + "number of other lines multiplied by 255".
    Export parameters
    NEW_OBJECT_ID
    Object ID of the document created during the send process.
    SENT_TO_ALL
    If this flag is activated ('X'), the document was sent to all specified recipients or, in the case of external forwarding, the corresponding send requests were delivered to the subsystem. If sending or delivery failed in one or more cases, the flag is not activated.
    Table parameters
    OBJECT_HEADER
    This table must contain the document class-relevant data. For example, SAPscript documents store information here about forms and styles, Excel list viewer documents store, amongst other things, the number of rows and columns and PC documents store their original file names.
    LINE
    Requires class-relevant document information line by line.
    OBJECT_CONTENT
    This table must contain the actual content of the document.
    LINE
    Requires the content of the document line by line.
    OBJECT_PARA
    This table is used only by documents that are to be processed. It must contain the SET/GET parameter that is transferred to the processing element.
    NAME
    Name of the SET/GET parameter. Only the first three characters are used.
    OPTION
    This field is not used.
    LOW
    Requires the value of the parameter in NAME.
    HIGH
    This field is not used.
    OBJECT_PARB
    This table is only used by documents to which a particular processing type is assigned. The meaning of the table depends on the processing type. If the processing element is a report, or transaction with transfer of values to the global memory, the table content is interpreted as the quantity of parameters with the relevant values and exported to the memory ID taken from the first row. If the processing element is a function module or a dialog module, the table is transferred to this as table parameter MSGDIAL.
    NAME
    If the processing element is a report or a transaction with transfer of values to the global memory, the field of the first row of the table must contain the name of the memory ID used for the export. The fields of the other rows accommodate the parameter names. If the processing element is a function module or a dialog module, the fields must contain values corresponding to the use of the module.
    VALUE
    If the processing element is a report or a transaction with transfer of values to the global memory, the field for the first row of the table must remain empty. The fields for the other rows accommodate the values belonging to the parameters in NAME. If the processing element is a function or dialog module, the fields must contain values corresponding to the use of the modules.
    RECEIVERS
    This table must contain the document recipients.
    RECEIVER
    Name of recipient.
    The following entry categories are possible:
    SAP user name of the recipient
    SAPoffice name of the recipient
    Shared distribution list
    Fax number in the form of structure SADRFD
    Internet address in the form of structure SADRUD
    Remote SAP name in the form of structure SADR7D
    X.400 address in the form of structure SADR8D
    ADR_TYPE
    Type of RECEIVER entry.
    The following values are permitted:
    'B' : SAP user name
    ' ' : SAPoffice name
    'C' : Shared distribution list
    'F' : Fax number
    'U' : Internet address
    'R ' : Remote SAP name
    'X' : X.400 address
    REC_ID
    If the recipient is a SAPoffice user, the user ID, instead of the recipient name in RECEIVER, can be entered in this field.
    REPLY_DOC
    If there is a value in this field, the document is a reply to the folder entry identified by the specified ID. A correspondence history is automatically created/continued.
    REC_DATE
    The date on which the document is to reach the recipient. This date cannot be guaranteed for external recipients as it depends on connected products.
    PROXY_ID
    If automatic forwarding is active in the recipient's system, this field contains the SAP user ID or the address ID of the external address to which the document was ultimately sent.
    RETRN_CODE
    When the recipient has received the document, the function module enters the value '0' in this field. If the document is not successfully received, a value unequal to '0' is entered in the field.
    EXPRESS
    If this flag is activated ('X'), the document is sent with the attribute 'express'. If the recipient is a SAPoffice user who is logged on, he or she receive a message immediately, saying that he or she has received an express mail.
    COPY
    If this flag is activated ('X'), the document is sent with the attribute 'copy'.
    BLIND_COPY
    If this flag is activated ('X'), the document is sent with the attribute 'secret copy'. If the recipient is a SAPoffice user, he or she can neither print nor forward the document.
    NO_FORWARD
    If this flag is activated ('X') and the recipient is a SAPoffice user, he or she cannot forward the document.
    NO_PRINT
    If this flag is activated ('X') and the recipient is a SAPoffice user, he or she cannot print the document.
    TO_ANSWER
    If this flag is activated ('X') and the recipient is a SAPoffice user, the user must reply to the document before he or she can delete it from his or her inbox.
    TO_DO_EXPL
    If this flag is activated ('X') and the recipient is a SAPoffice user, the user must process the document before he or she can delete it from his or her inbox.
    TO_DO_GRP
    If this field contains a value between '1' and '9', a SAPoffice user in the recipient group indicated by this number must process the document before the recipients can delete it from their inboxes. If the value '0' is entered, the document does not need to be processed.
    COM_TYPE
    Communication method used to send the document. This field is only relevant if the recipient is an address number, that is, if the document is sent externally via address management. If the field is empty, the standard communication type specified in address management is used.
    The following values are permitted:
    'INT' : Send via Internet
    'FAX' : Send as a fax
    'X40' : Send via X.400
    'RML' : Send in another SAP system
    LFDNR
    Current number from address management. This field is only relevant if the recipient is an address number, that is, if the document is sent via address management. If the field is empty, the default current number in address management is used.
    FAX
    This field is not used.
    COUNTRY
    This field is not used.
    SPOOL_ID
    This field is not used.
    NOTIF_DEL
    If this flag is activated ('X'), the sender receives confirmation when the recipient receives the document. He or she also receives a message if the document could not be delivered. This flag should only be activated for external sending, since internal sending is synchronous. Confirmation is only supported by a small number of mail systems, however. For example: X.400 and SAP SAP.
    NOTIF_READ
    If this flag is activated ('X'), the sender is notified as soon as the recipient has read the document. This flag should only be activated for external sending, since internal sending is synchronous. Read notification is only supported by a small number of mail systems, however. For example: X.400 and SAP SAP.
    NOTIF_NDEL
    If this flag is activated ('X'), the recipient receives a message if the document could not be delivered to the recipient. This flag should only be activated for external sending, since internal sending is synchronous. The message is only supported by a small number of mail systems, however. For example: X.400 and SAP SAP.
    SAP_BODY
    If this flag is activated ('X'), SAP specific data is transferred to the document in an external body part when sending via X.400. This flag should only be activated if the target system is an SAP System.
    Exceptions
    TOO_MANY_RECEIVERS
    Too many recipients were specified. The active user does not have authorization to send to this number of recipients.
    DOCUMENT_NOT_SENT
    The document could not be sent. It was not delivered to any of the specified recipients.
    DOCUMENT_TYPE_NOT_EXIST
    The document class specified does not exist or is not permitted.
    OPERATION_NO_AUTHORIZATION
    The document was not allowed to be sent because one of the required authorizations did not exist.
    PARAMETER_ERROR
    The combination of parameter values transferred to the function module was not a permitted combination.
    X_ERROR
    Am internal error or a database inconsistency has occurred.
    ENQUEUE_ERROR
    A lock required for the send process could not be set. It is probable that another user is processing.
    Example
    Sending a confidential RAW document to an internal user and an Internet address. The new document is also placed in the sender's outbox.
    DATA: OBJCONT LIKE SOLISTI1 OCCURS 5 WITH HEADER LINE.
    DATA: RECLIST LIKE SOMLRECI1 OCCURS 5 WITH HEADER LINE.
    DATA: DOC_CHNG LIKE SODOCCHGI1.
    DATA: ENTRIES LIKE SY-TABIX.
    DATA: NAME(15).
    Fill the document
    DOC_CHNG-OBJ_NAME = 'URGENT'.
    DOC_CHNG-OBJ_DESCR = 'Read at once !'.
    DOC_CHNG-SENSITIVTY = 'P'.
    OBJCONT = 'Hey guys, time for lunch !!!'.
    APPEND OBJCONT.
    OBJCONT = 'Lets get going !'.
    APPEND OBJCONT.
    DESCRIBE TABLE OBJCONT LINES ENTRIES.
    READ TABLE OBJCONT INDEX ENTRIES.
    DOC_CHNG-DOC_SIZE = ( ENTRIES - 1 ) * 255 + STRLEN( OBJCONT ).
    Fill the receiver list
    CLEAR RECLIST.
    RECLIST-RECEIVER = SY-UNAME.  " replace with <login name>
    RECLIST-REC_TYPE = 'B'.
    RECLIST-EXPRESS = 'X'.
    APPEND RECLIST.
    CLEAR RECLIST.
    RECLIST-RECEIVER = '[email protected]'.
    RECLIST-REC_TYPE = 'U'.
    APPEND RECLIST.
    Send the document
    CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
         EXPORTING
              DOCUMENT_TYPE  = 'RAW'
              DOCUMENT_DATA  = DOC_CHNG
              PUT_IN_OUTBOX  = 'X'
         TABLES
              OBJECT_CONTENT = OBJCONT
              RECEIVERS      = RECLIST
         EXCEPTIONS
              TOO_MANY_RECEIVERS         = 1
                   DOCUMENT_NOT_SENT          = 2
                  OPERATION_NO_AUTHORIZATION = 4
                   OTHERS                     = 99.
        CASE SY-SUBRC.
          WHEN 0.
            LOOP AT RECLIST.
              IF RECLIST-RECEIVER = SPACE.
                NAME = RECLIST-REC_ID.
              ELSE.
                NAME = RECLIST-RECEIVER.
              ENDIF.
              IF RECLIST-RETRN_CODE = 0.
                WRITE: / NAME, ': succesfully sent'.
              ELSE.
                WRITE: / NAME, ': error occured'.
              ENDIF.
            ENDLOOP.
          WHEN 1.
            WRITE: / 'Too many receivers specified !'.
          WHEN 2.
            WRITE: / 'No receiver got the document !'.
          WHEN 4.
            WRITE: / 'Missing send authority !'.
          WHEN OTHERS.
            WRITE: / 'Unexpected error occurred !'.
        ENDCASE.
    Notes
    To send an existing document, you must use the function module SO_OLD_DOCUMENT_SEND_API1.
    If the active user is still to be able to process the document after it has been sent, it must be moved to the outbox when sent using the flag PUT_IN_OUTBOX. You can use the function module SO_FOLDER_READ_API1 to read the contents of the outbox and the object ID to find the document sent.
    It is not possible to use a user address name as the recipient since this may not be unique. To get around this problem, you can use the function module SO_NAME_CONVERT_API1. This provides a hit list in response to a specified name, for which a dialog is constructed with a choice of required values.
    Parameters
    DOCUMENT_DATA
    DOCUMENT_TYPE
    PUT_IN_OUTBOX
    COMMIT_WORK
    SENT_TO_ALL
    NEW_OBJECT_ID
    OBJECT_HEADER
    OBJECT_CONTENT
    CONTENTS_HEX
    OBJECT_PARA
    OBJECT_PARB
    RECEIVERS
    Exceptions
    TOO_MANY_RECEIVERS
    DOCUMENT_NOT_SENT
    DOCUMENT_TYPE_NOT_EXIST
    OPERATION_NO_AUTHORIZATION
    PARAMETER_ERROR
    X_ERROR
    ENQUEUE_ERROR
    U can use other FM also
    <b>SO_DOCUMENT_SEND_API1
    SO_NEW_DOCUMENT_ATT_SEND_API1
    SO_OLD_DOCUMENT_SEND_API1</b>
    Reward points if helpful.
    Regards,
    Hemant

  • Function module 'SO_NEW_DOCUMENT_ATT_SEND_API1' not sending detail in email

    Hello experts,
    I am using function module 'SO_NEW_DOCUMENT_ATT_SEND_API1' to send emails from a workflow method. The emails are being sent out and received but there is no detail in the email.
    The following are my parameters.
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        DOCUMENT_DATA                    = gd_doc_d
        PUT_IN_OUTBOX                    = 'X'
        COMMIT_WORK                      = 'X'
    TABLES
       PACKING_LIST                     = it_packin
       OBJECT_HEADER                    =
       CONTENTS_BIN                     =
       CONTENTS_TXT                     = it_message
       CONTENTS_HEX                     =
       OBJECT_PARA                      =
       OBJECT_PARB                      =
       RECEIVERS                        = it_receiv
    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
    I am inserting the detail in internal table 'it_message' but this is not transmitted....can anybody point out what I need to do to get detail in the email.
    Thanks to all who might reply..

    Hi,
    Have you made sure that your code works without workflow? Just put it to a report and execute it with dummy values and see if it sends the email properly. If that works, then the problem might be in the workflow. I would first make sure that the bindings are correct - that your internal table containing the details is passed to the task. This you can see from the workflow log in the container.
    Regards,
    Karri

  • Using unicode in sms sending :)plz. urgent reply is needed.

    when i want to send a sms of string of unicode. is it necessary to encode it in UTF8 or UTF16 ???
    when i encode it then the length of the string comes larger.
    can i send sms as a string of unicode without changing its length????
    like this:
    String str="\u270F";
    // now str's length is 1
    str = new String(str.getBytes("UTF16"));
    //now str's length is 4!!!!!!!!
    plz. urgent reply is needed.
    best regards
    tanvir

    By default SMS has it's own text encoding and therefore you cannot use UTF8 nor UTF16. There is a special UCS2 encoding, alowing for 70 unicode characters to be send (per sms). See: http://www.dreamfabric.com/sms/

  • Can iCal send details of appointments as text messages?

    Hi everyone, I am not sure if this is the appropriate place to ask, if not, please direct me to where this would be more appropriate.
    I have been asked to provide a mac based solution for a client who uses mac mini and iPad as part of his business. He books clients (they are all one off clients, no repeats) using iCal and he wants to send the details of the appointment to the client as a reminder 24 hours before the appointment is due. Is there any way I can get iCal (or indeed any application for mac or iPad) to do this? Keeping in mind, he wants the reminder message sent to his client, not to himself, as obviously he can look at his own calendar to remind himself when/where appointments are taking place.
    Thank you all.

    Hi,
    It would be possible by using the iCal 'Run Script' alarm type. You'd set an Applescript to send the SMS. From Googling, there appears to be some options to do this, see: http://www.smsmac.com/help/discover/applescript/ , http://macscripter.net/viewtopic.php?id=34525 (for this one, you'd need the recipients phone email address), http://network-heretics.com/blog/?p=26 , http://forum.skype.com/index.php?showtopic=32933 (using Skype). Your main problem will be how to get the info from iCal, the third link here uses a variant of ones I have used to find the event details. IMO it would depend what your client has set up already as to what would be most useful.
    Best wishes
    John M

  • Job, Supervisor field and Table details - Urgent please

    Need to document fuctional/technical specs to extract <b>Job</b> and <b>Supervisor</b> field details in OM. I am trying to understand what is the Table and field for these Objects / data elements ?
    <b>Is it T513-STELL for job or is it HRP1000?
    What about Supervisor -- what is the Table and field where employee's Supervisor data is stored? .</b>
    Really appreciate any input.

    T513 is not always in sync with HRP1000. For Jobs, I would prefer to look up the Table HRP1000 with OTYPE = 'C'.
    Regarding, the other part of your question, the supervisor details are actually on the PA side.. you can use the function call RH_GET_LEADER.
    ~Suresh

Maybe you are looking for

  • Buying a season one episode at a time - discount for the last few episodes?

    If I am not sure about a show, I would prefer to watch the pilot and maybe and episode or two before buying the season. Is itunes smart enough to know that if I buy an episode or two and then buy the season that the season price should be discounted

  • How to properly partition separate Root, Applications, and Users volumes?

    Wondering if there's an official Apple recommended method to set Applications and Users directories on different physical Volumes (be it a separate partition or separate physical drive). The bottom of this Apple document alludes to this by stating, "

  • ITunes updated to 7.3.1 and now won't open

    I started iTunes and it automatically updated. Now I get a message that OSX 10.4.7 is required to use iTunes. This computer will only go to 10.4.3. I tried downloading the system updaters, but they will not install because the 1GHz processor isn't en

  • Adding a device to a zone

    Hello, I have been trying to virtualize an old Solaris 8 machine to a container with great success....except... The software running on this server uses appletalk to communicate to file shares and printers. When I tried a fresh install of the softwar

  • C and C++ applications - Solaris 8 to Solaris 10 transition

    I am about to be involved in the process of building and deloying C and C++ applications on Solaris 10, that currently are built and run on Solaris 8. I do not anticipate significant problems, based on a review of the Solaris 10 release notes (partic