Skip to Content

SAP FSCM or Financial Supply chain management for Credit Management is a widely used SAP Application package on an SAP implementation.

The business logic for the credit management function exists with the SAP FINBASIS core component.  Interestingly the integration medium used for the above is SAP PI.  SAP PI provides out of the box integration content around FSCM.

The core scenarios involved in FSCM are Creditworthiness Query and Credit Exposure updates.

 

 

image

The FSCM Creditworthiness calls are synchronous in nature and are triggered whenever a configured document type like Sales Order/Delivery/Invoice is changed or created.

Though the FSCM business function lays on the same box as ECC, the driver for using PI, in my opinion was to leverage SAP FSCM as a separate SAP product for clients not implementing ECC.

This PI integration can sometimes become a major pinch-point of PI and operations in general.  The following are the distinct disadvantages which I observed:

 

 

  • The above brings PI on a critical path for the order acceptance process. This is because if PI communications are not up, order save or create fails due to the synchronous credit queries failing.
  • It also makes scheduling outage/maintenance windows for PI difficult, and unavailability of PI, might have adverse business impacts on incoming orders via various channels.

 

  • This process also takes a major performance hit on PI.  Each Synchronous message engages additional dialog resources on PI, whereby increasing CPU utilizations. In one of my implementations, the customer’s business process involved accepting over half a million orders a day.  This results in as many calls to PI. Analysis showed that over 60% PI resources consumption was due to the above calls.

 

  • This also increases the effective order creation time in ECC, due to an additional loop in PI.

 

Overall a PI based solution for a customer, implementing SAP adds considerable overhead.

 

Looking into the future – Per SAP documentation and product management briefings, there is a potential non PI solution available for SAP ECC Ehp5.  It is a web service – WSRM based solution.  The web service provider and the consumer are on the same physical system. In my opinion the following could be dis-advantages of the solution:

 

  • Web Service calls would also go through the ICM.  This increases the number of HTTP connections to be opened for direct ECC order creation calls.
  • Along with this Web service also bring in an additional overhead, whereby impacting the order creation or change times.

 

Overall the WS-RM solution might also add additional overheads.

 

A far simpler solution in this use-case would be to eliminate PI as well as Web Services and do a direct ECC query.  This can easily be achieved as the Function Modules and bAdis exists in ECC.

I did this for one of my client, who had a requirement of over .5 million orders a day.   This can be achieved, by simply by-passing the call to the outbound proxies and calling the inbound proxies directly via an implicit enhancement. This can be done on the method  CHECK_CREDIT of class IF_UKM_CREDIT_QUERY_R3.

 

The following is the advantage to this approach:

  • It reduces the load on PI for Sync Calls
  • It  reduces the order creation times
  • It makes the maintenance of PI more  manageable
  • It does not create any additional load on the ICM either.

 

I feel such a solution is far more sustainable and performant in such situations.

 

I am working on putting a How to Document for the same and would post it soon somewhere on SDN.

To report this post you need to login first.

4 Comments

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

  1. Sascha Wenninger
    Hi Abhishek,

    One of our projects is currently implementing FSCM on ECC 6.05 with the new WS-RM integration. It seems to work quite well and it’s simpler design (as opposed to sync calls via PI) is a bonus. Even so, we had to spend a little bit of time on the WS-RM configuration as none of us had done it before (and there may have been the odd bug in the documentation 😉

    I agree though that it’s odd that there is no standard way to do integration without webservices for customers who run FSCM on their central ECC system. It woul be nice to have an option.

    (0) 
    1. Abhishek Vinayaka Post author
      Hi Sascha,

      WS-RM or webservices based integration makes sense for cross component communication. It does create additional communication overhead when  the web service host and consumer are on the same system.

      I have implemented the non-PI non-WSRM option for one of my implementation. Would put in a blog on how to achieve the same soon.

      Abhishek

      (0) 
      1. Jennie Chen

        Hi Abhishek,

        Have you had a chance to put a blog for how to implement the non-PI non-WSRM option as you mentioned earlier?  We are currently planning to switch our FSCM from PI to WS-RM, but the overhead of web service is still a big concern to us.  We would like to evaluate the 3rd option if we have one.  Thanks!

        (0) 
    2. Mahima Gupta

      Hi Sascha ,

      In my current project we are trying to configure FSCM with WS-RM integration but there seems to be some issue . It is throwing an error related to PI. BADis have been implemented and Web Services have bene configured but still the error is coming .

      Would apprecaite your help on this .

      Mahima .

      (0) 

Leave a Reply