alert types

10.05.2011 of 26

SAP Note 500051 - Alert monitor overview (AMO) alerttypes

Note Language: English Version: 8 Validity: Valid Since 12.04.2005

The displayed SAP Note is not up to date in the selected language /

Summary

SymptomThe APO alert monitor is the monitoring tool in APO used to provide anoverview of the different business problem situations in a plan.The alert monitor is integrated with all functional applications of the APOand accordingly it can determine the different alert types from thedifferent applications. In order to display the actual alerts for thesealert types, you must set them in the alert monitor profiles. An alert typereflects a possible business problem situation (such as a supply shortage);the alert is the actual case in which, for example, a sales order xy cannotbe covered because the stock or the capacities are not sufficient for that.This note provides an overview of the alert types that exist in APO andgives a short description in each case.

Other termsAPO, alert monitor, consulting, settings, alert profiles, profilemaintenance

Reason and PrerequisitesAOT (alert object type) is a group of alert types that belong togetherfrom a business perspective and that are technically summarized and shownin a common grid display, that is, they have a standard output structure.An example of an AOT would be order alerts - product-dependent (200).ATID (alert type ID) is the type of an exceptional situation. For example,order has shortage (22).The alert itself, as it appears in the display, is an instance of an alerttype, if, for example, there is not enough of part yz to cover sales orderxy.

New alert types for APO Release 3.1 (AOT/ATID):

o 0055/0551 Maturation time not completed (requirement)

o 0055/0552 Maturation time not completed (receipt)

o 0055/0553 Shelf life too short (requirement)

o 0055/0554 Shelf life too short (receipt)

o 0055/0555 Shelf life too long (requirement)

o 0055/0556 Shelf life too long (receipt)

o 0055/0557 Receipt without pegging relationship with expiration date

o 0260/0261 Below minimum days' supply (DB)

o 0570/0571 Campaign interrupted

o 0570/0572 Setup or clean-out order lies within a campaign

10.05.2011 of 26


o 0665/0665 Container-conforming pegging violated

o 1200/1201 Sales scheduling agreement: Message from admissibilitycheck

o 1200/1202 Sales scheduling agreement: Message from feasibilitycheck

o 1210/1211 Sales scheduling agreement: Message re product

o 1220/1221<object> Confirmation relating to procurement schedulingagreement

o 3700/3701 Violation of quantity-based plan validity

o 3700/3702 Violation of time-based plan validity

o 3700/3703 Remaining requirements at component level

o 4000/1111 Requirements planning - macro message alerts

o 6001/6101 Alert from the Supply Chain Event Management

New alert types for SCM Release 4.0 (AOT / ATID):

o 0100/0034 Sales scheduling agreement in past

o 0250/0252 Required days' supply exceeded

o 0600/0601 Machine breakdown (SCEM)

o 0660/0066 Quantity set to 0 (container resource)

o 0900/0901 Exception for procurement planning

o 1700/1702 Demand planned after latest start date/time

o 1700/1703 Demand planned before earliest start date/time

o 1700/1704 Demand not planned

o 1760/1762 Average resource overutilization

o 1760/1763 Average resource underutilization

o 1760/1764 Capacity overload on bucket resource

o 4500/0426 Upper limit of customer-specific errors exceeded

o 5100/5101 Confirmed delivery quantity different

o 5100/5102 Confirmation received for non-existent delivery

o 5100/5103 Notification of different delivery date

o 5100/5104 Different products in proof of delivery

10.05.2011 of 26


o 5100/5105 Delivery number exists more than once

o 5100/5106 Delivery item does not exist

o 5200/5201 Open PO quantity < TLB quantity

o 5200/5202 Open PO quantity > TLB quantity + stock in transit

o 5200/5203 Order item does not exist

o 5200/5204 IDOC stock in transit larger than stock in transit in theAPO

o 5200/5205 Key figure missing in message item

o 5300/5301 VMI - master data alert

o 6002/0005 No response from TSP

New alert types for SCM Release 410 (AOT/ATID):

o 0210/0211 Confirmed quantity exceeds requested quantity

o 0210/0212 Confirmed quantity less than requested quantity

o 0400/0415 Linking of modes between orders violated

o 0500/0516 Linking of modes violated in an order

o 0620/0625 Non-interruptible activity interrupted by a break

o 0620/0626 Activity violates synchronization on the resource

o 0655/0657 Resource overload in bucket (PP/DS)

o 1500/1503 Transport does not adhere to rules

New alert types for SCM release 5.0 (AOT / ATID):

o 0200/0235 Order scheduled without consideration of block limits

o 0500/0517 Minimum interval in order violated due to block limitscheduling

o 2500/2501 Capacity of handling unit too low

o 2500/2502 Capacity of resource too low

o 2500/2503 Capacity of storage location too low

o 2500/2504 Material quantity too low in storage location

o 2500/2505 Material quantity too low in handling unit

o 2500/2506 No access to storage location

10.05.2011 of 26


o 2500/2507 No access to handling unit

o 2500/2508 Resource break

o 2500/2509 Additional handling unit

o 2500/2510 Additional material quantity

o 2500/2511 General error in WM warehouse task

o 2530/2531 General error in transfer posting

o 2550/2551 Stock removal rejection

o 2550/2552 General error in warehouse request

o 2560/2561 General error in wave

o 2580/2581 General error in quality check

o 2590/2591 General error in WM physical inventory

o 4100/4102 Time-based violation with demand combination

o 4100/4103 Quantity-Based violation with demand combination

o 6000/6003 Order changed in OLTP

o 6001/6012 Transport: Resource overloaded

SolutionCurrent alert list (sorted according to application):

PP/DS

AOT 0050: Requirement/receipt alerts (Date/time alerts)

o ATID 0003: Product too late (fixed pegging)

The requirement of an order (input node) comes chronologicallybefore the receipt pegged with it (output node).

This delay is longer than the alert threshold defined in thelocation product master for a delay.

The alert is displayed in the requirements node.

o ATID 0004: Receipt date violated (fixed pegging)



10.05.2011 of 26


The alert is displayed in the receipt node.

o ATID 0005: Product too late (dynamic pegging)




o ATID 0006: Receipt date violated (dynamic pegging)




o ATID 0011: Product too early (fixed pegging)

The receipt of a product is further in advance of therequirement pegged with it than specified by the alertthreshold for earliness defined in the location product master.


o ATID 0012: Receipt date too early (fixed pegging)



o ATID 0013: Requirement with characteristics mismatches (fixedpegging)

A base planning object does not match the product due to itscharacteristics.

Characteristics mismatches may occur if orders in a fixedpegging network are changed manually. The alert is triggeredwhen a receipt element and a requirement element are peggedwith each other but they have an incompatible characteristic(such as color).

This alert is displayed in the requirements node of the peggingrelationship in question.

o ATID 0014: Receipt with characteristics mismatches (fixed pegging)

A part does not match the product due to its characteristics.

10.05.2011 of 26


Characteristics mismatches may occur if orders in a fixedpegging network are changed manually. The alert is triggeredwhen a receipt element and a requirement element are peggedwith each other but they have an incompatible characteristic(such as color).

This alert is displayed in the receipt node of the peggingrelationship in question.

o ATID 0017: Product too early (dynamic pegging)



o ATID 0018: Receipt date too early (dynamic Peg.)



AOT 0055: Shelf life alerts

o ATID 0551: Maturation time not completed (requirement)

A product has a requirement, the date of which comes before theend of the required minimum maturation time.

The alert is displayed in the requirements node of the peggingrelationship in question.

o ATID 0552: Maturation time not completed (receipt)

A product has a requirement, the date of which comes before theend of the required minimum maturation time.

The alert is displayed in the receipt node of the peggingrelationship in question.

o ATID 0553: Shelf life too short (Demand)

A product has already exceeded its minimum shelf life at thetime of the pegged requirement.


o ATID 0554: Shelf life too short (receipt)

A product has already exceeded its minimum shelf life at thetime of the pegged requirement.

The alert is displayed in the receipt node of the pegging

10.05.2011 of 26


relationship in question.

o ATID 0555: Shelf life too long (requirement)

The expiration date is after the required maximum shelf life.


o ATID 0556: Shelf life too long (receipt)

The expiration date is after the required maximum shelf life.

The alert is displayed in the receipt node of the peggingrelationship in question.

o ATID 0557: Receipt without pegging relationship with expirationdate alert

A receipt that is still not pegged with a requirement (surplus)expires in the examination period.

The alert is displayed only if the surplus is also in theexamination period.

AOT 0100: Order in the past

o ATID 0030: Sales order in the past

The requirement of a sales order is in the past but it has notyet been confirmed.

o ATID 0031: Receipt date in the past

A receipt date is in the past but the receipt has not yet beenposted or the inward delivery completed indicator has not yetbeen set.

o ATID 0032: Start date in the past

The start date of an order is in the past but the order has notyet been started (production order) or there is still an openrequirement in the receipt node for a stock transport.

