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.

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 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..

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

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

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

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.

Validity start and end fields in Scheduling agreement

Hi,
We are experiencing an issue where in for Transactions of ME31L, ME32L, ME33L for some users we the fields of Validity Start date (Header )and Validity End date (Header) is not appearing. These fields have been made Mandatory still for the users for which they don't appear they are able to save the Sch Agreement without inputting this information. Is this something to do with authorisation issue ?
Please help,
Thanks,
Sam

No I have already made the fields mandatory but the problem is only validity fields do not appear in ME31L, ME32L, ME33L for certain users and they do for others.
Sam

Insp. Lot Start Date

Gurus
I have one inspection lot of origin 03 i.e. production. This production order has 3 operations in which 2nd operation has control key related to inspection. Operation 10 is not for QM
Whole Order is released on 10.12.2009 and accordingly i can see lot start date as 10.12.2009 WHICH IS WRONG.
Lot start date should be when operation 20 is starting i.e. 12.12.2009 but it shows 10.12.2009 when order is released. It should be operation specific dates
Why is system taking order release date as inspection lot start date? Is this standard SAP???
Please reply
Regards

Dear Vicky
03 inspection start date is based on operation date only. It is not based on the release day of the production .
When an inspection lot is created for a production order, the scheduled start of the order is used as the planned starting date.
you can get the same in the sap help also. Go to QA03 for the 03 inspection lot > DATA for lot origin> press f1 on inspection start date
Check the order for the inspection lot and confirm whether the date maintained for the QM operation is 12.10.2009
Regards
Gajesh

Date Validation - End date before Start date

This may be a very simple validation but I seem to be having trouble. I've got a form which requires a date range to be selected (Date Picker fields)...a Start date, and an End date.
I've created a Function Returning Boolean validation with the code as:
begin
if :P1_END_DATE < :P1_START_DATE then
return false;
else
return true;
end if;
end;This works 99%, except when the date range spans years.
For example, when I select '21-Dec-2010' in the start date and '4-Jan-2011' in the end date. The validation fails, and thinks the end date is before the start date.
Do I need to compare the year part of the date, before doing the rest? Or is the '<' not suited for this sort of check?
Edited by: djston on Dec 20, 2010 12:13 PM

Sorry, false alarm, it looks like I had my logic a little backwards :)

[CF10] CFINPUT custom validation start and end dates

Hello, everyone,
Another developer that I am working with is working with a form that has start and end dates. He'd like to be able to use custom JavaScript validation to make sure that not only are the dates in proper format (that part of the JS is working fine), but that it will also check to make sure that the start date will always be prior to (or equal to) the end date, and will throw an alert if the end date is before the start date.
I've Googled for this, and am finding informative suggestions on just making sure the date is in the right format, or falls within a certain range, but nothing on how to make sure that one date is before (or less than) another.
I'm guessing that data binding might be a part of it. Can anyone suggest how to set these fields so that each has a validateat="onblur" that will check both values?
Also, as a related issue, he has the CF datepicker working as far as entering the dates, but since the field doesn't get/lose focus on this, how do we trigger the function?
V/r,
^_^

i had tried this a few times but I kept getting an invalid numer to character error. Maybe my syntax was off. Let me try again.
I must have had syntax errors. I tried it again, the way you typed it out and it worked. Before I was using '/' instead of '-' to separate the date fields.
Thanks again!!

Prevent user change PO data except Validity start , Validity end and ...

Hi,
I use BAdI: ME_PROCESS_PO_CUST method:PROCESS_ITEM to check if any change PO data after that PO was released. The change will accept only if the changed fields were Validity start, Validity end and Delivery date.
If user change other fields, i use the BAdI to set data in that field back to old data. My problem is when user delete item the field Delete Indicator was set to 'L' so i change it back to blank by method set_data but it still show delete indicator in PO screen.
anybody has any idea?!
best regards

