Auto Batch creation with nomenclature at material level

[former_member2091]

Hello All,

In a previous client, we have used auto batch creation at Process order release but then system generates increasing numbers as defined in range.

Now, I was exploring if it is possible to generate batches based on a certain nomenclature.

Requirement is FGdescription/YY/MM/count, in this way and since it has product description it will change for each material.

[former_member2091]

Hello All,

Thanks for your inputs.

I am trying to follow the steps suggested above and will keep posting for updates/issues faced.

Keeping this post alive till then.

[janbuchmann]

Hi

While the previous post is obviously correct, you should perhaps consider the following: external batch number range means that users can also create batches manually with pretty much any external numbers. Which means they could enter YYYY instead of YY or M instead of MM. It might therefore be advisable to also implement BAdI BATCH_MASTER to validate the batch number against your nomenclature.

[rupesh_brahmankar3]

Hello,

Create a production scheduling profile in transaction CORY and set Automatic Batch Creation in the Order -2 Autom. batch creation at order release.

Assign this to your material master work scheduling view. Then it will create a batch in process order at the time of release.

For external batch number as you said FGdescription/YY/MM/count.

Set the external batch number OMCZ then use use SAP enhancement SAPLV1ZE. for external batch number assignment use your custom logic for material specific external batch number EXIT_SAPLV01Z_001. You use this exit to replace the number range object and/or interval proposed by the system with your own number range object and/or interval.

Please refer this discussion on same topic

Batch creation in production order

Best Regards,

R.Brahmankar

[former_member42743]

I'm curious. How many characters are you expecting? The batch number is usually limited to 12 characters. In your post, I see that at least 8 characters are used by your nomenclature if your count is 9 or less. 9 characters if counts are 99 or less.

Logically it seems that only 4 or fewer characters are available for the material description and really, probably only 2.

Did you implement an enhancement for extended batch numbers?

Do you really utilize potentially 40+ character batch numbers? Many labels typically used in stock would not use that.

And having to type that stuff in as a batch number would really become tedious.

As a functional guy I'm really curious as to how and why this nomenclature is utilized in daily practice and why.

Craig

[former_member2091]

Hi Craig,

I posted this nomenclature to make it more understandable, We are using 10 char batch with above nomenclature but material description takes 3 or 4 chars depending on products.

I can see why this caused confusion.

[former_member42743]

Ok.

I would recommend very highly that you don't use an intelligent batch number.

It typically results in downstream problems later or years later when suddenly that new product shows up, or the company buys another company and tries to bring their products on board, or you want to expand production to 1000 units instead of 999, or 10,000 instead of 9999.

Etc. etc.. These always look great and seem to make sense when you do them. But more often than not you come to regret the decision.

[former_member2091]

Hi Craig,

When you mention, not using intelligent batch number I am assuming that you mean generating batch numbers with a certain nomenclature. Right?

If it is material specific, since we assign Prod Sched in Material master Why it will have a problem for new products?

Am I missing something here?

[former_member42743]

If I could see the future, I could tell you exactly why. I can't tell you with 100% certainty that you'll ever have a problem. I can only tell you that after doing this now since1994, and until last year, as an independent consultant, where I have worked with many, many major companies, and a few small ones, I would say there is a very good chance, (70/30 maybe?) that a significant issue will happen with that design in the next 2-10 years. And maybe the development is worth it if it hangs in there for ten years.

But frankly, I've see very few companies that don't do some type of major overhaul on their systems before then though. Either a merger, acquisition, expansion, new product, regulatory requirement, or a major system upgrade like S4 Hanna. Then you're rewriting the development for Hanna. Or the next ERP system. Or you adopt another "system" or nomenclature for another product line. Now you have two ways of doing things. Two developments to manage. Two to upgrade to Hanna. Then a third nomenclature comes along. Then a fourth. Trust me.. it never ends. Even in relatively stable, "stale" companies.

Invariably this is done because people want shortcuts to get their info and as a feel good thing, (its what we always had, it saves me from looking it up, etc...). Not because of a regulatory or even a real, concrete $$$$ saving reason. Its just nice to do this. If people need to walk around "looking for stuff" it's usually a sign your logistics suck to start with or your planning is bad.

If you need more info, print more info on the label. If it's that critical, give them a bar code on the label and a phone app that'll decode it for them. Or an RF gun. Or an apple watch. Give them an Ipad with a Fiori front end.

If you MUST apply intelligence to batch numbers, limit it to a defined global standard that WILL be adopted by ALL products now and in the future. Don't include material dependent info. Most major companies I've been in usually limit intelligence in batch numbers to a few things. Some type of date code to indicate mfg date. Maybe one or two characters to indicate a production location. Sometimes a code for a business division. But nothing related to material or descriptions, and especially not to quantities. Sales people love to change names and descriptions! All of this is encrypted so none company personnel don't know what it all means. And often, these are hard coded into the system and assigned to orders at a set interval in the process. There are limited chances to manually input them.

These types of intelligent batch numbers are primarily for customer service around returns and complaints. They know their batch codings and can know right away on the phone call with a customer if its one of their batches or not if the customer can provide the batch number. And it can assist in the early stages of a recall or investigation.

Don't add complexity to a system that shouldn't need it. (And has enough already to start with!)

Craig

[lingaiahvanam]

Hi Akash,

You can create custom batch number based on requirement with the following enhancement details.

Enhancement: PPCO0001

Function module: EXIT_SAPLCOBT_001

Best Regards,

Lingaiah