Have you checked our new Android App!!! Please download and learn oracle at ease

November 28, 2012

Below are the setups need to be done before defining Items

Container Type:
Setup à Items à Container Type

Item Status:
Setup à Items à Item Status

 

Defining Picking Rule:

Move to Setup à Rules à Picking

Defining Item Types:

Setup à Items à Item types

 

Item Templates:

Setup à Items à Templates
Then select New

 

Overview of Item Categories:

·         Item Categories defined to group items logically according to different characters and this is used for different reports and programs.
·         Define Item Flexfields
·         Define Categories
·         Define Category sets
·         Assign default category sets to functional areas
·         Assign items to categories.

Define Flexfield Structure for Categories:

Setup à Flexfields à Key à Segments

Define Categories:

Setup à Items à Categories à Category Codes
Then select New

Define Category Sets:

Setup à Items à Categories à Category Sets

Item Catalogs:

Item Catalog is used to add descriptive information to items and to partition the item master into different groups of items which share common characteristics.
Once the process of defining and cataloging items is complete, you can:
·         Provide standard language in referring to items, enabling companies in the same industry to communicate effectively without needing to name their items identically.
·         Store a detailed description of what an item is without having to embed that meaning in the item number.
·         Use descriptive elements as search criteria for items.
·         Update the item description with a concatenated value of the item catalog group information.
·         Find common existing parts when developing an engineering prototype.
Setup à Items à Catalog Groups

Read More

1 comments:

November 27, 2012

Item Setups and Controls before defining Item

Certain set of Setups and controls need to be defined before defining an Item. These controls enable to maintain, group, query, reference and delete items.
1.       Create an Item Master organization to define all of your items. This enables you to assign items to other organizations without re-creating all of the item information.
2.       Set attribute control levels. Choose between centralized and decentralized control of item attributes. For each item attribute, you can determine whether the value of the attribute should be the same for an item in every organization in which you define the item.
3.       Define container types for the physical attribute group.
4.       Set status controls to use attributes, such as Purchasable and Transactable, to control the functionality of each item. You can set them for any type of item status.
5.       Define picking rules for the Order Entry attribute group.
6.       Define item types to use when defining items. These values appear in the list of values for the User Item Type item attribute.
7.       Define templates to assign major attributes that are the same for a group of items. Apply the template when you create an item, and fill in only the item attributes not already defined by the template.
8.       Define cross-references to establish relationships between items and entities such as old item numbers or supplier item numbers.
9.       Define commodity codes for use in customer items.
10.   Define customer items and customer item cross-references.
11.   Defining kanban cards and pull sequences.
12.   Define categories and category sets to group items for various reports and programs. A category is a grouping of items with similar characteristics. A category set is a grouping of categories.
13.   Define item catalogs to group items that share similar descriptive elements. Use the catalogs to search for items by descriptive elements instead of by part number.
14.   Optionally, define delete constraints that are verified before you can delete an item.
Read More

0 comments:

Defining Locators

Inventory Super User à Setup à Organization à Stock Locators

Select New
There are 4 tabs: Parameters, Capacity, Dimensions, and Coordinates.

Parameters:

Locator: Enter the Locator with specific segments as defined for your business.
Description: Enter a proper description to identify.
Subinventory: Enter the subinventory name where the locator resides.
Type: Select the type, how you want to use the locator.

Capacity:

Choose the Capacity alternative region.
Enter a value for the maximum number of items you can store in this locator.
Enter unit of measure and maximum volume values describing the volume of inventory that can be stored in this locator.
Enter unit of measure and maximum weight values describing the weight of inventory that can be stored in this locator.
Similarly enter the details for Dimensions and Coordinates.
Save your Jobs once done.
Read More

1 comments:

Defining Subinventory

Go to Inventory Super User responsibility
Setup à Organization à Subinventories

Click on New
Name: Should be a unique alphanumeric name
Description: Short description of the subineventory
Status: By default it takes as Active
Default Cost Group: Attach the Cost group here.
Type: Storage or Receiving, as per the requirement

Main Alternative Region:

