Customer stock assigned

[former_member722016]

Dear All

Stocks are placed in bins. We need to allocate the bin stock to certain customers so where a sales order is created for that customer, the stock is picked from that bin.

Let me know whether any process will meet the above requirement

Regards

[Ajit_Routray]

Hi llatch

Addition to above answers,you could also look the below solution, reserve with batch characteristics using QM during incoming stocks (Production/Purchase), and then create batch determination strategy for delivery align with previous customer batch characteristics.

Hint: https://answers.sap.com/questions/13025926/procedure-to-change-batch-characteristic-is-materi.html

https://help.sap.com/viewer/2bc3ee8d1c83404e8cf62418640004f2/2020.000/en-US/145ebd534f22b44ce1000000...

Kind Regards,

Ajit

[Andreas_Mergler]

Hi Lucas,

three suggestions:

(A) If you know for which customer stock is being produced you could define several storage locations (and corresponding stock types in EWM) ... only feasible if you have a limited number of customers only.

(B) You could create a (virtual) batch for each customer (e.g. batch number = customer number) to separate stocks. Could work if you do not have to differentiate between real lots.

(C) You could define separate material numbers for each customer.

Best regards

Andreas

[PatrickMueller]

Hello Lucas,

Have you considered a combination of fixed storage bins and non-mixed behaviour on storage type yet?

Regards,

Patrick

[former_member722016]

Hi Patrick, yes, I did. But they have bulk storage, where mixed HU are stored. I mean, in the same bin, you may be have HU's that you can pick for any customer and HU's that you can pick only for specific customers. Batch classification is something we are considering but I was looking for something better. We also considered use special stock for sales order (E) but it doesn't work because when they produce the stock the SO may not exists. So basically, they know for which customer they are producing but there's not SO yet.

Thanks!

[PatrickMueller]

Hello Lucas,
well yes, the scenario that you describe would be perfect match for SO stock. So now it depends how much custom development you would include in the project, how much from standard functionality you want to use, and/or how much manual steps or convenience functions your customer needs.

Best case would be Sales Order Stock (SOS).

As alternative, you could define a project for each customer and post the produced HUs to Project Stock (PJS) of the corresponding customer. Once you have SO, you have posting change from PJS to SO.

Alternatively, you could have an ad-hoc inspection for each produced HU and map the inspection docs/insp.lots to customers. Of course, before picking you would have to close the inspection. Still too many functions which are unrelated to your actual process.

You could also post each HU to Q- or Blocked stock by default and build a custom mapping table HU<->customer which you would evaluate lateron when SO exists to post from Q/B to free available stock for SO.