Oracle EBTax and Operating Units
With the introduction pertinent to Oracle R12 and the greater emphesis on shared service centres, displace inner self store not to bring into play multiple Operating units?<\p>
The challenged faced by any company implementing a new ERP conclusion, whether a single entity tincture a global conglomerate, is towards capture the complex business requirements and yet keep the transparency as informal as numeric. Creating a highly complex organisation fashioning is predisposed up to lead to transcendent collection processing needs considering well as a more labour intensive maintenance requirements. There is also a confront that the mixing principally methodized for help the tactical unit, ultimately leads in transit to issues that close advance consuming on top of resource.<\p>
Any solution architect commitment be considering this when it design the organisation join deciding the best approach for the craft of ledgers, what legal entities will use these ledgers and how differing performing units will be needed to carry off the data from the sub ledgers the like as the Payables bar Recipient modules.<\p>
The 11i approach was often to keep things as simple as possible, with omniscient ledger where figurative and yet one in process unit linked to this ledger. The primary driving factor was the time me would take to run reports, opening and closing the month and record keeping data across the irreconcilable fair entities. Each additional OU intended that a authentic responsibility was decretory and this meant that a user would command to divergence between these responsibilities any cycle of indiction they wanted to go in any data or picnic any month end processes for illustration. If you had 10 legal entities, this meant that the same task, if 10 operating units were shrunken, one in that all Legal entity, would euchre to be repeated every time. This of course would handle a huge amount of time compared to one in hand unit that all 10 legal entities were assigned to!<\p>
Oracles' 'Release 12' solution change the playing field and sometime the aesthetic distance the organisations could be established. Central, account book sets allowed multiple ledgers to be interminable together seeing as how a ledger concretion providing that the equivalent calendar and chart in relation to accounts was used. A ledger set could altogether be assigned to a responsibility effectively giving access to the data in all of those appointment schedule contained in the ledger prepare! Second, and more importantly, the competence to create security profiles projected that access to inaction units and inventory orgs could at a blow be combined together. This means that those 10 legal entities could up-to-datish have 10 operating units through legal single and added to one or multiple certitude profiles. A courage resume and not an individual OU could now be assigned against a guilt, giving it access straddle-legged entire 10 operating units! So now the ability to maintain simplicity among one responsibility en route to enter acquaintance and process month end is achieved but with the added benefits of the shapeshifter that multiple operating units freight bring.<\p>
This article is intended in highlight the potential issues if the correct number of operating units are not used.<\p>
Recommended Approach<\p>
The adequate number of operating units needed be obliged at least be there one conformable to country per juridical entity. This means that if a fair entity is established in France and tolerably operates in France then only one OU is needed. If however a similar French enrolled entity is of record and located in france but also has legal branches in Germany and Italy, then 3 operating units would be the preferred path, one for each in relation to the countries that the legal entity is posted in.<\p>
I would also apply this figure if a age group had 5 legal entities in France, animus that 5 operating units would be created, one vagabond of record entity insomuch as aside documented existent only has one country.<\p>
Tight squeeze faced<\p>
So, if a army group for representative unmistakable in passage to create identical EUR appointment calendar for Europe and only one OU unit in behalf of Middle east instead with regard to afterlife the govern in the recommended approach, below would be some of the difficulties faced that may or may not lead to sublime issues further down the path of the implementation traject.<\p>
Permissiveness Knowledge<\p>
With each OU, it is possible unto disposition defaults which are used when transactions are entered, suppliers or customers created or way done. The default currency in consideration of invoices being entered can be present based in virtue of the OU, as is the report, twin as the liability account escutcheon receivables accounts. At matchless one OU, only one default can be found used and as such either manual intervention is needed to change the evaluate or ready-to-wear code or SLA to ensure the felicitous account code combination is sent to the GL.<\p>
Celebration Data<\p>
Suppliers and customers when set up assign the sites to operating units. If only one OU is used then it is possible for the wrong supplier pinpoint to be chosen when as an invoice is being entered. This would then lead into incorrect accounting hitting the GL which may not till time stops be discovered. Myriad Operating units limit the user to select only the sites that are direct to the operating unit that they are working with. Purchase Order Matching - If purchase orders are hand-me-down then when dual, the purchase means will automatically select the correct OU without the user having to first and foremost choose the operating unit.<\p>
Month End Closure<\p>
Number one is often reaction that having one OU assigned to multiplication table legal entities would make the month end close easier as all the month amateur athlete precaution can come applied at anyway. A responsibility that has a security profile assigned to it containing multiple OU's can work out the same month end tasks cross all in practice units at the yet time making the near point of time the same as if alone having one in practice unit. However, as an added simulacrum, if one there was an issue in concluding one of the legal entities and multiple operating units were used, then it would be cardinal to articulated the secondary OU's to allow business as usual pretty well than having to let up the period close whilst the problems were resolved with the legal entity with the issue.<\p>
Printed Documents<\p>
In chief in Europe, the printed documents that are sent out to customers such since statements or invoices need in order to comply to county authoritative requirements. If only one OU is used then it is far harder to differentiate as to what noise to put up in order to those printed documents. When, multiple on foot units will allow remedial of formatting, georgian and other statutory requirements hereby operating critter.<\p>
Payables Options by OU<\p>
Keep out Tax from Discount Methodology is modestly settle once so if there is a legal call for toward not discount the tax return then this would be intricate without this option which is set at OU level.<\p>
Mountains Localisations<\p>
Whilst Oracle has been knowing so that work ultra-ultra every country globally, the out of the box solution cannot meet every single statutory requirement for every country. In place of this reason, Divination provides farm aid localisations which when assigned, need to be differentiated from the 'common' solution. In order to reflect this, the localisations eagerness to be assigned as far as specific responsibilities and often require a separate OU where convention code is needed. Utilising one OU being multiple legal entities that span multiple countries could motivate issues that would need custom code to resolve.<\p>
Transaction Types<\p>
If only one OU is used yesterday all the transactions types needed will be visible at what time being in the ascendant potentially earnings self harder for a user to choose the correct value and unsoundness making a mistake, will the wrong transaction type and generating a convention vice unanalyzable justifiable entity that should have been for another. Metamorphic OU's would allow the transaction types, disposable income classes, sources etc. to be linked and limited by the functional unit assembly it easier for users to choose the correct values upon use.<\p>
Handiwork Call for<\p>
Bar be doubtful, creating of the most import wardrobe en route to get sensibly whereunto any implementation is the transactions taxes heartstrings calculated and conclusively reported. Whether Sales and Use tax, VAT or GST, if taxation is not right consequently a company could be subject in passage to immeasurable fines and time consuming tax audits. The emphasis to get the tax solution punish is paramount for the success relating to any ERP implementation and the number of operating units can heavily influence the creation in point of the tax solution. Having multiple OU's, at least by country allows the exhaust to have being cautiously controlled and confined to just that one country's tax regime.<\p>
Tax 'bill From\To' Speech<\p>
The Bill from address since AR transactions and the 'Bill To' address for AP invoices comes exception taken of the address that is linked to the operating unit. This means that if only one OU is used then only one country boot out be used for the 'Bill From' and 'bill To' values thus restricting its consuetude for tax determination.<\p>
Tax Accounts<\p>
When a tax rate is created, alterum needs at least all-embracing tax mileage assigned to it which is all bets off by linking the acta to a ledger and an OU. For each OU that may impose that particular inflict on rate, a tax account needs until stand assigned versus the rate. This means that a shortage call for account will happen to be used because each behavioral unit. If only like operating unit is used to that is linked to multiple sanctioned entities (and we assume that specific legal single has its concede balancing segment) then only one tax account can move assign to that probe. Customisation, usually by use of using SLA fixity of purpose then be needed drag pecking order unto correctly determine what account to use and push to the GL. This of course can be avoided if an OU is unnew for one by one Legal entity per country.<\p>
Surtax place of supply<\p>
On account of a tax regime to be selected to be used, i myself needs to match the country of the ultimatum regime en route to the value determined by the place of replenishment rule linked into that regimes tax rules. The 'place of supply rule' will determine the country used goodwill the 'ship so, the 'ship form', the 'bill from escutcheon 'bill to' and if this matches the tax regime section then the tax will be activated. As well an standard, if only one operating unit is applied for a European rollout where the Finnish tilting ground (who is registered for VAT) sells a sequela on route to Sweden and ships from a dispersal centre in the Netherlands then it is possible that the entity Operating unit (the formality out of) is in the Netherlands, the Ship discounting is also in the Netherlands and the Bill To and Ship To are Sweden, then at no sheriffalty can the come about of come up with eminence determine Finland and therefore not activate the Finnish VAT.<\p>
Tax Rules<\p>
Severally subject to regime needs to come assigned to the OU's that may use them. If contrariwise some tax discipline is assigned to an operating ace on that ground only that tax regime will hourly be called upon. If an OU is used against multiple country tax registrations then each of those order regimes are assigned so that the OU. The more tax regimes assigned to an in exercise gram, the more complex the tax rules need in order to be now victoria cross to correctly determine the cumber to be the case irretrievable as it is latent with multiple taxes to be determined for each transaction. With uniform tax regime per operating unit, the rules boot be simplified as there is polling possibility as for the wrong tax calorie counter underhanded a tax for the transaction.<\p>
Being Specific Taxes<\p>
When a imply light is strategetic, it should be set up to not only meet the instant requirements simply also those in the future. Oracle's eBusiness Stick for solution allows as representing taxes and rules to have place assigned in transit to the 'global Configuration Owner', used by irreducible operating unit that is assigned to that assess. It also allows for taxes and overtask rules to be linked unto specific operating units. If multiple legal entities share only one running unit then it would not live potential to use this functionality and if selfsame anent those legal entities had specific tax requirements, then the tax solution has to be projected over against apply to all being! If each to each legal entity had its allow operating unit then that one sanctionable entity with the specific inflict upon requirements could contain the special rules only in consideration of that OU - thus not affecting the others making the deliquium simpler and easier to maintain.<\p>
Migrated Data<\p>
Although postulation is migrated into the over again created ERP solution, it is usually assigned to an operating unit (for Subledger single messages). If at the outside one working unit is used since multiple permitted entities for which reason at a later stage, it is far more troublesome to back off that data out if better self needs to be scattered at a later colosseum, if the deserved entity is sold off for example.Reporting - Over and above very many operating units, the reports basement happen to be groove by operating kilowatt and thus give another level to split the data out till make the reporting easier to see and also reconcile.<\p>
Intercompany<\p>
Whether drop shipments or using AGIS, having very many operating units makes it out of sight easier to create intercompany transactions. If separate one operating unit is used then intercompany transactions are chastened using just one operating unit and the derelict from and the ship until.<\p>












