DEALER
Nick Name Password
 
XML Real-time Error Messages   |   XML format for sending orders to Morris   |   Specification for Morris Realtime XML Protocol

XML Availability Schedule and Naming Conventions

Inventory Feed Protocol:


When it comes to .xml files that you will receive from Morris Costumes, you have several choices. This webpage will: 1) Define terminology used to describe these files; 2) Breakdown the components of each file, using examples of what they look like and/or what the file URL looks like; And 3) Discuss when you will receive these files, which is most often your (the customer's) choice. From there, it's up to you to determine which file(s) will be most relevent for your system.

Here is a list of current .xml files available to you:
1) "Available batch" files: a record of available inventory.
2) "Results" file: a (nearly) immediate response to your placed order or batch.
3) "Open Orders Summary" file: summary of ALL currently open orders.
4) "Daily Summary" file: a record of all "changed" orders that day; includes 'picked', 'invoiced', 'added', 'deleted', etc.
5) "Weekly Summary" file: same as daily summary, but weekly.
6) "Current Load History" file: most current (real-time) record of orders/batches loaded, whether successful or not.
7) "Daily Load History" file: daily record of ALL the orders/batches loaded, whether successful or not.
8) "Weekly Load History" file: weekly record of ALL the orders/batches loaded, whether successful or not.

First, let's look at file Format:

"With" or "Without" Detail:
The term "With detail" refers to the contents of the file. Files "with detail" contain the quantity, the description, price, and weight (if known) of the item(s). Click HERE for an example of an .xml file "WITH DETAIL".

The term "WithOUT detail" refers to the contents of the file. Files "withOUT detail" simply do NOT contain the description, price, or weight. But DOES contain the quantity. Click HERE for an example of an .xml file "WITHOUT DETAIL".

Now, we'll begin to breakdown the .xml file, and explain some of the terminology used to name the files:

Here is an example of a URL (a web link) you might receive from Morris:

              http://morris.morriscostumes.com/out/available_batch_11111yyyyy.xml

Starting with the "available_batch_" portion: this describes the content of the .xml file. Other content descriptions you may see are "available_batch", "openorders_summary_", or "daily_summary_", to name a few. It all depends on the content of the file. I'll go into more detail about each file later.

Next, "11111" is representing your customer number.

And finally, the "yyyyy" stands for several things. In this case, each "y" represents a "yes".. in other cases, you may see "nyyyn" or "nyyyy", etc. The "n", stands for "no".
Here's what they mean:

The 1st "y":    "With detail?" y or n
The 2nd "y":    "Include the North Carolina location?" y or n *
The 3rd "y":    "Include the California location?" y or n **
The 4th "y":    "Combine the location inventory?" y or n ***
The 5th "y":    "Includes ALL active items?" y or n ****

* Your system must be set up to receive inventory from the North Carolina location.
** Your system must be set up to receive inventory from the California location.
*** "Combined" means that the shipping location will be unknown to you. Your system must be set up for this.
**** "All" items means the file includes ALL active items (vs. "changes" to inventory only).

Ex: http://morris.morriscostumes.com/out/available_batch_11111yyyyy.xml

The example above indicates that you've been sent an "available batch"; that your customer number is "11111"; that your system is set to receive inventory from both NC and CA; that you are set up to receive "combined" location files; and that this file includes "ALL" active items.

So which files will I get, and when:
As indicated earlier, it's up to you to decide which files you wish to receive from Morris Costumes. It's not necessary to receive any of them, if you do not wish. It's also up to you to determine when you'd like to receive them. We already have a schedule of when these files are being sent, but this can be modified to your request.
*NOTE: When you receive the link to these file(s), they will be COMPRESSED and end with ".tgz"

