Contract validity start date should be better left blank

Hello,
We have customized the contract start and end date as optional (because some time they do not know the date at the moment of the creation of the contract).
The issue is that the system propose today's date, even if the user delete the proposed date the system fill this data again.
Someone know how we have avoid this proposed date.
Cheers,
Marta

Hi Martha,
You can change the default date in Validity start period, just remove the date and enter the new date system will accepts the new validity date.
Check the document type you are using to create Contract and in IMG settings check the the field selection used against this Document type.Then set the same in define screen layout.
Also check whether any screen exit is used for this transaction in SHD0.
Might be somebody has defaulted the validity date as today's date.
rgds
Chidanand

Similar Messages

Source List Validity Start Date

I have noticed that, if the source list validity start date and contract validity start date are same then, the contract price is not considered while creating PO and receive error message as "Source not included in list despite source list requirement"
If I change the validity start date of source list to one day before the validity start date of Contract then system is picking the contract price in PO and able to save PO successfully.
Is there any way to create PO even if the validity start date of source list and contract are same?

from OSS Note 44368 - ME51 ME57 Contract as source of supply
A contract that is valid on the delivery date but not on the current date is not taken into account in the source determination process.
Cause and prerequisites
This is programmed this way.
Solution
For reasons of upward compatibility, check will continue to be carried out on basis of current date.
However, if you wish the check to be against delivery date, you can implement the modification described under the advance corrections.
If Note 116464 is implemented in a 4.0B Release, use the advance correction from Release 4.5A, however, in Release 4.0B the program name is LMEQRF01.

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

Restriction of Validity start date in Info record ME11/12

Hi,
Can anybody suggest how can we put a check in validity start date of conditions so that back date is not selected while putting the price/conditions in info record.
Regards
sachin

hi..
When u create info-record for any comabination of material and vendor..u go to condition tab ..where ehile defining condition type and their details u can specify their validity....
and after saving this..if u again want to see that condtion type then it prompt u for "choose validity" for which u want to see the condition type...
Hope it works,,
Thanks..

Start date should be after the dd.mm.yyyy or later error message.

We have recently applied HR support packs 46 to 51 and now when updating Personal Data (IT0002), Bank Details (IT0009) or Addresses (IT0006), the following error message is displayed 'Start date should be after the 07.02.2010 or later'. Where the screens allow for a future date to be entered we have done so, but the same error message appears.
Has anyone encountered this problem after apply support packs?
Jason

Hi,
Check what is the date maintained in table V_T569R.
With Reagrds
Shyam V

Subtype Validity Start date Check

Hi All,
For one of the infotype we created a new subtype with the validity in future date say 01102010.
Now if i go to infotype i am able to create the record for this new subtype with the start date as 01042010 which should not be allowed.
I checked the table V_T582A and also the time contraint for the infotype.
Time constraint for the infotype depends upon the subtype and in the subtype table it is mentioned as 2.
I know that we have the custom check for the infotype but is it possible through stadard settings
Pls guide me on this
Regards,
Umesh Chaudhari

Hi Umesh,
Though the subtype table for 0071 (Pension funds GB) is V_T591A; it also reads T5G30 to identify the schemes..
Table T5G30 in turn has got various Pension Schemes with Start Date/End Date.. If you Start Date and End Date of the Plan is in Future (01102010) and if you intend to maintain the new scheme (Subtype) from 01042010; an error is displayed..."Scheme XXX is unknown for this period; check pension table entries."
Kumarpal Jain.

Comparing dates (Start date should not be later than End date etc ...)

Hello All,
I have a table (5 rows) with 7 columns. Of which the first to columns are the start date and the end date. Can someone kindly advise on how I can go about to ensure that there is some validation mechanism in place such that the start date is not later than the end date and vice versa ? Thank you very much.
from
Kwok Wei

Hi
Use calculated attributes as Pran suggested. It should work. Where are you getting the data from. Is it from R/3. The node bound to the table ui element is it a model node. Anyway Here is the link on how to use the calculated attribute.
http://help.sap.com/saphelp_nw04/helpdata/en/7f/a0384162316532e10000000a1550b0/frameset.htm
regards
ravi

