Hi Dayakar,
In addition to Ankur Patel's excellent tips, I would like add on technical tips for you.
I am also suspicious of interface issue between FI-AR and FSCM.
Check-list for this kinds of errors;
1. High-level Web service configuration and connectivity
tx SOAMANAGER, service administration > web service configuration >
select 'CreditPaymentBehaviourSummaryNotification_In' or any target web service of interest,
click apply selection > overview tab > click 'Open Web Service navigator for selected binding'
(this directly test web service connectivity between provider and consumer, you might need some setting in PI/SLD in order to use this kinds of WS testing)
also check configuration for CreditPaymentBehaviourSummaryNotification_Out or any target web service of interest.
2. General messasing processing in ECC side
tx SXMB_MONI -> select 'Monitor for Processed XML Messages'
any error status and XML file may light on root causes
3. Low level messasing processing in ECC side
tx smq1 (messages inbound e outbound queue), smq2 (messages inbound e outbound queue)
any weird actions in system level could disrupt whold credit actions
4. SLD check in ECC side
In some(special) case, you might need to maintain ECC server information in SLD database, depending on your landscape. Just simply test it in tx SLDCHECK
5. ECC server optimization
In complex error case, ECC server level parameters should be optimized in order to allocate sufficient resource for processing web service. (eg QRFC parameter)
Best regards,
Ted
