Skip to content

BOM Data

This interface is applicable for data integration API, read Api Access Process first

remark:Bom covers all business contents of ODM,ODM builds complete machines/half machines and semi-finished products by itself for all Lenovo sites, and this Scope is only available for DBDS. It does not interfere with the BS BOM currently transmitted by ODM and is separate from each other

FrequencyTimeData amount
Daily0:00:00Incremental/full

Request address

  • API
EnvironmentURL
Testhttps://api-cn-t.lenovo.com/uat/v1.0/supply_chain/scc/open_platform/data/sync/odm/bom
Prodhttps://api-cn.lenovo.com/v1.0/supply_chain/scc/open_platform/data/sync/odm/bom
  • FTP
EnvironmentPartner directoryLenovo directoryFile name
Test/Planning/SCC/{appName}/odm/bom//Planning/SCC/{appName}/odm/bom/feedback/bom_{crud}_{yyyyMMddHHmmss}_
Prod/Planning/SCC/{appName}/odm/bom//Planning/SCC/{appName}/odm/bom/feedback/bom_{crud}_{yyyyMMddHHmmss}_

Sample:/Planning/SCC/LCFC/odm/bom/bom_update_20220928123000_001

Request data description

ParamKeyField TypeLengthRequiredPCG-NBISGMBG-MoblieMDSC-TBPCG-Smart DevicePCG-DockingPCG-DTDescriptionExample
uidString32unique id
buYString50YYYYYYYYThinkNB/IdeaNB/ThinkDT/IdeaDTThinkNB
odmYString100YYYYYYYYODM nameLCFC
odm_father_itemYString20YYYYYYYYODM father item part number712801000000
father_itemString50YYYYYYYYLenovo father item part numberSA78D09909
odm_child_itemYString20YYYYYYYYODM child item part numberBLXSC28C60966
child_itemString50Lenovo child item part numberSC28C60966
quantity_perNumber10.6YYYYYYYYusage num in father item100
effective_start_dateDateYYYYYYYYBOM effective start time2000-08-01
effective_end_dateDateYYYYYYYYBOM effective end time2000-08-01
priorityInteger3YYYYYYYYpriority of alternative item2
alternative_codeYString50YYYYYYYYalternative code34
splitNumber1.2split in bom0.2
versionString14YYYYYYYYversion. in format: yyyyMMddHHmmss20220801152347
remarkString200remark
comment1String100reserved field
comment2String100reserved field

Response data description

ParamTypeDescription
codeString0: success, others:failed
msgStringthe detail message, especially useful on failure

Request sample

json
{
  "batch_id": "10197",
  "batch_size": 1,
  "seq_id": "1",
  "seq_size": 1,
  "data": [
    {
      "bu": "ThinkNB",
      "odm": "LCFC",
      "odm_father_item": "712801000000",
      "father_item": "SA78D09909   ",
      "odm_child_item": "BLXSC28C60966",
      "child_item": "SC28C60966   ",
      "quantity_per": "100",
      "effective_start_date": "2022-08-01",
      "effective_end_date": "2022-08-01",
      "priority": "2",
      "alternative_code": "34",
      "split": "0.2",
      "version": "20220801152347",
      "remark": "self input",
      "comment1": "",
      "comment2": ""
    }
  ]
}

Success response sample

json
{
  "code": "0",
  "msg": "request success"
}

Fail response sample

json
{
    "code": "E00V00",
    "msg": "data verification failed!",
    "result": [{
        "row": {
            "odm": "LCFC",
            ...
        },
        "verify": [{
            "type": "value length exceed",
            "fields": "version"
        }]
    }]
}