E-commerce: Getting Started with B2B XML

dankessler — Tue, 10 Jan 2012 20:15:04 -0800

Join the NAMM Tech Committee and Get Started with B2B e-commerce

Thursday, January 19 • 11 a.m.–Noon • Room 204A

In today's challenging and uncertain economy, finding efficiencies and cost savings in your business processes is imperative. Today many large‹and not-so-large‹companies in the music products industry are significantly improving their business efficiencies by using XML-based transactions. The NAMM B2B XML standard is the most widely used standard in the global music products industry. In one hour, the standard will be explained and explored with the intent of enabling you and your company to get started and go further using the industry standards.

Topics we will cover:

XSL Transforms

dankessler — Tue, 10 Jan 2012 19:25:46 -0800

Although XML is a precise and efficient method for storing and transmitting data, it can be difficult for a person to read and understand. A technology called XSLT (eXtensible Stylesheet Language Transformations) exists that allows you to convert (transform) the data in an XML document into a more readable, browser-renderable format such as HTML.

The basic steps involved in this process are:

Write an XSLT transform for a specific type of XML file (e.g., invoice-v2011.1.xml)
- B2B
read more

Product Category Codes

dankessler — Tue, 10 Jan 2012 16:52:52 -0800

NAMM maintains a comprehensive list of musical product categories, including category descriptions, level paths, unique code numbers, and inactive dates, for use with the B2B documents. Although the full list of well over 700 categories is too lengthy to publish in this guide, a small sample is shown below.

Code

Inco Terms Codes

dankessler — Tue, 10 Jan 2012 16:43:37 -0800

The International Chamber of Commerce (Inco) shipping terms codes reproduced below are used in the Invoice and Purchase Order documents.

Code

PO Status / Det Ack Example

dankessler — Tue, 10 Jan 2012 16:22:36 -0800

<?xml version="1.0" encoding="utf-8"?>
<NAMM_POStatus version="2011.0">
  <Id>DocumentIDNumber</Id>
  <POStatusRequestId>123456ZZZZ</POStatusRequestId>
  <Timestamp>2011-01-15T08:58:23</Timestamp>
  <BuyerOrderId>432543</BuyerOrderId>
  <DateOrdered>2011-01-15</DateOrdered>
  <BuyerName>Joe Schmoe</BuyerName>
  <Supplier>
    <PartyId>123456789012</PartyId>
    <Name>Korg Inc.</Name>
    <Address>
      <Attn />
      <Address1>123 N Main St</Address1>
      <Address2 />
      <Address3 />
      <City>Anytown</City>
      <State>NY</State>
      <PostalCode>10011</PostalCode>
      <Country>United States</Country>
      <CountryCode>US</CountryCode>
    </Address>
  </Supplier>
  <SoldTo>
    <PartyId>987654321012</PartyId>

PO Status Request Example

dankessler — Tue, 10 Jan 2012 16:19:33 -0800

<?xml version="1.0" encoding="utf-8"?>
<NAMM_POStatusRequest version="2011.0">
  <Timestamp>2011-07-19T10:34:02</Timestamp>
  <Id>S2S3050_PO691630-1</Id>
  <Supplier>
    <PartyId>0761294001004</PartyId>
  </Supplier>
  <SoldTo>
    <PartyId>1100001001675</PartyId>
  </SoldTo>
  <BuyerOrderIds>
    <BuyerOrderId>123456</BuyerOrderId>
    <BuyerOrderId>987654</BuyerOrderId>
    <BuyerOrderId>654321</BuyerOrderId>
  </BuyerOrderIds>
</NAMM_POStatusRequest>

Price Book Example

dankessler — Tue, 10 Jan 2012 16:14:03 -0800

<?xml version="1.0" encoding="utf-8"?>
<NAMM_PRICEBOOK version="2011.0">
  <Id>S2S3050_PO691630</Id>
  <Timestamp>2011-07-19T08:23:30</Timestamp>
  <Supplier>
    <PartyId />
    <Name />
    <Address>
      <Address1 />
      <Address2 />
      <Address3 />
      <City />
      <State />
      <PostalCode />
      <Country />
      <CountryCode />
    </Address>
  </Supplier>
  <SoldTo>
    <PartyId />
    <Name />
    <Address>
      <Address1 />
      <Address2 />
      <Address3 />
      <City />
      <State />
      <PostalCode />
      <Country />
      <CountryCode />
    </Address>
  </SoldTo>
  <Items>
    <Item EffectiveDate="2011-07-19T08:23:30">
      <BarCodeId>761294084991</BarCodeId>

Transport Options

dankessler — Tue, 10 Jan 2012 15:24:14 -0800

In the B2B scenario described above, the XML documents must be electronically transmitted between partners in order for data sharing to take place. Therefore, the transmission method used, called a transport protocol, must be understood and implemented by both parties to a transaction.

The set of protocols used for Internet communications is called the Internet Protocol Suite, commonly known as TCP/IP (Transmission Control Protocol/Internet Protocol). The two most popular transport protocols in use today are HTTP and FTP, discussed below.

Transaction Sequence

dankessler — Tue, 10 Jan 2012 15:18:36 -0800

A typical sequence of events between a product supplier and product buyer and the associated documents, in chronological order, might be as follows.

Both supplier and buyer complete and release mutually-available identification information in a Party document.
The supplier sends a catalog of available products to the buyer in an Item document.
The buyer acknowledges receipt of the Item document with a Functional Acknowledgement document.
The supplier sends a price list for available products to the buyer in a PriceBook document (optional).
- B2B
read more

PO Status / Det Ack Schema

dankessler — Tue, 10 Jan 2012 15:05:55 -0800

PO Status / Det Ack

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="NAMM_POStatus">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Id"
                    type="xs:string" />
        <xs:element name="POStatusRequestId"
                    type="xs:string" />
        <xs:element name="Timestamp"
                    type="xs:dateTime" />
        <xs:element name="BuyerOrderId"
                    type="xs:int" />
        <xs:element name="DateOrdered"
                    type="xs:date" />
        <xs:element name="BuyerName"
                    type="xs:string" />
        <xs:element name="Supplier">
          <xs:complexType>
            <xs:sequence>

PO Status Request Schema

dankessler — Tue, 10 Jan 2012 15:02:30 -0800

PO Status Request Schema

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="NAMM_POStatusRequest">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Timestamp"
                    type="xs:dateTime" />
        <xs:element name="Id"
                    type="xs:string" />
        <xs:element name="Supplier">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="PartyId"
                          type="xs:decimal" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="SoldTo">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="PartyId"

Price Book Schema

dankessler — Tue, 10 Jan 2012 11:21:17 -0800

Price Book

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="NAMM_PRICEBOOK">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Id"
                    type="xs:string" />
        <xs:element name="Timestamp"
                    type="xs:dateTime" />
        <xs:element name="Supplier">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="PartyId"
                          type="xs:string" />
              <xs:element name="Name"
                          type="xs:string"
                          minOccurs="0" />
              <xs:element name="Address"
                          minOccurs="0">

Sell Through

dankessler — Tue, 10 Jan 2012 10:20:05 -0800

Sell Through – sellthrough-v2012.1.xml

Tag

PO Status / Det Ack

dankessler — Tue, 10 Jan 2012 10:05:40 -0800

PO Status / Detailed Acknowledgement – postatus-v2011.0.xml

Tag

PO Status Request

dankessler — Tue, 10 Jan 2012 10:00:47 -0800

PO Status Request – postatusrequest-v2011.0.xml

Tag

Pricebook

dankessler — Tue, 10 Jan 2012 09:44:00 -0800

Price Book – pricebook-v2011.0.xml

Tag

ASN_2009.2_Example.xml

dankessler — Wed, 02 Nov 2011 11:52:10 -0700

S2S3050_PO691634 2008-01-15T07:34:00 345678 2008-01-15 2008-01-22 0761294001004 Ladron Corporation

9900 S.

Item v2011.1 Example

dankessler — Tue, 02 Aug 2011 20:21:47 -0700

2011-08-11T05:39:10.887 38A6C25A-2344-4343-B53D-B8706E1A37DA 0670716000009 405012500 405012500 KA-193 ADAPTER KAOSSILATOR MINIKP PANDORA & AMPWOR N N KORG CN 0.0000

Item v2011.1 XSD

dankessler — Tue, 02 Aug 2011 20:12:26 -0700

Price Book [aka Cost Book]

dankessler — Thu, 21 Jul 2011 10:54:40 -0700

