Print      Open PDF Version of Online Help


Previous Topic

Next Topic

Sample Transaction Fields

Use the Sample Transaction Edit page to add a sample transaction, or update details for an existing sample transaction that has a status of In Progress. The Sample Transaction Edit page shows the complete set of fields for a sample transaction.

TIP: You can also edit sample transactions on the Sample Transaction List page and the Sample Transaction Detail page. For more information on updating records, see Updating Record Details.

NOTE: Company administrators can customize Oracle CRM On Demand in a variety of ways, such as changing the names for record types, fields, and options in lists. So, the information you see might differ from the standard information described in the online help.

The following table provides additional information regarding some of the sample transaction fields. Depending on the type of sample transaction that you have open (Transfer In, Transfer Out, Inventory Adjustment, Disbursement, Samples Lost), all of these fields might not be applicable.

Field

Description

Key Transaction Information

Name

The unique identifier of the sample transaction (this is system generated).

Date

The date for the sample transaction.

When you enter a date that falls within an active inventory period, the Inventory Period: Start Date and Inventory Period: End Date fields are automatically populated. An error message displays if you enter a date that does not fall within any existing inventory periods, or a date that is greater than the current system date.

Sample transactions cannot be created for reconciled periods. An error message displays if you enter a date that falls within a reconciled period or an inactive period.

Type

The type of sample transaction can be one of the following:

  • Transfer Out
  • Inventory Adjustment
  • Samples Lost
  • Sample Request
  • Disbursement
  • Transfer In

Transfer Out, Inventory Adjustment, Samples Lost, and Sample Request are user generated transactions; Disbursement and Transfer In are system generated transactions.

NOTE: It is critical that you do not customize or change the order of the Type picklist for Sample Transaction Field Setup as the cascading picklist functionality may be affected.

Status

The status of the sample transaction can be one of the following:

  • In Progress
  • Submitted
  • Processed with Discrepancies
  • In Transit
  • Processed
  • Adjusted

Expected Delivery Date

The date that the sample is due to be delivered.

Tracking #

A unique number that you and the customer can use to track the delivery of the sample.

# of Packages Sent

The number of packages that are included in the sample.

Transfer To

The person to whom a transfer out transaction is logged. This person receives the sample and must acknowledge receipt of the sample.

When creating a transfer out transaction, this is a required field.

Transfer From

The person who is transferring the samples (that is, the person who creates the Transfer Out transaction).

Inventory Period: Start Date

The start date of the inventory period associated with the sample transaction. This is a read-only field, which is automatically populated only when the date that you enter in the Date field falls within an active inventory period.

The inventory period restricts the products and sample lot numbers that are available for selection when adding Transaction Item line items. It also ensures that for the selected inventory period, only valid products and sample lot numbers are available for selection.

Inventory Period: End Date

The end date of the inventory period associated with the sample transaction. This is a read-only field, which is automatically populated only when the date that you enter in the Date field falls within an inactive inventory period.

The inventory period restricts the products and sample lot numbers that are available for selection when adding Transaction Item line items. It also ensures that for the selected inventory period, only valid products and sample lot numbers are available for selection.

Adjustment Reason

The reason for creating or adjusting the sample transaction. Reason codes include the following:

  • Lost
  • Found
  • Theft
  • Human Error
  • Initial Count
  • Request

Comments

The user can enter additional information about the sample transaction in this field.

Attachment

If this field is exposed on the page, you can attach a file to the sample transaction record. The field initially shows a paper clip icon on the record Edit page:

Attachment

You can attach a file to the sample transaction record by clicking the paper clip icon on the record Edit page and then selecting the file that you want to upload.

After the file is uploaded and the record is saved, the Attachment field on the record Detail page shows the name and size of the attachment file. On the record Edit page, the field also shows the paper clip icon and an X icon that can be used to remove the file.

You can attach only one file to each sample transaction record.

For instructions on attaching files to records through the Attachment field, and information about the restrictions on file sizes and file types, see Attaching Files to Records through Attachment Fields.

Key Contact Information

NOTE: This read-only information is populated for disbursement transactions only. Oracle CRM On Demand automatically generates disbursement transactions whenever sales representatives drop or disburse samples during a sales call. For more information, see Dropping Samples During a Sales Call and Viewing Disbursement Transactions.

Contact

The full name of the physician or hospital contact to whom the disbursement was made.

Contact First Name

The first name of the contact to whom the disbursement was made.

Contact Last Name

The last name of the contact to whom the disbursement was made.

Contact Type

The contact type.

Contact Account

The account associated with this contact.

Contact Email

The email address for this contact.

Related Information

See the following topics for related, sample transaction information:


Published 5/4/2012 Copyright © 2005, 2012, Oracle. All rights reserved. Legal Notices.