Sap master data

©SAP AG 2007

ISM Trading Industries

Enhancements Master Data - SAP ERP2005 EnhP2

©SAP AG 2007

Department store / Shop maintenance

Article hierarchy maintenance

Article master maintenance

Transportation chains and staging time

Article substitution – Master Data

© SAP AG 2007

Article Master Maintenance: Enhancement

FunctionalityInclusion of the Article Description for variants when maintaining EANs in the article master

BenefitsThe new functionality is a simplification for customers who change EANs for variants more often.

UseIn article master maintenance (Transactions MM4X), a new column was added to the additional data under the tab strip “EAN Maintenance” to display the article descriptions of the variants for the given logon language. The “Article Description” column was inserted after the “VR – Other Vendor Reference” column and can also be moved to suit customer-specific requirements. The column is only visible at generic article level if the EANs of all variants are listed.

©SAP AG 2007






© SAP AG 2007

Transportation Chains and Staging Time (1)

FunctionalityEnhanced storage levels for transportation chain and staging time

BenefitsThe storage levels for external transportation chains and their staging time were enhanced with the functionality to provide more detailed data retention levels to be able to support more scenarios within the scheduling of the procurement controlling.Example:An external vendor supplies two different distribution centers with the same articles. The transportation chain/staging time for delivery vary for these articles depending on the distribution center.

© SAP AG 2007

Transportation Chains and Staging Time (2)

UseBesides the existing storage level for vendor master data (General Data) the transportation chain and staging time can be maintained at Purchasing Organization Data level (including alternative data on site and/or vendor subrange level) within vendor master data maintenance (transactions XK0x).Additionally the transportation chain and staging time can also be maintained in the purchasing inforecord maintenance (transaction ME1x) similar to the existing maintenance possibility in the article master data maintenance (MM4x).Besides the enhancement of the storage levels, the reference logic during the creation of master data records containing a transportation chain and a staging time has been adapted.Finally, the access logic to find a transportation chain with its staging time within the scheduling has been extended according to the new storage levels.The existing storage levels are now:

At vendor level (LFA1)At vendor, purchasing organization level (LFM1) -> newAt vendor, purchasing organization, vendor subrange and/or site level (LFM2) -> newAt purchasing info record, purchasing organization level (EINE)At purchasing info record, purchasing organization, site level (EINE)

©SAP AG 2007






© SAP AG 2007

Department Store / Shop Maintenance – Enhancement (1)

FunctionalityEnhancements to function for copying Sales Area and Company Code data when creating Shops

BenefitsThe system will now copy the sales area data for the department store customer to the shop, regardless of whether the customer sales areas for the department store are the same as the sales areas in the general site-specific data on the department store.

UseThe new feature is available while creating a new shop with transaction WRFSHOPDEP and WRFSHOPCAT.When creating a new Shop under a Department Store, all the Sales Area segments of the Department Store are copied to the new Shop.The system no longer checks whether the customer sales areas for the department store are the same as the sales areas in the general site-specific data on the department store.When creating a new Shop under a Department Store, all Company Code segments of the Department Store are copied to the new Shop.The system no longer checks whether the customer company codes are the same as the company code in the general site-specific data on the department store.A new “Sales Area” Button in the “Shop Data Distribution Chain” tab strip of the “Detail Maintenance for Shop” screen allows selecting any of the copied Sales Area and enter specific data for this Sales area.

© SAP AG 2007

Department Store / Shop Maintenance – Enhancement (2)

Example

Org.Data/Calendar Department Store

Debitor

Sales organization: V001Distribution channel: V1



Debitor

Shop Sales organization: V001Distribution channel: V2


©SAP AG 2007






© SAP AG 2007

Article Hierarchy – Enhancements (1)

FunctionalityNew consistency check reportNew User interface for the Simulation function New User interface for the Copy function

BenefitsThe consistency check report inform the user about existing inconsistencies in an article hierarchy and help him to analyze and to eliminate them.The new interfaces for the Simulation- and the Copy-Function areeasier to use for the customer.

© SAP AG 2007

Article Hierarchy – Enhancements (2)

UseConsistency report (transaction WMATGRP12)

The consistency report checks the general consistency of the articlehierarchy such as : nodes or articles without a parent node or inconsistent validities between a node and its parent node.Beside the general consistency logic within the article hierarchy maintenance, the consistency report detects database errors occurred because of incorrect functionality or other inconsistent operations. The report generated by the consistency check informs the user, using three different lists, about inconsistent data found in an article hierarchy. The lists show all the inconsistency categories description in a tree format. Rows under each category are giving all the details about where the inconsistency is coming.

New User interface for the Simulation function (WMATGRP08N)Remark: The logic behind the transaction is the same as the previousversionNew User interface for the Copy function (WMATGRP06N)Remark: The logic behind the transaction is the same as the previousversion

©SAP AG 2007






© SAP AG 2007

Article Substitution – Master Data

FunctionalityEnhanced Maintenance for assignments of follow-up/replacement article-relationships

BenefitsThe master data maintenance in ERP was enhanced in order to mapthe new ERP- and F&R-functionality for the article substitution.

UseThe master data maintenance in ERP (transaction WRFFUART) was enhanced:

In addition to the distinction between follow-up and replacement relationships that has already been implemented, there are two new indicators “event-controlled” and “time-controlled” for both follow-up categories (control of follow-up type number).

For each assignment, the entry of conversion factors will be supported, for example, 2 base units of article A correspond to 4 base units of follow-up article B. The base unit original article and follow-up/replacement article will be displayed.

For any article at any time on any level (for example, site), there may exist no more than one follow-up article and no more than one replacement article.

Additional plausibility checks are carried out, for example, no priorities are definable for the follow-up/replacement relationships considered in the business process article substitution.

© SAP AG 2007

Copyright 2007 SAP AG. all Rights Reserved

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

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

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Sap master data

Documents

Transcript of Sap master data