没有合适的资源?快使用搜索试试~ 我知道了~
sap bp增强开发手册
需积分: 5 1 下载量 84 浏览量
2024-01-10
14:06:16
上传
评论
收藏 797KB PDF 举报
温馨提示
试读
26页
Cookbook for enhancing the SAP Business Partner with additional customer/vendor fields
资源推荐
资源详情
资源评论
Cookbook for enhancing the SAP Business Partner with
additional customer/vendor fields
Customer Edition 1.15 – July, 13
th
, 2021
Source
The source of this document is SAP note 2309153. Please check this note regularly to get the latest
version of this document.
The example coding used in this cookbook is provided by SAP note 2295823. It might be necessary to
implement this note to have this coding available in your system.
Change History
Version 1.15 (July 13
th
, 2021)
- Chapter 3.5.5 – BDT Field Groups – BUS2
--> Correct description how to enhance existing FMOD2 function modules with own logic
Version 1.14 (February 12
th
, 2018)
- Chapter 3.10 – Field modification for blocked customer/vendor
Version 1.13 (May 04
th
, 2017)
- Chapter 3.5.2 – Necessary section to screen assignments in BDT customizing
Version 1.12 (April 20
th
, 2017)
- Wrong structure BUS_EI_EXTERN in section 2.3.2 corrected to CVIS_EI_EXTERN
- Wrong structure BUS_EI_EXTERN in section 5.2 corrected to CVIS_EI_EXTERN
Version 1.11 (April 19
th
, 2017)
- Hyperlinks of document references in section 1.3 updated
Version 1.10 (October 06
th
, 2016)
- New chapter 6 for mass processing (Central API) created
- Removing scenario where appended fields are not available in complex structure
BUS_EI_EXTERN
Version 1.00 (June 13
th
, 2016)
Cookbook – Extending SAP Business Partner with customer/vendor datasets
© Copyright SAP SE 2018 Page 2 of 26
1 General Information
In SAP Business Suite (ERP 600 and Enhancement Packages), customer master data and vendor
master data transactions such as FD01, FD02, FD03, XD01, XD02, XD03, FK01, FK02, FK03, XK01,
XK02 and XK03 have been enhanced by customers with additional fields using the Business Add-In
(BAdI) technology. In the customer and vendor master dialog transactions, these fields were
integrated by adding additional sub-screens to the existing screens.
Moving to a SAP S4HANA release, traditional customer/vendor master transactions are made
obsolete and replaced by the business partner transaction BP. Because of this, all extension-specific
fields have to be integrated into the business partner.
This document provides a guideline how customers can transfer the enhancements they have made in
the customer/vendor transactions to transaction BP, so that a maintenance of these fields remains
possible after the upgrade to a S4HANA release.
Important
There are three different scenarios, which have to be considered differently:
Scenario A Integration of complete tables in customer namespace that refer to
customer / vendor master
Scenario B Integration of own appends of customer/vendor master core tables
(e.g. appends to tables KNA1 or LFA1)
Scenario C* Integration of a new development into the SAP Business Partner*
*Scenario C is not in scope of this document. New requirements with the goal to enhance master data
in S4 releases with own fields should be developed completely within the SAP Business Partner.
Please refer to the guidelines for enhancing the SAP Business Partner:
• BDT (Business Data Toolset) – Developer’s Manual
• Help Portal – Business Partner Extensibility
• Easy Enhancement Workbench (EEW)
Please find document links to these topics in reference table in chapter 1.3.
Cookbook – Extending SAP Business Partner with customer/vendor datasets
© Copyright SAP SE 2018 Page 3 of 26
1.1 Used tools and frameworks
Enhancements to the SAP Business Partner can be made by using the frameworks / tools mentioned
below:
• BDT (Business Data Tool Set) – Enhance dialog screens in transaction BP
• XO Framework (Extensible Objects) – Validate data and store them in memory
• CVI Synchronization – Map the data from BP to customer/vendor master
and save them to the database
1.2 Idea in a nutshell
The BDT will be used to enhance the existing screens in transaction BP with the additional required
fields, tables or checkboxes. The XO framework will be used to validate and to store the data in the
memory. BAdI implementations within the CVI synchronization will collect the data from XO memory
and save it to the database, in case additional data is not part of the complex interface structure.
For mass processing the “Central API” is available. This interface provides the functionality for creating
and updating master data including both core and application data.
1.3 Document references
Topic
Reference
BDT (Business Data Tool Set)
BDT Developer’s Manual
Link to SAP User Assistance
XO Framework (Extensible Objects)
SAP note “1623809 - Developer documentation for the XO framework”
Link to SAP note 1623809
CVI (Customer-Vendor-Integration)
SAP note “956054 - BP_CVI: Customer/vendor integration as of ERP 6.00”
Link to SAP note 956054
Help Portal
Link to SAP Documentation
Easy Enhancement Workbench (EEW)
Help Portal
Link to SAP Documentation
Business Partner Extensibility
Help Portal
Link to SAP Documentation
→ Functions → Extensibility
Cookbook – Extending SAP Business Partner with customer/vendor datasets
© Copyright SAP SE 2018 Page 4 of 26
Table of Contents
1 General Information ____________________________________________________ 2
1.1 Used tools and frameworks ____________________________________________________ 3
1.2 Idea in a nutshell ____________________________________________________________ 3
1.3 Document references _________________________________________________________ 3
2 General integration overview ____________________________________________ 5
2.1 BDT Integration ____________________________________________________________ 5
2.2 XO overview ________________________________________________________________ 6
2.2.1 Scenario A – Integration of own tables in customer namespace ______________________ 6
2.2.2 Scenario B – Integration of core table appends __________________________________ 6
2.3 Saving data to the database ____________________________________________________ 6
2.3.1 Scenario A – Saving data in own tables ________________________________________ 6
2.3.2 Scenario B – Saving data in core table appends __________________________________ 6
3 Settings in BDT – Business Data Toolset ___________________________________ 7
3.1 General information about naming conventions in BDT _______________________________ 7
3.2 Own BDT application – Transaction BUS1 _________________________________________ 7
3.3 Separate BDT datasets – Transaction BUS23 ______________________________________ 7
3.4 Registering tables – Transaction BUSG ___________________________________________ 8
3.5 BDT Assignments of screen->section->view->field group->field – Transaction BUS4 ________ 8
3.5.1 BDT screen sequences – Transaction BUS6 ____________________________________ 8
3.5.2 BDT screens – Transaction BUS5 ____________________________________________ 8
3.5.3 BDT sections – Transaction BUS4 ____________________________________________ 8
3.5.4 BDT views – Transaction BUS3 ______________________________________________ 8
3.5.5 BDT field groups – BUS2 ___________________________________________________ 9
3.6 BDT events – BUS7 __________________________________________________________ 9
3.7 Additional functions – BUS9 ___________________________________________________ 10
3.8 Assignments Dynpro field->DB field and DI field->DB field – BUSB and BUSB_DI _________ 11
3.9 BP_Views – BUSD __________________________________________________________ 11
4 XO Framework – Extensible Objects _____________________________________ 12
4.1 Scenario A – Integration of own tables in your namespace ___________________________ 12
4.1.1 Create Memory Object (MO) class ___________________________________________ 12
4.1.2 Create Persistence Object (PO) class _________________________________________ 12
4.1.3 XO Customizing _________________________________________________________ 13
4.2 Scenario B – Integration of core table appends ____________________________________ 15
4.2.1 Create Validation Object (VO) classes ________________________________________ 15
4.2.2 XO Customizing _________________________________________________________ 18
5 CVI – Saving data to database ___________________________________________ 19
5.1 Scenario A – Saving data in own tables in your namespace __________________________ 20
5.2 Scenario B – Saving data in core table appends ___________________________________ 22
5.2.1 Foreign key checks of appended fields ________________________________________ 22
6 Mass Data Processing – Central API _____________________________________ 24
6.1 Scenario A – Processing data of non-core tables __________________________________ 24
6.2 Scenario B – Processing data in core table appends ________________________________ 24
6.3 Data validation _____________________________________________________________ 24
6.4 Committing changes and error handling __________________________________________ 25
7 Debugging ___________________________________________________________ 26
Cookbook – Extending SAP Business Partner with customer/vendor datasets
© Copyright SAP SE 2018 Page 5 of 26
2 General integration overview
For details about the Extensible Objects (XO) tool see note 1623809 (the note contains a developer
documentation as attachment). The complete XO customizing is maintained in transaction XO80. Only
the XO business object type BUSINESS_PARTNER is relevant for the CVI enhancement.
The purpose of this chapter is to provide an overview over the necessary activities using the
tools/frameworks mentioned in chapter 1.1. In chapters 3, 4 and 5 the detailed steps to be executed
per tool/framework are described. The relation between the overview chapter and the detail chapters
is as follows:
• chapter 2.1 (BDT integration) → details see chapter 3
• chapter 2.2 (XO integration) → details see chapter 4
• chapter 2.3 (Saving data to DB) → details see chapter 5
2.1 BDT Integration
This sub-chapter provides the overview of the BDT integration of the CVI. You can find the detailed
activities in Chapter 4 below.
The integration of XO into BDT has been implemented in a generic way. The major part of the integration
is implemented generically. All further new datasets or core table appends that are integrated into BDT
using XO do not need to care about this part. If the integration is done as described below, the framework
will take care of the generic logic automatically. Especially most of the BDT events are treated
generically by the so-called BDT-adapter. The generic implementation is provided by class
• XO_BDT_ADAPTER (generic class for BDT integration).
On top of this, there is class:
• Class CVI_BDT_ADAPTER_INTERN with specific enhancements for CVI Business Partner
datasets
Within the BDT adapter classes you find methods (generic_*; e.g. GENERIC_ISDAT or
GENERIC_ISSTA), that are called by the BDT event function modules (XO_GENERIC_EVENT_* in
transaction BUS7). These methods are generically responsible for processing the corresponding
events for all Financial Services and CVI datasets. For these events, no individual implementation is
necessary.
In addition, there are BDT settings that need to be implemented individually. For example in the
corresponding view in BDT, a PBO and a PAI module need to be registered for every view. Within
these two function modules the selection of data for this dataset from XO memory as well as the
saving of the changed data into XO memory later on are implemented. Further individual BDT settings
that need to be considered are for example a new BDT application per extension (separate for
customer and vendor enhancements), and of course the complete screen construction (screens,
sections, views, field groups, datasets).
In addition dynpros (SE80-screens) need to be implemented in transaction SE80 including PBO and
PAI logic within the BDT function group that is responsible for the corresponding BDT application. The
already mentioned PBO- and PAI-function modules need to be implemented there as well.
You can find more details including a precise step-by-step description about the BDT implementation
in chapter 3 below.
剩余25页未读,继续阅读
资源评论
work_mac
- 粉丝: 26
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 基于CarNet实现裂缝检测python源码+文档说明+数据+图片(课程设计)
- 课程设计-基于耐火材料裂缝剥落检测python源码+课件
- 基于OpenCV的视频道路车道检测python源码+文档说明+实验演示+图片+使用方法(高分毕业设计)
- 基于OpenCV的案例:图像边缘、角点和轮廓检测,图像分割,图像增强;图片拼接;运动目标检测,颜色直方图比较,三帧帧差法,抠图
- SmartPlug-html大一笔记
- SmartPlug-proteusdemo
- Preliminary Findings on Handmade Rattan Baby Crib andBassinet Designs Regarding.zip
- aveebfq_v1.2.83_downyi.com.apk
- 基于有机发光二极管(OLED)的建模优化算法的matlab仿真源码+数据+文档说明+项目说明(高分课程设计)
- hash01-test.c 本人哈希表(一)的示例代码,仅供参考!
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功