Quick guide for configuration of SAP Credit management web services without SAP PI
When you are configuring SAP FSCM web services - you have two options
- Configure as a multisystem with PI
- Configure as a local shortcut back to same system
This quick guide describes configuration of option 2 - as a local shortcut without PI
At first we have to be sure, that our Web service framework is configured correctly.
T-Code SRT_UTILS
 |
| Picture 1 |
At first run Check Technical Web Service Config option and choose a client number
 |
| Picture 2 |
On the next picture is shown result of the check how we want it to be - correct.
 |
| Picture 3 |
If there is problem with Idempotency and RFC Destination, you can click through the option right from the result list.
If there is some problem - at first run option Technical Web Service Configuration (from Picture 1)
 |
| Picture 4 |
And run the program.
 |
| Picture 5 |
This automatic configurations should be enough in most cases and after multiple runs, all should be green (in a check from Picture 3). If there are still problems we need to perform manual configuration.
If the problem is with bgRFC (green field on Picture 3) - you need to choose option bgRFC Configuration from SRT_TOOLS (Picture 1) and there go to the last tab Define Supervisor Dest.
 |
| Picture 6 |
If the field Destination (pink in the picture) is empty, you need to create new destination using the New button (yellow).
 |
| Picture 7 |
If the problem is Service RFC Destination and user (blue field on Picture 3), you need to create new destination in the tcode SM59 with the name WS_SRV_SAP_WSRT<clnt>, where <clnt> is nr. of current client.
 |
| Picture 8 |
Also create user SAP_WSRT with role SAP_BC_WEBSERVICE_USER
 |
| Picture 9 |
If the problem is Idempotency (pink field on Picture 3), you need to plan a job using tcode WSIDPADMIN
 |
| Picture 10 |
If the problem is Delay logon user (violet field on Picture 3), run report WSS_SETUP using tcode SE38
 |
| Picture 11 |
Set SAML 1.1 to Use Logon Ticket Trust
Result list should be all green.
 |
| Picture 12 |
Next you have to set endpoints to web services used by the framework. Services should be interconnected to itself using the local shortcut option.
Next process repeat for every web service from this list:
- CreditCommitmentNotification - Update credit exposure
- CreditManagementAccountByIDQuery - Provide credit master data
- CreditPaymentBehaviourSummaryNotification - Update payment behavior summary
- CreditWorthinessQuery – Carry out credit check
In tcode SOAMANAGER go to the Web service configuration option
 |
| Picture 13 |
Fill the field Object name with the asterisk wildcard (eg. CreditCommitmentNotification*)
You need to choose Consumer proxy (service with out at the end). If there are more of them, I choose the one with UKM in the name (works for me)
 |
| Picture 14 |
Click on proxy (service) and on the next screen, choose Create local shortcut
 |
| Picture 15 |
Fill port name and description - I usually use the name of the service, and check option Logical port is default
 |
| Picture 16 |
On the next screen search for the definition of (incoming) service. This service will be called by this proxy. Use same name but with the _In at the out (instead of out)
 |
| Picture 17 |
You can also check if the selected service is compatible with proxy
 |
| Picture 18 |
Now press finish.
Dont forget to repeat this activation process for every services from the list.
Next sources:
CreditQ provides Business Credit Management Techniques for your business. It's useful for both Suppliers & Buyers. Report payment defaulter now on CreditQ platform.
ReplyDeleteHi,
ReplyDeleteNicely explained. I really enjoyed your blog, thank you for posting it. I have learned about Business Reports' significance & the structure of a business report. Many agencies are providing business reports and MNS Credit Management Group is one such agency. I was searching for credit management company and your blog seems to be a great help for me.