TBMM13-Purchaising Process Scheduling Agreement
To Be Process
Purchasing Process Scheduling agreement
V2-TBMM13 - Purchasing Process - Scheduling AgreementV4
Table of content
21.1Document updates and validations
22Scope
22.1Process scope description
22.2Application architecture (global)
32.3Cross references
33Process
43.1Core model - process flow and description
63.2Revision level or customer material number change
management
83.3Country or customer specific - process flow and
description
83.3.1Country specific process Flow
84Business Rules
84.1Core model Business rules
94.2Country or customer specific Business Rules
95Key elements of system implementation
95.1Core model Key elements of system implementation
95.1.1Pre-requisites
105.1.2Steps of the process
125.1.3Revision level or Customer material number change
management
145.1.4Scheduling agreements content
235.1.5Scheduling agreement scheduling lines
255.1.6Scheduling agreements - Data sent to FLEXNET
285.2Country or customer specific Key elements of system
implementation
285.2.1Country specific Elements for system implementation
285.3Summary
286Organizational roles and impacts
297Application specific development requirements
298Key volume & performance indicators
299Added value for the Business and economical
considerations
Document updates and validations
The table below lists all modifications and updates done on the
considered document. Fill in Date, Author and a summary of the
documents update content, reason and/or objectives.
Updates
Date
Version
Author
Comment
09/05/02
V0
C. Hemery
Document creation
28/06/02
V0
J.A. Sanz
Document reading
23/09/02
V1
C. Hemery
Document adjustment
22/10/02
V1
C. Hemery
Document completion : raw glass management in Spain and Revision
level management
25/10/02
V2
C. Hemery
Document adjustment
25/03/03
V3
C. Hemery
Document update : document types and Creation profiles
12/04/03
V3
G. Lepp
Document update : Add the 00D0 creation profile
25/09/03
V4
D. Francois
Document update
29/12/04
V4
D. Francois
Document update
The table below lists all the successful validations done on the
document ; if the document was asked for validation but not
validated then there is no entry in this table (status by default
is OK).
Validations
Date
Version
Validation Resp.
Comment
1 Scope
1.1 Process scope description
This document describes the use of scheduling agreements and
purchasing delivery schedules by Sekurit.
It deals with all types of purchases performed through
scheduling agreements, i.e. :
logistic materials : glass products
strategic products that are included in BOMs
Recurrent purchases of products of the general warehouse
The sites concerned are all types of plants : glass plants,
extrusion / encapsulation plants and service centers.
Out of scope :
Other purchasing document types : purchase requisitions,
purchase order, contracts and request for quotations,
particularities in Scheduling Agreements for purchasing
processes (such as sub-contracting, consignment ) are tackled in
the purchasing process documents (TBMM15 - Purchasing Process
SubContracting, TBMM17 - Purchasing Process Intercompany, TBMM18 -
Purchasing Process Intracompany, TBMM20 - Purchasing Process
Consignment).
Transition period :
( Within Sekurit Avenir V1, stock movements for raw glass and
PVB / Functional interlayers are directly treated in SAP.
( Within Sekurit Avenir V2, stock movements for raw glass and
PVB / Functional interlayers are treated in FLEXNET and interfaced
with SAP.
So, during the transition period, we should be able to send
Scheduling Agreement for Raw glass / PVB, Functional interlayers /
glass products to FLEXNET systems, and Scheduling agreements for
glass products only to DCS.
1.2 Application architecture (global)
If relevant for Logistics (tradable semi-finished and finished
products), raw glass or PVB / Functional interlayers that are
managed in FLEXNET, the Scheduling Agreement is sent to FLEXNET via
a ZBLAORD_RCV idoc type. It contains data of the scheduling
agreement, but data of the delivery schedule are not sent to
FLEXNET.
For other material types which are only managed in SAP, nothing
is sent to FLEXNET.
1.3 Cross references
V2-TBMM08Supply - Manage deliveries requests
TBPP13Supply / Delivery requests
TBMM09Purchasing process per material type
TBMM14Purchase process Purchase orders
TBMM15Purchase process Sub-contracting
TBMM16Purchase process Third Party
V2-TBMM17Purchase process Inter-company
V2-TBMM18Purchase process Intra-company
V2-TBMM20Purchase process Consignments
TBMM22Document Outputs
TBMM23Document Forms
TBMM25General Warehouse Entries
TBIN02Process Receiving
2 Process
2.1 Core model - process flow and description
The process objective is :
manage a purchasing document to send our requirements to the
vendor.
We should distinguish two process flows :
( Purchased product not relevant for MRP calculations
Not relevant.
Products not relevant for MRP calculations are procured with
contracts / purchase orders.
( Purchased product relevant for MRP calculations
Perimeter : procured products relevant for MRP calculations are
:
products included into the BOM (Bill Of Material)
COMPONENTS
COMMON
BENDING / TEMPERING
Raw Glass
Connector
Semi-finished products (HLB1)
EXTRUSION / ENCAPSULATION
Finished products (FER1)
Naked glass
Enamel
Polymer
Silver paste
SERVICE CENTERS
Primer
Mirror pads (Raindetectors)
BENDING / LAMINATING
Pastic Profiles
PVB
Rubber parts (Rubber inserts & Rubber profiles)
Functional interlayers
Other pastic parts (Plastic inserts)
Components for PVB/Functional interlayers preparation : Heating
network
Metallic parts
Components for PVB/Functional interlayers preparation :
Conducting line
Modules pre-assembly
Components for PVB/Functional interlayers preparation :
Connectors
Connectors
Raw glass is procured from Saint-Gobain Glass.
Tradable semi-finished and finished products are either procured
from external vendor or procured from group vendors, in
inter-company or intra-company flows.
The other components are procured from external vendors.
other components managed in stock but not part of the BOM, for
example : Thinner, Lubricant and Silica, Acetylene, Plastic
separators, polystyrene protections, metallic pieces for ribbon and
ribbon, Cutting, drilling and soldering tools,
Scheduling agreements can also be created for other materials
(from the general warehouse), that are regularly purchased.
Pre-requisites to this flow are presented below but also
detailed in part 5.1.1 Pre-requisites (Master data).
SAP
Scheduling
agreement
Requirement
planning
Scheduling
agreement -
Schedule
lines
Other strategic materials, included in
BOMs
Other products, not included into
BOMs
, managed in stock
Buyer
For a regular purchasing flow, it is interesting to maintain a
purchasing scheduling agreement : among other purchasing processes,
it enables MRP calculations to update automatically schedule lines
when required. Then, the purchaser can control the MRP result but
he is not compelled to transform each time a purchase requisition
into a purchase order.
Step 1 : Scheduling agreement creation
MRP calculations update schedule lines when required only once
the scheduling agreement has been created : it is a pre-requisite
to the purchasing process. There can be several items in a
scheduling agreement : as long as the products are purchased to the
same vendor and delivered to the same site, they can be set into
the same scheduling agreement.
However, when there is a very long list of materials for the
same vendor /and purchasing group, the best way is to divide it in
several scheduling agreements (according to an easy criteria) :
example for raw glass : for most plants, there is one scheduling
agreement per color of the glass. Otherwise, the document is very
difficult to handle.
It is also necessary to update the source-list with the
scheduling agreement number and item : Cf. TBMM04 - Purchasing
Master Data.
V1 document type
LP Scheduling agreement. Used for purchases for inter-company
flows with receiving plant within Sekurit Avenir 1 solution.
Several document types are used within Sekurit Avenir solution
:
LPA Scheduling Agreement (most frequent type).
Used for purchases from external vendor (including
sub-contracting, consignment) and for inter-company flows with
receiving plant within Sekurit Avenir 2 solution.
Also used in V2, but only for glass products :
ZLP Scheduling Agreement. Used for purchases from inter-company
vendors applying a Push mode, i.e. the vendor sends goods without a
customer demand. Only applied between SGSE and Devisa.
LUTransport transfer Scheduling agreement. Used when
transferring stocks between plants belonging to the same company
intra-company flows, in a Pull mode.
ZLU Transport transfer Scheduling Agreement. Used when
transferring stocks between plants belonging to the same company
intra-company flows, in a Push mode.
Scheduling agreement should be created for one year (not
compulsorily a civil year) : scheduling agreements used for more
than one year should be replaced by another scheduling
agreement.
It is difficult to handle a scheduling agreement for more than
one year, since the goods receipts and invoices are then difficult
to analyse.
Outputs :
( Printout : Once created, the scheduling agreement can be
printed and sent to the vendor.
( Idoc creation to be sent to FLEXNET :
an idoc is sent to the receiving FLEXNET system, to be used as a
reference for goods receipts
in a Push mode (ZLP and ZLU document types glass products only),
an Idoc is sent to the shipping Flexnet system, to be used as
reference for the shipping.
Responsible : Master data manager or forecast demander
(purchaser).
Step 2 : Material Requirement Planning
MRP calculations : the job is planned to run every week runs
everyday. It compares the needs, the stocks and the forecasted
resources (outstanding purchases or planned orders) to the
requirements, to trigger if necessary a planned order or a
purchase.
( To determine whether the product is produced and / or
purchased, master data are used (material, source-list, quota
arrangement).
( To determine if a scheduling agreement is used, master data
are used (source-list).
( If there is a need for the material, on a plant and at a date
consistent with the scheduling agreement indicated in the
source-list, the MRP runs creates schedule lines (in the scheduling
agreement) to fullfil this need.
Responsible : automatic for MRP calculations.
Step 3 : Scheduling Agreement schedules lines (Delivery
schedules) management
From the MRP analysis, schedule lines can be checked. They can
also be checked / changed directly from the purchasing
document.
For a schedule line, a creation indicator is determined, to
differentiate what was created by MRP and what was created
manually.
Outputs :
( Printout : once updated and if wanted by the purchasing
department, the delivery schedule can be printed and sent to the
vendor.
( No idoc is triggered because delivery schedules are never sent
to FLEXNET.
Responsible : forecast demander (purchaser).
Remark : reminders on schedule lines can be launched and
printed.
Step 4 : Scheduling Agreement modification
Several types of modification are possible in a Scheduling
Agreement :
Item creation : the new item is to be taken into account
Item modification, to change one or several data, including flag
the Delivery complete indicator once the ordered quantity has been
received
Item blocking : it enables to block an item for supply and
receipt
Item deleting
Outputs : in all these cases,
( a modification printout is printed to be sent to the
vendor,
See to be on printing of purchasing documents ACO MM TBP 40 for
more details. indicating only the changed data in the purchasing
document
( and for products managed in FLEXNET, an idoc is sent to
FLEXNET to update the purchasing document. But purchasing prices
are not visible in FLEXNET.
Remark : the person responsible for planning and communication
with the vendor (who manages the scheduling agreement) is also
responsible of claims management.
2.2 Revision level or customer material number change
management
Perimeter :
Our OEM customers manage, for glass products purchased to
Sekurit, their reference (Customer material number) and a revision
level. When a modification is performed on the product, either the
Revision Level (RL) or the customer material number is changed.
Products concerned are finished products and thus, tradable
semi-finished products on the supply chain.
This process describes the procedure applied when this
modification occurs.
When the customer changes its material reference or its revision
level, the rule is to change the SAP product code for all products
physically changed by the customer modification.
For instance, in a logistic flow
SAP
Scheduling
agreement
Requirement
planning
Flexnet
Buyer
Idoc
type ZBLAORD_RCV
for the Scheduling
agreement
Scheduling
agreement
-
Schedule
lines
Glass products
Strategic products : raw glass and PVB
Receiving plant
SAP
Scheduling
agreement
Requirement
planning
Requirement
planning
Flexnet
Buyer
Idoc
type ZBLAORD_RCV
for the Scheduling
agreement
Scheduling
agreement
-
Schedule
lines
Glass products
Strategic products : raw glass and PVB
Receiving plant
If a modification is asked on encapsulation part, the flow
becomes
Glass
plant
Extrusion /
Encapsulation
plant
Service centre
Customer
Production
Product A
Product A +
Encapsulation
Product B
Product B +
Value addition
Product C
A
C
B
( If no agreement is concluded with the customer, it means that
if the customer changes its code, Sekurit has to stop to deliver
the old material code and immediately begins to deliver the new
one. This will influence the Sekurit production Strategy to make as
few stock as possible.
In this case, low stock will cost less to Sekurit but will be
difficult to implement as the new products must be produced
immediately.
( If an agreement is concluded with the customer to allow
Sekurit to clear out the old reference stock before delivering the
new reference, Sekurit can still deliver the old reference while
the customer sends its requirements on the new reference.
In any case, all Sekurit plant (planners) participating to the
concerned product supply chain should be informed of the
modification.
For all plants concerned by the product modification, the
previously described pre-requisites of the process should be
reviewed. If there is no agreement with the customer, it should be
reviewed immediately. If an agreement is concluded, it should be
reviewed once the old reference stocks have been cleared out.
In the previous example, it concerns two products :
the tradable semi-finished product B becomes D
the finished product C becomes E.
If the flow between the two plants is an inter-company flows
:
Old product
New product
Material
While customer requirements are integrated on the old product,
the old product master is declared with Discontin. Part to transfer
production requirements onto the new product
Once the stocks have been cleared out, marked for deletion on
the shipping and receiving plants,
If stocks have not been cleared out, it is not marked for
deletion
Created in copy of the old product, on the shipping and
receiving plants.
Vendor
No modification required
Info-record
It should be marked for deletion
Created for the new product, with the correct cession price, on
the receiving plant.
Source-list
The items of the source-lists should be deleted.
The source-list for the new product, on the receiving plant, is
created.
Quota-arrangement
The items of the quota-arrangement should be deleted.
The quota-arrangement for the new product, on the receiving
plant, is created.
Scheduling agreement
The item of the scheduling agreement is blocked, to stop its use
in planning and send an idoc to block the item in FLEXNET.
A new item is created, either in the same scheduling agreement,
or in another scheduling agreement.
If the flow between the two plants is an intra-company flows
:
Old product
New product
Material
While customer requirements are declared on the old product, the
old product master is declared with Discontin. Part to transfer
production requirements onto the new product
Once the stocks have been cleared out, marked for deletion on
the shipping and receiving plants,
If stocks have not been cleared out, it is not marked for
deletion
Created in copy of the old product, on the shipping and
receiving plants.
Source-list
The items of the source-lists should be deleted.
The source-list for the new product, on the receiving plant, is
created.
Quota-arrangement
The items of the quota-arrangement should be deleted.
The quota-arrangement for the new product, on the receiving
plant, is created.
Scheduling agreement
The item of the scheduling agreement is blocked, to stop its use
in planning and send an idoc to block the item in FLEXNET.
A new item is created, either in the same scheduling agreement,
or in another scheduling agreement.
2.3 Country or customer specific - process flow and
description
2.3.1 Country specific process Flow
3 Business Rules
3.1 Core model Business rules
( Modifications in Scheduling Agreements
There are several types of modifications in Scheduling
agreements :
If an error was made when creating or if the agreement with the
vendor is modified (for example quantity), it is possible to change
data in a scheduling agreement.
It is also possible to add one or several items if the vendor is
supplying other products.
If a scheduling agreement was already used to receive goods and
perform invoice verification, but the purchaser decides not to
purchase products to this vendor anymore, it is possible to block
one or several scheduling agreement items.
If an error was made when creating and an item cannot be used
(for example wrong product code), it is possible to delete a
scheduling agreement item.
( Communication language
Whichever is the communication language with the vendor,
purchasing documents are printed in the language of the purchasing
company.
3.2 Country or customer specific Business Rules
( Germany
Use of the Acknowledgment number of the purchasing document to
store the vendor acknowledgment number, per item in the system.
( Spain, for products except Raw glass.
To use Executive Receipt Settlement which is authorized in Spain
for national vendors, if declared in vendor master data, it is set
in the purchasing document. Then, when declaring the goods receipt,
the vendor delivery note is required and the anticipated invoice
can be created in the system. A form is printed out to be sent to
the vendor.
For instance, automatic invoicing will be used for glass
products purchases between Cristaleria / Devisa, and between Devisa
/ Cristaleria.
Cf. TBMM35 - Executive Receipt Settlements
4 Key elements of system implementation
4.1 Core model Key elements of system implementation
4.1.1 Pre-requisites
Two kind of pre-requisites are tackled : master data and
customizing.
4.1.1.1 Master data
Here is a list of the necessary data to create a purchasing
Scheduling Agreement. The detail of each data can be found in the
linked To Be Process.
Please refer to pre-requisite scheme in part 3.1.
Concerning purchase processes specificities, such as
sub-contracting and consignment, they are also detailed in the
linked To Be Process.
( Material
The material purchasing data should at least be declared in the
receiving plant. These data are, for instance : the purchasing
group, the order unit, the purchasing value key (which determines
the reminder days and tolerance limits).
Cf. TBMM02 - Material Master
( Vendor
The purchasing vendor master data should be declared on the
purchasing organization. These data are, for instance : the order
currency, terms of payment.
Reminder : there is one purchasing organization per country.
Cf. TBMM03 - Vendor Master Data
( Purchasing info-record
The purchase info-record should be declared, for the product and
the vendor, on the purchasing organization or on the purchasing
plant. It contains, for instance, the agreed price per unit with
the vendor.
Cf. TBMM04 - Purchasing Master Data
( Source-list
The source-list is only created once the scheduling agreement
has been created, because to ensure the MRP runs correctly, it has
to contain the scheduling agreement number, the item number and the
indication that delivery schedule lines should be created on the
base of this document (2 in the column MRP).
Cf. TBMM04 - Purchasing Master Data
( Quota-arrangement
The quota arrangement is not a pre-requisite to the scheduling
agreement, but to MRP.
Cf. TBMM04 - Purchasing Master Data
4.1.1.2 Customizing
For LPA document type only, Creation profiles are used. The
Creation profile can control :
the creation periodicity of the releases (scheduling agreement,
delivery schedules), i.e. the period in which releases against a
scheduling agreement are created and transmitted to the vendor,
and
the way in which the quantities transmitted to the vendor are
aggregated (starting from the current creation date of the
release).
In SGS case, only aggregation functionality is used.
Creation profiles are created per plant. So, a data collection
is required per plant, to list all possiblities, depending on the
product family or the vendors.
Codification rule : XXYZ
WhereXX number of requirement days aggregated per days
Y number of requirement days aggregated per weeks
Znumber of requirement days aggregated per months.
4.1.2 Steps of the process
Perimeter : procured products relevant for MRP calculations are
:
products included into the BOM. Product types are :
FER1 for tradable semi-finished products and finished
products,
ZHLB for non glass semi-finished products (such as
Prlaminat),
STRA for strategic parts.
other components managed in stock but not part of the BOM.
Product types are :
STRA for strategic parts,
HIBE for consumable parts,
ERSA for spare parts,
VERP for packaging.
Please refer to process flow scheme in part 3.1.
Step 1 : Scheduling agreement creation
MRP calculations update schedule lines when required only once
the scheduling agreement has been created : it is a pre-requisite
to the purchasing process. There can be several items in a
scheduling agreement : as long as the products are purchased to the
same vendor and delivered to the same site, they can be set into
the same scheduling agreement.
However, when there is a very long list of materials for the
same vendor /and purchasing group, the best way is to divide it in
several scheduling agreements (according to an easy criteria) :
example for raw glass : for most plants, there is one scheduling
agreement per color of the glass. Otherwise, the document is very
difficult to handle.
It is also necessary to update the source-list with the
scheduling agreement number and item : Cf. TBMM04 - Purchasing
Master Data.
V1 scheduling agreement
LP Scheduling agreement. Used for purchases for inter-company
flows with receiving plant within Sekurit Avenir 1 solution. It is
created using ME31L transaction.
Several document types are used within Sekurit Avenir solution
:
LPA Scheduling Agreement (most used document type). Used for
purchases from external vendor (including sub-contracting,
consignment) or inter-company flows with receiving plant within
Sekurit Avenir 2 solution.
It is created using ME31L transaction.
Also used in V2, but only for glass products :
ZLP Scheduling Agreement. Used for purchases from inter-company
vendors applying a Push mode, i.e. the vendor sends goods without a
customer demand. Only applied between SGSE and Devisa. It is
created using ME31L transaction.
LUTransport Scheduling agreement. Used when transferring stocks
between plants belonging to the same company intra-company flows,
in a Pull mode. It is created using ME37 transaction.
ZLU Transport Scheduling Agreement. Used when transferring
stocks between plants belonging to the same company intra-company
flows, in a Push mode. It is created using ME37 transaction.
For LPA, LP and LU document types, the same number range is used
: 5500000000 to 5599999999.
For ZLP and ZLU document types, the number range is : 5700000000
to 5799999999.
Document numbers are assigned by the system.
Scheduling agreement should be created for one year (not
compulsorily a civil year) : scheduling agreements used for more
than one year should be replaced by another scheduling agreement
(otherwise, they become very difficult to handle).
Outputs :
( Printout : Once created, the scheduling agreement can be
printed and sent to the vendor. Printing orders (message type ZNEU)
are defined per purchasing group.
( Idoc creation to be sent to FLEXNET :
an idoc type ZBLAORD_RCV is to be sent to the receiving FLEXNET
system, it is triggered by the message type XNRC. Output orders are
defined per purchasing group.
in a Push mode (ZLP and ZLU document types glass products only),
an Idoc type ZBLAORD_SH is sent to the shipping Flexnet system, to
be used as reference for the shipping. It is triggered by the
message type XNSH.
Responsible : Master data manager or forecast demander
(purchaser).
Step 2 : Material Requirement Planning
MRP calculations : a job is planned to run every week. It
compares the needs, the stocks and the forecasted resources
(outstanding purchases or planned orders) to the requirements, to
trigger if necessary a planned order or a purchase.
( To determine whether the product is produced and / or
purchased, master data are used (material, source-list, quota
arrangement).
( To determine a scheduling agreement is used, master data are
used (source-list).
Responsible : automatic for MRP calculations.
Step 3 : Scheduling Agreement schedules (Delivery schedules)
management
From the MRP analysis transactions MD05 or MD06 schedule lines
can be checked. They can also be checked / changed directly from
the purchasing document transactions ME38 (change) or ME39
(display).
For a schedule line, a creation indicator is determined, it is
set to :
B if it was created by MRP, this type of schedule line is
changeable at any time by new MRP calculations
R if it was created manually, this type of schedule line is not
changeable by new MRP calculations .
But in any case, for a schedule line not yet delivered, the
scheduled quantity is changeable.
Outputs :
( Printout : once updated and if wanted by the purchasing
department, the delivery schedule can be printed and sent to the
vendor. Printing orders are defined per purchasing group
for LPA document types, message type ZLPH. Triggered when using
ME84transaction,
for LP, ZLP, LU and ZLU document types, message type ZLPE can be
triggered manually.
( No idoc is triggered because delivery schedules are never sent
to FLEXNET
Responsible : forecast demander (purchaser).
Remark : reminders on schedule lines can be launched and
printed.
Message type ZREL
Step 4 : Scheduling Agreement modification
Several types of modification are possible in a Scheduling
Agreement :
Item creation : the new item is to be taken into account
Item modification, to change one or several data, including flag
the Delivery complete indicator once the ordered quantity has been
received
Item blocking : it enables to block an item for supply and
receipt
Item deleting
Outputs : in all these cases,
( a modification printout is printed to be sent to the
vendor,
( and for products managed in FLEXNET, an idoc is sent to
FLEXNET to update the purchasing document data
an idoc type ZBLAORD_RCV is to be sent to the receiving FLEXNET
system
in a Push mode (ZLP and ZLU document types glass products only),
an Idoc type ZBLAORD_SH is sent to the shipping Flexnet system.
4.1.3 Revision level or Customer material number change
management
When the customer changes its material reference or its revision
level, the rule is to change the SAP product code for all products
physically changed by the customer modification.
For instance, in a logistic flow
Glass
plant
Extrusion /
Encapsulation
plant
Service centre
Customer
Production
Product A
Product A +
Encapsulation
Product D
Product D +
Value addition
Product E
A
E
D
If a modification is asked on encapsulation part, the flow
becomes
Automatic
Material Requirement
Planning
Master data manager
Scheduling agreement
creation, on receiving plant
Demand Forecaster / Purchaser
Scheduling Agreement schedule
lines creation / modification
Master data manager
Vendor, on Purchasing
Organization
Master data manager
Material, on receiving plant
Receiving Plant
Master data manager
Purchase info-record, on
receiving plant
Physical
Goods
transfer
ZBLAORD_RCV
1
3
2
Pre-requisites
Master data manager
Source-list creation, with
the Scheduling Agreement
reference
Process flow
Demand forecaster
Scheduling agreement
modification
4
Master data manager
Quota-arrangement
creation
( If no agreement is concluded with the customer, it means that
if the customer changes its code, Sekurit has to stop to deliver
the old material code and immediately begins to deliver the new
one. This will influence the Sekurit production Strategy to make as
few stock as possible.
In this case, low stock will cost less to Sekurit but will be
difficult to implement as the new products must be produced
immediately.
( If an agreement is concluded with the customer to allow
Sekurit to clear out the old reference stock before delivering the
new reference, Sekurit can still deliver the old reference while
the customer sends its requirements on the new reference.
In any case, all Sekurit plant (planners) participating to the
concerned product supply chain should be informed of the
modification.
For all plants concerned by the product modification, the
previously described pre-requisites of the process should be
reviewed. If there is no agreement with the customer, it should be
reviewed immediately. If an agreement is concluded, it should be
reviewed once the old reference stocks have been cleared out.
In the previous example, it concerns two products :
the tradable semi-finished product B becomes D
the finished product C becomes E.
If the flow between the two plants is a inter-company flows
:
Old product
New product
Material
While customer requirements are declared on the old product,
declared with Discontin. Part to transfer production requirements
onto the new product
Once the stocks have been cleared out, marked for deletion on
the shipping and receiving plants,
If stocks have not been cleared out, it is not marked for
deletion
Transaction MM06 (*)
Created in copy of the old product, on the shipping and
receiving plants.
Transaction MM01 (*)
Vendor
No modification required
Info-record
It should be marked for deletion
Transaction ME15
Created for the new product, with the correct cession price, on
the receiving plant.
Transaction ME11
Source-list
The items of the source-lists should be deleted.
Transaction ME01
The source-list for the new product, on the receiving plant, is
created.
Transaction ME01
Quota-arrangement
The items of the quota-arrangement should be deleted.
Transaction MEQ1
The quota-arrangement for the new product, on the receiving
plant, is created.
Transaction MEQ1
Scheduling agreement
The item of the scheduling agreement is blocked, to stop its use
in planification and send an idoc to block the item in FLEXNET.
Transaction ME32L (**)
A new item is created, either in the same scheduling agreement,
or in another scheduling agreement.
Transaction ME32L (**)
If the flow between the two plants is a intra-company flows
:
Old product
New product
Material
While customer requirements are declared on the old product,
declared with Discontin. Part to transfer production requirements
onto the new product
Once the stocks have been cleared out, marked for deletion on
the shipping and receiving plants,
If stocks have not been cleared out, it is not marked for
deletion
Transaction MM06 (*)
Created in copy of the old product, on the shipping and
receiving plants.
Transaction MM01 (*)
Source-list
The items of the source-lists should be deleted.
Transaction ME01
The source-list for the new product, on the receiving plant, is
created.
Transaction ME01
Quota-arrangement
The items of the quota-arrangement should be deleted.
Transaction MEQ1
The quota-arrangement for the new product, on the receiving
plant, is created.
Transaction MEQ1
Scheduling agreement
The item of the scheduling agreement is blocked, to stop its use
in planification and send an idoc to block the item in FLEXNET.
Transaction ME32L (**)
A new item is created, either in the same scheduling agreement,
or in another scheduling agreement.
Transaction ME32L (**)
*When created or changed, an idoc type ZMATMAS is automatically
created to send the material data to FLEXNET, for each plant on
which the material is declared.
**When created or changed,
for the Receiving FLEXNET system, a message type XNRC is created
in the scheduling agreement to create an idoc type ZBLAORD_RCV.
For the Shipping FLEXNET, in case of an intra or inter-company
flow with a PUSH mode, it is required to send the scheduling
agreement data to both receiving and shipping plant. So, a message
type XNSH is created in the scheduling agreement.
4.1.4 Scheduling agreements content
Here is the list of data used in Scheduling agreements :
HEADER DATA
Field
Status
Mandatory / Optional
Description
Changeable data : Y/N
Agreement
Display
Number of the outline agreement, affected by the system.
Company code
Display
Company, determined through the ordering plant
Purchasing group
Mandatory
Key for a buyer or a group of buyers, who is/are responsible for
certain purchasing activities.
Y
Supplying plant
Optional
Describes the plant from which the ordered material is
supplied.
In case of inter-company purchasing flow, determined
automatically when the vendor number is filled in.
In case of intra-company flow, filled in.
N
Vendor
Mandatory
Supplying vendor account number
N
Agreement type
Mandatory
LPA for external vendors and inter-company vendors, for
receiving site within Sekurit Avenir V2 solution,
LP for external vendors and inter-company vendors, for receiving
site within Sekurit Avenir V1 solution,
ZLP for inter-company vendors, applying a PUSH mode,
LU for intra-company vendors (transfers)
ZLU for intra-company vendors, applying a PUSH mode.
N
Purchasing organization
Mandatory
Organizational unit that negotiates the general conditions of
purchase for several plants or a single plant.
There is 1 purchasing organization per country.
N
Administration fields
Agreement date
Mandatory
Creation date of the agreement
N
Item number interval
Mandatory
Determines the size of the steps between the default item
numbers.
Y
Item interval for sub-items
Not used in SGS
Optional
Currently not used
Validity start
Validity end
Start of validity period. Default value : creation date
End of validity period
Y
Language
Mandatory
Default value : language of the vendor. Changeable when creating
the scheduling agreement.
Not used for printout : printouts are currently performed in the
purchasing company language.
N
Indicator : goods receipt message
Not used in SGS
Optional
Indicator specifying that the system is to issue an appropriate
message to the buyer following each goods receipt in respect of
this purchase order.
Terms of delivery and payment
Payment terms
Optional
Key for defining payment terms composed of cash discount
percentages and payment periods.
Only Required for External Vendors
Brought from the vendor master.
Y
Payment in 1
Optional
Number of days, determined through the previous payment terms
key.
Y
Percentage for first cash discount
Optional
Cash discount percentage rate applied to the shortest payment
terms, determined through the previous payment terms key.
Y
Payment in 2
Optional
Number of days, determined through the previous payment terms
key.
Y
Percentage for second cash discount
Optional
Cash discount percentage rate applied to the shortest payment
terms, determined through the previous payment terms key.
Y
Payment in 3
Optional
Number of days, determined through the previous payment terms
key.
Y
Target value
Not used in SGS
Optional
Total value of all materials to be released against the
agreement.
Currency
Mandatory
Default value = Order currency
Y
Exchange rate
Mandatory
Factor for the conversion of a foreign currency into local
currency. Calculated automatically if order currency is different
from the local currency.
Y
Indicator: fixing of exchange rate
Not used in SGS
Optional
Determines that the exchange rate calculated or entered in the
purchasing document is fixed.
Incoterm
Part 1
Part 2
Optional
Incoterms specify certain internationally recognised procedures
that the shipper and the receiving party must follow for the
shipping transaction to be successfully completed.
Additional information for the primary Incoterm : provides
details of the port from which the delivery leaves.
Y
Reference data
Quotation date
Not used in SGS
Optional
Date on which the vendor submitted the quotation
Quotation
Not used in SGS
Optional
Number of vendor's quotation
Your reference
Optional
Customer's or vendor's internal reference
Y
Sales person
Optional
Responsible salesperson at vendor's office
Brought from vendor master
Y
Our reference
Not used in SGS
Optional
Your company's internal reference number or code.
Usable if our requirements are transmitted to vendors via EDI
(Electronic Data Interchange) messages.
Supplying vendor
Optional
If the vendor from whom the goods are ordered is not the actual
supplier, you can enter the account number of the supplying vendor
here.
Y
Invoicing party
Optional
This number denotes the vendor invoicing the ordered material or
services rendered
Determined through partner function PI Invoice presented by
Y
Taxes
Country of sales tax ID number
Optional
Specifies the key for the country of the VAT registration
number
Determined through the company or the purchasing
organization.
Y
Text overview
Header text
Optional
Free text Printed
Y
Header note
Optional
Free text Not printed
Y
Pricing types
Optional
Free text Printed
Y
Deadlines
Optional
Free text Printed
Y
Terms of delivery
Optional
Free text Printed
Y
Shipping instructions
Optional
Free text Printed
Y
Terms of payment
Optional
Free text Printed
Y
Warranties
Optional
Free text Printed
Y
Penalty for breach of contract
Optional
Free text Printed
Y
Guarantees
Optional
Free text Printed
Y
Contract riders (clauses)
Optional
Free text Printed
Y
Asset
Optional
Free text Printed
Y
Other contractual stipulations
Optional
Free text Printed
Y
Delivery
Optional
Free text Printed
Y
Vendor memo (general)
Optional
Free text - Not printed
Y
Vendor memo (Purch. Org.)
Optional
Free text - Not printed
Y
Vendor address
Title
Name
Search terms
Street / House number
Postal code / City
Country
Mandatory
Brought from vendor master data.
Printing rule : this address is printed, except :
if a different supplying vendor is declared in Header / Details
view,
if a different Ordering Address vendor is declared in Partner
functions view (partner function OA).
Y
Language
Telephone
Fax
Mandatory
Brought from vendor master data.
Y
Conditions
Net value currency
Display
Order currency
Net value
Display
Calculated : sum of the items conditions
Condition types :
PB00 or PBXX, depending on the items condition types,
SKTO for discounts. In Germany, discounts are taken into account
when receiving the goods, in the other countries, they are taken
into account when posting the invoice. (Customized by FI for
payment conditions).
Statistics
Created on
Display
Creation date
Created by
Display
User who created the document
Last item
Display
Number of the current last item of the agreement
Partners
They are brought from vendor master
Ordering address
Optional
Number of vendor account responsible for the order
Y
Vendor
Mandatory
Number of vendor account
Y
Delivering plant
Optional
Number of vendor account responsible for the delivery
Used in case of intra-company flow
Y
Invoice presented by
Optional
Number of vendor account responsible for the invoice
Y
Messages
Message type
Optional
Two message types are managed :
ZNEU, for a printout. Triggered automatically.
XNRC, for an idoc creation. Triggered if the receiving plant
works with FLEXNET
XNSH, for an idoc creation. Triggered in a PUSH mode, if the
shipping plant works with FLEXNET.
XNEU, for an idoc creation. Triggered only for glass products
and if the receiving plant works with DCS.
Y
Import
Mode of transport (when goods cross border)
Optional
Identifies the mode of transport (for example: road, rail, or
sea) by which the goods cross a border during export or import. Set
to 3. Brought from vendor master.
Y
ITEM DATA
Field
Status
Mandatory / Optional
Description
Changeable data : Y / N
Agreement item
Mandatory
Item in the agreement
Given by SAP
N
Item category
Optional
Key defining how the procurement of a material or service item
is controlled. Categories used :
Blank for standard
K for consignment
L for sub-contracting
U for stock transfer (document type LU)
N
Account assignment category
Optional
Key specifying whether accounting for an item is to be effected
via an auxiliary account. Are used :
F for internal order
K for cost center
Y
Material number
Mandatory
Purchased material number.
N
Material description
Mandatory
Material short text, brought from material master in the
language of the vendor
Y
Material group
Display
Key that you use to group together several materials or services
with the same attributes.
Brought from material master.
Plant
Mandatory
Plant which should receive the ordered goods
N
Storage location
Optional
Storage location which should receive the ordered goods
Y
Quantity and price
Target quantity
Mandatory
Total quantity, agreed with the vendor, that can be scheduled
(in the case of a scheduling agreement item).
This quantity is not blocking if passed in SAP, neither in
FLEXNET.
Y
Order unit
Mandatory
Unit of measure in which the material is ordered. It is copied
from material master data.
N
Net order price
Mandatory
Purchasing price : brought from
Purchase info-record if exists,
from the last purchase order if exists,
filled in manually if none of previous objects exist.
Y
Equals
Denominator for conversion
Order UoM
Numerator for conversion
Mandatory
Conversion of order unit into base unit.
To convert a quantity, whose unit of measure is not the same as
the base unit of measure, into the base unit of measure, the system
requires a quotient : Quantity (in alternative unit of measure) =
quotient x quantity (in base unit)
Y
Indicator: update info record
Optional
Indicator that determines
whether the purchasing info record for this vendor and material
is to refer to this PO item, and
whether the item is to be valid for the entire purchasing
organization or just for the plant.
Y
Other data
Reminder 1
Reminder 2
Reminder 3
Optional
Number of days representing the time interval at which reminders
or urging letters / messages are to be issued to the vendor. The
basis for the reminder intervals is the delivery date or deadline
for submission of quotations. Reminding levels should be set out in
ascending order of time.
There are copied from the material master, or from the purchase
info-record if it exists.
Y
Confirmation control key
Not used in SGS
Display
Key that determines which confirmation categories are expected
for a PO item (e.g. order acknowledgment, shipping
notification).
Acknowledgment number
Used in Germany
Optional
Number of the vendor's order acknowledgment.
Y
Indicator : acknowledgment required
Not used in SGS
Determines whether the purchasing document (purchase order,
outline agreement, etc.) is to be acknowledged by the vendor.
Requirement tracking number
Optional
Number that facilitates the monitoring of the procurement of
required materials or services.
Used in Scheduling agreement for tradable glass products : set
to X if the document is to be used as a reference document in
FLEXNET (for CIM Shipping process).
Y
Vendor material number
Optional
Material number used by the vendor.
Brought from purchase info-record.
Y
Estimated price indicator
Not used in SGS
If you do not know the exact net price of a material, you can
indicate that the price is an estimated price. In consequence, a
greater price variance is tolerated during invoice verification
than would be the case in the event of an exact net price.
Print price indicator
Optional
Determines whether or not the price is to be included in the
purchase order printout. Currently causes troubles with Appic
printouts if not flagged.
Flagged by default
Y
GR / IR control
Under-delivery tolerance
Optional
Percentage up to which an under-delivery of this item will be
accepted.
It is copied from material master.
Y
Over-delivery tolerance
Optional
Percentage up to which an over-delivery of this item will be
accepted.
It is copied from material master.
Y
Unlimited over-delivery delivery allowed flag
Optional
Indicator that specifies whether unlimited over-delivery can be
accepted.
It is copied from material master.
Y
Tax code
Mandatory
The tax code represents a tax category which must be taken into
consideration when making a tax return to the tax authorities. Tax
codes are unique per country. The tax rate calculation rules and
further features are stored in a table for each tax code.
Filled in.
Y
Shipping instructions
Not used in SGS
Key for the relevant shipping instructions. Key denoting the
packaging and shipping instructions issued to the vendor.
Quality inspection indicator
Automatically positioned
Indicator that specifies whether the material is subject to
quality inspection, and whether a goods receipt is posted to stock
in quality inspection.
Automatically positioned from material master.
Delivery completed indicator
Automatically positioned
Indicator showing that the purchase order item is to be regarded
as closed.
Automatically positioned if positioned during the goods
receipt.
Final invoice indicator
Automatically positioned
Indicates that the last invoice from a vendor has been received
for an item and/or that no further invoice is expected.
Automatically positioned if positioned during the invoice
verification.
Delivery completed indicator
Automatically positioned
If this indicator is set, no further deliveries can be generated
for the item.
Automatically positioned from once the delivery created, if it
is decided to create only one delivery.
GR
Display
Goods receipt indicator
GR non-val
Not used in SGS
Display
Indicator specifying that the goods receipt for this item is not
to be valorized.
IR
Optional
Specifies whether the purchase order item involves an invoice
receipt.
Default flagged
N
GR base-IV
Optional
Indicator specifying that provision has been made for GR-based
invoice verification for a purchase order item or invoice item.
Flagged
N
ERS
Used only in Spain
Optional
Evaluated receipt settlement (ERS)
Brought from vendor master.
Y
Account assignments
Only available if purchased is performed for a non stocked
material (cost center or order)
G / L account number
Optional
G/L account in a chart of accounts
Y
Company code
Display
Company code responsible for these account assignments
Business area
Optional
Business area responsible for analysis, determined
automatically
Y
Cost center
Optional
If Account assignment category K
Y
Order
Optional
If Account assignment category F
Y
WBS element
Not used in SGS
Optional
Work Breakdown Structure Element
Unloading point
Optional
Point at which the material is to be unloaded (for example dock
1)
Y
Goods recipient
Optional
Recipient for whom the material or the service is destined
Y
More indicator
Optional
When you select this field, all account assignments are shown in
a dialog box.
Y
Conditions
Condition type
Display
The following condition types are used, independently of the
product family :
price = PB00 if brought from a purchase info-record or PBXX if
set manually
FRB1 for Freight (in value)
RA01 for Discount % on gross price
RB00 for Discount (value)
GRWR for Statistical value = transport value in % between the
border and the delivery point, used for Intrastat declaration.
The four last condition types are either set in the info-record,
or set manually in the purchasing document.
Remark : if the purchasing price is changed in the info-record,
the price in the scheduling agreement is not automatically updated.
Price should be also manually changed in the scheduling agreement
item.
Y
Rate
Mandatory
= Net price
Y
Net value currency
Mandatory
Order currency
Y
Net value
Mandatory
Calculated : sum of the items conditions
Y
Text overview
Item text
Optional
Free text Not printed
Y
Info record PO text
Optional
Free text Printed
Brought from Purchase info-record
Y
Material PO text
Optional
Free text Printed (replaces material short text)
Brought from material master
Y
Delivery text
Optional
Free text Printed
Y
Info record note
Optional
Free text Not printed
Y
Statistics / General
Info record
Display
Info-record number if it exists for the vendor / material /
purchasing organization / plant.
N
Requisition
Display
Purchase requisition number and item number if the agreement was
created referring to this requisition.
N
Agreement
Display
Agreement number and item number if the agreement was created
referring to this outline agreement.
N
RFQ
Display
Request for quotation number and item number if the agreement
was created referring to this RFQ.
N
Last changed on
Display
Last item modification date
Statistics / PO history
Table
Display
List of documents declared in the system referring to the
scheduling agreement :
Goods receipt movements (goods receipt or return to vendor
movements)
Invoice verifications
Delivery notes if inter or intra-company flows
Goods issues of deliveries if inter or intra-company flows.
Statistics / Changes
Table
Display
List of modifications made on this scheduling agreement :
User who performed the modification
Date and hour of the modification
Transaction used
Object modified, with the old and the new value.
Delivery Address
Delivery address
Mandatory
All coordinates of the receiving plant. Brought from plant
customizing
Y
Taxes
Not used in SGS
Taxes data
Additional data
Creation profile
Mandatory for LPA document types
It controls :
the creation periodicity of the releases (scheduling agreement
delivery schedules) - the release creation and transmission to the
vendor,
the way in which the quantities transmitted to the vendor are
aggregated (starting from the current creation date of the
release)
There is one Creation Profile per requirements transmission
method defined with our vendors.
Y
Import
Data are optional (purchasing document can be saved) but if
missing, they will block the intrastat declaration.
Commodity Code / Import Code No.
Optional
Official (8 digit) key corresponding to the EC harmonised system
for the description and coding of merchandise.
The commodity code is used for statistical purposes and must be
declared to the authorities for various foreign trade transactions,
both import and export transactions.
Brought from material master.
Y
Manufacturer number
Optional
= Vendor number
Y
Country of origin
Optional
Country code of the main (default) plant producing the material.
This information is required for the declarations regarding goods
receipts/exports and goods dispatches / imports which are made to
the authorities.
Brought from info-record if it exists or from material
master.
Y
Region of origin
Optional
Describes more precisely the origin of goods. Used in Germany
(land), Belgium and France (department).
Brought from info-record if it exists or from material
master.
Y
Export / Import procedure
Optional
For business transactions within the European Community (EC),
the export/import procedure code is part of the information that
you submit in monthly reports to Intrastat and is of statistical
interest only. Filled in.
Values to be used are defined per country.
Y
Business transaction type
Optional
Classifies the type of business transaction which is performed.
Determined through customizing.
Y
4.1.5 Scheduling agreement scheduling lines
Scheduling lines are only manageable once the scheduling
agreement has been created.
We will not detail again header and item data that are managed
in the scheduling agreement, but only schedule data.
SCHEDULE DATA
Field
Status
Mandatory / Optional
Description
Changeable data : Y / N
Delivery schedule
Category of delivery date
Mandatory
Format of the delivery date. Usually D for Day format but could
be
T Day format
W Week format
M Month format
Y*
Delivery date
Mandatory
Date on which the goods are to be delivered
Y*
Scheduled quantity
Mandatory
Quantity to be delivered by the vendor in respect of this
schedule line.
Y*
Time spot
Y*
Indicator : firm or trade-off zone
N
Creation indicator
Display
Indicates whether the schedule line was created manually (R) or
automatically (B-MRP)
Statistic-relevant delivery date
Date for the calculation of the delivery time, which takes into
account the vendor delivery times.
Y*
Purchase requisition number
Display
Purchase requisition number transformed into the schedule
line.
Purchase requisition item
Display
Purchase requisition item transformed into the schedule
line.
Cumulative scheduled quantity for item
Display
The cumulative scheduled quantity = sum of the cumulative
received quantity and the cumulative open scheduled quantities up
to the key date of the schedule line.
Previous cumulative quantity
Display
Cumulative quantity notified to the vendor at the time of the
last transmission.
Previous quantity
Display
Quantity notified to the vendor at the time of the last
transmission.
GR quantity
Display
Quantity already delivered to date with regard to this item or
schedule line.
Number of reminder / urging messages for schedule line
Display
Number of times a reminder or message urging delivery
(expediter) has been sent with respect to a line of a delivery
schedule created under a purchase order or scheduling
agreement.
Schedule line is fixed
Display
Indicator that "fixes" the schedule line and determines that it
cannot now be automatically changed via Materials Planning and
Control/MRP.
Cumulative issued quantity
Display
Cumulative quantity of the material issued up to this schedule
line.
Quantity delivered
Display
Delivered quantity for schedule line from stock transfer
Open quantity
Display
Ordered quantity that is still to be delivered.
Committed quantity
Display
Quantity which is available or which can be delivered by means
of warehouse stock and/or receipts.
Committed date
Display
Date that the committed quantity is available or can be
delivered
Components / Overview
Only for sub-contracting purchasing documents (Item category =
L)
Material
Mandatory
Material number of the component
Y
Required quantity
Mandatory
Required quantity of the component = scheduled quantity of the
finished product adjusted with scraps (operation or component)
Cf. Remark below
Y
Plant
Mandatory
Same than the scheduling agreement item plant
Y
Requirements date for the component
Mandatory
Date that the requested quantity of material is required
Y
BOM item number
Mandatory
This number refers to the sequence of components in a bill of
material
Y
Messages
Message type
Optional
Three message types are managed :
LPET, for a printout through the standard SAP form.
ZLPE, for a printout through the Appic form
XLPE, for an idoc creation. Not used anymore, used to be created
for SGSVI.
Y
* if the delivery line was not delivered
Remark : beware of the item target quantity and the component
required quantity.
By default, when creating the sub-contracting scheduling
agreement item, the component required quantity is set
proportionally to the target quantity. For example, if 1
semi-finished product is needed in BOM (Bill of Material) to
produce 1 finished product, and if the target quantity for finished
product is 1000, then the semi-finished product required quantity =
1000.
4.1.6 Scheduling agreements - Data sent to FLEXNET
Data are sent to FLEXNET via ZBLAORD_RCV and ZBLAORD_SH idoc
types.
They are sent to DCS via a BLAORD idoc type.
Idocs are only triggered if necessary :
ZBLAORD_RCV idoc type is created when creating a message type
XNRC in the purchasing document
ZBLAORD_SH idoc type is created when creating a message type
XNSH in the purchasing document
BLAORD idoc type is created when creating a message type XNEU in
the purchasing document.
XN* triggering rules are based on the purchasing group.
Here is the list of data sent through BLAORD idoc type
Segment
Type
Segment / Field
Type
Field
Content
E1EDK01
F
CURCY
Currency
F
WKURS
Exchange rate
F
ZTERM
Terms of payment key
F
BSART
Document type
F
BELNR
IDOC document number : Document number
F
RECIPNT_NO
Number of recipient : Supplier number
E1EDKD1
F
EKORG
Purchasing Organization
F
EKGRP
Purchasing group
E1EDK14
F
QUALF
IDOC qualifier organization
F
ORGID
IDOC organization : Purchasing Organization
E1EDK14
F
QUALF
IDOC qualifier organization
F
ORGID
IDOC organization : Purchasing group
E1EDK14
F
QUALF
IDOC qualifier organization
F
ORGID
IDOC organization : Scheduling Agreement type
E1EDK14
F
QUALF
IDOC qualifier organization
F
ORGID
IDOC organization : Company code
E1EDK03
F
IDDAT
Qualifier for Idoc date segment Document date
F
DATUM
IDOC : date
E1EDK03
F
IDDAT
Qualifier for Idoc date segment Date IDOC created
F
DATUM
IDOC : date
E1EDK03
F
IDDAT
Qualifier for Idoc date segment Quotation date (supplier)
F
DATUM
IDOC : date
E1EDK03
F
IDDAT
Qualifier for Idoc date segment Start of validity for outline
agreement
F
DATUM
IDOC : date
E1EDK03
F
IDDAT
Qualifier for Idoc date segment End of validity for outline
agreement
F
DATUM
IDOC : date
E1EDKA1
F
PARVW
Partner function
F
PARTN
Partner number
F
TELF1
1st telephone number of contact person
F
TELFX
Fax number
F
IHREZ
Your reference (partner)
F
BNAME
IDOC user name
F
PAORG
IDOC organization code
F
ORGTX
IDOC organization code text
F
PAGRU
IDOC group code
E1EDKA1
F
PARVW
Partner function
F
PARTN
Partner number
F
TELF1
1st telephone number of contact person
F
IHREZ
Your reference (partner)
F
BNAME
IDOC user name
E1EDKA1
F
PARVW
Partner function
F
LIFNR
Vendor number at customer location
Contains the Plant
F
NAME1
Name 1
F
NAME2
Name 2
F
STRAS
Street and house number 1
F
ORT01
City
F
PSTLZ
Postal code
F
LAND1
Country key
F
SPRAS
Language key
F
REGIO
Region
E1EDKA1
F
PARVW
Partner function
F
PARTN
Partner number
E1EDK02
F
QUALF
IDOC qualifier reference document
F
BELNR
IDOC document number
F
DATUM
IDOC : date
F
UZEIT
IDOC : time
E1EDK02
F
QUALF
IDOC qualifier reference document
F
BELNR
IDOC document number
E1EDK17
F
QUALF
IDOC qualifier : terms of delivery
F
LKOND
IDOC delivery condition code
E1EDK18
F
QUALF
IDOC qualifier : terms of payment
F
TAGE
IDOC number of days
E1EDK18
F
QUALF
IDOC qualifier : terms of payment
F
TAGE
IDOC number of days
E1EDKP1
F
EKORG
Purchasing organization
F
PARVW
Partner function ID
F
LIFN2
Reference to other vendor
Repetitive segment for every partner function
E1HTXT1
F
TDOBJECT
Texts : application object
F
TDID
Text ID
F
TDSPRAS
Language key
S
E1HTXT2
F
Tag column
F
Text line
Repetitive segment for every text
E1EDP01
F
POSEX
Item number
F
PSTYP
Item category
F
MENGE
Quantity
F
MENEE
Unit of measure
F
BMNG2
Quantity in price unit
F
PMENE
Price unit of measure
F
VPREI
Price (net)
F
PEINH
Price unit
F
NETWR
Item value (net)
F
NTGEW
Net weight
F
GEWEI
Weight unit
F
MATKL
IDOC material class
F
EVERS
Shipping instructions
F
BPUMN
Denominator for conversion of order price unit into order
unit
F
BPUMZ
Numerator for conversion of order price unit into order unit
S
Z1EDP19 BR6
F
ZBEDNR
SAP reference document
F
ZLOEKZ
Item status
S
E1EDP02
F
QUALF
IDOC qualifier reference document
F
BELNR
IDOC document number
S
E1EDP19
F
QUALF
IDOC object identification such as material n
F
IDTNR
IDOC material ID
F
MFRNR
Manufacturer number Contains Storage location
S
E1EDP19
F
QUALF
IDOC object identification such as material n
F
IDTNR
IDOC material ID
F
KTEXT
IDOC short text Contains material description
F
MFRNR
Manufacturer number Contains Storage location
S
E1EDP17
F
QUALF
IDOC qualifier : Terms of delivery
F
LKOND
IDOC delivery condition code
F
LPRIO
Delivery priority
S
E1EDPD1
F
BEDNR
Requirement tracking number
F
PRSDR
Print price
F
UNTTO
Underdelivery tolerance limit
F
UEBTO
Overdelivery tolerance limit
F
MAHN1
Number of days for first reminder / urging letter
F
MAHN2
Number of days for second reminder / urging letter
F
MAHN3
Number of days for third reminder / urging letter
F
LABNR
Order acknowledgment number
F
MWSKZ
Tax code
F
WEBRE
Indicator : GR-based invoice verification
F
WERKS
Plant
F
LGORT
Storage location
S
E1ITXT1
F
TDOBJECT
Texts : application object
F
TDID
Text ID
F
SPRAS
Language key
S
E1ITXT2
TDFORMAT Tag column
TDLINE Text line
Repetitive segment for every text
E1EDS01
F
SUMID
Qualifier for totals segment for shipping notification
F
SUMME
Total value of sum segment
F
SUNIT
Total value unit for totals segment in the shipping
notification
E1EDS01
F
SUMID
Qualifier for totals segment for shipping notification
F
SUMME
Total value of sum segment
F
SUNIT
Total value unit for totals segment in the shipping
notification
4.2 Country or customer specific Key elements of system
implementation
4.2.1 Creation profiles
SPAIN:
Plant 010
Days
Weeks
Months
Plant 011
Days
Weeks
Months
Plant 013
Days
Weeks
Months
0001
30
0003
90
0001
30
0002
60
0043
28
90
0002
60
0003
90
0806
8
180
0003
90
0013
7
90
0030
21
0030
21
0040
28
00D0
90
00DO
90
0040
28
0806
8
180
0D00
90
Plant 020
Days
Weeks
Months
Plant 021
Days
Weeks
Months
Plant 022
Days
Weeks
Months
00D0
90
00DO
90
00D0
90
Plant 023
Days
Weeks
Months
Plant 024
Days
Weeks
Months
Plant 026
Days
Weeks
Months
00D0
90
00DO
90
00D0
90
Plant 027
Days
Weeks
Months
00D0
90
GERMANY
for connectors : 1424 plants : 424, 441, 442
for raw glass : 0735 plants : 441, 442, 448, 449
for mirrorpads : 1464 plants : 422, 441
for PU (extrusion) : 0084 plants : 422, 442
for rahmen (encapsulation) : 0774 plants : 422
for silverpaste : to be defined plants : 441, 442, 448, 449
for drehte : 0045 plants : 441
for cleaner and primer : 1464 plants : 422, 442
for PVB : 0043 plants : 441
for logistic products : 0084 all plants
pastes : 1436 (Silber, UV, IR) : 441, 442
FRANCE
For plant 560:
0042 (used for silver paste,enamel, embases, connectors)
0001 (Cleaner, Primer)
0806 (Raw glass with a planning calendar 6d/7 associated)
0083 (PVB)
0080 (PET)
For plant 561:
0011 (silver paste, enamel, connectors, plastic parts)
0001 (Cleaner, Primer)
0806 (Raw glass with a planning calendar 5d/7 associated)
For plant 300:
0042 (for all types of material)
For All plants (560, 561, 571, 572, 573, 574, 575, 576, 577,
578, 579, 581, 582, 583, 590, 591, 592, 300) for logistics
products: 0084
4.2.2 Fax sending
The delivery schedule of LPA scheduling agreements can be sent
by fax :
either in the place of the printout (systematic sending by fax
when ZLPH is launched via ME84)
or manually with a special message type : ZFAX
4.2.3 Push / Pull flows in inter-intracompany
SPAIN :
PUSH flows
between glass plants and service centers
between Devisa and service centers
PULL flows
all other flows
GERMANY
No PUSH flow in inter-intracompany
FRANCE
4.3 Summary
Action
Transac. / data
Comments
1. Pre-requisites
MM03
XK03
ME13
ME33L
ME03
MEQ3
Display material master
Display vendor master
Display info-record
Display Scheduling agreement
Display Source-list
Display Quota Arrangement
2. Material Requirement Planning
3. Scheduling agreement schedule lines creation /
modification
ME38
Maintain scheduling agreement schedule
4. Scheduling agreement modification
ME32L
Change Scheduling agreement
5. Release creation
ME84
Generation of Scheduling Agreement release
IMMM008-Partner determination
IMMM016-Stock transport scheduling agreement
IMMM017-Incoterms
IMMM018-Commodity codes
IMMM019-Business transaction types
IMMM020-Import_Export procedure
IMMM023-Number ranges for purchase orders
IMMM025-Message types
IMMM026-Layout sets per message type
IMMM027-Message determination schemas
IMMM028-Partner roles per message type
IMMM031-Confirmations for PO
IMMM032-New units of measure
IMMM052-Creation Profiles
5 Organizational roles and impacts
( For a regular purchasing flow, it is interesting to maintain a
purchasing scheduling agreement : among other purchasing processes,
it enables MRP calculations to update automatically schedule lines
when required. Then, the purchaser can control the MRP result but
he is not compelled to transform each time a purchase requisition
into a purchase order.
( Master data management
As detailed in pre-requisites, master data are necessary before
creating a scheduling agreement. So, master data maintenance
procedures should be synchronized with purchasing documents
management procedures.
Master data required :
material,
vendor,
purchasing master data : info-record, source-lists, quota
arrangements.
( Profiles management
Impact of use of Scheduling Agreement and Contracts on user
profiles should be worked out.
( Use of a new scheduling agreement type : document type LPA,
for which :
there is a new field to maintain, the Creation Profile
the delivery schedule release is slightly different.
( Factory calendar changed : on 7 days.
In Sekurit Avenir V1, the factory calendar was set on a 5 days /
week basis. For planning constraints, it is set to a 7 days / week
basis. This will have an impact on purchasers work : if working
with a purchasing document type different from LPA, MRP might
create delivery dates on every possible day.
6 Application specific development requirements
( Only relevant for intra-company process : Cf. V2-TBMM18 -
Purchasing Process - intra-company flows-v1.
A specific customizing concerns the idoc sent to FLEXNET :
instead of sending the idoc sent to the receiving FLEXNET system,
for intra-company flows in PUSH mode, the scheduling agreement
content is sent to both sending and receiving FLEXNET systems.
The Idoc structure has been changed :
MM_112_AIG_Download_SA_BLAORD
( For printout : page setup is not performed in SAP but in an
external application, APPIC.
So, when a ZNEU message is created, it triggers a data
extraction which is then sent to APPIC. The extraction programs
are
ZMFMM010_CONLIV for the scheduling agreement
ZMFMM010_LIVRAISON for the scheduling agreement delivery
schedule.
Specifications of the extraction program are under S:\Core
Solution\Development\aig_aid_aigd\Mm\ MM_010_AIGD_Purchase
order_YMM_PORD.
7 Key volume & performance indicators
In date 27/09/02, here are scheduling agreements creations
volumes :
Germany
France
Italy
Belgium
Spain
1998
100
1999
245
2000
288
1526
24
39
2001
314
95
43
27
2002
178
25
29
9
1
8 Added value for the Business and economical considerations
EMBED Word.Picture.8
Glass
plant
Extrusion /
Encapsulation
plant
Service centre
Customer
Production
Product A
Product A +
Encapsulation
Product B
Product B +
Value addition
Product C
A
C
B
SAP
Scheduling
agreement
Requirement
planning
Scheduling
agreement -
Schedule
lines
Other strategic materials, included in
BOMs
Other products, not included into
BOMs
, managed in stock
Buyer
_1097068240.doc
SAP
Scheduling
agreement
Requirement
planning
Scheduling
agreement -
Schedule
lines
Other strategic materials, included in
BOMs
Other products, not included into
BOMs
, managed in stock
Buyer
