CRM Technical training extracts

1. CRM tables maintained using naming conventions like

CRMD* - Transaction data
CRMC* - Customizing data
CRMM*- Master data
2. Main Tcode in CRM is CRMD_ORDER to maintain update and delete any order.
3. Business transaction category also known as OBJECT_TYPE
Business transaction type also known as PROCESS_TYPE.
4. Data is stored in the form of Data sets and also known as Business Transaction
Subobjects. Data sets are linked to the Buss. Trans. With m:n relationship
Datasets

ADM HEADER

SALES

ADM ITEM

Partner

LEAD

Sales & Org data

Pricing

OPPORTUNITY

Business Transactions
5. Standard report program and FM to view the above relationship between
datasets and buss tran. Categories for any order is CRM_ORDER_READ
6. To maintain BP role as Sold To Party , in the Sales Area Data -> maintain
Sales Org, Distribution Channel and Division. In the Billing -> Maintain
Customer Pricing Procedure.
7. Products are maintained using Tcode COMMPRO1 . Maintain Item Cat. Group
, Sales area data i.e. Sales org, Dist. Channel and Division , Condition type.
8. To have successful sales transaction, there should be at least 1 common sales
area data present for BP( of role Sold to party ) and product.
9. To create a Businesss Transaction for sales, maintain Sold to party, product,
and sales area.

10.

For product, Item Category and Pricing procedure is determined.

Item Category Determination :

Item Category. =

Buss. Tran. Type + Item Cat group

* Get Item Buss. Cat. Group from Product in COMMPRO1

* Maintain entry in SPRO->CRM->Transactions->Basic Settings
Pricing Procedure Determination :
Pricing. Procedure = Sales org + Dist. Channel + division + Cust.
pricing Proc. + Doc. Pricing proc.
Sales org + Dist. Channel + Division is derived from the Sales area data
maintained for BP and product.
Cust. Pricing Proc. is maintained in the Billing Tab in the Sold to party
role of BP.
Doc. Pricing Proc. Is maintained in SPRO for a business transaction type at
SPRO->CRM->Transactions->Basic Settings->Define Trans. Types
Finally with these 5 keys, maintain the Pricing procedure at SPRO->CRM>Basic functions-> pricing->Pricing in Buss. Transac.-> Determine Pricing
proc.
And Maintain the above created Pricing Proc at SPRO->CRM->Basic
functions-> pricing->Pricing in Buss. Transac.->Define settings for Pricing
->Create / Maintain pricing procedures.
Here add the condition types as per the logic with the entries maintained in
the product -> conditions data.
11. No of tabs assigned to any buss. Transaction category are maintained in the
view CRMV_OBJECT_ASSI
12. To find out the Db table names, use CRMD_ to the output tables of FM /
report CRMD_ORDER_READ
13. To make a change in the order through program following rough steps are
executed
1. Get the Header / Item Guid
2. Call CRM_ORDER_READ
3. Call CRM_<obj name>_MAINTAIN_OW
To view the details of the fields to be changed in the debugging
1. Make a change in the field and start debugging using /h.
2. Set a breakpoint at FM CRM_ORDER_MAINTAIN

3. Check the entries in the internal table CT_INPUT_FIELDS and select

value in OBJECTNAME where internal table FIELD_NAMES has some
entries.
4. Create a break point at FM CRM_<objname>_MAINTAIN_OW
5. In the locals tab, check structure
CS_<obj name>* and get the
GUID ids.
14. CRM_INTLAY_GET_PROCESS_MODE to check if its Create /Change/
display mode
CRM_INTELAY_GET_HEADER_GUID , CRM_INTLAY_GET_PROCESS_TYPE
15.
The BAdIs are named as COM_<obj name>_BADI , ORDER_SAVE
To find the BAdI ,
1. Put break point in method CL_EXITHANDLER=>Get_INSTANCE
2. Put a breakpoint at statement GET BADI
3. Put a breakpoint in FM SXV_GET_CLIF_BY_NAME
16.

While creating a BSP application - >

Controller -> create a controller class inherited from
CL_BSP_CONTROLLER2
Model - > Create a model class inherited from CL_BSP_MODEL