Frequently, we have a business need to connect with an external third-party system from within the SAP environment by using an external web service to pull information. In such cases, knowing how to Create Consume and Troubleshoot SAP Web Service Consumer is essential to ensure smooth integration and data flow between SAP and the external system.
In layman terms, there are a few information present in the outside framework and is required in SAP framework. To accomplish this we would have to make SAP Web Administration Purchaser to call outer web administration from SAP framework.
A web service is required that is external to SAP. Either create one or ensure that one is available to you. All you need is a WSDL URL. In this article on how to create consume and Troubleshoot SAP Web Service Consumer, I will demonstrate how to access the bindings and include the URLs for all the bindings defined for a service.
Also, Read – WSDL File in SAP
Steps
Expecting we have been given a WSDL (displayed above) to use from inside ABAP, we would go to the SAP framework and follow the means as portrayed beneath.
Use Exchange SE80. Open Bundle in which you need to make the assistance and go to Big business Administrations and right snap on ‘Make’.
A spring up will show up. Select Help Buyer choice and snap ‘Cont.’. We are choosing Administration Buyer as we are consuming outer help into SAP climate.
For the Help Buyer source, we can pick among ‘Backend’, Endeavor Administration Archive, Outside WSDL/Pattern. Kindly select Outer WSDL/Blueprint and press proceed.
We can pick among Nearby document, URL, HTTP Objective and Administration Library. Pick URL choice and snap on Proceed.
Enter the WSDL in the URL way and snap on proceed.
You could get issues on clicking ‘Proceed’ in the wake of entering WSDL in URL way. I experienced underneath issues and am reporting something similar for reference.
ISSUE # 1 – Exception occurred in communication framework: Connection refused.
Resolution –
This issue comes when the firewall isn’t open for this framework. Raise a ticket with Framework Security group to get firewall open for this framework and issue will be settled.
ISSUE # 2 Exception occurred in library handler.
Resolution –
In Table SPROXSET set name NO_RPC_STYLE to esteem ‘X’ against your client id. Essentially, this will sidestep SIDL library and mistake won’t come.
In the following stage, it will request TR subtleties and bundle task. Enter the subtleties and press keep on completing the Shopper Administration creation.
ISSUE # 3 – Logical port template is inconsistent, regenerate and activate it
We were getting the beneath blunder ‘Legitimate port layout is conflicting, recover and initiate it’ at whatever point we were attempting to open any help buyer.
Resolution-
For this, I found one SAP Note 2315041 which we executed and blunder got settled.
When buyer administration is made, intermediary class and strategies will get made consequently which will be consumed in ABAP report.
All things considered, it isn’t prepared for use. You want to get the consistent port for the purchaser intermediary made and here comes the job of Premise group. A legitimate port is made for a particular customer intermediary to get to one specific restricting on the supplier framework. Raise a pass to Premise group to make the consistent port.
Go to t-code SOAMANAGER.
Click on Web Administration Setup. Search with object name as your intermediary class name.
Click on the inside name and you will be explored to underneath screen where subtleties of the legitimate port will be shown. When the intelligent port is made by Premise group, a passage will be made
To dive more into config side, here is the connection I found on SDN.
Quick Testing
It’s likewise conceivable to test the Purchaser Intermediary without making a program, utilizing exchange SE80. Follow these moves toward trigger a test-call:
- Go to exchange SE80 and show the Purchaser Intermediary object (Alter Item > Upgraded Choices > Undertaking Administrations > Client Intermediary).
- Click on the Test (F8)
- On the choice screen determine the Sensible Portand select the Strategy.
- Click on Execute (F8).
- With the XML Proofreader (Ctrl+F2)you can alter the information upsides of the solicitation XML.
- To set off the call, click on Execute (F8).
Now the fun part. How to call the web service from ABAP?
Make an occasion of the intermediary class passing the intelligent port name.
Then call the intermediary strategy to get the information into the inward table as.
ISSUE # 4 – Authenticate SOAP:1,027 SRT: Serialization / Deserialization Failed
While attempting to consume the intermediary, if beneath special case is tossed while executing the call to the web administration strategy.
“SOAP:1,027 SRT: Serialization / Deserialization Failed”
You truly need to guarantee for any date field about the data type used. ABAP type ought to be ISO plan if it gives the mix-up on testing:
YOU MAY LIKE THIS
SAP ABAP future in next coming years
Your Guide To Data Science Career 2024
ABAP Test Cockpit(ATC) – Introduction and Steps