Scope of Business Objects in MDM

Hi MDM Experts
What is the scope of Business Objects in MDM,
How MDM can leverage its features and functionalities by using Business Objects.
Regards
Gaurav

Hi
I know that "MillerCoors" was using SAP MDM & BO DQ
The comparison between SAP MDM & BO DQ capabilities are listed below. Putting it straight.
1) Both have data quality capabilities. Validations for SAP MDM & Transforms for BO DQ. But the capabilities of BO DQ are much stronger than SAP MDM
2) Both have de-duplication functionalities. While SAP MDM does not provide fuzzy matching capabilities, you more effectively find duplicates using BO DQ. But, merging of records, selecting individual fields for merged record is not possible in BO DQ. SAP MDM has an upper hand here.
3) Data enrichment is not possible in SAP MDM. BO DQ has built in dictionaries for Address check, zip codes etc.
Both tools have capabilities to connect to third party service like D&B. SAP MDM via the Enrichment Controller & DQ via web services.
4) Data Management workflow capabilities of integrating users, data stewards in the data quality process is better in SAP MDM.
Based on these points, if one is going for a BO DQ + SAP MDM approach, to get the best results we can design all the data quality validations, transformations, de-duplication, enrichment in BO DQ & the master data management activities like data governance, business process etc in SAP MDM.
Read the below weblog for more information
/people/ketan.phanse/blog/2008/11/27/taking-the-best-from-bo-dq-sap-mdm-worlds

Similar Messages

Business Object Data Services (BODI) without SAP MDM?

Hi,
From an architectural point of view; do you always have to use SAP MDM when you want to use the Business Object Data Services (e.g. for data validity checks when creating customers)?
Or can you use Business Object Data Services in combination with SAP ECC without MDM?
Best regards,
Marius

All Depends on your business needs.
1) As in if you want to use most effective cleansing (BODS contains inbult infor for Adderess cleansing) along with some data governance(Validation, assignments,MDM Workflow) I would say fo with BO-MDM Integration.
2) Here I am not sure via BODS - ECC you can handle ongoing maintainance , it is supreb for first time data load.
so it is better if you use ECC-BO-MDM ---> BI/ECC for smooth transition through out landscape.
3) Here also try to check the data structure compactiblity between BODS and ECC as per their version, it can also create a big impact.
Hope these points can clear many doubts
Rgds
Deep

Sap mdm or master data services from business objects ...

hi
i knew sap is acquiring business objects , but BO is having a software package called master data services , whose functions are same as sap mdm which is already available for few customers , then how sap is planning on these two procucts. are these two products going to be mixed or only one will be there in market . any body any idea ?
or . master data services is going to be an addon to sap mdm ?
akhil
Edited by: akhil k on Jan 20, 2008 2:13 AM

Hi Akhil,
Please go through these link i think they may help:
1. ttp://www50.sap.com/m1/global/bobj/le/packages/mdm.htm
2. Enterprise master data management (MDM) should always be the objective of any ... This approach extends Approach 4 by exposing master data services in the ...
http://www.b-eye-network.com/view/5051
3.Solving the SOA Data Dilemma with Master Data Services
http://www.b-eye-network.com/view/6034
Akhil, from 3rd link it looks like that this MDS( master data services) is same as MDM just the thing to be noticed is MDS term is used with SOA and MDM is an independent tool to provide MDS.
Rewards if found helpful.
Regrds,
Alok

MDM OR BUSINESS OBJECTS OR WEB DYNPRO or SOLUTION MANAGER

gurus can anyone tell me is it helpful to learn MDM or BO or WEB DYNPRO or SOLUTION MANAGER for crm consultants? To what extent this technologies are useful for crm consultants.

Hi Shiva,
What kind of SAP CRM Consultant Role you are referring to ? Is it Functional Consultant, Technical Consultant or a Techno Functional Consultant ?
For a Functional Consultant - SAP Solution Manager and Business Objects makes more sense, while the a basic understanding of Technologies like (Web Dynpro ) is also required.
For Techno Functional Consultant - Web Dynpro understanding is very important followed by MDM, Business Objects and Solution Manager.
Hope this has cleared your doubts and thrown some lights on your question.
Hope this helps.
Thanks,
Samantak.

Need information on Business Object XI R3 with Dashboard Design (Xcelsius)

Hi,
we are planning to install Business Object XI R3 with Dashboard Design (Xcelsius). In order to do this SAP has advised that we require Netweaver 7.0 Enhancement Pack1, Support Pack5.
Could you please let us know if it would take to upgrade and also any dependencies (do we also need to upgrade ECC, BI, SRM or Portal). we did not install EHP for any of the components in our landscape except solution manager (EHP1 SPS22).
Please help in providing the information.
Thanks,
Mohan K

Hi Jeff,
thank you very much for your prompt help.
But my query is do we need to upgrade any of the SAP components (ECC, SRM, Portal, MDM or SOLMAN) which are present in our landscape. no SAP components is of relase EHP except SOLMAN system.
Please suggest.
Thanks,
Mohan K

Access restriction for business objects in same solution

Hi All,
Requirement: I have one single solution with 4 modules. 1 module is common and other 3 are industry specific. When i roll it out to a customer, i what restrictions on Business Objects. So that i can roll out single or combination of modules as per requirement.
Hence the configuration requirement would be as follows:
   We need one core configuration for the entire solution which will have the Common Scope part included in it.
   We need industry wise configuration ( could be business configuration )
   Script level screen restriction.
We tried creating a BAC element with Business Topic and Business Options and tried to link BO's to it. But we are finding a problem with this solution, even a user will be able to change the configuration and get access to a module which he didn't pay for.
Regards,
Rudhra Udayakumar
[email protected]

Hello Rudhra,
If the switches are in the BC every user with access to the BC can switch the modules on and off.
As we do not support the interaction / referenceing between different solutions (at least not in the near future ) you need to put all you need in one solution.
I understand that you want to make a reuse of the Common module somehow.
My suggestion would be
Develop the Common in a Solution Template
Develop each industry specific in an own solution
(Re-)Deploy the Common Solution Template to each of the industry specific solutions
You can then sell the industry specific solution one by one and have only one development source for the Common module.
HTH,
   Horst

DTO, Business Objects and architectural layers design

Hi everybody,
What would prevent one from using Business objects (properties + getters/setters and bevaviour related to a business entity) thru all tiers of a J2EE Web application ?
Example : DAO layer populates BO properties, Business layer uses BO behaviour , web layer stores BO in some scope (request,session,...) for view presentation of the BO properties.
Compared to a DTO/VO (only properties, no behaviour) solution :
- If the application is distributed the BO solution adds serialization overhead (possibl performance bottlenecks) if BO's are large objects.
- If there is requirements for clustering , storing large BO's in session adds session replication overhead.
- BO solution breaks layer isolation , but practically speaking what could be the consequences of it ?
- Some BO properties need formatting for text deiting by the views and cannot be displayed as is.
- BO solution is a more OO approach than using only data objects
What other arguments can you think of ?

