There were two queries in the past, where the control on TECO of Order was sought, in GI related matters.

  1. Prevent TECO if Components exist and Goods movement not done for an Order.
  2. Prevent TECO if open Reservations are there.

These questions are a sort of FAQ, during repetitions of which I often fail to search my own previous replies having solutions, due to the fact that the Titles have many variations. Due to this, to make my search easier and for the purpose of members to find solutions without posting a discussion, I am trying to preserve the solutions I worked out for those queries, which I always test and post.



As always, there can be opinions that we should be able to achieve this through user status route, . But what I observed is that this is not achievable through this method. That too complex requirements in the context of Operations and Components line items of an Order the user-exit/enhancement route does always work perfect.


Now let's see the solution codes for the above 2 codes.

The User Exit here

As many of us know that when it is the matter of TECO, the user-exit comes into picture is IWO10004. Here we need to put the codes given below to achieve the above requirements in the include  ZXWO1U03 .


The code below works for the 1st requirement.

Prevent TECO if Components exist and Goods movement not done for an Order.

 DATA: BEGIN OF i_resb1 OCCURS 100.
         INCLUDE STRUCTURE resb.
 DATA:END OF i_resb1.
 ASSIGN ('(SAPLCOBC)resb_bt[]') TO <fs_resb1>.
 i_resb1[] = <fs_resb1>.
  DELETE i_resb1[] WHERE xloek = 'X'.
 IF i_resb1[] IS NOT INITIAL.
WHERE aufnr = caufvd_imp-aufnr.
   IF i_aufm IS INITIAL.
     MESSAGE: 'TECO not possible because Goods movement not done.' 
 UNASSIGN: <fs_resb1> .


This code, checks the entries in the AUFM table for Goods movement against the current Order and stops TECO if no entries are found. This takes care of the Delete line items also.




The code below works for the 2nd requirement.

Prevent TECO if open Reservations are there.

 DATA: BEGIN OF i_resb OCCURS 100.
         INCLUDE STRUCTURE resb.
 DATA:END OF i_resb.
 ASSIGN ('(SAPLCOBC)resb_bt[]') TO <fs_resb>.
 i_resb[] = <fs_resb>.
 DELETE i_resb[] WHERE xloek = 'X'.
 IF i_resb[] IS NOT INITIAL.
   LOOP AT i_resb.
     IF i_resb-kzear <> 'X'.
       MESSAGE: 'Open Reservations Exist, TECO not possible' 
 UNASSIGN: <fs_resb> .


This code, checks whether all Reservation items have been done GI or not. If a single one is left without GI or without Deletion indicator, then it prevents the TECO to happen.


Any user-exit codes we get, should be fine-tuned to our requirements by specifying its limits (like confining it to certain Order type or some other parameter) by enclosing the code into IF and ENDIF.

All user-exits function when they are assigned to a project created through CMOD.

It is obvious that we should text our work well in Dev servers to satisfaction before we adopt it.

Thank you & Regards


We use Equipment PRTs in the production orders and we generate measuring documents in the equipment master.

Depending on the Operation quantity we want to create a measuring documents. It works fine, except the calculation was wrong.

We use formulas now, however it took a couple of hours to analyze how the Standard formulas are (not) working.


Here a short overview about the formula parameters:



Plant Maintenance and Customer Service -->Maintenance Plans, Work Centers, Task Lists and PRTs -->Production Resources/Tools -->

Production Resource/Tool Assignments -->Formulas


Standard formulas for PM (PRT) (see Configure Formula Definition)

SAPF01 PRT: Quantity

SAPF02 PRT: Usage value


SAP_12 and SAP_13: Parameters from the "old" PRT master (see CF03 -->Details --> Extras--> Formula Constants) In the equipment master you cannot maintain it. So when you use Equipments as PRT SAP_12 and SAP_13 are always blank and the Standard formulas does not work.


SAP_03: Labor time

SAP_08: Base quantity

SAP_09: Operation quantity

SAP_11: Operation splits


In our case: We only use SAP_09 (Operation quantity)


Moreover you have to maintain the Standard values "usage value" and "usage value UOM" in the order, because if the usage value UOM is empty no calculation is done. (Best place to maintain it is in the Routing)

We can integrate PM Work Center with HR Work Center in transaction IR02.





PM Work Center Master as below:




PM WC linked to HR WC, as below:




Per the logic, the Cost center in PM WC and CC in PERNR should be same:





The cost center in PERNRs has to be same as Cost center in WC master:







Used WC 1000 in equipment EQUI1000 below:



Created WO: WO1000, using equipment EQUI1000, as below:




We can assign the personnel number at operation level.










Time Confirmation, below. We can again select the PERNR from among the PERNRs already assigned to HR WC for the PM WC. The selected PERNR refers to the person who has performed the actual work. It may be different from the one assigned at operation level.







Cost posted, as below:



Cost posting against the cost center, as below:



Hope it is useful. Any other inputs are welcome.


In the past, assets were designed in large construction teams but companies in recent decades focus more and more on their core activities. The management of capital goods is being organized in the (supply) chain of owners, users, manufacturers, research institutes, IT, service providers and so on. The complexity of modern systems (e.g., mechatronics) and sustainability issues have placed more pressure on cooperation: openness, interaction and stability in the relationship foster joint innovation in product, process and technology. Focus on opportunities rather than risks makes this cooperation successful.

Please follow this link to download the whitepaper>>


Author:   Leo A.M. Van Dongen

NedTrain Fleet Services

University of Twente, Faculty of Engineering Technology

To stay ahead of the competition and continue to prosper, it is essential that asset-intensive organizations maximize their return on assets (ROA). Whatever asset your business relies on, this conference is built to equip you with the knowledge you need to help ensure improved visibility, safety, reliability, efficiency, and control across your assets.

Part of our International SAP Conference Series on Extended Supply Chain, the International SAP Conference on Asset Management is designed with the user in mind and will put you in direct contact with a diverse range of asset-intensive organizations who are successfully using SAP’s suite of solutions to achieve peak operational performance of their plants, equipment, and facilities.


Case studies from organizations including EDF, Evonik, Gasunie, Marenco Swisshelicopter, Lanxess, NedTrain, Sitech, and more will allow you to hear real-life successes, challenges, and lessons learned.

Andreas Renker from Marenco Swisshelicopter, for instance, will give an overview about how they are innovating their maintenance processes with augmented reality and 3D visualization for maintenance, repair, and overhaul (MRO).




Get insight into the challenges of a helicopter design and maintenance company. Learn more about their innovative business use case based on the example of the first Swiss helicopters and about possibilities using augmented reality, 3D visualization, and business analytics with 3D products. Mr. Renker will also give an future outlook for predictive maintenance at Marenco Swisshelicopter. The presentation will close with a informative demonstration of different applications.

Want to learn more about the other case studies and SAP presentations? The Agenda is now ready to view for the International SAP Conference on Asset Management.


Get more information, confirm your place, or contact the event team at +44 (0) 121 200 3810 or


This event offers a compelling opportunity for you to connect with like-minded peers from Europe and beyond. Don’t miss this opportunity to help your organization achieve superior asset performance.

I look forward to welcoming you to Düsseldorf.


To learn more about the SAP solutions for asset management, please access these complimentary resources.

Jogeswara Rao Kavala

PM/CS/QM Tables

Posted by Jogeswara Rao Kavala Jul 30, 2015


Years ago when I was a SAP and SCN beginner, I was searching Google for an article which could explain me how various tables are connected in PM. Then I got a picture depicting the same. I did not remember the source even. Related searches afterwards never took me to that link again. But the picture remained with me. During several occasions of replying in SCN discussions I posted this picture, which members always were very happy to have. But in one discussion a member expressed difficulty in making out the names of the tables because of the low resolution of the same. Indeed there was a legibility issue. Low resolution was perhaps because I reduced the size of the source picture due to bytes limitation in SCN (1Mb). Then I did some editing of the picture (like PrintScr in 4 pieces and joined them together) which reduced the bytes to well within the limits, at the same time improved the legibility much better than what I got from net. That post is still being liked by the members who happen to visit the discussion. With a thinking that this information will be better searched through a blog post rather than to be in the corner of some discussion, this picture is posted here for the benefit of the members who are in need and haven't yet come across. For me  the objective is to preserve a knowledge piece.

Note: I remember this belongs to the times of ECC 4.6 version, but still is most valid to PM tables configuration of ECC6.0 and above. Obviously this information is equally relevant to CS and QM modules.

... And here it is: (click on the image)

PM Tables.jpg

Also, we get good information about tables from this link by Pete Atkin: FAQ: PM/CS Tables

Thank you and Regards


In this document I will be discussing the automatic serializing of a material, while Goods Receipt.


Consider material 757, which has been assigned Serial No Profile = PM.


In the serial no profile, we have 2 settings for “Equipment Requirement”.


  • Proposal: w/o equipment
  • Always with equipment


For the above serial no profile PM, Equipment requirement is defined as “Without Equipment”.

So the common expectation would be that when we do GR of this material, serial no will be automatically created. And the equipment no will not be generated because of “without equipment” definition.




Doing GR for 757, using 501 movement type. (Using 501, to avoid PR, PO process)



Since the Material Master 757 has been assigned with a serial no profile, all stock  of 757 is supposed to be serialized on GR. Therefore, when we add 757 in MIGO, a serial no tab automatically appears.



Serial number can be mentioned manually, as well as automatically by checking the check box.

Check the serial numbers created for material 757 in IQ08.




We can see that serial no 1 to 5 has been created and also equipment numbers 10005707 to 10005711 has been created automatically.


So point to be noted here is that, on GR serial no is created and also EQUIPMENT NO is created, contrary to the expectation of “no equipment would be created”.

However, if we try to open eq master in IE02, the equipment doesn’t exist.




Here, we need to do something called as “Activation of Equipment View”. Only then we can access eq master in IE02.


Double click the equipment no in the IQ08 screen.




We can see that Equipment field in the above screen is still empty.


Now click the “Equipment View” (activate) button.




On pressing the “Activate Eq View” button, we get this screen. Now the eq no is shown as 10005707. This means that the eq view has been created for this serialized material (serial no 5 for material 757).

Just Save and the equipment view will be saved.

Now go to IE02 for eq 10005707. Equipment master is now available and can be accessed.




So the meaning of Setting “Eq Requirement = Without Equipment” is that:

  • Equipment number will be automatically created, along with serial no, on doing GR.
  • Equipment master is still not accessible in IE02, till the equipment view is activated manually.



Further if Eq Req = Always without equipment.

In this case, the process is exactly same, only difference being that we do not need to activate the equipment view, since it is already activated.








IE02: 10005713




Further point to be noted is that in both cases Equipment status is ESTO. (Equipment in stores)

Business meaning of ESTO is that, this material 758 serial no 2 is inventorized in store. And for using this material as an equipment, the status of the equipment should be AVLB. For doing this the material should be Goods Issued from stores to the required cost center (Account assignment cost center).


Doing GI, for the material 758, serial no 2 for cost center 1000.




After GI of serialized material:


  • From Inventory side: Material stock will be issued and stock in MMBE will reduce by 1
  • From PM side: Equipment which was earlier lying in stores, has been issued and is now AVAILABLE (AVLB) for installation.




Further, we need to maintain the Organizational data of this equipment manually, by maintaining plant, cost center, planning plant and work center.



Final Take Away:

  1. 1. So the meaning of Setting “Eq Requirement = Without Equipment” is that:
    • Equipment number will be automatically created, along with serial no, on doing GR.
    • Equipment master is still not accessible in IE02, till the equipment view is activated manually.
  2. 2. In both cases (with and w/o eq) equipment status will be ESTO. For using this equipment, this serialized material has to be Goods Issued to required cost center. On GI, eq status changes to AVLB
  3. 3. In both cases, we need to maintain the Organizational data manually for the equipment.

In this blog I want to describe a feature which is already available via the Web User Iinterface in Enterprise Asset Management. You just have to use it.


After event recording via Asset Viewer – what is behind it?


After Event Recording suites the purpose that a technician identifies an issue at a piece of equipment, immediately fixes the issue and reports later the time spent and the material consumed. Very often he is not able to identify  the equpiment number and searches along the hierachy of the Functional Location.

This all can be done in the Web User Interface of EAM.


  1. The technician opens the Asset Viewer searches along the hierarchy and after identifying the right piece of equipment he does a right click and selects “Confirm unplanned Job”
  2. Now a new Tab opens where most of the fields are already populated.
    He now enters his time spent, materials consumed, confirmation longtext and is able to create an activity report as well.
    He then can set the order and the notification to the status technical completion.AFter_Event_2.jpg


