1 2 3 6 Previous Next

SAP Master Data Governance

77 Posts

Dear MDG-Community!


Looking for information on how to build a UI for your custom object?

Then check-out the updated documentation on the help portal:

Creating User Interfaces for Single Object Processing


If you have the change to attend SAP TechEd && d-code, there is also a hands-on session on creating a custom object scenario, including the creation of a UI configuration. Join us at session DMM265 Build Processes for Your Own Master Data with SAP Master Data Governance in Las Vegas, Berlin, or Bangalore.


Can’t get there? Check-out SAP TechEd && d-code online!


Best regards,


Dear MDG-community!


With the availability of SAP MDG 7.0 SP03 we also enhanced the documentation around the change request process. Now, there is a new topic on the help portal: Configuration of the Change Request Process


This topic and its related sub-topics

- explain the change request process

- tell you about step, step type and status

- suggest a notation for change request process flow

- show how to configure the rule-based workflow in detail


We look forward to hear your feedback!


Additionally I want to make you aware of the new edition of the SAP workflow book. It also includes an extensive chapter on MDG - A must-know for all MDG Gurus! (All authors donate their proceeds to Doctors without Borders).


See: Hot off the presses, Practical Workflow for SAP http://scn.sap.com/community/bpm/blog/2014/08/03/hot-off-the-presses-practical-workflow-for-sap


And https://www.facebook.com/Workflowbook


All the best,


Hi SCN folks,

TechEd && d-code is coming closer and I prepare myself for some interesting days soon to come.  I will be in Berlin (November 11–13, 2014) at the EIM table and I am looking forward to having meetings with our customers, partners and of course with many of you.  Please stop by to chat about all EIM related topics.  I can also show you a lot of new live demos showcasing many of the latest new  EIM features. Specifically I have prepared in the last weeks the following scenarios to share with you:

  1. MDG-HANA Roundtrip Demo:
    This will guide you through brand new content which has been available since MDG7 SP02 in Q2 2014: Starting with triggering a MDG CR from a mobile app and approval in NWBC, we will then check the MDG Analytical Reporting dashboard. Lastly, we will drill down in the HANA search to the newly created supplier
  2. New MDG Fiori Apps:
    We have all the new MDG Fiori Apps up and running – we materials, customers or supplier request forms in addition to the new  financial Fiori Apps.
  3. New MDG Hana Drill Down Search for MDG-Suppliers
    This is a dedicated demo for the enhanced capabilities in the HANA Drill Down search. The demo concentrates on a supplier example.
  4. New MDG Analytics based on HANA and SAP Smart Business
    This is very exciting content: We will explore the new dashboard Tiles and Drill Downs available and additionally show how we can configure our own reports.
  5. MDG-IS including single sign-on (SSO)
    An improvement on our existing scenario but still worth looking into the details. I have managed to setup the Single Sign On between the two solutions, as well as the ability to pick multiple records for remediation.
  6. MDG-C: New Workflow Template-content based workflow routing
    Content-based routing is a well-known requirement for a master data related processes. This demo will show you the brand new MDG standard template which supports also parallel processing of content based routing. Triggering the process is done from NWBC or from Fiori app.
  7. MDG-M: BRFplus workflow – Content based routing on Material Group
    Content based workflow routing for material master data.
  8. New MDG-DMS Integration
    This will show you the new capabilities around integration of Document Management Services and MDG including a side panel graphical display to view attached images.
  9. MDG-M: Multiple Record Processing
    Was introduced with MDG7 and has interesting features available.
  10. Like & Lean UIs for Customers and Suppliers
    See how simple you can trigger new Change Requests for customers and suppliers. The complexity of the business partner is hidden to the end user.


Again, I look forward to hopefully seeing you soon and I hope we can also talk about other topics and  answer all your questions.
Let’s see us at TechEd && d-code
Best Regards

To get a complete picture of the lectures and hands-on sessions offered in the context of SAP Master Data Governance at SAP d-code 2014, you can simply go to the agenda builder for the event in Las Vegas or Berlin, and filter by search term "SAP Master Data Governance”.
This way, you get an overview of all related sessions. From there, you can dig into the individual sessions that you are interested in to get the details.


Here are agenda builders for

already filtered for SAP Master Data Governance


Check it out and filter according to your specific needs.



