Examine Account Index Error

Hi,
I have some resources with names ending with a pair of parentheses. e.g. ABC (India), XYZ (USA)
When I click on Examine Account Index in the resource tab (admin interface), it gives me this error message -
An Error Occurred: 'com.waveset.util.WavesetException: This item was not found: Resource: ABC (.'.
Steps to reproduce -
1-     Login to the admin interface.
2-     Click on Resources
3-     Click on Examine Account Index
4-     Click on the + sign at the left of the folder called: Database Table
5-     Click on the + sign at the left of the resource called: ABC (India)
I see another resource with name ABC (India) Systems, and follow above steps, it works fine.
I think it gives me error only when the resource name ends with a closing parentheses.
Please suggest.
Thanks.

There is, It may or may not apply to your case.
Bug#4252: Recon confused by account names only differing in case.
description
On resources where account names are case-sensitive, it is possible to have two accounts which are identical except for case differences. When this happens recon will effectively not see the instances beyond the first of the matching accounts.
/description
There must be other ways for the index to get messed up, I am seeing the same error and we're using a numeric value as our account name so this can't be it. You are supposed to be able to delete the account index and it will be recreated at your next FULL reconcile. I haven't tried this yet so your mileage may vary but it looks relitavely safe.
I got this recomendation in a response to my ticket for the same problem I hate to pass on a solution I haven't had the opportunity to try yet (we use password sync so I can't afford to have my accounts unliked during the week.)
3.3 My best guess is that there's a problem with one of the account
index records. I would suggest:
3.3.1 Save the current account index (lh console; export Account.xml
Account)
Note 1: I wouldn't suggest the "-v" ... there are almost certainly a
huge number of accounts and this will only slow down the execution
Note 2: This could produce 1-2 G of data (or more, depending on how
many account objects)
Note 3: This export could take a LONG TIME ... depending on size.
This can be done while IdM is running.
Note 4: This export isn't strictly necessary, deleting the account
index is a safe operation ... meaning recon will rebuild it as
necessary
3.3.2 Run a full reconciliation to rebuild the account index

Similar Messages

Java.lang.NullPointerException in 'Examine Account index' Tab

When I open a ressource in the Examine Account index Tab I get the error message 'java.lang.NullPointerException' within a message window.
Is there a Bug withing IDM?

There is, It may or may not apply to your case.
Bug#4252: Recon confused by account names only differing in case.
description
On resources where account names are case-sensitive, it is possible to have two accounts which are identical except for case differences. When this happens recon will effectively not see the instances beyond the first of the matching accounts.
/description
There must be other ways for the index to get messed up, I am seeing the same error and we're using a numeric value as our account name so this can't be it. You are supposed to be able to delete the account index and it will be recreated at your next FULL reconcile. I haven't tried this yet so your mileage may vary but it looks relitavely safe.
I got this recomendation in a response to my ticket for the same problem I hate to pass on a solution I haven't had the opportunity to try yet (we use password sync so I can't afford to have my accounts unliked during the week.)
3.3 My best guess is that there's a problem with one of the account
index records. I would suggest:
3.3.1 Save the current account index (lh console; export Account.xml
Account)
Note 1: I wouldn't suggest the "-v" ... there are almost certainly a
huge number of accounts and this will only slow down the execution
Note 2: This could produce 1-2 G of data (or more, depending on how
many account objects)
Note 3: This export could take a LONG TIME ... depending on size.
This can be done while IdM is running.
Note 4: This export isn't strictly necessary, deleting the account
index is a safe operation ... meaning recon will rebuild it as
necessary
3.3.2 Run a full reconciliation to rebuild the account index

Account determination error in FI doc during SD billing doc posting.

hi,
when I create one billing doc ref to s/o,
I check account determination in condition type:
G/L account no.: 110000
Provision acc. : 120000
in FI doc,
should debit 110000 and credit 120000
but current status is credit 110000 and debit 120000
Please help.
Thanks.

Hi,
One of the following could be the reasons for the Account determination error.
Please check.
1.Incorrect account assignment group entered in the customer and material master
Resolution:Maintain correct account assignment group in customer and material master,Eg.External Domestic,Z1 - External Foreign,Internal Foreign,etc,.
2.GL account not extended to the respective company code.
Resolution:Extend the required GL account to the company code.
Regards,
Sophia Xavier