"Session" data applies to the session. Thus when I
order a book and it is added to my shopping cart the
session data might be used to store that information.
But that data in of itself is not a "business
s object". It is, by definition, session data.Ok conceptually speaking it is session data, but from
a technical point of view you need an Object instance
of some sort to hold that data.No actually you don't.
There are a number of ways to maintain session data. With tradeoffs between each.
What I was talking about (which does not mean I think
It is a good idea...) is using the BO properties for
holding that data and storing the BO instance(s) in
the session.
And I still don't see that this is a "Business Object". No more so than a security key is a "Business Object".
The best term is session data and you might have different groupings (data not behavior) within that.
Exactly what behavior do you envision?Any computational behaviour that uses the BO
properties and is needed to implement a use case.
This behaviour is used to calculate data that is not
persisted by the DAO as is but rather computed from
m other persisted data.
Give me an exact example.
For example it would be quite reasonable to have a DTO that represents a "rectangle" and that DTO would have a height and width and the DTO would have a method that return the area (multiplying the two data points.)
Conversely my previous example of the zipcode, the DTO should NOT have a method to validate that the zipcode exists although it could validate that it has the correct form (5/9 digits in the US.)
The problem is coupling. If the BO needs the
database layer (see the zipcode example above) then
the GUI layer is going to need the database layer is
well. Even though the GUI will never use the
database layer.I understand that this coupling applies to
distributed architectures where you package your
applications in different jars/wars/ears. In this
case If BO's ared used thru all layers, The GUI
(web) layer needs the data access layer jars even if
it will never use it.
This clearly adds coupling.
But in the case of a collocated application (a single
war) it does not change anything.
No. The point is not how the application is architected.
The point is that the GUI layer is then dependent on the database layer internals.
Consider another example, the DTO is produces a formatted xml string using a XML library. Now you need to create the database layer for the system. The database layer does not need the XML at all. And yet just to compile the database layer you are going to have to provide the XML library. This represents coupling that serves no purpose. And although in very small projects it might be convienent in larger projects coupling like that will cause problems and confusion.
And? Are you suggesting that the BO should do the
formatting?No I mean that DTO/VO's could have either text
formatting/editing methods or property types (e.g
String formatted property for a date) that facilitate
the work of the presentation layer. And most of the time that is going to be incorrect.
"Formatting" for a web page is likely to be different than for a printed report. And for a backend system it might need XML which is still a different format. Adding all of that to the DTO is not the way to do it. (In the same way that the database and gui code should not be intermixed.)
I would not put
any similar formatting behaviour in the BO. That's
why I consider this issue while comparing BO and
DTO's
- BO solution is a more OO approach than using only
data objects
No it isn't.
An object that prints itself is not more OO than one
that is printed.
I thought one of the purpose of OO programming was to
group behaviour and dataCertainly, but it doesn't mandate that one form of grouping is better than another. After if that was the sole concern then why not have just one object for the entire application - that is one way to "group" it.

Business Package for MDM 5.5 SP3

Hi
We are struggeling a little bit with the connection to the MDM Server.
Portal version = NW04 Stack14, MDM version = 5.5 SP3 and the Business Package for MDM has been installed in the EP.
SAP EP on a single server, MDM on a single server.
In the documentation for the Busines Package for MDM at page 4 where we are "Creating Portal Systems Objects for Custom Repositories", I have a question regarding the MDM server references.
Step 1. System adm - System conf - System Landscape - My folder - New - System - MDM Server - Next
Step 2. System name= MDM, ID=mdm, prefix=com.xx, Language = English, Description = My test - Next
Step 3. MDM Server = ???? The host of which the MDM server is running or the MDM server itself - and which password should we use, The password for the host, the MDM server or the database????
Regards
Kay-Arne

Hi.
I managed to solve this issue by myself:)
I think the error is that I used the system templates from sp2....
Either way, i created a system from par "com.sap.pct.mdm.tech.systems" and filled in name, id, prefix, language and description. From there I opened the object, selected:
Usermanagement
    - Usermapping: admin,user
Connection properties
    - MDM 5.5 Host Server: Myserver
    - Repository Language: English [US]
    - Repository Port:     2005
    - Schema Language:     English [US]
System Aliases:
    - My_MDM
Saved the object
Maintained the userid and password through Personalize
Connection Test - and it works
From there I created a iView (MDM) and followed the wizard
Regards
Kay-Arne

New to Business Objects

Hi Gurus!!
I have been working in SAP MDM area for 3 years and now I want to enrich my technical skillset.In order to so I thought it would be good to learn BO.
So could you experts pls guide me on what is BO all about , and how can I learn it?
Thanks in advance!!
Ravi

Hi,
Please go through this blog to get some idea about BOBJ tools and installation.
/people/community.user/blog/2008/11/17/businessobjects-enterprise-xi-r2-beginner-tutorial
After reading this blog Please go through help.sap.com to get more documents about BOBJ. download trail version of BOBJ and start working with it.
please go through these links also.
https://www.sdn.sap.com/irj/boc/business-objects-for-sap?rid=/webcontent/uuid/20f83c7e-3f2a-2c10-7dbf-a5ec14611a1e [original link is broken]
https://www.sdn.sap.com/irj/boc/business-objects-for-sap?rid=/webcontent/uuid/a02d2792-452a-2c10-7c8f-ddd50dad779b [original link is broken]
Thanks,
SK.
Edited by: Vallabhaneni SK on Jun 17, 2009 4:04 PM

