Errors on Discovering Asset using Discovery Plan**

I just found out the errors when I tried to add the asset using discovery plan. The error appear on the step of "PopulateModel" , I just dont know why it failed.
Anyone please help me :)
Errors
Model Population fail for the OpsCenter-3178b13b/com.sun.hss.domain:name=10.20.7.53-global,type=ZoneServerContainer at 10.20.7.53 (10.20.7.53) OpsCenter-3178b13b/com.sun.hss.domain:name=10.20.7.53-global,type=ZoneServerContainer removed from the domain model (10029)
Thx.

Did you find a solution to this error ?

Similar Messages

ERROR: insufficient privileges while using EXPLAIN PLAN command

Hi,
I have a table named TEST and i ran following command on this table.
SQL> EXPLAIN PLAN FOR
2 SELECT NAME FROM TEST;
SELECT NAME FROM TEST
ERROR at line 2:
ORA-01031: insufficient privileges
So which privilege do i need to give for using EXPLAIN PLAN command.
Thank.

http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14211/ex_plan.htm#i19260
SQL> @C:\oracle\product\10.2.0\db_1\RDBMS\ADMIN\utlxplan.sql
Table created.
SQL> select table_name from user_tables where table_name='PLAN_TABLE';
TABLE_NAME
PLAN_TABLE
You might consider checking dba_tables to check the owner in your case and may be you don't privilege on that table.

Getting error while loading assets using API

The error is as follows.
l_error:Error: function fa_cache_pkg.fazcbc returned failure
l_error:Error: function fa_addition_pub.do_addition returned failure
Can anyone please let me know if you have solution

