Phased rollout

This version of the software is currently available only to early adopter SaaS customers as the first step in our phased rollout. Click here to view an earlier version.

Content in dataload spreadsheets

This section provides an overview of the dataload spreadsheets. Additional instructions are provided within the spreadsheets. Data Management provides out-of-the-box dataload spreadsheets that can be copied to create your own spreadsheets.

Important

The out-of-the-box spreadsheets cannot be modified by a DMT User or DMT Admin. Only an AR Administrator can modify these spreadsheets.

Related topics

Adding Product Catalog entries Open link

Each workbook contains related spreadsheets. The first tab provides instructions for using the spreadsheet. Each of the subsequent tabs corresponds to the form into which the data is populated.

Column headings provide instructions for completing that column of the spreadsheets according to the following standards:

  • A green column heading indicates a required field.
  • An orange column heading indicates a field that might be required, depending on a value set in another column. 
  • Text in the first row provides instructions for entering data in the column.

The number above each column heading is the database length of the field. This number corresponds to the number of bytes in the field. For English and other single-byte languages, the number of bytes is the same as the number of characters. Double-byte languages use two bytes per character.

Validation on each column indicates if you entered data longer than this maximum allowed length.

The successful validation of field lengths in Microsoft Excel spreadsheets for multi-byte languages does not guarantee that the data will be imported successfully. The data import process uses the number of bytes when importing to fields while Excel validates the number of characters.

This validation occurs only when you type in the spreadsheet cells. If you bring in data by copying and pasting from another source or by importing data into the spreadsheet, you bypass the validation.

When you are completing spreadsheet fields that involve either selecting numbers or words, and your data is localized, you must select a number instead of a word.

