This document provides an overview of scheduling agreements and their structure in SAP. It describes how scheduling agreement delivery schedule lines can be automatically generated from MRP. It also explains the differences between scheduling agreements created with and without release documentation, and outlines the business process for creating a scheduling agreement with release documentation. This involves creation of the scheduling agreement, assigning a release creation profile, setting up a source list record, generating delivery schedule lines from MRP, and creating scheduling agreement releases.
Guide to Configure Custom SD Output Types in S/4HANA Using BRF+Ashish Saxena
BRF+ is part of SAP provided decision service management tool (DSM) and it is not new in SAP. But doing output management via BRF+ is new in S/4 HANA system. Before knowing how output determination and management is done in S/4 HANA system using BRF+, we must know what is BRF+ and how it works.
BRF+ is comprehensive application programming interface (API) and user interface for defining and processing business rule. It allows us to model rules in an intuitive way and to reuse these rules in different applications.
Guide to Configure Custom SD Output Types in S/4HANA Using BRF+Ashish Saxena
BRF+ is part of SAP provided decision service management tool (DSM) and it is not new in SAP. But doing output management via BRF+ is new in S/4 HANA system. Before knowing how output determination and management is done in S/4 HANA system using BRF+, we must know what is BRF+ and how it works.
BRF+ is comprehensive application programming interface (API) and user interface for defining and processing business rule. It allows us to model rules in an intuitive way and to reuse these rules in different applications.
Recurring inspection means inspection of the material at regular intervals like every month, every year etc. The system can automatically create inspection lots at predefined intervals for selected batch materials. You can plan such inspections by having the system monitor the date for a recurring inspection. Recurring inspections are triggered by a report that you can execute manually or that the system can execute automatically (provided it has been planned as a background job). When recurring inspections are triggered automatically, the background job executes the report, which in turn selects the batches and creates the inspection lots according to your processing parameters. Recurring inspection process widely used in Process industries like Pharmaceutical, Chemical and Food industries
In this presentation , I have covered WM-PP interface. The presentation gives an overview of the concept as well as the process flow with and without the interface.It also talks about the master data and the various parameters that play a key role in the WM-PP processes
Recurring inspection means inspection of the material at regular intervals like every month, every year etc. The system can automatically create inspection lots at predefined intervals for selected batch materials. You can plan such inspections by having the system monitor the date for a recurring inspection. Recurring inspections are triggered by a report that you can execute manually or that the system can execute automatically (provided it has been planned as a background job). When recurring inspections are triggered automatically, the background job executes the report, which in turn selects the batches and creates the inspection lots according to your processing parameters. Recurring inspection process widely used in Process industries like Pharmaceutical, Chemical and Food industries
In this presentation , I have covered WM-PP interface. The presentation gives an overview of the concept as well as the process flow with and without the interface.It also talks about the master data and the various parameters that play a key role in the WM-PP processes
JAVA 2013 IEEE CLOUDCOMPUTING PROJECT Mining contracts for business events an...IEEEGLOBALSOFTTECHNOLOGIES
To Get any Project for CSE, IT ECE, EEE Contact Me @ 09849539085, 09966235788 or mail us - ieeefinalsemprojects@gmail.com-Visit Our Website: www.finalyearprojects.org
Mining contracts for business events and temporal constraints in service enga...IEEEFINALYEARPROJECTS
To Get any Project for CSE, IT ECE, EEE Contact Me @ 09849539085, 09966235788 or mail us - ieeefinalsemprojects@gmail.co¬m-Visit Our Website: www.finalyearprojects.org
Running head ACQUISITION STRATEGY PIEZOELECTRIC EMBEDDED TRA.docxSUBHI7
Running head: ACQUISITION STRATEGY: PIEZOELECTRIC EMBEDDED TRANSDUCERS UNDER WALL GEOSTRUCTURE PROGRAM
4
ACQUISITION STRATEGY: PIEZOELECTRIC EMBEDDED TRANSDUCERS UNDER WALL GEOSTRUCTURE PROGRAM
Acquisition Strategy: Piezoelectric Embedded Transducers (PET)
Under the WALL Geostructure Program
XXXXXX
ASCM 628 Section 9040 2172
University of Maryland University College
March 11, 2017
This strategic plan will specify the details relating to the acquisition of Piezoelectric Embedded Transducers (PET) to be utilized to provide enhanced surveillance capabilities for the new Wide Alignment Limited Loading (WALL) Geostructure Program. As referenced by Kim, Roberts & Brown (2016), United States federal policy and regulatory guidance encourage the use of fixed-price contracts in an effort to secure best value for purchasing groups; therefore, the form of contract that shall be utilized shall be a Fixed Price Economic Price Adjustment (FPEPA) contract to account for the uncertainties of future economic conditions that may cause fluctuations in the future costs of supplies and equipment that the contractor might be required to provide under contract and would not at this time be predictable. Contract Type
Pursuant to 41 USC 253 and 10 USC 2305, competition will be full and open and the contract shall be both severable and non-severable. For the procurement of 1,000 Piezoelectric Embedded Transducers, the contract shall be non-severable; however, any elements relating to their maintenance and non-developmental support and data to be reported shall be considered non-severable. Additionally, given the complexity and technical nature of this service, price alone is not sufficient to determine the award and therefore, the contract will be awarded based on a contracting by negotiation bidding process. Furthermore, it is assumed that the U.S. Immigrations and Customs Enforcement (ICE) Acquisitions Division wishes to hold discussions regarding the contract to ensure that its needs are clearly communicated and met to its satisfaction. To allow ICE to have maximum flexibility in awarding the contract, the trade-off process shall also be initiated.
Planning Fundamentals
The subsequent planning fundamentals shall also be incorporated within this strategic plan as they are essential for the PET sourcing and future negotiations: (1) Contractor Performance Requirements, (2) Deliverables, and (3) Assumptions.
Contractor Performance Requirements and Deliverables
The contractor shall be responsible for providing substantial value to ICE in the form of required hardware to ensure the enhancement of the surveillance capability for the WALL program, software to certify the technical monitoring and successful operation of the hardware, and the non-developmental support and data which will be utilized to analyze the stabilization and sustainabili ...
BSA/515r3 - HWE Website
Contract Plan
Initiating Office:
Project Title:
Requiring Activity:
Estimated Value:
Contract Type:
APPROVALS
Contract Plan is approved.
__________________________________
__________________________________
(Requiring Official) (Requiring Official's Supervisor, if needed)
Date: __________________
Date: ___________________
__________________________________
__________________________________
(Insert name), Contracting Officer
(Insert name), General Counsel
Date: __________________
Date: ___________________
__________________________________
Lorraine Allison, Director, Procurement
Support Office
Date: _________________
A. BACKGROUND AND OBJECTIVES
1. Statement of Need. Introduce the plan by a brief statement of need. Summarize the technical and contractual history. Discuss feasible contract alternatives, prior contracts, and any related in-house efforts.
2. Applicable Conditions. State all significant conditions affecting the system, such as requirements for compatibility with existing or future systems or programs; and any known cost, schedule, and compatibility or performance constraints.
3. Costs and Period of Performance. The projected expenditure for the proposed system is based upon the Independent Government Cost Estimate (IGCE) and is shown below:
PERIOD
COST
PERFORMANCE
Base Year
$0.00
MM/DD/YYYY through MM/DD/YYYY
1st Option Year
$0.00
MM/DD/YYYY through MM/DD/YYYY
3rd Option Year
$0.00
MM/DD/YYYY through MM/DD/YYYY
4th Option Year
$0.00
MM/DD/YYYY through MM/DD/YYYY
Total
$0.00
4. Capability or performance. Specify the required capabilities or performance characteristics of the supplier or the performance standards of the services and how they relate to the need.
5. Delivery or performance-period requirements. Describe the basis for establishing delivery or performance-period requirements. Explain and provide reasons for any urgency or justification for not providing for full and open competition.
6. Trade-offs. Discuss the expected consequences of tradeoffs among the various cost, capability or performance and schedule goals.
7. Risks. Discuss the technical, cost and schedule risks and describe what efforts are being planned to reduce risk and the consequences of failure to achieve goals.
a. Technical:
b. Cost:
c. Schedule:
B. PLAN OF ACTION
1. Product or Service Description. Explain the choice of product or service description types (including performance-based contracting descriptions) to be used in the plan.
2. Potential Sources.
a. Prospective Offerors: Prospective offerors will be identified using…
b. Market Research: Market Research was conducted by …
Address the extent and results of the market research and indicate their impact on the various elements of the plan
3. Competition. The proposed plan will be solicited on a ____ competitive ____ noncompetitive basis.
If full and op ...
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
1. APAC Procurement Business Module
Scheduling Agreement Procedure Training Document
Local Group Companies
Submit Date, 22-Nov-04
<Confidential>
<Other Clause>
Copyright @ 2003 Holcim Services (Asia) Ltd.
2. APBM
Document Control
Document Name Scheduling Agreement Procedure Training Document
Author Ha Tran
File Name & Path
Created 22-Nov-04
Last Edited
Printed on
Version Revision Date Revision Description Author Sign-off
V 1.0 22-Nov-04 Ha Tran
Document Approval
Role Name Signature Date
Distribution List
Role Name Signature Date
Scheduling Agreement Procedure Training Document 2/43
This document is for Super Users Training on 17 – 21 January, 04
3. APBM
Table of Contents
OVERVIEW .......................................................................................................................................... 4
STRUCTURE........................................................................................................................................ 4
AUTOMATIC GENERATION OF SA DELIVERY SCHEDULE LINES ............................................... 5
FIRM ZONE AND TRADE-OFF ZONE ....................................................................................................... 5
SCHEDULING AGREEMENTS WITH AND WITHOUT RELEASE DOCUMENTATION ................... 6
WITHOUT RELEASE DOCUMENTATION (IN THE STANDARD SYSTEM, DOCUMENT TYPE LP) ......................... 6
WITH RELEASE DOCUMENTATION (IN THE STANDARD SYSTEM, DOCUMENT TYPE LPA)............................. 6
CREATE SA RELEASES: ....................................................................................................................... 7
GENERATE SA RELEASES IN THE SCHEDULING AGREEMENT DELIVERY SCHEDULE ................................... 7
EXAMPLE OF THE EXCLUSIVE USE OF FORECAST DELIVERY SCHEDULES:................................................. 8
EXAMPLE OF THE USE OF BOTH FORECAST AND JIT DELIVERY SCHEDULES: ............................................ 8
EXAMPLE: ........................................................................................................................................... 8
BUSINESS PROCESS PROCEDURE............................................................................................... 10
1. CREATION OF SCHEDULING AGREEMENT WITH RELEASE DOCUMENTATION ...................................... 10
2. ASSIGNMENT OF SCHEDULING AGREEMENT RELEASE CREATION PROFILE TO THE MATERIAL MASTER
RECORD ........................................................................................................................................... 19
3. CREATION OF SOURCE LIST RECORD FOR THIS SCHEDULING AGREEMENT SUBJECT TO MRP RUN ..... 25
4. GENERATION OF SA DELIVERY SCHEDULE LINE ITEM FROM MRP ................................................... 29
5. CREATION OF SCHEDULING AGREEMENT RELEASE FOR SA DELIVERY SCHEDULE LINE ITEM ............ 33
Scheduling Agreement Procedure Training Document 3/43
This document is for Super Users Training on 17 – 21 January, 04
4. APBM
Overview
A scheduling agreement is a longer-term arrangement with the vendor covering the supply of
materials subject to predetermined conditions. The conditions are valid for a predefined period and
predefined total purchase quantity.
Scheduling agreements have several advantages:
• Using scheduling agreements enables you to reduce processing times and the amount
of paperwork within the enterprise. A delivery schedule issued against a scheduling
agreement can replace a large number of standard purchase orders or contract release
orders.
Scheduling agreement delivery schedule lines do not constitute an independent
document but are part of the scheduling agreement. Procurement via scheduling
agreements thus enables to reduce the volume of document used.
• Volumes of stock on hand can be reduced to a minimum through application of the Just-
in-Time (JIT) principle, involving the specification of exact delivery time-spots.
• The vendors’ lead times are reduced. It is not necessary to deliver the entire quantity
covered by the scheduling agreement at once; instead, a series of smaller quantities can
be delivered in accordance with the delivery schedule lines. In this case, the vendors
can receive due notification of such required quantities and delivery dates and times well
in advance.
Structure
Scheduling agreements can be created either without reference to another document, or with
reference to an outline agreement requisition, an RFQ, or another scheduling agreement. Since R/3
4.0A, scheduling agreements can also be created with reference to a centrally agreed contract, thus
facilitating the utilization of centrally negotiated prices.
A scheduling agreement consists of number of items, for each of which a procurement type (item
categories) is defined. The following procurement type exist:
• Standard
• Consignment
• Subcontracting
• Third-party
• Stock transfer
• Text
Item categories M and W are not allowed. In the case of scheduling agreement items involving
subcontracting work, the materials or components to be provided to the subcontractor with respect to
each scheduled delivery of the ordered item can be specified.
Conditions can apply to the entire scheduling agreement. Conditions specific to the material to be
delivered must be entered at item level. Their validity can be time-dependent or time-independent,
depending on the document type.
If the scheduling agreement item was created with reference to a centrally agreed contract, the
conditions in the scheduling agreement should not be changed, since the system always refers to
the current conditions of the central contract.
Costs incurred can be distributed/apportioned among different controlling objects through the
account assignment. It is not allowable to use account assignment category ‘U’ (unknown) in
scheduling agreements.
The total quantity of material to be supplied specified in the scheduling agreement item can be
divided into a series of partial quantities with individual delivery dates in the lines of the delivery
Scheduling Agreement Procedure Training Document 4/43
This document is for Super Users Training on 17 – 21 January, 04
5. APBM
schedule for the scheduling agreement ie. delivery of the total quantity of material specified in a
scheduling agreement item is spread over a certain period in a delivery schedule, consisting of lines
indicating the individual quantities with their corresponding planned delivery dates. Scheduling
agreement delivery schedule lines can be created with or without reference to a purchase
requisition. Scheduling agreement delivery schedule lines can also be generated automatically
through material requirements planning (MRP) in R/3.
It is possible to issue scheduling agreement releases (SA releases) notifying the vendor that the
required material shall be delivered on the scheduled dates ie the scheduling agreement releases
(comprising a header and the actual delivery schedule) are issued to the vendor, instructing the
latter to effect deliveries of the relevant material on the dates shown. The scheduling agreements
with or without release documentation can be used which is determined via the document type.
Using various confirmation types, the vendor can indicate to the relevant purchasing organization his
acceptance of delivery dates or inform the enterprise of any variances from planned delivery dates.
Note on the term “release”: In MM Purchasing, this term is used A) as a generic term covering
various kinds of order document issued against outline agreements (these may be release orders
issued against contracts or – as here – scheduling agreement releases, i.e. types of rolling delivery
schedule issued against scheduling agreements), and B) in connection with an internal approval or
expenditure authorization process for purchasing documents. In both cases, “releasing” can be
regarded as equivalent to “giving the green light” to go ahead with a certain action (e.g. to the vendor
to deliver a certain quantity of materials, or to Purchasing to create or issue a PO for items
requested by a user department).
Automatic Generation of SA Delivery Schedule Lines
In the case of large-volume transactions with a high degree of repetition (repetitive manufacturing), it
is desirable to have scheduling agreement delivery schedule lines generated automatically. A
particular advantage in scheduling agreement (hereinafter called SA) processing is the automatic
generation of SA delivery schedule lines via material requirements planning (MRP).
SA delivery schedule lines can be generated automatically through MRP if certain prerequisites are
fulfilled:
• The scheduling agreement must be clearly designated as a source of supply for MRP in
the source list.
• Automatic SA delivery schedule lines must be allowed via the source list (MRP indicator
‘2’).
• The procurement indicator F (external procurement) must have been set in the MRP
data of the material master record.
• Automatic SA delivery schedule lines must be allowed in MRP. The Automatic
Schedule Lines (Scheduling Agreements) indicator determines whether or not the
system generates SA delivery schedule lines in the opening horizon only or in the
planning horizon during the planning run.
Firm Zone and Trade-off Zone
The firm zone and trade-zone define the degree to which delivery schedule lines are binding.
Scheduled delivery dates in the near future are more binding than those in the more distant future.
For an item of a scheduling agreement, a firm zone and a trade-off zone can be defined as follows:
• Firm zone (production go-ahead period)
The firm zone defines the point in time (calculated from the current date) at which the
production go-ahead period ends. The production go-ahead period begins with the
current day’s date. The schedule lines falling within this zone, or period, are fixed, and
can thus be regarded as equivalent to firm orders.
• Trade-off zone (material go-ahead period)
Scheduling Agreement Procedure Training Document 5/43
This document is for Super Users Training on 17 – 21 January, 04
6. APBM
The trade-off zone defines the point in time (calculated from the current date) at which
the material go-ahead period ends. The material go-ahead period begins with the end
of the production go-ahead period. Delivery schedule lines falling within this period can
be less binding in nature than those in the firm zone. MRP can be set up in such a way
that either only the delivery schedule lines within the firm zone or the lines within both
zones are fixed (firmed) automatically
All schedule lines with delivery dates lying beyond the firm and trade-off zones (that is, relatively far
in the future) fall within the planning zone.
Both the production and material go-ahead periods are printed in the delivery schedule for
information purposes.
The firm and trade-off zones are both calculated in calendar days. These zones are entered in the
additional data for the relevant scheduling agreement. The necessary settings for automatic fixing
(firming) of schedule lines are also made in MRP there.
Scheduling Agreements With and Without Release Documentation
Scheduling agreements can be used with or without release documentation. This is controlled in
Customizing, via an indicator, when the document type is defined for scheduling agreements.
The advantage of working with scheduling agreement release documentation is that there is always
a record of when particular delivery schedule information which can be displayed at any time, is sent
to the nominated vendor.
Without release documentation (in the standard system, document type LP)
The delivery schedule lines have official character – that is to say, they are transmitted to the vendor
as they are saved in the system. The system does not document in details releases against the
scheduling agreement that have been sent to the vendor. Therefore, in the case of the document
type without release documentation, the message control facility should be set up in such a way that
a message is immediately sent to the vendor if any changes are made to the delivery schedule
stored in the system.
With release documentation (in the standard system, document type LPA)
If scheduling agreements with release documentation is used, the delivery schedule lines are not
transmitted directly to the vendor. Initially, the lines of the delivery schedule stored in the system for
an LPA scheduling agreement are for internal information only. A message informing the vendor of
the material requirements cannot be transmitted to the vendor until an scheduling agreement
release, that is, a forecast (FRC) or Just-in-Time (JIT) delivery schedule is explicitly created.
Through this process, the way the schedule lines are represented can be changed. With the release
documentation, the scheduling agreement releases (delivery schedules) transmitted to a vendor
over a certain period at any time can be displayed. This enables to trace precisely when particular
information are specifically sent to the vendor. There are two types of scheduling agreement release
• Forecast (FRC) delivery schedules
Can be used to give the vendor a medium-term overview of material requirements.
• Just-in-Time (JIT) delivery schedules
Can be used to inform the vendor of the short-term (near future) requirements. This
type of schedule shows requirements per day or even per hour.
Scheduling agreement releases can only be generated for scheduling agreements with release
documentation. A scheduling agreement with release documentation is created if a document type
for which the release documentation indicator has been set in Customizing is used. For the
standard document type LPA, the indicator is preset.
Scheduling Agreement Procedure Training Document 6/43
This document is for Super Users Training on 17 – 21 January, 04
7. APBM
A scheduling agreement release can be created either manually or automatically on a regular basis
with the aid of a report. When using the report (online or in the background), scheduling agreement
releases can be generated either for all selected items of a scheduling agreement or only for those
items for which schedule lines have been newly created or changed. The release documentation
enables to find out when particular information are sent to the vendor.
If scheduling agreements with release documentation are used, the Just-in-Time (JIT) delivery
schedule is available in addition to the forecast (FRC) schedule as of R/3 4.0A. Forecast delivery
schedules can be used to give the vendor a medium to long-term overview of material requirements.
JIT delivery schedules can be used to inform the vendor of the short-term (near future)
requirements. This type of schedule shows requirements per day, or even per hour.
Create SA releases:
SAP Menu Logistics Material Management Purchasing Outline Agreement Scheduling
Agreement Delivery Schedule Create SA Release.
Generate SA releases in the scheduling agreement delivery schedule
Edit Generate Forecast/JIT Schedule.
Scheduling agreements with or without release documentation are created. Since the release
documentation indicator is preset in Customizing for the standard document type LPA, it is possible
to work with release documentation if this document type is used. In the case of the standard
document type LP, the release documentation indicator is not set.
Whether or not both forecast and JIT delivery schedules against a scheduling agreement with
release documentation can be generated, is determined by the JIT delivery schedule indicator in the
material master record. In order to be able to work with JIT schedules, the JIT delivery schedule
indicator must be set in the material master record (Purchasing or MRP2 View) and in the additional
data for the scheduling agreement item. No JIT delivery schedules can be created unless this
indicator has been set (which should be made before the scheduling agreement is created).
As of R/3 4.0A, there is a scheduling agreement release creation profile for scheduling agreement
with release documentation. The use of a release creation profile is optional. This profile controls
the creation periodicity of scheduling agreement releases and the aggregation of scheduled
quantities. The profile is defined in Customizing on a plant-specific basis and can be assigned in the
vendor master record or in the scheduling agreement item.
If the plant-specific data of a vendor master record already includes the release creation profile, the
latter is automatically adopted in the additional data of a scheduling agreement item with the vendor
and the relevant plant. If the vendor master record does not include the creation profile, it is optional
of entering this profile in the additional data of a scheduling agreement item manually.
With release creation profiles, it is possible to define the criteria for the scheduling agreement
releases creation (the quantities and delivery dates to be transmitted to the vendor, for instance).
The release creation profile is an instrument used to determine when releases against a scheduling
agreement are generated and sent to the vendor. It controls the creation periodicity of the
scheduling agreement releases and – starting from the current date of release creation – the way in
which quantities are aggregated. The release creation periodicity determines the time interval (for
example, daily or weekly) in which scheduling agreement releases are generated and transmitted.
Different time intervals for forecast delivery schedules and JIT schedules can be defined.
The aggregation of scheduled quantities determines the time horizons for which the schedule line
quantities of a schedule agreement item are to be consolidated to form total quantities. It is possible
to define different time horizons for forecast delivery and JIT schedules. This enables to aggregate
scheduled quantities for forecast delivery schedules to a greater extent than for JIT schedules, which
are usually transmitted to the vendor showing delivery requirements for calendar days, or hours.
Scheduling Agreement Procedure Training Document 7/43
This document is for Super Users Training on 17 – 21 January, 04
8. APBM
It is also possible to define the delimitation of the transmission horizon in the release creation profile.
This enables to transmit an aggregate forecast or preview of quantities of a material required in the
medium and long-term in a forecast delivery schedule and details of required quantities to be
delivered in the short term in a JIT delivery schedule.
Example of the exclusive use of forecast delivery schedules:
For a scheduling agreement for which delivery schedule lines covering several months have been
maintained, a release creation profile may provide for current releases to be transmitted weekly, for
example. The release quantities are to be aggregated as follows: no aggregation of the schedule
line data for the first 10 days as of the current date of release creation; daily aggregation from the
10th to the 30th day; and monthly aggregation from the 30th to the 60th day.
Example of the use of both forecast and JIT delivery schedules:
For a scheduling agreement for which delivery schedule lines covering several months have been
maintained, a release creation profile may provide for current JIT schedules to be transmitted twice
weekly, and forecast schedules to be transmitted only in the event of changes in the delivery
scheduling data that exceed predefined tolerances. The release quantities are to be aggregated as
follows: in the case of the JIT schedule, no aggregation of data for the first seven calendar days,
daily aggregation from the eighth to the 10th day. The forecast delivery schedule consolidates the
data from the seventh to the 100th day on a weekly basis.
Noted that it is recommended by SAP to define the Creation Profile field as a mandatory field for all
scheduling agreement with release documentation.
Via the creation profile, it can be specified that a tolerance check is to be carried out if scheduling
agreement releases need to be created following changes in the overall delivery schedule.
Releases for changed scheduling agreement items can be generated on the basis that predefined
tolerance limits have been exceeded. Using tolerance limits, it can be possible to specify that
scheduling agreement releases are to be generated only in the event of major changes in the overall
delivery schedule. The tolerance limits are defined in the release creation profile in Customizing
which can be defined for a maximum of three checking periods per scheduling agreement release
type (FRC and JIT).
Example:
A line of the overall scheduling agreement delivery schedule stored in the system is changed as
follows: instead of the original 100pc, 103pc are now needed on the scheduled delivery date. This
represents a change of 3% in the quantity. Since the upper tolerance limit for JIT delivery schedule
(5%) has thus been exceeded, an new JIT schedule is generated.
Instead of the original 105 pc, only 104 pc are now needed. This change is within the set tolerance
– the lower tolerance limit for forecast delivery schedule is 5% - so that no new scheduling
agreement release is generated automatically.
The status of the scheduling agreement releases can be determined from the screen for scheduling
agreement delivery schedule maintenance. The traffic light colors are to be interpreted as follows:
• Yellow
When the maintenance screen for a scheduling agreement delivery schedule is first
invoked, the traffic light always initially shows yellow. This is because no scheduling
agreement release that could be transmitted to the vendor yet exists. As soon as a
release in the form of a forecast or JIT delivery is generated, then the traffic light
changes to green. If or when the current release is sent to the vendor, the traffic light
changes back to yellow.
• Green
Scheduling Agreement Procedure Training Document 8/43
This document is for Super Users Training on 17 – 21 January, 04
9. APBM
The green light signifies that a current release exists, but it has not yet been transmitted
to the vendor. This release can be sent.
• Red
If changes are made to the schedule within the horizon for forecast or JIT delivery
schedules before the last scheduling agreement release has been transmitted to the
vendor, the traffic light changes to red. The red light signifies that the already existing
release data differs from the current scheduling data. A scheduling agreement release
exists, but its data does not match up with that of the current overall delivery schedule in
the system. As soon as a new release is generated, the traffic light changes back to
green.
Noted that if only the scheduling agreement release type Forecast (FRC) delivery
schedule is used in scheduling agreement processing, the traffic lights relate
exclusively to FRC schedules. If both scheduling agreement release types FRC and JIT
delivery schedules are used, the traffic lights relate exclusively to the status of the JIT
schedules.
Scheduling Agreement Procedure Training Document 9/43
This document is for Super Users Training on 17 – 21 January, 04
10. APBM
Business Process Procedure
1. Creation of Scheduling Agreement with Release Documentation
1.1. Access transaction by
Via Menu Logistics Materials Management Purchasing Outline
Agreement Scheduling Agreement Create Vendor Known
Via Transaction Code ME31L
Key T-Code: ME31L
Fig-01
Scheduling Agreement Procedure Training Document 10/43
This document is for Super Users Training on 17 – 21 January, 04
11. APBM
1.2. On “Create Scheduling Agreement : Initial Screen” screen, fill in the data as below:
Fig-02
Field Name Description R/O/C/D User Action and Values
Vendor Alphanumeric key uniquely R Enter the vendor number
identifying a vendor
Agreement type Indicator allowing R Enter “LPA”
differentiation between
various kinds of outline
purchase agreement in the
SAP system
Agreement date Date the agreement was R Enter the agreement date
created
Agreement Number of the outline O Enter the agreement number
agreement
Purch. Denotes the purchasing O Enter the purchasing organization
organization organization
Purchasing group Key for a buyer or a group O Enter the purchasing group
of buyers, who is/are
responsible for curtain
purchase activities
Item category Key defining how the O Enter the item category
procurement of a material
or service item is
controlled
Acct assignment Specifies whether O Enter the account assignment
cat. (Account accounting for an item is to category
assignment be effected via an auxiliary
Scheduling Agreement Procedure Training Document 11/43
This document is for Super Users Training on 17 – 21 January, 04
12. APBM
Field Name Description R/O/C/D User Action and Values
category) account
Plant Specifies the key for a R Enter the plant number
production facility of
branch office within the
company
Storage Location Number of the storage O Enter the storage location number
location at which the
material is stored
Material group Key that you use to group O Enter the material group
together several materials
or services with the same
attributes, and to assign
them to a particular
material group
Req. tracking Number that facilitates the O Enter the requirement tracking
number monitoring of the number
procurement of required
materials or services
Vendor sub- Subdivision of a vendor’s O Enter the vendor sub-range
range overall product range
according to various
criteria
Determines whether the O Select the indicator
purchasing document is to
be acknowledged by the
vendor
Press “ENTER” or click on
icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 12/43
This document is for Super Users Training on 17 – 21 January, 04
13. APBM
1.3. On “Create Scheduling Agreement : Header Data” screen, fill in the data as below:
Fig-03
Field Name Description R/O/C/D User Action and Values
Validity start Date as of which services R Enter the validity start date
can be performed or
materials deliver
Validity end Date up to which services R Enter the validity end date
can be performed or
materials delivered
Incoterms (part1) Commonly-used trading O Enter the Incoterms
terms that comply with the
standards established by
the International Chamber
of Commerce (ICC)
Incoterms (part2) Additional Information for O Enter the information
the primary Incoterms
Quotation date Date on which the vendor O Enter the quotation date
submitted the quotation
Quotation Number of vendor’s O Enter the quotation number
quotation
Click on icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 13/43
This document is for Super Users Training on 17 – 21 January, 04
14. APBM
1.4. On “Create Scheduling Agreement : Item Overview” screen, fill in the data as below:
Fig-04
Field Name Description R/O/C/D User Action and Values
Material Uniquely identifies a R Enter the material number
material
Short text Short description of the O Enter the short text
material
Targ. qty. (Target Total quantity, agreed with R Enter the target quantity
quantity) the vendor, that can be
released or scheduled
against the relevant
agreement
OUn (Order Unit) Specifies the unit of R Enter the order unit
measure in which the
material is ordered
Net price Net price per price unit R Enter the net price
Per (Price Unit) Specifies how many units R Enter the price unit
of the purchase order price
unit the price is valid for
OPUn (Order Indicates the unit of R Enter the order price unit
price unit) measurement to which the
purchase order price
relates
Matl group Key that you use to group R Enter the material group
(Material group) together several materials
or services with the same
attributes, and to assign
Scheduling Agreement Procedure Training Document 14/43
This document is for Super Users Training on 17 – 21 January, 04
15. APBM
Field Name Description R/O/C/D User Action and Values
them to a particular
material group
Item Item starting from which R Enter the item number
the document is to be
displayed
Select the item, then click on
icon to maintain additional
information
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 15/43
This document is for Super Users Training on 17 – 21 January, 04
16. APBM
1.5. On “Create Scheduling Agreement : Item XXXXX” screen, fill in the data as below:
Fig-05
Field Name Description R/O/C/D User Action and Values
InfoUpdate Determines whether the O Enter the update info record
purchasing info record for indicator
this vendor and material is
to refer to this PO item,
and the item is to be valid
for the entire purchasing
organization or just for the
plant
Order acknowledgement O Select the indicator
requirement indicator
Underdel. tol. Percentage (based on the O Enter the percentage
(Underdelivery order quantity) up to which
tolerance limit) an underdelivery of this
item will be accepted
Overdeliv. tol. Percentage (based on the O Enter the percentage
(Overdelivery order quantity) up to which
tolerance limit) an overdelivery of this item
will be accepted
Tax code A tax category which must O Enter the tax code
be taken into consideration
when making a tax return
to the tax authorities
Shipping instr. Specifies the packaging O Enter the shipping instructions
(Shipping and shipping instructions
instructions) issued to the vendor
Click on icon
Scheduling Agreement Procedure Training Document 16/43
This document is for Super Users Training on 17 – 21 January, 04
17. APBM
Legend: R = Required, O = Optional, C = Conditional, D = Display
1.6. On “Create Scheduling Agreement : Item XXXXX Additional Data” screen, fill in the data
as below:
Fig-06
Field Name Description R/O/C/D User Action and Values
Creation profile Release Creation Profile R Enter the creation profile
After making necessary entries in
respective fields, click on icon to
return to the Item Overview screen
of the Scheduling Agreement. And
click on icon to post the
Scheduling Agreement
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 17/43
This document is for Super Users Training on 17 – 21 January, 04
18. APBM
Fig-07
Scheduling Agreement Procedure Training Document 18/43
This document is for Super Users Training on 17 – 21 January, 04
19. APBM
2. Assignment of Scheduling Agreement Release Creation Profile to the
Material Master Record
2.1. Access transaction by
Via Menu Logistics Materials Management Material Master Material
Change Immediately
Via Transaction Code MM02
Key T-Code: MM 02
Fig-08
Scheduling Agreement Procedure Training Document 19/43
This document is for Super Users Training on 17 – 21 January, 04
20. APBM
2.2. On “Change Material (Initial Screen)” screen, fill in the data as below:
Fig-09
Field Name Description R/O/C/D User Action and Values
Material Alphanumeric key uniquely R Select the material number to
identifying the material which the Quota Arrangement
Usage Key is to be assigned
Change number Number used to uniquely O Enter the change number if you
identify a change master make a change with reference to a
record change number, or create a object
with a change number
Click on icon
or press “ENTER”. Then the pop
up screen appears as shown.
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 20/43
This document is for Super Users Training on 17 – 21 January, 04
21. APBM
2.3. On the pop screen, maintain information as specified in the table below:
Fig-10
Field Name Description R/O/C/D User Action and Values
Select the appropriate logical
screen and click on icon. Then
the pop up screen appears as
shown.
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 21/43
This document is for Super Users Training on 17 – 21 January, 04
22. APBM
2.4. On the pop screen, fill in the data as below:
Fig-11
Field Name Description R/O/C/D User Action and Values
Plant Key uniquely identifying a R Select the plant number
plant
Click on icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 22/43
This document is for Super Users Training on 17 – 21 January, 04
23. APBM
2.5. On “Change Material XXXXXXXXXXXX (TH –Spare Parts1)” screen, fill in the data as
below:
Fig-12
Field Name Description R/O/C/D User Action and Values
JIT sched. Determines whether it is R Enter the JIT delivery schedules
indicator possible to generate JIT indicator
delivery schedules in
addition to forecast
schedules for a material
specified in a purchase
scheduling agreement
Click on icon to update of the
material master record
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 23/43
This document is for Super Users Training on 17 – 21 January, 04
24. APBM
Fig-13
Scheduling Agreement Procedure Training Document 24/43
This document is for Super Users Training on 17 – 21 January, 04
25. APBM
3. Creation of source list record for this Scheduling Agreement subject to
MRP run
3.1. Access transaction by
Via Menu Logistics Materials Management Purchasing Master Data
Source List Maintain
Via Transaction Code ME01
Key T-Code: ME01
Fig-14
Scheduling Agreement Procedure Training Document 25/43
This document is for Super Users Training on 17 – 21 January, 04
26. APBM
3.2. On “Maintain Source List: Initial Screen” screen, fill in the data as below:
Fig-15
Field Name Description R/O/C/D User Action and Values
Material Alphanumeric key uniquely R Enter the material number
identifying the material
Plant Specifies the key for a R Enter the plant number
production facility or
branch office within the
company
Press “ENTER”
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 26/43
This document is for Super Users Training on 17 – 21 January, 04
27. APBM
3.3 On “Maintain Source List: Overview Screen” screen, maintain information as specified in
the table below:
Fig-16
Fig-17
Scheduling Agreement Procedure Training Document 27/43
This document is for Super Users Training on 17 – 21 January, 04
28. APBM
Field Name Description R/O/C/D User Action and Values
Make the appropriate selections
and/or entries in the relevant fields.
Then click on icon to validate
the correctness of the entered
values before posting the source
list record.
In case, the testing run returns with
the result that all source list
records is OK, then the posting will
be made.
Click on icon to post the
source list record.
Legend: R = Required, O = Optional, C = Conditional, D = Display
Fig-18
Scheduling Agreement Procedure Training Document 28/43
This document is for Super Users Training on 17 – 21 January, 04
29. APBM
4. Generation of SA Delivery Schedule Line Item from MRP
4.1. Access transaction by
Via Menu Logistics Materials Management Material Requirement Planning
(MRP) MRP Planning Single-Item, Single-Level
Via Transaction Code MD03
Key T-Code: MD03
Fig-19
Scheduling Agreement Procedure Training Document 29/43
This document is for Super Users Training on 17 – 21 January, 04
30. APBM
4.2. On “Single-Item, Single-Level” screen, fill in the data as below:
Fig-20
Field Name Description R/O/C/D User Action and Values
Material Alphanumeric key uniquely R Enter the material number
identifying the material
MRP area Number of the MRP area R Enter the MRP area number
for which material
requirements planning
should be carried out
separately
Plant Key uniquely identifying a R Enter the plant number
plant
Indicator controls that the R Select the indicator
MRP result is displayed for
information purposes
before saving
Press “ENTER” twice so as to
trigger the running of MRP for the
selected material item
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 30/43
This document is for Super Users Training on 17 – 21 January, 04
31. APBM
4.3. On “Planning Result: Individual Lines” screen, maintain information as specified in the
table below:
Fig-21
Field Name Description R/O/C/D User Action and Values
After making a necessary
validation of procurement proposal
after MRP run, click on icon to
save the result of MRP run
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 31/43
This document is for Super Users Training on 17 – 21 January, 04
32. APBM
Fig-22
Scheduling Agreement Procedure Training Document 32/43
This document is for Super Users Training on 17 – 21 January, 04
33. APBM
5. Creation of Scheduling Agreement Release for SA Delivery Schedule Line
Item
5.1. Access transaction by
Via Menu Logistics Materials Management Purchasing Outline
Agreement Scheduling Agreement Create SA Release
Via Transaction Code ME84
Key T-Code: ME84
Fig-23
Scheduling Agreement Procedure Training Document 33/43
This document is for Super Users Training on 17 – 21 January, 04
34. APBM
5.2. On “Create Releases” screen, fill in the data as below:
Fig-24
Field Name Description R/O/C/D User Action and Values
Specifies the type of R Select the indicator
scheduling agreement
release to be created
Plant Specifies the key for a R Enter the plant number
production facility or
branch office within the
company
Planning area Number of the MRP area R Enter the MRP area number
for which material
requirements planning
should be carried out
separately
Materials planner Specifies the number of O Enter the materials planner
the MRP controller or number
group of MRP controllers
responsible for material
planning for the material
Material Alphanumeric key uniquely R Enter the material number
identifying the material
Vendor Alphanumeric key uniquely O Enter the vendor number
identifying a vendor
Scheduling Alphanumeric key uniquely O Enter the scheduling agreement
agreement identifying purchasing number
document
Indicates that the release R Make sure that the indicator will be
creation process will be ‘deactivated’
Scheduling Agreement Procedure Training Document 34/43
This document is for Super Users Training on 17 – 21 January, 04
35. APBM
Field Name Description R/O/C/D User Action and Values
carried out as a test run
Click on icon to generate both
JIT and FRC Delivery Schedule
Line Items
Legend: R = Required, O = Optional, C = Conditional, D = Display
5.3. On “Create Releases” screen, maintain information as specified in the table below:
Fig-25
Field Name Description R/O/C/D
User Action and Values
Go to transaction ME38 view the
status of the Scheduling
Agreement
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 35/43
This document is for Super Users Training on 17 – 21 January, 04
36. APBM
5.4. On “Maintain Sch. Agmt. Schedule : Initial Screen” screen, maintain information as
specified in the table below:
Fig-26
Field Name Description R/O/C/D User Action and Values
Press “ENTER” or click on
icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 36/43
This document is for Super Users Training on 17 – 21 January, 04
37. APBM
5.5. On “Maintain Sch. Agmt. Schedule : Item Overview” screen, maintain information as
specified in the table below:
Fig-27
Field Name Description R/O/C/D User Action and Values
Select the SA line item, then click
on icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 37/43
This document is for Super Users Training on 17 – 21 January, 04
38. APBM
5.6. On “Overview: Release Against Sched. Agreement XXXXXXXXXX, Material XXX” screen,
maintain information as specified in the table below:
Fig-28
Field Name Description R/O/C/D User Action and Values
Select either ‘JIT’ Release
Document or ‘FRC’ Release
Document and then click on
icon or
icon
accordingly
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 38/43
This document is for Super Users Training on 17 – 21 January, 04
39. APBM
5.7. On “Overview: JIT schd.” screen, maintain information as specified in the table below:
Fig-29
Field Name Description R/O/C/D User Action and Values
Select ‘Release Number’ (Release
Number > 0), then click on
icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 39/43
This document is for Super Users Training on 17 – 21 January, 04
40. APBM
5.8. On “FRC sched. 1: Output” screen, click on icon to save this Scheduling Agreement:
Fig-30
Scheduling Agreement Procedure Training Document 40/43
This document is for Super Users Training on 17 – 21 January, 04
41. APBM
5.9. To print SA Delivery Schedules, enter Transaction ME9E:
Key T-Code: ME9E
Fig-31
Scheduling Agreement Procedure Training Document 41/43
This document is for Super Users Training on 17 – 21 January, 04
42. APBM
5.10. On “Message Output” screen, fill in the data as below:
Fig-32
Field Name Description R/O/C/D User Action and Values
Document Alphanumeric key uniquely R Enter the document number
number identifying purchasing
document
Vendor Alphanumeric key uniquely R Enter the vendor number
identifying a vendor
Purchasing Denotes the purchasing R Enter the purchasing organization
organization organization
Purchasing group Key for a buyer or a group O Enter the purchasing group
of buyers, who is/are
responsible for certain
purchasing activities
Document type Identifier allowing O Enter the document type
differentiation between the
various kinds of
purchasing document in
the SAP system
Document date Date on which the O Enter the document date
purchasing document was
created
The indicator that system R Select the indicator
selects only messages for
scheduling agreement
releases
Click on icon
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 42/43
This document is for Super Users Training on 17 – 21 January, 04
43. APBM
5.11. On “Message Output” screen, maintain information as specified in the table below:
Fig-33
Field Name Description R/O/C/D User Action and Values
Select proper Message Type
(either JIT or FRC) and then click
on icon and then
click on icon to
print out
Legend: R = Required, O = Optional, C = Conditional, D = Display
Scheduling Agreement Procedure Training Document 43/43
This document is for Super Users Training on 17 – 21 January, 04