Conventions for Describing Data Values Clause Samples

Conventions for Describing Data Values. ‌ Table 3-11 defines the data types used by BCRC for their external interfaces (inbound and outbound). The formatting standard defined for each data type corresponds to the data type identified for each field within the interface layout. This key is provided to assist in understanding the rules behind the formatting of the data values in the layout fields. Numeric Zero through 9 (0 to 9) Padded with leading zeroes Numeric (5): “12345” Numeric (5): “00045” Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM221 “ Text A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y” Text (18): “▇▇▇▇▇▇▇@▇▇▇▇▇▇.▇▇▇” Text (12): “ ▇▇▇-▇▇▇-▇▇▇▇” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces Populate with spaces Internal Use Populate with spaces Populate with spaces
View SourceView Similar (24)
Conventions for Describing Data Values. The table below describes the data types used by the BCRC for its external interfaces (inbound and outbound). The Formatting Standards used with each data type correspond to the requirements of the interface layout.
View SourceView Similar (2)
Conventions for Describing Data Values. The table below describes the data types used by the COBC for its external interfaces (inbound and outbound). The Formatting Standards used with each data type correspond to the requirements of the interface layout.
View SourceView Similar (2)
Conventions for Describing Data Values. The table below defines the data types used by COBC for their external interfaces (inbound and outbound). The formatting standard defined for each data type corresponds to the data type identified for each field within the interface layout. This key is provided to assist in understanding the rules behind the formatting of the data values in the layout fields. Data Type /‌ Field Formatting Standard Examples Numeric • Zero through 9 (0 € 9) • Padded with leading zeroes • Numeric (5): “12345” • Numeric (5): “00045” Alpha • A through Z • Left justified • Non-populated bytes padded with spaces • Alpha (12): “TEST EXAMPLE” • Alpha (12): “EXAMPLE “
View SourceView Similar (2)
Conventions for Describing Data Values. The table below defines the data types used by BCRC for their external interfaces (inbound and outbound). The formatting standard defined for each data type corresponds to the data type identified for each field within the interface layout. This key is provided to assist in understanding the rules behind the formatting of the data values in the layout fields. Numeric Zero through 9 (0  9) Padded with leading zeroes Numeric (5): “12345” Numeric (5): “00045” Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM221 “ Text A through Z (all alpha) + 0 through 9 (all numeric) + special characters: • Comma (,) • Ampersand (&) • Space ( ) • Dash (-) • Period (.) • Single quote (‘) • Colon (:) • Semicolon (;) • Number (#) • Forward slash (/) • At sign (@) Left justified Non-populated bytes padded with spaces Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “▇▇▇▇▇▇▇@▇▇▇▇▇▇.▇▇▇” Text (12): “ ▇▇▇-▇▇▇-▇▇▇▇” Text (12): “#34 “ Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces Populate with spaces Internal Use Populate with spaces Populate with spaces • The System shall be able to receive an external file from a VDSA partner. The System shall be able to confirm the external VDSA partner file format. • The System shall be able to match the valid VDSA partner external file to the Eligibility Database. • The System shall be able to update a CMS MSP record based on differences found between a valid VDSA partner external file and the Eligibility Database. • The System shall be able to create an MSP transaction file from the VDSA partner MSP record and the Beneficiary Master Record. • The System shall display error descriptions in CHAPS for severe errors identified on BCBS and VDSA files.
View SourceView Similar (2)

Related to Conventions for Describing Data Values

  • Contract Schedule The information set forth in the Contract Schedule is true and correct.

  • NASPO ValuePoint Summary and Detailed Usage Reports In addition to other reports that may be required by this solicitation, the Contractor shall provide the following NASPO ValuePoint reports.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Auction Schedule; Method of Submission of Orders (a) The Funds and the Auction Agent shall conduct Auctions for each series of Preferred Shares in accordance with the schedule set forth below. Such schedule may be changed at any time by the Auction Agent with the consent of the Fund, which consent shall not be withheld unreasonably. The Auction Agent shall give notice of any such change to BD. Such notice shall be received prior to the first Auction Date on which any such change shall be effective. Time Event ---- ----- By 9:30 A.M. Auction Agent advises the Funds and the Broker-Dealers of the Maximum Rate as set forth in Section 3.2(a) hereof.