Error when retrieving all backend systems SPS12

After upgrade system to SPS12, there was a error in UME:
"An unexpected error occurred when retrieving all backend systems available for user mapping."
Does anyone given this error?
#1.5 #003048323AFA006A0000004700005F10000438C0C2A59F50#1188300457345#com.sap.security.core.wd.assignusermapping.AssignUserMappingComp#sap.com/tcwddispwda#com.sap.security.core.wd.assignusermapping.AssignUserMappingComp#adm2#577##srv.retail.com_DEP_34251450#adm2#a5fdb470555911dc85f8003048323afa#SAPEngine_Application_Thread[impl:3]_22##0#0#Error##Java###An unexpected error occurred during retrieval of all backend systems available for user mapping for principal ''''.
[EXCEPTION]
#2#USER.PRIVATE_DATASOURCE.un:adm3#com.sap.security.core.wd.exception.UmeUiException: java.lang.NoSuchMethodError
     at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.handleThrowable(UmeUiFactoryCompInterface.java:2865)
     at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getUserMappingSystems(UmeUiFactoryCompInterface.java:1671)
     at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getUserMappingSystems(InternalUmeUiFactoryCompInterface.java:605)
     at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getUserMappingSystems(InternalUmeUiFactoryCompInterface.java:982)
     at com.sap.security.core.wd.assignusermapping.AssignUserMappingComp.refreshSystems(AssignUserMappingComp.java:339)
     at com.sap.security.core.wd.assignusermapping.AssignUserMappingComp.setPrincipal(AssignUserMappingComp.java:288)
     at com.sap.security.core.wd.assignusermapping.wdp.InternalAssignUserMappingComp.setPrincipal(InternalAssignUserMappingComp.java:230)
     at com.sap.security.core.wd.assignusermapping.AssignUserMappingCompInterface.resetComponent(AssignUserMappingCompInterface.java:139)
     at com.sap.security.core.wd.assignusermapping.wdp.InternalAssignUserMappingCompInterface.resetComponent(InternalAssignUserMappingCompInterface.java:136)
     at
Message was edited by:
        Alexander Ardashov

Hi Alexander,
The exception "java.lang.NoSuchMethodError" means that a Java method has been called which does not exist.
Only two possibilities:
a) Your upgrade was only partial successful
b) A bug by SAP
I would consider to reinstall SP12 and if it still doesn't work, open an OSS message.
Hope it helps
Detlev

Similar Messages

Error when calling R3 backend system

