KMM - Reconciliation Process
Functional Summary
The reconciliation process for the KMM module is intended to assist the Accounts Payable processor with the processing of the invoice transactions via the KMM
module. These transactions are system generated and rely on the vendor’s cXML Invoice information to be processed. The system will be generating GLIB
transactions based on the Original purchase order and Invoice received by the supplier.
Assumptions
Purchase Order has been submitted via cXML to Supplier.
Purchase Order (submitted) includes the purchasing (ghost) card information (in the cXML PO transmission) and vendor will utilize this card number for
payment.
Invoices will need to be received via cXML format (as outlined by cXML standards - http://xml.cxml.org/current/cXMLUsersGuide.pdf).
Although there is no actual payment to the vendor (since they will be utilizing the ghost card); the system should generate a GLIB transaction based on the
original purchase information.
Requirements
Create a page that will enable the supplier to submit their Invoices utilizing cXML standards. The process should follow the request response model as outlined
by the cXML.org standards. Request-Response transactions can be performed only over an HTTP or HTTPS connection. The following figure illustrates the steps
in a Request-Response interaction between parties A and B:
(Samples of cXML Invoices are listed in the Sample Section.)
Invoices received should be saved in the database. When an invoice is received and parsed, a GLIB transaction should be generated in KFS.
Need the ability to generate reports based on the following: (see sample section)
1)
2)
3)
4)
5)
Discrepancies based Substitutions
Price Discrepancies Purchase Order vs Invoice received (per line item)
Over-shipments
Invoices received without a corresponding Purchase Order
Ghost Card/Invoice Transactions Discrepancies
Need the ability to identify and exclude Discrepancy Transactions from future reports. (Review Sample Area)
Database tables
Current UCDBuy database:
EP_PRXML_T (this table is used to capture the Punch-out Request cXML submitted to the vendor)
Name
Data Type
--------------------------- -----------------------------KEY_ID
VARCHAR2(100)
NOT NULL
(Payload ID)
ORDR_NBR
USER_ID
SPAID
PR_XML
(Order Number)
(Customer User ID)
(Supplier Auxiliary ID)
(PR cXML request)
VARCHAR2(10)
VARCHAR2(8)
VARCHAR2(28)
CLOB(4000)
NOT NULL
NOT NULL
EP_POXML_T (this table is used to capture the PO cXML submitted to the vendor)
Name
-----------------------------KEY_ID
ORDR_NBR
USER_ID
PO_URL
PO_XML
PO_RESPONSE_XML
Data Type
-----------------------------VARCHAR2(100)
NOT NULL
VARCHAR2(10)
NOT NULL
VARCHAR2(8)
NOT NULL
VARCHAR2(250)
CLOB(4000)
CLOB(4000)
(Payload ID)
(Order Number)
(Customer User ID)
(Suppliers PO URL)
(PO cXML submission)
(PO cXML response)
EP_INVOICEXML_T (this table is used to capture the Invoice cXML submitted by the vendor)
Name
-----------------------------KEY_ID
WHSE_LOC
ORDR_NBR
INVOICE_NBR
PROCESSED_IND
INVOICE_XML
Data Type
-----------------------------VARCHAR2(100)
NOT NULL
VARCHAR2(2)
VARCHAR2(10)
VARCHAR2(15)
VARCHAR2(1)
CLOB(4000)
(Payload ID)
(Catalog Code)
(Order Number)
(Vendor Invoice Number)
(Processed Indicator)
(Invoice cXML)
EP_INVOICE_T (This table is used to capture the invoice after its parsed)
Name
-----------------------------WHSE_LOC
TRANSACTION_ID
ORDR_NBR
ORDR_ITM_NBR
COMM_CD
COMM_UI_CD
COMM_CATLG_DESC
QTY_SHIP
UNIT_PRC
TAX_AMT
TOT_LINE_AMT
RECEIVED_CD
RCVED_COMMENTS
USER_ID
CHKIN_DT
DT_SHIP
MATCH_IND
GL_PROCESS_IND
ACTIVE_IND
INV_NBR
Data Type
-----------------------------VARCHAR2(2)
NOT NULL
VARCHAR2(15)
NOT NULL
VARCHAR2(10)
NUMBER(4,0)
VARCHAR2(28)
VARCHAR2(3)
VARCHAR2(300)
NUMBER(7,0)
NUMBER(11,3)
NUMBER(11,3)
NUMBER(19,2)
VARCHAR2(1)
VARCHAR2(300)
VARCHAR2(8)
DATE
DATE
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(15)
(Warehouse/Catalog Code)
(Transacation ID)
(Order Number)
(Order Item Number)
(Item Number)
(Unit of Measure)
(Item Description)
(Quantity Shipped)
(Unit Price)
(Tax Amount)
(Total Line Amount)
(Received Code) **
(Received Comments) **
(Received User ID) **
(Received Date) **
(Date Shipped)
(Match Indicator)
(General Ledger Processed)
(Active Indicator)
(Vendor Invoice Number)
** This is an optional process that enables campus departments to indicate whether or not they received the product. Please note this process is hardly ever
been used.
EP_CC_DISCREPANCY_T (This table is used to exclude discrepancy transactions from future reports)
Name
-----------------------------BATCH_NBR
TRANSACTION_ID
REFERENCE_NBR
ORDR_NBR
ORDR_ITM_NBR
INV_NBR
USER_ID
COMMENTS
ACTION_DATE
BANK_TRNS_DT
Data Type
-----------------------------VARCHAR2(14)
NOT NULL
VARCHAR2(10)
NOT NULL
VARCHAR2(23)
NOT NULL
VARCHAR2(10)
NUMBER(4,0)
VARCHAR2(15)
VARCHAR2(8)
NOT NULL
VARCHAR2(300)
DATE
DATE
(DaFIS Batch ID – processing Credit Card Trans.)
(Transaction ID)
(Bank Reference Transaction Number)
(Order Number)
(Order Item Number)
(Invoice Number)
(User ID – that excluded this transaction from list)
(Comments)
(Date that this transaction was excluded)
(Bank Posted Date)
EP_WHSE_T (This table is used primarily to identify the elements used on the B2B data exchange)
Name
-----------------------------WHSE_LOC
PCARD_NBR
EXP_DT
OFFSET_COA_CD
OFFSET_ACCT_NBR
OFFSET_SUB_ACCT_NBR
OFFSET_OBJECT_CD
OFFSET_SUB_OBJ_CD
OFFSET_PROJECT_CD
ORIGIN_CD
BUYOUT_IND
SNDR_PAYLOADID
SNDR_SHARED_SECRET
SNDR_CREDENTIAL_DOMAIN
SNDR_USER_AGENT
RCPT_SHARED_SECRET
RCPT_CREDENTIAL_DOMAIN
RCPT_IDENTITY
VEND_PR_URL_ADDR
VEND_PO_URL_ADDR
ACTIVE_IND
SPCL_HANDLE_IND
UNSPSC_CD
SHIPTO_ID
PUNCHOUT_IND
SNDR_CREDENTIAL_TYPE
DEPLOYMENT_MODE
ALTERNATE_ADDRESS_SEQUENCE
ADDRESS_ID

