Business partner repository

Hello
i am looking for the Business partner standard respository layout and content,
Please let me know where i can find it
Thank you
Nadine

Ah, I see, in that case I'm not sure because the standard structure changes with the new versions of MDM. For example, the structure of the business repository is different in SP05 than SP06. However, you can get a pretty good idea as to what the repository structure is by looking at the mapping spreadsheet that you can get from the service marketplace at this location:
https://websmp202.sap-ag.de/~sapidb/011000358700004121872006E
If you go down to the "Installation" category and download MDM 5.5 SP06 - Business Content: Business Partner (ZIP File) then you will find the field mappings, this lets you know what fields and checks tables exist in the repository, and how to map them to ECC tables and IDocs.

Similar Messages

Can I use one Business Partner repository for Vendor and Customer?

Can I use one Business Partner repository for Vendor and Customer? or do we have to use Vendor and Customer Repository separately. How can we do that? What are the pros and cons? can any one provide some examples:

Hi Deepak
The key purpose of SAP "enabling" the facility of multiple main tables in a repository is to primarily "manage" those master data objects that are related to each other. Typical examples will be a) Customer - Material, b) Supplier - Material, etc.
While, it is pretty easy to add multiple main tables in a repository, it is also important to understand the purpose of doing so based on the business requirements.
Besides, you got to be aware that in case you are "fixing" any issues with one main table (master data object) for which you have to unload the repository, the users will not be able to use the repository that has a main table defined for other master data object. Hence, there are pros and cons of using this capability of multiple main tables.
So, it is really important to understand the "W's" - What, Why, When, Where, Who of Data modeling before actually working on the "H" - How to in the SAP MDM tool.
Hope this helps.
Regards
Neelesh

Relationship in Business Partner repository.

I need to do a relationship among the BP where each record in Main Table correspond a BP (Person or Organization).
The relationship should link the BPs as shown below:
Records
1; John
2; Mary
3; ACME
In record 1, I need to say that John is married with Mary, where Married is a type of the relationship and that Mary is Owner of the ACME, where u201COwneru201D is other relationship type.
I have tried to configure a Relationship (where the parent and child tables were the Main Table) in MDM, but I couldnu2019t to do it because the screen for this feature was locked. I need to be certified that the child link exist in the repository.
Thank you.
Evandro.

Hello Evandro,
I am listing the steps to create a relationship manually.
1. Create 2 records in the relationship table in console, one for "Married to" and the other one for "Owner". In order to do that the repository needs to be unloaded.
2. Once you create these 2 records in the table through console, load the repository.
3. Log on to the Data Manager.
4. Now as per your example, there are 3 records in the main table, namely
     JOHN
     MARY
     ACME
5. Select only one record in the record list area e.g. JOHN (where you see the list of records)
6. Then, in the record edit area, double click on the relationship tab,
7. New Window opens up.
8. HERE ALL THE OPTIONS ARE GRAYED OUT. But Select the relationship which you want to create, in our case married to.
9. Now select the record MARY in the record list area. (NOT in the pop window, but main window).
10. Then on the top bar menu, select Relationships --> Adds to Group.
11. Now close the Pop window and observe that the relationship has been created between JOHN and MARY.
Let me know if it worked for you. if not, post some more information about your problem such as where you tried to configure and what options were grayed out.
Please update.
Thanks
Shai
I need to do a relationship among the BP where each record in Main Table correspond a BP (Person or Organization).
The relationship should link the BPs as shown below:
Records
1; John
2; Mary
3; ACME
In record 1, I need to say that John is married with Mary, where Married is a type of the relationship and that Mary is Owner of the ACME, where u201COwneru201D is other relationship type.
I have tried to configure a Relationship (where the parent and child tables were the Main Table) in MDM, but I couldnu2019t to do it because the screen for this feature was locked. I need to be certified that the child link exist in the repository.
Thank you.
Evandro.

Difference between Business Partner and Customer Master repository

