More than 5 years ago we wrote a blog on how to best monitor a discrete manufacturing process. Back then key figures like “Production/Process Orders overdue for Release” and “Production/Process Orders overdue for Technical Closure” have been described. Some other key figures, that describe process steps in-between, were left out back at that time. Such key figures as
    

  • Production/Process Orders Released without first Confirmation
  • Production/Process Orders overdue for Final Confirmation
  • Production/Process Orders overdue for Delivery Completed

    All those key figures were optimized from a technical runtime perspective, i.e. those key figures are only reading from tables AUFK, AFKO and AFPO and do not select data from the status table JEST, which is typically huge.

    Customers are usually so used/trained on looking at system status (e.g. CRTD, REL, PCNF, CNF, PDLV, DLV) for a production/process orders, that those users are having difficulties to understand what the above mentioned key figures are measuring. This  blog shall help to bridge this gap and shall explain how the key figures in Business Process Analytics map to the system status in a production/process order.

    Mapping Business Process Analytics key figures to system status in order

    I will explain the key figures in the logical order of a discrete manufacturing process

      1. Production/Process Orders overdue for Release
        • measures those orders which have been created (status CRTD) and where the scheduled release date already lies x days in the past, but where no actual release took place (i.e. status REL not yet reached)
      2. Production/Process Orders Released without first Confirmation
        • measures those orders which have been released (status REL) and where the actual release date lies x days in the past, but where no initial confirmation took place (i.e. status PCNF not yet reached)
      3. Production/Process Orders overdue for Final Confirmation
        • measures those orders which have been released (status REL) and where the scheduled end date already lies x days in the past, but where no final confirmation took place (i.e. status CNF not yet reached)
      4. Production/Process Orders overdue for Delivery Completed
        • measures those orders which have been released and at least initially confirmed (status REL & PCNF) and where the scheduled end date already lies x days in the past, but where no delivery completed flag was set (i.e. status DLV not yet reached)
      5. Production/Process Orders overdue for Technical Closure
        • measures those orders which have been released, initially confirmed and are complete regarding delivery (status REL & PCNF & DLV) and where the scheduled end date already lies x days in the past but where no (technical) completion took place (i.e. neither status TECO nor CLSD has been reached yet)

    Let’s summarize it in a short table:

    Key figure Active status reached Possible further active status Waiting for status
    Production/Process Orders overdue for Release CRTD REL
    Production/Process Orders Released without first Confirmation REL PCNF
    Production/Process Orders overdue for Final Confirmation REL PCNF CNF
    Production/Process Orders overdue for Delivery Completed REL & PCNF CNF or PDLV DEL
    Production/Process Orders overdue for Technical Closure REL & PCNF & DEL CNF

    TECO/CLSD

    Further reading

    Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under 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 Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

    To report this post you need to login first.

    Be the first to leave a comment

    You must be Logged on to comment or reply to a post.

    Leave a Reply