Send context - Urgent

Hi,
We are using a send context to send message from one BPM to another BPM in XI.
I know that we can use any arbitary name as the send context.
But whats the meaning of giving the special charcter ' * '.
SW015_TO_SW007*.
Thanks,
John

Hi,
>>SW015_TO_SW007*.
It might be possible that in the configuration part there are more then one configured receiver.
SW015_TO_SW007_AAA
SW015_TO_SW007_BBB
SW015_TO_SW007_CCC
Thanks
Farooq

Similar Messages

  • Regarding send step in bpm--"send context"

    i want to use the send step in my bpm with send context.
    The send context is a freely definable string, which you specify in the send step. You query the send context in a condition in the receiver determination in the Integration Directory. You must specify the send context to be able to send messages from the same message interfaces to different receivers in different send steps.
    but i did n't understand regarding the explanation given above.
    could u plz help me out

    Hi
    When you use Receiver determination step in BPM to get a list of receivers for a send step.
    You need to define send context to send messages from the same interface to different receivers in different send steps. As list of receivers is collected using receiver determination.
    Now you can use this to set condition(send context) based receiver in ID Receiver determination.
    Thanks
    Gaurav

  • Receiver determination step - Send context

    Hi Experts,
    I have understood from SAP library and others threads that send context in the receiver determination step is used to send value for the conditions we have added in ther receiver determination and fetch only receivers those satisfy the cretiria.
    Please validate whether my understand is right or not?
    If its correct, then my question is can we populate this value dyanmically, say field value from another message.
    Please clarify.
    Thanks,
    Kar

    Check if the below link is of any interest to you:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
    From the link:
    Condition: when the AirlineID field in the message payload has the value LH, then the message is
    forwarded to the receiver business system BUS_100. A context object of the same name from the ES
    Repository is used to access the AirlineID field in the message.
    It talks about normal receiver determination as against the receiver determination step (of BPM) which you want....

  • Send Context in BPM

    hi,
    I have more than 2 conditions in the SWITCH condition in BPM.
    For each SWITCH condition i have a SEND step inside.
    Branch 1 -> Send 1
    Branch 2 -> Send 2 ...
    Idea is once the condition is satisifed in the SWITCH condition, using the <b>SEND CONTEXT</b> in the SEND step i will try to use this SEND CONTEXT in my receiver determination.
    It seems like it doesn't like the SEND within the SWITCH.
    Any other ways?
    Thanks,
    Tirumal

    Hi
    When you use Receiver determination step in BPM to get a list of receivers for a send step.
    You need to define send context to send messages from the same interface to different receivers in different send steps. As list of receivers is collected using receiver determination.
    Now you can use this to set condition(send context) based receiver in ID Receiver determination.
    Thanks
    Gaurav

  • How to use send context in ccBPM

    Hello,
    I am trying my first BPM process. I am using the send step while I need to specify the receiver using send context. The value of the send context should be:
    The send context is a freely definable string, which you specify in the send step. You query the send context in a condition in the receiver determination in the Integration Directory. You must specify the send context to be able to send messages from the same message interfaces to different receivers in different send steps.
    My questions is how to query the send context in condition of the receiver determination (RD). The condition  of RD is basically variable operator value, while variable could be field of the payload or context object. I don't see how to query the send context in a RD condition. Can somebody explain it?
    Thanks
    Jayson

    Hi Jayson
    You must specify the send context to be able to send messages from the same interface to different receivers in different send steps.
    Check this
    http://help.sap.com/saphelp_nw04/helpdata/en/11/13283fd0ca8443e10000000a114084/content.htm
    Thanks
    Gaurav

  • 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?

  • Getting Error : Exception sending context initialized event to listener

    I am using JWSDP1.2 and tomcat that's bundled with it.
    I am trying out a simple jsf appln very similar to the "Usernamebean" example.Each time i deploy my war file and try to access my webapp, i get the following error in tomcat's log. Driving me nuts !
    Jun 12, 2003 12:23:04 AM org.apache.catalina.core.StandardHostDeployer install
    INFO: Installing web application at context path /finaljsf from URL jar:file:/C:/jwsdp-1.2/webapps/finaljsf.war!/
    Jun 12, 2003 12:23:05 AM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigListener
    javax.faces.FacesException: javax.faces.application.ApplicationFactory
         at javax.faces.FactoryFinder.getImplementationName(FactoryFinder.java:400)
         at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:203)
         at com.sun.faces.config.ConfigParser.parseConfig(ConfigParser.java:91)
         at com.sun.faces.config.ConfigListener.contextInitialized(ConfigListener.java:127)
         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3670)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4106)
         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:843)
         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:827)
         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:623)
         at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:315)
         at org.apache.catalina.core.StandardHost.install(StandardHost.java:837)
         at org.apache.catalina.manager.ManagerServlet.install(ManagerServlet.java:712)
         at org.apache.catalina.manager.HTMLManagerServlet.install(HTMLManagerServlet.java:306

    I was using an older version of tiles.jar. Hence the error. Started working after I moved to the latest version of struts.jar

  • SEVERE: Exception sending context initialized event to listener instance

    Hi,
    I am seeing the following error when trying to deploy my war file using tomcat 6.0.18. War file is built with JSF 1.2 and Java 1.6.0_12. Could anyone please let me know what could be the reason.
    Thanks.
    Jun 12, 2009 3:09:37 PM com.sun.faces.config.ConfigureListener contextInitialized
    WARNING: JSF1059: WARNING! The com.sun.faces.verifyObjects feature is to aid developers not using tools. It shouldn''t be enabled if using an IDE, or if this application is being deployed for production as it will impact application start times.
    Jun 12, 2009 3:09:37 PM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:213)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
         at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
         at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719)
         at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
         at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
         at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
         at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
         at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
         at org.apache.catalina.core.StandardService.start(StandardService.java:516)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Caused by: org.xml.sax.SAXParseException: cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1951)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685)
         at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:273)
         at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:240)
         at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:186)
         at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:100)
         at javax.xml.validation.Validator.validate(Validator.java:127)
         at com.sun.faces.config.ConfigManager$ParseTask.getDocument(ConfigManager.java:434)
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:394)
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:351)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)

    More logs:
    Jun 12, 2009 3:09:37 PM org.apache.catalina.core.StandardContext listenerStart
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:213)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
         at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
         at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719)
         at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
         at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
         at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
         at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
         at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
         at org.apache.catalina.core.StandardService.start(StandardService.java:516)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Caused by: org.xml.sax.SAXParseException: cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1951)
         at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685)
         at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:273)
         at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:240)
         at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:186)
         at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:100)
         at javax.xml.validation.Validator.validate(Validator.java:127)
         at com.sun.faces.config.ConfigManager$ParseTask.getDocument(ConfigManager.java:434)
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:394)
         at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:351)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:619)

  • How to query send context of ccBPM in IR?

    Calling a Receiver Determination Defined in the Integration Directory
           1.      In the Receiver From field of the properties area of the send step, select Send Context.
           2.      In the Send Context field, specify a character string for the send context.
    You can choose the character string yourself. You must specify the send context to be able to send messages from the same message interfaces to different receivers in different send steps.
           3.      Query the send context in a corresponding condition in the receiver determination in the Integration Directory.
    My question is, the send context is not a part of the payload of xml, how to query the send context in IR?
    Thanks in advance.

    Hi YiNing Mao,
       Were you able to solve the problem?
       I am also facing a similar issue where i have to receiver determination with condition ProcessStep = ASNtoAII. ASNtoAII is defined as send context in IR in the BPM.
       What is the right way to give the condition
    1. In concerned receiver determination for the receiver service you give this condition
    2. when we select the condition do we need to select XPATH node or the other node to give condition ProcessStep in left operand.
    3. Do we need to give the send context against ProcessStep as ASNtoAII or 'ASNtoAII' ? The difference between two is one is without quotes other is with quotes.
    Looking forward to help from you.
    Thanks and regards,
    Amit Deshpande

  • Logic Pro X - why is the sends context menu so hard to bring up on existing bus

    Why is the sends context menu in the mixer window so hard to bring up on a bus that has already been assigned, e.g when you want to change or remove it?  If I want to remove a bus send from a channel or change the bus number, I should be able to click on the bus and select the option.  But it seems to only come up some times, not consistently.
    Thanks.

    Just happened to me. Then realized that I had clicked the "link" button off in the Piano Roll Editor and clicking it back on fixed it.

  • 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.

  • 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

  • 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/

  • 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

  • Sending context information to namedcache.get

    I have a distributed cache backed by a data store. when I invoke NamedCache.get(), apart from the key, I would like to pass additional context to the get method, that is passed on to the load method of the database store class. I want to acheive something like:
    NamedCache.get(mykey, Object myContext),
    resulting in load(myKey, context)
    Is there a means to do this?
    Thank You

    I am hoping the key->table is a static mapping? If so maybe you could instantiate the CacheLoader with knowledge of this mapping and it could then determine the table to use for the load?
                             <cachestore-scheme>
                                  <class-scheme>
                                       <class-name>com.hraja.coherence.cachestore.KRMCacheStore</class-name>
                                       <init-params>
                                            <!-- xml version -->
                                            <init-param>
                                                 <param-type>xml</param-type>
                                                 <param-value>
                                                      <krm-map>
                                                           <key-relational-mapping>
                                                                <key>key1</key>
                                                                <table>table1</table>
                                                           </key-relational-mapping>
                                                           <key-relational-mapping>
                                                                <key>key2</key>
                                                                <table>table2</table>
                                                           </key-relational-mapping>
                                                      </krm-map>
                                                 </param-value>
                                            </init-param>
                                            <!--
                                                 # delimited string version <init-param>
                                                 <param-type>string</param-type>
                                                 <param-value>key1=table1,key2=table2</param-value>
                                                 </init-param>
                                            -->
                                       </init-params>
                                  </class-scheme>
                             </cachestore-scheme>The other alternative is to take the JPA Entity annotation approach and decorate your class with this meta-data that you analyze in your load method...
    --harvey                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Maybe you are looking for

  • How do i move my address book from one computer to another?

    MacBook 10.5 > MacBook 10.6 Thanks!

  • Unable to open image from bridge to ps

    Am running Windows 7 64 bit, with CS5 64 bit. When I try and open a tiff file in Bridge to Photoshop, no dice. Control/O does nothing. "Open with" wants to open in Internet Explorer 9 (default). No trouble opening from Bridge to ACR. Any help would b

  • Who created Doc.

    Hi, My client requirement is, when user made a payment via F-53 tcode then it will generated document number. My question is who generated this document? I had checked BSEG, BSAK , BSIS and BSAS table where no user id column to determine that who gen

  • Date field on Selection Screen

    Hi All, I need to create Date field (From and To) in the selection screen. The Date format should appear as YYYY-MM-DD. I have defined this requirement as below. select-options: s_date for sy-datum no-extension default sy-datum. Due to above line, da

  • How can i do to upload my movies from the ipad to the i cloud?

    How can i do to upload my movies from the ipad to the i cloud?