Start date mismatching

Dear all,
When we create organizational unit the system should take the date of companies incoporation , when I create jobs or position for that Org unit then the orgnization unit, jobs, positions date is automatically taking different date only for few objects.
Pls do let me know the solution for the same.
Thank u
Regards
Srilatha

Thanks Kumar,
See its like, When ever Im creating the Org Unit, all the sub org units, Depts, Jobs & Positions should go with the same date.
(i.e the companies incorporation date). But while im configuring the objects,(o) & positions(s). few of them are taking the hapazard dates which are not coinsiding with the Root Org unit date.
Hope Im clear know.
Regards
Srilatha

Similar Messages

Data mismatch

Hi all,
My project manager shown screen shot like data mismatch from r/3 side and bw report, Now i have to analysis where it is
strucked give me steps to follow find that error, you guys surely have idea where and all possible to get stuck please give yr
suggestion, then i can easy find that problem.
thanks & regards,
R. Saravanan

Hi Saravanan,
Goto R3 side--> RSA3 Transaction > Enter the DS name> Give some restriction w.r.t some Characteristics --> Extract the data
Come to BW side> RSA1 trans> you can start checking with the either Infocube content/ MP contents> right click> Display data> Give the same restrictions as you gave in the R3 RSA3 trans> Execute
Compare the field values whether you are getting the same data or not.
if the data is matching here, then there might be some filtering in the Query--> check that filtering & check the data accordingly
If it is not matching at Cube/MP level--> Then compare the data at PSA level before which check all the Routines/Update rules/ Transformations because there is a possibility that the data might be filtered in any of these levels.
Hope it helps!
Regards,
Pavan

Integration with Outlook - how to increment end date and time from start date/time

Hi,
I want to add a variable amount of time to an appointment start date and time in outlook, through vba in access. Code below shows what I've done:
======================================
Dim olApp As New Outlook.Application
Dim olAppointment As AppointmentItem
Dim myRequiredAttendee As Outlook.Recipient
Set olAppointment = olApp.CreateItem(olAppointmentItem)
With olAppointment
.Start = DateValue(strStartDate) + TimeValue(strStartTime)
.Duration = intDuration
.End = DateValue(strStartDate) + ????????
=======================================
What do I replace the ????? with so that it increments the start time by any duration I decide in minutes? Using the duration doesn't seem to work and I also want to be able to have the appointment span a number of days, e.g. could start at 930am on
Monday and end at 10am on Weds, but want to set the end time relative to the start time.
Thanks,
Chris.
_________________________________________________________ Every day is a school day!

I've tried that, but it throws out a datatype mismatch error :(
It would be helpful if you posted the exact code you tried. In my tests, setting teh .Duration property appears to work. However, if you want to set the .End property to a specific number of minutes after the date/time of the .Start property,
this works for me:
With olAppointment
.start = DateValue(strStartDate) + TimeValue(strStartTime)
.End = .start + TimeSerial(0, intDuration, 0)
End With
Assuming, that is, that intDuration contains the number of minutes the appointment should last.
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

How to Update employee Effective Start Date

Guys
i am getting error while making terminate of an employee the error is being occurred as "the Person Must Exist as an Employee at the Time Specified by date start". after lot of finding, Ii came to know that the problem is being occur due to mismatch effective start date & original date of hire. so i need to update effective start date instead of Date Start(Hire date).Can you tell any one, Which api need to use update for this issue,
Kindly help me.

There is no API to update effective Start Date column.
Your case falls into the type of data corruption in application tables. You either need to correct the data by yourself or take the help of Oracle support to correct the person data.
If you decide to correct the data without taking help from Oracle support, you can always take help of these forums in doing the same. we will be more than happy to help you. :)

Data Mismatch problem in Production system

