Business Partner SAP S4 HANA insights
深入了解SAP S4 HANA Business Partner
The following blog post provides an insight into the SAP S/4 HANA system and how business partner setup must be done for migration. 以下博文深入了解了SAP S/4 HANA系统，以及迁移时该如何设置Business Partner。
I would like to share a glimpse of my current experience with SAP S/4 HANA migration. 我想与大家分享一下我目前在SAP S/4 HANA迁移方面的经验。
Many of us always struggle where to start, how to start and finally ends with why to start ? 我们中的许多人总是挣扎着从哪里开始，如何开始，最后以为什么开始而结束？
Let us discuss, how to start/maintain a system with clean data and migrate to SAP S/4 HANA. 让我们讨论一下，如何使用干净的数据启动/维护系统并迁移到SAP S/4 HANA。
For a successful implementation of the data migration, it is vital that the system is populated with a complete and accurate set of data from legacy systems that meets the technical requirements of target systems and the business requirements of its users. 为了成功实施数据迁移，系统中必须包含一组完整、准确的数据，这些数据来自遗留系统, 并且满足目标系统技术要求和用户业务要求的。
In any project, appropriate understanding and analysis of the data of the source system and the ‘to be’ system allows a program of data management actions to be defined and implemented to produce a data set: 在任何项目中，对源系统和“未来”系统数据的适当理解和分析允许定义和实施数据管理行动计划，以生成数据集：
- That maximizes the value of legacy data used in the new system. 使新系统中使用的旧数据的价值最大化。
- That makes data available to accelerate business benefit delivery使数据可用，以加快商业利益的交付。
- That meets the data demands of business processes. 满足业务流程的数据要求。
- That meets the technical data demands. 满足技术数据要求。
- Takes care of pain areas of the current data quality. 关注当前数据质量的难点领域。
With current project experience, I have divided into below categories根据目前的项目经验，我将其分为以下几类
- Analysis – of the system (source and target) and source data对系统（源和目标）和源数据的分析
- Enrichment – the source data 对源数据做增补
- Cleansing – the data 对数据做清理
- Consolidation – final output which is going to be migrated 合并–得到最终需要迁移的数据
SAP S/4 HANA offers you many new possibilities for managing your business partner data. But many SAP customers realize: a smooth transition is impossible with the data as it is – the quality is just too poor. SAP S/4 HANA为您管理业务伙伴数据提供了许多新的可能性。但许多SAP客户意识到：数据的现状不可能实现平稳过渡——质量太差了。
Companies found data migration is more difficult than expected, let us go through how (with my knowledge) 公司发现数据迁移比预期的更困难，让我们（以我的知识）了解一下如何迁移
- Today, customer and supplier data might be distributed everywhere. Tomorrow, you want it consolidated in one database (the “SAP Business Partner”) 如今，客户和供应商数据可能分布在任何地方。明天，您希望将其整合到一个数据库（“SAP Business Partner”）里。
- Eg: company ABCD may be having their businesses in different countries and maintaining their transactional data in various databases and they have decided to consolidate their customer data and supplier’s data at one point. 例如：公司ABCD可能在不同的国家开展业务，并在不同的数据库中维护其交易数据，并且该公司在某个时刻决定整合其客户数据和供应商数据。
- And here is a solution what are we talking about. 有一个解决方案，即是本文正在讨论的。
Issues generally what we face: 我们面临的一般问题：
- Countless duplicates make it very hard to identify the truly active business partners. 无数的数据重复使得识别真正活跃的业务伙伴非常困难。
- Closer to go-live, companies discover that data is incorrect and incomplete, automatic transactions do not go through; deliveries might end up at the wrong address. 接近上线时，公司发现数据不正确且不完整，无法进行自动处理；送货可能会到达错误的地址。
- As the go-live date looms, the time has run out to organize a manual data cleanup. 随着上线日期的临近，组织手动数据清理的时间已经不多了。
In SAP S/4 HANA, Business Partner is the leading object and single-entry point to maintain Business Partner, Customer, and Supplier (formerly known as Vendor) master data. This is to ensure ease of maintenance of the above master data and to achieve harmonization between them. Compared to classical ERP transactions, maintenance of Customer and Supplier master data via Business Partner has multiple advantages. Some of them are as follows: 在SAP S/4 HANA中，Business Partner是维护业务伙伴、客户和供应商主数据的主要对象和单一入口点。这是为了确保上述主数据易于维护，并能实现它们之间的协调。与传统的ERP系统相比，通过Business Partner维护客户和供应商主数据具有多重优势。其中包括：
- Business Partner allows maintenance of multiple addresses with corresponding address usages. Business Partner允许维护具有相应地址用途的多个地址。
- In classical transactions, one customer can only be associated with one account group. But in Business Partner, multiple roles can be associated with the same Business Partner. 在传统交易中，一个客户只能与一个账户组关联。但在Business Partner中，多个角色可以与同一Business Partner关联。
- Maximal data sharing and reuse of data which lead to easier data consolidation. 最大限度地共享和重复使用数据，从而简化数据整合。
- General Data available for all different Business Partner roles, specific data is stored for each role. 通用数据适用于所有不同的Business Partner角色，存储每个角色的特定数据。
- Maintenance of multiple relationships to the same Business Partner. 维护与同一Business Partner的多个关系。
- Maintenance of Time Dependency at different sub-entities roles, address, relationship, bank data, etc. 维护不同子实体角色、地址、关系、银行数据等的时间相关性。
Description描述:
There are redundant object models in the traditional ERP system. Here the vendor master and customer master are used. The (mandatory) target approach in SAP S/4 HANA is the Business Partner approach. 传统ERP系统中存在冗余的对象模型。这里使用的是供应商主数据和客户主数据。SAP S/4 HANA中的（强制性）目标方法是Business Partner方法。
Business Partner is now capable of centrally managing master data for business partners, customers, and vendors. With current development, BP is the single point of entry to create, edit, and display master data for business partners, customers, and vendors.
Business Partner现在能够集中管理业务合作伙伴、客户和供应商的主数据。在当前的开发中，BP是为业务合作伙伴、客户和供应商创建、编辑和显示主数据的单一入口点。
Using RFC functions, we can target to load/migrate the data to SAP S/4 HANA. 使用RFC功能，我们可以将数据加载/迁移到SAP S/4 HANA。
There are standard RDP (Rapid Data Mart) functionalities were offered by SAP, it is the best to part of creating business partners. SAP提供了标准RDP（快速数据集市）功能，这是创建business partners的最佳方式。
Like using CVI functions, we can create, edit and delete*(this is a huge topic could be discussed, here deleting could be considered as limited to the individual roles). 与使用CVI函数一样，我们可以创建、编辑和删除*（这是一个可以讨论的巨大主题，这里可以将删除视为仅限于单个角色）。
In native application, it is not possible to migrate customer and vendor/supplier together to the target system, the question arises here is: can we achieve this through a business partner approach in SAP S/4 HANA? 在本机应用程序中，不可能将客户和供应商一起迁移到目标系统，那么问题来了：我们能否通过SAP S/4 HANA中的business partner方法实现这一点？
The answer is: YES, we can. 答案是：是的，可以。
The solution is: Maintaining with different roles in a business partner for supplier and customer. 解决方案是：为供应商和客户在业务合作伙伴中维护不同的角色。
Ideally, for a customer- it will be FLCUXX(FLCU00/FLCU01) 理想情况下，对于客户而言，应为FLCUXX（FLCU00/FLCU01）
As below: 详情如下:
角色FLCU00将是客户的财务视图，角色FLCU01将是客户的销售视图。
In details: 详情如下：
How to navigate to Business partner? 如何导航到Business partner？
Answer is:答案是：
Go to SAP screen and Tcode – BP 输入事务代码BP.
Then you can find the next screen with business partners: 然后，您可以在下一个屏幕中找到业务伙伴：
You can easily identify with roles, what are you dealing with: 你可以很容易地识别角色:
The base role should be a business partner- 000000- In general, you need to do nothing here, it will automatically be created with other roles by default. 基本角色应该是业务伙伴-000000-通常，您不需要在此处执行任何操作，默认情况下，它将与其他角色一起自动创建。
Let us see other roles here for customer and vendor integration: 让我们在此了解客户和供应商集成的其他角色：
- Business Partner -000000
- Customer- FLCUXX
- Customer Account
- Customer sales
- Vendor -FLVNXX
- Vendor accounting
- Vendor purchasing
You can easily identify in below screen: 您可以在下面的屏幕中轻松识别：
The subcategory roles will be replaced XX with 00/01/02 follows (customization part). 子类别角色将被后续的00/01/02替换XX（自定义部分）。
In a nutshell, we can send these roles along with additional details which were required like general data along with address, identification details, sales organizations, company details, vendor general data, vendor purchasing information and maintaining relationships(another tricky part and important for BPs) 简而言之，我们可以发送这些角色以及所需的其他详细信息，如一般数据以及地址、身份详细信息、销售组织、公司详细信息、供应商一般数据、供应商采购信息和维护关系数据（另一个棘手的部分，对BPs很重要）。
英文原文地址：
Business Partner SAP S/4 HANA insights | SAP Blogs
-完-
2021-10-7 翻译于住处。
1151
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
