Availability Check

[Former Member]

Hi,

Can someone tell me if we check the daily requirements in av check in mm02, whether it will confirm if the order when the stock is not there?

2. what is the use of NO Check in the checking group at the T.CODE OVZ2.

[Former Member · Accepted solution]

Dear Siva,

Availability check happens with the combination of checking group and class, now as per the availabity check control you do, and if you provide the with replenishment lead time etc like wise the system will respond.

if you do not mention lead time the stock will not get confirm and comes to the page of delivery proposal delivery date

hope it clears ur doubt, if it helps reward points.

[Former Member]

hi,

when you select KP no check, availability check is not carried out for that material. We always need not have availability check running in all the business scenarios. Thats why the option is given.

and depending on the material master MRP settings, various processing/lead times are calculated and the order can get confirmed at the latest possible date.

thanks

sadhu kishore

[Former Member]

Hi Siva,

Marking the daily requirement means that the stock requireements are transferred to MM/PP on a daily basis. The system will still check if the required quantity of the items are available on the required date and then only confirm the delivery date.

Secondly,

The 'No check' indicator switches off the availability check according to ATP logic for the checking group concerned.

This is used in scenarios such as issuing a quotation/Contract where you require to carry out availability checking to arrive at a delivery date but no requirements are transferred to MRP as there is no delivery going out.

<b>Reward points if helpful</b>

Regards

Sai

[former_member227476]

dear siva

Availability check:

Configuration setting:-

Availability check with ATP logic or against planning:-

Define checking group:

Checking group define what kind of requirement record system use to create when sales order & deliveries are processed for this material. We can create 2 kinds of requirements records

Individual requirement records: that means system creates requirement record for each S&D document.

Summarized requirement Records: That means system creates requirement records under certain condition in the material master record. There are 2 type of summarized requirement record:

Summarized requirement records for each day.

Summarized requirement records for each week

Define checking Action;

Here we define 01- daily requirement -B 02- Individual requirements -A

Where b-total record per day

A-single record per day

B) Define material Block for other users:

When 2 users tries to confirm the quantities for the sales order for same material at a time system will be confused to confirm the quantities both sales orders. So has to avoid this kind of situation we can block the materials from confirming the quantities for 2 users at a check, check block

C) Define checking group default values:

Checking group is going to be determined depending upon the material type & plant.

-Go to new entries, specify material type, ex;-FERT

& plant = checking group of availability check: 02

D) Carry out for Availability check:

Here we define checking rule for the Availability check & allocate them to the checking group. The checking rules specify the scope of the availability check. For a respective transaction, means which planned receipts & planned issues systems has to taken into consideration and also it determines whether system has to take RLT into consideration.

Action:

*Select checking group of availability check-02, checking rule=01

*Go to details icon, & check which planned receipts & planned issues system has taken into consideration for availability check

*save it, exit.

E) Define procedure by Requirement class:

Here we define requirement class whether on availability check & TOR should be carried out the setting that we carries out at requirement class level they are at global level. There setting automatically copied into define from of requirement class and vice versa.

Action:

*Choose requirement class: 041 & check availability check & TOR (requirement)

F) Define procedure for each schedule line category:

Here we carry out fine tuning setting for availability check at schedule line category level. Here we define whether system has to carry out Availability check for particular transaction.

Ex:- if we want to implement a availability check w/o TOR for a particular transaction. According to settings at requirement class level TOR & availability check function activate & those setting will be copied into the schedule time category by default, so that at schedule line category level we deactivated TOR

G) Determine procedure for each Delivery Item category:

Here we switch on or switch off availability check functions of a delivery item category

*choose item category ‘TAN’. & specify the appropriate value.

H) Checking group for updating back orders:

Here we assign checking group to a plant that rule specifies for individual application, according to which the availability check is carried out;

I) Define Default settings:

Here we define the result of the availability check.

*Choose your sales Area, & check fixed dates& Qty options & specify ‘D’ or ‘E’

Where: D- Dialog box in the case of shortages (one time delivery)

E- Dialog box in the shortages (delivery proposal).

rewards pls

siva