Source Datav1.0
SAM (Non-PIT)
ChinaScope SAM product/supply-chain source fields.
Buy by the field
40 priced fields
Pick the fields you need — priced individually below.
Whole set$6,958.33/mo
Exactly the sum of its fields — no bundle premium, no bundle discount
Pay annually · save 20% — $66,800/yr
ⓘ Take the whole set from the field list below — select everything, add it to your basket, and check out there.
Data due diligence
- Point-in-time: no
- Not point-in-time; a restatement replaces the original.
- Personal data: none
- No personal information.
- Web collection: no
- No web collection; sourced from filings or a licensed feed.
- Generative AI: yes
- Generative AI was used in producing part of this dataset; see the product's Data sourcing answers.
The personal-data values are descriptive, not risk grades: no personal information in any dataset is collected from individuals; all of it is drawn from mandatory public company disclosure or already-published news.
Declarations published by ChinaScope. Open the Due diligence tab and sign in to read the full questionnaire.
SAM (Non-PIT)
samSource DataChinaScope SAM product/supply-chain source fields.
Daily source stitch · data frontier 2026-10-28
11. Field reference: every column
The full field dictionary: every table, every column, with its type and meaning. One real sample row is shown per table.
fin_secu_sam_period
Table · pick one of 6
fin_secu_sam_period
17 columns · grain (primary key): secu × report_date
| Column | Name | Type | Null | Description |
|---|---|---|---|---|
operation | CDC operation flag | string | yes | A record-maintenance flag marking whether this row was added (A), updated (U), or deleted (D) in the latest data delivery, so you can apply incremental changes correctly when keeping your copy in sync. |
id | Record ID | string | yes | ChinaScope's unique row identifier for one reporting entity's data in one financial reporting period. The table's grain is one row per listed security (or per non-listed bond issuer) per reporting period, so a single underlying company can appear in several rows for the same period when it has multiple listings, or both listed-share and bond-issuer records. |
secu ·PK | Security code | string | no | ChinaScope's standardized stock code for the listed security. The suffix marks the listing venue: _SZ_EQ (Shenzhen, including ChiNext), _SH_EQ (Shanghai, including the STAR Market), _BJ_EQ (Beijing Stock Exchange), and provisional _TEMP_EQ codes. _KC_EQ is ChinaScope's pre-listing code for a company applying to list on the STAR Market: a company that lists then also appears under its listed code (same company_id2), sometimes for the same periods. The number in a _KC_EQ code is ChinaScope's own and can repeat an unrelated listed code. secu is a primary key and is always present. |
publish_date | Public-record (filing) date | date | no | The announcement date of the first report for this period. When a later report restates the period, the standardized figures in fin_secu_sam_product and fin_secu_sam_product_calc come from that later report but keep this date, so for them it is earlier than when they became public; the as-reported columns are correctly dated by it. |
report_date ·PK | Report end date | date | no | The fiscal period-end (closing) date that the reported segment figures cover, formatted year-month-day. |
p | Reporting period length (months) | string | yes | The number of months of activity the period covers: 6 (interim/half-year) or 12 (annual). |
q | Reporting period quarter | string | yes | A code for which fiscal reporting milestone the row represents: Q2 is the interim (half-year) report and Q4 is the annual report. |
y | Fiscal year | integer | yes | The financial (fiscal) year to which this reporting period belongs. |
fy | Fiscal year-end (MM-DD) | string | yes | The month-and-day on which the company's fiscal year closes, defaulting to 12-31 for A-shares; useful for identifying companies with a non-December year-end. |
currency | Reporting currency | string | yes | The standard currency code in which this period's monetary segment figures (revenue, cost, profit) are denominated. |
is_valid | Valid flag | boolean | yes | A validity flag; every row in this dataset is 1 (valid/current). Do not read 1 as 'the most recent fiscal year': records from many past years are also flagged 1. |
company_id | ChinaScope security ID (S-id) | string | no | A ChinaScope S-form internal id (e.g. S000200) that resolves to the SECURITY master base_stock by its internal id: measured ~100% present there and 0% in the company master, so it is NOT the company key. To reach the company's master profile use company_id2 (the CSF-form company id). Its precise business role is under ChinaScope confirmation (understood to identify the issuer for non-listed bond issuers). |
company_type | Company type | string | yes | A code for the kind of reporting entity; every row in this dataset is 1 (a listed company). |
market | Market code (as-of report) | string | yes | A code identifying the market or exchange on which the company is listed. |
company_id2 | Company ID (CSF master) | string | no | ChinaScope's institution code that resolves this row to the company's master profile information, identifying the underlying company entity. |
create_time | Record create timestamp | timestamp | no | The timestamp recording when this record was first created in the dataset. |
update_time | Record update timestamp | timestamp | yes | The timestamp recording when this record was most recently updated in the dataset. |
Sample row:
operation: A
id: S0000832025-12-312025Q412-3112
secu: 002072_SZ_EQ
publish_date: 2026-02-11
report_date: 2025-12-31
p: 12
q: Q4
y: 2025
fy: 12-31
currency: CNY
company_id: S000083
company_type: 1
market: 1002
company_id2: CSF0000000892
create_time: 2026-02-11 16:09:09
update_time: 2026-02-11 16:09:09
·
Sourced as-delivered from ChinaScope, with resolved codes and structural links computed by Numinor. Licensing passes through to you; fields are served exactly as the vendor issues them.
01
Access & FAQ
- How do I buy just a few fields?
- Check the fields you want and you'll see your running subtotal. Select every field and the whole-set price applies automatically. Add them to your basket and check out — this dataset, or fields combined across several.
- Can I evaluate these fields in the Matrix before I buy?
- Yes — load the actual source tables in the Matrix and analyze them with an AI agent before you buy. See the Overview tab for this dataset’s Matrix evaluation lag; “None” means no intentional delay.
- How is it delivered?
- Apache Parquet over a signed-URL REST API, the same pipe as Construct Data. The free Matrix sandbox serves an evaluation snapshot. Its delay, if any, is shown in the Overview tab.
- When is each update available, and how reliable is it?
- Source data refreshes on the ChinaScope cadence and is delivered through the same signed-URL pipeline as Construct Data, with the same manifest/status behaviour. Evaluate freshness yourself in the Matrix before you commit.
- Why are some fields free and others cost thousands?
- Price tracks non-replicability. Resolved codes and structural links are the moat; machine scores and raw text are cheap; identifier keys are free. Figures are priced per table; codes are charged once per dataset.
Still have questions? Contact Sales →
02
Questions This Dataset Comes Up In
Public reference pages answering a question that spans several datasets, this one among them. No account needed.
- Why a join to China A-share company data silently drops rowsEntity resolution in Chinese company data is partial, and the resolved share differs by dataset and by relationship type. An inner join discards exactly the rows that were not resolved, and those rows are not a random sample.
- Which China A-share datasets are point-in-time, and which only look like itA dataset is point-in-time only if it tells you when a figure became public, not just which period it covers. Several widely used China datasets carry the period and not the filing date, which reads as point-in-time and is not.
- Disclosed versus inferred: two kinds of China supply-chain and ownership dataDisclosed data is what filers published about themselves and arrives already consolidated. Inferred data is constructed and is built to be aggregated. The two obey opposite rules, and treating one like the other double-counts or under-counts.
- One company, many securities: why A-share company counts come out too highCompany facts attach to each listed security, so a company with two listings appears twice. Grouping on the ticker instead of the company key inflates every company-level aggregate.
- When to roll up subsidiaries in China company data, and when it double-countsWhether to roll up depends on whether the dataset is already consolidated. Some ChinaScope tables are pre-aggregated up the tree, some are deliberately not, and one column inside SAM is a subtree total that looks additive and is not.
- Primary key versus grain: why de-duplicating China filing data deletes real rowsThe column that uniquely identifies a row and the columns that say what the row is about are not the same thing. De-duplicating on the second silently discards real disclosures.
- Which industry tree should you use for China equities?ChinaScope Reference carries five independent industry schemes in one table. They are separate trees, not levels of one hierarchy, and mixing them in a single grouping is meaningless.