Hi,
I have a scenario that sends some data to a Z_Bapi on our R3 system. The process is failing but I'm SXI_MONI I'm not getting errors reported and I'm not getting the last message from my Inegration Process to my R3 system reported.
However when I look at the PE and examine the send message synchrounously Work item, I can see the error in the graphic view. The process runs all the way through my various steps but should then perfrom a transformation before calling the R3 system. The transformation isn't shown on the graphic and I get an error image which looks like a broken red block on the step which sends the data to the r3 system.
I realise this is a little cryptic so have provided a trace of the PE manager to see if that helps. I have checked my adapter (in the adapter monitoring part of the runtime workbench) and that is working fine. I would be extremely grateful to anyone who was able to help.
Thanks in advance
John
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4395AE1A-A40F-095F-E100-0000AC1E1BAF</SAP:MessageId>
<SAP:TimeSent>2005-12-06T15:23:10Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>BS_CUSTOMER_DATA_TEAM</SAP:Service>
<SAP:Interface namespace="http://skunkworks.ordnancesurvey.com/custupdate">MI_CUSTOMER_UPDATE_OUTBOUND</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>IPCUSTINTEGRATION</SAP:Service>
<SAP:Interface namespace="http://skunkworks.ordnancesurvey.com/integration">MI_CUSTOMERUPDATE_CONFIRMATION_RESPONSE</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>e+o2Rj6ePbuEqoQgC6bRsg==</SAP:ObjectId>
<SAP:SWCV>A7YEkB3+EdqlqNjyrB4brw==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://skunkworks.ordnancesurvey.com/integration">MI_CUSTOMERUPDATE_CONFIRMATION_RESPONSE</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="false" ApplicationAckRequested="false" ApplicationErrorAckRequested="false" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2005-12-06T15:23:10Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>4395AE1A-A40F-095F-E100-0000AC1E1BAF</SAP:MessageId>
<SAP:Info>host:ermprot1:8000::remote-addr:172.30.18.12</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2005-12-06T15:23:10Z" wasRead="false">
<SAP:Engine type="IS">is.00.ermprot1</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>4395AE1A-A40F-095F-E100-0000AC1E1BAF</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2005-12-06T15:23:10Z" wasRead="false">
<SAP:Engine type="PE" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>
<SAP:MessageId>4395AE1A-A40F-095F-E100-0000AC1E1BAF</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20051206</SAP:Date>
<SAP:Time>152310</SAP:Time>
<SAP:Host>ermprot1</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>SunOS</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>001</SAP:AdapterStatus>
<SAP:User>XIAPPLUSER</SAP:User>
<SAP:TraceLevel>3</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId />
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService />
<SAP:QIdInternal>XBQO$PE_WS90100001</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">AC1E1BAF09604395ACDE0C4C</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="MSGID">4395AE1AA40F095FE1000000AC1E1BAF</SAP:EOReferenceOutbound>
<SAP:MessageSizePayload>605</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>605</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>526</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>PE</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>48</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.348334</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.374455</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.374499</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.537662</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.544475</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.557175</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.557718</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.567097</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.567617</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.5826</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.582648</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.788221</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.794996</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.850987</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.852019</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152310.863395</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="ermprot1">20051206152310.86393</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="end" host="ermprot1">20051206152311.042167</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>43940953D1920960E1000000AC1E1BAF</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName />
<SAP:ToPartyName />
<SAP:ToServiceName />
<SAP:ToInterfaceName />
<SAP:ToInterfaceNamespace />
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">PE</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">00000000000000000000000000000000</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">PE</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
<Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
<Trace level="1" type="T">content-type text/xml</Trace>
<Trace level="1" type="T">user-agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; (R1 1.5); .NET CLR 1.1.4322)</Trace>
<Trace level="1" type="T">host ermprot1:8000</Trace>
<Trace level="1" type="T">content-length 605</Trace>
<Trace level="1" type="T">remote-addr 172.30.18.12</Trace>
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 4395AE1AA40F095FE1000000AC1E1BAF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 4395AE1AA40F095FE1000000AC1E1BAF</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0013</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0013</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 4395AE1AA40F095FE1000000AC1E1BAF</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IPCUSTINTEGRATION</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IPCUSTINTEGRATION MI_CUSTOMERUPDATE_CONFIRMATION_RESPONSE</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_CUSTOMERUPDATE_CONFIRMATION_RESPONSE</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO0___0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 001</Trace>
<Trace level="2" type="T">Increment log sequence to 002</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 7BEA36463E9E3DBB84AA84200BA6D1B2</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 03B604901DFE11DAA5A8D8F2AC1E1BAF</Trace>
<Trace level="1" type="T">Interface Mapping http://skunkworks.ordnancesurvey.com/integration IM_CUSTOMER_UPDATE_CONFIRMATION</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_CUSTOMER_UPDATE_CONFIRMATION_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_CUSTOMER_UPDATE_CONFIRMATION_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_CUSTOMER_UPDATE_CONFIRMATION_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_CUSTOMER_UPDATE_CONFIRMATION_ completed. (executeStep() of com.sap.xi.tf._MM_CUSTOMER_UPDATE_CONFIRMATION_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-BS_CUSTOMER_DATA_TEAM</Trace>
<Trace level="2" type="T">-IPCUSTINTEGRATION</Trace>
<Trace level="2" type="T">http://skunkworks.ordnancesurvey.com/integration.MI_CUSTOMERUPDATE_CONFIRMATION_RESPONSE</Trace>
<Trace level="2" type="T">create outbound binding for Process Engine</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2005-12-06T15:23:10Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Channel for Process Engine: PE</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = PE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_CALL_BPE</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">determined process: WF task WS90100001</Trace>
<Trace level="3" type="T">......extracting from header: ConversationId = ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">......extracting from header: SenderParty = ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">......extracting from header: SenderPartyAgency = ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">......extracting from header: SenderPartyScheme = ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">......extracting from header: SenderService = BS_CUSTOMER_DATA_TEAM ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">......extracting from header: Interface = MI_CUSTOMERUPDATE_CONFIRMATION_RESPONSE ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">......extracting from header: InterfaceNamespace = http://skunkworks.ordnancesurvey.com/integration ,</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="3" type="T">created BPE proxy for message 4395AE1AA40F095FE1000000AC1E1BAF</Trace>
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:11Z CET qRFC raised on XBQO$PE_WS90100001</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:11Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
<Trace level="3" type="T">Async processing: skip mapping of response</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2005-12-06T15:23:11Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>

