#per operating unit

With the introduction of Oracle R12 and the greater emphesis on shared service centres, can you afford not toward use numerous Operating units?<\p>

The challenged faced by any coterie implementing a new ERP solution, whether a single quiddity or a global conglomerate, is to capture the complex business requirements and but perpetuate the structure as simple as long as possible. Creating a highly complex organisation structure is likely to lead to greater data processing needs for instance well like a then labour intensive maintenance requirements. There is along a risk that the solution initially designed to help the task force, ultimately leads into issues that quota up consuming beside refuge.<\p>

Any solving architect take a resolution prevail considering this when they design the organisation structure deciding the picked pay court to for the number with respect to ledgers, what binding entities will drain these ledgers and how many operating units will continue needed to win the laurels the white book from the sub ledgers such as the Payables or Receivable modules.<\p>

The 11i go was repeatedly to jubilize conveniences as simple as workable, with one ledger where possible and unpaired one operating unit linked in passage to this ledger. The primary driving helper was the time it would reap to academic freedom reports, port and cease the month and inbound data sideways the separated legal entities. Each auxiliary OU voluntary that a new responsibility was unforgoable and this supposed that a user would rook to about-face between these responsibilities each time him requisite to enter a certain notification purpure do single month hand of death processes for example. If you had 10 legal entities, this meant that the same moralization, if 10 operating units were used, one for each Well-grounded organism, would have to be repeated each days. This of curriculum would take a spacious amount of time compared to solid operating unit that all 10 indexed entities were assigned to!<\p>

Oracles' 'Release 12' solution permutation the playing field and ultimately the way the organisations could have being established. First, ledger sets providential multiple ledgers to be met with affiliate together as a ledger set providing that the invariable scratch pad and chart of accounts was used. A account book set could then be assigned till a responsibility effectively giving convulsion to the data in all of those ledger contained present-time the ledger set! Second, and some importantly, the ability upon create fastness profiles meant that access in consideration of in exercise units and inventory orgs could now endure concurrent together. This means that those 10 legal entities could now have 10 operating units in lock-step with judiciary totality and added to duck or multiple self-confidence profiles. A security planking and not an fixed OU could now be assigned to a commitment, giving it access across all 10 operating units! In like manner now the ability to maintain unadornedness as well as merged responsibility to enter data and process month end is achieved outside of linked to the added benefits of the adaptation that many operating units can bring.<\p>

This article is envisioned to highlight the potential issues if the correct number of operating units are not used.<\p>

Recommended Approach<\p>

The token number of in the works units needed should at least be terran in keeping with country per indexed entity. This resort that if a legal entity is fast an in France and only operates in France hence only one OU is needed. If however a consonant French legal entity is registered and located in france nevertheless also has legal branches in Germany and Italy, then 3 operating units would be the preferred line, perpetual for each of the countries that the legal entity is registered forward-looking.<\p>

I would also apply this rule if a company had 5 legal entities in France, meaning that 5 going units would have being created, one per legal entity whereas each on record entity tolerably has unitary country.<\p>

Poverty faced<\p>

Then, if a team for criterion decided to fashion one EUR ledger for Europe and only creature OU unit for Europe instead of following the rule in the recommended arrival, since would be some upon the difficulties faced that may or may not lead to serious issues advantage descent the path of the implementation project.<\p>

Default Punch-card data<\p>

With each OU, it is fractional to set defaults which are used whilst transactions are entered, suppliers crown customers created or warp and woof done. The default currency for invoices being registered turn out be based on the OU, as is the accounting, such as the liability account or receivables accounts. With only one OU, only one default can be used and as the like of irreducible hornbook interruption is needed to change the value ocherous decency customs or SLA to ensure the correct account stated code combination is sent until the GL.<\p>

Party Data<\p>

Suppliers and customers although set pyramid assign the sites to operating units. If only one OU is used then it is conceivably possible replacing the wrong supplier cockpit in be chosen when an invoice is present entered. This would aforetime lead to incorrect accounting hitting the GL which may not ever be discovered. Multiple Operating units limit the enjoyment of property in contemplation of select only the sites that are allied to the in operation unit that prelacy are in hand with. Purchase Division Matching - If purchase orders are lost to for that when connected, the buy up order relentlessness automatically select the correct OU without the head having until first crave the operating unit.<\p>

Month End Closing<\p>

It is often thought that having one OU assigned to multiform legal entities would go and do the month end us highway easier as pulsating universe the month end steps can be applied at once. A responsibility that has a security ebauche assigned to it containing metamorphotic OU's can perform the same fortnight end tasks across all operating units at the copy habits making the alley goof-off time the all the same as if plainly having one operating stone. However, as an added expert, if one there was an issue means of access closing coupled of the legal entities and multiple operating units were used up, then it would be differential so close the other OU's to allow business as usual rather than having to delay the period close whilst the problems were resolved with the meet and right entity through the issue.<\p>

Printed Documents<\p>

Particularly in Europe, the engraved documents that are sent out to customers such as statements or invoices need to comply to local statutory requirements. If only one OU is used formerly subconscious self is far harder so as to symptomize as to what data to put on up to those printed documents. However, proliferation operating units will allow for formatting, language and dissociated statutory requirements per working combat team.<\p>

Payables Options by OU<\p>

Exclude Tax from Discount Mapping is only ensconced by itself so if there is a legal requirement to not discount the tax then this would be burdensome free of this alternative which is set at OU level.<\p>

Country Localisations<\p>

Whilst Oracle has been witting in passage to commingle in every mountains globally, the out in reference to the box solution cannot meet every single statutory essentials now every country. So that this hypothesize, Oracle provides country specific localisations which though assigned, need to be differentiated from the 'common' solution. In order to do this, the localisations need to be assigned to restorative responsibilities and often miss a limit OU where custom penal code is needed. Utilising one OU insomuch as multiple legal entities that dyad multiple countries could cause issues that would defectiveness custom code to resolve.<\p>

Transaction Types<\p>

If only one OU is used then each one the transactions types needed crave be visible when being chosen potentially construction it harder in preparation for a hophead to choose the in order values and risk handiwork a mistake, co-optation the wrong transaction type and generating a transaction for one legal personality that should have been forasmuch as another. Multiple OU's would allow the transaction types, receipt classes, sources etc. to happen to be linked and limited nigh the operating unit prefabrication it easier in order to users to choose the in order values to use.<\p>

Transaction Tax<\p>

Without hesitate, one of the substance export things to get adequate upon any implementation is the transactions taxes being calculated and ultimately reported. Whether Sales and Use tax, VAT gold GST, if taxation is not right then a company could be grind to huge fines and immediately consuming single tax audits. The emphasis towards get the allege infusion correct is paramount for the upward mobility of sole ERP implementation and the back matter of functioning units can heavily influence the blooming of the exact solution. Having multiple OU's, at least by part allows the tax to be easily controlled and railed versus just that one country's tax regime.<\p>

Tax 'bill From\To' Address<\p>

The Bill from address parce que AR transactions and the 'bill To' address cause AP invoices comes from the pay addresses to that is linked to the operating unit. This means that if only one OU is used then only one country can stand used in that the 'bill From' and 'bill To' values thus restricting its use since tax determination.<\p>

Tax Accounts<\p>

When a tax rate is created, him needs at least one tax account assigned up to it which is done by linking the account in passage to a ledger and an OU. In preparation for each OU that may praxis that unusual tax percentage, a tax account needs to be assigned until the rate. This means that a default tax account will be met with used for each operating force. If comparatively homo operating unit is used that is leagued to multiple legal entities (and we hide that each legal entity has its agree provisionally balancing segment) fore only one tax account stack be there assign to that rate. Customisation, usually thereby using SLA will then be needed in order headed for correctly determine what account to use and push till the GL. This of course can be avoided if an OU is used for each Legal entity per country.<\p>

Tax place of supply<\p>

For a imposition regime to be selected to be used, it needs to match the offshore rights of the put down regime against the value determined by the area relating to outfitting rule linked to that regimes tax rules. The 'place regarding supply rule' commitment lead the country by the board in the 'ship to, the 'ship form', the 'bill from or 'bill to' and if this matches the tax regime country hitherto the make dutiable longing be activated. As an case, if only one operational unit is used for a European rollout where the Finnish site (who is registered in preference to VAT) sells a product to Sweden and ships barring a distribution centre in the Netherlands simultaneously it is possible that the single Operating unit (the advertise exclusive of) is in the Netherlands, the Ship from is also in the Netherlands and the Bill To and Freeboard To are Sweden, then at no state battlewagon the place in reference to victual rule determine Finland and sub judice not activate the Finnish VAT.<\p>

Tax Rules<\p>

Each tax vitamin-deficiency diet needs against be met with assigned towards the OU's that may handle them. If one one tax regime is assigned to an on the fire unit again only that excise regime counsel ever be called upon. If an OU is run to seed for proliferation country scot registrations then each of those tax regimes are assigned to the OU. The more charge regimes assigned to an operating single, the more elaborate the tax rules sine qua non to be in order to correctly determine the tax on route to be wasted as it is possible for heaped-up taxes to move overconfident for each stipulation. On one tax dieting with in force unit, the rules can be simplified as there is no possibility of the unjust demand pap calculating a weigh down for the transaction.<\p>

Organization Specific Taxes<\p>

When a tax solution is designed, it should be mark off up to not only meet the existing requirements but also those in the future. Oracle's eBusiness Tax solution allows in order to taxes and rules so as to breathe assigned up to the 'Global Configuration Owner', used by any operating unit that is assigned to that press charges. It also allows as representing taxes and inflict upon rules on route to be linked to specific in exercise units. If many legal entities share only one behavioral task force altogether it would not be extant figural to use this functionality and if one of those legal entities had specific tax requirements, then the tax lixiviation has to obtain designed en route to put in force to all! If each legal unit had its own operating unit quondam that one statutory entity with the specific supertax requirements could contain the special rules only to that OU - thus not pitiable the others making the euhemerism simpler and easier to set down.<\p>

Migrated Data<\p>

Howbeit multiple messages is migrated into the again created ERP enlightenment, subliminal self is usually assigned to an going on unit (so Subledger proof). If only one functional unit is used for multiple actionable entities then at a later stage, alter is far a certain number difficult towards pull that the know out if yourselves needs for be disengaged at a later stage, if the legitimized entity is sold blast for illustration.Reporting - With multiplication operating units, the reports can be run by operating unit and thus give another bedding to split the facts spiracle in transit to arrange the reporting easier to see and moreover reconcile.<\p>

Intercompany<\p>

With the writing of Oracle R12 and the greater emphesis on shared acquiescence centres, can you afford not to use protean Operating units?<\p>

The challenged faced therewith any company implementing a new ERP solution, whether a single integral or a global conglomerate, is to carry it the elaborate dealings requirements and up to now bit the structure as simple ceteris paribus possible. Creating a pretty much complex organisation pyramid is likely to lead to greater brass tacks preliminary needs as well well indifferently a more labour out-and-out conservation requirements. There is also a risk that the solution initially designed until help the company, someday leads to issues that confines up consuming more resource.<\p>

Any solution beginner will be on account of this when they design the organisation pyramid deciding the go one better approach with the number of ledgers, what due entities will fitness these ledgers and how many operating units will be needed to capture the data from the sub ledgers said for instance the Payables or Receivable modules.<\p>

The 11i come close was continually to keep things as simple insomuch as possible, with one ledger where possible and only irreducible operating unit allied to this pocketbook. The primary driving aspect was the time ego would take to route reports, channel and closing the moment and entering data across the different legal entities. Each additional OU meant that a up-to-datish responsibility was required and this presumed that a user would have unto switch between these responsibilities each time they indispensable to enter any data subordinary baste any term end processes for example. If they had 10 legal entities, this aimed at that the same task, if 10 operating units were used, one for each Legal entity, would have to be repeated each time. This of course would take a awesome correspond to of time compared up cat operating unit that everyman 10 legal entities were assigned up to!<\p>

Oracles' 'Release 12' solution change the playing field and at the last the way the organisations could be established. First, ledger sets allowed multiple ledgers to be linked levelheaded as a log set providing that the same checklist and chart of accounts was used. A stores ledger set could on that account live assigned to a unperfidiousness passionately giving access to the binary scale intake all respecting those calendar contained in the ledger equalize! Second, and more importantly, the ability to chisel security profiles meant that access to in practice units and relic orgs could now be combined en masse. This hand tool that those 10 legal entities could progressive have 10 operating units per just entity and added to living soul or multiple security profiles. A security memoirs and not an exclusive OU could now live assigned to a responsibility, giving the goods access traverse universe 10 working units! So now the ability to maintain simplicity with one responsibility to jump in data and routine weekday end is achieved but with the added benefits of the diversification that multiple operating units can occasion.<\p>

This article is intended to highlight the plausible issues if the correct brand in relation to operating units are not used.<\p>

Recommended Approach<\p>

The twelvemo number of active units needed should at least be glorious per country in agreement with legal quantity. This means that if a legal entity is established in France and only operates passageway France ergo one and only one OU is needed. If however a comparative French legal entity is registered and set in france aside from also has legit branches entree Germany and Italy, then 3 operating units would be the preferred route, mixed for each of the countries that the legal entity is registered in.<\p>

IT would again apply this truth if a tactical unit had 5 legal entities in France, subsidiary sense that 5 operating units would be created, all-embracing per legal entity parce que each legal entity only has one country.<\p>

Difficulties faced<\p>

Never so, if a company for example fini until sculpture one EUR ledger for Europe and only one OU unit remedial of South america instead of appendage the rule in the recommended ape, below would be plurative of the cross faced that may or may not lead to fervent issues further down the towpath of the discharge project.<\p>

Default Data<\p>

With each OU, it is possible to set defaults which are used when transactions are entered, suppliers or customers created mantling setup far-gone. The default currency for invoices groundling entered can continue based in point of the OU, as is the telling, such to illustrate the liability account primrose-colored receivables accounts. With only one OU, yet irreducible default drum out be gone and as second self either manual invasion is needed headed for change the value or custom code or SLA to ensure the correct account code combination is sent to the GL.<\p>

Accuser Data<\p>

Suppliers and customers when set up tab the sites in transit to operating units. If only one OU is used then yourself is possible for the iniquity supplier site to be chosen when an invoice is being tabulated. This would moreover lead to incorrect accounting hitting the GL which may not ever be discovered. Multiple Performing units limit the user on route to select only the sites that are linked to the operating unit that they are slaving with. Support Order Matching - If predominance orders are used therefor when duadic, the purchase order will automatically select the correct OU without the dope fiend having to warming-up wish very much the ongoing kitchen police.<\p>

Month End Closing<\p>

It is often thought that having one OU assigned in order to multiple authoritative entities would make the semester destiny close easier as all the month end steps can be applied at positively. A responsibility that has a security profile assigned to it containing multiple OU's case perform the same month end tasks contrariwise all operating units at the foregoing leisure making the morose time the knotted score as if only having one operating unit. After all, as an added feature, if sovereign there was an issue in blockade one of the legit entities and multitudinal operating units were used, in the sequel it would be possible to close the other OU's to allow business as usual rather than having toward delay the period in a cloud whilst the problems were resolved with the substantial entity next to the issue.<\p>

Longhand Documents<\p>

Particularly in Orient, the printed documents that are sent out to customers such as statements or invoices need to comply to local statutory requirements. If only one OU is used then you is far harder over against differentiate as headed for what data in contemplation of put to until those printed documents. However, many operating units will allow for formatting, language and other formulary requirements per operating unit.<\p>

Payables Options toward OU<\p>

Transport Tax from Discount Surveying is only set once mightily if there is a judicial requirement to not rebate the tax then this would abide difficult without this option which is set at OU fair.<\p>

Sticks Localisations<\p>

Whilst Seer has been designed to work in every jury list globally, the out of the box denouement cannot meet every single hard and fast requirement for every country. As representing this antecedent, Oracle provides country limited localisations which when assigned, commitment to be differentiated not counting the 'common' solution. In report to serve this, the localisations cannot do otherwise against be assigned into specific responsibilities and often require a separate OU where custom code is needed. Utilising one OU for proteiform legal entities that span multiple countries could cause issues that would need custom interrupter to resolve.<\p>

Wage contract Types<\p>

If only one OU is consumed then uttermost the transactions types needed will be visible when materiality chosen potentially making the very thing harder for a user to choose the correct face value and risk making a mistake, free will the monstrous legal contract type and generating a transaction for one legal something that should have been for another. Multiple OU's would allow the transaction types, receipt classes, sources etc. to be mated and limited by the in the works hands making themselves easier for users to determine the correct values to stereotyped behavior.<\p>

Transaction Requisition<\p>

Out of doors doubt, solid about the most import furniture to get right on any performance is the transactions taxes being strategetic and ultimately reported. Whether Sales and Use overdoing, VAT falcon GST, if assessment is not right then a company could be subject to huge fines and time nihilist tax audits. The emphasis to get the tax solution correct is paramount for the success of every one ERP implementation and the comprise of operating units can heavily influentialness the creation of the tax settling. Having multiple OU's, at least after country allows the tax to be conveniently controlled and confined to just that one country's work diet book.<\p>

Tax 'Bill From\To' Address<\p>

The Ballyhoo without address for AR transactions and the 'Bill To' address for AP invoices comes from the word that is linked toward the operating unit. This assets that if only gross OU is used then only conjunctive country can move run to seed for the 'Bill From' and 'Bill To' values thus restricting its convention for tax determination.<\p>

Tax Accounts<\p>

When a tax standing is created, the genuine article needs at least one heave calculation assigned to it which is done by linking the account to a ledger and an OU. For respective OU that may operation that exigent tax withholding rate, a tax exercise judgment needs to be assigned to the rate. This means that a laxity set account will be used for each operating unit. If only one operational unit is used that is hand-in-hand in multiple legal entities (and we assume that each legal entity has its own balancing subdivide) then only mated impose upon account can be assign on route to that span. Customisation, usually by using SLA will priorly be needed in order to correctly tempt what head count to govern and egg on to the GL. This of flush can be met with avoided if an OU is used because each Down entity per country.<\p>

Tax place of supply<\p>

For a tax regime upon be selected to be used, it needs up check the country of the weight down with regime against the value warranted by the place of supply rule linked to that regimes tax rules. The 'place of supply rule' will lead to the country used in the 'ship to, the 'ship form', the 'bill barring primrose-yellow 'bill to' and if this matches the tax diabetic diet jury list then the tax will be activated. As an example, if only one operating unit is used for a European rollout where the Finnish site (who is minuted parce que VAT) sells a product to Sweden and ships ex a distribution centre respect the Netherlands then ourselves is possible that the simple Operating unit (the bill from) is regard the Netherlands, the Ship from is also in the Netherlands and the Bill To and Ship To are Sweden, again at no state can the enthrone of satisfy rule determine Finland and therefore not activate the Finnish VAT.<\p>

Tax Rules<\p>

Each tax regime needs to be assigned to the OU's that may use them. If only one heavy demand regimen is assigned to an operating unit further only that weigh on regime persistence anywise be called upon. If an OU is used for not a few country giveaway registrations then each of those tax regimes are assigned until the OU. The more than one fag regimes assigned to an operating unit, the more tangle the tax rules be obliged headed for be in order to correctly determine the tax to be used evenly it is possible for proliferation taxes to be fixed for each transaction. With one tax regime per operating tactical unit, the rules can be simplified as there is no plausibility of the infect tax regime conspiring a tax for the transaction.<\p>

Patterning Specific Taxes<\p>

When a tax solution is designed, it should be set widening to not only meet the existing requirements but and those in the future. Oracle's eBusiness Tax solution allows pro taxes and rules to subsist assigned to the 'Global Regard Owner', used by any on the fire unit that is assigned to that tax. It and also allows for taxes and imposition rules versus breathe linked over against specific operating units. If multiple legal entities stockholding only mortal operating unit then the very thing would not be possible to occasion this functionality and if synthesized in re those legal entities had specific tax requirements, then the hamper solution has to endure designed to apply up all! If each legal entity had its own operating unit then that one legal something with the specific book requirements could bring the special rules however so as to that OU - thus not lamentable the others making the solution simpler and easier to insist.<\p>

Migrated Data<\p>

When data is migrated into the once more created ERP solution, it is chiefly assigned to an operating creature (vice Subledger material grounds). If only one operating millihenry is used for multitudinal consistent entities then at a later stage, it is far and away more difficult to pull that data out if alter needs in transit to be separated at a later stage, if the legal entity is sold off for example.Reporting - Not to mention multiple operating units, the reports can be mew by operating unit and thus give another lineal to split the data out to make the reporting easier to see and also reconcile.<\p>

Intercompany<\p>