Oracle R12 Order Management key table details & descriptions

Oracle R12 Order Management key table details & descriptions

Entered
OE_ORDER_HEADERS_ALL	This table records the sale order header details
OE_ORDER_LINES_ALL	This table records the sale order line details
OE_PRICE_ADJUSTMENTS	When discount gets applied
OE_ORDER_PRICE_ATTRIBS	If line has price attributes then populated
OE_ORDER_HOLDS_ALL	If any hold applied for order like credit check etc
Booked
OE_ORDER_HEADERS_ALL	Booked_Flag=Y, Order booked.
WSH_DELIVERY_DETAILS	Released_Status Ready to release
Pick Released
WSH_DELIVERY_DETAILS	Released_Status=Y Released to Warehouse (Line has been released to Inventory for processing)
WSH_PICKING_BATCHES	After batch is created for pick release
MTL_RESERVATIONS	This is only soft reservations. No physical movement of stock
Full Transaction
MTL_MATERIAL_TRANSACTIONS	No records in MTL_MATERIAL_TRANSACTIONS
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES
WSH_DELIVERY_DETAILS	Released to warehouse
WSH_NEW_DELIVERIES	If Auto-Create is Yes then data populated
WSH_DELIVERY_ASSIGNMENTS	Deliveries get assigned
Pick Confirmed
WSH_DELIVERY_DETAILS	Released_Status=Y Hard Reservations. Picked the stock. Physical movement of stock
Ship Confirmed
WSH_DELIVERY_DETAILS	Released_Status=C ; Shipped ; Delivery Note get printed Delivery assigned to trip stop quantity will be decreased
MTL_MATERIAL_TRANSACTIONS	On the ship confirm form, check Ship all box
WSH_NEW_DELIVERIES	If Defer Interface is checked then OM & inventory not updated. If Defer Interface is not checked: Shipped
OE_ORDER_LINES_ALL	Shipped_Quantity get populated
WSH_DELIVERY_LEGS	1 leg is called as 1 trip.1 Pickup & drop up stop for each trip.
OE_ORDER_HEADERS_ALL	If all the lines get shipped then only flag N
Auto Invoice
WSH_DELIVERY_DETAILS	Released_Status=I Need to run workflow background process.
RA_INTERFACE_LINES_ALL	Data will be populated after work flow process.
RA_CUSTOMER_TRX_ALL	After running Auto Invoice Master Program for
RA_CUSTOMER_TRX_LINES_ALL	Specific batch transaction tables get populated

Customer Information
HZ_PARTIES	This table stores basic information about customers
HZ_PARTY_SITES	This table links a party (HZ_PARTIES)and a location (HZ_LOCATIONS) and stores locations-Specific party information such as a person’s mail etc.
HZ_LOCATIONS	This table stores information about an address & provides physical location information about parties and customer accounts.
HZ_CUST_ACCOUNTS	This table stores the customer’s account number
HZ_CUST_ACCT_SITES_ALL	This table stores all customer account sites across all operating units. Customer account sites are addresses, for customer accounts, where the deploying company does business with its customers.
HZ_CUST_SITE_USES_ALL	This table stores business purposes assigned to customer account sites. Each customer account site can have one or more purposes.
RA_CUSTOMERS	This table stores Customer Name, Number & ID
Price Details
QP_LIST_HEADERS_B	This table stores the header information for all Price lists.
QP_LIST_LINES	This table stores the line information for all Price lists.
Items On Hand Qty
MTL_ONHAND_QUANTITIES	To check On Hand Qty Items.
Payment Terms
RA_TERMS	Payment terms
Sales Order Holds
OE_HOLD_DEFINITIONS	This table stores information about hold name and its validity period
OE_HOLD_AUTHORIZATIONS	This table stores information about who has the authority to apply and release holds.
OE_HOLD_SOURCES_ALL	This table stores information of the hold source criteria.
OE_ORDER_HOLDS_ALL	This table stores information of all the orders and lines that are on hold and the link to hold sources and hold releases.
Hold Release
OE_HOLD_RELEASES_ALL	Hold released Sales Order
Credit Check Details
OE_CREDIT_CHECK_RULES	To get the Credit Check Against Customer.
Cancel Orders
OE_ORDER_LINES_ALL	Cancel Order Details.
Automatic Numbering System
AR_SYSTEM_PARAMETES_ALL	You can check Automatic Numbering is enabled/disabled
Document Sequence
FND_DOCUMENT_SEQUENCES	Document Sequence Numbers
FND_DOC_SEQUENCE_CATEGORIES	This table stores information about document categories that are defined for various products in the Oracle Applications product suite. Each row includes an identifier of the application to which the category belongs, the name of the category, the category code, the name of the database table storing the category, and a description for the category.
FND_DOC_SEQUENCE_ASSIGNMENTS	This table stores information about assignments of document sequences to various documents.
Default Rules For Price List
OE_DEF_ATTR_DEF_RULES	Price List Default Rules
End User Details
CSI_T_PARTY_DETAILS	To capture End user Details
Sales Credit
OE_SALES_CREDITS	Sales Credit Information
Attaching Documents
FND_ATTACHED_DOCUMENTS	Attached Documents and Text information
FND_DOCUMENTS_TL	Fnd documents short text
Blanket Sales Order
OE_BLANKET_HEADERS_ALL	This table stores the common Attributes between sales order and sales agreements at header level
OE_BLANKET_LINES_ALL	This table stores the common Attributes between sales order and sales agreements at line level
Processing Constraints
OE_PC_ASSIGNMENTS	Sales order Shipment Schedule Processing Constraints

