Dear Laurent,

Thanx for your response.

As per my understanding Bidder will be used upto RFx response. Before award he will be converted to Supplier. i.e. Supplier can work as Bidder and supplier.

So Bidder and Supplier can have surrogate bidding. When I checked in system both Bidder and Supplier has "permit surrogate bidding" check box.

I checked the FM suggested by you, BBP_BIDDER_GETDETAIL_NEW, found following tables:

ET_STATUS_SET

ET_BIDCC

Can you guide me in which I need to select.

Can you help me where can I find table details of Bidder / supplier in which I can get "Permit surrogate bidding" field.

Regards,

Sai Krishna

Hi Gurus,

Please let me know if there is possibility to maintain authorization control at Position ID level in Investment Management.

Regards

Naveen

Hi Vekat,

If you have not implemented SAp note before I would suggest take help from Bais team,

Directly do not do because it will have negative impact too.

Tcode coe Note implementation - Snote.

Regards,

ganesh Bothe

Abhideet,

Can you confirm that you are using SAP GUI(windows) 7.20 Patch level 4 or higher or SAP GUI (Java) 7.20 Revision 9.1 or higher?

If yes, please refer to SAP note 619208.

I hope this helps you.

Regards,

Ashvin

Hi Luis,

What is the OData service URI for item count and the response? Is it blank or 0 or OData service call error?

Regards, Masa

SAP Customer Experience Group - CEG

Hi Srivastavs,

Now, I don't find any error on the dev_rout tab, but, what is the command to see the running status.

I logged in and check saposs RFC connection failed.

Thanks & Regards

Ahsan

HI Tej,

I would like to understand why do we need setoff conditions for non cenvatable conditions. I mean, if we need to inventories full excise, why can't we just use JMIP and use NVV against that condition type. Why do we need JMX2 in this case. Please help me in understanding the use of set off conditions for non-cenvatable excise condition.

Hi,

please send your views for my above request.

Thanks & Regards,

Jai Prabhu.

Hi Rana,

Now I don't see any error in dev_rout file, but how to know the saprouter running status.

Below is saposs connection error.

Thanks &  Regareds

Ahsan

Hi Hari,

i already read these documents before ask.

I'M cleared most of the points but embedded query data into excel sheet I'm not sure.

THanks

dear BI consultants  ,.

can any one answer this

The record of view2 is already uploaded to target with one barcode number if we use the date as upload criteria.

If the record from the view one is uploaded today with the same barcode number what happens .

Overwrite the record or modify the existing record ?

view 1  >        data source             |    data source    |

                                                                                              DSO

view 2  >             data source        |     data source   |

The problem is operation t , operation , zusr1 , zusr  , is empty they must be field  with the values in the view 2 .

The data is loaded based on the date criteria while loading in the info package where the data loss is happening and the data in the target is miss matching.

The process chain is working daily but the data is not loaded correctly from view 2 into info package and the psa will be not having the records.

The data field in the view one does not match with date field in the view 2 .

The key figure here is the barcode number only (so only one record exist for on barcode)

HI Zoltan,

Yes  you got my requirement,  I have already added  several customer field in the same page  as per guidance by  SAP Note  762984 , mentioned by Anil.

  Now I want to add a custom button called "Fetch ECC DIR"  and when user click on that ,need to call ECC RFC Module.

  Thanks for your inputs, as am very new to BSP ,can you kindly provide some more details how can I achieve this,it would be of great help.

thanks

Channa

Hi

What is your splitting rule? Is it activity? if yes seems all the activity quantities are equal, kindly confirm.

Rajneesh

Hi,

Please check your host and services files once.

500235 - Network Diagnosis with NIPING

2000132 - Configuring RFC connections to the SAPNet R/3 front end (OSS) correctly

Follow above notes to fix your connection problems.

Regards

Hi,

Hope it helpful.

Try.

Create the Search help and include in  screen painter.

Regards,

Venkat.

Dear Experts,

We are facing an issue where we are getting some errors in dev_server0 file. We now need to find as to why these errors are coming and from where to go and correct it.