Hi Vinod,
The error is as follows.
FA Details Update Failed for BX Number:BX130614
FA Details Update Failed x_error_buf:ORA-0000: normal, successful completion - FA Details Update Failed ....!
l_error:
l_error:Error: function fa_cache_pkg.fazcbc returned failure
l_error:Error: function fa_addition_pub.do_addition returned failure
l_error:
l_error:
l_error:
l_error:
l_error:
l_error:Error: function fa_cache_pkg.fazcbc returned failure
l_error:Error: function fa_addition_pub.do_addition returned failure
l_error:
l_error:
l_error:
l_error:
l_error:
l_error:Error: function fa_cache_pkg.fazcbc returned failure
l_error:Error: function fa_addition_pub.do_addition returned failure
l_error:
l_error:
l_error:
l_error:
the code which we are using is.
lx_trans_rec.transaction_type_code          :='CAPITALIZED';
        lx_trans_rec.transaction_date_entered       :=l_receiving_date;
        lx_dist_trans_rec.transaction_type_code     :='CAPITALIZED';
        lx_dist_trans_rec.transaction_date_entered :=l_receiving_date;
        lx_asset_hdr_rec.book_type_code             :='CTO CORP BOOK';
        lx_asset_desc_rec.asset_number              :=p_bx_number;
        lx_asset_desc_rec.description               :=l_make||'.'||l_model;
        lx_asset_desc_rec.asset_key_ccid            :=1001;
        lx_asset_desc_rec.in_use_flag               :='YES';
        lx_asset_desc_rec.inventorial               :='YES';
        lx_asset_desc_rec.owned_leased              :='OWNED';
        lx_asset_desc_rec.new_used                  :='NEW';
        lx_asset_desc_rec.current_units             :=1;
        lx_asset_desc_rec.unit_adjustment_flag      :='NO';
        lx_asset_type_rec.asset_type                :='CAPITALIZED';
        lx_asset_cat_rec.category_id                :=1;
        lx_asset_fin_rec.date_placed_in_service     :=l_receiving_date;
        lx_asset_fin_rec.deprn_start_date           :=l_receiving_date;
        lx_asset_fin_rec.deprn_method_code          :='STL';
        lx_asset_fin_rec.life_in_months             :=240;
        lx_asset_fin_rec.cost                       :=l_purchase_price;
        lx_asset_fin_rec.original_cost              :=l_purchase_price;          --Added by sive for the Original cost
        lx_asset_fin_rec.recoverable_cost           :=l_purchase_price;          --Added by sive for the Original cost
        lx_asset_fin_rec.prorate_convention_code    :='CTO PRORAT';
        lx_asset_fin_rec.depreciate_flag            :='YES';
        -- deprn info
   lx_asset_deprn_rec.ytd_deprn                   := 0.00;
   lx_asset_deprn_rec.deprn_reserve               := 0.00;
   lx_asset_deprn_rec.bonus_ytd_deprn             := 0;
   lx_asset_deprn_rec.bonus_deprn_reserve         := 0;
            l_asset_dist_rec.units_assigned         := 1;
            l_asset_dist_rec.expense_ccid         := 1060;--4013;
            l_asset_dist_rec.location_ccid         := 1;--1001;
            l_asset_dist_rec.assigned_to         := NULL;
            l_asset_dist_rec.transaction_units      :=1;
            lx_asset_dist_tbl(1)             := l_asset_dist_rec;
           FA_ADDITION_PUB.DO_ADDITION(
            -- Standard Parameters --
            p_api_version           => 1.0,
            p_init_msg_list         => FND_API.G_FALSE,
            p_commit                => FND_API.G_FALSE,
            p_validation_level      => FND_API.G_VALID_LEVEL_FULL,
            x_return_status         => l_return_status,
            x_msg_count             => x_msg_count,
            x_msg_data              => l_msg_data,
            p_calling_fn            => l_calling_fn,
            -- Transaction Object --
            px_trans_rec            => lx_trans_rec,
            px_dist_trans_rec       => lx_dist_trans_rec,
            -- Asset Object --
            px_asset_hdr_rec        => lx_asset_hdr_rec,
            px_asset_desc_rec       => lx_asset_desc_rec,
            px_asset_type_rec       => lx_asset_type_rec,
            px_asset_cat_rec        => lx_asset_cat_rec,
            px_asset_hierarchy_rec => lx_asset_hierarchy_rec,
            px_asset_fin_rec        => lx_asset_fin_rec,
            px_asset_deprn_rec      => lx_asset_deprn_rec,
            px_asset_dist_tbl       => lx_asset_dist_tbl,
            -- Invoice Object --
            px_inv_tbl              => lx_inv_tbl);
                        IF (l_return_status <> fnd_api.g_ret_sts_success)
                        THEN
                                x_ret_code := sqlcode;
                                x_error_buf := sqlerrm||' - FA Details Update Failed ....!';
                                FND_FILE.PUT_LINE( FND_FILE.LOG,'FA Details Update Failed for BX Number:'||p_bx_number);
                                FND_FILE.PUT_LINE( FND_FILE.LOG,'FA Details Update Failed x_error_buf:'||SUBSTR(x_error_buf, 1, 200));
                                      IF (fnd_msg_pub.count_msg > 1)
                                      THEN
                                            FOR j IN 1 .. fnd_msg_pub.count_msg
                                            LOOP
                                                  fnd_msg_pub.get(p_msg_index      => j,
                                                                  p_encoded        => 'F',
                                                                  p_data           => l_msg_data,
                                                                  p_msg_index_out => l_msg_index_out);
                                                 l_error   :=    SUBSTR(l_error, 1, 400)||SUBSTR(l_msg_data, 1, 400);
                                                 FND_FILE.PUT_LINE( FND_FILE.LOG, 'l_error:'||SUBSTR(l_msg_data,1,400) );
                                            END LOOP;
                                      ELSE
                                            fnd_msg_pub.get(p_msg_index       => 1,
                                                           p_encoded         => 'F',
                                                            p_data            => l_msg_data,
                                                            p_msg_index_out   => l_msg_index_out);
                                            l_error      :=     SUBSTR(l_error, 1, 400)||SUBSTR(l_msg_data, 1, 400);
                                                 FND_FILE.PUT_LINE( FND_FILE.LOG, 'l_error:'||SUBSTR(l_msg_data,1,400) );
                                      END IF;
                        ELSIF (l_return_status = 'S')
                        THEN
                                   x_ret_code := sqlcode;
                               x_error_buf := sqlerrm||'FA Details Updated Successfully ';
                                FND_FILE.PUT_LINE( FND_FILE.LOG,'FA Details Updated Successfully for BX Number:'||p_bx_number);
                        END IF;
   END;
Regards,
Siva

Error SP2-0027 while using explain plan

