Configuration Guide for Oracle CRM On Demand Life Sciences Edition > Setting Up a Business Process to Lock Records >

Creating a Business Process to Lock Sample Transaction Records


You can configure a business process to lock sample transaction records so that after a sample transaction is submitted, it cannot be modified. The following conditions apply:

  • When the transaction status is set to Submitted, Processed, or Processed with Discrepancies, you cannot edit any of the fields in the record because they are read-only (except for Comments), and you cannot delete the transaction record.
  • When the transaction status is set to In Transit, you cannot edit any of the fields in the record because they are read-only (except for the Comments and Date fields), and you cannot delete the transaction record. You can edit the Comments field after a transaction is submitted.

If you want to change a sample transaction that has already been submitted, then you must create a new sample transaction of the type Inventory Adjustment.

Use the following procedure to create a business process to lock sample transaction records in Oracle CRM On Demand Life Sciences Edition that satisfy these conditions. This task is a step in Setting Up Business Processes to Lock Records in Oracle CRM On Demand Life Sciences Edition.

NOTE:  This procedure is only an example. Configuring a business process to lock sample transaction records varies according to Oracle CRM On Demand installation, and depends on the customer's business rules for locking data.

To create a business process to lock sample transaction records in Oracle CRM On Demand Life Sciences Edition

  1. In Oracle CRM On Demand, click the Admin link, and then click Process Administration.
  2. Click New on the Process List page and on the Process Edit page:
    1. Enter a name for the process in the Process Name field, for example, Locking a Sample Transaction Record.
    2. In the Object Name field, select Sample Transaction from the menu.

      The Transition field automatically displays Status by default.

    3. (Optional) In the Description field, enter a description of the business process.
    4. Click Save.
  3. On the Process List page, open the business process (Locking a Sample Transaction Record) that you just created.
  4. On the Process Detail page, click Add in the Transition States section, and set up the transition states for the business process as described in the following table:
    State
    Disable Update Check Box
    Disable Delete/Remove Check Box

    Submitted

    Selected

    Selected

    In Transit

    Not selected

    Selected

    Processed

    Selected

    Selected

    Processed with Discrepancies

    Selected

    Selected

    Adjusted

    Selected

    Selected

  5. On the Process Detail page in the Transition States section, configure the transition states:
    1. Open the transition state.
    2. On the Transition State Detail page, click Add in the Field Setup section, add the required fields for the transition state, select the read-only check box for the fields as required, then click Save.

      For example:

      • For the Submitted, Processed, and Processed with Discrepancies transition states, select read-only for all fields except the Comments field.
      • For the In Transit transition state, select read-only for all fields except the Comments and Date fields.
    3. On the Transition State Detail page, click Add in the Related Access Control section, then add the related access controls for the transition state as described in the following table:
      State
      Record Type
      Disable Create/Add
      Check Box
      Disable Update
      Check Box
      Disable
      Delete/Remove Check Box

      Submitted

      Transaction Items

      Selected

      Selected

      Selected

      In Transit

      Transaction Items

      Selected

      Not selected

      Selected

      Processed

      Transaction Items

      Selected

      Selected

      Selected

      Processed with Discrepancies

      Transaction Items

      Selected

      Selected

      Selected

      Adjusted

      Transaction Items

      Selected

      Selected

      Selected

    4. Click Save.
  6. Sign out of Oracle CRM On Demand, and then sign in again for the changes to take effect.

Sample Transaction Record State Stage Definitions

Table 12 describes the state stages for a sample transaction record.

Table 12. Record State Stage Definitions for a Sample Transaction
State Stage
Description

In Progress

When you create a professional call or an account call, its state is initially set to In Progress.

Submitted

The sample transaction is submitted. For example, you can submit a sample transaction of the type Transfer Out.

InTransit

The sample transaction is in transit mode. For example, when you submit a sample transaction of the type Transfer Out, its status changes to Submitted, and Oracle CRM On Demand automatically creates a new recipient transaction record of the type Transfer In with a status of In Transit.

Processed

The sample transaction is processed without any discrepancies. For example, when you acknowledge the full receipt of a samples transfer, the status of the sample transaction changes to Processed. For more information about acknowledging full receipt of a samples transfer, see Oracle CRM On Demand Online Help.

Processed With Discrepancies

The sample transaction is processed with discrepancies. For example, when you acknowledge the partial receipt of a samples transfer, the status of the transaction changes to Processed with Discrepancies. For more information about acknowledging partial receipt of a samples transfer, see Oracle CRM On Demand Online Help.

Adjusted

The sample transaction has been adjusted. To resolve discrepancies between physical counts and electronic counts of the inventory, end users and samples administrators must create and submit adjustment transactions.

Rejected

The sample transaction has not been approved.

Configuration Guide for Oracle CRM On Demand Life Sciences Edition, Release 32 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.