Account determination error in Billing

Dear Expert,
I create one billing doc(1840000318) based on SO:1810000296. But in the posting status it is showing "Posting document not created(account determn error) in billing. I did not found any FI relavant docs for this billing in open item customer list.
*Anyone can advice me why the FI docs not created automatically..???
**Do you think there any missing configuration set?
***Or if I cancel the billing docs then it will okay or not ?
Thanks & b.Rgds
Bishnu

Hi Bishnu,
Check Points for Account Determination.
1. Ensure Cutomer master (Xd02)Sales Area Data- Billing Tab-- Acc Assign Grp ---Should be maintained
2. Material Master -
Sales Org-2----
Acc Assign Grp..Should be maintained.
3. In VKOA maintain
Application- V Chart of Accounts--Sales Org ---Acc Assgn Gp Of Cust -Acc Assgn Gp of Material-Acc Keys (ERL,ERS,ERF)----& G/L Account.
4. In ur Pricing Procedure i.e V/08... Maintain Reqt -2 corresponding to ERL,ERS,ERF. & Subtotal =9 in front of net total.
Revert for further clarification.
Regards
Amit Gupta

Account determination error in Invoice document posting

Problem - When generating the invoice document to customer, an error is displayed - Document is saved (Account determination error). As a consequence of this step, the invoicing is not able to create FI document
My Analysis-
Account determination is done in G/L account assignment (VKOA screen)
For my billing document, the system is not able to find the GL account (below are screenshots)
In VKOA screen, I already defined the GL account determination using KOFI procedure.
I initially defined in table 2 Cust.Grp/Account Key and it didnt work.
So I defined in both the tables 1 as well - Cust.Grp/MaterialGrp/AcctKey
But still system is not reading the tables and obtaining the GL account no
Any advice on why its not working?

Hi Nikhil,
As per the screen shots i could observe that you didn't maintained acct asst grp of customer.
check the acct asst grp of customer field in billing tab is maintained or not.
other possible reason may be in your pricing procedure -check whether the accounting keys are maintained or not.
This could solve your issue.

How can I remove an email account from my mail box list? I added the account as an iCloud IMAP account in error.

How do I remove an mailbox I recently added as an iCloud IMAP account in error? It should have been added as a POP account.

Highlight it in Mail > Preferences > Account and click on the "-" tab at the bottom of the list panel.

Invalid column Index error - While consuming Calculation view via Native SQL

Hi Experts,
I am trying to consume a Calculation view (sql script one) , which has input parameters, via Native SQL in a ABAP program .
Code snippet for the same would be as follows , Upon execution, it throws an error "Invalid Column Index (8) error " . Can anyone help what could be the issue here ?
Thanks in Advance,
Suma
REPORT ZTEST_HANA2.
*Report to consume Calculation view (script based) from ABAP
PARAMETERS: ip_docnr type BELNR_D,
            ip_gjahr type GJAHR,
            ip_bukrs type BUKRS,
            ip_blgr type FAGL_RLDNR.
   DATA: LO_SQL_STMT TYPE REF TO CL_SQL_STATEMENT,
          LO_CONN     TYPE REF TO CL_SQL_CONNECTION,
          LO_RESULT   TYPE REF TO CL_SQL_RESULT_SET,
          LV_SQL      TYPE STRING,
          LR_DATA     TYPE REF TO DATA.
    DATA: LX_SQL_EXC           TYPE REF TO CX_SQL_EXCEPTION,
          LT_SEPMAPPS_CLSDINV TYPE TABLE OF SEPMAPPS_CLSDINV,
          LV_TEXT              TYPE STRING.
    TRY.
