Use when Power BI work needs live connector planning or metadata access for SAP OData/CDS, Salesforce, Dataverse, SQL, Fabric, Power BI REST, Snowflake, Databricks, APIs, or enterprise warehouses.
원문 언어: 영어
메뉴
이 저장소의 skills
SkillsMP는 rweisssieker-xp/PowerBi-Codex-Plugin에서 259개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
rweisssieker-xp/PowerBi-Codex-Plugin수집된 skill 259개 중 40개를 표시합니다.
Use when Power BI work needs live connector planning or metadata access for SAP OData/CDS, Salesforce, Dataverse, SQL, Fabric, Power BI REST, Snowflake, Databricks, APIs, or enterprise warehouses.
원문 언어: 영어
Use when Power BI sources include transport visibility, carrier, parcel, freight, shipment tracking, project44, FourKites, Transporeon, Shippeo, Descartes, DHL, FedEx, UPS, TMS, or carrier APIs.
원문 언어: 영어
Use when Power BI sources or closed-loop actions involve low-code, workflow, RPA, Power Apps, Power Automate, UiPath, Automation Anywhere, Blue Prism, Nintex, Camunda, or business process automation.
원문 언어: 영어
Use when Power BI artifacts need German-English or multilingual KPI names, report titles, glossary terms, descriptions, acceptance documents, training material, or global enterprise rollout support.
원문 언어: 영어
Use when natural-language requests should become DAX measures with KPI contracts, semantic context, tests, validation, and guardrails against incorrect filter or date logic.
원문 언어: 영어
Use when natural-language source extraction requirements should become Power Query/M designs for APIs, OData, SQL, files, pagination, incremental refresh, typing, error handling, or schema drift.
원문 언어: 영어
Use when Power BI sources include OCR, IDP, invoice capture, document extraction, ABBYY, Kofax, OpenText VIM, Basware, Esker, Rossum, Azure AI Document Intelligence, or AP automation.
원문 언어: 영어
Use when Power BI needs planning, writeback, forecasting, what-if simulation, scenario analysis, price-volume-mix, inventory, capacity, working capital, budget, forecast, or operational planning.
원문 언어: 영어
Use when Power Query extraction or transformation needs tests for query folding, schema drift, nulls, duplicates, pagination, type conversion, incremental refresh, privacy levels, or source reconciliation.
원문 언어: 영어
Use when industrial enterprise questions require Power BI KPI visibility across additional end-to-end process chains, micro-processes, cross-system handoffs, and action-oriented management cockpits.
원문 언어: 영어
Use when Power BI analysis needs event logs, process variants, bottleneck detection, rework loops, conformance checks, cycle time, throughput, lead time, or process mining for Order2Cash, Procure2Pay, Production, Service, Maintenance, or Finance processes.
원문 언어: 영어
Use when Power BI sources include procurement suites, sourcing, supplier risk, spend analytics, Coupa, Ivalua, Jaggaer, SAP Ariba, GEP, Scoutbee, Riskmethods, Sphera Supply Chain Risk, or supplier portals.
원문 언어: 영어
Use when Power BI sources include QM, QMS, EHS, CAPA, complaints, nonconformance, audits, inspections, quality notifications, SAP QM/EHS, ETQ Reliance, MasterControl, TrackWise, Intelex, Sphera EHS, Enablon, Veeva Quality, or LIMS.
원문 언어: 영어
Use when AI/KI answers should retrieve from enterprise BI knowledge such as KPI catalogs, semantic models, report docs, source metadata, glossary, tickets, acceptance evidence, CoE standards, or process documentation.
원문 언어: 영어
Use when a customer-specific Power BI/Fabric target architecture must be generated for source landscapes such as SAP plus Salesforce plus MES, Oracle plus WMS plus Snowflake, Dynamics plus Dataverse plus Fabric, or hybrid Excel/data warehouse legacy estates.
원문 언어: 영어
Use when Power BI work touches finance, regulated industries, audit, ESG, quality, export control, privacy, validation, internal controls, or compliance standards such as IFRS, HGB, US GAAP, SOX, CSRD, ISO 9001, IATF 16949, GMP, FDA, GxP, GDPR, or sanctions.
원문 언어: 영어
Use when Power BI usage telemetry, report views, page views, load times, audience behavior, dead reports, unused pages, or adoption should drive report optimization and portfolio cleanup.
원문 언어: 영어
Use when Power BI cockpits should be designed by enterprise role such as CEO, CFO, COO, Sales Director, Plant Manager, Supply Chain Manager, Controller, Quality Manager, Maintenance Manager, or Service Manager.
원문 언어: 영어
Use when industrial KPI changes need candidate root-cause hypotheses across ATP, supplier, production, credit block, master data, transport, invoice block, pricing, quality, maintenance, or demand changes.
원문 언어: 영어
Use when Power BI sources or governance depend on identity, security, access, Entra ID, Okta, Ping Identity, SailPoint, CyberArk, BeyondTrust, IAM, PAM, RBAC, access reviews, or privileged access.
원문 언어: 영어
Use when Power BI semantic model versions need diff, regression, breaking-change detection, changed measures, changed relationships, deleted fields, downstream impact, or release validation.
원문 언어: 영어
Use when Power BI sources include subscription, recurring revenue, billing, usage, invoicing, revenue recognition, Zuora, Chargebee, Stripe Billing, Salesforce Revenue Cloud, SAP BRIM, Oracle Revenue Management, or SaaS/aftermarket monetization systems.
원문 언어: 영어
Use when Power BI sources include tax, compliance, audit, GRC, controls, risk, SOX, VAT, indirect tax, audit management, Workiva, Diligent, SAP GRC, AuditBoard, Vertex, Avalara, or ONESOURCE.
원문 언어: 영어
Use when Power BI sources include treasury, cash, banking, payments, cash forecasting, bank statements, EBICS, SWIFT, Kyriba, SAP Treasury, Serrala, TIS, Coupa Treasury, or banking APIs.
원문 언어: 영어
Use when Power BI sources include WHS, WMS, warehouse management, warehouse automation, robotics, scanners, AutoStore, Kardex, Dematic, Swisslog, Körber, Manhattan, Blue Yonder WMS, SAP EWM/WM, Zebra, Honeywell, or warehouse execution systems.
원문 언어: 영어
Decide whether a Power BI request should be built new, extended, fulfilled from an existing certified dataset, bought as a standard app, migrated, consolidated, or retired.
원문 언어: 영어
Create audit-ready evidence packs for Power BI reports and datasets. Use for KPI approval, RLS testing, source reconciliation, data privacy, assumptions, deployment approvals, and compliance reviews.
원문 언어: 영어
Score whether data sources are ready for Power BI implementation. Use for data completeness, key quality, history, grain, source ownership, PII, refreshability, query folding, schema stability, and KPI suitability.
원문 언어: 영어
Use when Power BI solutions need cross-system master data mapping for customers, suppliers, products, materials, accounts, assets, employees, plants, legal entities, cost centers, profit centers, projects, or hierarchies.
원문 언어: 영어
Use when Power BI work depends on ERP, CRM, SCM, HCM, EAM, PLM, MES, service, finance, or industry systems from major vendors and source-system structures must be mapped to business processes.
원문 언어: 영어
Track executive value from Power BI expert reduction. Use for saved expert hours, report consolidation, certified dataset adoption, fewer refresh failures, faster delivery, reduced capacity cost, and business impact.
원문 언어: 영어
Design Power BI root-cause cockpits for industrial process problems across source systems. Use for margin erosion, delivery delays, backlog, cash issues, supplier failures, production losses, quality cost, inventory risk, forecast error, downtime, warranty,…
원문 언어: 영어
Analyze Power BI lineage and impact when fields, tables, measures, sources, refresh schedules, RLS rules, or certified datasets change. Use for change impact, owner notification, regression scope, and release planning.
원문 언어: 영어
Turn natural-language business questions into verified Power BI report designs. Use when users ask questions like why customers churn, what drives margin, where inventory risk exists, or which process bottlenecks matter, and the answer must include data…
원문 언어: 영어
Manage reusable Power BI patterns for domains, page layouts, KPIs, DAX, RLS, validation, refresh, and delivery packs. Use when standardizing repeatable expert knowledge into templates.
원문 언어: 영어
Convert Power BI requests into implementation backlog items for Jira, Azure DevOps, Linear, or GitHub Issues. Use for stories, tasks, acceptance criteria, data requirements, tests, dependencies, and definition of done.
원문 언어: 영어
Run Power BI release quality gates. Use before publishing, certifying, migrating, or changing reports and semantic models to verify KPI definitions, RLS, refresh, performance, ownership, documentation, and acceptance.
원문 언어: 영어
Assign risk scores to Power BI reports, datasets, and delivery plans. Use for business risk, KPI risk, security risk, performance risk, refresh risk, maintenance risk, adoption risk, and portfolio prioritization.
원문 언어: 영어
Run structured Power BI requirements interviews for business users. Use to collect outcome, KPI, grain, dimensions, source systems, security, refresh, acceptance, and delivery constraints before experts build anything.
원문 언어: 영어
Map industrial process questions to source systems and source objects for Power BI. Use for SAP ECC/S4HANA, SAP BW, SAP Datasphere, Salesforce, Dynamics, Oracle, Infor, IFS, Siemens Teamcenter, Windchill, MES, SCADA, historian, WMS, TMS, ServiceNow, Jira,…
원문 언어: 영어