REG:Grouping of Idocs

Hi All,
          I have a Idoc to file scenario , where i need to group the idocs with respect to a field from the Idoc.
Is this possible in graphical mapping? If not which mapping is preferable.
Thanks,
Thomas

Hi Thomos,
Grouping Idocs : It is possible in Graphical mapping using BPM and With Out Using using BPM i am explaning you BPM Part Below:
Procedure for grouping Idocs:
Eg:
There are two Message Mappings involved in the whole scenario. First mapping is N:1 Mapping which will be used in BPM and second Mapping is 1:1 Mapping:
1.     First Message Mapping à N: 1 u2013 Mapping between IDoc (occurrence u2013 0...unbounded in "Messages" tab) to IDoc with changed occurrence of its top node (IDOC) as 0...unbounded. This message mapping will be used in BPM u2013 transformation step.
Use BPM:
Description: This BPM collects all Idocs for 10 minutes which are of Message Type (ZMATMAS05) according to unique Fields in the control segment Eg: RCVPRN (Reciver Partner Number ) and calls N: 1 mapping to bundle the collected Idocs in a One External Definition for that IDOC.
Use
You use a wait step ( ) to incorporate a delay in a process. Usually, you use a delay to define when the next step in the process is to start. You can define a delay as either a point in time or a period of time.
At runtime, the step waits until the specified point in time is reached or the specified period of time has passed. The system then continues the process by proceeding with the next step.
A background program should be scheduled to run every 10 minutes to analyse any material records that have been created or changed or deleted that have occurred to the material master records in the last minute.
Thanks,
Satya Kumar

Similar Messages

  • Reg: File to Idoc Hierarchial mapping

    Hi Experts,
    We have a scenario of flat file to idoc where in we have 4 segments(01 to 04)(with hierarchies) in source file to be mapped to idoc. We have followed Riaz blog    http://www.riyaz.net/blog/xipi-convert-flat-file-to-deeply-nested-xml-structures-using-only-graphical-mapping/.on mapping flat file to deeply nested structures . 
       We have encountered one unique issue in the intermediate level mapping where, when assigning hte id numbers, the instances of one segment are grouped together.  This is creating a problem. 
    Ex: in source str we have nodes in the order
    01
    02
    03
    04
    02
    03
    04 and so on..
    After the test of intermediate mapping, it shows teh follw sequence:
    01
    02
    02
    03
    03
    04..
    The node seq in the target str should have been similar to that of the source.. but here its not so.. 
    if i am using just one instance of 01 till 04 nodes.. the final xml str is created perfect.. Can any please let me know what could be the possible error??
    Or please let me know if there is any other simple procedure to finish this.
    Thanks in advance, awaiting your reply..
    Best Regards,
    Giri

    Hi,
    Please go through the following links..
    http://wiki.sdn.sap.com/wiki/display/XI/SampleJAVAMappingcodeusingPI7.1+API
    http://wiki.sdn.sap.com/wiki/display/XI/UsingPI7.1APIforJavamapping
    and also,
    http://help.sap.com/saphelp_nwpi71/helpdata/en/bd/c91241c738f423e10000000a155106/content.htm
    If u get any doubt u can post the problem....
    Babu

  • How to find out error segments in a group of Idocs

    Hi,
    1. For every 5 minutes Idocs are coming in to R3 from some third party systems, and this scenerio some of the Idocs are in failed status as well.
    My doubt is how to see the all segments at a time, since there might be some problem with the data, so I need to check the each and every segment all time.  Is there any way to findout all segments at a time for the group of the idocs of the same message type.
    2. How to find out the error in segments of the idoc.
    Many thanks in advance.
    Thanks.
    Ahmed.

    Hi Mujeeb Ahmed 
    I dont have SAP System in front. Any way check the menu bar, there you can fine SEGMENT WITH ERROR OPTION
    Regards
    Kumar

  • Reg:file to idoc scenario

    In a file-xi-idoc scenario i created a business service for legacy
    system and a business system for R/3 receiver system
    i didn't assign logical system for the sender business service
    and assigned a logical system for the reciver business system
    so while maintaining partner profile in the R/3 system
    i have to give partner no:
                        partner type:
    here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
    so then what do i need to give in the above two fields?
    answers required briefly

    Hello,
    you know this pdf:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
    Could be helpful.
    Regards
    Patrick

  • Reg: JDBC to IDOC Scenario Message Mapping

    hi Friends
    i am designing a Scenario JDBC - IDOC for accounting document interface using ACC_DOCUMENT03 idoc.
    i need the mapping program for that to map the JDBC fields with the IDOC fields, so can anyone help me the mandatory fields and the constant values for the IDOC which has to be mapped.Along with this can i know why the constants will be assigned to the fields like Begin =1 , MSGFN = 009 etc how these constants are defined.
    Thanks&Regards
    suman.

    Hi,
    for mapping constants in graphical msg mapping, select your target IDOC field..........then you have a constant in the below screen.........click it and then double-click on constant to change the value of the constant field.........then map this constant to your target IDOC field.
    for knowing which are the mandatory fields, ask your functional guys to tell you the mandatory fields in data segment of your IDOC and regarding Control segment EDIDC, you have to map fields which have sender and reciever system details.
    Regards,
    Rajeev Gupta
    Edited by: RAJEEV GUPTA on Feb 2, 2009 7:55 AM

  • Reg:Steps in IDOC Scenario

    Hi,
        I am very new to IDOC concept so can anyone tell me what is the use and why do we want to create,
    1)RFC Destination
    2)Port
    3)Logical sysytem name
    4)Partner Profile ,in IDOC Scenario and also let me know the steps that I have to implement  while doing that scenario.
    Thanks in advance
    B.Lavanya

    Hi,
    This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
    To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
    STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
    We need to do the following settings in XI
    1)   Create an RFC Destination to the Sending System in transaction code (SM59)
    a)   Choose create
    b)   Specify the name of the RFC destination
    c)   Select connection type as 3 and save
    d)   In the technical settings tab enter the details SAP SID/URL and system number#
    e)   Enter the Gateway host as same details above SID/URL
    f)   Gateway service is 3300+system number#
    g)   In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code  IDX1
    a)   Select create new button
    b)   Enter the port name as SAP+SID (The starting char should be SAP)
    c)   Enter the destination client
    d)   Enter the RFC Destination created in SAP R/3 towards other system
    e)   Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a)  Create new
    b)  IDOC Message Type
    c)  Enter port created in IDX1
                        SETTINGS IN SAP R/3
         We need to do the following settings in R/3
         Logon to Sap R/3 System
    1)   Create an RFC Destination to XI in transaction code  (SM59)
    a)   Choose create
    b)   Specify the name of the RFC destination
    c)   Select connection type as 3 and save
    d)   In the technical settings tab enter the details SAP SID/URL and system number#
    e)   Enter the Gateway host as same details above SID/URL
    f)   Gateway service is 3300+system number#
    g)   In the Logon /Security tab, enter the client user & Password details of Destination system
    h)   Test the connection and remote logon.Both must be succesful
    2)   Create communication Port for Idoc processing Using Transaction(We21)
    a)   First Select Transactional RFC and then click create button
    b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
    d)   Enter the RFC Destination created in SAP R/3 towards other system.
    e)   Save
    3)   Create Partner Profile with Outbound Parameters (WE20)
    a)   Create New
    b)   Create the Partner no. name as same the logical system name of the destination system
    c)   Select Partner type LS
    d)   Enter details for Type: US/USER, Agent, and Lang
         Then Save
    e)   Select Partner no. and LS which were create above
    f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g)   Select Message type
    h)   Double click on Message Type and Then Enter the details  for Receiving port, Pack size=1 and Basic type
    I)   save
    4)   In Transaction SALE, Create Logical System
    a).  Go to Basic Settings-> First Define logical systems
         and then assign logical systems
    b)   Double click on Define the logical systems
    c)   Give data for your Logicaal System and Name
    d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e)   Assign the logical system name to the client
    5)   Create Customer Distribution model in the transaction code BD64
    1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3)   Save the Distribution model
        Generate Partner Profiles
    Click on Menu Item ‘Generate Partner Profiles’
        It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
        Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4)   Distribute Customer Distribution Model
        In the menu item  GO to Edit->Modal View-> ‘Distribute’ to the destination client
        Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
                 Step2:Repository
    1)       From the Integration Builder page, select “Integration Repository”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server
    2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
             From the list of Software Component Versions, Choose your own software component version .Click Import.
    3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this  software component. A screen will appear .Switch to display mode. After doing this first add  a namespace under Namespaces.
             Your NameSpace is urn : DSZVFGD
    4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
             After this specify the connection parameters to the R/3 system:
    4.1)     System  :SAPFOX
    4.2)     Client  :800
             Then Save it. The new namespace will be visible under software component version node in the left frame.
             Under the namespace node,  you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
    4.3)     Application server:172.25.5.7
    4.4)     System number:00
    4.5)     User name: DEVELOPER
    4.6)     Password: Password of Sap R/3 system.
             Then click continue .You will find IDOC node. Click on this node and select the   Idoc  which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any  Idoc Structure. We need to create a structure for file only.
    5).      Under your namespace in the left frame, expand the node “Interface objects”. You will find a node “DATA TYPES”
    6)        Create new data types.
    6.1)      Right click on “Data types” and select “New”.
               Your Data Type is :DT_FILE
              In the data type Editor ,Create a structure having Elements of type String  ,  integer,  Boolean , Float etc as per the requirement.
              Save the object.
    6.2)      The Import function for XSD  files enables you to upload message definitions from external sources. The object type “External Definition” is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from “External Definition
              no need to create Data types. They are imported directly as Message types.
    6.3)      To do so, In the left hand frame  Under  ” Interface objects” Create a new object of type “External Definition” and give name to it.
              Select the following.
    6.3.1)    Category: XSD.
    6.3.2)    Messages: From All Available Global Elements.
    6.3.3)    File:
              Once the XSD is imported, click on “Message” tab , You should be able to see 2 messages(Request and Response)
    7).      Create a new Message  Type.
    7.1)     In the left hand frame under “Interface objects”, right click on the “Message types” and select new.
    7.2)     Give a suitable name to the Message type.(MT_ messagetype).
    7.3)     For the section “Data type used” you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
             Save it.
    8).     Create a Message interface
    8.1)    In the left hand frame under “Interface objects”, right click on the “Message Interface” and select new and name(MI_ messageinterface) it
    8.2).   The interface Should be  Inbound  and mode should be Asynchronous  .It should reference your Message type(Use F4 or Search help).
            Save it.
    9) .    Create a graphical mapping  between the target document and the sender .
    9.1)    In the left hand frame ,expand “Mapping objects”. Right click on “Message mapping” and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
    9.2)    As Source message select  your own Idoc .You can choose “Search  for Integration Object”.As a reminder you can find your Idoc or Rfc under Software Component-  >     Namespace->Imported Objects.
    9.3)    As Target Message you can choose your Message type  .Choose “Search  for Integration Object”.
    9.4)    Now that we have defined the  Source and Target message, we can start defining the Mapping rules.
    9.5)    Map the fields of  Source document  to the equivalent fields in  Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
            Save It.
    9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
    9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
    10).     Create an Interface Mapping.
    10.1)   In the left hand Frame  expand “Mapping objects”. Right Click on “Interface Mapping” and  Name it. You are in a Interface Mapping Editor .Assign the following References.
    10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose” Search  for Integration Object”.
    10.3)   Target interface:    Your Inbound Interface( The Target document interface).
            Then Select  'Read Interface' and Assign your  'Mapping Program' .
            Mapping Program: Your Message mapping.
            Then Save it.
    11.)    Finally , in the left hand frame ,go to your change list and Activate it
               STEP 3: Directory
    1)      From the Integration Builder page, select “Integration Directory”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server.
            Create a Scenario Object
    2).     The First Step is to create a Scenario Object
            This will serve as container for all your configuration work. Create and save a scenario object
    3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node “Service without Party” and right –click on “Business System”->Assign Business System
    4)      In the wizard , leave the party name blank and then select  your own Business System. Uncheck the box ”Create Communication Channel Automatically”.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
    5) .    Create a Communication Channel.
    6).     Expand your service and right click on “Communication Channel”. Name your Communication Channel
            Here we need to configure the adapter.
         Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
              For the Receiver, Specify the following Parameters
    6.1       For the adapter type , use the F4 help  and select FILE.
    6.2       Specify “Receiver” since the adapter will be  sending XML files from XI to the  FTP server.
    6.3       Specify the following parameters.
              Transport Protocol: File Transport Protocol.(FTP)
              Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
              Adapter Engine: Integration Server
              For the File system access Parameters, enter the following
              Source Directory:VILAS
              File Name: Input.txt
    6.4       For the FTP Connection Parameters, Specify the Following
              Server: 172.25.7.116
              Port: 21(by default)
              Data Connection: Passive
              Connection security: None
              Connection Mode:  Permanently
              Transfer Mode: Binary
    6.5       For Processing Parameters, Specify the following
              File construction mode: Add Time Stamp
              File Type: Binary
    6.6       For Content Conversion Parameters, Specify the Following
              RecordSet Structure:
              Adapter Status: Active
              The receiver file adapter is now configured. Save your Communication Channel.
               Create an Receiver Determination.
    7).       From the left frame Create a new “Receiver Determination” object. This is the main part of routing process, where you assign a receiver for your message.
    7.1)      Select your sender service and interface.
              Sender:
              Party:  blank
              Service:  Sender service(Business system)
              Interface : Sender interface
    7.2)      In the “Configured Receivers” area ,  choose the Service for the Target System.. Save your Receiver Determination
                Create an Interface Determination.
    7.3)       Next create an “Interface Determination” object. Now that we have defined a receiver of message  ,we need to assign an Inbound interface and an Interface mapping
    7.3.1)     In the Receiver Determination   you just created, have a look at the area “Configuration Overview for Receiver Determination”   at bottom of your screen and press Refresh  for that the Business system you assigned is displayed  in that area as well.
    7.3.2)     In the column “Receiver(Partner/Service)” open the details by clicking the node .The Entry “Not defined” shows you that there is no interface determination present.
               Right click on the Entry “Not defined” and select “ New specific”,  in order to create a new interface determination object
    7.3.3)     You are now in  the screen “Edit Interface Determination”. In the section “Configured Inbound Interfaces” select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
               After choosing the Inbound Interface,  It is shown in the Interface Determination
    7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
    7.3.5)     When you are done ,  Save the Interface determination object.
    8.)         Create a Sender Agreement.
               In the left hand frame , right click on “Sender Agreement” ->New
    8.1)       Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Outbound Interface
    8.2)       In the screen “Edit Service Agreement” use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
    9.)         Create a Receiver Agreement.
               Finally you will create a  'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
    9.1)       Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of your screen click Refresh.
    9.2)       In the Column “Receiver Agreement(Communication Channel) “ right click and select “New Specific”.
               Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Inbound Interface
    9.3)       In the screen ”Edit Receiver Agreement” for the field Receiver Communication Channel use  the input help F4 and select your communication channel. Save and Close it
               Your Configuration is complete. Activate the objects.
    PLZ REWARDS POINTS
    VIKAS

  • Reg File to IDOC scenario with Acknowledgment

    Hi Experts!
    In  a File to IDOC scenario , how to get the  acknowledgment back to PI after posting the IDOC to SAP system and send the acknowledgment to the sender system.
    What setting needs to be done in Sap  and PI? Is it better if we have a BPM or is it good to have another interface to pass the acknowledgment IDOC back to the file sender.
    Regards,
    Srini

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • REG: Error in IDoc adapter outbound processing

    Hi All,
          I had a couple of doubts regarding these IDoc's.
    1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
    "IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
    Can any one help me to Solve my Problem
    2) How to find out whether the IDoc is of synchronous or Asynchronous mode
        and how to  handle the synchronous type of IDoc's
    Thanks in advance.
    with Regards,
    Kalyan Dannapaneni.

    Hi Kalyan,
    IDOCs are only Aynchronous (EO or EOIO).
    If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
    Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
    Best regards,
    Silvia

  • Reg Group by function

    I want to get an output using group by function of there is no data in the table to display a particular value
    for eg:
    SELECT TRUNC(updated_date) DATE1 , COUNT(1) COUNT FROM table
    where TRUNC(updated_date) >=TRUNC(SYSDATE-18) AND TRUNC(updated_date) <=TRUNC(SYSDATE)
    GROUP BY TRUNC(updated_date)
    ORDER BY TRUNC(updated_date) DESC;
    DATE1     COUNT
    6/16/2012     14208
    6/15/2012     307825
    6/14/2012     172988
    6/6/2012     138790
    6/5/2012     167562
    6/4/2012     51870
    6/2/2012     130582
    6/1/2012     239806
    But i need the missed out date i.e 6/3/2012 - 0, 6/7/2012 - 0 to be displayed since there is no data on the repective dates.

    You should probably ask this question in the SQL and PL/SQL forum:
    PL/SQL
    You'll find answers quicker.

  • Reg:Grouping Key

    Hi
    How to pay single check to multiple vendors

    Dear,
    Group key in the vendor master is used to group all the Vendors with same kind of business, and it is not possible to give one check to multiple vendors unless otherwise they have a mutual understanding out side of sap. That mean they will encash one check given to one vendor and distribute among themselves accordingly.

  • Reg SAP ECC IDOC documentation

    Hi Friends
    Where we can get SAP ECC IDOC documentation help for especially  Functional Consultant.
    Thanks In Advance
    Regards
    SR

    Hi Ravi,
         Hope this links will fullfill your need.
    http://www.sdn.sap.com/irj/sdn/ale
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
    Thanks
    Vinayak

  • Reg. ALE / IDOC understanding

    Dear Friends
    I hearing about IDOC very often but I cann't understant that for what purpose it is used. Please explain the situation of usage.
    kindly give example in MM module.
    thanks in advance
    Rajakumar.K

    Hi Kumar,
    These are called RFC.In simple way we can call them from non sap also and with in sap also ex bapi,idoc etc.In case of mm you can create material all views and changes also you can do.You can create po,pr etc.IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program.Not on;y in mm module we can use it other module also.
    [Idoc In MM|IDOC with MM ??;
    Regards,
    Madhu.

  • Account Groups in the IDoc is different Message no. B1356

    Hi Experts,
    We are setting up CfC using the HCI interface, when we make a change on a customer (Which has been sent from ERP), in CfC, we get an inbound IDoc error in ERP "Account group in IDoc is different":
    Error Message:
    Diagnosis changes cannot be made automatically to the account group of a customer master record. The customer with number 00000XXXXX currently has account group 0020, but the account group 0001 is contained in the intermediate document. Procedure: Please change the account group manually to 0001 and then try to process the intermediate document again.
    The error makes sense since account 00000XXXXX was created in ERP with account group 0020. This was then sent to CfC where we have mapped a lot of account groups e.g. (CRM000 = 0001, CRM000 = 0010, CRM000 = 0020 etc.) When we map more account groups to the same internal account role in CfC (Via. Code list mapping), it is required to have one default outboud meaning that every change to an account will be sent with the role 0001 (If that is the default outbound, in this case it is).
    We are working with multiple account groups comming from ERP, all these account groups are Sold Tos, therefore we need to be able to send data from CfC to ERP, without the IDoc getting stuck in the validation.
    I was told in a CfC training session from SAP, that Sold tos should always be mapped to CRM000, therefore I haven't created different roles for different account groups.
    Do you have any recommendations on this issue? Is it recommended to create new Roles in CfC for every account group (remember that these are all sold tos, so they should work exactly as the standard role CRM000), or do we need to work with somekind of BAdi in inboud for ERP? Any thoughts are ideas?
    Best Regards
    Anders

    for information, I found this note 1914662, I think this will solve the issue.

  • Issue of grouping IDOC segments in huge loads

    Hi All,
    My Scenario is File to IDoc. No problem in posting IDoc in R3. But when i see the Idoc structure in R3, all the data records are grouped in different segements as seen below:-
    This is how i see in we05.
    IDoc No (00000000001234)
    - Control Rec.
    - Segments 000001 to 001000
    - S01 Segment 000001 (Actual records)
    - S02 Segment 000002
    - S03 Segment 000003
    - Segments 001001 to 001001
    - S04 Segment 000004
    - S05 Segment 000005
    - S06 Segment 000006
    - Status Rec.
    I dont want the grouping of Idoc segments to take place. It should be under same data segment.
    Please provide me your valuable solutions to resolve the same.
    Note: This problem occurs only when processing huge records.
    Thanks in advance,

    Hi Sriram,
    It is the standard program flow of  transaction WE02 which checks the number of segments.if the count is more than 1000,it creates a another group and displays it for the sake of readability.
    Anyway it does not affect the inbound processing of the IDOC.
    Thank you.
    Regards,
    Karun.M

  • IDOC not coming in status 30 for collecting idocs

    Hi All,
    We have a requirement in which we need to collect idocs and send together.
    To achieve I am making Collect idocs in Partner profiles so that it goes in status 30 and hence I can run program RSEOUT00 to make it status 03 and hence write in file as a group of idocs.
    Now inspite of making collect idocs in partner profile, its not coming in status 30 but directly coming in status 03.
    Please let me know what may be the reason for the same.
    Thanks,
    Vivek

    Hi vivek,
    If you have set the Collect Idoc option in partner profile then the IDOC's will be collected , irrespective of kind of port you are using and the packet size doesn't matter in this case.
    It seems to me that the program RSEOUT00 is already scheduled in your system.
    Can you check in SM37 , by putting the program RSEOUT00 and check if any user has scheduled the program.
    Hope this helps.
    Harry

Maybe you are looking for