This document outlines a process to restrict a user from using account aliases that are incompatible with the transaction action in Oracle Apps. It involves defining an account aliases flexfield and values, then personalizing the Miscellaneous Transaction form to check the transaction action ID against allowed values from a generic dispositions flexfield when a new transaction line is created. The custom code will restrict the user if the values do not match.

1. Restrict User From Use Account Aliases Incompatible With Transaction Action
Purpose : Restrict User From Use Account Aliases Incompatible With Transaction Action
1- Descriptive Flexfield
AccountAliases

2. Value Set: SH TRANSACTION_ACTION_ID

3. Values
1 Issue FromStore
27 ReceiptIntoStore

4. DefiningAccountAliases

6. Personalization On Miscellaneous Transaction
Perform the following forms Personalization on Miscellaneous Transaction Form
1. Login to Oracle Apps with the specified user name and password
2. Navigate to Inventory Responsibility > Miscellaneous Transaction
3. Click Help > Diagnostics > Custom code > Click on the last selection: 'Personalize'
RestrictUser FromUse AccountAliase Incompatible WithTransactionAction-1

7. WHEN-NEW-BLOCK-INSTANCE
MTL_TRX_LINE
${item.mtl_trx_header.transaction_action_id.value}!=(SELECTATTRIBUTE1
FROMMTL_GENERIC_DISPOSITIONS
WHERE (ORGANIZATION_ID=:parameter.org_id)
AND DISPOSITION_ID=:SOURCE_FLEX_ID)

8. RestrictUser FromUse AccountAliase Incompatible WithTransactionAction-2
WHEN-NEW-BLOCK-INSTANCE
MTL_TRX_LINE
${item.mtl_trx_header.transaction_action_id.value}=(SELECTATTRIBUTE1
FROMMTL_GENERIC_DISPOSITIONS
WHERE (ORGANIZATION_ID=:parameter.org_id)
AND DISPOSITION_ID=:SOURCE_FLEX_ID)

10. Test