Do you see the error while creating AR transactions "System cannot determine geographical information for this location and cannot derive a tax jurisdiction"??

You might want to check if the geography and tax validations are enabled for that country for which you are seeing this error....

If they are enabled then you might have not run the 'Geography name referencing program' for this country...

To implement the solution, execute the following steps:

1. First check if there is a value for profile option HZ :Generate Party Number, if no, set it to 'yes'. Post that follow the below steps.
2. For the ship-to/bill-to which is failing navigate to the customer form and look up the particular ship-to/bill-to record. Please make note of the site number 
3. Run the following queries to determine the location_id which is failing
   
   
   select party_site_id, party_id, location_id
   from hz_party_sites
   where party_site_number = '&site_number';
   
   
   select location_id, country, address1, address2, address3, city, postal_code, state, county
   from hz_locations
   where location_id = &location_id; 
4.  once you have the valid location id, then run this query
   
   select map_status, location_id
   from hz_geo_name_reference_log
   where location_id = &location_id;
   
   Map_status S means that the location_id is successfully created.
   Map_status E means that the location_id has not been successfully created.
   
   
5. Navigate to Trading Community Manager -> Administration -> Geography Hierarchy
   
   Click on Manage Validations, and find the geography mapping and validations.
   
   For eg:
   State, County, City, Postal Code
   
   Verify if tax validation and geography validation is enabled for each of the segments
   
   
6. In the customer form, query the customer in question and review the ship-to, bill-to addresses
   
   The format you selected under the geography hierarchy must match what you have entered under each bill-to, ship-to
   
   for example if you are missing the county and you have selected to have this segment validated under the geography hiearchy, you must have this field entered for the ship-to, bill-to under the customer.

R12: Build Program Ends with Error after Review of Invoices RUP4

Build Program Error:

I am trying to make batch payment in Release 12 via a Payment Manager.

The invoice which are selected by the payment process request belong to 2 operating units. The problem comes with the build progam getting errored out.

The out file displays the following message:
"Build program error: Exception occured when attempting to create payments from the documents payable of the provided payment service request."

The log file is as follows:

---------------------------------------------------------------------------
Payments: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

IBYBUILD module: Build Payments
---------------------------------------------------------------------------

Current system time is 22-JUN-2009 15:08:50

---------------------------------------------------------------------------

**Starts**22-JUN-2009 15:08:50
**Ends**22-JUN-2009 15:09:08
BUILD PROGRAM ERROR - CANNOT CREATE PAYMENTS
---------------------------------------------------------------------------
Start of log messages from FND_FILE
---------------------------------------------------------------------------
---------------------------------------------------------------------------
End of log messages from FND_FILE
---------------------------------------------------------------------------

---------------------------------------------------------------------------
Executing request completion options...


Finished executing request completion options.

---------------------------------------------------------------------------
Concurrent request completed
Current system time is 22-JUN-2009 15:09:09


Could someone please provide a solution for this??

Please refer to this document: Note: 558114.1

Granting access for Banks to Legal Entity

With release 12, the legal entity took the ownership of the banks. To grant access to banks

1) Access user management responsibility
2) Go to roles and Inheritance tab
3) Select roles and responsibilities, choose our responsibility name and the appliction to which it belongs to
4) Click on update icon
5) Select the tab security wizards
6) Run thesecurity wizard named, CE_UMX_Securitywizard
7) Choose the legal entities to whichyou would want to give the access and save the information

Why should we do this???

You would not need to, unless you want to associate a legal owner(LE) while creating a bank account ;)

AP/ AR Netting Set ups and transactions

Setups required for AP/AR Netting:

1. Netting control Account:
In GL module
Path: Setup>Financials>Flexfields>Key>Values
Segment qualifier for netting control account = Liability

2. Netting bank, branch and bank account.
Netting flag to be set as yes for the bank account
use netting control account in placeof cash and cash clearing account

Note:
? Reason for defining netting control account.
:) To facilitate us to use it as cash account while defining netting bank account

? Why should you use netting control account in place of netting bank account
:) As you not actually paying or receiving cashwhile you are performing netting

3. Netting receipt class
Receivables module
path: setup>receipts>receipt classes

? Why do we need a netting receipt class
:) To facilitate the system to create a receipt automatically specifying the mode in which we received this receipt as netting

4.Netting Agreement
Canbe created either from payables or receivables
path(AP) payments>netting>netting agreement
path(AR) receipts>netting>netting agreement


5. Netting batch
Picks the invoices and AR transactions to be netted as per the criteria specified in the netting agreement.

6. Submit the netting batch.Review the invoices and transactions picked. Resubmit the batch and viewthe proposed and final netting reports.

Making payments of multiple operating units

Are you trying to make payment of invoices pertaining to multiple operating units having different transacting currencies??

Here is the list of what you need.
1. A bank with multiple currency flag enables. Similarly the check boxes of multi currency payments and multi currency receipts should be enabled.

2. A payment process profile with the payment format specified for the payable documents defined for the bank

3. Exchage rate type and rate defined for the foeign currencies

