ABUMN-error "Posting transaction is not possible (Value date not allowed)"

Hi,
When we are trying to transfer asset within company code thru Tcode ABUMN, we are getting a error as
"Posting transaction is not possible (Value date not allowed)"
What actually we are doing is we are trying to transfer the previous year asset for example say 01.04.2007 assets on today.
the Parameters are as below
Document date :26.03.2008
Posting Date :26.03.2008
Asset value date is 01.04.2007.
Then the system is throwing an error and not alloing to post the previous year transfers.
Can any one help me out.
Cheers
Sri

Hi,
I think, if you give old asset value date, system will give you the error. This may be because, you are trying to transfer the assets with old values, means in your examble the dep. from the 01.04.2007 to 29.02.2008 whould have been charged.
So, give the current year date means any date from 01.01.2008 to till date.
If you read F1 help for the value date column, it states,
Asset value date
The asset value date is the value date for Asset Accounting. It can deviate from the posting and document date and be in posting periods already closed for Financial Accounting. However, the posting year and asset value date year must be the same.
Since the asset value date can have a direct influence on the amount of depreciation, the system creates a default value when it can. You can specify in Customizing how the the default asset value date is determined by the system.
Hope it helps
Saravanan.A

Similar Messages

Error in CJ88 Posting transaction is not possible (value date not allowed)

When i try CJ88 with a wbs element, it shows the following error :
Posting transaction is not possible (value date not allowed)
Message no. AA 478
Diagnosis
A retirement was already posted on the asset 000022400733 0041 on 20091231. Based on the value date 20091231 of the transaction, this transaction should have been included in the calculation of values for the retirement.
System Response
The transaction is rejected.
Procedure
Check the value date of the transaction.
In need to put year 2009 in date of the transaction, but it isnt posible. ¿Why? I dont know very much about asset accounting...

Hi
It is not allowing for WBS element final settlement, because of your asset already retairement was done.
By best suggetion is, You will create the new WBS element and transfer the all cost line items from old WBS element to new WBS element, then you will try to settlement for another asset in CJ88.
I hope it will use for you.
Regards
PVCPVC

Posting not possible (Value date earlier than capitalization date)

Hello , we are getting the error shown below. I'am not sure where to go to fix this can any offer any advice.
Thank you
Posting not possible (Value date earlier than capitalization date)
Message no. AA 322
Diagnosis
Asset 000000040048 0000 was first capitalized on 20080831.
You cannot post to an asset that was not yet capitalized.
Procedure
You have the following options:
Change the asset value date of your posting.
Capitalize the asset by posting an acquisition.

Generally this message will come , if you have created a asset with a capitalization date say 31/08/2008 and you are settling a Internal order for last period say 07 on with a posting date earlier than capitalization date , say 15/08/2008.
The System will not allow you to post because the value date cannot be earlier than capitalization date.
Change the value date to later than capitalization date and post.

ABNAN- Posting not possible (Asset does not manage postable areas)

Hi Experts,
I am trying to do a post capitalization creating a new asset using transaction ABNAN with the transaction type 400.
I get the Error " Posting not possible (Asset does not manage postable areas) "
Can some one help me with this.
Thanks in Advance
Vijayanth

Dear,
Check Asset master if it has depreciaiton areas activated.
Regards,
Chintan Joshi.

Payroll not possible because data is missing: WPBP: 01 SV: 00 ST: 00

Hi,
I have created a new org structure with a set of employee. I have maintained all the needed infotypes ( 0000,0001,0003,0007,0008..)
When i try to run payroll for those emp's, im getting the error message:
<u>Payroll not possible because data is missing: WPBP: 01 SV: 00 ST: 00</u> under rejected personal numbers.
What setting i have to do inorder to run payroll.
Rgds,
Ven.

Hello,
How absen quota 2006 is related to payrun..
However i have maintained all the said infotype, but still get the error .
Rgds,
Ven.
Message was edited by:
ven onk

SSO logon not possible; logon tickets not activated on the server

When I am on RWB
1) click "component monitoring" ->"display all"
2) click "CCMS"
I get a popup says:
"SSO logon not possible; logon tickets not activated on the server"
I find some threads about this on SDN but they are about
EP. My case is PI7.0SP08.
Please advise how to overcome this issue?
Thanks w/ points.
Message was edited by:
jennifer lee

hI,
do you have the follwoing in our SXMB_ADM if not add them.
SXMB_ADM->IntegrationEngine configuratin-> edit the speicifc configuratin then add the follwoing
Category:RUNTIME Parameters: logging Value:1
If its done. check this alos...whether your browser settings will accept the cookies or not. for SSO logon ticket method you need to have cookies accepted by our browser so check it. in internet page slect TOOLS ->internet options then ckeck for cookies settings.
How to Enable Single-Sign-On for XI 3.0 at:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/69d95112-0d01-0010-8297-fa31feea26e0
/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
http://help.sap.com/saphelp_nw2004s/helpdata/en/5c/b7d53ae8ab9248e10000000a114084/content.htm
regards
manoj kumar