Dear Experts,
We have been encountering serious data mismatch problems with our source system since 29th Dec 2010.
We have realized this mismatch only on 11th Jan 2011. So, we have deleted entire data from 29th Dec 2010 onwards to 11th Jan 2011. Then we tried to load delta again as per our Process Chain sequence. Since then, our production system has become very inconsistent. We found that the entire data from 29th Dec 2010 to till date is started giving mismatch.
Our system got damaged in terms of data drastically. If I delete any bad requests from our Cubes & Data Store Objects, the next time when we try to load data, cube & Data Store Objects is showing the deleted request no. is not updated properly. Because of this, our Process chain is daily failing to complete and giving so many technical errors. We are totally confused to restore our data from 29th Dec 2010 to till date.
Can any one please help us to restore our data fully and Process Chain to run successfully...............?
Thanks in Advance,
Suman

Hi Suman,
I understood that you are using 3.x version of BW
such kind of issues occurs if you distrub the delta sequence by deleting the requests without making them red.
you can resolve this two ways......
1) Go to reconstruction tab of the DSO and CUBE, select all the req from 29th Dec 2010 thru 11th Jan 2011 and reconstruct them. once they appear in the request tab. make all the requests to red (set the QM status to RED) one by one and delete them from the CUBE and DSO.
This should set the delta status back to 29th and you will be able to run a repeat delta from then in your next delta.
2) Go to RSRQ and give the SID or the Request ID one by one that it is giving you ( request no. which is not updated properly)
Mke the QM status as RED for all of them.
Since you have already deleted them from the targets, just changing the QM status to RED will be sufficinet.
You have make the QM status to RED inorder to inform the system that the requset is incorrect one and has been deleted.
Once it is set to RED, system will not prompt any req and say "request no.# not updated properly".
i suggest you the second option.
Once you resume the delta load, it should run successfully.....and if you feel some data is still missing from 29th Dec 2010 thru 11th Jan 2011, just run a full repair load the get the data back.
If your Datasource is of LO extraction u may need to fill the setup tables to perform full repair.
Please let me know if the Datasource is of LO extraction. Also let me know once the issue is resolved.
Regards,
Sudheer.
Edited by: Sudheer Kumar Kurra on Jan 22, 2011 7:58 AM
Edited by: Sudheer Kumar Kurra on Jan 22, 2011 8:03 AM

Position 1000001 not available for the start date of the infotype record

Dear Experts/Gurus,
I am getting the following error message "Position 1000001 not available for the start date of the infotype record" while trying to upload employees HR Master data in PA40.
I know the reason why because the position is created on 01.05.2009 & employee DOJ is 01.02.2006 both are mismatch & the position date has to be changed earlier date than DOJ but i don't know how to do.
Please let me know how to sort out this issue asap.
Rgds,
Vikrant

Dear Friend,
Use PP02, select the position no, select infotype 1000 (Object), select planning status & validity(date) and then use the copy function to change the start date.
Regards,
Aks

Restriction of Validity start date in Scheduling agreement

Hi,
I am not able to convert the message 06 170( Start of validity period is in the past) in error message , when i am going to define attributes of system messages in purchasing and converting this message into error , system still does not give error message when i am selecting back validity start date in the header of Scheduling agreement (me32l)
What can be the possible reason.
Regards
Sachin

Hi,
I believe the message 06-170 is hard-coded in Include "MM06EFRP_EKKO-KDATE" in the Program SAPMM06E
Laufzeitbeginn in der Vergangenheit -
    IF ekko-kdatb < sy-datlo.
      MESSAGE w170 INTO gl_dummy.
      mmpur_message 'W' '06' '170' '' '' '' ''.
Please consul your ABAP Team on this to change it to Error.
But SAP does not recommend changing standard Programs, so please discuss this and see that its really required and will not have any effects to your business process, because there may be instances wherein you might require to create scheduling agreements with a past validity date sometime in future based on business requirement.
Regards
Chandra Shekhar

Data Mismatching in DSO

