Same batch in deifferent plants-blocked

Dear Gurus
Our client has different Plants in various locations. when we Postgoods Issue in Outbound delivery the system doesn't allow if the material with same batch is being processed at other location. can this be avoided where in same batch of a material in different plants at diff. locations can be processed simultaneously.
regards
Jim

>
Jimvero wrote:
> Dear Gurus
>
> Our client has different Plants in various locations. when we Postgoods Issue in Outbound delivery the system doesn't allow if the material with same batch is being processed at other location. can this be avoided where in same batch of a material in different plants at diff. locations can be processed simultaneously.
> regards
> Jim
Check the level at which batches are managed. This can be done in the node:
Logistics - General > Batch Management > Specify Batch Level and Activate Status Management
I guess your batch level is currently material level. If you change it to plant level, this problem might get solved. But then the system will maintain different data for the same batch number in different plants.
Check the following link:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/25/2838714f7811d18a150000e816ae6e/frameset.htm
Regards,
Aroop

Similar Messages

Batch Master Changes reflecting all plant with same Batch

HI,
When we are doing any change in Batch Master ( MSC2n ) for one plant like Shelf Life expiry date or Classification data for one plant.
its automatically reflect on all plants for same batch.
Example:
Material : 123456
Batch : 10925
Shelf Life Expiry is : 31.12.2014
Plant : 1000
This Batch is available on 10 plants for same material.
Now when i change Expiry date from 31.12.2014 to 31.12.2015 on Plant 1000 for Batch 10925
its also change on all other 10 plants.
How can we restrict this behaviour we only want to change on 1000 plant . should not change other plats.
Regards

Thanks all for your replies. yes i have check the system and Batch Level is defined on Material Level.
Jurgen actually this question is not related to expiry exactly. just for
good understanding of question i put question like this.
in classification tab we have one parameter "Release Status" which have value
X or Y. X means release and Y means Not release.
We are using this parameter for Auto batch determination purpose. if value is Y then this
batch will not come in auto batch determination.
same thing happend to this parameter. when we change value of this parameter in classification in one plant it is refelecting on all plants. which i dont want.
i hope you get my point.

Batch Managment at Plant

Hi, good day
If somebody know about, how can I do to make the choice Batch management at MM01 is only at the Plant and not in general.
That is, a material is with Batch management in a Plant and another Plant the same material without Batch management.
If anyone has an idea about this, please anything would be helpful

Hi,
Yes, it is possible only for whole plant not for a particular material in a plant. if it is active at a plant level then system will ask for batch.
Batch Management can be activated in three levels. They are
1. Client Level
2. Plant Level
3. Material Level
At plant level, the batch number is unique in conjunction
with the respective material and the plant.
At Material level, the batches are unique at material level, that is, the batch is independent of any plant. The same batch
number can also be assigned to another material.
At client level, the batch number is unique in the whole client. It indicates that batches are managed uniquely for
exactly one material, that is, independently of the plant, the same batch can exist only once for all materials.
Example
a) Plant 1000 item code A Batch 1
b) Plant 2000 item code A Batch 1
IMG --> Logistics General --> Batch Management --> Specify Batch Level and Activate Status Management
Hope Help U !!!
Regards,
Pardeep Malik

Process Order creates Multiple Inspection for Same Batch

Hi Guys,
Expert opinion is needed to have this issue fixed.
Issue:When a new Process Order is created it automatically creates in storage location A. There are times when a process order needs to be created into another storage location B. When the Process Order is created and then is changed from A to B it will create two inspection lots for one batch, one for each storage location. From the plant perspective they only need one Inspection lot as they will not create two set of samples for testing since it is the same batch it just went into a different storage location then it was originally created for. Is there a way to change SAP so that it only creates one Inspection lot per batch.
Control InspLot field in QM view for Insp Type 04 is X
We had different scenarios with same Batch
SCENARIO #1: Sloc is changed to B prior to Release, in CRTD status of order Sloc was A
So there are 2 Insp. Lot created one for A & another for B after GR in Sloc B
SCENARIO #2: Sloc is changed to B after Release
IL is created after Release of order with Sloc A, after changing Sloc B in process order and performing GR, new IL is created for Sloc B
Business scenario is certain times of the year where one creates a PO with one Sloc and then it needs to be GR into a different Sloc.
They are generating a lot of IL’s that are not used and it seems like every year they need to get UD’s made on IL’s for finance to close out the year which is cumbersome.
Please suggest way out, objective is one process should have one IL per Batch irrespective of Sloc
Regards
Nitin Desai

