BPM and IDoc

Hi all,
we have set up a scenario where an IDoc is the trigger for a Business Process which then sends an IDoc to another system. Unfortunately this Business Process is not beeing triggered! Has anyone succeeded in starting a similar process???

Hi,
we have encountered another problem. Our scenario looks like this IDoc ->XI -> BPM -> XI -> IDoc, when sending without the BPM part there is no problem. But when involving BPM we get a problem with ALE logical system name. I demands that we have a logical system name for the Business process when creating the IDoc. Does anyone have a solution for this?
Brgds
Kalle

Similar Messages

  • Asynchronous, but need Ack without using BPM and IDocs.

    Hi Experts,
                     I would like to do a scenario i.e., "Asynchronous communication, but need Acknowledgement without using BPM and also without using IDocs whether it is sender side or receiver side". Please help me.
    Thanks in advance
    Srihari.

    Without using BPM will be little longer process. But the alternative way is to add one more receiver in the receiver determination and send some file to that location with the actual mapping getting executed for the actual receiver. and in the second interface you can get the file created at second receiver back to the source location. But this will be little long as compared to synchronous scenarios.
    Flow:
    Source
              Receiver 1--> Actual mapping as per requirement
              Receiver 2(For Ack)--> Create a mapping with blank file sent to Receiver
    Receiver 2-->File Adapter--> Source through 2nd mapping/interface and keep the File adapter pooling interval around 5 sec or less so that you can get the file back to source location.
    Regards
    Anand

  • BPM and IDOCs

    I have an scenario where I have to create sequentially several IDOCs.  This can be created through BPM but my concern is each IDOC has to get processed before the next IDOC is created, is there a way I can check to see if the IDOC was processed.  I was thinking of calling a BAPI to check if the IDOC was processed.  Is there any other way to handle the above, if so would appreciate your input.
    Thanks in advance for any suggestions.
    Sunil Achyut

    the standard way to check if an IDoc has been processed is to use the ALEAUD IDoc which serves like an acknowlegment for IDocs. XI will automatically translate the differenet IDoc status values into the corresponding acknowledgment status, so you can use a send step with application ack in the BPM and the BPM will only continue processing when an ALEAUD with a status corresponding to permanent positiv application ack has been received.
    Here is some information on the usage of ALEAUD:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6550507d11d18ee90000e8366fc2/content.htm
    and here is a how to document for acknowledgments with IDocs using ALEAUD: https://websmp102.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
    Regards
    Christine

  • BPM and Dynamic JMS

    Hi
    Here's a sample code written to receive a message from a JMS Queue. The external resources to connect to the JMS queue are configured.
         logMessage ":::::::Before Receiving:::::::"
         jmsMessage as JmsMessage= receiveMessage(DynamicJMS, configuration : "jmsConfig")
         logMessage ":::::::Receiving:::::::"
         msg as String=jmsMessage.textValue
         messagId as String = jmsMessage.messageId
         logMessage ":::::::message received is :"+msg
    This code is written in the Global Automatic Activity which is configured as an Automatic JMS Listener.
    The weird thing is that when I debug the method in BPM Studio(10.3.1), it works fine and I am able to receive the message.
    However when I start the Process Engine, I find that the message is not received and the logs show the following error:
    The method 'CIL_globalAutomatic' from class 'Sample.BPMOSB.Default_1_0.Instance' could not be successfully executed.
    Caused by: java.lang.NullPointerException
    fuego.lang.ComponentExecutionException: The method 'CIL_globalAutomatic' from class 'Sample.BPMOSB.Default_1_0.Instance' could not be successfully executed.
    +     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:519)+
    +     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:273)+
    +     at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:219)+
    +     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)+
    +     at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)+
    +     at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)+
    +     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)+
    +     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)+
    +     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)+
    +     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)+
    +     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)+
    +     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)+
    +     at fuego.server.AbstractProcessBean.runGlobalJmsActivity(AbstractProcessBean.java:3023)+
    +     at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:113)+
    +     at fuego.component.Message.process(Message.java:576)+
    +     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)+
    +     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)+
    +     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)+
    +     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)+
    +     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)+
    +     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)+
    +     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)+
    Caused by: java.lang.NullPointerException
    +     at Sample.BPMOSB.Default_1_0.Instance.CIL_globalAutomatic(Instance.xcdl:11)+
    +     at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)+
    +     at java.lang.reflect.Method.invoke(Unknown Source)+
    +     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:512)+
    +     ... 21 more+
    Please, help me, I have spend a lot of hours into this...
    Edited by: user13017288 on May 6, 2010 4:55 AM

    Hello,
    It seems doable without using BPM.
    step1 : Idoc > PI(7.1) <> JDBC stored procedure call
    step2: If the Sync. JDBC call is successful then make a sync. BAPI call to R/3.
    You can use a two-step mapping.
    1.) The first one calls the stored procedure using UDF or Java Mapping (as was suggested in earlier threads)
    2.) The input to the second mapping will be the response from 1. You can use RFCAccessor to execute the BAPI.
    step3: If JDBC all fails ( in step 1 ) it should tigger an emial and do not make BAPI call ( do not execute step 2).
    Use XI/PI alerting framework for failed messages. The BAPI call can/cannot be executed by using a try-catch statement in the root node of 2nd mapping (1..1 occurrence), return suppress in the root node if conditions are not met or return a value if otherwise.
    Note: Consider this blog in your design, /people/thorsten.nordholmsbirk/blog/2008/11/04/why-xi-mappings-should-be-free-of-side-effects
    Hope this helps,
    Mark

  • Idoc Acknowledgements and Idoc Packaging

    All,
    I am implementing a requirement wherein we need to post 2 different types of Idoc's from our BPM.  The Business requirements is such that until the Idoc 1 is not processed by the R3 system, the Idoc 2 should not be posted from XI as there is dependency in the data.
    This can be addressed using  Application Acknowledgements. The solution to this is to use the send step in my BPM with application acknowlegement. Until the application acknowledgement is not received for the first send step , the next send  step will not be processed and so things will / should work fine.
    The problem comes in the fact that the Idoc's being sent out of XI use Idoc Packaging, ie., the First Send Step uses Idoc Packaging to post multiple Idoc's to the target system.  A question that arises due to Idoc packaging and Idoc ack's are,
    <i><b>How will the Idoc Ack's be sent back to XI?</b></i>
    I have read through the online help and it states that every ALE AUDIT Idoc can contain the status of maximum 500 Idoc's. Now, in  my  case , when using my Idoc packaging, if the number of Idoc's are greater than 500, how will the Application Acknowledgement for the Idoc's work?  Will I still get a single acknowlegement in my BPM or will I get multiple acknowledgements? Will Send Step with Application acknowledgement still hold good?
    Any ideas, thoughts / experiences on using idoc ack's with idoc packaging?
    Regards
    Bhavesh

    If I undestatood correcty you have 2 send step, the first send a message containing multiple IDoc (IDoc Packaging). In this first send step you set the application Acknowledgements.
    I think that this is not managed from the BPM, bacause the acknowledgements will come someone positive and someone negative, and so when the first send step will be completed ?
    I think that the solution must to be changed a little bit, or removing the IDoc Packaging, or removing the wait of Acknowledgements.
    Also take in mind that if you use a BPM with many possible correlation (Acknowledgements) you will have bed performances.
    Regards,
    Sandro

  • Difference between IDOC Bundling and IDOC Packaging

    Hi,
    Can anybody please explain the difference between IDOC bundling and IDOC packaging?
    Thanks,
    Loveena.

    Hi,
    IDoc Bundling is the changing the occurance of IDoc.
    In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
    1.Import the IDoc to XI.
    2.Export the IDoc(i.e XSD format) and save it to the local machine.
    3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
    4.Save it as an XSD file Itself.
    5.Import the XSD file in the IR under the External Defination.
    6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
    Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
    IDoc Packing is collecting of IDoc
    <a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
    Regards
    Santhosh
    Remember to set the thread to solved when you have received a solution
    [url=Use a Good Subject Line, One Question Per Posting - Award Points;  Use a Good Subject Line, One Question Per Posting - Award Points[/url]

  • New to xi and idocs

    hi,
    can u pls tell me how to create idocs and how to use that idocs in xi.
    regards
    Sri

    Hi,
    Firt you should create IDoc in R3 and that Idoc structure to be imported into XI.
    -In name space , select imported objects option and enter the system information
    - under imported objetc - right clickand import objects and enter the app server details and system no and user,pwd ,,
    later import the required Idoc. into XI..
    See below links regarding Idoc related Blogs..
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
    Some documets regading ..
    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
    Please check this online document for ALE and IDoc.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Regards
    Chilla..

  • Design Question - BPM and dynamic JDBC adapters

    Hello,
    I need help to finish my scenario.
    scenario:
    step1 : Idoc > PI(7.1)  <>  JDBC stored procedure call
    step2: If the Sync. JDBC call is successful  then make a sync. BAPI call  to R/3.
    step3: If JDBC all fails ( in step 1 ) it should tigger an emial and do not make BAPI call ( do not execute step 2).
    I have 200 SQL servers and each time IDOC goes to any one of these 200 servers  ( yes, only one server ) , depending on the connection parameters in one of the idoc segment.
    Questions:
    1. Can we do this without BPM?
    2. can we configure dynamic JDBC adapte depending on the login credentials in IDOC ( server name, port, user name , passwore).
    3. If dynamic JDBC adapter configuration is not possible, what should be my design. Do i need to create 200 communication channels and 200 rec. determination, 200 interface determination, 200 receiver agreement..I dont think this is a good design

    Hello,
    It seems doable without using BPM.
    step1 : Idoc > PI(7.1) <> JDBC stored procedure call
    step2: If the Sync. JDBC call is successful then make a sync. BAPI call to R/3.
    You can use a two-step mapping.
    1.) The first one calls the stored procedure using UDF or Java Mapping (as was suggested in earlier threads)
    2.) The input to the second mapping will be the response from 1. You can use RFCAccessor to execute the BAPI.
    step3: If JDBC all fails ( in step 1 ) it should tigger an emial and do not make BAPI call ( do not execute step 2).
    Use XI/PI alerting framework for failed messages. The BAPI call can/cannot be executed by using a try-catch statement in the root node of 2nd mapping (1..1 occurrence), return suppress in the root node if conditions are not met or return a value if otherwise.
    Note: Consider this blog in your design, /people/thorsten.nordholmsbirk/blog/2008/11/04/why-xi-mappings-should-be-free-of-side-effects
    Hope this helps,
    Mark

  • Regarding Future WLI Products, BPM and diiference with Aqualogic

    Regarding Integration and BPM products from BEA I have the following queries:
    1) What is the next major release for Weblogic Integration product and what Enhancements will be there?
    2) Which BEA product is going to have Business Process Management (BPM) functionality supporting BPEL Server and BPEL designers?
    3) How BEA differentiates the BEA AquaLogic from BEA Weblogic Integration?
    regards,
    neeraj
    ?:|

    I found some more information here:
    Workflow in SAP NetWeaver
    I still look forward to more insight as to when to choose BPM and workflow!

  • Is there a way to see on itunes to all my songs the bpm and the key to every song?

    I have some external programs such as BPM Analyser or Mixmeister that i can scan all my songs and have the bpm and the key to every song!Is there a Plug-in or something else that i can have that as a "category" on Itunes so dont need to open another program to do that?It will be useful to the same list to have all and don't need to use external program.If someone know something about that please help.

    There's a field and column for BPM in iTunes - control-click on any of the column headers to see the full list, from where you can select the BPM column to appear. This if course presumes that the utility you're using will write the BPM information into that field; most will. There's no specific field for the key signature, so the utility would have to write that information into another field such as the Comments.
    Regards.

  • PI 7.1 scenario -- File to File , File to IDOC  and IDoc to File Scenario

    Hi All,
    *I have PI 7.0 . I have in that File to File , File to IDOC  and IDoc to File Scenarios*
    File to File -- This scenario is working fine.
    File to IDOC   --  Setting done in PI 7.0 like SM59,  IDXI, IDX2  and in R/3 like SALE (logical system)---  This scenario is working fine.
    IDoc to File  --  Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
    Now I need to move to PI 7.1  -- for File to File , File to IDOC  and IDoc to File Scenarios.
    Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
    If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
    Regards

    >
    Rickkk wrote:
    > Hi,
    >
    > Idoc metadeta is updated through idx2?
    >
    > Regards
    If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
    You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

  • What is inbound XML message type and idoc type in Purchase Order response

    Hi ,
    We are on SRM 7 ECS , support pack SAPKIBKV08.
    We have a process in which vendor will send a Purchase Order response  which will be
    converted to XML format by a middleware. This XML message will come to
    SRM and post a POR. I want to do the EDI mapping for this XML message,
    but there is no message type and idoc type in SRM for Purchase Order
    response. How do I map my message type in SRM to the vendor sent fields
    in middleware .
    Please advise
    Rgds
    Sumendra

    Hi,
    You can process with XML without IDoc.
    Vendor->  (XML) -> PI -> (XML) -> SRM.
    Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
    http://esworkplace.sap.com
    Regards,
    Masa

  • Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

    Hi Experts,
    Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
    What objects i can skip.
    My PI system is 7.3 dual stack.
    I have seen below blogs, still its confusing to me.
    When and how to create an scenario in SAP PI without mapping objects.
    Pass Through Scenario with no Mapping in PI 7.1
    Appreciate your help on this.
    Regards,
    Mohan.

    Hi Mohan
    In pass thru interface you don't need to create any ESR objects, only ID objects are required.
    Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
    Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
    Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
    Regards
    Osman

  • Difference between BAPI and IDocs

    hello all
    what is difference between BAPI and IDocs

    Hi,
    BAPI
    One of the big plusses for BAPIs is that the interface and function are not supposed to change.  This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
    Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
    The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
    You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
    BAPIs probably have better performance since they don't do the screen flow processing.
    In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
    BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    IDOC
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed.   Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data.   The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    Regards,
    Bhaskar

  • How to start with ALE and Idocs

    Hi,
    I want to start with ALE/Idocs, Could you please guide me from where should I get the docs for that.
    A lot of thanks in Advance

    Hi Nitin ,
    Pls go through the book by Arvind Nagpal , one of the best books that no one should miss.
    Have a look at this site as well
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/
    Check this thread, where you have step by step creation of IDOCs:
    idocs
    Check these links, where you get the complete information on IDOCs:
    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.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    Regards,
    Vvieks

Maybe you are looking for