## 2. Creating and publishing an OData UI service based on BO interface or CDS View
##  Note
## Prerequisites :
- Business Catalog SAP\_A4C\_BC\_DEV\_PC is assigned to your user, which allows you to create and publish OData UI services. See Business Catalogs for Development Tasks.
## Steps
<!-- image -->
1. As developer user, create an OData UI Service based on the business object interface or CDS view suitable for UI consumption:
1. In SAP Business Application Studio and Microsoft Visual Studio Code you can use the UI Service Generator to generate an OData UI Service. See UI Service Generation.
##  Note
When using the OData UI service generator in SAP Business Application Studio, communication with the ABAP environment is established via destinations (see Creating a Destination to the ABAP System for SAP Business Application Studio or Creating a Destination for CrossSubaccount Communication). As part of this destination for backend connectivity, you must define an additional property, HTML5.Timeout . This value represents the maximum time to wait for a response (in milliseconds) from the destination (refer to Additional Properties of a Destination). Given the complexity and time-consuming nature of creating an OData UI service,
it is recommended to configure a destination timeout of at least 300000 milliseconds to avoid potential timeouts.
2. In SAP Business Application Studio, utilize the SAP system service provider as part of the Service Center view to explore business objects or CDS views and their properties, then generate an OData UI service from an ABAP business object interface or CDS view. For more details, refer to Explore SAP System Business Objects and ABAP CDS Views. While creating an OData UI service from the Service Center view, the UI Service Generator will be opened for the actual generation of the service.
##  Note
If the underlying business object interface/CDS view does not support UI consumption, a corresponding warning will appear before adding an OData UI service from the SAP system service provider to the project.
This method currently only supports the creation based on SAP-provided business object interfaces and CDS views.
3. OData UI services can be created in ABAP development tools for Eclipse either manually by creating an OData UI service binding or by utilizing the Generate ABAP Repository Objects wizard. See Creating Service Binding and Generating ABAP Repository Objects.
##  Note
If the underlying business object interface/CDS view is not suitable for UI consumption, the Generate ABAP Repository Objects wizard will display a relevant warning.
2. When using the UI Service Generator in Business Application Studio or Visual Studio Code (directly or opened via the Service Center view), the service binding for the OData UI service is automatically published. This allows you to continue with the SAP Fiori application implementation without additional steps.
While creating the OData UI service in ABAP development tools for Eclipse, you have to publish the corresponding service binding so it will be available in the service catalog. For more information, see Using Service Binding Editor for OData V4 Service .
## Next Step
Develop an SAP Fiori Application UI based on the OData UI Service. See Develop an SAP Fiori Application UI and Deploy it to ABAP Using SAP Business Application Studio and Develop an SAP Fiori Application UI and Deploy it to ABAP Using Visual Studio Code.
## Related Information
Generate your own custom UI Service based on a Business Object Interface
Video: Create an SAP Fiori Application Based on an ABAP Business Object (BO) with SAP Build