X:[HJ#M;W$REH • Address • Country or region • Jurisdiction code • Tax registration number • Tax types and groups
+E M @[I)J • Tax types and groups
R E#FJ2K M/G
\^]`_ba]`cdfe \g]`_bhi_7dAj:k`cml n^o7e pdrq)srt`cml u7l v l c w
as^v diex\g]f_ pd`cdAy jzl or]fcml n^o
\)]f_pngt7s7jxd7o`c
• Date • CRM item object type
SAP AG 2004
If you create billing documents using CRM Billing, the taxes are determined via the Transaction Tax Engine.
To trigger the Transaction Tax Engine call, you need define the condition type 77( (for tax calculation and the net price) or 77( (for tax calculation and the gross price). Recommendation: use the &50 pricing procedure.
As of SAP CRM 4.0, there is a WD[GRFXPHQW. This document is stored permanently in a system and can be accessed at all times. The Tax Document comprises all input and output data for a particular Transaction Tax Engine (TTE) tax determination and calculation.
You can find a check list for the TTE’s basic settings in the online documentation.
The TTE determines and calculates tax based on the condition records and tax exemption licenses. The TTE uses the transferred data to determine the tax event, tax type(s) and the corresponding tax record. The simulation transaction TTE_SIMULATION supports: y Tests of all Customizing parameters y Tests of all tax calculation results y Saving documents
© SAP AG
CR100
9-21
0DVWHU'DWDIRU7D[&DOFXODWLRQLQ&50 7D[FODVVLILFDWLRQRI%XVLQHVV3DUWQHUDQG3URGXFWV &XVWRPL]LQJ 7D[7\SHV
7D[*URXSV - 'HIDXOW%XVLQHVV3DUWQHU7D[*URXSVIRU7D[&DOFXODWLRQ - 'HIDXOW 3URGXFW 7D[*URXSVIRU 7D[&DOFXODWLRQ
SAP AG 2004
Tax calculation requires classification of business partners and products. The business partner and product tax classification is made by assigning tax groups to the tax types (for example, VAT, sales tax) that must be determined in any given country. The tax groups indicate whether a business partner is liable for or exempted from the respective tax type that is imposed. In Customizing, the tax type specifies which taxes are determined for each country. y Corresponding tax groups are defined for business partners and products for each tax type. The combination of tax group, the country (or region), and tax type determines the tax condition record. y A default tax group can be defined for business partners and products per country and tax type. When a business partner or a product has not been assigned a tax classification, the default tax group is used.
© SAP AG
CR100
9-22
&XVWRPL]LQJ 7D[7\SHVDQG7D[*URXSV
SAP AG 2004
A prerequisite for business partner and product tax classification is the definition of country-specific tax types and tax groups in Customizing. The WD[W\SH specifies which taxes are determined for each country. The DFFHVVVHTXHQFH specifies the order in which condition records are accessed for a country when more than one tax type has been defined for it. The WD[FDWHJRU\ is a distinct grouping of taxes to which tax types belong such as sales tax, withholding tax or excise tax. Corresponding tax groups are defined for business partners and products for each tax type. The combination of tax group, the country (or region), and tax type determines the condition record. A default tax group can be defined for business partners and products per country and tax type. When a business partner or a product has not been assigned a tax classification, the default tax group is used.
© SAP AG
CR100
9-23
3ULFLQJ)XQGDPHQWDOV 6XPPDU\
'HVFULEHWKH,QWHUQHW3ULFLQJDQG&RQILJXUDWRU ,3&
8QGHUVWDQGWKHHVVHQWLDOIHDWXUHVRIWKHFRQGLWLRQWHFKQLTXH 'HVFULEHWKHSULFLQJIXQFWLRQV
0DNHFHUWDLQVHWWLQJVLQSULFLQJ&XVWRPL]LQJ
&DUU\RXWFRQGLWLRQPDLQWHQDQFHLQ6$3&50
SAP AG 2004
© SAP AG
CR100
9-24
([HUFLVHV 8QLW
&503ULFLQJ
7RSLF &RQGLWLRQ0DLQWHQDQFHDQG&XVWRPL]LQJ At the conclusion of this exercise, you will be able to: • Maintain conditions in the SAP CRM system • Maintain conditions in the SAP ERP system • Understand certain basic Customizing settings related to pricing in transactions You want to set up your sales and service transactions so that, when transactions are processed, pricing is carried out and the relevant pricing elements are found for each business transaction. You also want to familiarize yourself with condition maintenance, which is used in both the ERP and CRM systems. 1-1
Conditions and Condition Maintenance in the CRM System
1-1-1 Create a sales transaction of the type 6DOHV3URFHVV with the business partner 0HJDVWRUH and enter the product +7 with the TXDQWLW\ pieces.
1-1-2 Check in the transaction’s item details to see if the system found a FXVWRPHU GLVFRXQW (.).
1-1-3 Try entering a FXVWRPHUGLVFRXQW into the transaction manually, with a value of . Is this possible?
1-1-4 In the future, the customer should receive a FXVWRPHUGLVFRXQW (.) of for transactions of this type. This agreement should last from today until the end of the year. Maintain a condition master record in the 6$3&50 system accordingly.
1-1-5 Create another sales transaction of the type 6DOHV3URFHVV with the business partner ##0HJDVWRUH and enter the product +7 with theTXDQWLW\ pieces. What do you notice about the conditions screen? Save the transaction and note the number. _______________
© SAP AG
CR100
9-25
1-2
Conditions and Condition Maintenance in the ERP System
1-2-1 In the SAP CRM system, create a sales transaction of the type 4XRWDWLRQ with the business partner 6WRFNPDQQ and enter the product called 0RQLWRU with a TXDQWLW\ of pieces.
1-2-2 Check in the transaction’s item details to see if the system found a SULFH (35). Is this a customer-specific material price? How do you know?
1-2-3 In the future, you want the customer to receive a customer-specific material price of (85 per piece for transactions of this type. With quantities of SLHFHV of more, the material costs (85 for this customer. This agreement should last from today until the end of the year.
Maintain a condition master record in the 6$3(53 system accordingly.
1-2-4 Create another sales transaction of the type 4XRWDWLRQ with the business partner 6WRFNPDQQ and enter the product called 0RQLWRU with a TXDQWLW\ of pieces. What do you notice about the conditions screen? Call up the access analysis. What is the name of the condition table on which this customer-specific material price is based? _______________ Please note that this is a database table, in which important information relating to the price conditions is saved. The conditions table in Customizing does not have the prefix CNCCRMPR. Save the transaction and note the number. _______________
© SAP AG
CR100
9-26
1-3
Customizing Pricing 1-3-1 Take a look at one of the transactions from the previous exercise. 1-3-2 What pricing procedure was determined? Transaction from 1-1:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB Transaction from 1-2:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 1-3-3 What factors influence the determination of a pricing procedure? Where in the system are the concrete values of the factors for your business transactions from the previous exercise? Transaction from 1-1: _________________________________ ___________________________________________________ ___________________________________________________ Transaction from 1-2: _________________________________ ___________________________________________________ ___________________________________________________ 1-3-4 Can you make any changes to the two pricing procedures in the SAP CRM system’s Customizing? Transaction from 1-1:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB Transaction from 1-2:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB 1-3-5 You want to display the customer-specific material price (which you created in the ERP system) (FRQGLWLRQW\SH35) in general condition maintenance. To do this, set up a separate condition maintenance group – =&0* (PDLQWHQDQFHJURXS ##) – containing the corresponding condition table / condition type. Use a suitable description.
Specify that this condition maintenance group is in the *&0 (general condition maintenance) context.
1-3-6 In general condition maintenance, check if you can display condition master records of condition type PR00 in the condition maintenance group ZCMG##.
© SAP AG
CR100
9-27
© SAP AG
CR100
9-28
2SWLRQDO([HUFLVHV 6HUYLFH 2-1
Conditions and Condition Maintenance in the CRM System
2-1-1 Create a service process of the type 6HUYLFH2UGHU with the business partner 6WRFNPDQQ$* and enter the product 5HSDLU with the TXDQWLW\ 68.
2-1-2 Check in the transaction’s item details to see if the system found a FXVWRPHU GLVFRXQW (.).
2-1-3 Try entering a FXVWRPHUGLVFRXQW into the transaction manually, with a value of . Is this possible?
2-1-4 In the future, the customer should receive a FXVWRPHUGLVFRXQW (.) of for transactions of this type. This agreement should last from today until the end of the year. Maintain a condition master record in the 6$3&50 system accordingly.
2-1-5 Create another service process of the type 6HUYLFH2UGHU with the business partner 6WRFNPDQQ$* and enter the product 5HSDLU with the TXDQWLW\ 68. What do you notice about the conditions screen? Save the transaction and note the number. _______________ >oGDWDVKHHW@
© SAP AG
CR100
9-29
2-2
Customizing Pricing 2-2-1 Take a look at the transaction from the previous exercise. 2-2-2 What pricing procedure was determined?
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
2-2-3 What factors influence the determination of a pricing procedure? Where in the system are the concrete values of the factors for your business transactions from the previous exercise? __________________________________________________ ___________________________________________________ ___________________________________________________ 2-2-4 Can you make any changes to the pricing procedure in the SAP CRM system’s Customizing? BBBBBBBBBBBBBBBBB
2-2-5 You want to display the customer-specific material price (which you created in SAP ERP) (FRQGLWLRQW\SH35) in general condition maintenance. To do this, set up a separate condition maintenance group – =&0* (PDLQWHQDQFHJURXS ##) – containing the corresponding condition table / condition type. Use a suitable description.
Specify that this condition maintenance group is in the *&0 (general condition maintenance) context.
2-2-6 In general condition maintenance, check if you can display condition master records of condition type 35 in the condition maintenance group =&0*##.
© SAP AG
CR100
9-30
6ROXWLRQV 8QLW
&503ULFLQJ
7RSLF &RQGLWLRQ0DLQWHQDQFHDQG&XVWRPL]LQJ
1-1
Conditions and Condition Maintenance in the CRM System
1-1-1 Create a sales transaction of the type 6DOHV3URFHVV with the business partner 0HJDVWRUH and enter the product +7 with the TXDQWLW\ pieces. 6$30HQXo6DOHVo0DLQWDLQ6DOHV7UDQVDFWLRQV Choose&UHDWH7UDQVDFWLRQ(
icon).
Select 6DOHVo6DOHV7UDQVDFWLRQ.
Enter 0HJDVWRUH in the 6ROGWRSDUW\ field and confirm your entry.
In the 3URGXFW field, enter the number +7 with the TXDQWLW\ and confirm your entry.
1-1-2 Check in the transaction’s item details to see if the system found a FXVWRPHU GLVFRXQW (.). Click on the ([SDQGGDWDDUHDV icon (
Choose the &RQGLWLRQV tab.
) to see the item details.
The list of displayed condition types does QRW include the entry 0K07.
1-1-3 Try entering a FXVWRPHUGLVFRXQW into the transaction manually, with a value of . Is this possible? Choose $SSHQG5RZ(
).
Ctyp:
.
Amount:
The minus sign (-) and unit (%) are added automatically. You do not need to save the transaction.
1-1-4 In the future, the customer should receive a FXVWRPHUGLVFRXQW (.) of for transactions of this type. This agreement should last from today until the end of the year. Maintain a condition master record in the 6$3&50 system accordingly.
6$30HQXo0DVWHU'DWDo3ULFHVDQG&RQGLWLRQVo0DLQWDLQ &RQGLWLRQV &50
Application:
%83$',6&28
Maintenance group: … © SAP AG
CR100
9-31
… Choose
(([HFXWH).
In the data area, enter the value 0K07 in the &RQGLWLRQ7\SH (&W\S) field on the right and confirm your entry. Enter: 6DOHV86
Sales Organization:
Distribution Channel:
Division:
1XPEHURI0HJDVWRUH
Customer:
Amount:
WRGD\
Valid-From Date:
(QGRI\HDU
Valid-To Date: Save your data.
1-1-5 Create another sales transaction of the type 6DOHV3URFHVV with the business partner ##0HJDVWRUH and enter the product +7 with theTXDQWLW\ pieces. What do you notice about the conditions screen? Now the list of displayed condition types includes the entry 0K07 with the amount 3%. Save the transaction and note the number. _______________
© SAP AG
CR100
9-32
1-2
Conditions and Condition Maintenance in the ERP System
1-2-1 In the SAP CRM system, create a sales transaction of the type 4XRWDWLRQ with the business partner 6WRFNPDQQ and enter the product called 0RQLWRU with a TXDQWLW\ of pieces. 6$30HQXo6DOHVo0DLQWDLQ6DOHV7UDQVDFWLRQV
Choose&UHDWH7UDQVDFWLRQ(
icon).
Select 6DOHVo4XRWDWLRQ.
Enter ##6WRFNPDQQ in the 6ROGWRSDUW\ field and confirm your entry.
In the 3URGXFW field, enter the number of the product with the description 0RQLWRUand the TXDQWLW\and confirm your entry.
1-2-2 Check in the transaction’s item details to see if the system found a SULFH (35). Is this a customer-specific material price? How do you know? Click on the ([SDQGGDWDDUHDV icon ( Choose the &RQGLWLRQV tab.
) to see the item details.
Select the row with condition type PR00 and click on the 'LVSOD\FRQGLWLRQ UHFRUG button. The condition record is not related to a customer, it depends instead on the following keys: 6DOHVRUJDQL]DWLRQ'LVWULEXWLRQFKDQQHO3URGXFW,'. Alternatively, you can answer this question by carrying out an access analysis. 1-2-3 In the future, you want the customer to receive a customer-specific material price of (85 per piece for transactions of this type. With quantities of SLHFHV of more, the material costs (85 for this customer.
This agreement should last from today until the end of the year.
Maintain a condition master record in the 6$3(53 system accordingly.
6$30HQXo/RJLVWLFVo6DOHVDQG'LVWULEXWLRQo0DVWHU'DWDo &RQGLWLRQVo6HOHFW8VLQJ&RQGLWLRQ7\SHo&UHDWH 35
Condition Type:
Select ENTER, then the key combination &XVWRPHUPDWHULDOZLWKUHOHDVH VWDWXV and confirm this. …
© SAP AG
CR100
9-33
…
Sales Organization:
Distribution Channel:
1XPEHURI6WRFNPDQQ
Customer:
1XPEHURI\RXU0RQLWRU
Material:
Amount:
WRGD\
Valid-From Date:
(QGRI\HDU
Valid-To Date: Choose scales (
).
In the second row, enter:
Scale quantity:
Amount: Save your data.
1-2-4 Create another sales transaction of the type 4XRWDWLRQ with the business partner 6WRFNPDQQ and enter the product called 0RQLWRU with a TXDQWLW\ of pieces. What do you notice about the conditions screen?
The system LQFOXGHV the FXVWRPHUVSHFLILFPDWHULDOSULFH. Call up the access analysis.
Select the $FFHVVbutton.
Expand the entry for condition determination. Expand the entry for 6WHS (35; green).
Expand the entry $FFHVV.
What is the name of the condition table on which this customer-specific material price is based?
The condition table is called &1&&50356$3.
Please note that this is a database table, in which important information relating to the price conditions is saved. The conditions table in Customizing does not have the prefix &1&&5035. Save the transaction and note the number. _______________
© SAP AG
CR100
9-34
1-3
Customizing Pricing 1-3-1 Take a look at one of the transactions from the previous exercise. 1-3-2 What pricing procedure was determined?
Open each of the transactions and go to the +HDGHU2YHUYLHZ tab page.
Transaction from 1-1:
3ULFLQJSURFHGXUH&50 Transaction from 1-2:
3ULFLQJSURFHGXUH 59&(8 1-3-3 What factors influence the determination of a pricing procedure? Where in the system are the concrete values of the factors for your business transactions from the previous exercise? Determining the pricing procedure can be affected by the following factors: 6DOHVRUJDQL]DWLRQ'LVWULEXWLRQFKDQQHO'LYLVLRQ'RFXPHQWSULFLQJ SURFHGXUHand&XVWRPHUSULFLQJSURFHGXUH.
The 6DOHVRUJDQL]DWLRQ'LVWULEXWLRQFKDQQHOand'LYLVLRQ are displayed in the transaction on the 2UJDQL]DWLRQ tab page. The document pricing procedure is assigned to the transaction type. $UFKLWHFWXUHDQG7HFKQRORJ\o&RQILJXUDWLRQo&XVWRPL]LQJ
Go to the 6$35HIHUHQFH,0*.
6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo 7UDQVDFWLRQVo%DVLF6HWWLQJVo'HILQH7UDQVDFWLRQ7\SHV Select entry =6$/ and click on the 'HWDLOV icon (
).
In the dialog structure, double-click on $VVLJQPHQWRI%XVLQHVV 7UDQVDFWLRQ&DWHJRULHV
Select the 6DOHV transaction category and double-click on &XVWRPL]LQJ KHDGHU in the dialog structure.
The document pricing procedure is called &50 .
The customer pricing procedure is stored in the sold-to party’s master data. It is located in the sales area data related to this case on the %LOOLQJtab page. The customer pricing procedure is called 6WDQGDUG $ . Transaction from 1-1:
6DOHV86
Sales Organization:
Distribution Channel:
QRQH!
Division: Document Pricing Procedure: Customer Pricing Procedure:
… © SAP AG
CR100
9-35
… Transaction from 1-2:
,'(675
Sales Organization:
Distribution Channel:
QRQH!
Division: Document Pricing Procedure: Customer Pricing Procedure:
$
1-3-4 Can you make any changes to the two pricing procedures in the SAP CRM system’s Customizing? 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo %DVLF)XQFWLRQVo3ULFLQJo'HILQH6HWWLQJVIRU3ULFLQJo&UHDWH 3ULFLQJ3URFHGXUH Transaction from 1-1:
1R, it is not possible to make changes in the SAP CRM system. The pricing procedure was transferred from the SAP ERP system by Customizing download (source: R/3). 1-3-5 You want to display the customer-specific material price (which you created in the ERP system) (FRQGLWLRQW\SH35) in general condition maintenance. To do this, set up a separate condition maintenance group – =&0* (PDLQWHQDQFHJURXS ##) – containing the corresponding condition table / condition type. Use a suitable description.
Specify that this condition maintenance group is in the *&0 (general condition maintenance) context.
6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo 0DVWHU'DWDo&RQGLWLRQVDQG&RQGLWLRQ7HFKQLTXHo&RQGLWLRQ 7HFKQLTXH %DVLFVo&UHDWH0DLQWHQDQFH*URXS
Select 1HZ(QWULHV.
=&0*
Maintenance group:
0DLQWHQDQFHJURXS
Description:
Confirm your input, select the new entry and go to &RQGLWLRQ0DLQWHQDQFH *URXS 'HWDLO. …
© SAP AG
CR100
9-36
…
Select 1HZ(QWULHV.
Counter:
&50
Application:
35
Use:
6$3
Condition table:
35
Condition Type: Description: &XVWRPHUVSHF0DWHULDOSULFH Save your entries.
0DLQWDLQ&RQGLWLRQVmaintenance context: *&0 Select 1HZ(QWULHV.
=&0*##
Group: Save your entries.
1-3-6 In general condition maintenance, check if you can display condition master records of condition type PR00 in the condition maintenance group ZCMG##. 6$30HQXo0DVWHU'DWDo3ULFHVDQG&RQGLWLRQVo0DLQWDLQ &RQGLWLRQV &50
Application:
=&0*##
Maintenance group:
Choose ([HFXWH.
In the structure area on the left, select the fields &RQGLWLRQ7\SH and 6ROG 7R3DUW\. Click on 6HOHFWUHFRUGV (
)
In the dialog box that then appears, enter the following: 35
Condition Type:
1XPEHURI6WRFNPDQQ
Sold-To Party:
Choose ([HFXWH.
Condition records are displayed (at least one). However, it is not possible to change the master record because it was transferred from the ERP system and was not intended for processing in the SAP CRM system.
© SAP AG
CR100
9-37
2SWLRQDO([HUFLVHV 6HUYLFH 2-1
Conditions and Condition Maintenance in the CRM System
2-1-1 Create a service process of the type 6HUYLFH2UGHU with the business partner 6WRFNPDQQ$* and enter the product 5HSDLU with the TXDQWLW\ 68. 6$30HQXo6HUYLFHo0DLQWDLQ6HUYLFH3URFHVVHV
Choose&UHDWH7UDQVDFWLRQ(
icon).
Select 6HUYLFHo6HUYLFH2UGHU
Enter ##6WRFNPDQQ $* in the 6ROGWRSDUW\ field and confirm your entry. In the 3URGXFW field, enter the number 5HSDLU with the TXDQWLW\ 68 and confirm your entry.
2-1-2 Check in the transaction’s item details to see if the system found a FXVWRPHU GLVFRXQW (.). Click on the ,WHPGHWDLO button to see the item’s detail.
Choose the &RQGLWLRQV tab.
The list of displayed condition types does QRW include the entry 0K07.
2-1-3 Try entering a FXVWRPHUGLVFRXQW into the transaction manually, with a value of . Is this possible? Choose $SSHQG5RZ(
).
Ctyp:
.
Amount:
The minus sign (-) and unit (%) are added automatically. You do not need to save the transaction.
2-1-4 In the future, the customer should receive a FXVWRPHUGLVFRXQW (.) of for transactions of this type. This agreement should last from today until the end of the year. Maintain a condition master record in the 6$3&50 system accordingly.
6$30HQXo0DVWHU'DWDo3ULFHVDQG&RQGLWLRQVo0DLQWDLQ &RQGLWLRQV &50
Application:
%83$',6&28
Maintenance group: Choose
(([HFXWH).
…
© SAP AG
CR100
9-38
…
In the data area, enter the value 0K07 in the &RQGLWLRQ7\SH (&W\S) field on the right and confirm your entry. Enter: ,'(675
Sales Organization:
Distribution Channel:
Division:
1XPEHURI6WRFNPDQQ$*
Customer:
Amount:
WRGD\
Valid-From Date:
(QGRI\HDU
Valid-To Date: Save your data.
2-1-5 Create another sales transaction of the type 6HUYLFH2UGHU with the business partner 6WRFNPDQQ$* and enter the product 5HSDLU with the TXDQWLW\ 68. What do you notice about the conditions screen? Now the list of displayed condition types includes the entry 0K07 with the amount 3%. Save the transaction and note the number. _______________ >oGDWDVKHHW@
© SAP AG
CR100
9-39
2-2
Customizing Pricing 2-2-1 Take a look at the transaction from the previous exercise. 2-2-2 What pricing procedure was determined?
Open the transaction and select the 3ULFHVtab page in the 7UDQVDFWLRQGDWD.
3ULFLQJSURFHGXUH&50
2-2-3 What factors influence the determination of a pricing procedure? Where in the system are the concrete values of the factors for your business transactions from the previous exercise? Determining the pricing procedure can be affected by the following factors: 6DOHVRUJDQL]DWLRQ'LVWULEXWLRQFKDQQHO'LYLVLRQ'RFXPHQWSULFLQJ SURFHGXUHand&XVWRPHUSULFLQJSURFHGXUH.
The 6DOHVRUJDQL]DWLRQ'LVWULEXWLRQFKDQQHOand'LYLVLRQ are displayed in the transaction on the 2UJDQL]DWLRQ tab page. The document pricing procedure is assigned to the transaction type. $UFKLWHFWXUHDQG7HFKQRORJ\o&RQILJXUDWLRQo&XVWRPL]LQJ
Go to the 6$35HIHUHQFH,0*.
6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo 7UDQVDFWLRQVo%DVLF6HWWLQJVo'HILQH7UDQVDFWLRQ7\SHV Select entry =6##and click on the 'HWDLOVicon (
).
In the dialog structure, double-click on $VVLJQPHQWRI%XVLQHVV 7UDQVDFWLRQ&DWHJRULHV
Select the 6DOHV transaction category and double-click on &XVWRPL]LQJ KHDGHU in the dialog structure.
The document pricing procedure is called 6HUYLFH3URFHVV 6 .
The customer pricing procedure is stored in the sold-to party’ s master data. It is located in the sales area data related to this case on the %LOOLQJtab page. The customer pricing procedure is called 6WDQGDUG $ . ,'(675
Sales Organization:
Distribution Channel:
QRQH!
Division: Document Pricing Procedure: Customer Pricing Procedure:
© SAP AG
CR100
6
9-40
2-2-4 Can you make any changes to the pricing procedure in the SAP CRM system’ s Customizing? 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo %DVLF)XQFWLRQVo3ULFLQJo'HILQH6HWWLQJVIRU3ULFLQJo&UHDWH 3ULFLQJ3URFHGXUH
On the other hand, pricing procedures that were transferred by Customizing download from the SAP ERP system cannot be changed in the CRM system. This applies particularly to transactions from the 6DOHV area. 2-2-5 You want to display the customer-specific material price (which you created in SAP ERP) (FRQGLWLRQW\SH35) in general condition maintenance. To do this, set up a separate condition maintenance group – =&0* (PDLQWHQDQFHJURXS ##) – containing the corresponding condition table / condition type. Use a suitable description.
Specify that this condition maintenance group is in the GCM (general condition maintenance) context. 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo 0DVWHU'DWDo&RQGLWLRQVDQG&RQGLWLRQ7HFKQLTXHo&RQGLWLRQ 7HFKQLTXH %DVLFVo&UHDWH0DLQWHQDQFH*URXS
Select 1HZ(QWULHV.
=&0*
Maintenance group:
0DLQWHQDQFHJURXS
Description:
Confirm your input, select the new entry and go to &RQGLWLRQ0DLQWHQDQFH *URXS 'HWDLO. Select 1HZ(QWULHV. Counter: Application: Use: Condition table: Condition Type:
&50
35
6$3
35
Description: &XVWRPHUVSHF0DWHULDOSULFH Save your entries.
0DLQWDLQ&RQGLWLRQVmaintenance context: Select 1HZ(QWULHV.
*&0
=&0*
Group: Save your entries.
© SAP AG
CR100
9-41
2-2-6 In general condition maintenance, check if you can display condition master records of condition type 35 in the condition maintenance group =&0*##. 6$30HQXo0DVWHU'DWDo3ULFHVDQG&RQGLWLRQVo0DLQWDLQ &RQGLWLRQV &50
Application:
=&0*
Maintenance group:
Choose ([HFXWH.
In the structure area on the left, select the fields &RQGLWLRQ7\SH and 6ROG 7R3DUW\. Click on 6HOHFWUHFRUGV (
)
In the dialog box that then appears, enter the following: 35
Condition Type:
1XPEHURI6WRFNPDQQ
Sold-To Party:
Choose ([HFXWH.
Condition records are displayed (at least one). However, it is not possible to change the master record because it was transferred from the SAP ERP system and was not intended for processing in the SAP CRM system.
© SAP AG
CR100
9-42
&50%LOOLQJ &RXUVH2XWOLQH
8QLW
P\6$3 &50± $Q2YHUYLHZ
7UDQVDFWLRQ 3URFHVVLQJ
2UJDQL]DWLRQDO0DQDJHPHQW
3DUWQHU3URFHVVLQJ
%XVLQHVV3DUWQHUV
3URGXFW0DVWHU
$FWLYLW\ 0DQDJHPHQW
$FWLRQV
3ULFLQJ)XQGDPHQWDOV
&50%LOOLQJ
&500LGGOHZDUH
3HRSOH&HQWULF&50 $SSHQGL[
SAP AG 2004
© SAP AG
CR100
10-1
&50%LOOLQJ %LOOLQJ3URFHVV2YHUYLHZ %LOOLQJ&XVWRPL]LQJ
SAP AG 2004
© SAP AG
CR100
10-2
%LOOLQJ 8QLW2EMHFWLYHV $WWKHHQGRIWKLVXQLW\RXVKRXOGEHDEOHWR ([SODLQWKHP\6$3 &50%LOOLQJSURFHVV
&UHDWHDQGGHVFULEHELOOLQJGRFXPHQWV
1DPHWKH&XVWRPL]LQJVHWWLQJVUHOHYDQWIRU&50%LOOLQJ
SAP AG 2004
© SAP AG
CR100
10-3
%LOOLQJ %XVLQHVV6FHQDULR
,'(6ZRXOGOLNHWRXVHP\6$3 &50%LOOLQJIRU LQYRLFLQJVHUYLFHWUDQVDFWLRQVDQGVDOHVRUGHUV
SAP AG 2004
© SAP AG
CR100
10-4
,QWHJUDWLRQRI%LOOLQJLQWKH6DOHV6FHQDULR 4XRWDWLRQDQG2UGHU0DQDJHPHQWLQP\6$3 &50 &UHDWH TXRWDWLRQ
&UHDWH FXVWRPHU LQTXLU\
&UHDWH6DOHV 2UGHU
0RQLWRUVWDWXV RIRUGHU
$QDO\]HVDOHV SURFHVVHV
&UHDWHGHOLYHU\DQGSLFNSDFN DQGSRVWJRRGVLVVXH
&UHDWHLQYRLFH
SAP AG 2004
© SAP AG
CR100
10-5
([DPSOHRI,QWHJUDWLRQRI%LOOLQJLQ6HUYLFH6FHQDULR 6HUYLFH2UGHU0DQDJHPHQW 5HTXHVWD TXRWDWLRQ
&UHDWHDQG VXEPLWD TXRWDWLRQ
&UHDWH LQYRLFH
&RQYHUWWKH TXRWDWLRQLQWRD VHUYLFHRUGHU
3HUIRUPDQDO\VHV
$FFHSW TXRWDWLRQ
([HFXWH DVVLJQPHQW SHUIRUP FRQILUPDWLRQ
&UHDWHDQGRSWLPL]H DVVLJQPHQWV
SAP AG 2004
© SAP AG
CR100
10-6
6\VWHP/DQGVFDSH
6$3&50 &50 6DOHV 6HUYLFH
&50%LOOLQJ
6$3%:
6$35 6$3(&&
SAP AG 2004
You can bill for different business transactions directly in mySAP Customer Relationship Management (mySAP CRM). These transactions include: y Sales orders (with or without reference to delivery) y Service orders, service contracts, service confirmations, complaints processing Using CRM Billing, you can combine a service order item with a sales order item together in an invoice and thereby simplify communication with your customers. If you simply want to bill CRM sales orders and are currently using SAP Sales and Distribution (SAP SD), you have the option of using either SD Billing or CRM Billing. For billing contracts, service orders or confirmations or complaints, you should principally use CRM Billing. The R/3 components SAP FI-AR (Accounts Receivable) or FI-CA (Contract Accounting) have to be implemented if you wish to post billing documents in Financial Accounting. You need SAP BW for statistical reporting of billing documents
© SAP AG
CR100
10-7
3URFHVV2YHUYLHZ 7KHELOOLQJSURFHVVFRQVLVWVRIWKUHHPDMRUVWHSV ,QSXWSURFHVVLQJ %LOOLQJ
2XWSXWSURFHVVLQJ
EDGF!FCH!I J
DGKMLNH O1D P DGF!H LQDGK R
,QSXW SURFHVVLQJ
2XWSXW SURFHVVLQJ
%LOOLQJ
%LOOLQJ GXH OLVW
%LOOLQJ GRFXPHQWV
! %$ &( ' ) #"+" *
, ' -%.
24/13 5 0 6
798 ';: <= 3 / 0 ?> 6 <@ 4 9:;
GS@T DKUI@VGF W V TV
A <@ C$ 4&/10 -;B9-
SAP AG 2004
During LQSXWSURFHVVLQJ, CRM Billing takes over billing-relevant items from different business transactions and saves them as billing due list items. As of CRM Release 5.0, you can use an external interface to copy data from non-SAP systems to the CRM Billing due list. It supports the following formats: y IDoc; XML SOAP via HTTP; XML via the Exchange infrastructure y For more information, see the documentation for function module CRMXIF_BEA_DL_CRMB_SAVE. During ELOOLQJ, related billing due list items are also grouped together as far as possible from different CRM business transactions and transferred to a joint billing document. From the billing due list, you can process both single and collective billing from billing due list items and also trigger them to run in the background. You can cancel individual billing documents and also execute collective cancellations. The system transfers information on cancellations automatically to Financial Accounting. 2XWSXWSURFHVVLQJ consists of invoice output, the transfer to mySAP Financials, and retrieval for SAP BW. The ledger posting of billing data takes place either in SAP FI-A/R or in SAP FI-CA. CRM Billing provides all relevant billing data for the SAP Business Warehouse for statistical reporting.
© SAP AG
CR100
10-8
,QSXW3URFHVVLQJ %LOOLQJUHOHYDQW EXVLQHVV WUDQVDFWLRQVRUWUDQVDFWLRQLWHPV - &RQWUDFWV - 6HUYLFHFRQILUPDWLRQV - 'HOLYHULHV - 2UGHUV -« $XWRPDWLF %LOOLQJGXHOLVWLVFUHDWHG
7KH ELOOLQJ GXH OLVWLWHPV FRQWDLQ DOO WKH GDWD QHHGHG IRU ELOOLQJ
SAP AG 2004
As soon as you have saved a business transaction in which at least one item is relevant to billing, the system automatically transfers the data from this billing request item to the CRM Billing billing due list. The system executes the following steps, up to saving the billing-relevant data. CRM Billing uses the data from application Customizing to determine the item category of CRM Billing for the transferred data record. When the system cannot determine an item category (if, for example, the item category determination is not set up completely), the system has to reject the transferred data record because no billing is possible without the item categories. Here the system subjects the transferred items to a processing check, which, in the following cases, results in the rejection of transferred items: CRM Billing saves all successfully processed and completed data as billing due items. You can search for billing due list items using various selection criteria. You can display the details of each billing due list item. You can display the billing due list items, y That are blocked for billing y That are incomplete There are two ways of setting a billing block y You give the business transaction item the billing block status. y You block the billing item category for billing with the corresponding indicator.
© SAP AG
CR100
10-9
%LOOLQJ3URFHVV %LOOLQJ 0HWKRGV
• ,QGLYLGXDOELOOLQJ GLDORJ
• &ROOHFWLYHELOOLQJ GLDORJ
• &ROOHFWLYHELOOLQJ EDFNJURXQG
• &ROOHFWLYHELOOLQJ MREFRQWUROOHG
Billing split
K W DGK
DGF!FCHCIQJ Merging
P DGFCH LQDKMR
P DGF!H L DGKMR
DGKMLNH O1D
X CH FCF!H!I J PZY OQ[Q\]DGI T X CH FCF!H!I J PZY OQ[Q\]DGI T
X !H FCF!HCI J P Y OG[Q\]DGI T
SAP AG 2004
As a subprocess of billing, CRM Billing transfers billing due list items to billing document items and assigns these to the billing document headers. Therefore, billing documents (for example invoices, credit and debit memos) are created from items which come from a wide range of CRM Business Transactions. Split criteria in billing document header data includes the billing unit, payer, bill-to-party, billing document type, billing date, terms of payment and the 6SOLWFULWHULD field. You can also influence the splitting criteria via the copy requirements. For this, choose 6$3 ,PSOHPHQWDWLRQ*XLGH→&XVWRPHU5HODWLRQVKLS0DQDJHPHQW→ %LOOLQJ→ 'HILQH&RS\ 5HTXLUHPHQWV In the case of delivery-related CRM Billing, the billing status is changed in R/3 Delivery and the CRM billing document is updated in the SD document flow SAP note 504730 describes the 6XEVFULSWLRQIRUGRFXPHQWIORZRIGHOLYHU\LQ5.
© SAP AG
CR100
10-10
%LOOLQJ'RFXPHQWV +HDGHU GDWD 3D\HU %LOOLQJ W\SH %LOOLQJ GDWH %LOOLQJ XQLW «
,WHPGDWD
3URGXFW 4XDQWLW\ 3ULFHVDQGFRQGLWLRQV 6ROGWRSDUW\ «
SAP AG 2004
Billing documents are not exchanged between the CRP and ERP systems. As long as the invoices have not been transferred to Accounting, it is possible to make certain changes to the invoices (such as changing the value date), to the prices and to the texts. CRM invoices generate the sales data for the rebate. You can cancel individual billing documents and also execute collective cancellations. The system transfers information on cancellations automatically to Financial Accounting.
© SAP AG
CR100
10-11
2XWSXW3URFHVVLQJ
BBBB BBBB BBBB BBBB
;^4;
(53
%,
, ' -9.
7+8 '%: <@
([WHUQDO ,QWHUIDFH ;,)$GDSWHU
6 <= 9:
SAP AG 2004
Output processing in CRM Billing aids the transfer of follow-up applications and SAP tools with billing document data and is split into the following processes: y Output of invoicing documents through different output media (for example, printer, fax, e-mail or external output management systems) y Transfer of billing data to a range of SAP ERP accounting applications y Provision for the SAP Business Information Warehouse (SAP BI) y Connection of any non-SAP applications to the external interface of CRM Billing – You can find more information about connection under ,QWHUIDFHVIRUFRQQHFWLQJWRH[WHUQDOV\VWHPV.
CRM Billing enables invoice output through the following output media: Printer, Fax, E-mail, Optical Archiving, External printing channels (Pickup through CRM Billing XML Interface).
The SmartForm processes the invoice in the layout you require. The formation of a specific invoice depends on the billing type (for example invoices, credit or debit memos as well as cancellation documents) of the corresponding action.
You can monitor the transfer to Accounting (status, error handling).
You can carry out the transfer to Accounting separately (at a later point in time). You can enrich account determination either simply or flexibly (condition technique).
© SAP AG
CR100
10-12
%LOOLQJ 2SWLRQ 'LUHFW %LOOLQJ 3D\HU %LOOLQJ'DWHV
P HCK_D@O T ` HaF!FaH!I JNb
7UDQVDFWLRQ
%LOOLQJ 'RFXPHQW
2.
SAP AG 2004
Direct billing allows you to create billing documents directly, without having to explicitly process the billing due date. Prerequisite: the 'LUHFW%LOOLQJ indicator in the payer’s sales area data (billing tab page). Incomplete or blocked billing due list items cannot be billed directly. Incorrectly processed transactions appear in the billing due list. There is a BAdI for triggering direct billing under other conditions.
© SAP AG
CR100
10-13
%LOOLQJ 2SWLRQ %LOOLQJ 3ODQV %LOOLQJSODQSURFHGXUHWUDQVDFWLRQW\SHLWHPFDWHJRU\ ELOOLQJSODQW\SH 3D\HU
3HULRGLFELOOLQJ VXFKDVFRQWUDFWV
h dMe dMl _e i
i d f em e j
c c ' ' %;' ' aCB B d e j k l dMg dMh d i end e_e ef ek e_l fm
f d_m d_j eg fU^d
g dd d k eh
h d_e d_l ^e i
(85
0LOHVWRQHELOOLQJ VXFKDVSURMHFWV
h dMe dMl _e i
i d f em e j
c c ' ' %;' ' aCB B d e j k l dMg dMh d i end e_e ef ek e_l fm
f _d m d_j eg Uf d
g d d d k eh
r1sQtvuwExzy|{s1s
h d_e d_l ^e i
2 2 =oo ;%' ' aaB B d e i j k l dMf dMg d h d i e_m end ee ef e_j ek
f dMm dMj e g
g d_d dMk e_h
h dMe dMl _e i
i d_f e^m e^j
p p ' ' :4:+q q d e j k l dMg dMh d i end e_e ef ek e_l fm
f d m d j e_g fnd
(85
(85
p p ' ' :+:+q q d e j k l dMg d Mh d i end ee ef ek
pp '' BB d e j k l dMg dMh d i end e_e ef ek e_l fm
i dMf e_m _e j
f Md m dMj e g
g _d d dMk e_h
} s tvu~Exzyr1s s
h dMe dMl _e i }
i d_f e^m e^j
f d m d j e_g fnd
g ^d d d_k e^h
g ^d d d_k e^h
sQtvuwExzyr1s s
SAP AG 2004
The billing plan specifies when a certain amount is invoiced. Service contracts and leasing scenarios in particular use billing plans. As of CRM 5.0, it is also possible to map usage-based billing. Billing plans are also used in this case. You set up billing plan types and billing plan determination in Customizing: y 6$3,PSOHPHQWDWLRQ*XLGH→ &XVWRPHU5HODWLRQVKLS0DQDJHPHQW→ 7UDQVDFWLRQV→ %DVLF 6HWWLQJV→ %LOOLQJ3ODQ
© SAP AG
CR100
10-14
&XVWRPL]LQJ 2UJDQL]DWLRQDO 'DWD %LOOLQJVSHFLILFDVVLJQPHQWVRIRUJDQL]DWLRQDOXQLWV 6$35HIHUHQFH,0*
&XVWRPHU5HODWLRQVKLS0DQDJHPHQW 0DVWHU'DWD
2UJDQL]DWLRQDO0DQDJHPHQW
&URVV6\VWHP$VVLJQPHQWV
6DOHV2UJDQL]DWLRQ 6DOHV2UJDQL]DWLRQ
%8
&RPSDQ\&RGH
6DOHV2UJDQL]DWLRQ 6HUYLFH2UJDQL]DWLRQ
%8
&RPSDQ\&RGH
SAP AG 2004
The billing unit (BU) is a CRM business partner that has the role %LOOLQJ8QLW. The billing unit can be defined independently of the sales or service organization as a standalone. You can assign more than one sales organizations to a billing unit (cross-sales organization billing). A billing unit is uniquely assigned to a company code.
© SAP AG
CR100
10-15
%LOOLQJ 'RFXPHQW &XVWRPL]LQJ %LOOLQJGRFXPHQWVSHFLILF&XVWRPL]LQJVHWWLQJV 6$35HIHUHQFH,0*
&XVWRPHU5HODWLRQVKLS0DQDJHPHQW %LOOLQJ
'HILQH1XPEHU5DQJHV
'HILQH%LOOLQJ5HOHYDQFHRIWKH%XVLQHVV7UDQVDFWLRQ,WHPV
'HILQH%LOOLQJ7\SHV
'HILQH,WHP&DWHJRULHV
'HILQH,WHP&DWHJRU\'HWHUPLQDWLRQ
SAP AG 2004
To be able to use all the CRM Billing functions, you must maintain all the activities in the Implementation Guide under the %LOOLQJ node. For this, in IMG (SPRO) choose &XVWRPHU 5HODWLRQVKLS0DQDJHPHQW %LOOLQJ. Under 'HILQH%LOOLQJ7\SHV, you define billing types for CRM Billing. A billing type specifies a billing document’s characteristics and properties. The billing type attributes determine how the system behaves during billing. Under 'HILQH,WHP&DWHJRULHV, you define the item categories for CRM Billing. The item category determines the properties and characteristics of the billing due list items and the billing items. The item category attributes specify how the system behaves during input processing and billing. Under ,WHP&DWHJRU\'HWHUPLQDWLRQ, you make settings for item category determination in CRM Billing. Item Category Determination is used to define the item category for CRM Billing from data on CRM business transactions. There are two possible ways of doing this: y In the activity $VVLJQ,WHP&DWHJRU\, you can assign the item category for CRM Billing to a specific combination of transaction type (process type of source application) and an item category of the relevant CRM business transaction.
© SAP AG
CR100
10-16
&XVWRPL]LQJ )XUWKHU 6HWWLQJV $GGLWLRQDO&XVWRPL]LQJ6HWWLQJV ³6HUYLFHV´ 6$35HIHUHQFH ,0*
&XVWRPHU 5HODWLRQVKLS 0DQDJHPHQW %DVLF)XQFWLRQV
3ULFLQJ
3DUWQHU'HWHUPLQDWLRQ 7H[W'HWHUPLQDWLRQ
,QWHJUDWLRQ6HWWLQJV 6$35HIHUHQFH ,0*
&XVWRPHU 5HODWLRQVKLS 0DQDJHPHQW %LOOLQJ
,QWHJUDWLRQ
7UDQVIHUWR$FFRXQWLQJ
7UDQVIHUWR*OREDO7UDGH6HUYLFHV
SAP AG 2004
Under Service-related Customizing, you make settings for the services used by CRM Billing: pricing, partner processing, text processing, and action processing. Under Integration-related Customizing, you make settings for integrating Billing with accounting applications. Settings regarding document types, accounts and tax codes for accounting documents are made here.
© SAP AG
CR100
10-17
&RQILJXULQJ WKH %LOOLQJ $SSOLFDWLRQ
,QWHJUDWLRQZLWK&RQWUDFW$FFRXQWLQJ ),&$
6XSSOHPHQWDU\ LQYRLFH
,QWHUFRPSDQ\ELOOLQJ
0XOWLOHYHO LQWHUFRPSDQ\ ELOOLQJ ,QYRLFH VSOLW XVLQJ FRQGLWLRQV
*76LQWHJUDWLRQ
%LOOLQJ FRUUHFWLRQ 5HWURDFWLYH ELOOLQJ
&RXQWU\VSHFLILF IXQFWLRQV
SAP AG 2004
The Billing Engine Framework enables you to flexibly adjust the billing application. For details of the additional functions in the context of CRM Billing, see y 6$3,PSOHPHQWDWLRQ*XLGH→ &XVWRPHU5HODWLRQVKLS0DQDJHPHQW→ %LOOLQJ→ &RQILJXUH $SSOLFDWLRQ
© SAP AG
CR100
10-18
&50%LOOLQJ 8QLW6XPPDU\
([SODLQWKHP\6$3 &50%LOOLQJSURFHVV
&UHDWHDQGGHVFULEHELOOLQJGRFXPHQWV
1DPHWKH&XVWRPL]LQJVHWWLQJVUHOHYDQWIRU&50%LOOLQJ
SAP AG 2004
© SAP AG
CR100
10-19
© SAP AG
CR100
10-20
([HUFLVHV 8QLW
&50%LOOLQJ
7RSLF &UHDWLQJ%LOOLQJ'RFXPHQWV At the conclusion of this exercise, you will be able to: • Understand the organizational units needed for billing and the assignments of these units • Work with the billing due list and create individual billing documents • Carry out certain necessary Customizing settings to set up CRM Billing You want to settle sales and service transactions with CRM Billing and so you want to familiarize yourself with this application.
1-1
Relevant Organizational Data for CRM Billing. 1-1-1 Check if one or more billing units exist in the CRM system. Make a note of the numbers. 6HDUFKIRUEXVLQHVVSDUWQHUVWKDWKDYHWKHUROH%LOOLQJ8QLW %($
1-1-2 Check in Customizing which of these billing units was assigned to the sales organization 6DOHV86 1-1-3 Which company code is this billing unit assigned to? 1-2
Create a new order of the type 6DOHV7UDQVDFWLRQ(=6$/ for the customer 0HJDVWRUH and the product +7 SLHFH and maintain it in the sequence in the ERP system. 1-2-1 Save the order and check which pricing procedure was used. Save the order and note the number. __________________ >oGDWDVKHHW@ 1-2-2 Check whether your created order was transferred to SAP ERP.
© SAP AG
CR100
10-21
1-2-3 Go to the SAPERP system and deliver your order. Make a note of the delivery number. _____________ >oGDWDVKHHW@ 1-2-4 Can you find an entry for your process in the billing due list after carrying out the delivery? If not, why? ______________________________________________________ 1-2-5 Carry out picking and posting goods issue in the SAP ERP system for your process. 1-2-6 Open the billing due list billing in the CRM system again and check again if you can find your transaction within this list. 1-2-7 Create a billing document for your sales process. 1-2-8 Are accounting documents generated in the SAP ERP system? _________________________________ 1-3
Check the relevant Customizing for CRM Billing.
1-3-1 Check the %LOOLQJUHOHYDQFH indicator for the item category =6$/ (which was determined in your transaction). ______________ 1-3-2 Check out which item category for billing is assigned to your source process category /) 'HOLYHU\ in SAP ERP and source item category =6$/. ______________ 1-3-3 Take a look at the details for this item category. What billing type is used by default? Do billing due list items need to be released before they can be billed?
© SAP AG
CR100
10-22
2SWLRQDO([HUFLVHV 6HUYLFH 1-1
Relevant Organizational Data for CRM Billing. 1-1-1 Check if one or more billing units exist in the CRM system. Make a note of the numbers. 6HDUFKIRUEXVLQHVVSDUWQHUVWKDWKDYHWKHUROH%LOOLQJ8QLW %($
1-1-2 Check in Customizing which of these billing units was assigned to the sales organization 6DOHV86 1-2
Create a service confirmation of the type &RQILUPDWLRQ =6(& for the customer 0HJDVWRUH. 1-2-1 Create the confirmation with the following data and check which pricing procedure was used. &50%LOOLQJ##
Transaction Description: Executing Service Employee:
Sold-To Party:
1XPEHURI0HJDVWRUH
Product:
659B
Enter a service item on the 6HUYLFH tab page. Quantity:
Choose the status &RPSOHWH.
68
Save the confirmation and note the number. __________________ >oGDWDVKHHW@ 1-2-2 Create a billing document for your confirmation. 1-2-3 Are accounting documents generated in the SAP ERP system? _________________________________ 1-3
Check the relevant Customizing for CRM Billing.
1-3-1 Check the %LOOLQJUHOHYDQFH indicator for the item category 69&3 (which was determined in your transaction). ______________ 1-3-2 Check out which item category for billing is assigned to your source process category =6(& &RQILUPDWLRQ and source item category 69&3. ______________ 1-3-3 Take a look at the details for this item category. What billing type is used by default? Do billing due list items need to be released before they can be billed?
© SAP AG
CR100
10-23
© SAP AG
CR100
10-24
6ROXWLRQV 8QLW
&50%LOOLQJ
7RSLF &UHDWLQJ%LOOLQJ'RFXPHQWV
1-1
Relevant Organizational Data for CRM Billing. 1-1-1 Check if one or more billing units exist in the CRM system. Make a note of the numbers. 6$3PHQXo0DVWHU'DWDo%XVLQHVV3DUWQHUVo0DLQWDLQ%XVLQHVV 3DUWQHU Click on Open BP (
) and use the 3DUWQHUVE\%35ROHsearch help. %($ %LOOLQJ8QLW
BP role: Choose ENTER. Numbers of the billing units:
_________________________________________________________ 1-1-2 Check in Customizing which of these billing units was assigned to the sales organization 6DOHV86
6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo 0DVWHU'DWDo2UJDQL]DWLRQDO0DQDJHPHQWo&URVV6\VWHP$VVLJQPHQW RI2UJDQL]DWLRQDO8QLWVo$VVLJQ%LOOLQJ8QLWVWR6DOHV2UJDQL]DWLRQV
The sales organization Sales US is assigned %LOOLQJ8QLW. 1-1-3 Which company code is this billing unit assigned to?
6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo 0DVWHU'DWDo2UJDQL]DWLRQDO0DQDJHPHQWo&URVV6\VWHP$VVLJQPHQW RI2UJDQL]DWLRQDO8QLWVo$VVLJQ&RPSDQ\&RGHVWR%LOOLQJ8QLWV
Billing unit 33 is assigned &RPSDQ\&RGH. 1-2
Create a new order of the type 6DOHV7UDQVDFWLRQ(=6$/ for the customer 0HJDVWRUH and the product +7 SLHFH and maintain it in the sequence in the ERP system. 1-2-1 Save the order and check which pricing procedure was used. Save the order and note the number. __________________ >oGDWDVKHHW@
6$3PHQXo6DOHVo0DLQWDLQ6DOHV7UDQVDFWLRQV
Choose &UHDWH7UDQVDFWLRQ and then 6DOHV→6DOHV3URFHVV. Enter the data for the order. … © SAP AG
CR100
10-25
…
Select the +HDGHURYHUYLHZtab.
The pricing procedure found is &50 This pricing procedure was defined in the CRM system. 1-2-2 Check whether your created order was transferred to SAP ERP. Go to the transaction’s change mode. As soon as you are there, you will see in the document flow that there is a replicated sales document.
6ZLWFKEDFNWRGLVSOD\PRGH
1-2-3 Go to the SAPERP system and deliver your order. Make a note of the delivery number. 6$3PHQXo/RJLVWLFVo6DOHVDQG'LVWULEXWLRQo6DOHVo2UGHUo 'LVSOD\
Enter the order number of order you just created and choose 6DOHV 'RFXPHQWo'HOLYHU. Save the delivery. ___________ >oGDWDVKHHW@
1-2-4 Can you find an entry for your process in the billing due list after carrying out the delivery? If not, why? __________________________________________________ 6$3PHQXo6DOHVo%LOOLQJo0DLQWDLQ%LOOLQJ'XH/LVW
In the creation data, enter the value CRM-## as the user and select 0DLQWDLQ There is no entry for your process EHFDXVHJRRGVLVVXHKDVQRWEHHQ SRVWHG\HW.
1-2-5 Carry out picking and posting goods issue in the SAP ERP system for your process. 6$3(DV\$FFHVV0HQXo/RJLVWLFVo6DOHVDQG'LVWULEXWLRQo 6KLSSLQJDQG7UDQVSRUWDWLRQo2XWERXQG'HOLYHU\o&KDQJHo6LQJOH 'RFXPHQW Enter your outbound delivery number, confirm your entry by choosing ENTER and select )ROORZRQ)XQFWLRQVo&UHDWH7UDQVSRUW5HTXHVW.
Enter %DFNJURXQG in the )RUHJURXQG%DFNJUQGfield. In the $GRSWSLFN TXDQWLW\ field, select parameter 2 (to book goods issue immediately). 1-2-6 Open the billing due list billing in the CRM system again and check again if you can find your transaction within this list. 6$3PHQXo6DOHVo%LOOLQJo0DLQWDLQ%LOOLQJ'XH/LVW Now there will be an entry with your delivery number.
© SAP AG
CR100
10-26
1-2-7 Create a billing document for your sales process.
In the Billing Due List, select your entry and choose ,QGLYLGXDO%LOOLQJ.
Save the invoice. 1-2-8 Are accounting documents generated in the SAP ERP system?
6$3PHQXo6DOHVo%LOOLQJo0DLQWDLQ%LOOLQJ'RFXPHQWV
Go to the created billing document and choose 'LVSOD\'RFXPHQWIORZ.
In the document flow ( ). documents ( 1-3
), you can go to the created Accounting
Check the relevant Customizing for CRM Billing.
1-3-1 Check the %LOOLQJUHOHYDQFH indicator for the item category =6$/ (which was determined in your transaction). ______________ 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo %LOOLQJo'HILQH%LOOLQJ5HOHYDQFHRI7UDQVDFWLRQ,WHP&DWHJRULHV
Go to item category =6$/
Billing relevance: 'HOLYHU\5HODWHG&50%LOOLQJ 1-3-2 Check out which item category for billing is assigned to your source process category /) 'HOLYHU\ in SAP ERP and source item category =6$/.
,0* 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQW o%LOOLQJo,WHP&DWHJRU\'HWHUPLQDWLRQo$VVLJQ,WHP&DWHJRULHV
Choose &50% (CRM Billing).
Go to the line with 6RXUFH3URFHVV&DWHJRU\/) and 6RXUFH,WHP &DWHJRU\=6$/.
Billing item category ='(/ is assigned.
1-3-3 Take a look at the details for this item category. What billing type is used by default? Do billing due list items need to be released before they can be billed? ,0* 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQW o%LOOLQJo'HILQH,WHP&DWHJRULHV Select &50% (CRM Billing). Take a look at the details for item category ='(/ (
).
The billing type ,QYRLFH ) is stored as the default value.
The billing block indicator is not set; in other words, invoices do not have to be released.
© SAP AG
CR100
10-27
© SAP AG
CR100
10-28
2SWLRQDO([HUFLVHV 6HUYLFH 1-1
Relevant Organizational Data for CRM Billing. 1-1-1 Check if one or more billing units exist in the CRM system. Make a note of the numbers. Search for business partners that have the role %LOOLQJ8QLW (%($).
1-1-2 Check in Customizing which of these billing units was assigned to the sales organization 6DOHV86 1-2
Create a service confirmation of the type &RQILUPDWLRQ =6(& for the customer 0HJDVWRUH. 1-2-1 Create the confirmation with the following data and check which pricing procedure was used. 6$3PHQXo6HUYLFHo0DLQWDLQ6HUYLFH&RQILUPDWLRQV
Choose &UHDWH7UDQVDFWLRQ and then 6HUYLFH&RQILUPDWLRQ→&RQILUPDWLRQ. &50%LOOLQJ
Transaction Description: Executing Service Employee:
Sold-To Party:
1XPEHURI0HJDVWRUH
Product:
659B
Enter a service item on the 6HUYLFH tab page.
68
Quantity:
In the WUDQVDFWLRQGDWD, choose the 3ULFHV tab page.
The SULFLQJSURFHGXUH is =6599. It was created in the CRM system.
Choose the status &RPSOHWH.
Click on the &RPSOHWH button in the )DVW(QWU\ view (top). Save the confirmation and note the number. __________________ >oGDWDVKHHW@ 1-2-2 Create a billing document for your confirmation.
In the Billing Due List, select your entry and choose ,QGLYLGXDO%LOOLQJ.
Save the invoice. __________________ >oGDWDVKHHW@
© SAP AG
CR100
10-29
1-2-3 Are accounting documents generated in the SAP ERP system?
Go to the created billing document and choose 'LVSOD\'RFXPHQWIORZ. In the document flow ( ). documents ( 1-3
), you can go to the created Accounting
Check the relevant Customizing for CRM Billing.
1-3-1 Check the %LOOLQJUHOHYDQFH indicator for the item category 69&3 (which was determined in your transaction). 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo %LOOLQJo'HILQH%LOOLQJ5HOHYDQFHRI7UDQVDFWLRQ,WHP&DWHJRULHV
Go to item category 69&3
Billing-relevance: WUDQVDFWLRQUHODWHGELOOLQJDFFRUGLQJWRRUGHUTXDQWLW\ 1-3-2 Check out which item category for billing is assigned to your source process category =6(& &RQILUPDWLRQ and source item category 69&3.
,0* 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQW o%LOOLQJo,WHP&DWHJRU\'HWHUPLQDWLRQo$VVLJQ,WHP&DWHJRULHV
Choose &50% (CRM Billing).
Go to the line with 6RXUFH3URFHVV&DWHJRU\=6(& and 6RXUFH,WHP &DWHJRU\69&3.
Billing item category 6&1 is assigned.
1-3-3 Take a look at the details for this item category. What billing type is used by default? Do billing due list items need to be released before they can be billed? ,0* 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQW o%LOOLQJo'HILQH,WHP&DWHJRULHV Select &50% (CRM Billing). Take a look at the details for item category 6&1 (
).
The billing type ,QYRLFH6HUYLFH7UDQVDFWLRQ =)6( is stored as the default value.
The billing block indicator is not set; in other words, invoices do not have to be released.
© SAP AG
CR100
10-30
&500LGGOHZDUH &RXUVH2XWOLQH
8QLW
P\6$3 &50± $Q2YHUYLHZ
7UDQVDFWLRQ 3URFHVVLQJ
2UJDQL]DWLRQDO0DQDJHPHQW
3DUWQHU3URFHVVLQJ
%XVLQHVV3DUWQHUV
3URGXFW0DVWHU
$FWLYLW\ 0DQDJHPHQW
$FWLRQV
3ULFLQJ)XQGDPHQWDOV
&50%LOOLQJ
&500LGGOHZDUH
3HRSOH&HQWULF&50 $SSHQGL[
SAP AG 2004
© SAP AG
CR100
11-1
&500LGGOHZDUH &500LGGOHZDUH2YHUYLHZ %XVLQHVV'RFXPHQWV %'RFV 0RWLYDWLRQ 'DWD([FKDQJH6$3&50² 6$35 &RQVLVWHQF\DQG0RQLWRULQJRIWKH 'DWD([FKDQJH
SAP AG 2004
© SAP AG
CR100
11-2
&500LGGOHZDUH 8QLW2EMHFWLYHV $WWKHHQGRIWKLVXQLW\RXVKRXOGEHDEOHWR 'HVFULEHWKHPDLQWDVNVRIWKH&500LGGOHZDUH
([SODLQGDWDH[FKDQJHEHWZHHQ6$3&50DQGDQ(53V\VWHPDQG SHUIRUPWKLV
$GPLQLVWUDWHWKHHVVHQWLDOIHDWXUHVRIGDWDH[FKDQJH
$VVHVVPRQLWRULQJRSWLRQVIRUGDWDH[FKDQJH
SAP AG 2004
© SAP AG
CR100
11-3
7HFKQLFDO,QWHJUDWLRQYLD&500LGGOHZDUH
&500LGGOHZDUH 3URYLGHVVHDPOHVVEDFNHQGLQWHJUDWLRQ 3URYLGHVJURXSZDUHLQWHJUDWLRQ 6\QFKURQL]HV0RELOH&OLHQWV ,VDQLQWHJUDOSDUWRIWKH&506HUYHU
&500LGGOHZDUH
5HTXLUHV
1RH[WUDVRIWZDUH 1RH[WUDLQVWDOODWLRQ 1RH[WUDVHUYHU
SAP AG 2004
The CRM enterprise with the CRM middleware and CRM applications is at the core of the CRM system landscape. It takes advantage of all the benefits of the SAP Web Application Server, including load balancing, high availability, integration, and security. The CRM server can run as a stand-alone solution or with various back-end systems. If SAP R/3 is the back-end system, only a plug-in is needed to handle data exchange with the SAP CRM server. CRM middleware handles data exchange with third-party systems. mySAP CRM supports two types of mobile scenarios: Laptop computers and handheld devices. Laptops employ the solutions for mobile sales and mobile service, which are synchronized (using the CRM middleware) with the applications on the SAP CRM server. Handheld applications can be used in either online or offline mode. The exchange of information between SAP CRM and other components, such as SAP BW and ERP back-end systems, occurs over the CRM middleware.
© SAP AG
CR100
11-4
&506\VWHP/DQGVFDSH
*URXSZDUH
&RPPXQLFDWLRQ 6WDWLRQ
&506HUYHU
6$3%: 6$3(53 %DFNHQG
0RELOH&OLHQWV
SAP AG 2004
The &506HUYHU contains the CRM middleware, which handles the data exchange with internal applications and external major components, such as an SAP ERP systems used as the back-end, an SAP Business Information Warehouse or non-SAP systems. The CRM middleware also synchronizes the databases of mobile clients with the CRM database. 0RELOH&OLHQWV are normally laptop computers on which the 0RELOH6DOHV0RELOH6HUYLFH DSSOLFDWLRQ is executed. Mobile clients typically connect temporarily (for example, via modem) to the CRM Server for data exchange. The mobile clients are connected to the CRM Server via the FRPPXQLFDWLRQVWDWLRQ. 6$3%: (the SAP Business Information Warehouse) is the SAP data warehouse application. The CRM middleware can exchange messages with QRQ6$3(53V\VWHPV via standard interfaces, for example, XML – SOAP. *URXSZDUHVROXWLRQV that are supported: Microsoft Exchange and Lotus Domino. If you want to link more than one CRM system or more than one ERP system, see Notes 640570 and 853430.
© SAP AG
CR100
11-5
&506HUYHU$UFKLWHFWXUH &506HUYHU &500LGGOHZDUH C
PDLQSDUW
+ E: < >C DF ! @ %J HG I K + 7MIONP F: !-Q>$ $ % +" : + 3-AB: + : "8 L(: R^TS>U V WbYXc [Z5(S >\T^]?_L(Z2Wda` >\ 2S
&506HUYHU$SSOLFDWLRQV
+ "8< 79=%; $> : 2' ! =? @
• • •
! #" $ '&( ) ,+ /. % * " *-.% *
%XVLQHVVREMHFWV • • •
0 !-1 2 1 4 3 1 #0 5'6! 3
1HW:HDYHU $SSOLFDWLRQ6HUYHU 6$3:HE$SSOLFDWLRQ6HUYHU
&50'DWDEDVH
SAP AG 2004
The data exchange between the CRM Middleware and external systems is performed via adapters. The adapters map and convert data between various formats. The CRM system supports the handling of &50EXVLQHVVREMHFWV, such as business partners, activities and opportunities, products and product catalogs, in several CRM functional areas such as Internet Sales, Service Interaction Center, Telesales, and Campaign Management. The CRM Server applications exchange data with the CRM middleware via the &50$GDSWHU. Business Document (BDoc) messages are used for data exchange and data processing within a CRM system environment (business documents process and transport business objects as one unit). Synchronization BDocs handle data synchronization with mobile clients; messaging BDocs are used for messaging between components such as SAP ERP and SAP CRM.
© SAP AG
CR100
11-6
%XVLQHVV'RFXPHQWV %'RFV 0RWLYDWLRQ ,GHD SURFHVVRUWUDQVSRUWEXVLQHVVREMHFWVDVRQHXQLW 0RELOH&OLHQWV (53
([FKDQJH FXVWRPHU 6PLWK .1$ $'5& .199
0RELOH&OLHQWV (53
0LGGOHZDUH%URNHU
0LGGOHZDUH%URNHU
%'RF ³6PLWK´
SAP AG 2004
The motivation for using %XVLQHVV'RFXPHQWV %'RFV as a data container for processing business objects that logically belong together (for example, all data about one order or one partner and so on) and for transporting them as one unit is that this avoids having to process or transport several individual table entries. %'RFPHVVDJHV are used for data processing within the CRM system and for data replication toward Mobile Clients. %'RFW\SHV are defined and managed in the BDoc Repository with the the BDoc Modeler.
© SAP AG
CR100
11-7
:KDWDUH%'RFV" 'LVWLQFWLRQ
.1$
%'RF W\SH VWUXFWXUH
$'5& .199
%'RF PHVVDJH &XVWRPHU%'RF ³6PLWK´ 7$6. ³XSGDWH´ )LHOGV &,7< ³1HZ
%'RF FODVVHV e 0HVVDJLQJ%'RFV
e
6\QFKURQL]DWLRQ %'RFV PRELOHRQO\
DOVR ³LQVHUW´RU³GHOHWH´ P%'RF 6%'RF
SAP AG 2004
When talking about %'RFV, a distinction must be made between BDoc type, the BDoc instance and the BDoc message: y A %'RFW\SH or structure must be defined for each required business object, for example, Contact Person, Sales Order. It contains all table entries that make up the corresponding business object. y A %'RFLQVWDQFH is a concrete example of a given BDoc type containing all field values. It does not exist as a BDoc yet but is still to be found in the database. y A %'RFPHVVDJH (or just %'RF) contains modified fields only. These include new fields and deleted fields. The difference between a BDoc message and a BDoc instance is that there is only one BDoc instance for a business object but there can be multiple BDoc messages (with their own IDs) for one BDoc instance. However a BDoc instance is replicated to a mobile client using a BDoc message where all fields are filled.
© SAP AG
CR100
11-8
,QERXQG DQG2XWERXQG 3URFHVVLQJ 6$35RUDQ\RWKHUV\VWHP
4XHXH 5$GDSWHU ,QERXQG
P%'RF
2XWERXQG
$GPLQ &RQVROH
9DOLGDWLRQ
P%'RF
&50'% &50DSSOLFDWLRQV
5$GDSWHU 4XHXH
SAP AG 2004
During data exchange, data is transferred to the CRM server via the appropriate queue. The data is validated through a validation service. The messaging layer uses PHVVDJLQJ%'RFW\SHV for data exchanges with the CRM Server applications, ERP back-ends and external systems. The Administration Console will determine the receivers of the data. The appropriate adaptor services are called and sent to the outbound queue. The CRM middleware can apply simple intelligent replication to Messaging BDoc types. A messaging BDoc type acts like an envelope: The CRM middleware cannot access the data inside the envelope but can access data on the envelope. Each application uses different address information so that, for example, sales orders can be routed according to the sales organization.
© SAP AG
CR100
11-9
'DWD([FKDQJHEHWZHHQ(53%DFN(QGDQGWKH&50 6\VWHP ,QLWLDODQG'HOWD/RDG FRQWUROOHGE\2EMHFW 0DQDJHPHQW
&50 6\VWHP
(53 6\VWHP
'HOWD/RDGFRQWUROOHGE\ $GPLQLVWUDWLRQ&RQVROH
SAP AG 2004
Initial data transfers from ERP to the system are controlled by 2EMHFW0DQDJHPHQW. Here you can use filter criteria to restrict the scope of the data according to your requirements. These filter criteria then apply for the delta data exchange too. To start the initial load, using Transaction R3AS (6$3PHQX→$UFKLWHFWXUHDQG7HFKQRORJ\→ 0LGGOHZDUH→'DWH([FKDQJH→,QLWLDO/RDG→6WDUW) When changing filter criteria later, this must be checked very carefully as, in some circumstances, it can lead to inconsistencies in the data set. Allocation of data from CRM to other systems (including ERP) is controlled by the $GPLQLVWUDWLRQ FRQVROH.
© SAP AG
CR100
11-10
5HSOLFDWLRQ$GPLQLVWUDWLRQ² $GPLQLVWUDWLRQ&RQVROH 6WDUOLNHUHSOLFDWLRQ
1RKLHUDUFKLFDOGLVWULEXWLRQQHWZRUNV 5HSOLFDWLRQWRVLWHVQRWSHUVRQV $GPLQ &RQVROH
6LWH( 1RQ6$3 V\VWHP
(
' $ %
&
6LWH' 5%DFNHQG 6LWHV$& 0RELOH&OLHQWV
SAP AG 2004
The replication takes place in a star-like fashion from the CRM Server to the Mobile Clients (sites A, B and C), SAP R/3 back-ends (site D) or non-SAP back-ends (site E). There is no KLHUDUFK\ in this system. The data is therefore stored in the CRM database and in the local client databases. No storage repository exists for regulating distribution. Data is replicated to VLWHV (local databases) and not to individual persons. A UHSOLFDWLRQPRGHO defines the rules for how data is distributed. The replication model is created and administered in the Administration Console. The main tasks performed with the $GPLQLVWUDWLRQ&RQVROH are: y Setting up and maintaining the UHSOLFDWLRQ, that is, maintaining replication objects, publications and subscriptions y Managing mobile employee (users) and their passwords y Defining sites, the logical representation of data receivers within the CRM Middleware y Assigning employees to sites (site type Mobile Client only) y Defining and administering organizational structures. To call the administration console, choose the following path: $UFKLWHFWXUHDQG7HFKQRORJ\→ 0LGGOHZDUH→$GPLQLVWUDWLRQ→ $GPLQLVWUDWLRQ&RQVROH(Alternatively, you can use Transaction SMOEAC).
© SAP AG
CR100
11-11
5HSOLFDWLRQ0RGHO %'RF f ! g+$ 2hJ ' 1 5)1 5HSOLFDWLRQ2EMHFW f K ''Q1 ! i2'!0j 4+$ #Q1$& !- /$$6 * f ?!/ ' $ /' k ml $ / 3XEOLFDWLRQ f G ! * $ * !-1+ * !l- ml' $ / 6XEVFULSWLRQ f " ! F=/ $1 Hl!-M / mlk /$ / 6LWH$ 6LWH% 6LWH&
SAP AG 2004
The above model describes simple intelligent replication - such as transfer of data to the mobile client. You can call the BDoc modeler via the following path: 6$3PHQX→$UFKLWHFWXUHDQG7HFKQRORJ\→ 0LGGOHZDUH→'HYHORSPHQW→0HWD2EMHFW0RGHOLQJ→%'RF0RGHOHU Replication Objects, Publications and Subscriptions can be administered via the Administration Console (SMOEAC). There is a 1:1 relationship between BDoc and Replication Object. There is a 1:n relationship between Replication Object and Publication (mBDoc). There is a 1:n relationship between Publication and Subscription.
© SAP AG
CR100
11-12
&50'%
53OXJ,Q
2EMHFW0DQDJHPHQW² ,QLWLDO/RDG
5 $GDSWHU
&506HUYHU
5'%
(536\VWHP
6LQJXODUGDWDORDGIURPRQHV\VWHPRUGDWDEDVHWRDQRWKHU
'XHWRGHSHQGHQF\RIREMHFWVDVSHFLILFVHTXHQFHGXULQJGDWDORDG LVQHFHVVDU\ &XVWRPL]LQJ
%XVLQHVVREMHFWV
3DUHQWFKLOGUHODWLRQVKLSEHWZHHQGLIIHUHQWREMHFWV
SAP AG 2004
You can load customizing and business objects from SAP backend system to SAP CRM. Usually a customizing load is started before business objects are loaded. Occasionally, the sequence in which objects are loaded may be significant, for example when downloading customer material info records from SAP ERP. In such cases, you must load information for business partners, material masters and plants first before you begin to load customer material information.
To start initial data transfer, choose in the SAP menu → Architecture and Technology → Middleware → Data
Exchange → Initial Data Transfer.
© SAP AG
CR100
11-13
%DFN(QG,QWHJUDWLRQ² 6XSSRUWHG2EMHFWV &XVWRPL]LQJ &XVWRPL]LQJ 3ULFH 3ULFH &RQGLWLRQV &RQGLWLRQV
%XVLQHVV3DUWQHUV %XVLQHVV3DUWQHUV 3URGXFWV 3URGXFWV
6DOHV2UGHUV 6DOHV2UGHUV
&50
4XRWDWLRQV 4XRWDWLRQV
5
%XVLQHVV %XVLQHVV
DJUHHPHQWV DJUHHPHQWV
n n odoaoaodp5p5q(q(rarbsOt rdrvuuxw wp(pLovLqLq(ycyTzvLraras s { { || t t } } } t t rdrvu8u8~2~5s s bYs sOqLqd{ {
SAP AG 2004
$GDSWHUREMHFWV can be exchanged between a source system and a target system, for example, between an SAP R/3 system and the CRM Server. Examples are business partner master data, orders and product master data. Load objects are stored in the SMOFOBJECT table. They are grouped as follows: y Business objects y Customizing objects y Condition objects Which objects are loaded to which target systems depends on the business process and has been defined for each application. Generally, initial loads and delta loads can be performed from SAP R/3 (SAP ECC) to CRM and vice versa (and CRM to CDB in case of a mobile scenario). However, conditions will be loaded only from SAP R/3 (SAP ECC) to CRM. Sales orders will usually be loaded from CRM to SAP R/3 (SAP ECC) for further execution.
© SAP AG
CR100
11-14
2EMHFW0DQDJHPHQW² /RDG)LOWHULQJ ,QLWLDO'HOWD 2EMHFWVSHFLILF ILOWHU FULWHULD %XVLQHVVREMHFWV 1DPH $WWULEXWH %LOORI0DWHULDO &RQWDFW &XVWRPHUV
'HVFULSWLRQ &ODVVLILFDWLRQ $WWULE %LOORI0DWHULDO &RQWDFW3HUVRQ0DVWHU &XVWRPHU0DVWHU
D
2EMHFWILOWHUVHWWLQJV 7DEOH
[
:
)LHOG
-F
K
23
/RZ
-
+LJK
>$ ' Ë Ë Ë Ë Ë Ë Ë Ë
*
,QDFWLYH
;
SAP AG 2004
The objects to be exchanged between CRM and SAP R/3 systems can be filtered using ILOWHU FULWHULD. Filters for the initial load are also used for the delta load from the SAP R/3 system. For the initial load toward the SAP R/3 system, there is no filtering of the load objects. Filter settings, which are stored in table SMOFFILTAB, refer to table fields. The filter for business objects are predefined (stored in table SMOFFILFLD) whereas filters for customizing or condition objects can be set on existing fields. Filter options allow the filtering of business objects at the source, at the target, or at both the source and the target for business objects. However, business data are usually filtered at the source. Customizing or condition objects can be filtered at the source only. Saving a filter entry triggers the automatic transfer to the Plug-In in SAP R/3. The transaction to specify the filter criteria is found under $UFKLWHFWXUHDQG7HFKQRORJ\! 0LGGOHZDUH!'DWD([FKDQJH!2EMHFW0DQDJHPHQW!%XVLQHVV2EMHFWV&XVWRPL]LQJ 2EMHFWV&RQGLWLRQ2EMHFWV.
© SAP AG
CR100
11-15
6WDUWLQJDQG0RQLWRULQJWKH,QLWLDO/RDG
6WDUWLQJ
6HOHFWWKHREMHFWVWREHORDGHGIURPWKH6$35V\VWHPRUIURPWKH &50GDWDEDVH
6HOHFWWKHVRXUFHDQGGHVWLQDWLRQVLWHV
6WDUWWKHLQLWLDOORDG
0RQLWRULQJ
0RQLWRU2EMHFWV
8VHWKH0LGGOHZDUH3RUWDO
SAP AG 2004
The transaction to start the initial load can be found at $UFKLWHFWXUHDQG7HFKQRORJ\→0LGGOHZDUH →'DWD([FKDQJH→,QLWLDO/RDG→6WDUW. While there are no restrictions for UHSHDWLQJGDWDWUDQVIHUV from SAP R/3 to CRM, data transfers from CRM to the consolidated database follow a different logic. To avoid inconsistencies between the consolidated database and mobile application databases, a repeated initial data transfer from CRM to the consolidated database is prevented. If you are sure that no Mobile Clients have been supplied with data or that no data can be extracted again, then a repeated initial data transfer from CRM to the consolidated database can be carried out. To do this, you must change an entry in table SMOFINICUS (for more information, go to the SAP Library). The transaction used to monitor the initial load is under $UFKLWHFWXUHDQG7HFKQRORJ\→0LGGOHZDUH →'DWD([FKDQJH→,QLWLDO/RDG→0RQLWRU2EMHFWV. If the initial data transfer is not successful, have a look at SAP Note 309734. This contains some useful hints on making a JHQHUDOHUURU DQDO\VLV. You can also use the 0LGGOHZDUH3RUWDO or 0RQLWRULQJ&RFNSLW under $UFKLWHFWXUHDQG 7HFKQRORJ\→0LGGOHZDUH→0RQLWRULQJ→&HQWUDO0RQLWRULQJ→0RQLWRULQJ&RFNSLW.
© SAP AG
CR100
11-16
'DWD&RQVLVWHQF\
&50
5
'DWD,QWHJULW\0DQDJHU
6\QFKURQL]DWLRQRIWUDQVDFWLRQDOGDWD
5HTXHVWV
)RUGDWDZLWKQRGHOWDORDGFDSDELOLW\
SAP AG 2004
In certain cases, you need tools to correct data inconsistency. y Data Integrity Manager: more information on one of the next slides. y Requests: If you already know where the inconsistencies are you can use a request. The request loads selected data (business, customizing data and conditions) from an ERP Back-End to the CRM Database or vice versa. Note that the Request of objects from the CRM Database to an ERP Back-End is not supported for all objects. The transactions to define and start a request are R3AR2 and R3AR4, respectively.
© SAP AG
CR100
11-17
(QKDQFHG² 'DWD,QWHJULW\0DQDJHU &URVVFRPSRQHQWGDWDLQWHJULW\ )XQFWLRQVDWDJODQFH
)UDPHZRUNIRUFRPSDULQJDQGUHV\QFKURQL]LQJ GDWDEDVHV &RPSDULVRQRIEXVLQHVVREMHFWV
(53 %DFNHQG
$WREMHFWLQVWDQFHOHYHO $WILHOGOHYHO
6\QFKURQL]DWLRQRIEXVLQHVVREMHFWV /RDGLQJRIPLVVLQJREMHFWV 6\QFKURQL]DWLRQRI REMHFWGHWDLOV
L]H URQ K F V\Q 5H
&RPSDULVRQ
&506HUYHU
1RQ6$3 6\VWHP ^! ? Q$
SAP AG 2004
With the Data Integrity Manager (DIMa), you can detect and repair inconsistencies between objects across components within the SAP CRM system landscape. An SAP CRM system landscape usually consists of more than one database. Every SAP CRM system has a CRM database. In most cases data exchange with one or more SAP R/3 back-end systems is necessary. A FRQVROLGDWHGGDWDEDVH is the basis for data exchange with mobile clients. It is very important to keep the objects in the different databases or datasets synchronized. The Data Integrity Manager compares data in different components and displays inconsistencies. The data comparisons are always carried out for the CRM database and an R/3 back-end database, and the CRM database and the consolidated database. For many objects, it is also possible to synchronize the data via the Data Integrity Manager. There are two compare types available in the Data Integrity Manager: header compare and detail compare. A header compare checks if an object instance exists in both databases. A detail compare compares all data of an object instance found in both databases. Some objects may not allow a header compare. The detail compare is then carried out.
© SAP AG
CR100
11-18
0RQLWRULQJ2YHUYLHZ
&500LGGOHZDUH 0RQLWRULQJ&RFNSLW
+$ 2 K Q !-1 c 7 D1 " 1 &506HUYHU
+ $ K ! 3cK % *
%'RF )ORZ
+$ 2E K 1 79D" 7
D
H1'Q!-1 1 1 + : i2E!-'&
%xA
^
7cD" :
++$ ' !
6$35V\VWHP
Q!-1 1/1
7cD"
! !- % QL 2 H
+$ 2 7 D" 1 1 -!K 1'Q!M1 9
F1 'Q!-1 1 1
SAP AG 2004
Useful transactions: y SMWP (Monitoring Cockpit) y SMW00 (Error Handler) y SMW01 (Display BDoc Messages) y SMW02 (BDoc Message Summary) y SMQ1 (Outbound Queue Monitor) y SMQ2 (Inbound Queue Monitor) y SMQR (Queue-In Scheduler) y SMQS (Queue-Out Scheduler) y SMWT (Middleware Trace) y R3AS (Start Initial Load) y R3AC6 (Define Middleware Parameters) y R3AR2 (Define Requests) y R3AR3 (Monitor Requests) y R3AR4 (Start Requests) y SDIMA (Data Integrity Manager) y SBDM (BDoc Modeler)
© SAP AG
CR100
11-19
'LVSOD\LQJ%'RF 0HVVDJHV² 60: 5HSURFHVV%'RF PHVVDJH 'HOHWH%'RF PHVVDJH
k!-- &
*
Q!- * ! !- ! % H QL G
6HOHFWD %'RF PHVVDJH
+$ 2H' K +$ 2H' 2h/K + +?$ 2H' K $ $+ +$ 2 k!-K + I
0! '1E!/l * !? E/# 3cK *
SAP AG 2004
The 'LVSOD\%'RF0HVVDJHV function lists all BDoc messages (transaction SMW01). It displays the following: y The BDoc ID and BDoc type, the BDoc state, the flow context, the queue name, the date and time when the BDoc message was sent y The flow trace, the data and error segments, the service in which the error occurred (last service reached), the recipient list y The succession of BDocs if a mobile scenario is in place Successfully processed messages appear with a green light, those still in process with a yellow light, and those with a terminal error condition with a red light. If a message is in process and does not get processed within a reasonable amount of time, it is possible to restart the message, view the message content, or discard the message. A BDoc message can be marked as deleted. (Note that deleting BDoc messages can lead to data inconsistencies however.) It is also possible to make a second attempt at processing. You should delete successfully-processed BDoc messages at regular intervals. This is usually done using fix-scheduled reorganization jobs.
© SAP AG
CR100
11-20
+LQWVIRUDQ(UURU$QDO\VLV /RDG([DPSOH /RDG&506HUYHUWR6$35V\VWHP
&KHFN%'RF PHVVDJHVLQFOXGLQJWKHPLGGOHZDUHWUDFHLQIRUPDWLRQ
&KHFNWKHRXWERXQGTXHXH
&KHFNWKHWDEOH%'2&B75$&.LQWKH6$35V\VWHP
&KHFNWKHRXWERXQGTXHXHRIWKH6$35V\VWHP
&KHFNWKHLQERXQGTXHXHRIWKHP\6$3 &50V\VWHP &506HUYHU
'HOWD /RDG
2XWERXQG TXHXHV
P%'RF
,QERXQG TXHXHV
6$35V\VWHP 'DWD8SORDGWR $SSOLFDWLRQ
6WDWXV LQIRUPDWLRQ
2XWERXQG TXHXHV
SAP AG 2004
A SRVVLEOHHUURUVLWXDWLRQ would be that a business object was changed in a CRM Server application, but the change (delta load) is not received in the SAP R/3 system. In case of errors or missing data updates in the target system, you can perform the following steps: y Check Display BDoc Messages including the middleware trace information. y Check the outbound queue y Check the table BDOC_TRACK in the SAP R/3 system (which shows information on the data handling of the R/3 application). y Check the outbound queue of the SAP R/3 system y Check the inbound queue of the mySAP CRM system In addition, you should verify the RFC destination and the logical system assigned to your site (in the Administration Console) and the CRM Middleware parameter settings in the CRM system and the SAP R/3 system (for example, CRMRFCPAR). (See also unit on installation and configuration.)
© SAP AG
CR100
11-21
&500LGGOHZDUH 8QLW6XPPDU\
'HVFULEHWKHPDLQWDVNVRIWKH&500LGGOHZDUH
([SODLQGDWDH[FKDQJHEHWZHHQ6$3&50DQGDQ(53V\VWHPDQG SHUIRUPWKLV
$GPLQLVWUDWHWKHHVVHQWLDOIHDWXUHVRIGDWDH[FKDQJH $VVHVVPRQLWRULQJRSWLRQVIRUGDWDH[FKDQJH
SAP AG 2004
© SAP AG
CR100
11-22
([HUFLVHV 8QLW
&500LGGOHZDUH
7RSLF $GPLQLVWUDWLRQ&RQVROH
At the conclusion of these exercises, you will be able to: • Make certain settings in the Administration Console and reproduce these. Settings in the Administration Console are instrumental in defining data distribution to other systems. For this reason, you should make sure you become familiar with some features of the Administration Console.
1-1
Familiarize yourself with the $GPLQLVWUDWLRQ&RQVROH. The Administration Console essentially specifies which data from the CRM system is to be distributed to other systems. 1-1-1 Start the Administration Console.
1-1-2 Display the details for the 6LWHobject. Display the details for the SAP R/3 site. What is the RFC destination of the site and what is the logical system? RFC destination: __________________ Logical system: __________________ 1-1-3 Take a closer look at the RFC destination and perform a test to find out which system is being addressed. To display the RFC destination, use Transaction QVP ($%$3FRQQHFWLRQV).
Find the corresponding destination and test this by carrying out a (test) remote login.
1-1-4 Examine the existing assigned subscription $OO%XVLQHVV3DUWQHUV 0(6* . What is the assigned publication and replication object used? _________________ _________________ Are there criteria values assigned to the subscription?
BBBBBBBBBBBBBBBBB
© SAP AG
CR100
11-23
© SAP AG
CR100
11-24
([HUFLVHV 8QLW
&500LGGOHZDUH
7RSLF 2EMHFW0DQDJHPHQWDQG'DWD7UDQVIHUV IURP6$3(53
At the conclusion of these exercises, you will be able to: • Make settings for data exchange of business partners from ERP to the CRM system. Before carrying out the initial data transfer, you need to perform some important preparatory tasks. This includes defining suitable filter criteria for data transfers. You familiarize yourself with Object Management to enable you to define data transfers from the ERP system to the SAP CRM system more accurately. 2-1
Familiarize yourself with 2EMHFW0DQDJHPHQW. In Object Management, you specify which data from the ERP system is to be transferred to the CRM system.
2-1-1 Take a look at the details for the &86720(5B0$,1business adapter object. Which Business Document (Bdoc) is the adapter object linked to? 2-1-2 Do filter settings exist which restrict loading of ERP business partner data? 2-1-3 In the ERP system, create a new (customer) business partner for the account group 6ROGWRSDUW\5!&50 and check whether this is transferred successfully to the SAP CRM system. Use transaction QYGor, alternatively, /RJLVWLFVPHQXo 6DOHVDQG'LVWULEXWLRQo0DVWHU'DWDo%XVLQHVV3DUWQHU o&XVWRPHUo&UHDWHo6DOHVDQG'LVWULEXWLRQ Enter a IRUPRIDGGUHVV, a QDPH and the FRXQWU\. Save the master record make a note of the number. ______________ 2-1-4 Does the business partner appear in SAP CRM? Perform a search in Business Partner Processing using the R/3 customer number. What number does the business partner have in the SAP CRM system? 2-1-5 Using the same method, take a look now at the details for the Customizing adapter object =&5BB'2. Which table does this object refer to? This information is relevant for the next exercise.
© SAP AG
CR100
11-25
© SAP AG
CR100
11-26
([HUFLVHV 8QLW
&500LGGOHZDUH
7RSLF ,QLWLDO'DWD7UDQVIHUV
At the conclusion of these exercises, you will be able to: • Perform an initial data transfer of Customizing data
You make filter settings in Object Management and transfer Customizing data from the ERP system.
3-1
In the following exercise, you make an initial data transfer of Customizing data. To do this, you use separately defined Customizing tables and adapter objects.
3-1-1 Display the contents of table =&5B in the ERP system.
Use transaction Q, QVHor,alternatively, 6$3PHQXo 7RROVo$%$3:RUNEHQFKo2YHUYLHZo'DWD%URZVHU Which contents are displayed? Which tables are displayed? Note the name of one continent. ______________________
3-1-2 Display the contents of table =&5B in the SAP CRM system. Which contents are displayed? 3-1-3 Define filter criteria for the data transfer (Customizing adapter object =&5BB'2). You want to perform an initial data transfer but restrict the data transfer by only transferring countries from one continent.
0DNHVXUH\RXHQWHUWKHILOWHUGHILQLWLRQFRUUHFWO\
3-1-4 Now perform the initial load for your table =&5B.
3-1-5 Display the contents of table =&5B in the SAP CRM system. Which contents are displayed now?
© SAP AG
CR100
11-27
© SAP AG
CR100
11-28
([HUFLVHV 8QLW
&500LGGOHZDUH
7RSLF 'DWD([FKDQJHDQG7URXEOHVKRRWLQJ
At the conclusion of these exercises, you will be able to: • Call a monitor that is important for data exchange • Reprocess erroneous BDoc messages It is inevitable that BDoc messages will occasionally be processed with errors. You deliberately cause an erroneous data transfer for a business partner, search for and locate the error and then rectify it.
4-1
In the following exercise you exchange business partner data between the ERP and SAP CRM systems and, in doing so, cause a deliberate error during data transfer. Using a suitable monitor, you perform an error analysis and rectify the problem.
4-1-1 In the 6$3&50 system, open the business partner 6WRFNPDQQ$*in &KDQJHPRGH
4-1-2 Change the customer 6WRFNPDQQ$* in the (53 system by entering an additional region for instance and then save the master record. 4-1-3 Check that this change is displayed in the SAP CRM system. To do this, exit the Business Partner transaction and restart it. 4-1-4 Take a look at the BDoc message that was generated during this data exchange. Use Transaction QVPZor 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUH o0RQLWRULQJo0HVVDJH)ORZo'LVSOD\%'RF0HVVDJHV
Select the EXVLQHVVSDUWQHUQXPEHUusing the queue name for example. To do this, you need to display additional selection options. 4-1-5 Take a look at the error message. Why does the message have the error status (E04)? 4-1-6 Ensure that the business partner ##Stockmann AG is not being processed in the CRM system and reprocess the BDoc message. Check that the data has been processed correctly by, for example, opening the business partner again.
© SAP AG
CR100
11-29
© SAP AG
CR100
11-30
6ROXWLRQV 8QLW
&500LGGOHZDUH
7RSLF $GPLQLVWUDWLRQ&RQVROH
1-1
Familiarize yourself with the $GPLQLVWUDWLRQ&RQVROH. The Administration Console essentially specifies which data from the CRM system is to be distributed to other systems. 1-1-1 Start the Administration Console. 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUHo $GPLQLVWUDWLRQo$GPLQLVWUDWLRQ&RQVROH
1-1-2 Display the details for the 6LWHobject.
Display the details for the SAP R/3 site. Choose the 6LWHREMHFWW\SH and then 'LVSOD\REMHFW ( Double-click
)
on the R/3 node.
Choose 6LWHDWWULEXWHV
What is the RFC destination of the site and what is the logical system?
The RFC destination is ',,Band the logical system is 7 &/17 . 1-1-3 Take a closer look at the RFC destination and perform a test to find out which system is being addressed. To display the RFC destination, use Transaction QVP ($%$3FRQQHFWLRQV).
Find the corresponding destination and test this by carrying out a (test) remote login.
Call transaction QVP and choose the $%$3FRQQHFWLRQ',,B.
Choose the 5HPRWH/RJLQ pushbutton.
A new session is started in the ERP system. Close the session again.
1-1-4 Examine the existing assigned subscription $OO%XVLQHVV3DUWQHUV 0(6* . Double-click either the $OO%XVLQHVV3DUWQHUV 0(6* entry in the structure tree on the left or in the detail area of the 5site (6XEVFULSWLRQV tab page).
What is the assigned publication and replication object used?
If you called up the details of the subscription, choose the 3XEOLFDWLRQV tab page. The publication name is $OO%XVLQHVV3DUWQHUV 0(6* Are there criteria values assigned to the subscription?
1RThe replication object is of the type simple unfiltered and cannot be assigned criteria values. © SAP AG
CR100
11-31
© SAP AG
CR100
11-32
6ROXWLRQV 8QLW
&500LGGOHZDUH
7RSLF 2EMHFW0DQDJHPHQWDQG'DWD7UDQVIHUVIURP 6$3(53
2-1
Familiarize yourself with 2EMHFW0DQDJHPHQW. In Object Management, you specify which data from the ERP system is to be transferred to the CRM system.
2-1-1 Take a look at the details for the &86720(5B0$,1business adapter object. Which Business Document (Bdoc) is the adapter object linked to? 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUHo'DWD ([FKDQJHo2EMHFW0DQDJHPHQWo%XVLQHVV2EMHFWV Select &86720(5B0$,1 and choose 'HWDLOV (
%83$B0$,1.
BDoc link:
).
2-1-2 Do filter settings exist that restrict loading of ERP business partner data? Choose the R/3 source site and the Filter Settings tab.
1RILOWHUVKDYHEHHQPDLQWDLQHG
2-1-3 In the ERP system, create a new (customer) business partner for the account group 6ROGWRSDUW\5!&50 and check whether this is transferred successfully to the SAP CRM system. 6$3PHQXo/RJLVWLFVo6DOHVDQG'LVWULEXWLRQo0DVWHU'DWDo %XVLQHVV3DUWQHUo&XVWRPHUo&UHDWHo6DOHVDQG'LVWULEXWLRQ Account group:
6ROGWR3DUW\5!&50
Form of Address:
&RPSDQ\
Choose (17(5.
7UDQVIHU
Name:
'(
Country:
Save the master record make a note of the number. ______________ 2-1-4 Does the business partner appear in SAP CRM? Perform a search in Business Partner Processing using the R/3 customer number. What number does the business partner have in the SAP CRM system? 6$3PHQXo0DVWHU'DWDo%XVLQHVV3DUWQHUVo0DLQWDLQ%XVLQHVV 3DUWQHU …
© SAP AG
CR100
11-33
… Using the Locator, search for the business partner. 2UJDQL]DWLRQ
Search:
5FXVWRPHUQXPEHU
By:
&XVWRPHUQXPEHU
(Number):
2-1-5 Using the same method, take a look now at the details for the Customizing adapter object =&5BB'2. Which table does this object refer to? This information is relevant for the next exercise. 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUHo'DWD ([FKDQJHo2EMHFW0DQDJHPHQWo&XVWRPL]LQJ2EMHFWV Select =&5BB'2 and choose 'HWDLOV ( Choose the 7DEOHV6WUXFWXUHV tab page
).
The table is =&5B#.
© SAP AG
CR100
11-34
6ROXWLRQV 8QLW
&500LGGOHZDUH
7RSLF ,QLWLDO'DWD7UDQVIHUV
3-1
In the following exercise, you make an initial data transfer of Customizing data. To do this, you use separately defined Customizing tables and adapter objects.
3-1-1 Display the contents of table =&5B in the ERP system.
6$3PHQXo7RROVo$%$3:RUNEHQFKo2YHUYLHZo'DWD%URZVHU =&5B.
Table Name:
Choose (17(5 followed by Execute (
).
Which contents are displayed?
FRXQWULHVDQGWKHUHOHYDQWFRQWLQHQWVDUHVKRZQ Which tables are displayed?
0$1'7, &28175< and &217,1(17. Note the name of one continent.
3-1-2 Display the contents of table =&5B in the SAP CRM system. Which contents are displayed? 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o$%$3:RUNEHQFKo 2YHUYLHZo'DWD%URZVHU Choose (17(5 followed by Execute ( 7KHUHOHYDQWWDEOHLVHPSW\
).
3-1-3 Define filter criteria for the data transfer (Customizing adapter object ZCR540_##_DO). You want to perform an initial data transfer but restrict the data transfer by only transferring countries from one continent.
0DNHVXUH\RXHQWHUWKHILOWHUGHILQLWLRQFRUUHFWO\
6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUHo'DWD ([FKDQJHo2EMHFW0DQDJHPHQWo&XVWRPL]LQJ2EMHFWV Select =&5BB'2 and choose 'HWDLOV (
).
Choose the Tables/Structures tab page and press the Filter pushbutton ( ). Select the 5 source site and then press Change (
).
…
© SAP AG
CR100
11-35
… Enter the following filter settings Field:
&217,1(17
Operator:
(TXDOWR =ORZ
LOW:
for example(8523(
Save the settings. You will receive a message confirming that these filter criteria have been changed successfully in the backend system.
3-1-4 Now perform the initial load for your table =&5B.
6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUHo'DWD ([FKDQJHo,QLWLDO/RDGo6WDUW =&5BB'2
Load object: Choose
(([HFXWH).
Acknowledge the popup.
3-1-5 Display the contents of table =&5B in the SAP CRM system. Which contents are displayed now? 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o$%$3:RUNEHQFKo 2YHUYLHZo'DWD%URZVHU Choose (17(5 followed by Execute (
).
The table now contains some entries with countries from the continent you entered in the filter criteria.
© SAP AG
CR100
11-36
6ROXWLRQV 8QLW
&500LGGOHZDUH
7RSLF 'DWD([FKDQJHDQG7URXEOHVKRRWLQJ
4-1
In the following exercise you exchange business partner data between the ERP and SAP CRM systems and, in doing so, cause a deliberate error during data transfer. Using a suitable monitor, you perform an error analysis and rectify the problem.
4-1-1 In the 6$3&50 system, open the business partner 6WRFNPDQQ$*in &KDQJHPRGH 6$3PHQXo0DVWHU'DWDo%XVLQHVV3DUWQHUVo0DLQWDLQ%XVLQHVV 3DUWQHU
Open the business partner ##Stockmann AG and switch to change mode.
4-1-2 Change the customer 6WRFNPDQQ$*LQWKHERP system by entering an additional region for instance and then save the master record. 6$3PHQXo/RJLVWLFVo6DOHVDQG'LVWULEXWLRQo0DVWHU'DWDo %XVLQHVV3DUWQHUo&XVWRPHUo&KDQJHo6DOHVDQG'LVWULEXWLRQ 1XPEHURI6WRFNPDQQ$*
Customer: Choose ENTER.
for example,
Region: Save your data.
4-1-3 Check that this change is displayed in the SAP CRM system. To do this, exit the Business Partner transaction and restart it. 6$3PHQXo0DVWHU'DWDo%XVLQHVV3DUWQHUVo0DLQWDLQ%XVLQHVV 3DUWQHU The changes are not displayed. 4-1-4 Take a look at the BDoc message that was generated during this data exchange. 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o0LGGOHZDUHo0RQLWRULQJ o0HVVDJH)ORZo'LVSOD\%'RF0HVVDJHV Select the EXVLQHVVSDUWQHUQXPEHUusing the queue name for example. Choose $GGIXUWKHUVHOHFWLRQRSWLRQV (
1XPEHURIEXVLQHVVSDUWQHU
Queue name: Choose
).
(([HFXWH).
If multiple entries are listed, search for the correct entry using transmission time and transmission date.
© SAP AG
CR100
11-37
4-1-5 Take a look at the error message. Why does the message have the error status (E04)?
Select the relevant entry (red traffic light) and choose %'RF0HVVDJH(UURU
5HFLSLHQW (
).
One of the messages indicates that the business partner is currently being processed. 4-1-6 Ensure that the business partner ##Stockmann AG is not being processed in the CRM system and reprocess the BDoc message. Check that the data has been processed correctly by, for example, opening the business partner again. Select your entry and choose 5HSURFHVV%'RF0HVVDJH (
).
The message that follows is very important and in this case you can answer using
© SAP AG
CR100
11-38
3HRSOH&HQWULF&50 &RXUVH$JHQGD
8QLW
P\6$3 &50± $Q2YHUYLHZ
7UDQVDFWLRQ 3URFHVVLQJ
2UJDQL]DWLRQDO0DQDJHPHQW
3DUWQHU3URFHVVLQJ
%XVLQHVV3DUWQHUV
3URGXFW0DVWHU
$FWLYLW\ 0DQDJHPHQW
$FWLRQV
3ULFLQJ)XQGDPHQWDOV
&50%LOOLQJ
&500LGGOHZDUH
3HRSOH&HQWULF&50
$SSHQGL[
SAP AG 2004
© SAP AG
CR100
12-1
3HRSOH&HQWULF&50
,QWURGXFWLRQ WR3HRSOH&HQWULF &50
6$31HW:HDYHU 3RUWDO3RUWDO&RQWHQW 3HRSOH&HQWULF 8,² $SSOLFDWLRQ 3RUWDODGPLQLVWUDWLRQ
3HRSOH&HQWULF 8,² &XVWRPL]LQJ
SAP AG 2004
© SAP AG
CR100
12-2
3HRSOH&HQWULF&50 8QLW2EMHFWLYHV $WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWR 1DPHVRPHEDVLFSURSHUWLHVRI3HRSOH&HQWULF&50
8QGHUVWDQGWKHUROHFRQFHSW
([SODLQSHUVRQDOL]DWLRQRSWLRQVLQ3&8, 0DNHVLPSOHFKDQJHVWRSRUWDOFRQWHQW
SAP AG 2004
© SAP AG
CR100
12-3
3HRSOH&HQWULF&50DQGWKH6$31HW:HDYHU 3RUWDO 7KH6$31HW:HDYHU 3RUWDOLVDSUHUHTXLVLWHIRU XVLQJ3HRSOH&HQWULF&50 (53
%,
&506\VWHP
6$3 1HW:HDYHU 3RUWDO
«
&50DSSOLFDWLRQV
%URZVHU
SAP AG 2004
The SAP NetWeaver Portal enables users to access various SAP and non-SAP applications as well as documents and other information sources. BSP = Business Server Page. A BSP application is – like with a transaction in the classic sense – an application that is functionally self-contained. This application is not executed in the SAPGUI however, but in a Web Browser.
© SAP AG
CR100
12-4
3HRSOH&HQWULF&50² 3URSHUWLHV%HQHILWV %URZVHU7HFKQRORJ\ (no additional installation on client)
5ROHEDVHGaccess to information 6LQJOH6LJQ2Q
,QWXLWLYHDQGHDV\WROHDUQ(same patterns for navigation and layout used on all screens) $GDSWDEOH
SAP AG 2004
User-friendly user interface: y Intuitive and recognizable interaction design y Easy navigation and Web-like behavior Preconfigured user roles: y Preassembled content for complete business tasks y Easy adaptation of the roles for specific needs Knowledge Management (KM): y Users want easy access to the knowledge of the entire enterprise through a single point of access. y Documents should be displayed within their specific context (for example, a CRM transaction). This context should be automatically accessed from the KM search result list. Personalization and configuration: y Users require personalization options to adapt content to their liking. y User interface needs to be flexible and configurable to embrace customer-specific business requirements.
© SAP AG
CR100
12-5
%XVLQHVV3DFNDJHV 3UHGHILQHG3RUWDO&RQWHQW :KDWLVDEXVLQHVVSDFNDJH"
%XVLQHVV3DFNDJHVDUHSUHGHILQHG SRUWDODSSOLFDWLRQVWDUJHWHGWRDVHW RIUHODWHGUROHVRUWRDVSHFLILF DSSOLFDWLRQV\VWHP
%XVLQHVV3DFNDJHVIRU6$3SRUWDOV FRQWDLQSUHFRQILJXUHGFRQWHQWVIRU H[HFXWLRQRIEXVLQHVVWDVNV7KLV HQDEOHVHDFKHPSOR\HHLQ\RXU FRPSDQ\WRKDYHDFFHVVWR UHOHYDQWLQIRUPDWLRQWRPDNH HIIHFWLYHGHFLVLRQVWDNH DSSURSULDWHPHDVXUHVDQGDOVRWR FROODERUDWHZLWKRWKHUV
%3IRU3URMHFWV %3IRU&ROODERUDWLRQ %3IRU6$3&50 %XVLQHVV3DFNDJH IRU3RUWDO8VHUV
SAP AG 2004
The usage of other Business Packages depends on the business scenario. The documentation of the Business Packages can be found in the SAP Developer Network. Business Packages (BP’s) are compressed files containing all roles, worksets, iViews, and so on. Business Packages (BP’s) can be downloaded from the SAP Developer Network and uploaded to the Portal server.
© SAP AG
CR100
12-6
'HOLYHU\RI%XVLQHVV3DFNDJHV %XVLQHVVSDFNDJHVDUHDYDLODEOHYLDWKH6$3'HYHORSHU1HWZRUN XQGHUKWWS VGQVDSFRP &XVWRPHUVFDQEURZVHWKH3RUWDO &RQWHQW3RUWIROLRIRUWKHIROORZLQJ LQIRUPDWLRQ &RQWHQWVRIEXVLQHVVSDFNDJHV
$VVRFLDWHGZRUNVHWV IRUYDULRXV XVHUJURXSV
&XVWRPHUVFDQVHDUFKEDVHGRQ VXFKFULWHULDDV %DFNHQGFRPSRQHQWV 5ROHVDQGWDVNV
,QGXVWU\VHJPHQWV
SAP AG 2004
The Portal Content Portfolio page is the primary delivery mechanism for business packages. It has three primary functions: y Informing customers about available packages, worksets, and iViews and making this content available for download y Supporting the developer community in creating new content and offering it to SAP Portals customers y Delivering updates and patches You can obtain business packages from SAP and from both certified and non-certified partners via the Internet under https://www.sdn.sap.com/irj/sdn/developerareas/contentportfolio. On the website, you can perform searches for business packages and also inform yourself about the details of certain business packages. To download business packages, you need a user ID, which you can also request on this website. This user enables you to access all business packages available. Provided that you possess the licenses required, you can start downloading business packages immediately. 1RWH: Consultants should always use the customer’ s user ID to download business packages from the Portal Content Portfolio. For further information on installation of business packages, see KWWS KHOSVDSFRP! 'RFXPHQWDWLRQ! 6$31HW:HDYHU! 6$31HW:HDYHUV! 6$31HW:HDYHU/LEUDU\! SAP NetWeaver Key Areas -> 3HRSOH,QWHJUDWLRQ! 3RUWDO! $GPLQLVWUDWLRQ*XLGH! &RQWHQW $GPLQLVWUDWLRQ! %XVLQHVV3DFNDJH$GPLQLVWUDWLRQ! %XVLQHVV3DFNDJH/LIHF\FOH
© SAP AG
CR100
12-7
3HRSOH&HQWULF&50² 5ROH&RQFHSWV ,QGLYLGXDOSHUVRQV SHUIRUP YDULRXV MREIXQFWLRQV EXVLQHVVDFWLYLWLHVDQG WDVNV
3HRSOH&HQWULF&50
FRPSULVHVDOOFRQWHQWVUHTXLUHGIRU SHUIRUPLQJDMREIXQFWLRQDVDUROH $UROHFRQVLVWVRIZRUNVHWV IRUHDFKEXVLQHVVDFWLYLW\ (DFKZRUNVHW SURYLGHVSDJHV DQGL9LHZV WRDFFHVVDOO XQGHUO\LQJDSSOLFDWLRQV QHHGHGWRSHUIRUPDWDVN
SAP AG 2004
The UROH is one of the central concepts of the SAP NetWeaver Portal. A role is a collection of tasks, services and information for a group of users. The role defines which service and information the user should be able to access and the activities he or she may perform. User access to content is determined by UROHGHILQLWLRQV. A portal role is a collection of content. The portal content is developed to enable access to information that is relevant for the company that uses the portal. The roles define which content parts are available for each function role in the company. Users are assigned to the role or roles that provide content relevant to them. A user has access to the content that has been assigned to all of his or her roles. The role definition determines the navigation structure within the portal. The navigation structure consists of the top-level navigation bar, and the detailed navigation tree. The top-level navigation bar is a series of tabs in the title area of the portal header. A page can display a detailed navigation tree. The navigation tree presents a hierarchical list of portal pages and services. A user can navigate portal pages and services by clicking on the nodes in the detailed navigation tree. Using the role definition, users can specify whether detailed navigation trees are to be shown. In addition, the role definition is used to configure both navigation at the highest level and also detailed navigation.
© SAP AG
CR100
12-8
3HRSOH&HQWULF&50² 3HUVRQDOL]DWLRQ 3HUVRQDOL]DWLRQPHDQV SURYLGLQJWKHULJKWLQIRUPDWLRQ IRUWKHULJKWSHUVRQDWWKHULJKW WLPH 3HUVRQDOL]DWLRQKDVWRFRYHU DZLGHDUHD
3HUVRQDOL]DWLRQPXVWEHHDV\WR XVH3HUVRQDOL]DWLRQLVD
FHQWUDOSXUSRVHRI3HRSOH &HQWULF&50WRDGMXVWWKH DSSOLFDWLRQWRWKHLQGLYLGXDO UHTXLUHPHQWVRIWKHXVHU
SAP AG 2004
Personalization is a critical success factor for mySAP CRM: y Easy customization and personalization enables the user to have the right information at the right place. y Personalization enables quick navigation to relevant information. y Personalization provides an optimized working environment for users.
© SAP AG
CR100
12-9
3HRSOH&HQWULF&50² 3HUVRQDOL]DWLRQ2SWLRQV 6HOHFWSRUWDOVW\OH
0RGLI\FRQWHQWDQGOD\RXWRISRUWDOSDJHV 3HUVRQDOL]HL9LHZV LQSRUWDO
3HUVRQDOL]H&50DSSOLFDWLRQV
$GGREMHFWVWRRUUHPRYHREMHFWVIURP)DYRULWHV 6DYHVHOIGHILQHGVHDUFKYDULDQWV
SAP AG 2004
0DNLQJ3HUVRQDOL]DWLRQ6HWWLQJV For information about personalization of the portal, have a look in the SAP Library under KHOSVDSFRP. Choose the following path there: 'RFXPHQWDWLRQ!6$31HW:HDYHU!6$3 1HW:HDYHU!3HRSOH,QWHJUDWLRQ!3RUWDO!(QG8VHU*XLGH!3HUVRQDOL]LQJ\RXU3RUWDO For information about personalization of iView, have a look in the SAP Library under KHOSVDSFRP. Choose the following path there: 'RFXPHQWDWLRQ!6$31HW:HDYHU!6$31HW:HDYHU! 3HRSOH,QWHJUDWLRQ!3RUWDO!(QG8VHU*XLGH!8VH&RQWHQW!3HUVRQDOL]HL9LHZ
© SAP AG
CR100
12-10
3HRSOH&HQWULF&50² 3HUVRQDOL]H&50$SSOLFDWLRQV
SAP AG 2004
You can use the 3HUVRQDOL]H link to personalize a results list - for example show/hide fields and influence the sequence of the fields.
© SAP AG
CR100
12-11
3HRSOH&HQWULF &50² )DYRULWHV 2EMHFWV 3UH 3UH DQGVHOI DQGVHOIGHILQHGVHDUFKYDULDQWV
$GG5HPRYHDFWLYHREMHFWWRIURP)DYRULWHV
SAP AG 2004
Objects can be added or removed from the list of my favorite objects. Using the advanced search users can create and store their self defined search variants. These search variants can be selected and executed from the drop-down listbox. Also predefined searches (CRM customizing) are shown in the drop down listbox.
© SAP AG
CR100
12-12
:RUNLQJZLWK3HRSOH&HQWULF&50 );< =?>@<=
A&B+CED FD C1D G/H
I
D C1J
Q =1
KMLON CP+G N H
&HQWUDO6HDUFK
$ ! %#"&
243, 5: 65
*0798
$ ! %#"&
'. (" ) / +*0 ,1- $ ! %#"&
SAP AG 2004
Central search: y Searching for specific data and documents is one of your most important tasks in People-Centric UI. The iView for the central search provides you with a fast and flexible tool in the portal. y You can stipulate which business objects and which attributes are available for each business object in the central search. Various views are available: y List: This is mainly used for searching and displaying various data records. You also have an ([WHQGHGVHDUFK option with this view. y Summarized: This provides the most important information for a selected application in a single view. Note you cannot enter or edit any data on this page however. y Details: Details are contained in a screen area in which you can view and edit all information for an application.
© SAP AG
CR100
12-13
3RUWDO$GPLQLVWUDWLRQ² 2EMHFW$VVLJQPHQWV
[,N U\]
T?UV G R HSG N XYU N1Z HSG+C
KLS^ G
D WD G I D W&D G I
SAP AG 2004
Possible object assignments y Pages can contain pages and iViews y Worksets can contain worksets, pages and iViews y Roles can contain roles, worksets, pages and iViews y Groups can contain users y Roles can be assigned to groups and users y iViews can not contain other content objects
© SAP AG
CR100
12-14
3RUWDO$GPLQLVWUDWLRQ² &RS\LQJ5ROHV 3DVWH DV'HOWD/LQN WRVSHFLILFDUHD
&RS\IURPVWDQGDUG SRUWDOFRQWHQW
SAP AG 2004
&RS\LQJD5ROH 8VH: You can copy an existing role and then edit the copied version. 3URFHGXUH y Select a role in the role catalog (%URZVHU structure). y Right-click the role and choose &RS\. y Navigate to the customer specific area within portal content directory. - Use right-click and e.g. choose 3DVWH if you want an independent object. - Use right-click and e.g. choose 3DVWHDV'HOWD/LQN if you would like inheritance take place (Parent-Child relationship). y Open your role and change properties accordingly.
© SAP AG
CR100
12-15
3RUWDO$GPLQLVWUDWLRQ² &KDQJLQJ5ROHV 2SHQWKHUROH
0RGLI\UROHFRQWHQWDFFRUGLQJWRUHTXLUHPHQWVIRUH[DPSOH - $GGDVVLJQUHPRYHZRUNVHWV - $GGDVVLJQUHPRYH L9LHZV
SAP AG 2004
&KDQJLQJ([LVWLQJ5ROHV 3URFHGXUH y Select a role in the Portal Content (either %URZVH or 6HDUFK tab) area and right-click on the object. Choose 2SHQ to edit the role. y You can edit the object by adding new entries or removing existing ones and by changing properties. y If possible, save your role. When you remove a Workset from a role (Delete), changes are effective immediately. No save necessary. 0RGLI\LQJ3RUWDO5ROHV'HOLYHUHGE\6$3 You should QHYHU modify roles delivered by SAP (such as the role for the portal administrator and the Knowledge Management administrator). If you want to adjust or change an object that does not belong to your namespace, DOZD\VXVHWKH GHOWDOLQNSURFHGXUH. Also read Delta Links and Upgrade of Business Packages.
© SAP AG
CR100
12-16
3RUWDO$GPLQLVWUDWLRQ² $VVLJQLQJ8VHUVWRD5ROH
User Management System (LDAP Directory)
Portal
$VVLJQLQJD*URXSWRD5ROH
*URXS
8VHU 8VHU
5ROH 5ROH
8VHU *URXS
5ROH
8VHU 8VHU
SAP AG 2004
E.g. Lightweight Directory Access Protocol (LDAP) is supported. The SAP NetWeaver Portal is an easy-to-use tool for assigning roles to users and groups or, conversely, for assigning users or groups to roles. Procedure for Assigning Roles y Search for the user in 8VHU$GPLQLVWUDWLRQ!5ROHV y Edit the user. y Search for available roles and assign them to the user. y Save the user. Every user will be assigned to group (YHU\RQH and the role HXBUROH.
© SAP AG
CR100
12-17
&XVWRPL]LQJ RI9LHZV 6HOHFWL9LHZV
$GDSW4XHU\6WULQJLQFOXGLQJDYLHZ
(GLWL9LHZ SURSHUWLHV
appl=CRMM_ACCOUNT EOYLHZ 6$/(6&...
SAP AG 2004
CRM uses an approach where only one BSP application exists (CRM_BSP_FRAME). All the various applications like Account Management, Opportunity Management and so on are managed internally by a URL parameter known as $33/. The personalization is realized by the BLVIEW parameter.
© SAP AG
CR100
12-18
'LIIHUHQW5ROHV0DSWRWKH'LIIHUHQW9LHZV
$FWLYLW\0DQDJHPHQW
6DOHV 9LHZ
:LWKWKHKHOSRIWKH&50YLHZFRQFHSWFXVWRPHUVFDQ FUHDWHVSHFLDOOD\RXWGHULYDWLYHV2QHRUPRUHYLHZVFDQEH XVHGLQHDFKUROH7KLVHQVXUHVWKHJUHDWHVWSRVVLEOH IOH[LELOLW\,QWKLVH[DPSOHWZRYLHZVKDYHEHHQFUHDWHGIRU DFWLYLW\PDQDJHPHQWVLQFHERWKVDOHVDQGVHUYLFH GHSDUWPHQWKDYHPDLQWDLQDFWLYLWLHVEXWXVHGLIIHUHQW OD\RXW
$FWLYLW\0DQDJHPHQW
6HUYLFH 9LHZ
SAP AG 2004
To create a view, choose the following path: 6$3,PSOHPHQWDWLRQ*XLGH! &XVWRPHU5HODWLRQVKLS 0DQDJHPHQW! /D\RXWRI8VHU,QWHUIDFH 3HRSOH&HQWULF8, ! $SSOLFDWLRQ/D\RXW! 9LHZ The iView property $GGLWLRQDO4XHU\6WULQJ 2SWLRQDO3URSHUW\ allows you to address a view; use parameter EOYLHZ YLHZ!
© SAP AG
CR100
12-19
0RGLILFDWLRQVLQWKH&506\VWHP $VVLJQDVXLWDEOHLQGLYLGXDOUROHWRWKHSRUWDOUROHLQWKH&50V\VWHP
0RGLI\QDYLJDWLRQ 85/JHQHUDWLRQ IRU\RXUUROH
0RGLI\WKHOD\RXWRI\RXU3&8,DSSOLFDWLRQV
SAP AG 2004
Transaction CRMC_BLUEPRINT_C leads you directly to the /D\RXWRIWKH8VHU,QWHUIDFH 3HRSOH &HQWULF8, The &XVWRPL]LQJWRROreplaces the Business Application Builder and the CRM Designer. This is started via an (ABAP) transaction and is QRW a graphical drag and drop tool. You can use the Customizing tool to modify field groups, group tab pages and group toolbars. The Customizing tool displays both static and dynamic elements, provides a preview and contains a consistency check.
© SAP AG
CR100
12-20
3HRSOH&HQWULF&50 8QLW6XPPDU\
1DPHVRPHEDVLFSURSHUWLHVRI3HRSOH&HQWULF&50
8QGHUVWDQGWKHUROHFRQFHSW
([SODLQSHUVRQDOL]DWLRQRSWLRQVLQ3&8,
0DNHVLPSOHFKDQJHVWRSRUWDOFRQWHQW
SAP AG 2004
© SAP AG
CR100
12-21
© SAP AG
CR100
12-22
([HUFLVHV 8QLW 3HRSOH&HQWULF&50
7RSLF )DPLOLDUL]LQJ\RXUVHOIZLWKWKH3HRSOH&HQWULF8, DQGWKH$FFRXQWVDSSOLFDWLRQ
R-
At the conclusion of these exercises, you will be able to: • Create search queries and understand their meaning • Personalize a results list • Explain the difference between the List and Form views. People-Centric User Interface users need to get a better understanding of the PC UI application. As a first step it is necessary to understand simple personalization features when creating result lists.
1-1
Familiarize yourself with the People-Centric UI and its applications. Using the example of the $FFRXQWV application, you familiarize yourself with the personalization options. 1-1-1 Log on to the portal.
/LQNXVHUDQGSDVVZRUGDUHSURYLGHGE\\RXUWUDLQHU
1-1-2 Select the application $FFRXQW0DQDJHPHQW→$FcountV→ $FFRXQWV. Select Extended Search. This is only available in the List view. If necessary, switch to this view.
Search for accounts with the postal code .
Save your query under &5 Describe exactly what is saved
________________________________________________________ 1-1-3 Personalize the search result list. Choose the Personalization link, select and deselect fields and change the order of appearance. 1-1-4 Only display accounts for the city of Seattle. 1-1-5 Sort your search result list by house numbers. 1-1-6 Export the results list to a file.
© SAP AG
CR100
12-23
© SAP AG
CR100
12-24
([HUFLVHV 8QLW 3HRSOH&HQWULF&50
7RSLF &506SHFLILF&RQWHQWLQ(3 RAt the conclusion of these exercises, you will be able to: • Reproduce portal personalization options • Explain the basic content of a standard portal role You would like to become familiar with user and content information within the Enterprise Portal. You also need to gain a better understanding of standard portal content such as roles, worksets, pages and iViews.
2-1
Analyze an existing portal user as well as an existing portal role. In the following you will become familiar with user management (Identity Management) for the SAP NetWeaver portal. 2-1-1 Take a look at portal personalization. Which options do you have to personalize the user specific portal environment?
2-1-2 In 8VHU$GPLQLVWUDWLRQsearch for user 0LNH%XUWRQ and display the details. a) Which user ID is assigned to Mike Burton? b) To which roles is this user assigned? c) Which other actions can you execute from the user search result list?
2-1-3 Take a look at the icon legend within &RQWHQW$GPLQLVWUDWLRQ→3RUWDO &RQWHQWYou will see some of those icons again in the further course of this exercise. 2-1-4 In &RQWHQW$GPLQLVWUDWLRQ,search for the 6HUYLFH0DQDJHUrole, open it and find out more about the content of this role. a) Where is this role located in the portal catalog? b) Which worksets are assigned to the role? How many of them are marked as entry points? Use the legend as a reference.
c) What are the contents of the 2SSRUWXQLW\0DQDJHPHQW workset in the 6HUYLFH&\FOHworkset?
d) Call up the &XVWRPHUV page in the Service Performance Analysis workset of the $QDO\WLFV workset. How many iViews does this page comprise? d) How do you find out which BW query is called from each of these iViews?
© SAP AG
CR100
12-25
© SAP AG
CR100
12-26
([HUFLVHV 8QLW 3HRSOH&HQWULF&50
7RSLF &RS\LQJDQG&KDQJLQJD5ROH RAt the conclusion of these exercises, you will be able to: • Copy a standard PCUI role and modify it. • Make necessary settings in the SAP CRM system. You would like to become familiar with user and content information within the Enterprise Portal. You also need to gain a better understanding of standard portal content such as roles, worksets, pages and iViews.
3-1
Copying a portal role and changing it according to your needs. In the steps that follow you will copy an existing portal role and then modify it. In addition, you will generate a suitable user role in the CRM system corresponding to the portal role responsible for portal navigation for example.
3-1-1 Create a subfolder *5283 in the folder CRM Training
3-1-2 Copy the 6HUYLFH0DQDJHU role from the corresponding folder in the newlycreated ##Group folder. Right-click to use the copy & paste function.
Change the 'HVFULSWLRQ,' and 1DPH of the role to 6HUYLFH0DQDJHU. What is the complete ID for this role? You can find this information further down under4XLFN,QIR.
3-1-3 Delete the $QDO\WLFV workset. Answer the dialog with
3-1-4 Go to 8VHU$GPLQLVWUDWLRQ and assign the newly-created role to the user CRM-##. Refresh the display (F5). What do you notice?
Go to $FFRXQWVDQG3URGXFWV→$FFRXQW0DQDJHPHQW →$FFRXQWVand call the Account Media Store (3271). Can your see any hyperlinks on the 2SSRUWXQLWLHV tab?
© SAP AG
CR100
12-27
2SWLRQDO([HUFLVHV 3-1-5 Generate a new user role in the CRM system.
Create a new user role =B3&&B6(59,&(B0$1$*(5in the SAP CRM system using the existing role SAP_PCC_SERVICE_MANAGER as a template.
3-1-6 Assign the newly-created role to the user CRM-##. 3-1-7 Assign your newly-created portal role to the individual role you have just created. Carry out this setting in CRM Customizing. 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo /D\RXWRI8VHU,QWHUIDFH 3HRSOH&HQWULF8, o1DYLJDWLRQ 85/ *HQHUDWLRQ o$VVLJQ3RUWDO5ROHWR6LQJOH5ROH 3-1-8 Use the role copier to generate object links. /D\RXWRI8VHU,QWHUIDFH 3HRSOH&HQWULF8, o1DYLJDWLRQ 85/ *HQHUDWLRQ o8VH5ROH&RSLHUIRU2EMHFW/LQNV
6$3B3&&B6(59,&(B0$1$*(5
Individual role (source): Confirm the entry with ENTER. Individual role (destination):
=B3&&B6(59,&(B0$1$*(5
Confirm your entry with ENTER. Destination role priority:
10
Execute the activity in test mode to start with and then GHVHOHFW the 7HVW 0RGHFKHFNER[. 3-1-9 Log on to the portal again and check whether the hyperlinks are now visible.
© SAP AG
CR100
12-28
6ROXWLRQV R-
8QLW 3HRSOH&HQWULF&50
7RSLF )DPLOLDUL]LQJ
1-1
Familiarize yourself with the People-Centric UI and its applications. Using the example of the $FFRXQWV application, you familiarize yourself with the personalization options. 1-1-1 Log on to the portal.
/LQNXVHUDQGSDVVZRUGDUHSURYLGHGE\\RXUWUDLQHU
1-1-2 To save the search strategy, choose 6HDUFKTXHU\«
Only the search attributes are saved, not the search result list. If you select your predefined search the next time, the system starts the search again with exactly the same search attributes, though the result list might be different.
1-1-3 Click on the 3HUVRQDOL]H link in the upper right area of your result list. 1-1-4 Click the Filter On button and enter Seattle in the Cityrow. 1-1-5 Perform a single or double click on the House Number field. 1-1-6 Choose the Export pushbutton.
© SAP AG
CR100
12-29
© SAP AG
CR100
12-30
6ROXWLRQV R-
8QLW 3HRSOH&HQWULF&50
7RSLF &506SHFLILF&RQWHQWLQ(3
2-1
Analyze an existing portal user as well as an existing portal role. In the following you will become familiar with user management (Identity Management) for the SAP NetWeaver portal.
2-1-1 Click on the 3HUVRQDOL]H link in the upper right corner of the browser window.
Users can personalize the portal theme for example (influences the fonts and colors of portal pages) or portal language. Users can also change their user profile and password. In addition, users can configure WorkProtect mode which allows them to set the handling of unsaved data during navigation. 2-1-2 Choose User Administration→ Identity Management
Under the ([WHQGHGVHDUFK for XVHUV, enter the surname %XUWRQ and press (17(5.
a) Mike Burton’ s user ID is 6(59,&(5(3.
b) Choose the $VVLJQHG5ROHV tab Select 5HFXUVLYHVHDUFK and choose 6WDUW. You can see that the user is assigned to the roles [Description] (YHU\RQHUROH, &508VHU, &56HUYLFH 5ROH and 3HUVRQDOL]DWLRQ. c) You can, for example, modify or lock the user. …
© SAP AG
CR100
12-31
… 2-1-3 The following icon legend can be observed:
© SAP AG
Folder
iView (Hidden)
iView Target)
Folder (Added to Delta Link
iViewTemplate Target)
Folder (Changed in Delta Link
Page Target)
iView (Added to Delta Link
Page Template Target)
iView (Changed to Delta Link
Workset T)
Portal Page (Added to Delta Link
Role Link T)
Portal Page (Changed to Delta
Page Layout Target)
Workset (Added to Delta Link
Unclarified Link T)
Workset (Changed to Delta Link
Business Object
Business Object (Existing)
iView (Locked in Page)
Business Object Operation
CR100
12-32
2-1-4 Click&RQWHQW$GPLQLVWUDWLRQ→3RUWDO&RQWHQW and go to the Search tab. Enter the following: Search In: Object Type: Search For:
Press 6HDUFK.
(QWLUH3RUWDO&DWDORJ
5ROH
6HUYLFH0DQDJHU
Select the ILUVWHQWU\ in the results list. In the Quick Info, you will see the identity for this role. This ends in FUPVFVHUYLFHPDQDJHU
a) Perform a right-click and select 6HDUFKLQ3RUWDO&DWDORJ. The directory structure of the portal catalog will open up and you will see the relevant location.
Right-click to open this role and choose 2SHQÆ2EMHFW.
b) In the details area on the right hand side, you will see that the following worksets are assigned to the role:
+RPH6HUYLFH&\FOH,QVWDOODWLRQV6HUYLFH3HUIRUPDQFH$FFRXQWVDQG 3URGXFWV$QDO\WLFVand0DUNHW Six of the seven worksets are marked as entry points, meaning that they show up in first level navigation. It is not necessary to check the properties of the worksets. The font (bold) provides you with you the information.
c) The workset 2SSRUWXQLW\0DQDJHPHQW contains three pages 2YHUYLHZ2SSRUWXQLWLHV 6XPPDU\ and $QDO\VLV plus 2SSRUWXQLWLHV iViews.
c) Right-click the &XVWRPHUV page and choose (GLW. The page contains two iViews.
e) Select one of these iViews and choose the 3URSHUWLHVpushbutton.
In the 3URSHUW\(GLWRUon the right-hand side. choose the 3URSHUW\&DWHJRU\ &RQWHQW±%([:HE$SSOLFDWLRQ. Here you will find information on the BW Report ID.
© SAP AG
CR100
12-33
© SAP AG
CR100
12-34
6ROXWLRQV R-
8QLW 3HRSOH&HQWULF&50
7RSLF &RS\LQJDQG&KDQJLQJDUROH
3-1
Copying a portal role and changing it according to your needs. In the steps that follow you will copy an existing portal role and then modify it. In addition, you will generate a suitable user role in the CRM system corresponding to the portal role responsible for portal navigation for example. 3-1-1 Link, user and password are provided by your trainer.
Navigate to &RQWHQW$GPLQLVWUDWLRQ→3RUWDO&RQWHQW
Use the %URZVH structure on the left to navigate to 3RUWDO&RQWHQW→&50 7UDLQLQJ Right-click to create a subfolder *URXS.
3-1-2 Stay within the %URZVH structure and navigate to:
3RUWDO&RQWHQW→&RQWHQW3URYLGHGE\6$3→VSHFLDOLVW→&50→5ROHV Search for the 6HUYLFH0DQDJHU role.
Right-click to select the role and choose &RS\.
Navigate to the newly-created folder within &507UDLQLQJ and right-click to 3DVWHDVGHOWDOLQN.
Answer the dialog with
Once you have inserted the role into your folder, first change the ID by right-clicking to select the object and choose &KDQJH,'. Follow the instructions in the dialog and assign VHUYLFHPDQDJHUas the new object ID.
Now open the object and change the GHVFULSWLRQand QDPH of this role to VHUYLFHPDQDJHU The complete ID for the new role is:
SFG SRUWDOBFRQWHQWFRPVDSWUDLQLQJ&507UDLQLQJ*UXSSHFRPVDS SFWFUPVHUYLFHPDQDJHU Save your settings.
© SAP AG
CR100
12-35
3-1-3 Right-click on the Analytics workset and choose 'HOHWH. Answer the dialog with
Choose &KDQJH and go to the $VVLJQHG5ROHV tab.
Search for your newly-created role using the search string *##service*.
Select your role and choose $GG.
Press the 6DYH button in order to save the user. Press F5 or use the browser refresh icon.
7KHWRSOHYHOQDYLJDWLRQVKRXOGQRZLQFOXGHVHYHUDOQHZHQWU\SRLQWV WKDWRULJLQDWHIURPWKHVHUYLFHUHSUHVHQWDWLYHUROH.
Go to $FFRXQWVDQG3URGXFWV→$FFRXQW0DQDJHPHQW→$FFRXQWVand call the Account Media Store (3271). Choose the 2SSRUWXQLWLHVtab
+\SHUOLQNVDUHQRWDYDLODEOH/RJRIIDQGFORVHWKHEURZVHU
© SAP AG
CR100
12-36
2SWLRQDO([HUFLVHV 3-1-5 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o6\VWHP$GPLQLVWUDWLRQo 8VHU0DLQWHQDQFHo5ROH$GPLQVWUDWLRQo5ROHV Role:
6$3B3&&B6(59,&(B0$1$*(5
To role:
=B3&&B6(59,&(B0$1$*(5
Choose &RS\5ROH.
Choose &RS\$OO.
3-1-6 6$3PHQXo$UFKLWHFWXUHDQG7HFKQRORJ\o6\VWHP$GPLQLVWUDWLRQo 8VHU0DLQWHQDQFHo8VHUV User:
CRM-##
Choose &KDQJH.
Choose the 5ROHV tab.
=B3&&B6(59,&(B0$1$*(5
Role: Save the user.
3-1-7 6$3PHQXo&RQILJXUDWLRQo&XVWRPL]LQJ Choose 6$35HIHUHQFH,0*.
6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo /D\RXWRI8VHU,QWHUIDFH 3HRSOH&HQWULF8, o1DYLJDWLRQ 85/ *HQHUDWLRQ o$VVLJQ3RUWDO5ROHWR6LQJOH5ROH
Select 1HZ(QWULHV. Role:
=B3&&B6(59,&(B0$1$*(5
Portal role: FRPVDSWUDLQLQJ&507UDLQLQJ*UXSSHFRPVDSSFWFUPVHUYLFHPD QDJHU Save this data. 3-1-8 6$3,PSOHPHQWDWLRQ*XLGHo&XVWRPHU5HODWLRQVKLS0DQDJHPHQWo Layout of User Interface (People-Centric UI) → Navigation (URL Generation) → Use Role Copier for Object Links Individual role (source): 6$3B3&&B6(59,&(B0$1$*(5 Confirm the entry with ENTER. Individual role (destination):
=B3&&B6(59,&(B0$1$*(5
Confirm the entry with ENTER. Destination role priority:
10
Execute the activity in test mode to start with and then GHVHOHFW the 7HVW 0RGHFKHFNER[. 3-1-9 The hyperlinks will now be displayed.
© SAP AG
CR100
12-37
© SAP AG
CR100
12-38
$SSHQGL[ &RXUVH2XWOLQH
8QLW
P\6$3 &50± $Q2YHUYLHZ
7UDQVDFWLRQ 3URFHVVLQJ
2UJDQL]DWLRQDO0DQDJHPHQW
3DUWQHU3URFHVVLQJ
%XVLQHVV3DUWQHUV
3URGXFW0DVWHU
$FWLYLW\ 0DQDJHPHQW
$FWLRQV
3ULFLQJ)XQGDPHQWDOV
&50%LOOLQJ
&500LGGOHZDUH
3HRSOH&HQWULF&50 $SSHQGL[
SAP AG 2004
© SAP AG
CR100
Appendix-1
$SSHQGL[ %DVLF)XQFWLRQVDQG8QGHUO\LQJ &XVWRPL]LQJ &50 0LGGOHZDUH
SAP AG 2004
© SAP AG
CR100
Appendix-2
$GGUHVV'HWHUPLQDWLRQ %3$GGUHVVHV Address 1 BP
Address 2
$GGUHVV7\SHV Correspondence address Delivery address
Address 3 $SSOLFDWLRQ
7UDQVDFWLRQ Send letter Send reminder
Application program
Deliver goods
&XVWRPL]LQJ
&RQWURO
SAP AG 2004
Through Customizing, you can ensure that the different addresses of a business partner are determined correctly by the system for the different partner functions in a business process (for example, send invoice to bill-to address). In the Business Partner master, you enter the different addresses of the business partner. One address is marked as the standard address. You can assign the addresses to different address types (address usages), which you predefined in the Customizing. Several addresses can be assigned to the same address type, but only one is marked as the standard address.
© SAP AG
CR100
Appendix-3
&XVWRPL]LQJIRU$GGUHVV'HWHUPLQDWLRQ 6$3%XVLQHVV3DUWQHU² $GGUHVV'HWHUPLQDWLRQ 'HILQH7UDQVDFWLRQV
'HILQH$GGUHVV7\SHV
$VVLJQ7UDQVDFWLRQWR$GGUHVV7\SH
&50² 3DUWQHU'HWHUPLQDWLRQ3URFHGXUH
(QWHU$GGUHVV7UDQVDFWLRQIRU3DUWQHU)XQFWLRQLQ3URFHGXUH
SAP AG 2004
SAP Reference IMG: &URVVDSSOLFDWLRQFRPSRQHQWV→ 6$3%XVLQHVV3DUWQHUV→%XVLQHVV3DUWQHUV→%DVLF6HWWLQJV→ $GGUHVV'HWHUPLQDWLRQand so on. &XVWRPHU5HODWLRQVKLS0DQDJHPHQW→%DVLF)XQFWLRQV→3DUWQHU3URFHVVLQJ→'HILQH3DUWQHU 'HWHUPLQDWLRQ3URFHGXUH
© SAP AG
CR100
Appendix-4
0DLQWHQDQFHRI,QWHUQDWLRQDO$GGUHVV9HUVLRQV (QKDQFHPHQWRIH[LVWLQJIXQFWLRQV
0DLQWHQDQFHRILQWHUQDWLRQDODGGUHVVYHUVLRQVIRU
!
2UJDQL]DWLRQV
!
3HUVRQV
! !
*URXSV
&RQWDFWSHUVRQV
'HILQLWLRQRILQWHUQDWLRQDODGGUHVVYHUVLRQVLQWKH&XVWRPL]LQJ $GGLWLRQDOPDLQWHQDQFHIRUQDPHDQGQDPHGHSHQGHQW DWWULEXWHV
0DLQWHQDQFHRILQWHUQDWLRQDODGGUHVVYHUVLRQVVWDUWHGIURPWKH GHWDLOHGDGGUHVVYLHZ 3ULQWSUHYLHZIRULQWHUQDWLRQDODGGUHVVYHUVLRQV
SAP AG 2004
The worldwide use of SAP software requires the use of many different fonts. International address versions (or versions for short) are an attribute of Business Address Services that enable addresses to be printed in different fonts depending on the country. In this context, the term GLIIHUHQWIRQWV does not refer to special country-specific letters or symbols within a character set, such as vowels with umlauts in German and vowels with accents in French, but rather fonts that consist of their own character sets. When printing addresses, note that the font of the addresses to be printed is not determined by the current logon language or the logon language at the time of address creation. International address versions enable the same address to be printed in different fonts (or versions), depending on certain parameters. A Japanese address is to be printed in Kanji (Chinese characters) if the sending company is also in Japan, or in international font if the sending company is not in Japan. See also SAP Note 316331 about international address versions.
© SAP AG
CR100
Appendix-5
(QVXULQJ'DWD&RUUHFWQHVVDQG&RQVLVWHQF\ &KHFN'XSOLFDWH
6WDQGDUGL]HGLQWHUIDFHIRULQWHJUDWLRQRIUGSDUW\RUFXVWRPHU VSHFLILFWRROV
3RVWDOYDOLGDWLRQIRUDGGUHVVHV
&KHFNDJDLQVW55HJLRQDO6WUXFWXUH
6WDQGDUGL]HGLQWHUIDFHIRULQWHJUDWLRQRIUGSDUW\RUFXVWRPHU VSHFLILFWRROV
&KHFNRQEDQNGHWDLOV
$UFKLYLQJ
3UHGHILQHGYDOXHVDQGRUFKHFNWDEOHV IRUFHUWDLQILHOGV
SAP AG 2004
In Business Address Services, interfaces for partner products are provided for the attachment of tools for duplicate check and error tolerant searches. The prerequisite for the duplicate check is that a solution of a third-party provider is used and the implementations for the Business-Add-Ins ADDRESS_UPDATE and ADDRESS_SEARCH are active (transaction SE19). You can customize postal validation. You can maintain a separate post-customizing for each country. The archiving flag (BUT000-XDELE) is set manually or via a BAPI. Data dependency test: The business partner cannot be archived when the following statements are true: y The business partner is a reference business partner. y The business partner is being used in a business transaction (for example, in an activity, opportunity, sales order, lead). Business transactions must first be archived. y The business partner is an active organizational unit. y Relationships to a product exist (for example, customer order number): Partner/product ranges must first be archived. y An Internet user exists.
© SAP AG
CR100
Appendix-6
%XVLQHVV3DUWQHU'DWD &OHDQVLQJ ,Q'DWD&OHDQVLQJWKHIROORZLQJKDSSHQV
,GHQWLILHGGXSOLFDWHVFDQEHEURXJKWWRJHWKHUZLWKWKHGHSHQGHQW GDWDDQGREMHFWV $OOGHSHQGHQWGDWDDQGREMHFWVFDQEHSUHVHQWHGJUDSKLFDOO\LQD WUHHVWUXFWXUH
$IWHUGDWDFOHDQVLQJWKHGXSOLFDWHFDQEHDUFKLYHGDXWRPDWLFDOO\
%HQHILWV
5HGXFHGGDWDUHGXQGDQF\
,PSURYHGTXDOLW\RIGDWD
SAP AG 2004
,QWHJUDWLRQ: Before GDWDFOHDQVLQJ can be carried out, the redundant data must be determined in the system. The following possibilities for duplicate recognition exist: y External search engine – The Business Address Services (BAS) provide an interface for integrating any necessary external software such as a search engine. y Customer-owned programs y Services from data providers to search your data for possible duplicates In individual cases you can find potential business partner duplicates in the hit list of the business partner search. 3UHUHTXLVLWHV Redundant data records must have been determined in the system. To use the Business Address Services interface, make the following settings in Customizing: In the IMG, choose %DVLV→%DVLV6HUYLFHV→$GGUHVV0DQDJHPHQW→$FWLYDWH'XSOLFDWH&KHFN,QGH[ 3RROV Perform the following system settings in the SAP Business Partner IMG: Choose &URVV$SSOLFDWLRQ &RPSRQHQWV→6$3%XVLQHVV3DUWQHU→'DWD&OHDQVLQJ→0DLQWDLQ1XPEHU5DQJHV'HILQH 3ULRULWLHV$FWLYDWH'DWD&OHDQVLQJ
© SAP AG
CR100
Appendix-7
%XVLQHVV3DUWQHU$UFKLYLQJ 3URFHGXUH
3KDVH
3KDVH
3KDVH
"
"
"
" "
6HOHFWLRQ &KHFNLQJ 6HWWLQJRIV\VWHP VWDWXVWR$5&5
:ULWLQJRIGDWD WRWKHDUFKLYH (all data records with status $5&5
"
&KHFNLQJ RI DUFKLYHG GDWD 'HOHWH IURP GDWDEDVH
SAP AG 2004
The archiving flag (BUT000-XDELE) is set manually or via a BAPI. Data dependency test: The business partner cannot be archived when the following statements are true: y The business partner is a reference business partner. y The business partner is being used in a business transaction (for example, in an activity, opportunity, sales order, lead). Business transactions must first be archived. y The business partner is an active organizational unit. y Relationships to a product exist (for example, customer order number): Partner/product ranges must first be archived. y An Internet user exists. Phases 2 and 3 of the archiving process must be initiated directly in the Archive Development Kit (ADK). The phase 1 tasks can be completed by periodic collective processing. Status ARCR stands for archivable.
© SAP AG
CR100
Appendix-8
6HDUFKIRU$UFKLYHG'RFXPHQWVLQ3HRSOH&HQWULF8, ,QWKH3HRSOH&HQWULFXVHULQWHUIDFH\RXFDQVHDUFKIRU DUFKLYHGGRFXPHQWVDQGGLVSOD\WKHP
SAP AG 2004
© SAP AG
CR100
Appendix-9
'DWH0DQDJHPHQW 'DWH0DQDJHPHQWHQDEOHV\RXWRSURFHVVDVPDQ\ GDWHVDV\RXUHTXLUHLQDGRFXPHQW ([DPSOHVRI'DWH7\SHVLQ%XVLQHVV7UDQVDFWLRQV 'DWHW\SH
'DWHUXOH
$FWLYLW\
3ODQQHGGDWH $FWXDOGDWH
&XUUHQWGDWH
6DOHV FRQWUDFW
&RQWUDFWVWDUW 9DOLGLW\SHULRG &RQWUDFWHQG &DOOFXVWRPHU
&XUUHQWGDWH \HDU &RQWUDFWVWDUW YDOLGLW\SHULRG &RQWUDFWHQG± ZHHNV
SAP AG 2004
Date management enables you to process as many dates as you wish in a transaction. It is used, for example, in contracts (for cancellations date, run times), activities (total duration of an activity), and quotations (valid to date). You can use date management in any other transaction types. You define specific dates, or the system can calculate dates using date types, durations and date rules. The date profile controls which reference objects, time duration, date types, and date rules can be used in a specific transaction type.
© SAP AG
CR100
Appendix-10
'DWHVLQ%XVLQHVV7UDQVDFWLRQV² 6$3*8,
'DWHW\SH
'DWHUXOH
SAP AG 2004
© SAP AG
CR100
Appendix-11
'DWH3URILOH
3URFHVV7\SH
,WHP&DWHJRU\
'DWH3URILOH :KLFKGDWHW\SHVFDQ,XVH"
:KLFKGXUDWLRQVDUHLQFOXGHG"
:KDWDWWULEXWHVKDYHEHHQJLYHQWRWKHGDWHV DQGGXUDWLRQV" +RZDUHWKHGDWHVGHWHUPLQHG GDWHUXOHV "
:KHUHGRWKHGDWHVDQGGXUDWLRQVDSSHDULQ WKHGRFXPHQW"
SAP AG 2004
Date types are descriptions of business transaction dates, for example, start of contract, end of contract, date of signature. The duration is the period between two points in time. It consists of a numerical value and definable time unit. Date rules for calculating times are defined in XML.
© SAP AG
CR100
Appendix-12
&RQWHQW0DQDJHPHQW
7KHIROORZLQJIXQFWLRQVDUHDYDLODEOHLQ&RQWHQW 0DQDJHPHQW &UHDWLQJFKDQJLQJFRS\LQJDQGGHOHWLQJGRFXPHQWV
6WRULQJGRFXPHQWVLQIROGHUV IROGHUVWUXFWXUH
,PSRUWLQJGRFXPHQWVIURPDQGH[SRUWLQJGRFXPHQWVWRDORFDO3&
([SRUWLQJGRFXPHQWVWR\RXU3&
5HIHUHQFLQJGRFXPHQWVWKDWDUHOLQNHGWRRWKHUWUDQVDFWLRQV
,QFOXGLQJ85/VLQWKHVWUXFWXUH
6HDUFKLQJGRFXPHQWV
6HQGLQJGRFXPHQWV
0DQDJLQJYHUVLRQV
3UHYLHZLQJGRFXPHQWV
SAP AG 2004
Content Management is a function of the SAP Web Application Server, which is used in SAP CRM in various areas, for example, for business partner- and product master data.
In the business transaction, the various Content Management functions are available on header- and item level.
Integration with the ArchiveLink functionality: In Customizing, you can define which documentation for the appropriate business objects is linked to the ArchiveLink functions. To do this, in Customizing, select the :HE$SSOLFDWLRQ6HUYHU! 6$3:HE$SSOLFDWLRQ6HUYHU! %DVLV 6HUYLFHV! $UFKLYH/LQN Additionally, you can create ArchiveLink documents from Content Management.
The exchange of Content Management documents with CRM Mobile is possible. Usage of filter profiles allows you to specify which documents are to be transferred to the Mobile Client.
For technical information on Content Management, see the SAP Help portal under http://help.sap.com -> SAP NetWeaver -> SAP Web Application Server -> SAP NetWeaver Components -> SAP Web Application Server -> Basis Services / Communication Interfaces (BCSRV) -> Knowledge Provider (BC-SRV-KPR) -> Content Management Service (BC-SRV-KPR).
Please see OSS note 720434 for information on $XWKRUL]DWLRQVIRUGRFXPHQWV.
© SAP AG
CR100
Appendix-13
&RQWHQW0DQDJHPHQW² 6$3*8,
)ROGHUVWUXFWXUH
3UHYLHZSURSHUWLHVRUYHUVLRQV
SAP AG 2004
Functions for Content Management are on the 'RFXPHQWV tab page.
Special functions in SAP GUI: y Sending documents: You can send business partners documents linked to a business transaction, for example, by e-mail or fax. y Creation of personal- and generally visible notes at document level. y Document templates: You can define templates for your documents that will be available to you later in Content Management. For more information, see the Implementation Guide under &XVWRPHU5HODWLRQVKLS0DQDJHPHQW→%DVLF)XQFWLRQV→&RQWHQW0DQDJHPHQW→'HILQH 'RFXPHQW7HPSODWHV.
© SAP AG
CR100
Appendix-14
&RQWHQW0DQDJHPHQW² 3HRSOH&HQWULF8VHU,QWHUIDFH
SAP AG 2004
Functions for Content Management are on the $WWDFKPHQWV tab page.
© SAP AG
CR100
Appendix-15
6\VWHP/DQGVFDSH 'DWD&RQWDLQHUV8VHG
0RELOH&OLHQWV
;0/)LOHV ,'RFV62$3 RU$6&,,)LOHV
2WKHU V\VWHPV 'DWD([WUDFWV ([FHO:RUNERRNV
%'RF 0HVVDJHV &50 0LGGOHZDUH &RPPXQLFDWLRQ 6WDWLRQ
%:
&506HUYHU 'LUHFW$FFHVV YLD%$3,V
6$35V\VWHP
SAP AG 2004
%'RFPHVVDJHVserve as data containers on the CRM Server and between the CRM Server and the Mobile Clients. Data from SAP R/3 systems and other systems are received via BAPIs, XML files, Idocs or ASCII files. This data is mapped to fill BDocs for further distribution. Several layers can be distinguished to technically enable the data transfer between the systems involved: y The TCP/IP transfer protocol is usually used on the network. y Remote Function Calls (RFCs) or the File Transfer Protocol (ftp) provide data. y BDocs, IDocs, XML messages or ASCII flat files contain the actual data.
© SAP AG
CR100
Appendix-16
6LWH7\SH&RQFHSW ,GHD
(YHU\UHFHLYHULVUHSUHVHQWHGE\DQDEVWUDFWVLWH
YDULRXV VLWHW\SHV
5HSOLFDWLRQDGPLQLVWUDWLRQ 6LWH$
6LWH%
6LWH&
6LWH'
0RELOH&OLHQW
6$35 6\VWHP
&50&'%
1RQ6$3 6\VWHP
5HVXOW
'DWDUHSOLFDWLRQWRGLIIHUHQWV\VWHPVFDQEHDGPLQLVWHUHGLQD XQLIRUPZD\
SAP AG 2004
In an SAP CRM system environment, local components or VLWHV must be connected to the central component permanently or temporarily so that messages can be exchanged. Sites (not users) are the smallest addressable unit in Replication and Realignment. They are identified by a global identifier (GUID). Each site has a VLWH type. Sites of the same type use the VDPHDGDSWHU for exchanging data between the CRM Server and the sites. There is a range of site types available for connecting SAP components. Sites are created in the Administration Console, a CRM Middleware tool for the administration of the data exchange of sites (local components). An SAP R/3 system is created, for example, as a site using the site type R/3. SAP provides many standard site types: CRM, CDB, R/3, Mobile client, External interface for XML, External interface for Idocs. You can create your own user-defined site types in Customizing. To do this, choose: 6$3 ,PSOHPHQWDWLRQ*XLGH→&XVWRPHU5HODWLRQVKLS0DQDJHPHQW→0LGGOHZDUHDQG5HOHYDQW &RPSRQHQWV→&RPPXQLFDWLRQ6HWWLQJV→&UHDWHVLWHVDQGVXEVFULSWLRQV
© SAP AG
CR100
Appendix-17
6\QFKURQL]DWLRQ%'RFV ² 6\QFKURQL]DWLRQ)ORZ
V%'RF
0 )& ($)+ , $-$-/.
6\QFKURQL]DWLRQ)ORZ
,QERXQG$GDSWHU 0DSSLQJ6HUYLFH 0HVVDJHIORZ 0RELOH%ULGJH P%'RF 9DOLGDWLRQ5HSOLFDWLRQ V%'RF &'%6HUYLFH 5HSOLFDWLRQ DQG5HDOLJQPHQW 6HUYLFH
&'%
2XWERXQG$GDSWHU
#$ %'& ($*) + , $-*$-/.
SAP AG 2004
The main tasks of a synchronization flow comprise the storage of files in the consolidated database (CDB) and the realignment service, that is, the redistribution (synchronization) of data to mobile clients $UFKLWHFWXUHDQG7HFKQRORJ\→0LGGOHZDUH→0RQLWRULQJ→4XHXHV→0RQLWRULQJ5 5 4XHXHV An LQERXQGsBDoc can be processed in two ways: y If assigned to an mBDoc, it is (always) mapped to this mBDoc, which is then passed to messaging flow for validation in the CRM Server. y If not assigned to an mBDoc, the sBDoc is (always) passed to synchronization BDoc outbound processing. 2XWERXQGprocessing can be done in two ways: y Initial load processing updates the CDB only. y Notification (delta) processing takes place if the data distribution is active (table SMOFINICUS) and receiver determination, realignment, extract, and other processes need to run.
© SAP AG
CR100
Appendix-18
7KH([WHUQDO,QWHUIDFH$GDSWHU ;0/62$3&KDQQHO
&506HUYHU &500LGGOHZDUH P%'RF
0HVVDJHV )ORZ
$GDSWHUIRUH[WHUQDO LQWHUIDFH
&50 $SSOLFDWLRQ
6$3 ([FKDQJH ,QIUDVWUXFWXUH
;0/
;0/ 0HVVDJLQJ 6\VWHP
;0/
6$3%XVLQHVV &RQQHFWRU
;0/
132 4/56 #87:9 ; %<%'=
SAP AG 2004
The figure shows a more detailed overview of SOAP/XML processing. SOAP/XML messages can be sent to XML messaging systems, which convert the XML into other XML schemata based on mapping rules and send these messages to other applications based on routing rules. For CRM – Business Connector communication, IDocs should be used. An IDoc transfer is quicker in comparison to SOAP/XML because, unlike an XML document, the IDoc document contains no metadata information (tags), therefore, the size of document sent down the line is substantially smaller in comparison.
© SAP AG
CR100
Appendix-19
7KH([WHUQDO,QWHUIDFH$GDSWHU $/(,'RF &KDQQHO &506HUYHU
6$3 ([FKDQJH ,QIUDVWUXFWXUH
&500LGGOHZDUH P%'RF
0HVVDJHV )ORZ
&50 $SSOLFDWLRQ
)ODWILOH LQ,'RF IRUPDW
ADFE $GDSWHUIRUH[WHUQDO LQWHUIDFH
132 4/56 #>7?9
ADFE GHIKJ .LM- (N*% ; - 6 7>9POQ$ .DR) -/. . CB())-S/%T(ULE . (V= (. .*DF&E -
%'@BA C
;0/
UG3DUW\$/( &RQYHUWHUV UG3DUW\$/( 0HVVDJLQJ 6\VWHP (', 6XEV\VWHP
(', ,'RF
,'RF
(',
SAP AG 2004
The figure shows a more detailed overview of IDoc processing. IDocs can be used to send messages to the Business Connector where an IDoc XML document will be established and mapped to other XML schemata such as Rosetta Net, xCBL or the customer‘s own schemata. IDocs can be used to send messages to a flat file. IDocs can be used to send messages to an ALE converter where IDocs are mapped to standardized message formats (EDI communication). IDocs can be used to send messages to an ALE messaging system. In contrast to an ALE converter, the message handler will not perform any conversion or mapping but instead receives IDocs and sends them to applications for processing. IDocs can be used to send messages to an EDI subsystem. In contrast to an ALE converter, the EDI subsystem does not use direct program-to-program communication for transferring IDocs.
© SAP AG
CR100
Appendix-20
,QWHJUDWLRQ&50² %XVLQHVV,QIRUPDWLRQ:DUHKRXVH
([WUDFWRI&50 %XVLQHVV 2EMHFWV
&506\VWHP &500LGGOHZDUH %'RF )ORZ
%'RF
%: $GDSWHU
6$3%:6\VWHP
'RZQORDGRI 6ROXWLRQ :RUNERRNV
5HSOLFDWLRQ RI6ROXWLRQ :RUNERRNV
SAP AG 2004
The 0LGGOHZDUH%URNHU provides data to an SAP Business Information Warehouse (SAP BW) system and receives reports from an SAP BW system to replicate them to Mobile Clients. However, only the extract function is available in a pure CRM Server Applications scenario (without Mobile Clients) because CRM Server Applications users will have direct access to an SAP BW system. The load of Solution Workbooks to the CRM system and, consequently, to Mobile Clients, is covered in the course 7$&500RELOH6DOHV6HUYLFH. The SAP BW is linked to the CRM Server partly by the Middleware Broker, partly by direct RFCs and BAPIs. The %:DGDSWHUextracts data from the SAP Business Information Warehouse (SAP BW) for the following BDoc types: y Sales orders, opportunities, leads, activities, contracts, billing documents (mBDoc types) y One single sBDoc: Chemical Market Potentials. Further customer-defined extractions of sBDocs without using a messaging flow are possible. y Product and campaign master data, which is not handled by the CRM middleware By default, changes to master data by a CRM Server Application always trigger a BDoc flow. However, the BW adapter does not use this BDoc flow for product data or campaign master data but receives the data from the application directly to put those data in a DataSource structure into the outbound queue where it is pulled by the SAP BW system using scheduled requests.
© SAP AG
CR100
Appendix-21
© SAP AG
CR100
Appendix-22