V2 Retail · SAP RFC Hub

46

Total API Controllers

LIVE

IIS .36 — Port 9292

82

Azure DAB Tables

SAP Dev

192.168.144.174 / Client 210

7

Module Categories

All 125 APIs — Via Swagger

All live endpoints are documented and testable in Swagger UI — auto-generated from the deployed controllers on IIS .36.

🔍 Open Swagger UI — All 125 APIs ↗

Try any endpoint directly — fill parameters and hit Execute. Auto-updates when new RFCs are deployed.

SAP RFC → Live API

Upload an RFC .docx → AI generates C# controller → deployed to SAP in <2 min

📄 Upload .docx

→

🤖 AI Parse

→

⚙️ C# Generate

→

📦 GitHub Push

→

🚀 Live API

RFC Document

📄

Drop your RFC document here

or browse files

.docx · .txt · .md

SAP Environment

Dev

192.168.144.174 · Client 210

Quality

192.168.144.179 · Client 600

Production

192.168.144.170 · Client 600

Azure Data API Builder

82 tables from DataV2 @ 192.168.151.28 exposed as REST/OData endpoints via Azure DAB.

Open DAB API Explorer ↗

OData Query Examples

GET /api/PO_DATA_AKA?$top=100&$filter=STORE_CODE eq 'DL01' GET /api/ET_ZADVANCE_PAYMENT?$top=50&$orderby=POSTING_DATE desc GET /api/SALE_DATA_CM_AKA?$select=STORE_CODE,AMOUNT&$top=20

RFC → Data Lake Sync

Daily sync at 1:30 AM IST via GitHub Actions. SAP RFC data flows to DataV2 SQL → Azure DAB.

SAP Dev RFC → Worker /relay-rfc → DataV2 SQL .28 → Azure DAB API

Part 1 — RFC API Deployment

📄

1. Upload RFC Document (.docx)

SAP Function Builder export — RFC Generator tab

🤖

2. AI Parses RFC Parameters

Claude extracts RFC name, import/export params, table structures

⚙️

3. C# Controller Generated

ASP.NET WebAPI controller with SAP NCo binding auto-generated

📦

4. Push to GitHub (akash0631/rfc-api)

Controllers/Finance/ or Controllers/[Module]/ — path filter auto-triggers deploy

🏗️

5. Build & Deploy to V2DC-ADDVERB

GitHub Actions (deploy-iis.yml) → copies DLL to C:\V2RfcTest\bin\ → recycles V2RfcTestPool

🚀

6. Live on sap-api.v2retail.net

Cloudflare Tunnel → V2DC-ADDVERB IIS :9292 → SAP Dev (192.168.144.174 / Client 210)

⚠️ Note for NEW controllers: VS Build on .36 required once → then all future deploys are fully automated via GitHub push

Part 2 — Data Lake Sync

🕐

1. Scheduled Trigger — 1:30 AM IST Daily

GitHub Actions (p4_sync.yml) runs on cron schedule

📡

2. Call SAP RFC via sap-api.v2retail.net

Cloudflare Worker → IIS .36 → SAP Dev — fetches latest data

💾

3. Store in DataV2 SQL Server

192.168.151.28 — SAP data written to DataV2 database tables

🌐

4. Exposed via Azure DAB (82 Tables)

my-dab-app.azurewebsites.net — OData REST API with $filter, $top, $skip, $select

SAP Dev RFC → Worker /relay-rfc → DataV2 SQL .28 → Azure DAB API

Infrastructure

Component	Detail	Status
V2DC-ADDVERB IIS	192.168.151.36:9292	● Live
Cloudflare Tunnel	v2-sap-api → sap-api.v2retail.net	● Connected
CF Worker	sap-api.v2retail.net/pipeline	● Live
GitHub Runner (iis)	V2DC-ADDVERB — label: iis	● Online
GitHub Repo	akash0631/rfc-api (PUBLIC)	● Active
Azure DAB	my-dab-app.azurewebsites.net	● Live
SAP Dev	192.168.144.174 · Client 210	● Active
Data Lake SQL	192.168.151.28 · DataV2 DB	● Active

Active GitHub Workflows

Workflow	File	Purpose
Build and Deploy to .36 IIS	deploy-iis.yml	Auto-triggers on Controllers/** push → compiles & deploys DLL
Deploy RFC Portal	deploy-portal.yml	Deploys portal/rfc_hub.html to Cloudflare Pages
Deploy RFC Worker	deploy-worker.yml	Deploys worker/index.js to Cloudflare Workers
P4 Data Lake Sync	p4_sync.yml	Daily 1:30 AM IST — SAP RFC → DataV2 SQL
Restart .36 Runner	restart36_NOW.yml	Emergency: restarts GitHub Actions runner on .36