Hierarchy - description

Hi experts,
i have InfoPackage to create hierarchy from txt file. In hierarchy folder (selection) i have description of hierarchy and technical name and new name of hierarchy after loading ( tech. name ).
My question - I would like to change description of hierarchy, i can see button (Header Data ) over InfoObject, i can change name of hierarchy, but after loading the description is taken from desc. in InfoPackage again and i didn't find how to change desc. in InfoPackage.
Thanks in advance
Martin

Hi Martin,
that's strange. Here's a workaround - not a fix:
How about you just created a new Infopackage after you renamed the hierarchies as described in my last post and test whether that works.
If it does not solve the problem, raise a customer message with SAP. Maybe it's a bug.
Good luck,
Ralf
Edited by: Ralf Boye on Dec 14, 2009 4:55 PM

Similar Messages

About the Hierarchy description change to chinese

Hi,
About the Hierarchy,
I want to display the Hierarchy description change to chinese,
I change the Hierarchy description to chinese in Discoverer Administrator,
But the Hierarchy description still show column name in Discoverer Viewer,
If I change the Hierarchy attribute name to chinese in Discoverer Administrator,
and the Hierarchy description still show column name in Discoverer Viewer,
It's important issue for my end user,
so anyone can help me ?
your sincerely,
Yeh

Hi Bernhard,
Answer to your Question:
The original setting :
ANLB-PERFY = 12.
T090NA-XDAILY= " "
some one changed the Dep Key with
T090NA-XDAILY= X
I made the below change:
T090NA-XDAILY= " ".
then there is no error for the Asset.
Please let me know how to identify all the assets that have this error. You have mentioned RAAFAR00 'Recalculate depreciation'.
so my understanding is if i run the program the warning for all the assets appear.
Does calculation of Depreciation AFAB report the assets with errors.
Thanks,
Raja.

Hierarchy Descriptions missing

Hi,
I uploaded hierarchies into an info object which was successful.
My problen is that when i check the hierarchy in BW in the infoobject it shows only node ids for the nodes and not the descriptions as shown in R/3.
I've never loaded hierarchies before so, do not know where i could have gone wrong. if you need more inputs please let me know.
Thanks in advance
Sid

Yes, the texts are loaded. should the descriptions be present in the text table of the infoobj. If so, I cannot find it.
when I run the extraction from rsa6 in the source system it shows all the descriptions.
is there some way to debug and find out why the descriptions are not being loaded in BW
Sid

Change Hierarchy description

Hi All,
Is there a way in BW by means of which I can change the description (not technical name) of already existing hierarchy?
I tried changing in the header but when I reloaded it got back its old name, in infopackage when I did a rename it created a new hierarchy with a new technical name.
Any Idea if thats possible or its a draw back of BW.
Thanks in advance,
Tina.

Hello Tina,
Did you already found a solution for your problem?
We're facing the same over here.
Greetings,
René

Hierarchy Description fields...

Hi Experts,
As of now we have a couple of flat-filehierarchies. Now when we do a flat-file load, evrn though we have set up values for the columns short/medium/long description,the system just seems to be picking the values from the Text table of the InfoObject and ignores the description in the flat-file.
For example for a particulat organization(say XX)...if the text table doesn't contain a description but the flat-file for the hierarchy has a description of 'ABC',the hierarchy structure doesn't contain the description for organization'XX'.
Is this how a hierarchy load is supposed to work(by referencing the descriptions from the text table?) if so, what is the use of the description fields in the hierarchy flat-file?
Thanks
Arvind

Hi Ganesh,
Thanks for your reply,
I need to move data from hierarchy table to taxonomy table using validations and assignments.
Thanks in Advance
bharat.chinthapatla

BEx Selection screen Hierarchy display (text - key)

Hi,
We have a new query deployed that uses several hierarchies in the selection screen.
When running the reports, the drop down for the hierarchies on the variable selection screen displays the full text.
However, the users are more familiar with the key value and would prefer to see that. In the actual report, the keys are displayed.
I am trying to find where the default display can be set for the hierarchies on the BEx selection screen so I can show the key values?
Thanks!
Darryl
Edited by: Darryl Goveas on Nov 16, 2011 12:14 PM

Create a FM like below and a wrapper for it so you can call it as part of process chain; we load all of our hierarchies then call this:
FUNCTION ZBW_CHANGE_HIER_DISPLAYNAME.
""Local Interface:
*" EXPORTING
*"     VALUE(RETURN) TYPE BAPIRET2
data: hieid(25) type c,
        hienm(30) type c,
        lgtxt(60) type c.
RETURN-TYPE = 'I'.
RETURN-ID = '01'.
Select each hierarchy from list table
select nhieid nhienm t~txtmd
into (hieid, hienm, lgtxt)
from rshiedir as n
join rshiedirt as t
on nhieid = thieid
where n~objvers = 'A'
and   t~objvers = 'A'.
    if sy-subrc = 0.
    concatenate Key and Text
      concatenate hienm '-' lgtxt into lgtxt SEPARATED BY space.
    update table with new description
      update rshiedirt
      set TXTLG = lgtxt
      where langu = 'E'
      and hieid   = hieid
      and objvers = 'A'.
      if sy-subrc = 0.
        RETURN-NUMBER = '001'.
        RETURN-MESSAGE = 'Successfully updated Hierarchy Descriptions.'.
      else.
        RETURN-NUMBER = '002'.
        RETURN-MESSAGE = 'Error when updating Hierarchy Descriptions.'.
      endif.
    else.
      RETURN-NUMBER = '003'.
      RETURN-MESSAGE = 'Error when selecting Hierarchy Descriptions.'.
    endif.
endselect.

JS CS4 splitting the document path

