What This API Solves

The Kingdee Cloud Xingchen V2 /jdy/v2/bd/store warehouse query API is the source endpoint for warehouse master data sync in the WDT–Kingdee supply chain integration. It filters and paginates warehouse data by enable status, modification time, and category, providing authoritative warehouse codes and names for downstream inbound, outbound, transfer orders, and inventory queries. It prevents downstream business documents from being blocked due to missing or mismatched warehouses.

API Capability Overview

Authentication: Kingdee Cloud WebAPI standard authentication, AccessToken in request header.
Method: GET /jdy/v2/bd/store.
Filter parameters: enable (status, 1/0), modify_start_time / modify_end_time (millisecond timestamp range for incremental), group_id (warehouse category ID).
Pagination mode: page (default 1) + page_size (controlled by the Qeasy Cloud variable PAGINATION_PAGE_SIZE), with incremental scenarios sliced by modification time.
Response structure: An array of data objects, each carrying primary key id, code number, name, and extended configuration fields.
Strategy type: QUERY_ONLY, with Target configured as a no-op write, no data lands in the target system.
Scheduling: Typically deployed to run daily at 06:01 (crontab 1 6 * * *), with the incremental window closed by modify_end_time.

Typical Field Mapping

Field Name	Type	Meaning	Practical Notes
id	string	Warehouse primary key, unique identifier	Cross-system mapping key, paired with WDT warehouse ID
number	string	Warehouse business code	Preferred field for mapping to WDT warehouse code and store warehouse code
name	string	Warehouse display name	For business display; use `number` to disambiguate duplicates
enable	string	1-Enabled, 0-Disabled	Must align with WDT warehouse enable status during sync
group_id	string	Warehouse category ID	Filter by finished goods, raw material, virtual warehouses, etc.
group_number	string	Warehouse category code	Stable key for cross-system category mapping
group_name	string	Warehouse category name	Used for business identification, prone to change
is_allow_freight	string	Whether location/bin management is enabled	When enabled, downstream must supplement bin data
is_allow_neg	string	Whether negative stock is allowed	Affects issue-before-receive business rules

How to Configure in Qeasy Cloud

In the Qeasy Cloud Data Integration Platform, this API is typically wrapped via the Kingdee Cloud Xingchen V2 adapter. Configure id as the metadata primary key and number as the code field, with strategy type set to QUERY_ONLY. The Qeasy Cloud field mapper will automatically translate id → warehouse_id, number → warehouse_code, name → warehouse_name, enable → status, is_allow_freight → enable_location_management, is_allow_neg → allow_negative_stock into the downstream model with no manual conversion required. Pagination parameters are uniformly injected by the platform as page and page_size; once the incremental fields are bound to modify_start_time / modify_end_time, the platform automatically slides the window per schedule.

Cross-Scenario Practical Points

Dual-track primary key and code: Both id and number must be persisted. The former is used for precise cross-system association, the latter for business-readable mapping. Missing either causes downstream document push to fail to locate the warehouse.
Close the incremental window with modify_end_time: Prefer under-fetching to over-fetching. Cross-day scheduling boundary values are the most error-prone in real scenarios.
Strict sync of enable status: Disabled warehouses (enable=0) must be shielded downstream; otherwise dirty data of orders being placed against disabled warehouses will appear.
Use category fields for semantic grouping: group_name distinguishes e-commerce warehouses, offline warehouses, and virtual warehouses, and is relied upon for routing in WDT multi-store multi-warehouse scenarios.
Location management is a downstream switch: When is_allow_freight=1, outbound orders must carry bin/location information, otherwise they stall at Kingdee's validation step.
Align negative stock policy in advance: Differences between is_allow_neg and business rules should be confirmed with warehouse management ahead of time to avoid post-sync policy conflicts.

Pitfall Review

Pitfall 1: Matching warehouses by name only. A single enterprise may have multiple "main warehouses"; relying solely on name for matching will cause collisions. The safe practice is to use number as the mapping key.
Pitfall 2: Passing local time zone as incremental start time. Kingdee returns millisecond timestamps; passing a local time string directly loses 8 hours and causes data loss. This is where things easily go wrong.
Pitfall 3: Disabled warehouses still participating in inventory queries. If the enable filter parameter is not passed, disabled warehouses are pulled back as well, causing errors downstream when no enabled warehouse can be found.
Pitfall 4: Category name mistaken for code. group_name is volatile; cross-system integration must use group_id or group_number, not be tempted by readability.
Pitfall 5: page_size set too large triggers rate limiting. Kingdee Cloud Xingchen caps single return; in Qeasy Cloud we recommend stress-testing with the platform default first, then fine-tuning based on network conditions.

When to Use

This API applies to WDT–Kingdee Cloud Xingchen supply chain integration scenarios where Kingdee is the authoritative source for warehouse master data. The boundary is that it does not cover in-warehouse bins or inventory balances; if bin-level data or stock quantities are required, an inventory query and bin master data API must be combined.

Kingdee Cloud Warehouse Query API Field Manual: P2-283 Cross-Scenario Authoritative Tutorial