I'm using explain paln command in order to get the tables
acceeded by a SQL query.
When I use the command with some of them, that's OK.
But when I use it with a query of 4999 characters, it gives me
this error message:
SP2-0027: Input is too long (> 2499 characters) - line ignored
Has anybody an idea to solve this problem or to change this
limit of 2499?

user12043927 wrote:
Open the file (or copy the sql) in a text editor and then resave the file as a different file type.
In Microsoft Word, you click on File, Save As, then select file type 'text only with line breaks' and save the file. Once this is done, you can successfully run the script from SQL*Plus or Server Manager.You never get a second chance for your first impression.
As your first post you resurrect a ten year dead zombie post.
SWEET!
Can you find a post that is older & dormant to boost your post count?

Error while creating Legacy Asset using AS91

Error is as follows
E698 SYST: Abnormal termination (ANLB-LGJAN 1 not equal to ANLC-GJAHR
In 2008 during implementation, there was a mis match between FI & AA.
In AA Takeover values were not updated but GL entry was made. Now since depreciation is run, it is not allowing to update takeover values in AS92.
Now the i have planned to follow this procedure
Firstly Reset Depreciation
Then to create new Assets in AA copying previous assets without Takeover values using AS 91 & update those takeover values in new assets.
Then FI & AA values would match & then i can run depreciation.
But in 2nd step i am stucked, as when i try creating new asset using AS91 it is giving above error.
What should be date of legacy data transfer in spro? i have maintained 30.09.2008
In OAAQ i have maintained closed FY =2007
In OB52 i have Opened both 2008 & 2009 posting periods.
What more has to be done?

Hi Paul
I have taken a production copy in different client & have done all these with the client's permission.
Following are the reasons with example
suppose these are 4 assets at the time of implementation
1 Asset A       Acquisition value 100000/-      Accumulated Depreciation       20000/-
2 Asset B       Acquisition value 200000/-      Accumulated Depreciation       30000/-
3 Asset C       Acquisition value 300000/-      Accumulated Depreciation       40000/-
4 Asset D       Acquisition value 400000/-      Accumulated Depreciation       50000/-
In implementation following happened by mistakenly
Asset A & B were properly created using AS91 & in GL also entry properly made using OASV
but for Asset C, entry was made using OASV but in AA Tcode AS91 Asset Master was created but Takeover values were not updated.
for Asset D entry was made in OASV but in AA Asset number was not at all created.
so when you see asset master C in AW01N acquisition value is blank & planned depreciation is also missing.
i think individually all data was not cross tallyied.
So the Balance sheet is tallyied with entry in FI
but
in AA there are 100 assets without takeover values & 300 assets for which Asset Masters are not at all created in AA.
& depreciation for 2008 has been run on other assets excluding these 400 assets.
So now AA closing cannot be done as the FI & AA balances are not reconciled.
& now we have to update takeover values creating new asset masters using AS91 but system is not allowing us.
Could you suggest some solution for these problems
Thanks in Advance

Error while creating the ASSET using LSMW BAPI method ( BUS1022 )

Hello,
Im creating assets using the below LSMW BAPI method
Business Object      BUS1022
Method                     CREATEINCLVALUES
Message Type         FIXEDASSET_CREATEINCLVALU
Basic Type              FIXEDASSET_CREATEINCLVALU
the following errors were triggered while populating the values to ACQ_VALUE and ORD_DEP value.
Correction to ordinary dep. greater than acc. dep. in area 01
Correction to ordinary dep. greater than acc. dep. in area 30
Correction to ordinary dep. greater than acc. dep. in area 31
Correction to ordinary dep. greater than acc. dep. in area 32
if i pass only ACQ_VALUE, I am able to create the asset with out any issues.
Can you guys plz guide me to fix this issue to create the asset with both ACQ_VALUE and ORD_DEP values??
Cheers,
Sriram.

Hello,
Review AO21.
Regards
Waza

Error while creating fixed asset using BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE

Hi
I am getting an error stating "O DEP START field is not ready for input, while trying to create asset using the BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE.How to make the field input enabled in BAPI .Kindly suggest.
Thanks

Hello,
Review AO21.
Regards
Waza

Error AA662 in Asset accounting after upgrade to ECC 6

Hi,
After upgrade to ECC6 from R3 Enterprise, when we try to browse an asset, using transaction code AW01N, and go to posted values/Comparisons tab we get the following error:
SYST: You cannot change the depreciation periods
     Message no. AA662
Asset affected: 000000003983-0000
Diagnosis
    Processing terminated because the number of depreciation periods in company code 1100 has been changed. However, you cannot change the number of
    periods in your live (productive) system.
Procedure
    Change the depreciation periods back to the original value in company code 1100. The number of depreciation periods is determined by the fiscal year version and the use of half-periods. At least one of these parameters was changed.
     If you want to change your system so that you can now work with half-periods, you have to use depreciation keys with time-dependent period control in that company code.
    If you need to make general changes to the number of periods for calculating depreciation per fiscal year, you will have to consult your system administrator.
We were not getting this error in R3 enterprise. We have tried implementing sap note 1009699 but it does not resolve the issue. What we observed is, AA662 occurs if you change the number of period in the fiscal year version or the use of half-periods, after you have already posted to assets. The most common cause is a different value in field ANLB-PERFY which is the number of periods in the fiscal year. If the number entered here does not correspond to the number of posting periods of the fiscal year used, the system raises error AA662 (except for none posted areas for which ANLB-PERFY = 000 or areas with depreciation to the date for which ANLB-PERFY = 365). For us there are many assets with ANLB-PERFY=24.
Is there a way to fix this problem by some config change or data fix. If any of you have come across a similar issue or have any insights on the same, please respond back.
Regards,
Milan
([email protected])

Hi All,
I could not find any solution to fix this in new depreciation calculation method. I also did not get any help from SAP or SDN. So, we decided to switch back to the old calculation method.
There are 3 ways of implementing the old calculation.
1. SAP Note 984161 : Code change at ABAP level.
2. User Level : By setting the user parameter FAA_DC_SWITCH to OLD
3. By default Config : If we make an entry in V_TABWD_VID in SM30 and create a new entry with Acct. Transaction ID to 'AMBUAFAR000000000000', It should use old calculation method.
Thanks,
Milan
+1-310-691-3978
+91-994-571-5063

Error in generating data source from planning area

Hi experts! I have an error while making data source from planning area:
after the screen when i fill in the data source name (Window name: Generate export data source) i have the SYNTAX_ERROR Message:
Syntax error in program /sapapo/cl_im_extract_ex======cp
the main reason: the type /BI0/9A0IVWKNDGD is unknown
what you can suggest to solve this problem?
Thanks.

Dear Andrey Kudriavzev,
The reason is the program is trying to use the datatype '/BI0/9A0IVWKNDGD' which does not exist in the system.
Go SE11 to cross check if it exists. Check dataelement radiobutton -> enter /BI0/9A0IVWKNDGD -> Choose display option. You would need to create this datatype in the system. I feel there must some OSS Note related to this.
Search for an OSS Note. Raise one if you cannot find the relevant notes.
Regards,
Naveen.

Fixed asset error: 21151: error while posting asset document: '100000039'

Hello Experts,
How are you? We have a client who have encountered an error during fixed asset retirement thru scrappingu2026.In one retirement document, SAP did not assign an account in the account column but still the document was saved but with erroru2026On her next retirement document, she could no longer save her document and the error points to the last retirement document she has saved with error. We have tried to cancel the document and its journal entry but still she could no longer retire assets using scrapping. All other retirement transaction using scrapping could not be saved.
The client is using SAP B1 8.81 patch 5.
Thanks and best regards,
Luz

hi Luz Cornejo,
please do check this SAP Note: [1246921|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3030303132343639323126]
regards,
Fidel

FA Retirement- 21151: error while posting asset document: '100000039'

Hello Experts,
I have a client who encountered this error during fixed asset retirement - scrapping.
After selecting the asset to be retired, sap did not assign an account in the account column, but the user
was able to save the document. After saving it, the user needs to retire again another asset - scrapping, but the document would not be saved because of this error: 21151: error while posting asset document '100000039'. The document number the systems is referring to is the last document saved but sap did not assign an account code.
Please help. My client is using sap b1 8.81 patch5.
Regards,
Luz

Hi Too Mui Hwee,
What we did is to put letters on the number so the series will continue example there is already 100333, 100334, 100335 since the error is encountered from 100333. We add 100333A, 100334A, 100335A.
Thanks

Using patch plans for 12.1.0.2 target oracle home fails with 'PREREQ_MESG: Unable to get the version of OPatch'

We are attempting to use patch plan to apply PSU and one-offs to a new 12.1.0.2 database oracle home. Our EM version is 12.1.0.4.
We are experiencing the same issue described in ''Bug 20271609 : Unable to get the version of OPatch". This bug is closed as 'duplicate bug to filer' but we do not appear to have visibility into what patch/bug fixes the issue.
Description from the above mentioned bug is our same issue. We do not have this issue when we use patch plans against an 11.2.x oracle_home target. It is unique to 12.1.0.2 oracle_home target.
Description from the bug:
The Plan failed in step "Run Prerequisite Checks" with the following errors:
PREREQ_NAME: Minimum Version of OPatch
PREREQ_DESC: Check if the required version of OPatch is present on the target
PREREQ_TYPE: PATCH_TOOL_CHECK
PREREQ_STATUS: FAILED
PREREQ_MESG: Unable to get the version of OPatch at
/u01/app/oracle/product/12.1.0/dbhome_2/Opatch
We have opened an SR to see if we can get more info on what was already identified as a bug. Has anyone else experienced this issue? If so, can you share any patches or workarounds (other than manually applying patches) that you found useful?
Thanks.

You'll probably get the same info from Support, but the workaround is to use the Patch Database (however that doesn't work if there's no DB target associated to that home). If you were trying to do patchign out of place (clone home, patch, then move db's), EM can do this for you. If you're just installing a new DB Home and trying to patch, then i don' think there's another workaround. The base bug is marked fixed though, so a backport for the 12.1.0.6 plugin should be available very soon. I would ask the support analyst to request the backport for your plugin/patch level...