I'm trying to split the document file path so I may navigate up one or two folders and then into a specific subfolder.
When I try to split the "myDoc.filePath" it errors. If I split "myDoc.name" it works correctly.
var myDoc = app.activeDocument;
var myDocPath = myDoc.filePath;
var mySplit = myDoc.name.indexOf ("_");
var myFileName = myDoc.name.slice (0,mySplit);
var myPdfFolder = myFileName + "pdf";
var mySavePath = myDocPath
var mySplit2 = myDoc.filePath.indexOf (myFileName);
var myFinalPath = myDoc.filePath.slice (0,mySplit2) + myFileName + "/" + myPdfFolder;
alert(myFinalPath);
Can someone shed light on how to split the document path?
Thanks,
John
Document path: ~desktop/N123456/working/N123456_01
Note: the last folder name does not always exist. Often the "working" folder is the last folder. Working folder and N123456pdf reside on the same level.
Goal is to change the save to document path: ~desktop/N123456/N123456pdf

Here's some code I wrote recently to find a folder named "Snippets" starting from the location of a document. It first looks in the same folder and then its parent and on up until it reaches the top of the file hierarchy:
//DESCRIPTION: Search for Snippets folder from Document location
(function() {
    if (app.documents.length > 0) {
        var myFolder = locateRelatedFolder(app.documents[0].filePath, "Snippets");
        if (myFolder == null) {
            alert("Unable to locate Snippets folder");
            return;
        } else {
            alert("Snippets folder is: " + myFolder);
    function locateRelatedFolder(folder, name) {
        while (folder != null) {
            var relatedFolder = Folder(folder + "/" + name);
            if (relatedFolder.exists) return relatedFolder;
            folder = folder.parent;
    } // end locateRelatedFolder
I've enclosed the code in an anonymous function. Don't let that put you off. You could just delete the first line after the description and the last line.
Dave

How to write ABAP code behind, the OLAP navigation functions

Hi SDN Community,
We have created an artificial hierarchy within BEx, using order structure elements, or characteristic key figures as SAP calls them.
Now, the only feature that dosent seem to be present within the OLAP, is to expand all hiearchy nodes.
It allows you to expand one hierarchy node, but not all the structure element nodes.
I have tried command sequencing by specifying the technical id's of the the structure elements found via RSRT2, but this dosen't work.
I have seen that when the nodes are expanded, that there is indeed standard SAP ABAP code executing back in the datawarehouse.
Hence, do you know
- Where to make ABAP enhancements for OLAP functionality
- How to execute this ABAP (will it be by using Web API and javascript enhancements)
- Is this possible, or has it been done by anyone?
Thank you.
Simon

Hi Thomas,
I have been working with a brilliant ABAP'er, and together we
implemented a solution in the START method, that makes use of the
following methods and expands all the hierarchy nodes at start.
And this class can be omitted in the Print all view we have formulated
as only a collapsed view has been specified there.
thank you.
Simon
I found this all in that class interface CL_RSR_REQUEST
for N_R_REQUEST
for N_R_DATA_SET
Initial Value: Set Drilldown State of a Hierarchy
Description: 'SET_DRILL_STATE'
this looks like the method that gets executed. what do you think?
can you code this in the program
constants C_CMD_SET_DRILL_STATE type RSRCMDID
value 'SET_DRILL_STATE'. "#EC NOTEXT
methods SET_DRILL_STATE
importing
value(I_AXIS) type RRXAXIS optional
value(I_POSITION) type I optional
value(I_FOCUS_IOBJNM) type RSIOBJNM optional
value(I_DRILLSTATE) type RRXDRILLSTATE optional
value(I_TOGGLE) type RS_BOOL default RS_C_FALSE
!I_R_PARAMETER type ref to CL_RSR_PARAMETER optional
exporting
!E_KEEP_LAST_LINES type I
!E_KEEP_FIRST_LINES type I
!E_NEW_LINES_FROM type I
!E_NEW_LINES_TO type I
!E_NODE_POSITION_FROM type I
!E_NODE_POSITION_TO type I
exceptions
NO_PROCESSING
X_MESSAGE .

Problem while using olap cwm2 by pl/sql objects

Dear all:
I want to build an olap multidimension model by oracle cwm2 api. I created the multidimension model successfully by call the cwm2 api directory. however, when I try to write objects to encapsulate the cwm2 apis, it was not work. here is my codes:
call cwm2 api directly, it's work.
/* create star schema */
create table customer (
id number primary key,
id_continent number,
id_country number
create table selling_month (
id number primary key,
yr number (4),
mth number (12) check (mth between 1 and 12),
id_quarter number,
id_month number,
end_of_month date,
end_of_quarter date,
end_of_year date
create table product (
id number primary key,
id_category number
create table item_sold (
qty number(4),
id_customer references customer ,
id_month references selling_month,
id_product references product
/* create dimension */
begin
cwm2_olap_dimension.create_dimension(
user, -- dimension owner
'CUSTOMER_DIM', -- dimension name
'Customer', -- display name
'Customers', -- plural name
'Customer', -- short description
'Customer' -- description
end;
begin
cwm2_olap_dimension.create_dimension(
user, -- dimension owner
'PRODUCT_DIM', -- dimension name
'Product', -- display name
'Product', -- plural name
'Product', -- short description
'Product' -- description
end;
begin
cwm2_olap_dimension.create_dimension(
user, -- dimension owner
'TIME_DIM', -- dimension name
'Time', -- display name
'Time', -- plural name
'Time', -- short description
'Time', -- description
'Time' -- dimension type, note: this is the only time dimension in this example
end;
/* create hierarchy */
begin
cwm2_olap_hierarchy.create_hierarchy (
user, -- owner of dimension to which hierarchy is assigned
'CUSTOMER_DIM', -- name of dimension to which hierarchy is assigned
'CUSTOMER_HIER', -- name of hierarchy
'Customer hierarchy', -- display name
'Customer hierarchy', -- short description
'Customer hierarchy', -- description
     'UNSOLVED LEVEL-BASED' -- solved code
end;
begin
cwm2_olap_hierarchy.create_hierarchy (
user, -- owner of dimension to which hierarchy is assigned
'PRODUCT_DIM', -- name of dimension to which hierarchy is assigned
'PRODUCT_HIER', -- name of hierarchy
'Product hierarchy', -- display name
'Product hierarchy', -- short description
'Product hierarchy', -- description
'UNSOLVED LEVEL-BASED' -- solved code
end;
begin
cwm2_olap_hierarchy.create_hierarchy (
user, -- owner of dimension to which hierarchy is assigned
'TIME_DIM', -- name of dimension to which hierarchy is assigned
'TIME_HIER', -- name of hierarchy
'Time hierarchy', -- display name
'Time hierarchy', -- short description
'Time hierarchy', -- description
'UNSOLVED LEVEL-BASED' -- solved code
end;
/* creating levels */
-- Levels for the customer dimension
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'CUSTOMER_DIM', -- name of dimension to which level is assigned
'LVL_ALL_CUSTOMERS', -- name of level
'All customers', -- display name
'All customers', -- plural name
'All customers', -- short description
'All customers' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'CUSTOMER_DIM', -- name of dimension
'CUSTOMER_HIER', -- name of hierarchy
'LVL_ALL_CUSTOMERS', -- name of level
null); -- parent level
end;
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'CUSTOMER_DIM', -- name of dimension to which level is assigned
'LVL_CUSTOMERS_CONTINENT',-- name of level
'Customer on continent', -- display name
'Customers on continent', -- plural name
'Customers on continent', -- short description
'Customers on continent' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'CUSTOMER_DIM', -- name of dimension
'CUSTOMER_HIER', -- name of hierarchy
'LVL_CUSTOMERS_CONTINENT', -- name of level
'LVL_ALL_CUSTOMERS'); -- parent level
end;
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'CUSTOMER_DIM', -- name of dimension to which level is assigned
'LVL_CUSTOMERS_COUNTRY', -- name of level
'Customer in country', -- display name
'Customers in country', -- plural name
'Customers in country', -- short description
'Customers in country' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'CUSTOMER_DIM', -- name of dimension
'CUSTOMER_HIER', -- name of hierarchy
'LVL_CUSTOMERS_COUNTRY', -- name of level
'LVL_CUSTOMERS_CONTINENT');-- parent level
end;
-- Levels for the product dimension
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'PRODUCT_DIM', -- name of dimension to which level is assigned
'LVL_ALL_PRODUCTS', -- name of level
'All products', -- display name
'All products', -- plural name
'All products', -- short description
'All products' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'PRODUCT_DIM', -- name of dimension
'PRODUCT_HIER', -- name of hierarchy
'LVL_ALL_PRODUCTS', -- name of level
null); -- parent level
end;
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'PRODUCT_DIM', -- name of dimension to which level is assigned
'LVL_PRODUCT_CATEGORY', -- name of level
'Product category', -- display name
'Product categories', -- plural name
'Product categories', -- short description
'Product categories' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'PRODUCT_DIM', -- name of dimension
'PRODUCT_HIER', -- name of hierarchy
'LVL_PRODUCT_CATEGORY', -- name of level
'LVL_ALL_PRODUCTS'); -- parent level
end;
-- Levels for the time dimension
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'TIME_DIM', -- name of dimension to which level is assigned
'LVL_YEAR', -- name of level
'Year', -- display name
'Years', -- plural name
'Year', -- short description
'Year' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'TIME_HIER', -- name of hierarchy
'LVL_YEAR', -- name of level
null); -- parent level
end;
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'TIME_DIM', -- name of dimension to which level is assigned
'LVL_QUARTER', -- name of level
'Quarter', -- display name
'Quarters', -- plural name
'Quarter', -- short description
'Quarter' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'TIME_HIER', -- name of hierarchy
'LVL_QUARTER', -- name of level
'LVL_YEAR'); -- parent level
end;
begin
cwm2_olap_level.create_level (
user, -- owner of dimension to which level is assigned
'TIME_DIM', -- name of dimension to which level is assigned
'LVL_MONTH', -- name of level
'Month', -- display name
'Months', -- plural name
'Month', -- short description
'Month' -- description
end;
begin
cwm2_olap_level.add_level_to_hierarchy (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'TIME_HIER', -- name of hierarchy
'LVL_MONTH', -- name of level
'LVL_QUARTER'); -- parent level
end;
/* specify the level to hierarchy relationship */
-- Customer
-- Product
-- Time
/* specify the dimesion attributes */
begin
cwm2_olap_dimension_attribute.create_dimension_attribute_2 (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'End Date', -- display name
'End Date', -- short description
'End Date', -- description
1); -- use name as type
end;
/* specify the level attributes */
begin
cwm2_olap_level_attribute.create_level_attribute_2 (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'LVL_YEAR', -- name of level
'End Date', -- name of level attribute
'End Date', -- display name
'End Date', -- short description
'End Date', -- description
1); -- use name as type
end;
begin
cwm2_olap_level_attribute.create_level_attribute_2 (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'LVL_QUARTER', -- name of level
'End Date', -- name of level attribute
'End Date', -- display name
'End Date', -- short description
'End Date', -- description
1); -- use name as type
end;
begin
cwm2_olap_level_attribute.create_level_attribute_2 (
user, -- owner of dimension
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'LVL_MONTH', -- name of level
'End Date', -- name of level attribute
'End Date', -- display name
'End Date', -- short description
'End Date', -- description
1); -- use name as type
end;
/* mapping the levels to columns in the dimension table */
-- Customer
-- Hierarycies (from high to low): ID_COUNTRY->ID_CONTINENT->ID
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'CUSTOMER_DIM', -- dimension name
'CUSTOMER_HIER', -- name of hierarchy
'LVL_ALL_CUSTOMERS', -- name of level
user, -- owner of dimension table
'CUSTOMER', -- name of table
'ID_COUNTRY', -- name of column
null -- name of parent column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'CUSTOMER_DIM', -- dimension name
'CUSTOMER_HIER', -- name of hierarchy
'LVL_CUSTOMERS_CONTINENT', -- name of level
user, -- owner of dimension table
'CUSTOMER', -- name of table
'ID_CONTINENT', -- name of column
'ID_COUNTRY' -- name of parent column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'CUSTOMER_DIM', -- dimension name
'CUSTOMER_HIER', -- name of hierarchy
'LVL_CUSTOMERS_COUNTRY', -- name of level
user, -- owner of dimension table
'CUSTOMER', -- name of table
'ID', -- name of column
'ID_CONTINENT' -- name of parent column
end;
-- Product
-- Hierarchies: ID_CATEGORY->ID
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'PRODUCT_DIM', -- dimension name
'PRODUCT_HIER', -- name of hierarchy
'LVL_ALL_PRODUCTS', -- name of level
user, -- owner of dimension table
'PRODUCT', -- name of table
'ID_CATEGORY', -- name of column
null -- name of parent column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'PRODUCT_DIM', -- dimension name
'PRODUCT_HIER', -- name of hierarchy
'LVL_PRODUCT_CATEGORY', -- name of level
user, -- owner of dimension table
'PRODUCT', -- name of table
'ID', -- name of column
'ID_CATEGORY' -- name of parent column
end;
-- Time
-- Hierarchies: YR->ID_QUARTER->ID_MONTH
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'TIME_DIM', -- dimension name
'TIME_HIER', -- name of hierarchy
'LVL_YEAR', -- name of level
user, -- owner of dimension table
'SELLING_MONTH', -- name of table
'YR', -- name of column
null -- name of parent column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'TIME_DIM', -- dimension name
'TIME_HIER', -- name of hierarchy
'LVL_QUARTER', -- name of level
user, -- owner of dimension table
'SELLING_MONTH', -- name of table
'ID_QUARTER', -- name of column
'YR' -- name of parent column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(
user, -- dimension owner
'TIME_DIM', -- dimension name
'TIME_HIER', -- name of hierarchy
'LVL_MONTH', -- name of level
user, -- owner of dimension table
'SELLING_MONTH', -- name of table
'ID_MONTH', -- name of column
'ID_QUARTER' -- name of parent column
end;
/* creating cube */
begin
cwm2_olap_cube.create_cube(
user, -- cube owner
'Test_Cube', -- name of cube
'Test Cube', -- display name
'Test Cube', -- short description
'Test Cube' -- description
end;
/* mapping ... */
begin
cwm2_olap_table_map.map_dimtbl_hierlevelattr (
user, -- dimension owner
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'TIME_HIER', -- name of hierarchy
'LVL_MONTH', -- name of level
'End Date', -- name of level attribute
user, -- owner of table
'SELLING_MONTH', -- name of table
'END_OF_MONTH' -- name of column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevelattr (
user, -- dimension owner
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'TIME_HIER', -- name of hierarchy
'LVL_QUARTER', -- name of level
'End Date', -- name of level attribute
user, -- owner of table
'SELLING_MONTH', -- name of table
'END_OF_QUARTER' -- name of column
end;
begin
cwm2_olap_table_map.map_dimtbl_hierlevelattr (
user, -- dimension owner
'TIME_DIM', -- name of dimension
'End Date', -- name of dimension attribute
'TIME_HIER', -- name of hierarchy
'LVL_YEAR', -- name of level
'End Date', -- name of level attribute
user, -- owner of table
'SELLING_MONTH', -- name of table
'END_OF_YEAR' -- name of column
end;
/* adding dimension to cube */
begin
cwm2_olap_cube.add_dimension_to_cube (
user, -- owner of cube
'Test_Cube', -- name of cube
user, -- owner of dimension
'CUSTOMER_DIM' -- name of dimension
end;
begin
cwm2_olap_cube.add_dimension_to_cube (
user, -- owner of cube
'Test_Cube', -- name of cube
user, -- owner of dimension
'PRODUCT_DIM' -- name of dimension
end;
begin
cwm2_olap_cube.add_dimension_to_cube (
user, -- owner of cube
'Test_Cube', -- name of cube
user, -- owner of dimension
'TIME_DIM' -- name of dimension
end;
/* creating the measure */
begin
cwm2_olap_measure.create_measure (
user, -- owner of cube
'Test_Cube', -- name of cube
'sold items', -- name of measure
'sold items', -- display name
'sold items', -- short description
'sold items' -- description
end;
/* Creating the join relationship between the fact table and the dimension tables */
begin
cwm2_olap_table_map.map_facttbl_levelkey (
user, -- owner of cube
'Test_Cube', -- name of cube
user, -- owner of fact table
'ITEM_SOLD', -- name of fact table
'LOWESTLEVEL', -- storetype
'DIM:' || user || '.CUSTOMER_DIM/HIER:CUSTOMER_HIER/LVL:LVL_CUSTOMERS_COUNTRY/COL:ID_CUSTOMER;' ||
'DIM:' || user || '.PRODUCT_DIM/HIER:PRODUCT_HIER/LVL:LVL_PRODUCT_CATEGORY/COL:ID_PRODUCT;' ||
'DIM:' || user || '.TIME_DIM/HIER:TIME_HIER/LVL:LVL_MONTH/COL:ID_MONTH;'
end;
/* measure? */
begin
cwm2_olap_table_map.map_facttbl_measure (
user, -- owner of cube
'Test_Cube', -- name of cube
'sold items', -- name of measure
user, -- owner of fact table
'ITEM_SOLD', -- name of fact table
'QTY', -- name of column
'DIM:' || user || '.CUSTOMER_DIM/HIER:CUSTOMER_HIER/LVL:LVL_CUSTOMERS_COUNTRY/COL:ID_CUSTOMER;' ||
'DIM:' || user || '.PRODUCT_DIM/HIER:PRODUCT_HIER/LVL:LVL_PRODUCT_CATEGORY/COL:ID_PRODUCT;' ||
'DIM:' || user || '.TIME_DIM/HIER:TIME_HIER/LVL:LVL_MONTH/COL:ID_MONTH;'
end;
/* validating the cube */
begin
cwm2_olap_validate.validate_cube (
user, -- owner of cube
'Test_Cube' -- name of cube
end;
encapsulate cwm2 apis into objects (IT WAS NOT WORK)
--base class
create or replace type BaseClass as object (
objUser varchar2(255),
objName varchar2(255),
constructor function BaseClass(objUser varchar2, objName varchar2) return self as result,
member function getName return varchar2
INSTANTIABLE NOT FINAL;
--dimension facade
create or replace type DimensionFacade under BaseClass (
hierName varchar2(255),
constructor function DimensionFacade(objUser varchar2, objName varchar2) return self as result,
member procedure setHierarchy(hierName varchar2),
member function addLevel(levelName varchar2, parentLevel varchar2) return boolean,
member function addAttribute(attrName varchar2, levelName varchar2) return boolean,
member function addAttribute(attrName varchar2) return boolean,
member function mapLevel2FactTable(levelName varchar2, tableName varchar2, colName varchar2, parentCol varchar2) return boolean,
member function mapAttribute2DimTable(levelName varchar2, attrName varchar2, dimTable varchar2, colName varchar2) return boolean
INSTANTIABLE FINAL;
--cube facade
create or replace type CubeFacade under BaseClass (
measureName varchar2(255),
constructor function CubeFacade(objUser varchar2, objName varchar2) return self as result,
member procedure addDimension(dimName varchar2),
member procedure setMeasure(measureName varchar2),
member function mapMeasure2FactTable(tableName varchar2, colName varchar2, mapStr varchar2) return boolean
INSTANTIABLE FINAL;
object implementation
prepared: 2006-12-12
author: copper
--base class
create or replace type body BaseClass as
constructor function BaseClass(objUser varchar2, objName varchar2) return self as result
is
begin
self.objUser := objUser;
     self.objName := objName;
     return;
end;
member function getName return varchar2
is
begin
return self.objUser;
end;
end;
--dimension facade
create or replace type body DimensionFacade as
constructor function DimensionFacade(objUser varchar2, objName varchar2) return self as result
is
begin
self.objUser := objUser;
self.objName := objName;
cwm2_olap_dimension.create_dimension(objUser, objName, objName||' display', objName||' plural', objName||' short des', objName||' description');
dbms_output.put_line('create dimension ok, dimension name:'||objName||',dimension user:'||objUser);
return;
end;
member procedure setHierarchy(hierName varchar2)
is
begin
self.hierName := hierName;
cwm2_olap_hierarchy.create_hierarchy (objUser, objName, hierName, hierName||' display', hierName||' short des', hierName||' description', 'UNSOLVED LEVEL-BASED');
dbms_output.put_line('set hierarchy ok, dimension name:'||objName||',dimension user:'||objUser||',hierarchy name:'||hierName);
end;
member function addLevel(levelName varchar2, parentLevel varchar2) return boolean
is
begin
cwm2_olap_level.create_level(objUser, objName, levelName, levelName||'display', levelName||' plural', levelName||' short des', levelName||' description');
cwm2_olap_level.add_level_to_hierarchy (objUser, objName, hierName, levelName, parentLevel);
dbms_output.put_line('create level and add level to hierarchy ok!');
return true;
end;
member function addAttribute(attrName varchar2, levelName varchar2) return boolean
is
begin
cwm2_olap_level_attribute.create_level_attribute_2 (objUser, objName, attrName, levelName, attrName, attrName||' display', attrName||' short des', attrName||' description', 1);
return true;
end;
member function addAttribute(attrName varchar2) return boolean
is
begin
cwm2_olap_dimension_attribute.create_dimension_attribute_2 (objUser, objName, attrName, attrName||' display', attrName||' short des', attrName||' description', 1);
return true;
end;
member function mapLevel2FactTable(levelName varchar2, tableName varchar2, colName varchar2, parentCol varchar2) return boolean
is
begin
cwm2_olap_table_map.map_dimtbl_hierlevel(objUser, objName, hierName, levelName, objUser, tableName, colName, parentCol);
return true;
end;
member function mapAttribute2DimTable(levelName varchar2, attrName varchar2, dimTable varchar2, colName varchar2) return boolean
is
begin
cwm2_olap_table_map.map_dimtbl_hierlevelattr (objUser, objName, attrName, hierName, levelName, attrName, objUser, dimTable, colName);
return true;
end;
end;
--cube facade
create or replace type body CubeFacade as
constructor function CubeFacade(objUser varchar2, objName varchar2) return self as result
is
begin
self.objUser := objUser;
self.objName := objName;
cwm2_olap_cube.create_cube(objUser, objName, objName||' display', objName||' short des', objName||' description');
return;
end;
member procedure addDimension(dimName varchar2)
is
begin
cwm2_olap_cube.add_dimension_to_cube (objUser, objName, objUser, dimName);
dbms_output.put_line('ok!');
end;
member procedure setMeasure(measureName varchar2)
is
begin
self.measureName := measureName;
cwm2_olap_measure.create_measure (objUser, objName, measureName, measureName||' display', measureName||' short des', measureName||' description');
end;
member function mapMeasure2FactTable(tableName varchar2, colName varchar2, mapStr varchar2) return boolean
is
begin
cwm2_olap_table_map.map_facttbl_levelkey (objUser, objName, objUser, tableName, 'LOWESTLEVEL', mapStr);
cwm2_olap_table_map.map_facttbl_measure (objUser, objName, measureName, objUser, tableName, colName, mapStr);
return true;
end;
end;
--dimension modula using sample
create or replace package DimensionModuleSample as
procedure buildMultidimensionCube;
end;
create or replace package body DimensionModuleSample as
procedure buildMultidimensionCube
is
dimC DimensionFacade; --customer
dimP DimensionFacade; --product
dimT DimensionFacade; --time
cub CubeFacade;
ret boolean;
begin
dbms_output.put_line('start build dimension module!');
dimC := DimensionFacade(user, 'CUSTOMER_DIM');
     dimP := DimensionFacade(user, 'PRODUCT_DIM');
     dimT := DimensionFacade(user, 'TIME_DIM');
dimC.setHierarchy('CUSTOMER_HIER');
dimP.setHierarchy('PRODUCT_HIER');
dimT.setHierarchy('TIME_HIER');
     ret := dimC.addLevel('LVL_ALL_CUSTOMERS', null);
ret := dimC.addLevel('LVL_CUSTOMERS_CONTINENT', 'LVL_ALL_CUSTOMERS');
ret := dimC.addLevel('LVL_CUSTOMERS_COUNTRY', 'LVL_CUSTOMERS_CONTINENT');
ret := dimP.addLevel('LVL_ALL_PRODUCTS', null);
ret := dimP.addLevel('LVL_PRODUCT_CATEGORY', 'LVL_ALL_PRODUCTS');
ret := dimT.addLevel('LVL_YEAR', null);
ret := dimT.addLevel('LVL_QUARTER', 'LVL_YEAR');
ret := dimT.addLevel('LVL_MONTH', 'LVL_QUARTER');
     ret := dimT.addAttribute('end date');
ret := dimT.addAttribute('end date', 'LVL_YEAR');
ret := dimT.addAttribute('end date', 'LVL_QUARTER');
ret := dimT.addAttribute('end date', 'LVL_MONTH');
     ret := dimC.mapLevel2FactTable('LVL_ALL_CUSTOMERS', 'CUSTOMER', 'ID', null);
ret := dimC.mapLevel2FactTable('LVL_CUSTOMERS_CONTINENT', 'CUSOMTER', 'ID_CONTINENT', 'ID');
ret := dimC.mapLevel2FactTable('LVL_CUSTOMERS_COUNTRY', 'CUSTOMER', 'ID_COUNTRY', 'ID_CONTINENT');
ret := dimP.mapLevel2FactTable('LVL_ALL_PRODUCTS', 'PRODUCT', 'ID', null);
ret := dimP.mapLevel2FactTable('LVL_PRODUCT_CATEGORY', 'PRODUCT', 'ID_CATEGORY', 'ID');
ret := dimT.mapLevel2FactTable('LVL_YEAR', 'SELLING_MONTH', 'YR', null);
ret := dimT.mapLevel2FactTable('LVL_QUARTER', 'SELLING_MONTH', 'ID_QUARTER', 'YR');
ret := dimT.mapLevel2FactTable('LVL_MONTH', 'SELLING_MONTH', 'ID_MONTH', 'ID_QUARTER');
ret := dimT.mapAttribute2DimTable('LVL_YEAR', 'END DATE', 'SELLING_MONTH', 'END_OF_YEAR');
ret := dimT.mapAttribute2DimTable('LVL_QUARTER', 'END DATE', 'SELLING_MONTH', 'END_OF_QUARTER');
ret := dimT.mapAttribute2DimTable('LVL_MONTH', 'END DATE', 'SELLING_MONTH', 'END_OF_MONTH');
cub := CubeFacade(user, 'TEST_CUBE');
cub.addDimension(dimC.getName);
     cub.addDimension(dimP.getName);
     cub.addDimension(dimT.getName);
     cub.setMeasure('SOLID IMEMS');
     ret := cub.mapMeasure2FactTable('ITEM_SOLD', 'QTY',
'DIM:' || user || '.CUSTOMER_DIM/HIER:CUSTOMER_HIER/LVL:LVL_CUSTOMERS_COUNTRY/COL:ID_CUSTOMER;' ||
'DIM:' || user || '.PRODUCT_DIM/HIER:PRODUCT_HIER/LVL:LVL_PRODUCT_CATEGORY/COL:ID_PRODUCT;' ||
'DIM:' || user || '.TIME_DIM/HIER:TIME_HIER/LVL:LVL_MONTH/COL:ID_MONTH;');
exception
when OTHERS then
dbms_output.put_line('get error!');
end;
end;
--test codes
begin
DimensionModuleSample.buildMultidimensionCube;
end;
the error information is:
14:23:05 ORA-06510: unhandled user-defined exception
14:23:05 ORA-06512: "OLAPSYS.CWM2_OLAP_UTILITY", line1660
14:23:05 ORA-01403: no data found
14:23:05 ORA-06512: "OLAPSYS.CWM2_OLAP_LEVEL", line28
14:23:05 ORA-06512: "OLAPSYS.CWM2_OLAP_LEVEL", line57
14:23:05 ORA-06512: "OLAPSYS.CWM2_OLAP_LEVEL", line456
14:23:05 ORA-06512: line2

Hi,
Please see if these documents help.
Note: 367607.1 - FDPSTP Failed Due to ORA-01861: Literal Does Not Match Format String
Note: 370272.1 - not able to run the report set having unsupported date format of fnd-date4
Note: 376034.1 - How to Handle New Date Formats in SQL*Plus and PL/SQL Procedures?
Regards,
Hussein

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;
/

Table and field name for the goods receipt date in SAP CRM

Hi,
can some one provide me The TABLE-FIELD from SAP CRM system for GOODS RECIPT DATE.
It is the same as Received material date in DIsplay:Return and replacemnt screen in CRM.
Thanks,
Chetan

Few more tables:
BUT0BANK         Business Partner: Bank Data
BUT0BK           BP: Bank details
BUT0CC           BP: Payment Cards
BUT0ID           BP: ID Numbers
BUT0ID_BIP_NOHIT Business Information Provider: Logging of non identified BP
BUT0IS           BP: Industries
BUT0VP           BP: Business Partner Assignment and Links
BUT100           BP: Roles
BUT150           BP relationship: Attribute table (test different.type TBUKR)
CRMM_BUT_BUHI_1 R/3 Customer Sales Area CRM BP Hierarchy Group Mapping
CRMM_BUT_BUHI_2 R/3 Leaf Customer Sales Area CRM BP Hierarchy Group Mapping
CRMM_BUT_CONTNO Mapping Table Business Partner Relationship – Contact Person
CRMM_BUT_CRMOBJ Buffer: Which BPs are in Which Systems
CRMM_BUT_CUSTNO Mapping Table Business Partner – Customer
CRMM_BUT_FRG0040 Business Partner Sales Classification List
CRMM_BUT_FRG0041 Business Partner Sales Classification
CRMM_BUT_FRG0042 Business Partner Sales Classification List Order Blocks
CRMM_BUT_FRG0050 Business Partner – Status
CRMM_BUT_FRG0060 Business Partner – Business Hours
CRMM_BUT_FRG0061 Business Partner – Business Hours Interval
CRMM_BUT_FRG0070 Business Partner Excluded Partner Functions List
CRMM_BUT_FRG0071 Business Partner Excluded Partner Functions
CRMM_BUT_FRG0080 Business Partner – Sales Area – Partner Function List
CRMM_BUT_FRG0081 Business Partner – Sales Area – Partner Function
CRMM_BUT_FRG0100 CRM Business Partner: Status
CRMM_BUT_KOR0040 Business Partner Korea
CRMM_BUT_KOR0041 Business Partner Korea History
CRMM_BUT_LNK0010 Business Partner – Sales Rule List
CRMM_BUT_LNK0011 Business Partner – Sales Rule
CRMM_BUT_LNK0020 Business Partner – Shipping Rule List
CRMM_BUT_LNK0021 Business Partner – Shipping Rule
CRMM_BUT_LNK0030 Business Partner – Billing Rule List
CRMM_BUT_LNK0031 Business Partner – Billing Rule
CRMM_BUT_LNK0140 Business Partner Organization Rule List
CRMM_BUT_LNK0141 Business Partner Organization Rule
CRMM_BUT_MIGRATE Migration Table: Fields Changed In CDB
CRMM_BUT_SEMPL00 Sales Employee for Contact Person Relationship: Admin. Tech.
CRMM_BUT_SEMPL01 Sales Employee to Contact Person Rel.: Data Table
CRMM_BUT_SET0010 Business Partner – Sales Rule Period
CRMM_BUT_SET0020 Business Partner – Shipping Rule Period
CRMM_BUT_SET0030 Business Partner – Billing Rule Period
CRMM_BUT_SET0140 Business Partner Organization Rule Period
CRMM_BUT_TDAR010 Business Partner – Time-Dependent Appointment Rules
CRMM_BUT_TDAR011 Business Partner – Time-Dependent Appointment Rule Intervals
CRMM_BUT_TDAR012 Business Partner – Time-Dependent Appt Rule Single Intervals
BUT_DNC          BP: Telephone Numbers of the “Do Not Call” List
BUT_DNC_OLD      BP: Telephone Numbers of the “Do Not Call” List
BUT_FRG0010      Business Partner: Tax Classification
BUT_FRG0011      Business Partner: Tax Classification
BUT_HIER_NODE    Business Partner Hierarchy Group
BUT_HIER_NODE_BP Business Partner Hierarchy Group – Bus. Partner Assignment
BUT_HIER_NODE_D Business Partner Hierarchy Group – Description
BUT_HIER_STRUCT Business Partner Hierarchy Group – Hierarchy Relationship
BUT_HIER_TREE    Business Partner Group Hierarchy
BUT_HIER_TREE_D Business Partner Group Hierarchy – Description
BUT_HIER_TYPE    Business Partner Group Hierarchy Category (GUID)
CRMD_ACTIVITY_H Activity Header table
CRMD_ACTIVITY_I Activity Reporting: Activity Line Item Extension
CRMD_TM_ACTIVITY Activity reference
CRMD_LEAD_H Lead Header table
CRMD_OPPORT_H Opportunity Header table
CRMC_T077D : customer account groups
BUT_HIER_TREE Business Partner Group Hierarchy
CDBC_T_PRODUCTID Mapping: Product Id
CDBD_ORGMAN Business transaction – organizational unit -set
COMC_PRODUCT General Product Settings
COMC_R3_FIELDS Assignment of R/3 material master fields to CFOP
COMM_CATEGORY Category
COMM_CFGMAT Basic Data for Materials
COMM_HIERARCHY Category Hierarchy
COMP_TYPES Hierarchy Tool: Comparison Type Check Table
CRMC_CPRICPROC Customer Pricing Procedures
SMOKVBEZ15 Assignment employees to positions
CRMMLSGUID: GUID entry (should match GUID in CRMPRLS)
CRMM_BUT_CUSTNO : Also GUID table (GUID here should match GUID in R/3 table CRMKUNNR)
SMOFSUBTAB : Mapping & Parameters
SMOFDSTAT : Download Monitor (R4AM1)
SMOFFILTAB : Filters (Should match filters in R3AC1 & R/3 Table CRMFILTAB)
SMOFOBJECT Definition of Objects for Download
SMOFOBJPAR Parent Objects of an Object in Table
SMOFPARSFA Middleware Parameter
SMOFQFIND Queue Finder Table for MW-Queue finder
SMOFTABLES Definition of Tables for Download
CRMD_ORDERADM_H = Document Header Table
CRMD_ORDERADM_I = Document Line item Table
COMM_PR_FRG_ROD: Product Sales Set - Product – Assignment
CRMV_PR_SALESA: Product - Sales Order Set

How to create Import format for building version Hirerarchy and Node

Hi
i Want to know how to create Import format for building version Hirerarchy and Nodes.Can anyone show me with example or format for version Hierarchy with few nodes for the hierarchy
i Want to Build   this   1. Version1 (Version)
                                 2.Account (Hirerarchy)
                                 3. Balancesheet (Limb)
                                 4. Assets (Limb)
                                 5. Cash (Leaf)
Thanks,

Please follow the DRM User Guide,
http://docs.oracle.com/cd/E17236_01/epm.1112/drm_user.pdf
Below is my preferred approach, by selecting only relation and Hierarchy sections,
The relation section contains the Node Name and Parent Name ( you can include any other properties, but as a best practice keep the Parent Node as the last column).
The Hierarchy ( Hier ) section contains the Hierarchy Name, Top Node and Hierarchy description
Follow the Import steps and provide a Name for the version.
++++++++++++++++++++++++++++++++
[relation]
AC_BalanceSheet AC_Account
AC_Asset AC_Account
AC_Cash AC_Account
[hier]
Account AC_Account AccountHier
++++++++++++++++++++++
Note: Please delete all the special characters (TAB) created at the end of [relation] and [hier] sections while you copy the content from an Excel sheet to a Notepad.

CMD executions in table class interface via ABAP

Hi SDN Community,
Would it be possible to code in ABAP , and Command statements that can be placed in the web templates.
can this be done in the Table class interface.
For example, the command to expand a hierarchy node that is produced in RSRT2, is
CMD=SET_DRILL_STATE&DATA_PROVIDER=DP=234D5W1FC9W6311O66UCVSRN9E2&IOBJNM=4D5W27AIW32VTOY02REHCSL6Y&TOGGLE_STATE=X
How can this if possible be placed in a Table Class Interface, and coded in ABAP to achieve the expansion of the hierarchy node.
thank you.
Simon

Hi Thomas,
I have been working with a brilliant ABAP'er, and together we
implemented a solution in the START method, that makes use of the
following methods and expands all the hierarchy nodes at start.
And this class can be omitted in the Print all view we have formulated
as only a collapsed view has been specified there.
thank you.
Simon
I found this all in that class interface CL_RSR_REQUEST
for N_R_REQUEST
for N_R_DATA_SET
Initial Value: Set Drilldown State of a Hierarchy
Description: 'SET_DRILL_STATE'
this looks like the method that gets executed. what do you think?
can you code this in the program
constants C_CMD_SET_DRILL_STATE type RSRCMDID
value 'SET_DRILL_STATE'. "#EC NOTEXT
methods SET_DRILL_STATE
importing
value(I_AXIS) type RRXAXIS optional
value(I_POSITION) type I optional
value(I_FOCUS_IOBJNM) type RSIOBJNM optional
value(I_DRILLSTATE) type RRXDRILLSTATE optional
value(I_TOGGLE) type RS_BOOL default RS_C_FALSE
!I_R_PARAMETER type ref to CL_RSR_PARAMETER optional
exporting
!E_KEEP_LAST_LINES type I
!E_KEEP_FIRST_LINES type I
!E_NEW_LINES_FROM type I
!E_NEW_LINES_TO type I
!E_NODE_POSITION_FROM type I
!E_NODE_POSITION_TO type I
exceptions
NO_PROCESSING
X_MESSAGE .

Hierarchy variable description not displaying correctly

Hi all,
I'm using 0ORGUNIT hierarchy variable in several queries either based on the characteristic 0ORGUNIT, or based on the navigational attribute 0EMPLOYEE_0ORGUNIT.
When I execute the query with 0EMPLOYEE_0ORGUNIT hierarchy variable the selection node description displays the Medium description, which is correct.
Whe I execute the query with 0ORGUNIT hierarchy variable the selection node displays the Short description, which is incorrect, as I need it to display the Medium description.
The settings for the object in both query properties are set to display Text Medium Length, and 0ORGUNIT infoobject Business Explorer tab dipslays text, text type is medium Length and bex description is long text, but still when I try to select the node in the parameter selection before query execution the description differs in both cases, any idea why??
Please advice, much appreciated.
Thanks!
M.

Hi,
I understand what you're saying, and unfortunately I can't attach any screenshots here but both queries use the Medium Description in the object properties and it's maintained in the text table /BI0/TORGUNIT as well (short and medium).
However, the BEx Descpription is only in short and long text, there is nothing I can change or maintain about that.
It looks like everything is as it should be, because for one query I can see the medium text properly, but not for the other, even though I'm using the exact same settings, apart from the fact that in one query I use 0ORGUNIT and in the other it's used as a navigational object 0EMPLOYEE_0ORGUNIT.
It's a funny thing indeed....
Thanks
M.

Can we import multiple language descriptions in Hierarchy tables of MDM

Hello Experts,
I am using MDM 7.1 SPS4 and working on the Vendor Repository standard content.
My source file of Regions table contains data in multiple languages for each region record. All the required destination language fields have been mapped properly in the standard map. Import action is set to 'Create' for new records and 'Update Mapped only fileds' for existing records. Matching criteria has Name<English> filed defined in it.
However, after importing these hierarchy records, in data manager only the Name description of English is populated while all other language descriptions for the same record is shown in Red (i.e not populated with the expected data).
Is this a limitation of MDM itself or am I missing some setting?
Thanks in advance,
Elizabeth.

Hi Elizabeth,
steps for importing into hierarchy tables
To add new multilingual records:
1 If necessary, create the hierarchy from the current language layer Name field that contains the hierarchy information (e.g. using the Split Hierarchy command).
2Map the current language layer Name field and then Map/Add the entire set of hierarchy values.
3 Map the other language layer Name field(s). No value mapping is necessary.
4 Map the [Remote Key] field.
5 Record match using: (a) the Name field; (b) the [Remote Key] field (if the Name field was not value mapped); or (c) the combination of both.
To update the language layer of existing records:
Map the other language layer Name field(s). No value mapping is necessary.
Map the [Remote Key] field.
Record match using the [Remote Key] field and set the import action to Update (All Mapped Fields).
Just try and if you need any other info then please get back to me.
Thanks,
Sudhanshu

Hierarchy - description

Similar Messages

Maybe you are looking for