Relationships within BPR

Hi,
Where can I see the hierarchy within BPR in a way that I can download? Say, se16 tables. I want to use the hierarchy outside of the solution manager system for documents etc.
Thank you,
Mike

Hello Mike,
unfortunately there is no way to download the BRP content. BPR is part of the ST-ICO component. But you can look at the following web page for evaluation: https://implementationcontent.sap.com/bpr
cheers
Volker

Similar Messages

M:N relationships within a dimension: Standard process vs. BI Data model

Hi,
I just completed a review of the u201CMulti-Dimensional Modeling with BIu201D from this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84 and I have a quick question here:
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
i.e. my understanding is that, based on Standard Process it is NOT possible to place two characteristics in M:N relationships in the SAME dimension but with BI Data Model, this, the author points out is possible
u201Cdue to the usage of surrogate keys (DIM-IDs) in the dimension tables allowing the same material several times in the dimension tableu201D i.e. although material is the unique key of the dimension.
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
Thanks

Hi Amanda.......
In a dimension table, any number of semantically related dimension attributes are stored in a hierarchy (parent-child relationship as a 1:N relationship). If an M:N relationship exists between dimension attributes, they are normally stored in different dimension tables.
I checked the document.........
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
Here the first thing that I want to tell u is that............the diagram shown here is Classic Start Schema............since Extended Star Schema will never store Master data in Dimension tables.........it stores Masterdata in seperate Master data tables..........and nowadays..............Classic Star schema is obsolet.......Dimension table will only store Dimension id and SID......
Now the Standard process is that..........anything which is Describing a master data..........can be added as an Attribute of that master data.......
Suppose........Employee is the Masterdata.then Ph no can be one of the Attribute of this master data......
So this the Standard Process.........but this cannot be followed every time.........why........already explained.....
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
Bcoz ..........we use compounding Characteris tic to define the Master data uniquely.........and we load compounding Characteristic seoerately...which is independent of the Master data........ie......compounding Characteristic there is a seperate master data tables...........so ..........problem resolved......
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
For Compounding Characteristic............u hav to laod the Coumpoundede master data seperately..which is a overhead...........moreover while query execution......two tables will be accessd..which may result a performance issue.......Performance can be affected when compounded characteristics are used extensively, particularly when a large number of characteristics are included in a compounding. In most cases, the need to compound is discovered during data modeling.
Regards,
Debjani.........

1:N relationships within a dimension

We are using OBIEE 10.1.3.3
I have a request from users where they want attributes within a dimension where those attributes have a 1:N relationship.
Example, Sales is dimensioned by Customer and Time.
The granularity of the Sales Fact is Day and Customer.
Now each customer can be know by different names and that attribute is known as Customer Synonym. There is a 1:N relationship between Customer and Customer Synonym. The users want to see both Customer and Customer Synonym and also query sales. When I add the Customer Synonym table within the same logical table source and run a query,the Sales numbers are doubled counted where there are more than one Synonyms. To avoid confusion we have trained users about this issue. However, I would like to figure out a better way to avoid the double counting. I cannot create a dimension out of Customer Synonym because the grain of the sales data is customer.
Is there a better design pattern within OBIEE to address this issue ?
Any suggestions would be appreciated.

Ya got your requirement,I got an idea or think its a suggestion lets give a try
If you know SQL coding and as you said they are alternative names,you can do 1 thing instead of displaying both names as different columns.You combine them in SQL it is concatenated like this
customer_name||' '||customer_synonym so result=AB Corporation Alpha Beta Corporation Barclay Corporation
so end result AB Corporation Alpha Beta Corporation Barclay Corporation 100
but this can be written in the query itself or may be as a condition you should give a try and play around.
Hope it helps you.
Cheers,
Kranthi

One-to-many relationship within one bean

