Create B2B messages
post
/fscmRestApi/resources/11.13.18.05/b2bMessages
Request
Header Parameters
-
AgentID:
This is the service provider ID if a service provider is used to send B2B messages, for example, XYZ Service Provider. If Agent information isn't passed as a header, it's assumed that no service provider is being used, that is, the value for service provider is None.
-
AgentIDType:
This is the type of service provider ID if a service provider is used to send B2B messages, for example, Name. If Agent information isn't passed as a header, it's assumed that no service provider is being used, that is, the value for service provider is None.Example:
Name
-
Content-Type(required):
Specifies the type of content being sent to the server. The valid value is application/xml.Example:
[ "application/xml" ]
-
DocumentType(required):
Type of document that's being sentExample:
[ "AcknowledgeChangePurchaseOrder", "AcknowledgePurchaseOrder", "SupplyPlanningData", "AcknowledgeInvoice", "ProcessForecast", "SupplyForecast", "AcknowledgeReceiptAdvice", "ProcessInvoice", "ProcessShipment", "ProcessReceiptAdvice", "ProcessPurchaseOrder", "ChangePurchaseOrder", "CancelPurchaseOrder", "CreditNote" ]
-
Prefer:
Prefer is an optional header. If the Prefer header is specified with the value respond-async, the service will process the request asynchronously. If the Prefer header is not included, the response will be handled synchronously.Example:
respond-async
-
SenderID(required):
This is the ID of the party that's sending the B2B message; the trading partner ID, for example, ABC Company.
-
SenderIDType(required):
This is the type of ID of the party that's sending the B2B message; the trading partner ID type, for example, Name.Example:
[ "Generic", "DUNS", "Direct", "GLN", "MISC", "NetworkID", "Name", "PHONE", "TAXID" ]
Supported Media Types
- application/xml
Nested Schema : ApplicationArea
Type:
Show Source
object
-
BODID: string
Business Object Document IDExample:
EXT_MSG_ID
-
CreationDateTime: string
(date-time)
Date and time of creationExample:
2017-03-01T00:00:00.000Z
-
Receiver: object
Receiver
-
Sender: object
Sender
Nested Schema : Sender
Type:
Show Source
object
-
LogicalID: string
Sender logical IDExample:
IND_BOD_TP
Nested Schema : Process
Type:
object
Nested Schema : InvoiceHeader
Type:
Show Source
object
-
DocumentDateTime: string
(date-time)
Document date and timeExample:
2017-03-01T00:00:00.000Z
-
Extension: object
Extension
-
ID: string
Invoice IDExample:
PZ1
-
ShipToParty: object
ShipToParty
-
TotalAmount: number
Total invoice amountExample:
50
Nested Schema : InvoiceLine
Type:
Show Source
object
-
ExtendedAmount: number
Extended amount for the lineExample:
61.5
-
InvoiceCharge: object
InvoiceCharge
-
PurchaseOrderReference: object
PurchaseOrderReference
-
Quantity: number
Quantity of the itemExample:
1
-
TotalAmount: number
Total amount for the invoice lineExample:
61.5
-
UnitPrice: object
UnitPrice
Nested Schema : Extension
Type:
Show Source
object
-
typeCode: string
Example:
DFF
-
ValueText: string
Example:
One-Time
Nested Schema : Location
Type:
Show Source
object
-
ID: string
Ship to location ID (e.g., 'GE-PM_HQ')Example:
GE-PM_HQ
Nested Schema : PurchaseOrderReference
Type:
Show Source
object
-
ID: string
Purchase order reference IDExample:
1002531
-
LineIDSet: object
LineIDSet
-
LineNumberID: string
Line number IDExample:
1
Response
Supported Media Types
- application/xml
200 Response
Successful Processing
Root Schema : jsonErrorResponse
Type:
Show Source
object
-
error: array
error
-
messageGuid: string
A unique identifier for the message, null if the request failed.
-
result: string
The result of the operation, indicating either "ERROR" or "SUCCESS".
202 Response
Request has been accepted for processing, but processing has not been completed or may not have started.
Root Schema : jsonErrorResponse
Type:
Show Source
object
-
error: array
error
-
messageGuid: string
A unique identifier for the message, null if the request failed.
-
result: string
The result of the operation, indicating either "ERROR" or "SUCCESS".
400 Response
Bad Request - Various Error Scenarios
Root Schema : xmlErrorResponse
Type:
Show Source
object
-
error: array
error
-
result: string
The result of the operation, indicating either "ERROR" or "SUCCESS".
401 Response
Invalid User - Unauthorized
403 Response
User is Not Authorized
415 Response
Unsupported Media Type
500 Response
Internal Server Error