Version: 1.

Social Services AET Extensions

Cookbook

History

Version Date Status (Comments)

1.0 2011-01-31 Final

1.1 2011-03-09 Revised

1.2 2013-01-29 Enhanced

1.3 2014-02-19 Added chapter Using field

extensions

1
Table of Contents
1 Application Enhancement Tool (AET) ......................................................................... 3
1.1 Overview ................................................................................................................................................3
1.2 Architecture ..........................................................................................................................................3
2 Extensions in CRM system .......................................................................................... 5
2.1 Generate a new extension in CRM System .....................................................................................5
2.2 Test a new extension in CRM System ..............................................................................................8
3 Extension in ERP System............................................................................................. 9
3.1 Make the new extension in CRM system also available in ERP system ....................................9
3.2 Metadata transfer from CRM to ERP system ..................................................................................9
3.3 Create DDIC objects in ERP system ...............................................................................................11
3.4 Create Append in ERP system ........................................................................................................12
3.5 Display Content of an Extension Table in ERP system ..............................................................12
3.6 Create additional entries for archiving object PSSC_SXP .........................................................13
4 Using field extensions ................................................................................................ 14

2
 1 Application
Enhancement
Tool (AET)
1.1 Overview
The Application Enhancement Tool has been introduced to enhance CRM applications. You can use the
tool to search for enhancements, and to display, create, change, and delete enhancements. Enhancement
might be a flat or a deep structure.

The Application Enhancement Tool is integrated in the UI Configuration Tool and can be started in this
tool. The fields that you have added to an application are available in the UI configuration of the
corresponding UI component and view. You can make these new fields available on the user interface by
adding them to the view.

The Application Enhancement Tool offers the following main functions:

Creating custom fields

Defining dropdown list boxes for custom fields
Translating field labels and entries in dropdown list boxes
Assigning search helps and check tables to custom fields
Using different data types, such as characters, dates, times, and numbers

For details please refer to SAP Documentation

http://help.sap.com/saphelp_crm70/helpdata/en/20/b0f4f819e844df9f47bc9c70c795f4/content.htm.

1.2 Architecture
Enhancement data stored in CRM system is automatically transferred to CRM Middleware using a
customizing defined structure with appended deep structures. ERP also uses a structure but with different
naming convention. The ERP structure has the same setup. It receives data from CRM Middleware and
transfers it to ERP persistency layer.

3
4
 2 Extensions in
CRM system
2.1 Generate a new extension in CRM System
Please logon to a CRM client you have full access to the AXT role and start the AET Toolset.

In the search page please select Enhancement Object SSP for Social Service Plan or SDP for Social
Deduction Plan (depends on which object shall be enhanced).

In the Table Assignment Block please select New to create a new extension or click on the Enhancement
ID to do some changes.

5
Set the package you want to write your changes to (in most cases it will start with prefix Z*). Select
ORDERADM_H as the part of the Business Object.

Type in the Description Name for the Enhancement and add the fields, types, length etc. you want to be
stored by the extension. Make sure that the Generate flag is checked.

6
Please click on Save and Generate: the extension will be generated in the CRM system.

What will be done technically during generation process on DDIC level?

Generating 1 domain for every field

Generating 1 data element for every field with reference to the domain with equal name
Generating data structures required for internal processing
Generating table types with reference to the data structures required for internal processing
Generating a database table containing the fields described above
Generating an append structure (deep structure)
Create an append in the structure defined in AET customizing for CRM middleware data transfer
containing the deep structure (CRMS_PS_4S_AET_H):

7
2.2 Test a new extension in CRM System
Please logon to a CRM client using the CASEWORKER role. Start configuration mode and enable the
function.

After enabling the configuration mode you will see a new icon in your toolbar. Click on it.

Select the extension you have created in chapter 1.2.

Save and close your configuration.

Choose a valid transport request.

Your main application screen (SSP or SDP) has been enhanced by an additional assignment block. Test
your Enhancement is working correct: create, change and delete entries (click on Edit List).

8
 3 Extension in ERP
System
3.1 Make the new extension in CRM system also available in ERP
system
The data changes you have made at the end of the last chapter have only been stored in the CRM system.
If you want further changes be also be available in the ERP side you have to setup the ERP system for data
transfer.

