Update for Release 1302 - August 2013
In this blog, I want to share the information on my solution template “SAP Business Suite BO List”.
You can download the solution template (from the Business Center, see details below) and import it into a customer-specific solution. The template is for SAP Cloud for Customer (Customer OnDemand) 1302. In the template you will find functionality to read business document from a SAP Business Suite system through an SAP enterprise service and display them in a Embedded Component that you can use for example in the Account Thing Inspector.
In the following figure, you can see the Account Thing Inspector, extended with a new tab that shows a list of sales orders from an SAP ERP system.
The concrete implementation is done for reading sales order from an SAP ERP system. You can easily replace the enterprise service for sales orders by an enterprise service for different BOs. (Please note that Customer OnDemand has already a standard functionality to read sales orders from an SAP ERP system. So this template is meant to show the capability of reading business document from a SAP Business Suite system through an SAP enterprise service, and extend this to other SAP Suite BOs.)
How to use the solution template?
Prerequisites:
To import the solution template into your solution:
See also the documentation on solution templates. (To download the documentation, select https://help.sap.com/sdk , SAP Solutions OnDemand Studio 1302, Complete help: Print version. In the documentation, see section “Solution Templates Quick Guide for Customer-Specific Solutions”)
What are the details of the solution?
The solution contains an embedded component BusinessObjectList.EC.uicomponent (EC). This EC invokes a custom BO BusinessObjectList and triggers the GetResult action of the BO. The GetResult action calls a web service that reads a list of SAP business suite BOs. The list is displayed in the EC.
The following figure shows the architecture overview:
If you want to test the solution, you have to create a communication system and communication arrangement in the system. For details, see the documentation on “External Web Service Integration”.
For my tests I have used the SAP ERP workplace (erp.esworkplace.sap.com). A service path, enter “sap/bc/srt/pm/sap/ecc_salesorder009qr/800/default_profile/2/binding_t_http_a_http_ecc_salesorder009qr_default_profile”. You need a user on the SAP ERP workplace (see below). Unfortunately SAP has closed the test systems for the SAP ERP workplace as of 2013. So you need an individual ERP test system for testing.
Having the communication arrangement created, you can test the result in the text UI that you can find in the solution (BusinessObjectListTest.QA.uicomponent). For example, you can enter AccountID = 1000 (the famous “Becker Berlin” account).
Finally, you can add the EC to the Account Thing Inspector:
Addition Remarks:
You can find all SAP enterprise services on the SAP Enterprise Services Workplace homepage http://esworkplace.sap.com. On this page you can register a user for the test landscape. As of 2013, this service has been closed.
You can also browser through the business objects from ERP, CRM, SCM and SRM and find the enterprise services. The services that can be used for creating a BO list have follow the naming convention “Query Business Object In”.
The services provide 2 types of WSDL file: “ESR” and “Endpoint”. In the “Endpoint” WSDL, you can find the service endpoint of the test landscape that you need to configure the communication arrangement.
You cannot import this solution template into a ByDesign system, but this is rather a technical problem. But you can build this use case also on ByDesign in the same way. A stable anchor that you can use to incorporate the EC is available in the Account OIF.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
10 | |
10 | |
9 | |
8 | |
7 | |
7 | |
7 | |
7 | |
6 |