CWM Restrictions 604

December 2010 1

Funct ions, Res tr ic t i ons, and E xcl usion s inSAP CWM

(SAP ECC604 Industr y ExtensionCatch Weight Management)

SAP Catch Weight Management inERP 6.04: Restrictions

S A P C a t c h W e i g h t M a n a g e m e n t i n E R P 6 . 0 4 : R e s t r i c t i o n s

October 2010 2

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corpora-tion.

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 theUnited 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World WideWeb 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 technol-ogy 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 andservices mentioned herein as well as their respective logos are trademarks or registered trade-marks of SAP AG in Germany and in several other countries all over the world. All other productand service names mentioned are the trademarks of their respective companies. Data con-tained in this document serves informational purposes only. National product specifications mayvary.

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


October 2010 3

History of Changes

The following table provides an overview of the most important changes that were made in thelatest versions.

Restriction List Version Important Changes

1.00 (October 2008)

1.10 (October 2010) New chapter 4 of released restrictions


October 2010 4

1. INTRODUCTION ....................................................................................... 6

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

1.2. Impact of enhancement package 4 (and higher) ....................................................................... 6

1.3. Background of existing restrictions .......................................................................................... 6

1.4. Localization ............................................................................................................................... 8

1.5. Enhancement packages for ERP 6.0 ......................................................................................... 8

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

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

Material Valuation ............................................................................................................................. 11

Moving Average Price ........................................................................................................................ 12

Product Cost Controlling ................................................................................................................... 13

Account Assignments.......................................................................................................................... 15

3. FUNCTIONAL RESTRICTIONS IN LOGISTICS ..................................... 16

3.1 Material Master ...................................................................................................................... 16

3.2 Materials Management - Inventory ........................................................................................ 17

3.3 Materials Management – Goods Movements ......................................................................... 18

3.4 Materials Management – Procurement .................................................................................. 20

3.5 Production ............................................................................................................................... 21

3.6 Sales & Distribution (SD) ........................................................................................................ 23

3.7 Warehouse Management (WM) .............................................................................................. 25

3.8 Handling Unit Management (HUM) ....................................................................................... 25

3.9 Project System (PS) ................................................................................................................. 26

3.10 Plant Maintenance (PM) ......................................................................................................... 26

3.11 Quality Management (QM) ..................................................................................................... 27

4. RELEASED RESTRICTIONS ................................................................. 28


October 2010 5

5. MISCELLANEOUS ................................................................................. 29

5.2 Other Industry Solutions ........................................................................................................ 29

5.3 SAP Business Suite Integration ............................................................................................... 29

5.4 Direct Store Delivery ............................................................................................................... 29

5.5 Reporting in ERP .................................................................................................................... 29

5.6 BAPIs, IDOCs, and BI Extractors .......................................................................................... 30

5.7 Overview of transactions not available with CWM ................................................................ 31


October 2010 6

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 thestandard solution SAP ERP 6.0 which are no longer available after activating CWM 6.0. Most ofthese functions are rarely used by customers and often also unknown to consultants.

This restrictions document is complementary 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 thisrestrictions document. Please be aware, that also prerequisites described in the documentationmight be interpreted as restrictions in the usage of ERP 6.0 when CWM is activated.

SAP recommends not making any decisions just on reading this document. SAP offers a 2 daysworkshop in order to explain and discuss CWM features and restrictions. The experienceproves, that most restrictions are either not relevant or might be bridged by alternative ap-proaches. Please contact your local SAP sales organization in order to get more informationabout this workshop.

1.2. Impact of enhancement package 4 (and higher)

With enhancement package 4 for ERP6.0, the architecture of SAP CWM has been changed.This new architecture has impact on the restrictions caused by CWM. In order to facilitate thereading of the restrictions document as well as the maintenance, it was decided to separate therestrictions document as of EHP4. In this current version, you’ll find information about restric-tions as of EHP4.

If you don’t have activated the EHP4 Business Function of CWM, please refer to the restrictionsdocument which covers CWM based on the old architecture (SAP ERP6.0 incl. EHP3). Also ifyou have imported EHP4 or higher and you don’t have activated the CWM Business Function ofEHP4 or higher, the restrictions document of the old architecture remains relevant for you.

1.3. Background of existing restrictions

Within the industry solution CWM, a new concept of units of measurements for materials is in-troduced. This concept enables one unit of measure suitable for logistics and another unit ofmeasure suitable for financials and controlling to be used within the same material. Additionally,the relationship between both units of measure can be variable. Quantities for goods move-ments therefore have to be recorded in both units of measures in parallel with additional toler-ance checks if required.

As a result restrictions do exist compared with the SAP ERP standard system.

From a high level perspective, 2 major reasons for existing restrictions can be identified:

1. With the old architecture (see chapter 1.2.), special components were in place (LIMEand Inventory Accounting). Those 2 components had been responsible for a number ofrestrictions. With the new architecture, it might be assumed that a series of those re-strictions are no longer present. However, in order to delete such restrictions from thisdocument testing and approval of SAP development is a mandatory prerequisite. SAPis striving to test all restrictions in this category as quickly as possible.If you as a customer or partner or SAP consultant want to support this process,please send your experiences with restrictions to Solution Management for CWM.


October 2010 7

2. Another category of restrictions are those which are not impacted by the architecturalchange but are caused by the CWM data and process model. It cannot be expectedthat such type of restrictions can be deleted from this document on short or medium no-tice.

In order to make the above mentioned categories more transparent for you, we have indicatedfor each restriction in this document whether it belongs to category 1 or 2.

Most functional restrictions are valid for the entire Industry Extension CWM, irrespective of thetypes of materials which are used. In case that a restriction is only relevant for a catch weightmaterial (cw material) this is explained explicitly.

It has been a major objective of SAP that CWM supports all the main ERP processes and thosethat are important for the Consumer Products Industry. However, it might happen you expe-rience situations where CWM does not support some other ERP standard functions or Enter-prise Extensions provided by enhancement packages, although this might not be detailed in theCWM documentation or listed as a restriction.

In general, functionality you intend to use in your Business Suite implementation must be testedbefore the decision on its usage is made. The CWM scenario provided by Solution ManagerContent can be seen as an example of a typical business process flow; all of the functions with-in this scenario have been tested by SAP.

CWM can only be activated and used in the industry version of SAP ERP. Within an SAP ERPsystem which is (e.g.) used as a Retail-system, CWM cannot be used.

Additionally, also specific functions of the ERP Retail system which are available within an SAPERP Industry system (e.g. updating the purchase order price conditions based on the goodsreceipt related to the purchase order) are not implemented in CWM.

Some examples of functions not supported by CWM are:

Cross-docking in warehouse management

Confirmation of production within results recording for inspection lots

Some business processes are implemented differently in CWM (compared with standard SAP),as otherwise data inconsistencies would have resulted. Some process steps are therefore notsupported with CWM. Please see the following example:

Billing with reference to sales orders without deliveries (within CWM, parallel quantitiesare not recorded within the sales order but rather in the delivery and the goods move-ments for the delivery.Except for third-party orders, billing is therefore only possible with reference to the deli-very.)However, billing with reference to sales order is possible for non-Catch Weight mate-rials


October 2010 8

1.4. Localization

SAP ERP is localized for a series of countries. This information can be found in SAP’s ServiceMarketplace. However, CWM is only localized for a limited number of countries. Currently, thesecountries are

United States

Germany

Denmark

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.5. 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 newCWM business functions) delivered by enhancement packages has never been tested within aCWM-activated ERP system. Because of this, customers have to assume, that all new functio-nality, 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 thisdocument.

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 doc-ument as an exception form this general statement.


October 2010 9

2. Functional Restrictions in Financials and Valuation

Overall functions that are not supported in CWM

Restriction name Category (see 1.3.)

Explanations

Account-based prof-itability analysis

1 Account-based profitability analysis is not supported inCWM.

Multiple accountassignments

1 Multiple account assignments are not possible in CWMfor production / process orders and subcontracting be-cause they would require non-valuated goods receipts,which are not supported for those orders.

Released with SAP Note 1415986 / Support PackageSAPK-60406INISCWM

Inventory valuationonly uses the valua-tion unit of measure

2 The value flow for inventory valuation is based only onthe new valuation unit of measure. All functions andprocesses within inventory valuation can therefore onlyuse the valuation unit of measure.

Easy Cost Planning 2 ECP is based on the template technique. The cost esti-mate is stored as plan data on CO objects, for example,WBS elements or internal orders. This function is partic-ularly relevant in engineering and construction and lessrelevant in the consumer products industry.Only the base unit of measure is supported for materialsin Easy Cost Planning. Costs are neither calculated nordisplayed in the valuation unit of measure.

Template allocations 1 Template allocations are not supported by OverheadCost Controlling (CO-OM) in combination with produc-tion orders or process orders.Environments that are not supported include:001 Material cost estimate / Manufacturing order002 Reference and simulation costing003 Material cost estimate w/o quantity structure006 Gen. cost object / cost object hierarchy008 Sales order010 Product cost collector111 Sales order012 CO manufacturing order113 CO manufacturing order126 Sub-environment: product cost collector

Business areas andfunctional areas arenot updated

1 Postings to material accounts are not updated with thebusiness area or the functional area.For other ledgers (for example, general ledger), func-tional areas are supported.

Euro conversion 1 The Euro conversion tools are available in the standardSAP ERP solution but have not been adapted to CWM.It is recommended that Euro conversion is performedbefore the CWM solution is implemented.

Periodic transfer ofmaterial inventoryand WIP to ClassicProfit Center Ac-counting.

1 Periodic transfer of WIP and material inventories into theClassic Profit Center Accounting are not supported withCWM. Instead online transfer of additional balance sheetaccounts can be used.


October 2010 10

Additional lines inProfit Center Ac-counting for internalgoods movements

1 With CWM it is not possible to post additional lines forinternal revenues, internal deliveries from other profitcenters and internal changes of inventory, although thisfunctionality can be used in the standard SAP ERP solu-tion without implementing transfer prices and the materi-al ledger.

Statistical balancesheet accounts

1 Statistical balance sheet accounts are used for examplein combination with the Project System, WBS elements,and reconciliation accounts for assets. These can thenbe included in the budget availability check. Statisticalbalance sheet accounts are not supported in CWM,which also means restrictions for budget checks.

