Integrating across Environments

Objective

After completing this lesson, you will be able to create a connection with the model entity in another environment.

The Model Reference Feature

In this lesson, we explore the Model Reference feature within the SAP environment. This powerful functionality enables you to integrate, connect, and consume data from model entities that exist in other environments within the same tenant. Understanding how to use Model References is crucial for creating a seamless and interconnected data ecosystem within your organization.

Flowchart of data management process from environment setup to model entity reader integration, showing optional fields, connections, functions, and various stages including inbound and outbound processes and calculations.

Key Functionalities of Model Reference

Integration Across Environments

The Model Reference feature facilitates the integration of data across different environments within the same tenant:

Cross-Environment Connectivity: Effortlessly connect to model entities across multiple environments, enabling a unified view of your data landscape.
Data Consumption: Consume data from these interconnected models as if they were part of your current environment.

API State Requirement

To ensure seamless integration and consumption of model data, certain prerequisites must be met:

Active API State: The environment from which model entities are being consumed must have at least one model entity with its API State set to Active. This activation allows the model entity to be accessible for external consumption.

Inbound - Cross Environment Integration

In order to establish connection to another environment using model reference, in manage connection application create a connection using Environment as connection target type.

An image showing a user interface for creating a connection with options for Environment and Connection Target Type, along with a description of the Manage Connections application that provides access to the list of available connections in the tenant and allows integration of the environment with another environment's model entities within the same tenant.

Environment: The environment where the connection is created. Choosing the linked environment ID directs you to the environment's General Information screen.
Connection*: Composed of up to 10 characters of capital letters and numbers with no space in between, such as "CONNENVME".
Description*: Composed of text with up to 200 characters that often provides connection information, such as "Connection to ENVME Environment".
Connection Target Type: A read-only field providing connection target type information.
Model Filter: Used to filter out the models coming from the target to the ones which match the expression (pattern). Supports JavaScript regular expressions.
Target Environment: Choose the environment where you want to consume the model entity from.

It is important that the selected environment has a model entity with API State = "Active". For more information about setting the API state of a function to "Active".

An image of a user interface labeled UMREF01, showing sections for General Information and Models, with fields for Environment, Description, Model Filter, and Target Environment. Instructions and options to create or discard a draft are also visible.

After creating a connection, model entities available in target environment will be added.

An image of a user interface displaying a table of models with columns for Function, Sync Model, Sync Connection, and Original Name. The table lists four models, with options to Edit, Delete, Sync Connection, and Sync Models at the top.

In sync model column, we can select those model entities which we want to consume.

An image of a user interface showing a table of models with columns for Function, Sync Model, Sync Connection, and Original Name. The model Z_PA_DOCUMENTS is selected in the Sync Model column, and instructions to select models for import are provided at the bottom.

After that, mapping of the fields need to be performed. When fields mapping is done, click on apply and then on Sync Model to actually pull in the Model Entity from Target Environment into your Source Environment.

An image of a user interface displaying a table of model fields with columns for Environment Field, Original Name, Class, and Type. Eight model fields are listed with options to Edit, Delete, Sync Connection, and Sync Models at the top, and an Apply button at the bottom.

After syncing the models, reactivate the environment and then check the data that is pulled in the system.

An image of a table displaying financial data with columns for ID, Company1, Description, Year, Tax Free Income, Capital Gain, Dividend, and Currency. Three entries are listed with information for Sunshine France, Sunshine Holding, and Sunshine Germany for the year 2023.

Universal Model enables user to easily achieve cross environment integration. For that purpose, specific funcion has been created. Watch step-by-step guidance on how to pull-in the data from another environment in the same tenant.

Continue to quiz