As of SCM release 4.0, the alert is not displayed for a purelyexternal procurement.

o ATID 0033: Opening date in the past

The opening date of an order is in the past but thecorresponding planned order has not yet been converted into aproduction order or the corresponding purchase requisition hasnot yet been converted into a purchase order.

In-house production:

Opening date = start date - opening period

10.05.2011 of 26


External procurement:

Opening date = delivery date - planned delivery time - openingperiod

o ATID 0034: Sales scheduling agreement in the past

The alert is the counterpart of the ATID 0030 alert forscheduling agreements.

AOT 0150: Operation alerts

o ATID 0001: Confirmation date (operation) in the past

The end date/time of a suboperation of a production order is inthe past but the operation has not been confirmed.

AOT 0200: Order alerts - product-dependent

o ATID 0021: Order creates surplus

There are remaining quantities after all receipts andrequirements are pegged.

o ATID 0022: Order has shortage

A requirement cannot be covered after all receipts andrequirements are pegged.

o ATID 0230: External RFQ process not started

A bid invitation has not yet been converted into a purchaseorder.

o ATID 0235: Order scheduled without consideration of block limits

A receipt/dispatch of an activity is not scheduled to the limitof the corresponding block even though the activity is in ablock for which the 'Consideration of block limits' indicatorwas set.

Setup activities and continual nodes are not taken intoaccount.

AOT 0210: Underconfirmation/overconfirmation alerts

o ATID 0211: Confirmed quantity exceeds requirement quantity

The confirmed quantity for an order exceeds the requirementquantity.

o ATID 0212: Confirmed quantity less then requirement quantity

The confirmed quantity for an order is less than therequirement quantity.

AOT 0250: Days' supply alerts

10.05.2011 of 26


o ATID 0001: Below minimum days' supply

The forecasted days' supply from the preset days' supply typesof a location product is less than the required minimum days'supply.

o ATID 0252: Required days' supply exceeded

The forecasted days' supply from the preset days' supply typesof a location product exceeds the required minimum days'supply.

AOT 0260: Days' supply alerts (database)

o ATID 0261: Below minimum days' supply (DB)

The forecasted days' supply from the preset days' supply typesof a location product is less than the required minimum days'supply.

The alert is stored on the database.

AOT 0300: Order alerts - product-independent

o ATID 0041: Order not scheduled

An order was created but it is (partially) deallocated.

o ATID 0042: Order outside its validity period

The start date/time of an activity of the order lies outsidethe effectivity period (of its validity period) of this order.

AOT 0400: Constraint alerts - cross-order

o ATID 0011: Below minimum interval between orders

The preset minimum interval between two orders was notachieved.

o ATID 0013: Maximum interval between orders exceeded

The preset maximum interval between two orders was exceeded.

o ATID 0415: Linking of modes between orders violated

The mode linkage was activated for two activities that arepegged with each other. This alert is triggered if the twoactivities run on different modes.

AOT 0500: Constraint alerts within order

o ATID 0012: Below minimum interval within an order

The preset minimum interval between two activities within anorder was not achieved.

10.05.2011 of 26


o ATID 0014: Maximum interval within an order exceeded

The preset maximum interval between two activities within anorder was exceeded.

o ATID 0516: Linking of modes violated in an order

The mode linkage was activated for two activities that arepegged with each other. This alert is triggered if the twoactivities run on different modes.

o ATID 0517: Minimum interval in order violated due to block limitscheduling

The preset minimum interval between two activities within anorder was not achieved due to the block limit scheduling.

If you select only alert types 0012 & 0014 in the alertprofile, the system also generates the constraint alerts thatwere caused due to the block planning but these constraintalerts do not contain the information that it was the blockplanning that caused the alert situation.

If you select alert types 0012 & 0014 and also alert 0517, thesystem generates constraint alerts that are caused by blockplanning scheduling only as alert 0517.

If you select only alert type 0517 in the alert profile, thesystem generates only the constraint alerts that were causeddue to the block limit scheduling.

AOT 0570: Campaign alerts

o ATID 0571: Campaign is interrupted

On a resource, there are several orders combined into acampaign that all require the same setup status. There is anorder in this campaign that requires another setup status. Thistriggers the alert.

o ATID 0572: Setup or clean-out order lies within a campaign

Set-up and clean-out orders should always be at the beginningor at the end of the campaign. The alert is triggered if theyare between two orders belonging to a campaign.

AOT 0600: Resource alerts PP/DS

o ATID 0052: Resource overload on single-activity resource

