Skip to main content

Overview

Intro​

UBC
UBC [Unified Backend Connector]

In the complex ecosystem of enterprise solutions, SAP stands out as a benchmark of reliability and efficiency. Leveraging this powerhouse, Industrious Consulting proudly presents UBC – the SAP-Tech Based Unified Bridge for Cross-System Workflows.

Harnessing the robustness of SAP technology, UBC seamlessly integrates varied digital platforms into a singular cohesive workflow. This doesn’t just ensure system-to-system collaboration, but it optimizes processes to resonate with the SAP standards of excellence. UBC represents the confluence of SAP's technical prowess with our vision of a seamlessly integrated digital environment.

The brilliance of UBC is its ability to translate the complexities of diverse systems into an intuitive, SAP-tech powered operational flow. This ensures that businesses can maintain the reliability and scalability they expect from SAP, while also benefiting from streamlined, cross-system workflows.

Step into a realm of enhanced efficiency, where SAP's technological excellence merges with the transformative capabilities of UBC:

  • UBC is an SAP certified "out of the box solution" to interface dedicated processes with SAP systems offering out-of-the-box integrations
  • Drives and enables digitalization of processes (also mobile access to critical or "fast moving" processes)
  • Automatization of workflows - easily built and self-service possibilities
  • Business users get direct access and insights to all relevant data outside and inside the chain directly within their well-known SAP apps/transactions
  • Improve visibility of your processes using the powerful monitoring and workflow techniques
  • Easily configured or enhanced mapping of data to ERP processes and back
  • First class developer tools for common requirements like IDOC and JSON mapping using well-known ABAP patterns
  • Full access to all SAP Standard Business Objects and Custom Objects
  • UBC leaves a "near-no" footprint in your SAP systems and needs no additional architectural components.

Component Architecture​

UBC is organized by different components, but always delivered as a whole product.

UBC

You will find the parts of the product documentation in its sections in the sidebar on the left.

System setup​

Each dedicated use case has its own setup routines, the following can be considered as common:

  • Execute the setup tasklist using transaction /UBC/SETUP_BASIC
  • The task list creates bgRFC destinations, activates SICF services, checks workflow-configuration, activates BC-Set, etc. See step documentation for further details. Consider having enough authorization! We have template roles ready, reach out to us if needed!

Authorization​

There are a few template roles ready, reach out to us if needed. The standard delivery does not contain the template roles, but they can be some kind of "kick start".

UBC authorization objects​

  • /UBC/RESTPto restrict for REST-service usage within UBC.rest (enabled parameter /UBC/AUTH_CHECK)
  • /UBC/IO_IF to restrict for interface usage within UBC.io, available fields are activity and interface.
  • /UBC/IO_CC to restrict the display of messages in UBC.io for a specific company code. Please note that the company code has to be linked for the proxy. Defaults in template roles enable to use all the conUBC interfaces without restricting for organization/company.

Template roles​

  • /UBC/SERVICE enables the usage of all exposed interfaces from UBC.rest which can also be seen in Swagger UI. Thus, this is ideal for a service and/or test user. Please note, that authorization for a specific REST service is only checked if parameter /UBC/AUTH_CHECK was set for SICF node and thus, the role is not needed if the parameter is not set.
  • /UBC/MONITOR is intended for users who need to monitor /UBC/ tasks. Read access to view in-/outbound messages in standard interfaces of UBC.bo, including payload. This role also includes SAP standard roles SAP_BC_BMT_WFM_CONTROLLER and SAP_BC_SRV_USER to be able to access SAP Standard workflow protocols within UBC.flow. It is also possible to restrict by a company code in the IO monitor. The company code has to be linked to a proxy on its setup.
  • /UBC/ADMINSTRATOR includes roles /UBC/MONITOR, /UBC/SERVICE and adds authorization to research and adapt any customizing activity within UBC. Also, this role includes SAP standard roles SAP_BC_BMT_WFM_ADMIN and SAP_BC_SRV_EDI_ADMIN which enables to use standard functionalities, e.g., for IDOC monitoring which goes through UBC.idoc layer. This role extends the pure monitoring focused role /UBC/MONITOR with some standard administration tasks. It is mandatory for the setup of UBC or any new business object within UBC (authorization for customizing transactions). This should be assigned to users who require full administration authorization and capabilities within UBC.
  • /UBC/DEVELOPER includes /UBC/ADMINISTRATOR and extends with developer roles to use developer transaction, debugging, etc. Intended to use for a UBC developer. Includes SAP standard roles like SAP_BC_BMT_WFM_DEVELOPER, SAP_BC_DWB_ABAPDEVELOPER or SAP_BC_SRV_EDI_DEVELOPER.

Data Archiving​

Every component with persistence (BO, IO, FLOW) has its own Data Archiving mechanism and is described in the relevant sections.