Set "OrderQuantity" to 100;
Set "Strike Price" to 101.5;
Set "Ticker Symbol" to "AAPL"
Set "Side of Order" to 1;
Set "Message SenderID" to A500;
Set "Message ReceivedID" to B500;
Create Output;
Store Document;
So where is the actual FIX Code?
Where are the different FIX tags like 55,461,453 etc?
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any version of FIX including 4.0, 4.1,4.2,5.0 etc;
The correct FIX output will be produced, irrespective of the order in which the
fields are set by the programmer resulting in higher quality
Set "Message Identifier" to FX100M100;
Set "Sender Party" to MAT500;
Set "Receiver Party" to REC300;
Set "Side of Order" to 1;
Set "Message SenderID" to A500;
Set "Message ReceivedID" to B500;
Create Output;
Store Document;
Where are the different XML tags like executionAdvice/termination/payment/
paymentAmount/currency?
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any version of FpML including 4.0, 4.1,4.2,5.0,5.5 etc;
The correct FpML output will be produced, irrespective of the order in which the
fields are set by the programmer resulting in higher quality
Set "Application Id" to F;
Set "ServiceId" to 01;
Set "Logical Terminal" to EBCFC1002;
Set "SessonNumber" to 0000;
Set "Sequence Number" to 50000000002;
Set "Message Type" to 101;
Set "Receiver Address" to ECBFDET0XXXX;
Set "Message Priority" to 1;
Set "Delivery Monitoring" to 1;
Set "Country"="TownName"+","+"Country"
Create Output;
Store Document;
So where is the actual SWIFT Code?
Where are the different SWIFT tags like Field51A, Field32B, Field56D?
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any SWIFT version required by your partner or Central Bank;
The correct SWIFT output will be produced, irrespective of the order in which the
fields are set by the programmer resulting in higher quality
Set "MessageIdentification" to F;
Set "CreationDateTime" to Current Time;
Set "Number of Transactions" to 5;
Set "Total InterBank Settlement Amount" to 1000;
Set "Total InterBank Settlement Amount Currency" to EUR;
Set "Settlement Method" to CLRG;
Set "End to End Identification" to A500;
Set "Clearing System Id" to KBC;
Set "InterBank Settlement Date" to 2014-10-10;
Create Output;
Store Document;
So where is the actual SEPA Code?
Where are the different SEPA XML elements like FIToFICstmrCdtTrf, TtlIntrBkSttlmAmt
and CdtTrfTxInf?
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any SEPA version required by your partner or Central Bank;
The correct SEPA output will be produced, irrespective of the order in which the
fields are set by the programmer resulting in higher quality
Set "Transaction Type" to Illustration Request;
Set "Transaction Execution Date" to Current Time;
Set "Illustration Request Image Type" to PDF;
Set "Line of Business" to Life;
Set "Policy Status" to Approved;
Set "Party FirstName" to Rhonda;
Set "PartyGender" to Female;
Set "Product Code" to 801;
Set "Payment Mode" to OLI_PAYMODE_MNTHLY;
Create Output;
Store Document;
So where is the actual Acord Code?
Where are the different Acord XML elements like TXLife, Producer , FirmName?
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any Acord version required by you or your partner;
The correct Acord output will be produced, irrespective of the order in which the
fields are set by the programmer resulting in higher quality
Set "Purchase Order Number"to ABC5000;
Set "Purchase Order Date" to 2014/10/12
Set "Buyer Party Name" to Acme Buyer;
Set "Seller Party Name"to Acme Seller;
Set "Item Description" to IPhone 6 Plus;
Set "Buyer Item Code" to IPHONE6P
Set "Item Quantity" to 1000
Set "Item UOM" to EA;
Create Output;
Store Document;
So where is the actual SAP Code?
Where are the different SAP IDOC tags like E1EDKA1, E1EDP01, E1EDP02
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any SAP IDOC version required by your partner.
The correct SAP IDOC output will be produced, irrespective of the order in
which the fields are set by the programmer resulting in higher quality
Set "Purchase Order Number"to ABC5000;
Set "Purchase Order Date" to 2014/10/12
Set "Buyer Party Name" to Acme Buyer;
Set "Seller Party Name"to Acme Seller;
Set "Item Description" to IPhone 6 Plus;
Set "Buyer Item Code" to IPHONE6P
Set "Item Quantity" to 1000
Set "Item UOM" to EA;
Create Output;
Store Document;
So where is the actual xCBL Code?
Where are the different xCBL tags like OrderHeader, OrderParty, BaseItemDetail
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any xCBL version required by your partner.
The correct xCBL output will be produced, irrespective of the order in
which the fields are set by the programmer resulting in higher quality
Set "Document Identifier"to ABC5000;
Set "Order Issue Date Time" to 2014/10/12
Set "BillTo Name" to Acme Buyer;
Set "ShipTo Name"to Acme Seller;
Set "Supplier Item Description" to ABC;
Set "Item Part Number" to ABC3000
Set "Item Quantity" to 1000
Set "Item UOM" to EA;
Create Output;
Store Document;
So where is the actual Ariba cXML Code?
Where are the different cXML tags like OrderRequest,
OrderRequestHeader, UnitPrice etc?;
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce the correct Ariba cXML, irrespective of the order in
which the fields are set by the programmer resulting in higher quality
Set "Purchase Order Number"to ABC5000;
Set "Purchase Order Date" to 2014/10/12
Set "Buyer Party Name" to Acme Buyer;
Set "Seller Party Name"to Acme Seller;
Set "Item Description" to IPhone 6 Plus;
Set "Buyer Item Code" to IPHONE6P
Set "Item Quantity" to 1000
Set "Item UOM" to EA;
Create Output;
Store Document;
So where is the actual EDI/X12 Code?
Where are the different X12 Segments like ST, BEG,N1,N2,N3,PO1?
MOND Encapsulates the field definitions for you, enabling you to separate
the business logic from the data format.
With this encapsulation, the above code can be used
to produce any X12 version required by your partner.
The correct X12 output will be produced, irrespective of the order in
which the fields are set by the programmer resulting in higher quality
MOND is used to manage the supply chain of some of the most well known brands in the industry.
In 2014, MOND Cloud has provided 99.99% availability at no extra cost to our customers.
Whether it is on-premise or Cloud, MOND provides a proven rock-solid high performance platform that ensures secure transactions and access to
mission critical business processes and data.
The best way to start learning MOND is to work through the tutorial.
Begin tutorial