Error While Creating Technical System for SNC

Hi There,
I am trying to create technical system for SNC in SLD, I am not able to seee SNC as a s/w component/product in the list.
when I checked the list of components in SLD, I found SNC is there under product "SCMSNC" but this product is not in the list of products.
Please help me how I can get "SCMSNC" product in the product list.
Thanks,
Nishant

Can you please explain it little bit clearly?
I think you first create product, then SWC and then try to create Technical system.
While you will create the Technical system, in the last step it will ask you for installed products.
There you can specify ur product.
Thanks,
Hetal

Similar Messages

Error while creating Technical System

Hi
i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
When i press next, It is throwing this error. Do anyone have any idea about this.
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
    at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
    at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
    at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    ... 27 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Sat Oct 14 19:38:14 GMT+05:30 2006
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
Web Dynpro Code Generation Infos
sap.com/tcsldwd~main
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~landscape
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/tcsldwd~businesssystem
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~technicalsystem
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
sap.com/tcsldwd~softwarecatalog
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~namereservation
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
Detailed Error Information
Detailed Exception Chain
java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
     at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
     at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
     at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks in Advance
Vijay Raheja

HI Michal Krawczyk,
Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
It is asking me for :
-URL of target SLD system, e.g. http://host:port/
-User
-Password.
What should i give here. WHat will be port for R/3 system to which i want to connect.
Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
Thanks,
Vijay Raheja

RFC Error While Creating Technical System in SLD As Web AS ABAP

Hi Experts,
I was Posted This Thread in Most of the Modules like ABAP, Exchange Infrastructure.
But there is No Such Right Answers . So Finally I Got Idea to Post it in SAP NetWeaver Administrator Module.
For Creating a TS for Web AS ABAP For R/3 in SLD Automatically I Followed these Steps.
Log on to R/3 System
1) Go to SLDAPICUST TC
2)Entered Host name of the XI System ,Port, User As PIAPPLUSER, and Master PWD.
And Checked Primary Check Box.Saved
3) Goto RZ70 TC
4) Entered Host name And Gateway Service of XI System.And Activated
5) Clicked on Start Data Collection.
Here I Got the Error As "RFC call failed : Error opening an RFC connection"
Then
1) If I Executed SLD_NUC in SM59 With SAP XI Details Means It's giving Error Like as Follows "TheGetT1002 : error ( Msg - 10 not found )"
If I Executed SLD_NUC in SM59 With SAP R/3 Details Means It's giving Error Like as Follows "program SLD_NUC not registered"
Please let me Know the Solution
Points will be Given If the Problem Is Solved
Regards
Khanna

Hi Tanuj,
When I Executed SLDCHECK in R/3 System it's Giving The Following Wrror.
Exchange Infrastructure: Test LCR Connection
Properties of RFC destination SAPSLDAPI
RFC host: %%RFCSERVER%%
program id: SAPSLDAPI_NONUNICODE
gateway host: SAPPLMIDES
gateway service: sapgw00
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
Error opening an RFC connection.
Summary: Connection to SLD does not work
=> Check SLD function and configurations
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host: %%RFCSERVER%%
program id: LCRSAPRFC_NONUNICODE
gateway host: sapplmides
gateway service: sapgw00
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
Error opening an RFC connection.
Please Help me....
Regards
Khanna

Error while creating a task for creating an generic task /app/dac/CustomSQ

Hi ,
I have created a sql file in DAC server /app/dac/CustomSQLs/ ,just to fire an update sql in database
In DAC task tab i have created a task with the following:
Command for incremental load :/app/dac/CustomSQLs/DBNameBeforeLoad.sql
Primary source :flatfileconnection
target source:DBCONNECTION_OLAP
Execution type:SQL FILE
Task phase:GENERAL
I created subject area and assembled ,then created a Execution plan.
When i try to execute this EP ,it shows the following error in DAC log:
ANOMALY INFO::: Error while creating a task for creating an generic task /app/dac/CustomSQLs/DBNameBeforeLoad.sql
MESSAGE:::/app/dac/CustomSQLs/DBNameBeforeLoad.sql - invalide template name!
EXCEPTION CLASS::: com.siebel.analytics.etl.etltask.TaskInitializationException
com.siebel.analytics.etl.etltask.SQLFileTask.doInit(SQLFileTask.java:69)
com.siebel.analytics.etl.etltask.GenericTaskImpl.init(GenericTaskImpl.java:194)
Does my above configuration is correct ..?