lv_sql = |SELECT * FROM "_SYS_BIC"."DEMO-ABAP/CA_GET_FI_DATA" | &&
                 |WITH PARAMETERS ('placeholder'= ('$$p_DOCNR$$','{ ip_docnr }'),| &&
                  |'placeholder'=('$$p_GJAHR$$','{ ip_gjahr }')| &&
                  |,'placeholder'= ('$$S_BUKRS$$','{ ip_bukrs }')| &&
                  |,'placeholder'= ('$$p_base_ledger$$','{ ip_blgr }') )| .
         LO_CONN = CL_SQL_CONNECTION=>GET_CONNECTION( ).
         "Create an SQL statement to be executed via the connection
          LO_SQL_STMT = LO_CONN->CREATE_STATEMENT( ).
         "Execute the native SQL query
         LO_RESULT = LO_SQL_STMT->EXECUTE_QUERY( LV_SQL ).
         "Read the result into the internal table lt_sepmapps_clsdinv
         GET REFERENCE OF LT_SEPMAPPS_CLSDINV INTO LR_DATA.
         LO_RESULT->SET_PARAM_TABLE( LR_DATA ).
         LO_RESULT->NEXT_PACKAGE( ).
         LO_RESULT->CLOSE( ).
         LO_CONN->CLOSE( ).
    CATCH CX_SQL_EXCEPTION INTO LX_SQL_EXC.
         LV_TEXT = LX_SQL_EXC->GET_TEXT( ).
         MESSAGE LV_TEXT TYPE 'E'.
    ENDTRY.

Hi Suma,
Post the SQL you success run directly on Studio together with error message (even if is the Invalid column index error).
Check there if the parameters case is working properly... Is it really this confusing options:
p_GJAHR
S_BUKRS
p_base_ledger
Why not all lower or all upper? Anyhow you must test and find which option works according your modeling
Regards, Fernando Da Rós

G/L Account blocked Error while posting goods delivery in VL02n transaction

Our Requirement is to change the G/L account which is proposed by OBYC(automatic account determination ) as per the movement typ and order reason from a Ztable. We need a place to code this logic before this OBYC check happens due to which we getting the account blocked error.
Please suggest some user exit or enhancemnet point where we can place this logic.

hi Ramki.,
I had configured a Surcharge on delivery in the condition type to be calculated on the qty delivered. Say for every Gallon, a surcharge of 0.2 cents is charged. I had maintained ths surcharge as a separate condition type and assigned it to a separate G/L a/c.
Now during PO creation, in the header , the price remains the same as i give for the Unit price.
IN the conditions tab in Item level, the surcharge is added on to the gross price and i get a Net Price.
Without saving the PO, when i go to see the Print-preview, i see only the Gross price.
After saving the PO, in print review, i see
1. Unit gross price under Sl.No.1
2. After the Item description, immediately, there is qty ordered x unit price + surcharge and them following Nett price
3. At the bottom right corner of the PO, i get qty ordered x unit price only . Surcharge amount does not appear.
How do i get the Total Nett price i.e qty ordered x unit price + surcharge to appear on the bottom right of the PO.
Is it a standard functionality for the Total price to appear or does it involve the role of ABAP programming.???
Do clarify my doubts
Tx
MahesH

While doing service in service po we get account assignment error pls help

while doing services in service po we get error account assignment error (se181) pls help to resolve

Hi,
a service line can be never saved WITHOUT the account assignment details (except acc. ***. category U in in the PO item).
In case the table ESLL will have entry but the accounting tables eskl has got no entry or has entries with deletion flag, it would be an inconsistent situation.
You can set on the screen SAPLMLSK 0200 the deletion flag (ESKL-LOEKZ) for your service account assignment, but without entering a new account assignment information the system would not allow you to leave this screen. When you set the deletion flag for service line in the account assignment detail screen, you must enter right afterwards a new account assignment information in order to leave the screen without the error message 06 408.
Regards,
Edit

Account determination error

hi
when i a creating a billing document for third patry sales with refernce to sales order
while saving the doc i am facing error called account determination error
can i now where i am wrong
do i have to amitained ant record in VKOA
if yes what
Screen shot
http://www.4shared.com/file/59857963/f56431d5/fico.html
Regards
Vini

The access you are using for maintaining the condition record. The screen shows the first two accesses which means that there is something wrong with that.
If your acct determination is not carried out then it will say acct. det has not been done . \
Looks like your condition records and the acct. determination seems to be a problem.
GO to acct. det. in BAsic functions- revenue acct detemination I think its VKOA and check your account determnation to see if your account keys and accounts have been correctly maintianed.
Check your pricing procedure to see if all the relevant condition types have been assigned to the account keys.
check if your condition records have been maintianed in the correct accesses. It will solce your problem.
regds
Jude

Account Determination error while goods receipt

