2018-08-17 549064

549064 - FAQ: Rescheduling/backorder updating in R/3

Version 23 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category FAQ
Release Status Released for Customer Released On 30.09.2014
Component SD-BF-AC ( Availability Check )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 549064

Symptom

This note contains a list of frequently asked questions relating to rescheduling

in the area of R/3 SD - Available-to-Promise (ATP).

For a list of all available FAQ notes relating to ATP, see SAP Note 835219.

List of questions

1. When materials and documents are processed by a rescheduling process, can

I use these materials and documents at the same time?

2. The existing selection criteria and filter criteria are insufficient.

What should I do?

3. Why does the rescheduling process always shift the confirmation of a

purchase order (PO) item further into the future?

4. A goods receipt was posted, and quantities are now available. Why does
the system not confirm an individual PO item earlier than determined by
purchase order (PO) scheduling even though the goods are available now?

5. Can I distribute the worklist across several rescheduling runs and run
them at the same time to improve system performance?

6. Why is an item that uses product selection not confirmed (earlier) in

rescheduling, even though sufficient stock exists?

7. Why does rescheduling return incorrect results or results that cannot be

reproduced if I use different delivery priorities in a document?

8. What must I do to exclude an item from rescheduling?

9. Why does the result list for rescheduling display an item without a
confirmed quantity even though the item was saved with a confirmed quantity
(that is, transaction VA02 displays a different confirmed quantity than
rescheduling)?

10. Why does the rescheduling process confirm an item in the sales order if
this item is not confirmed when the sales order is changed and the item is
checked; or why does the rescheduling process confirm earlier?

11. Why do the results of two successive rescheduling runs that are executed
immediately after each other for a material differ, although the
availability situation has not changed? The only difference between these
two rescheduling runs is that in one of the runs, more documents have been
selected because further materials have been specified.

© 2018 SAP SE or an SAP affiliate company. All rights reserved 1 of 7

2018-08-17 549064

------------------------------------------------------------------

1.

Question:

When materials and documents are processed by a rescheduling process, can I use
these materials and documents at the same time?

Answer:
No, you must avoid this. Rescheduling ignores the documents that are being processed at the same
time; this leads to incorrect results. The rescheduling process should run at a time when other
activities can be reduced to a minimum. This may have several effects; for example, the following
scenario may occur:

Ten pieces are available. Two orders that have a requested quantity of five pieces each exist, and one
order that has a requested quantity of ten pieces; however, this order is currently being processed.
Depending on the prioritization within rescheduling, the result is either correct or incorrect. If the
order that is currently being processed is one of the first two orders, the system blocks its quantities.
These reserved quantities are then included in the invoice of the other orders. In this case, the result
is correct.

However, if the order that is currently being processed is one of the last orders, the system allocates
the reserved quantities to the other two orders (this redistribution of the quantities is the purpose of
rescheduling). The system then reaches the order that is being processed and realizes that this
document is blocked. The system therefore includes this document without any changes (that is, with
its confirmation). The system has created an overconfirmation.

There is no universal solution for this problem. If the document was included in rescheduling from
the start and then changed using transaction VA02, the confirmed quantity of this document could
become zero. Since the document and its confirmed quantities have already been included in
rescheduling, the system would then create an underconfirmation.

------------------------------------------------------------------

2.

Question:

The existing selection criteria and filter criteria are insufficient. What
should I do?

Answer:
Manual backorder processing offers enhanced options in APO. In the R/3 system, however, you can
copy the report SDV03V02 and use your own selection there. We regard this report as a template
only. The requirements of individual customers are too diverse and specific to include the
corresponding functions in the standard system.

------------------------------------------------------------------

3.

© 2018 SAP SE or an SAP affiliate company. All rights reserved 2 of 7

2018-08-17 549064

Question:

Why does the rescheduling process always shift the confirmation of a purchase
order (PO) item further into the future?

