Siebel Field Service Guide > Repairs > Overview of Siebel Repair >

Inventory Transactions for Repairs


Repair activities, generated from an activity plan, move parts from inventory location to inventory location. Each time a part moves, an inventory transaction is generated. Validations are performed for each transfer; for example, to move an asset to a destination inventory location, it must belong to a source inventory location. These steps summarize the transaction process for an internal repair:

  1. Generate an inventory transaction as a Stock Transfer.
  2. Commit the inventory transactions.
  3. Update the inventory location ID (Prod_INV_ID) on the repair number (S_PART_RPR).

The rules for these inventory transactions are summarized in Table 133.

Table 133.  Rules for Inventory Transactions: Internal Repair
Inventory Level1
(InvLoc + Status + Avail)
 
Old Value
New Value
Transactions Required?
NULL
NULL
No
NULL
INV1
No
INV1
INV1
No
INV1
INV2
Yes. Normal inventory transaction as Stock Transfer, with all validations.
INV1
NULL
No

1Previously a "bucket."

Repairs Sent to a Third-Party Vendor

In Shipping > Repair Pick Ticket (seeRepair Pick Ticket View), the Process Shipment button generates transactions of the type Ship to TP (Third Party) to move a product from the defective inventory location to the third-party vendor, and sets the variables Defective and On Hand. This transaction updates the variables INVLOC_ID, INV_STATUS_CD, and INV_AVAIL_CD. These steps summarize the transaction process:

  1. Generate inventory transaction as Ship to TP and De-Allocate.
  2. Commit inventory transactions.
  3. Update the inventory location ID (Prod_INV_ID), inventory location (INVLOC_ID), status (INV_STSTUS_CD), and availability (INV_AVAIL_CD) on the Repair Number (S_PART_RPR), using the BusComp FS Repair Without Update logic.

The rules for these inventory transactions are summarized in Table 134.

Table 134.  Rules for Inventory Transactions: Send to Third-Party Vendor
Inventory
Transaction
Type
Source
Destination
Inventory
Inventory Level1
Assets2
Inventory
Inventory Level1
Assets2
Ship to TP
Source Invloc ID
Comes from the Service Order screen, Line Items view, Actions subview and is the Source Location field.
On Hand
Good/Defective
Yes
Destination Invloc ID
Comes from the Service Order screen Line Items view, Actions subview and is the Destination Location field.
On Hand
Defective
Yes
De-Allocate
Source Invloc ID
Comes from the Service Order screen, Line Items view, Actions subview and is the Source Location field.
Reserved
No
Customer
On Order
No

1Previously a "bucket."

2The assets rows are included in the transaction validation if the product is serialized.

Repairs Received from a Third-Party Vendor

On the Receiving screen, the Receive PO, Receive RMA, and the Receive Internal Order views, the Process Receipt command generates transactions, of the type Receive from TP, to move a product from a third-party vendor to the desired inventory location. This transaction updates the variables INVLOC_ID, INV_STATUS_CD, and INV_AVAIL_CD.

To receive an item from a third-party location, define the third-party location in the Orders screen, Terms view and the receiving location in the To Inventory field in the Receiving screen, Line Item Receipts view.

To go to the Receive PO, Receive RMA, or the Receive Internal Order view, first navigate to the Receiving screen, All Pending Orders view, and then click on a Receive Type field for any record. This exposes the Receive PO, Receive RMA, or Receive Internal Order views, with their subviews: [Receipt] Line Items, Received Line Item, and Serial Numbers.

These steps summarize the transaction process:

  1. Generate an inventory transaction as Receive from TP.
  2. Commit the inventory transaction.
  3. Update the inventory location ID (Prod_INV_ID), inventory location (INVLOC_ID), status (INV_STSTUS_CD), and availability (INV_AVAIL_CD) on the Repair Number (S_PART_RPR), using the BusComp FS Repair Without Update logic.

The rules for these inventory transactions are summarized in Table 135.

Table 135.  Rules for Inventory Transactions: Receive from Third-Party Vendor
Inventory
Transaction
Type
Source
Destination
Inventory
Inventory Level1
Assets2
Inventory
Inventory Level1
Assets2
Receive from TP
Source Invloc ID
Comes from Service Order screen, Line Items view, Actions subview
and is the Destination Location field.
On Hand
Defective
Yes
Destination Invloc ID
Comes from Service Order screen, Line Items view, Actions subview and is the Source Location field.
On Hand
Good/Defective
Yes

1Previously a "bucket."

2The assets rows are included in the transaction validation if the product is serialized.

Third-Party Vendor Swaps an Asset During Repair

If the third-party repair vendor returns a different part, the inventory transactions fails unless the new asset exists in the third-party inventory location. The user can accomplish this in one of two ways:

Returning to Good Inventory

To return a product to good inventory:

Changing the values in the repair record triggers an inventory transaction which changes the inventory quantity.

Shipping to a Customer

If the defective part was received with an RMA Repair/Return, then the repair center returns the part using the regular shipping process (Allocate, Pick Ticket, and Ship).

When the part is repaired, either internally or by a third-party vendor, it receives an inventory level; for example, On Hand/Good. When the part is shipped, the inventory transaction records the product movement, but the information on the Repairs screen still points to the same inventory level, that indicates the last location for the repaired item in inventory. The inventory movements for a product do not update the last location of the product in the repair record.


 Siebel Field Service Guide 
 Published: 21 April 2003