lc conflguraLlon

Whats Internet Pricing and Configurator

IPC is a SAP CRM concept used to Ietch all Pricing inIormation when a customer is creating
a sales order ,a quotation or a contract.
The conIiguartor part oI IPC is used to help the customers decide the various characterstics oI
the product they order when they create an order, quotation or an contract.(Its the CRM
version oI Jariant Configuration in SAP R/3).

To understand the pricing we should Iirst know where IPC is placed in SAP CRM 5.0 and
SAP CRM 2007.

Starting Irom CRM 5.0 to CRM 2007 , SAP has introduced the concept oI VMC.VMC is the
virtual machine part oI SAP kernel AS ABAP, provides a run time environment to execute
java code. IPC is no longer a standalone server which it was in CRM 4.0 and previous
versions, it is now a part oI SAP kernel AS ABAP.

The advantage is that now each user is given a new VMC session and when a VMC is down ,
it only eIIects a single user not all users.

The VMC is contained within the SAP kernel AS ABAP, and so it does not have to be
installed separately. Though it does have to be activated by changing a Iew proIile
parameters. ote 854170 describes how to do this.


ow Pricing Is Triggered





When a customer creates an order on the SAP CRM Ecommerce B2B or B2C applications.
The Iollowing steps are undertaken Ior pricing to be triggered.

$tep 1.
The customer inputs the values oI the product he wishes to buy.
$tep 2.
Depending on the Sales Area(Sales Org, Distribution Channel and Division) , Partner
Determination Procedure and Document
Pricing Procedure the Pricing Procedure on CRM system is triggered.(These are basically
part oI Base Customization oI SAP CRM )
$tep3.
Within pricing procedure we have condition types , these are the various kinds oI calculations
required to Iind the total price oI the item
$tep 4.
Within condition types we have access sequence,the system reads the Iirst condition type oI
the pricing procedure and determines the assigned access sequence.
This step, together with the Iollowing , is repeated Ior each condition type on the pricing
procedure.
The system reads the access sequence with the condition tables. The sequence oI the
condition tables Iorms the search strategy Ior determining the individual condition
records.The system reads the Iirst condition type oI the pricing procedure and determines the
assigned access sequence. II the system does not Iind a valid condition record Ior the Iirst
condition table, it carries on and searches Ior a condition record Ior the next condition table.
. Step 5.
Once the system has Iound a valid condition record Ior a condition table, it makes the
result available to pricing in the Iorm oI prices and discounts.

&seful Links and Transactions
Transactions
1. sm53( admin Ior VMC )
2. sm52( VMC viewer )
3. /sapcnd/uedev ( the java coding must be uploaded using this and the IPC libraries
can be downloaded)
4. /sapcnd/ueass (used Ior maintaing metadata entries and registring the userexit)
5. . /sapcnd/GCM:- General condition maintenance


Link
1. Pricing UserExit Manual and project structure Ior
Eclipse https://service.sap.com/sap/support/notes/809820

Creating the Project structure

$tep 1. Download j2se version 1.4 Irom http://java.sun.com/j2se/1.4.2/download.html

$tep 2. Use Netweaver Developer Studio or download clipse 3.1 from
http://www.eclipse.org/downloads.

$tep 3. Create an empty Iolder like C:/IPC_DEV

$tep 4. Unzip the Iile attached to SAP Note
https://service.sap.com/sap/support/notes/809820 in the subdirectory
C:/IPC_DEV/PRC_UE_CUSTOMER

$tep 5. Start the transaction SAPCNDUE_DEV.

$tep 6.Download the libraries in the directory C:/IPC_DEV/PRC_UE_CUSTOMER.

Step 7. Start eclipse or NWDS and select as workspace the manual created folder (C:\PC_D'.
clipse will create the meta data for
an empty workspace
Step 8. Select File
mport. and mport an isting Project into Workspace. Select the PRC_U_CUSTOMR
folder as root directory. clipse should show the PRC_U_CUSTOMR as project name
Step 9. Now the JR System Libraries have to be added to the build path of eclipse. Activate the
contet menu on the
project (right mouse click and select Build Path
Add Libraries. Select JR System Library and use a 1.4.
version
Step 10. Prepare the AP source and build the HTML documentation. Activate the contet menu (right
mouse click on
build_api_doc.ml and select Run As
&#1000c6;Ant Build. Please ignore the error message thrown during that process
Step 11. Refresh the eclipse Project by right mouse clicking on the project and selecting Refresh (F5
in the contet
menu
ow to create logs on VMC
In the transaction sm53,on the leIt side we can see Log Administration, in that we also see
the Log ConIiguration.

We can speciIy the various severity levels like at the package or class level.

1. InIo
2.Warning
3.Erorr
4. Fatal
5.Debug

Logs can now be viewed at the same transaction sm53.
The log entries can also be filtered by different criteria such as Severity, Log Name (which is the
class name or package or User.


Types Of &ser Exits

1 Number Dependent( frequent|y used)

Called as number dependenL because Lhese userexlLs requlre formula number Lo be asslgned for
Lhem Lo be execuLed used ln Lhe cusLomlzlng parL of prlclng procedure

Var|ous types are
11 kequ|rement(kL)
12 Cond|t|on 8ase Iormu|a(8AS)
13 Sca|e 8ase Iormu|a (SCL)
14 Cond|t|on Va|ue Iormu|a(VAL)
1S Copy Iormu|a(C)
16 Group key Iormu|a(Gk)

2 Cne Un|que Imp|ementat|on

. Item Culculutlon Begln Formulu (CAB)
. Item Culculutlon FnJ Formulu (CAF)
. ConJltlon Inlt Formulu (CNI)
.4 Item Inlt Formulu (I1I)
.S ocument Inlt Formulu (OI)
.6 Conflgurutlon Formulu (CF0)

3 Mu|t|p|e Act|ve Imp|ementat|on

31 r|c|ng In|t(kI) (rev|ous|y CRMDocument$tandardExit)
32 r|c|ng repare (k) (rev|ous|y CRMItem$tandardExit.)
$etting VMC in Debug Mode
To make the debugging active we have to set the parameter PRCRFC as X using the
transaction su3 , in the tabs named parameter.
This happens Ior the user Ior which we want the debugging to be active.





In the transaction sm 52 , you can see the status oI the debugging , the various statuses are
ot active: Debugger is not active
$tarted: Debugging has been started
Waiting: VM is waiting Ior the debugger client to connect
Active: VM is connected to the debugger client
$topping VM is closing the connection to the debugger