Answer:
In this case, rescheduling behaves in the same way as an individual ATP check: If you use individual
purchase order (PO) processing, you can specify in the item in the PO whether a confirmation by the
vendor is mandatory. All of these unconfirmed PO items are constantly scheduled again until the
confirmation of the vendor fixes the date. For further information, see Note 401058.

------------------------------------------------------------------

4.

Question:

A goods receipt was posted, and quantities are now available. Why does the
system not confirm an individual PO item earlier than determined by purchase
order (PO) scheduling even though the goods are available now?

Answer:
A PO item does not check against the ATP logic and it therefore does not confirm against new stock
that was posted either. Instead, the PO item is automatically confirmed when a purchase requisition
can be created. The system therefore does not evaluate the changed stock situation. This missing
function is added by a modification solution. Consulting Note 149421 describes this modification
solution.

------------------------------------------------------------------

5.

Question:

Can I distribute the worklist across several rescheduling runs and run them at
the same time to improve system performance?

Answer:
Yes. In general, this is possible. You must ensure that you do not use the same combination of
material and plant in several runs. For example, the components of a bill of material (BOM) must not
be contained in other BOMs to ensure a unique selection that does not overlap with another
selection. This is because the scheduling run does not know that the material of the sales order is
already processed by another run.

No. This is not possible if delivery group correlation is permitted for the rescheduling (modification
note 804305). All order items that have the same delivery group and that are relevant for the ATP
check are part of the worklist of a selection, even if they are not included in the current variant
(selection material/plant).

During rescheduling, the system blocks the order that is to be processed, and all items of the same
delivery group carry out an ATP check one after the other. The system only releases the order again
afterwards. If several jobs that have order items of the same delivery group run at the same time, and
if a sales order has already been blocked due to a run, rescheduling the order fails.

------------------------------------------------------------------

© 2018 SAP SE or an SAP affiliate company. All rights reserved 3 of 7

2018-08-17 549064

6.

Question:

Why is an item that uses product selection not confirmed (earlier) in

rescheduling, even though sufficient stock exists?

Answer:
All items that use product selection (PROSA) are excluded from being processed in rescheduling if a
material has been selected or if the "Unconfirmed documents required" indicator has been set. In
addition, all partially delivered items with PROSA are excluded from rescheduling. If you select the
main PROSA item only, this does not make any sense anyway because by definition, this item is not
relevant for requirements.

------------------------------------------------------------------

7.

Question:

Why does rescheduling return incorrect results or results that cannot be

reproduced if I use different delivery priorities in a document?

Answer:
Implement Notes 335575 and 350172 to improve system performance. These notes are already
included in the standard system in the current Support Package. These notes add up the data records
of the items that have already been processed in order to provide this data in an aggregated form for
the next check. Errors occur during this summation if the document contains different delivery
priorities and therefore the items of different documents must be processed together. In this case,
you cannot use these notes and you have comment out the source code.

Within a delivery group (that is, if you use complete delivery in the entire document), you must
generally use only one delivery priority because otherwise, the confirmed quantities may be
incorrect.

------------------------------------------------------------------

8.

Question:

What must I do to exclude an item from rescheduling?

Answer:
Set the "Fixed date and quantity" indicator. As a result, the item remains confirmed and only issues
requirements for the amount of its confirmed quantity.

------------------------------------------------------------------

9.

Question:

Why does the result list for rescheduling display an item without a confirmed
quantity even though the item was saved with a confirmed quantity (that is,
transaction VA02 displays a different confirmed quantity than rescheduling)?

© 2018 SAP SE or an SAP affiliate company. All rights reserved 4 of 7

2018-08-17 549064

Answer:
You are using a credit block for which no deletion of the confirmed quantities is set. Rescheduling
does not support this function. The system always assumes that a blocked document does not have
confirmed quantities. The rescheduling result is therefore incorrect since such a document still uses
quantities that should be distributed to other documents by the rescheduling run. As a result, an
overconfirmation may be created.

------------------------------------------------------------------

10.

Question:

Why does the rescheduling process confirm an item in the sales order if this
item is not confirmed when the sales order is changed and the item is checked;
or why does the rescheduling process confirm earlier?

Answer:
The rescheduling checks without accumulation. When the sales order is changed and the item is
checked, the accumulation is taken into account in accordance with the Customizing settings (see
Customizing transaction OVZ2).
For the Customizing setting in transaction OVZ2, we recommend that you use accumulation=3
(accumulation of requested quantity when created, accumulation of confirmed quantity when
changed) for the check.
This allows different confirmations for the rescheduling (transaction V_V2) and for changing the
sales order (transaction VA02). This is the correct system response.

Example:
October 26, 2005 Plant stock 1
October 21, 2005 Sales order no. 1 Required quantity 2 Confirmed 1
November 10, 2005 Planned order quantity 1
November 10, 2005 Sales order no. 2 Required quantity 1 Confirmed ?

If transaction VA02 is used for checking sales order 2, a quantity of 0 is confirmed (provided that
accumulation is used for the check; see Customizing transaction OVZ2, "Accumulation" column).
During rescheduling (transaction V_V2), a quantity of 1 is confirmed.

In this context, the following remarks are helpful:

a) The rescheduling reschedules only non-fixed requirements so that the indicator for fixed
scheduled quantities retains its significance. That means that the rescheduling does not change fixed
requirements.

b) The rescheduling works without cumulation because otherwise receipts that are scheduled in the
near future are blocked by requirements that are further in the future and cannot be distributed. It is
precisely redistribution that is a significant component of rescheduling. Taking cumulation into
account would restrict this.

c) For non-fixed sales order requirements, you can set the rescheduling to behave identically to
transaction VA02
by deactivating the cumulation in customizing transaction OVZ2.

------------------------------------------------------------------

11.

© 2018 SAP SE or an SAP affiliate company. All rights reserved 5 of 7

2018-08-17 549064

Question:

Why do the results of two successive rescheduling runs that are executed
immediately after each other for a material differ, although the availability
situation has not changed? The only difference between these two rescheduling
runs is that in one of the runs, more documents have been selected because
further materials have been specified.

Answer:
This system behavior may occur if the chosen sort sequence is not unique; in particular, if the
document number and the item number were not selected as a sorting criterion. A different material
selection may change the sequence in which the document items for a material are processed when
these document items are of equal status according to the sort sequence. The cause is that the
program-internal sorting algorithm may swap the sequence of entries of an equal status in a manner
that cannot be predicted (see SAP Note 521487). This system behavior is not an error. If you want the
rescheduling result to be unambiguous, the document number and the item must be specified as a
sorting criterion.

Other Terms

V_V2, BOP, XTAB, selection, credit check, credit limit, dynamic credit check,
WMENG, BMENG, XTAB, selection, SDV03V02, fixing, fixed date, fixed date and
quantity, FIXMG, parallel processing

Reason and Prerequisites

Solution

Other Components

Component Description

SD-BF-AC-BOP Backorder Processing, Rescheduling

This document refers to

SAP Note/KBA Title

835219 FAQ: ATP composite note

821739 FAQ : Rescheduling Transaction (V_V2) in Purchasing

© 2018 SAP SE or an SAP affiliate company. All rights reserved 6 of 7

2018-08-17 549064
521487 SORT - Stable sorting

401058 New purchase order scheduling changes confirmation date

350172 Performance: Rescheduling for best-selling materials

335575 Performance: Rescheduling for best seller materials

This document is referenced by

SAP Note/KBA Title

149421 Individual purchase order: No SD update from GR

821739 FAQ : Rescheduling Transaction (V_V2) in Purchasing

835219 FAQ: ATP composite note

401058 New purchase order scheduling changes confirmation date

350172 Performance: Rescheduling for best-selling materials

335575 Performance: Rescheduling for best seller materials

© 2018 SAP SE or an SAP affiliate company. All rights reserved 7 of 7