Starting lot number prefix is required when Lot Control = Full lot control

While releasing a part from Agile getting below error.

Error: Starting lot number prefix is required when Lot Control = Full lot control

Cause You have to specify Lot Prefix in the  template when you have Lot Control=Full Lot Control.

Resolution Please correct the Item Templates in Oracle EBS and resubmit the ECO from AIA queue.

What is the difference between MTL_SYSTEM_ITEMS,MTL_SYSTEM_ITEMS_B tables?

What is the difference between MTL_SYSTEM_ITEMS,MTL_SYSTEM_ITEMS_B tables?

mtl_system_items is a synonym that points to mtl_system_items_b

mtl_system_items used to be the actual items table in older versions.
But in recent version the mtl_system_items_b is the items table. If any old code was using mtl_system_items, the synonym helps it compile and thus make this change backward compatible.

Oracle follows the following convention to handle multi-language.
The b stands for base table. And then there is a table called tl (e.g. mtlsystem_items_tl). In the _tl table, for each base record, you can find multiple records - one for each language that you use.

MTL_SYSTEMS_B is the base table and MTL_SYSTEM_ITEMS is a synonym for MTL_SYSTEM_ITEMS_B.Because of this synonym, old code written that used mtl_system_items still compiles without any problem. That is the sole purpose of the synonym.

What is MTL_SYSTEM_ITEMS_B table?

MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. You can specify item-related information in fields such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning, MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.

You can set up the item with multiple segments, since it is implemented as a flexfield. Use the standard 'System Items' flexfield that is shipped with the product to configure your item flexfield.

The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore, the same item can be defined in more than one organization.

Each item is initially defined in an item master organization. The user then assigns the item to other organizations that need to recognize this item. A row is inserted for each new organization the item is assigned to. Many columns such as MTL_TRANSACTIONS_ENABLED_FLAG and BOM_ENABLED_FLAG correspond to item attributes defined in the MTL_ITEM_ATTRIBUTES table.

Two unit of measure columns are stored in MTL_SYSTEM_ITEMS_B table. PRIMARY_UOM_CODE is the 3-character unit that is used throughout Oracle Manufacturing. PRIMARY_UNIT_OF_MEASURE is the 25-character Unit of Measure that is used throughout Oracle Purchasing. Unlike the PRIMARY_UOM_CODE, the Unit of Measure is language-dependent attribute, however, PRIMARY_UNIT_OF_MEASURE column stores value in the installation base language only.

API to purge concurrent program

--API to purge concurrent program
Begin
fnd_program.delete_program('XXCUST_AR_RPT','Receivables');
commit;
End;

--API to purge data definition

BEGIN
XDO_DS_DEFINITIONS_PKG.DELETE_ROW('AR','XXCUST_AR_RPT');
END;

--API to purge XML template
BEGIN
XDO_TEMPLATES_PKG.DELETE_ROW('AR','XXCUST_AR_RPT');
END;

Overview on Multi-Org Structure

Overview on Multi-Org Structure


What is Multi-Org

Multi-Org is an enhancement to Oracle applications that enables you to model multiple business units in an enterprise using a single installation of Oracle applications. In a multi-org architecture you can keep data secure and separate from each business unit.

The following are the benefits of multi-org:

            •          You can use a single installation of any Oracle Applications product to support any
          number of business units, even if those business units use different set of books.

            •          Secure access to data so that users can access only information that is relevant to them.

            •          You can define an organizational model that best suits your business requirements.

Organization Model



The multi-org model provides a hierarchy that dictates how transactions flow through different business units and how those business units interact. You define the organizations and the relationships between them.

Business Group
 This is an Organization that represents the consolidated enterprise, a major division, or an operation company and has no accounting impact. The Business Group partitions Human Resources information and the Purchasing Approval Hierarchy. If you request a list of employees (in any module) you will see only those employees in the Business Group of which your Operating Unit is a part. Multiple Legal Entities can relate to a single Business Group.
You must have at least one Business Group. For a new installation, Oracle Applications provides a default business group called Setup Business Group. You can define additional business groups as required for your enterprise.

Set of Books
 A set of books (SOB) is a financial reporting entity that shares the three Cs: a particular chart of accounts (accounting flexfield structure), functional currency, and financial accounting calendar. You create sets of books using the Set of Books window in Oracle General Ledger. You define all other types of organizations using the Organizations window.

Legal Entity
 A legal entity represents a legal company for which you prepare fiscal or tax reports. You assign tax identifiers and other legal entity information to these types of organizations.

Operating Unit
 An operating unit represents an organization that uses any Oracle sub ledger application, for example, Order Management, Payables. It may be a sales office, a division, or a department. An operating unit is associated with a legal entity. Information is secured by operating unit for these applications. Each user sees information only for their operating unit. Responsibilities are linked to a specific operating unit by the MO: Operating Unit profile option.

Multi-Org Access Control (MOAC)
     Multi-Org Access Control, or MOAC, enables users to access multiple operating units from a single application responsibility.

    Operating unit security will be preserved such that companies can effectively implement security and shared services at the same time.

   Enhanced Multi-Org Reporting provides the ability to process and report critical financial information at different levels of the enterprise.
      
Prior to Release 12, each responsibility could access only one operating unit.  Therefore, users who had to manage multiple operating units had to log in and log out of multiple responsibilities to perform their tasks. In Release 12, users can perform tasks for multiple operating units without changing responsibilities and its achieved by setting up MO: Security profile.

Usage Example:


In 11i, If a company had three operating units Belgium, Holland, and Denmark, the company would have to create three responsibilities, one for each operating unit.  And users, who had to enter invoices into all 3 operating units, had to log into each one of the EMEA responsibilities separately.

With Multi-Org Access Control in R12, each application responsibility can access multiple operating units. The company can create a single EMEA responsibility for all three operating units and users would only have to log in once to perform tasks such as: entering payables invoices, viewing consolidated requisitions, performing collections, and processing receiving and drop shipments.

It is required to set up either the MO: Operating Unit or MO: Security Profile profile option for each application responsibility to use Multiple Organizations context sensitive applications. If the MO: Security Profile is set, then the MO: Operating Unit profile is ignored.

Data security is maintained using security profiles that are defined for a list of operating units and determine the data access privileges for a user When drilling down on balances from Oracle General Ledger, General Ledger ignores the operating unit profile setting to allow you to drill down to your subledger details, regardless of which operating unit originated the transaction.

The OU field visible for all relevant transactions and relevant setups.  On data entry, the system will derive the OU, when possible.  E.g. if user enters a PO default invoice, the supplier site determines OU.

·         Create Security Profile
·         Run Security List Maintenance program
·         Setup profile option MO: Security Profile
·         Setup profile option MO: Default Operating Unit


Note: If a responsibility has to access only one operating unit, then set the profile option - MO: Operating Unit. If a responsibility has to access multiple operating units, then define a security profile with multiple operating units assigned and assign it to the MO: Security Profile profile option