Customer Account creation rule is different in ECC and CRM

[ravikanthy]

Couple of customers were not replicated to CRM because of config issues. However, we don’t have that config maintained on the ECC as well. But it’s a hard error on the CRM while creating that customer in CRM. Can we make both CRM and ECC consistent in Customer creation rules.

Please note that we haven’t made any customizations on ECC Side to bypass this.

Example 1: We doesn’t have Geo-coder maintained in the ECC for PS, but ECC allowed to create the customer however creation of account on CRM side got failed.

I got the same error when I tried to maintain that Country in CRM directly in the customer account.

Example 2: Receiving the Tax number category error on the CRM side, however ECC also doesn’t have that Tax category maintained.

[ravikanthy]

Thank You Britta for you response.

We haven't customized any rules in Customer Creation on both ECC and CRM. Does this mean that SAP Standard behavior is different between ECC and CRM?

Gecoders or Tax Configurations are in synch on both ECC and CRM, because of the different rules from SAP, customer creation is failing on the CRM side.

Though its little risky and painful to bypass the restrictions on CRM side by doing some customization, it will be still our last choice as its hard to find out all the standard rules to include them in the custom code.

Best Regards,

Ravi

[brittacarols]

Based on the information you've provided, it seems that there is a discrepancy between the customer creation rules in ECC and CRM systems. Some customers are not being replicated to CRM due to configuration issues, even though the same configuration is not maintained in ECC. This is causing hard errors in CRM during customer creation.

To make both ECC and CRM consistent in customer creation rules, it is important to identify the specific configuration issues that are causing the errors in CRM. Once these issues are identified, you can work to update the configurations in both systems to ensure they are consistent.

For example, in the case of the Geo-coder not being maintained in ECC for PS, you may need to update the configuration in ECC to ensure that it is consistent with the configuration in CRM. Similarly, for the Tax number category error, you may need to update the configuration in both systems to ensure consistency.

It is important to note that customizations should not be made on the ECC side to bypass this issue. Instead, focus on identifying and resolving the configuration issues in both ECC and CRM to ensure that they are consistent in their customer creation rules.