Skip to Content
Volker von Gloeden
Volker von Gloeden
June 18, 2012 6 minute read

New key figures for BPMon & BP Analytics, especially for working capital improvement

Follow RSS feed
0 Likes 219 Views 5 Comments

Last Monday (June 11th, 2012) the new ST-A/PI 01P plug-in was shipped to customers and this means that many new key figures have been shipped for Business Process Monitoring and Business Process Analytics in SAP Solution Manager. This blog will give a short overview about what is new. Many new key figures were especially created in order to improve your working capital and supply chain planning efforts. And we provide new key figures for SAP Transportation Management (SAP TM) which was not covered before.

The new ST-A/PI 01P is available for download and can be found under (SMP login required) http://service.sap.com/supporttools.

A complete list/catalog of all available out-of-the-box key figures is available as MS PowerPoint presentation at (SMP login required in both cases)

  Remark: On slides 1 and 2 (Table of Content) you can find hyperlinks where you can directly access the respective chapter of interest.

The following new Lead Time calculations have been developed for SAP ERP:
  • Time from  Sales Document Item creation to Invoice (in days)
  • Time from Outbound delivery creation to Post Goods Issue (in hours)
  • Time from Post Goods Issue to Invoice (in days)
  • Time from Shipment creation to Shipment Completion (in days)
  • Time from Shipment creation to Shipment End (in days)
  • Time from Open item creation FI-AP to clearing (in days)
  • Time from Open item creation FI-AR to clearing (in days)
New monitoring objects and key figures have been developed in the following areas in SAP ERP:
  • Material Master Data (Materials without backflushing indicator, standard price or moving average price)
  • Customer Master Data (SD invoices with different payment terms)
  • Vendor Master Data (MM invoices with different payment terms)
  • Vendor Payments (early or late payments in FI-AP)
  • Customer Payments (late payments in FI-AR)
  • Check Deposit Transaction (not complete posted)
  • Cost Estimates (not released)
  • IS-U Data Exchange Task (data exchange process in certain status)

New monitoring objects and key figures have been developed for SAP Transportation Management:
  • Transportation Requests (created & changed per day)
  • Transportation Orders  (created & changed per day)
  • Freight Settlement documents (created & changed per day)
  • Forwarding Settlement documents (created & changed per day)   
New key figures were introduced for Sales Documents, Sales Document items, SD Invoices, Purchase Orders, Stock Transport Orders, Goods movements, Production/Process Orders, Outbound deliveries, Delivery items, Reservations and Open Vendor items FI-AP. Some examples are:
  • Number of changed orders (you can check if “no touch” orders are really not touched after creation)
  • Overdue SD requirements (you can check if old sales requirements still exist in table VBBE which might lead to inaccurate planning and availability check results)
  • Changes of SD document items
  • Unconfirmed schedule line items
  • Sales invoices with open FI-AR items (instead of just checking open & overdue FI-AR items in general you can specifically check which SD invoices were not yet cleared on FI side)
  • Debit memos / Debit memo items created in reference period (including orer reasons)
  • PO Items with Invoice Receipt Qty greater Goods Receipt Qty
  • Overdue STO schedule lines & overdue STO schedule lines in transit
  • Goods movements created with reason & cancelled goods movements in reference period
  • Production/Process Order components overdue for consumption (you can check for order reservations which have not been completely withdrawn although the requirements date lies in the past)
  • Production/Process Orders with planned qty unequal actual order qty
  • Production/Process Orders with Planned Orders start date unequal Order start date
  • Conversion of Planned Order too early/late
  • Release date of Production/Process Order too early/late
  • Incomplete outbound deliveries
  • Missing fields in incomplete outbound delivery items
  • Overdue LE requirements (you can check if old sales requirements still exist in table VBBE which might lead to inaccurate planning and availability check results)
  • Reservation items overdue for final issue indicator
  • Reservation items with final issue indicator/deletion indicator
  • Blocked items for payment where cash discount is endangered or lost (these key figures already existed for MM invoices and are now also available for FI-AP)

In the area of interface monitoring new CRM middleware monitoring capabilities have been introduced, especially related to synchronization issues between mobile site and CRM server.

Besides all these new key figures that have been shipped with ST-A/PI 01P there has been also a lot of news with ST710 support package 5, e.g. a complete new setup environment for Business Process Monitoring and Business Process Analytics and a new and enhanced version of Business Process Analytics which is described in greater detail in this separate blog. Basic new features are the benchmarking over values (in a dedicated currency) and some Advanced Benchmarking that allows benchmarks over material/plant combinations et.al.

New Analytics.png

Heads-up if you use the new ST-A/PI 01P on the managed system together with an “old” SAP Solution Manager release lower than SP5

With the new ST-A/PI 01P together with the new Business Process Analytics features with SAP SolMan 7.1 SP5 it is now possible to benchmark users and document values (in a dedicated currency). As this is very sensitive data it needs to be secured with new roles and authorization objects which are part of ST-PI 2008_1_* support package 06. So if you are using Business Process Monitoring or Business Process Analytics in an SAP Solution Manager release before 7.1 SP5 together with an ST-A/PI lower than 01P in the managed system, then the following happens

  1. If your ST-PI 2008_1_* support package level is lower than 06 in the managed system (i.e. the new authorization objects do not exist in your environment), then the columns with user and value information in any detail list will be always blank.
  2. If your ST-PI 2008_1_* support package level is 06 (or higher) in the managed system (i.e. the new authorization objects exist in your environment), then you have to configure and generate one of the new roles SAP_MANAGED_BPOANA_ALL or SAP_MANAGED_BPOANA_DIS in the managed system and assign it to the respective user profile in order to access available business data (e.g. detail list, execution of transaction ST13). Otherwise you users will no longer be able to navigate into the detail list at all or perform an age analysis.

More details on the new roles and authorization obejcts will be given in a separate blog.

Further information

You can find all necessary information about Business Process Analytics in this document.

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered at http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

.

The following blogs (in chronological order) provide further details about Business Process Monitoring functionalities within the SAP Solution Manager.

Assigned tags

Related Blog Posts

    Related Questions

      5 Comments
      You must be Logged on to comment or reply to a post.
      • Former Member

        Hi Volker von Gloeden,

        It very helpful to define business scenarion for new object.

        I have one question:

        There is any retention period to store BPMon data in infocubes of solman?

        • Volker von Gloeden Post author

          Hi Karthik,

          I don’t know if I understood your question correctly, but let me answer in the following way. You can define data retention times for the BPMon data itself, i.e. with the default settings the alert data is aggregated to a daily basis after 3 days and the data is completely deleted after 30 days (e.g. after the SL reporting is done). If you want to persist the data you can optionally store it in an InfoCube. There is no additional retention time for the InfoCube data.

          Kind Regards

          Volker

          • Former Member

            Hi Volker,

            Thanks for reply.

            I have the requirement to save BPMon date for 12 to 15 months of business process like OTC …etc  to check the client sale.

            Whether it is possible in Table E2E_BI_DELETE to change $Delta Value or some where?

            Rg,

            Karthik

            • Volker von Gloeden Post author

              Hi Karthik,

              sorry but from your short description I still do not get what you want to achieve: Are your referring to BPMon alerting and you want to store data in InfoCube 0SM_BPM or are you referring to BP Analytics and InfoCube 0SM_BPMRH?

              Anyway no sales data is stored as this is something that the “normal” SAP BW does. BPMon or Analytics stores information how many documents/items have been either processed or are outstanding/overdue/erroneous.

              KR

              Volker