plugins/sap-rpt1/skills/sap-rpt1/SKILL.md
SAP-RPT-1-OSS local tabular prediction workflows for FI/CO prototype datasets. Use when preparing SAP finance CSV exports for classification or regression experiments with source-verified setup, leakage checks, and governance review.
npx skillsauth add secondsky/sap-skills sap-rpt1Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use SAP-RPT-1-OSS for local, source-reviewed tabular prediction experiments on FI/CO CSV extracts. Keep this skill scoped to prototype and research workflows; do not present predictions as production finance, credit, audit, payment, or compliance decisions.
Use this skill when preparing or reviewing SAP finance tabular data for local SAP-RPT-1-OSS experiments, especially:
Do not use this skill as a hosted SAP-RPT API integration guide, production scoring service, SAP AI Core deployment guide, or live SAP extraction workflow.
references/data-governance.md before touching real finance data.py -3.11 or .venv\Scripts\python.exe; on macOS/Linux this might be python3.11 or .venv/bin/python.scripts/fico_data_prep.py --dry-run --input "<file.csv>" --target <column> to inspect schema and leakage risks.scripts/rpt1_oss_predict.py --dry-run --input "<file.csv>" --target <column> to review local SAP-RPT-1-OSS prerequisites.--encoding <encoding> or --delimiter ';' when enterprise CSV exports are not UTF-8 comma-delimited.Detailed v1 recipes live in references/fico-use-cases.md.
| Area | V1 depth | Typical target | First reference |
|------|----------|----------------|-----------------|
| FI-AR | Detailed | paid_late, days_late, default_flag | Payment default / late payment |
| FI-AP | Detailed | discount_lost, discount_amount_lost | Cash discount leakage |
| FI-GL | Detailed | manual_review_flag, reversal_flag, outlier_flag | Journal anomaly |
| CO/PS/CO-PA/FI | Starter only | Overrun, margin, cash, dispute, credit risk | Use-case matrix rows only |
Prefer source extracts already flattened to one row per prediction object, such as one invoice, one vendor invoice, one journal line, or one journal document. Rename technical SAP fields into semantic column names before inference; SAP-RPT-1-OSS uses column names and values as part of the tabular context.
Use S/4HANA starting points such as ACDOCA plus relevant master data and process extracts where available. Use ECC fallback tables only as starting points, not universal truth. Never assume table availability, field semantics, or release behavior without checking the target system.
Define the as-of date before selecting features. Exclude fields created or updated after that prediction point.
Common leakage examples:
Before using real FI/CO data, confirm business owner approval, legal/compliance approval, field minimization, masking of personal and bank-related data, time-based validation splits, documented target definitions, and human review. Use references/data-governance.md as the minimum checklist.
Do not use predictions as the sole basis for payment blocking, credit decisions, collections action, write-offs, audit conclusions, or control sign-off.
For Windows, macOS, Linux, and managed non-admin workstations, use references/enterprise-portability.md before suggesting setup or execution commands. Prefer user-writable virtual environments, approved cache locations, quoted paths, and explicit output locations.
references/source-review-2026-06-18.md: public source/model/product-page review and open upstream issue list.references/fico-use-cases.md: detailed FI-AR, FI-AP, and FI-GL recipes plus starter matrix rows.references/data-governance.md: minimum data governance and model-card checklist.references/enterprise-portability.md: Windows, macOS, Linux, non-admin, proxy/cache, and CSV export guidance.scripts/fico_data_prep.py: read-only CSV schema, target, and leakage inspection helper.scripts/rpt1_oss_predict.py: opt-in local inference wrapper for SAP-RPT-1-OSS.assets/*.csv: synthetic FI/CO sample datasets only.Treat upstream SAP-RPT-1-OSS issues as source-reviewed limitations, not fixed behavior. See references/source-review-2026-06-18.md for issue numbers and titles reviewed from SAP-samples/sap-rpt-1-oss.
Local inference can download gated model artifacts, populate local caches, require Hugging Face authentication, and require substantial memory. Commands bundled with this plugin must not run inference directly.
Sources reviewed: SAP-samples sap-rpt-1-oss, Hugging Face SAP/sap-rpt-1-oss, and the SAP product page for SAP-RPT.
Verification scope is public source/model/product-page review only. Live SAP tenant validation, live SAP system validation, hosted SAP-RPT API validation, local inference benchmark validation, and production finance workflow validation were not performed.
Product boundary:
tools
Use when automating SAP BW query inspection, InfoProvider metadata reads (characteristics, key figures), metadata-verified specification review, unsaved draft preparation, or human-confirmed query draft population through Eclipse or HANA Studio with BW Modeling Tools.
tools
Use when an agent must inspect or operate an authenticated SAP web UI through an in-app Browser, Microsoft Edge CDP, or an existing Playwright client, especially when SAP SSO reuse, isolated Edge profiles, deterministic target selection, screenshots, or browser bootstrap recovery is required.
tools
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.
tools
SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows, comments, permissions, visual regression, and reusable QA automation. This skill should be used when building SAC end-to-end tests, onboarding SAC dashboards into Playwright, creating dashboard profiles or scenario YAML, using Microsoft Edge/CDP, Chrome DevTools MCP, Vercel Labs agent-browser, or manual discovery for SAC components, testing SAC optimized stories, configuring SAC auth storage state, managing visual/data baselines, testing comments, planning writeback, data actions, multi actions, role-based views, restricted Windows/company environments, or creating SAC failure triage artifacts.