There are several things that come to mind.
First and foremost, get the planning right so that the process orders are created properly the first time around. This is a business issue. Yes.. I don't know your business.. no, you really aren't all that different then the thousands of other businesses using SAP. The root cause of this is you don't know what is going where when you order it or in the case of process orders, where you intend to make it or store it. That's a basic planning problem.
2 - you must have early lot creation turned on, "Y". You can't be using "X". X would only create an 04 lot when you do the GR so if you change the storage location prior to the Process order being released I'm not sure how you are generating two lots. Are you sure all the lots in question are 04 lots? Are you maybe seeing an 03 lot? Or possibly an 08 lot? Something doesn't sound right here.
3 - If you receive into two storage locations from one process order, you will get two inspection lots. No way around this. There is stock associated with these. You could use customization to suppress the second receipt but that stock would go right to UR with no inspection.
4. Don't change the storage locations in the process orders at all. You can use the stock posting screen in the UD and change the storage location when you make the UD.
5. Another option is to again, don't change the storage location in the PO but use QAC2 transaction to transfer the inspection lot into the proper storage location.
You need to explain your scenarios better cause I really don't see how you are getting the two lots when you make all your changes in the process order prior to releasing the process order. That doesn't make any sense at all.
Craig

GR Posting- in same batch

Hi Gurus ,
I have a doubt related to batch determentation:-
If I post a GR with batch 123456 of 50 qty of material which exp. date is 28'th feb 2011.
Again I post one more GR of 30 qty of matrial which has the same material,same plant,same sloc and same batch 123456.
only difference is the exp. date,suppose it's now 10'th march 2011.
hence after posting above both gr stock will show the qty 80 in the batch 123456.
So my query is how system do distinguish between 50 qty of materials and 30 qty of materials,
bcoz both has the different exp. date ,so at the time of GI both should have the different nature.

>
Tiwari Himanshu wrote:
> Thanks for the replay Jogen,
>
> I agree with you
>
> The best pratice is to use the different batches for different exp. date of the product.
>
> 1.but SAP do not restrict it. I do not know why?
> 2.Can be restrict it, I mean if any end user use the same batche for a product having different exp. date/mfg date.
>    system can not be permitted for the same.
> 3.I have one more doubt, can be use the concept of shelf life without batch detemination?
>   If yes then whats its significance. I mean whats logic behind this recomended by sap.
>
>
>                                                                                Waiting for your replay
>                                                                                Thanks in advance........
SAP allows as well to extend the shelf life with MSC2N, so doing it directly with the next receipt is just a short cut.
If users are choosing an old batch and cahnging the shelf life, then this is by intention.If you want prevent that , then you have to find a user exit. I would talk to user to to get knowldege why he does it this way, maybe he needs training.
Yes, with warehouse managment you can manage shelf life too, with some limitations.

Batch locked if some other user using same batch

Dear All,
I am facing the batch lock error which say like this :
Batch XXXX of material XXXX is already locked by userXXX. Message no. M3682
Now practically we have the same batch at different distribution centres at different plants. so even if any 1 person is doing anything on that batch than system gives this error message to other person.
Can you please give me any solution to overcome the same.
Thanks in advance......

Firstly please check if you have activated the batch level as 'Batch unique at material level'. If yes, we have to confirm that the system behavior that you are facing is the standard system design.
Please, consider that when you define the batch at material-level, then,the batch data is not plant-depended. This means that a lock on the batch will have effect on postings in all plants.
However, you might want to consider a modification to this standard behavior, see the following notes:
157423 - Message M3682 for goods movement to the same batch.
633750 - MIGO: Message M3682 with goods movement to same batch.
1422983 - MIGO: Message M3682 during goods movement to same batch

Same Batch Material to be sold at different selling prices

Hello,
I have a customer requirement where a material at depot belonging to the same batch should be sold at different sales price.
Eg: on 1st of May, Material XYZ belonging to batch AB052011 of 100 qts was GR into the Depot at Rs 100 / qty. A selling Price PR00 will be maintained at Rs 100 / qty. On 5th of May, sales happen for 50 qts, hence PR00 condition of Rs 100 /Qty will be picked accordingly. Till this point everything is fine.
Price change happens for the material at the plant.
Again on 15th of May another GR for XYZ material of Batch AB052011 of 200 qts was GR'ed into the Depot at Rs 150 / qty now. Accordingly PR00 price was changed to Rs 150 /qty.
On 20th of May the total stock of Material XYZ belonging to Batch AB052011 is 250 qts. On 20th if sale happens for 250 qts, Customer requirement is pick a PR00 of Rs 100 for the 50 qts and PR00 of Rs 150 for the remaining qty.
We dont want to allow price to be changed manually, this should only happen through condition records. Is there any way by which I can create a condition table which allows me to maintain two different prices for the same batch at a given point of time.
Regards
Raj

