IPC Installation and Data Download

mySAP CRMIPC Install and Data Download

PSO Info Days – Salt Lake City

SAP America, Inc. 2003, mySAP CRM – IPC Installation and Data Download 2

mySAP CRM – IPC Installation and Data Download

IPC Installation IPC Data Download from R/3 to CRM IPC Data Download from CRM to Mobile SCE setup (Configuration Engine) Data Model for Pricing and Configuration





IPC Installation

Two Important installation scenarios• (a) CRM Online• (b) Mobile

(a) CRM Online Scenario Installed along with CRM Server installation. Primarily used for

* Online CRM Applications* Internet Sales and Service* CIC (Customer interaction Center)

(b) Mobile Scenario Primarily for Offline scenario. Installed on each Laptop

running CRM Mobile Sales and Service Application.


CRM Online-System

Middleware

Internet Sales CIC

Online Client

WorkplaceMarketing & Campaign

IPC Installation (CRM Online)

IPC Server


IPC Installation (CRM Online)

Important information

• Refer IPC installation Guide for details

• Set Middleware Parameter ‘PricingType’ as per your needs (Transaction - R3AC6)

•Set IPC Parameters File. Admin.bat is the front-end GUI utility for this activity

• Make Sure you install/update all the User Exits. Keep Track of IPC Patches and consistently update IPCPatch.jar

• Use Admin.bat to test the Database Connection

• Use SXE_Log.html to check any installation problem


IPC Installation (Mobile)

CRM Online-System

Middleware

Data exchange:•Master Data (Address, Products, etc.)•Sales- Service Documents•Sales Pricing Engine (SPE)•Sales Configuration Engine (SCE)•Customizing-Information•Daily Delta-Information

Mobile Client

Offline Client

IPC


IPC Installation (Mobile) – I


• Install Java Run-Time Environment (JRE 1.3.1_05 and higher) before starting CRM installation. (Refer OSS note 433855)

• Install IPC Engine by executing SPEInstall.bat (The Latest version corresponding to a Service Pack is available in a directory under SAP\Mobile, which is created after running Dev Env upgrade)

• Set IPC Class Path Parameter _JPI_VM_OPTIONS (Refer OSS note 433855)

• Set IPC Parameters File. Admin.bat is the front-end GUI utility for this activity. Use Admin.bat to test the Database Connection also.

Continued …


IPC Installation (Mobile) - II


• Make Sure you install/update all the User Exits. Keep Track of IPC Patches and consistently update IPCPatch.jar

• Check Registry Area under HKLM\Software\SAP\MSA\SPE and HKLM\Software\SAP\MSA\SCE

• Check Mobile\bin\SXE_Log.html to find any installation problem. Execute SPC.bat and test sample Document Creation.

• SPC uses IDES and SCE uses SCEKBS database. Check their creation.

• Run SQL Profiler in the Background while starting the Mobile application. There should be lot of SQL statements under I-net Driver area indicating IPC initialization





Data Download from R/3 to CRM

Steps to download data from R/3 to CRM

(a) Prepare CRM for Customization Download

(b) Download Pricing Customization

(c) Execute the Report /SAPCND/RV12N001

(d) Download Pricing Conditions



Prepare CRM for Customization Download

• Identify all Pricing Procedures relevant for download to CRM, and check their details in R/3

• Specify Price Procedure Determination Settings in CRM IMG

• For all Relevant pricing Procedures, check Access Sequence Fields. Not all R/3 fields are supported by CRM e.g VKBUR, MATKL. Follow these steps to map additional R/3 fields• Use the maintenance view V_CND_MAP_CNVFLD in CRM

to check the existence of mapping. If not available create new Z fields and map to remote R/3 fields.

• Go to IMG Setting CRM->Basic Functions -> Pricing

-> Define Settings for Pricing ->Field Catalogs and add Z fields in the Field Catalog



Download Pricing Customization

• Trigger Initial Load of object DNL_CUST_CNDALL from R/3 to CRM (Transaction R3AS)

• In case of multiple clients, download DNL_CUST_CNDALL for 1st client and then download following objects for rest of the clients• DNL_CUST_CND• DNL_CUST_PRC• DNL_CUST_FGD

