Overview

This structure represents the unique key fields associated with identifying a culture. Cultures govern how numbers are displayed (currency symbol, periods, commas, etc) on invoices. For example, if an engagement's currency is Canadian dollars, you will have two options for culture: English (Canada) and French (Canada). For some currencies, there are no options for Culture. Cultures can be identified by OpsCultureName or OpsCultureNumber. When specifying a PwsOpsCultureRef as an input to a web service, you may specify one or both the OpsCultureName and/or OpsCultureNumber. However, if you do specify both, they must both refer to the same Culture or the Culture reference will not be considered valid. When a PwsOpsCultureRef is returned in the response to a web service, both the OpsCultureName and OpsCultureNumber will be populated, and guaranteed to refer to a single culture.

Format

PwsOpsCultureRef

PwsOpsCultureRef
- OpsCultureId: Int16
- OpsCultureName: String (15)
- OpsCultureNumber: Int16

Elements

Element	Data Type	Required?	Description	Sample Data
OpsCultureId	Int16	No	The culture Id is a unique identifier for a culture. For internal use only.
OpsCultureName	String (15)	One of OpsCultureName or OpsCultureNumber is required	The culture name is a unique identifier for a culture	en-US
OpsCultureNumber	Int16	See OpsCultureName	The culture number is a unique identifier for a culture	1033

Usage Example(s)

Example 01

                  <b:EffectiveDefaultOpsCultureIdentity>
                     <b:OpsCultureId i:nil="true"/>
                     <b:OpsCultureName>en-US</b:OpsCultureName>
                     <b:OpsCultureNumber>1033</b:OpsCultureNumber>
                  </b:EffectiveDefaultOpsCultureIdentity>