Hi Folks,
We have data mismatch issue for one info object ( BASE UOM ) when the data goes from staging DSO to conformance DSO.I will explain the issue here.
For one invoice no the Base UOM value dispayed as M2 in the staging DSO.When the data goes from staging DSO to conformance DSO,in the conformance DSO the Base UOM dispayed as Blank value.There is no code written for calculation of Base UOM in transformation level.This is direct a mapping to field Base UOM in the conformance DSO from staging DSO.For all other invoices the Base UOM value dispalyed correctly in conformance DSO when compare to staging DSO. For one specific invoice the base UOM value showing as blank in the conformance DSO.
Could you please give me your suugestions what the reasons for showing base UOM value showing as a blank value in Conformance DSO.
Thaks for your advance.
Regards,
Nag

Hi,
You will have to check following things,
1) Check if other records with base unit value as M2 are updated properly in conformance DSO. This will make sure that there is no issue with this particular base unit.
2) As you have mentioned other records are successfully getting updated, you might have to debug the data load for this particular record. Do the selective data loading and check, where the unit is getting cleared.
You can also check if there is any conversion routine at the infoobject level.
Regards,
Durgesh.

Delta load from ODS to cube failed - Data mismatch

Hi all
We have a scenario where the data flow is like
R/3 table - >dataSrc -- > pSA - >InfoSrc -> ODS ->Cube.
The cube has an additional field called "monthly version"
and since it is a history cube , it is supposed to hold data
snapshots of the all data in current cube for each month .
We are facing the problem that the Data for the current month
is there in the history ODS but not in the cube . In the ODS ->Manage->requests
tab i can see only 1 red request that too with 0 recs.
However ,In the cube -> manage-> reconstruction tab , i can see 2 Red request
with the current month date. Could these red requests be the reason for
data mismatch in ODS and cube .
Please guide as to how can i solve this problem .
thanks all
annie

Hi
Thanks for the reply.
Load to Cube is Delta and goes daily .
Load to ODS is a full on daily basis .
Can you help me how to sort this issue . I have to work directly in production env . so has to be safe and full proof .
Thanks
annie

Change in start date of tax depreciation not for posting in mid of year

Hi Experts,
Tax depreciation area is not for posting. The fiscal year is from Jan to Dec. I want to calculate tax depreciation from May 2011 based on Net Book Value of tax depreciation as on 30.04.2011. But once I change the start date of tax depreciation in asset master to 01.05.2011, the system ignores the previous depreciation so I am not getting the NBV of tax depreciation of 30.04.2011.
Is any setting is required to get this. I can not do changes in posting rules since this tax depreciation is not for posting any thing.
The fiscal year 2010 is closed and NBV of tax depreciation as on 31.12.2010 of one asset is 80000, If I change the start date of tax depreciation from 1.1.2011 then system correcly take NBV of 31.12.2010 for further depreciation calculation. But if i change the start date of depreciation in between of year the system is calculating depreciation based on NBV of 31.12.2010 but ignores the tax depreciation from 1.1.2011 to 30.04.2011, which I previously run using AFAB.
Need your assistance to know is it feasible to do this.
Thanks and Regards,
Harshad

Hi Harshad
The behaviour of the system is very much correct, it is designed to behave that way...
One, you should not have changed the dep start date....
two, NBV in SAP is always taken to be NBV @ the start of the year....
The best wayout I can suggest here is, if you are on EhP4 and EA-FIN active
a. Change the Dep Key in the asset... You can maintain Time Dependant Dep Terms in asset master i.e. Dep Key X from Jan-Apr and Dep Key Y from MAy onwards
b. This will however, calculate dep based on NBV at the start of the year, but based on new useful life
c. Considering your eg: The system is posting more depreciation i.e. 5333 instead of 5155.... So, calculate this amount outside the system and post a Manual Write up ABZU inorder to reduce the Dep and increase the NBV
Even if you are on not on EhP4, you can follow the same approach as above.... i.e.
a. Change the Dep Key in asset master.... This will throw up new dep figure, on the basis of New Useful life and NBV at the start of the year
b. Post a write up from ABZU....
No need to do Asset to asset transfer in my opinion
Only diff between EhP4 and Non EhP4 is that the differential depreciation would be lesser if you are on EhP4... i.e. instead of 5333 now, system may throw up depreciation amount of 5666.. So, you may need to post write up of 5666-5155
br, Ajay M

Change in start date of tax depreciation in mid of year

Hi Experts,
Tax depreciation area is not for posting. The fiscal year is from Jan to Dec. I want to calculate tax depreciation from May 2011 based on Net Book Value of tax depreciation as on 30.04.2011. But once I change the start date of tax depreciation in asset master to 01.05.2011, the system ignores the previous depreciation so I am not getting the NBV of tax depreciation of 30.04.2011.
Is any setting is required to get this. I can not do changes in posting rules since this tax depreciation is not for posting any thing.
The fiscal year 2010 is closed and NBV of tax depreciation as on 31.12.2010 of one asset is 80000, If I change the start date of tax depreciation from 1.1.2011 then system correcly take NBV of 31.12.2010 for further depreciation calculation. But if i change the start date of depreciation in between of year the system is calculating depreciation based on NBV of 31.12.2010 but ignores the tax depreciation from 1.1.2011 to 30.04.2011, which I previously run using AFAB.
Need your assistance to know is it feasible to do this.
Thanks and Regards,
Harshad

Hi Harshad
The behaviour of the system is very much correct, it is designed to behave that way...
One, you should not have changed the dep start date....
two, NBV in SAP is always taken to be NBV @ the start of the year....
The best wayout I can suggest here is, if you are on EhP4 and EA-FIN active
a. Change the Dep Key in the asset... You can maintain Time Dependant Dep Terms in asset master i.e. Dep Key X from Jan-Apr and Dep Key Y from MAy onwards
b. This will however, calculate dep based on NBV at the start of the year, but based on new useful life
c. Considering your eg: The system is posting more depreciation i.e. 5333 instead of 5155.... So, calculate this amount outside the system and post a Manual Write up ABZU inorder to reduce the Dep and increase the NBV
Even if you are on not on EhP4, you can follow the same approach as above.... i.e.
a. Change the Dep Key in asset master.... This will throw up new dep figure, on the basis of New Useful life and NBV at the start of the year
b. Post a write up from ABZU....
No need to do Asset to asset transfer in my opinion
Only diff between EhP4 and Non EhP4 is that the differential depreciation would be lesser if you are on EhP4... i.e. instead of 5333 now, system may throw up depreciation amount of 5666.. So, you may need to post write up of 5666-5155
br, Ajay M

Issue on Ordinary Depreciation Start Date and Disposal of Asset

Hi All.
I am facing the following the issues.
Fiscal Year is from July - June
First Problem: Company acquired the asset Vehicle on 26.Dec.2008. System proposes Ordinary Depreciation Start Date as 01.Jan.2009 rather then proposing Ordinary Depreciation Start Date as 01.Dec.2008.
Since depreciation for previous year has been posted the client later found out that instead of calculating depreciation for 7 months depreciation was only calculated for 6 months. I tried to manually change the dep. start date but the system doesnot update the previous years values, it's still calculating depreciation for 6 months and not 7 months. Is there anyway in updating the previous fiscal years depreciation values.
2nd Problem: I created a test case scenario today i.e. 16.09.2009 by creating and capitalizing an asset vehicle. Once I capitalized the asset the system automatically proposed the start date as 01.10.2009 and not 01.09.2009 which is what i require. What setting do i need to check or maintain in order to solve this issue because the user does not want to manually change the date each time an asset is created.
3rd Problem: Similar to this now when client disposes of an asset suppose on 10.Feb.2009 (FY2009). The system calculates depreciation till the month in which disposal takes place (February), the client does not want this, their requirement is that depreciation should be calculated one month before disposal takes place i.e. in this case Dep should be calculated till Month of January.
Your assistance will be highly appreciated.
Mohammed Ali Khan.

