, , , , ,

How to configure System Items Flexfield

1.    First define value set for item flexfield segments.
Go to inventory responsibility and navigate to value set.
Setup -> Flexfield->Validation->Sets
2.       Define Value Set for Item Section.
Choices: List Type, Enter format validation of your own choice, validation type.

3.       Define Value Set for Sub Section.
Sub Section Value Set is dependent on item section.
To configure select dependent validation type and click on Edit Information.
4.       Define Value Set For Serial No.
Serial No is also dependent on item section.
5.       Now value set for Condition Code and future segment.
Ok we are done with first part of creating value set. Now for second step .

6.       Navigate to Key Flexfield Segments Definition Form.
         Setup -> Flexfield->Key->Segments
7.       Now search with flexfield title “System Items”.
8.       Click on Segments and navigate to  Segment Summary Window.
Now enter your desired item segments name and their corresponding value sets.
Column indicates the database fields that will hold entered value for specific segment.
9.       After entering segments summary navigate back to KFF segments window. Save form and check freeze flex field definition option.
10.       Now compile your KFF.
      It is configured now.
/by
, , , ,

Configuring Work Day calendar in oracle Inventory

If you want to predict needs of your material or to plan material requirement then you can configure workday calendar for this.
Work day calendar(Oracle Inventory Calendar) provide lot of flexibility in terms of shifts, pattern for working days also you can configure exceptions.
Following are Configuration Steps.
1.       Go to work day calendar.
Setup>Organizations>Calendars

On Workday Calendar Window.

You can choose weekly calendar, monthly or periodic calendar type.
Like 4/4/5 is two four-week periods followed by one five week period and 5/4/4 is vice versa.
For twelve months in a year use calendar months.
 13 Periods is thirteen for week period’s year wise.
Start date and end date are very important in configuring work day calendar.
As your organization standard on and off days will be calculated on the base of start date along with week day.
i.e.  For standard five day week your start date must fall on Monday.
Ok it’s all done on work day calendar window.
Workday Patterns

Now navigate to Workday pattern window.
Like 5 days on 2 day off or 7 day on 0 day off. Whatever is your requirement?
Configuring Shifts

Multiple no of shifts can be configured for single calendar.

Enter shift start time and end time.
Likewise you can separately define different shifts and their specific time lines.

Now navigate back to Inventory Calendar window and save you work.
Saving your work will generate complete calendar from start date to end date given in calendar window.

Handling Exception
Click on any date and then navigate to exceptions window. Do this by choosing the exception list button.
Here you can define exception related to this date.
Like in following picture we create an exception by declaring and off day as on.

Save your work.

/by
, , , ,

How to Define Cost Type In Oracle Inventory

Cost type is required while we define any new organization.

Some cost types which are already defined are Average and Frozen.
Steps to Define.
Choose inventory responsibility and navigate to form.
Setup -> Costs -> Cost Types
On Cost Type Window

Default cost type is basically used for items where any specific type is not defined.
Date to inactivate cost is used to inactive your cost at specific date except for average and frozen cost type because frozen and average cost cannot by inactivate.
If multi org is checked then this type is available for all organization but not its costs.
If unchecked then this type is only available for organization which created it.
If allow update is checked then this cost type can be updated by available average cost update processes.

If for this type you want component yield effect in rollup then check this box.

Once Cost Type is defined let’s Move forward to Defining and configuring Inventory Organization

/by
, , , ,

New Terminologies in R12

Some of the new terminologies used in Oracle Applications Release 12 are:

11i Vs. 12

Sets of Books = Ledgers
Global Accounting Engine = Subledger Accounting
AX Posting Sets of Books = Secondary Ledgers
Global Intercompany System = Advanced Global Intercompany System
GL Intercompany Accounts = Intracompany Balancing
Translated Currency = Balance level RCs
Multiple Reporting Currencies = Reporting Currencies
MRC Primary Set of Books = Primary Ledger
MRC Reporting Set of Books = Reporting Currency
Thin MRC Reporting Book = Journal level RC
Full MRC Reporting Book = Subledger level RC
Translated Balance = Balance Level RC

Hope it will be helpful. ………..

/by
, , , , , , , , ,

R12: Create, Allocate and Transact a Move Order using APIs

Move Orders in Oracle provide good functionality for approval based movement of material with in an inventory organization. Move Order Approvals use a workflow (INV: Move Order Approval) for approvals and hence provide flexibility to extend it for approvals.
Move Orders can be created from different sources. These move orders are identified by Move order type at the header level.

Different types of move orders are:
Move Order Requisitions: These are created from the move order form. Based on the setup at the organization and item level, move orders require approval before they can be allocated and transacted. These requisitions can be created to charge an account or move the material from one subinventory to another.
Replenishment Move Orders: These are auto-created with pre approved status. Depending on the planning type you can replenish the quantity in a subinventory for an item. Three types of replenishment plans (in relation to move orders) are available:

  1. Min-max Replenishment Planning
  2. Kanban Replenishment Planning
  3. Replenishing Count planning

Based on these sources, when appropriate programs are run, move orders are automatically created.
Pick Wave Move Order Requisitions: These move orders are specifically for the sales order picking process. When Pick Releasing program is run move orders are created as preapproved and allocated. Pick Confirm process transacts these pick wave move orders.
Move orders contain headers and lines. All types of approved move orders have to be allocated (basically reserved) before they can be transacted. Depending on the item transaction controls (Subinventory, Locator, Revision, Lot or Serial number) move order creation and allocation gets complex.
The process is simple. Create and approve Move orders, allocate move order lines and transact them.
In this article let us review creating, allocating, and transacting a move order requisition of first type (requisitions) using APIs. These move orders will be created in pre approved status and hence do not use workflow. Move Order Issue transaction type is used in this example. An account is chosen while creating this move order. When successfully transacted, this account gets debited, crediting inventory account of the subinventory. From the user interface, to create Move orders, Move Orders window is used.
The lines are allocated when allocation step is performed. In this example the logic for allocation and transaction is borrowed from pick confirmation code. To allocate and transact same form is used: Transact Move Orders.
If the item is lot and serial number controlled (as in this example), you have to pass the lot number and serial number information into the move order lines table parameter. And also make sure to pass another parameter (p_suggess_serial) as true. This will automatically take care of allocating the lot and serial numbers into the appropriate table as mentioned in the process flow. Also when we allocate the move order from the user interface, the records in the form are created in the mtl_material_transactions_temp table with transaction_status as 2, which allows the user to change the values from user interface. But in order to perform transaction from SQL, you have to change this value to 3 so that the transaction manager can pick these records up. You find that logic in the allocating code.
The tables affected in each process step are mentioned in the process flow. Code for each step as well as complete code to create, allocate and transact can be see here:
Oracle R12 Create Order using APIs
Oracle R12 Allocate Order using APIs
Oracle R12 Transact Order using APIs
Oracle R12 Move Order using APIs

/by