Error occurs during Asset Master Record Creation.

Hello SAP Gurus,
The error occurs during asset master record creation.
Our fiscal year variant is Z6 (July to June). The asset was acquired in June 15 (previous fiscal year) but was only set up on July 30 (this fiscal year) . When we put the depreciation start date as 15 June the error appeared. While saving the Asset master we are getting below error.
We tried the same with Post Capitalization of Asset (ABNAN) there also we are getting same error.
ERROR: - as below
u2003
SYST: *You cannot determine the period for rule 02 to 05.08.08 ( todayu2019s date )*
*Message no. AA613*
*Diagnosis*The system could not determine a depreciation period on 05.08.08 for period control 02 of the period control method of phase N1 of depreciation key INTERN-00001-0000.
Procedure
Maintain the assignment of the periods for the period control entered.
Proceed
If the period control you entered is a standard period control, you can assign the periods automatically.Proceed
Please find enclosed attachment for clear description of the error.
Please share your experiences regarding this subject.
Thanking you in anticipation.
Regards,
Suresh.
09986375966

Hi,
have you generated the period controls properly? If not, the error is raised correctly by the system.
To generate period controls go to:
IMG Asset Accounting -> Depreciation -> Valuation Methods -> Period Control -> Generate Period Controls / or you can use OA84
Regards,
Markus

Not able to use EXPLAIN PLAN in Toad

hi,
I am not able to use Explain Plan in Toad. The error it gives is the table PLAN_TABLE doesn't exit.
But after seeing this error I did run the script "UTLXPLAN.sql" in order to create the plan_table table.
After installing the above table I am not able to use EXPLAIN_PLAN from toad, Its giving same error Table PLAN_TABLE doesn't exit though i created it successfully in the proper schema.
Thanks in advance
Ram

check and post.
SQL> select owner from dba_tables where table_name='PLAN_TABLE';
before using toad ,first u should connect to sqlplus by that user and issue
SET AUTOTRACE ON.
Kuljeet

Muse error message re: Asset

Hi -- I got a error message on my Muse site when I open the site now:
"This document contains a link to an asset being unsampled. You should resize it smaller, or relink to a larger asset using the Assets panel."
Anyone had this error? How do you identify what asset the error is referring to? What is unsampled?
I am new to Muse and would appreciate any help/advice on this -- Bertine

You probably resized one of your asset iamges too large.
If you look at the "Assets Panel" shown below, it will give you a detailed description of the error or problem, and give you a solution to fix it!!
Hope this helps!
Julia

Errors on Discovering Asset using Discovery Plan**

Similar Messages

Maybe you are looking for