Make sure notes 1561185 (CRM) and 1561087 (ERP) have been implemented in your systems and you
have authorization to create DDIC objects in the actual ERP client (in most cases you will need
authorization on S_DEVELOP level).

3.2 Metadata transfer from CRM to ERP system

Make sure a RFC connection is available from current ERP client to CRM client where you have created
your AET extensions. Start transaction SE38, enter program RPSSC00_GENERATE_AET_DATA.

Report Prerequisites:

The user executing the report needs to have the following authorization in ERP system:
Authorization object F_SC_ADM, Activity (ACTVT) 16, Program RPSSC00_GENERATE_AET_DATA.
The Report calls functions in CRM system using a RFC user. The RFC user nees to have the
following authorization in CRM system: Authorization object CRM_4S_AET, Activity (ACTVT) 03.

Report Execution:

Enter the logical system (CRM client) your current ERP client is connected to
Enter the Extended Business Object you have selected in chapter 2 of this document (SSP for
Social Service Plan or SDP for Social Deduction Plan)
Decide whether you like to execute the program in Simulation or Productive Mode (please choose
Simulation Mode = X for a first try).

9
Execute. A list will be displayed showing the extensions already existing in CRM system for the selected
Extended Business Object (SSP or SDP). Select one or multiple extensions for Extension Metadata Transfer
from CRM system to ERP system (RFC call).

As a result you will see the structure of the extension you have already created in the CRM system:

10
3.3 Create DDIC objects in ERP system
To get a template for the field setup in ERP please goto CRM system, start transaction SE11 and display
database table ZTAB0003DY (table name has been displayed in the extension structure list of report
RPSSC00_GENERATE_AET_DATA after transfer in the last chapter)

According to the CRM setup (database table ZTAB0003DY) you have to create the DDIC objects also in ERP
system. Please follow the following sequence:

Sequence According to structures in CRM system

1 Create Domains with corresponding type
2 Create Data Elements with corresponding Domain
3 Create Database Table with the correct keys (example: ZTAB0003DY)
4 Create Component Structure
5 Create Table Type containing the component structure

As a result 2 objects should exist in ERP system in a 1:1 relationship (same name, same fields, same data
element names, same domains):

database table ZTAB0003DY (name is an example only)

sub component type ZZFLD00012B (see chapter 3.4)

11
3.4 Create Append in ERP system
Please enhance structure PSSCS_AET_H with the table type (position 5 of the sequence table above).
More or less structure PSSCS_AET_H in ERP system should be identical with structure
CRMS_PS_4S_AET_H in CRM system. Please make sure the append names are equal in both systems.

The setup of the sub component type in CRM source system can be displayed clicking on the highlighted
button in report RPSSC00_GENERATE_AET_DATA.

Test a new Extension in ERP system and make sure data entered in extension field assignment block on
CRM side is also stored in ERP system (content of table ZTAB0003DY can be displayed using the Display
Content Function described in chapter 3.5).

3.5 Display Content of an Extension Table in ERP system

After saving data in CRM system the content of an extension table can be viewed using report
RPSSC00_GENERATE_AET_DATA. Please select the correct extension entry and click on button Show
Table Content. After execution the first key in the result table represents the External ID of the SSP/SDP.

12
3.6 Create additional entries for archiving object PSSC_SXP
As last step please create additional entries for archiving object PSSC_SXP as shown below.

For each table you have created a separate entry for the archiving object is needed in case you would like
to have the content archived automatically when archiving SXP documents in ERP.

These entries are modifications but there is no other way to include the enhancement tables
automatically into the archiving of SXP documents. Please do the entries with record item numbers
starting with 9000. Then SAP guarantees that the entries wont be overwritten by standard entries coming
in a support package or a new release.

13
 4 Using field
extensions
It is also possible to enhance the SSP or SDP by single fields.

However, in contrast to table extensions, there is no tool support offered on ERP-side for field extensions:
The program RPSSC00_GENERATE_AET_DATA (described below) only supports table extensions.

After having generated fields with AET, you have to enhance the delivered CI_ includes of the
corresponding structures on header or item level on ERP-side manually using appends.

14