Posting not possible (Posting yr.earlier than capitalization yr.)

Hi gurus
while posting write up through ABZU ; I am getting an error message that posting year is earlier than Capitalization year Message No: AA328.
When i checked the group asset first acqusition on date was in future.
I donot know how it was happen.
Please give suggestion to solve this issue .
Thanks & Regards
Binoj M D

hi
Got the solution. Screen layout changed.
for that group asset and now it is working fine.

Similar Messages

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.

NTLM Authentication : why is it not possible to create more than one NTLM realm ?

Hello,
I'm wondering why it is not possible to create more than one NTLM realm on a wsa.
Can you explain exactly what is the blocking point ?
Thanks in advance
Regards

Well, at this point (pre 7.5), there isn't an agent, the WSA is joined to the domain, just like a Windows box, it authenticates via that trust relationship. From that point it is all based on how NT/Active Directory domains work. As long as there is a trust between the domains, you can can auth users from as many domains as you like.
There is an agent in the works. The ADAgent will be released with 7.5. The code is already available, it was released with the ASA ver 8.4, and it will be used to pass authentication info to the WSA. At this point, current versions still require trust relationships between all of the domains touched.
Taken from the setup guide: http://www.cisco.com/en/US/docs/security/ibf/setup_guide/ibf10_install.html#wp1054011
Before you configure even a single domain controller machine using the
adacfg dc create
command, ensure that the AD Agent machine is first joined to a domain (for example, domain
J
) that has a trust relationship with each and every domain (for example, domain
D[i]
) that it will monitor for user authentications (through the domain controller machines that you will be configuring on the AD Agent machine).
Depending on your Active Directory domain structure, the following scenarios are possible:
1. Single Forest, Single Domain—There is only one domain, D[i] for all domain controller machines, which is one and the same as domain J. The AD Agent machine must first be joined to this single domain, and since no other domains are involved, there is no need to configure any trust relationship with any other domain.
2. Single Forest, Multiple Domains—All the domains in a single forest already have an inherent two-way trust relationship with each other. Thus, the AD Agent must first be joined to one of the domains, J, in this forest, with this domain J not necessarily being identical to any of the domains D[i] corresponding to the domain controller machines. Because of the inherent trust relationship between domain J and each of the domains D[i], there is no need to explicitly configure any trust relationships.
3. Multiple Forests, Multiple Domains—It is possible that domain J might belong to a forest that is different than the forest to which one or more of the domains D[i] corresponding to the domain controller machines belong. In this case, you must explicitly ensure that each of the domains D[i] has an effective trust relationship with domain J, in at least one of the following two ways:
a. A two-way external trust relationship can be established between the two domains, D[i] and J
b. A two-way forest trust relationship can be established between the the forest corresponding to domain D[i] and the forest corresponding to domain J

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

TS1702 The Calendar app that came on my i4S Phone does not sync the correct time for items posted on my Yahoo Calendar. Actually, they post exactly 4 hours earlier than the correct time on my Yahoo Calendar. Does anyone have a "fix" to correct the "time

The Calendar app that came on my i4S Phone does not sync the correct time for items posted on my Yahoo Calendar. Actually, items post exactly 4 hours earlier than the correct time on my Yahoo Calendar. My i4S is in the correct New York time zone. Help?

I posted this question a while ago and didn't receive any responses but there are a lot of people who have viewed it and 10 have said they have the same question so I thought I would update you that I added my nanny to my exchange server account (created an email for her) and I send all invites to that email address and they work. So sending invites from an exchange server account to a non-exchange server account apparently is a bug so to solve it, get on an exchange server I guess.

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.

Error posting with trans.type 159 not possible (no aquisition posted)

Hello All,
A user has created an PO for asset with GR non valuated in 2007 and has performed a MIGO/GR in the same year 2007. Now in 2008 the user has received an invoice against the said asset and wants to post it thru Trans MIRO.
At the time of posting the invoice the user gets the error "posting with trans.type 159 not possible (no aquisition posted)" . Since this is a completely new asset and GR non valuated asset process is a standard in SAP why is the system recognising the transation type as 159 i/o trans type 100 ie new asset aquisition.
If i post a dummy value to the same asset using FB01 the system accepts the value but the same process if i intend to follow usin MIRO system does not allow.
Can you guys help me
Thanks
Nelson