Hi Rajendra,
Option1:
Assuming that you are only talking about Batch Number based price (and not Batch characteristics based price) you can maintain price condition record based on Batch where Batch number will be one of the key criteria in your Access Sequence. So you many need to create a new Condition table with Material/Batch Number and insert it into your Pricing condition Access Sequence.
Since you will not know what batch you deliver till the goods been issued, you may need to redetermine the Pricing procedure during the Billing. Based on the batch that is delivered system will redetermine the Price from Condition record maintained on Batch basis.
Option2:
If you are talking about Batch Characteristics based Price, you have more to do.
Please check these forums links which might help you and also look at the OSS Note: 675409
http://www.sapfans.com/forums/viewtopic.php?f=5&t=285438
http://www.sapfans.com/forums/viewtopic.php?f=5&t=222440
Good Luck

SAP MM Batch characteristics during Plant to plant stock transfer

Hello,
I have a requirement where if i have 100 kg of a batch A in X plant and i transfer 70 kg of this batch A to Y plant. So now i have 70 kg of Batch A in X plant and 30 kg in Y plant.
I want the batch characteristics of the batch A to be copied in Plant B as well, but when plant B does some quality testing and overwrites a few batch characteritics this should not affect the batch characteritics of the Batch A in plant X. ( We donot want to create a new batch in Plant Y due to traceability reasons)
We have maintained Batch level at "Plant level" in config
Any pointers to userexit to force copy the batch characteristics initially from Plant X to Plant Y for Batch A is also welcome.
Thanks
Anurag

Please dont post the same question in multiple forums. Continue in one thread
thanks
G. Lakshmipathi

Problems in having common material and batch in different plants

Hi all,
As the material with the same batch is existing in different plants, we are facing some problems in processing the Process Messages.
If some user who belongs to a different plant is processing the batch for the material, the Process messages are not being sent the destination as we get an error message that the reservation is currently processed by user (who actually belongs to a different plant). This is effecting the Business.
Can anyone tell me how we can prevent this? Could the reservation and Batch status set as plant level control via standard IMG change ?
Regards,
Brijesh

Yes Rajanikanth,
But can you please let me know whether it is not possible to restrict this so that the batch processed in different plants should not affect in our plant?
Thanks.
Regards,
Brijesh

Lookup in same batch of messages

hi all,
is it possible to do a lookup in same batch of messages?
Ex.
FTP-XI-R/3
A textfile was transferred in FTP. I need to do a lookup if there are any 2 similar messages (messages containing same value in a certain field).

Hi Ignatius,
>>my scenario is with 2 different textfiles containing two different messages
So if i understood correctly the same record can come in two different files and you want to avoid the duplication in the target system? so you are planning to do a lookup of the idx5 messages and see whether the record already exists or not in some previous message?
I think using idx5 it wont be feasible to do a comparison. Either send the duplicated data to the target and handle it there or, create a z table in PI and do a RFC lookup which will search for the unique field value in table. If the value is not found it will update the table, else will return a duplicate status and you can then handle it in PI.
Regards
Suraj

Same batch selected in two different Deliveries

Dear all
I have a problem in Outbound delivery creation..
I have created 2 different outbound deliveries. While creating & Batch determination of first outbound delivery Batch number X with qty 100 is selected. Then it is saved with out PGI.
when i create the second outbound delivery also the same batch number X with qty 100 is selected. Actually it should not happen. Because i have total stock of Batch no X is only 100.
Please guide me how to solve this issue.
Regards
Bala

you might have selected bacth but not completed picking thats why system allowed another batch selection with same quantity. pIcking reserves the quantity. Hope this will help you.
Thanks & Regards
Amit

Process Order -Batch determination for a BOM material(same batch)

Hi Friends,
Thanks in advance.
Let us say, a material (ROH) has so many batches as A,B,C & D. Whenever we create a new process order, system has to pick only the particular batch( say -C here) in the process order BOM through batch determination. (during process order creation stage)
1.How to achieve the same ?
2. What are the ways are there to achieve the same ?
3.Is there any Exit for this?
Regards,
Mani

