Kony CRM - Sales Business Connector Installation Guide

Kony

CRM - Sales

Business Connector

Installation Guide

Release 02.02Document Relevance and Accuracy

This document is considered relevant to the Release stated on this title page and the document version stated on the Revision History page.

Remember to always view and download the latest document version relevant to the software release you are using.

© 2014 by Kony, Inc. All rights reserved 1 of 171

Kony CRM BC Install GuideVersion2.2

Copyright © 2014 by Kony, Inc.

All rights reserved.

March, 2015

This document contains information proprietary to Kony, Inc., is bound by the Kony license agreements andmay not be used except in the context of understanding the use andmethods of Kony Inc, software withoutprior, express, written permission. Kony, Empowering Everywhere, Kony MobileFabric, Kony Modeler, andKony Visualizer are trademarks of Kony, Inc. Microsoft, theMicrosoft logo, Internet Explorer, Windows, andWindows Vista are registered trademarks of Microsoft Corporation. Apple, the Apple logo, iTunes, iPhone, iPad,OS X, Objective-C, Safari, and Xcode are registered trademarks of Apple, Inc. Google, the Google logo,Android, and the Android logo are registered trademarks of Google, Inc. Chrome is a trademark of Google, Inc.BlackBerry, PlayBook, Research in Motion, and RIM are registered trademarks of BlackBerry. All other terms,trademarks, or servicemarks mentioned in this document have been capitalized and are to be considered theproperty of their respective owners.



Revision History

Date DocumentVersion

Description of Modifications/Release

11/18/2014 2.2 Updated Data Profiles, ECS Processes,

Customer Extensibility Configuration for

02.02 Release.

09/15/2014 2.1 Added Data Profile Extensibility for 02.01

Release.

07/30/2014 2.0 Document Release for Kony SAP CRM

Business Connector installation.



Table of Contents

1. Preface 6

1.1 Purpose 6

1.2 Intended Audience 6

1.3 Formatting Conventions 6

1.4 Contact Us 8

2. SAP Environment Prerequisites 9

3. Installing Kony CRM - Sales Business Connector 10

3.1 Importing the Standard SAP Transport 11

3.2 Running the Check-Install Process 14

3.3 Verifying KonyCRM - Sales BusinessConnector Configurations 21

3.4 Verifying KonyCRM - Sales BusinessConnector ProcessRules 100

3.5 Implementing Business Add-In (BAdI) for Extract 116

4. Installing Kony CRM Business Connector - ECC Interface 124

4.1 Importing the Standard SAP Transport 125

4.2 Running the Check-Install Process 126

4.3 Verifying KonyCRMBusinessConnector - ECC Interface Configurations 127

5. Working with Customer Extensions 146

5.1 Implementing a Customer-Include Structure 146

5.2 Implementing a BADI Method (Business Add-in) 153

5.3 Maintaining a Customer Extensibility Configuration 160



5.4 Maintaining Data Profile Extensibility Configuration 163

6. Working with Customer Extensions - ECC Interface 165

6.1 Implementing a Customer-Include Structure 165

6.2 Implementing a BADI Method (Business Add-in) 166

6.3 Maintaining Customer Extensibility Configuration 168

7. Appendix: Namespace Repair 171


1. Preface Kony CRM BC Install GuideVersion2.2

1. Preface

Customer RelationshipManagement provides best-in-class functionality for marketing, sales and

service. It supports customer-facing business processes acrossmultiple interaction channels. SAP

Customer RelationshipManagement enables organizations to focus on strategies for customer-driven

growth to provide a superior customer experience.

A BusinessConnector refers to prepackagedmobile application interfaces. Every Business

Connector corresponds to a specific functional area in SAP.

The KonyCustomer RelationshipManagement (CRM) BusinessConnector provides a pre-packaged

support for Activity, Opportunity and Business partner management integration using Data, and

Integration objects.

KonyCustomer RelationshipManagement BusinessConnector - Sales (CRMSales) Installation

Guide provides installation and configuration instructions for Kony SAP CRM - Sales Business

Connector for EnterpriseMobility into a SAP environment.

This document also provides instructions to extend the standard BusinessConnector functionality if

the customer requires.

1.1 Purpose

This document describes how to install KonyCustomer RelationshipManagement Business

Connector - Sales (CRMSales).

1.2 Intended Audience

This document is intended for Basis Administrators who are responsible for installing KonyCustomer

RelationshipManagement - Sales BusinessConnector. It is assumed that the add-in is already

installed into SAP.

1.3 Formatting Conventions

Following are the formatting conventions used throughout the document:



Convention Explanation

Convention Explanation

Monospace n User input text, system prompts, and responses

n File path

n Commands

n Program code

n File names.

Italic n Emphasis

n Names of books and documents

n New terminology.

Bold n Windows

n Menus

n Buttons

n Icons

n Fields

n Tabs.

URL Active link to a URL

Note Provides helpful hints or additional information

Important Highlights actions or information that might cause problems to

systems or data


http://a/


1.4 Contact Us

Wewelcome your feedback on our documentation.Write to us at [email protected].

For technical questions, suggestions, comments or to report problems on Kony product line, contact

[email protected].


mailto:[email protected]?subject=Documentation Feedback

mailto:[email protected]

2. SAP Environment Prerequisites Kony CRM BC Install GuideVersion2.2

2. SAP Environment Prerequisites

Read this information to understand the SAP environment prerequisites. Before you install KonyCRM

BusinessConnector, make sure that your computer meets the following software requirements.

Component Requirement

SAP add-in 24.04.03, and above

SAP CRM 7.1, and above

Note: A high level knowledge of functionality is essential. Youmay refer Kony for SAP Technical

Library on KonyDeveloper Portal for more information.


http://developer.kony.com/KonyForSAP

3. Installing Kony CRM - Sales Business Connector Kony CRM BC Install GuideVersion2.2

3. Installing Kony CRM - Sales Business Connector

The KonyCRMBusinessConnector installation involves a number of steps. You have to perform the

following procedures to install the KonyCRM (Sales) BusinessConnector:

1. Importing the Standard SAP Transport

2. Running the Check Install Process

3. Verifying KonyCRM - Sales BusinessConnector Configurations

4. Verifying KonyCRM - Sales BusinessConnector ProcessRules

5. Implementing Business Add-In (BAdI) for Extract

Note: All objects utilize the SAP registered /SKYTECH/ namespace so there is no impact on

existing SAP, and Customer objects.



3.1 Importing the Standard SAP Transport

The KonyCRMBusinessConnector is provided as a zip file that contains a standard SAP transport.

