Skip to content

Universal data synchronization FTP solution

A unified FTP solution for partners to synchronize data to Lenovo. Please understand the FTP access process before connecting.

File Directory

  • After determining the integration solution, Lenovo will allocate the corresponding file directory
EnvironmentService AddressPartner Send File DirectoryLenovo Send File DirectoryFile Name
Test***.lenovo.com/Planning/SCC/{appName}/{data_category}/{biz_key}//Planning/SCC/{appName}/{data_category}/{biz_key}/feedback /{biz_key}_{crud}_{yyyyMMddHHmmss}_
Official***.lenovo.com/Planning/SCC/{appName}/{data_category}/{biz_key}//Planning/SCC/{appName}/{data_category}/{biz_key}/feedback /{biz_key}_{crud}_{yyyyMMddHHmmss}_

Public directory parameters

Parameter locationParameter nameDescriptionExample
PathappNamePartner Short NameFixed Assignment
Pathdata_categoryData classificationODM, T1, TN, etc., specific business interfaces are fixedly allocated
File namebiz_keyBusiness data nameFixed allocation of specific business interfaces
File namecrudSynchronization typeFull coverage: all (clear historical data, then write current data), add: insert, modify: update, delete: delete
File nameyyyyMMddHHmmssTime20221001003000
file nameserialdaily flowmainly to avoid duplication

Public request parameters

PositionNameRequiredTypeLengthDescription
BodyappNameString10Partner short name, optional
Bodybatch_idYString16Batch ID, generated by partners to ensure batch uniqueness
Bodybatch_sizeYNumber---Total amount of data in the batch
Bodyseq_idYStringWithin the batch, each sequence number
Bodyseq_sizeYNumber---Each time, the amount of data to be pushed 5000 >= size >= 1

Public response parameters

LocationNameRequiredTypeFormatDescriptionExample
BodycodeYString---Status code"0" represents success, other failures can refer to the return code
BodymsgNString---Prompt messageIf it is not "0", an error message will be prompted
BodyresultNobject/array---data body
BodyrowNobject---original data row
BodyverifyNobject---Specific error fields and error reasons
  • Request example
json
{
  "batch_id": "LCFC202206230001",
  "batch_size": "250000",
  "seq_id": "1",
  "seq_size": "2",
  "data": [
    {
      "LENOVO_PN": "SD10W87241",
      "PLANT": "H121",
      "QTY": "1000"
    },
    {
      "LENOVO_PN": "SD10W87241",
      "PLANT": "H121",
      "QTY": "1000"
    }
  ]
}
  • Response example
json
{
  "code": "0",
  "msg": "request success"
}
  • Exception examples
json
{
  "code": "E00V00",
  "msg": "data verification failed!",
  "result": [
    {
      "row": {
        "odm": "LCFC",
        "odm_pn": "45109112310",
        "location": "1234",
        "version": "20220915080100123456"
      },
      "verify": [
        {
          "type": "value length exceed",
          "fields": "version"
        }
      ]
    }
  ]
}