Code Description AA
Ball
AB
Bulk Pack
AC
Acre
AD
Bytes
AE
Amperes per Meter
AF
Centigram
AG
Angstrom
AH
Additional Minutes
AI
Average Minutes Per Call
AJ
Cop
AK
Fathom
AL
Access Lines
AM
Ampoule
AN
Minutes or Messages
AO
Ampere-turn
AP
Aluminum Pounds Only
AQ
Anti-hemophilic Factor (AHF) Units
AR
Suppository
AS
Assortment
AT
Atmosphere
AU
Ocular Insert System
AV
Capsule
AW
Powder-Filled Vials
AX
Twenty
AY
Read more →
B2B purchases are made in a number of ways today. There are a few requirements that differentiate B2B commerce from B2C commerce:
Buyers have contracts with suppliers - these may include negotiated prices and product restrictions
Buyers’ orders often need to be be approved internally prior to being placed with the supplier
Orders need to be recorded in the buyers financial system
Brick and Mortar Before eCommerce, there were physical stores, now referred to as brick and mortar stores.
Read more →
Catalogs files containing a suppliers products can be loaded into many eProcurement systems to allow employees to shop from the catalog from within the eProcurement system.
File Formats CSV CIF (Catalog Interchange Format) cXML Index
OCI 5 JSON
BMEcat
EDIFACT PRICAT
EDI X12 832 Price/Sales Catalog
Transmission Methods Email
HTTP(S)
FTP / FTPS / SFTP
Considerations Product images - image URL’s are most commonly used but an archive of image files may be utilized
Read more →
Recommendations for PunchOut Sites PunchOut sites may stop functioning properly in Chrome 80 if they are embedded in a frame by the eProcurement system. When a PunchOut site is embedded in a frame, it will no longer be able to set cookies unless a SameSite=None attribute is added to the cookies. Assuming the eProcurement application is unable to remove the frame around the PunchOut site, one of the options below will need to be implemented.
Read more →
Overview CIF (Catalog Interchange Format) was developed by Ariba as a file format for catalog files. The file format builds on the CSV file format by adding a header/footer and standardizing column headings.
CIF_I_V3.0 <catalog attributes> DATA <catalog items> ENDOFDATA Header The CIF file header contains attributes that define how the body of the file should processed.
The first line of the header should contain the CIF file signature and version number in the following format: CIF_I_V<version>.
Read more →
eProcurement systems use commodity codes to classify purchases. Spend analytics systems can analyze the categorized purchases to provide insight on how an organizations money is being speant. Suppliers may need to include commodity codes in their catalogs depending on their customers requirements.
UNSPSC UNSPSC is an open classification system for products and services. UNSPSC codes are 8 numeric digits that correspond to a commodity such as Staplers or Laptops. The UNSPSC classification system is organized as a 4 level hierarchy of: Segment, Family, Class, and Commodity.
Read more →
Overview CSV catalog files are a popular method of providing buyers with product information and pricing. Typically, the supplier is responsible for exporting their product information into a CSV format, transmitting it to the buyer, and the buyer is responsible for importing the catalog into their eProcurement system. CSV catalogs can be suitable for use with smaller catalogs, where pricing changes infrequently, and the catalog does not contain configurable items.
Read more →
cXML OrderRequest The sample files below are based on real orders from the specified eProcurement systems.
Coupa (2019)
PeopleSoft 8.55.15
Workday (2019)
cXML ConfirmationRequest The sample files below are based on real order confirmations from the specified suppliers or eCommerce systems.
Amazon (2019)
EqualLevel GO (2019)
Read more →
Overview The cXML Level 2 PunchOut standard enables buying organizations to search for and find PunchOut items within their procurement application, instead of having to search each suppliers' site directly. Level 2 makes suppliers’ products more accessible to buying organizations, increases the visibility of suppliers' products, and increases visits to suppliers' PunchOut sites. When the shopper finds an item they are interested in, they PunchOut directly to the item on the suppliers PunchOut site.
Read more →
ConfirmationRequest The cXML ConfirmationRequest document is used to confirm receipt of an order and provide additional information about the status of the order.
The ConfirmationRequest document is typically sent from the supplier’s eCommerce/ERP system to the buyer’s eProcurement system. The ConfirmationRequest and child elements are defined in cXML Fulfill.dtd rather than the cXML.dtd.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.040/Fulfill.dtd"> <cXML payloadID="1539635340.3061645@example.com" timestamp="2019-01-01T12:34:56+00:00"> <Header> <!-- credentials go here --> </Header> <Request> <ConfirmationRequest> <ConfirmationHeader confirmID="7890" operation="new" type="detail" noticeDate="2019-01-01T12:34:56+0000"> <!
Read more →