hello all,
Does S1 support a container managed one-to-many relationship to itself?
I used the verifer to verify my DD and the error is reported. (this prototype is migrated from weblogic6.1 and I use the S1 migration tool for the DD generation)
-----------------database schema-----------------
CREATE TABLE t_class_a
c_name VARCHAR2(255),
one_class_a_for_ma2918_id VARCHAR2(32), /* untruncated name: one_class_a_for_many_class_a_id */
object_id VARCHAR2(32) NOT NULL
CREATE UNIQUE INDEX t_class_a_id_PK ON t_class_a ( object_id );
ALTER TABLE t_class_a ADD ( CONSTRAINT t_class_a_id_PK PRIMARY KEY ( object_id ) USING INDEX );
ALTER TABLE t_class_a ADD ( CONSTRAINT FK_0 FOREIGN KEY ( one_class_a_for_ma2918_id ) REFERENCES t_class_a ( object_id ) );
---------------------------ejb-jar.xml------------------
<abstract-schema-name>ClassABean</abstract-schema-name>
<cmp-field>
<field-name>objectId</field-name></cmp-field>
<cmp-field>
<field-name>name</field-name></cmp-field>
<primkey-field>objectId</primkey-field>
<relationships>
<ejb-relation>
<ejb-relation-name>manyClassA_oneClassA</ejb-relation-name>
<ejb-relationship-role>
<description>optional</description>
<ejb-relationship-role-name>OneClassA-in-manyClassA_oneClassA</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>ClassAEJB</ejb-name></relationship-role-source>
<cmr-field>
<cmr-field-name>manyClassAsForOneClassA</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type></cmr-field></ejb-relationship-role>
<ejb-relationship-role>
<description>optional</description>
<ejb-relationship-role-name>ManyClassA-in-manyClassA_oneClassA</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>ClassAEJB</ejb-name></relationship-role-source>
<cmr-field>
<cmr-field-name>oneClassAForManyClassA</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
</relationships>
-----------sun-cmp-mapping.xml--------
<sun-cmp-mapping>
<schema>mySchema</schema>
<entity-mapping>
<ejb-name>ClassAEJB</ejb-name>
<table-name>T_CLASS_A</table-name>
<cmp-field-mapping>
<field-name>objectId</field-name>
<column-name>OBJECT_ID</column-name></cmp-field-mapping>
<cmp-field-mapping>
<field-name>name</field-name>
<column-name>C_NAME</column-name></cmp-field-mapping>
<cmr-field-mapping>
<cmr-field-name>manyClassAsForOneClassA</cmr-field-name>
<column-pair>
<column-name>T_CLASS_A.OBJECT_ID</column-name>
<column-name>T_CLASS_A.ONE_CLASS_A_FOR_MA2918_ID</column-name></column-pair></cmr-field-mapping></entity-mapping></sun-cmp-mapping></sun-cmp-mappings>
I beleive the migration tool missing the cmr-filed mapping for the oneClassAForManyClassA relation role.
but even if I add this mapping it still can't pass the verifiy.
So do I miss any thing or I can conclude S1 not support this one-to many self relation?
Any hint would be welcome.

It does.
There is a known problem with parsing self-referenced relationship info - the one side (with <multiplicity> Many) must be the first in the <ejb-relation> entry.
Regards,
Marina

Relationships in Address Book entries

Are there any applications which make use of the relationships within the OS X address book entries? I'm talking about the ability to specify one's brother, spouse, parents etc...
Does this field actually serve a practical purpose for anything?
I'm just curious
Terence

Address Book imports & exports data in "vCard" format, a standard that is widely used & understood by many applications. This more or less defines how the data fields are structured & provides for such things as an open ended method for defining fields beyond the obvious ones like name, address, phone number, etc.
In Address Book, if you click & hold on a field like spouse, you get a popup menu with a few options, like going to that person's card or doing a spotlight search on their name. Since this is open ended, you can create any 'relationship' field you want & use it with these popup options. What's more, Apple provides the ability to define new options for the menu & a way to pass field data to them, which allows developers (including everyday users with some knowledge of AppleScript) to add plugins to increase the functionality of the application.
I'm not aware of any plugin that extends the functionality of relationship fields ("related names" in AppleScript terminology), but it should be possible to create them in much the same way other plugins are created. If you are interested, you might want to check out the structure of the script plugins Apple offers (see Apple - Software - AppleScript - iCal) or of third party ones (see burger locator for a silly but educational example).

