Adding batch classification via RF thru function module

[Former Member]

Hello,

I have a requirement to capture the country of origin at GR time and add it to the batch classification characteristic, Country of Origin. I have my batch class and characteristic created and when I add the data via BAPI_BATCH_CREATE, the country code shows in the batch header, but not in the batch class charateristic. How do I populate the batch class charateristic?

PS, my batch class charateristic is referenced to MCH1-HERKL and MCHA-HERKL.

Gary

[former_member42743]

Why aren't you using the SAP provided characteristic LOBM_HERKL?

Why are you creating another one?

And you shouldn't be able to reference one characterisitc to more than one field as you indicate.

With any characterisitic that references a specific field or LOBM characteristic you cannot change the value via batch classification. You have to change the field/value via other means such as MSC2n or in the document that creates the batch.

FF

[Former Member]

I am using class type 023, Batch. And within that I am using characteristic COUNTRY_ORIGIN. Is this LOBM_HERKL? Where do I verify this? Its not visible in cl03 or ct03. BTW, I got it to work by adding the MCHA to the table ref data in the characteristic.

MCH1 HERKL

MCHA HERKL

Gary

[former_member42743]

No one has probably updated your standard characteristics in the system. You do this in config.

Logistics-General>Batch Management>Batch Valuation-->Update Standard Characteristics

Execute that and it should create your LOBM characterisitcs.

FF

[Former Member]

I don't think anyone did that. Problem is we are and have been using a non-standard characteristic for SLED date. Would updating standard chars affect this?

[Former Member]

Also, on another post somewhere, I see the discussion re: BMBC to diaplay classification data but it was never resolved. The classification screen there is not intuitive, I enter batch class: BATCH_CLASS, but what do I enter under search with characteristic? Can I enter a characteristic value I want displayed?

[former_member42743]

No. It won't affect your existing characteristics. You'll just have two characteristics you can use now.

In the case of SLED date you might want to change over though. For example SAP has an OSS note on batch determination that allows you to use the LOBM characterisitcs it to make sure that batches are selected for a delivery that won't expire during shipment.

Otherwise there probably isn't a huge need for you to switch. But you might find some of the other LOBM characteristics nice to have on your batch class. I like LOBM_UDCODE as this shows the last UD code made on the batch. You can then use it for a simple grading of batches. UD code A1 = grade 1. UD code A2 = grade 2, etc... Then you can set up batch search strategies for customers to only ship Grade 1 batches or Grade 2 batches.

FF

[former_member42743]

With regard to BMBC.

On the classification tab, enter in a Selection class. This can be literally any batch class you want to use. Click on the "New" button at the end of the selection class line. The characteristics for that class should appear. You can then enter a value for say the SLED of <= 10/01/2012. All batches with the SLED characteristic and a SLED of <= 10/01/2012 will be displayed.

Usually we use this feature in conjunction with the Batch class field in the upper section. You would specify a specifc batch class of materials to search. Or you can narrow your list down by using the material tab and limiting the selection to a specific material(s).

FF

[Former Member]

Thanks, that did it. I'm going to activate the standard chars and begin using them for COO. We deliver everything the next day, so SLED in transit is not an issue, we also have some custom batch selection code I'd rather not deal with right now. But there are some others that look interesting.

[JL23]

only the LOBM characteristics get their data automatially.

you have to use object dependencies to retrieve the batch characteristic value from the batch record field.

[former_member42743]

Jurgen:

I would respectively disagree with your comment. You can create a characteristic that references a specific table and field. If it is not ambigious for the system to show it, it will display the value in that field. You cannot of course edit the value via classification. I've never needed a dependency to populate the value. The difference I think is that if you want a batch characteristic that could be edited via classification, then you are correct, you would need a dependency or procedure to populate the characteristic from a table field. But changing the value in classification would not change the value in the original source field.

I have often added the characteristics Batch_creation_date referenceing MCH1-ERSDA. You can use LOBM-HSDAT of course, but some clients have preferred the batch creation date even though that doesn't reflect the mfg date. I've also done this for the Batch_created_by field and Batch_last_changed field. The vendor and vendor batch field are also often set up as a referenced characteristic.

Adding these are nice so that these can be used in standard classification reports such as what can be created in the BMBC transaction and exported to Excel. Having the vendor and vendor batch in these reports is pretty obvious when you are comparing vendors and/or products. Adding a few of these can greatly save the creation of many custom reports.

FF

[JL23]

Thank you redriver for pointing me into the right direction. it was the allowed change that always prevented the referenced characteristics to get a value.