verify the following settings:
1. mapping of ECC plant and storage location and logical system number with the appropriate availability group code since this links the stock types in EWM to ECC org elements (SPRO -> EWM -> Interfaces -> ERP Integration -> Goods movement)
2. ensure the availability group configuration is correct (SPRO -> EWM -> GR Process -> Configure availability group for putaway) - check all applicable nodes in this configuration since the availability group code is assigned in the pertinent storage types

Portal Runtime Error while creating new system in portal content

Hi
Can anyone solve my problem, i am geting error while creating new system in p ortal content
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file

Hi,
Check this link for creating system object
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun

RUNTIME ERROR WHILE CREATING NEW SYSTEM IN EP6

Hi
Can anyone solve my problem, i am geting error while creating new system PORTAL FOR to connect biw 3.5 system
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file
thanks in advance
Rock

hi,
check the log file and let me the the error.
manish

CIM_ERR_ALREADY_EXISTS: Error while creating Business System

Hi,
I am getting following error while creating Business System in SLD, the Technical System is already created from RZ70 transaction in the IDES system
Error Creating business system: CIM_ERR_ALREADY_EXISTS: Instance already exists://inbbssun01/sld/active:SAP_LogicalALESystem.CreattionClassName="SAP_LogicalALESystem", Name = "LSIDES800.SystemName.800.SystemName.IDS.SystemNumber.0020224902.SystemHome.idesecc"
Thanks,
RP

Hi,
This error means that a business system with this name(or associated with this technical system) is already there in SLD.
You need to check that before you try creating it (might be someone else have created it before)
Updated
If you have created and deleted a business system and then trying to recreate one then you need to delete all the instance of it from Content Management (in SLD)
Regards
Suraj
Edited by: S.R.Suraj on Nov 9, 2009 12:34 AM

Regarding error in creating technical system of type WEB AS ABAP

while creating technical system of WEB AS ABAP i have few doubts
1) host name:(do we have to give sap system name or xi system name)
and while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER i.e xi3/sxi what ever it may be,so am facing very difficulty while creating communication channel and not able to select the integration engine under the ADAPTER ENGINE ,so please provide me suitable solution with screen shoits if possible ,it very urgent for me

pls check this
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
as per ur doubt
1. host name:; sap system (can find under system status info-->database of R/3)
2. SId is system status->database>name (3) characters
3.while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER--as fra as this info that is there when u follow the wizard of creating Business system , also did u select business system role as application system name then probly u can get the related server name ,make sure ur technical system is created well

Error while creating datasource userdsn for oracle 10g Errorcode (998)

while creating datasource userdsn for oracle 10g i am getting error "The setup routines for the oracle in OraDb10g_home1 odbc driver could not be loaded due to system error code 998" please give reply soon

Thanks for your reply , Steve.
I noticed that there is a default datasouce on the EM with the following parameters:
<data-source
 class="com.evermind.sql.DriverManagerDataSource"
 name="OracleDS"
 location="jdbc/OracleCoreDS"
 xa-location="jdbc/xa/OracleXADS"
 ejb-location="jdbc/OracleDS"
 connection-driver="oracle.jdbc.driver.OracleDriver"
 username="scott"
 password="->pwForScott"
 url="jdbc:oracle:thin:@localhost:1521:oracle"
 inactivity-timeout="30"
 />
The location and xa-location attributes that I use for my "test" data source are the same as the default one. So, could this be the issue?
What should be the values for location and xa-location attributes from my "test" data source?
Any help will be greatly appreciated.
Thanks,
Shyam

Error while creating SOURCE SYSTEM