1) "Available Batch" files:

    If you are set up to receive "COMBINED" location information, your "available batch" options are:


    1) The "Changes" file, without detail, which is currently being sent out every 30 minutes. ex: [available_batchnyyyn.xml]
            *NOTE: Every time a new file goes out, the old one is OVERWRITTEN. There is only ONE existing file.

    2) The "All" active items file, with detail, which is currently being sent out on the 1st & 3rd Sundays of the month.
            ex: [available_batch_customeryyyyy.xml]

    3) The "All" active items file, without detail, which is currently being sent out every night. ex: [available_batchnyyyy.xml]
            *NOTE: Every time a new file goes out, the old one is OVERWRITTEN. There is only ONE existing file.


    If you are set up to receive "SEPARATE" location information, your "available batch" options are:

    1) The "Changes" file, without detail, which is currently being sent out every 30 minutes. ex: [available_batchnyynn.xml]
            *NOTE: Every time a new file goes out, the old one is OVERWRITTEN. There is only ONE existing file.

    2) The "All" active items file, with detail, which is currently being sent out on the 2nd & 4th Sundays of the month.
            ex: [available_batch_customeryyyny.xml]

    3) The "All" active items file, without detail, which is currently being sent out every night. ex: [available_batchnyyny.xml]
            *NOTE: Every time a new file goes out, the old one is OVERWRITTEN. There is only ONE existing file.


    If you are set up to receive "REAL-TIME"* xml information, your "available batch" options are:
       * "Real-Time" refers to your system being directly linked to Morris' system, and has the capability of receiving the most current
           inventory information available. For more information, email Scott Morris at
morris@morriscostumes.com

    1) The "Changes" file, without detail, which is currently being sent out immediately upon any change in inventory
        AND/OR every 30 minutes. ex: [available_batchnynyn.xml]
            *NOTE: Every time a new file goes out, the old one is OVERWRITTEN. There is only ONE existing file.

    2) The "All" active items file, with detail, which is currently being sent out every Sunday night.ex: [available_batchyynyy.xml]               *NOTE: Every Sunday night, this file OVERWRITES. There is only ONE existing file.

2) "Results" file: a (nearly) immediate response to your placed order or batch.

3) "Open Orders Summary" file: summary of ALL currently open orders. Currently being sent out daily.

4) "Daily Summary" file: record of ALL "changed" orders that day; includes 'picked', 'invoiced', 'added', 'deleted', etc. Sent out daily.

5) "Weekly Summary" file: record of ALL "changed" orders that week; includes 'picked', 'invoiced', 'added', 'deleted', etc. Sent out weekly.

6) "Current Load History" file: most current (real-time) record of orders loaded, whether successful or not.

7) "Daily Load History" file: DAILY record of ALL the orders (and attempted orders) loaded, whether successful or not.

8) "Weekly Load History" file: WEEKLY record of ALL the orders (and attempted orders) loaded, whether successful or not.



File Splitting:

The splitting of XML file into multiple XML files affects only the various summary files (daily, weekly, monthly, annual for both the regular summary and the load history). If there are more than 2500 orders in any given summary it will split. There is a file naming convention (and hence URL naming convention) such that wherever it used to say ".xml" it will now say "_###.xml" where "##" is the three digit file number. So if the file was: /dog/cat/daily_summary_04012007.xml and there are three files, they will become:

/dog/cat/daily_summary_04012007_001.xml
/dog/cat/daily_summary_04012007_002.xml
/dog/cat/daily_summary_04012007_003.xml

For those receiving real-time postings of files they will get a posting for each of the three files. For those receiving email notification, they will get one email listing all three files. Within each file are two new tags: <file_no> and <of> ... in the above example the files would have:

<file_no>1</fileno><of>3</of>
<file_no>2</fileno><of>3</of>
<file_no>3</fileno><of>3</of>

So that any automated software can tell that they have all the files and which one they are working on, in addition there is a new tag; <file_count> which is the number of orders in that file. The original tag <Count> is still the total of the report ... so in the above example if there were 7000 orders total they all three would have

<Count>7000</Count>

and the first two would have

<file_count>2500</file_count>

and the third would have

<file_count>2000</file_count>

NOTE: if only one file then the files will remain as they are, including the old name, and not have any of the new tags !!!!!


Click --> How to SEND .xml files to Morris! <-- Click

~~~~~~~~~~~~~~~~~~~~~

Incoming Post Format:
userid=xxxxxx
password=xxxxxx
xml_url=full path (URL) to xml file
message=done

Always post to: /cgi-bin/doxml.cgi?userid=xxxx&password=yyyy&xml_url=piggy&message=done userid=xxxxx and password=yyyy



XML Real-time Error Messages   |   XML format for sending orders to Morris   |   Specification for Morris Realtime XML Protocol
©2009 Morris Costumes. All Rights Reserved.
     Programmed by Star Web Creations