Skip to Content

This section is the critical piece for service notifications.  Without this configuration you have nothing.  So let’s jump right in./wp-content/uploads/2014/08/blog02_01_519655.png

IMG–>Plant Maintenance and Customer Servic–>Maintenance and Service Processin–>Maintenance and Service Notification–>Notification Creation–>Notification Types–>Define Notification Types

 

/wp-content/uploads/2014/08/blog02_02_519676.png

Now, like every good consultant, I believe in leveraging what’s already there. So taking a look at the existing notifications is always the best place to start.  In my experience, the S3 is the best notification to copy from in terms of creating a service notification, but like everything, you need to work with your audience.  My example will copy the S3, but I’ll still explain what everything means.

 

/wp-content/uploads/2014/08/blog02_03_519677.png

Now, here’s what we get to start with.  Like much of plant maintenance, you don’t have a lot of functionality in the initial create.  All the power comes in the follow on pieces of configuration.  So let’s cover the pieces.

  • Notification Type & Description – pretty self explanatory.  Stick with Z* for your names to be safe.
  • Notification Cat.  – you can’t change this if you copy from a notification type.  You always want 03 anyway.  In general, this is primarily for grouping of notifications.
    • 01-Maintenance
    • 02-Quality
    • 03-Service
    • 04-Claim
    • 05-General
  • Notification Origin – this sets up the screen sequence.  Again, this is tailored toward either service, maintenance, claims, or quality.  I prefer to always stick with 06.
  • Reference Time – this determines what date suggested when you complete the notification. For my money, I prefer D.
    • A-malfunction start
    • B-Notification Receipt
    • C-Malfunction End
    • D-Notification Completion
  • Catalog Profile – this is a big one.  This defines what catalogs should be available and used in the notification. I’m a proponent of using the catalogs as much as possible to give you as much information as possible.  This means having catalog choices that make sense for the audience.  We’ll talk more about catalogs in a future section.
  • Update Group (stats) – this is for the PMIS (logistics information)  I rarely touch this, since the PMIS has never been especially useful in the service world.
  • Early no.Alloc – this one is very important.  Some clients want a number as soon as you enter into the transaction (IW51 for example).  This means even if you don’t save something, the number is used up.  Other clients want those consecutive numbers, even if that means they can’t give the “ticket” number until the notification is saved. Work with your client.  If they don’t care, uncheck this box.
  • Number Range – this one is self explanatory.  We’ll talk more about this when we look at the notification number range.  One thing to note, if you copy from a notification type, the number range gets assigned.  This is different from the service order.  Just something to be aware of.

That’s it.  Save and you have your new notification type.


If you’re interested in great tips and tricks on SAP service management, variant configuration or production planning, check out my blog at: http://paperstreetenterprises.com/blog/ There is also a link to some SAP Easy Buttons =)

Thanks for reading,

Mike CTO – JaveLLin Solutions, LLC

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