Hi Velmurugan & Vishwas,
Thnaks for your feed back.
1. Is there any other ways without batch classification ? ( Because there are so many material without MM-classification view.....and client wants without extending the Classification view for MM master as it suggests same batch for all GI for delivery & GR for purchase.....)...We want only for process order batch determination.....
2. Is there any exit for this ?
3. Is it possible through any kind of Characteristic assignment in the Sort sequence? How?
Regards,
Mani

Same batch picked on two different delivery notes

Hi all,
We have a situation whereby on occasion the same batch of a material is picked by SAP on two different delivery notes.
I'm trying to get to the bottom of why this is happening - from what I can tell this only seems to happen when the initial delivery is PGI'ed after the planned PGI date. i.e. delivery A created on Sep 1st with a planned PGI date of Sep 5th. Actual PGI date turns out to be Sep 7th (two days later). Delivery B created on Sep 6th - SAP picks same batch on delivery B as on delivery A. Delivery B needs to be manually amended with a different batch selection.
Am I correct in saying that SAP standard functionality only allows for the batch to be scheduled for delivery (cannot be picked on another delivery note) up until the planned PGI date? If so, how I can I prevent this from happening?
I need to try to get to the bottom of why this issue is happening.
Any useful answers will be rewarded!
Many thanks!

you might have selected bacth but not completed picking thats why system allowed another batch selection with same quantity. pIcking reserves the quantity. Hope this will help you.
Thanks & Regards
Amit

Same batch in different Process Order

Hi Expert
I have created one Process Order in COR1.Before saving the data batch is alloted for that Process
Order.At the same time another person is created the another Process Order in the diiferent location
and he also got the same batch what i got since both of them are not save d the data.
The isuue is we get the same batch both the person.It is a serious issuen in our case.Please let me know it is a configuration issue.
Regards
Manoj

Hi Manoj,
It is highly impossible that system will give both the users same batch number. Even if both of you have created Process orders at the same time..System will not allot the same numbers as the numbers are alloted from the buffer. Incase both users get the same batch number then, system will allow only one you the users to save it. The other user will get a error (or atleast an warning msg.) check this yourself and you will get an answer to the problem. By changing the configuration it wont help as the probability of both the users releasing the PO at the same time is still possible.
Regards,
Zoheb Hasan

Are new MB replacements using the same batch of bad 8600M chips?

My Macbook Pro Santa Rosa from 2007 just died yesterday. I brought it in for Logic Board replacement. It'll cost some days of productivity. But two things occur to me:
1. Do these replacement logic board use the same batch of dodgy nVidia 8600M chips? If that's the case, then anyone getting them replaced is essentially getting a chip that will eventually fail again within 2-3 years. And that's just not a real solution but just a temporary fix. It looks likely because one of my friends had his replacement Logic Board fail within 8 months of its replacing.
2. While the extension of coverage for this problem is a generous gesture on Apple's part, people who have invested in Applecare are not getting any real benefits for this issue from their investment. They're going to be just as much in the cold as everyone else once support is EOL on this item. Shouldn't there be an extension of Applecare as well? Or maybe a discount on a newer model?
I really expected this investment to work at least 6-8 years. Now it looks like it's closer to 4. I'm very nervous about using a machine that I know will at some point just fail again. And I'm just not in a position to sell this one and buy a newer one.

If you read the support documentation, you learn they "may" use refurbished parts. But that does not mean necessarily it would be the same bad batch.
It would certainly not reflect well on them if it is a bad batch. However, if your read my FAQ*:
http://www.macmaps.com/badram.html
You'll learn it is more an art than a science to identify all quality memory chips. So while one can't guarantee there aren't additional chips that are not bad, it is more unlikely that chips that were definitely bad in the first plcae were recycled into your refurbished board.
So be prepared with some backup, in event something does fail*:
http://www.macmaps.com/backup.html
And yes, there are many machines that do last 8 years, even from
the more current machines. A lot depends on usage, and if you have power issues*:
http://www.macmaps.com/frayguide.html
and if you ensure the machine is on a surface where it is less likely to overheat.
If you get repeated failure of repairs, you should insist on getting a replacement Mac when next contacting AppleCare.
- * Links to my pages may give me compensation.

Same batch in deifferent plants-blocked

Similar Messages

Maybe you are looking for