I am trying to receive a Purchase order thru MIGO transaction. I got an error message saying "Account Determination for entry IPGL FR1 0040 not possible".
This error message came only when i had "FRB1" condition type in Purchase Order Conditions. Without FRB1 condition type in conditions i am able to receive the Purchase Order thru MIGO.
IPGL is the chart of accounts in our company.
What is FR1 in the error message ?
What is 0040 ?
What is the connection between condition type FRB1 and Account determination?
What do i need to do to fix the issue?
I greatly appreciate any help from you guys.

Prashanth,
I would encourage you to search the forum before posting any question (if you have the time, interest etc). It is likely that youu question (or a similar question) would have been answered previously.
Please search the forum with 'account determination error' for instance. I get 11 hits. You can try searching with other similar terms. Read the hits and then come back if you still have questions.
I don't intend to be unhelpful but I felt the need to point this out (although most people don't seem to care).
H Narayan

Account determination error for EK02

Hi,
I am using EK02 for unit costing in quotation used specially for PS.
I have assigned EK02 in the quotation doc type and have added the same to the pricing procedure (marked it manual & ststistical) and assigned it SubTotal-B.
It is working perfectly in the quotation but while in Sales Order it is giving account determination error for EK02.
I am unable to understand when there is no account key assigned to it, how is this error ?
Please advise immediately.
Regards,
Rajesh

Check the Requirement class in order - in procurement tab.
when you use the EK02 cost estimation condition type, Controlling documents get generated once you save the sales order.
i.e. the reason, in VKOA for the all the access keys maintained in order pricing procedure, should have valid record with Costing conditon type:KOFK.
maitain entries in table:005- Account key for all the account keys maitained
such as;
Application / Condition type-KOFK/ chart of accounts/ Acct key - G/L account ( here maintain same G/L account which have you assigned with Condition type KOFI)
it will solve your issue.

Account determination error at billing level

Hi,
for Account determination error at billing level
i checked the line item level for the material by highlighting the item, then GO TO > ITEM > ITEM DETAILS. here 5 line items are there , 4 line items have same "Acct asgnmt grp" and 1 line item is different at order level. i gess this is the problem if am wrong please correct me.
thanks
Edited by: pandu123 on May 26, 2011 2:24 AM
Edited by: pandu123 on May 26, 2011 2:32 AM

Hi Pandu
A/c deterimation error. 1st you check in customer master sales area data billing tab page with account assingment and go to material master u select particular material see in sales organization 2 tab with account assignment. and go to T.Code VKOA check the combination which is assiged A/c assingmnet group of customer and matrial account assingment group. If it is not come goto VFX3 and specify the customer execute and click on RELEASE FLAG. If it is error go to log see the digonsis.
Kind Regards
Chandra Mouli A

Account Determination Error - Discounts - ERS

Dear All,
When I am releasing my Billing Document, I am getting the "Account Determination Error".
My Requirement: Sales Discounts should not post to ERS Account Key.
Price          -     PR00 - 10000 ERL GL Account (10000)
Discount    -     K004 - 10%
                                     900
Base Price                   9, 100 INR
In the Accounting ENtry - it has to show only Customer Account 9100 Dr to Sales Revenue A/c 9100.
I don't want to show Sales Discount 900 Rs.
For this in pricing procedure configuration - i have removed ERS Act key (for not posting), becoz of this - I am getting the Account Determination Error.
Any Idea on How to Configure the above scenario?
Ganesh Varma G.

In pricing procedure
MAINTAIN SUBTOTAL CONDITION AFTER DISCOUNT IN PRICING. MAINTAIN THE DISCOUNT CONDITION AS STATISTICAL.
MAINTAIN ACCOUNT KEY ERL FOR SUBTOTAL.
STEP COND TYPE                FROM             TO         STAT     ACCT KEY
10       PR00                                                                             -
20       K004                                                                 X          -
         price after discount      10                  20                        ERL

Account determination error for Account key

Hi Everyone,
I have maintain one condition manual pricing e.g ZMRG where i m manually putting the margin of sales price
this condition is only for calculation and i dont want to post it to account. But at the time of bill it is giving me account determination error. In VF02 i check it is showing error due to not assigning the account key for that condition but here i dont want to post that condition to accounts.
Please suggest me the best possible way.
Regards
Shambhu

Hi,
You said that the condition is manual.
Now you saying:
i maintained the condition for it instead of only text in PP
Have you got the solution? Then please update.
Thanks,
Ravi

Examine Account Index Error

Similar Messages

Maybe you are looking for