This document gives an overview on the capabilities of external integration of SAP Business ByDesign / SAP Cloud for Customer custom solutions developed with SAP Cloud Applications Studio. This document is relevant for you if:
- You are developing (or planning) a custom solution for SAP Business ByDesign or SAP Cloud for Customer with SAP Cloud Applications Studio
- You are searching for means of integrating this solution with an external system.
Figure 1 shows an overview on the options.
Figure 1: Integration scenarios for ByD/SoD with External Systems
The following tables show the availability of the scenanrios:
| No | Inbound Calls (ByD/SoD Tenant as Server) | SAP Scenario (SAP BO and SAP UI/web service) | SAP Scenario Extensible? | Custom scenario (SAP BO and custom UI/web services | Custom scenario (custom BO and custom UI/web service) |
|---|---|---|---|---|---|
| 1 | Launch UI via URL | Yes | No | Yes (FP2.6) | Yes (FP2.6) |
| 2 |
Web service call (REST) |
No | No | Yes (FP4.0, SoD only) | Yes (FP4.0, SoD only) |
| 3 | Web service call (SOAP) | Yes | Yes (FP2.6) (1) | Yes (FP2.6) | Yes (FP2.6) |
| 4 | Receive iForms via Mail-Server | Yes | No | No | No |
| 5 |
Upload from file share |
Yes | No | Yes (FP2.6) | Yes (FP2.6) |
| 6 | Receive unformatted mails via mail server | Yes | No | Not applicable | Yes (FP2.6) |
Table 1: Inbound sceanrios. Comment: (1): SAP scenario must be prepared for extensibility
| No | Outbound Calls (ByD/SoD Tenant as Client) | SAP Scenario (SAP BO and SAP UI/web service) | SAP Scenario Extensible? | Custom scenario (SAP BO and custom UI/web service) | Custom scenario (custom BO and custom UI/web service) |
|---|---|---|---|---|---|
| 1 | Call services from UIs via mashup (RSS/Atom, REST, SOAP) | Yes | Yes (FP2.6) (1) | Yes (FP2.6) | Yes (FP2.6) |
| 2 | Custom controls (Silverlight) | Yes | Yes (FP2.6) (1) | Yes (FP2.6) | Yes (FP2.6) |
| 3 | Call web services in custom code (SOAP) | Yes | Yes (FP2.6) (1) | Yes (FP4.0) | Yes (FP4.0) |
| 4 | Call web services in custom code (REST) | Yes (Customer OD only) | No | Yes (FP4.0) | Yes (FP4.0) |
| 5 | Send Forms/iForms via mail, fax, print server | Yes | Yes (FP2.6)(1) | No (frontend print only) | No (frontend print only) |
| 6 | Download into file share | Yes | No | No | No |
| 7 | Send unformatted mails via mail server | Yes | No | No | Yes (FP2.6) |
Table 2: Outbound sceanrios. Comment: (1): SAP scenario must be prepared for extensibility
Terms and abbreviations used in this document:
- BO: Business object
- Studio: SAP Cloud Applications Studio (for SAP Business ByDesign / SAP Cloud for Customer)
- Custom BO: Business object implemented with the studio
- External Integration: Integration of a custom solution (customer-specific or via SAP store distribution) with an external system through web services, mail, …
- ByD/SoD tenant: Tenant on an SAP Business ByDesign or SAP Sales OnDemand system
Help resources used in this document:
- [Studio Library]: SAP Cloud Applications Studio Library: Available in the studio under https://help.sap.com_studio_cloud/
- [PSM Documentation] (FP3.5 and higher): Available in the studio under Help -> View Help -> Public Solution Model
- [Repository Explorer]: (FP4.0 and higher): In the studio, select View -> Other Windows -> Repository Explorer
- Thomas Schneider: SAP Business ByDesign Studio -Application Development: http://www.sap-press.com/products/SAP-Business-ByDesign-Studio-%E2%80%94-Application-Development.html
Table of Content:
- Launch UI via URL
- Web service call (REST)
- Web service call (SOAP)
- Call services from UIs via Mashup
- Custom controls (Silverlight)
- Call Web Services (SOAP) from Custom Code (BO Integration)
- Call Web Services (REST) from Custom Code (BO Integration)
- Formatted Input/Output (Print, Fax, Mail)
- Upload from File Share
- Send/Receive Unformatted Mails via Mail Server
Launch UI via URL
You can launch a UI from a ByD/SoD tenant via URL using an inport of the respective UI.
For OWL-based UIs, the basic URL schema is as follows:
https://<hostname>.<domain>
/sap/byd/nav
?bo_ns=<URL encoded BO namespace like specified in the OBN in-port>
&bo=<URL encoded BO name like specified in the OBN in-port>
&node=<URL encoded node name like specified in the OBN in-port>
&operation=<URL encoded OBN operation like specified in the OBN in-port>
optional:
&object_key=<URL encoded BO instance key, for example UUID> (note: no “-” separator is allowed and all characters must be upper case)
&key_type=<BO instance type (GDT)>
¶m = <any additional flat parameter that is required by the OBN in-port>
Example:
/sap/byd/nav?bo_ns=http%3A%2F%2Fsap.com%2Fxi%2FAP%2FCRM%2FGlobal&bo=Opportunity &node=Root&operation=Open&object_key=00163E01041602DE83D9D26C367E44A1&key_type=APC_V_UUID
For thing-based UIs (see Thing-Based UIs and Custom Solutions in Cloud for Customer), the basic URL schema is as follows:
https://<hostname>.<domain>
/sap/byd/nav
?bo=<URL encoded ThingType name>
&nav_mode=TI ( identifies the navigation to the thing inspector)
¶m.Key= <URL encoded UUID representation>
Example:
/sap/byd/nav?bo=YCHV8LLCY_PROJECT_TT&nav_mode=TI¶m.Key=00163E02944F1ED1B59B2A3517D83F98
To determine the tenant URL (https://<hostname>.<domain>), use the re-use service Context.GetSystemURL().
To determine UUID, use the re-use service this.GetObjectNodeReference().
Example coding:
// get URL, for example to show on the UI or send by mail
var URL =
Context.GetSystemURL() +
"/sap/byd/nav?bo=YCHV8LLCY_PROJECT_TT&nav_mode=TI¶m.Key=" +
this.GetObjectNodeReference().UUID.content.ToString();Availability: FP2.6 (for OWL-based UIs), SoD wave 4 (for thing-based UIs)
Transfer protocol: HTTPS
Authentification: User/password or user certificates
Scope: Launch a ByD/SoD UI (SAP or custom UI), prefill the data of an UI inport
Usage: User to system communication (for example display of a ByD/SoD document, create a ByD/SoD document via UI)
Development process overview:
- Open the ByD/SoD UI and analyze the inports of the UI
- Call the UI using the inport
Documentation: not yet available
Web service call (REST)
You can use REST/OData-based web services of the ByD/SoD tenant for user-to-system or system-to-system communication. SAP supports the OData-Protocol. OData follows many of the principles of REST. OData provides a uniform interface. This means that you address items in an OData feed (i.e. how to construct URIs), you interact with a service (using HTTP verbs), etc. in the same way across any OData Service, regardless of the data it exposes. For details on the OData protocol, see http://www.odata.org.
REST/OData-based web services are
- implemented with the UI designer in the thing type model on top of SAP BOs or custom BOs
- implemented with the report designer on top of SAP BOs or custom BOs
For a thing type-based REST service, the basic URL schema is as follows:
https://<hostname>.<domain>
/sap/byd/rest/
<name of the work center view> /
<name of the thing type>s
?<paramter list, for example filter, paging, etc.>
Example:
/sap/byd/rest/zcontract_wcf.wcf.svc/zcontracts?$filter=Account eq ‘THOMAS’&$top=1
Availability: FP4.0 and higher – SoD only
Transfer protocol: HTTPS/REST
Authentification: User/password or user certificates
Scope
- Read (query, retrieve) operations on top of a SAP BO or custom BO; write (create, update, delete, action) operations are not supported in FP4.0
- Request and response data type are flat structures and do not contains hierarchies
Usage: User to system communication (for example for native mobile devices)
Development process overview (1): thing type-based REST services
- In the studio select a business object and create a thing type (under “Create Screens”)
- Open the thing type in the UI designer and configure the binding and the navigation for the OData service
- Define the authorization (add the thing type to a work center)
Development process overview (2): report based REST services: To be done
Documentation: not yet available
Example:
https://<server>/sap/byd/rest/<wocview>/<thingtype>?<parameterlist>
Example:
https://qpc-cust905.dev.sapbydesign.com/sap/byd/rest/zcontract_t11_wcf.wcf.svc/zcontract_t11s?$filter=Account eq ‘THOMAS’&$top=1
See info on OData for ByDesign:
Web service call (SOAP)
You can use SOAP-based web services of the ByD/SoD tenant for user-to-system or system-to-system communication.
Availability: FP2.6 and higher
Transfer protocol: HTTPS/SOAP
Authentification: User/password or user certificates
Scope
- Multiple read (query, retrieve) and write (create, update, delete, action) operations on top of a SAP BO or custom BO
- Request and response data type can contain hierarchies including to-many multiplicity (for example: header – item – sub-item)
Usage
- System to system communication (for example ByD/SoD tenant to ByD/SoD tenant)
- User to system communication (for example for native mobile devices)
Development process overview
- In the studio select a business object and define a web service with multiple operations. Define the authorization profile (for user-to-system or system-to-system communication(as of FP4.0) )
- Activate the service endpoint and WSDL
- Assign the authorization profile to a user or define the system-to-system communication (communication arrangement, FP4.0)
- Download the generated WSDL and use in a client
Documentation:
- [Studio Library] (FP2.6 and higher): Developer Desktop -> Web Services
- Thomas Schneider: SAP Business ByDesign Studio -Application Development: Section External Web Services
Call services from UIs via Mashup
You can use mashup web services to consume an external web service, render the data in a data mashup component and include the mashup component in a UI (SAP UI that is prepared for extensibility or custom UI). Write back to the host UI is possible (SAP UI that is prepared for write-back or custom UI)
Availability: FP2.6 and higher
Transfer protocol: HTTP or HTTPS, SOAP, REST, or RSS/ATOM
Authentification: None, user/password, user certificates, API keys
Scope
- Request and response data type must be simple structures or lists
- Write back is available for a simple structure
Prerequiste: For integration into SAP UIs, SAP must prepare the UI with suitable outports and inports
Usage: User-to-system communication (ByD/SoD UI to external web service)
Development process overview
- In the studio (as of FP3.5) or in the Web Service Authoring view in the Application and User Management work center, define a REST Mashup Web Service (import the external web service definition (WSDL, REST or RSS/Atom URL) and extract/configure the parameters and authentification method)
- In the studio (as of FP3.5) or in the Mashup Authoring view in the Application and User Management work center, define a data mashup that invokes the web service and renders the output
- In the UI designer (extensibility explorer) add the mashup to the screen and configure the port binding
Documentation:
- [Studio Library] (FP2.6 and higher): Developer Desktop -> Mashups
- Thomas Schneider: SAP Business ByDesign Studio -Application Development Section Adding Mashups to User Interfaces
Custom controls (Silverlight)
You can implement a custom control (in Silverlight) and use Silverlight features for sending/receiving data
Availability: FP2.6
Transfer protocol: APIs (see documentation)
Scope: Launch a native Silverlight component from within the ByD/SoD UI
Usage: User to local system communication
Development process overview:
- In the studio create an embedded UI component (EC) as a “wrapper” for the Silverlight component
- Develop your Silverlight component
- Upload your Silverlight component into the studio and develop the binding
- Integrate the EC into a ByD/SoD UI
Documentation: [Studio Library] (FP2.6 and higher): Developer Desktop -> External Web Service Integration
Call Web Services (SOAP) from Custom Code (BO Integration)
You can call SOAP web services from custom code, for example in business object events and actions.
Availability: FP4.0 and higher
Transfer protocol: HTTP or HTTPS, SOAP
Authentification: None, user/password, user certificates
Scope
- Invocation of SOAP services from business partners (B2B scenarios) or external applications (A2A scenarios)
- Can be integrated in custom BO and BO extensions for SAP BOs (if the SAP BO is extensible)
Usage: System-to-system communication (B2B and A2A scenarios)
Development process overview
- In the studio (as of FP4.0), define an External Web Service Integration, import the external web service definition (WSDL) and activate the project item
- Implement the web service call in your script coding
- In the studio, define a Communication Scenario and select the required web service operations
- In the Application and User Management, Communication Arrangement view, create a new communication arrangement for the new communication scenario, configure the web service endpoint and logon credentials .
Documentation: [Studio Library] (FP4.0 and higher): Developer Desktop -> External Web Service Integration
Example:
BO Definition:
businessobject <BOname> raises WebServiceCoreError, WebServiceContentError {
message WebServiceCoreError text "Error occured in web service call in communication scenario &1" : LANGUAGEINDEPENDENT_LONG_Name;
message WebServiceContentError text "&1" : LANGUAGEINDEPENDENT_LONG_Name;Script code:
var request : Library::<WSID>.<Operation>.Request; // request structure
var response : Library::<WSID>.<Operation>.Response;// response structure
var scenario = "DemoCS"; // Scenario name
// fill the request
request. <...>
// execute the web service
response = Library::<WSID>.<Operation>(request, "", scenario);
// error handling
// no info at all
if (response.IsInitial()) {
raise WebServiceCoreError.Create("E", scenario);
}
// fault messages
var faultItems = response.CommunicationFault.Item;
var severity;
if (faultItems.Count() > 0) {
raise WebServiceCoreError.Create("E", scenario);
// do not send the complete error stack to the user. Assumption: last message is the most important on.
raise WebServiceContentError.Create("E", faultItems.GetLast().Note) ;
}
// evaluate the response
response. <...>Call Web Services (REST) from Custom Code (BO Integration)
You can call REST web services from custom code, for example in business object events and actions.
Availability: FP4.0 and higher
Transfer protocol: HTTP or HTTPS, REST
Authentification: None, user/password, user certificates
Scope
- Invocation of REST services from external applications (A2A scenarios)
- Can be integrated in custom BO and BO extensions for SAP BOs (if the SAP BO is extensible)
Usage: System-to-system communication (A2A scenarios)
Development process overview
- In the studio (as of FP4.0) or in the Application and User Management, Mashup Web Services UI, create a REST mashup Web service in your solution. Choose “Simulate” in the Mashup Web Services view to test it.
- Create a script file for your business object, for example, an action. Define the business logic to call the REST mashup Web service (see example below).
Documentation: [Studio Library] (FP4.0 and higher): Developer Desktop -> Mashups -> Tasks -> Defining the Business Logic to Call a REST Mashup Web Service
Example (script code):
import ABSL;
var serviceID :String;
var parameter : NameAndValue;
var parameters : collectionof NameAndValue;
serviceID = "PW00001";
parameter.Name = "keywords";
parameter.Value = "Rome";
parameters.Add(parameter);
var result = WebServiceUtilities.ExecuteWebService(serviceID, parameters);
var content = result.ResponseContent;
var returnCode = result.ReturnCode;Formatted Input/Output (Print, Fax, Mail)
Output management comprises all activities related to the output of documents in print, e-mail, or fax format. Form-based documents can be output on an ad hoc basis or as an integrated part of a business process.
Ad hoc output is generated when a user previews a document in Adobe Reader and either prints a paper copy or saves an electronic copy of the document in portable document format (PDF). This type of output does not require any configuration and can take place at any time.
Process-integrated output means that the output of a document is triggered and performed by the system as part of a business process. For example, a purchase order is created by an employee and sent to his or her manager for approval. On approval by the manager, the document is sent automatically to the output channel defined in the output settings of the document. This could be print, e-mail, or fax. Default output settings and output channel and form template rules can be created by key users to define how a particular document is output by the system.
In the studio, only custom ad hoc output scenarios are supported.
ByD supports interactive forms scenarios. Support for custom interactive forms scenario is not available.
Upload from File Share
In ByD/SoD key users can use can XML file to import third-party data from other systems into a business object. You can develop file input scenarios for SAP and custom business objects. Development of a download into a file share scenario is not supported in the studio.
Availability: FP2.6 and higher
Scope and Usage: Upload data into a business object
Development process overview
- In the studio select a business object and define a file upload scenario
- Activate the scenario. A file share is created that you can use to store the files to be uploaded.
- Download the generated WSDL and use it for example in Excel to define the file format
- In the Application and User Management work center, define an upload job (on time or recurring job)
Documentation: [Studio Library] (FP2.6 and higher): Developer Desktop -> Service Integration -> Tasks -> Create XML File Input.
Send/Receive Unformatted Mails via Mail Server
E-mails, fax documents activities are represented by the following business objects:
- EMailActivity: is used to record e-mails as business relevant interactions undertaken between employees on behalf of their enterprise, and its business partners. This business object enables users to track incoming e-mails, as well as outgoing e-mails.
- FaxActivity: is used to record sent or received faxes as business relevant interactions undertaken between employees on behalf of their enterprise, and its business partners. This business object allows the tracking of incoming faxes from business partners, as well as of internally generated, outgoing faxes.
EMailActivity and FaxActivity are released in the public solution model and can be used in custom applications.
The business object Social Media Activity records an interaction undertaken between an employee on behalf of the enterprise and its customer, communicated via social media channels. The Social Media Activity business object is not released (yet).
Availability: FP2.6 and higher
Scope and Usage: Send e-mails or fax documents, access sent or received e-mails
Prerequisite: E-mail and fax has to be set up in the ByD/SoD tenant
Development process overview
- Implement the access to the EMailActivity and FaxActivity in your script coding
Documentation:
- [PSM Documentation] or [Repository Explorer]: EMailActivity, FaxActivity (includes demo scripts for sending/reading EMailActivity, FaxActivity)
- [ByD/SoD Library]: Key User Administration -> Application and User Management -> Input and Output Management -> E-Mail and Fax Queues View -> Business Background -> Configuration: E-Mail and Fax Settings
Hi Thomas,
thanks for this great overview.
I would like to add the feature of Code snippet for HTML Mashups for chapter “call services from UIs via Mashup” (FP35 onwards). Within the html code snippet multiple prio in ByD defined REST Mashup Web Service can be consumed.
Regards,
Ralf
Hi Thomas,
Thanks a lot for this clarification and intro of the new FP4.0 platform features.
Look forward to test the new capabilities myself within the next weeks.
Regards,
Sven
Hi,
I added the section “Call Web Services (REST) from Custom Code”.
Regards,
Thomas
.
Hi there,
Today I was using the “URL launcher” as described above for accessing ByD Customer Quotes. That’s really a great feature. You’re able to launch almost any ByD UI from outside by putting together a simple https link. Wow!! I just struggled a bit with the UUIDs of the Quotes – but came to a solution! Please note that there’s (at least to my understanding) only one place in the solution where you get the UUID of your objects. Therefore you have to navigate to Business Analytics, select Data Sources. At the end I opened the data source “Sales Quote Headers” and brought UUIDs up by showing the “Node IDs”.
Regards,
Sven
Hi,
that’s a good point Sven, thank you. But I would appreciate more user friendly inports without UUIDs…it would make it easier to create integration on key user level.
Andreas
Hi Sven,
sorry for the late reply, but better late than never. You can also lauch the UI with the ID, for example:
https://<host_address>/sap/byd/nav?bo_ns=http%3A%2F%2Fsap.com%2Fxi%2FAP%2FCRM%2FGlobal&bo=SalesOrder&node=Root&operation=Open&object_key=252&key_type=APC_S_BTD_ID
You have to specify key_type=APC_S_BTD_ID. This works for BO which have an ID of type BusinessTransactionDocumentID (BTD ID) as alternative key. For other objects this may be a bit more tricky, for example if the alt key is structured. So I would recommend: if you are creating the URL in the system itself (for example to send them via e-mail), then I woudl recommend to use the UUID as key because each business object has an UUID as alt key. If you create the URL in an external system, then you can use the BTD ID as described.
Best regards,
Thomas
.
Hello,
your solution works for me too. But i also want to open a Customer, but i can’t find the bo for customers. What do i have the set for SalesOrder in your example to open a customer?
Best Regard,
Chris
XMLfile upload is not good enough at this moment, because it’s only support root level upload, not support hierarchy structure upload
OData mashup service seems to be removed from FP4.0
Hi Fred,
true. Dhowing the “OData service” option in the Mashup Web Services view was rather an incident. They never were officially rolled out. I have tested a couple of OData services with mashups, and they can be used with the “REST service” option because there is a large overlap. Please see alsoIntegration of SAP OnDemand Products with Business Suite via REST/OData Services.
thanks, Thomas!
Now I know the detail thing
Hi Thomas,
it’s great if you can give more detail things related “Send/Receive Unformatted Mails via Mail Server”
Kind Regards.
Fred
Hi Fred,
please see the PSM documentation of the EMailActivity BO. As of 4.0 you can find the PSM documentation in the studio under View -> Repository Explorer. Search for EMailActivity and you will see a coding example of how to create an e-mail.
As of 1302, we will provide a second way to send an e-mail from a custom BO. In the context menu of a BO project item, you will find the entry Enable Notification Rules. If you complete the wizard, the custom BO is enabled for notifications. This means that a key user can define notifications (and e-mail) that are posted by the BO. Please see the details of this feature in the documentation for 1302 (“what’s new”).
Regards,
Thomas
Hi Thomas,
you means if we create a email instance in the BO EMailActivity, a email will be sent from ByD automatically?
the email address is determined by Organizer party and Attendee party maste data?
thank!
kind Regards.
Yes. Of course, you need to call the the Send() action!
Thomas,
I propose that Line 19: of the code above be changed from:
to:
The datatype of the Mesage defined in line 3 is LANGUAGEINDEPENDENT_LONG_Name. This datatype has a maximum of 40 characters, and the faultItems.GetLast().Note has a maximum length of 200 characters. As is stated in the documentation, making an assignment like that may cause the script to abruptly quit without warning.
Also, to assist the developer during development, one might want to insert the following after line 19:
var lastFault = faultItems.GetLast();
Trace.Error(“wsError:CategoryCode”, lastFault.CategoryCode.content);
Trace.Error(“wsError:Note”, lastFault.Note);
Trace.Error(“wsError:ReferenceMessageElementName”, lastFault.ReferenceMessageElementName);
Trace.Error(“wsError:SeverityCode”, lastFault.SeverityCode);
Trace.Error(“wsError:TypeID”, lastFault.TypeID);
Trace.Error(“wsError:WebURI”, lastFault.WebURI);
Best,
Greg
Hi Greg,
makes sense!
Best regards,
Thomas
.
Hi Thomas,
first of all thanks for the great overview on the capabilities of external webservice integration.
Yet, there are some pain points where we´ll need deeper understanding.
For testing and learning reasons I am trying to consume the webservice of another ByDesign tenant (e.g. I´m importing the WSDL-file of ManageCustomerIn). I´d like to create customers in that system. It would be interesting to have more details on that approach. Currently, it is a lot of trial and error. We also have problems with the communication arrangements (Error accessing service; Service Ping ERROR: Error when calling SOAP Runtime functions: SRT: Processing error in Internet Communication Framework: (“ICF Error when receiving the response: ICM_HTTP_TIMEOUT”) ()”).
For the coming projects this year we´ll have to use a lot of integration capabilities of SAP Business ByDesign. For example we want to build an integration to Lotus Notes Domino
and to other WebService-Providers (AdressCheck).
Unfortunately, documentations on external webservice integrations are really rare. It could be great if SAP could provide more documents/descriptions as they are also great tutorials on some other technical topics done by SAP.
Best Regards,
Rufat
Hi Thomas,
I’m playing with the “Launch UI via URL” option in this context:
An user is checking a Quote in ByD and would like to check the details of the Opportunity in Cloud for Customer. I have two “basic questions”:
I’ve checked how to access to that information via a Mashup and I’ve added this Mashup in ByD. I’ve hardcoded the opportunity number to a concrete value:
https://myXXXXX.crm.ondemand.com/sap/byd/nav?bo_ns=http%3A%2F%2Fsap.com%2Fxi%2FAP%2FCRM%2FGlobal&bo=Opportunity&node=Root&operation=Open&object_key=44571&key_type=APC_S_BTD_ID
It has worked well because the user I’m using in ByD exists in CoD and has access to that opportunity. But I have a doubt:
Could we pass user name and pwd as parameters in that URL without having to use the SDK?. I’ve tried both to use:
https://username:password@my…. and https://my…&user=XXXX&password=YYY
but it has not worked.
Apart from that I don’t know if it’s possible to use a variable to populate the Opportunity number (&object_key) instead of using a fix value (without using the SDK)?
Thanks. Cheers. Oscar.
Hi Oscar,
unfortunately it is not supported to explicitely pass user & pwd in a URL. Our security people do not permit this feature.
Best regards,
Thomas
.
Great overview! Thanks!
Miguel
Hello Thomas,
Thanks for sharing the details here, but i have issues using it for 1411 release.
I have created URL in both the ways
1. https://myXXXXXX.crm.ondemand.com/sap/byd/nav?bo_ns=http%3A%2F%2Fsap.com%2Fxi%2FAP%2FCRM%2FGlobal&bo=Opportunity&node=Root&operation=Open&object_key=<UUID>&key_type=APC_V_UUID
For the link specified in point 1 it open the opportunity view as blank and doesnt display any data.
2. https://myXXXXXX.crm.ondemand.com/sap/byd/nav?bo=COD_OPPORTUNITY_THINGTYPE&nav_mode=TI¶m.Key=<UUID>
For the link specified in point 2 it creates a new opportunity instead of opening the opportunity for the specific UUID.
Can you please suggest how this can be resolved for us ?
Best Regards,
Sumukh Kapoor.
Hi Sumukht,
can you please open an incident for this issue with the real data. It is hard to do an analysis w/o data and system access here. I am not aware that something changed in the navigation in 1411, so the developers should have a look into it.
It would be great if you would post a solution here when the incident is solved
Best, Thomas
.
Hello Sumukh Kapoor,
I just tried both URL formats in my 1411 tenant and they both work fine.
As Thomas suggests, you should probably submit a ticket to help resolve the issue.
Regards,
Greg
hello Thomas / Greg,
the issue is resolved and the second link works, the opportunity was deleted for the UUID in use hence was the issue.
Best Regards,
Sumukh Kapoor.
Thanks for updating us!
Best regards, Thomas
Hi Thomas,
Thanks for the great blog on BydUI Architecture.
I have a question specific to Launch URLs for TI Screens,
currently from the blog above we can launch C4C TI URLs for display i.e. Navigate to an existing Opportunity/Quote/Account by giving the corresponding BO name and Nav Mode type as TI.
However, if we want to navigate to C4C BO QuickCreate Screen, I edited the URL to display the following:-
https://<hostname>.<domain>/sap/byd/nav?bo=COD_OPPORTUNITY_THINGTYPE&nav_mode=QC
But, the navigation did not take place.
I would like to understand, how do we understand/identify which parameters can be passed via to URL for a specific operation like –
1) Creation of Opportunity – Launch a QC
2) Creation of an Opportunity with Account Details in reference – Launch a QC with Account Details pre-populated.
Would appreciate your inputs on this.
Thanks.
Dedeepya
Hi Thomas,
Scope
Is it still not possible fro write operation of SAP BO or custom BO in ByD with REST?
Best Regards
Fred
Tushank Thakur