Multi Org Support

Multiple Organizations enabled products do not support viewing secured data across operating units. However, you can create custom reports or windows to view secured data across operating units by using the full–table views.

Inherent Limitations of Oracle Multi Org Design in Release 11i, Product Limitations of Oracle Rel 11i Multi Org Functionality.

• Multiple Organizations enabled products do not support viewing secured data across operating units. However, you can create custom reports or windows to view secured data across operating units by using the full–table views.
• Multiple Organizations enabled products process transactions within an operating unit. There is no additional support for centralization/decentralization of business functions. For example, the following combinations are not supported: centralized payables with decentralized purchasing, centralized purchasing with decentralized payables, centralized receivables with decentralized orders, and centralized disbursement with decentralized vouchering.
• Inter-company payable and Receivable Support is limited to Order Management / AR – Sell products through one legal entity and ship them from another and Oracle Projects supports cross–charge transactions, which result when a resource from one organization charges to a project owned by another organization.
• Standard product features show supplier and customer transactions for a given operating unit. The Supplier Customer Netting report, for example, calculates the net balance of receivable and payable transactions for the current operating unit.
• You can receive against purchase orders only in the operating unit to which your responsibility is connected. As before, a purchase order’s ship–to organization must be in the purchase order’s set of books.
• For internal sales orders, you can ship from an inventory organization belonging to another operating unit, set of books, or chart of accounts. However, inter company payable and receivable invoices are not automatically generated for internal requisitions.
• In–transit shipments across organizations in different sets of books are not supported.
• Only operating units with the same Accounting Flex-field and SOB structure can share a AR sales Tax Location Flex field structure.
• Document sequencing is available at the set of books level. Legal entities for the same set of books must share document sequences. If each legal entity requires its own numbering sequence, you must set up a separate set of books for each legal entity.
• All of the operating units that share a set of books also share the same period statuses. When you update the period status to Open in one operating unit, that period is opened for all operating units within the set of books. When you attempt to update the period status to Closed in one operating unit, the system checks for un-posted transactions in all operating units within the set  of books. If there are un-posted transactions in any of the operating units, the system asks you to resolve the un-posted transactions for those operating units before it allows you to close the period for the set of books.
• When the Multiple Organizations enabled products post to Oracle General Ledger, you need to run the posting process from each operating unit. You cannot run the posting process for all operating units in the set of books in a single process.
• Indian Service Tax Regimes can be defined at the Operating Unit Level and one Service tax per OU as per India Localization IN60106D2 onwards.