Sales Docs from CRM to R/3

[Former Member]

Hi,

I created the Sales order of type ZFC(Frees Ads/Repls) in the CRM 4.0.

But the same did not flow back to R/3.

I have maintained the Number ranges,Transaction Types,Item Categories,Item category determinations etc in the CRM (as in R/3).

The order is getting created in CRM correctly but the same has not been replicated to R/3.

Is there any missing config to make this happen.

Thanks in advance.

Rohita D.

[former_member927251]

Hi Rohita,

Check your Middleware Configuration as follows :

CRM Middleware configurations

1. Source client for Client copy

Using t-code SCC3 in both CRM and ISU to get the source client used for client copy. Get source client for profile SAP_ALL.

2. RFC Destinations

Use t-code SM59 and check if the following RFC destinations have been created:

• CRM

o R/3 Destination for CRM e.g. CRTCLNT240

o R/3 Destination for ISU e.g. ISTCLNT240

o Logical Destination for Middleware R&R queues – one for current client and one for client 000. e.g. SAPCRM_MW_RR_240, SAPCRM_MW_RR_000

o TCP/IP Destination for IPC dispatcher e.g. IPC_RFC_DISPATCHER

o TCP/IP Destination for IPC server e.g. IPC_RFC_SERVER

• ISU

o R/3 Destination for CRM e.g. CRTCLNT240

o R/3 Destination for ISU e.g. ISTCLNT240

3. Logical Systems

Using t-code SALE check if the following logical systems have been created:

• CRM

o Own logical system – e.g. CRTCLNT240

o Logical system for ISU – e.g. ISTCLNT240

o Logical system for source client used in client copy – e.g. CRTCLNT200

• ISU

o Own logical system – e.g. ISTCLNT240

o Logical system for CRM – e.g. CRTCLNT240

o Logical system for source client used in client copy – e.g. ISTCLNT200

Check if own logical system is assigned to the client.

Path: Sending and Receiving systems -> Logical Systems -> Assign Client to Logical System.

Convert Logical System name in application tables

Use t-code BDLS to convert logical system names in the application system.

1. Enter old logical system name retrieved in step 1. e.g. CRTCLNT200

2. Enter new logical system name e.g. CRTCLNT240.

3. Select radio button Conversion of Client-Dependent Tables and execute the transaction.

This process needs to be carried out 4 times: twice in CRM and twice in ISU.

• CRM

o Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.

o Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.

• ISU

o Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.

o Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.

4. Middleware Parameter tables

Use t-code SM30 to maintain middleware parameters in following tables

• CRM

o Table SMOFPARSFA:

Change value for following parameter entry:

Key - R3A_COMMON

Para name - CRM_DEFAULT_DESTINATION

Value - Old ISU logical system -> new ISU logical system

E.g. ISTCLNT200 -> ISTCLNT240

• ISU

o Table CRMRFCPAR:

Delete the previous entry for the following key:

User - CRM

Object name - *

RFC Destination - Old RFC destination for CRM e.g. CRTCLNT200.

Load types - All Load Types

Create new entry with following data:

User - CRM

Object name - *

RFC Destination - New RFC destination for CRM e.g. CRTCLNT240.

Load types - All Load Types

In Queue flag - X

Send XML – No XML

o Table CRMPAROLTP:

Change value for following parameter entry:

Para name - CRM_DEFAULT_DESTINATION

User - CRM

Value - Old CRM logical system -> new CRM logical system

E.g. CRTCLNT200 -> CRTCLNT240

5. Admin Console (Sites and subscriptions)

Using t-code SMOEAC in CRM change attributes for the following sites.

• CRM site

o Name: Change name from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240

o Description: Change description from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240

o Site attributes: Change RFC destination from old CRM RFC destination to new CRM RFC destination e.g. CRTCLNT200 -> CRTCLNT240

o Click on get values button to refresh logical system details.

• ISU site

o Name: Change name from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240

o Description: Change description from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240

o Site attributes: Change RFC destination from old ISU RFC destination to new ISU RFC destination e.g. ISTCLNT200 -> ISTCLNT240

o Click on get values button to refresh logical system details.

Check if ISU site is assigned to following subscriptions.

• All Business Agreements (MESG)

• All Business Partner Relationship (MESG)

• All Business Partners (MESG)

• All Business Transactions

• IS-U Connection Objects (MESG)

• IS-U Contracts (MESG)

• IS-U Points of Delivery (MESG)

• Product Materials (MESG)

6. CRM Middleware Queues

Inbound Queues:

I. Execute transaction SMQR.

II. Change AS group from ‘DEFAULT’ to ‘parallel generators’. Path: Edit -> Change AS Group

III. Register following queues:

• CRM

o CSA*

o R3A*

• ISU

o R3A*

Outbound Queues:

I. Execute transaction SMQS.

II. Change AS group from ‘DEFAULT’ to ‘parallel generators’. Path: Edit -> Change AS Group

III. Register following queues:

• CRM

o CSA*

o R3A*

• ISU

o R3A*

R&R Queues:

I. Execute transaction SMOHQUEUE in CRM.

II. Check if all queues have status ‘Released’.

III. Start Queue Demon by clicking on ‘Start Queue Demon’.

<b>Please reward points if it helps.</b>

Regards,

Amit Mishra

[Former Member]

Hi Rohita,

In Admin Console of CRM (T.Code: SMOEAC), please check if you have subscribed to object 'All Business Transactions (MESG)' without giving any filter criteria on sales doc type (ZFC) for R/3 site. Did you check for BDoc messages? Did you have this replication problem of sales order for the first time?

Thanks.

Ajay Kiran

[Former Member]

Hai Rohit,

Check the following:-

1. Did you create the sites in Admin Console and assign the BusTrans Subscription.

2. Map the Org Models. CRM Org Model to Sales Org.

3. Are the BP, PRODUCT Mapping working properly.

If these work then, the rest of NUM.RANG. RFC check them.

Check SMQ1 if the Sales order is in outbound queue in CRM

Check SMQ1/SMQ2 in both sys

check SMW01 for the data transfer.

Regards,

Prem

[Former Member]

Hai Rohit,

Check the following:-

1. Did you create the sites in Admin Console and assign the BusTrans Subscription.

2. Map the Org Models. CRM Org Model to Sales Org.

3. Are the BP, PRODUCT Mapping working properly.

If these work then, the rest of NUM.RANG. RFC check them.

Check SMQ1 if the Sales order is in outbound queue in CRM

Check SMQ1/SMQ2 in both sys

check SMW01 for the data transfer.

Regards,

Prem

[KaushalShah]

You should have an R3 site maintained in SMOEAC. Also, that site should have a subscription for sales documents (bdoc BUS_TRANSACTION_MESSEGE).

Hope this helps.

Regards,

Kaushal

[Former Member]

Hi,

Check the settings in Admin Console..

Wregds,

Prasad