Validity end date tab is suppressed in scheduling agreement

Hi ,
In scheduling agreement , Validity end date tab is suppressed ,
There is no layout is assigned to the doc type & standart transaction varient is acitve , but while doing ME31L above field is not coming ( it is in suppressed / hide mode )
Please let me how to get that validity date tab in scheduling agreement.
Thanks,
Pradeep

Hi,
Go to SPRO > IMG > MM > Purchasing > Purchase Order > Define Screen Layout > NBF > Administrative data, header > make the fiels Validity Period field optional / Required.
Hope this will help you.
Regards,
Manish Jain

Similar Messages

CIF of SA is not consistent for Validity End Date

Hello gurus,
Our company is quite new in using SNC, and we bumped into this problem (see description below), and hopefully this forum can help us.
<Description>:
When the Scheduling Agreement is CIFed from R/3 (ECC) to SNC, the Validity End Date does not get updated each time.
It gets updated sometimes, but not always. It is inconsistent behaviour.
<Example>:
Scheduling Agreement A
Validity End Date: 31.12.2012 Changed to 30.11.2012 in R/3.
Performed CIF using Transaction Codes CFM1 and CFM2.
Correctly updated the Validity End Date in SNC.
For the same Scheduling Agreement A updated Validity End Date to 31.01.2013 in R/3.
Performed CIF using Transaction Codes CFM1 and CFM2.
The Validity End Date was not updated in SNC & remained as 30.11.2012.
For the same Scheduling Agreement A updated Validity End Date to 15.10.2012 in R/3.
Performed CIF using Transaction Codes CFM1 and CFM2.
The Validity End Date was not updated in SNC & remained as 30.11.2012.
Thanks guys
Tuffy

Hi Tuffy,
1 - I am just wondering if after the Delete the existing External Procurement Relationship in SNC, and CFM1 and CFM2 the SA (i.e. changed my validity end date value) to the SNC, will the problem of the SNC side not able receive the changed SA??
When there is a change in the SA, integration model would create the same in SNC if it does not exist. But the transfer from ERP does not happen just like that. First, make sure that the message type (CIFSRC) has been checked in BD50 and then schedule a job to periodically transfer the SAs.
2 - What does the tcode the person in the SNC side have to double check to ensure the SA is transmitted there??
The t-code is /SAPAPO/MTI2 - External Procurement Relationship.
3 - Someone in our company advise BASIS team to check the transactions BD50 and BD52. What exactly does it mean and does it help?
This is correct. I mean guys who are responsible for Integration model need to set-up BD50, BD52 so that changes to SAs are transferred periodically.
Regards,
Sandeep

Validity start and Validity End date in PO

HI gurus
can you plz tell me how to activate validity start and Validity End date in PO
Neha

Hi,
It is applicable for PO done for Frame work oder with Doc type - FO(Frame work order)as its an agreement of supply of stock only between specified period.For this kind of Doc type system makes it mandatory to enter the valisity start and end date.
Thanks

Query on extension of validity end date of Qualification - PD

Hi All,
I want to extend the validity end date of a qualification.
I tried T-code OOQA however the validity dates are greyed out .
Can anyone please help me with this?
Best Regards,
Kanika

It can be done using Tcode- RE_RHGRENZ4.
Thanks all...
Kanika

Change validity end date on activity type

Is there a way to change the validity end date of an activity typre. Currently it is 9999 we would like to change it to 2011.
We would like to use a particular activity to cost current standards but dont want to use it for planned estimates that we will create for 2011. I am assuming if the validity ends in 2011 it will resolve the problem. I know we could create alternate routings and different production version but I am trying to avoid that and see if we can find a short cut.
Your help in this regard will be much appreciated

Hey Greta,
I executed the report but it says ,"The deletion could not be carried out, plan records still exict on cost center for activity type." I have deleted every thing from kp26 for that particular combination of activity type and Cost center.
Any ideas as to what is happening!!
Regards,