S2S3050_PO691630 123456789012 Korg Inc.

123 N Main St Anytown NY 10011 United States US

987654321012 Joe's Musi

PO Status Request

dankessler — Thu, 21 Jul 2011 10:33:05 -0700

2011-07-19T10:34:02 S2S3050_PO691630-1 0761294001004 1100001001675 123456 987654 654321

SellThrough

dankessler — Thu, 21 Jul 2011 10:29:26 -0700

S2S3050_PO691630 2011-07-19T08:23:30 1100001001675 Joe's Music Store

Joe Owner 321 Main Street Music City NY 12345 USA US

0761294001004 Roland Corporation US

5100 S

Updated Proposed 2009.2 Item Schema and Sample Document

McGloine — Wed, 13 Apr 2011 15:31:34 -0700

As discussed in our meeting today:

1) The View attribute is no longer required. So [<Image view =”Undefined”>] is no longer required. You can just use this [<Image>]. Undefined is implied when the View attribute is missing.

2) I added the CarouselSequence attribute as optional. Its in the schema and the new sample file. Both attached to this post.
[<Image View='Front' Caption='Look how cool this is' CarouselSequence='1'>]

3) I am going to start beta testing with at least one trading partner this week.

Bill

NAMM Ad-hoc Technology Meets to Expand B2B Standards

dankessler — Sat, 15 Jan 2011 10:09:34 -0800

The NAMM Standard Promotes Cost Savings and Efficiencies in the Music Products Industry

At this year's NAMM Show, NAMM’s Ad-Hoc Technology Committee concluded another round of face-to-face meetings. For the past few years, experts from across all channels of the music products industry have partnered together, designing XML-based documents developed to streamline and improve electronic transactions between trading partners in the music products industry.

The committee is currently focusing on a unified categorization standard to facilitate interchange of product data between sellers and buyers. In the coming weeks, a proposed draft from the meeting will be published for comments on http://www.namm.org. Other topics discussed included documents to support electronic software distribution.

The NAMM Standards Implementation Guide and Specifications are published on NAMM’s Web site at http://www.namm.org/initiatives/b2b. This site is open to all NAMM Members and also features related resources for NAMM Members.

The Ad-Hoc Technology Committee comprises technical experts who represent NAMM Member companies. The committee is made up of Paul Ward, Roland U.S.; Robin Walenta, West Music; MaryAnne DelMundo, Guitar Center; Jerry Grochowski, Hal Leonard; Greg Bryniak, D’Addario; Amy Pearson, Sweetwater; William McGloine, Korg; Pat Murphy, Tri-Tech; Gordon O'Hara, RetailUp!; Gary Duvall, Yamaha; and Dan Kessler, NAMM.

Tri-Technical Systems Inc.

pmurphy — Fri, 08 Jan 2010 12:24:07 -0800

Tri-Technical Systems provides a point of sale (POS), inventory management, accounting and business software application that is used by more than 1500 music retailers. Tri-Technical Systems supports all versions of all documents.

Categories Project Update

dankessler — Wed, 06 Jan 2010 16:32:11 -0800

The attached files represent the progress to date on the categories project (see post titled "Categories Project Overview" for details on this project if you are new to it).
This file represents progress as of January 6, 2010 and has been graciously prepared by Johanna & Gordon from RetailUp. It includes reconciling categories from: RetailUp TriTech West Music USA MI Import/Export Sweetwater NAMM Universal Classification Please review and comment.

Detailed Ack Draft | From West & Roland

dankessler — Sat, 12 Dec 2009 10:34:46 -0800

NAMM B2B Interest Group Meeting

dankessler — Mon, 07 Dec 2009 14:23:13 -0800

Start: 01/14/2010 - 6:00pm

End: 01/14/2010 - 7:00pm

Timezone: Etc/GMT-8

Please join for snacks and a short presentation about the latest developments in NAMM's Tech Cmte Standards Development.

Do You want to be more efficient? Join dozens of other NAMM Member companies who are doing electronic commerce using the NAMM Standard. Network with others who are interesting in doing it just like you.

Find out how to move forward. Get linked into resources needed. Don't let this opportunity get away

NAMM 'Universal Product Classification' System

dankessler — Fri, 13 Nov 2009 15:59:02 -0800

This document contains the draft classification system developed by NAMM several years ago. As far as I know, it is not in use anywhere except NAMM. It still remains another systematic approach to classification although most agree that it is too detailed.

Classifications Used for Music USA

dankessler — Wed, 11 Nov 2009 16:34:08 -0800

Here is a file that contain categories used for NAMM 'Global Report'. Also include are the official 'import and export' codes used in the US.

IG Redline

dankessler — Wed, 11 Nov 2009 10:17:50 -0800

Published version

Sweetwater

dankessler — Tue, 10 Nov 2009 11:46:48 -0800

Categories Project Update as of 10-16-09

retailup — Fri, 16 Oct 2009 11:13:58 -0700

The attached files represent the progress to date on the categories project (see post titled "Categories Project Overview" for details on this project if you are new to it).

Semi-Detailed Ack

dankessler — Thu, 15 Oct 2009 14:50:43 -0700

Sweetwater Item Classifications

akpearson — Thu, 15 Oct 2009 13:47:38 -0700

Attached is an Excel file with the classifications we use internally at Sweetwater. Please note that this does *not* reflect the classifications on the web, which I don't have easy access to at this time. Thanks!

PO_v2009.1.xsd

dankessler — Tue, 13 Oct 2009 20:00:47 -0700

PO_2009.1_Example.xml

dankessler — Tue, 13 Oct 2009 19:59:59 -0700

S2S3050_PO691630 2008-12-25T08:23:30 1100001001675 Joe's Music Store

Joe Owner 321 Main Street Music City NY 12345 USA US

Party_v2009.1.xsd

dankessler — Tue, 13 Oct 2009 19:58:21 -0700

Party_2009.1_Example.xml

dankessler — Tue, 13 Oct 2009 19:57:21 -0700

2008-08-13T08:32:00 NAMM000000123999*00000 NAMM Roland Corporation U.S. http://www.rolandus.com NAMM000000123999*00001 NAMM Main Roland Corporation U.S.

5100 S.

Item_v2009.1.xsd

dankessler — Tue, 13 Oct 2009 19:55:23 -0700

Item_2009.1_Example.xml

dankessler — Tue, 13 Oct 2009 19:53:59 -0700

2009-12-03T12:00:00 I999_123456 0761294001004 FantomX6 Fantom-X6 Workstation Keyboard Powerhouse Workstation with an Ultra-Friendly Interface 2395 1437 China Roland

Invoice_v2009.1.xsd

dankessler — Tue, 13 Oct 2009 19:52:21 -0700

Invoice_2009.1_Example.xml

dankessler — Tue, 13 Oct 2009 19:51:14 -0700

S2S3050_PO691634 2008-01-15T08:34:00 1100001001675 Joe's Music Store 12345678 D 0761294001004 Roland Corporation U.S.

5100 S Eastern Ave Los Angeles CA 9004

FunAck_v2009.1.xsd

dankessler — Tue, 13 Oct 2009 19:48:44 -0700

FunAck_2009.1_Example.xml

dankessler — Tue, 13 Oct 2009 19:46:18 -0700

2008-01-14T10:34:02 S2S3050_PO691630-1 0761294001004 1100001001675 C01 Received

Categories Project Overview-- What are the goals? How will we proceed?

retailup — Tue, 13 Oct 2009 14:26:54 -0700

Attached find a summary overview of the categories project as discussed at the 10-15-09 and the Summer Session 2009 meetings of the Committee.

If you are new to the process-- this document summarizes why sharing categories with this group is important, what we plan to achieve and the steps we are taking to produce a Category Guidance document and encourage manufacturers and publishers to use it when they provide data to dealers and service providers.

Ad Hoc Technology Committee
Category Project Update
Gordon O’Hara- Retail Up!

Review from previous meeting

Goal

ASN_v2009.1.xsd

dankessler — Tue, 13 Oct 2009 08:15:49 -0700

MF Fields for Item Doc

dankessler — Wed, 16 Sep 2009 14:26:01 -0700

I received this from Tami Ramey at Musician's Friend last month. We should review our document and make sure that we have accounted for their requirements.

Points of Contact for Implementing XML

akpearson — Wed, 16 Sep 2009 11:27:34 -0700

Until we can get a true registry up for who all is using the XML Standard, please post the company name and contact information for the person at your company who should be contacted by partners wishing to implement the XML Standard.