SAP零售ERP：深入理解商品主数据的秘密

需积分: 9 155 浏览量更新于2024-07-15 收藏 861KB PDF 举报

"《ERP零售文章主数据深度解析：揭秘SAP零售背后的秘密》" 本文是一篇针对SAP零售领域的企业资源规划（ERP）主数据的专业指南。作者Björn Panter和Dr. Axel Woelke，分别在SAP AG公司拥有丰富的经验和深厚的专业背景。Björn自1998年起在SAP的IS零售主数据支持部门工作，积累了大量处理ERPRetail和ERP PLM主数据项目的实战经验，他的专长集中在这些领域的数据管理策略上。Axel Woelke则从2004年开始担任ERP PLM领域的支持顾问，专注于主数据管理，尤其是ERPRetail的主数据。本文并非传统的用户手册，而是对ERP零售主数据的整体“集成文章主数据”进行了一次深入剖析。它探讨了以下几个关键主题： 1. 整体架构：文章详细介绍了ERP零售主数据的内部结构，包括如何设计和组织数据模型，以确保数据的一致性和高效性。 2. 流程流：文章揭示了主数据创建、维护和更新的实际操作流程，以及如何确保这些过程在整个零售业务环境中无缝衔接。 3. 批量数据处理：作者分享了处理大规模主数据的方法，以及如何优化性能，避免在数据导入或更新时可能出现的问题。 4. 参考数据处理：深入讨论了如何管理和维护引用数据，如商品分类、价格列表等，确保其准确性和实时性。 5. 继承和复制处理：解释了如何在新实体创建时利用继承和复制功能，减少重复工作并保持数据一致性。 6. 性能影响因素：分析了影响主数据处理速度的关键因素，如数据库设计、索引优化和并发处理策略。 7. 最佳实践：提供了一系列避免常见问题和挑战的实用建议，确保在实际应用中能够顺利应对复杂的零售业务场景。 8. 适用范围：文章适用于所有SAP ERPRetail的版本，欲了解更多详细信息，读者可访问SAP企业资源规划主页获取最新资讯。无论是对于系统管理员、数据分析师还是业务用户，这篇文章都提供了宝贵的知识和洞察，帮助他们在ERP零售环境中更有效地管理主数据，提升业务效率。通过深入理解这些秘密，用户可以避免潜在的数据管理陷阱，并在日常运营中更好地利用SAP系统的功能。

Article Master Data of ERP Retail -Deep Dive into Some Secrets

between vendor to DC and DC to site, the determination of a source of supply will have impact on logistic

master data of article master. Depending on this setting, some logistic parameters will be taken from the

vendor level. Changes on vendor data e.g. planned delivery time will change article master data in a mass

update run.

Merchandise Categories

In ERP Retail, the role of material groups is covered by merchandise categories (MC), with strongly

enhanced functionality, however.

Merchandising categories are maintained by the following transactions:

• WG21 - create MC

• WG22 - change MC

• WG23 - delete MC

• WG24 - display MC

The following functionalities are implemented for merchandise categories:

• The merchandise category characterizes a logical grouping for the articles.

• It is possible to build up hierarchies of MC's, with inheritance of properties.

• It is possible to deposit templates (reference articles) in the MC. By doing so, values are proposed

for all articles created on basis of this MC.

• It is possible to deposit a 'value only article'. Thus, inventory management does not have to count

exactly on article level, but on value only article level is sufficient. This means, not '5 oranges for

70 Cent each and one lemon for 50 Cent' are booked, but only 'tropical fruits for 4 Euro'.

• It is possible to deposit, just like in a class, characteristics in the MC. In addition, there is a

'relevance indicator' deciding whether the characteristics are only informative, just like

characteristics in classification, or if they are relevant for the creation of variants. We will talk about

this special topic later.

• If, for some articles in the MC, different characteristics are necessary, it is possible to deposit them

in a characteristic profile which can be applied if needed (optional).

• An overview on all articles assigned to this MC is possible.

For maintenance of MC hierarchies, the following transactions are available:

• CLWM - create hierarchy level

• CLWN - change hierarchy level

• CLWP - delete hierarchy level

• CLWO - display hierarchy level

• CLW1 - maintain hierarchy assignment

• CLW2 - display hierarchy assignment

• CL6C - graphical hierarchy display

• WGUS - use of material groups

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Article Master Data of ERP Retail -Deep Dive into Some Secrets

From the technical point of view, a MC is at the same time a material group (as in material master) and a

class of internal class type 026 (as in classification). For this reason, the MC data is stored redundantly in

two different tables.

For the standard material master, MC's are stored in customizing table T023, just like the 'standard' material

group. Here, all material specific data, like reference article or value only article, is being stored. The

descriptions in different languages are stored in table T023T.

This means here we have a combination of a classical customizing table T023 and a transactional

classification assignment.

That’s also the reason why a transport of merchandise categories between systems is not possible in ERP

retail. This is a very common support situation. Consultants know the standard functionality only and mess

up the retail system. Based on this situation, we removed the possibility to maintain merchandise categories

directly from customizing and referred to the retail area menu WWG1.

A summary about FAQs about merchandise categories can be found in note 359940.

Let us focus on technical details.

For the classification, MC's are stored in the node table KLAH, just like a 'standard' class. Hierarchy levels

and characteristic profiles are also deposit there. The different objects are distinguished from each other by

the flag KLAH-WWSKZ. The following values are possible:

• KLAH-WWSKZ = 0 Hierarchy Level

• KLAH-WWSKZ = 1 Merchandising Category

• KLAH-WWSKZ = 2 Characteristic Profile

• KLAH-WWSKZ = 3 Generic Article

• KLAH-WWSKZ = initial ‚Standard’ Class

That means in ERP retail, we use the standard classification system for creating classes, but give them an

own semantic. With the help of the WWSKZ field we distinguish the usage. Some of you will remark here a

very special of the classes, the so called ‘generic article’. In one of the following chapters we will focus on

that.

The descriptions are stored in table SWOR as keywords as well as in table T023T.

Hierarchy assignments are being stored the same way as in a class hierarchy, in “edge” table KSSK. The

assigned objects are not identified by the name of the MC or the hierarchy level, but by the internal class

number (KLAH-CLINT) and Characteristic profiles as well. The flag MAFID on table KSSK indicates that the

assignment is not a classified object, but a classified class. (K for class assignment and O for object

assignment).

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

剩余39页未读，继续阅读

ChriSongJ

粉丝: 0
资源: 2

SAP零售ERP：深入理解商品主数据的秘密

Article Master Data of ERP Retail - Deep Dive into Some Secrets

藏经阁-Deep Dive Into Catalyst_ Apach.pdf

deepdive和deepke的区别

学习后端应该准备什么书籍

基于deepdive的知识抽取实例

ckeditor5中文文档

天池实验室安装d2lzh_pytorch

有什么devops书籍推荐吗

The filename, directory name, or volume label syntax is incorrect. The filename, directory name, or volume label syntax is incorrect. ERROR conda.cli.main_run:execute(47): `conda run python D:\DeepLearning\dive_into_deep_learning\MLP.py` failed. (See above for error)

最新资源