/ ""
mymarket.com e-Procurement Solution
Integration Recommendation
14 February 2011
Page 1 of 7 /

Vendor Web Service Integration
into
mymarket.com
Version: Version 1.2
Date: 14 February 2011

Document Revision History

Name / Date / Version / Description
Leon Weed / 16/09/2010 / 0.1 / created
Leon Weed / 09/12/2010 / V1.1 / Updated
Leon Weed / 14/02/2011 / V1.2 / Updated

Table of Contents

1Acronyms Used

2Overview

3XML Schemas

4XML Data Definitions

5Required URL for Client Posting

6Testing – eProcurement

7Go Live

1Acronyms Used

Through this document, certain acronyms or abbreviations are used:

Acronym / Meaning
BORG / Business Organisation/Business Unit
EBO / Enterprise Buying Organisation
ERP / Enterprise Resource Planning system (i.e. Financial system)
MMC / MyMarket.com
User / System User
Vendor / Supplier on the MyMarker.com system
Web Services / Software system to allow intercommunication between computer systems
XML / Language/format to share data via the internet

2System flow Diagram

3Overview

  • There are two transactions involved in this integration:
  • Vendor Transaction sent from Client System (with Synchronous response)
  • The Vendor Synchronisation into the MMC system uses a standard a standard Web Service (using a standard XML schema) that shall receive messages from the client which can be of the following:

Vendor create

Vendor update

Vendor block

Vendor unblock

  • Status update from MyMarket to Client System (Asynchronous)
  • The status of the processing (consuming) of these documents is returned to the client for update of their transaction history.
  • Using the MyMarket myIntegration application; messages (XML) sent from Client into MMC can be viewed along with returned statuses.
  • Access to the standard MyMarket XML schemas are included in this document
  • The client URL for the return Status Messages or Integration layer is stored in a table within the MyMarket myDocuments database.

4XML Schemas

The XML schema is named:

  • MMCAdoptionSupplierRequest.xsd

The documents are available at the following web site. Use the most recent version of the documents – Version 1.5:

  • Save Applicable XSD file(s)into a working directory
  • Right mouse click
  • Select Save Target As…
  • Common Types XSD must be downloaded into same directory
  • NOTE: These files must be saved as .XSD. Right-mouse clicking on the links will default to .XML.
  • From the XSD, with the use of a third party application (XMLSpy), sample XML data can be generated
  • The XSD can also be used to Publish or create your Web Service Definition File (WSDL)

Important Note: The latest version of this schema is to be used.

5XML Data Definitions

6Required URL for Client Posting

Preproduction:

Production (Live):

The asynchronous Statusresponse from MMC to Client requires a URL to post into too.

The Client is to submit these via the MyMarket IT Test Department (Aadila Jada on 011 731 7600).

7Testing–eProcurement

The testing of the Client developed Web Service can be done as follows:

  • Create the Pre-Production Environment
  • Contact MyMarketTesting Department to create a test Client environment on the MyMarket Pre-Production system (if not already set up)
  • A call will be logged on the MyMarket Pre-Production facilitator to do this
  • Once the Pre-Production environment is set up, log in details will be sent to the Requestor.
  • Client Posting URL
  • The Client URL that MyMarket will post to needs to be recorded in the appropriate (Pre-Production) table. This will be added by the MyMarket developer and coordinated by the MyMarket Testing Department.
  • Contact MyMarket Testing Department to log a call on the Web Service Developer (Temporary step – Will become part of an Information Questionnaire – IQ - document to be developed)
  • Testing (Vendor Synchronisation)
  • The Client Tester can log into the ERP Integration application
  • XML document can be:
  • XML Viewed
  • All messages exchanged between the two Web Services are stored and can be viewed
  • The results of these posts are assessed by the Client in their development environment
  • NOTE: It will always be required that the MyMarket Technical Developer be consulted before the testing commences. This is due to the various software constraints in posting to and consuming the XML feed. This may be as simple as a phone discussion or may require more in-depth involvement.

8Go Live

The processisas follows:

  • Once Client Testing Complete
  • Live Client Posting URL
  • The Client URL that MyMarket will post to needs to be recorded in the appropriate (Live) table.
  • Contact MyMarket Help Desk to log a call on the Web Service Developer (Temporary step) for Live Set Up
  • myIntegration Application
  • Automatically posts/receives XML documents based on the rules as set up
  • The User logs into the myIntegrationapplication as trained to view Status, XML messages and resubmit if necessary