In essence with just a few clicks the following objects / process steps  are created:

  • Maintenance order, which is released
  • Time confirmation for this order
  • Goods issue against this order
  • Notification creation (Activity Report)
  • Notification and order are set to technical completed



With this functionality which is available you will simplify the daily life of your technician




Prerequisite for this is:

  • Implementation of OSS Note 2129222
  • Allocation of the the WD Application to the role of the technican as shown in the picture below
  • Maintenance of the Launchpad via transaction LPD_CUST



You can find more detailed information about configuration of Web User Interface in EAM via this LINK


A direct access to more information on new EAM features is available via the innovation discovery tool. You can access the tool here.


Enjoy using this functionality

In SAP Plant Maintenance implementations, often there is a need of the client to suggest KPIs/Metrics which could help them to gauge the performance of their maintenance team/assets. Many of the times client is already having some metrics/KPIs to gauge the performance but those are loosely defined; in many other times there are no well-defined KPIs identified.


This document will provide a list of KPIs that could be suggested to clients to monitor the performance of their maintenance team or company’s assets. Note that to calculate some of these KPIs custom reports/dashboards may need to be developed.


First of all let me explain the difference between a KPI and a metric. Many times both these terms get mixed and the client gets confused. A metric wrt Plant Maintenance is a number or a percentage which defines how maintenance team/assets are performing as compared to company objectives. A KPI is also a metric i.e. KPI is also a number or a percentage but KPI is a metric which has the power to provide to the management some recommendations to improve performance/reduce costs. So all KPIs are metrics but all metrics are not KPIs.


Let’s define some KPIs for Plant Maintenance. In order to make this more structured, let’s start with the basic steps in a typical maintenance scenario:


Problem Identification> Order Planning> Scheduling>Completion> Root Cause Analysis


We will define KPIs in all these areas one by one:


KPIs in Problem Identification:


  1. % or No. of Preventive Maintenance vs Reactive Maintenance Orders
  2. % or No. of Notifications in OSNO status for more than x days


KPIs in Order Planning:


  1. % or No. of Planned orders vs Unplanned orders/Emergency Orders
  2. % or No. of Work orders where actual cost/planed cost variances exceeds x %
  3. % or No. of Work orders in CRTD status for more than x days
  4. % or No. or Work orders delayed due to stock outs


KPIs in Order Scheduling:


  1. % of scheduled man-hours to total available man-hours per week/month
  2. % or no. of work orders where scheduled date is on or before expected date of start of work


KPIs in Order Completion:


  1. % or no. of work orders completed within x no. of days
  2. % or no. of work orders recalled i.e. work not completed as expected
  3. % or no. of notifications associated with work orders where cause/damage code is not filled
  4. % or no. or work orders executed internally vs by external vendor


KPIs in root cause analysis:


  1. Total maintenance cost per equipment category or maintenance cost per equipment category
  2. Ratio of planned maintenance costs vs actual maintenance costs
  3. Mean time to Repair (MTTR)
  4. Mean time between failures (MTBF)
  5. % Availability of equipment


Apart from these there are multiple queries/metrics that could be used to get a large number of metrics. Refer link below:


As a good consultant, we should filter out the metrics and recommend only few critical KPIs so that the company is not overloaded with tons of data and metrics and is able to make critical business decisions using a handful of KPIs.




We are delighted to announce that the brochure is now available for download for the International SAP Conference on Asset Management. Over two days, this comprehensive customer-centric event will give you access to SAP leadership and solution management, as well as a diverse range of SAP users from multiple industries.


To name a few customers that will present their case study:

  • EDF Energy
  • Evonik Industries
  • Gasunie
  • Lanxess
  • Marenco Group
  • NedTrain
  • Sitech
  • and more!


Check out the brochure and register today:


For more information please contact us @ +44 121 200 3810 or email



The main objective of this blog to explain SAP PM beginners to understand the difference between Technical Object Cost Center and Work Center Cost Center with a live example.

Pl. Note : This document is based on particular configuration where the settlement of the work order goes to Equipment Cost Center.


Technical Object Cost Center:


Technical Object cost center are referred as cost receivers and Work Order Cost will be settled to this cost center.


Ter 1.jpg


Work Center Cost Center:


Work Center Cost Centers are used to calculate the cost of the work done (Labor Work). This is the responsible cost center for the work order. This also requires assignment of cost center in the work center and maintaining the Activity Pricing.


Maintenance Order:


