Siebel Life Sciences Guide > Closing Adverse Events and Complaints >

Reviewing Lockdown Fields (End User)


About Lockdown Fields

For most purposes, you want your product issue data to contain the up-to-date information. For example, if an account has changed its name, you want have its current name appear in all product issues records so that a query for the current name returns the complete set of product issues associated with the account, both before and after the name change.

However, for record keeping, you may also want to maintain some relational data exactly as it was when the product issue was closed. For example, after the product issue was closed, Dana Frederick changes her name to Dana Feldman. Her new name was updated through the Contacts screen, and this change is reflected in the current product issue record. However, the Lockdown view for the product issue shows Dana's name when product issue was closed. (See Figure 24.)

Figure 24. Lockdown Example
Click for full size image

The application should be configured so that the fields appropriate for your business processes are locked down. In the preconfigured application, some fields are locked down at review complete and others are locked down when the product issue is closed.

How to Review Locked Down Fields for a Product Issue

This task is a step in Process of Closure for AECM.

To view lockdown fields for a product issue

  1. Navigate to Product Issues screen > Product Issue List view.
  2. Drill down on a product issue.
  3. Click the Lockdown view tab.

    Lockdown fields show the field values as they were when the product issue was closed.

    NOTE:  For multivalue fields, only the primary value is locked down.

Siebel Life Sciences Guide Copyright © 2008, Oracle. All rights reserved.