UPC_F104 Entry not possible, var does not have replacement type user-spec.

Hi,
On of my exit variable keeps issuing me the following message when selecting a value:
UPC_F104 Entry not possible, var does not have replacement type user-spec. vals
This exit variable is based on other variables (non-user specific). The indicator 'Restriction of values required by user' is flagged.
Any idea what might be the issue ?
Thanks
David

David,
User exit variables won't work if there are multiple rows of values being derived incase 'Restriction of values required by user' is flagged.
Make sure that derivation of variable value is restricted to only one row.
if you have a need to derive multiple rows of values, simply uncheck the flag 'Restriction of values required by user' & you will be good to go.
hope it helps.

Error AU133 Account 'Contra account: Acquisition value' could not be found

I have this error when running RAPERB2000 program in IDES ECC6.0.
I have checked AO90 and this B/S account (199990) is maintain correctly in area 64 for the account determination.
This is the job log:-
02.12.2010 23:21:41 Errors occurred during the posting run (see the log)
02.12.2010 23:21:41 Company code AA01, depreciation area 64, fiscal year 2010, account group 30000
02.12.2010 23:21:41 Account 'Contra account: Acquisition value' could not be found for area 64
02.12.2010 23:21:41 Company code AA01, depreciation area 64, fiscal year 2010, account group 40000
02.12.2010 23:21:41 Account 'Contra account: Acquisition value' could not be found for area 64
02.12.2010 23:21:41 Company code AA01, depreciation area 64, fiscal year 2010, account group 30000
02.12.2010 23:21:41 Account 'Contra account: Acquisition value' could not be found for area 64
02.12.2010 23:21:41 Document INT-000026 was created successfully for Asset Accounting
02.12.2010 23:21:41 Company code AA01, depreciation area 99, fiscal year 2010, account group 20000
02.12.2010 23:21:41 Document INT-000027 was created successfully for Asset Accounting
02.12.2010 23:21:42 Errors occurred during the posting run (see the log)
Anyone has any idea why this error occur?

Hi,
Error AU133, is generally issued from some wrong or missing customizing. The text of the error message indicates in your case that a "Account 'Contra account'" and area 64 is concerned.
1) At first, please double check if in in AO90 (or table T095) the account is maintained for area 64. Do you have not defined a contra account for acquisition value postings in the Asset Accounting Customizing settings (Transaction AO90)?
Further, check in tr. OADB if you have defined "Different Depreciation Area XX". That means area 64 takes the account determination from area xx and perhaps there it is no account defined?
If this is not the reason:
2) Execute report RACKONT1 or transaction OAK4. Account determination should be set following the rules explained in SAP note 7595. Even if some account is not directly used, the account determination has to be completed. If output from RACKONT1 is not error free, it indicates that your customizing is wrong. You might correct it with the help of note 7595.
Furthermore:
3) You have defined the account in Asset Accounting, however, it is not created in the affected company code. Check whether the account is correct and create it for the company code, if necessary.
4) You have entered an asset reconciliation account for the "Contra account: Acquisition value posting" (for example, the same account as for the "Acquisition:Acquis. and production costs" account). This is not permitted.
5) As "Contra account: Acquisition value posting" you entered an asset G/L account. If necessary change the automatic posting indicator in the G/L account master record.
Regards Bernhard

CRMD_SHORTCUT modification is not possible when customizing not allowed cli

CRMD_SHORTCUT modification is not possible when the client closed to
customizing.
How can we change the AUDIENCE TYPE and the AUDIENCE KEY of a saved
search when the client is a productive and no changes allowed settings
has been made?

Hi, why don't you just make a navigation banner (bar) with the buttons they should be able to reach? Page group properties is where you decide the default navigation banner. So make a new banner for your users and set it as the default one.
Kristin

Deletion of Document templates not possible - 'Ok' 'Cancel' not displayed

Hello,
I want to delete a few Document templates. I use the business role 'SALESPRO', I go to 'Document Templates', choose a template, press the button 'Delete' (icon garbage bin) and a I get a pop-up window but without the buttons 'OK', 'Cancel' .
The pop-up is empty not even the title 'Confirm Deletion'.
Why's that ?
Any hints on how I could tackle this ?
I am deep in debugging but I do not seem to get anywhere, started from here:
Class CL_CRM_OI_T_TEMPLATELIST_IMPL
METHOD eh_ondeletetempl_btn.
DATA:
    lv_title TYPE string,
    lv_text TYPE string.
IF gr_confirm_popup IS NOT BOUND.
    lv_title = 'Confirm Deletion'(001).
    lv_text = 'Do you really want to delete?'(002).
    CALL METHOD comp_controller->window_manager->create_popup_2_confirm
      EXPORTING
        iv_title          = lv_title
        iv_text           = lv_text
        iv_btncombination = if_bsp_wd_window_manager=>co_btncomb_okcancel