Maintenance Order is created and planning is done for labor hours with a requirement of 8 Hrs.

Ter 3.jpg

Operation Line Item Should contain all the Fields highlighted in yellow.


Activity Price (KP26):


Activity price is maintained in combination with Cost Center and Activity type.


Plan Cost:

ter  4.png


Planned Cost = Total Work (Hrs) * Activity Price (KP26) / unit


                     = 8 * 10 = 80 USD


Actual Cost:


On confirming the Operation, Actual cost is generated.


Actual Cost = Actual hours Confirmed * Activity Price (KP26) / unit


                  = 6 * 10 = 60 USD


The cost of the labor utilized in the work order is calculated based on the Cost Center assigned to the work center.


Settlement rule generation:


With respect to the configuration, settlement rule is generated automatically once the work order is Technically Complete.

ter 6.png

Settlement receiver is picked from Equipment Cost Center.

On performing the settlement, Work Order cost is settled to Equipment Cost Center. Below Screenshot is taken soon after executing KO88 transaction, which will display the cost flow is from the Maintenance order (Sender) to the cost center (Receiver).



Also you can see both the cost centers in the work order


     1.     Equipment Cost Center in Location Tab under Account Assignment

     2.     Work Center Cost Center in Additional tab.

Join us in Düsseldorf on October 5-6 for the International SAP Conference on Asset Management. This event is packed with opportunities for you to meet with SAP experts, partners, and customers in a collaborative learning environment. Discover how innovation from SAP can drive superior performance across your asset lifecycle.


management 2.png

The Agenda is now ready to view for the International SAP Conference on Asset Management.


Whatever type of asset your organization needs, this event is packed with opportunities:


  • Two half-day preconference workshops giving you comprehensive insight into the SAP Enterprise Asset Management (SAP EAM) solution and the SAP Multiresource Scheduling application
  • Keynotes and solution road map presentations from SAP
  • Time to meet privately with SAP executives and solution experts
  • Customer case studies from a diverse range of companies, including Evonik, Gasunie, Nedtrain, Lanxess, Marenco Swiss Helicopter, Sitech, and more
  • Partner exhibition and a multitude of networking opportunities together with the co-located International SAP Conference for Chemicals


Get more information, confirm your place, or contact the event team at +44 (0) 121 200 3810 or


This event offers a compelling opportunity for you to connect with like-minded peers from Europe and beyond. Don’t miss this opportunity to help your organization achieve superior asset performance.

I look forward to welcoming you to Düsseldorf.

In SAP Plant Maintenance implementation projects, there are always points of integration with FICO. Though the cost structuring, capturing and reporting is the work of FICO consultants, I am trying to cover here some basic concepts and terminologies which a PM consultant should be aware of:


Let’s first differentiate between FI and CO i.e. finance and controlling modules. I try to make it very simple here. FI is used for external legal reporting say balance sheet reporting, profit and loss statements etc. whereas CO is used for internal managerial reporting for decision making. Note the term legal in FI i.e. a company is bound by country laws while defining anything in FI, there is nothing legal as such while working in CO as it is intrinsic to company.


Key element in FI which a PM consultant should be aware of isG/L account or general ledger account. This is the most basic element to collect financial information about a business. A G/L account is an item within a general ledger. This is created by SAP transaction FS00. When a company creates a financial report such as balance sheet, most of the data is derived from the General Ledger.  G/L accounts can be broadly classified into 4 categories: assets, liabilities, expenses and revenues. The G/L account most relevant to PM is expense G/L accounts, for example utilities expense, maintenance expense, wages expense etc.


Now let’s talk about CO module. CO module has 5 sub-modules. The sub-module most relevant to PM is Cost Center Accounting. Key elements in Cost Center Accounting are cost center; cost elements, activity types etc.


Cost element acts as a link between FI and CO modules. How? Cost elements are corresponding revenue and expense elements to a G/L account. But this depends upon business requirements. Where COPA (Profitability Analysis which is another sub-module in CO) is active, then both expense and revenue
accounts (GL) are cost elements but where COPA is not active, then revenue account should not be made as cost element. Example of primary cost lements are material costs, personnel cost, energy cost etc. There are secondary cost elements also but let’s not go into that detail. Whenever a cost element is created, it needs to give a cost object to it. Cost object can be cost center, internal order, production order etc.


