AvailableTest Data
Source-system data (Org62 orders, Workday invoices) or Oracle staging-table data (sales orders, reduction orders, invoices) — you choose which to mimic.
Source-shaped test data, on request.
The Oracle Transformation Layer between Salesforce Org62, Workday and Zuora RMS is being migrated to Snowflake. To regression-test that migration end to end we need source-shaped data that behaves like production. This workspace creates it in a few clicks.
Capabilities
Available
AvailableLoad to Snowflake
Insert a finished job's rows into the prefixed TEST_ copies of the Oracle landing tables in Snowflake (key-pair login, configured in config/<env>.env). Source-system files are reshaped into the landing table they feed.
PlannedValidate with dbt
Run dbt tests against the loaded data to compare the migrated Snowflake layer with Oracle TL.
PlannedSchedule Runs
Run the generate → load → validate flow on a schedule with Apache Airflow.
UpcomingAgentforce
An in-app assistant. Scope to be defined with the team.
How the data is made
- You choose what to mimic — the source systems (Org62
RMSSync__c, Workday invoices) or the Oracle staging tables (SFDC_RPRO_INT_SO_STAGE,SFDC_RPRO_INT_INV_STAGE). - Valid data only — every combination was observed in the real data; staging rows also pass the Oracle TL validation.
- Minimum, not random — the smallest set of whole records that still covers every observed pair of business values (order type, usage model, currency, …).
- Test data and safe — identifiers carry a test-data marker; names are prefixed
SYN. - Orchestrated by Robot Framework — generate → validate → export, with a Robot report for every run.
How your session works
- Open Test Data Generator in the left menu, pick what to mimic (Source System Data or Oracle Staging Data) and click a tile. A job card appears below the tiles with its Job ID and a live progress bar.
- You can start several jobs at once — they run in parallel, each with its own Job ID.
- When a job finishes, download its file(s) or load them straight into Snowflake.
- Nothing is saved. There is no database. Reloading or closing the page ends your session and discards every job and file; a fresh session starts on the next load.
Test Data Generator
Choose which data to mimic, then pick a tile to start a Robot Framework run. The files are validated before you can download them.
Generate Sales Orders
Available CSVSource: Org62
Lands in: SFDC_RPRO_INT_SO_STAGE
RMSSync__c (Order / OrderItem / Product2 / Contract / Account)
Complete real-pattern orders (one per scenario) covering every order type, usage model, currency, channel, revenue-treatment and FDM path seen in the Org62 sandbox.
- Minimum set
- 105 scenarios · 264 records
- Coverage
- 2029 of 2030 observed value-pairs
Generate Reduction Orders
Available CSVSource: Org62
Lands in: SFDC_RPRO_INT_SO_STAGE
RMSSync__c where Order.Type = 'Cancel' (Reduction Order)
Cancel orders delivered with the original order they reverse and, where one exists, the replacement order, so the amendment chain is intact.
- Minimum set
- 28 scenarios · 171 records
- Coverage
- 1677 of 1677 observed value-pairs
Generate Invoices
Available CSV
Source: Workday (AR invoices via MuleSoft)
Lands in: SFDC_RPRO_INT_INV_STAGE + SFDC_RPRO_INT_SO_STAGE
SFDC_WD_RPRO_INV_STG shape: INV, CM-RO (reduction credit memo), CM (courtesy credit memo)
Invoices raised against the generated Org62 orders, credit memos reversing generated Reduction Orders, and courtesy credit memos, across every observed currency / ledger (SOB) setup.
- Minimum set
- one invoice per covering order + one credit memo per reduction scenario
- Coverage
- 23 INV, 20 CM-RO and 3 CM currency/ledger setups observed
Generate Workday Invoice JSON
Available JSONSource: Workday (AR invoices via MuleSoft)
Lands in: SFDC_WD_RPRO_INV_STG + SFDC_RPRO_INT_SO_STAGE
Workday invoice payload (JSON) that MuleSoft loads into the Oracle table SFDC_RMS.SFDC_WD_RPRO_INV_STG
The same validated invoices and credit memos as Generate Invoices, delivered in the JSON shape Workday sends: one invoice object with its invoice lines nested below, ready to be loaded into the Oracle staging table that precedes SFDC_RPRO_INT_INV_STAGE.
- Minimum set
- one invoice per covering order + one credit memo per reduction scenario
- Coverage
- Same 23 INV, 20 CM-RO and 3 CM setups as Generate Invoices
Generate Staging Sales Orders
Available CSVSource: Oracle staging tables
Lands in: SFDC_RPRO_INT_SO_STAGE
SFDC_RPRO_INT_SO_STAGE rows with TRAN_TYPE = 'SO'
Real staging sales orders, one per scenario, covering every order type, currency / ledger, product category, revenue treatment, region and usage model seen in the table. Every row passes the Oracle TL validation.
- Minimum set
- 198 scenarios · 349 records
- Coverage
- 2729 of 2732 observed value-pairs
Generate Staging Reduction Orders
Available CSVSource: Oracle staging tables
Lands in: SFDC_RPRO_INT_SO_STAGE
SFDC_RPRO_INT_SO_STAGE rows with TRAN_TYPE = 'RORD' (reduction orders)
Reduction orders with negative quantities, delivered with the original order they reverse where the table holds it, so the amendment chain is intact. Every row passes the Oracle TL validation.
- Minimum set
- 106 scenarios · 273 records
- Coverage
- 1831 of 1837 observed value-pairs
Generate Staging Invoices
Available CSVSource: Oracle staging tables
Lands in: SFDC_RPRO_INT_SO_STAGE + SFDC_RPRO_INT_INV_STAGE
SFDC_RPRO_INT_INV_STAGE rows: INV (invoice) and CM-RO (reduction credit memo)
Invoices and credit memos built from generated sales-order lines, carrying the values RevPro copies from them (ship-to country, region, GL accounts, order type ...). The real table fails 100% of rows without those; these pass the Oracle TL validation.
- Minimum set
- 51 scenarios · 103 records
- Coverage
- 120 of 120 observed ledger / order-type / line-shape pairs
Tip: Generate Invoices, Generate Workday Invoice JSON and Generate Staging Invoices also export the orders their invoices point at, so the files load together.
Jobs in this session
Click a tile to start a run — its job card will appear here.
Load to Snowflake
Finished jobs whose data can be inserted into the prefixed TEST_ tables. Loading is all-or-nothing and asks you to confirm first; if a target table is missing and cannot be created, nothing is loaded.
No data is ready to load yet.
Generate data first. Once a job finishes it is listed here, ready to be inserted.
Snowflake environment
Choose the default Snowflake instance for loading and clearing test data. It applies to every job until you change it or the server restarts (then it is back to QA).