What is the difference between Business Partner and Customer Master repository ?
Is the Business Partner repository to be used in case CRM is also in landscape ? or Customer master repository is good enough ?
Sandesh

Hi,
If the landscape has both CRM and SAP ECC a business partner repository model should be good.
If it has ECC alone.a Customer Repository is needed.
But when there are many legacy systems which also contains master data fields, the standard business repository provided by SAP wont provide a good solution as it wont cover the legacy master fields..In this case its better to go for a customized repository and you can use the standard repository as a reference.
Thanks

Material vs. Products and Business Partner vs. Customer and Vendor

Hi,
Just wondering if there's any SAP recommendation for using 'Products' repository vs. Material repository. Similarly, is there any SAP recommendation for using 'Business Partner' repository vs. Customer and Vendor repositories.
Can anyone would like to shed some light on what is recommended with pros and cons? Any help will be highly appreciated.
Thanks

Hi Mins,
you can group the repositories in the following way:
Group 1
- Material
- Vendor
- Customer
Group 2
- Product
- Business Partner
Repositories of Group 1 are related to the corresponding R/3 (ERP) data models. The repositories cover a large part of the R/3 fields and can be used to integrate your R/3 systems with MDM as they contain import and syndication maps for R/3.
Repositories of Group 2 are related to the common CRM and SRM data model. Those repositories have been developed with the goal to integrate CRM, SRM and R/3 with MDM. Unfortunately the structure of the Group 1 repositories was not capable to fullfill this. Group 2 repositories contain import and syndication maps to all remote systems (CRM, SRM, R/3). But those repositories are not as large as the Group 1 as the first task of the Group 2 repositories was the data consolidation scenario.
There is no general recommendation which repository to use. It depends on the project setup on customer side:
- If you want to use MDM for R/3 only, it makes sense to use Group 1
- If you want to use MDM for R/3 only, but you want to consolidate your customers and vendors in one single repository, you should use the Business Partner Repository because this one can hold both object types
- If you want to use MDM for CRM and SRM, you should use Group 2
So a general recommendation could be to check the Master Data setup and landscape within your project and then to choose the corresponding repository.
Kind regards
Michael

Business content - Customer, Business Partner or both

Hi
We have a task where we need to decide which business content to choose: Customer or Business Partner. Our current requirements points out that we can fulfill 90% of the requirement by utilizing the Customer information modell in SAP ECC.
Our MDM scenario (decentralized MDM strategy) looks like this:
Customer created in SAP ECC and then sent via SAP PI to SAP MDM. From SAP MDM the customer data is then distributed to SAP CRM and other non-SAP systems.
Should we utilize both the business content (Customer, Business Partner) in SAP MDM as templates since the business content for Customer is based on ECC and business content for Business Partner is based on SAP CRM. If so I assume that we need to create a syndication to the Business Partner repository for each customer created in the Customer repository. Then we need to initiate a syndication to SAP CRM from the Business Partner repository. Is it better in this scenario to have Customer- and Business Partner in the same repository?
So two questions based on the above input:
Which Business content to use Business Partner, Customer or both?
Should they be in separate repositories or in the same? (I understand that by keeping them in the same we create a more tight connection so that if you want to make changes in the Customer repository we need to unload the repository and thereby also influencing the Business Parter related harmonization processes).
Br
Göran
Edited by: Göran Westin on Feb 11, 2011 5:19 PM

Hello Göran,
Customer created in SAP ECC and then sent via SAP PI to SAP MDM.
From SAP MDM the customer data is then distributed to SAP CRM and other non-SAP systems.
I would suggest to consider Centralized MDM strategy (Still like to know the thought behind Decentralized MDM Strategy).
Customer should be created first in SAP MDM and then it should be syndicated to other systems.
Benefits of having Centralized MDM strategy are...
1. You can differentiate between potential Customers and Actual Customer by implementing Approval process.
2. You can use MDM key strength, that is Match & Merge feature which help avoiding duplicates.
3. You cat get most out of SAP MDM using Centralized MDM strategy.
Which Business content to use Business Partner, Customer or both?
Depends on your business need.
Should they be in separate repositories or in the same?
Having them in two independent repositories will be beneficial, because...
1. For avoiding tight connection (as you stated)
2. You can use SAP Business Content very well.
3. Repositories created based on SAP Business Content will be flexible from long term perspective (Upgrade, Maintenance etc).

