DataFlow : Hub and Spoke

DataFlow enables an organization to define a simple landscape of hub-and-spoke systems so that you have a single hub system that controls all the workflow and access and several spoke systems that are managed by the system.

Configuration tree :  /PROMENTA/DATAFLOW_HAS  (Override this tree)

Connectivity between the hub and spokes is facilitated by SAP RFC connections. End-users normally require an SAP user in each system that they will connect to.

Prerequisites

Determine all your systems, landscapes and groups as below :

Landscapes : the collection of SAP systems that make up an SAP “landscape” of Development, Quality and Production (and additional systems). For example – you may have one landscape for Domestic business and another separate landscape for the International business.

Systems : Individual SAP systems where each system belongs to a specific landscape

For example : DE1, QA1,PR1 make up Domestic systems, DE2,QA2,PR2 make up the International systems

Hub landscape : You will define one set of systems to be the Hub. 

Spoke landscapes : You will define all other landscapes as spoke landscapes. These systems receive connections from the hub but all workflow and requests are managed in the hub.

Continuing the example – you may define the Domestic landscape to be the hub landscape. This means that DE1 is the hub for all development systems, QA1 is the hub for all Quality systems etc

Configuration

Create an override of the core tree /PROMENTA/DATAFLOW_HAS

Each SAP system must be created under the “Systems” node.

Each system is assigned a role (Hub or Spoke), a group (DEV systems, QA systems)  and a landscape (International, Domestic etc)

The decision tree is defined in the development systems (of the HUB) and migrated through to Production via SAP transports.

System Parameters

SYSID  =  <SAP System ID>  

MANDT = <SAP client>  

GROUP = <the group for the server – eg DEV if it is a dev server, QA if it is a QA server etc> 

ROLES = <Roles of this server. Possible values are HUB, SPOKE. A server can be both hub and spoke>

RFC_READ = <the RFC destination used to read data from the hub>

RFC_UPD = <the RFC destination used to update the data from the hub>

FLDCGF = <landscape – the identifier for the landscape. This will link to the dataflow configuration for the processes>

Process Flow

The way the system determines which systems to list in the selection box and which are the hub or spoke is detailed below.

User accesses a dataflow process (eg Vendor request)

The process tree is read and the processes are extracted (eg Vendor create, Vendor change etc). The process tree will also define which processes apply to which landscape (eg Vendor creation-Domestic, Vendor creation-International etc). The linkage to landscape is done using the parameter HAS_SYSTEM of the DataFlow header)

The current system is then read and looked up the /PROMENTA/DATAFLOW_HAS tree. This defines then defines which landscape is logged into and which group (ie is this the DEV systems , the QA systems etc)

A new list of hub/spoke SAP systems is then derived using the current system group (DEV, QA etc)

The list of available and relevant systems that can be used are then shown to the user

 

 

Scroll to Top