cancel
Showing results for 
Search instead for 
Did you mean: 

Client need to be opened for what all objects?

Former Member
0 Kudos

Hi Experts,

I need to list all the objects for which clients need to opened for customizing/master data download, for ex. when we are downloading condition records we need client to be in open/modifiable state, So what I need now is suggestions based on your experience wherever you feel that cleint needs to be opened for this activity .

Thanks for sharing your experience.

With Regards,

Mayank Choudhary

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello,

Basically there are three type of "objects" that can be enabled/disabled for a particular client via the SCC4 transaction.

1. Cross-client customizing

Allow users to modify cross-client customizing.

2. Repository objects

Allow users to generate and develop. (developments are always cross-client nvdr)

3. Client-dependant customizing

For customizing download 1 and 3 should be open.

For master data nothing should be open.

For conditions all should be open, however, it depends on which conditions. For non-standard conditions (eg custom declared Customer Pricing Tables 6XX) CRM needs to generate these tables. This is only for the first initial load. For a delta load afterwards you don't require anything. (or maybe x-client, not 100% sure about this).

There is no real general rule of thumb since it all depends on WHICH custo/master/conditions objects you will actually load.

For larger systems it's good to have the "3client" approach.

One golden client 100 (allow x-client custo and client custo)

One data client 110 (only create data in here, custos made in 100 can be imported via transport in tac SCC1)

One development client 120 (only development)

This way you keep everything separated and 110 is always available for real testing in development.

Hope this helps,

Joost

stephenjohannes
Active Contributor
0 Kudos

I disagree as a three client approach on CRM is worthless in a standard vanilla middleware connection (one ERP to one CRM).

For development there is no real need to have more than one client in your CRM system unless you are doing a multiple transfer/multiple crm scenario or using the BI reporting and need that client.

Personally the three client approach in one instance IMHO is just a way to cause extra work and effort by folks who want to make their CRM system work like an ERP system and don't understand running a CRM system in an efficient manner. The three client CRM approach sounds like a nightmare only designed to keep consultants or someone employed full-time. Then again I guess when you have a bloated staff, you need to find work to do and more processes to invent to keep people busy.

The single CRM client approach is considered best practice unless you have a specific data transfer scenario that requires separate clients for data purposes(and not change management). It's been this way since 2.0C and beyond :).

Take care,

Stephen

former_member297645
Participant
0 Kudos

Hi Mayank,

Even I tried for the list of all cross-client download objects in vain. I figured a work around for this and found it helpful.

To check wether a particular object is downloading cross-client data:

1) Determine all the tables involved by executing CRM table SMOFTABLES with the adapter object name. (Ex: DNL_CUST_SHIP downloads data from the following tables: TINC, TINCT, TPRIO, TPRIT, TVSB, TVSBT.)

2) In order to check wether these tables are cross client or not, execute table DD02L in R/3 system with all the tables determined in step 1.

Ex: DNL_CUST_SHIP

Table : DD02L

Table name----


Client-specific

TINC----


X

TINCT----


X

TPRIO----


X

TPRIT----


X

TVSB----


X

TVSBT----


X

This means that none of the tables invloved in DNL_CUST_SHIP download are cross-client and can be downloaded without opening the client.

If there are any client independent tables involved then we need to open client and perform download.

Ex. DNL_CUST_CNDALL

The below mentioned tables are involved in DNL_CUST_CNDALL object download and are cross-client and hence the client needs to be open while downloading the object.

TMC1K

TMC1D

TMC1

T681

T682

T682I

T682T

T682Z

Hope this helps

Regards,

Aj K