This section provides tables of data values where the list of values was too lengthy to display in the spreadsheet.

    In the ProductCatalog.xlsx spreadsheet, the 01 PCT-ProductCatalog tab includes a column for configuration item (CI) type, which must be completed with one of the following values:

    • Account
    • Activity
    • Admin Domain
    • Application
    • Application Infrastructure
    • Application Service
    • Application System
    • BIOS Element
    • Bulk Inventory
    • Business Process
    • Business Service
    • Card
    • CDROM Drive
    • Chassis
    • Cluster
    • Communication Endpoint
    • Computer System
    • Connectivity Collection
    • Connectivity Segment
    • Database
    • Database Storage
    • Disk Drive
    • Disk Partition
    • Document
    • Equipment
    • File System
    • Floppy Drive
    • Hardware Package
    • Hardware System Component
    • Inventory Location
    • IP Connectivity Subnet
    • IP Endpoint
    • IPX Connectivity Network
    • Keyboard
    • Local Area Network (LAN)
    • LNs Collection
    • Local File System
    • Logical System Component
    • Mainframe
    • Media
    • Memory
    • Monitor
    • Network Port
    • NT Domain
    • Operating System
    • Package
    • Patch
    • Physical Location
    • Pointing Device
    • Printer
    • Processor
    • Product
    • Protocol Endpoint
    • Rack
    • Remote File System
    • Role
    • Share
    • Software Server
    • System Resource
    • System Software
    • Tape Drive
    • UPS
    • Virtual System Enabler
    • VM Ware
    • Wide Area Network (WAN)

    On the ProcessSetup-Incident.xlsx spreadsheet, the CFG_LoadDecisionTree tab includes a column for Locale, which is a required field that must be completed with a locale code, such as en_US for English (US).

    If you create decision trees in English or in any of the languages into which the application is localized, you might complete the column with any of the following locale codes:

    • de_DE 
    • en_US 
    • es_ES 
    • fr_FR 
    • it_IT 
    • ja_JP 
    • ko_KR 
    • pt_BR 
    • zh_CN
    • ru_RU


    Best practice

    If the environment is expected to be only English, do not install all locales that support version 8.3.04 and later. Some fields created by Process Designer on non-English locales might require manual layout updates.

    On the People.xlsx spreadsheet, the NTE_LoadCFGNotificationEvents tab includes columns for Module Name and Notification Event, both of which are required fields. This section lists the module names in Remedy ITSM along with the applicable notification events.

    BMC Remedy ITSM module

    Applicable notification events

    Asset Management

    • Asset Scheduled Decommission
    • Asset Scheduled Maintenance
    • Bulk Inventory Reorder
    • CI Status Change
    • Configuration Item Approval
    • Configuration Scheduled Maintenance
    • Contract Expiration
    • Contract Expiration Warning
    • Escalated Notifications
    • License Management Exception
    • Resolution Escalation
    • Response Escalation
    • Unavailability Assignment

    Broadcast

    Broadcast Notification

    Incident

    • Assignment 
    • Change Associations 
    • Incident Escalation 
    • Known Error Solution 
    • Known Error Workaround 
    • OLA Resolution Escalated Notification 
    • OLA Resolution Escalation 
    • OLA Response Escalated Notification 
    • OLA Response Escalation 
    • Ownership Assignment 
    • Problem Investigation Associations 
    • Problem Investigation Completion 
    • Resolution 
    • SLA Resolution Escalated Notification 
    • SLA Resolution Escalation 
    • SLA Response Escalated Notification 
    • SLA Response Escalation 
    • UC Resolution Escalated Notification 
    • UC Resolution Escalation 
    • UC Response Escalated Notification 
    • UC Response Escalation 
    • Unavailability Restored

    Infrastructure Change

    • Approval 
    • Approval Information 
    • Approval Resolution Escalated Notification 
    • Approval Resolution Escalation 
    • Change Coordinator Assignment 
    • Change Coordinator Approval Rejection 
    • Change Coordinator Completion 
    • Change Coordinator Latent Completion 
    • Change Coordinator Planning 
    • Change Coordinator Pre-planning 
    • Change Coordinator Re-scheduled 
    • Change Coordinator Scheduled 
    • Change Coordinator Scheduled For Review 
    • Change Manager Assignment 
    • Change Manager Approval Rejection 
    • Change Manager Completion 
    • Change Manager Group Escalation 
    • Change Manager Latent Completion 
    • Change Manager Next Dependent Change 
    • Change Manager Planning 
    • Change Manager Pre-planning 
    • Change Manager Predecessor Completion
    • Change Manager Re-scheduled
    • Change Manager Scheduled
    • Change Manager Scheduled for Review
    • Change Worklog Assignment
    • Implementer Assignment
    • Implementer Planning
    • Implementer Pre-planner
    • Implementer Scheduled
    • Manual Notification
    • Non-Approval Information
    • OLA Resolution Escalated Notification
    • OLA Resolution Escalation
    • OLA Response Escalated Notification
    • OLA Response Escalation
    • Requester Change Cancellation
    • Requester Change Receipt Confirmation
    • Requester Completion
    • Requester Change Re-scheduled
    • Requester Change Scheduled
    • Requester Rejection
    • SLA Response Escalated Notification
    • Task Cancellation
    • Task Pending
    • Unavailability Restored

    Problem Management

    • Change Completed 
    • Known Error Assignment 
    • Known Error Manager Assignment 
    • Problem Assignment 
    • Problem Cancelled 
    • Problem Completed 
    • Problem Coordinator Assignment 
    • Solution Assignment 
    • Unavailability Restored

    Reminders

    Reminders Notification

    Request Management

    • Assignment 
    • Request Cancellation 
    • Request Definition Status Changed 
    • Request Manager Assignment 
    • Request Rejected 
    • Request Response Escalation 
    • Request Status Changed
    • Request Submitted 
    • Work Order Assignee Assignment 
    • Work Order Manager Assignment 
    • Work Order Status Cancelled 
    • Work Order Status Completed 
    • Work Order Status In Progress 
    • Work Order Status Pending 
    • Work Order Status Rejected 
    • Work Order Submit

    Task Management

    • Task Assigned 
    • Task Status Changed

    This section lists the permission groups in BMC Remedy ITSM, along with the applicable license types. For a more detailed description of each permission group, see  Permission groups hierarchy Open link .

    Remedy ITSM permission group Applicable license types
    Read Fixed Floating None Not Applicable
    Activity Config



    Yes
    Activity User



    Yes
    Activity Viewer



    Yes
    Administrator



    Yes
    ApprovalAdmin



    Yes
    ASE-Administrator



    Yes
    Asset Admin
    Yes Yes Yes
    Asset Config
    Yes Yes Yes
    Asset User
    Yes Yes Yes
    Asset Viewer



    Yes
    Browser



    Yes
    CM Dashboard User



    Yes
    Command Event Master



    Yes
    Config Categorization Admin



    Yes
    Config Categorization User



    Yes
    Config Group Mapping Admin



    Yes
    Contact Location Admin



    Yes
    Contact Organization Admin



    Yes
    Contact People Admin



    Yes
    Contact People HR Admin



    Yes
    Contact People User



    Yes
    Contact Support Admin



    Yes
    Contract Admin
    Yes Yes Yes
    Contract Config
    Yes Yes

    Contract User
    Yes Yes Yes
    Contract Viewer



    Yes
    Cost Manager
    Yes Yes Yes
    Customize



    Yes
    DMT Admin



    Yes
    DMT User



    Yes
    DSL Master



    Yes
    DSL Viewer



    Yes
    Email Rule Config



    Yes
    Incident Config
    Yes Yes

    Incident Master
    Yes Yes

    Incident Submitter Yes



    Incident User
    Yes Yes

    Incident Viewer



    Yes
    Infrastructure Change Config
    Yes Yes

    Infrastructure Change Master
    Yes Yes

    Infrastructure Change Submit Yes



    Infrastructure Change User
    Yes Yes

    Infrastructure Change Viewer



    Yes
    Licensing


    Yes
    Notification Admin



    Yes
    Problem Config
    Yes Yes

    Problem Master
    Yes Yes

    Problem Submitter Yes



    Problem User
    Yes Yes

    Problem Viewer



    Yes
    Purchasing User
    Yes Yes

    Receiving User


    Yes
    Release Config


    Yes
    Release Master


    Yes
    Release User


    Yes
    Release Viewer



    Yes
    Requester Console Config



    Yes
    Requester Console Master



    Yes
    ROI Admin



    Yes
    ROI Viewer



    Yes
    Security



    Yes
    SLM Config
    Yes Yes

    SLM Customer
    Yes Yes

    SLM Manager
    Yes Yes

    Sub Administrator



    Yes
    Summary Definition Config



    Yes
    Task Administrator



    Yes
    Task Application Config



    Yes
    Task Manager



    Yes
    Task Process Config



    Yes
    Task User



    Yes

    On the Transactional-SharedComponents.xlsx spreadsheet, the SHR_LoadAssociation tab is used to specify associations (or relationships) between records. The following table shows valid relationship types.

    In the table, the Associated On Form is the parent form while the Associated To Form is the child form.

    Associated On Form Name

    Relationship Type

    Associated To Form Name

    AST:CI Unavailability

    Related to

    CHG:Infrastructure Change

    AST:CI Unavailability

    Related to

    HPD:Help Desk

    AST:CI Unavailability

    Related to

    PBM:Problem Investigation

    AST:CI Unavailability

    Related to

    RMS:Release

    AST:Configuration Item (CI)

    Used by

    CTM:People

    AST:Configuration Item (CI)

    Owned by

    CTM:People

    AST:Configuration Item (CI)

    Supported by

    CTM:People

    AST:Configuration Item (CI)

    Owned by

    CTM:Support Group

    AST:Configuration Item (CI)

    Supported by

    CTM:Support Group

    AST:Configuration Item (CI)

    Used by

    CTM:Support Group

    AST:Configuration Item (CI)

    Owned by

    CTM:People Organization

    AST:Configuration Item (CI)

    Supported by

    CTM:People Organization

    AST:Configuration Item (CI)

    Used by

    CTM:People Organization

    AST:Configuration Item (CI)

    Managed by

    CTM:People

    AST:Configuration Item (CI)

    Managed by

    CTM:People Organization

    AST:Configuration Item (CI)

    Managed by

    CTM:Support Group

    AST:Configuration Item (CI)

    Approved by

    CTM:People

    AST:Configuration Item (CI)

    Approved by

    CTM:People Organization

    AST:Configuration Item (CI)

    Approved by

    CTM:Support Group

    AST:Configuration Item (CI)

    Created by

    CTM:People

    AST:Configuration Item (CI)

    ALL

    CTM:People

    AST:Configuration Item (CI)

    ALL

    CTM:People Organization

    AST:Configuration Item (CI)

    ALL

    CTM:Support Group

    AST:Configuration Item (CI)

    Created by

    AST:PurchaseRequisition

    AST:Configuration Item (CI)

    Attached to

    AST:Contracts

    AST:Configuration Item (CI)

    Related to

    AST:PurchaseRequisition

    AST:Configuration Item (CI)

    Terms and Conditions of

    AST:Contracts

    AST:Configuration Item (CI)

    Impacted by

    TMS:Task

    AST:Configuration Item (CI)

    Moved by

    TMS:Task

    AST:Configuration Item (CI)

    Changed by

    TMS:Task

    AST:Configuration Item (CI)

    Installed by

    TMS:Task

    AST:Configuration Item (CI)

    Removed by

    TMS:Task

    AST:Configuration Item (CI)

    Related to

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Upgraded by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Repaired by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Impacted by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Moved by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Installed by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Removed by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Changed by

    CHG:Infrastructure Change

    AST:Configuration Item (CI)

    Related to

    HPD:Help Desk

    AST:Configuration Item (CI)

    Restored by

    HPD:Help Desk

    AST:Configuration Item (CI)

    Impacted by

    HPD:Help Desk

    AST:Configuration Item (CI)

    Restored by

    HPD:Template

    AST:Configuration Item (CI)

    Impacted by

    HPD:Template

    AST:Configuration Item (CI)

    Related to

    PBM:Problem Investigation

    AST:Configuration Item (CI)

    Related to

    PBM:Known Error

    AST:Configuration Item (CI)

    Related to

    PBM:Solution Database

    AST:Configuration Item (CI)

    Investigated by

    PBM:Problem Investigation

    AST:Configuration Item (CI)

    Impacted by

    PBM:Known Error

    AST:Configuration Item (CI)

    Impacted by

    PBM:Problem Investigation

    AST:Configuration Item (CI)

    Terms and Conditions of

    AST:LicenseCertificates

    AST:Configuration Item (CI)

    Attached to

    AST:LicenseCertificates

    AST:Configuration Item (CI)

    Related to

    RMS:Release

    AST:Configuration Item (CI)

    Upgraded by

    RMS:Release

    AST:Configuration Item (CI)

    Repaired by

    RMS:Release

    AST:Configuration Item (CI)

    Impacted by

    RMS:Release

    AST:Configuration Item (CI)

    Moved by

    RMS:Release

    AST:Configuration Item (CI)

    Installed by

    RMS:Release

    AST:Configuration Item (CI)

    Removed by

    RMS:Release

    AST:Configuration Item (CI)

    Changed by

    RMS:Release

    CHG:Infrastructure Change

    Related to

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Upgrades

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Repairs

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Related to

    CHG:Infrastructure Change

    CHG:Infrastructure Change

    Impacts

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Moves

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Installs

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Removes

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Changes

    AST:Configuration Item (CI)

    CHG:Infrastructure Change

    Dependent

    CHG:Infrastructure Change

    CHG:Infrastructure Change

    Related to

    AST:PurchaseRequisition

    CHG:Infrastructure Change

    Related to

    AST:CI Unavailability

    CHG:Infrastructure Change

    Related to

    HPD:Help Desk

    CHG:Infrastructure Change

    Caused

    HPD:Help Desk

    CHG:Infrastructure Change

    Corrects

    HPD:Help Desk

    CHG:Infrastructure Change

    Initiated by

    PBM:Known Error

    CHG:Infrastructure Change

    Related to

    PBM:Known Error

    CHG:Infrastructure Change

    Related to

    PBM:Problem Investigation

    CHG:Infrastructure Change

    Member of

    RMS:Release

    CHG:Infrastructure Change

    Related to

    RMS:Release

    CHG:Infrastructure Change

    Initiated by

    PBM:Solution Database

    CHG:Infrastructure Change

    Related to

    PBM:Solution Database

    HPD:Help Desk

    Related to

    AST:Configuration Item (CI)

    HPD:Help Desk

    Duplicate of

    HPD:Help Desk

    HPD:Help Desk

    Original of

    HPD:Help Desk

    HPD:Help Desk

    Related to

    HPD:Help Desk

    HPD:Help Desk

    Caused

    HPD:Help Desk

    HPD:Help Desk

    Caused by

    HPD:Help Desk

    HPD:Help Desk

    Restores

    AST:Configuration Item (CI)

    HPD:Help Desk

    Resolved by

    HPD:Help Desk

    HPD:Help Desk

    Resolved

    HPD:Help Desk

    HPD:Help Desk

    Impacts

    AST:Configuration Item (CI)

    HPD:Help Desk

    Related to

    AST:CI Unavailability

    HPD:Help Desk

    Related to

    CHG:Infrastructure Change

    HPD:Help Desk

    Caused by

    CHG:Infrastructure Change

    HPD:Help Desk

    Corrected by

    CHG:Infrastructure Change

    HPD:Help Desk

    Investigated by

    PBM:Problem Investigation

    HPD:Help Desk

    Related to

    PBM:Problem Investigation

    HPD:Help Desk

    Resolved by

    PBM:Known Error

    HPD:Help Desk

    Related to

    PBM:Known Error

    HPD:Help Desk

    Resolved by

    PBM:Solution Database

    HPD:Help Desk

    Related to

    PBM:Solution Database

    HPD:Help Desk

    Resolved by

    PBM:Problem Investigation

    HPD:Help Desk

    Related to

    RMS:Release

    PBM:Known Error

    Initiated by

    PBM:Problem Investigation

    PBM:Known Error

    Related to

    PBM:Problem Investigation

    PBM:Known Error

    Initiates

    PBM:Solution Database

    PBM:Known Error

    Related to

    PBM:Solution Database

    PBM:Known Error

    Related to

    AST:Configuration Item (CI)

    PBM:Known Error

    Related to

    PBM:Known Error

    PBM:Known Error

    Identified by

    PBM:Problem Investigation

    PBM:Known Error

    Impacts

    AST:Configuration Item (CI)

    PBM:Known Error

    Initiates

    CHG:Infrastructure Change

    PBM:Known Error

    Related to

    CHG:Infrastructure Change

    PBM:Known Error

    Resolved

    HPD:Help Desk

    PBM:Known Error

    Related to

    HPD:Help Desk

    PBM:Known Error

    Initiates

    RMS:Release

    PBM:Known Error

    Related to

    RMS:Release

    PBM:Problem Investigation

    Investigated by

    PBM:Problem Investigation

    PBM:Problem Investigation

    Investigates

    PBM:Problem Investigation

    PBM:Problem Investigation

    Related to

    AST:Configuration Item (CI)

    PBM:Problem Investigation

    Initiates

    PBM:Known Error

    PBM:Problem Investigation

    Related to

    PBM:Known Error

    PBM:Problem Investigation

    Related to

    PBM:Solution Database

    PBM:Problem Investigation

    Investigates

    AST:Configuration Item (CI)

    PBM:Problem Investigation

    Identified

    PBM:Known Error

    PBM:Problem Investigation

    Related to

    PBM:Problem Investigation

    PBM:Problem Investigation

    Impacts

    AST:Configuration Item (CI)

    PBM:Problem Investigation

    Related to

    AST:CI Unavailability

    PBM:Problem Investigation

    Related to

    CHG:Infrastructure Change

    PBM:Problem Investigation

    Investigates

    HPD:Help Desk

    PBM:Problem Investigation

    Related to

    HPD:Help Desk

    PBM:Problem Investigation

    Resolved

    HPD:Help Desk

    PBM:Problem Investigation

    Related to

    RMS:Release

    PBM:Solution Database

    Initiated by

    PBM:Known Error

    PBM:Solution Database

    Related to

    PBM:Known Error

    PBM:Solution Database

    Related to

    PBM:Problem Investigation

    PBM:Solution Database

    Related to

    AST:Configuration Item (CI)

    PBM:Solution Database

    Resolved

    HPD:Help Desk

    PBM:Solution Database

    Related to

    HPD:Help Desk

    PBM:Solution Database

    Created

    HPD:Help Desk

    On the Transactional-SharedComponents.xlsx spreadsheet, the SHR_LoadAssociation tab is used to specify associations (or relationships) between records. This tab includes two columns for Request Type that identify the request type of the two records being associated and that must be completed with one of the following text or numeric values:

    • 6000—Configuration Item 
    • 9000—Incident 
    • 12000—Infrastructure Change 
    • 15000—Solution Database 
    • 16000—Known Error 
    • 20000—Problem Investigation

    For more information, see Populating Service or CI fields in a record by using Transactional-SharedComponents.xlsx.

    On the Transactional-Change.xlsx spreadsheet, the CHG_LoadInfrastructureChange tab includes columns for Timing and Timing ReasonTiming is a required field on the Infrastructure Change form. Timing Reason is a required field for the Timing values listed in the following table. This table lists the values available for Timing and the corresponding values for Timing Reason

    Timing values Timing Reason numeric values Timing Reason text values

    Expedited

    1000

    Customer/business need

    2000

    Insufficient lead-time
    3000 Known error correction
    4000 Scheduling conflict

    On the Support_Group.xlsx spreadsheet, the CFG_BusinessTimeWorkdays tab and CFG_BusinessTimeHolidays tab include a column for time zone, which must be completed with the correct time zone offset for the region in which the support group is based.

    The time zone entry must take this form:

    • (GMT-12:00) Eriwetok, Kwajalein 

    • (GMT-11:00) Midway Island, Samoa 
    • (GMT-10:00) Hawaii 
    • (GMT-09:00) Alaska 
    • (GMT-08:00) Pacific Time (US & Canada); Tijuana 
    • (GMT-07:00) Arizona 
    • (GMT-07:00) Mountain Time (US & Canada) 
    • (GMT-06:00) Central Time (US & Canada) 
    • (GMT-06:00) Mexico City (Tegucigalpa) 
    • (GMT-06:00) Saskatchewan 
    • (GMT-05:00) Bogota, Lima, Quito 
    • (GMT-05:00) Eastern Time (US & Canada) 
    • (GMT-05:00) Indiana (East) 
    • (GMT-04:00) Atlantic Time (Canada) 
    • (GMT-04:00) Caracas, La Paz 
    • (GMT-03:30) Newfoundland 
    • (GMT-03:00) Brasilia 
    • (GMT-03:00) Buenos Aries, Georgetown 
    • (GMT-02:00) Mid-Atlantic 
    • (GMT-01:00) Azores, Cape Verde Is. 
    • (GMT) Casablanca, Monrovia 
    • (GMT) Greenwich Mean Time: Dublin, Edinburgh, Lisbon, London 
    • (GMT+1:00) Amsterdam, Copenhagen, Madrid, Paris, Vilnius 
    • (GMT+1:00) Belgrade, Sarajevo, Skopje, Sofija, Zagreb 
    • (GMT+1:00) Bratislava, Budapest, Ljubljana, Prague, Warsaw 
    • (GMT+1:00) Brussels, Berlin, Bern, Rome, Stockholm, Vienna 
    • (GMT+2:00) Athens, Istanbul, Minsk 
    • (GMT+2:00) Bucharest 
    • (GMT+2:00) Cairo 
    • (GMT+2:00) Harare, Pretoria 
    • (GMT+2:00) Helsinki, Riga, Tallinn 
    • (GMT+2:00) Israel 
    • (GMT+3:00) Baghdad, Kuwait, Riyadh 
    • (GMT+3:00) Moscow, St. Petersburg, Volgograd 
    • (GMT+3:00) Nairobi 
    • (GMT+3:30) Tehran 
    • (GMT+4:00) Abu Dhabi, Muscat 
    • (GMT+4:00) Baku, Tbilisi 
    • (GMT+4:30) Kabul 
    • (GMT+5:00) Ekaterinburg 
    • (GMT+5:00) Islamabad, Karachi, Tashkent 
    • (GMT+5:30) Bombay, Calcutta, Madras, New Delhi 
    • (GMT+6:00) Almaty, Dhaka 
    • (GMT+6:00) Colombo 
    • (GMT+7:00) Bangkok, Hanoi, Jakarta 
    • (GMT+8:00) Beijing, Chongqing, Hong Kong, Urumqi 
    • (GMT+8:00) Perth 
    • (GMT+8:00) Singapore 
    • (GMT+8:00) Taipei 
    • (GMT+9:00) Osaka, Sapporo, Tokyo 
    • (GMT+9:00) Seoul 
    • (GMT+9:00) Yakutsk 
    • (GMT+9:30) Adelaide 
    • (GMT+9:30) Darwin 
    • (GMT+10:00) Brisbane 
    • (GMT+10:00) Canberra, Melbourne, Sydney 
    • (GMT+10:00) Guam, Port Moresby 
    • (GMT+10:00) Hobart 
    • (GMT+10:00) Vladivostok 
    • (GMT+11:00) Magadan, Solomon Is., New Caledonia 
    • (GMT+12:00) Auckland, Wellington 
    • (GMT+12:00) Fiji, Kamchatka, Marshall Is

    For forms that include Status as a required field, Status Reason is a required field for the status values indicated in the following tables. These tables are grouped by the spreadsheet used to upload data to the forms.

    Status reasons for Transactional_CI.xlsx

    On the Transactional_CI.xlsx spreadsheet, the tabs include columns for Status and Status Reason. The following table lists the values available for Status and the corresponding values for Status Reason

    Status values Status Reason numeric values Status Reason text values
    Ordered no values no values
    Received no values no values

    Being Assembled

    no values no values
    Delete 4000 Obsolete
    Deployed no values no values
    Disposed 4000 Obsolete
    Down 1000 Scheduled
    2000 Maintenance
    3000 Out of Service
    End of Life 4000 Obsolete
    In Repair no values no values
    In Inventory no values no values
    On Loan no values no values
    Reserved no values no values
    Return to vendor 5000 RMA - Return To Vendor
    6000 RMA - Return to Distributor
    Transferred no values no values

    Status reasons for Transactional-Change.xlsx

    On the Transactional-Change.xlsx spreadsheet, the CHG_LoadInfrastructureChange tab includes columns for Status and Status ReasonStatus is a required field on the Change form. Status Reason is a required field for only certain Status values. The following table lists the Status values for which Status Reason is a required field and the values available for Status and the corresponding values for Status Reason.

    Status values Status Reason numeric values Status Reason text values
    Planning In Progress 28000 Accepted
    29000 Assigned
    30000 Built

    Implementation In Progress

    14000 In Rollout
    17000 In Development

    18000

    In Test
    19000 In Build
    20000 In Rollback

    21000

    In Documentation
    13000 In Verification
    Pending

    27000

    Manager Intervention
    25000 Miscellaneous
    22000 Vendor Purchase
    26000 Future Enhancement
    23000

    Support Group Communication

    24000 Task Review
    Rejected 12000 Insufficient Task Data
    15000 Insufficient Change Data
    16000 Schedule Conflicts
    Completed 10000 Final Review Required
    9000 Final Review Complete
    11000 Additional Coding Required
    Closed 5000 Successful
    6000 Successful with Issues

    7000

    Unsuccessful
    8000 Backed Out
    Cancelled 1000

    No Longer Required

    2000 Funding Not Available
    3000 To Be Re-Scheduled
    4000

    Resources Not Available

    Status reasons for Transactional-Release.xlsx

    On the Transactional-Release.xlsx spreadsheet, the RMS_Release tab includes columns for Status and Status ReasonStatus is a required field on the Release form. Status Reason is a required field for only certain Status values. If the Release Request Status is Pending then the Status Reason is Mandatory.

    Status values Status Reason numeric values Status Reason text values
    Registered 20200 Communication

    Pending

    21000 More information
    25000 Miscellaneous
    27000 Manager Intervention
    22000 Vendor Purchase
    26000 Future Enhancement
    20200 Communication
    28000 Change Review
    In Progress

    20100

    Planning

    20200

    Communication

    19000 Build

    20000

    Deployment

    18000 Test

    Rejected

    32000

    Schedule Conflicts

    33000

    Insufficient Data

    34000 Business Case Rejected
    Completed

    29000

    Final Review Required
    30000 Final Review Complete
    31000 Additional Coding Required
    Canceled


    35000

    No Longer Required
    36000 Funding Not Available
    37000 To Be Re-Scheduled
    38000 Resources Not Available
    Closed

    39000

    Successful

    40000

    Partially Deployed

    41000

    Unsuccessful

    42000

    Backed Out

    Status reasons for Transactional-Contract.xlsx

    On the Transactional-Contract.xlsx spreadsheet, the CTR_LoadContractBase tab includes columns for Status and Status ReasonStatus is a required field on the CTR:ContractBase form.

    Status values and corresponding Status Reason values are listed in the following table. The corresponding Status Reason values are optional. If no Status value is entered, the default value is Executed. 

    Status values Status Reason numeric values Status Reason text values
    Draft 

    2000

    In negotiation
    3000 Pending Signature
    Executed 1000

    Active

    4000

    Requires Attention

    5000

    Under re-negotiation

    6000 Change Pending
    7000 On Hold

    Historical

    8000 Expired
    9000 Terminated
    10000 Cancelled

    Status reasons for Transactional-Problem.xlsx

    On the Transactional-Problem.xlsx spreadsheet, several tabs include columns for Status and for Status ReasonStatus is a required field on each corresponding form. Status Reason is a required field for the Status values listed in the following table. This table lists the values available for Status and the corresponding values for Status Reason.

    Spreadsheet tab Status values Status Reason numeric values Status Reason text values
    Known Error Cancelled 1000 Duplicate
    2000 No Longer Applicable
    Corrected 3000 Pending PIR
    No Action Planned 4000 Funding Not Available

    Scheduled for Correction

    5000 Pending Infrastructure Change
    6000 Pending Third Party Vendor

    Problem Investigation

    Completed 1000 Known Error
    2000 Unresolvable
    3000 Solution Database
    4000 Enhancement Request
    Cancelled 5000 Duplicate Investigation
    Pending 6000 Local Site Action Required
    7000 Purchase Order Approval
    8000 Registration Approval
    9000 Infrastructure Change
    10000 Support Contract Hold
    11000

    Third Party Vendor Action Reqd

    12000 Pending Original Problem
    13000 Supplier Delivery
    14000 Request
    15000 Client Action Required
    16000 Client Hold
    17000 Monitoring Problem
    18000 Future Enhancement
    19000

    Automated Resolution
    Reported

    Solution Database Inactive 3000 Not Applicable

    Status reasons for Transactional-Incident.xlsx

    On the Transactional-Incident.xlsx spreadsheet, the HPD_LoadHelpDesk tab includes columns for Status and Status ReasonStatus is a required field on the Incident form. Status Reason is a required field for the Status values listed in the following table. This table lists the values available for Status and the corresponding values for Status Reason.

    Spreadsheet tab Status Reason numeric values Status Reason text values
    Pending 2000 Local Site Action Required
    3000 Purchase Order Approval
    4000 Registration Approval
    5000 Supplier Delivery
    6000 Support Contact Hold
    7000 Third Party Vendor Action Reqd
    8000 Client Action Required
    9000 Infrastructure Change
    10000 Request
    11000 Future Enhancement
    12000 Pending Original Incident
    13000 Client Hold
    14000 Monitoring Incident
    19000 Automated Resolution Reported
    Resolved 11000 Future Enhancement
    14000 Monitoring Incident
    15000 Customer Follow-Up Required
    16000 Temporary Corrective Action
    17000 No Further Action Required
    19000 Automated Resolution Reported
    Closed 1000 Infrastructure Change Created
    19000 Automated Resolution Reported
    Cancelled 20000 No longer a Causal CI


    On the Transactional-Incident.xlsx spreadsheet, the TMS_LoadTask tab includes columns for Status and Status ReasonStatus is a required field on the TMS:TaskGroup form. Status Reason is a required field for the Status values listed in the following table. This table lists the values available for Status and the corresponding values for Status Reason.

    Status values Status Reason numeric values Status Reason text values

    Closed

    1000 Success
    2000 Failed
    3000 Canceled

    Pending

    4000 Assignment
    9000 Error

    Staged

    5000 Staging in Progress
    6000 Staging Complete

    Waiting

    7000 Acknowledgement
    8000 Completion

    Status reasons for Transactional-Task.xlsx

    On the Transactional-Task.xlsx spreadsheet, the TMS_LoadTask tab includes columns for Status and Status Reason.

    Status Reason is a required field for the Status values listed in the following table. This table lists the values available for Status and their corresponding values for Status Reason. 

    Task Status values and corresponding Status Reason values 

    Status values Status Reason numeric values Status Reason text values

    Closed

    1000 Success
    2000 Failed
    3000 Canceled

    Pending

    4000 Assignment
    9000 Error



     

    Was this page helpful? Yes No Submitting... Thank you

    Comments