Material reservation for sales orders

[Former Member]

Dear Experts,

I was fancying that a reservation (material reservation -withdrawable relevant to location) created for a sales order(full qty) confirms the order during ATP check at delivery creation. I note that the reservation creates a requirement (which is understandable) but I expected the ATP quantity against which I am simulating the sales order delivery for availability check is should get confirmed considering this reservation as a receipt

Is this a normal behaviour. or am I missing to interpret something very basic.

Objective is: If I create a reservation manually (231 movement type) and assign it to a sales order, the corresponding delivery should be created at least for the quantity that is reserved or more if stock(ATP quantity) is available.

PS: For simplicity sake I did ensure that quantity reserved was also available on the base date (available against ATP)

What I do with these reservations later is another story.

Appreciate your replies.Let me know if more context or information is required.

Regards

L.

[Former Member · Accepted solution]

Loknath,

What makes you think that a requirement will be considered to be a receipt? Did you actually try this?

Best Regards,

DB49

[Former Member · Accepted solution]

Thanks DB49 for asking the right question

As I mentioned I did not think..I just fancied based on my rustic sense. But as I discover and interepret after testing, it seems to be essentially a scope element issue i.e. I can valuate reservation as a receipt or a requirememnt (per the MB* transaction selections) but what I could not figure out is the differece betweeen

-Reservation as an Issue

-Reservation as a receipt.

i.e. MB21 document does not announce if it a receipt or a requirement but under reservations in I see in MMBE and MB25 there is a receipt side and issue side. Unrestricted stock being the stock inclusive of reserved stock ?. at least for the material I am testing. The recipient I specified is the ship-to party and Plant as the plant at which sales order and delivery is created.

in APO I see the reservation with this title

Process Order: Reservation xxxx (With consumption) - PrdRes(W) is the ATP category

The reservation is confirmed and reduces the CuATP which is fine. Beyond this I am unable to interpret why I can't confirm my delivery. For now assume that check control is same for both sales order and delivery

What is that I am missing to intrepret. Probably absolutely basic. Would much appreciate your analysis

Regards

Lok

[Former Member · Accepted solution]

Loknath,

Yes, a reaservation can be either supply or demand. This is determined by the movement type from ERP underlying the reservation. If you want to increase the cumulative ATP, then you need to create a reservation against a movement that will increase stock, and not reduce stock. In this case, a 231 is unsuitable.

I don't know what you want me to analyze. I haven't been able to determine your business requirements.

Best Regards,

DB49

[Former Member · Accepted solution]

Thanks DB49

This is what is the requirement

Day 0

Create an order (sales) - qty 100 > ATP check > confirmed 50 (one time delivery)

Day6 (or any date after day 0)

Create a reservation for a specific quantity of a specific batch and assign to this sales order. This batch qty at the time of creation of reservation MAY not exist at the plant where I am creating reservation.

Create reservarion- qty 32, batch B, confirmed 10 (batch-plant segment ATP)

Day16 Create a delivery (same check control as sales order) from this sales order

Expected result: IF entire quantity is available

Confirmed delivery Qty - 100 of which

Line1: 32 of batch B,

Line2: 68 of original product requested.

Note that for some reasons I dont want to enter batch is sales order and neither do I have batch determination active at delivery. Batch determination happens subsequently at picking. The idea is to respect the batches thus adopted from "corresponding" reservation against the sales order. For this "adoption" we are prepared to write a small development to update these batches before the ATP check is called when creating delivery.

It is absolutely fine if what's reserved was not available at the time of creation of delivery is which case

Line1- 10 of batch B

Line2- 90 of original product

It is in this context that I wanted reservation to be a receipt for delivery confirmation. Now you mention 231 is not the right movment type. I tried a couple of other movement types but all these reservations are showing up as requirment in both business event A and B.

Regards

Loknath

[Former Member · Accepted solution]

Loknath,

Well, you have done quite a nice job in confusing me. You still haven't mentioned any business requirements, you have only mentioned solution proposals.

I don't know what you are trying to accomplish. However, there may be some opportunity in using Fixed Pegging in APO. Read more here

http://help.sap.com/saphelp_scm70/helpdata/EN/5f/b1ce4060b7dd50e10000000a1550b0/frameset.htm

I don't know if I have answered your question, but there it is.

Best Regards,

DB49

[Former Member · Accepted solution]

Thanks DB49,

Pegging is where it all started. but pegging by no means is a gurantee of confirmation unless I consider pegging in check control.

Heres the requirement expressed in simplest terms. I hope this is well placed requirement for someone dealing in persishables and aged products like wine and cheese.

For certain customer orders, I have the opportunity to deliver named batches whereever they are in the supply network to begin with, from a delivering plant where eventual batch determination however sophisticated the search strategy will(may) not pick such batches even if they are available

E.g. I am keen on delivering a batch ABY45ZZ (I just made up) with certain "characteristic Y" to a specific order before I deliver batches that are determined by the system.

Regards

L

.

[Former Member · Accepted solution]

Loknath,

Hmm, a change in direction....

pegging by no means is a guarantee of confirmation unless I consider pegging in check control.

Absolutely, that was why the link I published was "Fixed Pegging in the ATP process". What were you expecting? Of course you are going to change your ATP, that is the whole point of this dialogue.

Anyhow, your latest requirements are typically supported by using Characteristics Based availability checking.

http://help.sap.com/saphelp_scm70/helpdata/EN/4c/642661045f4b55e10000000a42189e/frameset.htm

If CDP ATP is unsatisfactory, then I fall back to my original suggestion, which is to use MTO ATP, using planned orders, and perhaps also using fixed pegging in the ATP check. It would take quite a few stars to be badly out of alignment for your sales order to 'miss' your designated batch using this functionality.

If neither of these proposals is acceptable, then I would say you are probably facing a customized solution. And, in case you are inclined to ask, no, I do not recommend such a solution, nor do I ever offer assistance for ehhanced solutions in these forums.

Best Regards, & Good Luck,

DB49

[Former Member · Accepted solution]

Thanks DB49,

This re-assures that I was thinking right to begin with.. ATP with characteristics. No answers needed futher

Full points on this one. post closed

Regards

Lok