Scribd
Upload
80 views1 page

2 General Integration Overview

Uploaded by

Raj Panigrahi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
80 views1 page

2 General Integration Overview

Uploaded by

Raj Panigrahi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

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 4, 5 and 6 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 4
• • chapter 2.2 (XO integration) → details see chapter 5
• • chapter 2.3 (Saving data to database) → details see chapter 6

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 are the classes


• • FSBP_BDT_ADAPTER_INTERN (inheriting from XO_BDT_ADAPTER, several methods
redefined): Specification for Financial Services Business Partner datasets
• • Class CVI_BDT_ADAPTER_INTERN (inheriting from FSBP_BDT_ADAPTER, several
methods redefined): Specification 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 many more details including a precise step-by-step description about the BDT implementation in
chapter 4 below.

You might also like