Friday, January 23, 2015

Definitions Used in Intercompany Accounting

 
Intercompany Accounting Basics:
Intercompany Journal
This is a journal entry which has transactions for at least 
two different companies (or balancing segment values).

Intercompany Journal Out of Balance
An out of balance intercompany journal is one which does not have equal
credit and debit totals for each group of lines by company.

Balancing Segment
This is the accounting flexfield segment that has the balancing segment 
qualifier assigned to it. Typically the balancing segment stores the company 
values. However, it could represent the cost center, the department or some
other values.
The terms balancing segment and company segment are usually interchangeable. 
It is mandatory that one segment of your accounting flexfield be designated
as the balancing segment.

Intercompany Segment
The intercompany segment is the accounting flexfield segment that has 
the intercompany segment qualifier assigned to it. This qualifier is only 
available in release 11i and is optional.  This segment shares the same
value set as the balancing segment.

Clearing Account
A clearing account is a temporary account that holds amounts to be 
transferred to another account. 

Clearing Company 
This is the company value used to clear payables or receivables transactions. 
General Ledger uses this company to balance intercompany transactions.

Trading Partner
Trading partner is the company against which the line transaction is made.

Transaction Types
Transactions types are the classifications for journal entries based on
the number of companies involved in the credit and debit side
of the transaction.

The different transaction types are:

One to One: Two different companies in the journal. One company 
has the net debit balance and the other has a net credit balance.

Many to One: Different companies have net debit balance and one 
company has net credit balance.

One to Many: One Company has net debit balance and more than one 
companies have net credit balance.

Many to Many: Two or more companies have net debit balance and 
two or more companies have net credit balance.

Sunday, January 11, 2015

How to create Employee as a customer in AR

 

Requirement:

How to create HR employee as a AR Customer, after completing this employee will be acted as a customer then have to use them in AR & OM.

Solution:

AR: Show Parties Without Accounts In DQM

Please set the Profile option at site level and query the Employee name in the customer screen with Person as a header selection.

image

Query has exceeded 200 rows. Potentially more rows exists, please restrict your query.

 

Error while querying workflow notification to view the history.

SNAGHTML124f88ca

Solution:

This is the expected behavior. The application throws the warning message 'Query has exceeded 200 rows. Potentially more rows exist, please restrict your query.' , when the process crosses the 200 row limit which is being set in profile

FND: View Object Max Fetch Size.


The profile FND: View Object Max Fetch Size can be changed to a higher value.  However, as per Oracle Applications guidelines increasing the value can have a performance impact.

1. Go into the responsibility: System Administrator (or equivalent).
2. Navigate to Profiles > Query the profile FND: View Object Max Fetch Size at Site, Application (Oracle Configurator)
and User Level
3.Change the value from 200 to a higher value (i.e. 250, 300 etc..).
4. Log out of the Application and back in.
5. Please retest the issue.
6. If the issue is resolved, please migrate the solution as appropriate to other environments.

Monday, January 5, 2015

APP-PAY-06882: Assertion failure detected at location py3vntsetup:2.

 

Error:

Error while Payroll processing:-

HR_6882_HRPROC_ASSERT
LOCATION py3vntsetup:2
APP-PAY-06882: Assertion failure detected at location py3vntsetup:2.

Cause: an internal error has occurred at location py3vntsetup:2.

Action: please contact your Oracle customer representative.

Fix:


This is an environment issue with the newly cloned instance.



PY_LIB_PATH is set correctly with the Quantum library path, however, the Quantum Data Update Installer process is not able to access the Quantum libraries.


1) Relink PYUGEN and PYUVEN


adrelink.sh force=y ranlib=y 'pay PYUGEN'
adrelink.sh force=y ranlib=y ‘pay PYUVEN’

2) Bounce concurrent managers



3) Retest the issue.