Hence cost elements are nothing but cost carriers. They carry the cost from FI G/L account and transfer to cost objects such as cost centers. So cost element will answer: What is the cost? And cost center will answer: Where is the cost going?


Let’s relate the above concepts with Work Order costing. In work order configuration for costing we assign cost elements to value categories. Value categories are nothing but classification of costs in a work order example labor cost, material cost, and external services cost etc. So whenever we issue any material against a work order or say somebody charges time against a work order, a G/L account gets hit which simultaneously hits the corresponding
cost element which puts cost in the work order and cost stays in the work order temporarily. Now, when we do the settlement of the work order, all the costs are moved from work order to settlement object which may be a cost center or WBS element or an internal order etc.


These are some basics of cost flow concepts which a PM consultant must be aware of. I will try to cover some more similar concepts in my next blog.

SAP's Influencing Programs

Customer Influence gives you the opportunity of interacting directly with SAP development teams.


As a part of this SAP´s Influencing program the Customer Engagement Initiative (CEI) is a structured approach for close end-to-end collaboration between customers and SAP teams during the full development cycle for planned products and solutions and new releases or enhancement packages. CEI offers an opportunity for customers to influence SAP development in collaboration with their peers. This helps SAP create products and solutions that meet our customers' needs, reflect best business practices and realize process and technology innovations.


The Asset Intelligence Network is an innovation initiative which will fundamentally change and improve the way assets are defined and managed. We aim to provide a Global Registry of Equipment to be shared - based on suitable access and authorization rights - between multiple parties (e.g. OEMs, asset owners/operators, engineering firms).


This results in a Common Definition of Machines that delivers new business models and true operational excellence, both within the company as well as for cross-company collaboration processes.


At this stage we are looking for end users who, in the course of their daily work, are using, creating, maintaining, and managing product or asset related information. In doing so, they are collaborating with other persons, both inside and outside their company. We will cover the different views of OEMs, operators and EPCs. We will engage with customers in end user research activities to:

  1. Gain insights on how customer users are currently working with and collaborating on asset information.
  2. Understand the tasks, needs, motivation and challenges of potential future users of the planned solution.
  3. Validate and receive feedback on the functionality, design and usability of the planned solution.



You have the possibility to influence the solution and its capabilities in an early stage of development.


You can find all related information for that project via the following link:

Use the link to read more on this project and to register for the CEI initiative!

Over past few years, SAP EAM has been tremendously enhanced. However, most of our customers and end-users of SAP EAM are not are not even aware of these new capabilities because they are published in very technically oriented or not well known places.  Even if one knows about the possibility to use these new features, many find configuration of these new feature challenging,

To simplify process of finding out this information, we are planning to record sessions  for many of these functional enhancements and show how to set them up in a sandbox environment. Hope this would motivate you to actively use these new features.

We are planning to make these session available via YouTube that can be accessed using following link.

The lists of some topics that we are planning to cover are:

•        Introduction to SAP EAMTube          


•        How to find Innovation and Improvements        

          –      How to search new Improvement        

          –      How to search new Innovations

•        How to improve user experience using Side Panel


         –      Overview of Side Panels        

         –      Configuring and setting up content for side panel        

         –      Preparing a SAP GUI  transaction for using it with Side Panel        

         –      Updating and creating new content for side panels        

         –      Setting up Business Context Viewer

•        How to improve user experience using web dynpro        


         –      Overview of Web Dynpro        

         –      How to configure and adapt the user interactions        

         –      How to use the Implementation guide        

         –      New features added with Business Function for Simplicity 3 and 4        

         –      New features added with Business Function for Simplicity 5 and 6

•        Improved maintenance and reliability analysis using HANA        

         –      HANA Live content for plant maintenance        

         –      Using HANA Live with Lumira and Predictive Analysis        

         –      Adapting content to Customize your analytical needs        

         –      Performing Weibull analysis and Monte Carlo Simulation to evaluate probability of failure

•        Improved user interface with Fiori        

         –      Factsheets to access Asset Information on your finger tips        

         –      How to create your own Fiori App        

         –      Roadmap for EAM Fiori Apps

Currently we are planning to publish ten videos over the next few months . Please use comments fields and provide us with your suggestions and advice to improve the content. If you find some topics of particular interest please also let us know so we can record additional sessions.


Filter Blog

By author:
By date:
By tag: