The Service Management Experts
Menu

sap

Home / Posts tagged "sap" (Page 3)

Variant Configuration – Value Comparison

Now, this topic is related to my last post.  Specifically, when you have a material variant that you need to transfer the stock from a return.  Often there are characteristics that should not be included when you are doing a value comparison of a configuration for a material variant or a serial number.  An example of this is a reference characteristic.

However, there can be other characteristics that are based on a reference characteristic that should also be ignored when you are attaching a serial number or performing type matching.  In order to set any characteristic to be excluded from the check, you can use the following program:

RCU_EXCL_CHARACTERISTICS

Simply enter in the characteristics that should be ignored (You can even make it specific to

just one material)

this is a pretty useful program to determine what should be considered when doing a value comparison, and don’t be surprised if you need to keep running it every time you get a new return for a while.  Just because different cstics will pop up based on what you’re returning.  Either way, this is great for material variants/variant matching, and an absolute requirement for stock transferring.

I encourage you to check it out.

Have fun…

As always, if you are you interested in more help, please contact us and let us know what we can do for you.

Mike

Variant Configuration – Return Configurable Materials

I’ve been a roll with VC for the blogs, so I’m gonna keep going with it (besides, I’ve been pouring all my SM knowledge into the SM E-course).  Today I want to talk about the configuration needed to handle return configurable materials.  I’m also going to talk a little about the processes you’ll need to consider when you decide to accept configurable returns.

First, the easy part.  the configuration is pretty straight forward.  Most of the work is already done for you out of the box.  The item category REC is meant for configurable materials.  The one major change that I encourage is in the item category configuration.  Being a purest, I’ll always encourage you to copy it and make a ZREC, but that’s your call.  The one field that I change is the Special Stock Indicator.  Why you may ask?  If you don’t set this, when you attempt to do your Post Good Receipt on the configurable item if you don’t change this to be E, you won’t get stock back in the system.  Rather, you will get a confirmation of service when you receive this.  Me, I’m a fan of knowing exactly what is coming into my plant.  In addition, I might be able to strip this part down for components, or maybe even resell it.  What this means is that when you receive the item in, it will be sales order stock for your return sales order.

This brings me to the process process portion of the VC return.  Now in order to use this, you will need to do some material movements.  I’m not going into a MIGO lesson here, but you need to know that you must either issue this directly from the sales order ot another sales order, or you might even need to create a material variant and then transfer the stock.  I’ll talk more about the material variant process in another post…  Anyway, returns in VC can be complicated.  Be sure you’re aware of the process cost.  If your product is cheap enough, it could be worth it to leave the settings as they are, and just throw the item away as soon as it arrives.

Anyway, more to come on VC returns, but this will get you started,

Remember, if you need VC or SM help, please contact me and let me know how I can assist you.

Thanks,

Mike

Variant Configuration – Requirement Types

Well, today is a quick lesson that I just relearned.  When you are configuring the sales order/item category for a variant configuration item, one of the big things you have to configure is the requirement types.  Now there are some standard ones, but based on what you need, you’ll probably still tweak.

So let’s start at the beginning… where do you configure this?
Txn: SPRO  Sales and Distribution–>Basic Functions–>Availability Check and Transfer of Requirements–>transfer of requirements

In here, the first 3 pieces are what you generally need to be concerned with.  All the real work happens in the define requirements Classes step.  In here, you can define if the order generates a planned order, a production order, a service order, can it take configuration? the screen shot below shows you the full assortment of items you can control.  Ultimately, you will need to use trial and error to fit your business.  the screen shot is for the standard 040, which works for configurable items.  Certain things like the accounting section will need input from your FICO team, but out of the box, this one will work for you.

Now, once you’ve created or modified your requirement, you’ll need to create the requirement class.  I personally think this step is silly, but you have to do it.  I’ll usually name the class the same as the requirement, but do whatever you like.

Now for the last step.  Assign the requirement to your item category.  use the configuration:  Determination of Requirements Types using Transaction.

Use the search to find your VC item category.  In the second column enter in your requirements class.  Now, the last and final piece, put a 1 in the third column.  This is a subtle thing, but it tells configuration to follow the requirements settings in your sales order, not in the material master.  If you don’t put the 1 in there, you could spin your wheels for a while (like I just did) trying to figure out why it’s ignoring your Sd settings.  Anyway, that’s your tip of the day…

As always, I’m learning the hard way so you don’t have to =)

If you’re in need of consulting or SAP Add-in applications, please don’t hesitate to contact us.  We’ll soon be releasing several new VC applications, including a history report.

thanks for reading,

Mike

 

Variant Configuration – BOM Class Nodes

Happy Halloween,

I hope you consider this a treat, and not a trick =)  Today I wanted to talk a little about using class nodes in a variant bill of material.  In the old days, this was using class type 200, however, you are no longer constrained to using just 200, you can use 300 as well.  This is a handy method to dynamically add materials to a variant bill of material.  I’ll start with the how…