Two activities are simultaneously scheduled on a resource.

o ATID 0053: Resource overload on multiactivity resource

More activities than allowed are scheduled simultaneously on aresource or the maximum resource utilization is exceeded.

10.05.2011 of 26


o ATID 0054: Characteristics mismatches on resource

An activity containing a characteristic attribute (such ascolor) that does not match the time is scheduled on a resource.

o ATID 0601: Machine breakdown (SCEM)

The breakdown of a resource was detected in Supply Chain EventManagement.

AOT 0620: Alerts for activities on a resource

o ATID 0625: Non-interruptible activity interrupted by a break

A non-interruptible activity is interrupted by a break.

o ATID 0626: Activity violates synchronization on the resource

An activity violates the synchronization on a resource.

AOT 0650: Average resource utilization (PP/DS)

o ATID 0001: Average resource overutilization

The average utilization of a resource over a certain period(bucket) is greater than the threshold value defined in thealert profile.

o ATID 0002: Average resource underutilization

The average utilization of a resource over a certain period(bucket) is less than the threshold value defined in the alertprofile.

o ATID 0051: Resource overload on bucket resource

The planned utilization of a resource within a period (bucket)is greater than the available capacity.

AOT 0655: Resource utilization on bucket resource (PP/DS)

o ATID 0657: Resource overload on bucket resource (PP/DS)

The planned utilization of a resource within a period (bucket)is greater than the available capacity.

AOT 0660: Container resource alerts

o ATID 0061: Maximum quantity exceeded (container resource)

The system generates this alert when the quantity in thecontainer exceeds the maximum fill level entered in theresource master.

o ATID 0062: Minimum production quantity shortfall (containerresource)

10.05.2011 of 26


There is a shortfall of the minimum production quantity of thecontainer resource.

o ATID 0063: Stock < 0 (container resource)

The system generates this alert when the quantity in thecontainer is theoretically less than zero. This situation canoccur only in connection with shortages.

o ATID 0064: Filling violates allowed remaining quantity (containerresource)

For a production, a container must drop below a certain maximumquantity again before it can be refilled.

o ATID 0065: Invalid combination (container resource)

Two materials that you want to fill into the container cannotbe processed with each other.

o ATID 0066: Quantity set to 0 (container resource)

The system generates this alert when you try to fill a productinto a container in which there is another product.

AOT 0665: Container resource alerts - cross-order

o ATID 0665: Container-conforming pegging violated

The system generates this alert when two orders are pegged witheach other and one order accesses a container resource but theother one does not, or when both orders access differentcontainer resources, that is, the receipt fills a differentcontainer resource than the resource used by the requirement.

AOT 0700: Problem in the order network (Receipt/requirement)

o ATID 0060: Requirement with problem in the order network

A requirement selected from the alert profile is affected by aproblem that exists in the previous order network.

It may take a long time for the system to determine this alert,depending on the size of the previous order network.

o ATID 0061: Receipt with problem in the order network

A receipt selected from the alert profile is affected by aproblem that exists in the order network.

It may take a long time for the system to determine this alert,depending on the size of the order network.

AOT 0750: Problem in the order network (order)

o ATID 0070: Order with problem in the order network

10.05.2011 of 26


An order selected from the alert profile is affected by aproblem that exists in the previous order network.

It may take a long time for the system to determine this alert,depending on the size of the order network

AOT 0900: Planning heuristic alerts

o ATID 0901: Exceptions during the procurement planning

Several exceptions may occur during a planning heuristic. Theseexceptions are usually stored in the planning log. However,selected business messages can also be written to the alertdatabase and can be displayed in the alert monitor using thisalert type.

AOT 1100: Bid invitation alerts (collaborative planning)

o ATID 1101: Quotation received for RFQ process

The creator of an RFQ has received a new quotation.

o ATID 1102: Decision date/time of the RFQ exceeded

The deadline for decision for received quotations has expiredand a decision has not been reached.

o ATID 1103: No quotation received for RFQ

A quotation has not yet been received for an RFQ.

o ATID 1104: No quotation for RFQ, end date/time exceeded.

The deadline for decision for an RFQ has already been exceededand a quotation has not been received.

o ATID 1111: Response to RFQ process not yet created

A quotation has not yet been created for a received RFQ (thealert occurs for the supplier).

o ATID 1112: RFQ was withdrawn

An RFQ that was already received was withdrawn again.

The system generates the alert for the supplier, regardless ofwhether a quotation was already created for the RFQ.

o ATID 1113: Inquiry was changed

An RFQ that was already received was changed again.