SAP recommends to delete DNL_CUST_CNDALL in other clients.

• It will download all customization data from R/3 to CRM.



Execute the Report /SAPCND/RV12N001

• Execute this Report after Initial Load is finished

• Set Application = CRM, Usage = PR, select ‘Conversion of Customization from R/3 to CRM’ and execute it. Typically there are missing parent keys in the downloaded data. This step will correct all that data.

• Set Application = CRM, Usage = PR, select all the check boxes in the first section ‘Select Objects to be generated’ and execute it. It will create all Condition Objects and Tables. It creates CRM and CDB table for each Condition (including 500+ customer tables). Naming Convention for CRM tables is

‘CNCCRMPR’ + ‘SAP’ (< 500) /’CUS’ (> 500) + xxx (number)

• Select ‘Delete Inconsistent Customizing’ and execute it. It will clean up everything inconsistent.



Download Pricing Conditions

• Basically all the data in Axxx table of R/3 which needs to be downloaded to CRM.

• For A001 to A500, there are standard Download objects available with names like DNL_COND_Axxx. (Use Transaction R3AC5 to get the list)

• For A501 to A999, create additional Adapter Objects. Fill in all the details as DNL_COND_Axxx object. After that in the section ‘Tables/Structures’, change the Table name to required A table.

• Trigger the Download (Transaction - R3AS). Use R3AM1 to monitor the status of download.

• Verify all the data in corresponding CRM tableCNCCRMPR + ‘SAP’/’CUS’ + xxx





Data Download from CRM to Mobile

Steps to download data from CRM to CDB/Mobile

(a) Download Pricing Customization from CRM to CDB

(b) Execute the Report CND_MAST_GEN_TRANSFER_OBJECTS

(c) Download Pricing Conditions from CRM to CDB

(d) Create Replication and Publication Objects



Download Pricing Customization from CRM to CDB

(a) * Go to table SMOFOBJECT, filter on OBJCLASS = CONDCUSTOMIZING and OBJNAME = CRM* Pick up all entries and create a variant in R3AS4 and execute it.

* Unlike R/3 to CRM, there is no report like /SAPCND/RV12N001 for this scenario. As everything is already corrected and generated in previous steps



Report CND_MAST_GEN_TRANSFER_OBJECTS

• This report can be used to created Condition tables in CDB an Related BDocs. Naming Convention of a condition table in CDB isCMBCCP + ‘SAP’(< 500) /’CUS’ ( > 500) + xxx (Table Number)e.g. CMBCCPSAP004, CMBCCPCUS903.

• CDB tables are generated by /SAPCND/RV12N001 execution also. If you want to create and repair again for CDB scenario, this report should be used for table creation.

• After checking created tables, select following options and execute the report• Generation Synchronization Bdocs• Activation Synchronization Bdocs• Define Secondary Index for Mobile ClientsIt will create and Activate all sBdoc which are a must for data

distribution with CDB and Mobile Clients.



Download Pricing Conditions from CRM to CDB

• Basically all the data in CNCCRMPR(SAP/CUS)xxx table of CRM which needs to be downloaded to CDB.

• For 001 to 500, there are standard Download objects available with names like CRM_CCPSAPxxx. (Use Transaction R3AC5 to get the list)

• For 501 to 999, create additional Adapter Objects. Fill in all the details as CRM_CCPSAPxxx object. After that in the section ‘Tables/Structures’, change the Table name to required 500+ table number. Also, link the appropriately generated Bdoc.

• Trigger the Download (Transaction - R3AS). Use R3AM1 to monitor the status of download. Verify all the data in corresponding CDB table

CMBCCP + ‘SAP’/’CUS’ + xxx



Create Replication and Publication Objects

• There are already Replication and Publication Objects for Customizing download. Additionally, create Subscriptions and assign them to a site for data distribution to Mobile Client.

• For all Condition tables > 500, create Replication Object for each Synchronization BDoc. As per Customer needs, either create Bulk or Intelligent Replication Object.

• Create one Publication for all BULK Replication Objects. Create a corresponding subscription and assign to Sites.

• For each Intelligent Replication, create Publication and Subscription objects and assign them to site.

