demand_supply
This interface is applicable for data integration API, read Api Access Process first
Request address
- API
- FTP
Environment | Partner directory | Lenovo directory | File 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
Param | key | Type | Required | Length | Description |
---|---|---|---|---|---|
uid | String | 32 | unique id | ||
bu | Y | String | Y | 50 | business unit |
odm_or_t1_supplier | String | Y | 200 | ODM/T1 name | |
vendor_code | Y | String | Y | 30 | vendor code |
vendor_name | String | 60 | TN vendor csite | ||
vendor_site | String | 20 | |||
t1_lenovo_pn | String | 200 | |||
tn_lenovo_pn | String | 200 | |||
tn_vendor_pn | String | 200 | |||
alt_group_name | String | 20 | |||
original_mfg_pn | String | 200 | origin manufacturing part no | ||
mfg_pn_desc | String | 20 | origin manufacturing part no description | ||
inventory_qty | Number | 13,3 | |||
inventory_date | Date | format: yyyy-mm-dd | |||
bps_qty | Number | 13,3 | shortage quantity | ||
bps_date | Date | shortage cut off time,eg:2022-10-17 | |||
measure_list | Y | list | measure collection | ||
measure | Y | String | Y | 20 | Demand、Supply、Gap |
flag | String | 20 | |||
day | Y | Date | Y | By Daily | |
day_qty | Y | Number | Y | 13,3 | |
version | Y | String | Y | 8 | version(YYYYMMDD) |
Response data description
Param | Type | Required | Description |
---|---|---|---|
code | String | Y | 0:successful, other:failed |
msg | String | Y | message |
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"
}]
}]
}