ASN Data
This interface is applicable for data integration API, read Api Access Process first
Request address
- API
Environment | URL |
---|---|
Test | https://api-cn-t.lenovo.com/uat/v1.0/supply_chain/scc/open_platform/data/sync/odm/asn |
Prod | https://api-cn.lenovo.com/v1.0/supply_chain/scc/open_platform/data/sync/odm/asn |
- FTP
Environment | Partner directory | Lenovo directory | File name |
---|---|---|---|
Test | /Planning/SCC/{appName}/odm/asn/ | /Planning/SCC/{appName}/odm/asn/feedback/ | asn_{crud}_{yyyyMMddHHmmss}_ |
Prod | /Planning/SCC/{appName}/odm/asn/ | /Planning/SCC/{appName}/odm/asn/feedback/ | asn_{crud}_{yyyyMMddHHmmss}_ |
Sample:/Planning/SCC/LCFC/odm/asn/asn_update_20220928123000_001
Frequency | Time | Data amount |
---|---|---|
Real Time | 0.00 | Daily |
Note:ODM's supplier ships DBDS material ASN information to ODM
ODM, as a supplier of Lenovo in house factory and remote site, needs to provide the shipping ASN reference T-1 BSR in SA&V scope
Request data description
TIP
Note: field requirements are different on bu, please refer to the following table
Param | Key | Type | default required | PCG-NB | ISG | Length | Descripton | Example |
---|---|---|---|---|---|---|---|---|
uid | String | 32 | Unique id | |||||
asn | Y | String | Y | Y | Y | 20 | ASN | 809*****20600 |
asn_line | Y | String | Y | Y | Y | 10 | ASN item Line | |
bu | String | Y | Y | Y | 50 | business unit | ||
odm | Y | String | Y | Y | Y | 40 | odm name | |
po | String | Y | Y | Y | 10 | purchase order | 752*****95 | |
po_line | String | Y | Y | Y | 6 | purchase order Line | 0 | |
odm_pn | String | Y | Y | Y | 20 | ODM part number | ||
odm_pn_desc | String | Y | 240 | ODM part number description | ||||
mfg_pn | String | Y | Y | Y | 200 | manufacturing part number | ||
lenovo_pn | String | Y | Y | Y | 18 | lenovo part number | ||
material_type | String | Y | Y | Y | 10 | BS/DS/DB | ||
procurement_mode | String | Y | Y | Y | 10 | VMI/Ship to ODM | ||
status | String | Y | Y | Y | 10 | Closed/Open/Cancel/Delete | Open | |
delivery_note | Y | String | Y | Y | Y | 100 | Delivery note number | 8*****01 |
delivery_line | Y | String | Y | Y | Y | 50 | Delivery line number | 0 |
delivery_qty | Integer | Y | Y | Y | 10 | delivery quantity | 0 | |
updated_eta | Date | Y | Y | Y | updated estimate time of arrival | 2022-06-24 | ||
eta | Date | Y | Y | Y | origin etiamate time of arrival | 2022-06-24 | ||
ship_date | Date | Y | Y | Y | ship date | 2022-06-24 | ||
version | String | Y | Y | Y | 14 | version yyyyMMddHHmmss | 20220809070600 | |
comment1 | String | 100 | reserved field | |||||
comment2 | String | 100 | reserved field |
Response data description
Param | Type | Description |
---|---|---|
code | String | 0: success, others:failed |
msg | String | the detail message, especially useful on failure |
Request sample
json
{
"batch_id": "90397",
"batch_size": 1,
"seq_id": "1",
"seq_size": 1,
"data": [
{
"asn": "8098*****0220622",
"asn_line": "1",
"bu": "ThinkNB",
"odm": "*****",
"po": "752*****895",
"po_line": "10",
"odm_pn": "****",
"odm_pn_desc": "odm_pn_desc述",
"mfg_pn": "mfgpn",
"lenovo_pn": "****",
"material_type": "DS",
"procurement_mode": "VMI",
"status": "Open",
"delivery_note": "809*****801",
"delivery_line": "1",
"delivery_qty": "0",
"updated_eta": "2022-06-24",
"eta": "2022-06-24",
"ship_date": "2022-06-22",
"version": "20220809070600",
"comment1": "",
"comment2": ""
}
]
}
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"
}]
}]
}