SAP S/4 HANA
Enterprise ERP system for Runwal Group covering project delivery, finance, procurement, and operations management.
Current State
SAP S/4 HANA deployed for Runwal Group operations. Managed by Manish (direct report to CTO). Integrated with Salesforce (sales/CRM), Snowflake (analytics), and N8N (automation workflows). Part of the enterprise data pipeline: Salesforce → Fivetran → Snowflake → Tableau/Power BI.
Key Learnings
-
openclaw-v2026322-whatsapp-recovery — WhatsApp recovery involving SAP integrations
-
runwal-fy-2026-27-strategic-direction-consolidate-entire — FY 2026-27 strategic direction includes SAP consolidation
-
enterprise-capability-expansion-5-pillars-from-digital-employee-analysis — Enterprise expansion includes SAP pillar
-
httpx-http2-extra-required-for-gold-stack-upgrades — HTTP/2 for SAP-adjacent services
-
mcp-upgrade-api-client-method-signature-backward-compatibili — API backward compatibility
-
notebooklm-mcp-integration-pattern — MCP integration reference
-
openclaw-whatsapp-idle-watchdog-patch — WhatsApp watchdog context
-
upgrade-history-full — Full upgrade history
-
real-estate-domain-terminology-mmr-mumbai-metropolitan — Real estate domain terminology
-
runwal-group-business-context-indian-real-estate-developer — Runwal Group business context
-
runwal-team-structure-direct-reports-to-cto-manish-sap — Team structure: Manish manages SAP
-
booking-cancellation-module-audit-baseline-apr-2026 — Cancellation/Retention/Transfer module on Booking__c audited against BRD on 07-Apr-2026. Core skeleton is functional: st
-
quotation-credit-note-sap-integration-chain — The core quotation-to-ERP flow is: Offer_Master__c → Quote_Applied_Discounts__c → Quotation__c → Booking__c, with Credit
-
runwal-vantage-project-scope-canonical-reference — Runwal Vantage is a Tableau-grade internal BI platform forked from Redash. Scope: 9 Runwal functions, 500→1000 users, 5
-
vantage-snowflake-only-single-source-architecture — Runwal Vantage consumes only Snowflake as its data source. All upstream sources (Salesforce, SAP S/4, SharePoint CSV/Exc
-
bi-platform-single-source-principle-all-via-snowflake — R-Dash (Runwal’s internal BI platform) is architected as Snowflake-only consumption — Salesforce, SAP S/4, SharePoint CS
-
r-dash-single-snowflake-connector-zero-ingestion — R-Dash connects to Snowflake only as its sole data source. All upstream systems (Salesforce, SAP S/4, SharePoint CSV/Exc
-
r-same-snowflake-only-no-ingestion-architecture — R-Same is a consumption-only BI platform: Snowflake is the single active data source, and zero ingestion/ETL code exists
-
r-same-snowflake-only-no-direct-source-connectors — R-Same consumes data exclusively from Snowflake — no direct connectors to Salesforce, SAP S/4, or SharePoint inside the
-
r-same-snowflake-only-consumption-zero-ingestion — All upstream data sources (Salesforce, SAP S/4, SharePoint CSVs/Excels, other files) flow into Snowflake via existing up
-
sharepoint-snowflake-no-ingestion-in-analytics-platform — All upstream data sources (SharePoint, SAP, Salesforce) must materialize into Snowflake via dedicated pipelines (Fivetra
-
r-same-all-data-sources-funnel-through-snowflake-only — R-Same (Runwal Vantage BI platform) consumes Snowflake as its single data source — Salesforce, SAP S/4, SharePoint CSVs,
-
r-same-snowflake-only-consumption-ar4-constraint — R-Same consumes Snowflake as its single data source — zero ingestion code lives inside the platform. All upstream source
-
sharepoint-sap-salesforce-all-via-snowflake-zero-ingestion — R-Same consumes Snowflake as its sole data source — zero ingestion code inside the platform. All upstream sources (Sales
-
sharepoint-data-routes-through-snowflake-vantage-is-consumpt — Initial design explored a file-to-table materialisation shim inside R-Same to ingest SharePoint CSV/Excel directly. This
-
r-same-sharepoint-snowflake-upstream-only — R-Same consumes Snowflake only — all SharePoint CSV/Excel, Salesforce, and SAP data flows upstream via Fivetran/n8n befo
-
cost-observer-fivetran-sync-cost-observability-runwal-local — Cost Observer — Runwal Fivetran cost visibility (2026-04-23)
-
salesforce-mon-org-health-pull-2026-04-27-3-critical-runwal — Mon Org Health Pull — 2026-04-27 (Runwal Production)
-
encouraging-not-daunting-ui-design-dna-for-every-aj-owned-pr — AJ explicitly rejected the R-Plan v1 admin/planner UI (2026-05-04) — technically correct (proper WBS, RLS, CPM, audit) b
Known Issues
- notebooklmclientfromstorage-coroutine-not-awaited-coroutine — NotebookLM coroutine issue (affects SAP research)
Decisions
-
nova-decision-log-consolidated — NOVA decisions on SAP
-
clawteam-openclaw-multi-agent-swarm-evaluation — OpenClaw swarm for SAP automation
-
build-g2-cost-pre-flight-as-runwal-local-guardrail-inside-fi — Build G2 Cost Pre-Flight as Runwal-local guardrail inside fivetran-mcp, diverging from upstream Bible framework v19.1.3
-
proceed-to-phase-3-data-layer-with-three-explicit-bias-corre — Proceed to Phase 3 (data layer) with three explicit bias-correction measures from the premortem + bias-detect pass: (1)
-
shipped-pure-observability-cost-observer-on-fivetran-mcp-opt — Shipped pure-observability Cost Observer on fivetran-mcp (Option A). Enforcement scope fully discarded. Module cost_guar
-
sdrroc-fund-transfer-2-negation-requirement-is-satisfied-at — SDR/ROC fund-transfer “2% negation” requirement is satisfied at the architectural layer via SAP-driven X2_Received formu
-
referral-credit-note-scs-module-is-go-for-production-within — Referral + Credit Note + SCS module is GO for production within documented scope. Loyalty system (LockatedApp_LoyaltyEng
-
r-plan-layer-2-architecture-locked-2026-04-28-nextjs-16-pnpm — R-Plan Layer 2 architecture LOCKED 2026-04-28: Next.js 16 + pnpm 10 + Tailwind 3 + shadcn/ui + Drizzle + Postgres 17 + B
-
r-plan-layer-2-architecture-locked-2026-04-28-re-record-for — R-Plan Layer 2 architecture LOCKED 2026-04-28 (re-record for tag schema compliance — prior call cfde777c had XML escapin
-
close-fri-2026-05-01-deploy-window-with-zero-new-prod-code-d — CLOSE Fri 2026-05-01 deploy window with zero new prod code deploys. ROLL all ~17 pending fullcopy-only Apex changes (Saa
-
arj-44-fri-2026-05-01-deploy-window-close-roll-17-apex-to-tu — ARJ-44 Fri 2026-05-01 Deploy-Window Close — Roll 17 Apex to Tue 2026-05-05 CLOSED Friday 2026-05-01 deploy window with z
-
r-plan-default-ui-outline-mode-not-wbs-tree — R-Plan default UI = Outline Mode (not WBS-tree) /projects/[id] now renders Outline Mode (Notion/Linear/Asana style: phas
Relationships
Sources
- Vault notes: 14 references
Contradictions
(none)
Related
salesforce | snowflake | runwal | fivetran
- salesforce-quotation-dual-offer-model-architecture