Take.API

<back to all web services

ProblemModelRequest

The following routes are available for this service:
GET,POST/problem/SearchProblemById根据问题件编号获取问题件信息
ProblemModelRequest Parameters:
NameParameterData TypeRequiredDescription
IDbodyintNo主键
ProblemModelResponse Parameters:
NameParameterData TypeRequiredDescription
ProblemModelformProblemInfoYes问题件信息
ResponseBase Parameters:
NameParameterData TypeRequiredDescription
ErrorCodeformintYes返回编码,200之外的值都表示有错误
ErrorMsgformstringYes返回的消息
ProblemInfo Parameters:
NameParameterData TypeRequiredDescription
IDformintYes主键
PrepareIDformintYes配货详情ID
ProblemIDformstringYes问题件编号
RouteIDformstringYes提货路线编号
YBookingNumberformstringYes原商品订单编号
NBookingNumberformstringYes现商品订单编号
ProblemTypeformintYes问题件类型(0:重新下单,没有原订单号 1:重新下单,之前订单作废 2:保留原单,创建新的订单 3:保留原单,修改原单箱数 4:合并订单,绑定新的订单)
YBoxNumberformint?Yes原订单箱数
NBoxNumberformint?Yes现订单箱数
ProblemNumberformintYes问题商品箱数
ProblemCubeformfloatYes问题件总立方(单位立方)
ProblemWeightformfloatYes问题件总毛重(单位KG)
RemarksformstringYes问题描述
CreateByformstringYes创建人
CreateDTformDateTimeYes创建时间

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/ProblemModelRequest HTTP/1.1 
Host: bookinglogin.hart-worldwide.com 
Content-Type: application/xml
Content-Length: length

<ProblemModelRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/WinJo.Framing.DTO">
  <ID>0</ID>
</ProblemModelRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<ProblemModelResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/WinJo.Framing.DTO">
  <ErrorCode>0</ErrorCode>
  <ErrorMsg>String</ErrorMsg>
  <ProblemModel>
    <CreateBy>String</CreateBy>
    <CreateDT>0001-01-01T00:00:00</CreateDT>
    <ID>0</ID>
    <NBookingNumber>String</NBookingNumber>
    <NBoxNumber>0</NBoxNumber>
    <PrepareID>0</PrepareID>
    <ProblemCube>0</ProblemCube>
    <ProblemID>String</ProblemID>
    <ProblemNumber>0</ProblemNumber>
    <ProblemType>0</ProblemType>
    <ProblemWeight>0</ProblemWeight>
    <Remarks>String</Remarks>
    <RouteID>String</RouteID>
    <YBookingNumber>String</YBookingNumber>
    <YBoxNumber>0</YBoxNumber>
  </ProblemModel>
</ProblemModelResponse>