Data Type
-----------------------------VARCHAR2(2)
NOT NULL
VARCHAR2(25)
VARCHAR2(15)
VARCHAR2(2)
VARCHAR2(7)
VARCHAR2(5)
VARCHAR2(4)
VARCHAR2(3)
VARCHAR2(10)
VARCHAR2(2)
VARCHAR2(1)
VARCHAR2(25)
VARCHAR2(60)
VARCHAR2(60)
VARCHAR2(60)
VARCHAR2(60)
VARCHAR2(60)
VARCHAR2(60)
VARCHAR2(250)
VARCHAR2(250)
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(15)
VARCHAR2(30)
VARCHAR2(1)
VARCHAR2(25)
VARCHAR2(25)
VARCHAR2(1)
VARCHAR2(25)
(Catalog Code)
(Ghost Card)
(Expiration Date)
(Chart) *
(Account) *
(Sub-Account) *
(Object) *
(Sub-Object) *
(Project) *
(Origin Code – Used by DaFIS)
(Indicates Punch-out vs Hosted Catalogs)
(Sender Payload ID)
(Sender Share Secret)
(Sender Credential Domain)
(Sender User Agent)
(Recipient Share Secret)
(Recipient Credential Domain)
(Recipient Identity)
(Vendor Request URL Address)
(Vendor Purchase Order URL Address)
(Active Indicator)
(Special Handling Indicator)
(UNSPSC Default Code)
(SHIP-TO ID)
(Punch-out Indicator T/F)
(Sender Credential Type)
(Deployment Mode – DEVEL, TEST, PROD)
(Alternate Address Sequence – Currently not used)
(Address ID Code – DeptBldg)
This is the account that needs to be utilized if the transaction received can’t find a corresponding order/item
(within the system).
Samples (Existing UCDBuy System)
UCDBuy/PCard Invoice Discrepancies
This report allows for a 7 day delay between the most recent vendor invoice and receipt of purchasing card charge.
Merchant Name
Order Number Invoice No.
Transaction Amount Total P-Card Amount
Invoice Amount
Difference Transaction Date
Posted Date
VWR INTERNATIONAL INC 0000472222
42899113
$112.60
$16.90
$1.36
($15.54)
08/17/2010
08/17/2010
FISHER SCI DEF
5417454
$124.25
$248.50
$124.25
($124.25)
09/22/2010
09/23/2010
$77.27
$77.27
$0.00
($77.27)
08/31/2010
08/31/2010
$2,071.52
$1,842.38
$2,071.52
$229.14
08/27/2010
08/30/2010
0000421826
DMI* DELL HIGHER EDUC 0000469921
DMI* DELL HIGHER EDUC 0000471870
XF2JP9NP1
UCDBuy/PCard Invoice Discrepancies






