| # Where Available The Where Available button results in an ATP Overview report. The ATP check is performed on a specific date across multiple clusters. The algorithm looks at the ATP of the (clustered) plan item, which means that the check is performed on cluster level and not on individual warehouse level. Each plan item has a default warehouse, which will be the warehouse printed on the ATP Overview report, but the availability will always be checked for all warehouses together within the cluster. Note CTP cannot be checked during a 'where available'. Only an ATP check is permitted. Which items/clusters are taken into account? Two situations can be distinguished: Ignore Supplying Relations check box cleared Ignore Supplying Relations check box selected If the Ignore Supplying Relations check box is cleared, the Where Available command checks on the ATP of the item defined on the required date and for the ATP of all supplying items, multi-site. This ATP check includes all the warehouses of the cluster from which the demand originates, plus all warehouses of the clusters that are linked to that cluster by means of a supplying relation. The supply lead-time offset is also taken into account: planned delivery date versus planned receipt date. Example The following supplying relationships are set up for item X_ in the empty cluster (default warehouse WH1). The item also exists in a location (cluster 3) for which no supplying relationship is defined. Where - available example When you perform the where-available check for item X__ in on 25/4, the result is as follows:
Availability
Company | Warehouse | Available | Date
--- | --- | --- | ---
100 | WH1 | 20 | 25/4
100 | WH3 | 15 | 25/4
100 | WH5 | 10 | 25/4
200 | WHA | 40 | 25/4
The following clusters and items are checked: Example Note Note that the ATP of item X_CL3 is not part of the where available because the ATP does not have a supplying relation to X__. Example The ATP of item Q_CL2 is included in the where-available check, although the item code differs. If you do not ignore the supplying relationships, all of these items are checked, independent from the item code. The two components of item X__ are not included because (component) CTP is not permitted. The problem in each of these situations is that a supplying relationship must be defined to retrieve the goods from another cluster. In some cases, however, you might not want that because you only want to check the ATP and then deliver directly to the customer from the goods’ location. Therefore, if the Ignore Supplying Relations check box is selected, the Where Available command checks on the ATP of the item defined on the defined date and for the ATP of all items with the same (general) item code, but not multi-site. This check is carried out based on the item code. Therefore, all X_… items are included. Example Where available for item X__ in on 25/4:
Availability
Company | Warehouse | Available | Date
--- | --- | --- | ---
100 | WH1 | 20 | 25/4
100 | WH3 | 15 | 25/4
100 | WH6 | 25 | 25/4
The following clusters/items are checked: Example 2 Notice that the ATP of item Q_CL2 is not part of the where-available function because the system does not recognize that item Q_CL2 is a supplying item for X_. The check is carried out on the item code X_. In addition, item X__CL1 is also not included because this item resides in another company, and this check is only performed on a single site. |