Inventory organization setting procedure

Last Update:2014-01-10 Source: Internet

Author: User

Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

This document helps you successfully define inventory organizations in Oracle inventory applications

Applicability and Applications

This document applies to Oracle EBS 11i, R12, and all updated versions.

This document describes how to set the proper order of one or more new organizations. It aims to supplement and clarify the documents provided by the application. This is intended for new or common users in the inventory module. The necessary setup steps are explained in this document. More setup steps vary by version. For specific application versions, see the inventory user manual.

Related Documents

Oracle Manufacturing Implementation Manual

Oracle inventory User Manual

Oracle inventory Technical Reference Manual

You can use My Oracle Support> knowledge> Online Documentation> E-Business Suite documents and select your version.

Details

Inventory organization setting procedure

Procedure

L perform the following steps in sequence.

L to successfully define an organization in the inventory module, these are basic steps.

L more information about these steps and other optional steps can be found in inventory settings in the Oracle Manufacturing Implementation Manual.

Define a set of accounts (general ledger function) to define primary key elastic domains in the following order.

Path: Define/elastic domain/primary key.

Elastic domains to be set: system materials, material categories, material Category groups, storage space, account aliases, and sales orders

Define a location (for many features, including receiving and default shipping locations ).

Note: If you enter an organization in the form, only the organization that is displayed in the LOV is displayed. If the organization field on this interface is assigned a value, it will only be displayed in the drop-down list of the Organization.

Defines a calendar of work days, also known as a calendar of manufacture.

Each organization is associated with this calendar to schedule activities. Optional; defines a calendar exception set. Once completed, click 'special 'and create a calendar. We recommend that you define a calendar from the first day of the working week. For example, if the main calendar of work is from Monday to Friday and is closed on Saturday and Sunday, set the start date on the calendar as Monday and end date as Sunday.

Note: A calendar must define at least one shift and one working day. Use the date key to view the accuracy of the calendar before creation.

Define the organization.

Assign and enable corresponding organization categories for each defined organization (based on the expected structure ).

Note: There must be at least one inventory and one legal entity organization. The Business Group category is not required unless the multi-organization function is used.

Complete the minimum required information in each selected category.

A) Legal entity; a company identification number and set of books must be defined.

B) business entity; a legal entity must be defined. Business entities are optional.

C) Inventory organization;

I) accounting information, set of accounts, legal entities, and business entities (not independent ).

Ii) inventory information; Organization Code, material main organization and calendar, cost calculation organization and method, accounting information (this definition is in cost calculation, inter-organization and other accounting areas ), other settings are optional based on the customer's needs.

Iii) Receiving and customer/supplier information are optional.

Define the unit category. Then define the unit, and then define the unit conversion for the application.

Note: Each classification can have only one basic unit. Generally, the basic unit should be the minimum unit in the classification. There should be a logical relationship between units in a category. When the unit is invalid, the unit is converted first, and then the unit is invalid. If the unit is invalid, the Unit should also be invalid. Be careful. Once an item is defined in the main organization, the main unit of the item cannot be modified.

Define sub-inventory in the organization to represent the physical or logical location of the material.

The name and description must be completed. Other information is optional based on the customer's needs. At least one sub-inventory is defined in an organization.

The remaining organization definitions are optional based on the customer's needs.

A) define a slot to represent the storage structure of sub-Inventory (such as channels and boxes ).

B) define shipping networks and shipping methods to help inter-organizational transfers.

C) define the carrier

D) Define organization access. If a customer defines any access information for an organization, they must define all responsibilities for the organization they want to access. Otherwise, the non-column responsibilities do not work in the Organization.

E) define inter-company relationships for inter-organizational functions.

If these steps are completed, the organization is set up and can be used. Next, you should set the remaining parts of the inventory system. See the Oracle production implementation guide or the Oracle inventory User Guide to set the default values of materials, categories, costs, transactions, and other features of the Oracle inventory system. You can also contact Oracle global technical Support or My Oracle Support to obtain a list of patches important to the inventory module before implementing a new inventory. Note 726226.1: INV/WMS/RCV Family Patch Release History/Patchsets/RUPs ..

Configuration File

MO: Business Entity = {user business entity name}

It is mainly used in multi-organizational environments. Direct the responsibility to the corresponding business entity. Set the default business entity at the location layer. If more than one business entity is defined, this configuration file must be defined for each responsibility at the responsibility layer.

Main organization table

HR_LOACTIONS

Stores information about the organization location. Address, org_id, ship_to/bill_to site, and receiving location. In this table, LOCATION_ID is the primary key. This table is used by the interfaces or reports of the following modules: human resources, inventory, and procurement. For more information, see Oracle inventory technology or Human Resources Technical Reference Manual.

HR_ORGANIZATION_INFORMATION

All organization information defined in the storage system. It also stores information about most Organization types. This table is filled by the defined organization form (PERWSDOR. Each defined organization has one row of the organization, and one row of the Organization category defined on the form. ORG_INFORMATION_ID is the primary key of the table.