Delete Relationships via API

Can anyone tell me the correct method for deleting relationships within the repository using the API? It seems to me that deleting one end of a relationship would null-out the OTHER_RELATIONSHIP_END_REF value on the other end of the relationship and then the other end would have to be deleted separately but that doesnt seem to be the case. I have tried to retrieve the other end after deleting the first end and gotten a NO_DATA_FOUND exception. However, if I do not delete the other end then Designer throws an exception regarding a null value in the TO_ENTITY_REFERENCE property of the end I attempted to delete. I have taken steps to ensure the entities on both ends of the relationship are checked-out prior to performing the delete but I do not seem to be able to come up with a combination of deletes that completely removes the relationship.
Any help would be greatly appreciated.

I think I've solved my own problem: deleting one end of the relationship causes the other end to be deleted automatically -- nice.

Synchronising MDM with R3 | Relationships

Hi ,
Got a question for you folks . Lets say we make parent-child relationships within the same table . We can see the relationships in the data manager and also can manipulate it (adding more children to parent or removing a few from the parent or restructuring the multiple hierarchy ) . Now can this restructuring be directly pushed as it is in the R3 system ? Basically can we syndicate relationship alterations done in MDM to an R3 system and bring it in Sync to the changes done in the MDM system ?
Regards
Deepak Singh

MDM Cosolidate master data not master schema from external system and then send data back to R3 system. Schema design is independent of both the system in MDM and R3. So as per my knowledge there is no possibility for the same.
BR,
Alok

Copying Standard PS proj to standard PS Proj and keep all the relationships

Hi,
Not sure if i even have the correct forum or not but sure here goes.
I am trying to create a new Standard Project with all its WBS Elements (31 or so) all its Networks (31 or so) by copying an existing Project definition.
I have set up the New standard project with its WBS elements.
I can copy each Network to its appropriate WBS Element and the relationships within each network are maintained. However the relationships between each Network are not. Is there a way to copy a full set of networks and have the inter network relationships maintained as there is a lot of work in setting up each of these new standard Project definitions.
Dave

Hi David,
Since there is no function to copy the Standard Project into another as a whole, I doubt if the relationship will be copied.
A simple way to get around this will be to create a Project from the Operative Project and handle changes thro Validation & Substitutions
Regards

Basic questions on data modeling

Hi experts,
I have some basic questions regarding data modeling within MDM. I understand the available table types and the concept of lookup fields. I know that the MDM data modeling concept is different to the relational concept. But having a strong database background my first step was to design a relational data model which I would like to transfer to a MDM repository. Unfortunately I didn't found good information material on this. So here are some questions maybe you can help me:
1) Is it the right approach to model n:m relationships with multivalued lookup fields? E.g. main table Users with lookup field from subtable SapAccounts (a user can have accounts in different SAP systems, that means more than one account).
2) Has a record always be unique in MDM repositories (e.g. should we use Auto ID's in every table or do we have to mark a combination of fields as unique)? Is a composite key of 2 or more fields represented with marking these fields as unique?
3) The concept of relationships in MDM is only based on relationships between single records (not valid for all records in a table)? Is it necessary to define all relationships similar to the relational data model in MDM? Is there something similar to referential integrity in MDM?
4) Is it possible to change the main table to a sub table later on if we realize that it has also to be used as a lookup table for another table (when extending the data model) or do we have to create a new repository from scratch?
Thank you for your answers.
Regards, bd