Budgeting andavailability check formanufacturing or-ders and processorders

1 Budgeting and commitments for manufacturing ordersand process orders are not supported.

Dynamic item pro-cessor

1 The dynamic item processor cannot be used to chargeactual costs of services or projects directly to sales or-ders. This is especially relevant for make-to-order in theengineering or high-tech industry.Instead, you can charge planned costs to sales ordersand manually maintain sales prices based on the actualcost information from the original cost object (for exam-ple WBS elements or internal orders).

Accounting ALEscenarios

1 ALE scenarios that transfer accounting documents andmaster data have not been tested with CWM. This in-cludes 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 Financial Accounting (FI-GL) Special Purpose Ledger (FI-SL) ALE/Distribution in Product Cost Planning Distributed Profitability Analysis (CO-PA)


October 2010 11

Material Valuation

The following functions within material valuation are not supported:


Explanations

Company code asvaluation level

1 In CWM, valuations can only be performed at plant level.In the standard SAP solution, the company code may beused as the valuation level if production is not used. Forproduction plants the valuation level has to be on plantlevel either.A workaround would be to set equal prices in all affectedplants. Then you have to ensure that price changes areexecuted accordingly for all of those plants.

Split valuation onmaterial level

1 In CWM, split valuation is only implemented on batchlevel, not on material level.


Balance sheet val-uation (FIFO)

1 With CWM balance sheet valuation (FIFO) is not sup-ported

Released without any specific SAP Notes or SupportPackages

Balance sheet val-uation (LIFO)

1 With CWM balance sheet valuation (LIFO) is not sup-ported

Transfer prices 1 Transfer prices are not supported in the Material Ledgeror in Profit Center Accounting. However, depending onthe business in question, alternative, more appropriatesolutions might exist.


Valuated active in-gredient manage-ment, valuatedproduct units ofmeasure

1 Active ingredient management or product units of meas-ures can be used in CWM. However, valuation cannot bebased on active ingredient contents or product units ofmeasures. Instead of product units of measures for valu-ation the new, more flexible valuation unit of measurecan be used.

Goods receipt withnet value for pur-chase orders (dis-counts)

1 Net posting for goods receipts is not supported in CWM.

Separate reportingof exchange ratedifferences forgoods movements

1 CWM does not support separate reporting of currencyexchange rate differences within material valuation ingoods receipts and invoice receipt.

Direct postings tomaterials from in-voice verification

1 CWM does not support the function for performing directpostings to materials from invoice verification.Instead, transaction MR22 for debit/credit a material isavailable.

Inventory costingbased on plan oractual quantity struc-tures

1 Inventory costing based on planned or actual quantitystructures (CalcType “Inventory costing”) is not sup-ported in CWM.

Inflation Accountingfor Material Invento-ry

1 Inflation Accounting is part of the localizations for variouscountries. While Inflation Accounting in general has beentested and works (like for Fixed Assets) it is not


October 2010 12

supported for Material Inventory. It is assumed that inmost of the target segments of CWM this functionality isonly rarely used, because of the fast inventory turnoverrate caused by the perishable nature of the goods.

Moving Average Price

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

Restriction name Category (see1.3.)

Explanations

Statistical movingaverage price

1 The statistical moving average price is displayed for stan-dard price-managed materials, but it is not guaranteedthat it is calculated correctly.

External value forgoods issues

1 Released with SAP Note 1408730 / Support PackageSAPK-60406INISCWM


October 2010 13

Product Cost Controlling

The following functions within Product Cost Controlling are not supported:


Explanations

Subsequent alloca-tion of actual pricesand changedplanned prices tomanufacturing or-ders

1 Activity allocations are always valuated at the plannedprice of the period. CWM does not support subsequentadjustment of actual prices or changes to planned pricesand revaluation of activity allocations for production ordersand process orders.Actual valuation variants are not supported in CWM.

Distribution of“usage variances”

1 The distribution of “usage variances” to production andprocess orders is not supported with CWM.

Activity-based cost-ing

1 CO business processes (activities) cannot be used forcost assignments.

ALE scenarios forproduct cost esti-mates

2 ALE scenarios for product cost estimates are not sup-ported with CWM.

Origin groups 1 Origin groups are not supported with CWM.Joint production: splitcosts differently forcost elements

1 The splitting of costs according to equivalence numbersfor cost elements is not supported. All costs are calculatedwith the same logic, irrespective of the cost element equi-valents (no origin structure within the apportionment struc-ture). Released with SAP Note 1414566 and 1533484 /Support Package SAPK-60409INISCWM

Target cost calcula-tion and varianceanalysis

1 Currently it is not ensured that target cost calculation andvariance analysis are calculated correctly.


Fixed / variable split-ting on process andproduction orders

1 Actual costs on production and process orders cannot beseparated in fixed and variable portions. Within productcost planning and overhead management separate fixedand variable portions of the values are supported.


WIP based on targetcosts

1

Production orderswith cost assign-ments other thanmaterial

Rework orders

Production orderswithout header mate-rials

1 Production orders can only be settled to materials ac-counts. Therefore, no other account assignment can beused. In addition, it is not possible to use a non-valuatedmaterial as a header material, as this would require anadditional account assignment.Production orders cannot be settled to other productionorders. It is also not possible to use additional accountassignments.

Released with SAP Notes 1414566 and 1396599 /Support Package SAPK-60406INISCWM

Product cost control-ling by period

1

Product cost collec-torsCost object hierar-chies

1 Product cost collectors and cost object hierarchies are notsupported within CWM.


October 2010 14

Collective orderswithout automaticgoods movements

1 With CWM costs of production orders can only be settledto materials, but not to any other kind of assignment. It isalso not possible to transfer costs from one productionorder to another. Therefore collective orders can only beused with automatic goods movements so that all costscan be settled directly to the material and respective in-ventory accounts.


Product cost control-ling by sales orderand non-valuatedsales order stock

1 It is not possible to assign costs to sales orders (salesorder items with controlling objects).Product cost by sales order can only be used with va-luated sales-order stock. Valuation prices based on salesorders cannot be used either. Sales order stocks of mate-rials (as well as make-to-stock inventory) are valuatedusing the inventory price of the material at the plant.


Manual postings toproduction orprocess orders

1 Manual postings to production and process orders are notsupported in CWM; this includes general ledger postingsand manual reposting of costs.


PDCE - ProductDesign Cost Esti-mate

1 PDCE cannot be activated in combination with CWM.

BAPIs 1 The following BAPIs cannot be used for costing:

- Update of Prices in Material Master(method: CostEstimate.UpdatePrice)

Released without any specific SAP Notes orSupport Packages

- 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)


October 2010 15

Account Assignments

Not all account assignments are supported in CWM. For goods movements, purchase ordersand invoice verification, it is not possible to enter or post to an invalid account assignment. Forpurchase 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 assignment.

It is not possible with CWM to override the MM account determination (Customizing) by explicit-ly entering another account during Goods movement in MM (MIGO).


Explanations

Account assign-ments that are notsupported

1 - Sales orders- 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 account-ing to assets internal orders or cost centers might beused, with later posting of the costs to the asset. Inthe same way, in CWM it is not possible to accountpurchase orders directly to assets)

- Statistical account assignments for purchase orders,goods movements, and postings to manufacturingorders

- Assigned stock transport orders- Unevaluated goods receipts with account assign-

ment to production orders or process orders are notsupported

- Multiple account assignment for production orders,process orders, and subcontracting is not supported

Account assign-ments that aresupported

1 - Cost centers- 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)

October 2010 16

3. Functional Restrictions in Logistics

3.1 Material Master

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


Explanations

MM60, Materials List 2 This transaction was not adapted to CWM. This means,that no CWM-specific fields like PUoM are displayed bythis transaction.

MMAM, ChangeMaterial Type

1 This transaction was not adapted to CWM. This means,that CWM specifics like material valuation or parallelquantities are not analyzed by that transaction. As aconsequence, either a material type change for cw ma-terials is never possible or a change might be accepteddue to zero inventories in base unit of measure althoughinventory in parallel unit might be different from zero.


October 2010 17

3.2 Materials Management - Inventory

The following functions within Materials Management are not supported:


Explanations

Non-valuated salesorder stock

Project stock

1 These stock types are not supported in CWM. There-fore, goods movements of inventory for these stocktypes are not supported either. In addition, inventorycannot be assigned to PSP elements and then viewedas statistical inventory.


Cross-system mate-rials postings

1 Cross-system material postings are not enabled withinCWM.

Movement type 309(transfer postingsfrom material to ma-terial)

2 Movement type 309 is adapted for CWM. It is not possi-ble to have a movement from a standard material to aCWM material and back. (This is how the system be-haves for product quantity management.)

Batch level cannotbe “Plant level”

1

BMBC “Batch Infor-mation Cockpit”,“Display SelectionResult for Stock”report

2 The “Display Selection Result for Stock” report withinBMBC is not enabled to display quantities in PUoM.


October 2010 18

3.3 Materials Management – Goods Movements

The following goods movements (movement types), and their corresponding cancellations arenot supported:

Restrictionname

Category (see 1.3.)

Explanations

131 1 Goods receipt for run schedule header141 1 Goods receipt for subsequent adjustment for active in-

gredient231 1 Goods issue for a sales order (without shipping, with

sales order assignment)291 1 Goods issue for any account assignment309 partly 2 Transfer posting material to material is not supported for

CW-materials into non-cw materials and vice versa317 2 Creation of a structured material from constituent com-

ponents (Retail)319 2 Split structured material into components (Retail)340 1 Revaluation of a batch


415 1 Transfer posting to project stock Released with SAP Note 1414566 / Support Package

SAPK-60406INISCWM511 1 Free delivery from vendor – unrestricted-use stock


571 1 Goods receipt for assembly order to unrestricted-usestock

573 1 Goods receipt for assembly order to quality inspection575 1 Goods receipt for assembly order to blocked stock671 1 Returns for stock transport order via shipping677 1 Returns for stock transport order in one step (shipping)721 2 Sales value receipt – not affecting margins (Retail)731 2 Sales value receipt – affecting margins (Retail)

Restriction name Cate-gory (see1.3.)

Explanations

MM-Transactions related to goods movements:MB01 “Post goods receipt for PO”MB03 “Display material document”MBST “ Cancel material document”MB1B “Transfer posting”MB1C “Other goods receipt”MB31 “Goods receipt for production order”MBRL “Return delivery for material document”MBSF “Release blocked stock via mat. Doc.”

2 These transactions are notavailable in CWM.Transaction MIGO is de-signed to be used for the re-lated functions instead.


October 2010 19

Restrictionname

Category (see 1.3.)

Explanations

Account assign-ment duringgoods movement

1 In CWM, goods movements in MM can only be postedwith transaction MIGO.In CWM it is not possible to override the account-determination within customizing by explicitly determin-ing another account while performing the MIGO – trans-action.


October 2010 20

3.4 Materials Management – Procurement

The following functions within Procurement are not supported:


Explanations

Goods receipt withnet value for pur-chase orders(discounts)

1 Net posting for goods receipts is not supported in CWM,

Calculation of (e.g.freight-) conditionvalue based on realquantity specifiedduring GR

or based on realquantity specifiedduring GI in case ofSTO (stock transferorder)

2 If the UoM of the (e.g. freight-) condition is not the Price-UoM, the value of that condition will always be calcu-lated based on the planned conversion factor betweenthe Order-UoM and that condition UoM. This applies al-so in case the condition UoM might be equal to the Or-der-UoM.Only if the condition UoM is equal to the price-UoM, itsvalue 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/KGand additional freight condition 0,01 EUR/EA.GR: 10 EA with 90KGThe value of the goods will be 1 EUR x 90KG = 90EURThe value of the freight condition will be0,01 EUR/EA x (90KG / ( 10KG / 1 EA)) equals0,01 EUR/EA x 9 EA = 0,09 EUR

Batch-Input for crea-tion of purchaseorders or creation ofgoods movements

2 CWM does not support the ”Batch Input” technology toimport these objects. Instead, standard BAPIs for thisobjects are available and the related IDocs have beenenabled for the parallel unit of measure.Data migration and data upload and also data transferfrom external systems must be performed as part of thecustomer-specific implementation project. The standardinterface with IDocs can be used.

Purchase AccountManagement

1 Purchase account management (localization feature) isnot supported with CWM.


October 2010 21

3.5 Production

The following functions within Production are not supported:


Explanations

Repetitive Manufac-turing

1 No repetitive manufacturing function is supported inCWM. This also applies to cost object hierarchies, prod-uct cost collectors, product costs by periods and otherfunctions used in conjunction with REM (for example,material staging, confirmation of handling units for REM,packaging of handling units for REM)

Production orderswith other cost as-signments than ma-terial

Rework orders

Production orderswithout header mate-rials

1 Production orders can only be settled to materials ac-counts. Therefore, no other account assignment can beused. In addition, it is not possible to use a non-valuatedmaterial as a header material, as this would require anadditional account assignment.Production orders cannot be settled to other productionorders. It is also not possible to use additional accountassignments.

Released with SAP Notes 1414566 and 1396599 /Support Package SAPK-60406INISCWM

Make-to-order sce-narios

1 As inventory within CWM can only be valuated as ano-nymous stock, the standard MTO-scenarios (require-ment classes) do not work. However, it is possible to setup an own requirement class in order to realize a MTO-scenario with sales stock valuated like anonymous in-ventory


Goods receipt of cwmaterials from PlantMaintenance, ProjectSystem

2 Goods receipt of catch weight materials can only beposted for production orders and process orders. It isnot possible to produce catch weight materials with PMorders, network orders or WBS elements.

Joint production: splitcosts differently forcost elements

1 The splitting of costs according to equivalence numbersfor cost elements is not supported. All costs are calcu-lated with the same logic, irrespective of the cost ele-ment equivalents (no origin structure within the appor-tionment structure).

Released with SAP Note 1414566 and 1533484 /Support Package SAPK-60409INISCWM

Target cost calcula-tion and varianceanalysis

1 Currently it is not ensured that target cost calculationand variance analysis are calculated correctly.


Transfer of bill ofmaterials fromPS/PM/QM/CO-OM-OPA to production

1 This function is not supported in CWM.

Confirmations andactivity recordingwith CATS

1 CATS is not supported within CWM. The SAP standardtransactions of production or process order confirma-tions can be used. These transactions are enabled forcatch weight material postings for back flushing of com-ponents or automatic goods receipt of products.


October 2010 22


Explanations

Goods movementsfor production withMB31 or MB1A

2 Goods movements for production can be executed us-ing MIGO or goods movements within the confirmationtransactions. The old transactions MB1A and MB31 areno longer supported, as they have not been extendedfor CWM.

Interfaces for third-party systems

2 The SAP standard interfaces have been enhanced withthe catch weight functions. During implementation, inter-faces of third-party systems must also be enhanced, inorder to transfer the required information to SAP.


October 2010 23

3.6 Sales & Distribution (SD)

The following functions within Sales & Distribution are not supported:


Explanations

Order-related billing,except for third-partyorders