Model business partner in CUSTOMER repository

Hi Anyone have tried to model business partner in CUSTOMER repository?
The situation is like this:
a customer has many "sale data" entries, where many business partner can be assigned to a "sale data" entry. "Sale Data" is a qualified table field in CUSTOMER.
Thanks for your suggestions!

Hi Vinay,
Can you give more details to set up business partner in Sales Data (qualified table). What do you mean "multi-valued table for business partner". Are you refering the similar steps suggested by Rajani?
Another point is we are centually maintain customer in MDM, Customer data needs to syndicate using xml schema DEBMDM05. Multiple occurance partner entries needs to fill DEBMDM05-E1KNVPM elements: PARVW(Partner function),KUNN2(Cust# of BP) based on multiple occurence of Sales Data entries.
This is what I am doing:
1. Create business partner flat table to has two fields:
Partner function, Cust#
2. Create a qualifier field in Sales Data table. Its type is Lookup[Flat] (multi-valued), and point to the table created in step 1.
Please let me know if if I am doing the right thing.
Re: Rajani, Tanveer:
- business partner data comes initially from R3
- BP data will be maintained in MDM same as a customer entry.
- BP entry has to be linked to customer entry with account group as "Sold to".
I can use Relationships to main the sold-to <-> busniess partner(shipto, billto, payer...) assignment, but can not syndicate the relationships to XML file(DEBMDM06).
- BP assignement is better to be maintained under Sales Data(qualified table) as it is related Sales Area.
thanks!
David

RE:Business partner functions in customer Master creation

Do we need to send the Business partner functions while creating record in R3 thru MDM.
For any account group i pass the Idoc is expecting all Business partner functions to be defined for the account group to which am trying to create Customer.(As SH,BP,PY..)
Can anyone please explain me in brief the Business partner function -Problem in my scenerio............................Concept of Business Partner function while creating Customer.

In ECC partner functions are used when you have multiple addresses for the same customer. The partner function links those address records together. You could have multiple unique customer numbers on the KNA1 table, but in the KNVVP table (partner functions) you maintain the linkage between the main table records.
Partner functions are not recommended in MDM. These are generally not considered to be "enterprise level attributes" and therefore shouldn't reside in your customer repository in a central create scenario. Additionally, some of the complexity required to model partner functions can't be modeled in MDM at this time. When 7.1 comes out, there is a new data type called "tuples" which supports deeply nested structures, and therefore you could model a true partner function table inside the sales area table.

RE-FX :- Linking of Business partner to customer for rental Agreement

While linking BP to Customer it is giving the following error:-
Business partner cannot be assigned to customer

In ECC partner functions are used when you have multiple addresses for the same customer. The partner function links those address records together. You could have multiple unique customer numbers on the KNA1 table, but in the KNVVP table (partner functions) you maintain the linkage between the main table records.
Partner functions are not recommended in MDM. These are generally not considered to be "enterprise level attributes" and therefore shouldn't reside in your customer repository in a central create scenario. Additionally, some of the complexity required to model partner functions can't be modeled in MDM at this time. When 7.1 comes out, there is a new data type called "tuples" which supports deeply nested structures, and therefore you could model a true partner function table inside the sales area table.

How to update business partner in SRM through FM or using ABAP

Hi expert,
My requirement is to update the requester field in the Shopping Cart with another requester as well as some other CUF field. Through BBP_PD_SC_UPDATE i am able to update the CUF item fields but i am unable to update the business partner.
please help, its urgently...
regards,
Rahul

Hi Sankar,
1)You can use the program BSP_UPDATE_MIMEREPOS to upload the photos in the mime repository.
2)Use the following code to get the content from your mime and set the content to your interactive UI element as Xstring format.
    data:
    mime_repository type ref to if_mr_api,
    content type xstring,
    url type string value '/SAP/BC/BSP/SAP/myBSPapplication/rajkumar.jpg' .
