Design Manager Knowledge Base
Article
|
Title/Subject: |
.SIF file specification |
|
Category: |
Design Manager Professional 6.0 |
|
Type: |
Info. |
|
Last Reviewed: |
Friday, December 02, 2005 |
|
Article ID: |
10000099 |
Header
(one per file):
SF=<Specification
File-Cross Reference>
ST=<Specification
Title>
DXMP=<Yes
or No>
Records
(repeat for each item in file):
PN=<Product
Number>
PD=<Product
Description>
MC=<Manufacturer
Code (up to 5 chars.)>
TG=<Side
mark>
QT=<Quantity>
PL=<List
Price>
S-,
S%=<Discount Percentage, i.e.: Sell Price = PL – (PL * S- * 0.01)>
P%,
B%=<Purchase/Buy Percentage, i.e.: Purchase Cost = PL – (PL * P% * 0.01)>
ON=<Option
Number>
OD=<Option
Description>
AN=<Attribute
Number>
AD=<Attribute
Description>
PV=<Product
Picture - Path and Filename of a Windows Bitmap or TIF file>
DXJC=<Project
Code>
DXJN=<Project
Name>
DXBN=<Client
Billing Name>
DXB1=<Client
Billing Addr. Line 1>
DXB2=<Client
Billing Addr. Line 2>
DXBC=<
DXBT=<
DXBZ=<Client
Billing Zip code>
DXBP=<Client
Billing Phone>
DXBX=<Client
Billing Fax>
DXBM=<Client
Billing Contact>
DXSH=<Project
Default Ship To Name>
DXS1=<Ship
To Addr. Line 1>
DXS2=<Ship
To Addr. Line 2>
DXSC=<Ship
To City>
DXST=<
Ship To State>
DXSZ=<
Ship To Zip code>
DXSP=<
Ship To Phone>
DXSM=<
Ship To Contact>
DXCN=<Project/Client
Note Line #>
DXCD=<Project/Client
Note>
DXTN=<Sender’s
tracking number>
DXPO=<Sender’s
purchase order number>
DXPC,
PB=<Purchase/Buy Cost>
DXFC=<Freight/Shipping
Cost>
DXSN=<Update
Status Code – see list below>
DXSD=<Status
Data for previous DXSN>
Notes:
- Standard
SIF files (i.e. from Giza™ or CAP) are designed to be for a single project
only but they can be for multiple projects using the DXMP, DXJC and DXJN
options. Either SF or ST is
required – Both may exist but at least one has to be present. ST is displayed to the user when they
select the file for import; if ST is not present then SF is
displayed. It is a good idea to set
ST equal to the name of the Project so the Designer importing the SIF can
select the proper Design Manager destination Project. If the file contains
information for multiple projects (“DXMP=Yes” is in the header), then it
could be equal to the Designer’s name and the date so the Designer can
tell that they are working with a current file.
- PN, PD,
MC, QT, and PL are required. The
rest are optional. ON and OD must
be paired together, AN and AD must be paired together. PN must come before all other types as
it designates the beginning of a new item, after PN the order does not
matter (except that ON-OD, AN-AD, DXSN-DXSD must be paired). When using PV to import a picture, the
default directory of the .SIF file will be assumed (i.e.: if just a
filename is specified then the program will assume that the file exists in
the same directory as the .SIF file).
- MC is an up to
five-character alphanumeric. MC is
the manufacturer code of the party that sends the bill. For example, if the merchandise is from
many vendors, but the sender of the SIF files bills the client for all
merchandise, then MC should be the same for all items—that is, a
five-character acronym for the sender.
See #7 below.
- ON and OD
are meant to be any kind if additional info that is not normally part of
the product number or description, such as color or size.
- Attributes
(AN and AD) can be any kind of notes that go along with the item. It might be a good idea to include an
attribute with the original vendor in it, since the MC entry may be the
same if the sender bills the client.
- No
entries can contain an embedded CRLF, as this is the record terminator.
- Four
character acronyms are not part of the normal SIF file format. They begin with DX (Design Manager
Extension) to allow the creator of the SIF file send additional
information specific to Design Manager.
All DX entries are optional.
- If
“DXMP=Yes” is in the file header information (denoting a multiple project
SIF file), then DXJC and DXJN will be required on each item (after each
PN). DXJC (up to 30 chars.) is the
sender’s project code and DXJN (up to 30 chars.) is the sender’s project
name (i.e.: “Smith FL Summer Home”).
These need to be included along with each item. These are used when designating multiple
projects. The first time that a new
DXJC number is encountered by Design Manager the user will be asked which
project that it corresponds to, or will be allowed to create a new project
“on the fly.” The DX acronyms for the
Designer’s client’s billing address, shipping address, and notes are
optional and need only be included after the first DXJC for that project
in the SIF file. (Because they are only used to default fields when the
user creates a new project “on the fly”).
- DXTN, if present, must be
unique for all items in the file and is an alphanumeric field (up to 30
characters). The import will try to
update the information that already exists in the project by looking up
the item by this number. If an item
with this number does not exist, then a new one will be created. This allows an estimate to be
downloaded, and later the ordered items can be downloaded again without
creating duplicate items (to update the
- DXPO is
any alphanumeric up to 30 chars, if this is present then the items will be
considered as purchased by Design Manager.
This
- DXPC and
DXFC are the Estimated Cost of the item and the Estimate Freight Cost
respectively. If DXPC is present
then P% should not be present.
- DXSN and
DXSD are used to update Order Status information within Design
Manager. These two are always
paired together (ie: a DXSN, followed by a DXSD). All of these codes are optional. The following DXSN codes are valid:
DXSN=OD
DXSD=<mm/dd/yyyy>
-Order date, if this is not present
then the order date in Design Manager will be set to the current system date
when the item first comes through with a DXPO.
DXSN=SB
DXSD=<mm/dd/yyyy>
-Ship on/before date (date that the Designer
requires that the item be shipped by).
DXSN=AC
DXSD=<mm/dd/yyyy>
-Acknowledged
date (date the order was acknowledged by the vendor or the date that the
acknowledgement was received). If not
present and DXTN is used, this field get filled in with the current system date
the first time that a item’s information is updated.
DXSN=CFA
DXSN=<Yes or No>
-Cut for approval required. This means that the Designer wants a sample
of the fabric or material) before the supplier fills the order. If this is missing, then No is assumed.
DXSN=CA
DXSD=<mm/dd/yyyy>
-Date that the Cut for approval was
found acceptable and the order can be processed.
DXSN=ES
DXSD=<mm/dd/yyyy>
-Expected Ship Date (date that the item
is expected to be shipped from the Vendor to the Designer).
DXSN=N###
DXSD=<text>
-Status Notes, ### represents the line
number (ie: N001 is line 1, N002 is line 2, etc.)
Sample
SIF File (as displayed in a program such as Notepad, this example has three
items in it, the last one is an example of how a fee could be handled):
SF=Generic SIF;SIF-User
ST=Accessories for receptionist
workstation
PN=AKP2500-PA1821-AMP
DXTN=876776
MC=UDO
DXPO=100032
PD=KEYBOARD WITH MOUSE PAD
QT=2.000
PL=155.00
S-=0.00
DXPC=100.00
DXFC=9.00
AN=
AD=Idea Industries, Inc.
DXSN=ES
DXSD=
DXSN=N001
DXSD=Order placed on
DXSN=N002
DXSD=Shipped via UPS Ground on
PN=BSE29
DXTN=348898
DXPO=100032
MC=UDO
PD=Side Support Bracket, for 29"h
Work surface (1 pair)
QT=2.000
PL=33.00
S-=70.00
DXPC=10.00
DXFC=11.50
ON=G
OD=Grey
AN=
AD=Global Computer Products, Inc.
DXSN=N001
DXSD=Order placed on
PN=UDOFEE
PD=UDO Purchasing Fee for
MC=UDO
QT=0
PL=0.00
DXPC=11.00
DXPO=100032
DXTN=UDOFEE