The system generates the alert for the supplier, regardless ofwhether a quotation was already created for the RFQ.

AOT 1200: Sales scheduling agreement alerts - Schedulingagreement

10.05.2011 of 26


o ATID 1201: Sales scheduling agreement: Message from admissibilitycheck

This alert represents the total of all checks that are carriedout when an operative delivery schedule is entered.

The alert situation decides whether the scheduling agreementrelease can be processed automatically.

o ATID 1202: Sales scheduling agreement: Message from feasibilitycheck

Check of feasibility with regard to quantities and dates on thebasis of the stocks and the existing production program.

This check/alert is based on an actual scheduling agreement.

AOT 1210: Sales scheduling agreement alerts - Product

o ATID 1211: Sales scheduling agreement: Message re product

This alert results from a feasibility check and refers to aproduct.

AOT 1220: Procurement scheduling agreement alerts - LP

o ATID 1221: Confirmation relating to procurement schedulingagreement

This alert results from the check to determine whether atolerance was exceeded in the confirmation for a procurementscheduling agreement.

AOT 1301: Stock alerts

o ATID 1301: Stock fallen below safety stock level

The stock falls below the safety stock set in the locationproduct master.

o ATID 1302: Stock fallen below target stock level

The stock falls below the target stock set in the locationproduct master.

o ATID 1303: Stock exceeds target stock level

The stock exceeds the target stock level set in the locationproduct master.

TLB

AOT 1000: Deployment - product alerts

o ATID 2200: Fair share situation

10.05.2011 of 26


The available quantity is not sufficient to cover allrequirements.

o ATID 2201: Fair share situation with customers

Deployment run results in proportional distribution to thecustomers.

AOT 1500: Transport alerts - utilizations

o ATID 1503: Transport does not adhere to the rules

Alert from the new TLB: Rule profile was violated.

o ATID 2100: Means of transport overloaded

Volume, weight or number of pallet positions exceeded.

o ATID 2101: Shortfall of minimum utilization of a means of transport

There is a shortfall of the minimum volume, weight or number ofpallet positions.

o ATID 2102: Invalid order scheduling

Scheduling planned outside the possible periods

AOT 1501: Transport alerts - Delivery dates

o There is currently no active alert

MSP

AOT 1700: MSP maintenance object alerts

o ATID 1701: Compliance date exceeded

For legal reasons or specifications from the manufacturer,maintenance objects must only remain in use until a certaindate specified by the compliance date. The basis for definingthis date consists of flight hours, landing cycles, operatingtimes, and counter readings. If a maintenance object is used upuntil the compliance date (which is usually avoided inpractice), the utilization is 100%. If no maintenance has takenplace by the compliance date, the maintenance object must notbe used after this date. The object can only be used againafter appropriate maintenance has been performed.

o ATID 1702: Demand planned after latest start date/time

This alert is issued for each maintenance demand that isplanned after the latest start date(of the demand).

o ATID 1703: Demand planned before earliest start date/time

This alert is issued for each maintenance demand that isplanned before the earliest start date(of the demand).

10.05.2011 of 26


o ATID 1704: Demand not planned

This alert is issued for each unplanned maintenance demand.

AOT 1760: MSP-resource-alerts

o ATID 1762: Average resource overutilization

This alert is determined in PP and corresponds to the similaralert of AOT 650.

o ATID 1763: Average resource underutilization


o ATID 1764: resource overload on bucket resource


EWM

AOT 2500: WM: Warehouse task

A warehouse task is a document used to execute goods movements. A warehousetask can be based on logical or physical goods movements or changes tostocks. These include stock removals, putaways, internal movements, postingchanges, goods receipt postings and goods issue postings.The following alert types represent possible problems that may arise in awarehouse task.

o 2500/2501 Capacity of handling unit too low

o 2500/2502 Capacity of resource too low

o 2500/2503 Capacity of storage location too low

o 2500/2504 Material quantity too low in storage location

o 2500/2505 Material quantity too low in handling unit

o 2500/2506 No access to storage location

o 2500/2507 No access to handling unit

o 2500/2508 Resource break

o 2500/2509 Additional handling unit

o 2500/2510 Additional material quantity

o 2500/2511 General error in WM warehouse task

AOT 2530: WM: Posting changes

10.05.2011 of 26


A posting change is a change in stock attributes in the warehouse but thegoods remain in the same physical location.

o 2530/2531 General error in posting change

AOT 2550: WM: Warehouse request

