Wrong Assignment in AO90

Dear All,
By mistake we have assign Accumulated Deprecation account in Acquisition:Acquis. and production cost. in AO90 in balance sheet account. so because of that when we purchase any asset system post the entry in Acc Dep account insted of Asset account.
we have round about 10 entries in production server.
is there any solution to correct the above mistake as system will not allow to change the GL assigment and if i change it any how, then what to do with the balance which is posted in wrong GL.
Regards
Shayam

Hi,
You can raesolve this as per below....
1) Change the AO90 settings to expected GL account
2) Deactivate reconcililation settings in OAMK
3) Post the transfer entry from wrong GL account correct GL account thru FB01 (Enter parallel currencies value in respective field, if applicable
4) Activate reconciliation settings in OAMK
5) Check the sync in ABST2 report.
Best Regards,
Madhu

Similar Messages

Manual cheque wrongly assigned to payment doc.

Hi,
User wrongly assigned cheque number 111 to payment doc#15-1 via F-53, it should be assigned to doc#15-211.
Manual cheque 111 was already issued to vendor. How can i correct the assignment of cheque from payment doc# 15-1 to 15-211? Seems no way to edit it.
Please advise.
Eve

hi,
other wise 1 solution is their as per i know you have to cancel that cheque and document in fch8 give that voild reason and then you can go for new cheque ie., document will be reversed along with cheque and you can proceed with new cheque in manual ...
i hope this will solve your issue.
satishkumar.m

SLD - Solman wrong assignement in SMSY

Hello,
we add a new ERP 6.0 (Doublestack) System to SLD, but by starting the job LandscapeFetch the Solution Manager make a wrong assignement in transaktion SMSY.
The new ERP 6.0 System is now below the Netweaver JAVA Components and there is no Abap, but why?
I can´t find a solution, any help ?
thanks
Steven

Hi
Check the following notes - recommend to have latest LANDSCAPE_FETCH code
SV-SMG-SYS     1361991     2     39     SMSY: Incorrect database host names for Java systems
SV-SMG-SYS     1392489     1     52     SMSY: Übernahme eines Einzelsystems aus dem SLD
SV-SMG-SYS     1360590     3     36     SMSY: systems are created more than once
SV-SMG-SYS     1301106     11     49     SMSY: Enhancements and errors in Enhancement Package 1
SV-SMG-SYS     1319149     2     49     SMSY: Transferring the product information from SLD
SV-SMG-SYS     1376733     2     32     SMSY: Indicator NO_ABAP_INCLUDED cleared
SV-SMG-SYS     1303097     4     51     SMSY: Capitalized instance names from SLD
SV-SMG-SYS     1342337     1     38     Instances remain inactive
SV-SMG-SYS     1370396     1     37     JAVA installation number is not transferred from the SLD
SV-SMG-SYS     1350401     1     37     Incorrect leading product version set (data source SLD)
SV-SMG-SYS     1283307     24     33     SMSY: Product version cannot be determined correctly
SV-SMG-SYS     1335225     5     35     LANDSCAPE FETCH job: Termination with SCDT_LIS_IF 011
SV-SMG-SYS     1296512     4     39     SMSY: Product version transferred from deleted system
As mention before - pre-existing entries in SMSY with different data sources can cause problems - once a data source
has been decided upon creation you need to stick to it - or delete the system a re-create it via a different data source - deletion however can cause loss of existing customizing and inconsistencies if existing customizing has already been set up - changing data source after configuration has taken place is not recommended
Duplicates in SMSY or SLD can also mix import lines and target objects - both should be as consistent as possible before
a landscape fetch from SLD - you may even need to compare SLD with SMSY for any pre-existing entries
Best wishes
Stuart

Wrong assign messages in the collector logs

Hi,
Does anyone know what causes this type of errors to show up in the vCenterDC_Errors.log file for the embedded data collector?
2014-04-02T08:01:23.180-0400 ERROR [(32) HostsClustersAndVMTemplatesInventorySyncJob on VC 528] [propertyContent.PropertyContent] 7657: wrong assign : path=customValue[304], value=com.vmware.vim.CustomFieldStringValue@c6125d47
2014-04-02T08:04:12.968-0400 ERROR [(32) HostsClustersAndVMTemplatesInventorySyncJob on VC 528] [propertyContent.PropertyContent] 7445: wrong assign : path=customValue[304], value=com.vmware.vim.CustomFieldStringValue@64b6f789
2014-04-02T08:22:52.488-0400 ERROR [(32) HostsClustersAndVMTemplatesInventorySyncJob on VC 528] [propertyContent.PropertyContent] 6965: wrong assign : path=customValue[304], value=com.vmware.vim.CustomFieldStringValue@cae4c46a
2014-04-02T08:27:23.475-0400 ERROR [(32) HostsClustersAndVMTemplatesInventorySyncJob on VC 528] [propertyContent.PropertyContent] 7952: wrong assign : path=customValue[304], value=com.vmware.vim.CustomFieldStringValue@d33a1a8b
Cheers,
Milos

Hi Lakshmi,
I suspected as much, but it is great to have it confirmed.
We have been having some issues with the stats collection jobs failing and turning the status of the collector to down, so I was trying to wade through the voluminous logs and noticed these ERROR messages occurring regularly. One less thing to look into now
Thanks.
Cheers,
Milos

Employee group have been wrongly assigned during Hiring in PA40

Dear Guru,
I have one scenario where an employee; employee group have been wrongly assigned during Hiring PA40. The user has entered and assigned the employee group as Contract - Local instead of Contract - Foreigner in the Employee group field.
Please advice how to change and rectify this incident.
Thanks & Regards,
Wai Cheng - Yokota

Dear Guru,
Many thanks for all your advice.
I have use PA41 Transaction code to make the correction. However, I noted that the wrongly assigned Employee group remains unchanged in PA30 HR Master data.
Hence, I decided to use PA40 Hiring Action to make the correction by selecting Position/Band Change field. After save the correction in Copy Actions screen, it will lead you to Copy Organizational Assignment and save your entries. There will be a message appear at the bottom in regards to the position. Just click next arrow icon and click yes.
Go to PA30 HR Master data again, to verify that the correction and noted that it has change.
Regards,
Wai Cheng - Yokota

Wrong assignment of Balance sheet accounts for Asset Classes...

dear all,
there is wrongly assignment of acquisition balance sheet account in asset class in t code is AO85 that is, Acquisition:Acquis. and production costs an Accumulated Depreciation Balance sheet account have been assigned. Also in t code AO93 for ordinary depreciation same correct accumulated depreciation Balance sheet account have been assigned.
Now i can say that Acquisition balance sheet account and accumulated depreciation balance sheet account are assigned with same GL (i.e. accumulated depreciation account).
The transactions data have been posted for the asset class with different tcodes i.e.
ABAVN Enter asset transaction: Asset Retirement
OASV Enter Transfer Posting
AIBU AUC Settlement
ABUM Enter asset transaction: Transfer in company code
AB08 Documents from asset
I wanted to post transaction data with correct acquisition account. What should i do to correct posted transactions..
Waiting for positive response.
regards
saqib usman

The best way is to create a new asset class and to transfer the existing assets.
An other option is to change the G/l account in the development system and transport to production. In development it is only possible to this when there are no posting in this asset class. When there are posting you have the option to reset in development asset accounting. Then you can change the G/L account. Have a look to SAP-notes with your error there is a note for.
When the changes are in production you can make a manual correction with the transaction ABF1 (SAP note 69225).
With this option you have the problem that the original postings are no longer in line with the asset account assignment. When you want to do a currency conversion in the future you have to make correction posting again in the old fiscal year

IM Storage location has been wrongly assigned to a WH

Hello MM Sapperu2019s,
I have wrongly assigned one storage location which is relevant for IM to a WH.Now I need to deactivate the assignment which I have made in the below SPRO path,
SPRO-->Enterprise Structure >Assignment>Logistics Execution-->Assign warehouse number to plant/storage location
Please let me know what all the prerequestie / activity I need to take before I deactivate the assignment in the above path.
Awaiting for Your valuable replies.
Br
Kumar.S

Hello again,
Thnks for your valauble replies.I have checked the below tables in Prodution system and observed that there are no documents observed,
1.Checked any TRs available or not (LTBP Transfer requirement - item) - 0 (No Documents available)
2.Checked any TOs available or not (LTAP Transfer order - item ) - 0 (No documents availalbe)
3.Checked any Qunats available or not (LQUA Quants) - 0 (No documents availlable)
4.Checked any inventory data per quant available or not (LINV Inventory data per quant ) - 0 (No documents available)
So let me know the table details for PCN also.I can cross verify once in my production system.
Also please let me based on the above observation can i go head and deassign or deactivate the st location for the WH or not.
Please guide me with your valuable inputs.
Br
Kumar.S

Asset Under Construction- Wrong assigned for a Customer Project

Hello,
For a customer project, the AUC is created automatically which is not right.
We did analyisfrom our end.
1. It's a customer project
2. Investment profile is not assigned at the project profile level since it's a customer project.
3. we tried creating a project using the same profile in QAS environment,but the AUC is not created
So, could anybody help us in knowing what could have gone wrong, it will help us in our analysis.
Regards,
Nitin

Ok, the only way which I know where AUC gets created automatically for a WBSE is by assigning IM profile, but you say that your WBSE doesnt have IM profile. Check at the table level for the WBSE and see whether you can find the IM profile there or not. Also try to delete the AUC manually from asset transaction and see what message is getting issued.
What is your version of SAP? Also check the change documents, if you have activated, if someone has entered IM profile and later deleted, I can see some OSS notes for which AUC is not deleted even after removing IM profile from WBSE for versions like 4.6.

Cost centre group wrongly assigned to standard hierrachy

Hi Gurus,
Can any one tell me how I can remove a cost centre group assigned wrongly to a cost centre stnadard hierrachy. I also have a cost centre defined under that cist centre group.
Please help.

HI,
T-Code OKEON: reassign the cost center from this special cost center group to another standard hierarchy node. If your group does not contain cost centers anymore, you can delete it from the hierarchy.
best regards, Christian

Info record wrongly assigned to PO

Hi,
We have some inforecords assigned to som PO's this has happend because the user EVO setting is incorrect is there way to remove these assigned PO's instead of deleting them.
Thanks,
Suresh

One option is to put deletion indicator to the existing line items and create a New line Items with correct inforecord..
So that the PO number will not be changed..

Wrong assignment of user

Hi Folks,
Initially we assigned the user to the purchase organization and purchase orders created by him.Later business raised an issue saying that Assign me tab is not working for that particular user in Sourcing cockpit.As we analysed the Assign me and action tab in the sourcing cockpit is highlighted when the user is assigned to the purchase group only in org structure.
So now we thought of assigning that user to the purchasing group.Will we get any inconsistencies if we assign the user to the purchasing group now.Because already some of the documents already created with that Porg assignment.Please share your views in order to solve our issue
Thank you,
chakradhar.

Hi Chakri,
Gud to see you at SDN,
No inconsistency will be find for existing documents for that buyer, if you only assign that buyer to P.group which is beneath of same P.org.
Use drag and drop functionality via PPOMA_BBP
Many Thanks,
Venkat

Wrong assignment field (ZUORN) using transaction MR08

Hi all,
On SAP R/3 4.6b we run transaction MR01 with unplanned delivery costs. As we have some price differences, the FI document has a line with the right price diff. G/L account. This G/L account has its sort key field (ZUAWA) filled with code '013' (Material Number), so the assignment field (BSEG-ZUONR) of this price differences item on the FI document, is filled with the corresponding material number (BSEG-MATNR).
The oustanding point is, when we cancel this document using MR08 this assignment field is filled with the SAP standard sort key code '014' (P.O number + P.O item // BSEG-EBELN+BSEG-EBELP). This is the sort key belonging to the GR/IR G/L account of the FI document. Thus, we have a credit note with a different text on assignment field than the original invoce (only for the price diff. acount line) !!!
We have check taht this not occurs if the invoice have not any unplanned delivery costs.
We do not use either substitutions or user-exits for feeding the assignment field.
Could you please give me a hint?
Regards.

Hello Larry,
if it is a transport issue you may find further information about how to transport screen variants in the system.
transaction SHD0
i-icon for online documentation opens a page where you get further information on how to transport screen variants.
How that this may help.
Regards, Franz

Wrong assignment field (ZUORN) running MR08

Hi all,
On SAP R/3 4.6b we run transaction MR01 with unplanned delivery costs. As we have some price differences, the FI document has a line with the right price diff. G/L account. This G/L account has its sort key field (ZUAWA) filled with code '013' (Material Number), so the assignment field (BSEG-ZUONR) of this price differences item on the FI document, is filled with the corresponding material number (BSEG-MATNR).
The oustanding point is, when we cancel this document using MR08 this assignment field is filled with the SAP standard sort key code '014' (P.O number + P.O item // BSEG-EBELN+BSEG-EBELP). This is the sort key belonging to the GR/IR G/L account of the FI document. Thus, we have a credit note with a different text on assignment field than the original invoce (only for the price diff. acount line) !!!
We have check taht this not occurs if the invoice have not any unplanned delivery costs.
We do not use either substitutions or user-exits for feeding the assignment field.
Could you please give me a hint?
Regards.

I do not think you can reverse this. Once "Reference" is updated it cannot be changed, unlike line items "Assignment"
If you want to hide, the only option is to copy this program and make changes accordingly.
As far as defaulting "Assignment" is concerned, you better create a selection variant. Ask the user to select this variant at the time of execution.

Wrong assignment of plant to asset

Dear Expert
During the asset creation we assigned the plant no 1296 but the actual required was 1210 user changed after certain time and faced a problem of difference in amount.
Is there any way to sort out the problem.
Thanks - VG

solved by self effort

Fix Wrongly Assigned Device to a Device Category via EG44

Hi,
I wrongly Created a Device in a Device Category Axxx via EG44. This Device already exists in another Device Category Bxxx. I don't see an option to delete the Device from the Device Category Axxx. Does anybody know how to do this?
Thank you!
NR

That is very interesting. Did you try going to the tables EQUI, EGERS, V_EGER to see which tables has this device and which don't?
H_EGER is the search help for device in EL31. May be something is wrong with the refresh of that?
So just to retrace your steps, you created a device nnn in device category AXXX. Then realized there exists nnn in another device category BXXX?
I hope you are not using equipment number (EQUNR which is internal) instead of the combination of device category(MATNR) and serial number(GERAET).
It is against the rules of database management that a device exists in one table and doesn't in another and so the same goes with transactions that access the device.
Did anyone try to delete it from tables directly?

Wrong Assignment in AO90

Similar Messages

Maybe you are looking for