DOCSEARCHbyAlgolia
Submit Docs

Kern Wiki Documentation

website·Indexed 30 days ago

https://kern-wiki.netlify.app/

Technical documentation for data targeting and transformation processes, featuring guides on SAP server file handling (XLSX, CSV), Universal Tables, and specific SAP value targets such as ACOSP, ACOSS, and AFAGLFLEXT. Includes instructions for master data management (Cost Center, Profit Center, Internal Order) and data transformation operations like enrichment, filtering, and column-based copying.

Tokens
14.2K
Snippets
34
Records
144
Agent score
70%

What's inside Kern Wiki

  1. Overview of Table Data Enrichment in Kyra Stream

    The Table Data Enrichment function allows for the automatic mapping of fields from a Source table to a Target. It uses key comparisons to retrieve values from any table and transfer them to the Target. A common use case is transferring Cost Center Texts to a Target based on the Cost Center Number and the logon language.

  2. Overview of the Expand transformation

    The Expand transformation multiplies two tables (Source and Intermediate). For example, if the Source table has 10 rows and the Intermediate table has 5 rows, 50 rows are generated in the Target table. This is typically used for valuation tasks, such as multiplying sales quantities (Source) by various production cost components (Intermediate) where rows are matched based on a common key (e.g., material number).

  3. Understand the purpose of Allevo-own totals record tables

    Allevo-own totals record tables are used to store planning data for Allevo objects and temporary data for SAP objects that cannot be stored in original SAP tables (such as legacy data transfer or Allevo FID data). These tables allow users to record planning data temporarily before transferring it into SAP planning tables using specific selection criteria.

  4. Understand Universal Tables in Kyra Stream

    Universal Tables are virtual data sources in Kyra Stream that use an Entity-Attribute-Value (EAV) model. Unlike customer-specific Groundtables, they do not require creation via SAP transports (transaction SE11). Kyra Stream automatically converts EAV data into a conventional table format during process execution.

    Performance Considerations:

    • The conversion from EAV to conventional format incurs a performance cost.
    • In non-S/4HANA systems, Universal Tables should only be used for storing parameters, small data volumes, or sketching Groundtables.
    • In S/4HANA environments, performance should be verified during the implementation project for large data volumes.

  5. Use Satellite source type to determine quantity and value components

    In Allevo, the Satellite source type is used to determine quantity and value components for specific Cost Elements, Activity Types, or Key Figures through Detail Plans. This is typically used for specialized planning such as Cost Element Planning, Activity Type-Dependent Planning, Leasing and Investment Planning (including depreciation derivation), and Maintenance/Fleet Planning. Data retrieved via this source type can be processed further, such as for posting to SAP.

  6. Use SunTable for flexible data design in Allevo

    SunTable is a table type in Allevo that provides more flexible design options than Satellites. Unlike Satellites, SunTables have less dependency on standard CO Planning process parameters (such as Controlling Area, Planning Year, and Version) and do not have predefined keys. Because they lack predefined keys, any necessary data restriction must be implemented via advanced parameters.

  7. Manage Statistical Key Figures using the Master Data Statistical Key Figure Target Type

    The 'Master Data Statistical Key Figure' Target Type allows users to create new Statistical Key Figures or modify existing ones. During the creation process, only the fields explicitly provided are populated in the system; all other fields are left empty.

  8. Read Excel XLSX files stored on the SAP server

    When the source file to be read is stored directly on the SAP server, use the 'Excel XLSX File on the Server' source type. This functionality is similar to the standard 'Source Type XLSX' but specifically handles files residing on the server rather than local or external sources.

  9. Create and modify Internal Order Master Data

    Internal Orders can be created or modified using the source type. During the creation of a new Internal Order, only the fields explicitly provided are populated; all other fields remain empty. If the specific Order Type is configured for automatic number assignment, the system will automatically assign a new order number upon creation.

  10. Use FEEDBACK transformation for target object results

    The FEEDBACK transformation captures results returned by a Target Type after an Action (e.g., verifying if a Cost Center was successfully created) and saves that result into the Target. This is currently supported by all Target Types for the creation of CO master data.

  11. Extract financial accounting data using Balance Sheet Classic General Ledger

    The Balance Sheet Classic General Ledger source type allows for the extraction of financial accounting data from SAP systems that utilize the Classic General Ledger. Users must configure Object Selection parameters to define the scope of the data and TimeSet parameters to define the temporal and versioning constraints of the extraction.

  12. Capture action results using Feedback from the Target Object transformation

    The 'Feedback from the Target Object' transformation is used to process and store the result of an action (e.g., confirming if the creation of a Cost Center was successful) into the Target. This is possible if the Target Type provides this information. Currently, this functionality is supported by all Target Types used for the creation of CO master data.

    Configuration Requirements:

    • Action: Specify the Action whose Target Type contains the result to be read.
    • Field mapping: Map the source field from the Action to the target field where the result should be stored.