SAP Upgrade issue ABAP-PI Proxy error
Hi Guys,
We have an issue in SAP R3 system after the recent SAP upgrade.
The proxy programs in R3 were using SAP Standard structure in their development.
Standard structure : SAPPLCO_LOG_ITEM_CODE (TYPE SAPPLCO_LOG)
And so after the upgrade, There seems to be a new field added in the above standard structure and hence causing mismatch between the proxy program developed internal structure to the SAP standard structure.
We come to understand that this Standard structure is being used from SAP PI, Software component SAP APPL.
So SAP PI has old SAP standard structure and SAP R3 has new standard structure with additional field.
Can you please suggest how to overcome this issue. We have also raised an OSS ticket to SAP.
Kind Regards
Rajesh.S
Hi Harald,
Thank You for the information. I was able to download SAP_APPL 6.06 content from SAP service market place. Here We have a doubt before importing the new SAP APPL content. In market place downloads under SAP_APPL 6.06 we were able to see few many database downloads with last changed at 3.04.2014.
Our EHP upgrade for SAP_APPL is 6.06 , SP level 0007. So we should download / import the highlighted content version (SAPAPPL60607) in the screenshot from market place or download / import the latest change under SAP_APPL 6.06 download patch ? Kindly let us know.
Best Regards,
Rajesh.S
Similar Messages
-
ABAP Consumer Proxy error after upgraded from 7.0 SP14 to 7.01 SP3
The ABAP consumer proxy was created in ECC6 with Netweaver 7.0 SP14. After the system was upgraded to Netweaver 7.01 SP3 the proxy call started to get error back.
The first error message from the service provider said "SoapException: Server did not recognize the value of HTTP Header SOAPAction". This error was resolved by manually putting the correct action in the SOAManager configuration.
Ran the same test again and then the service provider complained about the To field in the SOAP Header. The error message said "SoapHeaderException: SOAP header To was not understood".
Below is the To field in the Requesting XML message from the 7.0 SP14 system that worked fine:
<n3:To soap-env:mustUnderstand="1" xmlns:n3="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope">
http://localhost:50081/AddSix.asmx
</n3:To>
Below is the To field in the Requesting XML message from the 7.01 SP3 system that did not work:
<wsa:To soap-env:mustUnderstand="1" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
http://localhost:50081/AddSix.asmx
</wsa:To>
It looks like the issue is with the xmlns:soap-env element that has different values in these two systems. Searched in SDN but could not find any related information. Please help if anyone has experienced similar issue or knows how to fix it.
Thanks,
JiannanGot solution from SAP through an OSS message. Below is SAP's solution:
Either the Message ID protocol should be switched off on the SAP
consumer side or turn on this protocol support on the .NET provider.
To switch off the Message ID protocol:
1. start the soa manager
2. find the consumer proxy
3. find the corresponding logical port
4. jump to the 'Messaging' tab
5. choose the 'Suppress ID Transfer' from the dropdown list of the Message ID Protocol field
Besides this setting I also have to specify the operation in the Operation specific tab of the logical port configuration. -
Hi ,
I am forwarding Vendor Data from SRM EBP to SUS with the predifined proxies given by SAP, bu t i get below error when it reaches SUS System.Message processing both in SAP EBP and SAP XI is fine.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX_TRADING_PARTNER_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack> <SAP:Retry>M</SAP:Retry>
</SAP:Error>
Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause ApplicationHi attached trace, kindly update wat could be the problem in case of EBP SUS Vendor replication
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<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="1" type="T">system-ID = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:21Z 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 = DD128437FD4A75F193690017A4F3435A</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler 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="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SSR</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WIP-SRINUS</Trace>
<Trace level="1" type="Timestamp">2008-04-25T04:58:24Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="Inbound Framework" />
- <!-- ************************************
-->
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o97" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o97">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o96" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>297</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o96">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>297</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
*<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA:034 -Organizational unit 00000008 does not exist; check entries Programm:* CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace> -
ABAP provider proxy error using Fault Message Type
Hello experts,
I'm using a provider ABAP proxy with a fault message type in the inbound service interface.
In the ABAP code on the backend system, I need to fill a database table.
in case the record exist --> fault + message back to SAP PI to be alerted.
I do this with a RAISE EXCEPTION TYPE.
I generated all necessary proxies.
The error I got on the backend system (SXMB_MONI) is this:
Application Error - Call Inbound Proxy
SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="xxxxx">FMT_xxxxxx</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
Can it be that I need to use something else instead of the RAISE EXCEPTION TYPE. to get something back to SAP PI?
Now the error is logged in SXMB_MONI on the backend system.
Please advice.
Thanks a lot
DimitriHi Dimitri,
Check out these links -
1. /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
2. http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
Regards,
Sunil Chandra -
SAP NetWeaver 2004s ABAP Trial Version - error code = 200
Hi all,
installation of SAP NetWeaver 2004s ABAP Trial Version
which was attached to the book ABAP-Objects ends again and again with
ProductException: (error code = 200; message="Java error"; exception = java.lang.Exception)
Attached you find information about
1) Host-file
2) Network connections
4) Error - Log
It seems that the [# [#]
echo 7/tcp
echo 7/udp
discard
9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
#Active users
systat 11/tcp users #Active users
daytime 13/tcp
daytime
13/udp
qotd 17/tcp quote #Quote of the day
qotd 17/udp quote
#Quote of the day
chargen 19/tcp ttytst source #Character generator
chargen
4) == E R R OR L O G ================================================
(Jan 1, 2007 1:07:15 PM), Install, com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles, err,
an error occurred and product installation failed. Look at the log file D:SAPNSPlog.txt for details.
(Jan 1, 2007 1:07:15 PM), Install, com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles, err,
ProductException: (error code = 200; message="Java error"; exception = java.lang.Exception)
STACK_TRACE: 15
ProductException: (error code = 200; message="Java error"; exception = java.lang.Exception)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.execute(StepWrapperInstallFiles.java:254)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllSteps(StepWrapperInstallFiles.java:224)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllInstallationSteps(StepWrapperInstallFiles.java:177)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.install(StepWrapperInstallFiles.java:268)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
(Jan 1, 2007 1:12:17 PM), Install, com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct, err,
An error occurred and product uninstallation failed. Look at the log file D:SAPNSPlog.txt for details.
(Jan 1, 2007 1:12:17 PM), Install, com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles, err,
ProductException: (error code = 200; message="Java error"; exception = java.lang.Exception)
STACK_TRACE: 15
ProductException: (error code = 200; message="Java error"; exception = java.lang.Exception)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.execute(StepWrapperInstallFiles.java:254)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllSteps(StepWrapperInstallFiles.java:224)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllUninstallationSteps(StepWrapperInstallFiles.java:192)
at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.uninstall(StepWrapperInstallFiles.java:313)
at com.installshield.product.service.product.PureJavaProductServiceImpl.uninstallProductAction(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.processActionsFailed(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
at java.lang.Thread.run(Unknown Source
== Remark to threads ========================
Thread a)
"I found it is very useful to have a clean system" => not applicable to me
Thread b)
deals with removing relics of previous installations => hints considered but error still appears
Thread c)
not applicable to meHi all
I've read your entrys.
Saw that the solution is missing.
It can be found in the manuals:
1. Download the "Registry Clean Tool for SAP NetWeaver 2004s ABAP" and use it.
2. Download the latest Version of "SAP NetWeaver 2004s ABAP" and un-rar it.
3. Install the "Microsoft Loopback Adapter" an activate it.
4. Retry to install.
Summary:
So the error 200 was caused for the first time from trying an installation without a Loopback Adapter, and after that from trying to re-install without cleaning the registry.
Now its working fine.
Thomas -
File - ABAP Server Proxy - Error - CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV
Hi,
I am working on File-ABAP Proxy(Server) scenario. I've created the repository and integration objects correctly and have activated them. When I do a Test Configuration in the Integration Directory, I am getting the below error:
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="2" type="T">......attachment XI_Context not found </Trace> <Trace level="3" type="T">Mapping already defined in interface determination </Trace> <Trace level="3" type="T">Object ID of Interface Mapping 50539A6C73A334AEA587C7CD0459B373 </Trace> <Trace level="3" type="T">Version ID of Interface Mapping 21A89031E65411DE9576D36A0A505355 </Trace> <Trace level="1" type="T">Interface Mapping urn:acc:pi:serverproxy OM_Member </Trace> <Trace level="3" type="T">Mapping Steps 1 JAVA_JDK com/sap/xi/tf/_MM_Member_ </Trace> <Trace level="3" type="T">MTOM Attachments are Transferred to the Payload </Trace> <Trace level="3" type="T">Dynamic Configuration Is Empty </Trace> <Trace level="2" type="T">Mode 0 </Trace> <Trace level="1" type="T">Field PARAMETRIZATION not a member of INPUT Thrown: com.sap.mw.jco.JCO$Exception: Field PARAMETRIZATION not a member of INPUT at com.sap.mw.jco.JCO$MetaData.indexOf(JCO.java:9897) at com.sap.mw.jco.JCO$Record.getTable(JCO.java:14710) at com.sap.aii.ibrun.sbeans.mapping.ParametrizationMap.newInstance(ParametrizationMap.java:64) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:111) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:72) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy376.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:266) </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
The above error says that the error is: "Mapping already defined in interface determination". But I've double checked my Interface Determination, it is correct.
And if I try to post the payload in the Integration Engine in RWB, I see the status as "Recorded for Outbound Processing" in SXMB_MONI. If I try to release the queue, the status is "SYSFAIL".
For your information, I'm working on SAP PI version 7.11 PI 7.1 EHP1 SPS 03.
Any inputs on this eror will be really helpful.
Thanks,
VijayHi Vijaya,
-->Try to execute the end to end scenario with out testing it in the Integration Directory(ID).
-->Even i faced some problem in the ID while testing the scenario through the TEST CONFIGURATION,but when i execute the end to end scenario it is successful.
Thanks -
<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[/oracle/***/sapdata1/SUM/sdt/log/SUM/DEFINE-TARGET-SOURCE_07.LOG]/-->
<!--PATTERN[DEFINE-TARGET-SOURCE_07.LOG]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Apr 18, 2015 8:03:30 PM [Info ]: The detected system topology is ABAP_ONLY
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Setting catalog key inbox.option to value true into shared input catalog.
Apr 18, 2015 8:55:43 PM [Info ]: Setting catalog key stack.option to value false into shared input catalog.
Apr 18, 2015 8:55:43 PM [Error ]: The provided Stack file or Directory: /oracle/***/sapdata1/TT_stack.txt, is not valid.
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog
Apr 18, 2015 9:05:45 PM [Info ]: Setting catalog key inbox.option to value false into shared input catalog.
Apr 18, 2015 9:05:45 PM [Info ]: Setting catalog key stack.option to value true into shared input catalog.
Apr 18, 2015 9:05:45 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException: /oracle/***/sapdata1/TT_stack.txt is not a valid stack definition file.
Could not parse XML file /oracle/***/sapdata1/TT_stack.txt.
org.xml.sax.SAXException has occurred: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
DETECT define_target define-target-dialog define-target-source com.sap.sdt.j2ee.services.servicesimpl.DefineTargetService class com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserExceptionHi Heng,
com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException: /oracle/***/sapdata1/TT_stack.txt is not a valid stack definition file.
Have you read the lines in log which you shared,It's completely an issue with your stack file generated or using.
SUM tool is clearly asking for stack.xml instead of stack.txt
Try to use stack.xml file here to proceed further for a successful upgrade.
Good luck !! -
ABAP Client Proxy error code: 401, error text: Unauthorized
Hi,
I have Client proxy in ECC for oubound interface in PI 7.0, when i look into SXMB_MONI of ECC i can see my message with Error "HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)".
As per few thread i already assign SAP_XI_APPL_SERV_USER role to PIAPPLUSER in ECC, still i am getting same eror.
I do not understand how this Proxy communication work, which ECC user will be use in communication and how this communcation link to RFC destination "SAP_PROXY_ESR" type G. Even i can not see type H in ECC so i created RFC destination of type G.
With Regards
SunilWe were able to get it working by making a change in the Integration Engine Configuration (in sxmb_adm).
Changed "Corresponding Integ. Server" from "http://<server>:<port>/sap/xi/engine?type=entry"
to "dest://RFCdestinationName" -
Hi Everyone,
In PI ESR, I have update the data enhancement structure with new field and I have mistakenly activated standard service Interface which is refering to ehancement structure.
Now in the ABAP side in SPROXY transaction, Interface is showing red. Since its standard proxy I am unable to regenerate the proxy.
Please let me know your suggession.
Regards,
SudheerHi,
Error is related to the connection set up done between ECC and PI.
Test the connection using sldcheck.
HTH
Rajesh -
Sap Interface Issues - SM58- the following errors were found
Hi Experts,
Could you please tell me...why are the following errors coming in SAP EDI .
Caller Function Module Target System Date Time Status Text Transaction ID
C10IBBITSN IDOC_INBOUND_ASYNCHRONOUS SAPBC4X-LOG_L 16.09.2011 08:14:28 com.wm.lang.flow.FlowException: SQL0803 - Duplicat 0ADE2828A6C64E73055FAD
C10IBBITSN IDOC_INBOUND_ASYNCHRONOUS SAPBC4X-LOG_L 16.09.2011 08:14:29 com.wm.lang.flow.FlowException: SQL0803 - Duplicat 0ADE2828A6C64E73055FAD
C10IBBITSN IDOC_INBOUND_ASYNCHRONOUS SAPBC4X-LOG_L 16.09.2011 08:14:29 com.wm.lang.flow.FlowException: SQL0803 - Duplicat 0ADE2828A6C64E73055FAD
C10IBBITSN IDOC_INBOUND_ASYNCHRONOUS SAPBC4X-LOG_L 16.09.2011 08:14:30 com.wm.lang.flow.FlowException: SQL0803 - Duplicat 0ADE2828A6C64E73055FADSo you are intentionally creating duplicate posts. You know as well as I do the difficulty in following threads when people post in several different places the same question, and not knowing which one to follow and respond to. In your case you posted the same question in 3 places.
-
Hi Experts,
My scenario R/3->XI(ABAP Proxy)--->SUS Systems
Getting the following error in SUS system.XI system it doesn't throw any error in moni.
I am new to proxy concepts.Also please let me know any related blogs or suggestions in this regards.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Call Inbound Proxy
-->
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX1_SUSIV_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
SudhansuHi Behera,
Can you debug your proxy using this blog:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502a7f0e-e5d9-2910-5aa2-976a8ed8384f&overridelayout=true
Also please check few solutions given in this threads for the same issue:
Re: Messages waiting in SUS Moni
Re: ABAP Inbound Proxy Error !
Regards,
---Satish -
Error during installation of SAP NetWeaver 2004s Abap Trial Version
The following error occurred during installation of SAP NetWeaver 2004s ABAP Trial Version:
ERROR 2008-03-13 09:47:27
FSL-00001 System call failed. Error 53 (Network path not found.) in execution of system call 'CreateFile' with parameter (
127.0.0.1\sapmnt\trans\bin\DOMAIN.CFG, GENERIC_READ|GENERIC_WRITE, FILE_SHARE_READ|FILE_SHARE_WRITE, NULL, CREATE_NEW, FILE_ATTRIBUTE_NORMAL, NULL), line (763) in file (synxcpath.cpp).
This error occurred at the end of the installation.
Any idea?
Thank's, Thiago.>
Thiago Amaral wrote:
> Ps: I already restarted my notebook.
That does not automatically start your instance. Have a look at the shortcuts SAP installed in your startmenu. There's both a startscript and a stopscript. -
Hi Experts,
I am upgrading my system to EHP5. While running phase MAIN_SHDRUN/ACT_UPG the upgrade stops and does not proceeds further. Below are the logs generated:
>> 2011/02/09 08:44:24 START OF PHASE MAIN_SHDRUN/ACT_UPG
running G:\EHPI\abap\exe\tp.exe pf=G:\EHPI\abap\bin\SHADOW.TPP checkimpdp RE2
>>>> Repository modifications <<<<
You must now include your repository modifications in the new SAP import.
6 modified objects are found to be adjusted and 0 objects are automatically
maintained by import of an adjustment transport bound to this procedure.
CAUTION: It is impossible to keep these modifications after you have
confirmed this query!
If you want to adjust your repository, please proceed as follows:
Logon to the shadow instance as user DDIC in client 000 on server
mb3ap1023 instance: 01
Set the System Change option with transaction SE06.
Create users for modification adjustment by copying user DDIC with
transaction SU01.
Logon to the shadow instance as ordinary user and make adjustments with
transaction SPDD. Refer to the manual for further information.
01) * Adjustments made, continue with procedure
02) - Continue without adjustments
03) - Exit this program
: Adjustments made, continue with procedure
Collecting adjustments ...
Collection done - creating cofile ...
running G:\EHPI\abap\exe\tp.exe pf=G:\EHPI\abap\bin\ACTUPG.TPP put RE2
=> Received signal Ctrl C from keyboard and exited at 20110209220536
Got interrupt. When you restart SAPehpi all currently running subprocesses
will be checked. It is strongly recommended to wait for
these processes (which is the default behaviour).
The above logs say that while upgrading it recieved ctrl C. Now I dont know how it received ctrl C. Also it always stops at 22:05 pm only.
Please help in resolving the above issue.
Thanks,
RJHi,
My Upgrade has again got stucked in Pre- Processing step, in MAIN_SHDRUN/ACT_UPG phase.
The error which I am getting is :
DSU Execution error:
Unable to execute the SDT request ABAP operation pre-execute on hostname mb3ap1023 instance 00 Pre-Uptime execution of the ABAP upgrade request ABAP has failed Error from unit observer Tool connector failed with FATAL ERROR: Missing id in line ' "15228" SFX;20110219203107;20110220033916;"Another SAPehpi (started first)";"SAPehpi":dw' . Connection to SAPup could not be established, see following messages. Could not connect to host mb3ap1023 on port 4240. java.net.ConnectException: Connection refused: connect java.net.ConnectException: Connection refused: connect
Please help me in resolving the above issue.
Thanks,
RJ -
SAP Upgrade ORA-00905: missing keyword
Dear experts,
we have a very urgent SAP upgrade case,
From SAP R/3 470 SR1 110 to ECC 6 EHP4 SPS09
source system have three languages ZH EN DE,it's a
non-unicode system,before SAP upgrade,From rscpinst, i delete language
German and change contry code to CN,
(China). Then there is only code page 8400,T-code: I18N check ok,now we have
a error during upgrade,i was already replace the kernel to 385 version(640_Rel Non-unicode,TP and R3trans alreay the latest version) repeat the SHADOW_IMPORT_UPG1 step but still fail,log result as follow,the SAPKLZHSR1EHP4ERP6F8.GS1 has incomplete conversion
but the previous log file I.E SAPKLZHSR1EHP4ERP6F7.GS1 also have incomplete conversion but no ORA-00905,we only have codepage 8400 and Non-unicode but why the log mention 4103 it's a Unicode code page,thanks a lot!
SHDUPGIMP1.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKLZHSR1EHP4ERP6F8.GS1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
1 ETP111 exit code : "8"
SAPKLZHSR1EHP4ERP6F8.GS1
4 ETW000 22 entries for RSMPTEXTS~ imported (SAPLMCB2 1*).
4 ETW000 1 entry for TLIBT~ updated (1MCB2).
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN %) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN %) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN %) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN ) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN ) deleted.
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN '
4 ETW000 0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN ) deleted.
4 ETW000 [ dev trc,00000] Wed Sep 7 10:41:04 2011 815387003 1338.120210
4 ETW000 [ dev trc,00000] OCIStmtExecute() failed with -1=OCI_ERROR 10 1338.120220
4 ETW000 [ dev trc,00000] SQL error 905: 6 1338.120226
4 ETW000 [ dbsloci.,00000] *** ERROR => Error 905 in stmt_fetch() from oci_execute_stmt(), orpc=0
4 ETW000 12 1338.120238
4 ETW000 [ dbsloci.,00000] *** ERROR => ORA-905 occurred when executing SQL stmt (parse error offset=110)
4 ETW000 9 1338.120247
4 ETW000 [ dev trc,00000] sc_p=0x140f618,no=67,idc_p=(nil),con=0,act=1,slen=149,smax=256,#vars=4,stmt=0x1783c10,table=
4 ETW000 17 1338.120264
4 ETW000 [ dev trc,00000] SELECT ID,OBJECT,LANGU,TYP,VERSION FROM "DOKIL~" WHERE (LANGU IN ( :A0 )) AND ID = :A1 AND OBJECT BE\
4 ETW000 9 1338.120273
4 ETW000 [ dev trc,00000] TWEEN :A2 ANALYSE#_DURCHF#REN % :A3 #?; 5 1338.120278
4 ETW000 [ dev trc,00000] sc_p=0x140f618,no=67,idc_p=(nil),con=0,act=1,slen=149,smax=256,#vars=4,stmt=0x1783c10,table=
4 ETW000 11 1338.120289
4 ETW000 [ dev trc,00000] Dumping DBSL stmt. cache: 5 1338.120294
4 ETW000 [ dev trc,00000] prep=0,lit=0,nsql=1,lobret=0,xop=1,dbcnt=0,upsh=(nil),stmtp=0x1784758,rtc=0
4 ETW000 29 1338.120323
4 ETW000 [ dev trc,00000] IN : cols=4,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=4294967295,rsize=28,vmax=32,bound=1,iobuf_p=0x1493510,vda_p=0x1784db0
4 ETW000 10 1338.120333
4 ETW000 [ dev trc,00000] lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0 6 1338.120339
4 ETW000 [ dev trc,00000] SELECT ID,OBJECT,LANGU,TYP,VERSION FROM "DOKIL~" WHERE (LANGU IN ( :A0 )) AND ID = :A1 AND OBJECT BE\
4 ETW000 7 1338.120346
4 ETW000 [ dev trc,00000] TWEEN :A2 ANALYSE#_DURCHF#REN % :A3 #?; 5 1338.120351
4 ETW000 [ dbds ,00596] ***LOG BY2=>sql error 905 performing FET [dbds#2 @ 596]
4 ETW000 14 1338.120365
4 ETW000 [ dbds ,00596] ***LOG BY0=>ORA-00905: missing keyword [dbds#2 @ 596] 6 1338.120371
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
4 ETW000 0 entries from FUNCT~ (1MCB_GRAPHIC_DAILY %) deleted.
4 ETW000 0 entries from FUNCT~ (%MCB_GRAPHIC_DAILY %) deleted.
4 ETW000 0 entries from TFTIT~ (1MCB_GRAPHIC_DAILY ) deleted.
4 ETW000 0 entries from TFTIT~ (%MCB_GRAPHIC_DAILY ) deleted.
SAPKLZHSR1EHP4ERP6F7.GS1
4 ETW000 1 entry for LDBNT~ imported (1FTI_TR_PL_CF *).
4 ETW000 0 d / 1 i / 0 u / 0 = 0% ucf LDBT~
4 ETW000 1 entry for LDBT~ imported (1FTI_TR_PL_CF).
4 ETW000 1 entry for TRDIRT~ inserted (SAPDBFTI_TR_POSITIONS 1*).
3WETW000 some text was mutilated during conversion from unicode to ascii in language '1'. This is the result: 'SP_JOTC ###############'
3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '530050005f004a004f005400430020002000200020002000200020002000200020003a571659a44e13664d881f75a74ec1542000200020002000200020002000' -> 'SP_JOTC ###############'
4 ETW000 REPOT1SAPDBFTI_TR_POSITIONS A replaced.
4 ETW000 0 entries from D020T~ (SAPDBFTI_TR_POSITIONS %) deleted.
4 ETW000 0 entries from D021T~ (SAPDBFTI_TR_POSITIONS %) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSFXXX 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSNXXX 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSN001 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSSEL 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSSXXX 1%) deleted.
4 ETW000 0 entries from TRDIRT~ (DBFTI_TR_POSITIONSTOP 1%) deleted.
SAPup.ECO
Phase SHADOW_IMPORT_UPG1:
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 2865 at 20110907101845
ENV: DIR_LIBRARY=/usr/sap/upgrade/upg_dir/abap/exenew
ENV: LD_LIBRARY_PATH=/usr/sap/upgrade/upg_dir/abap/exenew:/usr/sap/upgrade/upg_dir/jvm/jre/lib/amd64/server:/usr/sap/upgrade/upg_dir/jvm/jre/lib/amd64:/usr/sap/upgrade/upg_dir/jvm/jre/../lib/amd64:/usr/sap/GS1/SYS/exe/run:/oracle/GS1/102_64/lib
ENV: NLS_LANG=AMERICAN_AMERICA.WE8DEC
ENV: ORACLE_BASE=/oracle
ENV: ORACLE_HOME=/oracle/GS1/102_64
ENV: ORACLE_PSRV=GS1
ENV: ORACLE_SID=GS1
ENV: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
ENV: PATH=/usr/sap/upgrade/upg_dir/abap/exenew:/oracle/GS1/102_64/bin:.:/home/gs1adm:/usr/sap/GS1/SYS/exe/run:/opt/gcc295/bin:/opt/gnome/bin:/usr/games:/usr/bin/X11:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/global_lx/bin:/usr/global/bin
ENV: SAPSYSTEMNAME=GS1
ENV: auth_shadow_upgrade=0
ENV: dbms_type=ORA
ENV: dbs_ora_schema=SAPDAT
ENV: dbs_ora_tnsname=GS1
EXECUTING /usr/sap/upgrade/upg_dir/abap/exenew/tp (/usr/sap/upgrade/upg_dir/abap/exenew/tp) pf=/usr/sap/upgrade/upg_dir/abap/bin/SHDUPGIMP1.TPP put GS1
This is /usr/sap/upgrade/upg_dir/abap/exenew/tp version 376.03.38 (release 701)
This is /usr/sap/upgrade/upg_dir/abap/exenew/R3trans version 6.14 (release 701 - 03.06.11 - 17:57:00).
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
2EETW000 SQL error 905 occured: ORA-00905: missing keyword
/usr/sap/upgrade/upg_dir/abap/exenew/R3trans finished (0008).
ERROR: stopping on error 8 during SHADOW IMPORT
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
stopping on error 8 during SHADOW IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 8
meaning:
A tool used by tp produced errors
Process with ID 2865 terminated with status 8
B.R
Lance.
Edited by: Yen on Sep 7, 2011 8:11 AMHello,
Following upg master was used -
51036889_1 BS 7 SR1 Upgrade Master 1/2
51036889_2 BS 7 SR1 Upgrade Master 2/2
And the kernel dvd used was NUC -
51036767_4 BS 7 SR1 Kernel 7.01
After successful upgrade to ecc6 EhP4, Unicode conversion was done later with UC kernel DVD (during IMPORT)
Thanks -
I am trying to clear data in the forecast scenario in development under Data Tasks but got this error. How should I get around this issue please?
proxy error
the proxy server received an invalid response from upstream server.
the proxy server could not handle the request POST/HFM/Data/DBManagementClearData.asp
Reason:Error reading from remote server.
please help me out.
thanks in advance.
regards
anilHi Venkatrao,
I am also facing same problem ,did you get solution ? Please help me
Thanks and regards,
Shivanand
Maybe you are looking for
-
Editing sales doc in R/3 that was created in CRM
Hi all CRM Gurus I am in the process of cofiguring the CRM system to enable the creation of sales documents. All is working fine, I can create the sales doc is CRM, this them replicates through to R/3 without any errors, but I cant edit the sales doc
-
Installing windows 7 on mac book pro late 2013
Installing Windows 7 on Mac Book Pro Late 2013 Background Mac Book Pro Late 2013 uses a USB 3.0 hub for the external ports, the keyboard and mouse devices. Windows 7 does not have the drivers to support USB 3.0 ports so these must be integrated into
-
An error occurs when I try to raise the Listener (call RED_240), the error is the following one: LSNRCTL> start RED_240 Starting /oracle/app/oracle_10g/OraHome_1/bin/tnslsnr: please wait... TNSLSNR for Linux IA64: Version 10.1.0.2.0 - Production Syst
-
Trouble installing Solaris 8 from cd.
Hi, I am trying to install solaris 8 from cd using remote connection. first the pc got hung and now it gave this error message. WARNING: /pci@1f,4000/scsi@2/sd@6,0 (sd21): Error for Command: read(10) Error Level: Retryable Requested Block: 69440 Erro
-
One of the key of my keyboard has got a bit tough to type. Not a big issue, but it is rather annoying. I suppose that the problem is cause by something has got under the key and removing that alien object would resolve the issue. Does anybody know, h