Business Object Data Services

Hi! Is BO Data Services part of the MDM installation? or do we have to purchase this separately?
Regards
SF

Generally, SAP BusinessObjects Data Services and SAP NetWeaver MDM have separate license tags, but as of 2010, there is also a combined license for SAP NetWeaver MDM and SAP Business Objects Data Services. For details, please contact your Account Manager.
Best regards,
Markus

Solution Manager and Business Object

Hi all,
Have you seen any specific information (from SAP or others) indicating how SAP plan to integrate the Business Object Products into Solution Manager?
First of all I need information about the SOLAR01/02 transactions (e.g. will separate Business Objects development objects become available? Will ASAP be extended to include Business Objects Projects?)
Secondly I would like to know if the Operations scenario also will be enhanced in order to include Business Objects Solutions?
Any informations/links/etc. would be welcome
Thanks in advance
Peter Michael

Hi,
SOLAR01 - Business Blueprint
SOLAR02 - Configuration.
Implementation projects are projects to select and implement business processes in an SAP landscape. A Business Blueprint documents these business process requirements of a company. Collaborative business processes involve several companies
The Business Blueprint provides a common strategy of how your business processes are to be mapped into one or more SAP systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of an SAP solution implementation.
A Business Blueprint comprises the following structure elements in a hierarchy:
Organizational Units
Master data
Business scenarios
Business processes
Process steps
You assign content, for example, project documentation, Business Configuration Sets or transactions, to individual structure elements, in the SAP Solution Manager.
SOLAR02(Configuration) configures the process requirements specified in the Business Blueprint phase, in the system. If you use objects from the Business Process Repository in your own structures, some of them are already assigned to transactions and BC Sets. If you create structures independently, i.e. without objects from the Business Process Repository, you can assign transactions in the transaction Business Blueprint. You can assign BC Sets, IMG objects and test cases/business test requirements, in the transaction Configuration.

Career:Shift from ABAP to BW-Netweaver after business object takeover

Hi all,
Am an ABAPer with one and half years of experience.I will be thankful if sombody will tell me If its appropriate to move into BW-Netweaver as i heard BUSINESS OBJECT is likely to replace BW-Netweaver in near future.
Thanks.
Edited by: sandeep pande on May 12, 2008 7:18 PM
Edited by: sandeep pande on May 12, 2008 7:32 PM

Dear sandeep pande ,
BO was brought up by SAP and It will soon be included in SAP BI in next recent versions.SO its better to join BI. as it has more scope these days/
YOu should know the advantages of BI over BO
BO is the reporting toll of data warw house
BI is itself a data ware house.
the next generation SAP BI will be using BO as reporting tool instead of BeX.
BO is the reporting toll of data warw house.
on the front end it has CrystalReports.
this suit will be used in SAP as front end for EIM.
the latest version of BO is BO 11. 3.
BI is itself a data ware house.
the next generation SAP BI will be using BO as reporting tool instead of BeX.
For More Information check the following link
/people/kuhan.milroy/blog/2008/03/11/introduction-to-business-objects-suite-of-technologies
/people/ingo.hilgefort/blog/2008/02/19/businessobjects-and-sap-part-2
/people/ingo.hilgefort/blog/2008/02/07/businessobjects-and-sap-part-i
http://sap.blogs.techtarget.com/category/teched/
For knowing Overview of BI and go through BI certification follow these
If you are going to Start BI 7.0 courses
you could follow the books
TBW10 Datawarehousing concepts
TBW20 Reporting
TBW42 Adavnced Data warehousing concepts (authorization,Broadcasting,etc)
TBW45 Integrated Palnning
Online courses on APD,XI
Tamong these,TBW10 and TBW20 will be sufficient for you to start and know basic concepts
Overview of BI
http://www.sap.com/platform/netweaver/components/bi/index.epx
For more information please
refer these links
http://www.psimedia.ws
http://www.sap.com/uk/services/education/courses/bw.epx
http://www50.sap.com/useducation/curriculum/print.asp?jc=1&rid=285
http://www50.sap.com/useducation/curriculum/print.asp?jc=1&rid=458
http://www50.sap.com/useducation/certification/examcontent.asp
http://www50.sap.com/useducation/certification/curriculum.asp?rid=506&vid=5
http://www50.sap.com/useducation/certification/curriculum.asp?rid=420
http://csc-studentweb.lrc.edu/swp/Berg/BB_index_main.htm
Hope it helps,
Regards
Bala