Hi Chantima,
This is only a guess as I did not have time to validate...but only certain fields can be changed in the PROCESS_ITEM method...look at the structure MEPOITEM_TECH for the list that cannot be changed by the customer badi...your delete flag setting may be in there or the setting of the delete flag may update a field in this structure....
You may want to take a different approach and stop the changes from being made instead of backing them out....couple of possibilities include...
A. Restrict all users on this Tcode and PO document type I would look at the configuration in MM->Purchasing->Define screen layout at Document level. You can make fields display only instead of coding a solution.
B. If you have to have more control than provided in the config or need to code the solution, you may want to investigate using the Field selection methods (all start with FIELDSELECTION_*) to stop the changes from being made instead of backing them out after the changes are made.
Good luck.
Rob

Report for Validity Start and End Date in PO

Dear All
Is there any report where I can get PO validity start and end date which user input in addtional data header tab of PO?
Regards
Satish Kumar

Hi,
Yes, It is available standard report using T-code ME2N - Purchasing Document (PO) Per Document Number, enter the T-code and provide the following input data's are as follows.
Scope of List                 : ALV ( for Ms-Excel format report)
Plant                               :   __________ to __________ (if required)
Document Date              : ____________ to ___________ (if Required)
Execute the report shown by default in excel format and if required PO validity start and end data, you have to select Change Layout button and open new window options screen right side field option as Validity Per.Start, Validity Period End, Commutative number field data's are selected and click <--- arrow button and then click bottom tick marked button. Now, the report shown your requirement.
Hope, it is useful for you,
Regards,
K.Rajendran

Planned order creation with PDS valid on only order start date and not finish date

Hi All,
We have requirement to allow creation of planned order manually if production version is valid on order start date and not finish date. This is because lead time of order is longer. I refered OSS notes 385602. I could find out solution for this is implementation of OSS note 694140 to change validity mode at activity level to consider start date of first produce activity in validity interval. Problem is even If I create order in APO by implementiong this note planned order is not transfered to ECC and it gets stuck with error production version not valid.
Is there any way in ECC to control this? Any config or customization?
Regards,
Santosh

Nilesh,
I think there is a simple procedural skip happening in your business process. You are right when a planned order is created after MRP it would default assign it to the first available production version. 2options available for us,
1. First use transaction MF50 and do the line loading and assign the quantites to the production versions/Production lines, so that the actual capacity planning is getting completed. This way you can have planned orders with both the production versions and matching to your actual line capacity.
2. Use Quota arrangement concept, to automatically split the Planned orders during MRP for a percentage based on individual production versions.
Now when backflush is performed S225 table is updated and Planned order qty also gets reduced.
Hope this helps....
Regards,
Prasobh

Validation on start date and end date .

Hi every body ,
Hi have a problem on validation on the start date & end date problem.
I have taken two *<h:inputText>* & one *<t:commandLink>* controls.When I am clicking on the <t:commandLink> control I want to validate that end date should greater than start date .Could any body help me out from this problem .
Here is my code :
<rich:dataTable id="dataTable"
                           value="#{adminBacking.dataModel}"
                           var="item">
   <h:column>
     <f:facet name="header">
          <h:outputText value="Start Date" />
     </f:facet>
     <h:inputText size="11" id="startDate" value="#{item.startDate}" onclick="showCalendarControl(this);" />                      </h:column>
<h:column >
     <f:facet name="header">
          <h:outputText value="End Date" />
     </f:facet>
     <h:inputText size="11" id="endDate" value="#{item.endDate}" onclick="showCalendarControl(this);" />
</h:column>
<h:column>
     <f:facet name="header">
          <h:outputText value="Update Row" />
     </f:facet>
     <t:commandLink id="update" action="#{adminBacking.updateEvent}" value="Update" />
</h:column>
</rich:dataTable>**Here I am taking the date by a simple date picker in the start date & end date field.
Thanks ,
sb

You may find this example useful: [http://balusc.blogspot.com/2007/12/validator-for-multiple-fields.html].

Subtype Validity Start date Check

Similar Messages

Maybe you are looking for