Mass idoc corrections

Experts,
I have a requirement where i have to mass edit about 70000 idocs which belong to different IDOC types
which has a wrong value for a particular field in a segment. I need to replace with correct value and reprocess the idocs.
Is there any standard Tcode / Program which can help me with Mass IDOC corrections (or) in
any other way this mass correction be accomplished. This data is too huge to perform manually .
I already posted this question and i am yet to get a solution for this . It will be great if you can help.
Regards,
Nick

Hi Nick,
I would not suggest doing what is in the above link.  Undoubtedly a program is required.  However, I would do it the same as editing a single IDOC in via WE02.
Firstly identify all the IDOCs that you wish to process (various ways to do this) and then call FM (for each IDOC):
EDI_DOCUMENT_OPEN_FOR_EDIT
EDI_CHANGE_DATA_SEGMENT
EDI_DOCUMENT_CLOSE_EDIT
Basded upon your IDOC type you would know the segment name/structure to edit.
You can then re-process on-mass via transaction BD87
Cheers
Pete

Similar Messages

  • Problem with mass IDoc for Material Master

    Hi All,
    Can anyone suggest a solution to work with mass IDocs for Material master?
    We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
    Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
    Regards
    Pooja

    Hello Pooja:
    The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
    In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
    However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
    The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
    Hope this helps.
    Regards,
    Jorge.

  • Mass Idoc creation

    Hello Friends,
    Let me know if there is anyway to mass create idocs from file , Looking for program or transaction?
    Regards
    Prashant

    Hi,
    Check this link for more info.
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a670f507d11d18ee90000e8366fc2/frameset.htm
    Cheers
    VJ

  • Mass idoc deletion

    I need to perform a mass deletion of idocs over a year old. I believe that transaction we11 (program RSETESTD) can be used to delete idocs. Does we11 completely remove all traces of the idocs? Is this best practice or should idocs be archived first and then deleted from archive?
    Regards
    Brian.

    legal requirements are rarely made specific and vary from country to country (or even within)
    authorities are usually only telling you to keep data that is needed for tax purposes (or similar).
    so one company is identifying IDOCs as subject to this fulfillment, while others dont. (and it may depend as well on your external auditors - which is again usually just a individual person with his opinions, and a collegue of him auditing a different company may have a different view on this)
    You may have to distinguish by IDOC type , e.g. if it is an IDOC to ALE a customer master from ERP system to a GTS system, or an IDOC that is used to post an EDI invoice to your financial books.
    we are archiving IDOCs and keeping them the usual retention time in our archives

  • Mass idoc mail has been sent to many users

    Dears,
      recently many user got lots of mail with title 'EDI: Incorrect status for inbound IDoc' in their inbox .
      i have checked these standard inbound idocs , and the process code has been linked to one task, such as TS00008068.
    Via we19 i have created one error idoc and i have got one mail in inbox with title
    'EDI: Partner profile not available '.
      But such mail with title 'EDI: Incorrect status for inbound IDoc' has been to sent many users and i can not find what error triggered such workitem....
      should i set one agent in the agent assignment of standard task ?

    i just found that all these message with title 'EDI: Incorrect status for inbound IDoc' has been triggered with task TS30000020.
      any advice ?

  • How to correct the idoc  data in XI and repost

    Hi ,
    I doing file to idoc scenario, In this scenario  i am posting two target msg from one source msg , now the requirement is that second  target msg  is to validated against first target msg and if the condition is not met then stop the posting of second target msg and flag and error. after that target source msg needs to corrected and posted...
    For eg one target msg is payment idoc and second is sales idoc, i need to validate the sales and payment amount and if it does reconcile then stop the sales idoc , correct the ampount and post it
    Any ideas !!!!!!!!!!!!!
    Regards
    Swatantra

    Hi Dirk
    Thanks for the reply
    This is a retail scenario
    The source file contains the sales and payment against the artcile sold. sometimes the sales amount varies to payment made due to currency conversion or some other reason. There is tolerance limit for this variance , but if this differnce is above the threshold then sales idoc should not be processed and the data needs to check and corrected .....
    BTW i am doing abap maaping for  this scenario
    Any clues
    Regards
    Swatantra

  • Problems with new fields added for tc MASS for material master data.

    Hello to all.
    We created new fields in MARA table and added to the process of the tc MASS. We made the following steps and it almost works correctly:
    1-Add new fields to the object ZBUS1001, copy of bus BUS1001.
    2-Add new fields to table T130F
    3-Add new field to structure E1MARAM.
    4-Add new fields to structure CL_MMH1.
    5-Add new fields to structure MARA_TMP.
    6-Created a function module to control that the new fields not filled in MASS have a "/" value.
    If we run the mass for our objetct ZBUS1001 and put a new value or modify the value of new fields, the tc MASS works correctly.If we want to delete a value leaving the value empty,click to the carry out a mass change button and save the change, the system don´t delete the value and keep the first value.
    Do you know what the problem is , and what step we didn´t make it.
    Thanks in advance.
    Edited by: tonnetti pablo on Feb 6, 2008 7:45 PM

    Hi,
    Check ZTERMDT is checked under Attribute list as below.
    Hope it helps..
    regards,
    Raju

  • Vendor email address in IDOC

    We are trying to create a vendor payment file to be sent to our bank in IDOC format.   The IDOC type we are using is PEXR2002.   We are not able to populate the vendor email address (from vendor master data - SMTP_ADDR) into IDOC segment E1EDKA1 even though the email address is shown on the vendor master.   All other vendor master address information, such as Phone, Fax, show up correctly in that segment.   Does anybody know how we can populate the IDOC with the email address? 
    Thank you.

    Thanks, Ravi.   We are trying to avoid creating a user exit and since all the other vendor info populates the IDOC correctly, we're hoping there's a 'standard' way of getting the email there as well.

  • Missing/left-out segments/fields in IDocs - best practise

    Hi all,
    when SAP generates IDocs, occationally certain field/segments, instead of being blank, will not
    show up at all which causes mappings in XI to go awry. For instance, in a two line sales order,
    when you set a reason for rejection for order line 2, the corresponding line in the IDoc will have a
    ABGRU field populated with the reason of rejection's code, however the first line will not have a
    blank ABGRU field but instead it will not have any at all. Now, when you do the mapping of those
    to lines, because the first line doesn't have this field, the ABGRU queue will hold only one value
    which in all probability will end up in the first line when it should be mapped to the second.
    At this point, in lack of a better solution, what I'm doing is to add ABAP code to user exits and
    add a blank/dummy ABGRU field to the lines that do not have any in order to be able
    to map the IDoc correctly. That works but its not ideal. What other options are there?
    Am I missing something obvious?
    Thanks for your input.
    Frustrated,
    Sven

    Hi,
    You could try appending the node function mapWithDefault after the field so that the it will always have a default value instead of being suppressed.
    Hope this helps,
    Mark

  • Inbound function module for IDoc type INFRECMASS01

    Hello everybody,
    What is the inbound function module for IDoc type INFRECMASS01?
    I tried IDOC_INPUT_INFREC (as for IDoc INFREC01), but I got the following message (B1 044): Incorrect function module IDOC_INPUT_INFREC called up
    Thanks in advance
    Roland

    The only difference between INFRECMASS01 and INFREC01 is that repitition of the same segments. However, the standard function module is hardcoded with IDOC type INFREC01, so if you want to use the MASS IDOC copy the standard one and put in the logic to loop around and process the info records one by one.
    There is no standard funtion that can process mass idoc of the info record.
    Regards,
    Ravi
    Note:  Please mark the helpful answers

  • Idocs take time to reach XI from R/3.

    Idocs trigerred from R/3 takes around 45 mins to reach XI.
    What could be the possible reasons for the same??

    Hi,
    Check this from SAP help regarding mass IDOCs settings.
    Mass processing refers to bundling IDocs into packets that are then dispatched and processing in the receiving SAP system. Only one RFC call is needed to transfer several IDocs. Performance is considerably better if you dispatch optimal packet sizes.
    To set mass processing parameters, in ALE Customizing choose: Modeling and Implementing Business Processes ® Partner Profiles ® Generate Partner Profiles. For a given message type you can define the outbound parameters, packet size and processing mode.
    If the processing mode is set to Collect IDocs and transfer, outbound IDocs of the same message type and receiver are sent in a scheduled background job in an appropriately sized IDoc packet. The IDocs can be dispatched in a scheduled background job or in ALE Administration.
    Some distribution scenarios cannot support mass processing of inbound IDoc packets. This is especially true if the application sending the IDocs uses the ABAP command CALL TRANSACTION USING. In this case the outbound parameter PACKETSIZE must be set to "1".
    You can find a list of function modules for mass processing in ALE Development by choosing IDocs ® Inbound processing ® Function module ® Define attributes (BD51). These function modules have input type 0.
    Check this note as well
    Note 706521 - IDoc: Performance improvement when you create IDocs
    Regards,
    Venkata S Pagolu

  • BATMAS IDocs not gettting generated using Change Pointers

    Hi,
    I have scenario where I am supposed to replicate Batch between R/3 & Ware House Systems. So, for this I am using the standard BAPI to generate IDocs correctly for the batch.
    Now, when I go and change the document flow i.e. make changes to the Batch using transaction MSC2N and saving a new document is getting generated.
    Change Pointers are active globally and also on the message type. Now when I use the transaction BD21 to generate IDocs, they are getting created successfully for the distribution model that is existing. Now, when I add a filter in my distribution model based on Plant IDocs are not getting generated.
    Can any one let me know if I missed out any configuration step or else what needs to be done in order to solve this issue.
    Raghuram.

    Is this thread still valid? If not, please close the thread.
    If so, as no response has been submitted, please rephrase your question and/or provide further information to describe your requirement.
    Thanks
    Jason
    SDN SRM Moderator Team

  • IDOC - IDOC scenario with different message types

    Dear Experts
    I will like to have your expert opinion in the following question:
    I have an IDOC -> IDOC scenario. Wherein at the destination system I have a message type which does not exist at the source system.
    Also the IDOC type at destination system does not exist at the source system.
    Let say, I will be creating custom message type at source system (Z****) and will also be creating the custom IDOC type (z****) with the same structure, definition as the destination.
    Now my question is, even if there will be different message types and different IDOC types but with the same structure (the segment level definition
    and field attribute remains the same at both the system). The difference lies with the names. And I have proper mapping though process code.
    Will I be able to receive the IDOC correctly at destination?
    Thanks & Best Regards

    Hi All
    I figured out the answer myself now.
    You got to have same name for message type. All of you said this and this is rite.
    Coming to IDOC type, I did not really got clear idea on this from this discussion.
    But after working on a scenario, I learnt that, you can have different names for IDOCs, but provided that, whichever IDOC type the source system is sending, the same type must exist in your destination as well. Otherwise, system wont process your IDOC. But from mapping point of view, its upto individual how do thay handle mapping inside inbound process code for different idoc types / strucutes.
    Lesson learnt by me, ideally try to keep same name for both logical message and idoc type at both source and destination. If possible try to keep the structure level also the same. This is my view, learnt it the hard way.
    Cheers
    Shane

  • IDOC Creation-ERROR

    Hi All,
           I am using a zprogram to create a an IDOC Using 'Master_Idoc_Outbound'.Here  i am not using any user exist such that,but when i am executing the program i facing an error 26. that is Syntax Error in IDoc(mandatory group Missing).
    I have seen the blogs those are releated to the same error.but that doesn't match my problem.So I need your suggestion and inputs to over come this patch.
    thanks,
    Swathi.k

    Hi Swathi,
    When you have created a custom segment you would have added that as a child segment to a standard and you might have put that custom segment as mandatory in the WE30 transaction.
    And if there is no data for the standard segment then your child segment will not be populated even though the code is written in the userexit and as your custom segment is a mandatory segment in the IDOC definition it will throw the IDOC into 26 status.
    I have given you the explanation on the assumption that your custom segment is a mandatory segment in the IDOC, correct if I am wrong. Tell me what was the function module you have used to created that IDOC.
    Thanks,
    Mahesh.

  • Third party -IDOC -ALE

    Hi friends,
    Is it posssible for third party sales interface between vendor and customer through ALE or IDOC ......if so then how?
    Thanks
    Ivy

    >'Transaction IDX1: Port <XI Port>, client <XI client>, RFC destination  contain errors'
    > Mark Package (IDOCs [1..1]) as having been rejected by SAP peer
    >
    > How has a third party system to be configured, to send IDocs correctly to XI?
    I think the 3rd party system is configured correct, as the message reaches PI server.
    Check IDX1. The metadata provider (RFC destination) has to provide the same structure as the IDoc from 3rd party has.
    So you could enter the receiver of the IDoc as metadata provider.
    Check Sm21 for any valueable entry.

Maybe you are looking for