Skip to main content

Introduction

Kyra Stream consolidates 20 years of experience in planning and business processes into a modern process solution. With Kyra Stream, customers and consultants can map the individual requirements arising in the planning process as a continuous process and execute them in various ways.

The Idea Behind Kyra Stream​

The idea for Kyra Stream arose from the realization that every customer of Kern AG has an individual planning process, which can be solved precisely through the flexibility of Allevo. However, for specific issues, so-called customer-specific developments are often necessary for problem-solving. While these are identical for some customers, they differ again in detail. The result is a product consisting of individual building blocks. These are standardized but can be combined in such a way that customer processes can be individually formulated and mapped.

The Language of Kyra Stream​

With every letter we combine here into words and ultimately into this text, a blueprint develops for what characterizes our new product Kyra Stream. We have, so to speak, broken down our experience story "20 Years of Allevo" into letters and formed precisely fitting words from them. These language elements are combined into sentences with clear grammar. This allows many new stories to be told.

"Letters, words and sentences, grammar and stories" are metaphors for the ability to use Kyra Stream to form your desired business processes from data, business transactions, and transactions. The ability to track the process flow step-by-step and automate execution is very valuable.

This blueprint can also be found, for example, in the well-known Lego building blocks. The typical Lego brick consists of studs, the actual body, and the hollow interior, which, in conjunction with the studs of the next brick, forms a stable unit and can be extended as desired. Even if the construction appears at first glance to be a reduction in complexity, it opens up unforeseen possibilities.

The Grammar of Kyra Stream​

Kyra Stream was developed from the Kern Method. In the Kern Method, the three-beat Sender - Activity - Receiver forms the basic framework for sketching any processes. In Kyra Stream, this three-beat is found again in a different form. Kyra Stream speaks in Source - Transformation - Target:

  • Source – Which data source do I need?
  • Transformation – What do I need to change in the data?
  • Target – In which data target should the data be saved or posted?

A clear example is importing data. An Excel file contains a table whose data is to be written to an Allevo satellite or posted to an SAP table via an SAP BAPI.

  • Source – The table in the Excel file
  • Transformation – The fields of the Source must be mapped to the corresponding fields of the Target
  • Target – The satellite

While considering the example, the first Kyra Stream Process and its objects have already been sketched:

  • Source Type: XLSX
  • Transformation Type: MAP_FIELDS
  • Target Type: SAT

Thus, almost incidentally, the structure for a Kyra Stream Process has emerged from the explanation.

About This Manual​

In this manual, we introduce you to the definitions and the various Source Types, Transformation Types, and Target Types of Kyra Stream. We present ideas and examples with which we aim to inspire and motivate you to build your individual process model. Use Kyra Stream as your new toolbox with building blocks, with the help of which you can assemble new processes step by step. In Kyra Stream, the building blocks are called "Transformation Types" and each process step is an Action. A process is therefore a group of Actions.

If you require another building block, i.e., a new Transformation Type, please contact us directly. We will analyze your requirement, show you the solution, or develop a Transformation Type that precisely fits your task.

Kyra Stream is clearly structured. Kyra Stream has easily understandable building blocks. With a little practice, you can systematically and easily assemble your processes.

Practice makes perfect, and then "Kyra Streaming" is really fun because you quickly achieve reliable results that are very effective in practice. This manual familiarizes the reader with the definitions and various Source Types, Transformation Types, and Target Types of Kyra Stream. While it can provide ideas and examples, every solution derived from it will almost always be customer-specific.

Should it happen that a required Type does not exist, it can also be specially developed and integrated into Kyra Stream in the customer system.

Use Cases​

Before every finished solution, there is an idea, and just as a Lego model first arises in thought and then takes shape from the building blocks, Kyra Stream also thrives on the ideas of our customers.

Some examples for the application of Kyra Stream in an Allevo context:

  • Import a CSV file into a satellite
  • Read out the SAP Depreciation Simulation as an ALV and save it in a satellite for expert planning
  • Consolidate expert planning data from several satellites and post it in SAP
  • Read planning data from a version in SAP, multiply it by a factor per Cost Element from a table, and save it in a new version

Some examples for the application of Kyra Stream without an Allevo context:

  • Read prices from Purchasing Info Records and save them in a SunTable for processing; after processing, save the new prices back in the Purchasing Info Records
  • Create multiple Cost Centers based on a table
  • Post statistical key figures in Actuals from a CSV file
  • Read General Ledger line items from an ALV and revalue them for analysis purposes based on a table with exchange rates