Just a little background, We have migrated our solution manager from old host to new host, after this we are getting these errors, in the end of the trace pasted here you can see that it is trying to ping the old host, from where it is picking up the new host ??

I have checked in config tool and visual admin but dont see the old host values there. Can you please explain me how the java engine writes to this log file dev_server ? and where to check for old solution manager entries ?

---------------------------------------------------

trc file: "dev_server0", trc level: 1, release: "720"

---------------------------------------------------

node name   : ID799495250

pid         : 9083

system name : XXX

system nr.  : 79

started at  : Sat Sep 13 19:06:30 2014

arguments         :

          arg[00] : /usr/sap/XXX/JC90/exe/jlaunch

          arg[01] : pf=/usr/sap/XXX/SYS/profile/XXX_JC90_Hostname

          arg[02] : -DSAPINFO=XXX_79_server

          arg[03] : pf=/usr/sap/XXX/SYS/profile/XXX_JC90_Hostname

**********************************************************************

Used property files

-> files [00] : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

**********************************************************************

**********************************************************************

Bootstrap nodes

-> [00] bootstrap            : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [01] bootstrap_ID79949520 : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [02] bootstrap_ID79949525 : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [03] bootstrap_ID79949525 : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [04] bootstrap_ID79949525 : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

**********************************************************************

**********************************************************************

Worker nodes

-> [00] ID799495200          : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [01] ID799495250          : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [02] ID799495251          : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

-> [03] ID799495252          : /usr/sap/XXX/JC90/j2ee/cluster/instance.properties

**********************************************************************

**********************************************************************

JStartupReadInstanceProperties: read instance properties [/usr/sap/XXX/JC90/j2ee/cluster/instance.properties]

-> ms host    : Hostname

-> ms port    : 3978

-> OS libs    : /usr/sap/XXX/JC90/j2ee/os_libs

-> Admin URL  :

-> run mode   : normal

-> run action : NONE

-> enabled    : yes

**********************************************************************

[Thr 140422160041824] Sat Sep 13 19:06:30 2014

[Thr 140422160041824] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048m [jstartxx_mt. 2800]

[Thr 140422160041824] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/XXX/JC90/exe/jvmx.jar

**********************************************************************

JStartupIReadSection: read node properties [ID799495250]

-> node name          : server0

-> node type          : server

-> node execute       : yes

-> jlaunch parameters :

-> java path          : /usr/sap/XXX/JC90/exe/sapjvm_4

-> java parameters    : -verbose:gc -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.egd=file:/dev/urandom -Djava.security.policy=./java.policy -Dorg.omg.CORBA.ORB

Class=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap

.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.wily.in

troscope.agent.agentName=XXX_JC90_server0 -Dcom.wily.introscope.agentProfile=/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/Bytecod

eAgent/ISAGENT.8.2.4.0-2012-01-27/wily/core/config/IntroscopeAgent.profile -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkS

weepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+UseTLAB -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+HandlePromotionFailure -XX:Sof

tRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Dsun.io.useCanonCaches=false -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:/usr/sap

/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/connectors/AutoProbeConnector.jar:/usr/sap/SMD

/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/Agent.jar

-> java vm version    : 4.1.020 19.1-b02

-> java vm vendor     : SAP Java Server VM (SAP AG)

-> java vm type       : server

-> java vm cpu        : amd64

-> heap size          : 2048M

-> init heap size     : 2048M

-> stack size         : 2M

-> root path          : /usr/sap/XXX/JC90/j2ee/cluster/server0

-> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

-> OS libs path       : /usr/sap/XXX/JC90/j2ee/os_libs

-> main class         : com.sap.engine.boot.Start

-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path     : /usr/sap/XXX/JC90/exe/jstartup.jar:/usr/sap/XXX/JC90/exe/jvmx.jar

-> shutdown class     : com.sap.engine.boot.Start

-> parameters         :

-> debuggable         : no

-> debug mode         : no

-> debug port         : 57921

-> shutdown timeout   : 120 sec.

**********************************************************************

[Thr 140422160041824] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 140422160041824] JLaunchRequestQueueInit: create pipe listener thread