Click the Vendor Name to show only transactions for the credit card assigned to that vendor.
Click the Order Number to view the order in Decision Support.
Click the Invoice Number to view detailed information from Purchasing Card, Invoice and Sales tables.
If order or invoice number cannot be identified only information from Purchasing Card will be shown.
Click the REMOVE button to put in Accepted Discrepancy table.
Imbalances with invoice less than 7 days old are not displayed to allow time for purchasing card charge to arrive.
To remove related multiple transactions where the reason for acceptance is the same
check the checkbox for each transaction and the click the "Delete Multiple Discrepancies" button.
Catalog
Merchant Name
Order
Number
Invoice
No.
Transaction
Amount
Total P-Card
Amount
Invoice
Amount
Difference
Transaction
Date
Posted Date Remove
Laboratory
VWR
-
VWR
0000468290
INTERNATIONAL INC
43314433
$464.10
$232.94
$200.92
($32.02)
07/24/2010
07/26/2010
Laboratory
VWR
-
VWR
0000472222
INTERNATIONAL INC
42899113
$112.60
$16.90
$1.36
($15.54)
08/17/2010
08/17/2010
Laboratory
VWR
-
VWR
0000474718
INTERNATIONAL INC
43035575
$130.79
$19.61
$1.54
($18.07)
08/28/2010
08/30/2010
Laboratory
VWR
-
VWR
0000472222
INTERNATIONAL INC
42899113
($47.85)
$16.90
$1.36
($15.54)
09/15/2010
09/16/2010
Laboratory
VWR
-
VWR
0000468290
INTERNATIONAL INC
43314433
($196.34)
$232.94
$200.92
($32.02)
09/15/2010
09/16/2010
Laboratory
VWR
-
VWR
0000472222
INTERNATIONAL INC
42899113
($47.85)
$16.90
$1.36
($15.54)
09/21/2010
09/22/2010
Laboratory
VWR
-
VWR
0000474718
INTERNATIONAL INC
43035575
($111.18)
$19.61
$1.54
($18.07)
09/23/2010
09/24/2010
Laboratory
VWR
-
VWR
0000468290
INTERNATIONAL INC
43314433
($34.82)
$232.94
$200.92
($32.02)
09/24/2010
09/27/2010
Daily Invoice Transactions Discrepancies
Substitutions
Vendor
Order - Item PO
Commodity
No.
Commodity Code
Dell Computers
0000479486 - 1 224-2255
Office Max - 0000479611 - 1 P122651
UCDMC Catalog
Price Discrepancies
U/I Description
Inv.
Qty
Ship
Inv. Unit Inv.
Tax Inv. Total Date
Price
Amount
Amount
Shipped
Posted
Date
Invoice No.
A3567554
DESKTOP 1
EA WLS
MK710 UNIFY-R
$89.99
$7.87
$97.86
09/24/2010 09/27/2010 XF3CW5T73
P1MP-2241TE
RM PPR,BRITE TE 24# 1
8.5X11
$7.65
$0.63
$8.28
09/27/2010 09/27/2010 161920SEP2710
Vendor
Order - Item Commodity
U/I Description
No.
Code
Dell
0000478653 - 1 224-2257
Computers
Department Name:
EA 01:00 OPTIPLEX 1
960S;OptiPlex 960
Small Form Factor
Base
Standard
PSU
DANR: California State 4-H Office
Laboratory - 0000471138 - 1 MISC
Fisher
Scientific
Department Name:
Inv.
Qty
Ship
EA RESTOCKING
CHARGE
SM: Internal Medicine
PO Unit Inv. Unit Inv. Tax Inv. Total PO
Price
Price
Amount Amount Amount
$1,095.31 $1,095.30 $71.14
Percent
Date
Difference Shipped
$1,166.44 $1,185.67 -1.6219%
Posted
Date
Invoice
No.
09/24/2010 09/27/2010 XF3CP9XR5
F.A.U.: L-ARW3L04--8070--1
$682.37
$136.47
$0.00
$136.47
$738.67
-81.5249% 09/24/2010 09/27/2010 5668735
F.A.U.: S-ENRJ211--8030---
Over-Shipments
Vendor
Order - Item Commodity
No.
Code
U/I Description
Qty
Order
Laboratory - 0000479006 - 1 97014-322-PK PK VWR
BOX
VIAL 1
VWR
STORAG 2IN H PK12
Total
Inv. Qty Inv. Unit Inv.
Tax Inv.
Total Date
Qty Ship Ship
Price
Amount
Amount
Shipped
2
1
($17.72)
($1.46)
($19.18)
Posted
Date
Invoice
No.
09/27/2010 09/28/2010 43344252
UCDBuy Invoices No Order Match
Order - Item Commodity
No.
Code
Vendor
U/I Description
Qty
Ship
Inv.
Price
1
$10.97
$0.91
$11.88
09/22/2010 09/23/2010 5506202
SHIPMENT 1
$55.14
$0.00
$55.14
09/24/2010 09/27/2010 5668090
Laboratory
Scientific
-
Fisher -
NC9712479
EA O-RING
Laboratory
Scientific
-
Fisher -
MISC
EA DIRECT
CHARGE
Unit Inv.
Amount
Tax Inv.
Amount
Total Date
Shipped
Posted
Date
Invoice
No.
Laboratory
Scientific
-
Fisher -
1167824A
PK 2 CARDBOARD
12PK
BOX 12
$26.83
$28.17
$350.13
09/24/2010 09/27/2010 5668090
cXML Invoice Received (from Vendor)
<?xml version="1.0"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.009/InvoiceDetail.dtd">
<cXML version="1.2.011" payloadID="2007-06-19T09:59:08.8CDT.cXML.XC2JD11K8" timestamp="2007-06-19T09:59:08.8CDT" xml:lang="en-US">
<Header>
<From>
<Credential domain="DUNS">
<Identity>Dell</Identity>
</Credential>
</From>
<To>
<Credential domain="DUNS">
<Identity>ucdp</Identity>
</Credential>
</To>
<Sender>
<Credential domain="OracleSN">
<Identity>Dell</Identity>
<SharedSecret>UCDandDell</SharedSecret>
</Credential>
<UserAgent>Oracle Supplier Network</UserAgent>
</Sender>
</Header>
<Request deploymentMode="test">
<InvoiceDetailRequest>
<InvoiceDetailRequestHeader invoiceID="XC2JD11K8" purpose="standard" operation="new" invoiceDate="2007-06-18T12:00:00-6:00">
<InvoiceDetailHeaderIndicator/>
<InvoiceDetailLineIndicator/>
<InvoicePartner>
<Contact role="remitTo">
<Name xml:lang="en-US">DELL MARKETING L.P.</Name>
<PostalAddress name="default">
<DeliverTo>DELL MARKETING L.P.</DeliverTo>
<DeliverTo>C/O DELL USA L.P.</DeliverTo>
<Street>PO BOX 910916</Street>
<City>PASADENA</City>
<State>CA</State>
<PostalCode>91110-0916</PostalCode>
<Country isoCountryCode="US">US</Country>
</PostalAddress>
</Contact>
</InvoicePartner>
<InvoicePartner>
<Contact role="billTo">
<Name xml:lang="en-US">UCDavis</Name>
<PostalAddress name="default">
<DeliverTo>UCDavis</DeliverTo>
<DeliverTo>Materiel Management</DeliverTo>
<Street>Invoice Desk</Street>
<Street>202 Cousteau Place Ste 205</Street>
<City>Davis</City>
<State>CA</State>
<PostalCode>95618-7761</PostalCode>
<Country isoCountryCode="US">US</Country>
</PostalAddress>
<Email name="UCDavis">ucdep@ucdavis.edu</Email>
</Contact>
</InvoicePartner>
<InvoicePartner>
<Contact role="sales">
<Name xml:lang="en-US">BRIAN ROSALES</Name>
<PostalAddress name="default">
<Street>One Dell Way</Street>
<City>Round Rock</City>
<Country isoCountryCode="US">USA</Country>
</PostalAddress>
<Phone name="default">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<Number>2747799</Number>
</TelephoneNumber>
</Phone>
</Contact>
</InvoicePartner>
<InvoicePartner>
<Contact role="technicalSupport">
<Name xml:lang="en-US">default</Name>
<PostalAddress name="default">
<Street>One Dell Way</Street>
<City>Round Rock</City>
<Country isoCountryCode="US">USA</Country>
</PostalAddress>
<Phone name="default">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>2747799</Number>
</TelephoneNumber>
</Phone>
</Contact>
</InvoicePartner>
<InvoicePartner>
<Contact role="customerService">
<Name xml:lang="en-US">default</Name>
<PostalAddress name="default">
<Street>One Dell Way</Street>
<City>Round Rock</City>
<Country isoCountryCode="US">USA</Country>
</PostalAddress>
<Phone name="default">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>2747799</Number>
</TelephoneNumber>
</Phone>
<Fax name="default">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
</TelephoneNumber>
</Fax>
</Contact>
</InvoicePartner>
<InvoiceDetailShipping shippingDate="20070618T09:59:08.8CDT">
<Contact role="shipTo">
<Name xml:lang="en-US">UCDavis</Name>
<PostalAddress name="default">
<DeliverTo>UCDavis</DeliverTo>
<DeliverTo>VERLENDA SUTTON</DeliverTo>
<DeliverTo>Data Center and Client Services</DeliverTo>
<Street>IET CAMPUS DATA CTR</Street>
<Street>BAINER HALL DR.</Street>
<City>DAVIS</City>
<State>CA</State>
<PostalCode>95616</PostalCode>
<Country isoCountryCode="US">US</Country>
</PostalAddress>
<Email name="UCDavis">vsutton@ucdavis.edu</Email>
</Contact>
</InvoiceDetailShipping>
</InvoiceDetailRequestHeader>
<InvoiceDetailOrder>
<InvoiceDetailOrderInfo>
<OrderReference orderID="0000262364-1">
<DocumentReference payloadID="2007-06-18T10:34:50-0700@0000262364-1"/>
</OrderReference>
</InvoiceDetailOrderInfo>
<InvoiceDetailItem invoiceLineNumber="1" quantity="6">
<UnitOfMeasure>EA</UnitOfMeasure>
<UnitPrice>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">89.10</Money>
</UnitPrice>
<InvoiceDetailItemReference lineNumber="1">
<ItemID>
<SupplierPartID>GBA0477770</SupplierPartID>
</ItemID>
<Description xml:lang="en-US">01:00 Back-UPS ES 750 VA with Phone and Coax Protection</Description>
</InvoiceDetailItemReference>
<SubtotalAmount>
<Money>534.6</Money>
</SubtotalAmount>
<Distribution>
<Accounting name="AccountID">
<AccountingSegment id="0000262364-1">
<Name xml:lang="en-US">OLI</Name>
<Description xml:lang="en-US">3-ADMGENC-XPRES--</Description>
</AccountingSegment>
</Accounting>
<Charge>
<Money currency="USD">576.03</Money>
</Charge>
</Distribution>
</InvoiceDetailItem>
<InvoiceDetailItem invoiceLineNumber="2" quantity="2">
<UnitOfMeasure>EA</UnitOfMeasure>
<UnitPrice>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">170.10</Money>
</UnitPrice>
<InvoiceDetailItemReference lineNumber="2">
<ItemID>
<SupplierPartID>GBA0974063</SupplierPartID>
</ItemID>
<Description xml:lang="en-US">02:00 Back-UPS RS 1300 VA 120 V UPS System</Description>
</InvoiceDetailItemReference>
<SubtotalAmount>
<Money>340.2</Money>
</SubtotalAmount>
<Distribution>
<Accounting name="AccountID">
<AccountingSegment id="0000262364-2">
<Name xml:lang="en-US">OLI</Name>
<Description xml:lang="en-US">3-ADMGENC-XPRES--</Description>
</AccountingSegment>
</Accounting>
<Charge>
<Money currency="USD">366.57</Money>
</Charge>
</Distribution>
</InvoiceDetailItem>
</InvoiceDetailOrder>
<InvoiceDetailSummary>
<SubtotalAmount>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">874.80</Money>
</SubtotalAmount>
<Tax>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">67.79</Money>
<Description xml:lang="en-US">Total Taxes</Description>
<TaxDetail category="Sales Tax">
<TaxableAmount>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">874.80</Money>
</TaxableAmount>
<TaxAmount>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">67.79</Money>
</TaxAmount>
<Description xml:lang="en-US">state sales and use tax</Description>
</TaxDetail>
</Tax>
<SpecialHandlingAmount>
<Money description="Environmental Fee" currency="USD">0.00</Money>
</SpecialHandlingAmount>
<ShippingAmount>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">0.00</Money>
</ShippingAmount>
<NetAmount>
<Money currency="USD" alternateAmount="0.0" alternateCurrency="USD">942.59</Money>
</NetAmount>
<DueAmount>
<Money currency="USD">942.59</Money>
</DueAmount>
</InvoiceDetailSummary>
</InvoiceDetailRequest>
</Request>
</cXML>
cXML Response (various responses)
Invoice Accepted and Processed
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.011/InvoiceDetail.dtd">
<cXML payloadID="2010-29-09T10:05:36-0700@ucdavis.edu" timestamp="2010-29-09T10:05:36-0700" version="1.1">
<Response>
<Status code="201" text="Accepted ">Acknowledged Invoice - 2010-29-09T10:05:36-0700@ucdavis.edu </Status>
</Response>
</cXML>
Invoice Rejected Credentials not valid
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.011/InvoiceDetail.dtd">
<cXML payloadID="2010-29-09T10:05:36-0700@ucdavis.edu" timestamp="2010-29-09T10:05:36-0700" version="1.1">
<Response>
<Status code=" 401" text=" Unauthorized">2010-29-09T10:05:36-0700@ucdavis.edu -- Credentials provided were not recognized by the server.</Status>
</Response>
</cXML>
Invalid cXML received
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.011/InvoiceDetail.dtd">
<cXML payloadID="2010-29-09T10:05:36-0700@ucdavis.edu" timestamp="2010-29-09T10:05:36-0700" version="1.1">
<Response>
<Status code="406" text="Not Acceptable">An error occured while Parsing an XML document.</Status>
</Response>
</cXML>
The following table includes possible cXML status codes
Code
Text
Meaning
200
OK
The server was able to execute the request or deliver it to the final recipient. The returned Response might contain application warnings or errors:
the cXML Request itself generated no errors or warnings, however, this status does not reflect any errors or warnings that might be generated
afterward by the application itself. You will receive no further status updates, unless an error occurs during later processing.
201
Accepted
The request has been accepted for forwarding by an intermediate hub, or has been accepted by its ultimate destination and not yet been
examined. You will receive updates on the status of the request, if a mechanism to deliver them is available. As mentioned in
“StatusUpdateRequest” on page 202, the client should expect later StatusUpdate transactions.
204
No Content
All Request information was valid and recognized. The server has no Response data of the type requested. In a PunchOutOrderMessage, this status
indicates that the PunchOut session ended without change to the shopping cart (or client requisition).
280
The request has been forwarded by an intermediate hub. You will receive at least one more status update. This status could mean that the request
was delivered to another intermediary or to the final recipient with 201 status, or that it was forwarded via a reliable non-cXML transport.
281
The request has been forwarded by an intermediate hub using an unreliable transport (such as email). You might receive status updates; however,
if you do not received status updates, there is not necessarily a problem.
400
Bad Request
Request unacceptable to the server, although it parsed correctly.
401
Unauthorized
Credentials provided in the Request (the Sender element) were not recognized by the server.
402
Payment
This Request must include a complete Payment element.
Required
403
Forbidden
The user has insufficient privileges to execute this Request.
406
Not Acceptable
Request unacceptable to the server, likely due to a parsing failure.
409
Conflict
The current state of the server or its internal data prevented the (update) operation request. An identical Request is unlikely to succeed in the
future, but only after another operation has executed, if at all.
412
Precondition
A precondition of the Request (for example, a PunchOut session appropriate for a PunchOutSetupRequest edit) was not met. This status normally
Failed
implies the client ignored some portion of a previous transmission from a server (for example, the operationAllowed attribute of a
PunchOutOrderMessageHeader).
417
450
475
Expectation
Request implied a resource condition that was not met. One example might be a SupplierDataRequest asking for information about a supplier
Failed
unknown to the server. This status might imply lost information at the client or server.
Not
The server does not implement the particular Request. For example, PunchOutSetupRequest or the requested operation might not be supported.
Implemented
This status normally implies the client has ignored the server’s profile.
Signature
The receiver is unwilling to accept the document because it does not have a digital signature.
Required
476
Signature
The receiver is unable to validate the signature, possibly because the document was altered in transit, or the receiver does not support one or
Verification
more algorithms used in the signature.
Failed
477
500
Signature
The signature is technically valid, but is not acceptable to the receiver for some other reason. The signature policies or certificate policies may be
Unacceptable
unacceptable, the type of certificate used may be unacceptable, or there may be some other problem.
Internal Server
Server was unable to complete the Request.
Error
550
Unable to
Unable to reach next cXML server to complete a transaction requiring upstream connections. An intermediate hub can return this code when a
reach cXML
supplier site is unreachable. If upstream connections complete, intermediate hubs should return errors directly to the client.
server
551
Unable to
Unable to forward request because of supplier misconfiguration. For example, an intermediate hub failed to authenticate itself to a supplier.
forward
Clients cannot rectify this error, but this error might be resolved before the client retries.
request
560
Temporary
For example, a server might be down for maintenance. The client should retry later.
server error
GLIB Transaction
MMEP241 – should be the account the ghost card utilized for the transaction.
FY
2010
C ACCT
O
A
3 MMEP241
Obj
Cd
Bal
Type
0054
AC
Obj
Type
Code
AS
FP
Doc
Type
Origin
DocNo.
06
GLIB
L2
009120204
S
E
Q
1
Ledger Description
GENERATED OFFSET
GL Amt
$100.00
DB/
CR
Date
D
12/2/2009
ORG NBR
TRN POST
DT
12/2/2009
2010
3
MMEP241
3900
AC
RC
06
GLIB
L2
009120204
1
2010
3
V440AAA
0054
AC
AS
06
GLIB
L2
009120204
1
2010
3
V440AAA
8001
AC
EX
06
GLIB
L2
009120204
1
0 INC
.000 * RECHARGE INCOME *
GENERATED OFFSET
1 CY
100.00 ARGON 330 CU FT
$100.00
C
12/2/2009
$100.00
C
12/2/2009
$100.00
D
12/2/2009
*INCOME*
12/2/2009
12/2/2009
0000394880
12/2/2009