Today, SAP Master Data Governance (MDG) provides applications to centrally create, change and distribute master data. Being highly integrated with SAP Business Suite, MDG re-uses data models, business rules and process logic. It provides pre-build domain-specific content and a flexible framework to define data models, processes, and user interfaces also for custom-built master data.


If you'd like to be informed on the way ahead, you may check the product roadmap for SAP MDG which has just been updated, providing the current picture of the solution today (SAP MDG 7.0 SP02), planned innovations and future trends.


SAP customers and partners can check out the document on SAP Service Marketplace at http://service.sap.com/roadmaps => Product and solution roadmaps => Database & Technology (SAP Master Data Governance: Edition 2014Q3) (SMP log-in required).




You are trying to enhance standard data model by creating new entity types and creating relationships.



Error while trying to create a leading relationship for new entity type (SU type-4) on entity type-1 .


Error Screenshot




Create new relationship by prefixing ZZ i.e., ZZMATMARC1
MDG menu not visible on NWBC. Instead, It shows an error “The user menu tree for user is empty."
Error Screenshot
Role is assigned but folder is defined as a "link collection" instead of a "service map" - see:http://goo.gl/OEq9qa
Steps to solution
Step-1: Goto transaction PFCG


Step-2: Open your Role in edit mode.


Step-3: Goto ‘Menu’ Tab.


Step-4: Double click on the folder in which your views are defined. If no folder defined, then create one and move the views to this folder.


Step-5: Click on ‘Other Node Details’ button


Step-6: Select ‘Folder Option’ as ‘As Service Map'


Step-7: Save & Execute NWBC
Solution Screenshot




1378659 - NWBC known issues & what to check when opening a ticket


In service master i have  changed the number ranges in ACNR transaction .Now  we are facing the short dump

Asset condition was violated.This is due to the deletion of NR ,how to revert back

.i am able to create in AC03 with new number range But in Nwbc screen the mentioned short dump appears

Issue :


Whenever we are trying to Finalize the change Request (CR) which belongs to country Jersey C I, we have received the process error because of  below error message.




Solution :


To resolve this issue we have followed the below steps.


1.SAP OSS # 1901429 the country Jersey, C.I. ( Code: JE) is related to GB (this country is a crown dependency of the United Kingdom). But when we verified the country’s global parameter setup it is pointing to US (Screen shot: 1). Hence I believe for this reason we are getting the above  error message.







We have mapped  the country code JE to GB parameters.


2. Then we tried to finalize the change request again we have received the process error. This time the error message as "No geocoder for country JE maintained in system (table GEOCODERS)".


To resolve this we maintained the  below entry in the path SPRO--> SAP NetWeaver -->General settings --> Set Geocoding --> Assign Geocoding Program to Countries.



3. After this entry we tried to finalize the CR and received the error message as “Geocoder SAP0: Country specification is incomplete (Customizing)”. To resolve this I maintained the below value in table V_GEOT005 & V_GEOT005S (for Region details).



I found these  values from the URL : http://www.theodora.com/country_digraphs.html (Country : JE --> Geography) . The Geography code is similar to country code GB.


4. After this, when we tried to finalize the CR,we received the error message as “Telephone/fax code for country code JE is not maintained”. Based on this we maintained the entry in the below path


SPRO --> SAP NetWeaver  --> General settings --> Set Countries --> Define Country




I have found the Jersey Calling code from the URL: http://countrycode.org/jersey. This code is similar to GB.




After completing the above configuration, again I tried to finalize the CR  and this time it has been successfully finalized and created the Vendor Master in ECC without any issues.




I believe it might an useful.





just an small update on the work I'm doing with SAP MDG and SAP Information Steward integration: Last week I invested some time in getting the SSO working on an internal system. The good news is:

1. Its working as expected

2. Its pretty simple to configure the SSO.



