|
Siebel Life Sciences Guide > Completing Contact and Account Call Activities >
Transaction Processing for Call Activities
This topic covers transaction processing for contact and account call activities. Clicking the Submit button on Pharma call activity views causes a number of important events to occur within the application. Table 15 describes the specific actions that occur when clicking the Submit button on each listed Pharma view.
Table 15. Effects of the Submit Button on Siebel Life Sciences Views
|
|
|
Clicking the Submit button... |
Contact Call Detail |
Call Activities screen, then the Contact Call Detail view |
Disbursement |
Changes the contact call detail Status field to Submitted. Except for the Comment field, sets the record to read-only. Sets all child records to read-only. NOTE: The Disburse on Signature Capture system parameter is set to TRUE by default. This means that when the user clicks the Save button on Signature Capture view, the application decrements the inventory count for Samples Dropped only. For Promotional Items Dropped, transaction records are generated upon submitting the call.
If samples were dropped, and the Disburse on Signature Capture system parameter is set to FALSE, then clicking the Submit button creates a Samples Transaction History record. |
Account Call Detail |
Call Activities screen, then the Account Call Detail view |
Disbursement |
Changes the account call detail Status field to Submitted. Except for the Comment field, sets the record to read-only. Sets all child records to read-only. If the Disburse on Signature Capture system parameter is set to TRUE, the application decrements the inventory count for Samples Dropped only when the user clicks the Save button on Signature Capture view. If samples were dropped, clicking the Submit button creates a Samples Transaction History record only if the Disburse on Signature Capture system parameter is set to FALSE. |
Received Samples |
Samples screen, Transaction, and then the Received Samples view |
Transfer In if the approval flow is enabled. Otherwise, the status changes to Processed. |
Updates the user inventory to reflect the quantity entered in Received Quantity field of the Line Items list. Updates Sample Invoices by setting the Active flag to N (No). If the Invoice Status is processed, the application updates the Line Items list by:
- Setting the Stock Update flag to Y (Yes)
- Updates the Stock Position ID
- Changes the Item Status to Submitted
NOTE: A dialog box displays if Acknowledged Qty is not equal to the Shipped Qty. You can close the transaction with discrepancy, or keep the transaction open with partial received. A notification is created for both the sender and the reviewer when the transaction status is Processed with Discrepancies.
|
Admin view: Sample Order |
Sample Order Management screen, then the Samples Orders view |
Sample Order |
Updates the Samples Orders list by setting the Active flag to N (No). If the Order Status is submitted, the application updates the Line Items list by:
- Setting the Stock Update flag to Y (Yes)
- Updates the Stock Position ID
- Changes the Item Status to Submitted
NOTE: The Process and Reject buttons are enabled for Sample Order submitted by the user. Click the Process button to generate a Sample Send transaction with information copy form the request. Only items that exist in the administrator's inventory is added to the generated transaction.
|
Inventory Adjustments |
Samples screen, Transaction, and then the Inventory Adjustments view |
Inventory Adjustment |
Updates the user inventory to reflect the quantity entered in Quantity field of the Line Items list. Updates Sample Adjustments by changing the Active flag to N (No). If the Transfer Status is Submitted, the application updates Line Items list by:
- Setting the Stock Update flag to Y (Yes)
- Updating the Stock Position ID
- Changing the Item Status to Submitted
NOTE: The status of the original transaction changes to Adjusted and excluded from the inventory count. The Adjust Transaction status changes to Processed.
|
Sent Samples |
Samples screen, Transaction, and then the Sent Samples view |
Transfer Out |
Updates the user inventory to reflect the quantity entered in Line Items list Quantity field. Updates My Sent Samples by setting the Active Flag to N (No), Changes the Status to Submitted. If the Transfer Status is Processed, the application updates the Line Items list by:
- Setting the Update Flag to Y (Yes)
- Updating the Stock Position ID
- Changing the Item Status to Submitted
NOTE: A corresponding Received Samples transaction is created for the receiver.
|
NOTE: For all sample transactions, the status changes to Processed if approval is not required.
When a user clicks the Submit button in either the Contact Call Detail or Account Call Detail views, the application verifies that:
The application checks if dropped samples are recorded for the call:
- The samples exist in the inventory for the period indicated by the call's date and time.
- The period into which the samples will be recorded is an unreconciled period. If it is a reconciled period, a warning message appears.
- A valid lot number has been specified for dropped samples tracked by lot number.
- The Ref # field is not empty (paper signature only).
If the call passes these checks, the application:
- Creates a samples disbursement transaction, with a line item for each dropped sample recorded for the call.
NOTE: If the Disburse on Signature Capture system parameter is set to TRUE, the application decrements the inventory count for Samples Dropped only when the user clicks the Save button on Signature Capture view.
- Submits a disbursement transaction to update the samples inventory. If the submission of the disbursement transaction is successful, the application changes the call's Status field to Submitted.
- Sets the Last Call Date field for the contact or account to the date of the submitted call, and many fields in the call record become read-only.
The Siebel administrator can change the fields that become read-only after a call is submitted (or synchronized with Siebel Mobile application for Siebel Pharma on a mobile device). For information, see Siebel Pharma Developer's Reference.
NOTE: If attendees are recorded in an account call, an attendee call is created for each attendee, and the process described above is performed for each attendee call. Attendee calls are the same as contact calls except that they do not appear in the Activities view, and they are submitted automatically when the account call is submitted.
|