A warehouse request is a document that facilitates the processing ofwarehouse activities for a certain product. The warehouse activities forthe product include picking, putaway, posting changes, stock transfers(within the warehouse), and scrapping.

o 2550/2551 Stock removal rejection

o 2550/2552 General error in warehouse request

AOT 2560: WM: Wave

A wave includes warehouse request items that are due at a similardate/time.Items of warehouse requests that exist in the system can be combined towaves. The system transfers the items contained in a wave to the warehouserequest creation at the same time (the release time of the wave). Ittransfers the created warehouse request items together to the warehouseorder creation.

o 2560/2561 General error in wave

AOT 2580: WM: Check document

A check document ...

o 2580/2581 General error in quality check

AOT 2590: WM: Physical inventory

Inventories are carried out using PI documents.The physical inventory document is used to plan and carry out the physicalinventory, to enter the payment data and to post differences.

o 2590/2591 General error in WM physical inventory

ATP

AOT 3000: ATP - Product availability/check against forecastalerts

o ATID 3001: Availability check: shortage

An exception occurred in the availability check.

o ATID 3002: Check against forecast: shortage

An exception occurred in the forecast check.

o ATID 3003: Availability check: shortage (neutral result)

10.05.2011 of 26


An exception occurred in the availability check but the salesorder was accepted despite this.

o ATID 3004: Check against forecast: shortage (neutral result)

An exception occurred in the forecast check but the sales orderwas accepted despite this.

AOT 3500: ATP - Product allocation alerts

o ATID 3003: Product allocation: shortage

An exception occurred during the product allocation check.

o ATID 3006: Product allocation: shortage (neutral result)

It cannot be selected.

AOT 3600: ATP - Order alerts

o ATID 0001: ATID 0001: Check availability. Order due date changed byVS

An existing order was rescheduled by Vehicle Scheduling. Forthis reason, the availability must be checked again.

This alert corresponds to the Check availability as orderdate was changed by Vehicle Scheduling alert of AOT6000.

AOT 3700: ATP - Plan validity violation

o ATID 3701: Violation of quantity-based plan validity

In an order, the order quantity lies outside the quantity-basedvalidity of the source of supply for in-house production.

o ATID 3702: Violation of time-based plan validity

In an order, the order quantity lies outside the validityperiod of the source of supply for in-house production.

o ATID 3703: Remaining requirements at component level

A certain quantity of an order could not be converted because,for example, no valid source of supply for in-house productionis available.

This alert is determined at component level only.

SDP

AOT 4000: SDP - Database macro alerts

o ATID 0100: Requirement undercoverage (DB-alert)

10.05.2011 of 26


A requirement undercoverage is determined on a bucket resourceof a certain planning book.

The alert is written either in a background planning ormanually from a planning book to the alert database.

o ATID 0101: Target stock level exceeded (DB alert)

The target stock level is exceeded in a bucket of a certainplanning book.

o ATID 0102: Target stock level shortfall (DB alert)

There is a shortfall of the target stock level in a bucket of acertain planning book.

o ATID 0103: Shortfall below safety stock (DB alert)

There is a shortfall of the safety stock in a bucket of acertain planning book,.

o ATID 1000: Resource overload in bucket (DB alert)

In a bucket of a certain planning book, there is a resourceoverload.

o ATID 1001: Insufficient resource utilization in bucket (DB alert)

A resource is not utilized sufficiently in a bucket of acertain planning book.

o ATID 1002: Resource utilization in the bucket = 100% (DB alert)

In a bucket of a certain planning book, a resource is utilizedat exactly 100%. The resource may become a bottleneck.

o ATID 1111: Requirements planning - macro message alerts

Alert types that can be used in macros but that are deliveredunspecified from a business perspective.

o ATID 4100: Requirements planning - macro status alerts


o ATID 4101: Requirements planning - macro message alerts


AOT 4100: SDP - Requirement combination alerts (DB)

o ATID 4102: Time-based violation in demand combination

o ATID 4103: Quantity-based violation in demand combination

10.05.2011 of 26


AOT 4200: SDP - Dynamic Alerts

o ATID 0100: Requirement undercoverage (dynamic alert)

There is a demand shortage in a bucket of a certain planningbook.

When the alert monitor is called, dynamic alerts areautomatically determined from the current data of the planningbook, regardless of whether the alert monitor is called in theplanning book or as an independent transaction(/SAPAPO/AMON1). It is a prerequisite that the correspondingmacro is defined as a default macro.

o ATID 0101: Target stock level exceeded (dynamic alert)

The target stock level is exceeded in a bucket of a certainplanning book.

o ATID 0102: Target stock level shortfall (dynamic alert)

There is a shortfall of the target stock level in a bucket of acertain planning book.

o ATID 0103: Shortfall below safety stock (dynamic alert)

There is a shortfall of the safety stock in a bucket of acertain planning book.

o ATID 1000: Resource overload in bucket (dynamic alert)

In a bucket of a certain planning book, there is a resourceoverload.

o ATID 1001: Insufficient resource utilization in bucket (dynamicalert)

A resource is not utilized sufficiently in a bucket of acertain planning book.

o ATID 1002: Resource utilization in the bucket = 100% (DB alert)

In a bucket of a certain planning book, a resource is utilizedat exactly 100%. The resource may become a bottleneck.

.

FCS

AOT 4500: Requirements planning - forecast alerts

o ATID 0411: The forecast could not be executed

This alert is triggered if the forecast terminates with anerror. For background processing, you can set which situationthe system reads as an error in the activity for massprocessing.

10.05.2011 of 26


o ATID 0420: Upper limit of MAD exceeded

Check of different error measures in univariate forecasting.

o ATID 0421: Upper limit of error total exceeded


o ATID 0422: Upper limit of MPE exceeded


o ATID 0423: Upper limit of MAPE exceeded


o ATID 0424: Upper limit of MSE exceeded


o ATID 0425: Upper limit of RMSE exceeded


o ATID 0426: Upper limit of customer-specific errors exceeded

The alert arises from customer-specific error measures thatwere defined using the BAdI.

BAdI: /sapapo/sdp_fcsterr, Method: error_calculate

o ATID 0440: MLR: Upper limit of MAPE exceeded

Check of different error measures in multi-linear regression(several factors are taken into account in the regressionanalysis).

o ATID 0441: MLR: Shortfall of lower limit of R**2


o ATID 0442: MLR: Shortfall of lower limit of adjusted R**2


o ATID 0443: MLR: Shortfall of lower limit of Durbin-Watson


o ATID 0444: MLR: Upper limit of Durbin-Watson exceeded

10.05.2011 of 26



o ATID 0445: MLR: R**2 > Durbin-Watson


o ATID 0446: MLR: Upper limit of Durbin-h exceeded

Check of different error dimensions in multilinear regression(several f actors are taken into account in the regressionanalysis).

o ATID 0447: MLR: Shortfall of lower limit of T-test

Check of different error dimensions in multilinear regression(several f actors are taken into account in the regressionanalysis).

VMI

AOT 5100: VMI - Proof of delivery alerts

o ATID 5101: Confirmed delivery quantity different

The confirmed delivery quantity is different from the quantityin the actual delivery.

o ATID 5102: Confirmation received for non-existent delivery

The delivery number that is displayed in the proof of deliverydoes not exist.

o ATID 5103: Notification of different delivery date

The notification has been received that the delivery date isdifferent.

The delivery date is different from the planned delivery date.

o ATID 5104: Different products in proof of delivery

The products in the proof of delivery are different from theactual delivery.

o ATID 5105: Delivery number exists more than once

The delivery number in the proof of delivery already exists.

o ATID 5106: Delivery item does not exist

The delivery item in the proof of delivery does not exist.

10.05.2011 of 26


AOT 5200: VMI - Product Activity alerts

o ATID 5201: Open PO quantity < TLB quantity

The open purchase order quantity for the product is less thanthe quantity in all TLB orders.

o ATID 5202: Open PO quantity > TLB quantity + stock in transit

The open purchase order quantity for the product is greaterthan the total of the quantities of all TLB orders plus thestock in transit.

o ATID 5203: Order item does not exist

The order item in the TLB order does not exist.

o ATID 5204: IDOC stock in transit larger than stock in transit inAPO

The stock in transit from the PROACT IDOC is larger than thedetermined stock in transit in APO.

o ATID 5205: Key figure missing in message item

The key figure for the open purchase order quantity or thetransit quantity for example, does not exist in the messageitem of the PROACT IDOC.

AOT 5300: VMI - Master data alerts

o ATID 5301: VMI - Master data alert

Incompatible or non-existing master data is used in themessage.

VS

AOT 6000: Vehicle Scheduling - order alerts

o ATID 0001: Check availability. Order due date changed by VS

An existing order was rescheduled by Vehicle Scheduling. Forthis reason, the availability must be checked again.

o ATID 0002: Order not planned in transportation planning

The order was not scheduled in a transportation. There may beseveral reasons for this:

No suitable transportation lane or resource was found for thetransportation of the order.

