It is not mandatory; ITC has helped some customers implement the localization solution without installing Oracle MLS. However, we need to implement UTF8, or Unicode Transformation Format. IT Convergence provides MLS and non-MLS solutions to our customers, though from our experience, we’ve found the vast majority choose to go with a MLS solution.
Regarding Golden Tax, what are the considerations to take into account when upgrading from 11i to R12?
The major consideration is whether to use Oracle Standard Golden Tax adaptor to meet the local requirements or use a customized solution, a decision that will be based on the evaluation of the business requirements and Oracle standard functions.
In 11i, you need to develop a custom interface (i.e. ITC custom solution) to integrate the Golden Tax system with E-Business Suite.
In R12, this interface is available as a standard function, known as the Golden Tax Adaptor. This adaptor also provides additional functions for data reconciliation and data transfer between Oracle and the Golden Tax system. However, in our experience, some clients still chose to implement the custom Golden Tax interface in R12 due to the limitations and reduced flexibility of the standard function.
Does Oracle R12 have any patches that can be applied for the China Localization? How can we use R12 to consolidate a heavily customized 11i system?
The China localization components are standard features in R12, however, there are some additional patches that may need to be applied depending on the localization requirements; this will depend on the city or province where your operations are located.
Typically, for an upgrade we need to evaluate each customization in 11i and decide whether the customized feature could be replaced by any new features in R12 or we still need to modify the customization for the upgrade.
We use Vertex. Does Golden Tax require excluding vertex?
Oracle golden tax adaptor is for VAT invoice printing purpose, it is not for the same purpose as Vertex.
Do most US-based businesses maintain data elements in English and only provide Chinese translations for key elements (customer name, item description, etc.)?
Yes. We need to maintain Chinese translations for the data which will be included in the mandatory local documents and third-party facing documents. For example, the vendor name on the PO, or customer names that need to be interfaced to Golden Tax, etc. The reasons behind keeping Chinese translations for key data elements are: simplifying the third-party facing XML document, external system integration and preventing issues arising from local staff English proficiency.
Does China have any specific intercompany reporting needs?
No, the intercompany invoicing does not have any specific requirements, other than the requirements that the PRC government sets for all general invoicing and the local requirements set by the regional tax bureaus. Those regional requirements will be different according to the region.
In addition, the local statutory reports are based on each individual legal entity, the intercompany transactions need to be booked for each entity for local reporting purposes and will need to be eliminated at consolidated level.
If you missed this webcast and would like more information on meeting the challenges of implementing Oracle E-Business Suite in China, visit our China Services page, or register to download one of our white papers
Faster Integration, Better Visibility, Stronger Sales
Register for our webcast on Friday 19th and learn why Oracle Cloud Adapter is the answer to your ERP-SalesForce.com Integration prayers. Reserve your spot today for “Connect Salesforce.com to Oracle ERP via Oracle Cloud Adapter”