Yes you are correct. It is almost difficult to map relational database to mdm one. But again MDM is not 'just' a database. It holds much more 'master' information as compared to any relational db.
1) Is it the right approach to model n:m relationships with multivalued lookup fields? E.g. main table Users with lookup field from subtable SapAccounts (a user can have accounts in different SAP systems, that means more than one account).
Yes Here you need to use MV look up tables or can also try Qualifier tables if it gets more complex
2) Has a record always be unique in MDM repositories (e.g. should we use Auto ID's in every table or do we have to mark a combination of fields as unique)? Is a composite key of 2 or more fields represented with marking these fields as unique?
Concept of uniqueness differs here that you also have something called Display Fields (DF). A combination of DF can also be treated as Unique one. For instance while importing records if you select these DF as a combination, you will eliminate any possible of duplicates based on this combination. Auto Id is one of the ways to have a unique id once record is within MDM. While you use UF or DF to eliminate any possible duplicates at import level
3) The concept of relationships in MDM is only based on relationships between single records (not valid for all records in a table)? Is it necessary to define all relationships similar to the relational data model in MDM? Is there something similar to referential integrity in MDM?
Hmm... good one. Referencial Integrity. What I assume you are talking is that if you have relationships between tables then removing a record will not be possible as it is a foreign key for some record. Here MDM does not allow that. As Relationships within MDM are physical and not conceptual. For instance material can have components. Now if material does not exist then any relationship to components is not worthwile to maintain. Hence relationshsip is eliminated. While in relational model relationships are more conceptual. Hence with MDM usage of lookups and main table you do not need to maintain these kind of relationships on your own.
4) Is it possible to change the main table to a sub table later on if we realize that it has also to be used as a lookup table for another table (when extending the data model) or do we have to create a new repository from scratch?
No. It is not possible to convert main table. There is only one main table and it cannot be changed.
I went for the same option but it did not work. What I suggest is to look up your legacy system one by one and see what fields in general can be classified as Master, Reference, Transactional - You will start getting answers immediately.

How do you update multiple files in P6?

I have 4 project schedule files to update, all of them are part of the same project. Each file is one area of the project. There are relationships within each file, but there are also relationships among the files. So, if for example you update an activity and press F9, it may affect an activity that is on another file. What is the the best approach to update a project schedule like this in P6? Do you open each file, update it and then press F9? or, do you open all of the files, update and then press F9 with all the files open? Thanks.

I have 4 project schedule files to update, all of them are part of the same project. Each file is one area of the project. There are relationships within each file, but there are also relationships among the files. So, if for example you update an activity and press F9, it may affect an activity that is on another file. What is the the best approach to update a project schedule like this in P6? Do you open each file, update it and then press F9? or, do you open all of the files, update and then press F9 with all the files open? Thanks.

Creating a PDF with Bookmarks using Excel

Hello All,
I've been attempting to find an means of producing a PDF document from an Excel workbook with the resulting PDF displaying a bookmark tree which included parent/child relationships. I am running Excel 2010 and Adobe Acrobat X Pro.
At present, I am saving the workbook as a PDF document and then opening the PDF in Adobe in order to create the bookmarks. The bookmarks are created using the "New Bookmarks From Structure" option in Adobe and then choosing "Worksheet" as the structure element. The bookmarks are displayed in a tree but there are no parent/child relationships within the tree. Each member of the tree simply listed as the worksheet names were.
My goal is to display each rollup entity and its various children. The parent and the child entities are all individual worksheets within the source workbook. I have not been able to figure out how to structure my Excel source to make this happen in Adobe. Can anyone offer any insight? Thanks in advance for your help!
Jared

I've been looking for the same answer.
After I've enabled Acrobat on my Excel, and click preferences, then the whole programs crashes.
I found a couple of updates here http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611 which I am going to try out now... ifilter
Also check out this http://support.microsoft.com/kb/2800094.

Multi-query reports in Reports 3.0

When I run multi-query report in Reports 3.0 the report runs
correctly when I first load the report. However, when the report
is run for a second time the sub-queries do not appear to execute
and the report does not give a complete output, if any.
null