Thanks Paul for your reply, I checked the depreciation key. inthe key the "Aqu only allowed in capitalization year is marked as NO"
Therefore the problem is not the depreciation key
Thanks
Nelson

ABUMN: Posting with trans.type 300 not possible (No acquisition posted)

Hello everyone,
I have seen a few threads on this topic, however I am still not finding a resolution to my issue. I am very new to the FICO configuration scene and probably need a little more hand holding than the others who have asked this question.
I am having and issue using ABUMN while transfering a Capital Investment Project (CIP Asset) under a asset class of AUC, to a standard fixed asset. The CIP has been capitalized. However, when I try to perform the transfer I am receiving the following error:
Posting with trans.type 300 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 300 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
I have read through SAP NOTE 327088 (for retirements transfer variant 4) and it just doesn't help me with the issue. I know it probably should, but I do not know enough about this process in order for it to make a whole lot of sense.
If anyone can help me with this, it would be greatly appreciated. Again, I am very new, so I will probably have several follow-up questions as well.
Thanks in advance for the help!
Rhonda

Okay...
I have finally figured this out on my own.
When trying to transfer a capital investment project asset with an AuC class (asset under construction), ABUMN is not to be used.
1st. The internal order needs to be fully settled (KO02). Create a settlement rule "FUL" for the designated fixed asset.
2nd. Run "Actual Settlement" run via KO88.
This should transfer everything from the CIP asset to the fixed asset. You can double check this via the S_ALR_87011967 - ... by Plant report. Run this report prior to performing the steps above and the money will show in the CIP asset account, run it again after the above steps. The CIP should be zeroed out and the fixed asset should now carry the amount.

Posting with trans.type 645 not possible (No acquisition posted) Message no. AA324

Hello,
I have post the depreciation of asset, which is legacy asset & value arise through AS93.
Now i realized that the i have charged more depreciation. hence While doing Debit manual depreciation of Asset through T code ABAA & using transaction type 645, system showing error message,"Posting with trans.type 645 not possible (No acquisition posted) Message no. AA324".
Please help us to resolved this issue or any other way to write off the depreciation which is excess charged earlier for legacy asset.
Thanks & regards,
Pramod

Hi,
According to me you can create a new transaction type which is exact opposite to depreciation key 640 and then with that transaction type you would be able to post the unplanned depreciation by which the asset value will increase.
Regards,
Malhar.

Posting with trans.type 300 not possible (No acquisition posted)

Dear Gurus,
When I execute the T-code ABUMN, i've got the following message:
Posting with trans.type 300 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 300 belongs to a transaction type group, which can only
be used to post to assets to which posting has already been performed.
However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used
for the first acquisition to an asset.
Regards

Hi sapraj ,
Transaction type 300 is "transfer of retire. old assets data from cap. asset" ,which means before you transfer this asset, it has to be first capitalized , for asset capitalization, you may use transaction type 100
Mu

Posting with transaction type 160 is not possible at MR8M

MODERATOR: Do not post (or request) email address or links to copyrighted or confidential information on these forums. If you do, the thread will be LOCKED and all points UNASSIGNED. If you have some information, please consider posting it to the [Wiki|https://wiki.sdn.sap.com/wiki/display/ERPFI/Home] rather than sharing via email. Thank you for your assistance.
Hi All,
We raised a PO w.r.t CWIP asset and posted GRN (MIGO - Transaction typr:100) and Invoice (MIRO).
Here, Invoice posted wrongly, So we are trying to reverse the invoice with MR8M (which is posted thru MIRO).
But system populating one message as per the following:
Posting with transaction type 160 is not possible here, see long text
Message no. AAPO 177
Diagnosis:
Transaction type 160 has a depreciation limitation, although posting is not mandatory in all of the depreciation areas entered However, it is not possible to select depreciation areas in the current transactions.
Procedure:
Check the specification of transaction type 160 or use transaction MR8M to enter the transaction
Please help
Sairavi
kumarfi9gmailcom

Welcome to the forum.
As a newbie you should understand the forum rules where you are not suppose to post any basic or repeated question. To avoid this, you should make a search here
[Forum Search|http://forums.sdn.sap.com/search!default.jspa?objID=f327]
Type the same error text in Search Terms so that you will find the solution.
thanks
G. Lakshmipathi

Posting date/period 31.12.2014/009 is earlier than existing date/period 17.01.2015/010

Hi Experts
While posting of invoice document (T.Code MIRO) I got the below error message;
Posting date/period 31.12.2014/009 is earlier than existing date/period 17.01.2015/010
Message no. FI_E050
Diagnosis
Commitment postings to Funds Management require that the current transaction's posting date is earlier than the posting date of the original or change account assignment line item of the document.
I have checked several threads still i am not able to get answer -Invoice posting Error
Regards
Sp

Suraj,
please check following note
564439 - FM update date is earlier than an existing postings
Regards

Why can't I post my resume from Pages to the web or an email on my iPad?? I've tried using iCab, downloading google docs, etc. I understand it's not possible from iPad but why???

Why can't I post my resume from Pages to the web or an email on my iPad?? I've tried using iCab, downloading google docs, etc. I understand it's not possible from iPad but why??? If I can't use safari to do it is there any other way?? Seriously, are iPads only used for watching Hulu, playing games, fb and twitter? My phone can do that!! Worst $500 I ever spent.

We don't want to email it..... we want to upload it.
Then why did you say (emphasis added):
Why can't I post my resume from Pages to the web or an email on my iPad??
There are plenty of methods for putting a resume online, where a potential employer can download it, though admittedly the iPad is less flexible in this regard than a computer. Nobody ever has claimed otherwise. However, I get the feeling you're not actually looking for an answer to anything, and you're just posting to complain. Note that that is a violation of the Apple Support Communities Terms of Use, which you agreed to when signing up for an account here.
I wish I had gotten a Galaxy Tab.
Then sell your iPad and go buy one. You will have no problems whatsoever finding a buyer.

Transaction type 100 not possible (posting to affiliated company)

Hi All SAP Guru's
I am trying to post asset acquisition through F-90
Asset Dr Transcation Type 100
To, Vendor Cr
while saving the above document i am getting an error Transcation type 100 is not possible (Posting to Affiliated Company)
to explain further my client are using Trading Partner Concept, may be that is the reason document is not getting posted
In Transcation Type I tried to change Post to affiliated Company then system allowing to post the document, but in real sense we should not give post to affiliated company at Transcation Type
can anybody help, is there any alternative to go ahead
Regards
Sreenivasulu
Edited by: sreenivasulu VAS on Feb 26, 2009 1:57 PM

Hi,
When there's a trading partner in the document, you need to use a different transaction type for external acquisition.
Have you tried this? (I've used this one. without chaging document type setting)
150 Acquisition from an affiliated company
Difference from Transaction type 100 is posting type. 150 has a posting type of 'Post to affiliated company' whereas 100 has not.
Check with IMG (T-code: AO73)
Heeseon.

Transaction type ZGC not possible (posting to affiliated company) in ABSO

Hi all,
We have depreciation areas 01, 30, 31, 32 .
dep area 30, 31, 32 inherits the values from 01.
We want to post credit value to dep area 01 after doing the aqusition .
Hence we created a seperate transaction type ZGC ( in aqusitions- Tcode AO73) and limited it to dep areas 01, 30, 31, 32.
Transaction type ZGC is having credit and " do not post to affliated company " radio button is selected.
Now the issue is when we run ABSO to do a credit post in dep area 01 we are getting the below error .
Transaction type ZGC not possible (posting to affiliated company)
Message no. AA390
Diagnosis
For the current document, you specified either implicitly (via the customer/vendor), or explicitly (with a manual entry), that this posting is to an affiliated company. In this case, Asset Accounting requires you to use special transaction types. This enables the system to separately identify such transactions.
Procedure
Check the line items that you have already entered, and the transaction type you entered.
Not sure why it is asking for affliated company .
It will be great if any one help on this why we are getting this issue.

Hi Daya,
Please try to choose Trans.Type 100 in AO73 transaction code and select the radio button Post to affiliated company under Posting type.
Thanks,
Kumar

Posting not possible (Posting yr.earlier than capitalization yr.)

Similar Messages

Maybe you are looking for