Business Object Repository ( B O R )

Can some one please send me some data or links from where I can get data on Business object repository .

Hi,
SAP's Business Object Repository gives you an improved way to integrate business processes with external partners -- an increasingly necessary ability in the burgeoning e-marketplace economy.
The age of e has had a profound effect on the IT industry. Not only has it changed our way of life, but it has also forced systems such as SAP to embrace a new era of openness. Marketplace demands for flexible automation of inter-business workflow and intelligent data exchange have forced formerly very proprietary ERP systems to begin helping customers integrate with other companies and with e-marketplaces data formats. For the first time, companies must expose their business processes to the outside world.
In order to achieve this openness, SAP provides a technical infrastructure for the R/3 product, the Business Object Repository (BOR), which provides a simple yet powerful mechanism for external systems to trigger core business processes (such as placing an order) without concern for the underlying data structure. This level of abstraction is beneficial because it decouples R/3 from the external system. Either system is therefore free to change its internal business processes without affecting the other. SAP provides this technical infrastructure using a component-based view of its system. Each component or object provides a view of the data and the business processes that interact with that data. External systems can access this data via BAPI methods, which in turn access the underlying data structures of the system. It is the responsibility of the object and the BAPI to ensure the integrity of the data. This encapsulation of the data not only lends itself to external interfaces, but by using objects from within SAP, you can greatly reduce implementation, testing, and maintenance effort via the promotion of code reuse.
Business Objects
A business object is a problem-domain entity that you model in the SAP system, such as SalesOrder, BillingDocument, and Employee. The BOR stores all the objects in the R/3 system. The repository is a group of all the objects in the R/3 system. If the focus of objects is to model atomic business processes then it can be said that the BOR provides an enterprisewide view of business processes. By designing your ABAP code to fit your business processes you increase the ability of that code to flex when those processes are altered or integrated with external systems. This had made the object-oriented approach, which the BOR provides, essential to developing inter-business or e-business functionality.
Attributes
A business object is primarily represented by its attributes. You perform actions, such as create, update, or delete on the attributes by calling the methods of the object.
Attribute NetValue of Object BUS2032 (SalesOrder).
The majority of attributes are data-dictionary fields (for example, the NetValue attribute is defined by VBAK-NETWR). When you access an attribute of an object, you execute a SQL statement that retrieves the corresponding field in the database.
Definition of attribute NetValue.
You can also define attributes that do not exist in the data dictionary. These attributes are called virtual attributes. For example, a business partner has an attribute called BirthDate that is stored in the data dictionary. You can add a virtual attribute to the BusinessPartner object called Age. The age of a business partner is not stored in the database, but you can calculate it using the current date and the birth date of the business partner. If you implement the ABAP code that calculates Age, every time you access the Age attribute, the code executes and returns the business partners age.
Definition of virtual attribute Age.
This is an excellent example of one of the tools that a component-based approach provides. The external system does not need to concern itself with how to gather the data that it requires. The calling program needs only to access the attribute for the data to be returned. This is how business objects decouple the calling program (whether it be in R/3 or external to R/3) from the internals of R/3.
The BOR lets you define multi-line attributes. These attributes define one-to-many relationships between an object and other fields. These objects can be defined in the data dictionary or can also be virtual attributes.
An attribute that uniquely defines an object in the system is called a key attribute. In the case of a SalesOrder, the key attribute is VBAK-VBELN (the TableName and FieldName). It is not uncommon for an object to have several key fields. An example of this is object is the SalesArea (BUS000603) object type which has SalesOrganization (TVTA-VKORG), DistributionChannel (TVTA-VTWEG) and Division (TVTA-SPARTE) as key fields.
Methods
As mentioned earlier, the methods of an object represent the actions you take with objects attributes. An action in this example would include retrieving the status of one or more sales orders based on specific criteria. Methods are analogous to function modules in that they have importing and exporting parameters as well as exceptions, which you view by selecting a method and clicking on the toolbar button. This allows external systems (or internal developments) to pass and accept parameters from these methods just as if they were using function modules -- allowing external systems to call methods.
In Figure 4, the methods shown with the green LED are BAPIs that are called specifically from external systems. They can, however, be called from within the system itself. The method shown with the stop sign is obsolete, but retained for backward compatibility, and should not be used in new developments.
Methods of SalesOrder.
Delegation and Subtyping
One of the most complex concepts in object-oriented development is that of inheritance. This concept lets you extend core functionality by creating a child of the parent object that inherits all of its attributes and methods. For example, a Manager object is a subtype (child) of the Employee object. The Manager object has all the attributes of an Employee object (such as EmployeeID or Name) but also has some extra attributes (such as CompanyCar or ParkingSpace). SAP has not implemented inheritance in the BOR. However, it has provided subtyping and delegation, which offer an alternative way to extend R/3 functionality.
Subtyping
A subtype of an object is another object whose creation is based upon a parent object (see the preceding manager/employee example). The subtype maintains references to all the attributes and methods of its parent object. This means that any methods and attributes defined on the parent can be executed and accessed on the child object. I have often heard less-experienced developers refer to subtyping as copying the parent object. Although the effects can be similar, in order to achieve an understanding of some of the more advanced concepts, such as interface inheritance, it is important to realize that this is not accurate.
If a subtype object were merely a copy of its parent, then all the code contained within the parent would be physically copied to the child. This is not the case. The subtype simply maintains references to its parents methods and attributes. The real difference is that the subtype lets you redefine these methods and attributes. You can easily add your own business rules to the parent methods by redefining the subtypes method. In the following example, I will show why this distinction is so important.
Subtyping Case Study
As an ABAP developer at Acme Tyres Pty. Ltd., you have been given the task of implementing some security measures for the companys online store. The requirement is simple: The password must be at least six characters long.
Modifying SAP code leads to costly and complicated upgrades due to the modified code being overwritten by the newly delivered SAP code. Therefore, The challenge is finding a way of implementing the business logic without modifying SAP code.
After some investigation, you realize that the method CHANGEPASSWORD (in BAPI) on the object KNA1 (Customer) is called when customers change their passwords. All you need to do is create a subtype of KNA1 and then redefine the CHANGEPASSWORD method adding the ABAP code to ensure that the password is a minimum of six characters long. It is of course not wise to change SAP code even assuming you have the passwords, which can be provided only be SAP. After the method is redefined, you just need to implement the business rules in ABAP.
FIGURE 5 Redefinition of ChangePassword method.
It is imperative that once you redefine the method it still behaves in a similar manner. You are allowed to add extra business logic, but the method must still change the password rather than do something unexpected, like delete a customer. This is particularly important when SAP is being accessed from external systems. The external system will expect a method to provide certain functionality. The developer should take care to ensure that this expectation is met.
Delegation
Now that you have implemented a new CHANGEPASSWORD method, you need to tell the SAP system to use the redefined version of CHANGEPASSWORD and not the version that was delivered on the KNA1 object. This is similar to object-oriented inheritance but the two concepts do have fundamental differences.
Delegation for objects.
By making an entry in the delegation table, you tell R/3 that before executing a method on KNA1, it should first check if that method has been redefined on the subtype. If it has, then the system executes the redefined method . If it hasn't, then the system executes the original method. Figure 7 illustrates this process.
Execution flow for methods with delegation.
This delegation is powerful because it lets you implement your own business logic without modifying any SAP code. As long as the objects are properly delegated, your method will be executed.
Responsibility
So far I have shown you two major components of an object, its attributes and methods. The difficulty in SAP is that it has traditionally been a data-driven, procedural-development approach. The BOR is not well understood by developers and managers and thus it is shunned by those that stand to gain the most from it. If managers and developers alike would take a formalized approach to development using business objects, significant savings in the development, testing, and maintenance phases would be achieved. This is due to the high level of re-use that business objects encourage.
Having said this, when a powerful tool is put into the hands of an inexperienced person, chaos can (and usually does) ensue. If object-oriented design principals are not adhered to, then the resulting code has poor reusability and maintainability. Although an in-depth discussion of design issues is beyond the scope of this article, I will introduce in the following section one of the more fundamental design aspects of BOR programming: Responsibility.
When you are given the task of creating a method or attribute on an object, one of the most important questions you should ask is, Does this attribute or method belong on this object? This question is fundamental to an object-oriented design and the answer can make a world of difference. Answering this question incorrectly has detrimental effects on the development effort resulting in methods and attributes strewn across myriad objects, with no coherent structure. If the methods and attributes were strewn across several objects, it would be more difficult to provide a uniform interface to external systems. If an external system wants to execute a particular business process in R/3, it may need to access several business objects, thus increasing coupling and reducing the layer of abstraction between R/3 and the external system.
Lets take, for example, the requirement to be able to update a sales order. This is a common requirement and one that SAP usually implements for you. For the sake of the example, lets assume that SAP has not implemented this method. You will need to implement your own UPDATE method on one of the business objects. The question here is: Which object? This question is what I term as defining responsibility. Which object is responsible for having the UPDATE method on it? As shown in Figure 4, the answer in this cases is BUS2032 (SalesOrder). If you put it on any other object then you run the risk of no one else knowing of its existence. Next time there is a requirement to update a sales order, the developer will develop an additional method. You would then have two separate pieces of code that implement the same functionality. This duplication doubles development, testing, and maintenance requirements. On large projects, this can become a real problem and a maintenance and testing nightmare.
SAP recognizes the challenges facing developers in the e-business era. It is aware that if it wants to take R/3 to the next phase, it needs to continue evolving the ABAP language and ensure that powerful development tools are available to SAP developers.
Rising to the challenge, SAP has begun developing extensions to the ABAP language called ABAP objects (see "Introducing ABAP Objects," in the IntelligentERP feature archive for an excellent introductory article to ABAP objects by Jürgen Heymann and Horst Keller). These extensions will provide ABAP developers with a full range of object-oriented tools. Eventually, these new extensions will make BOR obsolete. However, the use of object-oriented development is sure to be an integral part of future SAP developments, regardless of where the world of e takes us.
Reward points
Regards

