Author: piehlm

I recently learned a cool trick when dealing with inter-company in-house repairs.  One of the scenarios in service management I’m seeing more often is having one facility bill for a repair while another company performs the repair.  There are 2 common ways of transacting this intercompany billing in the system.

1.  Create a repair sales order in both the billing and the repairing facility.  While this method provides the greatest flexibility, it also requires the greatest amount of transactional data to be entered.

2.  Create a single repair order with the main line item in the billing plant, and the receiving/repairing lines in the repair facility.

The biggest challenge with option 2 is billing the “billing plant” for the repair.  Sounds simple, but with only a single sales order, how can you invoice the customer and the “billing plant”.

That’s where I discovered this SAP provided report: RVIVAUFT that generates an inter-company invoice from the customer invoice.  it’s pretty simple and pretty slick.  there is however one drawback to this approach.  You can’t invoice the “billing plant” until after you invoice the customer.  Typically this shouldn’t be an issue, but depending on your business process it is something to be aware.

Hope you find this as useful as I did.

Well, I recently started helping a new client to revisit their current service processes across multiple organizations.  My first observation with all of their processes is that in many places things are disconnected because they aren’t using some of the functionality that is native to SAP.  This made me wonder, are there other places that aren’t connecting things in the system?  So I thought I’d do a post on serial number / Equipment history.  I think there will be follow on for connecting other documents later 🙂

So, on with the show.  the serial number history is an amazing resource, but only if you use the serial number properly.  If you are using standard SAP, in your equipment record there is a tab called serdata.  This magical tab is by far my favorite on the equipment record.  it gives you the material, serial number, if it’s currently in stock and of course the history button:

Now this is a sample history of a single serial number.  This becomes invaluable because if you look at the legend that included in this screenshot, you’ll see a huge list of documents that will be shown in the history, but only if you add the serial number to them.

Some of the biggest culprits are the SD delivery, especially if you do in-house repairs.  if you don’t add the serial number to the inbound delivery, it won’t show up anywhere in the document chain.  You can manually add it to the SD repair sales order (using the menu extras->technical objects), then even the sales order will show it.  Now, keep in mind, your serial number profile will define where the serial number is allowed and where it is required.  I’ll be doing a post soon talking about the serial number profile to give you more details.  the important detail to take away from today’s post is that everywhere you can put a serial number you should.  If you include it in a document, it will show up in the history and give you a complete picture of everywhere the number has been used.

This will be an ongoing post with more details, so don’t be upset that I’m keeping this kind of vague…  have to start somewhere 🙂

I’ve come to realize that I haven’t talked much about a very important aspect of service management, that’s serial numbers.  If you haven’t checked out my SDN post on the serial number profile, I recommend it.  It will help you understand this coming post even better.  Today I wanted to continue talking about the serial numbers, but today I want to focus on the system status’ you will encounter and what they mean to you.  Like everything in SAP, there are a lot of possible status’ out there, but I’m going to concentrate on the common ones you will see, and the some of the headaches you may encounter because of them.  Here’s the most common equipment status you’ll encounter:

• AVLB:  This is the easiest one to deal with, but the least informative.  This status is pretty much the same as saying I exist, but I don’t know where.  If you have the status AVLB, then you use it in scenarios from or to the customer.  Typically this status is assigned if you manually (or in mass) create the equipment record and it hasn’t been assigned to anything yet.
• ECUS:  This means that the equipment is at the customer.  If this status has been assigned, then you won’t be able to use it for outbound deliveries, or material movements (at least if you have stock checking turned on).  The only thing you can do with this status is an inbound delivery or Lock it.  You may also see this status combined with EDEL (which means that it is customer owned and on a delivery).
• ESTO: This means that the equipment is in stock at your facility.  it could be any plant or location, but it is now in stock, and you can no longer perform an inbound delivery, but you can do material movements on the serial number and you can do an outbound delivery.
• EDEL:  This means that it is on a delivery.  If you have an open delivery that has not been PGI’d or PGR’d, then you will see this status with either ECUS or ESTO (which will tell you if it’s an inbound or outbound delivery).  This can be a particularly nasty status.  I’ve seen many instances where deletion of a delivery does not always reset this status.  (Next post I’ll talk about how to fix things that get messed up).
• ELOK:  This is the same as marking the equipment for deletion.  Once you set this status you can’t do anything with the serial number.  If you need it, you can unlock it again, but as long as this status exist, the serial might as well NOT exist =)

I hope this helps explain the status’ a little better on the equipment.  Next time I’ll explain how you fix the status when SAP gets “Confused”.  ha ha ha.