Enterprise Service Automation (ESA) - PSFT (MOSC)

MOSC Banner

Tax Parameters in Customer Contracts

in Enterprise Service Automation (ESA) - PSFT (MOSC) 3 comments

Is there a logical reason PeopleSoft is designed to use 2 different tables for the tax parameters based on the type contract line? For fixed fee billing plans, it uses the tax parameters on the billing plan. For rate based (as-incurred) it uses the tax parameters on the CA_DETAIL table. This is causing a lot of confusion with the SHIP TO address that is being used so just wondering why it is designed this way. Thank you.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT ESA Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center