Creating metadata for AWs created programatically (11.2)
Hi guys
The aim is to create Analytic Workspace within certain tablespace and with certain number of physical partitions.
I tried following ways to create the AW:
1st way:
begin
dbms_aw.aw_create(name => 'MIS_LT', tbspace => 'AW_MIS_LT_DI', partnum => 15);
end;
2nd way:
begin
dbms_aw.execute('AW CREATE MIS_LT PARTITIONS 15 TABLESPACE AW_MIS_LT_DI');
end;
After executing code from either 1st way or 2nd way - I got the result that I could see that new AW (MIS_LT) when executing query:
select * from all_aws;
Unfortunaltely I could not see the newly created AW in AWM. I suppose it's somehow related to missing metadata (standard form metadata ?).
When executing following code:
begin
dbms_cube.import_xml( to_clob(
'<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<AW
Name="MIS_LT"
Version="11.2">
</AW>
</Metadata>'));
end;
PL/SQL block were executed successfully, but still MIS_LT was not visible in AWM (even after relogging):
When trying to execute following code (like above -but one simple dimension was added):
begin
dbms_cube.import_xml( to_clob(
'<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<StandardDimension
Name="CURRENCY_DIM_LT"
ETViewName="V_CURRENCY_DIM_LT"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETMemberTypeColumnName="MEMBER_TYPE"
ETDimensionOrderColumnName="DIM_ORDER"
ETHierarchyOrderColumnName="HIER_ORDER"
DefaultHierarchy="MAIN_HIERARCHY"
ValueDescriptionAttribute="LONG_DESCRIPTION">
<Hierarchy>
<LevelHierarchy
IsSkipLevel="False"
IsRagged="False"
Name="MAIN_HIERARCHY"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="V_CURRENCY_DIM_MAIN_HIERARC_LT">
<Description
Type="LongDescription"
Language="ENGLISH"
Value="MAIN HIERARCHY">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="MAIN HIERARCHY">
</Description>
<Description
Type="Description"
Language="ENGLISH"
Value="MAIN HIERARCHY">
</Description>
<HierarchyLevel
DimensionLevel="CURRENCY">
<HierarchyLevelMap
KeyExpression="MIS.MIS_CURRENCY_DIM.MCD_ID_CHAR"
Query="MIS.MIS_CURRENCY_DIM"
WhereClause="MIS.MIS_CURRENCY_DIM.MCD_CUNIT_ID = 2">
<AttributeMap
Name="LONG_DESCRIPTION"
Attribute="LONG_DESCRIPTION"
Expression="MIS.MIS_CURRENCY_DIM.MCD_CURRENCY_LEV_DESC">
</AttributeMap>
<AttributeMap
Name="CURRENCY_LONG_DESCRIPTION"
Attribute="CURRENCY_LONG_DESCRIPTION"
Expression="MIS.MIS_CURRENCY_DIM.MCD_CURRENCY_LEV_DESC">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
</LevelHierarchy>
</Hierarchy>
<DimensionLevel
Name="CURRENCY"
ETKeyColumnName="CURRENCY">
<Description
Type="LongDescription"
Language="ENGLISH"
Value="CURRENCY">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="CURRENCY">
</Description>
<Description
Type="Description"
Language="ENGLISH"
Value="CURRENCY">
</Description>
<VisibleAttribute
Name="CURRENCY_LONG_DESCRIPTION"/>
</DimensionLevel>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(100)"
AllowAutoDataTypeChange="False"
ETAttributeColumnName="LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
IsLevelUnique="False"
Name="LONG_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="Description"
Language="ENGLISH"
Value="Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(100)"
AllowAutoDataTypeChange="False"
ETAttributeColumnName="CURRENCY_LONG_DESCRIPTIO"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
IsLevelUnique="False"
Name="CURRENCY_LONG_DESCRIPTION">
<Description
Type="LongDescription"
Language="ENGLISH"
Value="CURRENCY Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="CURRENCY Long Description">
</Description>
<Description
Type="Description"
Language="ENGLISH"
Value="CURRENCY Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Organization>
<AWPrimaryDimensionOrganization
MVOption="NONE"
HierarchyConsistencyRule="CONSISTENT"
AddUniqueKeyPrefix="False"
AW="MIS_LT">
<MVCreationOptions
RefreshOn="DEMAND"
RefreshType="COMPLETE"
UsingConstraintsClause="TRUSTED">
</MVCreationOptions>
<AttributeOrganization
CreateIndex="False"
Attribute="LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="CURRENCY_LONG_DESCRIPTION">
</AttributeOrganization>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
</AWPrimaryDimensionOrganization>
</Organization>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="CURRENCY DIM">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="CURRENCY DIM">
</Description>
<Description
Type="Description"
Language="ENGLISH"
Value="CURRENCY DIM">
</Description>
</StandardDimension>
<AW
Name="MIS_LT"
Version="11.2">
</AW>
</Metadata>'));
end;
I got following errors:
ORA-34492 Analytic Workspace object MIS_REPORTS.MIS_LT!___AW_ALL_OBJECTS doesn't exists.
XOQ-01600 OLAP DML error when executing DML"SYS.AWXML!R11_MANANGE_DIMENSION"
All in all it's got to be related to some missing metadata. Is there any way to create that metadata from PL/SQL wihout using AWM?
Thanks in advance for any help.
Best Regards
Piotr
You are correct in suspecting missing "standard form" metadata.
The first two of you methods, "dbms_aw.aw_create" and "dbms_aw.execute" will both create an empty AW with no standard form metadata. Such an AW is fully supported and can be accessed through OLAP DML, but it is not visible in AWM and does not show up in the various USER_CUBE_* dictionary views.
The third method, dbms_cube.import_xml, should have created a valid "standard form" AW that was visible in AWM.
The error you got from your final method is easier to explain.
>
ORA-34492 Analytic Workspace object MIS_REPORTS.MIS_LT!___AW_ALL_OBJECTS doesn't exists.
XOQ-01600 OLAP DML error when executing DML"SYS.AWXML!R11_MANANGE_DIMENSION"
>
The problem is that the import_xml procedure can create a new "standard form" AW or modify an existing "standard form" AW. But it will not convert an existing non-"standard form" AW into a "standard form" AW. I suspect the same thing happened in your third method, but no error was reported.
The solution is to delete the empty AW by hand and then run your third method again.
begin
dbms_aw.execute('AW DELETE MIS_LT PARTITIONS');
dbms_cube.import_xml( to_clob(
'<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<AW
Name="MIS_LT"
Version="11.2">
</AW>
</Metadata>'));
end;
/
Similar Messages
-
Can't create blogs for users created in LDAP directory
I have an LDAP directory set up on an Open Directory Master and use it for user management. I want to allow users to create blogs off of the main web site. However, when I try to create a blog, it won't authenticate to any of the LDAP users, only the local user (of which the administrator account for the server is the only one).
LDAP directory users can access their personal websites, though (http://mydomain/~user).
Does anyone have any ideas how I can get the blog portion of the web site to allow my LDAP users to create a blog?
Thanks.Sorry, I should have mentioned I am using Leopard Server (10.5.5).
-
Creating MetaData using workbench
Hi all,
I'm trying to create metadata for some of my files, using the workbench,
without success. When I followed the instructions for the sample classes,
I can load the classes and manipulate them.
However, when I try to do the same with my classes, I can see one of two
things:
1. When choosing to create a class level metadata file, I can choose the
class file from the explorer like window, but the class name does not
get placed on the 'class name to add' edit box in the 'Choose classes'
dialog.
2. When trying to mount a jdo file, I get an exception (SAXException)
and a message that states that a class (the first listed in the file)
cannot be instantiated.
the workbench is configured with class paths that include the correct path,
i.e. my classes are in <classes>\company\product\model\beans and this path
is listed in the classpath config dialog. The workbench was started in
<classes>. The classes are of course compiled. the jdk is on the path
(JDK 5)
When using ant to perform the mapping (that I want to use workbench for)
it all works well.
What gives? What am I doing wrong and how can I get this to work?
Bonny
What am I missingHi all,
I'm trying to create metadata for some of my files,
using the workbench,
without success. When I followed the instructions for
the sample classes,
I can load the classes and manipulate them.
However, when I try to do the same with my classes, I
can see one of two
things:
1. When choosing to create a class level metadata
file, I can choose the
class file from the explorer like window, but the
the class name does not
get placed on the 'class name to add' edit box in
in the 'Choose classes'
dialog.
2. When trying to mount a jdo file, I get an
exception (SAXException)
and a message that states that a class (the first
rst listed in the file)
cannot be instantiated.
the workbench is configured with class paths that
include the correct path,
i.e. my classes are in
<classes>\company\product\model\beans and this path
is listed in the classpath config dialog. The
workbench was started in
<classes>. The classes are of course compiled. the
jdk is on the path
(JDK 5)
When using ant to perform the mapping (that I want to
use workbench for)
it all works well.
What gives? What am I doing wrong and how can I get
this to work?
Bonny
What am I missing
Ok, so I've found in another post that you need to explicitly specify the path to the compiled classes in the classpath arg when starting the kodo workbench. Previously however, I had only specified the path to the root of my project (the directory with bin & src as children) as the value of the "directory" argument. I'm assuming that the previous src & bin directories that were showing up (they still show now ...) are because of this setting. Although I can successfully choose a class to create metadata for, this still doesn't seem like things are configured correctly. More insight would be helpful!
Thanks,
P$ -
How to create Stubs for object
Hai all,
I created a object which extends javax.rmi.remote. i want create stubs for this object programatically. is it possible? (like Compiler.compile()).
Thanks
with regards
SreeIf you use Java 5, you can avoid the need to use stubs at all. Would that be a suitable solution?
Otherwise you can invoke sun.rmi.rmic.Main declared in tools.jar. E.g.
java -classpath %JAVA_HOME%\lib\tools.jar sun.rmi.rmic.Main -
Hi
I am a new comer to the JDO and KODO world.
My question is about the MetaData. So far, it seems to me that the only way
to create MetaData for a class is by coding it manually. I haven't found any
utility for that mentioned in Kodo documentation.
Is that really so? It is pretty surprising if it there is no automated tool
to create a generic metadata.
If this is indeed a manual process, I would like to know the experience of
people in this group; is this just a minor annoyance or significant work.
Thanks
ZafarThanks for the pointer; this is very useful. Will surely use it when we move
to actual development.
Zafar
"Tom Davies" <[email protected]> wrote in message
news:alrg5q$p2a$[email protected]..
Zafar Kazmi wrote:
Hi
I am a new comer to the JDO and KODO world.
My question is about the MetaData. So far, it seems to me that the only
way
to create MetaData for a class is by coding it manually. I haven't foundany
utility for that mentioned in Kodo documentation.
Is that really so? It is pretty surprising if it there is no automatedtool
to create a generic metadata.Have a look at Xdoclet, in section 8.3 of the Kodo manual.
If this is indeed a manual process, I would like to know the experience
of
people in this group; is this just a minor annoyance or significantwork.
>
If you are not mapping to an existing schema then the metadata is
simple, and even Xdoclet is overkill (IMHO).
Tom -
Hi,
I need little help, where do I create metadata for XML forms? Can I access them from form builder (EP7)?
Thanks a lot,
Jai
Message was edited by: Jai PaulHi,
You should read about:
Advanced concepts in Metadata properties in km.pdf you can find in:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/de31ec90-0201-0010-be95-f501d25027a8
How to create xml form.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee639033-0801-0010-0883-b2c76b18583a
Properties of XML Documents
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/9d1f39a27d0e4f8a69c891dc4a4a05/frameset.htm
Predefined Properties
http://help.sap.com/saphelp_nw2004s/helpdata/en/1a/9a4a3b80f2ec40aa7456bc87a94259/frameset.htm
Repository Services
http://help.sap.com/saphelp_nw2004s/helpdata/en/69/d96b86a84611d5993600508b6b8b11/frameset.htm
Patricio. -
IS IT POSSIBLE TO CREATE SLICER BASED ON CREATED SET?
HI ALL
I was wondering is it possible to create slicer for set created based on column items?
Data table looks like:
TABLE 1.
PRODUCER1 PRODUCER2 PRODUCER3 ....
PRODUCER50
PRODUCT 1
PRODUCT 2
SALES VALUES
PRODUCT N
I created set based on column items and called it PRODUCERS
What I need is to create slicer for PRODUCERS.
The problem is powerpivot does not give a possibility to create slicer! I can use PRODUCERS in my powerpivot table, but I can not create slicer!
I was wondering why? And is there any workaround?
Thanks for potential replies.Model structure is simple and looks like below.
Table 1. with main data.
Table 2. was created to build a slicer for producers.
Those tables are disconected ones.
TABLE 1.
PRODUCER1 PRODUCER2 PRODUCER3 .... PRODUCER50
PRODUCT 1
PRODUCT 2
SALES VALUES
PRODUCT N
Table2.
PRODUCERS
producer 1
producer 2
producer 50
To remind I need to be able to slice sales data by Producers.
What I am trying to do now is to:
- create slicer for Table 2.
- use this slicer to filter Table 1. ( I need a good measure to do this)
But I am not sure this workaround is possible. The measure I wrote returns error.
MEASURE:=IF(VALUES(Table 2[PRODUCERS])="producer 1",SUM(TABLE 1.[PRODUCER1],
IF(VALUES(Table 2[PRODUCERS])="producer 2",SUM(TABLE 1.[PRODUCER2],
IF(VALUES(Table 2[PRODUCERS])="producer 50",SUM(TABLE 1.[PRODUCER50], "")))
I could not find any similar topic to find a solution.
Did anyone meet similar problem? -
Unable to create Metadata connection for Dictionary Provider
Hi,
I am getting the following error while I try to run a Web Dynpro Application;
The initial exception that caused the request to fail, was:
com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
... 37 more
The JCo Connections are tested and pinged, they work fine.
Can anyone please tell what the error could be?The details exception list is as below:
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.dow.dc.model.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 34 more -
RFC Error: Unable to create Metadata connection for Dictionary Provider
I configured two RFC ('WD_XXX__MODELDATA_DEST and WD_XXX_RFC_METADATA_DEST). I tested it and it shown green light.
When I run my application that coonnect to CRM using RFC, I got the following errors:
<i>com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.xxx.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_ICEBERG_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:443)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:381)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:410)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:311)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:347)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
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.doGet(DispatcherServlet.java:40)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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)
Caused by: com.sap.dictionary.runtime.DdException: 'WD_XXX_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 49 more</i>
I understand that I need to configured the Metadata Dictionary type for the RFC. For this, I need to configure the Message Server properties (for load balancing).
But my Basis guy told me that CRM is an application server, so we only can configured with application server properties. Is this true? (I really doubt it) That is no Message Server connection to CRM system now.
If it is true, how can I create a RFC connection to CRM system?
Thanks for help.
KentHi KC,
Try the following links, they may help you.
http://help.sap.com/saphelp_nw04s/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
JCO connection
Using the SAP Enterprise Connector for generating BAPI Proxy Classes
points if useful
Thanks
Suresh -
Create clip spanning metadata for NanoFlash media?
The Convergent Design NanoFlash device records great looking 4:2:2
.MXF files to FAT32 CF cards without any associated metadata for linking
spanned clips (cut at the 4Mb limit) into a single clip on import.
Is there any sort of .xml (or other) that can be created and added to
the clip directory that will force Premiere to link spanned clips together?
NanoFlash Media Properties 56365001.MXF:
Type: XDCAM-HD 422 Movie
File Size: 3.5 GB
Image Size: 1920 x 1080
Pixel Depth: 32
Frame Rate: 29.97
Source Audio Format: 48000 Hz - 24 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00;03;31;06
Average Data Rate: 17.0 MB / second
Pixel Aspect Ratio: 1.0How about an .MXF re-wrapping script that
will bundle multiple spanned clips into one? -
Not able to create entries for ALBTCMON (SCM 4.10)
I am trying to create entries for monitoring jobs that start with "SAP_*" and I am trying to add entry into ALBTCMON table. But system is trowing the message as below.
===============================================================
Create data processing function module
Message no. SV023
Diagnosis
You have called the function for editing view contents. The function modules needed for the maintenance functionality of this view are not available in the system.
Procedure
The data processing function module must be re-generated.
Contact the system administration.
===============================================================
Can somebody tell whats wrong. I am working in SCM 4.10.
Regards,
GiridharaMake sure the xWebsites metadata field has the siteId of your site. And as Srinath said, make sure it's "Released"; which can take a moment or two.
-
Creating View for a table with parent child relation in table
I need help creating a view. It is on a base table which is a metadata table.It is usinf parent child relationship. There are four types of objects, Job, Workflow, Dataflow and ABAP dataflow. Job would be the root parent everytime. I have saved all the jobs
of the project in another table TABLE_JOB with column name JOB_NAME. Query should iteratively start from the job and search all the child nodes and then display all child with the job name. Attached are the images of base table data and expected view data
and also the excel sheet with data.Picture 1 is the sample data in base table. Picture 2 is data in the view.
Base Table
PARENT_OBJ
PAREBT_OBJ_TYPE
DESCEN_OBJ
DESCEN_OBJ_TYPE
JOB_A
JOB
WF_1
WORKFLOW
JOB_A
JOB
DF_1
DATAFLOW
WF_1
WORKFLOW
DF_2
DATAFLOW
DF_1
DATAFLOW
ADF_1
ADF
JOB_B
JOB
WF_2
WORKFLOW
JOB_B
JOB
WF_3
WORKFLOW
WF_2
WORKFLOW
DF_3
DATAFLOW
WF_3
WORKFLOW
DF_4
DATAFLOW
DF_4
DATAFLOW
ADF_2
ADF
View
Job_Name
Flow_Name
Flow_Type
Job_A
WF_1
WORKFLOW
Job_A
DF_1
DATAFLOW
Job_A
DF_2
DATAFLOW
Job_A
ADF_1
ADF
Job_B
WF_2
WORKFLOW
Job_B
WF_3
WORKFLOW
Job_B
DF_3
DATAFLOW
Job_B
DF_4
DATAFLOW
Job_B
ADF_2
ADF
I implemented the same in oracle using CONNECT_BY_ROOT and START WITH.
Regards,
MeghaI think what you need is recursive CTE
Consider your table below
create table basetable
(PARENT_OBJ varchar(10),
PAREBT_OBJ_TYPE varchar(10),
DESCEN_OBJ varchar(10),DESCEN_OBJ_TYPE varchar(10))
INSERT basetable(PARENT_OBJ,PAREBT_OBJ_TYPE,DESCEN_OBJ,DESCEN_OBJ_TYPE)
VALUES('JOB_A','JOB','WF_1','WORKFLOW'),
('JOB_A','JOB','DF_1','DATAFLOW'),
('WF_1','WORKFLOW','DF_2','DATAFLOW'),
('DF_1','DATAFLOW','ADF_1','ADF'),
('JOB_B','JOB','WF_2','WORKFLOW'),
('JOB_B','JOB','WF_3','WORKFLOW'),
('WF_2','WORKFLOW','DF_3','DATAFLOW'),
('WF_3','WORKFLOW','DF_4','DATAFLOW'),
('DF_4','DATAFLOW','ADF_2','ADF')
ie first create a UDF like below to get hierarchy recursively
CREATE FUNCTION GetHierarchy
@Object varchar(10)
RETURNS @RESULTS table
PARENT_OBJ varchar(10),
DESCEN_OBJ varchar(10),
DESCEN_OBJ_TYPE varchar(10)
AS
BEGIN
;With CTE
AS
SELECT PARENT_OBJ,DESCEN_OBJ,DESCEN_OBJ_TYPE
FROM basetable
WHERE PARENT_OBJ = @Object
UNION ALL
SELECT b.PARENT_OBJ,b.DESCEN_OBJ,b.DESCEN_OBJ_TYPE
FROM CTE c
JOIN basetable b
ON b.PARENT_OBJ = c.DESCEN_OBJ
INSERT @RESULTS
SELECT @Object,DESCEN_OBJ,DESCEN_OBJ_TYPE
FROM CTE
OPTION (MAXRECURSION 0)
RETURN
END
Then you can invoke it as below
SELECT * FROM dbo.GetHierarchy('JOB_A')
Now you need to use this for every parent obj (start obj) in view
for that create view as below
CREATE VIEW vw_Table
AS
SELECT f.*
FROM (SELECT DISTINCT PARENT_OBJ FROM basetable r
WHERE NOT EXISTS (SELECT 1
FROM basetable WHERE DESCEN_OBJ = r.PARENT_OBJ)
)b
CROSS APPLY dbo.GetHierarchy(b.PARENT_OBJ) f
GO
This will make sure it will give full hieraracy for each start object
Now just call view as below and see the output
SELECT * FROM vw_table
Output
PARENT_OBJ DESCEN_OBJ DESCEN_OBJ_TYPE
JOB_A WF_1 WORKFLOW
JOB_A DF_1 DATAFLOW
JOB_A ADF_1 ADF
JOB_A DF_2 DATAFLOW
JOB_B WF_2 WORKFLOW
JOB_B WF_3 WORKFLOW
JOB_B DF_4 DATAFLOW
JOB_B ADF_2 ADF
JOB_B DF_3 DATAFLOW
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs -
Problems with the "Date Created" Metadata in Adobe Bridge
Hi everyone.
I am currently working on an electronic photo library for our organization. Part of my mandate is to add a Date Created metadata on all the photos since it is very important to know when the photo was taken. Some photos were dated since 1980s. Since we do not have the digital version of the old photos, we end up scanning these and, in effect the date specified on the "Date Created" was the date it was scanned.
I have the date of some of the old photos when it was taken, but for some, I only have the month and the year (sometimes, just the year). Inventing a day and a month is not an option.
Is it possible to enter a month-year or just the year on the Date Created field under Metadata?
I appreciate your help.
Thanks,
.m.u.r.d.o.c.h.The problem is that dates are recorded in the file in different schemas. Bridge is displaying the XMP Date Created field which was likely derived from the original Exif date (probably DateTimeOriginal, but may be DateTimeDigitized). This will be the date recorded in the file by the scanner software at the time it was scanned.
The IPTC Date Created field is handled differently. It seems counterintuitive, but if you work in the news business you will know that news photographers often use the IPTC Date Created field more like a "date submitted" or "date scheduled" property, so that photos for a particular shoot which may have been captured over multiple days will sort together. Because of this, most image browsers will not update the XMP Date Created (or Date Taken) fields when the IPTC Core date is changed.
You can edit the original capture date in various programs, which should cause both the Exif and the XMP Date Created fields to be updated. Two that come to mind are Lightroom and BreezeBrowser Pro (for Windows). I've found that with certain images it is necessary to use both programs to get all the dates to line up. -
Problem while creating metadata files
I created metadata files to add styles to Photoshop Elements 8 (in Windows 7) and included them in the C:\Program Data\Adobe\Photoshop Elements\8.0\Photo Creations\layer styles folder. The first several worked great and successfully showed up in the Styles Palette. Later, when I was trying to add more styles I received a message in PSE 'Could not load styles because the file could not be found'. I closed PSE. Now every time I open Editor I receive this message and it locks up the program. The only way I can close PSE is through Task Manager.
Any suggestions on how to correct this?I put a copy of the third party styles in the Photoshop Elements Preset/styles folder and in the Photoshop Elements 8.0/Photo Creations/layer styles folder. From the Photo Creations/layer styles folder I selected an existing metadata file and copied it to my desktop. I changed the first part of the file name to the name of the new style (example: glitter 001.metadata). I then right clicked and opened with Notepad. When I found the name of the existing file I was using, I changed the name before the equation sign to the name of my new layer style with no spaces between words. Then I changed the name after the equation sign to the name of the new style with spaces between words (glitter001=glitter 001). I then deleted the lines below this except for the line /PSEContent leaving one space between the lines. I saved and closed the document. I then put the saved file in the Photo Creations/layer style folder. When I started PSE I held down the sift key when I selected Editor. As I said, the first two I did showed up fine. The next ones is where I had the problem.
I did all of this in the Admin account. When I go into my user account, PSE works but now I am afraid to try to add the layer styles. -
How to create DataSource for BI Source System in RSA1?
I have a BI Source System defined, however I can't figure out a way to create a new DataSource for it. I can create DataSource objects for all my other Source Systems, but I can't figure out how to do this for this BI system.
I select my BI Source System, right-click, choose "Display DataSource tree". When I right-click from the DataSource tree, I expect to get "Create Application Component" and "Create DataSource" options, but instead I only see "Replicate Tree Metadata" and "Replicate DataSources" options.
How can I create DataSource objects for my BI system?Hi,
I guess you want to create a custom developed source in BI itself. For that you need to create the data source in RSO2 and inside you need to give the specific aplication component under which you want this DS to be in. Generate a data souce and then go to BI My self Source system and then replicate that particular appl component o view your data source.
Hope this helps
Regards,
Srini
Maybe you are looking for
-
When you get a apple receipt for itunes songs and you paid with a itunes gift card do they charge you or give you store credit what's store credit is it good or bad or does it charge you if you have a free account with no credit cards at all is it ba
-
What happended to "Save As" in the SQL Worksheet?
I am using 14.22 in Windows XP. In the previous version 13.43 I used to: 1) Open a new SQL Worksheet. 2) Type in statements. 3) Press Ctrl-S to save the contents of the SQL Worksheet panel to a new file, an "Open File" dialog appeared. 4) Enter file
-
Report to create subopportunity
Hi EXPERTS, i have one requirement that, to write a report program to create subopportunity under one master opportunity and maintain link between this. Please help me to solve this? Thanks in advance, Saju.
-
Dear experts, I have a user decision step. Before the approver can approve or reject the workitem i need to show a tocde screen to him. Say for example CN25. My workitem will be generated only after initiator makes changes in that tcode. I want appro
-
More... Black Screen
My screen went black (you can still see the desk top through the black screen under light) a few days ago and I took it to the Apple Store. They sent me to an certified Apple Repair shop because my computer is considered "vintage". The repair shop di