Hello Mike,
Whenever you work on multi-query reports you have to set all
the relationship within the tables. If you have not specified
then specify within the where clause.
Try this. I hop your problems get solved.
From Subash.
Mike Donnerstag (guest) wrote:
: When I run multi-query report in Reports 3.0 the report runs
: correctly when I first load the report. However, when the
report
: is run for a second time the sub-queries do not appear to
execute
: and the report does not give a complete output, if any.
null

SQL for Parent-Child Hierarchy

Please suggest which would be best way to achieve the below logic.
SQL to pick up parent child relationship within same table with a certain logic.
Example:
mod_product_number     Product_Hierarchy
H555888     PH05678
H888987     H555888
H8889     H555888
H9955     H555888
H999999     H555888
P6666     H999999
P5555     H999999
Example: I expect the rows with H8889,H9955 & P6666 & P5555 to be sub-category values value for product hierarchy H555888.
If there are rows with H8888987 as Product_hierarchy, we will pull up those rows too for product hierarchy H555888.
The extra condition is we drill down only on 7 character mod_prod_number not on 5 character mod_prod_number. We pull out all sub category mod_prod_number for all distinct Product hierarchy.

You can use Hierarchical Queries
See.. http://docs.oracle.com/cd/E11882_01/server.112/e10592/queries003.htm
select lpad(' ',2*(level-1)) || to_char(trim(t.mod_product_number)) prod,
SYS_CONNECT_BY_PATH(t.product_hierarchy, '/') "Path",
LEVEL
from temp_table t
start with trim(t.product_hierarchy) = 'PH05678'
connect by prior trim(t.mod_product_number) = trim(t.product_hierarchy);
.     PROD          Path                    LEVEL
1     H555888          /PH05678                1
2       H8889          /PH05678 /H555888           2
3       H888987     /PH05678 /H555888           2
4       H9955          /PH05678 /H555888           2
5       H999999     /PH05678 /H555888           2
6         P5555     /PH05678 /H555888 /H999999      3
7         P6666     /PH05678 /H555888 /H999999      3

How to reflect DB changes to my Java objects?

Hi All,
I'm new to TopLink so please be patient... maybe my question is a bit silly.
I created an offline DB and a Toplink map and generated classes from my tables.
I added some foreign keys to the online db and I want them to reflect at the Java classes but everything I do doesn't regenerates the Java classes. I refreshed the offline db but the java object remains the same.
How can I regenerate them?
Thanks

Options
1. You could delete all the POJOs and redo the TopLink mappings from your amended DB (but you will lose any changes you've manually made to the POJOs)
2. You can make the changes manually (just follow the example of other foreign key relationships within you current code)
3. Start a new temporary project create the TopLink mappings from your amended DB and merge any POJOs you want into your existing POJOs
Regards,
Mike

Aperture 3 library won't show repair library screen

I tried to update my Aperture 2 library today (470GB) and everything worked just fine till it got to 96% and stayed at this percentage, so i force-quit Aperture. The library now only shows 400GB but I have one still in the old version with the rest of the pictures (according to the size). The new library opens but most of the thumbnails are screwed up (just vertical lines or black screens), so I wanted to repair the library (I also cannot import it into a completely new library) but holding down command & option while double-clicking the library just opens up the library instead of going to the repair window. Any ideas on how I can force it to come up?
EDIT: Totally forgot: It says in the activity that it is updating the library and going through the photos. No idea what it is doing, I'll let it run for now but it'll take some time till I know what it does, since it tells me it needs to go through >10,000 objects.
Message was edited by: Pfenya

Sorry that was not helpful. I am using the trial version only and HELP states 'Aperture provides a few methods for reconstituting your Aperture library and the file relationships within it.'
To repair or rebuild your Aperture library : - following by empty white space.
Having looked through Aperture Commands under the Aperture Menu I cannot find any likely entry other than I have already mentioned.
Good luck.

Relationships within BPR

Similar Messages

Maybe you are looking for