Hi John,
Pls check in SXI_CACHE to verify that the BPM(active in Integration Repository) has the latest version active on the ABAP stack.(I am saying this because you mentioned that a mapping step was missing..is it not..)
go to SXI_CACHE --> Integration Processes(double click), in the list that you get verify that the return code is 0.
Thanks & Regards,
Renjith.

Intermittent errors when retrieving through smart view (11.1.2.5.210) in Oracle 11.1.2.3.500

We are getting the below errors when retrieving from huge smart view sheets for couple of our applications. We have increased the time out settings from the local registry, server registry, mod_wl_ohs file, Web logic console, http.conf, Essbase.properties. Also, increased the JVM from opmn.xml & setCustomParamsAnalyticProviderServices.bat. However we still face the error.
Note: this is an intermittent error and does not happen all the time.
Cannot connect to the provider. Make sure it is running in the specified host/port. Error(12152).
Cannot connect to the provider. Make sure it is running in the specified host/port. Error(12031).
Also, we are facing retrieval performance issues after we upgraded to 11.1.2.3.500 after we migrated from 11.1.1.3.500. Has anyone faced this issue? if so, any suggestions in improving the retrieval performance (especially with MDX member formulas in ASO applications) in 11.1.2.3.500 version?
Smart view version: 11.1.2.5.210

Is there a load balancer being used?
Does the issue common on both Shared and Private connection?
Smartview client
     A)    add a essbase.cfg to the client machine in smartview\bin
             the file will have 3 entries
            NETDELAY 2000
            NETRETRYCOUNT 2000
            NETTCPCONNECTRETRYCOUNT 200
You can give it a try on a single client machine and check is the result is improved.

Potal Authorisation Error:"Failed to connect backend system.Check your syst

Hi Experts,
Please advise me on how to proceed....
I created a dashboard reports (5) based on 5 different reports in BI Queries using Visual Composer...I deployed them to portal and in portal i assigned those iviews to a role and assigned that role to a end user.
In BW end user is autorized to execute those 5 queries and in portal user is able to access those queries as well
But when he tried to execute Dashboard reports..it is displaying error
"Failed to connect backend system.Check your system definition and user priviliges"
Then i modified his authorisations in BW assigned SAP_J2EE_ADMIN role in BW and then in portal he is able to execute the Dashboard reports...by assigning the SAP_J2EE_ADMIN role he is able to execute dashboards in portal and he got more authorisation in portal than he required like 'Content Admin','User Admin' and 'System Admin'
I tried by using SAP_J2EE_GUEST role but he is getting error
"Failed to connect backend system.Check your system definition and user priviliges"
Please advise on how to proceed
Thanks

Hi,
Refer,
Visual composer
Failed to connect to backend system. Check your system definition and user
Regards,
P.Manivannan.

Error when posting IDoc *** in system ERP100

Hi Experts!
Can you pls help me with a goods receipt issue?
When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
The same msg is getting displayed in RZ20.
On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
What can be the reason for this problem please?
What is in general the way to analyse and solve this kind of issue?
Thanks a lot !!
imre

Hi,
First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of BBP_DOCUMENT_TAB.
Hope this helps.
Regards,
Kalyan

CTS + Error when Importing to target system (Q)