SNP Planned order START date should be displayed in DATA VIEW

Hello Guru's
I have a very complex requirement. It is as follows
We are using heuristics and capacity leveling for our requirement. We generally see the planned orders in the SNP view but here additional requirement is that we have to see the start date of the production planned in the date view, ie the client would like to know when the actual production starts and wants to see the quantity produced on the first day in the date view.
In capacity view,we can observe the resource load which is the start date of the production planned, this load is in percentage now do i related that into quanitity and even if we do related that percentage in quantity then how do i see it the SNP data view plan.

Hi Sriuppa,
you can use receipts view /sapapo/rrp4 transaction where you can see receipts. This transactions offers you the selection based on product,source,target,dates,resource and you will get the list of orders.
Secondly ,if you right click in the receipts cell,select display details,it will show you order details at the bottom of the data view.
Please let me know if it helps
Thanks
Amit

Settling Rebate Agreements with Validity Start Date not Start of the Month

Hello Experts,
I am currently trying to settle a rebate agreement with validity dates November 20, 2011 to December 31, 2011. However, after the credit memo is created, I noticed that the Service rendered date is today's date, but I expected it to be the same as my Settlement Date = November 30, 2011 (a month-end). Please advise if this is normal. If not, please advise how to correct the automatic entry of dates.
Thanks,
M

Hi
Kindly let us know what is the rebate agreement type that has been used for which you are facing problem and for which rebate agreement type you are getting the month end date.Check wheather scale basis is B(Value scale) has been maintained or not for the rebate agreement for which you are getting problem.So check the differences between the two rebate agreement types.As The service rendered date of the invoice line item is used to determine the validity of a rebate condition record
Regards
Srinath

Validation on Date Field in tabular Report

Hi All,
I have manually created the Tabular report and in that I have TWO DATE field
1)Start Date
2)End Date
Now i want to put validation on start date as - Start Date Should Be More than sysdate.
and validation on End date as - End Date should be More taht Start Date.
How to put the validation ?

Manish Jha wrote:
What is the error you are getting ? Try executing the process in SQL workshop with hard coded values of apex_application.g_f03 and debug the error.
Thanks,
Manish
>What is the error you are getting ? Try executing the process in SQL workshop with hard coded values of apex_application.g_f03 and debug the error.
Thanks,
Manish
Hi manish ,
I have Used the following code to validate end date should be more less than start date;
DECLARE
l_error VARCHAR2 (4000);
BEGIN
IF TO_DATE(apex_application.g_f05 (i), 'DD-MON-YYYY ') > TO_DATE (apex_application.g_f04 (i),'DD-MON-YYYY'
THEN
l_error :=l_error
|| '</br>'
|| 'Row '
|| i
||' ,TEST';
END IF;
END LOOP;
RETURN LTRIM (l_error, '</br>');
END;
it's giving the error like :
ORA-06550: line 16, column 6: PLS-00103: Encountered the symbol "RETURN" when expecting one of the following: begin function pragma procedure The symbol "begin was inserted before "RETURN" to continue. ORA-06550: line 16, column 24: PLS-00103: Encountered the symbol "BEGIN"
Error ERR-1024 Unable to run "function body returning text" validation.
What to change in the code?
Edited by: N.K on Jun 23, 2009 11:43 PM

Data validation for Date Field in Web Dynpro ABAP

Hi ,
In my WDA i want to perform data validation for date filed. (i.e. While creating a new record i have to check the Start Date should be always lesser than End Date.)
If u ll enter the wrong date it should validate the Date and throw an error message.
Please Reply soon its urgent.
Thanks,
Deepika

Hi,
First read the two attributes start date and end date.
Then write the following condition.
IF item_start_date > item_end_date.
Error message.
Endif.
For pop up error message you need to use Create_window method of the Interface if_wd_window.
Thanks.

Selection Screen validation for date

Hi,
I have a date in Select option s_budat which is a mandatory field
The Criteria for validation is
1) The start date should not be older than current date minus 8 weeks. Otherwise error message should appear:
EN: Start date is older than 8 weeks
2)The end date should not be more than one week ahead of date-from. Otherwise error message should appear:
EN: Selection period is more than 1 week
please help me to solve this
regards
Avi

