on 10-01-2012 7:32 PM
hi,
while scheduling the project using tcode cj20n in SAP PS getting some error.kindly help me to provide the solution.please find the error message
1. Can delivery date for material 0002/000000102001130254 be kept? Realistic date: 27.09.2012
2. Schedule conflict:constraint is too early.
3. Schedule conflict:constraint is too late.
4. Error calculating costs for network?
Please, do not make any error message as warning message, without understanding the impact.
The above error is good, it informing some part of business process is not completed, so just analyze that portion, and you will able to get to the result.
Thanks,
Nishan Dev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I am not inline with What Pranav has suggested. Changing message class does not give a scheduling impact on the project. Sorry being impolite.
I am copy pasting your questions and read answers below each line
1. Can delivery date for material 0002/000000102001130254 be kept? Realistic date: 27.09.2012
- Check at the required the date of delivery at component overview screen which you might have keyed in manually. Since required date is not the realising date and hence system is proposing realistic date i.e 27.09.2012. Please change the date as suggested by system. Please note that these dates are derived from PIR (Pruchase Info records) if maintained in the system.
2. Schedule conflict:constraint is too early.
- Did you maintian the constraints? if so check that date should be within the activity duration dates. Correct those dates
3. Schedule conflict:constraint is too late.
- Change the constrain date. Please try to maintain the constraint date either finish or start within activity duratiion dates.
4. Error calculating costs for network?
- What kind of error you are seeing while calculating costs on network. Are you maintaining the Activity type? is it cost center or what kind it is.
Please post error message our friends will suggest or myself depending on time zone.
Please note that don't try to cut short the things which will produce unrealistic output rather than realistic.
Regards,
Sudhakar
Message was edited by: Sudhakar Pappu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sudhakar,
Don't feel sorry. Its OK that you are putting your view.
There is some business scenario when this error message seems wrong.e.g. Emergency PO for any material. This one is exceptional case. Similarly there may be some other cases where requirement date calculated through PIR is not correct.So it is preferable to convert this error message to warning one.
However your point is right to check for realistic date which seems entered wrong.
Regards,
Pranav
Hi Neha,
If this is already warning message then don't bother for it. Else
Follow this-
1. Enter OLME.
2. Go to Environment data->Define system attributes and message
3. For message no. 245, change E ind to W
Note- Do it in consent with competent authority. This must be approved.
Involve MM consult in it.
Regards,
Pranav
Hi Neha,
If it is warning you can go ahead ignoring. but still you can try to find out your MM team what could be the lead time for procurement and accordingly you can input the required delivery date.
Keep trying to change the dates till you get the exact date.. but since it is warning you can ignore. Other way around is to check the PO delivery date and that would let you know what is the lead time required to procure the material. basing on this one you can input info for future requirements.
As Pranav already stated try that way. all the best
Regards,
Sudhakar
Hi Neha,
1. Make this message warning message instead of error message.
What scheduling method you are using. Also specify dates which you are entering in WBS, for which you are getting error message.
Regards,
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.