SAP

For me, I run in this with service contracts, but it could be anywhere you use a billing plan.  The idea is that you charge an annual price.  Say $12,000 for the year, and you want the billing plan to spread this evenly across periods. (say $1000/month or $3000/quarter).

The first thing that needs to happen is to update the pricing condition type.

Update the calculation type to be M for monthly or N for annual.

Now, if you choose annual, please be aware that the calculation is performed by days, not by months.  So if you bill monthly, the amount for Jan will be greater than Feb because of the difference in days per month.

SAP does provide OSS note:  92655 as a work around for this.

Thanks for reading,

If you use the RAS or RA order types, no doubt you recognize that you need integration of a lot of data between the two documents.  I recently ran into the issue where my partners were not copying from the sales order to my service order.

I checked that the partner determination procedure was assigned to the service order, all the standard order integration was in place.  Finally, I found a little used piece of configuration:

SPRO -> Plant Maintenance and Customer Service -> Master Data in Plant Maintenance and Customer Service -> Basic Settings -> Partners -> Copy Partner Functions to Master and Movement Data

What I forgot is that when you create a new partner determination procedure, you need to manually assign the partner functions that should be copied.

Simply check the box for all the functions you need.  Next time you create a service order, it will copy the partner functions to your service order.

Thanks for reading,

Whenever I start from scratch with configuration I tend to find something that I forgot.  This time around it was getting the operating time to be recognized by the service order.  I kept getting the error:  CN877

No operating time entered for the work center.

Turns out, the capacity hours were not maintained within the work center.

Press the capacity header button

Be sure to maintain the values for Start & Finish and the capacity hours.  If you maintain this, it should eliminate the error.

Thanks for reading,

Recently, I was configuring a workcenter for Service.  I thought I had everything taken care of, but I kept getting error CN863 everytime I made a new service order and entered in the times.  I checked the work center, but couldn’t find anything.

Well, I found transaction OIO9 is needed to maintain the default units for each planning plant.  As soon as i maintained the H for each value, I was able to get rid of the error.

Thanks for reading,

I recently got introduced to this new transaction so I wanted to write a quick post about it to keep locked into my brain for the future 🙂  It turns out that using this transaction you can do an installation (or dismantle) of an equipment record to (from) a functional location.  The idea behind this is that it will also take the item out of stock and immediately issue it to the order & “superior location” of your choosing.

Why is this cool?  if you have the proper infrastructure in place, namely a warehouse that is prepared for this, you can build the hierarchy while issuing materials to your service/maintenance order.  If you are trying to maintain the full history of what serial numbers have installed into a functional location, this transaction can be a huge step, as you can do the job in one step, instead of first issuing the material, then building/updating your hierarchy.

Now, my original investigation was looking for a better way to do a “find/replace” when I perform an exchange, but stumbling on this is certainly something that is very interesting to me.  I’m sure I”ll find a use for it sooner or later.

Remember to check out the OSS note:  https://launchpad.support.sap.com/#/notes/767108

this talks about the configuration for using the transaction.

Thanks for reading,

 

Well, I’ve been playing with adding new fields a lot lately.  And it’s all to do some pricing testing with a new field. So guess what, here we have the way to add a new field to pricing.  I found most of this information in an old SAP post.

Here I am giving a simple guide to add fields to the Pricing Field Catalogs:

For example you want to use field PSTYV (‘Sales document item category’) that is included in structure KOMP (‘Pricing Communication Item’) as a key for a condition table.

When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.

Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.

 

Here is how you fix this:

1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, ‘ZZ – sales document item category’ and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:

Component Component type

ZZPSTYV ZZPSTYV

Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.

4. Call up Transaction SPRO. Navigate to ‘Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control’ and execute ‘Define Condition Tables’.

Choose ‘Conditions: Allowed fields’ and include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.

6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:

MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.

In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.

For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.

For more information, see Transaction SPRO via the path ‘Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing’ and OSS Note 21040.

Thanks for reading,

Seems on a roll lately.  Today I wanted to share how to easily add additional fields to your sales order.  Again, I found a good post that already describes what you need.

Step by Step Guide How to Add custom field to Sales Order in SAP

Overall, it was much easier than I expected.

Thanks for reading,

I recently learned a new trick thanks to a well written blog.  I wanted to add a custom field to my service order.  I knew there was an exit IWO10018, but I didn’t know how to use it.  Turns out it’s pretty easy, but there was an extra step that missed, and this blog showed me where I went wrong.

https://blogs.sap.com/2014/04/20/iwo10018-user-fields-in-maintenance-order/

Thanks for reading,