Recommendation CRM - ISU Integration Enh. when Contract Creation long runtime via CRM Move-In

[NTeunckens]

Hello people

Can someone provide me with the best approach to handle the following issue :

We need to update some (custom) IS-U contract data and Replicate it between our IS-U and CRM system when a new Contract is created through MoveIn process from CRM. As SAP-KBA 1843479 suggests, BAdI's in both systems were implemented to handle non-standard data and the MoveIn-Out is generated from CRM ...

However, the Contract-Creation in IS-U seems to take 'longer' than the Replication ... When checking for relevant data (based on the newly created VERTRAG) in ECRM_CRM_UPLOAD / ECRM_CRM_DOWNLOAD BAdI's, we will not find it in the system yet, hence our Follow-Up actions will not go as expected. Basically the Replication process does not wait for a fully registered Contract in the EVER-table, hence we can not 'enrich' the Contract.

So my question :

What is the best approach to enable the 'enrichment' of the Created Contract? Should we enable this in the mentioned BAdI's, or is there an option via BAdI or UserExit upon Contract-Creation in IS-U?

My current line of thought would be to either try someting in the ECRM*-BAdI to enable a recurring lookup on the Contract OR make use of some other UserExit / BAdI in the IS-U process when the Contract is Created (added in EVER-table) ...

As I'm not well-versed in CRM, I would like to get some recommendations on which path to choose :

• SAP-KBA suggests the ECRM*-BAdI's, but how to enable a 'look for Created Contract until Found'?
• If I'm correct the BAPI "BAPI_ISUCONTRACT_CREATE" does also trigger these BAdI's which gives me confidence this would work in a background / no dialog scenario ...
• I'm familiar with IS-U UserExits for Contracts ("EXIT_SAPLES20_*"), but I believe they serve dialog-processes and so I'm not sure if they will be triggered ...
• I would like to keep away from modifying "Master Data Templates" for Move-In ...

I'm sure this must have come up in some projects, as the processing time might also be an issue expecting new records that are still undergoing 'creation' ...

Thanks for any suggestions

Kind regards

Nic T.

[NTeunckens]

As a quick follow-up, we're looking into the ISU UserExits from the Enhancement project "EMDK0001" to 'force' an explicit update of the "lost" data withing ISU as a 'fallback' ...