TACRM5 Class Questions

One Question on Mobile Clients

Question
Can multiple laptops be connected to one site? Or, does each laptop have to have its own site?
There's conflicting info. on this, as it says multiple employees can be assigned to a site. The issue
is: can each employee have their own laptop, or are they expected to share the same database
via a workgroup server.
Answer
There are two possible scenarios:
1. No workgroup is used and each laptop gets its own local database which is replicated
through synchronization with the middleware CDB.
2. All laptops share a CDB on a workgroup station, so in this situation all employees data would
reside in one place.
Scenario 1
Each installation (laptop) is a unique site. There should be one site for each laptop, and one
laptop for each site. One site can be assigned to one or more employees. Normally, one site is
assigned to one employee, however it is possible to have multiple users assigned to a site. On
the other hand, multiple installations (laptops) cannot be linked to one site.
Whenever a site is assigned to a laptop, SITEID value is stored in the registry of that laptop to
make sure not more than one site can be assigned to that laptop. Also, in the CRM Server, a
unique SQL Server Database ID is stored in that siteid record to make sure that this siteid is not
assigned to any other laptop. In other words, each installation/laptop has the SQL Server
Database 'ides', the ID of this database is recorded in the CRM Server against one unique single
site (table SMOHSITEID in CRM20x). This link between DB-ID and Site-ID is validated on each
data exchange. Therefore, one installation/laptop/ides database can be linked to only one site.
Attachment of one or multiple employees to a site via Admin Console does nothing in 2.0x or 3.0.
It is one of the features that will be used in the future.
Scenario 2
In case of workgroup scenarios, you setup one site on a server machine and a group of
employees can work with that using, for example, the Citrix solution. A site is a like an application
database here. Also, any of these employees can go to server machine and work there directly.
If you need multiple employees attached to a site:
If you need multiple employees attached to a site, then in case of 2.0x, it involves creating a Bulk
Subscription for all employees... then any employee can login on that site. In case of 3.0, you
have to create Employee Bulk Subscription as well as specific users intelligent subscription. As
many users subscriptions you create, that many users can connect to that site and use it.

Other Questions
Question 1)
Are orders from CRM re-priced in R/3 when they are sent to R/3?
Answer
Only if you configure it to re-price when going to R/3.
In CRM goto Table SMOFPARSFA, Parameter R3ACOMMON/PRICINGTYPE. Set Value from 'G'
to 'B' = re-price.

May need OSS Note 410907 to allow value 'B' as an entry.

Additional Question: Won't every order going from CRM to R/3 be priced in R/3? And if the
pricing conditions are not matched, won't they be different? (though they shouldn't be). As I
understand it, R/3 is the system of record for pricing, and it is copied from R/3 to CRM.
Orders are only re-priced in R/3 if you choose to re-price them with that table setting. R/3 will
accept the price (and conditions) given to it by CRM. The only 'matching' needed is the price
procedure CRM is passing must exist in R/3. CRM does get a copy of all the price records and
configuration from R/3 but the key to remember is that not all the R/3 pricing config is supported
in CRM. Nor is all the data R/3 uses in its pricing communication structure available in CRM (i.e.
VPRS = Cost). I recommend to all customers that they mimic only the needed steps in the R/3
price procedure that apply to the customer's net price. All other conditions and steps are usually
internal and do not need to be calculated in CRM. If you choose the re-price option, then these
will be executed in R/3 when the order passes.
Another Consultant says: From my experience, most people are not re-pricing orders when
transferring back to the R/3 system. Typically, Ive just seen customers do a re-determination of
taxes upon invoicing; possibly freight as well to carry in freight costs (from within R/3) from
Shipping.
It's a more complex topic that deserves further discussion, hope this sheds some light.
Question 2)
Does CRM Pricing take into account the Plant/Storage Location?
Answer
No. Standard R/3 pricing is sales area related (sales area/customer, sale area/material, sales
area/price list/material, etc) not plant related. I assume CRM is the same. (see CRM tables
SAP004, 5, 6 or 7).
This can be achieved, however, with some configuration and development work.
Question 3)
What's the purpose of Plant in CRM? It comes over as a Business Partner, but what does it do?
Answer
Purpose is for APO ATP checking: rules based ATP check where you first search one plant, then
another plant if theres not enough qty available in the first plant. Transaction CRM_LOCMAP is
where the cross-reference between the plant and CRM business partner is defined.
Plant also relates to taxes (what country/region the goods leave from).
Question 4)
Can you do availability check from R/3 (as opposed to APO) for all scenarios in CRM or only for
the Internet Sales scenario?
Answer
As of late November, we were told that within the CRM System, ATP can only be done via APO.
But, that there were plans to provide the option to do ATP check via R/3 in a Service Pack.
Yesterday I was told that it is possible that this may be in Service Pack 9 or 10 but I am waiting
to hear the definitive answer re: when R/3 ATP functionality within CRM will be available. As you
indicated in your question, right now we can only do R/3 ATP check in Internet Sales. Will keep
you posted on what I hear from CRM Product Management re: this topic.

Another Consultant: You can also do ATP from R/3 for the CRM online scenario.
Question 5)
What order statuses are viewable in CRM.
Answer
Open orders, completed, and delivery information.
Another Consultant: If you are talking about ISA, they are: Open, Partially Complete, Complete.