Data federator in business objects

Hi,
What is the use of data federator in business objects.
Regards,
G

HI,
The only option in this case is to 1) use Business Objects' Data Federator to bring XYZ data and BW (new) data together, 2) creating a relational universe, and 3) creating Crystal / WEBI reports using the relational universe; see Picture 1.
>> You can also combine the data by using a MultiProvider in BW which is access the data in BW and the data in the legacy system and an additional alternative is to move all the data into BW.
After 20 years goes by, and we no longer need to report on data housed in XYZ anymore, the environment will be turned off.
1) When this happens, wouldn't we want to remove Data Federator and the relational universe from the scenario ?
>> That depends on the approach you took
Ingo

SAP Log on into Business Objects server not working (Error FWB 00014)

Hello,
I recently installed Business Objects XI 3.1 Edge series, I am able to logon to enterprise and everything is working fine. I am even able to import roles from SAP system but I have two problems.
1. Logging on to enterprise using SAP user: I am getting the following error message when I choose SAP in the Athentication and enter SAP username and password and click log on.
"Account Information Not Recognized: All of your system's 0 Concurrent Access Licenses are in use at this time or your system's license key has expired. Try again later or contact your administrator to obtain additional licenses. (FWB 00014)".
2. Logging on to SAP system through SAP Logon pad: When I enter my username and passord in SAP system from the same server as I installed BusinessObjects I am getting a run time error.
Did any one of you had the same problem or does any one of you have any clue how to solve this?
Thanks in advance.

Hi,
I assume that you have a key for named licences (You can check this in the CMC under Licence keys).
What you need to do is to go in the CMC, navigate to Authentication->SAP->Options and select the Named users option.
Regards,
Stratos

Scope of Business Objects in MDM

Similar Messages

Maybe you are looking for