Oracle Advanced Pricing - Promotion Goods Modifier

Oracle Advanced Pricing - Promotion Goods Modifier

Oracle Order Management provides Promotion Goods feature using Oracle Advanced Pricing Modifier type “Promotion”

Example: If customer orders for Part A, then Part B to be supplied as a Promotional Goods.

1. Both the Part numbers are to be defined in Item Master and assigned to same organization.

2. Both the Part numbers are to be defined in Price List

3. Define a new Modifier with Modifier Type as “Promotion”, Modifier Number, enable Active & Automatic Flags, Modifier Name & Currency.

4. Define Modifier type as “Promotional Goods”& Start Date

5. Define Pricing Phase, Product Attribute as “Item Number” and Product Attribute Value (Part A)

6. Define Volume Type as “Item Quantity”, Break Point as “Point”, Operator as “Between”, UOM & Value From & To

7. Click Define Details and Define Get Product Attribute as “Item Number”, Get Product Value (Part B), UOM, Get Quantity

8. Define Qualifier for this Modifier for a customer & Save the Modifier

9. Run the “Build Attribute Mapping Rule” Concurrent

10. Create a Sales Order for the customer and Part Number A, once the Order is Booked Automatically System includes the Promotional Part number will be included in the sales Order

Setting User Password Requirements in Oracle Applications

Setting User Password Requirements in Oracle Applications

This post describes the optimal security in login password usage using below Below Profile settings in Oracle Application R12:

1.       Setting Password Case Sensitivity Requirement

2.       Setting Password Length Requirement

3.       Setting Hard to Guess Requirement

4.       Enabling Forgot Your Password Functionality

5.       Setting Login Attempt Limits

6.       Setting Time Limit after Resetting Password

1. Setting Password Case Sensitivity

Profile Option Name “Signon Password Case”

This profile determines whether the User Passwords can be treated as case sensitive / insensitive. Based on the profile option – Values defined.

a. Sensitive: All newly created or changed passwords are treated as case sensitive.
b. Insensitive: Passwords are treated as case insensitive.

Note: Passwords for existing user accounts must be reset after you change this setting.

2. Setting Password Length Requirement

Profile Option Name “Signon Password Length”

This profile determines the minimum number of characters required in a user password. The default setting is 5. Oracle recommends a setting of 8 or more.

3. Setting Hard to Guess Requirement

Profile Option Name “Signon Password Hard To Guess”

This profile enforces requirements that make it more difficult to guess what another user's password might be. These requirements come as a package; you must either accept or reject the whole. Oracle recommends a setting of Yes to accept the package.

4. Enabling Forgot Your Password Functionality

Profile Option Name “Local Login Mask”

Oracle recommends a setting of 40 for the Local Login Mask profile. This setting displays a "Forgot your password?" link on the Login page. If the user clicks this link, the system loads a page where the user can enter his or her username.

The user then receives an email stating, "Password reset requires approval." The user needs to click one of the choices "Approve" or "Reject" that automatically generate an email response. If the user ignores the notification, the request expires in four hours.

5. Setting Login Attempt Limits

Profile Option Name “Signon Password Failure Limit”

This profile option determines the maximum number of logins a user can attempt before the user's account is disabled. To reinstate the account a system administrator must unlock the account and reset the password. For example, if the value set is 3, it will lock the account if the user enters incorrect password 3 times.

6. Setting Time Limit after Resetting Password

Profile Option Name “Signon Password No Resuse”

This profile will set the minimum number of days that a user must wait after changing password before being allowed to reuse a password. The user can use the new password once and then must wait the number of days set before user can reuse the password.

For example, if the value of this profile is set to 5, a user who changes the password cannot reuse the password until 5 days after they reset.

If the profile value is set to the number 0, then there is no restriction on password reuse.

User Passwords Case Sensitivity in Oracle Application R12

User Passwords Case Sensitivity in Oracle Application R12

User Passwords Case Sensitivity in Oracle Applications in previous releases of Oracle Applications, user passwords were treated as case insensitive.

Now, Oracle Applications R12 user passwords can optionally be treated as case sensitive, depending on the Profile Option defined.

Case-sensitivity in user passwords are controlled by the Site Level Profile option "Signon Password Case"

This profile has two possible settings:

1. Sensitive:

Passwords are stored and compared as they are, with the password case preserved. During comparison, if the entered password does not match the decrypted version, then an error message is displayed. With Release 12, this option is the default behavior. All newly created or changed passwords are treated as case sensitive.

Note: Users who have not changed their passwords since the installation of release 12 are not affected until they do change their passwords. A password expiration utility is available if the System Administrator requires that all users convert to case sensitive passwords upon the next login.

2. Insensitive:

Passwords are treated as case insensitive. In Insensitive mode, passwords are stored and compared in uppercase, similar to that in earlier releases. The entered password and the decrypted password are converted to uppercase prior to comparison.

If you want to preserve case insensitivity in passwords, i.e. retain the behavior from previous releases, ensure that Signon Password Case value is either set to 'Insensitive', or not set at all.