Hello Khan,
The depreciation start date will get determined based on the period control method assigned to depreciation key,
Period control methods are defined in transaction code : OAVH
In period control method we will mention the depreciation start date for acquisition, additions and also depreciation end date for disposals, retirements.
SAP has given some default period control keys. If any of these are not suitable to your requirement you can create on your own period control methods.
THanks
Sai

Issue with Ord Start Date

Hi,
I am having issue with Ord Start Date.
When i create XYZ Asset now when i do the acquasation for that new asset. Example: Using FB01 i enter todays date and i do the posting.
Now when i go to DEP Area TAB for the DEP Key (M200) - The Ord Dep Start Date is 15 Dec 2010.
For this DEP Key Period Control Methods (T code - AFAMP) - Acquisation Entered is ( 6 that is - at the start of year) and the Period Control is ( T code - OAVS) (4 that is - First year convention at half year start date).
Our client is using the fiscal year as 1 June 2010 to 31 May 2011.
So when i do acquistion for the asset as per the period contol the Ord Dep Start Date should be 1 Dec 2010, but here it is talking 15 Dec 2010.
Why is system talking 15 days more.
Regards.

Hi
Which Fiscal year variant are you using??
Did you maintain it in OAVH? Copy the existing entry in OAVH for K4 to your Fisc Yr var and try again
And also, 04 does not figure for Acquisitions in AFAMP under 0004.... Whatever you specify in OAVH must also be a part of AFAMP
Regards
Ajay M
Edited by: Ajay Maheshwari on Oct 28, 2010 2:31 PM

Start Date for AP trial balance report

Hello
Am working on generating the Trial balance report in the Payables. I am running the "Accounts Payables Trial Balance report. For this report, in the parameters, there is "As of Date" parameter, but I do not have the "Start Date" parameter. I wanted to get a trial balance report for a given analysis period, like between Jan 03 and Dec 03.
Can any one please let me know about this.
Thank you
Bob

Hi Bob.
I'm affraid such report is not available.
You may get something similar by running the RX-only: Payables Invoice Register by Detail. You also have the option to change the way data appears on the report on it is an RX report.
Octavio

Process/Production Order WIP Reverse on Month starting date with postiing d

Hi Experts,
Is it possible to reverse the WIP of Production/Process Order at month starting date eg. 01/07/09. Posting date & Document date should be: 01/070/09.
In my current project production is batch management system. Some of the batches start at month ending days (Eg. 29/06/09) for we calculated WIP at dated: 30/06/09.
My Client wants to reverse that WIP next day, month starting hours Eg. 01/07/09 but while reversing the WIP system is posting the WIP reversing doc. posting date is 31/07/09.
Same batch which started production on 29/06/06 is closed at 03/07/09 as well as goods received same date. FG Stock A/c updated in accounting books.
At the same day If I print my trail balance system showing the Stock value double (WIP stock as well as FG stock)
First Month
Eg. Process Order WIP at 30/06/09                              : 50000/-INR
Second Month
      WIP Reversal Posting date:31/07/09 by system     : 50000/-INR
      FG Stock received at 03/07/09                               : 50000/-INR
If I Print Trail Balance on 03/07/09 system shows        : 1, 00, 000/-INR (based on Posting date)
Which is wrong..
Please tell me the way for Change the Posting date of WIP reverse document. OSS guys are replying as consulting issue.
I am waiting for your valuable reply.
Thanks & regards
Bhagiradha

In KO88, CO88 Select Menu bar Extras-> Posting date
Enter Posting and execute
Thanks for Rajesh (SAP Labs)
Thnaks & Regards
Bhagiradh

Start date mismatching

Similar Messages

Maybe you are looking for