Back to Details

bimp-erp-context

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

BIMP ERP Context

BIMP ERP 上下文

Use this skill when working with BIMP MCP tools to understand the ERP domain, entity relationships, and API behavior.
在使用BIMP MCP工具时可使用本技能来了解ERP领域知识、实体关系和API行为。

Entity Relationships

实体关系

Organization
  +-- Warehouse (storage locations)
  +-- Employee (staff)
  +-- Currency / VAT (reference data)
  |
  +-- Nomenclature (products & services)
  |     +-- NomenclatureGroup (categories)
  |     +-- UnitOfMeasurement
  |     +-- Specification (BOM: materials + quantities)
  |     +-- PriceList (per-product prices)
  |     +-- Inventory (stock balances per warehouse)
  |
  +-- Counterparty (customers & suppliers)
  |     +-- Contract (terms, currency, price list)
  |
  +-- Sales: Order -> SalesInvoice -> CustomerPayment
  +-- Procurement: SupplierInvoice -> PurchaseInvoice
  +-- Production: Specification -> ProductionOrder -> ProductionAssembly
  +-- Inventory: Movement, Write-off
Organization
  +-- Warehouse (storage locations)
  +-- Employee (staff)
  +-- Currency / VAT (reference data)
  |
  +-- Nomenclature (products & services)
  |     +-- NomenclatureGroup (categories)
  |     +-- UnitOfMeasurement
  |     +-- Specification (BOM: materials + quantities)
  |     +-- PriceList (per-product prices)
  |     +-- Inventory (stock balances per warehouse)
  |
  +-- Counterparty (customers & suppliers)
  |     +-- Contract (terms, currency, price list)
  |
  +-- Sales: Order -> SalesInvoice -> CustomerPayment
  +-- Procurement: SupplierInvoice -> PurchaseInvoice
  +-- Production: Specification -> ProductionOrder -> ProductionAssembly
  +-- Inventory: Movement, Write-off

Full Production Chain

完整生产链路

Counterparty (supplier)
  -> PurchaseInvoice (procure components)
    -> Inventory (components in stock)
      -> Specification (BOM: components -> product)
        -> ProductionOrder (plan production)
          -> ProductionAssembly (execute)
            -> Inventory (finished goods)
              -> SalesInvoice (sell to customer)
Counterparty (supplier)
  -> PurchaseInvoice (procure components)
    -> Inventory (components in stock)
      -> Specification (BOM: components -> product)
        -> ProductionOrder (plan production)
          -> ProductionAssembly (execute)
            -> Inventory (finished goods)
              -> SalesInvoice (sell to customer)

Ukrainian Terminology

乌克兰术语对照表

UkrainianEnglishAPI Entity
НоменклатураProductnomenclature
КонтрагентCounterpartycounterparty
СпецифікаціяSpecification/BOMspecification
Замовлення покупцяCustomer OrderinvoiceForCustomerPayment
РеалізаціяSales InvoicesalesInvoice
Прихідна накладнаPurchase InvoicepurchaseInvoice
Виробничий наказProduction Orderproduction-order
СкладWarehousewarehouse
ЗалишкиInventoryinventory
乌克兰语英文API实体
НоменклатураProductnomenclature
КонтрагентCounterpartycounterparty
СпецифікаціяSpecification/BOMspecification
Замовлення покупцяCustomer OrderinvoiceForCustomerPayment
РеалізаціяSales InvoicesalesInvoice
Прихідна накладнаPurchase InvoicepurchaseInvoice
Виробничий наказProduction Orderproduction-order
СкладWarehousewarehouse
ЗалишкиInventoryinventory

Key API Behaviors

核心API特性

  1. readList returns INCOMPLETE data for many entities (salesInvoice, specification, purchaseInvoice, production-order). Use 
    bimp_fetch_all
    with 
    enrich=true
    or call the 
    read
    endpoint for full details.
  2. No total count in paginated responses. Last page: 
    data.length < requested count
    .
  3. Max page size is 100 for offset/count pagination.
  4. All mutations are POST — even updates and deletes.
  5. UUID is the primary key for all entities.
  1. readList对多个实体返回数据不完整（包括salesInvoice、specification、purchaseInvoice、production-order）。请使用携带
    enrich=true
    参数的
    bimp_fetch_all
    ，或调用
    read
    端点获取完整详情。
  2. 分页响应中无总计数。判断最后一页的标准：
    data.length < 请求的数量
    。
  3. 偏移/计数分页的最大页长为100。
  4. 所有变更操作均为POST请求 —— 即便是更新和删除操作也一样。
  5. 所有实体的主键为UUID。

Planning & Accounting Fields

规划与会计字段

Available only via extended tools (
bimp_nomenclatures_read
, 
bimp_nomenclatures_upsert
):
FieldDescription
minStockMinimum stock level — triggers reorder
maxStockMaximum stock level — replenishment target
speedOfDemandDemand rate per period
insuranceReserveSafety stock buffer
deliveryTermDelivery lead time in days
plannedCostPlanned unit cost
These are NOT available in the standard 
bimp_nomenclature_read
tool.
仅可通过扩展工具（
bimp_nomenclatures_read
、
bimp_nomenclatures_upsert
）获取：
字段描述
minStock最低库存水平 —— 触发补货
maxStock最高库存水平 —— 补货目标
speedOfDemand每期需求速率
insuranceReserve安全库存缓冲
deliveryTerm交货提前期（单位：天）
plannedCost计划单位成本
以上字段在标准
bimp_nomenclature_read
工具中不可用。

Procurement Analysis Pattern

采购分析模式

  1. Read planning fields via 
    bimp_nomenclatures_read
    for each product
  2. Get current stock via 
    bimp_nomenclature_readStocks
  3. Fetch BOMs via 
    bimp_fetch_all
    with 
    tool=bimp_specification_readList
    , 
    enrich=true
  4. Calculate deficit: 
    max(0, minStock - currentStock)
  5. Explode BOM to get required component quantities
  6. Compare component needs against component stock
  7. Prioritize by 
    deliveryTerm
    (longest lead time first)
  1. 调用
    bimp_nomenclatures_read
    读取每个产品的规划字段
  2. 调用
    bimp_nomenclature_readStocks
    获取当前库存
  3. 使用
    tool=bimp_specification_readList
    、
    enrich=true
    参数调用
    bimp_fetch_all
    获取物料清单（BOM）
  4. 计算缺口：
    max(0, minStock - currentStock)
  5. 拆解BOM得到所需组件数量
  6. 对比组件需求与组件库存
  7. 按
    deliveryTerm
    优先级排序（交货期最长的优先）