Seasonal Procurement

Allocation Table

SAP AG 2005
 Motivation

Enhancements Overview

New Features and Dialogs

Conclusion

SAP AG 2005
 Motivation

Enhancements Overview

New Features and Dialogs

Conclusion

SAP AG 2005
 Motivation

In order to adapt the allocation table to the needs of fashion retailers

it is necessary to optimize some selection screens, views and
features
To get more information about or within allocation tables in a quicker
way new transactions and views have to be developed
In order to fit into the plan driven processes from the strategic
planning to operational levels (OAPC and seasonal procurement) the
allocation table has to be integrated.
The handling of allocation strategies and the strategies themselves
have to be improved and adapted to the requirements of seasonal
processes
In the seasonal procurement process the delivery cycles have very
often long lead times. Therefore it is necessary to make the
allocation table more flexible even after the follow on documents are
generated.

SAP AG 2005
 Motivation

Enhancements Overview

New Features and Dialogs

Conclusion

SAP AG 2005
 Enhancements Overview 1

Enhancing Allocation Table creation for reference to

purchase order
Enhancing Allocation Table creation for material mass
selection
Enhancing Allocation Table creation item fast change
New View - recipient matrix in the Allocation Table
New features for allocation strategies
New options for the follow-on document generation
Allocation Table
New Allocation Table list

SAP AG 2005
 Enhancements Overview 2

Generate allocation table for reference to purchase order

based on Operational Assortment Planning
Change of recipient data in the allocation table after
purchase order is created
Synchronization of allocation table if a corresponding
purchase order is changed
Management of consignment stocks in Allocation Table

SAP AG 2005
 Motivation

Enhancements Overview

New Features and Dialogs

Conclusion

SAP AG 2005
 Enhancing Allocation Table Creation

for Reference to Purchase Order

When creating ad-hoc allocation tables, it is now possible to select
existing purchase orders by the delivery date in the distribution
center.

for Material Mass Selection

Within the multiple material selection it is now possible to select
materials by material list or by article hierarchy.

for Item Fast Change

The fast change function allows you now to implement changes only
for specific retail sites for an item.
This function works only with the sub screens Communication Plant,
Procurement data, plants and the sub screen Delivery phases.

SAP AG 2005
 New View in the Allocation Table: Recipient Matrix

SAP AG 2005
 New Features for Allocation Strategies

New Features for allocation strategies when SAP BW is used:

New analysis level from the article hierarchy
Consideration of the characteristics LMH
Consideration of the characteristics season
Min/max variance from existing values
Consideration of minimum/maximum values for each store
from the article master
Fixed item quantity (distribution of remaining quantity)
If you use allocation strategies with generic articles, there is a
new option to proceed the selection screen only once and not
for each variant of the generic article
It is now possible to enter the variant name of an allocation
strategy at the item overview in allocation tables

SAP AG 2005
 New Options for the Follow-On Document Generation

The follow-on document generation for Allocation Table can

now call the new Function Modules of the seasonal procurement
including OTB-Check
including Datelines
Since the OTB-Check is not activated the old or the new
function modules can be chosen
The follow-on document generation for Allocation Table uses the
same grouping options as the seasonal procurement
There are new options to generate the follow-on documents for
Allocation Table:
Generate complete purchase orders only
Only all purchase order items for an allocation table

SAP AG 2005
 New Allocation Table List

SAP AG 2005
 New Allocation Table Generation

Within the new process Strategic Planning, Operational

Assortment Planning and Control and seasonal procurement
the allocation tables are generated by a new transaction.
This report can be started by multiple selections (article,
Purchasing List Number, Purchase Order, Deliverydate DC,
node of the article hierarchy, ) and the allocation tables can
be grouped by node of the article hierarchy, PO-Number, ...
All information like articles, dates, DCs and recipients are
taken from the OAPC or the referenced PO and are
automatically fixed in the generated allocation tables by the
report.
While the quantities for the key figure initial fix are taken
strictly from the OAPC the quantities for the key figure initial
variabel could be automatically recalculated by an an
allocation strategy.
The Purchase Orders and the Purchasing Lists get also
automatically an update with the numbers of the generated
allocation tables.

SAP AG 2005
 Generate Allocation Table for Reference to Purchase
Order based on Operational Assortment Planning
preliminary planning processes

Scheduling Status update Operational Assortment Planning and Control

Status update
Purchasing List

Line Items
of Purchasing List
Order Processing Allocation
backwards

forwards

Order List

Generation of AT on basis
Grouped Order Document of POs with reference
to Purchasing List

OTB Check

Allocation Table
Monitoring of R/3-Oder creation /
Procurement dates maintenance
Synchronisation
Synchronisation

SAP AG 2005
 Allocation Table: Changes and Synchronization

The recipient data in the allocation table can be changed after the
purchase order is created.
Possible changes are quantities, dates and the addition/deletion
of recipients.

There is a new synchronization of an allocation table if a

corresponding purchase order is changed and the follow-on
documents for the recipients are not already created.
The synchronization works with the following changes to the
purchase order (seasonal procurement only):

Quantity change (quantity, unit of measure)

Date change (goods received distribution center)
Change of distribution center
Deletion of an item (purchase order item deletion indicator)
Change of the Allocation Relevant Indicator

SAP AG 2005
 Motivation

Enhancements Overview

New Features and Dialogs

Conclusion

SAP AG 2005
 Conclusion

The allocation table is as of now a much more comfortable

and more adapted to the seasonal processes
With the new allocation table list it is much easier to identify
all the allocation tables which have to be updated because of
incompleteness
The allocation table can be automatically generated within the
new seasonal procurement process starting with the OAPC
With the new recipients matrix it is now possible to see most
of the articles and the corresponding recipients quantities on
one screen
With the strategy variant the handling of allocation strategies
is much easier

SAP AG 2005
 Copyright 2005 SAP AG. All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

SAP AG 2005