Skip to content

demand_supply

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

Request address

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

Request data description

ParamkeyTypeRequiredLengthDescription
uidString32unique id
buYStringY50business unit
odm_or_t1_supplierStringY200ODM/T1 name
vendor_codeYStringY30vendor code
vendor_nameString60TN vendor csite
vendor_siteString20
t1_lenovo_pnString200
tn_lenovo_pnString200
tn_vendor_pnString200
alt_group_nameString20
original_mfg_pnString200origin manufacturing part no
mfg_pn_descString20origin manufacturing part no description
inventory_qtyNumber13,3
inventory_dateDateformat: yyyy-mm-dd
bps_qtyNumber13,3shortage quantity
bps_dateDateshortage cut off time,eg:2022-10-17
measure_listYlistmeasure collection
measureYStringY20Demand、Supply、Gap
flagString20
dayYDateYBy Daily
day_qtyYNumberY13,3
versionYStringY8version(YYYYMMDD)

Response data description

ParamTypeRequiredDescription
codeStringY0:successful, other:failed
msgStringYmessage

Request sample

json
{

  }

Successful response sample

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

Failed response sample

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