Include in ATP: Indicate whether to include items in this subinventory in ATP calculations
Allow Reservation: Indicate whether to include this subinventory when you perform available-to-reserve calculations.
Nettable: Indicate whether the planning process uses the on-hand balance of these subinventory items as available inventory.
Quantity Tracked: Indicate whether each transaction for this subinventory updates the quantity on hand for the subinventory.
Note: If you leave this option unchecked, on-hand balances are not maintained and you cannot check or update the Asset Inventory, Include in ATP, Reservable, or Nettable options.
You can update this value only if there is no on-hand quantity for the subinventory.
Asset Subinventory: Indicate whether to maintain the value of this subinventory on the balance sheet.
Locator Control:
You can select an option only if you selected locator control as Determined at subinventory level in the Locator Control field in the Organization Parameters window. You can only update this option if there is no on-hand quantity for the subinventory.
None: Inventory transactions within this subinventory do not require locator information.
Prespecified: Inventory transactions within this subinventory require you to enter a valid predefined locator for each item.
Dynamic entry: Inventory transactions within this subinventory require you to enter a locator for each item. You may choose a valid predefined locator, or define a locator dynamically at the time of transaction.
Item level: Inventory transactions use locator control information that you define at the item level.
Picking Order: This value indicates the priority with which items can be picked from this subinventory, relative to another subinventory, where a given item resides.
Dropping Order: This value indicates the priority with which items can be dropped to this subinventory, relative to another subinventory at the time of receipt.
Inactive On: Enter the date, if you want this subinventory to inactivate.

Lead Times:

Optionally, enter pre-processing, processing, and post-processing lead times for items in this subinventory.
These lead times are used when you use min-max planning at the subinventory level.

Sourcing:

Select a source type for item replenishment
Inventory: Replenish items internally, from another subinventory in the same organization or another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
Subinventory: Replenish items internally from this subinventory.

Account:

Enter all General Ledger accounts as defined in the system as per the business requirement.
Save your job. This will create a subinventory.

GL Accounts Used in Subinventories
Material
Enter a general ledger account to accumulate material costs for items received into this subinventory. This is usually an asset account used for the value of goods stored in this subinventory.
For asset items, you use this account as a default when you generate purchase requisitions from MRP, min-max organization level planning, or reorder point planning. However, when you receive the purchase order, you use the appropriate valuation or expense account.
Outside Processing
Enter a general ledger account to accumulate outside processing costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you receive items for a job or schedule in Oracle Purchasing. Oracle Work in Process relieves this account at standard cost when you issue components to a job or schedule.
Material Overhead
Enter a general ledger account to accumulate material overhead or burden costs for this subinventory. This is usually an asset account.
Overhead
Enter a general ledger account to accumulate resource or department overhead costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you complete assemblies from a job or schedule. Oracle Work in Process relieves this account at standard when you issue components to a job or schedule.
Resource
Enter a general ledger account to accumulate resource costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you complete assemblies from a job or schedule. Oracle Work in Process relieves this account at standard cost when you issue components to a job or schedule.
Expense
Enter a general ledger account to accumulate expenses for this subinventory. For expense subinventories, this account is charged when you receive any item. For asset subinventories, this account is charged when you receive an expense item.
Encumbrance
ORACLE PURCHASING ONLY
Enter a general ledger account to hold the value of encumbrances against items in this subinventory. This account is used for purchase order receipts and returns.
Read More

1 comments:

November 22, 2012

Form Personalization

Oracle has provided a simple and easy feature to implement the customer specific requirements without modifying the underlying forms code or CUSTOM library. Although CUSTOM library still can be used for forms customization to implement the complex business logic, the personalization feature provided in the latest release is easy, faster and requires minimum development effort.
If user needs to personalize any details in a form like changing field names, adding some validations, etc, then Form Personalization can provide the way out in few simple steps.

Please follow here to go through Steps with example

Steps:

Step – 1:

Go to the specific form where you need the changes

Then we need to note down the block and field name which is needed in next steps.
So keep the cursor on the required field and then Go to Help --> Diagnostics --> Examine


Note down the Block and Field value.

Step -2:

Now the step to do the personalization
Follow this navigation
Help à Diagnostics à Custom Code à Personalize

This will show the Form Personalization window

Here you need to do the customization as per the requirement.
As you can see in this form, there are mainly 4 sections
1.       Rule
2.       Condition
3.       Actions
4.       Context

Step – 3:

Rule:

This is the section where you need to create the rules how your requirement is going to be executed. This section contains 4 segments, Seq, description, Level and Enabled flag.
Seq : Need to give the Sequence how the rule will execute (a number)
Description: Write a sort description of the rule which you are going to create
Level: Select the level where you want the rule to execute
Enabled: This is the flag which will enable or disable the rule.

Example:

Step – 4:

Condition:

Now need to set the condition.
This is the section where you will define when the rule will be executed.
This section contains 4 segments, Trigger Event, Trigger Object, Condition and Processing mode.

Trigger Event: This specifies where the rule will be executed. There are mainly 5 types of event which decided the trigger of the rule.

Trigger Object:  This is the Object in the form which decides at what level the rule will be executed.
The values can be “<Form Name>”, ‘<Block Name>” or “<Item Name>”
Condition: Here mention any SQL statement to control the execution of the rule when the mentioned criterion is met.
Processing Mode: This is the mode where you want the rules to be executed.

Example:

Step – 5:

Actions:

This decides what will happen when the rule will execute.
This contains 2 sections.
Left sections contains Seq, Type, Description, Language, Enabled
Seq: Mention the Action sequence which this rule will execute
Type: This is of 4 types, Property, Message, Builtin, Menu.
This decides which type of action, the rule will perform.
According to this the right section will come and need to fill the detailed actions.
Description: Write a description on the action which this will perform.
Language: Select the language
Enabled: You can enable or disable the actions here.
Right Section is a dynamic section; it appears depending on the Type field value in Left section.

Action Types:

Property
The action type “Property” is used to set the properties of the objects. The various objects include
“Item, Window, and Block etc.”.  Actual object name defined in the form should be entered after selecting the object type.
Property Name is the property to be changed
Value is the new desired value for the property.
The current value of the property will be displayed when clicked on the “Get Value” button.
Example:
Object Type = “Item”
Target Object = “:ORDER.ORDER_NUMBER”
Property Name = “PROMPT_TEXT”
Value = “Claim Number”
The value is interpreted at runtime, so you can use SQL functions and operators. Any value started with “=” operator will be interpreted at runtime; otherwise the value is treated as is entered in the value field


Message:
The action type “Message” is used to display custom messages during runtime. Message Type and Description should be entered after selecting the action type as “Message”. The available message types are “Error, Warning, Hint, Question and Debug”. Depending on the response expected from the user, the appropriate message type should be selected.
Example:
Message Type = “Hint”
Message Text = “Please Follow the Date format DD-MON-YYYY”


Builtin:
The action type “Builtin” is used to execute the form and AOL API’s. Depending on the API type selected, the parameters should be entered.
Example:
Builtin Type = FND_UTILITIES.OPEN_URL
Argument = http://www.oracle.com


Menu:
The action type “Menu” is used to activate the available special menus on the Tools menu.
Oracle Applications provide 45 special menus under Tools menu which can be used by customers based on their requirements.
Select the SPECIAL menu which is not used by the form. Menu label is the prompt which appears to the users when Tools menu is invoked, block specifies the blocks for which the special menu should be activated and Icon name is the .ico file name.
A separator can be created above the activated special menu by selecting the “Render line before menu” checkbox.
Example:
Menu Entry = SPECIAL4
Menu Label = Additional Order Header Information
Enabled in Blocks(s) = ORDER
Icon Name = Flower.ico


Step – 6:

Context:

Context manages to whom the personalization should apply. This is similar to the concept of using profile options in Oracle Applications. The various levels are Site, Responsibility, Industry and User. During runtime, the values provided in the context are evaluated and personalization rules will be applied. Usage of context is very vital in implementing the personalization to prevent the inappropriate users accessing these customizations of the form.
Example:
Context = Responsibility
Value = Order Management Super User



Step by Step Analysis

Requirement: Don’t allow the user to use more than 1 qty in Order line Qty field during creation of a sales order.

Solution:

Step -1:
Go to the specific form where you need the changes
Here in this case this will be the Sales Orders form and then Line Items tab.


Then we need to note down the block and field name which is needed in next steps.
So keep the cursor on the required field and then Go to Help à Diagnostics à Examine


Note down the Block and Field value.
Step -2:

Help --> Diagnostics --> Custom Code --> Personalize

Step – 3:
Fill the Rule section

Step – 4:
Fill the Condition section

Step – 5:
Fill the Actions section

Step – 6:
Fill the context As you need.
Save this.
Log out of the application and login again, then in Sales Order line item tab enter Qty field value as 1 and try to save, you can see the message.
Read More

6 comments:

Subscribe to

Help us to know you

Do you like learnoracle.in

Copyright © . Oracle Apps (SCM) . All Rights Reserved
Oracle Apps (SCM) is an online knowledge sharing blog which index online free tutorials, blogs and other sources, to get easier and accessible manner. The blog has been created keeping only one intention of sharing knowledge and for learning purpose. All trademarks, trade names, service marks, copyrighted work, logos referenced herein belong to their respective owners/companies. If any of the posting is violating copyright and you want us to remove that content. Please contact Here