R12: Project Task Location (Work Site) not Interfaced to AR Transaction Line Level Ship-To for Tax Purposes.
(Doc ID 2253319.1)
Last updated on NOVEMBER 15, 2022
Applies to:
Oracle Project Billing - Version 12.2.4 and laterInformation in this document applies to any platform.
Goal
In a single project, work can be performed at different sites that fall into various tax jurisdictions.
A location (work site) can be defined for each task, and Project billing invoice format grouping rules can specify work site as a grouping element (for example: Top Task, Work Site, Revenue Category, Exp Category, Exp Type), such that billed elements are grouped into separate PA draft invoice lines and interfaced into AR as separate transaction lines.
The expectation, with a grouping rule (whether labor or non-labor) that includes work site as a grouping element, is that the AR transaction lines would have the work site address as the line-level ship-to address. Thus, tax would be calculated for the specific tax jurisdiction of that line.
Current functionality defines the AR transaction line level addresses are the always the project customer ship-to address, and not the task level location (work site) address.
How can goods or services (products) be taxed using Project Billing, such that the tax calculated on such products are location-based using task level locations?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |