Query on Idoc Packaging with PI7.1 EHP1

HI PI Experts,
I have a scenario where batch run triggers the 100's of Idocs in R3 in few milli seconds, which means all Idocs are triggered in one go From R3.
Do we still need to set Check box for Collect Idocs in Partner Profile in R3 for Idoc Packaging ?
I want to make out the difference in 2 configs for Idoc Packaging where
A)  All Idocs are sent via Report run of RSEOUT00 at a go after collection.
B) All Idocs are triggered at same time via Batch Run at same time.
Assumption:
PI is configured to use Sender Idoc Adapter with Idoc Package Size of 10.
OR
I frame my Query in other way"
What does Collect Idoc and running Report RSEOUT00 achieve to make sure that Multiple IDOC Nodes come into 1 XML message? OR Its only PI Sender Idoc Adpater take care of it when multiple Idocs of same type comes through PI?
Please reply .
Regards,
Anurag

Hi Anurag,
In the sender IDOC adapter if the packaging option is not activated, then the IDoc packages get split into single PI messages, one PI message per IDoc. IDoc sender functionality is enhanced to preserve and process IDoc packages without splitting the IDoc package into individual PI messages. I.e. single PI message contains multiple IDocs including control records. Where as running the report RSEOUT00 will just send all the IDOCs that are in waiting state to their respective destinations.
For the sender IDoc adapter to be able to process packages, it should receive the IDocs in a group. I.e. in the sender partner profile the packaging option has to be activated. Though you've activated the packaging option in the sender partner profile, If you dont check collect option in sendet IDOC adapter then the IDOCs get splitted into individual PI messages.
Regards,
Priyanka

Similar Messages

  • Idoc configurations in PI7.3

    Hi Experts,
    For an Idoc scenario prior to PI 7.3, RFC destination, port, logical system and partner profile needs to be created in case of outbound Idoc scenario and again at XI side we need to create RFC destination, port and loading of meta data....
    Is the same is applicable for PI 7.3 as well? since Idoc resides in AAE in PI 7.3, I believe there could be some changes applicable for these settings of Idoc....
    Pls provide your inputs.....

    Hi,
    Along with the links provided by Phani and Gayatri you can laso refer this thread for IDoc configuration in PI7.3
    IDOC settings from sap r/3 to sap pi7.3
    IDoc Packaging in PI7.3
    http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/4096a6b3-3dc3-2d10-bf87-f63d5340a916
    Configuring PI 7.30 Java IDoc Adapter
    PI/XI: PI 7.3 New Java based IDOC adapter's configuration (sender, receiver) - teaser
    IDoc Acknowledments in PI7.3
    acknowledge handling for IDOC_AAE in sap PI 7.3
    IDoc_AAE acknowledgement handling in PI 7.3
    IDoc related error in PI7.3
    Processing error in Idoc_AAE sender channel
    Hope its informative.
    Regards,
    Amol

  • IDOC Packaging Problem

    Hello all,
    I have below scenario,
    collect multiple IDOCs and process them in single file. I did all the configuration for message Packaging. The messages are getting executed after the specified interval but not in single message they processed seperatly and and creating file per IDOC.
    Is there any one came across this scenario. please help me out in this. What is going wrong in this?

    Hi,
    >>>Actully, i am using below configuration, does anyone know if this configuration will work for IDOC packaging.
    no, the blog you mention has nothing to do with IDOC packaging into one file
    only this one works:
    /people/shabarish.vijayakumar/blog/2010/01/22/idoc-packaging--sap-pi-71-ehp1-and-above
    but as I already mentioned it I guess you're not reading my answers
    Regards,
    Michal Krawczyk

  • IDoc packaging

    Hi,
    If there are 5 IDocs in an IDoc and any one of them is failed,then will the entire IDoc package will fail or something else?
    Can you please tell me about such aspects of IDoc packaging?
    Thanks,
    Gayatri

    Hi,
    If there are 5 IDocs in an IDoc and any one of them is failed,then will the entire IDoc package will fail or something else?
    one idoc is failed in packet, the toatal packet will be failed.
    please gothrough below blogs,
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00cb6c77-74f0-2c10-82a5-9ec2a7a5a391
    http://sapxitutorials.blogspot.com/2011/04/idoc-packaging-sap-pi-71-ehp1-and-above.html
    regards,
    ganesh.

  • Idoc Packaging from sender side Idocs

    Hey,
    Can anybody suggest me the best approach/practice to do the idoc packaging with PI 7.0 SP 15.
    -Esha

    Hi,
    Refer
    SAP Network Blog: XI/PI: sender IDOC adapter packaging ?
    The specified item was not found.
    Message Packaging with Process Integration Component of SAP NetWeaver 7.0 - Webinar Powerpoint
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40a10c62-d000-2a10-c1a6-dbb3ce727300
    Thanks
    Swarup

  • IDoc packing with PI 7.1 EHP1

    Hello,
    how does IDoc packing (EHP1) work within a IDoc sender channel? Has anybody already tried it? Can I simply recieve "collected" IDoc from ECC (e.g. invoic IDocs) which are not splitted by IDoc adapter? So that I do not have to use a collect BPM any more?
    Thanks!
    Christoph

    > that means I have to "create" an IDoc sender channel to receive IDocs from ECC? How can I define whether IDocs should be received via this IDoc sender channel or via the "standard" IDoc adapter?
    >
    Yes, you do have to create an IDOC sender channel.  The IDOC packaging option in the CC distinguishs a standard idoc channel from idoc channel with packaging.
    > How to define the IDoc package size when I don't know how many IDocs will be sent from ECC to PI?
    I would recommend you to watch the below video from the timeslot 00:45, you will  http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/40a412a0-9501-2c10-cb83-f124e23d5373&overridelayout=true
    Pooja

  • PI7.1 EHP1 Java suppor packages LM-CORE Deployment ERROR

    Hi,
    I have installed PI7.1 EHP1 on Linux X86_64 /oracle 11.
    Successfully Updated the ABAP Stack support packages to 7.11 SPS07 thru
    SPAM, but During Java stack thru JSPM i have encountered follwoing
    error for LS-CORE
    7.11.7.3.
    Error: 1. Item is skipped because of failed deployment of the item
    sap.com_tclmwebadminflexstateview and because the applied error
    strategy is oneErrorstop 1. Contains Aborted Deployment Component
    sap.com_tclmwebadminflexstateview .
    LOG::
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[/usr/sap/JXD/DVEBMGS00/j2ee/JSPM/log/log_2011_09_22_20_20_06/deploy_2011-09-22_20-56-07.log]/>
    <!PATTERN[deploy_2011-09-22_20-56-07.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Sep 22, 2011 8:56:07 PM  [Info  ]:DC API is trying to connect to 'SJXD0001:50004'
    Sep 22, 2011 8:56:07 PM  [Info  ]:DC API has Connected to 'SJXD0001:50004'
    Sep 22, 2011 8:56:07 PM  [Info  ]:+++++ Starting  D E P L O Y action +++++ [ deployerId=5 ] [ timerId=177]
    Sep 22, 2011 8:56:07 PM  [Info  ]:Selected archives for deployment. [ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA
    Sep 22, 2011 8:56:07 PM  [Info  ]:DC API got Session id='161',time:[id:#177, elapsed: 23 ms.].[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:component version handling rule is UpdateLowerOrChangedVersionsOnly.[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:deployment workflow strategy is safety deploy strategy.[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:Error strategies[ deployerId=5 ]:
    Sep 22, 2011 8:56:07 PM  [Info  ]:error action 'DeploymentAction' is 'OnErrorStop'
    Sep 22, 2011 8:56:07 PM  [Info  ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
    Sep 22, 2011 8:56:09 PM  [Info  ]:clusterRestartTriggered for transactionId:161, clusterEventAction:cluster restart triggered
    Sep 22, 2011 8:56:09 PM  [Info  ]:Caught exception [P4ConnectionException]. Because cluster restart has been triggered beforehand, assuming a cluster restart.
    Sep 22, 2011 8:56:09 PM  [Info  ]:+++ Server is being restarted +++. The currently set engine start timeout is: 7200 seconds.
    Sep 22, 2011 8:56:09 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
    Sep 22, 2011 8:56:25 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
    Sep 22, 2011 8:56:41 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
    Sep 22, 2011 8:56:57 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 48 seconds. Remainig to timeout 7151 seconds.
    Sep 22, 2011 8:57:13 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 64 seconds. Remainig to timeout 7135 seconds.
    Sep 22, 2011 8:57:26 PM  [Info  ]:Wait for the operation 'Deploying' to finish
    Sep 22, 2011 8:57:28 PM  [Info  ]:Assuming a subsequent restart of the server due to exception: [P4ConnectionException], message: Error. Check your available working servers. Error message: the requested server is not available
    Sep 22, 2011 8:57:28 PM  [Error ]:[ Exception ]::Unexpected exception during the notification of cluster listeners
    Sep 22, 2011 8:57:28 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
    Sep 22, 2011 8:57:45 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
    Sep 22, 2011 8:58:01 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
    Sep 22, 2011 8:58:18 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 49 seconds. Remainig to timeout 7150 seconds.
    Sep 22, 2011 8:58:36 PM  [Info  ]:Obtaining the deployment result from the server ...
    Sep 22, 2011 8:58:37 PM  [Info  ]:Deployment result
    Sorted Items -
         1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcsld~data.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcslddata', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('FS', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
         2. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
              Deploy status is 'Skipped'
              SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
         3. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
              Deploy status is 'Skipped'
              SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
         4. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
              Deploy status is 'Skipped'
              SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
         5. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
              Deploy status is 'Skipped'
              SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
         6. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
         7. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjebasicadminsapcontrolapp.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcjebasicadminsapcontrolapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-ADM', dependencies :[( name 'tcjmx', vendor 'sap.com') , ( name 'adminadapter', vendor 'sap.com') , ( name 'tcjebasicadminsapcontrol~lib', vendor 'sap.com') ]
         8. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~com.sap.engine.customizing.ccms.sda'
              Deploy status is 'Skipped'
              SDA : name 'com.sap.engine.customizing.ccms', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826155427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'monitor', vendor 'sap.com') , ( name 'tcjmx', vendor 'sap.com') , ( name 'rfcengine', vendor 'sap.com') , ( name 'tcmonitoring~api', vendor 'sap.com') , ( name 'monitortree', vendor 'sap.com') ]
         9. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexflexcommons.sda'
              Deploy status is 'Skipped'
              SDA : name 'tclmwebadminflexflex_commons', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
         10. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
              Deploy status is 'Aborted'
              SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
         11. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
         12. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
         13. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.dbcontent.sda'
              Deploy status is 'Skipped'
              SDA : name 'com.sap.sl.ut.jddi.content', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('DBSC', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.sl.ut.jddi.schema', vendor 'sap.com') ]
         14. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
              Deploy status is 'Aborted'
              SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
    Deployment Items -
         1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
              Deploy status is 'Aborted'
              Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop
              1. Contains Aborted deployment component:
    sap.com_tclmwebadminflexstateview'.
              SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
              Composite Time statistics( ms ):
                   1.Check composite version : 24
                        1.1.Check version:sap.com_LM-CORE : 1
                        1.2.Check contained SDAs versions : 23
                   2.validate : 31
                        2.1.Check composite version : 31
                             2.1.1.Check contained SDAs versions : 31
                   3.Persist in storage : 11
              Contained DCs:
                   1.1 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_ear.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcsldcds~wsproxy_ear', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.2 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.namealloc.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110711084722.0000
              2. Already deployed component has version:7.1107.20110711084722.0000'.
                        SDA : name 'com.sap.lcr.namealloc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.3 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctc~interface_lib.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823083938.0000
              2. Already deployed component has version:7.1107.20110823083938.0000'.
                        SDA : name 'tclmctc~interface_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.4 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcslddpj2ee.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcslddp~j2ee', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.5 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.util.monitor.grmg.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110309073123.0000
              2. Already deployed component has version:7.1107.20110309073123.0000'.
                        SDA : name 'com.sap.util.monitor.grmg', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.6 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> apptracing.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826165427.0000
              2. Already deployed component has version:7.1107.20110826165427.0000'.
                        SDA : name 'apptracing', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23

    versions : 31
                             3.Persist in storage : 11
                   1.22 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~cdsclient_lib.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcsldcds~cdsclient_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.23 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.24 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_lib.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcsldcds~wsproxy_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.25 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> monitortree.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826155427.0000
              2. Already deployed component has version:7.1107.20110826155427.0000'.
                        SDA : name 'monitortree', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.26 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'com.sap.lcr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.27 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.28 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcmonitoring~sda.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826155427.0000
              2. Already deployed component has version:7.1107.20110826155427.0000'.
                        SDA : name 'tcmonitoringsda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.29 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.30 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
                        Deploy status is 'Aborted'
                        Description:'1. CFS Container reported an error. Check the causing exceptions for the reason for failure.
               -> [ERROR CODE DPL.CFS.0301] Error while notifying bootstrap about component "sap.com/tclmwebadminflexstateview". Collected error messages are: Collected bootstrap error messages ( appName:sap.com/tclmwebadminflexstateview) :
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/AC_OETags.js (No such file or directory)
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.html (No such file or directory)
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.swf (No such file or directory)
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/playerProductInstall.swf (No such file or directory)
                        SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.31 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.32 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.33 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.engine.heartbeat.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826155427.0000
              2. Already deployed component has version:7.1107.20110826155427.0000'.
                        SDA : name 'com.sap.engine.heartbeat', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.34 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> dsr.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826165427.0000
              2. Already deployed component has version:7.1107.20110826165427.0000'.
                        SDA : name 'dsr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.35 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtclmctccul~service_sda.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110815124828.0000
              2. Already deployed component has version:7.1107.20110815124828.0000'.
                        SDA : name 'tclmctcculservice_sda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.36 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.37 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
    Sep 22, 2011 8:58:37 PM  [Info  ]:+++ Deployment finished with status 'Error' +++.[ deployerId=5 ][#178: 149.398 sec]
    Sep 22, 2011 8:58:37 PM  [Info  ]:+++++ End  D E P L O Y action +++++[ deployerId=5 ]. Total time:[#177: 149.501 sec]

  • PI 7.1 EHP1 : IDoc packaging

    Guys
    I am currently on PI 7.1 EHP1 , Trying to do Idoc packaging for one scenario , I am not sure what size I have to put in the tab
    ( IDoc package size ) in sender IDoc channel . I  also donot know the frequency of IDocs . I saw one video in it it was told that the package size shouldnot exceed 2MB size .
    Please help in this regard
    Regards
    Ninad

    Hi Ninad,
    I had used IDOC packaging in one of my scenario, which is very similar to yours. I dont know how many idoc are coming from source system. I put 100 in the IDOC package size parameter. when you put 100 in this parameter it will create a file wil maximum 100 idocs if your system is sending more than 100 than it will create send file
    For example from source system you are getting 150 idocs so 2 files will be created
    file1 conatins 100 idocs, file2 contains 50 idocs
    Regards,
    Shradha

  • Query realted to IDOC packaging in case of  IDOC-SAPPI- FILE scenario

    Hi,
    I have requirement related to IDOC packaging, i.e. SAP ECC -SAP PI - FTP server.
    I have done the following settings:
    1) In WE20, I put the partner profile settings to collect mode.
    2) I am using RSEOUT00 to trigger the collected IDOCs for example 2 idocs together.
    3) In SAP PI, I have done the following settings
    a) I added the the parameter in sxmb-adm, RUNTIME , PACKAGING & Value 1
    b) I have used IDXPW t-code to activate the message packages for IDOC
    c) I run the job through sxmb_adm t-code, configure event driven message filtering
    d) I exported the xsd of ORDERS05 and changed occurence of source structure to 0 to Unbounded and imported it in Integration Repository.
    e) I am not using mapping & interface mapping as I just want to post the IDOC structure as it to the receiving FTP server. Therefore when I changed the occurence of ORDERS05 xsd to 0 to unbounded my idea was that in the outbound message interface it will be reflected which will be ultimately reflected in Integration directory.
    Problem Details:
    When I test for the 2 PO idoc from SAP ECC, it generates 2 messages in SAP PI and also 2 files in FTP server but actually it should generate one output file containing both the IDOC details.
    Note: I am just trying to merge 2 idocs of PO as IDOC package into one output message.
    Can anybody what configuration settings I am missing for the packaging.
    Thanks & Regards
    Prabhat

    Hi Prabhat,
    If you are using PI 7.0 EHp1 or PI 7.1 Ehp1, you can configure packaging parameter and create single file for multiple idocs without using BPM.
    In other case, you have to use BPM.
    But recommended approach would be to create XML file port on SAP ECC and create IDOC XML file.
    You must have set collect IDOCs option in partner profile.
    Now you can execute RSEOUT00 report program and specify IDOC type and number IDOCs to be collected.
    This configuration will generate IDOC XML file for number IDOCs you specified in RSEOUT00 report program.
    In PI you can use File adapter to pick the file.
    Here is the nice blog explaining entire process:
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    Best Regards,
    Divyesh

  • What is the difference between SAP NW PI7.1 and PI7.1 EHP1

    We have a customer using SAP PI7.1 EHP1. The application to be deployed
    isdeveloped on SAP Netweaver PI 7.1 SP06.
    We need to know if application developed and transported from PI7.1 is
    compatible with EHP1?
    Below are the Components used by the application .
    1) SSL communication using SOAP adapter
    2) Java mapping , Graphical mapping , XSLT mapping
    3) Customised EJB modules
    4) Adapter framework
    5) ALE layer for IDoc communication from ERP to PI
    6) RFC lookups to PI system and ERP system.
    Questions
    1)Will PI EHP1 be able to communicate with PI7.1 using SOAP adapter ?
    2) What is the difference between SAP NW PI7.1 and PI7.1 EHP1 ?
    Regards,
    Sneha

    Hi,
    EHP Pi7.1 new
    IPv6 Support in SAP Systems (new)
    Async/Sync and Sync/Async Bridge in the JMS Adapter (New)
    High Availability (New)   Locate the document in its SAP Library structure
    Use
    A new concept is available for setting up a high availability environment for SAP NetWeaver Process Integration (PI). To do this, you need SAP Web Dispatcher for load balancing, and you must reconfigure your HTTP, RFC, and RMI connections so that they can be used for load balancing. You must also make various configuration steps in other components of your PI environment.
    [Level 4: Document: XML to Text Conversion Module (New)] XML to Text Conversion Module (New)
    Message Packaging (New)
    Monitoring Milestones (New)   Locate the document in its SAP Library structure
    Use
    You can use the new scenario variant Monitoring Milestones of the Business Process Management scenario to define a monitoring process that can monitor events from different applications. A monitoring process can subscribe to events from SAP or non-SAP systems.
    check  given Link
    http://help.sap.com/saphelp_nwpi711/helpdata/en/61/8c3842bb58f83ae10000000a1550b0/frameset.htm
    Regards,
    Amit

  • Idoc packaging questions

    Hi
    I am aware that in Idoc packaging how Sender Idoc adapter packaging is done and also know that it is available from PI7.11
    I have 2 questions...
    1. Suppose there is a data issue with a single idoc ,,because of that entire package will fail...then it would call for finding the erroneous idoc ...correct the data and resend all the Idocs again..
      This problem can occur again and again...and because of this the entire package will be stopped..
    So is it a good option to not do packaging and send a single Idoc and insert it as a record in target database.
    2. In case i am doing idoc packaging the occurence of IDOC in mapping will still be 1..1.
        How do i manage my mapping such that each Idoc in the package should insert a separate record in the database table
    Hema

    >
    > 2. In case i am doing idoc packaging the occurence of IDOC in mapping will still be 1..1.
    >
    >     How do i manage my mapping such that each Idoc in the package should insert a separate record in the database table
    >
    Map IDoc to access tag, in this case one record for each IDoc will get inserted.

  • IDoc Packaging + Ack ALEAUD = bad behavior ?

    Hi,
    I'm in version PI 7.11 and I'm studying the IDoc packaging of EhP1 with Acknowledgment (ALEAUD).
    My scenario is a basic one: File -> PI --> ECC (100 idocs). And then ECC returns Ack.
    So for the returned Acknowledgment, I have that:
    - on ECC, I did ALE config, and I run programs RBDSTATE / RSEOUT00 to create one IDoc ALEAUD (Ack).
    - In PI, I use a sender CC (Idoc adapter) by using option "Idoc Packaging".
    - In PI, I use a Sender Agreement with Idoc ECC's ALEAUD and this sender CC.
    - In PI, I use program IDX_ALEREQUEST on ECC's ALEAUD idoc.
    My problem is:
    ECC send me ONE idoc ALEAUD which contains 100 segments corresponding to 100 Idocs received at the first step. BUT even if I used the "Idoc Packaging"... in IDX5 of PI, I have not one idoc ALEAUD, but I have 100 Idocs ALEAUD !
    And so after that my mapping is run 100 times instead of one ! Image if I need to return an email... with this PI behaviour, I will send 100 "Ack" emails.
    So does somebody know why IDoc Packaging does not work with ALEAUD whereas program IDX_ALEREQUEST is correctly used ?
    Thanks
    Mickael
    Note: I don't want to have to create a BPM to collect my ALEAUD Idocs. That's too heavy...
    And (for the moment), I don't want to create a specific ZALEAUD idoc...

    Hi Prashant,
    yes, I did not precise it, but of course IDXNOALE is used, else PI will generate an Ack of this ECC's ALEAUD... so a ack of a ack... but it's not really my problem.
    what I say is:
    - Request : PI -> 100 idocs MATMAS (for instance)
    - Ack : ECC return to PI only one idoc ALEAUD with 100 segments "E1STATE" corresponding to the 100 idocs MATMAS.
    - Ack : PI receive this only one ALEAUD... but in IDX5 and in SXI_MONITOR, we see in fact 100 IDocs ALEAUD with 1 segment E1STATE, instead of having only one idoc ALEAUD (like in ECC side) !
    So I'm searching a way to keep in PI the only one Idoc ALEAUD sent by ECC, in order to be able (for instance) to send only one email (and not 100 emails like it's the case for the moment).
    Regards
    Mickael

  • IDOC Packaging Sender CC

    Hi Gurus,
    I've been using IDOC packaging in the IDOC sender communication channel very well without any problems so far.
    Most of my scenarios I have to group several IDOCS and generate just one file, and using the new functionality I can reach my scenario easily and with good performance.
    However I am trying to configure this same thing for a new IDOC, but it's not working.
    So, I've checked the option in IDOC sender communication channel as usual, set up the size for 9999, I go to we20 and change the partner profile to collect IDOCs and also set it up to 9999 as package size.  Following this blog. IDoc Packaging - SAP PI 7.1 EHP1 (and above)
    However for this new configuration, when I trigger 2 or 3 IDOCS at the same time it creates 2 or 3 messages in PI as well, and it should create just ONE message in PI. What make me confuse is If I trigger 2 or 3 IDOCS for the other type of IDOC, regarding the old configuration it works...just one message is created in PI
    So I am really confused why for this IDOC is not working and for the OLD configuration is working. Am I missing something ?
    Thanks
    BEst REgards
    Diego

    Hi All,
    Yes, I had done everything
    In fact I wanted to see the IDOC being collapsed with several IDOC nodes in the monitoring.
    So the problem was solved quite easily I was triggering the IDOC through the program and the OutPut node was in blank and by default is set to 2 (transfer immediately) it skips the configuration that you have done in we20 and do it by itself.
    So I put the propoer Output mode (4) and it worked well
    Thank you for the answers
    Regards
    Diego

  • Read MULTIPLE idocs data with all sgmn to my internal table in a single

    Dear SAP Folks!
    I have a question, I know to read SINGLE idoc data with all segments, we have FM IDOC_READ_COMPLETELY but my requirement is to Read MULTIPLE idocs data with all segments to my internal table in a single shot without keeping this FM in loop! since it is performance issue, at a time i may want to read 1000 idocs data!
    Could anyone please let me know is there any way to get this, keeping mind of performance and any other FM?
    Best Regards,
    Srini

    Hi,
    I know idoc numbers and i can write a select Query to DB table EDID4 to get all segments data to my internal table. But i am looking for FM to do this. because i have too many number of idocs and each idoc is having many segments(I am thinking in performance point of view!) The FM IDOC_READ_COMPLETELY can accept only ONE IDOC number as import parameters at a time to get segment data. in similar way do we have any other FM? or other way? except select query to EDID4 table?
    Best Regards,
    Srini

  • URGENT- IDoc Packaging - Que- Michal blog

    Hi,
    I was following Micahl's blog - for idoc packaging -
    /people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
    But there is another blog, which also by Michal.
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change ,
    which is also mentioned in OSS note: Note 814393 - Multiple IDoc instances in an XI message.
    Do I need to do both of them to achieve the Idoc Packaging.
    I also noticed that in the first blog, it is about pushing Idocs out of R/3 system and in the second blog it is the other way round.
    Can any one please clarify.
    reg

    with the first blog, how does sxmb_moni screen looks like - R3 system, XI. On XI it should not make any diff as XI is still splitting the packages.
    Yes you are right...On R3 system, if packaging is done, then you will find all IDOCs as single message. As you said on XI it will not make any difference.
    With the 2nd blog, XI would show single message for each package, but with more instances of the Idoc payload. (As shown in the first blog - look at the 2nd pic). Which means that you saving the queues but the payload size is more here in this case.
    Yes..It show single message with more instance of IDOCs. You are right about saving the queues and payload size is also more

Maybe you are looking for

  • Unable to create Business Layer on top of SAP BW OLAP Connection - BI 4.0

    Friends, Need an useful information, why can't we create a business layer on top of SAP BW OLAP connection which is built with BICS driver. Today when i tried to create a business layer in IDT tool of BI 4.0 it didnt allow me to do so. Is it a s/w bu

  • Logitech MX900 Mouse & Solaris 10 x86 results in "Postattach failed for..."

    This USB-Mouse will not work with Solaris 10. I have the bluetooth-set Logitech DiNovo keyboard and MX900 mouse. As seen in the following logfile, the keyboard is recognized and the device is created, but the mouse fails. So i have to use my old dust

  • Valid Characters for PDF 1.6 User Password

    Hi, What character set is considered as a valid for user password in Pdf 1.6? I know Pdf 1,6 accepts only single byte characters in user password? Is there any set of valid password characters? I searched Pdf 1,6 spec and adobe forums, but couldn't f

  • Passing errors back to Source system in proxy in Sync communtion

    Hello Experts, I am developing a Sync Proxy-JDBC scenario. It works perfectly fine. In case if there is any error while delivering the data to JDBC receiver, we see error in SXMB_MONI in PI but can we pass same error to Source? i tried to use fault d

  • Checking the size of the object

    Hi all , i need to check the size of the Oracle internal table for the text index created . dr $r --table option 1: SELECT S.bytes Bytes, SYSDATE FROM DBA_SEGMENTS S, DBA_LOBS L WHERE l.TABLE_NAME='DR$TEXT_SEARCH$R' AND l.SEGMENT_NAME=S.SEGMENT_NAME;