In this blog, I would be explaining about the configuration of SAP Credit Management in SAP PI and ECC systems.
Before actually getting into that, let me brief a bit about what is SAP credit management and the purpose of it.
SAP Credit Management supports your company in determining the risk of losses on receivables from your business partners early and in making credit decisions efficiently and partially automated. It also supports you in a heterogeneous and distributed system landscape; by using system-independent XML interfaces. With SAP Credit Management, you can operate a centralized credit management.
The business systems [External] connected (for example, Sales and Distribution, Logistics Execution, and Financial Accounting) report the commitment of a business partner to SAP Credit Management via XML. These reports are then consolidated into the credit exposure in SAP Credit Management and checked against the current credit limit for the business partner. In addition to the credit limit check, you can also carry out other checks, such as oldest open item, maximum dunning level, or last payment.
SAP Credit Management is part of the SAP Financial Supply Chain Management. (From SAP Credit Management Configuration guide)
I was part of a SAP Credit Management implementation from SAP PI team to activate the required services.
Before activating the service in SAP PI make sure that the FINBASIS 603 and SAP APPL 6.03 software component versions are imported in to ESR. These can be downloaded from service market place and can be imported into ESR. Find the screen shots below:
SAP Credit Management is part of ES bundles, so it does not require any custom code (depending on requirement, the standard code can be enhanced) and make sure that the same above two namespaces are available in ECC systems in SPROXY T-code. If you can’t see in SPROXY T-code set filter for local objects or else contact basis team to import the standard package into your ECC system specific to SAP Credit Management.
Now, it’s time to activate the services in SAP PI. Below are the interfaces that will be activated in SAP PI:
Copy the process integration scenarios from standard software component version in to custom software component which we created and assign the required service interfaces and operation mapping from the input help. Find the screenshots below:
As per the above screen shot, a SAP ECC 6.0 system supports proxy communication. So for all the above 3 interfaces, ECC systems communicate with client proxy and server proxy with SAP PI before that proxy pre-configurations need to be done. Import the process integration scenario into ID by following below screen and assign the required parameters, by following wizard process automatically receiver communication channel, receiver agreement, interface determination and receiver determination will be created.
Difficult to find out both the outbound and inbound service interfaces, message types and operation mapping as we have two different software component versions and namespaces when configuring manually.