Transaction Default (Available in Item Wizard from r12.2 onwards)
When it comes to using Transaction Default mode, it is using direct table insert. Unfortunately, there isn't Oracle API available for this mode, so users will need to be extra diligent in testing before making the move to the production environment.
Note:
Oracle R12.2.X has public APIs for ‘Transaction Default’. The customers who are using Oracle R12.2.X can use ‘Item Wizard’ for ‘Transaction Default Mode’, because all the modes in the Item Wizard use public APIs and do not require the profile to be set to 'Yes'.
Oracle API for Transaction Default Mode is not available in Oracle 11i and Oracle R12.1.X. However, the customers using Oracle 11i and Oracle R12.1.X can still use the ‘Item Extension Wizard’ for the ‘Transaction Default Mode’ with direct table insert enabled.
To be able to add Transaction Defaults both at Subinventory and Subinventory/Locator, to an item.
Requirements:
Set the profile ‘More4Apps: IEW Activate Transaction Default Mode’ to "Yes". Note that this is using a direct table insert into the Oracle tables and is not supported by Oracle.
Rules and Exceptions:
Transaction Defaults are defined for any inventory organization you have access to.
Table insert can only occur if the item exists in Oracle for that inventory organization.
An item can only have one transaction default per organization and transaction type - however if a locator is provided then an additional default per org/transaction type and locator is allowed. Note - A different Subinventory is also allowed for this second default. Therefore, a total of one default with a locator is allowed, and another without a locator is allowed.
Updates are allowed. The Wizard automatically works out if the transaction is a Create or Update Transaction.
Delete Transaction Defaults are allowed.
Functionality Type:
This load type uses a custom API not supported by Oracle.
User Form Layout:
Spreadsheet Data Columns:
• Transaction Type – The user can assign a Locator or Subinventory default to an item. This allows for differentiation between two default types, similar to Oracle functionality.
• Organization Code.
• Item Number - This is a required field. Item must exist in the organization and the transactable attribute set to ‘Yes’.
If restrict locators is set to ‘Yes’ then only the locators assigned to the item in the item/subinventory are allowed to be used and must be an item in Oracle.
• Default Type - This is a required field. Currently Oracle only supports receiving, shipping and move orders.
• Default Subinventory - This is a list of subinventories within the organization. If the item is set to restrict subinventories then the item must be assigned to a subinventory first and only those subinventories in the list can be used.
• Default Locator - This is a locator within a subinventory. If the item is set to restrict locators then only the valid locators can be used.
• Delete Transaction Default - A check is made to see if the Org/Item/Subinv/Default type or Org/Item/Subinv/Default type/locator exists. If so, then this value can be set to Yes.
Refer to section:
