Skip to Content

In most customers implementations,it is decided that not all data is required to flow from one system to the other. Even if it is technically possible in standard integration.

The general recommendation is to apply all data filters in the middleware. But there are some exceptions of already built filters that we can laverage:

Data Exchange Filters – C4C Outbound

Consideration

All integration decisions in C4C, are controlled in the Business Configuration, there you can decide to integrate Accounts and Contacts uni or bi-directional, prospects and Account Hierarchies.

Apart from that there are not many Integration filters to be applied from C4C out of the box.

Data Exchange Filters – C4C Inbound (From ERP)

Consideration

When going live with a subset of the ERP solution (1 company, 1 sales org) the decision has to be made whether to replicate the entire organizational structure from ERP and whether to send all accounts or a subset of the accounts.

If the decision is made to send a subset of the accounts to C4C, filters will need to be added to either the outbound IDOC configuration or the middleware solution to only include accounts that exist in those org units in scope.

Limitations

The initial set of filters you can apply in ERP (Transaction BD64) are very few, only consider Account Groups, Org units, Channels , Divisions, region, Postal Codes, Contact Person Function, Country Key, Credit Control Area.

BD64.png

Recommendation

Filter in the backend system if :

  • Some sensitive records may not go out of the system at all
  • It is a Large portion of the data to be filtered out on HCI/PI: Example: Let’s assume ERP has 1,000,000 accounts and only 100,000 are relevant for C4C. In this case it would not make sense to send 1,000,000 IDocs to PI and throw away 90% of them.

Use this if your filter requirements can be fulfilled by the filter objects available in the distribution model

Simple scenarios can be supported this way:

ALE Distribution Model BADI: IDOC_CREATION_CHECK

There is a second BADI that may be used in this context

BADI BDCP_BEFORE_WRITE to prevent change pointers from being written

For both BADIs: Watch out to not to interfere with other ALE integrations at the customer!

If the ERP filters are not sufficient, then other filters can be applied in the middleware.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply