Bpm Pattern Collect Payload

I am trying to merge multiple inputs within a loop and then merge them in a transformation step and then send the merged output.
I am getting an error <i>"Expression must return a multiline value"</i> because I assigned a multiline container to the source message of the transformation step. I made sure that occurances for the messages are 0..unbounded.
Has anyone faced this issue before?

One more issue related to this scenario. As per SAP's pattern for "stop collect based on payload", the initial loop needs a condition based on the payload element.
My condition is
<i>(PurchaseOrder./p1:MT_PurchasOrderReq/TotalNumberOfMessages &#8800; MsgCount)</i> similar to SAP BPM Pattern.
I don't get any error in IR or ID, but once the integration process is activated in ID, I see a return code of 99 for this integration process in SXI_CACHE. The Activation log error says <i>'TOTALNUMBEROFMESSAGES' is not a component of data object 'PAYLOAD'</i>
I get the same error if I import SAP's BpmPatternCollectPayload integration process in to ID and activate it.
If I change my condition to <i>(MsgCount &#8800; 3)</i> then it works. Am I missing some kind settings?

Similar Messages

  • BPM Pattern Collect Message Mapping run time error

    Hi,
        I'm carrying out a replica of BPMCOLLECTMESSAGE Pattern from sap basis...
    Doing a simple file to file scenario and simple mapping....
    I'm getting a MAPPING RUNTIME error at the transform step.
    kindly help in this regards..
    The checks i'v made are...
    1. Deleted all the work flow items from SWWL transaction
    2.SXI_CACHE is 0
    3.Payload cross checked.
    Is there any solution please ???

    Hi,
       On  sending Stop message PE at technical details i get error stating :  *com/sap/xi/tf/_BpmPatternCollectMerge_com.sap.aii.utilxi.misc.api.BaseRuntimeException:RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0~*
    kindly look at the Trace error at PE
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
      <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
      <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">system-ID = PI2</Trace>
      <Trace level="1" type="T">client = 100</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2009-03-17T04:35:42Z CET</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = D3370BB6DF244EA7356EECD16D0E6FAD</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
      <Trace level="1" type="T">Queue name : XBTI0001</Trace>
      <Trace level="1" type="T">Generated prefixed queue name =</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface BpmPatternCollectIfStopCollect</Trace>
      <Trace level="1" type="T">select interface namespace http://</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>
      <Trace level="1" type="T">Continue single processing</Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI2</Trace>
      <Trace level="1" type="T">client = 100</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2009-03-17T04:35:42Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
      <Trace level="1" type="T">Reading sender agreement</Trace>
      <Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOX0__0002</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Generated prefixed queue name =</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>
      <Trace level="1" type="T">Continue single processing</Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI2</Trace>
      <Trace level="1" type="T">client = 100</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2009-03-17T04:35:42Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">No mapping required</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_OUT">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
      <Trace level="1" type="T">Reading receiver agreement</Trace>
      <Trace level="1" type="T">Outbound validation does not take place</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface BpmPatternCollectIfStopCollect</Trace>
      <Trace level="1" type="T">select interface namespace http://</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface BpmPatternCollectIfStopCollect</Trace>
      <Trace level="1" type="T">select interface namespace http://</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>
    Edited by: Robin on Mar 17, 2009 10:11 AM

  • BPM: collect payload problem

    hi all.....
    i created BPM pattern collect payload.
    BPM steps are...
    in loop receive-contaner1(append the recmsg to recmsg_multi)-container2(increment the counter)-loopend, transfermation-send
    And the container elements are.....
    counter.....simple type
    recmsg.....abs intrface
    recmsg_multi..........abs intrface (multi line)
    sendmsg...............abs intrface
    but in testing , i got the msg in information area as fallows..
    "container element 'recmsg' in step Receive is initialized but is not used"
    and in sxi_cache the return code is 99.
    how can i resolve this problem...
    can anybody help me?
    thanks,
    Kumar

    Hi,
    this message is just an information and will not cause the error.
    You should compare your process with the collectPayload pattern (SAP Basis -> System Patterns).
    Reactivate the process in the IR and you could also try to refresh the process in sxi_cache manually with "Repeat Activation".
    Regards
    Patrick

  • Collect Payload Pattern

    Hi All,
    I am trying to do a scenario using CollectPayload Pattern. The pattern has to pick two files with same structure and do the processing.For that, I have given the value for condition as two in the payload. As expected the pattern picks the input files successfully. But in the output, i am getting only one file as output which has the data of first picked file. I thought it will generate two output files. (For two input files)
    i also wrote a UDF for concatinating the two input values and assigning them to target, the output is single file with both input files data.
    My questions is do we need to take care of merging the collected inputs to output or am i going wrong somewhere in the scenario?
    Your suggestions will be very helpful for my learning.
    Thanks & Regards,
    Senthil.
    Edited by: senthil Nathan on Jun 2, 2009 11:30 AM

    One more issue related to this scenario. As per SAP's pattern for "stop collect based on payload", the initial loop needs a condition based on the payload element.
    My condition is
    <i>(PurchaseOrder./p1:MT_PurchasOrderReq/TotalNumberOfMessages &#8800; MsgCount)</i> similar to SAP BPM Pattern.
    I don't get any error in IR or ID, but once the integration process is activated in ID, I see a return code of 99 for this integration process in SXI_CACHE. The Activation log error says <i>'TOTALNUMBEROFMESSAGES' is not a component of data object 'PAYLOAD'</i>
    I get the same error if I import SAP's BpmPatternCollectPayload integration process in to ID and activate it.
    If I change my condition to <i>(MsgCount &#8800; 3)</i> then it works. Am I missing some kind settings?

  • BPM Patterns when used

    Hi,
    If we are using the BPM patterns. what are the necessary steps to do in IR and ID

    hi,
    The documentation editors of the example integration scenarios (demo examples) and the BPM pattern (in software component version SAP BASIS 6.40) contain hyperlinks to further documentation in SAP Help Portal.
    To ensure that these links work properly, you have to configure the following base location for software component version SAP BASIS 6.40:
    ·        Docu Storage Type: Knowledge Warehouse (File System)
    ·        Base-URL: http://help.sap.com/saphelp_nw04s/helpdata/
    Editing or Deleting Base Locations.
    InIntegration Builder: Design:
    integration process->(Start->Sender->Transform->Reciever->Stop)
    Integration Builder: Configuration
    Source and target communication channel
    integration process->Create->ByMIAA
    Reciever Determination-> Create 2(ip_target & Source)
    Interface determination-> Create 2 (ip_target & Source)
    Sender and Reciever argeement
    Thanks,
    Sendil.

  • BPM :: n To 1 Collected Payload Pattern issue

    Hi
    I am working on following scenario -->
    Web Page --> HTTP Adapter --> XI with BPM ( Using n To 1 Payload Pattern ) --> RFC Adapter --> SAP R/3 --> XI With BPM --> File Adapter --> Legacy System with Response from RFC
    Now everything is configured & when first time I executed the scenario it gives me " Green Flag " under Outbound Status for interface from Web Page to XI. Also date format error in next 2 messages. So I corrected the date format & execute it again.
    But since from than I am getting " <b>Red Flag</b> " ( <i>Message has error status on outbound side</i> ) under Outbound status. I checked my BPM under MONI also & all the mapping & configuration is fine. Even I made the Overall messages as 1 but still getting the same error.
    I am able to see the correlation ID of message also.
    Pls. suggest.

    Hi
    My Scenario is working now & I am able to correlate the payloads on Vendor Name. But I need to clarify the concept of n:1 Pattern.
    In my multi-mapping occurence of source message is 0 to N & Target message is 1. Now when I am sending the message in this format ( coming from web page when i am clicking the SUBMIT button two times ) :
    <p3:PurOrder_Request_MT xmlns:p3="http://BpmCollectMsg:AsyncSync:AlertMgt">
             <Total_Msgs/>
             <HEADER>
                <DOCDATE/>
                <VENDOR/>
             </HEADER>
             <ITEMS>
                <PURMAT/>
                <NETPRICE/>
                <UNIT/>
                <PRICEUNIT/>
             </ITEMS>
             <Items_Schedule>
                <QUANTITY/>
                <DELIVERYDATE/>
             </Items_Schedule>
          </p3:PurOrder_Request_MT>
    <p3:PurOrder_Request_MT xmlns:p3="http://BpmCollectMsg:AsyncSync:AlertMgt">
             <Total_Msgs/>
             <HEADER>
                <DOCDATE/>
                <VENDOR/>
             </HEADER>
             <ITEMS>
                <PURMAT/>
                <NETPRICE/>
                <UNIT/>
                <PRICEUNIT/>
             </ITEMS>
             <Items_Schedule>
                <QUANTITY/>
                <DELIVERYDATE/>
             </Items_Schedule>
          </p3:PurOrder_Request_MT>
    I am getting results in same format means two different nodes of " PurOrder_Request_MT ".
    But I was expecting results in this format ::
    <p3:PurOrder_Request_MT xmlns:p3="http://BpmCollectMsg:AsyncSync:AlertMgt">
             <Total_Msgs/>
             <HEADER>
                <DOCDATE/>
                <VENDOR/>
             </HEADER>
             <HEADER>
                <DOCDATE/>
                <VENDOR/>
             </HEADER>
             <ITEMS>
                <PURMAT/>
                <NETPRICE/>
                <UNIT/>
                <PRICEUNIT/>
             </ITEMS>
          <ITEMS>
                <PURMAT/>
                <NETPRICE/>
                <UNIT/>
                <PRICEUNIT/>
             </ITEMS>
             <Items_Schedule>
                <QUANTITY/>
                <DELIVERYDATE/>
             </Items_Schedule>
          <Items_Schedule>
                <QUANTITY/>
                <DELIVERYDATE/>
             </Items_Schedule>
          </p3:PurOrder_Request_MT>
    As in target they are coming as two different payloads & I am calling the RFC one time only. RFC is taking the data of first payload only. Right now my scenario is working more as creating a batch of payloads who has same Vendor Name. But my RFC doesn't take batch of payloads.
    Can you pls. explain what exactly the n:1 pattern means.
    Best regards
    Lalit

  • Bpm patterns?

    Hi xi,bpm expertsu2026.
    I am kid to xi so I am asking such these type of questions.
    While I am doing message mergeing of to xml file scenario I want to do this using BPM collect pattern payload dependent is it possible?  Same I want process two idocs ie.CREAMAS,MATMAS idocs data in to a single idoc in xi system is it possible by using BPM collect pattern payload dependent? After inserting this pattern how to define container elements? Is we need to give the details for each step in that pattern ,if any other way please give details?
    While am reading that pattern material i got a doubt that each and every pattern was explained different contaiter elements i.e. for example in collect pattern , container elements collect u201Cmessage,collect message list,new message,stop messageu201D when I dragged in to my message mergeing scenario those container elements are not appearing?
    Can any one please explain me the basic example scenario by using any pattern?
    thanks in advance.

    Hi XI Fresher,
      Try the collecting simple files scenario in to one using BPM and apply the same for idocs also.Plese refer the sample patterns step by step.so that u will get basic idea on using patterns.
    https://wiki.sdn.sap.com/wiki/display/stage/collectmultiplemessagesandbundlethemintoonemessage.
    As there are different idocs coming in .You can try with Multificondition also but u need not apply condition here.Jus fork with two branches and no condition for fork u can skip that step.
    https://wiki.sdn.sap.com/wiki/display/stage/BPMPatternMultiIfconditionExplained%28stepbyStep+Procedure%29
    Thanks,
    Ram.

  • BPM Idoc collection without calling the mapping in BPM

    Hi Expert,
    I have an IDOC to file scenario in which source side I have to collect multiple IDOC and map it to a single file .I am achieving it through BPM . at present I am using one multimapping and calling this mapping in the BPM under transformation step its working  fine  but due to some constraint  , Now I want to achieve it using BPM but without calling the Mapping in the BPM i.e I don't want to use Transformation step in the BPM. Is it possible ????
    Regards,
    Saurabh

    Hi Saurabh,
    If that is the case it is preferable to collect the IDocs in ECC and then send them to XI at one go.
    Cheers !
    Lokesh

  • How to Initialize Container Element in BPM..No Payload found

    Hi All,
    How do we initialize a container element in BPM if that container element is a message Interface.
    I am doing exception handling in BPM, so whenever a exception occurs i need to send a mail.
    So in the exception box i have a transformation step and a send step.
    In the transformation step what will be my source message?
    How do i initialize that source message?
    What i have done right now is created a dummy interface(abs) for source and then mapped with the target abs interface.
    When i execute the schenario,in the monitor i find in the Transformation step the following error
    <i>No payload found.</i>
    Regards,
    Sumit

    Hi Pinto,
    I too agreee. Lemme try to explain witha example.
    In my first transformation, MI_MAIL_TEMP_ABS is there along with 3 other interfaces. Each one is getting mapped i can see that in monitoring.
    Now in the exception branch in transformation step,
    i am mapping MI_MAIL_TEMP_ABS to MI_MAIL_ABS.
    Now in the send step im giving MI_MAIL_ABS as the interface name.
    Do you see anything wrong with this?
    <i>>>>>>>>Did you try to do outbound interface -> inbound interface mapping in the exception branch? Just to try to make your scenario work. Then you can investigate further on why the abs message is not being carried away.</i>
    Which outbound interface & inbound are you talking about?
    Regards,
    Sumit
    Message was edited by: Sumit Khetawat

  • BPM Idoc collection without transformation step

    Hello
    I have a simple scenario of outbound invoice idocs. The tricky thing now is that I want to collect them within a BPM process.
    The BPM is basically working as long as I have a transformation step before the sending wich transforms from a multiline idoc to a "non-multiline" file.
    My problem is that I don't want to put a mapping in the BPM, because depending on the values in the idoc I need to run different mappings.
    What I really want to do is to send back the collected files to the IE and process them with separate receiver determination per receiver.
    In this way I would only need 1 BPM and the configuration is done in the directory.
    Problem is already that I can't specify a multiline message in the sending step - not allowed.
    Anyone with a similar scenario who can help? I'm not sure what the receiverDetermination step does in a BPM, could this solve my issue?
    thanks
    David

    Hello
    I tried the ForEach block, but now the BPM is first collecting the idocs and sends them out individually in the send step.
    I've never used the forEach before, so the chance is good I made something wrong.
    After collecting I'm running
    1. Block - forEach
    - MultiLineElement = collected idocs
    - CurrentLine = wasn't sure, used abstract interface of the single idoc
    - local correlation = same correlation than in the collecting step
    2. Sending (inside block)
    - message = single idoc
    - Receiver from = send context
    - Conversation ID = I've choosen an Xpath expression
    - correlation = same than for collecting
    What I'm missing here as well is how to diferenciate the idocs I send back to the IE in the receiver determination since all come from the same service with the same interface? That's why I tried to set te Conversation ID, but it didn't appear anywhere in the XML trace.
    any idea?
    thx!

  • BPM message collect problem

    Hi,
    I have a problem with  collecting messages and sending them together. I'm trying to work out a simple correlation example. Its a File -> XI -> File scenario. I followed the blog
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    to work this out. My BPM looks like
    a block which contains an infinite loop with Receive and Container steps, an exception step and a deadline step with deadline 2 mins --> Transformation step --> Send step that sends out the bundled message.
    My problem is, after the file is being picked up by XI, nothing happens, on MONI the Outbound status is stuck in "Message being sent" status forever. On the Process engine workflow the deadline step is executed, but it is not proceeding to the Transformation and send step.
    I've read a lot of material on this forum, it seems simple but for some reason I'm not able to get this to work.
    Could somebody please guide me on this?
    Thanks
    Karthik

    Hi,
    Check this <a href="http://help.sap.com/saphelp_nw04/helpdata/en/96/0a2441509fa831e10000000a1550b0/content.htm">Montioring the BPE</a> for debigging your BPM.
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm">Collecting and Bundling -- Single Interface</a>
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/0e/56373f7853494fe10000000a114084/content.htm">Collecting and Bundling -- Multiple Interface</a>.
    Regards,
    Bhavesh

  • BPM patterns for using CIDX adapter

    Hi,
    I am trying to implement the below requirement and am having problems doing that. Any help or pointers would be appreciated.
    Requirement:
    We need to send an order create message from file system A to
    Elemica(using CIDX adapter) asynchronously and capture the RA back and
    convert it into a message and send it to a file system B.
    I tried the below scenarios already and could not maker it work:
    <b>Scenario 1</b>: I tried creating a scenario using Sync- Async bridge, but
    it did not work as I need to send some response back to the File system
    A. In this case I do not have any response to send.
    I created an external definition for RA and used it for mapping to the
    File system B interface.
    CIDX adapter is not accepting any messages if we try to send
    synchronously.
    <b>Scenario 2</b>: I could not make my scenario work if I am trying to create
    in my SWCV. So, I created all my abstract
    interfaces for my business process in the CIDX SWCV. Now I created
    Async – Sync scenario by sending a synchronous order create request to
    Elemica. It did not work as CIDX adapter does not support any
    synchronous messages( guessing).
    Apart from the above questions, I have few additional questions:
    1. Can we send synchronous messages to Elemica through CIDX
    adapter? If so, how do we configure our communication channel as
    only “Asynchronous” option is available.
    2. If we have File-Elemica-File scenario, how do we configure the
    scenario?
    3. Are there any blogs having scenarios with BPM involving CIDX
    adapter? If so, pls send a link.
    Thanks in Advance,
    GP

    Hi
    Try this
    check the following link for information on configuring CIDX Adapter http://help.sap.com/saphelp_nw04/helpdata/en/29/cb22419e2ab167e10000000a155106/plain.htm
    And on specifically on Single-Action responder directly on http://help.sap.com/saphelp_nw04/helpdata/en/0a/cb23412546ef6fe10000000a1550b0/content.htm
    Thanks

  • Too many BPM data collection jobs on backend system

    Hi all,
    We find about 40,000 data collection jobs running on our ECC6 system, far too many.
    We run about 12 solutions, all linked to the same backend ECC6 system. Most probably this is part of the problem. We plan to scale down to 1 solution rather than the country-based approach.
    But here we are now, and I have these questions.
    1. How can I relate a BPM_DATA_COLLECTION job on ECC6 back to a particular solution ? The job log give me monitor-id, but I can't relate that back to a solution.
    2. If I deactivate a solution in the solution overview, does that immediately cancel the data collection for that solution ?
    3. In the monitoring schedule on a business process step we sometimes have intervals defined as 5 minutes, sometimes 60. Strange thing is that the drop-down of that field does not always give us the same list of values. Even within a solution I see that in one step I have the choice of a long list of intervals, in the next step in that same business process I can only choose between blank and 5 minutes.
    How is this defined ?
    Thanks in advance,
    Rad.

    Hi,
    How did you managed to get rid of this issue. i am facing the same.
    Thanks,
    Manan

  • BPM condition: Compare Payload with Constant

    Hi everybody,
    if I like to compare the payload with a constant, do I have to User
    a) MYCONSTANT
    b) 'MYCONSTANT'.
    Thanks, Ragards
    Mario

    Mario,
    Inside UDF? Then it is "MYCONSTANT"
    using std function? Then it is MYFUNCTION
    Regards,
    Jai Shankar

  • Strange behaviour of adapter engine

    Hi guys,
    I´m working at a Idoc 2 File Scenario.
    From the source Idoc there should be created 2 files with special file names including the timeSent of the idoc and different contents.
    For that I have specified 2 interfaces and interface mappings in interface determination. I have selected
    "remain order at runtime" at interface determination.
    the files are created with correct file name but with same content.
    There is always the content of the first file taken.
    when i have a look at the result of the mapping in the integration engine, the mapping is correct.
    (payload of the pipeline step "technical routing" has the correct content)
    obviously there is a change from the correct file content in integration engine to incorrect content in adapter engine (shown in message monitoring in rwb)
    I´m using a java mapping where I specify the filename for the file adapter using the dynamic configuration functionality, which works fine.
    Has anybody an idea why the content is changed and the files have the same content. (hopefully)
    Thanks in advance.
    Kind regards
    Jochen
    Edited by: Jochen Gugel on Aug 6, 2008 8:36 AM

    HI,
    Try the collect pattern types.
    Check with this links:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm
    Correlation Collect pattern in  SAP XI
    Bpm Pattern Collect Payload
    Thanks,
    Sendil

Maybe you are looking for