Employee qualification assignment IT0024 validity end date update

I Would like to change the validity end date value on one specific qualification assigned to an employee.
I can't do it using PA30. Is there anybody able to tell me how can I do it?
Thank you

You can't change endda because infotype 2 endda has to be '31129999'.
It's explicit here in this validation in module POST_INPUT_CHECK.
form check_it0002.   "form aus mppers00 hierher verlegt    "VLDN212840_2
if psyst-first eq yes and cprel-endda lt high_date.
*   I105(RP): Gültigkeitsende muß gleich & sein
    p0002-endda = high_date.                               "VLDN212840_2
    cprel-endda = high_date.                               "VLDN212840_2
    message e105(rp) with high_date.
endif.
if psyst-ioper eq modify.
    if cprel-endda lt high_date and pskey-endda eq high_date.
      p0002-endda = high_date.                             "VLDN212840_2
      cprel-endda = high_date.                             "VLDN212840_2
      message e105(rp) with high_date.
    endif.
endif.
endform.                    " check_it0002
high_date is a constant with value '99991231'.
Anyway, why would you want to change the endda on infotype 2 ?

Validity end date is not getting copied from inquiry to quotation.

Hi Friends,
While creating quotation the validity end date is not getting copied from inquiry to quotation.
What setting needs to be done, pl suggest.
Regards,
Hari.

Sreehari,
i dont find any logic of having Same validity date for Quotation and Inquiry....
the simple reason is explained by example: Say you have created Inquiry on 1st november and end date is 15th novembr. Customer comes to you on 14th november and asked for Quotation, and if you refer quotation on that day that means its only applicable for one day, which generally wont be the case.
There is no option for copying the validity dates from Inquiry to Quotation as per standard. If you want, create routine, place it in copy control.
Thanks,
raja

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 :)

Validity End Date for A012 relation not updated

Hi All,
I am working on SRM5.0 and the HR org structure is replicated from ECC to SRM via idocs. Now, for one particular user, who holds position in 2 org units, the HRP1001 table data is incorrect.
For one of the relations A012 between S-O, the end date shown is in the past. I checked the ECC tables for this employee and the A012 relation is valid till 31/12/9999. But, in the SRM system, this date does not get updated.
Due to this employee is not shown as an approver for that particular org unit.
Does anyone know how I can update this date?
Regards,
Ancy

One of the Org unit is under the other org unit. So, I updated the position with the relation to the higher org unit only. So in the SRM system, by default, the supervisor for this org unit is the supervisor for the lower org unit too, unless there is a new supervisor for the lower org unit.

Workflow Substitutions - Force Validity End Date

Is there a way I can configure Business Workplace Substitution Validity date from and to dates to fall within a specific range? Can I prevent someone from using the default 12/31/9999 date when creating a substitute?

Hi Mark,
Well for starters a lot depends on:
a) What release/environment are you using?
b) What type of substitution - user to user or position to person are you using?
If you are using position to person, that's HR infotype A210 so you could use HR Structural Authorisations to only allow the infotype to be created e.g. up to the end of the current year.
If you are using user to user, its a bit harder. In that case its based on table HRUS_D2, which only checks the end date is a valid date.
So you would really have to code in an additional check from wherever you are maintaining the data.
So now the question is, how do your users maintain substitutions? i.e. in which release/environment? using which maintenance tool? Then you need to check out how that tool works.
E.g. you might be using the API SAP_WAPI_SUBSTITUTE_MAINTAIN or the table maintenance generated for HRUS_D2.
E.g. if its just the table maintenance view, you could add a table maintenance generation "event" with your additional check (go to the table maintenance generation and try menu Environment > Modification > Events).
Unfortunately the other maintenance tools use function modules - none of which currently offer any BADIs or user exits for adding additional checks. So at this stage it would be a mod. But a good thing to ask for in a development request perhaps.
Regards,
Jocelyn

Release date and release no of Scheduling Agreement

