Sign In |Help & Support
ALL SECTORS
  • ALL SECTORS
  • GB(National Standard)
  • CB(Shipping)
  • CECS(Engineering Construction)
  • CJ(Urban Construction)
  • CY(News and Publication)
  • DB(Provincial Standard)
  • DL(Electricity & Power)
  • DZ(Geology & Mineralogy)
  • FZ(Spinning & Textile)
  • GA(Public Security)
  • HB(Aviation)
  • HG(Chemical Industry)
  • HJ(Environmental Protection)
  • JB(Machinery)
  • JC(Building Materials)
  • JG(Building & Construction)
  • JJ(Metering)
  • JT(Highway & Transportation)
  • LY(Forestry)
  • MT(Coal)
  • NB(Energy)
  • NY(Agriculture)
  • QB(Light Industry)
  • QC(Automobile & Vehicle)
  • QJ(Aerospace)
  • SH(Petrochemical)
  • SJ(Electronics)
  • SL(Water Resources)
  • SN(Commodity Inspection)
  • SY(Oil & Gas)
  • TB(Railway & Train)
  • YB(Ferrous Metallurgy)
  • YC(Tobacco)
  • YD(Telecommunication)
  • YY(Medical Device)
Database: 365,228(8 Aug 2026)
business association replenishment request class replenishment request identifier replenishment request messages confirmed replenishment request replenishment request introduction standard overview table application replenishment request status code example canine antirust plastic films inflow → data fusion → data mining → data outflow
GB/T 35399-2017 in English

GB/T 35399-2017 in English

VALID

ebXML based replenishment request

  • Issued on:2017-12-29
  • Implemented on:2018-07-01
  • File Format:PDF
  • Delivery:Via email within 5 business days
Price(USD): $670.00
$650.00
Standard No: GB/T 35399-2017
Document status: VALID
Title in English: ebXML based replenishment request
Title in Chinese: 基于ebXML的补货请求
Language: English
File Format: Electronic (PDF)
Delivery: Via email within 5 business days
Issued on: 2017-12-29
Implemented on: 2018-07-01
Professional Classification: GB-National Standard
Related Keywords: business association replenishment request class replenishment request identifier
replenishment request messages
confirmed replenishment request
replenishment request introduction standard overview
table application replenishment request status code example
Related Topics: ask
GBT35399
GB/T 35399-2017

《GB/T 35399-2017基于ebXML的补货请求》由TC267(全国物流信息管理标准化技术委员会)归口,主管部门为国家标准化管理委员会。


Introduction

Standard Overview and Technical Background

This standard was proposed by the National Logistics Information Management Standardization Technical Committee (SAC/TC267) and specifies the structured specification of replenishment request messages based on ebXML in logistics information exchange. As a supporting implementation standard of GB/Z 25114.1-2010, its technical architecture inherits the core framework of ebXML business messages.


Analysis of the core class diagram system

Class diagram name Core attributes Business association
Replenishment request class Replenishment request identifier, type code Associated buyer/seller, item location information
Transaction participant class Global Location Number (GLN), address information Support for financial institutions, tax registration and other extensions
Inventory status line item Line item number, inventory status type Associate specific locations and trade items

Key code table application

Replenishment request status code example

When the buyer sends the COMMITTED status, it indicates a confirmed replenishment request; the PLANNED status is used for predictive replenishment planning. This code definition must be strictly mapped to the state machine of the ERP system inventory module.

Inventory status code application

QUARANTINED status identifies inventory to be inspected and is linked to the quality isolation area of the WMS system; the RESTRICTED_USE status is suitable for special management scenarios of expiring goods.


Key points for message implementation

  1. Structure selection: Select ITEM_BY_LOCATION or LOCATION_BY_ITEM structure type according to the business scenario
  2. Time processing: The DateTimeRange class must contain both beginDate/endDate and an optional timestamp
  3. Identification system: The GS1 standard GTIN (trade item) and GLN (party location) identifiers are mandatory

Standard evolution analysis

Compared with early EDI standards, this standard achieves the following through ebXML:

  • Structured class diagrams replace flat file formats
  • UML modeling ensures business semantic accuracy
  • Deep integration with the GS1 identification system

Sample only — not a preview of GB/T 35399-2017
Page: 1 / 0
100%

Loading PDF document...

Error loading PDF. Please make sure the file is valid and try again.

We also recommend