First, create yourself a class type 200 or 300, and be sure on the additional data that you check the following fields.

All of the fields are self explanatory, so I’m not going into a lot of details (please comment if you’d like more info).  The really important field is the first check box.  This will allow you to add it to the BOM.  The remaining fields will set some defaults for your and the additional behavior.

Once you have this class add, you need to make sure that the characteristic is either included in the your parent configuration (and is passed to your bom class node ) or is set using an object dependency at the BOM level.

Once you have this, you just need to attach the materials that can be selected using this class.  I prefer transaction CL24N to add the materails, but there are multiple ways to connect the material to the class using the standard classification transactions.  The important thing is that each material you enter needs to have the characteristic values set manually in CL24N.  This is how the system knows which material to replace the class node with.

Hopefully this all makes sense, because the part of the post I really want to talk about is some things to be aware of when using bill of material class nodes.  The first is change management.  If you use ECM to control your variant configuration bill of material, this method completely circumvents that process.  Using the class nodes, you can link and unlink materials with no ECM record.  So you must be aware of the loss of traceability when using this approach.  The second topic is that if you commonly obsolete and superscede materials in your bill of materials, finding where the materials are used can be a challenge as well.  The where-used for class types works, but if you are using CS15, you must remember to check the Class checkmark.  So if whomever is running the where used isn’t familiar that the part is used in VC class nodes, it could be easy to overlook when doing a replacement part.  This could lead to inaccurate BOM’s and confusion on the floor.  THis segways into the whole phasing out of a component on a bill of material.  If for example, you have a component that you will be replacing, but still have 50 pieces in stock that you would like to use up.  Managing the class type and when to change to the new component will be very manual and must be done at the right time by someone monitoring the stock.  it won’t be as simple as the rest of the boms that will be changed automatically using date shifting the of the ECO.

Now, despite this items, it has some very good features.  The first features is the required component.  This is especially useful if  you have order boms.  this is will quickly notify you if the class node failed to find a component (but only if you check the required box, see above).  If you use just selection conditions, you won’t get the easy visibility that component didn’t get picked that you were expecting.  The second cool feature, again related to order boms, is that you can manually find an item for a class node and replace it.  So if there is a component that is close, but normally used, you can manually select it from the list and pull it into your BOM.  this can be especially useful if you have multiple options for a single part, and you manage the part by your stock levels.  Someone can quickly evaluate which part you in stock, and switch the class node to that part (making your promise date look much better => ).

Well, I hope this was a treat for you…  if not, well, I’ll try better for next year,

As always if you need more in depth help, we offer consulting to help you streamline your VC processes,

thanks for reading,

mike

Variant Configuration – Pricing Descriptions of variant conditions using VK30

Just a short one for today =)  here’s a little trick for anyone new to variant configuration pricing.  When you use VA00 (or something similar) for your variant conditions the business sees your cryptic variant condition names.  if you go into transaction VK30, you can give it a a more meaningful name that will show up on the sales orders.  The one drawback is that you cannot have different descriptions by language.  Regardless, this will still allow you to provide a little more meaningful description to your sales order entry group.

Thanks a lot,

Mike

Variant Configuration – Pricing dependency Group

If you’ve been doing VC for a while, you might remember the days when nothing worked without an OSS note, performance was terrible, and it took discipline to build a model that would work for sales and manufacturing.  I remember those days fondly.  Well, pricing was no different.  That’s why I wanted to put this quick tip out there for you.  If you do variant pricing, a way to improve your performance is using the dependency group :  SAP_PRICNG  (no, I didn’t misspell pricing.  ha ha ha).  You simply need to add this into configuration.
SPRO–>Logistics General–>Variant Configuration–>Dependencies–>Define Groups

Once you add this dependency group, be sure to add this to all of your pricing object dependencies.  What this will do is it will only fire the dependency if you call for pricing.  Of course, this will depend on your configuration profile settings as well, but it does give you the opportunity to improve your performance.
Hope you find this useful,

As always, if you need any help in Variant Configuration or you are looking for some great applications to make your SAP life easier, please let me know.

thanks,

Mike

Variant Configuration – CWG – The Group in the know

Since, I recently attended  (and even presented at) the CWG conference in Marco Island, I figured this would be a good time to let you know about the group.  The CWG, or Configurator WorkGroup, is THE group if you do anything with Variant Configuration.  This group focuses on variant configuration, configure to order, engineer to order, and pretty much anything that has to do with being able to dynamically configure a product based on a set of rules.

http://configuration-workgroup.com/

If you’re not part of the CWG, I highly encourage you to get registered.  It’s free, and without a doubt, it has the most complete forum of VC related questions.  If you can’t find an answer here, make a post and it’s likely someone will have an idea that can solve your problem.

About my only complaint with the conference is that it tends to focuses heavily on the IPC (internet pricing and configuration), which is the web based/CRM based version of the variant configurator.  That’s not a bad thing, but there are a lot of us that care about the ERP based engine.  The conference this time around actually was good, because there was nearly a day of ETO/Specials processing in VC.  All of presentations are online from the past 10 years or so.

short story, I encourage you to involved… or check it out if you haven’t been there in a while…

good luck

Variant Configuration – Keep BOM Dependencies Simple

Having just gone to the CWG (configurator workgroup) for the first time in many years, I was reminded of my most famous story.  My friend Barry Scott Walton even told the story in his presentation.  He was nice enough to remove the names, to protect the guilty.  Some of you probably even remember this story…  It’s not the peanut butter piehl story, but perhaps I’ll share that one too someday…  This was the story of how Mike Piehl shut down MRP because I used very complicated BOM dependencies.

This was back when I worked for ADC Telecommunications and there was a mad scramble to get all of our CTO product lines converted onto to SAP before the dreaded Y2K.  Well, I was frantically working on product lines, and of course pushing the envelope, because no one ever said not to.  ha ha ha.  It all started on Wed.  I still remember grumblings of MRP being really slow, and wondering if I had done anything.  At the time, I couldn’t think of anything I did…  thursday came, the same issues were still occurring.  Then Friday, it became critical.  MRP hadn’t finished in 3 days, and no one seemed to know why.  After lots of digging, working with planning, IT, and even calling SAP’s platinum hotline, we narrowed down the issue.  We had created about 30 material variants and added a forecast to them.  In a normal world, this wouldn’t have been an issue.  But in my design, I used every tool I could in the BOM to make things work.  Well, my design was spot on.  The problem, which Barry later explained to me, was that MRP doesn’t read complex dependencies in the Bill of Material well.  And when I had a bunch of material variants, all with these complex rules, and then it read them over and over and over (because of the forecast)…  well, let’s just say, I become famous.

As soon as Barry explained the MRP issue (which in my defense was never documented anywhere in SAP), I quickly found a work around to get me by until I could rework all of the selection conditions.  I moved my variant table to a database table.  Now, I do not recommend this approach because you lose the tracability, but we had to do something quickly, and this gave us back the performance to get MRP running again (and still forecast those 30 parts).

The work took significantly longer, because I pulled all of the complex logic out of the selection condition, and moved it to the configuration profile.  This meant more characteristics at the top level, but the trade-off was well worth it.

To this day, I encourage all of my clients to keep it REALLY simple in the BOM.  SAP has done better in adapting MRP to handle variant configuration rules better.  But, in my opinion, you want the configuration profile to do all of the heavy lifting anyway, so this approach won’t steer you wrong.

Anway, learn from my experience…  Keep your BOM rules simple…  don’t add tables, don’t do complicated calculations…  just do simple assignments.  You’ll thank me later =)

Mike

Service Order Document Flow – Configuration

In a recent post, I talked about the document flow functionality.  One of the things I wanted to cover is how to turn on the service order document flow.  In the sales side, all of this information is turned automatically.  In SM, you need to manually turn on the pieces you want.  My recommendation is to turn all of these items.

First of all, this is where you go in configuration

Once inside the transaction, this is what you’ll see.

Now, I encourage you to make sure all the components you use are checked.  that’s all there is to service order document flow.

If you have any SM needs, please press the contact us button at the top of this page,

Thanks for reading,

Mike

Service Order change documents – Make sure this is turned on

One of the important pieces of tracking your metrics (and more importantly your improvement) in SAP hinges on having data.  In the service order, a lot of the change documents are turned off by default.  So I thought I’d put together a quick post to show you how to activate the Service Order change documents.  So, let’s start with where the configuration exists in SPRO

Now, here’s all things you should be aware of in this transaction.  First, find your order type and plant, then start scrolling across and make sure that you’ve checked everything that makes sense for your business:

Indicator: Status change document active for materials  this will track the status changes in a service order for the materials.  if you do metrics reports, you need this checked.

Increment this is the increment of operation numbers in your task list.

Status change document for header order/network this collects all the header level status changes.  Again, if you collect metrics, you need this checked.

Collective Requisition if you want a single purchase req for the whole order, check this box.  Otherwise you’ll receive a different pur req for each item.

Res/PurReq this determines if the purchase req/component is released as soon as it’s entered, or not until the service order has been released.  I’ll usually recommend (2).

PDC Active exactly what it says, plant data collection is active.

Indicator: Workflow for purchase order change you get the idea.

Indicator: creation of change documents active highly encouraged, so you can see all changes.

Ind.: Copy Net Price from Requisition into Purchase Order you get it.

Indicator: Status change document active for operations another change indicator.

Indicator: Status change document active for PRTs last change indicator

If you’re not sure you have this stuff set, I encourage you to go check.  If you don’t need it now, I’m sure you’ll need it in the future.

As always, if you need any SM assistance, please contact us,

Thanks,

Mike