Typically, two transport files (K######.SCT andR######.SCT) are provided in the zip that you

need to copy to the standard SAP transport library in binarymode. The corresponding target folders

to copy the transport files are, /usr/sap/trans/cofiles, and

/usr/sap/trans/data.

You then use the standard SAP transport system (for example, TP, STMS, Third Party software) to

import the software into the relevant SAP environment. SAP Basis support should be able to import

the software into the relevant SAP environment.

Note: You need to copy the transport files to the SAP trans directories in binarymode to avoid

possible corruption. In UNIX, youmay need to ‘chmod’ each file for the SAP TP utility to read the

contents.

To import using the SAP Transport Management System (STMS) in the CRM SAP system,

follow the steps using an authorized user id:

1. Log on to the CRMSAP system.



2. Run the transaction STMS.

3. Click Import Overview (F5) icon on the toolbar.

The Number of import queues:<number> appears.

4. Select the target system <System ID>, and double-click.

The requests for the target system appear.

5. Go to Extras > Other Requests > Add.

The Add Transport Request to Import Queue dialog appears.

6. Enter the transport request. For example, ERTK######.

The Add Transport Request appears asking to attach the new transport request to the queue of

the target system <System ID>.

7. Click Yes.



8. Highlight the new request, go to Request > click Import.

The Import Transport Request dialog appears.

9. Enter the target client <number> in Target Client, and under the Options tab > Import

Options, select all the options by selecting all the check boxes.

Note: The SAP Transport Management System (STMS) optionsmay slightly vary among SAP

releases. The general process is the same.



3.2 Running the Check-Install Process

After you import the KonyCRMBusinessConnector transport into the SAP system and before you

can use it, you need to run the Check Install process. This is a generic utility that installs all the CRM

Data Object, InterfaceObject, Profile definitions and other meta-data that is required. The Check-

Install process utility also checks that all the components are installed correctly and there are no ABAP

syntax and Data Dictionary errors. Youmay run this utility at any time.

The available BusinessConnector is automatically detected for installation when you run the

transaction /SKY/YECI or YECI.

To install the available Business Connector, follow these steps:

1. Log on to SAP system.

2. Run the transaction YECI in the CRMSAP system.

The business connector check-install release version is compared with existing version in the

system (if previously installed).

3. If the business connector check install release version is higher than the existing version or for

the new installation, the Confirmation dialog appears with the option to either install or cancel.



l Click Yes to install the business connector in the system.

n If any errors / warnings occurred during the installation, the Confirmation dialog

appears with the option to continue or cancel as shown below.

n Click No to dis-continue the installation.

A list of errors and / or inconsistencies appear for verification. Youmay re-start the

installation by executing transaction YECI.

n Click Yes to install the business connector (In spite of errors / warnings).

If the installation is successful, the Information dialog appears with themessage,

"Installation successfully completed".

l Click No or Cancel to exit the installation of that particular business connector.

The Confirmation dialog appears as shown above for all the relevant business connectors that

you can install in the system (If the system hasmultiple business connectors).

4. When the BusinessConnector is successfully installed, the business connector registration

information appears on themain screen of the YECI transaction along with the SKY release

information as shown below.



The YECI main screen is context sensitive to start the Check-Install process for the add-in or the

BusinessConnector software. This is an option to install an updated version of the software (in

case if the user has chosen No / Cancel option at the launch time of YECI).

5. Place the cursor in the relevant business connector registration details block and click Check

Install on the application tool bar (marked in red color in the below diagram).



The system starts to install the BC installation.

l If there exists any new versions of the business connector, a Confirmation dialog

appears with the latest version details and an option to install or cancel the business

connector.

n Click Yes to install the new version of business connector in the system.

i. If any errors / warnings occurred during the installation, the Confirmation

dialog appears with the option to continue or cancel as shown below.

ii. Click No to dis-continue the installation.

A list of errors and / or inconsistencies appear for verification. Youmay re-

start the installation by executing transaction YECI.

iii. Click Yes to install the business connector (In spite of error messages or

warningmessages).

If the installation is successful, the Information dialog appears with the

message, "Installation successfully completed".



After successful installation, the Software management workbench window

is updated with the new version of business connector registration details.



iv. Click Cancel to exit the installation of that particular business connector.

l If new version of the BusinessConnector does not exists, the Information dialog appears

with themessage,"Current release of BusinessConnector is already installed".



If you place the cursor outside the relevant business connector check install block or

outside registration details block, the Information dialog appears with themessage,

"Please position the cursor on a correct level for this option".



3.3 Verifying Kony CRM - Sales Business Connector Configurations

After you run the Check Install process, you need to verify or set up additionally the following CRM

Objects:

1. Data Profile

2. Server Profile

3. User Profile

4. ECS Processes

5. ECS Schedules



3.3.1 Data Profile

You use a data profile to determine the data that is required to be synchronized fromSAP to the

device. The data profile works out as delivered. Youmay need to confirm the final configuration based

on your business. Thismay be due to area of responsibility as required by the business process.

The Data profile is assigned to the DOB (Data Object). When it is assigned, the DOB synchronization

uses the rules as configured to determine the data required for synchronization.

To display the data profiles of a group, follow these steps:

1. Run the transaction, YVT4.

The Data Profile Manager dialog appears with the Selection Criteria section.

2. Enter /SKYTECH/CSA in Group and click Execute.

All the data profiles under the group appear.

The following are some of the data profiles that appear under the group:



l Data Profile/SKYTECH/CSA_TXN - Sales Automation Transaction Profile

l Data Profile/SKYTECH/CSA_USER - User Specific Download Profile

l Data Profile/SKYTECH/CSA_REPORTS - Reporting Profile

Note: The default Data Profiles are delivered as part of the BusinessConnector Check-Install.

You need to customize these profiles based on the customer requirements and use instead of the

standard.

3.3.1.1 Data Profile/SKYTECH/CSA_TXN - Sales Automation Transaction Profile

The following steps are the selection criteria for the DOB Data Profile.

Parameter Value

Selection Criteria USER_ID = "&USERID"

Server Level Selection None

User Level Selection *

a. The USER_ID is used by the Data Profiler to download / refresh data to themobile device. It is

currently configured to use the ("&USERID") value configured in the userid configured in the

User Profile.

You can re-configure the attributes and the selection criteria according to customer business

process.

b. The Server / User level selection is configured for all. You can re-configure the Server / User



level selection to use specific server / user according to customer business process.

3.3.1.2 Data Profile/SKYTECH/CSA_USER - User Specific Download Profile

The following steps are the selection criteria for the DOB Data Profile.

Parameter Value

Selection Criteria USER_ID = "&USERID"





a. The USER_ID is used by the Data Profiler to download / refresh data to themobile device. It is

currently configured to use the ("&USERID") value configured in the userid configured in the

User Profile.


process.



The Data Profile of /SKYTECH/CSA_USER:

3.3.1.3 Data Profile/SKYTECH/CSA_REPORTS - Reporting Profile

The following lists the selection criteria for the DOB Data Profile.



Parameter Value

Selection Criteria OPPTY_YEAR GE "2000"



a. TheOPPTY_YEAR is used by the Data Profiler to download / refresh data to themobile device.

It is currently configured to use the ("2000") value.


process.



The data profile of /SKYTECH/CSA_REPORTS:



3.3.1.4 Customising the Data Profile

Youmay customise the created data profile to meet the requirements of the customer environment.

1. Run the transaction YVT4.

The Data Profile Manager dialog appears with the Selection Criteria section.

2. Enter /SKYTECH/CSA in Group and click Execute.

The associated data profiles for the group appear.



3. Place the cursor on each of the data profile that you want to copy and click Copy on the

Application toolbar.

The Copy Data Object dialog appears.

4. Enter a new data profile identifier according to the customer naming convention, for example,

CUSTOMER_SA_REPORTS. Click Copy to continue. Repeat the copy process till you copy

the required data profiles.

a. When you copy all the required data profiles, re-assign the new data profile to a new

customer data profile group. Place the cursor on the new data profile and click Edit on the




TheMaintain Profile dialog appears.



5. Enter a new Group identifier according to the customer naming convention, for example,

CUSTOMER_CSA. Click Save.

The new data profile is re-assigned to the new group.

Note: For more information on configuration, refer to Installation and Upgrade > Installing

a Secure Container > Configuration Options section of Kony for SAP Technical Library on

KonyDeveloper Portal.

6. Tomaintain the rules of the data profile, run the transaction /nYVT4.

The Data Profile Manager appears with Selection criteria.




7. Enter CUSTOMER_CSA in Group, and click Execute.

The associated data profile for the group entered appears.

8. Place the cursor on each of the display nodes, and click Create, Edit, or Delete to complete the

chosen action on the associated rule (s).



9. To update the DOB definition with a custom profile name, run the transaction, YVTD in the SAP

system.

The Data Object (DOB) Workbench appears.



10. Click Execute.

All the data objects appear.



11. Double-click the CSA_TRANSACTION data object.

TheMaintain Data Object (CSA_TRANSACTION) dialog appears with updated profile

names as shown below.



12. To use custom data profiles created through the above procedure, you need to enhance the

corresponding programs to incorporate these profiles. The following table lists the program

nameswith the data profiles and attributes that are used in the current release.



DOB Program name Data profile Attributes DOBFunction

CSA_

TRANSACTION

/SKYTECH/CSA_

ACTIVITY_

MAINTAIN

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

ACTIVITY_

EXTRACT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

OPPORTUNITY_

EXTRT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

OPPORTUNITY_

MAINT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

LEADS_

EXTRACT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

LEADS_

MAINTAIN

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

CUSTREQ_

EXTRACT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

CUSTREQ_

MAINTAIN

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R



DOB Program name Data profile Attributes DOBFunction

CSA_

TRANSACTION

/SKYTECH/CSA_

PARTNER_

MAINTAIN

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

PARTNER_

EXTRACT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

TENDER_

EXTRACT

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

CSA_

TRANSACTION

/SKYTECH/CSA_

TENDER_

MAINTAIN

/SKYTECH/CSA_

TXN

USER_

ID

D/U/R

Note: The abbreviations displayed in the DOB Function column are download (D), refresh

(R), upload (U).

13. To use the customized data profile in the existing BC programs, maintain custom data profile

against the DOB in the data profile extensibility configuration table (/SKYTECH/CSA_DPF).

14. To add or modify attributes that need to be passed to the custom data profile, you have to

implement the BADI (refer to Implementing Business Add-In (BAdI) for Extract) defined for

corresponding program. Refer to BADI Definitions andMethods for more information. Maintain

the /SKYTECH/CSA_EXT table with BADI class andmethod details against AT_DATA_

PROFILE enhancement point.



Note: Refer to Maintaining Data Profile Extensibility Configuration section tomaintain

configuration of the data profile extensibility andMaintaining a Customer Extensibility

Configuration section to know how tomaintain the configuration tables.

15. Fill in the attributes table inside the BADI method AT_DATA_PROFILE and pass back to the

calling program. The following example shows the input parameters of the BADI method and

code snippet for filling the attributes inside BADI.



16. The calling program handles refreshing (uploading or downloading) the profile using the

attributes table.



3.3.2 Server Profile

You use a server profile to control the configuration that a device uses to connect with SAP.

Note: A default Server Profile is delivered as part of the BusinessConnector Check-Install. You

are recommended to use a copy of the default Server Profile to avoid custom configuration

overwritten in the subsequent Check-Install run.

To copy the server profiles, follow these steps:

1. Run the transaction YVT5 in the CRMSAP system.

The Server Profile Manager appears with the Selection criteria section:

2. Enter VTI_SAMPLE_SKYSYNC in Profile, and click Execute.



All the profiles and platforms under the entered profile appear.



3. Place the cursor on the profile name VTI_SAMPLE_SKYSYNC, and click Copy on the

application toolbar.

The Copy Profile (VTI_SAMPLE_SKYSYNC) dialog appears.

4. Enter a name that conforms to the customer custom naming convention. Click Copy.

A new Server Profile is created.

5. Youmay customize the created new Server Profile to meet the requirements of the customer

environment.

3.3.2.1 Customizing the Server Profile


The Server Profile Manager appears with Selection criteria.



2. Enter /SKYTECH/CSA in Profile, and click Execute.

The profile entered appears.

3. Expand the Instances node > *Master instance > Configuration > CLIENT >

IDENTITYCHECK.

The default Server Profile contains configuration that uses the SKY Identity check service. If you

require a different service, enter the service name that corresponds to the setup in the Sky

Gateway configuration.



For more information on configuration, refer to Installation and Upgrade > Installing a Secure

Container > Configuration Options section of Kony for SAP Technical Library on Kony

Developer Portal.





3.3.3 User Profile

You use a user profile to define amobile user login credentials and the associated roles when you

provision the application.

Note: A default User Profile is delivered as part of the BusinessConnector Check-Install. It is

advisable that the customer uses a copy of the default User Profile to avoid custom configuration

overwritten in the subsequent Check-Install run.


The User Profile Manager dialog appears with the Selection criteria section.

2. Enter CUSTOMER_CSA in Role, and click Execute.

All the user profiles that you entered in the role, appear.



3. Place the cursor on the role name /SKYTECH/CSA, and click Copy on the application toolbar.

The Copy Role dialog appears.

4. Enter a name that conforms to the customer custom naming convention. Click Copy on the

application tool bar.



A new User Profile is created.

Note: A default User Profile is delivered as part of the BusinessConnector Check-Install. You

need to customize these profiles as per the customer requirements and use instead of the

standard.

3.3.3.1 Customizing the User Profile

After you create a new User Profile, you can customize it to meet the requirements of the customer

environment.


The User Profile Manager appears with Selection criteria.

2. Enter CUSTOMER_CSA in Role, and click Execute.

The roles entered appear.



3. Create a newWork group and users.

a. Expand theWork group node > *Work groups and users > Work group > DEMO_CSA.

The expanded user credentials appear.

b. Place cursor onWork groups and users and click Create on the Application toolbar.

TheMaintain Work Group dialog appears.



c. Enter a name for the newWork group and click Save.

A new work group is created.

For example:

Work group CUSTOMER_CSA

Description

Customer

CRM Salesforce

d. Create new user for theWork group. Place the cursor on the new work group and click

the Create on the Application toolbar.

TheMaintain User dialog appears.



e. Maintain user login credentials and default parameters. Enter all the required customer

login credentials and click Parameter Values.

TheMaintain Parameter Values dialog appears.



f. Maintain the user Parameter Values. The following are some of the parameters

associated with the user and the values correspond to the customer organizational setup.

You can use these values as substitution parameters of Data Profiles.



COUNTRY AU

CURRENCY AUD

DIST_CHANNEL 10

LANGUAGE EN

ORG_UNIT O 50000003

PARTNER_ID 0000400000

SALES_GROUP O 50000003

SALES_OFFICE O 50000002

SALES_ORG O 50000001

g. Assign the newWork group to the new Role. Place the cursor onWork groups and click

Create on the Application toolbar.



TheMaintain Work Group() dialog appears.



h. Enter the newWork group, CUSTOMER_CSA and click Save.

The work group is assigned to the Role.

i. Un- assign the sample work group, /SKYTECH/CSA from the new Role. Expand the

Roles node > Work groups > and place the cursor on the work group

/SKYTECH/CSA, and click the Delete on the Application toolbar.

j. Activate the new role. Place the cursor on the new role and click Activate on the




The role is activated and ready for use.



3.3.4 ECS Processes

Create the required variants for the ABAP programs.

To create variants for the ABAP programs in CRM system, follow these steps:

1. Log on to the CRMSAP system.

2. Run the transaction YECW.

The Process Workbench dialog appears with Process selection.



3. Enter /SKYTECH/CSA in Process group, and click Execute.

All the process and phase definitions you entered in the process group appear.



Below are the ECS processes that require a variant configuration in CRM system. Generate

variants for the following ecs processes:

l ECS ProcessCSA_CREATE_ORDER - Create Order

l ECS ProcessCSA_ORDER_SYNC - SalesOrder Sync fromECC

l ECS ProcessCSA_ORDERMSG_SYNC - Order Msg Sync fromECC

l ECS ProcessCSA_EXTRACT_ACTCAT- Extract Activity Categories

l ECS ProcessCSA_EXTRACT_BPGROUPS - Extract Partner Groups

l ECS ProcessCSA_EXTRACT_BPSUBGRP - Extract Partner SubGroups

l ECS ProcessCSA_EXTRACT_CITY - Extract Cities



l ECS ProcessCSA_EXTRACT_COUNTRY - Extract Countries

l ECS ProcessCSA_EXTRACT_CURCODES - Extract CurrencyCodes

l ECS ProcessCSA_EXTRACT_DISTRICT- Extract Districts

l ECS ProcessCSA_EXTRACT_DPTMT - Extract Departments

l ECS ProcessCSA_EXTRACT_JOBFUN - Extract Positions of Contact Person

l ECS ProcessCSA_EXTRACT_REGION - Extract Regions

l ECS ProcessCSA_EXTRACT_TITLE - Extract Title

l ECS ProcessCSA_EXTRACT_ATRIBUTE - Extract Attributes

l ECS ProcessCSA_CUSTOMER_SYNC - Customer Sync fromECC

l ECS ProcessCSA_CUSTCREDIT_SYNC - Customer Credit Sync fromECC

l ECS ProcessCSA_EXCLUDSN_SYNC - Prices / FreeGoods Excl Cond Sync from

ERP

l ECS ProcessCSA_PAYTERM_SYNC - Payment TermSync fromECC

l ECS ProcessCSA_PRICE_SYNC - Price Sync fromECC

l ECS ProcessCSA_PRICE_SYNC_682I - Price Sync fromECC

l ECS ProcessCSA_PRICE_SYNC_682Z - Price Sync fromECC

l ECS Process SA_PRICE_SYNC_ITM - Price Sync fromECC

l ECS ProcessCSA_PRICE_SYNC_SCAL - Price Sync fromECC

l ECS ProcessCSA_PRODUCT_SYNC - Price Sync fromECC

l ECS ProcessCSA_HOUSEKEEP_ORREF - Housekeeping Upload Control GUID Link



3.3.4.1 Generating Variants for ECS Process CSA_CREATE_ORDER - Create Order

Parameter Value

Phase PHASE_0001

ABAP

Pgm

/SKYTECH/CSA_ORD_UPLD_

TO_ERP

Variant ORDER_UP_ERP

Exec

Mode

SERVER

a. Open the node <ECS Process CSA_CREATE_ORDER> > 001 PHASE_001.

Note: Here, the node <ECS Process CSA_CREATE_ORDER> is the place holder for the

ECS Process CSA_CREATE_ORDER - Create Order to generate the variants.

Consider the node of the respective ecs process for which you want to generate the

variants.

b. From the Execute ABAP object node, copy the ABAP program, /SKYTECH/CSA_ORD_

UPLD_TO_ERP and click Creates New Session in the tool bar.

A new session appears.

c. Run the transaction SE38.

The Subobjects for the ABAP program, /SKYTECH/CSA_ORD_UPLD_TO_ERP appear.



d. Paste the ABAP program (/SKYTECH/CSA_ORD_UPLD_TO_ERP) that you copied in

Program, select the Variants option, and click Display.

The following dialog appears.

e. Enter ORDER_UP_ERP in Variant and click Create.

The Edit Variants dialog appears.



Variants

Parameter Value

DOB Name CSA_DO_ERP_ORDER_

SYNC

Order Ref

Number

' '

f. LeaveOrder Ref. Number blank, enter CSA_DO_ERP_ORDER_SYNC in DOB Name, and

then click Attributes.

The Variant Attributes dialog appears.



g. Enter description for the variant in Meaning, and then click Save.

Similarly, generate variants for the below ECS processeswith the information given in tables:

3.3.4.2 ECS Process CSA_ORDER_SYNC - Sales Order Sync from ECC

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_DOB_SYNC_

FROM_ERP

Variant SLSORD_SYNC

Exec Mode SERVER

Variants



Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_ORDER_SYNC

DOB for

Device Sync

CSA_TRANSACTION

Server

Command

DOBREFRESH

Server

Group

*

Server ID *

3.3.4.3 ECS Process CSA_ORDERMSG_SYNC - Order Msg Sync from ECC

Parameter Value

Phase PHASE_0001



Parameter Value

ABAP Pgm /SKYTECH/CSA_DOB_SYNC_FROM_

ERP

Variant ORDMSG_SYNC

Exec Mode SERVER

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_ORDER_MSG_SYNC

DOB for

Device Sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *



3.3.4.4 ECS Process CSA_EXTRACT_ACTCAT- Extract Activity Categories

Parameter Value

Phase EXTRACT_ACTCAT

ABAP Pgm /SKYTECH/CSA_ACTCAT_EXTRACT

Variant /SKYTECH/LANGU

Exec Mode JOB

Variants

Parameter Value

Language Key EN



3.3.4.5 ECS Process CSA_EXTRACT_BPGROUPS - Extract Partner Groups

Parameter Value

Phase EXTRACT_BPGROUPS

ABAP Pgm /SKYTECH/CSA_BPGROUP_EXTRACT


Exec Mode JOB

Variants

Parameter Value

Language Key EN

3.3.4.6 ECS Process CSA_EXTRACT_BPSUBGRP - Extract Partner Sub Groups

Parameter Value

Phase EXTRACT_BPSUBGROUPS

ABAP Pgm /SKYTECH/CSA_BPSUBGROUP_

EXTRCT




Parameter Value

Exec Mode JOB

Variants

Parameter Value

Language Key EN

3.3.4.7 ECS Process CSA_EXTRACT_CITY - Extract Cities

Parameter Value

Phase EXTRACT_CITY

ABAP Pgm /SKYTECH/CSA_CITY_EXTRACT


Exec Mode JOB

Variants

Parameter Value

Language Key EN



3.3.4.8 ECS Process CSA_EXTRACT_COUNTRY - Extract Countries

Parameter Value

Phase EXTRACT_COUNTRY

ABAP Pgm /SKYTECH/CSA_COUNTRY_EXTRACT


Exec Mode JOB

Variants

Parameter Value

Language Key EN



3.3.4.9 ECS Process CSA_EXTRACT_CURCODES - Extract Currency Codes

Parameter Value

Phase EXTRACT_CURCODES

ABAP Pgm /SKYTECH/CSA_CURCODE_EXTRACT


Exec Mode JOB

Variants

Parameter Value

Language Key EN

3.3.4.10 ECS Process CSA_EXTRACT_DISTRICT - Extract Districts

Parameter Value

Phase EXTRACT_DISTRICTS

ABAP Pgm /SKYTECH/CSA_DISTRICT_EXTRACT




Parameter Value

Exec Mode JOB

Variants

Parameter Value

Language Key EN

3.3.4.11 ECS Process CSA_EXTRACT_DPTMT- Extract Departments

Parameter Value

Phase EXTRACT_DEPARTMENTS

ABAP Pgm /SKYTECH/CSA_DEPARTMENT_

EXTRCT


Exec Mode JOB

Variants

Parameter Value

Language Key EN



3.3.4.12 ECS Process CSA_EXTRACT_JOBFUN - Extract Positions of Contact Person

Parameter Value

Phase EXTRACT_JOBFUN

ABAP Pgm /SKYTECH/CSA_JOBFUN_EXTRACT


Exec Mode JOB

Variants

Parameter Value

Language Key EN

3.3.4.13 ECS Process CSA_EXTRACT_REGION - Extract Regions

Parameter Value

Phase EXTRACT_REGION



Parameter Value

ABAP Pgm /SKYTECH/CSA_REGION_EXTRACT


Exec Mode JOB

Variants

Parameter Value

Language Key EN

3.3.4.14 ECS Process CSA_EXTRACT_TITLE - Extract Title

Parameter Value

Phase EXTRACT_TITLE

ABAP Pgm /SKYTECH/CSA_TITLE_EXTRACT


Exec Mode JOB

Variants



Parameter Value

Language Key EN

3.3.4.15 ECS Process CSA_EXTRACT_ATRIBUTE - Extract Attributes

Parameter Value

Phase EXTRACT_ATTRIBUTES

ABAP Pgm /SKYTECH/CSA_ATTRIBUTE_

EXTRACT

Variant /SKYTECH/ATTR

Exec Mode JOB

Variants

Parameter Value

Class Type BUP

Class Group MKT_PT

RESP

Test Mode Select or clear the check box



3.3.4.16 ECS Process CSA_CUSTOMER_SYNC - Customer Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant CUSTOMER_SYNC

Exec Mode JOB

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_CUSTOMER_SYNC



Parameter Value

DOB for

Device Sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *

3.3.4.17 ECS Process CSA_CUSTCREDIT_SYNC - Customer Credit Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant CUSTCRDT_SYNC

Exec Mode JOB



Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_CUST_CREDIT_SYNC

DOB for

Device Sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *



3.3.4.18 ECS Process CSA_EXCLUDSN_SYNC- Prices / Free Goods Excl Cond Sync from ERP

Parameter Value

Phase PHASE_0001


ERP

Variant EXCLUDSN_SYNC

Exec Mode JOB

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_EXCLUDSN_SYNC

DOB for

Device Sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *



3.3.4.19 ECS Process CSA_PAYTERM_SYNC - Payment Term Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant PAYTERM_SYNC

Exec Mode JOB

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_PAYTERM_SYNC

DOB for

Device Sync



Parameter Value

Server

Command

DOBREFRESH

Server

Group

*

Server ID *

3.3.4.20 ECS Process CSA_PRICE_SYNC - Price Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant PRICE_SYNC

Exec Mode JOB

Variants



Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_ERP_PRICE_SYNC

DOB For

device sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *

3.3.4.21 ECS Process CSA_PRICE_SYNC_682I - Price Sync from ECC

Parameter Value

Phase PHASE_0001



Parameter Value


ERP

Variant PRICE_SYNC682I

Exec Mode JOB

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB

CSA_DO_PRICING

DOB For device

sync

Server

Command

DOBREFRESH

Server Group *

Server ID *



3.3.4.22 ECS Process CSA_PRICE_SYNC_682Z - Price Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant PRICE_SYNC682Z

Exec Mode JOB

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB


DOB For

device sync



Parameter Value

Server

Command

DOBREFRESH

Server

Group

*

Server ID *

3.3.4.23 ECS Process CSA_PRICE_SYNC_ITM - Price Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant PRICE_SYNC_ITM

Exec Mode JOB

Variants



Parameter Value

RFC

Destination

RFC

Destination

DOB


DOB For

device sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *

3.3.4.24 ECS Process CSA_PRICE_SYNC_SCAL - Price Sync from ECC

Parameter Value

Phase PHASE_0001



Parameter Value


ERP

Variant PRICE_SYNCSCAL

Exec Mode JOB

Variants

Parameter Value

RFC

Destination

RFC

Destination

DOB


DOB For

device sync

Server

Command

DOBREFRESH

Server

Group

*

Server ID *



3.3.4.25 ECS Process CSA_PRODUCT_SYNC - Price Sync from ECC

Parameter Value

Phase PHASE_0001


ERP

Variant PRODUCT

Exec Mode JOB

3.3.4.26 ECS Process CSA_HOUSEKEEP_SAORREF - Housekeeping Upload Control GUID Link

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_HOUSEKEEP_

SAORREF

Variant RETENTION_DAYS

Exec Mode JOB

Variants



Parameter Value

RETENTION_

DAYS

30

3.3.4.27 Customizing Variants for ECS Processes

You can copy existing variants and use them in the ECS processes using the following procedure. The

variant for the ECS process, CSA_CREATE_ORDER (Program: /SKYTECH/CSA_ORD_UPLD_

TO_ERP) is used as an example here.

To copy existing variants and use them in the ECS processes, follow these steps:

1. Open the node CSA_CREATE_ORDER > 0001 PHASE_0001.

2. From the Execute ABAP object node, copy the ABAP program, /SKYTECH/CSA_ORD_

UPLD_TO_ERP and click Create.

A new session appears.

3. Run the transaction SE38 in SAP.

The Subobjects for the ABAP program, /SKYTECH/CSA_ORD_UPLD_TO_ERP appear.



4. Paste the ABAP program (/SKYTECH/CSA_ORD_UPLD_TO_ERP) that you copied in

Program. Select the Variants option, and click Display.

The ABAP: Variants - Initial Screen dialog appears.

5. Place the cursor in Variant and press F4.

The existing variant names appear.



6. Select the existing Variant and press Enter.

The ABAP: Variants - Initial Screen window appears.

7. Click Copy tomake a copy of the existing variant.

The ABAP: Copy Variants dialog box appears.



8. Enter the Variant name based on Customer naming convention, and press Enter.

Once the variant is successfully copied, the confirmationmessage,"ORDER_UP_ERP copied

to ORDER_UPLOAD" appears.



9. Click Change to customize the variant parameter value based on Customer requirement.

TheMaintain Variant window appears.

10. Change the parameter values in the respective fields based on the customer requirement.

11. Click Variant Attributes.

The Variant Attributes window appears.



12. Provide proper description for the variant, enter a description for the variant Meaning and click

Save.

13. You need to attach the newly created variant to the corresponding ECS. Go to transaction

YECW, enter CSA_CREATE_ORDER as process name and click Execute.

14. Open the node CSA_CREATE_ORDER > 0001 PHASE_0001 and double-click PHASE_

0001.

The Process Workbench dialog appears.



15. ClickObject definition.

The ECS: Change ABAP object window appears.



16. Replace the already existing variant namewith the newly created variant name, ORDER_UP_

ERP and press Enter.

The Change Phase PHASE_0001 for Process <Process Name> window appears.



17. Click Save to successfully attach the newly customized variant to the ECS and close the

window.



3.3.5 ECS Schedules

To verify the scheduled ECS processes, follow these steps:

1. Run the transaction YECT in the CRMSAP system.

The Schedule Workbench appears with the Schedule selection.

2. Enter /SKYTECH/CSA in Schedule group, and click Execute.

All the scheduled ECS process definitions in the schedule group that you entered, appear.



3. Deactivate (Ctrl + F2) any ECS schedules that are not required.



4. Maintain the scheduled start date and time for each request as required.



3.4 Verifying Kony CRM - Sales Business Connector Process Rules

Follow these steps to verify CRM - Sales BusinessConnector process rules:

1. Partner Functions

2. Partner Function Relationships

3. Document Codes

4. Status Codes

5. CRMOrder Extract Control

6. Business Partner Extract Control



3.4.1 Partner Functions

Use the SAP table /SKYTECH/CSA to define the rules to displaymandatory partners for each CRM

transaction (activity / opportunity / lead /customer request / tender ) and the sort sequence of the

partners.

To define the rules to display mandatory partners for each CRM transaction and the sort

sequence of the partners, follow these steps:

1. Run the CRMSales Automation transaction /SKYTECH/CSA in the CRMSAP system.

The CRM Sales Automation dialog appears.

2. Click theMaster Data tab > Partner Functions.

The following window appears.



3. Enter the details for the keymandatory fields as shown in the table below.

Field Name Description

PARTNER_FCT Partner function

4. Ensure that the entered data is similar to that displayed in the Change View "Partner

functions": Overview table.

5. You can edit the data using the Change > Display (Cltr + F4) button or create new entries

using the New Entries option on the toolbar.



3.4.2 Partner Function Relationships

Use the SAP table /SKYTECH/CSAPTFM to define / map the partner function relationships for each

partner function.

To define / map the partner function relationships for each partner function, follow these steps:



2. Click theMaster Data tab > Partner FunctionMapping.






PARTNER_

FCT

Partner Function

PARTNER_

TYPE

Business Partner Category

PARTNER_

ROLE

Partner Role

4. Ensure that the entered data is similar to that displayed in Change View "Partner Functions

Relationship Type Mapping": Overview table.





3.4.3 Document Codes

Use the SAP table /SKYTECH/CSAORCD to specify document code for each transaction type. A

document code tells whether the transaction type is an opportunity or a customer inquiry.

To specify the document code for each transaction type, follow these steps:



2. Click theMaster Data tab > Document Codes.





Field Name Field Description

PROCESS_

TYPE

Business Transaction Type

CODE_TYPE Code Type

DOCUMENT_

CODE

Code

4. Ensure that the entered data is similar to that displayed in Change View "Document Codes

Table": Overview table.







3.4.4 Status Codes

Use the SAP table /SKYTECH/CSATTSA to specify status codes for each transaction type.

To specify status codes for each transaction type, follow these steps:



2. Click theMaster Data tab > Status Codes.






PROCESS_

TYPE





STATUS_

NO

User status

STATUS_

DESC

Object status

4. Ensure that the entered data is similar to that displayed in Change View "Transaction Status

Codes Table": Overview table.





3.4.5 CRM Order Extract Control

Use the SAP table /SKYTECH/CSAOREX to specify rules to extract data for each transaction type.

To specify rules to extract data for each transaction type, follow these steps:



2. Click the Config Data tab > CRM Order Extract Control.






OBJECT_

TYPE

Business Object Type

PROCESS_

TYPE


SALES_

ORG

Sales Organization ID

SALES_

OFFICE

Sales Office ID




SALES_

GROUP

Sales Group ID

4. Ensure that the entered data is similar to that displayed in Change View "CRM Order Extract

Control": Overview table.





3.4.6 Business Partner Extract Control

Use the SAP table /SKYTECH/CSABPEX to specify rules to extract data for any business partner.

To specify rules to extract data for any business partner, follow these steps:



2. Click the Config Data tab > Business Partner Extract Control.





Field Name Field Description

PARTNER_

TYPE

Business Partner Category

PARTNER_

ROLE

Partner Role

SALES_ORG Sales Organization ID

SALES_

OFFICE

Sales Office ID

SALES_

GROUP

Sales Group ID

4. Ensure that the entered data is similar to that displayed in Change View "Business Partner

Extract Control": Overview table.





3.5 Implementing Business Add-In (BAdI) for Extract

You require an SAP Business Add-In (BAdI) to trigger the extraction of CRMTransactions. As BAdIs

are a form of configuration in an SAP system, a BAdI implementation is not provided as part of the

CRMBusinessConnector transport. Consequently, you need to create the BAdI implementation in

the customer environment.

You need to the following BAdIs:

1. Creating a BAdI for CRMOrder (Activity, Opportunity, and Lead) Extract

2. Creating a BAdI for Business Partner Extract



3.5.1 Creating a BAdI for CRM Order (Activity, Opportunity, and Lead) Extract

To create a BAdI for CRM order (Activity, Opportunity, and Lead) Extract, follow these steps:

1. Run the transaction SE18 in the CRMSAP system.

The BAdI Builder: Initial Screen for Definitions appears.

2. Enter ORDER_SAVE in BAdI Name.

Note: TheORDER_SAVE is a standard BAdI that is triggered whenever a CRMorder is

saved.



3. Go to tool bar, click Enhancement Implementation > click Create.

The Business Add-In Builder: Create Implementation dialog appears.

4. Enter name of the implementation in Implementation Name, and click the green tickmark.

Note: Provide Implementation name according to custom development naming convention.

TheObject Editing: Initial Screen appears with the followingmessage:



5. Click the green tickmark.

The Business Add-In Builder: Change Implementation <Implementation Name> dialog

appears.

6. Enter a short description in Implementation Short Text.

7. On the Interface tab, enter name of the implementing class in Name of implementing class.

Note: KonyCRMBC is delivered with the class /SKYTECH/CSA_ORDER_SAVE as

standard for ORDER_SAVE BADI. You can choose to use this.



8. Provide /SKYTECH/CSA_ORDER_SAVE in Name of Implementing class. Youmay also

copy the class and use it.

9. Go to tool bar, click Activate business add-in implementation (Ctrl + F3) to activate the BAdI

implementation.

10. Test the Order extract trigger:

o Create an activity in SAP CRM

o Check the ECS process for CSA_EXTRACT_ACTIVITY run

o Check the DOB CSA_TRANSACTION for the data extract.



3.5.2 Creating a BAdI for Business Partner Extract

To create a BAdI for Business Partner Extract, follow these steps:


The BAdI Builder: Initial Screen for Definitions dialog appears.

2. Enter PARTNER_UPDATE in BAdI Name.

Note: The PARTNER_UPDATE is a standard BAdI that is triggered whenever a business

partner is saved.





4. Enter name of the implementation in Implementation Name and click the green tickmark.

Note: Provide Implementation name according to custom development naming convention.

TheObject Editing: Initial Screen appears with the followingmessage:

5. Click the green tickmark.


appears.



6. Enter a short description in Implementation Short Text.

7. On the Interface tab, enter name of the implementing class in Name of implementing class.

Note: KonyCRMBC is delivered with the class /SKYTECH/CSA_PARTNER_

EXTRACTas standard for PARTNER_UPDATE BADI. You can choose to use this.

8. Provide /SKYTECH/CSA_PARTNER_EXTRACT in Name of implementing class. Youmay

also copy the class and use it.

9. Go to tool bar, click Activate business add-in implementation (Ctrl + F3) to activate the BAdI

implementation.

10. Test the Partner extract trigger:

o Create an account/contact in SAP CRM

o Check the ECS process for CSA_EXTRACT_PARTNER run

o Check the DOB CSA_TRANSACTION for the data extract.


4. Installing Kony CRM Business Connector - ECC Interface Kony CRM BC Install GuideVersion2.2

4. Installing Kony CRM Business Connector - ECC Interface

Note: You need to perform the procedurementioned in this section only if the customer wants to

interface with the ECC system for the following functionality:

1. Order Creation

2. Material Extract

3. Customer Extract

4. Pricing Extract

5. Payment TermsExtract.

The KonyCRMBusinessConnector – ECC Interface installation involves a number of steps. You have

to perform the following procedures to install the KonyCRMBusinessConnector ECC Interface:

1. Importing the Standard SAP Transport

2. Running the Check Install Process

3. Verifying KonyCRMBusinessConnector Configurations - ECC Interface Configurations

Note: All objects utilize the SAP registered ‘/SKYTECH/’ namespace and so there is no impact on

existing SAP and Customer objects.



4.1 Importing the Standard SAP Transport

The KonyCRMBusinessConnector – ECC Interface is provided as a zip file that contains a standard

SAP transport. Typically, two transport files (K######.SKT andR######.SKT) are provided in

the zip that you need to copy to the standard SAP transport library in binarymode. The corresponding

target folders to copy the transport files are, /usr/sap/trans/cofiles and

/usr/sap/trans/data.

You then use the standard SAP transport system (for example, TP, STMS, Third Party software) to

import the software into the relevant SAP environment. SAP Basis support should be able to import

the software into the relevant SAP environment.

Note: The procedure for import in the ECC system is the same as described for the CRM system.

Follow the steps outlined in Importing the Standard SAP Transport using the two transport files

specified in the previous paragraph.



4.2 Running the Check-Install Process

After you import the KonyCRMBusinessConnector – ECC Interface transport into the SAP system

and before you can use it, you need to run the Check Install process. This is a generic utility that installs

all the CRMData Object, InterfaceObject, Profile definitions and other meta-data that is required. The

Check-Install process utility also checks that all the components are installed correctly and there are

no ABAP syntax and Data Dictionary errors. Youmay run this utility at any time.

The procedure to run the Check-Install Process in the ECC system is the same as described in the

CRM system. Follow the stepsmentioned in the Running the Check-Install Process section.

Additionally, for customerswith Add-in Release v24.04 and above, the following confirmation appears

in the SoftwareManagementWorkbench Tool (Transaction: YECI) after successful confirmation.



4.3 Verifying Kony CRM Business Connector - ECC Interface Con-

figurations

After you run the Check Install process, you need to verify or set up additionally the following CRM

Objects:

1. ECS Processes

2. ECS Schedules



4.3.1 ECS Processes

Create the required variants for the ABAP programs.

To create variants for the ABAP programs, in ECC system, follow these steps:

1. Log on to the ECC SAP system.

2. Run the transaction YECW in SAP.

The Process Workbench dialog appears with Process selection section.



3. Enter /SKYTECH/CSA in Process group, and click Execute.

All the process and phase definitions in the process group that you entered, appear.

Below are the ECS processes that require a variant configuration in ECC system.

l ECS ProcessCSA_CREATE_ORDER - Create SalesOrder

l ECS ProcessCSA_EXTRCT_ORDR_ECC - Extract SalesOrder Data

l ECS ProcessCSA_ORDER_SYNC - SalesOrder Data Sync to CRM

l ECS ProcessCSA_ORDERMSG_SYNC - SalesOrder Message Sync to CRM

l ECS ProcessCSA_CUSTCREDIT_SYNC - Customer Credit Sync to CRM

l ECS ProcessCSA_CUSTOMER_SYNC - Customer Sync to CRM

l ECS ProcessCSA_PAYTERM_SYNC - Payment TermsSync to CRM

l ECS ProcessCSA_PRICE_SYNC - Pricing Data Sync to CRM

l ECS ProcessCSA_PRODUCT_SYNC - Product Sync to CRM

l ECS ProcessCSA_EXTRACT_CUSTCRDT- Extract Customer Credit Data

l ECS ProcessCSA_EXTRACT_CUST_ALL - Extract Customer Data

l ECS ProcessCSA_EXTRACT_PAYTERM - Extract Payment TermsData

l ECS ProcessCSA_EXTRACT_PRICE_D - Extract Customer Data

l ECS ProcessCSA_EXTRACT_PROD_ALL - Extract Material Master Data

Similarly, generate variants for the below ECS processeswith the information given in tables:



4.3.1.1 ECS Process SA_CREATE_ORDER - Create Sales Order

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_CREATE_

SALESORDER

Variant CREATE_SLSORD

Exec Mode SERVER

Variants

Parameter Value

Sales Document Type

4.3.1.2 ECS Process CSA_EXTRCT_ORDR_ECC - Extract Sales Order Data

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_EXTRACT_

SALESORDER



Parameter Value

Variant EXTRACT_SLSORD

Exec Mode SERVER

Variants

Parameter Value

Document Date

Document Number

4.3.1.3 ECS Process CSA_ORDER_SYNC - Sales Order Data Sync to CRM

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_START_CRM_

PROCESS

Variant SLSORD_SYNC

Exec Mode SERVER

Variants



Parameter Value

Logical

Destination

ECS: Process

Name

CSA_ORDER_SYNC

4.3.1.4 ECS Process CSA_ORDERMSG_SYNC - Sales Order Message Sync to CRM

Parameter Value

Phase PHASE_0001


PROCESS

Variant ORDMSG_SYNC

Exec Mode SERVER

Variants

Parameter Value

Logical

Destination



Parameter Value

ECS:

Process

Name

CSA_ORDERMSG_SYNC

4.3.1.5 ECS Process CSA_CUSTCREDIT_SYNC - Customer Credit Sync to CRM

Parameter Value

Phase PHASE_0001


PROCESS


Exec Mode SERVER

Variants

Parameter Value

Logical

Destination

ECS:

Process

Name

CSA_CUSTCREDIT_SYNC



4.3.1.6 ECS Process CSA_CUSTOMER_SYNC - Customer Sync to CRM

Parameter Value

Phase PHASE_0001


PROCESS


Exec Mode SERVER

Variants

Parameter Value

Logical

Destination

ECS:

Process

Name

CSA_CUSTOMER_SYNC



4.3.1.7 ECS Process CSA_PAYTERM_SYNC - Payment Terms Sync to CRM

Parameter Value

Phase PHASE_0001


PROCESS

Variant PAYTERM_SYNC

Exec Mode SERVER

Variants

Parameter Value

Logical

Destination

ECS:

Process

Name

CSA_PAYTERM_SYNC



4.3.1.8 ECS Process CSA_PRICE_SYNC - Pricing Data Sync to CRM

Parameter Value

Phase PHASE_0001


PROCESS

Variant PRICE_SYNC

Exec Mode SERVER

Variants

Parameter Value

Logical

Destination

ECS: Process

Name

CSA_PRICE_SYNC

4.3.1.9 ECS Process CSA_PRODUCT_SYNC - Product Sync to CRM

Parameter Value

Phase PHASE_0001



Parameter Value


PROCESS

Variant PRODUCT_SYNC

Exec Mode SERVER

Variants

Parameter Value

Logical

Destination

ECS:

Process

Name

CSA_PRODUCT_SYNC

4.3.1.10 ECS Process CSA_EXTRACT_CUSTCRDT - Extract Customer Credit Data

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_EXTRACT_CRDT_

STATU



Parameter Value

Variant CUSTCRDT_EXTR

Exec Mode JOB

Variants

Parameter Value

I_HARD X

4.3.1.11 ECS Process CSA_EXTRACT_CUST_ALL - Extract Customer Data

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_EXTRACT_

CUSMASTER

Variant CUST_EXTRACT

Exec Mode JOB

Variants



Parameter Value

I_HARD X

Customer Number

(range)

4.3.1.12 ECS Process CSA_EXTRACT_PAYTERM - Extract Payment Terms Data

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_EXTRACT_PAYTERM

Variant PAYTERM_EXTR

Exec Mode JOB

Variants

Parameter Value

I_HARD X



4.3.1.13 ECS Process CSA_EXTRACT_PRICE_D - Extract Customer Data

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_EXTRACT_PRICE_

CON

Variant ZDELTA

Exec Mode JOB

Variants

Parameter Value

Usage of the

condition table

A

Procedure RVAA01

Condition Key

Condition Table

Validity Period

Update Select the radio button



Parameter Value

Delete

Delta Load Select the check box

Test Run

List Display

4.3.1.14 ECS Process CSA_EXTRACT_PROD_ALL - Extract Material Master Data

Parameter Value

Phase PHASE_0001

ABAP Pgm /SKYTECH/CSA_EXTRACT_MAT_

MASTR

Variant PROD_ALL

Exec Mode JOB



Variants

Parameter Value

Material

Number

Material Type FERT

I_HARD Select the check box

4.3.1.15 Customizing Variants for ECS Processes

The procedure to customize variants in the ECC system is the same as described for the CRM

system. Follow the stepsmentioned for the same in section Customizing Variants for ECS Processes.



4.3.2 ECS Schedules

To verify the scheduled ECS processes, follow these steps:

1. Run the transaction YECT in the CRMSAP system.

The Schedule Workbench appears with the Schedule selection.

2. Enter /SKYTECH/CSA in Schedule group, and click Execute.

All the scheduled ECS process definitions in the schedule group that you entered, appear.



3. Deactivate (Ctrl + F2) any ECS schedules that are not required.



4. Maintain the Scheduled start date, and time for each request as required.


5. Working with Customer Extensions Kony CRM BC Install GuideVersion2.2

5. Working with Customer Extensions

You can extend the functionality of the standard BusinessConnector to meet customer specific

requirements. This allows the customer to include and use additional fields in the existing tables and

add custom logic at predefined sections of the code using BADIs provided for the same.

The following sections describe inmore detail the steps required to implement customer extensibility:

l Implementing a Customer-Include Structure

l Implementing a BADI Method provided in the BADI Definition

l Maintaining a Customer Extensibility Configuration

l Maintaining Data Profile Extensibility Configuration

Note: Both the Customer-Include structure, and the BADI Method implementation are generated

in the customer environment and based on the custom development naming standards

respectively.

5.1 Implementing a Customer-Include Structure

To implement a Customer-Include Structure, follow these steps:


2. From the list of tables specified in Tableswith Extensibility section, choose a table (for example,

/SKYTECH/CSAACTI), enter in the Database table and click Display.



The following image appears.

3. Double-click the CI structure (For example, CI_SKYTECH_CSAACTI) at the end of the table

and double-click it to implement.

The Create Structure dialog appears.



4. Click Yes and provide the fields based on the requirement and click Save and Activate the

custom include structure.

5. Tomodify the LDB definition with the newly added fields of the Customer Include Structure,

follow these steps:

a. Run the transaction YVTL and give the corresponding LDB name and click Execute.



b. Click the Fields button on the application tool bar to select the newly added fields.

c. Observe the newly added fields without selecting into the LDB definition. Select the fields

and then Save and Activate the LDB definition so that the CI structure fields appear in

the LDB definition.

Note: The customer has to implement all the required Custom Include structures and

modify the LDB definitions as per the requirements.

5.1.1 Tables with Extensibility

The following is a list of CRMBusinessConnector tables that you can use for customer extensibility.



Table Name Description

/SKYTECH/CSAACTI Activities table

/SKYTECH/CSAACNT Activity notes

/SKYTECH/CSAACLK Activity links

/SKYTECH/CSAACBP Activity partners

/SKYTECH/CSAOPPT Opportunities

/SKYTECH/CSAOPLK Opportunity links

/SKYTECH/CSAOPIT Opportunity items

/SKYTECH/CSAOPNT Opportunity notes

/SKYTECH/CSAOPBP Opportunity partners

/SKYTECH/CSALEAD Leads

/SKYTECH/CSALDNT Lead notes

/SKYTECH/CSALDLK Lead links

/SKYTECH/CSALDBP Lead partners

/SKYTECH/CSACRQ Customer request table

/SKYTECH/CSARQNT Request notes

/SKYTECH/CSARQLK Request links

/SKYTECH/CSARQBP Request partners




/SKYTECH/CSATNDR Tenders table

/SKYTECH/CSATNDN Tender notes

/SKYTECH/CSATNDL Tender links

/SKYTECH/CSATNDP Tender partners

/SKYTECH/CSATNDI Tender product and services

/SKYTECH/CSABUPA Partners

/SKYTECH/CSABPAD Partner address

/SKYTECH/CSABPAT Partner attributes

/SKYTECH/CSABPHR Partner hours

/SKYTECH/CSABPNT Partner notes

/SKYTECH/CSABPRS Partner relations

/SKYTECH/CSAORHD Order header

/SKYTECH/CSAORITM Order items

/SKYTECH/CSASOLK Order links

/SKYTECH/CSAACCT Activity categories

/SKYTECH/CSABPGR Business partner groups

/SKYTECH/CSABPSG Business partner sub groups




/SKYTECH/CSACITY Cities

/SKYTECH/CSACTRY Countries

/SKYTECH/CSACRST Customer credit status

/SKYTECH/CSADIST Districts

/SKYTECH/CSADEPT Departments

/SKYTECH/CSAJOBF Positions of contact person: Texts

/SKYTECH/CSAORCD Document codes

/SKYTECH/CSAPRD Material master extract

/SKYTECH/CSAPRUM Alternate product UoM

/SKYTECH/CSAPYTM Payment terms

/SKYTECH/CSAREGN Regions

/SKYTECH/CSACUST Business partner extension

/SKYTECH/CSASHPT Ship to customers

/SKYTECH/CSATITL Title (business address)

The following is a list of CRMBusinessConnector tables that you can use for customer extensibility in

ECC system.


/SKYTECH/CSAORHD Sales order header table




/SKYTECH/CSAORIT Sales order items

/SKYTECH/CSASOLK Sales order links

/SKYTECH/CSACRST Customer credit status

/SKYTECH/CSACUST Business partner extension

/SKYTECH/CSASHPT Ship to customers

/SKYTECH/CSAPRD Material master extract

/SKYTECH/CSAPRUM Alternate product UoM

/SKYTECH/CSAPYTM Payment terms

5.2 Implementing a BADI Method (Business Add-in)

To implement a BAdI, follow these steps:

1. Log on to the SAP CRMsystem.

2. Run the transaction SE18 and provide the BadI name as shown below.

The list of available BADI definitions andmethods as specified in BADI Definitions andMethods

section appear. For this example, the BADI /SKYTECH/CSA_ACTICRE is considered.

3. Provide the BADI in the BAdI Name field.

The below screen appears with the BADI implementation details.





5. Provide the implementation name in Implementation Name and clickOK.


apears.



6. Provide the implementation short text in Implementation Short Text. Click Activate to activate

the BAdI implementation.

Themethods in the implementation appear.



7. Double-click any of themethod name and activate the same for further usage as shown below.

5.2.1 BADI Definitions and Methods

The following table lists the BADIs and their methods that are provided in the SAP CRMsystem for

customer extensibility.

The general guidelines for the usage of each of themethods are as follows:

AT_START: Available at the start of the processing immediately after the import of ECS data and

parameters. Recommended for logic that involves change of the initial data set before processing.

PRE_PROCESS: Available before the core processing functionality. For Example, Before important

BAPI calls. Recommended for logic that involves change of data passed to themain processing

modules.

POST_PROCESS: Available after the core processing functionality. For Example, After important

BAPI calls. Recommended for logic that involves change of standard results from themain processing

modules.



AT_END: Available at the end of a program. Recommended for logic that involves change of the final

set of data and synchronization with devices.

AT_DATA_PROFILE: Available after the standard data profile attributes are determined. This

method allows customers to add their logic to determine additional attributes or overwrite standard

attribute values according to customer profiles.

BADI Definition / Enhancement Spot Methods

/SKYTECH/CSA_ACTICRE l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_ACTIEXT l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_LEADCRE l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE




/SKYTECH/CSA_OPPTCRE l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_OPPTEXT l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_LEADEXT l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_REQEXT l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE




/SKYTECH/CSA_REQMAIN l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_TNDRCRE l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_TNDREXT l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE




/SKYTECH/CSA_BPCRE l AT_START

l PRE_CREATE

l POST_CREATE

l PRE_UPDATE

l POST_UPDATE

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_BPEXT l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

l AT_DATA_PROFILE

/SKYTECH/CSA_ORDUPLD l PRE_PROCESS

l POST_PROCESS

/SKYTECH/CSA_DOBSYNC l AT_DATA_PROFILE

5.3 Maintaining a Customer Extensibility Configuration

To maintain the configuration table (/SKYTECH/CSA_EXT), follow these steps:



1. Log on to the SAP CRM system.

2. Run the transaction /SKYTECH/CSA and click the Customer Extensibility tab.

3. Click Customer Extensibility Control.




4. Maintain the table with BADI implementation details as shown below.

5. Click Save.

The CRM Customer Enhancement Configuration Maintenance Screen window appears.

6. Tomaintain the table with BADI implementation details, fill in the fields as follows:

a. Field 1: Fill in the PGMNAME with ECS interface program.

b. Field 2: Fill in the ENHANCEMENTSPOTwith Enhancement spot / BADI method name

available for ECS interface program.

For example, for ECS interface CSA_EXTRACT_ACTIVITY, there are four Customer

enhancement spots. They are AT_START / PRE_PROCESS / POST_PROCESS /

AT_END.

Customersmay implement any or all of themethods according to their requirements.



c. Field 3: Fill in the CLASSNAME with BADI implementation class details.

In the above example, BADI Method (Business Add-in), the implementation ZACTI_

TEST_BADI was created.

d. Field 4: Fill in theMETHODNAME with the BADI implementationmethod name.

In the above example, BADI Method (Business Add-in), there are four methods for the

BADI.

Customersmay implement any or all of themethods according to their requirements.

Note: Customer BADI ClassName and Customer BADI Method name are created

in the customer environment with customer naming standards.

5.4 Maintaining Data Profile Extensibility Configuration

To maintain the data profile extensibility configuration, follow these steps:

1. Log on to the SAP CRMsystem.

2. Run the transaction /n/SKYTECH/CSA and click the Customer Extensibility tab > the Data

Profile Extensibility Control button.




3. Tomaintain the table with BADI implementation details, fill in the fields as follows:

a. Enter the DOB name in the Local database name field.

b. Enter the custom data profile name in the VTI: Profile id field.


6. Working with Customer Extensions - ECC Interface Kony CRM BC Install GuideVersion2.2

6. Working with Customer Extensions - ECC Interface

You can extend the functionality of the standard BusinessConnector to meet customer specific

requirements. This allows the customer to include and use additional fields in the existing tables and

add custom logic at predefined sections of the code using BADIs provided for the same.

The following sections describe inmore detail the steps required to implement customer extensibility:

l Implementing a Customer-Include Structure

l Implementing a BADI Method provided in the BADI Definition

l Maintaining a Customer Extensibility Configuration

Note: Both the Customer-Include structure and the BADI Method implementation are generated

in the customer environment and as per the custom development naming standards respectively.

6.1 Implementing a Customer-Include Structure

The procedure to implement a customer include the ECC system is the same as described for the

CRM system. Follow the stepsmentioned for the same in Implementing a Customer-Include

Structure. For the list of extensible tables, refer to Tableswith Extensibility.

6.1.1 Tables with Extensibility

The following is a list of CRMBusinessConnector tables that you can use for customer extensibility in

ECC system.


/SKYTECH/CSAORHDR Sales Order Header Table

/SKYTECH/CSAORITM Sales Order Items




/SKYTECH/CSASOLK Sales Order Links

/SKYTECH/CSACRDTS Customer Credit Status

/SKYTECH/CSACUST Business Partner Extension

/SKYTECH/CSASHPTO Ship To Customers

/SKYTECH/CSAPRD Material Master Extract

/SKYTECH/CSAPRDUM Alternate Product UoM

/SKYTECH/CSAPYTRM Payment terms

6.2 Implementing a BADI Method (Business Add-in)

The procedure to implement a BAdI method in the ECC system is the same as described for the CRM

system. Follow the steps outlined for the same in Implementing a BADI Method (Business Add-in)

section. For the list of available BAdI definitions andmethods, refer to BADI Definitions andMethods.

6.2.1 BADI Definitions and Methods

The following table lists the BADI Method that is defined in the SAP ECC system for customer

extensibility.

The general guidelines for the usage of each of themethods are as follows:

AT_START: Available at the start of the processing immediately after the import of ECS data and

parameters. Recommended for logic that involves change of the initial data set before processing.

PRE_PROCESS: Available before the core processing functionality. For Example, Before important

BAPI calls. Recommended for logic that involves change of data passed to themain processing

modules.



POST_PROCESS: Available after the core processing functionality. For Example, After important

BAPI calls. Recommended for logic that involves change of standard results from themain processing

modules.

AT_END: Available at the end of a program. Recommended for logic that involves change of the final

set of data and synchronization with devices.

BADI Definition /Enhancement Spot

Methods

/SKYTECH/CSA_ORD_

MAIN

l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

/SKYTECH/CSA_ORD_

EXTR

l AT_START

l PRE_PROCESS

l POST_PROCESS

l AT_END

/SKYTECH/CSA_CRDT_

EXT

l PRE_PROCESS

l POST_PROCESS

/SKYTECH/CSA_CUST_

EXT

l PRE_PROCESS

l POST_PROCESS

/SKYTECH/CSA_MAT_

EXTR

l PRE_PROCESS

l POST_PROCESS



BADI Definition /Enhancement Spot

Methods

/SKYTECH/CSA_PYTM_

EXT

l PRE_PROCESS

l POST_PROCESS

6.3 Maintaining Customer Extensibility Configuration

To maintain the configuration table follow these steps:

1. Log on to the SAP ECC system.

2. Run the transaction SM30.

TheMaintain Table Views: Initial Screen window appears.

3. Enter the name of the extension table /SKYTECH/CSA_EXT in Table/View, and click the

Maintain button.




4. Click the New Entries button.

The New Entries: Overview of Added Entries window appears.



5. Tomaintain the table with BADI implementation details, complete the fields as shown below.

a. Field 1: Fill in Interface Program Namewith ECS interface program. For example,

Interface program for ECS CSA_CREATE_ORDER is /SKYTECH/CSA_CREATE_

SALESORDER.

b. Field 2: Fill in Customer enhancement with Enhancement spot / BADI method name

available for ECS interface program.

For example, For ECS interface CSA_CREATE_ORDER, there are four Customer

enhancement spots. They are AT_START / PRE_PROCESS / POST_PROCESS /

AT_END.

The customer may implement any or all of themethods according to their requirements.

c. Field 3: The conf. flag field is auto-populated with X as valueswhen you save the data.

d. Field 4: Fill in the Customer BADI Class namewith BADI implementation class details.

For example, in the above example implementation, BADI Method (Business Add-in), the

test BADI class ZCREATE_ORDER_BADI_IMPLwas created while implementing the

BADI.

e. Field 4: Fill in the Customer BADI Method namewith the BADI implementationmethod

name.

For example, in the above example implementation, BADI Method (Business Add-in),

there are four methods for the BADI.

The customer may implement any or all of themethods according to their requirements.

Note: Customer BADI ClassName and Customer BADI Method name are created

in the customer environment with customer naming standards.


7. Appendix: Namespace Repair Kony CRM BC Install GuideVersion2.2

7. Appendix: Namespace Repair

To customize and /or to generate BAdI objects, you need to configure the /SKYTECH/ namespace for

repair and add the ABAP developer key to the SAP users. Refer to Installation and Upgrade >

Installing a SAP MEAP Server > Making Local SAP Repairs section of Kony for SAP Technical

Library on KonyDeveloper Portal for details on SAP namespace repair.



Kony CRM - Sales Business Connector Installation Guide

Documents