[Thr 140422125201152] JLaunchRequestFunc: Thread 140422125201152 started as listener thread for np messages.

[Thr 140422124148480] WaitSyncSemThread: Thread 140422124148480 started as semaphore monitor thread.

[Thr 140422160041824] SigISetDefaultAction : default handling for signal SIGCHLD

[Thr 140422160041824] Sat Sep 13 19:06:31 2014

[Thr 140422160041824] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

[Thr 140422160041824] MPI: dynamic quotas disabled.

[Thr 140422160041824] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

[Thr 140422160041824] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.

[Thr 140422160041824] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.

[Thr 140422160041824] CCMS: CCMS Monitoring Initialization finished, rc=0.

[Thr 140422160041824] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048m [jstartxx_mt. 2800]

[Thr 140422160041824] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/XXX/JC90/exe/jvmx.jar

**********************************************************************

JStartupIReadSection: read node properties [ID799495250]

-> node name          : server0

-> node type          : server

-> node execute       : yes

-> jlaunch parameters :

-> java path          : /usr/sap/XXX/JC90/exe/sapjvm_4

-> java parameters    : -verbose:gc -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.egd=file:/dev/urandom -Djava.security.policy=./java.policy -Dorg.omg.CORBA.ORB

Class=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap

.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.wily.in

troscope.agent.agentName=XXX_JC90_server0 -Dcom.wily.introscope.agentProfile=/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/Bytecod

eAgent/ISAGENT.8.2.4.0-2012-01-27/wily/core/config/IntroscopeAgent.profile -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkS

weepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+UseTLAB -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+HandlePromotionFailure -XX:Sof

tRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Dsun.io.useCanonCaches=false -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:/usr/sap

/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/connectors/AutoProbeConnector.jar:/usr/sap/SMD

/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/Agent.jar

-> java vm version    : 4.1.020 19.1-b02

-> java vm vendor     : SAP Java Server VM (SAP AG)

-> java vm type       : server

-> java vm cpu        : amd64

-> heap size          : 2048M

-> init heap size     : 2048M

-> stack size         : 2M

-> root path          : /usr/sap/XXX/JC90/j2ee/cluster/server0

-> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

-> OS libs path       : /usr/sap/XXX/JC90/j2ee/os_libs

-> main class         : com.sap.engine.boot.Start

-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path     : /usr/sap/XXX/JC90/exe/jstartup.jar:/usr/sap/XXX/JC90/exe/jvmx.jar

-> shutdown class     : com.sap.engine.boot.Start

-> parameters         :

-> debuggable         : no

-> debug mode         : no

-> debug port         : 57921

-> shutdown timeout   : 120 sec.

**********************************************************************

[Thr 140422160041824] JLaunchISetDebugMode: set debug mode [no]

[Thr 140422097188608] JLaunchIStartFunc: Thread 140422097188608 started as Java VM thread.

**********************************************************************

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack   : 1048576 Bytes

-> arg[  0]: exit

-> arg[  1]: abort

-> arg[  2]: vfprintf

-> arg[  3]: -verbose:gc

-> arg[  4]: -Djco.jarm=1

-> arg[  5]: -Djava.awt.headless=true

-> arg[  6]: -Djava.security.egd=file:/dev/urandom

-> arg[  7]: -Djava.security.policy=./java.policy

-> arg[  8]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[  9]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-> arg[ 11]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 12]: -Dcom.wily.introscope.agent.agentName=XXX_JC90_server0

-> arg[ 13]: -Dcom.wily.introscope.agentProfile=/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-0

1-27/wily/core/config/IntroscopeAgent.profile

-> arg[ 14]: -XX:MaxNewSize=600M

-> arg[ 15]: -XX:NewSize=600M

-> arg[ 16]: -XX:MaxPermSize=512M

-> arg[ 17]: -XX:PermSize=512M

-> arg[ 18]: -XX:+UseConcMarkSweepGC

-> arg[ 19]: -XX:+DisableExplicitGC

-> arg[ 20]: -XX:TargetSurvivorRatio=90

-> arg[ 21]: -XX:SurvivorRatio=4

-> arg[ 22]: -XX:+UseTLAB

-> arg[ 23]: -XX:+PrintGCDetails

-> arg[ 24]: -XX:+PrintGCTimeStamps

-> arg[ 25]: -XX:+HandlePromotionFailure

-> arg[ 26]: -XX:SoftRefLRUPolicyMSPerMB=1

-> arg[ 27]: -XX:HeapDumpPath=OOM.hprof

-> arg[ 28]: -XX:+HeapDumpOnOutOfMemoryError

-> arg[ 29]: -Dsun.io.useCanonCaches=false

-> arg[ 30]: -XX:+JavaMonitorsInStackTrace

-> arg[ 31]: -Xbootclasspath/p:/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/connect

ors/AutoProbeConnector.jar:/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-2012-01-27/wily/Agent.jar

-> arg[ 32]: -Dsys.global.dir=/usr/sap/XXX/SYS/global

-> arg[ 33]: -Dapplication.home=/usr/sap/XXX/JC90/exe

-> arg[ 34]: -Djava.class.path=/usr/sap/XXX/JC90/exe/jstartup.jar:/usr/sap/XXX/JC90/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

-> arg[ 35]: -Djava.library.path=/usr/sap/XXX/JC90/exe/sapjvm_4/jre/lib/amd64/server:/usr/sap/XXX/JC90/exe/sapjvm_4/jre/lib/amd64:/usr/sap/XXX/JC90/exe/sapjvm_4/jre/../

lib/amd64:/usr/sap/XXX/JC90/exe:/usr/sap/XXX/JC90/exe:/usr/sap/XXX/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/

usr/lib:/usr/sap/XXX/JC90/j2ee/os_libs:/usr/sap/XXX/JC90/exe:/usr/sap/XXX/JC90/exe:/usr/sap/XXX/SYS/exe/run:/oracle/client/10x_64/instantclient

-> arg[ 36]: -Dmemory.manager=2048M

-> arg[ 37]: -Xmx2048M

-> arg[ 38]: -Xms2048M

-> arg[ 39]: -Xss2M

-> arg[ 40]: -DLoadBalanceRestricted=no

-> arg[ 41]: -Djstartup.mode=JCONTROL

-> arg[ 42]: -Djstartup.ownProcessId=9083

-> arg[ 43]: -Djstartup.ownHardwareId=W0901032739

-> arg[ 44]: -Djstartup.whoami=server

-> arg[ 45]: -Djstartup.debuggable=no

-> arg[ 46]: -Xjvmx

-> arg[ 47]: -XsapSystem=79

-> arg[ 48]: -XmonGcCallback

-> arg[ 49]: -DSAPINFO=XXX_79_server

-> arg[ 50]: -DSAPSTARTUP=1

-> arg[ 51]: -DSAPSYSTEM=79

-> arg[ 52]: -DSAPSYSTEMNAME=XXX

-> arg[ 53]: -DSAPMYNAME=Hostname_XXX_79

-> arg[ 54]: -DSAPDBHOST=DBHostname

-> arg[ 55]: -Dj2ee.dbhost=DBHostname

**********************************************************************

**********************************************************************

(CompilerOracle read from file /usr/sap/XXX/JC90/exe/sapjvm_4/jre/.hotspot_compiler)

[Thr 140422097188608] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [server0]

**********************************************************************

[Thr 140421237438208] Sat Sep 13 19:06:33 2014

[Thr 140421237438208] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes

[Thr 140421237438208] JHVM_RegisterNatives: 8 of 9 methods in com.sap.bc.krn.perf.PerfTimes registered.

Sat Sep 13 19:06:35 2014

3.923: [GC 3.923: [ParNew: 409600K->2464K(512000K), 0.0187400 secs] 409600K->2464K(1994752K), 0.0189320 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]

[Thr 140421237438208] Sat Sep 13 19:06:36 2014

[Thr 140421237438208] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework

[Thr 140421237438208] JLaunchISetClusterId: set cluster id 799495250

