Transaction Source Types

A transaction source type is the type of entity against which Oracle Inventory charges a transaction. Along with a transaction action, it uniquely identifies the type of transaction you perform. When you perform a transaction, you specify a transaction type and a source. For example, for a PO receipt transaction, the transaction source type is Purchase Order and the actual PO number is the source.


Predefined Transaction Source Types

Oracle Inventory predefines a list of transaction source types for you. You can add more source types to this list or update the predefined types, however, you cannot delete the predefined types. Oracle Inventory provides the following predefined transaction source types:

• Account
• Account Alias
• Cycle Count
• Internal Order
• Internal Requisition
• Inventory
• Job or Schedule
• Layer Cost Update
• Move Order
• Periodic Cost Update
• Physical Inventory
• Project Contract
• Purchase Order
• RMA (Return Material Authorization)
• Sales Order
• Standard Cost Update

Updating a System-Defined Transaction Source Type

· Navigate to the Transaction Source Types window.


· Select the System Defined tabbed region.


· Update the name or description for a source type.


· Save your work.




Creating a User-defined Transaction Source Type


You can define additional transaction source types in the Transaction Source Types window. You can then use these user-defined transaction source types and predefined transaction actions to define a new transaction type. This user-defined transaction type is now a customized form of tracking transactions with which you can group and sort reports and inquiries. You can add source types for miscellaneous transactions, inter-organization and subinventory transfers, and account transactions


· Navigate to transaction source types window:


· Select the User Defined tabbed region.


· Enter a unique name for the transaction source type.


· Select a validation type:


· None: Do not validate the source against a predefined list of values.


· Value Set: Validate the source against a predefined list of values.


· If you select Value Set in the Type field, navigate to the Context field and select a valid context field value associated with the Transaction Source descriptive flexfield.


· Important: Values for this field are defined for the Transaction Source descriptive flexfield in the Descriptive Flexfield Segments window. See: Descriptive Flexfield Segments Window, Oracle Applications Flexfields Guide and Overview of Values and Value Sets, Oracle Applications Flexfileds Guide.


· Save your work.




Making a User-Defined Source Type Inactive:


· Select the User Defined tabbed region.


· Enter the date on which the source type becomes inactive.


· As of this date, you can no longer use the source type.




Deleting a User-Defined Source Type:





· You can delete a source type if it is not associated with a transaction type.