*        IV_CUSTOMBUTTONS =
      RECEIVING
        rv_result         = gr_confirm_popup
    gr_confirm_popup->set_on_close_event( iv_event_name = 'CONFIRM_POPUP_CLOSED' iv_view = me )."#EC NOTEXT
ENDIF.
gr_confirm_popup->open( ).
Initially I thought that there is some oscure authorization needed but the authorization trace did not show anything.
Thank you
ENDMETHOD.

Prasenjit,
I was about to post the solution. I discovered that component but the code did not even go to DO_PREPARE_OUTPUT.
The solution was to 'Disable Cookies' (marked this checkbox in the technical profile associated with the business role).
I got the idea to try this after I came across a method get_server_cookie that could not read the cookie previously set by set_server_cookie (to this extent I came to debug .

Patching Sneak Preview Developer Studio not possible?? (Note: 668887)

Hi,
Due to problems with Adobe Document Services (I always get a java.net.SocketTimeoutException: Read timed out exception that I can't solve) I thought about patching from SP11 to SP13.
I work with the Sneak Preview edition. The SAP note 668887 says that you should not patch the SAP NDS (Preview).
Did anyone try anyway?
Kind regards,
Tobias
Message was edited by: Tobias Mack

Currently latest versions of NWDS SP13 and SP14 are available in http://service.sap.com just uninstall sneak preview sp11 and install freshly install SP13 or 14, instead of applying patches it saves your time.
Regards,
RK

Blue screen solutions not possible; keyboad commands not working

I am stuck in blue sceen limbo; can't go back to Tiger (wish I could), but can't run Leopard, either. The installation seemed to go smoothly, but all I get is a the blue screen and a sad little cursor with nothing to click. I looked up the official answer (article # 306857), but I am unable to restart in safe mode, as a target disk, or with the installation disk. The ONLY keyboard command that seems to work is the eject button to get the installation disk out. I am going to the "Genius" at my local Apple Store tomorrow, but I am already seething!

Welcome to Apple Discussions!
You may need an Apple wired keyboard (your Powerbook's built-in keyboard is one, if that's where you installed it) to go through the proper boot sequence.
In the future when applying an update, follow these directions, and you shouldn't have more problems*:
http://www.macmaps.com/upgradefaq.html
- * Links to my pages may give me compensation.
Message was edited by: a brody

Asset Acquisition with Asset Value Date earlier than GI post.date

Dear all,
I am curently using SAP ECC 6.0. We are not creating AuC assets but directly capitalizing assets from investment accounts.
If a material is issued with a date in March and i try to acquire it with asset value date from a previous period, for example in February, the system doesnt issue any message and lets me post the transaction. The accountants claim that this hadnt been possible in the earlier version of SAP 4.6 that we had been using and that the system had issued an error message - "Posting not possible (Value date earlier than capitalization date)"
The accounting logic is that you cant capitalize an asset with a date earlier than the date when it has been in use, i.e. in our case it`s the date the material has been issued from the warehouse.
Does someone know what logic does SAP follow in this case - and if i can set a validation control that will check and compare the two dates?
Any opinion would be appreciated
KR
Severina Koleva

We are on ECC 5.0 and we do get that message, but it is a warning.
AA348...
that said, you can setup a validation using GGB0 and asset accounting

Posting not possible - AA439

Dear all,
Iu2019m having trouble to correct the values of a Proportional accumulated ordinary depreciation.
The system returned the following message:
AA439 - Posting not possible (Asset does not manage postable areas):Check the transaction type and the asset.
I verified the postable area of the asset and is correct. The transaction type is also available for this movements.
Please anyone can give me some tips?
Where can I solve this problem?
Regards,
P.

Hi
I would like you to take into account the following information.
This error is normally shown when the sum of
Accumulated depreciation + ordinary dep. Py = 0
You can only write up if a depreciation of previous fiscal
years exists.
The system checks internally if there is a depreciation area left
where write ups can be posted, i.e. where the accumulated depreciation
+ ordinary dep. PY <> 0. If not, the system deletes the corresponding
depreciation area from its internal tables giving you the error.
Please check in this case note 50761.
Best Regards,
Blaz

Posting complete retirement not poss.with value date

Hello,
The error is coming as "Posting complete retirement not poss.with value date" when i am executing ABUMN. I am providing the asset value date same as the old assets Capitalisation date.The output comes as:
Diagnosis
Transactions have been posted to asset 900035 0 with an asset value date or posting date later than the retirement date 15.06.2009.
I have tried with later date but same result.
JK

Hello Paul,
I am not retiring the asset. I am just transferring the old asset class to a new asset class. Like: 100001 was created wrongly under 1020 class. Now we have created 500005 asset under 1040 class which is a correct class. Now I am transferring from 100001 to 500005 with the transaction code ABUMN. I am providing the same capitalisation date as of 100001 in asset value date in ABUMN.
Hope you understand.
JK

ABUMN-error "Posting transaction is not possible (Value date not allowed)"

Similar Messages

Maybe you are looking for