Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Overview


This structure represents the unique key fields associated with identifying an expense document. An expense document is a virtual container for individual expenses / cost cards. Expense Documents can be identified by DocumentNumber or DocumentId. When specifying a PwsExpenseDocumentRef as an input to a web service, you may specify one or both the DocumentNumber and/or ExpenseDocumentUid. However, if you do specify more than one field, they must both refer to the same expense document or the expense document reference will not be considered valid. When a PwsExpenseDocumentRef is returned in the response to a web service, the DocumentNumber and ExpenseDocumentUid will be populated, and guaranteed to refer to a single expense document.

Format


PwsExpenseDocumentRef
  • PwsExpenseDocumentRef
    • DocumentNumber: String (50)
    • ExpenseDocumentId: Int32
    • ExpenseDocumentUid: Int64

Elements


Element

Data Type

Required?

Description

Sample Data

DocumentNumber

String

One of DocumentNumber or ExpenseDocumentUid is required

The document number is a unique identifier for an expense document

ER00697 

ExpenseDocumentId

Int32

No

The expense document Id is a unique identifier for an expense document. For internal use only.

 

ExpenseDocumentUid

Int64

Please see DocumentNumber

A unique and immutable identifier for an expense document

1152921504607683544 

Usage Example(s)


Example 01
            <a:ExpenseDocumentIdentity xmlns:b="http://projectorpsa.com/DataContracts/Shared/Common/">
               <b:DocumentNumber>ER00697</b:DocumentNumber>
               <b:ExpenseDocumentId i:nil="true"/>
               <b:ExpenseDocumentUid>1152921504607683544</b:ExpenseDocumentUid>
            </a:ExpenseDocumentIdentity>
  • No labels