Non-delivery costs are lower than the correspondingtransportation costs and the costs for earliness/delay.

The optimizer could not find a solution during the runtime

10.05.2011 of 26


allocated.

o ATID 6003: Order was changed in the OLTP

You can use this alert in the TP/VS check rule to recognize ifan order that is already assigned to a transportation has beenchanged in the OLTP.

AOT 6001: Vehicle Scheduling - transportation alerts

o ATID 0001: No transportation service provider found

A suitable transportation service provider to carry out atransportation was not found. The following may be the reasonsfor this:

No transportation service provider is assigned to thetransportation lane.

The capacity of the transportation service provider is notsufficient to carry out a transportation (Error occurs only inthe case of an automatic assignment if product scheduling iscarried out).

o ATID 6101: Alert from the Supply Chain Event Management

This alert is used in the TP/VS in the bid invitation, which ismonitored in the SCEM (if set).

o ATID 6012: Transportation: Resource is overloaded

This alert shows that a quantity transported exceeds theexisting capacity of the transportation resource.

This situation may occur if the transportation resource ismanually overloaded or if the order quantity increases afterthe transportation is created.

AOT 6002: Vehicle Scheduling - tendering alerts

o ATID 0001: Proposed shipment declined by TSP

The proposed transportation was declined by the transportationservice provider.

o ATID 0002: Proposed delivery date changed by TSP

Date proposals (planned departure/arrival) were changed by thetransportation service provider (planned transportation).

o ATID 0003: Proposed delivery date already in execution changed byexternal TSP

Date proposals (planned departure/arrival) were changed by thetransportation service provider (transportations alreadytransferred to OLTP).

o ATID 0004: Transfer order already in execution rejected by external

10.05.2011 of 26


TSP

A transportation already transferred to OLTP was declined bythe transportation service provider.

o ATID 0005: No response from transportation service provider

There is no response from the transportation service providerduring the bid invitation.

AOT 6010: Vehicle Scheduling - resource alerts

o ATID 0001: Loading resource is overloaded

A loading resource (inbound/outbound) is overloaded. Thishappens only if several planners are simultaneously workingwith the same locations to which loading resources areassigned.

Header Data

Release Status: Released for CustomerReleased on: 17.09.2009 07:48:22Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: SCM-APO-AMO Alert Monitor

Secondary Components:SCM-BAS-AMO Alert Monitor

The Note is release-independent

Related Notes

Number Short Text

826285 SDP/DP: Layouts for SDP/DP alerts are lost

825118 Performance optimization: building the hierarchy tree

820523 AMON on ITS - Context overflow / Memory allocation failure

808671 PP: LiveCache alerts out of the given validity are displayed

796769 SDP:Absolute threshold values for user-spec. supply shortage

10.05.2011 of 26


Number Short Text

781319 Creating a user-defined alert type

759125 Unpegged receipt with expiration date: Alert not displayed

755997 Modification: Start Date in the Past Alert for ext. proc.

750075 Modification: Shipping alerts without URL in the mail text

646818 Neutral results alerts in the availability check

609592 PERF: Using an index for the read status

545786 Authorization checks in the Alert Monitor

510189 SDP: Definition of user-defined texts for the display

508324 PP: Taking resources/ATP cat. selections into account

500889 When are shortage alerts generated for ATP?

500063 Overview of performance notes for the Alert Monitor

495166 Tips and Tricks for Handling Alert Monitor

443675 FCS: Use of selections when determining alerts

429053 Prioritization alert 'Shortf. in min. int. within order'

425448 Different cycles of operations of the monitor's Alert

422866 User-specific display hierarchies require change request

421222 APO 3.0: Authorisation for Alert Monitor

405804 Functionality: alternative alert text in MiniApp

374624 APO overcoverage alerts for safety stock

374265 CALL_FUNCTION_PARM_MISSING when calling alert monitor

373434 Use of threshold values in Alert Monitor Profile

371867 AMON date alerts display incorrect quantity

367757 AMON: Profile maintenance 'Average resource utilization'

367103 Working w/ threshold values in Alert Monitor profile

361495 Definition of checkboxes in PP/DS profile unclear

Attributes

Attribute Value

Transaction codes /SAPAPO/AMON1

Transaction codes /SAPAPO/AMON_SETTING

Transaktionscodes - manuell /SAPAPO/AMON1

Transaktionscodes - manuell /SAPAPO/AMON_SETTING

alert types

Documents

alert profiles

different alert types

alert monitor profiles

group of alert types

supply shortagethe alert

atid alert type id

sales scheduling agreement

shelf life