You are on page 1of 3

String Srl

v. Ciclamini, 6 20147 Milano Italy


+39.02.5832.7335

www.string.it
info@string.it

XML OrderList Format Description


This document describes the format of files containing orders coming from an ERP to be imported into
JobManager by means of the standard Import Order feature. You must be familiar with the
JobManager terminology and the XML language to fully understand this document.
An XML file for the Order Import contains one <OrderList> element, which is made by one or more
<Order> elements.
An <Order> must have a Code (normally the internal code of the factory), and optionally a Customer,
an OrderDate and a Deadline for delivery. Also optional is a destination job in the database.
Each <Order> is made of one or more elements of two types: <Shape> or <Article>.
A <Shape> element contains the order for one shape only, with separate Normal and Mirrored
quantities. The shapes are identified by their folder (Library) and their code (Code).
In case that there are more libraries with the same name, additional path elements can be added to
distiguish the two, (see in the examples, Season1/Model1 and Season2/Model1). An optional
MaterialCode attribute specifies the material code for the shape.
In Job Manager, shapes for subsequent versions of models are kept in parallel in subfolders of the
model; for these models, shapes from the latest version of the model are used, and the order will
specify just the model folder in the Library attribute: this to avoid the need to know which version is
the latest when producing the xml for the order.
An <Article> element contains the cutting order for all or a subset of the shapes of an article. The
article code must be unique in the database.
The attribute Quantity specifies the number of subsets that must be cut. The actual quantity for each
shape is obtained multiplying this quantity by the quantities normal and mirrored to obtain a single
item defined in the article.
To define the subset of shapes belonging to an article, two filter attributes can be used:
MaterialCodeFilter and SizeFilter.
The attribute MaterialCodeFilter selects the shapes of the article whose material code is the same.
The attribute SizeFilter selects only the shapes of that particular size. Only one size per filter can be
specified. To include more sizes, use more elements.
If no subset is identified, all the shapes of the article will be placed in the order.
Inside each <Article> element, a list of <MaterialCodeMapping> material code mappings can be
specified, so that the pieces that must be cut on a specific material will be grouped together at
production time.
For example, the two mappings:
<MaterialCodeMapping Original=Leather Actual=BlueSuede />
<MaterialCodeMapping Original=Lining Actual=SoftLining />
instruct the importer that all the pieces of the article that were assigned to MaterialCode Leather will
be actually cut on a BlueSuede leather, and the same applies to the Lining pieces, which will be cut
on SoftLining
A <MaterialCodeMapping> element is not required for each MaterialCode used in the Article. All the
pieces with no mapping will be grouped under the original MaterialCode.

XML Order List Format Specification

Rel. 1.3

28/01/2014

String Srl
v. Ciclamini, 6 20147 Milano Italy
+39.02.5832.7335

www.string.it
info@string.it

Example 1 An OrderList with Articles only


<?xml version="1.0" encoding="utf-8"?>
<OrderList>
<Order Code="Order001" Job=2013\07\04\Boston>
<Article Code="7272DS" MaterialCodeFilter=Leather SizeFilter="42" Quantity="10" >
<MaterialCodeMapping Original=Leather Actual=BlueSuede />
</Article>
<Article Code="7272DS" MaterialCodeFilter=Leather SizeFilter="43" Quantity="20">
<MaterialCodeMapping Original=Leather Actual=BlueSuede />
</Article>
<Article Code="073-b" SizeFilter="42" Quantity="30">
<MaterialCodeMapping Original=Leather Actual=BlueSuede />
</Article>
</Order>
<Order Code=" Order002" Customer=Jackobson>
<Article Code="521_INSOLE" SizeFilter="32" Quantity="10"/>
<Article Code="521_INSOLE" SizeFilter="33" Quantity="20"/>
<Article Code="521_INSOLE" SizeFilter="34" Quantity="30"/>
</Order>
</OrderList>
The order list above contains two orders (Order001 and Order002).
The Order001 requires:
10 pairs of the shapes of size 42 and 20 pairs of size 43 of the article "7272DS" that were to be cut
on Leather, to be actually cut on the material BlueSuede
30 pairs of all the parts of Article "073-b", Size "42", the parts that were to be cut on Leather to be
actually cut on the material BlueSuede, the other parts are still to be cut on the material specified in
the article.
The order Order002 requires:
10 pairs of all the shapes of the Article "521_INSOLE", Size="32"
20 pairs of all the shapes of the Article "521_INSOLE", Size="33"
30 pairs of all the shapes of the Article "521_INSOLE", Size="34"
The shapes of the second order will be cut on the material codes specified in the article.

XML Order List Format Specification

Rel. 1.3

28/01/2014

String Srl
v. Ciclamini, 6 20147 Milano Italy
+39.02.5832.7335

www.string.it
info@string.it

Example 2 Articles and Shapes


<?xml version="1.0" encoding="utf-8"?>
<OrderList Count="1">
<Order Code="Order001" Customer= OrderDate=10/06/2013 Deadline=20/07/2013 >
<Article Code="6675 T" Quantity="200" >
<MaterialCodeMapping Original=Leather Actual=BlueSuede />
</Article>
<Shape Library="Season01/Model_521" Code="7272DS" MaterialCode=BlueSuede Normal="50"
Mirrored="50"/>
</Order>
</OrderList>
This order will cut:
- 200 items of the article 6675 T, all the shapes; parts that were to be cut on leather will be cut on
BlueSuede
- 50 normal and 50 mirrored parts of the shape 7272DS in the folder Season01/Model_521; these
parts will be put together with the BlueSuede parts for the article above.

XML Order List Format Specification

Rel. 1.3

28/01/2014