FSCM via WS-RM (without PI ) - Update termination issue

Question

Hello experts .
We are trying to integrate SD with FSCM ( credit management) using WS-RM (without PI).
Details of the issue and steps followed so far.
Ideal Scenario :
Once we create / change a sales order ( in SD ) , the interface Creditworthinessquery_out (WS Consumer ) gets triggered (in SD) and the subsequent response CREDITWORTHINESSQUERY_IN(Provider) is triggered from FSCM (with the details of creditworthiness).Once the query response in received an notification is triggered from SD to FSCM (asynchronous service).
After receiving the query response the functionality of credit check happens while creating / changing the sales order .
Configuration steps followed in SOAMANAGER
We have created end points for all the relevant service interfaces (Providers) , and also created logical ports for the respective consumers.
During the creation of logical ports - for the consumers we used the WSDL (of the providers) as the inbound message action.
(This has been done to all the services query , notification that are relevant in our integration).
Current behavior / issue .
While creating sales order the sales order is not getting saved (getting updated in the database).System allows us to complete the sales order creation process and also we get a message as sales order saved successfully. But then there is a update terminated express document that pops up. Sales order is not getting updated in the database.
When I see the logs/traces in SOAMANAGER I see that the query out is successful , query in has the right response (in warning state though) . But no notification is being triggered ?? 
How to overcome this update termination issue ?
When we see the SM13 log , it points to SLD issue (LCR 010: Internal error in SLD API). why do we need a SLD without PI

Answer 1

Hi  ,
Finally we are able to solve the update termination issue . But again we are using a work around .
Situation :
Once we executed the VA01 transaction we were getting update termination issue . After lots of debuggung we found that system was trying to get the Business system details ( Own business system data ) . The table lcrt_clntcache had no values.
Solution
We inserted appropriate values in the Table LCRT_CLNTCACH (business system data ) and now it works .This is a work around we got as of now.Credit checks are happening successfully and also integration is good .
(typically if we define business system in SLD (PI) , and run SLD_CHECK , this table gets populated , but in our case we are not using PI instead we are using WS-RM)
But now few questions arise .
a) Why do we need a business system in case we are not using PI ( typically we define business system and technical system in PI )  and instead using WS-RM ?
b) Is it a good practice to update the table ( as did in workaround above )?
c) Is this any bug and needs to be consulted with SAP ?
Please let me know your views .
Edited by: Vedula Adeep on Jan 16, 2012 8:42 AM