0% found this document useful (0 votes)
410 views4 pages

User Transaction Guide Stahl Sap 4.7: Trigger

The document provides instructions for using the SAP transaction code CO09 to check the availability of materials in the system. It describes the key input fields needed, including material, plant, and checking rule. It then explains that the transaction will output the current material status as the cumulative available-to-promise quantity. Finally, it provides tips on how the availability check uses available-to-promise logic to determine if and when material requirements can be fully covered.

Uploaded by

guilherme
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
410 views4 pages

User Transaction Guide Stahl Sap 4.7: Trigger

The document provides instructions for using the SAP transaction code CO09 to check the availability of materials in the system. It describes the key input fields needed, including material, plant, and checking rule. It then explains that the transaction will output the current material status as the cumulative available-to-promise quantity. Finally, it provides tips on how the availability check uses available-to-promise logic to determine if and when material requirements can be fully covered.

Uploaded by

guilherme
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

USER TRANSACTION GUIDE STAHL SAP 4.

7
Function Module : Process Planning

Process Area : Material Requirements Planning

Transaction : CO09

Transaction Name : Availability overview

Author : Jacques van Riel

Last change date : 11/15/2004 03:27:00 PM

Trigger:

Prior to initiating production, the SAP R/3 system enables the production planner to verify the
availability of material required to satisfy requirements.

Business Process Procedure Overview


R/3 Enterprise
Production logistics
Availability of Material Overview

Input - Required Fields Field Value / Comments


Material Material for which an overview check is to be performed.
Plant Production Plant
Checking Rule Rule that defines the checking procedure to be used for the availability check.

OUTPUT - RESULTS COMMENTS


Current Material Status Cumulative ATP quantity for material

Tips and Tricks

The availability is determined according to the ATP (available to promise) method. Using
this method, the system checks :
 whether the material requirements can be covered on the requirements date, and
 at what point in time the requirements can be covered, if a full coverage of the
requirements is not possible on the requirements date.

Procedural Steps

1.1 Access the transaction by:

Via Menus Logistics  Production  Production Control


Control  Availability Overview, OR

Logistics  Production  KANBAN  Environment  Production Orders 


Control  Availability Overview, OR

Logistics  Production-Process  Production Planning  MPS  Environment 


Availability Overview, OR

Logistics  Project Systems  Resources  Capacity Requirements Planning 


Requirements  Production Order  Control  Availability Overview, OR

Logistics  Central Functions  Batch Management  Tools  Availability


Overview, OR

Accounting  Project Systems  Resources  Capacity Requirements Planning

/conversion/tmp/activity_task_scratch/579613756.doc Page 1 of 4
 Requirements  Production Order  Control  Availability Overview, OR

Logistics  Materials Management  Inventory Management  Environment 


Stock  Availability Overview, OR

Logistics  Sales and Distribution  Sales  Environment  Availability


Overview, OR

Logistics  Logistics Execution  Information System  Goods Receipt  Lists


for Material Stock  Availability Overview, OR

Executive Information System  Cross-Application  Master Data  Display


Stock/Requirements Situation  Capacity Requirements Planning
Via Transaction Code CO09

1.2 On the screen "Availability Overview", enter information in the fields as


specified in the table below:

Field Name Description R/O/C User Action and Values Comments


Material Material for Check R Enter or select via matchcode
Plant Production Plant R Enter or select via matchcode
MRP Area MRP Area number O Enter or select via matchcode
Checking Rule Checking rule for availability check R Enter or select via matchcode
With Reqmts With requirement quantities O Select Check Box
quants
Special Stocks Section Header
Sales Order Sales order number for check (can O Enter or select via matchcode
include item)
WBS Element Work Breakdown Structure Element O Enter or select via matchcode
Sold-to-party Customer number O Enter or select via matchcode
Consignment Consignment stock C Select as required
Ret. packaging Returnable Packaging C Select as required

/conversion/tmp/activity_task_scratch/579613756.doc Page 2 of 4
1.3 Use the ENTER icon to perform the check.

1.4 The “Availability Overview” screen will be presented in display mode.

GENERAL NOTES:

 According to ATP logic, the system checks whether the dependent requirements of each
component are covered by specific receipt and issue elements or by stock. This check is
carried out dynamically; that is, each time you carry out the check, the system
recalculates the current situation. If a quantity can be committed for the requirement date,
the system commits precisely this quantity in the dependent requirements. The ATP
quantity for the components is reduced by this committed quantity. Therefore, in the next
availability check, dependent requirements can only be committed for the amount of the
remaining ATP quantity.

 In planned independent requirements, the system only checks the open planned
independent requirement quantities created for the components. This means that the
ATP quantity is not included in this availability check, and neither are receipts or stocks.

This type of availability check is most useful:


 if assembly planning or phantom assembly planning is used in planning
components, or
 if quick statements about the availability situation are required and the results
from this check are precise enough.

The system uses the open planned independent requirements quantity at the component
level to determine a committed quantity, and this quantity is copied to the planned order
header in the Committed Quantity field. In contrast to the availability check according to
ATP logic, however, the committed quantity is not recorded in the dependent
requirements. The planned independent requirements of the components are not
consumed by the committed quantity but by the complete dependent requirements

/conversion/tmp/activity_task_scratch/579613756.doc Page 3 of 4
quantity. In subsequent availability checks, the system can only commit quantities for the
amount of planned independent requirements that have not yet been consumed.

/conversion/tmp/activity_task_scratch/579613756.doc Page 4 of 4

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy