Home » Categories » Solutions by Business Process » E-Business » XML

Specific Trading Partner Notes - BOSSFed

Datafile Software

Specific Trading Partner Notes - BOSSFed


BOSSFEed has defined a set of XML schemas, based on the BASDA schemas, and known as the opXML standard. These differ from BASDA schemas only in that an extra set of elements was defined to cover the special needs of BOSSFed members.

BOSSFed suppliers have different ways to prepare goods for shipment. Items may be shipped direct to their dealer, or await collection; items may be picked, wrapped and labelled on behalf of the dealer’s customer, and either shipped to the dealer, await collection, or shipped direct to the customer. There is not, however, any agreement between the suppliers as to how such services are to be coded. To accommodate the special order codes used by BOSSFed suppliers, the following technique is used to determine the correct code to use.

Each BOSSFed supplier is assigned a 4-digit short code, which is held in the PLA file

Some Y/N items are created in the POH file for the questions about whether to label or not, whether to ship to the customer or not, and whether to await collection. These three answers allied to the supplier short code create a unique code which can be used as a lookup to the GLU database to determine the order code to use. This code is created in the POH file as the item 139 XML_LOOKUP.

For BOSSFed templates, an entry is required in the lookup GLU database for each supplier and service combination, to supply the correct order type code to use for that supplier. These entries must be maintained manually using the Other Lookup Parameter option.

Example entries in the GLU file would look like this:
KING = order code S SPIC = order code D ISAW = order code HW
KINGY = order code PWL KING.Y = order code PWD KING..Y = order code C
SPICY = order code P SPIC.Y = order code T SPIC..Y = order code C
ISAWY = order code DD ISAW Y = order code DD etc. etc.

(The full stops in the example codes above are actually spaces.) The first line gives the codes as used for standard orders for Kingfield Heath (KING), Spicers (SPIC)and ISA Wholesale (ISAW).

The second line gives the codes used by Kingfield Heath for "picked and wrapped” goods delivered to the dealer, for "picked and wrapped” goods delivered direct to the dealer’s customer, and for normal goods that are to await collection rather than be delivered to the dealer. The third line are the same codes for Spicers, and the fourth for ISA Wholesale.
Custom Fields
  • Release ID: Standard
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Integrating XML Processes
Viewed 3491 times since Tue, Jul 10, 2012
Example Datafile XML Template
Viewed 14441 times since Tue, Jul 10, 2012
Transaction Template Structures
Viewed 1287 times since Mon, Jul 9, 2012
XML Audit Trail Report
Viewed 1282 times since Thu, Jul 5, 2012
Constants File - Other XML Associated Files
Viewed 1294 times since Tue, Jul 10, 2012
Supplier Codes
Viewed 1263 times since Tue, Jul 10, 2012
Application Considerations - Customer Information
Viewed 2887 times since Tue, Jul 10, 2012
Output XML File Questions
Viewed 1433 times since Mon, Jul 9, 2012
Sales Ledger Transactions (SLT)
Viewed 1655 times since Tue, Jul 10, 2012
Receive and Process Orders
Viewed 1346 times since Thu, Jul 5, 2012