Middleware: BDoc to IDoc conversion - init and delta

Hi,
First of all let me just say, that I know nothing about CRM (I'm an XI guy), but need to investigate on a matter, so please take that into accound when reading this post and responding to it.
Scenario:
Business Partners, Business Transaction Messages (orders and activities) need to be replicated to an external system. This is achieved by converting BDocs for the respective messages into IDocs via CRM Middleware and then sending IDoc to XI which in turn posts data to external database. This process should function both INIT and DELTA.
So far so good.
The problem is when having created for instance a new direct order and saved it. The BDoc is generated and converted to IDoc (CRMXIF_ORDER_SAVE02). In the fields OBJECT_TASK in the IDoc I get the expected 'I' for INSERT. This is what I expect.
Now, if I make a change to the order and saves it again the generated IDoc still contains just an 'I' for INSERT in the before mentioned fields. This is not to be expected - should be an 'U' for UPDATE, but this does not happen.
Anybody have any ideas why this happens and what is wrong?
Best Regards,
Daniel

Hi,
Thanks for your answer. I'm on CRM 5.0. The note you mentioned seems not to be related to my problem. My question is regarding "download" of data from CRM to XI through CRM middleware. When trying to do this the "change pointers" (fields OBJECT_TASK and/or TASK) are not set correctly in the IDoc's generated by middleware (everything is writtens INSERTs), which means I cannot from XI determine by the data received if I'm to perform an update/insert/delete into the database.
Best regards,
Daniel

Similar Messages

  • Full upload after INIT and Delta

    Hi Experts,
    a quick question - If there is INIT and Delta infopackage running  and I do another infopackage with full update option, will there be any issue in Delta?
    when do I need to run repair? only when there is possibility of duplicate loading?
    Thanks - SM

    Thanks Srini/Vikram for your respone.
    when there is deltas already running for the datasource , you can't request for Full but you can request using 'Repair full' which will acts and extract data as full load and it won't disturb present delta's
    >>. Thanks Srini. thats bottom line... after delta, you need to run repair full not full. and repair full will also pull data from setup table (history). I was thinking repair full is for taking care of duplicate, but dups we need to remove manually.
    where is repair full option in IP?
    where I can see all INIT conditions for a infopackage? for example INIT was done 3-4 times.. year 2001-2002, 2002-2003 etc, so all these INIT crit should be stored somewhere?
    Edited by: toti shu on Aug 31, 2010 5:08 PM
    Edited by: toti shu on Aug 31, 2010 5:11 PM

  • Need suggestions in doing my Init and Deltas

    Hello Experts,
    I am using the standard SALES OVERVIEW cube to store the sales data. I have introduced the custom built ODS to store the order level data in my flows. I am about to test my flows but I am afraid if the custom built ODS in the flows will create any problem while doing deltas as the standard Datasources are designed to update the cube directly.
    One more thing is, If I do the init and deltas now for my testing, is it possible to delete all the data from ODS and the cibe and do the init again and start the deltas? Will the custom ODS be a problem in such scenarios? I am assigning the 0RECORDMODE to 0STORNO in the transfer rules.
    Rgds,
    Nene.
    Message was edited by:
            Nene BW

    Hi
    You can test init and delta loads in both the ODS and Cube
    You can later on delete all the requests in the ODS and cube if you want to
    init again
    Assign points if useful
    Regards
    N Ganesh

  • CRM Bdoc to IDoc Conversion

    Hi All,
    I have extended BUS_TRANS_MSG Bdoc with custom Fileds ( as per requirement) and am looking to Convert the BDoc to IDoc.
    So Can any one know how to convert Bdoc to Idoc in SAP CRM 7.0.
    Kindly help me on this.
    Thanks,
    Raja

    Hello,
    The best way to interface data from CRM to external systems is by using the XIF adapter.
    The XIF adapter can be used to create outbound extractions via CRM middleware. Look in this forum or read the documentation for CRMXIF_ORDER_SAVE in your system to get a basic understanding.
    Basically you need to setup an outbound subscription to the XIF adapter for all business transactions.
    If you want to brute force the problem use the CRM_ORDER_READ function module combined with custom selects on CRMD_ORDER_INDEX to grab most of the data needed.
    some helpful links:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f?quicklink=index&overridelayout=true
    XIF adapter
    regards,
    Wim Olieman

  • Init and delta uploads using process chain

    Hi,
        I have a scenario where for the first upload i use init upload for that i have an infopackage now for the subsequent uploads i.e delta upload i get the option for the same only once i have run the init upload.
           so the doubt is can i use a process chain defined to carry out the whole task?????
    Regards

    Hi Virat,
    AS init is a one time activity, so what you can do is.
    1> set the init in infopack and run the process chain.
    2> remove the infopack and then include a new infopack with delta option or change the existing infopack to delta option.
    3> schedule the infopack.
    whatever you are expecting is not possible.
    Hope I answered your question.
    THanks and Regards,
    Suneel

  • Performing Init and Init of Delta in BI 7.0

    Hi,
    As we use to create two info packages in BW 3.5, one for "INIT" and another for "INIT of Delta".
    Do we have to create two infopackages in BI 7.0 too?
    If we create two info Packages, then do we have to create two DTP's too?
    Please let me know how does that work.
    Thanks,

    U have to create 2 IP's, and 1 DTP(delta) only.

  • SAP CRM 7.0 -- How tro make Conversion from Bdoc to IDoc

    Hi All,
    I have extended BUS_TRANS_MSG Bdoc with custom Fileds ( as per requirement) and am looking to Convert the BDoc to IDoc.
    So Can any one know how to convert Bdoc to Idoc in SAP CRM 7.0.
    Kindly help me on this.
    Thanks,
    Raja

    Hi Raja,
    Is there any reason that you want to convert this Bdoc to Idoc. let me know, will take from there.
    thanks

  • Idoc Conversion rule, Change pointers and Filters

    Hi Experts,
        Please any one can help me out, i need material or clear picture about Idoc Conversion rule, Change pointers and Filters where we can use these concepts what is the befit for these concepts.
    Thanks in advance,
    Ramesh.

    Hi,
    Check this link. It has got some of the tutorials you are looking for.
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    Cheers
    VJ

  • Question on Deltas after Init and Full load

    Hi
    We have an ODS X pushing data to two cubes A & B. ODS X data is initialized to Cube A long back and deltas are loading every day. Now We have recently created Cube B and made a fulll load from ODS X and loading the Deltas from ODS X with same info package we are using to load the deltas in to cube A. Do we get any data inconsistencies if we load like this ? Do I need to make a new init for Cube B to get proper deltas ? I'm hoping that Deltas will automatically take care of reversal in Cube B too...Please advice.
    Thanks
    Sam

    This looks fine, since u have already done full load from X to B, and currently loading delta to both A n B , it is fine, no need for new init.
    Regards,
    Rathy

  • Conversion of purchasing idoc to xml and sending with FTP to supplier

    Hello,
    I have a question about something i am not very familar with. And i could not find the answer in this forum.
    We have a supplier who wants to receive our orders by EDI.
    The plan is to convert the IDOC to XML and to send this XML by FTP to our supplier.
    Could anyone give me some hints to achieve this.
    usefull help will be rewarded.
    Gr., Frank

    Hi,
    1. Create XML port in WE21.
    2. Configer the partner profile in WE20 for required message type.
    3. Access the file by using transaction AL11.
    Thanks,
    Asit Purbey

  • No initial load of Customers, Material and delta load of Sales Orders.

    Hi Experts,
    I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
    But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
    - Customer_main load, it was succesful, but no BP's of R/3 are available.
    - Material, it failed in SMW01, SMQ2, the errors are:
    Mat. for Initial Download: Function table not supported
    EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
    EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
    Plant xx is not assigned to a business partner
    - Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
    We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
    Thanks,
    -Pat

    Hi Ashvin,
    The error messages in SMW01 for MAterial initial load is :
         Mat. for Initial Download: Function table not supported
         EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
         EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
         Plant 21 is not assigned to a business partner
    I have done the DNL_PLANT load successfully. Why then the plant error?
    Some of the messages for BP:
    Messages for business partner 1331:
    No classification is assigned to business partner 1331
    For another,
         Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
         City Atlanta does not exist in country US
         Time zone EST_NA does not exist
         You are not allowed to enter a tax jurisdiction code for country US
         Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
    Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
    Till these 2 are not solved, I cannot go into the Sales order loads.
    Any ideas will be greatly appreciated.
    Thanks,
    -Pat

  • Idoc to flatfile and mail

    Hello,
                 I have a scenario  where i am converting the idoc to file and mailing the same after converting it to flatfile .I have used TransformMessageBean for doing so.Now I need to implement the TO Field (mail )dynamically based on the payload.
    I tried to use the MultiMapping by using mail definition provided by XI ,but it results in mapping error.\
    Can somebody guide me on this.
    Thanks in Advance
    Rajesh

    Hello,
               I  have tried to do the same with the MessageTransformBean and two features are working fine independently.
    1. Converted the file into Flatfile and mail
    2. Execute the XSL Mapping for dynamic receiver.
    Now i want to combine both above features i.e after transforming the content to flatfile ,i need to sent this file to  recipient based on payload field.
    I tried to execute the same but i am stuck at XSLT error ,saying
    com.sap.aii.af.ra.ms.api.RecoverableException: Error in XSLT Conversion: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 48, 44, 52(:main:, row:1, col:3):
    Awaiting for replies
    Rajesh

  • Receiving binary IDOC via Queue and convert it to XML-IDOC

    Hello,
    we are focusing the following scenario:
    We receive an plain, binary IDOC in a MQSeries Queue. We want to pick it, transform it and place it into R/3 (of course using XI 3.0). Afterwards the other way around.
    I know the Howto for the ABAP mapping from XML-Idoc to plain IDOC. This may also work for our scenario. Do you agree?
    The other way around is more difficult. I assume that - since the IDOC adapter resides in the ABAP stack - we cannot re-use an existant adapter module in the JMS adapter. Right?
    I heared about JCO capabilities of "xmlizing" Idocs - but did not find hints within the javadoc. Anyway, would this really be the preferred way - writing an user exit for the adapter using JCO - to handle this? There must be a way to do it better, must it not?
    How did you guys face this problem - I think its a common one...
    Any starting points for a discussion are appreciated....
    Greets,
    helge

    Hi Helge,
    For the conversion of the incoming flat message, one could imagine a similar ABAP mapping as the one described for the XML->flat message conversion. The function module IDX_IDOC_TO_XML could be a good starting point for your search.
    To perform conversions in the Java stack (e.g. in an adapter module) might be a quite complex task since you first have to get the IDoc metadata. And there you cannot reuse existing function modules.
    Best regards
    Joachim

  • How to catch Delta Initialization and Delta Update in a Function Module

    Hi Experts:
    I'm developing a FM to extract data from R3. I wonder if anybody knows how to catch when i'm making a delta initialization and a delta update in my FM, because i have different parameters and routines from each one.
    Thanks in advanced.
    Points for helpfull answers.

    Hi,
    Keep one dummy date field in the structure. Make this dummy date field as delta enabled field. When you do Init load this date field value will be blank and next time when you do load it will have the last upload (in this case init load) date. You have to write a code before open cursor as below:
          LOOP AT s_s_if-t_select INTO l_s_select.
                                  WHERE fieldnm = '(dummy date field name)'.
             l_date = l_s_select-low.
          ENDLOOP.
    l_date will have the last upload date. This you can use to select the delta records from the table or for the further processing.
    If you want to check the value during Init or delta load, go to RSA3 and debug it(Don't use F - Full load. Use I or D in the update field).
    Hope this helps.
    PB

  • Error in IDOC: XML IDoc conversion: No known segments identified

    Hi Team
    i am facing error in my scenario.  When we are testing my  interface, another  Interface is picking up the Messages and resulting into an error.
    There is no mapping involved in my scenario.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    please help me out
    thanx in advance

    Hi,
      Do The following:
    1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
    2) Have a look into this SAP Note- 742093
    3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
    4) If any field which is mandatory in the idoc must not be disabled...take care about it.
    Hope this will help you...
    Regds,
    Pinangshuk.

Maybe you are looking for