SAP MDG comes with a DQR (Data Quality Remediation) scenario (see here: http://scn.sap.com/community/mdm/master-data-governance/blog/2013/10/22/sap-mdg-sap-information-steward-a-perfect-combination-for-data-quality-remediation-dqr-scenarios). In general you can integrate any Data Quality tool into this framework. Most of the time I have used SAP Information Steward but i have never tested the SSO between both stacks. The disadvantage of not having SSO configured is that the end users have manually login each time the DQ-dashboard comes up in the SAP MDG User Interface for DQR. With a configured SSO between both stack the users get automatically logged in into the dashboard! - Big advantage, big simplification!


What to do?

On high level you need to do the following steps:

  1. Define a authentication system in CMC - A wizard exists
  2. Generate and import certificates -  with SAP tools provides in your SAP Information Steward installation
  3. Define SSO in your configuration of SAP Information Steward
  4. Restart Tomcat/ Web Server of SAP Information Steward
  5. Define SAP ERP/MDG roles to be SSO'ed in SAP Information Steward
  6. Give the SAP users the correct right in SAP Information Steward


Instead of writing again a guide I would like to mention these detailed guides:






Want to see a demo?

if you want to see a demo, please contact your local SAP contact person The scenario is configured in our sapdemocloud (https://sapdemocloud.com/cloudportal/index.html)


Best Regards


Dear SAP Master Data Governance community,


On behalf of SAP MDG development and knowledge management, I am happy to announce the availablity of an additional SCN site about SAP Master Data Governance. The new site is aimed at featuring learning videos about specific data processing tasks across the master data domains that are supported with out-of-the-box content, while also covering specific processing tasks related to custom objects.
The intention is to give onboarding MDG users a quick start on user interaction in MDG processing.

As such, the new site perfectly complements our SCN learning offering which already features technical best-practice information covering MDG configuration and extensibility, which is specifically tailored for consultants.


As a starting point, the new site already presents three video recordings related to MDG processing topics in MDG for Financials, including change request processing for single and multiple objects, creating a profit center and creating an edition.


... and of course, this initital scope is planned to be extended.


Credit goes to the SAP MDG documentation team who made this possible. I really think this is a perfect means to convey easy-to-digest information about SAP MDG to the user community. Thanks a lot for this great piece of work!


We hope you'll find these videos beneficial for your daily work. Please let us know your thoughts. Your comments help us to continue this path of providing you with additional learning videos.

Thanks, and awaiting your feedback.



Every organization is now muddled with multi system ERP landscape. No matter how many IT consolidation projects are undertaken, after a few years it is back to square one. The dynamic business environment always allows evolution of niche IT solutions while the big brothers SAP & Oracle can keep gobbling them and enhance their portfolio but still within their portfolio of applications, the niche solution tend to maintain their uniqueness and all SAP & Oracle will do is to create a bolt on to their core product that will make the integration simplified.


The biggest pain area due to the multiplicity of IT or ERP systems is master data numbers being different in different systems. To make transactions pass through such multiple systems, interfaces will have all sorts of logic built-in to ensure the different master data numbers are somehow logically matched so that in all the systems same material/vendor/customer or any common master data is being transaction upon. But this turns out to be the weak link that breaks regularly.


Best practice on numbers for master data is never to build logic or intelligence in the numbering systems. Put it differently make it non-speaking so it will not identify itself to you. But this is the rule that is always broken in the environment I have painted above as the end users want the master data numbers to be intelligent and identify itself. Also in an environment where-in you have multiple applications or ERP systems, achieving common numbering systems means it has to be external numbering system. Sometimes this is called "Global Number".


Let us take for discussion the concept of "Global Material Number". By default this number will be externally defined which means some sort of logical process have to be defined. I would say it need not be very intelligent numbering system, but a simple program that can generate sequential numbers with say one character prefix or a suffix. There is no need to even list down the advantages of having a common number like "Global Material Number" across the IT or ERP systems as the benefits far outweigh the shortcomings of such a system.


Hence I strongly feel that having Global numbers that are externally defined in a multi IT or ERP system landscape should be considered a best practice too.


Any thoughts or counter views to my conclusion?

This blog is ment to show case the MDG parallel workflow and sending Email notification to requestor after approval.it is base on the documentation mention under link  http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30681c36-5884-2e10-85a1-cd9499942e37?QuickLink=index&…and also MDG-M: How To Send an Email Notification to the Requestor at Time of Material Activation. I thanks Rob for  good ducomentation which helps us to trigger the E-mail notification and also my colleguges who help me on this.


Business Scenario:While creation of material the two departments wants to approve the CR at the same time and also trigger the E-mail notification after activation of material.

1.Create the CR type.




2.Defining the services



3.Defining the user and Non-User decision table in BRF+,you have provide the Merge Type B(Badi) and Marge Paramaters as service which we defind in the perivous step.


Provide the workflow template which is created as per the Rob Docs MDG-M: How To Send an Email Notification to the Requestor at Time of Material Activation. and service names in the non-user decision table.


4.Define  BADI's use the Enhamcment spot USMD_SERVICE_PROCESSOR(SE18)


goto Badi Defination USMD_SSW_PARA_RESULT_HANDLER and Create implemenation


Provide the Implementation name ans text


Provide the Badi Name and implementing Class.


5.Providing the Code,click on the method IF_USMD_PARA_RSLT_HANDLER~HANDLE_PARALLEL_RESULT


check out the steps you have to provide the same steps in decision tables



6.Defining the filter types and save


follow similar method for defining the BADI USMD_SSW_SYSTEM_METHOD_CALLER and check the method




7.Create the CR for material







8.Check the status of Work flow you can see that the CR is in the two user que they can approve Parallel


Status of CR after approval from User 1


Status you can see the the both user has approved the CR and it went to next user


final approval the status has changed for Final Check Approved.




check the status of mail in SOST tcode and check the recipient



Open up the mail box and check the mail


we are working on extended Email notification once done will publish it as well.

As of May 2014, SAP Master Data Governance 7.0 is generally available with Support Package 2 (Feature Pack). MDG blogger Markus Kuppe has already provided useful information on the functional scope of MDG 7.0 and the enhancements added with MDG 7.0 SP02 (Feature Pack).


In this context, I'd like to add some news on the MDG 7.0 SP02 (Feature Pack) with a focus on the new SAP Fiori-based lean request scenarios for MDG. These new SAP Fiori apps extend the reach of SAP MDG to business contexts where business users with little or no SAP knowledge need to request master data directly on site (e.g., during a sales event) using their device of choice.




SAP MDG Fiori apps for master data requests


SAP Fiori apps for SAP Master Data Governance enable request scenarios for multiple master data domains, i.e., Business Partner, Supplier, Customer, Material, Cost Center, and Profit Center data. Business users can access these apps using the device of choice, such as a tablet or smart phone.


An offline demo clearly illustrates how a business user can use the SAP Fiori app, e.g., during a sales event to request the creation of a new B2B customer data record on a tablet PC.


Let's assume the folowing situation:


Story flow:




  1. A sales rep (business user with little SAP knowledge) enters basic data on an iPad, runs a duplicate check to see if the master data already exists, attaches a business card to the form, and finally submits the request.
  2. This triggers the creation of an SAP MDG change request, which is automatically routed to a local data steward for checking and completion in the MDG back-end. Accordingly, the local data steward runs the checks and completes missing data. During the MDG workflow all changes made to the record are highlighted, so that processors can clearly see what has been changed, which is another usability feature coming with SP02 (Feature Pack).
  3. A global data steward checks the completed request and gives final approval to activate the record.
  4. Another SAP Fiori app allows the sales rep to track the processing status of his requests.


To run through this end-to-end process that starts with the SAP Fiori lean request for customer data, click the demo link.

(To navigate, simply click the dotted orange-coloured box)



Hope it is useful for you.







For more information about SAP FIORI, see also the SCN blog by Masayuki Sekihara

May the 19th be with you! May 19th marked a great day for our SAP MDG customers. After an entirely overbooked and extremely successful Ramp-Up that started in November, SAP MDG 7.0 was released for general availability. In addition, SAP Master Data Governance 7.0 SP02 (Feature Pack) was released to customers on the same day, and marks the new go-to release that from now on everyone who is  planning to install SAP MDG should consider.


The MDG SP02 (Feature Pack) is very easy to consume. Similar to SAP MDG 7.0, it can be installed on top of Enhancement Package 6 for SAP ERP 6.0 as well as on top of Enhancement Package 7 for SAP ERP 6.0. For existing installations of SAP ERP 6.0 EhP6 or SAP MDG 6.1, this means that you don’t need to upgrade to any higher Enhancement Package, but can just upgrade to SAP MDG 7.0 SP02 in that system.


What’s new in SAP MDG 7.0 SP02 (Feature Pack)?

The Feature Pack builds on SAP MDG 7.0. With that release, we firstly enabled faster search with SAP HANA, duplicate detection, cleansing and matching. We secondly provided better usability for all standard and custom-defined master data objects, and thirdly, we delivered a more flexible foundation for higher business efficiency and refined process control.


In addition to that, the Feature Pack now provides a further improved user experience and easy access for business users, for example, by offering device-independent SAP Fiori apps for master data request scenarios and real-time insight into governance processes by enabling “smart business” KPIs.


SAP MDG Fiori apps for master data requests


SAP Fiori apps enable request scenarios for multiple master data domains like Business Partner, Supplier, Customer, Material, Cost Center, and Profit Center. Business users can access these apps from their device of choice. They will then enter some basic data, optionally run a duplicate check to see if the master data already exists, attach supportive documents to their request as needed, and submit their request. This will trigger the creation of an SAP MDG change request, which is forwarded to the next person for completion or approval.


Figure 1: SAP MDG Fiori app that allows business users to request a new cost center


SAP Smart Business for real-time insights into SAP MDG process KPIs


The use of SAP HANA is optional in SAP MDG 7.0. However, if you decide to run SAP MDG on top of SAP HANA SAP MDG uses SAP HANA’s capabilities, for example, for duplicate-detection and similarity-ranked search (for more details, see my last blog post on SAP MDG. 7.0). You can also make use of HANA being an in-memory, column-based database, and benefit from this in a multi-attribute drill-down selection that allows you to filter and analyze the intrinsic structures in your master data.


In the Feature Pack, we provide additional HANA-enabled values allowing for easy access, insight, and follow-up actions for the business. Since SAP HANA allows for fast access to aggregated data across multiple data sources, we enable fast calculation of key performance indicators, for example, to analyze the quality of SAP MDG’s governance process execution. This can be done to present the information in a Smart Business dashboard for real-time insight, and then to allow for follow-up and issue resolution.


The appropriate Smart Business content can be configured based on customer-defined HANA views. Examples of such key performance indicators include: the total number of change requests, the number of currently open change requests, change requests with the status final approval, long-running change requests that are still open, change requests with an exceeded processing time compared to an SLA, overdue change requests compared to due dates.


Figure 2: Key performance indicators in SAP Smart Business showing process quality in SAP MDG


Improved user experience: highlighting changes and the undo / redo feature


The main purpose of the Feature Pack is to improve the user experience. Let’s look at one example in more detail: the highlighting of saved and unsaved changes. If you switch on this new feature for end-users, the system displays saved and unsaved changes in two different colors on the SAP MDG user interface.


When you create a new object, the system highlights all unsaved changes in a certain color. If you change an existing object, the system also highlights unsaved changes, but in addition, it also highlights already saved changes in a second color. These are typically changes that were made by a different person earlier in the change request process, or changes you made yourself, but that have already been saved. “Changes” in this context refer to those values on the screen that would change a master data attribute compared to the last approved version of the master data – that is, compared to the “active” master data in SAP MDG terms.


Of course, this feature also works in conjunction with SAP MDG’s editions. If you change an edition-based object, for comparison. the system uses the active value either from the validity period the change refers to, or from the previous validity period. In case the object did not exist before the validity period the change refers to, or if the object was deleted in the previous validity period, the system highlights unsaved changes, but does not highlight saved changes.

The system also highlights table rows that refer to changes you can only see when navigating from a table row to the details of a dependent entity. It also allows you to distinguish new rows from changed rows in a table.


When you move your mouse over a highlighted field, the tooltip of the field displays the previous value. If you change a value several times before saving it, the tooltip displays the active value and the last saved value.


Figure 3: Highlighting saved and unsaved changes in two colors and displaying previous values in the tooltip


Another example of improved user experience is the new undo / redo feature. When you are processing a change request, the SAP MDG system records all your actions. For this, it collects exactly those actions in one “undo” step that are made in the web applications between two client/server roundtrips. Each of these steps carried out since you last saved the object can be undone. You can undo steps until you save or cancel. After having used the undo feature, you can use “redo” to recover your actions.


Figure 4: New undo / redo feature allows users to take back their proposed changes step by step


Other usability improvements


There are further usability improvements provided with SAP MDG 7.0 SP02. Let me just mention a few of them briefly. SAP MDG for Financial Data now allows users to efficiently create general ledger account data for multiple company codes by copying existing data from one company code to a new company code. It also allows creating a new general ledger account and the corresponding cost element in one maintenance step. One other highly desired feature is that you can now still change the ID of new financial master data later in the change request process. Often, when requesting a new financial master data, the final ID is not yet known to the requesting user. To allow both flexibility to the requestor and adherence to corporate numbering standards, SAP MDG for Financial Data now offers the feature to use a preliminary key first, and change it to the desired final number in a later step in the creation process.


In SAP MDG for Customer or Supplier, it is now possible to change the account group within MDG’s single object maintenance user interface. With the Feature Pack, the standard delivery also provides dedicated role-specific user interface configurations for efficient processing by experts. These include a specialized user interface covering company code data for customers or suppliers, a specialized user interface covering sales area data for customers, and one for purchasing organization data for suppliers. Users navigate directly to the specialized user interface from their (workflow) inbox based on their role and based on the step in the change request process. This saves the users several clicks for navigating to the right screen within the full change request.


Figure 5: Example of a specialized user interface covering sales area data for customers


SAP MDG for Customer or Material have also been enhanced. For example, there is an improved printing and an an enhanced copy function for material master data, as well as enriched integration with SAP PLM via Change Number and Material Revision Level, and a display option for thumbnail pictures in the SAP MDG Side Panel. The database search using SAP HANA was improved for material master data. The SAP Document Management System integration was improved. And the standard content was further enhanced: additional attributes are supported, such as storage location and the views containing material data for the warehouse. In addition, several enhancements of previously delivered material master data views are provided in the data model and the corresponding user interfaces.


As pointed out in one of my earlier blog posts, whenever we make additional investments in the MDG Application Foundation, the main focus is on extensibility, flexibility, usability, and ease of consumption. This means that we want to allow companies to create very flexible governance processes, with role-based user interfaces, but with very reasonable implementation efforts. One example of this in the Feature Pack is that we now provide customizing and configuration for all relevant SAP MDG user interfaces from one single place. A dedicated WebDynpro application is provided to manage all user interface configurations, for example, across single-object processing, multiple-record processing, and search. You can also copy a standard SAP user interface configuration to the customer namespace and configure it to your requirements.


Summary and outlook


You may have seen earlier documents about SAP MDG that describe how the focus of SAP MDG is on comprehensive master data ready for use in business processes by offering ready-to-run governance applications for specific master data domains. There, it is also stated that SAP MDG allows for customer-defined master data objects, processes, and user interfaces, and how it can distribute master data to SAP and non-SAP systems. SAP MDG is an important part of SAP’s Information Management portfolio that you might want to combine with additional tools like the SAP Information Steward for the monitoring of master data quality in all relevant systems and correction in SAP MDG, or like SAP Data Services for data quality services, validations and data enrichment.


If you look at SAP MDG 7.0 in particular, and at the recent Feature Pack, you’ll see that these enhancements focus on three aspects:


Firstly, SAP MDG now provides an even more flexible MDG Application Foundation that allows for refined control in the governance processes, leading to more flexibility and higher efficiency in the business. One example of this is the flexible Edition management for easier and more flexible scheduling of changes, a very intuitive access to the different states of master data that is valid in certain timeframes, higher transparency of past and planned changes, and a more granular control of replication timing. Another example is the parallel change requests combined with the concept of “interlocking”, which allows for many changes of the same master data object at the same time but without the risk of conflicting changes.


Secondly, enhancements to SAP MDG enable better usability providing easy access and insight for business people and allowing direct follow-up on found issues. We have looked at SAP Fiori, Smart Business, and several other usability improvements in this post. In addition, there are also the improved user interfaces for single-object maintenance, the cleansing case that allows for a reduction of duplicates during search or creation, and the multi-record processing function that allows changing multiple master data objects simultaneously in one single user interface.


Thirdly, as an option, SAP MDG can use SAP HANA for advanced duplicate-detection and search, or for multi-attribute drill-down selection. You can also use SAP HANA for efficient access to key performance indicators that are aggregated across multiple data sources to analyze the quality of governance process execution in your company.


We have already started the development of the next SAP MDG release. Stay tuned to read about more exciting enhancements and new capabilities as soon as we are ready to announce them.


You can find more information about SAP MDG on the SAP Master Data Governance page on SCN.


Filter Blog

By author:
By date:
By tag: