For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
I have a special interest on tax. Let me know how you go.
Uma
Cool David
Hi Saurabh,
Just interested to know "Why you are contemplating weather to add an LE to Ledger or not?" Any detail you can share would be great.
The reason why am asking this is , Generally you link to LE to Leddgers. Apart from Intercompany transactional requirements, this linkage will enable to run reports at LE level. so just curious to know whats going on with you.
Uma
Hi Tim,
As long as you get the bank number and branch number , I believe the descriptions can be modified later.
Where you may stuck is you required bank and branch names to be included in payment files or to be printed. Sure there will be inconvenience due to reading a text unknown from production system
Uma
Tim,
Migrating open invoices will get your balances reconciled. If they are already accounted and taxed in your legacy system, it requires an additional action of reversing both accounting and tax.
I am from Australia and we do not use 1099 here. I just googled for it. My limited understanding is "you require to report to legislative authorities on all invoices for the financial year"
Assuming my understanding here is correct, here is my thinking loud
(1) report out of 2 systems.
(a) Extract the closed invoice data from legacy system before it cuts off and keep it in excel
(b) migrate the open invoices to fusion
(c) Report from fusion to excel
(d) merge with data from (a)
(2) Migrate closed as $0 invoices
(a) Migrate closed invoice with all details with $0 amounts. Original header and line amounts are migrated with DFF attributes
(b) Develop a custom BI report to report using attribute fields for closed and actual fields for the rest
Hope that helps.
Uma
Thanks for the info. How is this different to cloud support (click on switch to cloud support)?
Uma
You got to be careful with spreadsheet date formats. They all not adhering to single date format.
And also don;t think one can add periods retrospectively.
Good idea to combine them all into one
Good stuff
Thanks Alvin for your efforts in documenting to share.
Uma
David,
What I meant is
(1) Enable doc sequences on journals.
(2) Load your data into GL Journals - GL journals do have enough DFF fields to let you add extra information
(3) Use the doc sequence number and load tax information into tax repository
(4) Use a custom report to link them
Yes, its not ideal, but given you do not have or you do not want to implement AR and Tax spreadsheets do not support DFF's, your options are limited, and there is no clean solution to it.
Uma
Receive an upgrade notification email yesterday. R11 is available now for customers.
Hi David,
Without the presence of Receivable module, I believe that is the only choice you have. Use GL Journal line DFF to populate all info and refer that line in tax repository. Its not elegant, but not sure any other choice.
Uma
David,
Given you do not have Receivable module and assuming FBDI is not supported for R10, you are left with only one choice to get the tax information loaded into repository i.e. Tax Journal (Sales journal) . This gives you only 2 description columns which you can design to use to get the customer name, something like comma separated values.
Uma
David,
I did had a quick look at R10 setups of my instances. It appears to me that there is no DFF available for Tax Repository. I believe that is the reason the excel templates do not hold Flex columns.
Secondly, if you check in the Enterprise Repository the FBDI Tax template is not available for R10.
Perhaps worth raising an SR
Uma