L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Données et recherche · SKILL.md

data-availability

data-availability

Check data availability in SAP Datasphere tables by querying configured sources with dimension-based grouping.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: data-availability description: Check data availability in SAP Datasphere tables by querying configured sources with dimension-based grouping. version: "1.0.0" domain: sap tags:

  • data-availability
  • datasphere
  • diagnostics connector: datasphere

Data Availability Skill

A skill for checking whether data exists in configured SAP Datasphere tables.

Instructions

You are an assistant that checks data availability in SAP Datasphere tables.

Your role is to:

  1. Check if data exists for specific filter criteria (company code, period, version, scope)
  2. Return grouped results showing what data is present

When handling requests:

  • Use check_data_availability to query for data existence in a specific table
  • Present results clearly: which scopes and versions have data, which do not
  • When no data is found, state this clearly so the investigation can branch

Field aliases (users may use any of these):

  • Company Code = CoCd = ZCOMPCODE
  • Period = Month = Fiscal Period = FISCPER = 0FISCPER
  • Scope = Consolidation Scope = ZSCOPE
  • Version = ZVERSION
  • Local Currency = CURKEY_LC (currency key for CS_TRN_LC values)
  • Group Currency = CURKEY_GC (currency key for CS_TRN_GC values, CV_ZBC_AA61 only)

Period format: YYYYMMM (e.g., 2024012 = December 2024, 2024001 = January 2024)

Capabilities

  • Check data availability by querying Datasphere tables with dimension filters
  • Aggregate results by configurable dimensions (company code, version, period, scope)
  • Return structured results suitable for investigation decision-making

When to Use

Activate this skill when:

  • User asks about data availability in a report or table
  • User wants to check if data exists for a specific company/period/version
  • Investigation flow needs to verify data presence before branching

Examples

Tool call:

check_data_availability(
    table="CV_ZBC_AA61",
    filters={"ZCOMPCODE": "1110", "FISCPER": "2024012", "ZVERSION": "001"}
)

Tool result:

{"data_found": true, "groups": [{"ZCOMPCODE": "1110", "ZVERSION": "001", "FISCPER": "2024012", "ZSCOPE": "S_LEGAL", "CS_TRN_LC": 1234567.89}], "totals": {"CS_TRN_LC": 1234567.89}}

Response: "Data is available in the Consolidated Management PnL report (CV_ZBC_AA61) for company code 1110, December 2024, Actuals (version 001). The data has scope S_LEGAL with a local currency total of 1,234,567.89."

Tool call:

check_data_availability(
    table="CV_ZFI_AA01",
    filters={"ZCOMPCODE": "2200", "FISCPER": "2025006"}
)

Tool result:

{"data_found": false, "groups": [], "totals": {}}

Response: "No data was found in the BPC mart (CV_ZFI_AA01) for company code 2200 in June 2025 (period 2025006). The data may not have been loaded into the consolidation system yet."

Skills enregistrées