You are on page 1of 29

S A P C at ch W ei g h t Man ag e m en t i n E RP 6.

0: R est r i ct i on s

SAP Catch Weight Management in


ERP6.00 - 6.03: Restrictions

Fu ncti ons, Restric tions, and E xcl usi ons


in SAP CW M
( S A P E C C 6 0 0 - E C C 6 0 3 I n d us t r y E x t e n s i o n
Catch Weight Mana gement)
Mat er ial Nu mber 500739 28
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Copyright
© 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 soft-
ware components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corpo-
ration.

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, WebS-
phere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corpora-
tion 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 tech-
nology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, ERP, 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 specifi-
cations may vary.

These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without repre-
sentation or warranty of any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

March 2010 2
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

1. INTRODUCTION..................................................................................... 5

1.1. Purpose and usage of this document ..................................................................................... 5

1.2. Background of existing restrictions ...................................................................................... 5

1.3. Localization ........................................................................................................................... 7

1.4. Enhancement packages for ERP 6.0 ..................................................................................... 7

2. FUNCTIONAL RESTRICTIONS IN FINANCIALS AND VALUATION ... 8


Overall functions that are not supported in CWM .......................................................................... 8

Material Valuation.......................................................................................................................... 10

Moving Average Price .................................................................................................................... 11

Product Cost Controlling................................................................................................................ 12

Account Assignments ...................................................................................................................... 14

3. FUNCTIONAL RESTRICTIONS IN LOGISTICS .................................. 15

Material Master .............................................................................................................................. 15

Materials Management - Inventory ................................................................................................ 16

Materials Management – Goods Movements ................................................................................. 17

Materials Management – Procurement .......................................................................................... 18

Production ...................................................................................................................................... 19

Sales & Distribution (SD) ............................................................................................................... 20

Warehouse Management (WM) ..................................................................................................... 22

Handling Unit Management (HUM) .............................................................................................. 22

Project System (PS) ........................................................................................................................ 23

Plant Maintenance (PM)................................................................................................................. 23

Quality Management (QM) ............................................................................................................ 24

4. MISCELLANEOUS ............................................................................... 25

Other Industry Solutions ................................................................................................................ 25

SAP Business Suite Integration ...................................................................................................... 25

March 2010 3
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Direct Store Delivery ...................................................................................................................... 25

Reporting in ERP............................................................................................................................ 25

BAPIs, IDOCs, and BI Extractors .................................................................................................. 26

Overview of transactions not available with CWM ....................................................................... 27

March 2010 4
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

1. Introduction

1.1. Purpose and usage of this document


The purpose of this document is to provide a complete overview about functions available in
the standard solution SAP ERP 6.0 which are no longer available after activating CWM 6.0.
Most of these functions are rarely used by customers and often also unknown to consultants.
This restrictions document is complemental to SAP’s Catch Weight Management Documenta-
tion, which is an integrated part of the SAP ERP 6.0 documentation. This means, that restric-
tions or prerequisites which are described already in the documentation are not replied in this
restrictions document. Please be aware, that also prerequisites described in the documenta-
tion might be interpreted as restrictions in the usage of ERP 6.0 when CWM ist activated.
SAP recommends not to make any decisions just on reading this document. SAP offers a 2
days workshop in order to explain and discuss CWM features and restrictions. The expe-
rience proves, that most restrictions are either not relevant or might be bridged by alternative
approaches. Please contact your local SAP sales organization in order to get more informa-
tion about this workshop.

1.2. Background of existing restrictions


Within the industry solution CWM, a new concept of units of measurements for materials is
introduced. This concept enables one unit of measure suitable for logistics and another unit of
measure suitable for financials and controlling to be used within the same material. Addition-
ally, the relationship between both units of measure can be variable. Quantities for goods
movements therefore have to be recorded in both units of measures in parallel, with additional
tolerance checks if required.
In order to realize this new concept, the industry solution CWM is based on a new architec-
ture, using the components LIME (Lean Inventory Management Engine) and Inventory Ac-
counting:
- LIME to enable the parallel recording and reporting of inventory in different units of
measures
- Inventory Accounting, to enable postings with the new valuation unit of measure for
financials and controlling
When the CWM solution is activated, all the processes that affect the material inventory (es-
pecially goods movements) are performed in LIME. In CWM, the new component Inventory
Accounting is responsible for price determination and valuation of inventory and goods
movements, as well as for updating relevant sub ledgers. To avoid process interruptions that
could result from the use of both the old and the new architecture, and to allow consolidated
reporting for documents and results, the previously used components, in particular from Mate-
rials Management, will be switched off completely. No difference will therefore be made be-
tween CWM-related and non-CWM-related procedures (for example, posting CWM materials
and posting standard materials).
This means that even processes that are not affected by the introduction of the parallel unit of
measure (for example, a goods movement triggered from Plant Maintenance) must be ad-
justed in line with the new architecture. As yet, not all of the known functions from the ERP
standard system have been enabled in the industry solution CWM. As a result, restrictions
exist, particularly for customers already using the ERP standard system. However, there are
also many functions and processes that have been newly implemented in CWM. As a result
of the new architecture, it has been possible to create new solutions to minimize or remove
some recent restrictions in the ERP standard system (for example, greater flexibility in prices

March 2010 5
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

for inventory valuation, such as modification of the standard price on a daily basis according
to new cost estimates, and automatic apportionment according to quantity where no other
apportionment has been provided for joint production).
All functional restrictions are therefore valid for the entire industry solution, irrespective of the
types of materials used, or whether or not the functions include materials.
It has been ensured that CWM supports all the main ERP processes and those that are im-
portant for the Consumer Products Industry. However, there may be instances where CWM
does not support some other ERP standard functions, although this might not be detailed in
the CWM documentation or listed as a restriction. In general, functionality must be tested
before the decision on its usage is made. The CWM validation scenario can also be viewed
as an example of a business process flow; all of the functions within this scenario have been
tested in depth.
CWM can only be activated and used in the industry version of SAP ERP. Within an SAP
ERP system which is used as a Retail-system, CWM cannot be used.
Additionally, also specific functions of the ERP Retail system which are also available within
an SAP ERP Industry system (e.g. updating the purchase order price conditions based on the
goods receipt related to the purchase order) are not implemented in CWM.
Areas for which new solutions have been created include:
Moving average price
New pricing tables and price update within product cost planning
Cost Object Controlling
Cost apportionment within joint production
None of the following have been implemented:
Cost object hierarchies and product cost collectors, thereby including any functions
from repetitive manufacturing
Active Ingredient Management, if batches are valuated according to their active in-
gredients
Activity-Based Costing
Actual Costing and Material Ledger
Repetitive manufacturing
Some business processes are implemented differently now in CWM, as otherwise (when us-
ing ERP standard logics) data inconsistencies would have resulted. Some process steps are
therefore not supported in CWM. These include:
Billing with reference to sales orders without deliveries (within CWM, parallel quanti-
ties are not recorded within the sales order but rather in the delivery and the goods
movements for the delivery. Except for third-party orders, billing is therefore only
possible with reference to the delivery.)
However, billing with reference to sales order is possible for non-Catch Weight
materials
Work in process to target costs for production orders and process orders (WIP is no
longer calculated within a separate process step but is activated immediately with any
postings made, so that target cost calculation no longer takes place within WIP.)

March 2010 6
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

1.3. Localization
SAP ERP is localized for a serie of countries. This information can be found in SAP’s Service
Marketplace. However, CWM is only localized for a limited number of countries. Currently,
these countries are
United States
Germany
Danmark
Spain

Regarding others countries, SAP cannot guarantee the availability of country specific functio-
nality for CWM like it is available in ERP 6.0 without CWM.

1.4. Enhancement packages for ERP 6.0


ERP 6.0 is continuously improved by so-called enhancement packages. Also for the IS-CWM,
SAP will provide new functionality with some of the enhancement packages (e.g. with en-
hancement package 3)
As a baseline statement, it has to be taken into account, that new functionality ( besides new
CWM business functions) delivered by enhancement packages has never been tested within
a CWM-activated ERP system. Because of this, customers have to assume, that all new func-
tionality, shipped with enhancement packages, is part of this restrictions document.
Examples of such types of restrictions are
LORD (Lean Order interface, OSS-note 1111624)
TDMS (SAP Test Data Migration Server)
A&D Subcontracting (separate Business Function since EHP4)
If there are exceptions known from this general statement, they will be published within this
document.
Functionality within enhancement packages, which is explicitly allocated to IS-CWM (like e.g.
Activity Based GR/IR Settlement within enhancement package 3), will not be listed in this
document as an exception form this general statement.

March 2010 7
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

2. Functional Restrictions in Financials and Valua-


tion

Overall functions that are not supported in CWM

Account-based profitability Account-based profitability analysis is not supported in


analysis CWM.
Multiple account assignments Multiple account assignments are not possible in CWM for
production / process orders and subcontracting because
they would require non-valuated goods receipts, which are
not supported for those orders.
Inventory Accounting only The value flow within Inventory Accounting is based only on
uses the valuation unit of the new valuation unit of measure. All functions and
measure processes within Inventory Accounting can therefore only
use the valuation unit of measure. No conversion to the lo-
gistics unit of measure, regardless of whether actual data or
planned conversion factors is possible within Inventory Ac-
counting
Easy Cost Planning ECP is based on the template technique. The cost estimate
is stored as plan data on CO objects, for example, WBS
elements or internal orders. This function is particularly rele-
vant in engineering and construction and less relevant in the
consumer products industry.
Only the base unit of measure is supported for materials in
Easy Cost Planning. Costs are neither calculated nor dis-
played in the valuation unit of measure.
Template allocations Template allocations are not supported by Overhead Cost
Controlling (CO-OM) in combination with production orders
or process orders in Inventory Accounting for CWM.

Environments that are not supported include:


001 Material cost estimate / Manufacturing order
002 Reference and simulation costing
003 Material cost estimate w/o quantity structure
006 Gen. cost object / cost object hierarchy
008 Sales order
010 Product cost collector
111 Sales order
012 CO manufacturing order
113 CO manufacturing order
126 Sub-environment: product cost collector
Business areas and functional Material postings are not updated with the business area or
areas not updated in Invento- the functional area within Inventory Accounting.
ry Accounting For other ledgers (for example, general ledger), functional
areas are supported.
For postings that originate in Inventory Accounting, function-
al areas can be determined by substitutions or assignments
of accounts to functional areas.
Euro conversion The euro conversion tools are available in the standard SAP
ERP solution but have not been adapted to CWM. It is rec-
ommended that euro conversion is performed before the
CWM solution is implemented.
Periodic transfer of material Periodic transfer of WIP and material inventories into the

March 2010 8
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

inventory and WIP to Classic Classic Profit Center Accounting are not supported with
Profit Center Accounting. CWM. Instead online transfer of additional balance sheet
accounts can be used.
Additional lines in Profit Cen- With CWM it is not possible to post additional lines for inter-
ter Accounting for internal nal revenues, internal deliveries from other profit centers and
goods movements internal changes of inventory, although this functionality can
be used in the standard SAP ERP solution without imple-
menting transfer prices and the material ledger.
Statistical balance sheet Statistical balance sheet accounts are used, for example, in
accounts combination with the Project System, WBS elements, and
reconciliation accounts for assets. These can then be in-
cluded in the budget availability check. Statistical balance
sheet accounts are not supported in CWM, which also
means restrictions for budget checks.
Budgeting and availability Budgeting and commitments for manufacturing orders and
check for manufacturing or- process orders are not supported.
ders and process orders
Dynamic item processor The dynamic item processor cannot be used to charge ac-
tual costs of services or projects directly to sales orders. This
is especially relevant for make-to-order in the engineering or
high-tech industry.
Instead, you can charge planned costs to sales orders and
manually maintain sales prices based on the actual cost
information from the original cost object (for example wbs
elements or internal orders).
Currency types Possible currency types are:
10 Company code currency
30 Group currency
40 Hard currency
50 Index-based currency
60 Global company currency

Inventory Accounting always uses currency type 10 (compa-


ny code currency) for prices and inventories.
Currency type 20 (Controlling area currency) is not sup-
ported.
Parallel Currencies Inventory Accounting supports up to three parallel curren-
cies. These are limited to the currencies that are used in the
company code as parallel currencies and that are converted
directly from the transaction currency.
Additional currencies cannot be used in CWM, since curren-
cy valuations and revaluations can be performed in the gen-
eral ledger.
Accounting ALE scenarios ALE scenarios that transfer accounting documents and mas-
ter data have not been tested with CWM. This includes for
example the following scenarios:
Logistics <> Accounting
Central Accounting - Decentralized Logistics
Decentralized Accounting - Central Logistics
Several Accounting Systems - Several ERP
Logistics Systems
Accounting <> Accounting
Cost Center Accounting (CO-OM-CCA)
Activity-Based Costing
Profit Center Accounting (EC-PCA-TL)
Scenarios in Asset Accounting

March 2010 9
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Financial Accounting (FI-GL)


Special Purpose Ledger (FI-SL)
ALE/Distribution in Product Cost Planning
Distributed Profitability Analysis (CO-PA)

Material Valuation
The following functions within material valuation are not supported:

Company code as valuation In CWM, valuations can only be performed at plant level. In
level the standard SAP solution, the company code may be used
as the valuation level if production is not used. For produc-
tion plants the valuation level has to be on plant level either.
A workaround would be to set equal prices in all affected
plants. Then you have to ensure that price changes are ex-
ecuted accordingly for all of those plants.
Split valuation on material In CWM, split valuation is only implemented on batch level,
level not on material level.
Balance sheet valuation With CWM only the following balance sheet valuation me-
thods are supported:
FIFO
Market price analysis
Range of Coverage
Lowest value

Transfer prices Price transfers are not supported in the Material Ledger or in
Profit Center Accounting. However, depending on the busi-
ness in question, alternative, more appropriate solutions
might exist.
Valuated active ingredient Active ingredient management or product units of measures
management, valuated prod- can be used in CWM. However, valuation cannot be based
uct units of measure on active ingredient contents or product units of measures.
Instead of product units of measures for valuation the new,
more flexible valuation unit of measure can be used.
Goods receipt with net value Net posting for goods receipts is not supported in CWM, due
for purchase orders (dis- to the different logic of the MAP. At the time of goods re-
counts) ceipts, the gross value (purchase order price) is posted to
the GR/IR account. At the time of invoice verification, the net
value can be posted. With periodic reconciliation, the differ-
ence is posted to the inventory and activated.
Separate reporting of ex- CWM does not support separate reporting of currency ex-
change rate differences for change rate differences within material valuation in goods
goods movements receipts and invoice receipt.
Instead, currency differences that occur because of changes
in the exchange rate are posted to the price difference ac-
counts, together with all other price differences for materials
valuated at standard price. For materials valuated at moving
average price the differences are posted to the material and
for purchase orders items assigned to cost objects. The dif-
ferences are posted to the cost object together with differ-
ences from other origins.
Direct postings to materials CWM does not support the function for performing direct
from invoice verification postings to materials from invoice verification.
Instead, a new transaction for debit/credit a material is avail-

March 2010 10
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

able.
Inventory costing based on Inventory costing based on planned or actual quantity struc-
plan or actual quantity struc- tures (CalcType “Inventory costing”) is not supported in
tures CWM. You can use product cost estimates to update materi-
al prices and inventory prices daily instead.
Inflation Accounting for Ma- Inflation Accounting is part of the localizations for various
terial Inventory countries. While Inflation Accounting in general has been
tested and works (like for Fixed Assets) it is not supported
for Material Inventory. It is assumed that in most of the target
segments of CWM this functionality is only rarely used, be-
cause of the fast inventory turnover rate caused by the pe-
rishable nature of the goods.

Moving Average Price


CWM supports the valuation of materials either according to a Standard Price approach or to
a Moving Average Price (MAP) approach. However, the following functions within MAP are
not supported:

Stock coverage check as in These restrictions arise from the new GR/IR processing with
Material Ledger with access changes in the posting logic.
to purchase order history or With goods receipt, the inventory price (MAP) is adjusted at
order history the transactional level, valuation of goods receipt is based on
the target costs. These are:
Goods receipts for purchase - purchase order price for external procurement
orders with reference to pur- - currently valid inventory price for subcontracting.
chase order history Variances are capitalized by periodic jobs in the inventory if
the quantities are covered, but are no longer transaction-
Transaction-based inventory based.
capitalization with invoice Additionally, the purchase order history no longer contains
receipts for purchase orders values, just quantities (the values can be analyzed within the
or for subcontracting orders new GR/IR journal, but not directly within the purchase order
history).
Statistical moving average The statistical moving average price is no longer calculated
price for standard price-managed materials.
Instead, it is possible to update the standard price daily with
actual cost estimates, so that it reflects the actual costs more
accurately than with a periodic update.
External value for goods is- With the moving average price, goods issues with an exter-
sues nal value are not supported.

March 2010 11
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Product Cost Controlling


The following functions within Product Cost Controlling are not supported:

Actual costing / Material CWM does not support actual costing based on the Material
Ledger Ledger. As the standard price may be updated with cost es-
timates daily in CWM, this issue is less important here than in
the standard SAP solution.
Subsequent allocation of Activity allocations are always valuated at the planned price
actual prices and changed of the period. CWM does not support subsequent adjustment
planned prices to manufac- of actual prices or changes to planned prices and revaluation
turing orders of activity allocations for production orders and process or-
ders.
Actual costing variants are not supported in CWM.
Distribution of “usage va- The distribution of “usage variances” to production and
riances” process orders is not supported with CWM.
Activity-based costing CO business processes (activities) cannot be used for cost
assignments.

ALE scenarios for product ALE scenarios for product cost estimates are not supported
cost estimates with CWM.
Origin groups Origin groups are not supported with CWM.
Joint production: split costs In CWM splitting of costs to joint products is supported based
differently for cost elements on:
Equivalence numbers
Actual quantities
Actual quantities weighted with equivalence num-
bers.

The splitting of costs according to equivalence numbers for


cost elements is not supported. All costs are calculated with
the same logic, irrespective of the cost element equivalents
(no origin structure within the apportionment structure).
Variance analysis with va- Production variances are periodically posted during WIP
riance categories on process clearing. Separate calculation of variances and their classifi-
and production orders cation into variance categories is not supported in CWM.
Consequently, the settlement of variance categories to CO-
PA is not supported. However, the total amount of variances
is transferred to CO-PA.
Fixed / variable splitting on Actual costs on production and process orders cannot be
process and production or- separated in fixed and variable portions. Within product cost
ders planning and overhead management separate fixed and vari-
able portions of the values are supported.
WIP based on target costs Actual costs within production are posted directly to WIP,
without a further processing step in between. Since the target
quantity is not known during the posting, the WIP cannot be
calculated based on target costs. Therefore, product cost
controlling by period is not supported with CWM.
Production orders with cost Production orders can only be settled to materials accounts.
assignments other than ma- Therefore, no other account assignment can be used. In ad-
terial dition, it is not possible to use a non-valuated material as a
header material, as this would require an additional account
Rework orders assignment.
Production orders cannot be settled to other production or-

March 2010 12
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Production orders without ders. It is also not possible to use additional account assign-
header materials ments.
Product cost controlling by Instead of the standard Cost Object Controlling processes,
period CWM has now new Inventory Accounting processes. Periodic
Cost Object Controlling is not supported.
Product cost collectors Product cost collectors and cost object hierarchies are not
Cost object hierarchies supported within Inventory Accounting for CWM.
Collective orders without With CWM costs of production orders can only be settled to
automatic goods movements materials, but not to any other kind of assignment. It is also
not possible to transfer costs from one production order to
another. Therefore collective orders can only be used with
automatic goods movements so that all costs can be settled
directly to the material and respective inventory accounts.
Product cost controlling by It is not possible to assign costs to sales orders (sales order
sales order and non-valuated items with controlling objects).
sales order stock Product cost by sales order can only be used with valuated
sales-order stock. Valuation prices based on sales orders
cannot be used either. Sales order stocks of materials (as
well as make-to-stock inventory) are valuated using the in-
ventory price of the material at the plant.
Manual postings to produc- Manual postings to production and process orders are not
tion or process orders supported in CWM; this includes general ledger postings and
manual reposting of costs.
PDCE - Product Design Cost PDCE was not developed to run in combination with other
Estimate FIN-SEM applications in the same client. As Inventory Ac-
counting is also a FIN-SEM application, PDCE cannot be
activated in the same client where CWM+InvAcc are acti-
vated.
BAPIs The following BAPIs cannot be used for costing:
- Update of Prices in Material Master
(method: CostEstimate.UpdatePrice)
- Marking Standard Cost Estimate
(method: CostEstimate.Marking)
- Release of Marked Standard Cost Estimates
(method: CostEstimate.Releasing)
- Determine Organizational Measures
(method: CostEstimate.AllowMaGet)
- Grant Marking Allowance for Costing
(method: CostEstimate.AllowMark)

March 2010 13
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Account Assignments
Not all account assignments are supported in CWM. For goods movements, purchase orders
and invoice verification, it is not possible to enter or post to an invalid account assignment.
For purchase orders and goods movements the account assignment is checked using a BAdI.
Also, in invoice verification the account assignment cannot be changed to an invalid assign-
ment.
It is not possible with CWM to override the MM account determination (Customizing) by expli-
citly entering another account during Goods movement in MM (MIGO). This is because of the
design of Inventory Accounting within CWM.

Account assignments that are - Sales orders


not supported - Product cost collectors (order category 05)
- Cost objects
- CO production orders (order category 04)
- Activity types
- Business processes (CO-ABC)
- Statistical internal orders
- Public sector objects (for example, funds)
- Assets (goods movements with accounting to assets is
not supported in CWM. Instead of direct accounting to
assets internal orders or cost centers might be used,
with later posting of the costs to the asset. In the same
way, in CWM it is not possible to account purchase or-
ders directly to assets)
- Statistical account assignments for purchase orders,
goods movements, and postings to manufacturing or-
ders
- Assigned stock transport orders
- Unevaluated goods receipts with account assignment to
production orders or process orders are not supported
- Multiple account assignment for production orders,
process orders, and subcontracting is not supported

Account assignments that are - Cost centers


supported - Production orders (order category 10)
- Process orders (order category 40)
- WBS elements (projects)
- Networks (order category 20)
- Maintenance orders (order category 30)
- QM orders (order category 06)
- Internal orders (order categories 01, 02)

March 2010 14
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

3. Functional Restrictions in Logistics

Material Master
The following functions related to the Material Master are not supported:

MM17, mass maintenance of This transaction does not support the mass maintenance
material master of CWM-specific fields. CWM-specific fields are either ap-
pends of table MARA or MBEW.
Appended fields of table MARA (e.g. /CWM/TOLGR can
be added to MM17 according to SAP note 216596. As a
consequence, mass maintenance of these fields is possi-
ble with MM17.
For appended fields of table MBEW (e.g.
CON_FIN_VALLEVEL and CON_FIN_VA) the procedure
according SAP note 216596 does not work. Mass main-
tenance of these fields is NOT possible with MM17 or with
other transactions.
MM60, Materials List This transaction was not adapted to CWM. This means,
that no CWM-specific fields like PUoM are displayed by
this transaction.
Additionally, the price information in this transaction is not
valid as this transaction still displays prices from MBEW
instead of prices from InvAvv.
In order to display a material list with prices, transactions
FAIV03-05 are available
LSMW, BAPI BTCI programs as well as BAPIs and IDOCS related to
material master (RMATIND, BUS1001, etc) were not
adapted to CWM. As a consequence, LSMW does not
support the import of CWM-specific material master fields.
For assistance (e.g. existing workarounds), please contact
CWM solution management
MMAM, Change Material This transaction was not adapted to CWM. This means,
Type that CWM specifics like material valuation or parallel quan-
tities are not analyzed by that transaction. As a conse-
quence, either a material type change for cw materials is
never possible or a change might be accepted due to zero
inventories in base unit of measure although inventory in
parallel unit might be different from zero. This will cause
severe inconsistencies within Inventory Accounting.

March 2010 15
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Materials Management - Inventory


The following functions within Materials Management are not supported:

Non-valuated sales order These stock types are not supported in CWM. Therefore,
stock goods movements of inventory for these stock types are
not supported either. In addition, inventory cannot be as-
Project stock signed to PSP elements and then viewed as statistical in-
ventory.
Cross-system materials post- Cross-system material postings are not enabled within
ings CWM.
Movement type 309 Movement type 309 is adapted for CWM. It is not possible
(transfer postings from ma- to have a movement from a standard material to a CWM
terial to material) material and back.
In addition, transfer postings between materials are not
supported if one material is inventory-valuated and the
other material is not inventory-valuated
Batch level cannot be “Plant The technical way how LIME stores stock information re-
level” quires that batches are unique on material or client level
BMBC “Batch Information The “Display Selection Result for Stock” report within
Cockpit”, “Display Selection BMBC is not enabled to display quantities in PUoM.
Result for Stock” report

March 2010 16
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Materials Management – Goods Movements


The following goods movements (movement types), and their corresponding cancellations are
not supported:
131 Goods receipt for run schedule header
141 Goods receipt for subsequent adjustment for active ingre-
dient
231 Goods issue for a sales order (without shipping, with sales
order assignment)
291 Goods issue for any account assignment
309 partly Movement type 309 is adapted for CWM. It is not possible
to have a movement from a standard material to a CWM
material and back.
In addition, transfer postings between materials are not
supported if one material is inventory-valuated and the oth-
er material is not inventory-valuated
317 Creation of a structured material from constituent compo-
nents (Retail)
319 Split structured material into components (Retail)
340 Revaluation of a batch
415 Transfer posting to project stock
511 Free delivery from vendor – unrestricted-use stock
571 Goods receipt for assembly order to unrestricted-use stock
573 Goods receipt for assembly order to quality inspection
575 Goods receipt for assembly order to blocked stock
671 Returns for stock transport order via shipping
677 Returns for stock transport order in one step (shipping)
721 Sales value receipt – not affecting margins (Retail)
731 Sales value receipt – affecting margins (Retail)

MM-Transactions related to These transactions are not available in CWM.


goods movements: Transaction MIGO is designed to be used for the related
MB01 “Post goods receipt for functions instead.
PO”
MB03 “Display material doc-
ument”
MBST “ Cancel material doc-
ument”
MB1B “Transfer posting”
MB1C “Other goods receipt”
MB31 “Goods receipt for pro-
duction order”
MBRL “Return delivery for
material document”
MBSF “Release blocked
stock via mat. Doc.”

Account assignment during In CWM, goods movements in MM can only be posted with
goods movement transaction MIGO.
In CWM it is not possible to override the account-
determination within customizing by explicitly determining
another account while performing the MIGO – transaction.
This is because of the design of Inventory Accounting with-
in CWM.

March 2010 17
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Materials Management – Procurement


The following functions within Procurement are not supported:

Goods receipt with net value Net posting for goods receipts is not supported in CWM,
for purchase orders due to the different logic of the MAP. At the time of goods
(discounts) receipts, the gross value (purchase order price) is posted
to the GR/IR account. At the time of invoice verification, the
net value can be posted. With periodic reconciliation, the
difference is posted to the inventory and activated.
Calculation of (e.g. freight-) If the UoM of the (e.g. freight-) condition is not the Price-
condition value based on real UoM, the value of that condition will always be calculated
quantity specified during GR based on the planned conversion factor between the Or-
der-UoM and that condition UoM. This applies also in case
or based on real quantity the condition UoM might be equal to the Order-UoM.
specified during GI in case of Only if the condition UoM is equal to the price-UoM, its
STO (stock transfer order) value will be calculated based on the real quantity

Example: 1 EA (BUoM) = 10 KG (PUoM)


PO: 10 EA (Order-UoM) ordered with price of 1 EUR/KG
and additional freight condition 0,01 EUR/EA.
GR: 10 EA with 90KG
The value of the goods will be 1 EUR x 90KG = 90EUR
The value of the freight condition will be
0,01 EUR/EA x (90KG / ( 10KG / 1 EA)) equals
0,01 EUR/EA x 9 EA = 0,09 EUR

Batch-Input for creation of CWM does not support the ”Batch Input” technology to im-
purchase orders or creation of port these objects. Instead, standard BAPI’s for this objects
goods movements are available and the related IDocs have been enabled for
the parallel unit of measure.
Data migration and data upload and also data transfer from
external systems must be performed as part of the cus-
tomer-specific implementation project. The standard inter-
face with IDocs can be used.
Purchase Account Manage- Purchase account management (localization feature) is not
ment supported with CWM, due to the different posting logic for
GR/IR.

March 2010 18
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Production
The following functions within Production are not supported:

Repetitive Manufacturing No repetitive manufacturing function is supported in CWM.


This also applies to cost object hierarchies, product cost
collectors, product costs by periods and other functions
used in conjunction with REM (for example, material stag-
ing, confirmation of handling units for REM, packaging of
handling units for REM)
Production orders with other Production orders can only be settled to materials ac-
cost assignments than ma- counts. Therefore, no other account assignment can be
terial used. In addition, it is not possible to use a non-valuated
material as a header material, as this would require an ad-
Rework orders ditional account assignment.
Production orders cannot be settled to other production
Production orders without orders. It is also not possible to use additional account as-
header materials signments.
Make-to-order scenarios As inventory within CWM can only be valuated as ano-
nymous stock, the standard MTO-scenarios (requirement
classes) do not work. However, it is possible to set up an
own requirement class in order to realize a MTO-scenario
with sales stock valuated like anonymous inventory
Goods receipt of catch weight Goods receipt of catch weight materials can only be post-
materials from Plant Mainten- ed for production orders and process orders. It is not poss-
ance, Project System ible to produce catch weight materials with PM orders,
network orders or WBS elements.
Joint production: Joint products can be valuated with planned cost propor-
Split costs differently for cost tions split between the different joint products within one
elements production order, actual costs can be settled with relation
to the actual quantities posted. However, costs cannot be
split differently for cost elements so that all cost element
equivalents are calculated with the same logic (no origin
structure within the apportionment structure).
Joint production: Apportionment structures can be maintained in the materi-
Change of equivalence num- al master only. They cannot be maintained in the individual
bers in order production or process order. With Inventory Accounting a
functionality is provided to automatically take into accout
the goods receipt quantities for distribution of the costs to
the co-products, however.
Variance analysis with va- Production variances are posted during WIP clearing. In
riance categories CWM they are not split further into variance categories.
Consequently the settlement of variance categories to CO-
PA is not supported.
Transfer of bill of materials This function is not supported in CWM.
from PS/PM/QM/CO-OM-OPA
to production
Confirmations and activity CATS is not supported within CWM. The SAP standard
recording with CATS transactions of production or process order confirmations
can be used. These transactions are enabled for catch
weight material postings for back flushing of components
or automatic goods receipt of products.

March 2010 19
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Goods movements for pro- Goods movements for production can be executed using
duction with MB31 or MB1A MIGO or goods movements within the confirmation trans-
actions. The old transactions MB1A and MB31 are no
longer supported, as they have not been extended for
CWM.
Interfaces for third-party sys- The SAP standard interfaces have been enhanced with
tems the catch weight functions. During implementation, inter-
faces of third-party systems must also be enhanced, in or-
der to transfer the required information to SAP.

Sales & Distribution (SD)


The following functions within Sales & Distribution are not supported:
Order-related billing, except For catch weight materials, order-related billing is only
for third-party orders supported for third-party processing (with a statistical
goods receipt for processing the parallel unit of measure).
Billing is based on the delivered quantities, as the delivery
(but not the sales order) supports materials handling in two
parallel quantities.
Billing plans For catch weight materials, billing plans are not supported
in CWM.
Billing of actuals for activities Billing of actual costs for activities such as services uses
to customers (dynamic item the sales order as a cost object. This function is not availa-
processor) ble in CWM. It is possible to charge planned costs, with the
actual costs remaining on the original cost object (for ex-
ample, project system or internal order). It is also possible
to maintain the service price manually within the sales or-
der according to the actual costs, but there is no direct link
between the sales order item and cost item.
Non-valuated sales order Sales order stock can only be used with valuated invento-
stock ry. Non-valuated sales order stock is not supported in
CWM since cost object controlling for sales orders is not
enabled in Inventory Accounting for CWM. Sales order
stock is always valuated with the price of the anonymous
stock.
Billing interface to non-SAP The billing interface to non-SAP systems and the BAPI
Systems for catch-weight used for billing are not adapted for catch-weight materials
materials in CWM.
Grouped Picking in a Delivery Grouped Picking (transactions VG01,02,03) does not sup-
note port the maintenance of the Parallel Quantities.
If Grouped Picking is required for CW-materials, usage of
leanWM is recommended.
Credit Memo (requests) and C/d memo requests and all similar documents (e.g. invoice
Debit Memo (Requests) with correction requests) are not able to store quantities in a pa-
reference to previous SD rallel unit. As parallel quantities in referenced documents
documents like invoices (e.g. invoices) would be lost, copy management into c/d
memo requests does not copy cw items.
It is possible to create c/d memo requests w/o referencing
previous documents for cw items, but in that case, the cal-
culation of a net value is only supported by conversion fac-
tors of the material master.
In order to create c/d memos based on entered parallel
quantities, they have to be based either on a delivery or on
a billing document.

January 2009 20
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Restricted support of re- The requirement class is a central object within SD in order
quirement classes to control the system behavior in different areas. One of
the controlled areas is the account assignment of the items
within a sales document.
As already explained in chapter 2.5 “Account Assignments”
of this document, Inventory Accounting does not support all
account assignments which are supported by ERP Core.
As the consequence of this, CWM only supports require-
ment classes in SD which comply to the following rules:
Account Assignment Category (KNTTP) must be
“M” (indiv. Cust w/o KD-CO)
Valuation of Special Stock (KZBWS) must be
“A” (Valuation w/o reference to sales doc) or
“blank” if the Special Stock Indicator (SOBKZ) is
“blank”.
Consumption Posting (KZVBR) must be
“blank” (no consumption posting)

Because of this, the following standard Requirement


Classes are not supported by CWM:
39 Service item
MkToOrdNoValW/o
40 cons
42 Mke-ord.cons plgVar.
43 Mke-ord.cons.charPlg
45 MTO val. with cons.
46 MMTO config. value.
47 MkToOrd.-mat.variant
48 Mke->O.mat.var.cons.
60 Mke->O.Cons. plngMat
61 Mk->O. MatVar.PlgMat
75 Project w/o stock
80 Mke-to-ord./ project
85 Mk->O./project/cons.
90 Project/cons./plgMat
91 Prod.lot plan-indiv.
201 Assembly: prod.order
202 Network
202 Assembly: plnd order
203 Service order
204 Repair service
206 Process order, stat.
207 Process order, dyn.
212 Netplan/proj.settlmt
KEB Cust.- individual PO
LCO MkToStock with CO

For some of the non-supported requirement classes, a


workaround might be to create an appropriate customer-
specific requirement class, avoiding the “forbidden” set-
tings

September 2008 21
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Warehouse Management (WM)


The following functions within Warehouse Management are not supported:

Immediate confirmation of Immediate confirmation of transfer orders can only be sup-


transfer orders ported if the values in both the logistics and the valuation
unit of measure are available or can be derived from other
transactional data, for example, from the associated han-
dling units. Otherwise TO creation and TO confirmation
have to be executed separately, as the actual quantities
are not available at TO creation and must be entered dur-
ing TO confirmation.
Transfer orders for the cross- The cross-docking process is not supported within CWM.
docking process
Transactions for mobile data The RF transaction LM05 (confirmation of transport orders
entry (RF transactions) with / without handling units) has been partly enabled for
CWM. Not supported with LM05 is picking of bulk storage
types.
Other RF transactions have to be adapted on a customer-
specific basis.

Handling Unit Management (HUM)


The following functions within Warehouse Management are not supported:

HU confirmation in repeti- No repetitive manufacturing functions are supported within


tive manufacturing (transac- CWM. This also applies to functions in Handling Unit Man-
tion MFHU) agement in conjunction with repetitive manufacturing.
Packing in repetitive manu-
facturing (transaction
HUP1)
Function modules for ma- The following function modules within PP-PI for material
terial identification (PP-PI- identification (PP-PI-MIR) are deactivated:
MIR) - COMI_HU_CONSUMPTION
- COMI_MATERIAL_COMPLETE_CHECK
- COMI_MATERIAL_SEQUENCE_CHECK
Material identification is mainly used within the pharmaceuti-
cals industry and is therefore not critical for the catch weight-
solution for food.

March 2010 22
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Project System (PS)


The following functions within the Project System are not supported:

PP production orders or This function is not supported within CWM.


process orders within project
structures
Project stock Project stock is not supported as a stock type by Inventory
Accounting in CWM. As such, inventory cannot be as-
signed to WBS elements and viewed as statistical invento-
ry.
Easy Cost Planning with ECP is based on the template technology. The cost esti-
catch weight materials mate is thereby stored as plan data on CO objects, such as
WBS elements or internal orders. This function is especial-
ly relevant in engineering & construction and less relevant
in the consumer products industry.
Only the base unit of measure is supported for materials in
Easy Cost Planning. Costs are neither calculated nor dis-
played in the valuation unit of measure.
Information system of PS Reports and info structures within PS are not adjusted for
catch weight fields.

Plant Maintenance (PM)


The following functions within Plant Maintenance are not supported:

Negative quantities within the Materials cannot be planned with negative quantities within
materials planning of PM PM. In joint production, this function is covered by produc-
tion orders, in manufacturing by process orders.
Plant maintenance orders for Plant maintenance orders cannot be used to manufacture
rework of catch weight mate- or rework catch weight materials, as the screens have not
rials been enhanced with the parallel unit of measure. It is poss-
ible to use PM to rework standard materials.
Information system of PM Reports and info structures within PM have not been ad-
justed for catch weight fields.

March 2010 23
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Quality Management (QM)


The following functions within Quality Management are not supported:

Confirmation of production Confirmation of production activities can be executed di-


within results recording for rectly via the confirmation transactions for production or-
inspection lots ders or process orders. Access via results recording for in-
spection lots (transaction QE11) is not enabled within
CWM for CW-materials
Correction of Inventory va- Those corrections cannot be performed with report
riances between QM inspec- ZQEVAC20 (OSS-note 48815).
tions lots an IM They can be posted using the MM inventory counting func-
tions instead.
Inventory Transfer booking For CW-materials, it is not supported to use the transfer
out of Quality notification actions of the “Action box” within Transactions
QM01/QM02
QM Information system Only the following QM-reports are adjusted for catch
weight fields (prerequisite: existing mat. documents):
RQEEAL10, RQEVAM10, RQEVAM30
Other reports and info structures within QM are not ad-
justed for catch weight fields.

March 2010 24
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

4. Miscellaneous

Other Industry Solutions


In ERP 6.0, CWM can be activated as an industry solution with the Switch Framework. It is
not possible to activate other industry solutions once CWM has been activated. Neither is it
possible to revert from a CWM system to a standard system.

SAP Business Suite Integration


SAP APO is provided only with the base unit of measure, which in CWM also serves as the
logistics unit of measure. Inventory in APO is only managed in the base unit of measure. Val-
ues in the parallel unit of measure are derived using the planned conversion factor from ma-
terial master, with a fixed conversion ratio. Planning functions use the base unit of measure
only.
SAP CRM integration is provided with the base unit of measure and the sales unit of meas-
ure, using the planned conversion factor.
SAP SRM integration is provided with the base unit of measure and the purchasing unit of
measure, using the planned conversion factor.
Integration to SAP MDM (Master Data Management) is not supported in CWM.
Integration to EWM (Extended Warehouse Management System) is not supported in CWM.

Direct Store Delivery


Direct Store Delivery processes are not supported within CWM.

Reporting in ERP
The following ERP reports are not supported in CWM:
Financials reports Financials reports are not adapted to CWM requirements.
However, a choice of Inventory Accounting specific reports
are available.
Cost object controlling reports Reports of Cost Object Controlling within CO-PC standard
functions are not adapted to CWM and therefore do not
display actual costs. After activation of CWM, all actual
costs are posted to the new Inventory Accounting objects
and are shown in different reports instead.
MMBE Instead, there is a new report /CWM/STOCK now available
MB52-MB54 with different layout and functionality. For example, the fol-
MB58 lowing functions from MMBE are not supported by
/CWM/stock:
Display of fixed storage location
Display of batch allocations to requirements
All other inventory related No existing inventory related reports were adapted to
reports, like e.g. MC46 etc. CWM.
LIS, SIS LIS and SIS are not adapted to CWM requirements

March 2010 25
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Please pay also attention to chapter 4.6 “Overview of transactions not available with CWM”.

BAPIs, IDOCs, and BI Extractors


Enhancements for BAPIs, IDocs and BI extractors are as described in the documentation.

March 2010 26
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

Overview of transactions not available with CWM


The following table gives an overview about standard ERP 6.0 transactions, which are not
available within a CWM600 system. Some of them were replaced by other transactions, how-
ever “replaced” does not mean, that exactly the same functions are provided.

Old TC Text-EN new TC

CKME Activation of Planned Prices


CKMPRP Maintain Planned Prices
CKMPRPN Price Maintenance
CKU1 Update Material Price
CO07 Create order without a material
CORO Create Process Order w/o Material
HUP1 HU creation in production
J1A3 MM goods issue revaluation
J1A5 MM Warehouse stock report (Arg.)
J1AX Market price determination program
J1AZ MM index adjustment program
KKC1 Create Cost Object
KKC2 Change Cost Object
KKC3 Display Cost Object
KKC7 Create Product Group
KKC8 Change Product Group
KKC9 Display Product Group
KKF1 Create CO Production Order
KKF2 Change CO Production Order
KKF3 Display CO Production Order
KKF6 Create Production Cost Collector
KKF6M Create Multiple Product Cost Coll.
KKF6N Maintain Product Cost Collector
KKF7 Change Production Cost Collector
KKF8 List Production Cost Collector
KKPH Collective Entry
KKPHIE Cost Object Hierarchy
KKPK Collective Entry
KKS1 Variances - Product Cost by Lot (C)
KKS2 Variances - Product Cost by Lot (I)
KKS5 Variances - Product Cost by Per. (C)
KKS6 Variances - Product Cost by Per. (I)
MB01 Post Goods Receipt for PO MIGO
MB02 Change Material Document MIGO
MB04 Subsequ.Adj.of "Mat.Provided"Consmp.
MB05 Subseq. Adjustmt: Act.Ingredient Mat
MB0A Post Goods Receipt for PO MIGO
MB11 Goods Movement MIGO
MB1A Goods Withdrawal MIGO
MB1B Transfer Posting MIGO
MB1C Other Goods Receipts MIGO
MB26 Picking list CO27

March 2010 27
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

MB31 Goods Receipt for Production Order MIGO


MB52 List of Warehouse Stocks on Hand /CWM/STOCK
MB53 Display Plant Stock Availability /CWM/STOCK
MB54 Consignment Stocks /CWM/STOCK
MB58 Consgmt and Ret. Packag. at Customer /CWM/STOCK
MB5B Stocks for Posting Date
MB5K Stock Consistency Check
MB5L List of Stock Values: Balances
MB5M BBD/Prod. Date BMBC
MB5S Display List of GR/IR Balances
MB5U Analyze Conversion Differences
MB5W List of Stock Values
MBBM Batch Input: Post Material Document
MBBS Display valuated special stock
MBLB Stocks at Subcontractor
MBNL Subsequent Delivery f. Material Doc. MIGO
MBRL Return Delivery for Matl Document MIGO
MBSF Release Blocked Stock via Mat. Doc. MIGO
MBSL Copy Material Document
MBST Cancel Material Document MIGO
MBSU Place in Stor.for Mat.Doc: Init.Scrn MIGO
MBWO Error Correction: Subs. Value Calc.
ME21 Create Purchase Order MEPO
ME22 Change Purchase Order MEPO
ME23 Display Purchase Order MEPO
ME27 Create Stock Transport Order MEPO
MF60 Pull List
MF63 Staging Situation
MF65 Stock Transfer for Reservation
MF68 Log for Pull List
MFHU Backflushing In Repetitive Mfg
MIGO_GS Subseq. Adjust. of Material Provided
MMBE Stock Overview /CWM/STOCK
MR21 Price Change FAIV02
MR22 Material Debit/Credit
MR32 Change Material Layer (LIFO)
MR33 Display Material Layer (LIFO)
MR34 Change FIFO Data
MR35 Display FIFO Data
MR39 Display Documents (LIFO)
MRF1 Execute FIFO Valuation
MRF2 Diplay Documents (FIFO)
MRF3 FIFO Valuation: Create Doc. Extract
MRF4 FIFO: Select Materials
MRF5 FIFO: Delete Valuation Data
MRL1 Perform LIFO Valuation: Single Matl
MRL2 Perform LIFO Valuation: Pools
MRL3 LIFO Lowest Value Comparison
MRL4 Display LIFO Valuation: Single Matl
MRL5 Display LIFO Valuation: Pools
MRL6 Select Materials
MRL7 Display Pool Formation
March 2010 28
S A P C at ch W ei g h t Man ag e m en t i n E RP 6. 0: R est r i ct i on s

MRL8 Create Base Layer


MRL9 LIFO Valuation: Create Doc. Extract
MRLA Check Pool Formation
MRLB Delete Layer
MRLC Transfer Third-Party Data
MRLE Change Group Structure
MRLF Create Version as Copy
MRLG Aggregate Layer
MRLI Generate Pools
MRLK LIFO: Adjust Units of Measure
MRLL LIFO: Reassign Material Layer
MRN0 Deter. Lowest Value: Market Prices
MRN1 Deter. Lowest Value: Rge of Coverage
MRN2 Determ. Lowest Value: Mvmt Rate
MRN3 Loss-Free Valuation
MRN8 Lowest Value: Price Variances
MRN9 Balance Sheet Values by Account
MRY1 Calculate Average Receipt Price
MRY2 Transfer Physical Inventory Prices
VL01 Create Delivery VL01N
VL02 Change Outbound Delivery VL02N
VL03 Display Outbound Delivery VL03N
VL31 Create Inbound Delivery VL31N
VL32 Change Inbound Delivery VL32N
VL33 Display Inbound Delivery VL33N

March 2010 29