2 For catch weight materials, order-related billing is onlysupported for third-party processing (with a statisticalgoods receipt for processing the parallel unit of meas-ure). Billing is based on the delivered quantities, as thedelivery (but not the sales order) supports materialshandling in two parallel quantities.

Billing plans 2 For catch weight materials, billing plans are not sup-ported in CWM.

Billing of actuals foractivities to custom-ers (dynamic itemprocessor)

1 Billing of actual costs for activities such as services usesthe sales order as a cost object. This function is notavailable in CWM. It is possible to charge plannedcosts, with the actual costs remaining on the originalcost object (for example, project system or internal or-der). It is also possible to maintain the service price ma-nually within the sales order according to the actualcosts, but there is no direct link between the sales orderitem and cost item.

Non-valuated salesorder stock

1 Sales order stock can only be used with valuated inven-tory. Non-valuated sales order stock is not supported inCWM. Sales order stock is always valuated with theprice of the anonymous stock.


Billing interface tonon-SAP Systemsfor catch-weightmaterials

2 The billing interface to non-SAP systems and the BAPIused for billing are not adapted for catch-weight mate-rials in CWM.

Grouped Picking in aDelivery note

2 Grouped Picking (transactions VG01,02,03) does notsupport the maintenance of the Parallel Quantities.If Grouped Picking is required for CW-materials, usageof leanWM is recommended.

Credit Memo (re-quests) and DebitMemo (Requests)with reference toprevious SD docu-ments like invoices

2 C/d memo requests and all similar documents (e.g. in-voice correction requests) are not able to store quanti-ties in a parallel unit. As parallel quantities in referenceddocuments (e.g. invoices) would be lost, copy manage-ment into c/d memo requests does not copy cw items.It is possible to create c/d memo requests w/o referenc-ing previous documents for cw items, but in that case,the calculation of a net value is only supported by con-version factors of the material master.In order to create c/d memos based on entered parallelquantities, they have to be based either on a delivery oron a billing document.

Output type SPED 2 For stock transfers with deliveries the output type SPED(creation of Inbound Delivery out of the Outbound Deli-very) cannot be used with cw materials


October 2010 24


Explanations

Restricted supportof requirementclasses

1 The requirement class is a central object within SD in orderto control the system behavior in different areas. One of thecontrolled areas is the account assignment of the itemswithin a sales document.As already explained in chapter 2.5 “Account Assignments”of this document, Inventory Accounting does not support allaccount 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)

The following standard Requirement Classes are not sup-ported by CWM:

39 Service item

40MkToOrdNoValW/ocons

42 Mke-ord.cons plgVar.43 Mke-ord.cons.charPlg45 MTO val. with cons.46 MMTO config. value.47 MkToOrd.-mat.variant48 Mke->O.mat.var.cons.60 Mke->O.Cons. plngMat61 Mk->O. MatVar.PlgMat75 Project w/o stock80 Mke-to-ord./ project85 Mk->O./project/cons.90 Project/cons./plgMat91 Prod.lot plan-indiv.

201 Assembly: prod.order202 Network202 Assembly: plnd order203 Service order204 Repair service206 Process order, stat.207 Process order, dyn.212 Netplan/proj.settlmt

KEB Cust.- individual POLCO MkToStock with CO

For some of the non-supported requirement classes, aworkaround might be to create an appropriate customer-specific requirement class, avoiding the “forbidden” settings


October 2010 25

3.7 Warehouse Management (WM)

The following functions within Warehouse Management are not supported:


Explanations

Immediate confirma-tion of transfer or-ders

2 Immediate confirmation of transfer orders can only besupported if the values in both the logistics and the val-uation unit of measure are available or can be derivedfrom other transactional data, for example, from the as-sociated handling units. Otherwise TO creation and TOconfirmation have to be executed separately, as the ac-tual quantities are not available at TO creation and mustbe entered during TO confirmation.

Transfer orders forthe cross-dockingprocess

2 The cross-docking process is not supported withinCWM.

Transactions formobile data entry(RF transactions)

2 The RF transaction LM05 (confirmation of transport or-ders with / without handling units) has been partlyenabled for CWM. Not supported with LM05 is picking ofbulk storage types.Other RF transactions have to be adapted on a custom-er-specific basis.

3.8 Handling Unit Management (HUM)

The following functions within Warehouse Management are not supported:

Restrictionname

Category (see 1.3.)

Explanations

HU confirmationin repetitive man-ufacturing (trans-action MFHU)Packing in repeti-tive manufactur-ing (transactionHUP1)

1 No repetitive manufacturing functions are supportedwithin CWM. This also applies to functions in HandlingUnit Management in conjunction with repetitive manu-facturing.

Function modulesfor material identi-fication (PP-PI-MIR)

2 The following function modules within PP-PI for materialidentification (PP-PI-MIR) are deactivated:- COMI_HU_CONSUMPTION

- COMI_MATERIAL_COMPLETE_CHECK

- COMI_MATERIAL_SEQUENCE_CHECK

Material identification is mainly used within the pharma-ceuticals industry and is therefore not critical for thecatch weight-solution for food.


October 2010 26

3.9 Project System (PS)

The following functions within the Project System are not supported:


Explanations

PP production ordersor process orderswithin project struc-tures

1 This function is not supported within CWM.

Project stock 1 Project stock is not supported as a stock type by Inven-tory Accounting in CWM. As such, inventory cannot beassigned to WBS elements and viewed as statistical in-ventory.


Easy Cost Planningwith catch weightmaterials

2 ECP is based on the template technology. The cost es-timate is thereby stored as plan data on CO objects,such as WBS elements or internal orders. This functionis especially relevant in engineering & construction andless relevant in the consumer products industry.Only the base unit of measure is supported for materialsin Easy Cost Planning. Costs are neither calculated nordisplayed in the valuation unit of measure.

Information systemof PS

2 Reports and info structures within PS are not adjustedfor catch weight fields.

3.10 Plant Maintenance (PM)

The following functions within Plant Maintenance are not supported:


Explanations

Negative quantitieswithin the materialsplanning of PM

2 Materials cannot be planned with negative quantitieswithin PM. In joint production, this function is covered byproduction orders, in manufacturing by process orders.

Plant maintenanceorders for rework ofcatch weight mate-rials

2 Plant maintenance orders cannot be used to manufac-ture or rework catch weight materials, as the screenshave not been enhanced with the parallel unit of meas-ure. It is possible to use PM to rework standard mate-rials.

Information systemof PM

2 Reports and info structures within PM have not been ad-justed for catch weight fields.


October 2010 27

3.11 Quality Management (QM)

The following functions within Quality Management are not supported:


Explanations

Confirmation of pro-duction within resultsrecording for inspec-tion lots

2 Confirmation of production activities can be executeddirectly via the confirmation transactions for productionorders or process orders. Access via results recordingfor inspection lots (transaction QE11) is not enabledwithin CWM for CW-materials

Correction of Inven-tory variances be-tween QM inspec-tions lots an IM

2 Those corrections cannot be performed with reportZQEVAC20 (OSS-note 48815).They can be posted using the MM inventory countingfunctions instead.

Inventory Transferbooking out of Quali-ty notification

2 For CW-materials, it is not supported to use the transferactions of the “Action box” within TransactionsQM01/QM02

QM Information sys-tem

2 Only the following QM-reports are adjusted for catchweight fields (prerequisite: existing mat. documents):RQEEAL10, RQEVAM10, RQEVAM30Other reports and info structures within QM are not ad-justed for catch weight fields.


October 2010 28

4. Released RestrictionsWith Support Package SAPK-60406INISCWM (exceptions are stated below) several CWMrestrictions have been released. If your system is not at this SP-level yet, please find belowrelevant SAP Notes. They are valid for ERP 6.0 with Enhancement Package 4.

Restriction Category (see 1.3.) SAP Note

Target cost calculation and variance analysis 1 1414566Project Stock 1 1414566Non-valuated sales order stock (MTO) 1 1414566Transfer posting to project stock (Mvt415) 1 1414566Revaluation of a batch 1 1414566Free delivery from vendor – unrestricted-use stock (Mvt511) 1 1414566Restricted support of requirement classes (incl. MTO) 1 1414566Make-to-order scenarios 1 1414566Joint production: split costs differently for cost elements 1 1414566Rework orders 1 1414566Collective orders without automatic goods movements 1 1414566Product cost controlling by sales order and non-valuatedsales order stock

1 1414566

Production orders without header material 1 1396599Production orders with cost assignments other than material 1 1396599Rework orders 1 1396599Create Order w/o material 1 1396599Transaction CORO and CO07 1 1396599

Multiple account assignments (except BF MAA) 1 1415986

Split valuation on material level 1 1416125

Transaction KKF2 and KKF3 1 1397012

External values for goods issues 1 1408730

Released with Support Package SAPK-60409INISCWM:Maintenance of origin structures in joint production

1 1533484

Further restrictions that have been released without anyspecific SAP Notes or Support Packages:

- Transfer prices- BAPl Update of Prices in Material Master (method:

CostEstimate.UpdatePrice)- Manual postings to production and process orders- Origin groups- Fixed / variable splitting on process and production

orders- CWM balance sheet valuation (FIFO)

1 –


October 2010 29

5. Miscellaneous

5.2 Other Industry Solutions

In ERP 6.0, CWM can be activated as an Industry Extension with the Switch Framework. It isnot possible to activate other Industry Extensions once CWM has been activated. Neither is itpossible to revert from a CWM system to a standard system.

5.3 SAP Business Suite Integration

SAP APO is provided only with the base unit of measure, which in CWM also serves as thelogistics 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 measureonly.

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 ofmeasure, 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.

5.4 Direct Store Delivery

Direct Store Delivery processes are not supported within CWM.

5.5 Reporting in ERP


Explanations

Financials reports 1 Financials reports are not adapted to CWM as theyshould not be affected. Please, contact Solution Man-agement in case you believe a report requires adapta-tion.

Cost object control-ling reports

1 Reports of Cost Object Controlling within CO-PC stan-dard functions are not adapted to CWM. They display ingeneral only the valuation quantity in valuation unit ofmeasure (VUoM) and the corresponding values.

All other inventoryrelated reports, e.g.MB56 etc.

2 In general inventory related reports which are not expli-citly mentioned in the CWM documentation (e.g. MB52)were not adapted to CWM.

LIS, SIS 2 LIS and SIS are not adapted to CWM requirements

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


October 2010 30

5.6 BAPIs, IDOCs, and BI Extractors

Enhancements for BAPIs, IDocs and BI extractors are only available if described in the CWMdocumentation.


October 2010 31

5.7 Overview of transactions not available with CWM

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

Old TC Text-EN new TC (or SAP Note / SP-level)

CKU1 Update Material Price

CO07 Create order without a material

CO07 available with SAP Note1396599 / Support PackageSAPK-60406INISCWM

CORO Create Process Order w/o Material

CORO available with SAP Note1396599 / Support PackageSAPK-60406INISCWM

HUP1 HU creation in productionJ1A3 MM goods issue revaluationJ1A5 MM Warehouse stock report (Arg.)J1AX Market price determination programJ1AZ MM index adjustment programKKC1 Create Cost ObjectKKC2 Change Cost ObjectKKC3 Display Cost ObjectKKC7 Create Product GroupKKC8 Change Product GroupKKC9 Display Product GroupKKF1 Create CO Production Order

KKF2 Change CO Production Order

KKF2 available with SAP Note1397012 / Support PackageSAPK-60406INISCWM

KKF3 Display CO Production Order

KKF3 available with SAP Note1397012 / Support PackageSAPK-60406INISCWM

KKF6 Create Production Cost CollectorKKF6M Create Multiple Product Cost Coll.KKF6N Maintain Product Cost CollectorKKF7 Change Production Cost CollectorKKF8 List Production Cost CollectorKKPH Collective EntryKKPHIE Cost Object HierarchyKKPK Collective EntryKKS5 Variances - Product Cost by Per. (C)KKS6 Variances - Product Cost by Per. (I)MB01 Post Goods Receipt for PO MIGOMB02 Change Material Document MIGOMB04 Subsequ.Adj.of "Mat.Provided"Consmp.MB05 Subseq. Adjustmt: Act.Ingredient MatMB0A Post Goods Receipt for PO MIGOMB11 Goods Movement MIGO


October 2010 32

MB1A Goods Withdrawal MIGOMB1B Transfer Posting MIGOMB1C Other Goods Receipts MIGOMB26 Picking list CO27MB31 Goods Receipt for Production Order MIGOMB5B Stocks for Posting DateMB5K Stock Consistency CheckMB5M BBD/Prod. Date BMBCMB5S Display List of GR/IR BalancesMB5U Analyze Conversion DifferencesMBBM Batch Input: Post Material DocumentMBBS Display valuated special stockMBLB Stocks at SubcontractorMBNL Subsequent Delivery f. Material Doc. MIGOMBRL Return Delivery for Matl Document MIGOMBSF Release Blocked Stock via Mat. Doc. MIGOMBSL Copy Material DocumentMBST Cancel Material Document MIGOMBSU Place in Stor.for Mat.Doc: Init.Scrn MIGOMBWO Error Correction: Subs. Value Calc.ME21 Create Purchase Order MEPOME22 Change Purchase Order MEPOME23 Display Purchase Order MEPOME27 Create Stock Transport Order MEPOMF60 Pull ListMF63 Staging SituationMF65 Stock Transfer for ReservationMF68 Log for Pull ListMFHU Backflushing In Repetitive MfgMIGO_GS Subseq. Adjust. of Material ProvidedMR32 Change Material Layer (LIFO)MR33 Display Material Layer (LIFO)MR34 Change FIFO DataMR35 Display FIFO DataMR39 Display Documents (LIFO)MRF1 Execute FIFO ValuationMRF2 Diplay Documents (FIFO)MRF3 FIFO Valuation: Create Doc. ExtractMRF4 FIFO: Select MaterialsMRF5 FIFO: Delete Valuation DataMRL1 Perform LIFO Valuation: Single MatlMRL2 Perform LIFO Valuation: PoolsMRL3 LIFO Lowest Value ComparisonMRL4 Display LIFO Valuation: Single MatlMRL5 Display LIFO Valuation: PoolsMRL6 Select MaterialsMRL7 Display Pool FormationMRL8 Create Base LayerMRL9 LIFO Valuation: Create Doc. Extract


October 2010 33

MRLA Check Pool FormationMRLB Delete LayerMRLC Transfer Third-Party DataMRLE Change Group StructureMRLF Create Version as CopyMRLG Aggregate LayerMRLI Generate PoolsMRLK LIFO: Adjust Units of MeasureMRLL LIFO: Reassign Material LayerMRN0 Deter. Lowest Value: Market PricesMRN1 Deter. Lowest Value: Rge of CoverageMRN2 Determ. Lowest Value: Mvmt RateMRN3 Loss-Free ValuationMRN8 Lowest Value: Price VariancesMRN9 Balance Sheet Values by AccountMRY1 Calculate Average Receipt PriceMRY2 Transfer Physical Inventory PricesVL01 Create Delivery VL01NVL02 Change Outbound Delivery VL02NVL03 Display Outbound Delivery VL03NVL31 Create Inbound Delivery VL31NVL32 Change Inbound Delivery VL32NVL33 Display Inbound Delivery VL33N

CWM Restrictions 604

Documents

Transcript of CWM Restrictions 604