Hi all,
I have configured CTS+ for our portal landscape. I'm using Solman 7.0 as domain controller. I have released a transport from D system to Q, It creates a Q buffer properly. But when I try import in Q, I get the following error;
Internal communication error with destination CTSDEPLOY
ERROR_WEBSERVICE_RUNTIME_INIT Error when instantiating the Web service runtime (No logical port 'CTS
>>>DEPLOY' exists for the proxy c lass 'CO_TFLDEPLOY_PROXY_VI_DOCUMENT' )
I am not able to fix this issue. Can someone help in this regards?
Thanks,

Do this:
1. Call transaction RZ21.
2. Choose "Technical infrastructure -> Reorganize segment table".
3. Choose "Add missing logical ports to this client", and choose "Execute".

Error when retrieving oracle clobs

Here's the sql statement that we are running:
SELECT dbms_lob.substr(sql_statement,dbms_lob.getlength(sql_statement),1) sql_statement FROM query
WHERE query_tk = [Param.1]
If the sql_statement is > 4000 chars, we are getting this error:
Fatal Error
A SQL Error has occurred on query, ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: at line 1 .

We are seeing this outside of xmii as well.
Here's the background. We originally tried to do a normal insert to the clob (thru xmii) but we got errors when inserting values of more than 4000 chars. So, we inserted the clob differently (code used below). That's when we started getting this new error. Is there another way to insert/retrieve clobs?
   --INSERT "base" row if it does not already exist.
   BEGIN
     SELECT query_tk
       INTO v_dummy
       FROM query
       WHERE query_tk = p_query_tk;
     EXCEPTION
       WHEN NO_DATA_FOUND THEN
         INSERT INTO query
           (query_tk
           ,last_updated_timestamp
           ,sql_statement
         VALUES
           (p_query_tk
           ,SYSDATE
           ,'DUMMY');
   END;
   --Initialize buffer with data to be inserted
   v_copy_length := LENGTH(p_sql_statement);
   -- get LOB handle
   SELECT sql_statement
     INTO v_lobloc
     FROM query
     WHERE query_tk = p_query_tk
     FOR UPDATE;
   dbms_lob.write(v_lobloc,v_copy_length,1,p_sql_statement);

Apache Rewrite rule for all backend systems?

Dear all,
Could anyone, write and give me the extact working rewrite rule in apache 2.0 for backend systems like R/3 and BW, ICH.
Paths for bakend systems are as follows.
R/3= http://r3server.compny.domain.com:r3port/sap/bc/gui/sap/its
BW= http://bwserver.compny.domain.com:bwport/sap/bw/BEx
(SSL configured in ICH)
ICH=http://ichserver.compny.domain.com:ichport/sap/bc/bsp
Kindly provide the above rules
Rgds
PRadeep

Dear all,
Could anyone, write and give me the extact working rewrite rule in apache 2.0 for backend systems like R/3 and BW, ICH.
Paths for bakend systems are as follows.
R/3= http://r3server.compny.domain.com:r3port/sap/bc/gui/sap/its
BW= http://bwserver.compny.domain.com:bwport/sap/bw/BEx
(SSL configured in ICH)
ICH=http://ichserver.compny.domain.com:ichport/sap/bc/bsp
Kindly provide the above rules
Rgds
PRadeep

Error when retrieving owner in universe, Pls help.

Hi Expert,
i'm getting this error when i was trying to make an object in universe.
Although, i already test the connection CMS and it's responding.
Exception: DBD, [MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"city_id" From "city" Table__1' at line 1State: 23000.
I'm using BO Edge 3.1 and MySQL 5.
How to solve it?
Thanks.
Regards,
Y Permana.

Yes, i did but the error still happening when i'm using MySQL database.
But the error didn't happen when i tried it in MsSQL database.
Any advise?
Thanks.
Regards,
Y Permana.

Error when using the variable System::ErrorDescription

HI All,
When I try to use the variable System::ErrorDescription I get the following error:
The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there.
Do I need to declare it or it's a variable that always is available to get exceptions from the execution states?

if this is in a Script Task then:
- add the variable in the Script task property ReadOnlyVariables list
- in the Script Code refer to it as
string ErrorDesc = (string) Dts.Variables["System::ErrorDescription"].Value;
Jan D'Hondt - SQL server BI development

Error when connect from portal system (abap ) to external ssl client - sm59

Hi I am tryign to setup a ssl connection from the abap sm59 portal system to an exteral server.. I have setup the certs that the client has given me in strust.but i m gettign the ffg error.
sysno      60
sid        PID
systemid   370 (Solaris on SPARCV9 CPU)
relno      7110
patchlevel 0
patchno    150
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    /usr/sap/PID/SYS/profile/PID_DVEBMGS60_pidevdb
pid        3911
[Thr 01] Thu Jun 14 08:38:48 2012
[Thr 01] TRACE FILE TRUNCATED
[Thr 07] Thu Jun 14 08:39:07 2012
[Thr 07] *** ERROR during SecudeSSL_SessionStart() from SSL_connect()==SSL_ERROR_SSL
[Thr 07]    session uses PSE file "/usr/sap/PID/DVEBMGS60/sec/SAPSSLA.pse"
[Thr 07] SecudeSSL_SessionStart: SSL_connect() failed
[Thr 07]   secude_error 536871970 (0x20000422) = "SSL record with the wrong SSLPlaintext.version received"
[Thr 07] >>            Begin of Secude-SSL Errorstack            >>
[Thr 07] ERROR in ssl3_get_record: (536871970/0x20000422) SSL record with the wrong SSLPlaintext.version received
[Thr 07] <<            End of Secude-SSL Errorstack
[Thr 07]   SSL_get_state() returned 0x00002120 "SSLv3 read server hello A"
[Thr 07]   SSL NI-sock: local=57.24.111.151:34110 peer=57.24.110.116:5081
[Thr 07] <<- ERROR: SapSSLSessionStart(sssl_hdl=10720d530)==SSSLERR_SSL_CONNECT
[Thr 07] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-57): SSSLERR_SSL_CONNECT {00020a7c} [icxxconn_mt.c 1957]
When i change the sm59 connection not to use ssl. it give me a pop up screen . and asks me to enter user and password...
He then give me a private key file .. i.e a .pfx file but not sure how to load this in strust. I tried to convert in useign sapgenpse. but it fails with teh ffg error
12% sapgenpse import_p12 -p /usr/sap/PID/amos/amos_client.pse /usr/sap/PID/amos/amos_client_pk.pfx
import_p12: MISSING password for PKCS#12 file "/usr/sap/PID/amos/amos_client_pk.pfx"
Please enter PKCS#12 encryption password: *******
PKCS#12/PFX file contains 1 keypair:
1. FriendlyName = "amos.server.interface.webuser.web_int.cert"
     X.509v3 (type=Both) RSA-2048 (signed with sha1WithRsaEncryption)
     Subject="CN=AMOS WebService Interface Client, OU=IT&S MRO, O=South African Airways (Pty) Ltd, L=OR Tambo International Airport, SP=Gauteng, C=ZA"
     Issuer ="[email protected], CN=ca.flysaa.com, OU=Certificate Authority, O=South African Airways (Pty) Ltd, L=OR Tambo International Airport, SP=Gauteng, C=ZA"
ERROR: Incomplete certification path -- NEED certificate of "[email protected], CN=ca.flysaa.com, OU=Certificate Authority, O=South African Airways (Pty) Ltd, L=OR Tambo International Airport, SP=Gauteng, C=ZA"!
I have attached a doc of what it looks like.. appreciate any help

Hi,
There is an error in the publishing of template
Template :"bbpsc02" is not publised in ITS.
Go to T.code: SE80
Publish all the templates again and check
Check with your SAP BASIS team for the help
Regards
Ganesh

EVDRE encountered an error when retrieving data from web server

Hi
When I am trying to open Data Input=>Build a schedule using a dynamic template in BPC version for SAP netweaver, I am getting the below error "EVDRE encountered an error retrieving data from the Web Server".
I am not able to open any template, every time I am getting the same message. I have tried again after reprocessing all the dimension.
Even I have tried in appset APSHELL also, there also I am getting the same error
Request you to help me to resolve the above error which will allow me to proceed further.
Thanks in Advance.
Venkat

Hi,
Beside Nilanjan's solution, this error could also occur when the expansion is running more rows than the Excel limit allows (65'000 rows and 256 cols for Excel 2003)...
Even when you're using suppress field to reduce the number of rows, the first sequence is to retrieve the complete dataset before performing any suppression. And this could of course exceed the limit sometimes.
Hope this helps.
Kind Regards,
Patrick

Error when retrieve resource by the property contentlink

We are facing problems to retreive an resource by the property "contentlink", for example:
We have an resource in the wpccontent repository, and your property "contentlink" has this value /irj/servlet/prt/portal/prtroot/docs/guid/3062f0a0-a97e-2c10-19ac-bcc642332ee1. When try to retrieve the resource, we received an Rerource404Exception error.
But when we replace the value in the address bar of web browser from /guid... by the value of property "shortID", that contains the value /guid/a05daa5e-a18a-2c10-14bf-cd2506ea3c94, the resource is displayed normaly.
The property "contentlink" can be with wrong values? Can anybody tell me why this happen?
Note: This error happen with any kind of resource, but not with all resources. The error occurs with some resources only. And the folder does not have versioning enabled.
Thanks & regards,
Raphael

Hi Shushmakad,
If you set Preserve Sequence Property=true. BizTalk will always expect source node will be in sequence, but you have option to change sequence of destination schema by updating xslt.
Can you test your map with sample input message with sequence.
Debug xslt (use this url for reference)
http://msdn.microsoft.com/en-us/library/ms255602(v=vs.110).aspx
Regards
Suman

I/O device error when trying to backup system image (any advice? please!)

Having posted this once with absolutely no response, I'll try again.
When trying to backup my K330B system image, I get "device error encountered with either the source or the destination (0x8078012D)" and "Additional information: The request could not be performed because of an I/O device error. (0x8007045D)" It recommends chkdsk/r on both the source and destination devices. I did this for C: and for the external drive I'm backing up to. No problems are found.
I also found the Lenovo Hard Drive Quick Test on the support site. It does not list K330B as one of the devices it is designed for, but I tried it anyway. It reported an error on the read test and two other tests that it performed when directed to test all partitions on the HDD.
Has anyone else had problems backup up the entire system image but no problems backing up just the C: partition?

Backing up system image using what program or component?
What brand hard drives? Most manufacturers have test utilities
for their drives, sometimes better at finding errors.
As HDQT you tried found some errors, you should test drives
more thoroughly as a first step.

Custom Report Erroring when using All as parameter

Hi All,
I am facing a problem in running custom report.
=> DB Server Info
RDBMS : 11.2.0.2.0
Oracle Applications : 12.1.3
I am getting following error.
REP-1401: 'afterpform': Fatal PL/SQL error occurred.
ORA-06502: PL/SQL: numeric or value error
custom report two parameters one is date parameter and name parameter
date parameter is using as fnd_date.canonical_to_date(:P_EFFECTIVE_DATE) in queries.
if I give name parameter for individual, then it works fine.
if I give name parameter as "All", then its erroring. I tried it in my best way, but its not working.
variable data length increased though its not working, can any one help me on this please....
Here is the Afterpform code
function AfterPForm return boolean is
lName VARCHAR2(5000); -- its changed from lName varchar2(50);
begin
IF :P_NAME <> 'All' THEN
lName:= 'AND name =:P_NAME';
ELSE
lName:='AND name in                                                             (select name from <******>
          order by name
END IF;
:P_Where_Clause := lName;
return (TRUE);
end;
Thanks for all your help so far.
Ram.
Edited by: user8822881 on Feb 9, 2012 10:43 AM

excuse i understood that you use All as parameter name
ORA 6502 is when you assign a char to a number or when assign a value which length is greater than the variable length
what's the dimension of p_where_clause for example?
you can trace with srw.message
--- <Code>
function AfterPForm return boolean is
lName VARCHAR2(5000); -- its changed from lName varchar2(50);
begin
srw.message(1,'step 1');
IF :P_NAME = 'All' THEN
srw.message(2,'step 2');
lName:='AND name in (select name from <table>
order by name
srw.message(3,'step 3');
ELSE
srw.message(4,'step 4');
lName:= 'AND name =:P_NAME';
srw.message(5,'step 5');
END IF;
srw.message(6,'step 6');
:P_Where_Clause := lName;
srw.message(7,'step 7');
return (TRUE);
end;
---</Code>
i think your query is not good
for example
lName:= 'AND name =:P_NAME';
when instance the query the query search this condition but no use the value of p_name parameter
write
lName:= 'AND name = '||''''||:P_NAME||''''; then :p_name take the value

Error when retrieving all backend systems SPS12

Similar Messages

Maybe you are looking for