data : date1 like sy-datum,
       date2 like sy-datum.
CALL FUNCTION 'HRWPC_BL_DATES_WEEK_INTERVAL'
EXPORTING
    DATUM                = sy-datum
    WEEK_PST             = 8
    WEEK_FTR             = 0
START_SUNDAY         =
IMPORTING
   BEGDA                = tdate
   ENDDA                = tdate1
EXCEPTIONS
INVALID_VALUES       = 1
OTHERS               = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
if s_date-low lt tdate.
message.
endif.
CALL FUNCTION 'HRWPC_BL_DATES_WEEK_INTERVAL'
EXPORTING
    DATUM                = s_date-low
    WEEK_PST             = 0
    WEEK_FTR             = 1
START_SUNDAY         =
IMPORTING
   BEGDA                = tdate
   ENDDA                = tdate1
EXCEPTIONS
INVALID_VALUES       = 1
OTHERS               = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
if s_date-high gt tdate1.
message.
endif.
regards
shiba dutta

Contract validity period

Hi,
We have some querries regarding Contract;
E.g:
1) The validity period of Service contract is 17.07.2008 to 17.07.2008
2) Service PO created on 17.07.2008
3) For creating the Service entry sheet on 18.07.2008, whether system will have any control of the contract validity period as the Help on the Validity period explains regarding the srvice entry sheet, however system is not giving any message while creating service entry sheet on 18.07.2008;
Please find the help available on contract validity;
*"Start of validity period*
*Date as of which services can be performed or materials delivered.*
*Use*
*In the case of outline agreements:*
*Start of the stipulated validity period of an outline agreement.*
*In the case of RFQs:*
*Start of the period in which the quotation is to be submitted.*
*In the case of purchase orders:*
*Start of the period in which the service is to be performed or the material delivered.*
**Note**
***Service entry sheets can only be created within the specified period."***In this help, all points are cleared except the last one regarding service entry sheet. Could you please explain the impact of last sentence in the help for service entry sheet.
Thanks in advance;
Regards
Shp
Edited by: Shp shp on Jul 18, 2008 7:15 AM
Edited by: Shp shp on Jul 18, 2008 7:16 AM

Hi
Thanks for quick reply, we have tried with both the delivery date 17.07.2008 & 18.07.2008, in both case system has accepted the service entry sheet.
Please suggest.
Thanks
Shp

Add Validity Start and Validity End On PO Header

Dear SAP,
need your help, I am trying to add Validity Start and Validity End Field on Additional Tab in Purchase Order header.
How do i add this field ?
i already check on MM define screen layout a document level, but there is not setting for this two field.

Hi Nizam,
The validity start date & end date are used only for service orders. In configuration goto IMG>MM>Purchasing>PO>Define screen layout at document level and check into Administrative data, header of ME21N , the field selection key attached to your document type (Say NBF) and for field selection key AKTH.
The fields Start of validity period & Validity period end of field selection key ME21N, NBF & AKTH should be set as optional then only required fields will be visible on screen.

SNP Planned Order start date in past

Hi
After SNP run, for the past requirements it is giving avaiablilty data as today but the planned order start date is in past. Now this order fails in CIF as the production version in R/3 is valid from today.
In the strategy profile we have backward+reverse with infinite scheduling. In this case the start date should be todays date for past requrirements... am I correct?
Regards
Abhishek Rai

Hello Abhishek,
We are also facing the same issue. Did you find any solution to this issue?
We are on SCM 7.0 with EHP1.
Thanks,
Mangesh

Contract validity start date should be better left blank

Similar Messages

Maybe you are looking for