Material Document Data

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

Scenario

• ODM inventory transfer, and ODM HUB information are required during calculation of ETA Accuracy
• Such as: converting defective products into good products & ODM HUB GR, etc.

Request address

• API

Environment	URL
Test	https://api-cn-t.lenovo.com/uat/v1.0/supply_chain/scc/open_platform/data/sync/odm/material_doc
Prod	https://api-cn.lenovo.com/v1.0/supply_chain/scc/open_platform/data/sync/odm/material_doc

• FTP

Environment	Partner directory	Lenovo directory	File name
Test	/Planning/SCC/{appName}/odm/material_doc/	/Planning/SCC/{appName}/odm/material_doc/feedback/	material_doc_{crud}_{yyyyMMddHHmmss}_
Prod	/Planning/SCC/{appName}/odm/material_doc/	/Planning/SCC/{appName}/odm/material_doc/feedback/	material_doc_{crud}_{yyyyMMddHHmmss}_

Sample：/Planning/SCC/LCFC/odm/material_doc/material_doc_update_20220928123000_001

Frequency	Time	Data amount
Daily or Real time	00:00:00	Daily version of data(Incremental)

Request data description

Param	Key	Type	Required	Length	Description	Example
uid		String		32	Unique id
odm	Y	String	Y	40	ODM name	LCFC
bu	Y	String	Y	50	business unit	ISG
moving_track_number	Y	String	Y	50	moving track number	****
odm_pn		String	Y	1000	ODM part number	****
odm_pn_desc		String	Y	1000	ODM part number description	XXXX
lenovo_pn		String		100	Lenovo part number	****
material_type		String	Y	10	DB/DS/BS/RB	DS
mfg_pn		String		1000	Manufacturing part number	XXX
qty		Number	Y	13,3	moving quantity	100
movement_date		Date	Y		movement date	2022-08-01 00:00:00
movement_type		String	Y	10	movement type：BTG/HUB IN/HUB OUT/GTB/V_GTB/V_BTG/V_TSF_IN/V_TSF_OUT
commodity		String	Y	50	commodity
odm_desc		String		500	ODM description	****LIMITED
version		String	Y	14	version in format yyyyMMddHHmmss	20220809070623
comment1		String		100	reserved field
comment2		String		100	reserved field
comment3		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

{
  "batch_id": "90497",
  "batch_size": 1,
  "seq_id": "1",
  "seq_size": 1,
  "data": [
    {
      "odm": "odm_1",
      "bu": "ISG",
      "moving_track_number": "6901027745",
      "odm_pn": "****",
      "odm_pn_desc": "ODM 物料描述",
      "lenovo_pn": "****",
      "material_type": "DB",
      "mfg_pn": "HG21100014",
      "qty": "10",
      "movement_date": "2022-09-15",
      "movement_type": "BTG",
      "commodity": "commodity",
      "odm_desc": "GOLDWINTRADING(HK)LIMITED",
      "version": "20220809070600",
      "comment1": "",
      "comment2": "",
      "comment3": ""
    }
  ]
}

Successful response sample

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

Failed response sample

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