Transaction part.
1. Raise invoices intherespective OUs
2. create a payment process request via payment manager
3. generate payments

Validate Application Accounting Definition

Unable to create online accounting???

When you are implementing on a fresh instance for you to be able to do the accounting of your transactions. you should run the following request "Validate Application ccounting Definition" request.

Make sure that both in GL and AP the period in which the transactions exist are open.

Cheers.

Invoice currency field grayed out

Invoice currency field grayed out:

I created a multi org with 2 OUs one in the US and the other in India. The currencies are USD and INR respectively. While keying in an invoice, the invoice currency tab is greyed out and only one currency is automatically picked and is not letting me change???

Soulution:

Go to Currency tab in Payable options and enable the check box, multiple currencies. Give the realised gain and relaised loss account and the rounding differences account.

And your problem is solved :)

Release 11i iPayment module now made obsolete with R12

releas11 ipayment module now made obsolete

The module ipayment in release 11 is now made obsolete and all the functionality that could be done earlier is now available via the new module Oracle Payments with effect from release 12.

Oracle Payments concentrates on two processes, broadly stated:
--> Funds Capture Process
--> Funds Disbursement Process

Enhancements in Payables with Release 12

Enhancements in Payables with Release 12

Lets have a brief look at the enhancements in the payables module with release 12
1. Suppliers became a part of Trading Community Architechture(TCA)
2. Banks ownership moved to Legal Entity and now supplier banks can be defined in
supplier definion page it self.
3. The contra charge functionality in R11 is now known as AP Ar Netting
4. Invoice Lines concept and there by line level approval, line level hold, mapping at
line level to asset books or to projects
5. Retainae and Retainage release
6. Recoupment
7. Now batch payments cant be made within payables module but can be dont using the new module oracle payments.

R12 Payables - Hierarchy in which liability account defautls

Hierarchy in which liability account defaults in Oracle Payables

1. Financial Options
2. Supplier
3. Invoice

First the system would look at the accounting details tab of the supplier definition for liability account. If a value is defined for liability account;then this value has precedence to the one provided at financial options.

So when creating an invoice once the supplier(Trading Partner)name is specified the system would look in to the accounting tab of supplier definition. If nothing is specified here, the system would pick the value provided in financial options. Please note that The account provided in financial options would automatically be populated in the suppliers accounting tab; but this can be overridden;

Also note that the one provided at suppliers accounting tab defaults to the invoice created for this supplier but this can be overriden. Only this is you have to select in the menu Folder>Show Field>Liability Account; once the liability account is displayed change liability account that is getting defaulted.

AS - 29 Provisions, Contingent liabilities and Contingent Assets

AS 29 a brief summary

Hi I would just like to provide a brief overview of

AS 29 - Provisions, Continget liabilities and contingent assets:

A provision should be recognised in Fin Sts if the following three conditions are satisfied:

1) There is a present obligation as a result of past events
2) It is probable that an outflow of resources embodying economic benefits wud be required to settle the obligation;
3) A reliable estimate of the amount of the obligation could be made.

If all the above three conditions are satisfied then recognise a provision; else,disclose it as a contingent liability unless the possibility of the outflow of resources is REMOTE.


U shud not forget that ----->

A provision should be disclosed at an amount equal to the best estimate( taking account of related future events) of the expenditure required to settle the obligation.

->It should not be discounted to present values( where as IAS 337 requires discounting)

->It should be disclosed pre-taxAlso do not forget to consider the effect of latest legislations, if their enactment is virtually certain.

->Reimbursements:
if say u have to create a prov of rs one lakh and u expect a reimbursement of 20,000(say from insurance people) - then create a seperate asset to the extent of 20000
...........mind u that reimbursement should be recognised only if its receipt is virtually certian



AS 29 - Disclosure Requirements

Well these differ on the basis of whether the company you are auditing is a level one entity or level two or in level three ..

as u correctly guessed if you are in
----> level one : disclose all
----> level two : except some diclose all
----> level three : there is some more lenience

well if the company u r auditing is in LEVEL TWO you DONT need to disclose these:

->with regards to provision:
-nature of the obligation-expected timing of outflows as a result of above obligation-uncertainities wid respect to above obligation-reimbursement with respect to above provisions

if it is LEVEL THREE COMMPANY:In addition to the above u dont need to dislose the following with regards to contingent liability:-Description and nature of the contingent liability-financial impact of such liability-uncertainities relating to above-any possibility of related reimbursement.

If the company is in LEVEL ONE disclose all the above and also disclose:

1) Opening and Closing balances of a provision
2)additional provisions made during current year, also additions made to the existing ones
3)Amounts used in current year from the provision created
4)any reversal of provisions
5)also if Contingent liability relates to a lawsuite and if the disclosures relating to the same would lead to any problems for the company.......
then company need not disclose the same and should mention the fact of existence of dispute


mm also if an enterprise needs to disclose smthg as per this AS but is not disclosing the fact should be stated in the notes.

Well I know its quite big, but better than the verbatim standard...