Demand & Supply

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

frequency	time	data amount
Weekly	1st version Before 18:00 for Mon 2nd version Before 12:00 for Tue Final version Before 18:00 Tue	Weekly version of data(full amount)

• API

Env	URL
test	https://api-cn-t.lenovo.com/uat/v1.0/supply_chain/scc/open_platform/data/sync/ems/demand_supply
prd	https://api-cn.lenovo.com/v1.0/supply_chain/scc/open_platform/data/sync/ems/demand_supply

business data description

Field	key	Field type	Field Length	Dixon Required Field	LCFC Required Field	Description	Example
fcst_version	Y	String	8	Y	Y, copy	Fcst version, the Monday of the week when LNV publish box/sbb demand	20230313
bu	Y	String	50	Y	Y, copy	Lenovo business unit, follow the BU data received in LNV box/sbb demand	ThinkNB
site	Y	String	50	Y	Y, copy	DIXON	DIXON
odm	Y	String	40	Y	Y, copy	DIXON	LCFC
family	Y	String	6000	Y	Y, copy	FAMILY1, match with Lenovo Box demand info	T14S_2_TIGER
upper_material		String	20000	Y	Y, copy	SBB1/SBB2/…	SBB1/SBB2/…
commit_type	Y	String	10	N/A - for demand publish to LCFC. Y - for the Commit(ETA) provide to LNV.	Y	PART: indicate the part has no risk. Dixon can expect there's no shortage for the part should the demand pull in / upside.PART1: indicate the part has risk of shortage. Dixon need to use the exact supply feedback to run its later planning process.MB: the MB suppply plan provided by Dixon. MUST be considered in LNV box commit.	Part
material_type		String	10	Y	Y, copy	Follow material master data definition: DB/DS/SFG
commodity		String	50	N/A	Y	Follow material master data definition	ME-D Cover
ems_pn	Y	String	1000	Y	Y, copy	EMS PN	AM1U8000300
ems_pn_desc		String	100	Y	Y, copy	EMS PN Description	HX4B0_D_COVER_ASSY_WLAN_AL
lenovo_pn		String	100	Y	Y, copy	Lenovo PN
mfg_pn		String	200		Y	Manufacturer Part Number
odm_supplier_name	Y	String	2000	LCFC	Y, copy	ODM Original supplier
alternative_code		String	50	Y	Y	LCFC provide unique identification based on the PNs covered - dynamic changing every time.	34840
boh_ooi_raw		Number	10,2	Y	Y, copy	DBDS parts inventory at the time of LNV MRP snap make whole the demand/supply scope, all including the WIP.
boh_ooi_sfg		Integer	10	Y	Y, copy	SFG parts inventory at the time of LNV MRP snap make whole the demand/supply scope, all including the WIP.
boh_ooi_fg		Integer	10	Y	Y, copy	FG parts inventory at the time of LNV MRP snap make whole the demand/supply scope, all including the WIP.
boh_vmi		Integer	10	0
otw		Integer	10	Y	Y, copy	on the way. Intransit qty at the time of LNV MRP snap.
booking_qty		Integer	10	0
lead_time		Integer	10	0
eff_start_date		Date	10			Data cutoff date	2022-01-01
measure_list		Array		Y	Y
measure	Y	String	20	Y	Y	Demand (Dixon→LCFC) ETD (LCFC→ Dixon) ETA (Dixon → LNV)	Demand
date_list		Array		Y	Y
date	Y	Date		Y	Y	Demand date or supply date - depending on the scenario.	2022-01-01
date_qty		Integer	10	Y	Y	Demand qty or supply qty.	100
remark		String	200
version		String	14	Y	Y	Dixon/LCFC system auto generated timestamp.	20220800000000
comment1		String	100
comment2		String	100

request sample

{
	"batch_id": "90497",
	"batch_size": 1,
	"seq_id": "1",
	"seq_size": 1,
	"data": [{
		"fcst_version": "20230313",
		"bu": "ThinkNB",
		"site": "DIXON",
		"odm": "DIXON",
		"family": "T14S_2_TIGER",
		"upper_material": "SBB1",
		"commit_type": "Part",
		"material_type": "DB",
		"commodity": "ME-D Cover",
		"ems_pn": "AM1U8000300",
		"ems_pn_desc": "HX4B0_D_COVER_ASSY_WLAN_AL",
		"lenovo_pn": "LE2T8300301",
		"mfg_pn": "MFGU8202601",
		"odm_supplier_name": "KCS",
		"alternative_code": "AM2U8000301",
		"boh_ooi_raw": "40",
		"boh_ooi_sfg": "1",
		"boh_ooi_fg": "2",
		"boh_vmi": "90",
		"otw": "34",
		"booking_qty": "6000",
		"lead_time": "13",
		"measure_list": [{
			"measure": "Demand",
			"date_list": [{
					"date": "2022-01-01",
					"date_qty": "100"
				},
				{
					"date": "2022-01-02",
					"date_qty": "100"
				}
			]
		}],
		"remark": "",
		"version": "20220800000000",
		"comment1": "",
		"comment2": ""
	}]
}

success response sample

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

failed response sample

{
    "code": "E00V00",
    "msg": "data verification failed！",
    "result": [{
        "row": {
            "ems": "DIXON",
            ...
        },
        "verify": [{
            "type": "value length exceed",
            "fields": "version"
        }]
    }]
}