mime_repository = cl_mime_repository_api=>get_api( ).
call method mime_repository->get
    exporting
      i_url     = url
    importing
      e_content = content.
wd_context->set_attribute( name = 'DATAS' value = content ).
Thanks,
Rajkumar.S

Retrival of tel no. and mob. no for a Business Partner (SAP IS-U)

Hi,
There is a requirement in my report where-in i need to display the telephone number and the mobile number of a business partner contained in Address-Independent Communication.
Do you how we can retreive these number preferably from TABLES ?
Regards,
Imran

Irrespective of the module of SAP you can find the tables of any fields
goto se80
|
click on repository information system
|
expand ABAP Dictionary
|
expand fields
|
double click on table fields
on the right side of the screen enter the fieldname/description of the field and press execute to find the tables where the field is present. once you get into one table you can know the others by clicking on the where used list.
regards,
srinivas

XI Content for Business Partner

hi,
can anyone suggest what is the XI Content for Business Partner in CRM. i just need the exact name so that i can download it from the service marketplace.
thanks.
krishnan

Hi,
We have uploaded the XI Content for CRM Business Partner into the Repository. We are able to find the Message Type --> ABABusiness Partner.
How do I proceed further. Shall I copy this message type to my namespace and create Message Interfaces and proceed with mapping the source and target.
In that case, how will the function module BUPA_OUTBOUND_MAIN identify the message interface created in XI. I understand that there is some proxy code within the function module BUPA_OUTBOUND_MAIN. How this proxy calls the message interface which I have created in XI.
Krishnan

Photograph of the Business Partner

Hi ,
We want to exhibit the photo of the Business Partner at the UI view and at the pdf of the fact sheet.Though its possible to attach the photograph which will be available as link but requirement is show everytime when the detailed screen of that Business Partner opens.
Regards,
Chaturvedi

Hi,
You can have the required changes like Photograph of the BP on SAP WEB UI instance by making changes at Runtime Repository Editor Tool TCODE: BSP_WD_CMPWB. And also new fields may have to be added to the Web UI to meet business requirements. This should be done always using SAP delivered tools like Easy Enhancement Workbench EEWB,Application Enhancement Tool AET(available from CRM 7.0). Append Structures should be used only in a case above options are not available for a Business Object.

Where can I see ARCHIVED Business Partner Change Documents?

Hi,
I am archiving change documents of BPs with infostructure and Content Repository so that the change documents can be displayed in Archive Explorer TX SARI.
Now I am wondering if the archived change documents could also be displayed in transaction BP.
There in the menu is the option:
- Environment
- Archived Data
When I click on this I get the error message
There is no suitable active info structure
Message no. Q6507
But I have info structure SAPCHANGEDOCU1 active (I can see also in table AIND_STR2).
When I debug the transaction u2013 Environment u2013 Archived Data I see that it is expecting archiving object CA_BUPA (Business Partner) and not the archiving object CHANGEDOCU.
Does this mean that in the menu I only can see ARCHIVED BPs and not archived BP change documents?
I the archive Explorer the only place I can see the archived BP change documents?
Thanks in advance,
Thomas

Hi Ram,
Although, there is no standard functionality where you can see blocked business partners in the SAP ECC system. Please can you let me know as to why you are required to see blocked business partners in the SAP ECC system.
But if really required, you can design such a thing and that is possible as I have worked on a similar requirement some time back.
Regards,
Aman

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

Business partner repository

Similar Messages

Maybe you are looking for