[Thr 140421237438208] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 140421237438208] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

Sat Sep 13 19:06:56 2014

25.123: [GC 25.124: [ParNew: 412064K->19711K(512000K), 0.0637410 secs] 412064K->19711K(1994752K), 0.0639660 secs] [Times: user=0.11 sys=0.01, real=0.06 secs]

Sat Sep 13 19:07:12 2014

40.580: [GC 40.580: [ParNew: 429311K->29173K(512000K), 0.0519500 secs] 429311K->29173K(1994752K), 0.0521270 secs] [Times: user=0.13 sys=0.03, real=0.05 secs]

Sat Sep 13 19:07:33 2014

61.542: [GC 61.542: [ParNew: 438767K->33447K(512000K), 0.2340120 secs] 438767K->33447K(1994752K), 0.2342630 secs] [Times: user=0.20 sys=0.01, real=0.24 secs]

[Thr 140419186808576] Sat Sep 13 19:07:40 2014

[Thr 140419186808576] JHVM_RegisterNatives: com.sap.security.core.server.vsi.service.jni.VirusScanInterface

[Thr 140419817953024] JHVM_RegisterNatives: com.sap.mw.rfc.driver.CpicDriver

[Thr 140419056793344] Sat Sep 13 19:07:44 2014

[Thr 140419056793344] JHVM_RegisterNatives: com.sap.mona.api.JMonAPI

[Thr 140419056793344] CCMS: openMonitoringSegment(): inside static JMON Lib: already connected.

73.318: [GC 73.318: [ParNew

Sat Sep 13 19:07:45 2014

: 443047K->51355K(512000K), 0.3971100 secs] 443047K->51355K(1994752K), 0.3975090 secs] [Times: user=0.32 sys=0.01, real=0.40 secs]

[Thr 140419046287104] Sat Sep 13 19:07:46 2014

[Thr 140419046287104] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140419046287104] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 371

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

[Thr 140418981148416] Sat Sep 13 19:07:52 2014

[Thr 140418981148416] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418981148416] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 391

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

[Thr 140421237438208] Sat Sep 13 19:07:55 2014

[Thr 140421237438208] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]

[Thr 140418976945920] Sat Sep 13 19:07:58 2014

[Thr 140418976945920] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418976945920] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 342

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

Sat Sep 13 19:08:03 2014

92.009: [GC 92.010: [ParNew: 460955K->49499K(512000K), 0.1107400 secs] 460955K->49499K(1994752K), 0.1112760 secs] [Times: user=0.29 sys=0.02, real=0.11 secs]

[Thr 140418979047168] Sat Sep 13 19:08:04 2014

[Thr 140418979047168] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418979047168] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 342

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

[Thr 140418968540928] Sat Sep 13 19:08:10 2014

[Thr 140418968540928] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418968540928] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 342

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

[Thr 140418970642176] Sat Sep 13 19:08:15 2014

[Thr 140418970642176] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418970642176] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 414

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

[Thr 140418972743424] Sat Sep 13 19:08:21 2014

[Thr 140418972743424] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418972743424] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 140

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

[Thr 140418974844672] Sat Sep 13 19:08:26 2014

[Thr 140418974844672] ***LOG Q0I=> NiPConnect2: XX.XX.XXX.XX:XXXX: connect (111: Connection refused) [nixxi.cpp 3286]

[Thr 140418974844672] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 140

    (SI_ECONN_REFUSE/111; I4; ST; XX.XX.XXX.XX:XXXX) [nixxi.cpp    3286]

Hi Ebad

1.  Have you check the SAP Note 33135 for your issue?

2. Check this link for you refer
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c06c8846-c160-2d10-d18e-d9961e9c7219?overridelayout=t…

BR

SS

Hi,

When we report event in TM , in execution node we have the status a) Directly reported for the document  b) reported from EM.

Whats the basic difference between them. Does point b, means that event is reported in em web UI and then thru RFC , it gets updated in TM.

but then does sap uses the sap logic and BADI when propagation works and when pre processing functionality is used.

Hi

I think you will have no problem closing the year without reconciliation.

shachar