Hi All,
I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
Error in source system RXX_100
Message no. RSAR502
Diagnosis
With Remote Function Call to system RXX_100 error Screen output without connection to user. ccurred.
Procedure
Remove the cause of the error.
Kindly provide me suggestions and DOCS related to the same.
Suitable points will be awarded for replies.
Expecting your kind reply,
Vineeth

Hi ,
In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
973555 - System must be open for creating/connecting source systems
Thanks,
Shanaka

Error while creating logical port for Consumer Proxy in SOAMANGER

Hi,
While creating logical port for my consumer proxy in SOAMANGER, I am getting the error shown below
SRT Framework exception: HTTP: Current user does not have the required authorization to access the HTTP destination
I have searched in the forums but none of the answers helped me.
I have specifed my PI user ID and password and the user has the followwing roles assigned to it.
SAP_BC_WEBSERVICE_SERVICE_USER
SAP_BC_WEBSERVICE_ADMIN_TEC
SAP_BC_WEBSERVICE_CONSUMER
SAP_BC_WEBSERVICE_ADMIN
Current user in the error message refers to the PI user that i have specified or the user with which i have logged in the backend ABAP system?
Please help me reslove this issue.
Thanks and regards
Sreehari Nambiar

Hi,
Please add the following roles as well.
SAP_BC_WEBSERVICE_ADMIN_BIZ
SAP_BC_WEBSERVICE_DEBUGGER
SAP_BC_WEBSERVICE_OBSERVER
Also make sure that you are doing the role comparison after adding all SAP* roles in your profile.
Let me know if this works?
Thanks,
Sridhar

Error while creating MDM system on Portal

Hi All,
I am trying to create MDM system in EP. MDM is 5.5 SP06. EP is 7.0 . We have upgraded the MDM sca files on Portal from SP05 to SP06.
While creating the system , after entering the server, we are getting the following error.
com.sap.mdm.internal.protocol.manual.ServerException: File failed a crc check
Please help
Regards
Shilpa

Hi Shilpa,
If this is your MDM build version 5.5.63.80 SP06. It means you are using MDM 5.5 SP06 Patch3 hotfix 80.
You need to find the Sca file of compatible with this version.
So they should be
- MDMJAVAAPI06_03.sca
- BPMDMAPPLN06_03.sca
- BPMDMTECHN06_03.sca
The hotfix number can slightly differ but the Support pack and patch number must match.
You need to follow this link:
http://service.sap.com/swdc
(download MDM support packages) Download>support packages and patches>entry by application
group>sap netweaver>sap mdm>sap mdm 5.5>Entry by component>Portal content
Then select which MDM portal content you want and check what is the version of those available sca files.
based on the availablity of the sca files you need to upgrade/downgrade or server.
As compatibility between the server version and sca files is a must for proper functioning.If its not possible to change your mdm server version then you can ask your Basis team to hunt the matching sca files for you.
Hope It Helped
Thanks & Regards
Simona Pinto

Error while Creating a formula for field AZNOR (T-Code : OP17)

Dear Experts,
i am facing a problem in Transaction OP17 while creating a formula for field AZNOR ( No of indivual capacity in work center) in work center (T-Code : CR02) .
It shows the error
The data object "F" has no component called "AZNOR''..
Please let me know the solution..
Thanks & Regards
Birendra Kumar

Hi,
I have the same problem.
Could You tell me witch is the correct origin?
Thanks a lot!
Bye
Laura

Getting the following error while creating the model for webdynpro app.

Plugin Name: Web Dynpro Model Editor Services
Plugin ID : com.sap.ide.webdynpro.service.modeleditor
Class :ap.ide.webdynpro.modeleditor.wizards.model. creation.ModelDialog
Method : nextPressed
Exception : org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError)
This is the error i am getting while creating the model for the webdynpro application. Can some one help ?
Thanks & Regards
Lalith

hi
This error occurs mainly due to the reason that particular plugin is not there in the NWDS.
So please try to reinstall the NWDS or try tracing out whether that particular plugin is there or not.
Thank,
kris

Error while creating a system object for R3 in portal

Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

I created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj

Error While Creating Technical System for SNC

Similar Messages

Maybe you are looking for