Hi All,
I have a problem with Scheduling agreement.
I have created a scheduling agreement with long validity period.
I maintained delivery schedules within that validity period.
I have generated forecast schedules. then using ME84, creating a releases.
the problem is occurs here.
it was not updating the release no and release date for the schedule line.
still it is showing a *yellow light* .
where is the problem and why it was not updating.
and can u please explain the process and significance of those lights.
Thanks in Advance.
Regards
Kishore

Verify the table T161M has the values
kvewe = 'B'
kappl = 'EL'
druvo = 1
kschl = LHPA
as mentioned in the code.
The solution is add in SPAD the

Dates and quantities copied from Scheduling Agreement to Delivery Order

Hi everybody,
we're experiencing a problem with copying control for dates/quantities between Scheduling Agreement and Delivery Order.
If we define a Forecast Delivery Schedule with more lines/dates into a Scheduling agreement, when I create a Delivery Order with reference to a specific date the system always copies the first forecast delivery schedule date, disregardful the date specified in the selection criteria for delivery creation and with the fact that this could have already been carried out.
Here's an example:
Forecast Delivery Schedule into Scheduling agreement:
(Date) 12.03.07   (Quantity) 10 TO
(Date) 13.03.07   (Quantity) 12 TO
(Date) 14.03.07   (Quantity) 15 TO
When delivery has to be created with reference to Scheduling Agreement, the system doesn't about the date specified in selection parameters (e.g. 14.03.07) and copies the quantity of the first forecast delivery schedule line (10 TO).
Does anybody knows how to maintain Copying Control for dates and quantities between Scheduling agreement to Delivery Order?
Thank you!
Luca

Dear Pattanaik,
check data transfer from copy controls.for this T-code is VTLA
here select your doc type and select details and check also item.check inside both types data trasfer wich is assigned change from this item to header.your problem may ve coming from here.
hope this will helps you
Prem

Delivery date is no use in scheduleing agreement.

We are using scheduling agreement and automatic schduling line for purchasing.
I already maintain delivery days =2 days and GR day=2days in scheduling agreement.
after MRP running, I found the delivery days is no use.
For example.
requirement date:2009.04.17
MRP result: scheduling line delivery date=2009.04.15 ( !only GR day=3 is in use)
I think the delivery date should be 2009.04.13
I am using standard TB (daiy lot size and the setting for Scheduling Requirements date := delivery date)
why is the delivery date no use in MRP running?
tks in advance.

Hi
If you have used GR processing time in scheduling agreement (example 2 days) if the requirement is on 25.04.2009, then proposed delivery date is for 23.04.2009. GR processing time reduces plans 2 worksday for processing and reduces 2 working days as per factory calender to propose delivery date.
Planned delivery time will not be considered if the requirement date is more closer than the planned delivery time. You will see an exception message in MRP results for that.
Regards
Antony

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

How to set up start and end dates for validity of contract account in FICAx

Hi,
Can anyone tell me where can I set up the validitiy period for the contract account in FICA. In contract creation, I could just see the contract validity start date. I also need to know the validity end date. Please let me know the solution asap.
Points will be awarded for all the useful answers.
Thanks
Santosh

Yes, you're right, you would then need to develop a lot of user exits to prevent the re-use of the contract account after the validity date.
I'm think in a strange solution, it could work but you'll need to test it. if a contract account is marked for deletion (Field FKKVKP-LOEVM equal to 'X') no further action can be made over it, When you create you contract account you can schedule a change using as validity date (Field BUS000FLDS-VALDT ins the change contract account screen) to the end date of you contract account and set this deletion flag. then you run FPP2A to activate the schedule changes, before you get to the end date the flag is not set, when you get to the end date FPP2A will activate the flag and the contract account becomes not usefull.
If you do this, you have be careful because all the postings to the contract account won't be possible, it means that if there are payment to be made, interests to be calculated, etc... nothing will be posted.
Cheers,

Validity end date tab is suppressed in scheduling agreement

Similar Messages

Maybe you are looking for