• ConnTrans at Client end will bring the data to Laptops. Create a sample document using SPC.bat to verify the consistency.





SCE Setup (Configuration Engine) - I


• No additional software installation

• Download following additional Objects from R/3 to CRM• SCEIt will download all Knowledge Bases defined in R/3 and bring to CRM Online database. Check table COMM_SCEKB to ensure proper download of all the versions of a knowledge base.

• Download Objects from CRM to CDB• CONFIGURATIONIt will download all Knowledge Based from CRM and bring it to CDB. The data is downloaded in 3 tablesSMOSCEKBHD - Header Table to KBsSMOSCEKBI - Initial Load info for KBsSMOSCEKBD - Delta Load info for KBs


SCE Setup (Configuration Engine) - II


• Create new Subscriptions for each KB and assign to site. Optionally

• Activities on Laptops• Based on SMOSCEKBHD, all KBs will be initialized• •If there is a data in SMOSCEKBI and SMOSCEKBD, then all the data will be imported to SCEKBS database by Import Manager.

• After Importing the data in SCEKBS database, data from IDES tables will be deleted. SMOSCEKBHD will be the link between IDES and SCEKBS database.





Pricing

Order

Access Sequence

ConditionType

Pricing Masters

PricingProcedure

The system determines the pricing procedure based on sales organization, distribution channel,division, the document pricing procedure typeassigned to the order type and the customer pricingprocedure type assigned to the customer.

An order is entered

Looks at the first condition type in thepricing procedure.

Determines the access sequence definedfor the condition type

Looks at the first condition table(set of keys) of the condition type.

Looks through the pricing master recordsto find one with key values that match thevalues within the order.

If a match is found, the price/discount/freight... is added to theorder, and the system goes to the next condition type in the pricingprocedure.

ConditionTable

If no price records arefound, SAP goes to thenext condition table inthe sequence.


Price Procedure Determination

Sales Order (OR)

Customer 9900-XX

Customer Master

Cust. Pric. Proc : 1

Configuration ofSales Doc Type: OR

Doc. Pric. Proc : A

Sales Area

Customer Pricing Procedure

Document Pricing Procedure

Pricing ProcedureRVAJUS

is Determined


Pricing Procedure Determination

Customer Pricing Procedure

Mobile Client:

Table SMOKNVV, Field KALKS

Document Pricing Procedure

Mobile Client:

Table SMOTVAK, Field KALVG

Pricing Procedure Determination

Mobile Client:

Table CDBC_PRCPROC_DET

SALES_ORG DIS_CHANNEL DOC_PRIC_PROC CUST_PRIC_PROC PRICING_PROCEDUR

O 50000101 10 7 1 RVCEU3


Pricing Data Model (Mobile and CDB)

CDBC_P_CN_PPD

CDBC_P_CN_PPDT

Pricing Procedure

CDBC_P_CN_PP

CDBC_P_CN_PPT

Pricing Procedure Controls

Pricing Procedure


Pricing Data Model (CRM Online)

PRCC_COND_PPD

PRCC_COND_PPDT

Pricing Procedure

PRCC_COND_PP

PRCC_COND_PPT

Pricing Procedure Controls

Pricing Procedure



CDBC_P_CN_CT Condition Types

CDBC_C_T681

CDBC_C_T681T

Condition Table Meta Data

Condition Types

CDBC_C_T681E Condition Table Fields



PRCC_COND_CT Condition Types

/SAPCND/T681

/SAPCND/T681T

Condition Table Meta Data

Condition Types

/SAPCND/T681E Condition Table Fields



CDBC_C_T685

CDBC_C_T685T

Condition Types

CDBC_C_T682

CDBC_C_T682T

Access Sequences

Condition Types with Access Sequences

CDBC_C_T682I

CDBC_C_T682Z

Access Elements

Fields in Access Sequences



/SAPCND/T685

/SAPCND/T685T

Condition Types

/SAPCND/T682

/SAPCND/T682T

Access Sequences

Condition Types with Access Sequences

/SAPCND/T682I

/SAPCND/T682Z

Access Elements

Fields in Access Sequences


Questions ?