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

Similar Messages

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

Mass change Condition valid to dates into Info record

Hi,
is there any mass changes for condition validity to dates into purchase info record?????
i have check into MEMASSIN, there is field for conditions valid to Date,
Pl. guide .
Regards,
Devendra

Hi,
It is not possible to change validity date using MEMASSIN - Mass Maintenance t code.
You need to create LSMW with recording method to achieve this. we are doing the same.
It is very easy. And take care that while recording select the validity button and click executive to record the do not double click on the validity tab.
Reg

PO creation date and info record validy price relation.

Dear Gurus,
While creating a PO, when I change the PO creation date, price in the PO will change according to the validity start date based on the PIR.I believe thats the logic right? I have a scenario, I'm facing a problem that when I change the PO creation date between 2011 and 2012 period, the price of the PO at times will not change according to the PIR validity start date. Is there any OSS note related to this issue or I'm missing out any logic?
Validity periods
Validity on        Validity to         Deletion Flag.
04.11.2011       31.12.2011              x
01.01.2012       31.12.9999

HI,
By default, the pricing conditions are dependant on PO document date.
But there are different options like, whether you want your pricing to be dependant on Delivery date of PO item or current date (sy-datum) or GR date etc.
This filed is available in 2 places: 1. Vendor master>purchasing data> Pricing Date Control
2. Info record>Purchasing data> Pr.Date Cat.
Check in these 2 places and then simulate pricing by changing the corresponding date.

Restrict OM Infotype start date as 12/31/9999

Hello Experts,
I want to restrict OM infotype start date on entering start date as 12/31/9999.
One of the OM infotype is accepting and saving that record when entered start date as 12/31/9999.
Please let me know how to restrict doing that.
Thank you.
Regards,
Saurabh

Hi Saurabh ,
Implement BADI definition HRBAS00INFTY . In Method AFTER_INPUT or IN_UPDATE , code as :
READ TABLE new_image INTO w_new_image INDEX 1.
if w_new_image-begda = '99991231' .
*Throw a Error Message as "Start Date cannot be 12/31/9999' .
endif .
Thanks ,
Sucharita Das

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.

Supply Option dates in info record

Hello
My users specified "Available From" and "Available To" dates in Info Record. They would like these dates to be automatically emptied when both dates are past dates.
Can this be done ?
Thank you.

Our users would like to use info record to temporarily (for a period of time) block a PO to be assigned to a vendor. One option is to specify the available from and available to fields in info record.
Once the period is over, the users would like the two dates to be emptied so POs can be assigned to this vendor again.
Thanks,

Sales order cost estimate to be updated in Info Record (ME11)

Hi,
We have two plants: (a) Sales plant and (b) Manufacturing Plant.
At sales plant, sales order (external) is created and for same external sales order we create another sales order (internal) at the manufacturing plant.
At the manufacturing plant we have the option of doing sales order cost estimate (VA02/ CK51N).
We want to update info record (ME11) at sales plant with sales order cost estiamte value at the manufacturing plant. How this is possible? please suggest.
Regards,
Bijay

Hi
Ask your SD guy which routine is used during the pricing.. You need to write ABAP code in the routine in order to fetch the values from the Sales Order cost estimate
usually, the sales order cost estimate is stored in EK02 condition type... You can read the value from EK02 cond type in Mfg plant and update it in Sales plant
br, Ajay M

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.

Validity period field in Info record

Hi all,
I encounter the following problem while creating an info record. The validity field was mandatory, but the field was grey and evantually i couldn't enter anything... Can anyone clarify my doubt???
Message was edited by:
Antony anburaj

Hi
In ME11,While creating Info Record, In Pur.Org.Data1 Screen, you will find that the Valid to Field in Grey....If you want to give give valid to Date, then In the same screen, Go to Conditions, and there you can give Valid from and Valid to Details and all...
Reward if useful
Regards
S.Baskaran

PR Deliv Date doesn't take from the Master data or Info Record

Dear All,
When i create a PR manualy by ME51N, the delivery date can always calculate from the planned delivery time in info record or Material master, but when the PR is generate from a Sales order, the delivery date always the date when the SO is created.
Can anyone please advice me on this issue?
Thank you very much,
Regards,
Chee Wee

CW,
You still have not mentioned the Planned delivery time in the two purchase requisitions (auto vs manual). I will assume they are the same for now. Planned delivery time can be viewed in ME53N > select item; review item details, select 'quantities/dates' tab. PDT is displayed, along with GRPT. Let me know if they are dramatically different.
It sounds like you are using SAP's "Individual Purchase Order" functionality.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dd/5601d4545a11d1a7020000e829fd11/frameset.htm
If you are not, then it is probably a similar but customized functionality ('create PO automatic' is not typical unless you have an EDI relationship that needs this functionality). No matter, the solution is probably the same..
In this scenario, during Sales order entry, the system will normally propose a date to the order entry person, based on planned delivery time. If this person does not 'fix' the date at that time, then the system will create a purchase requisition with a delivery date that matches the requirements date of the Sales order, regardless of Planned delivery time. If the order entry person instead selects the 'Fix date qty flag' during order entry, the system will accept the standard Purchase Requisition scheduling (starting from today and including Planned Delivery time), and create a confirmation date in the Sales order that is consistent with the planned delivery time. The confirmation date then becomes the requirements date for the Sales order.
You can review the fix-date-qty flag in the sales order. VA03 > select item > then Goto > item > schedule lines. The Fixed Date and Qty is a checkbox in the upper left hand side. I am not in front of a system this evening, so I can't advise you if you change the flag and re-ATP the order, if the Purchase requisition will automatically be rescheduled. If it is not, you should be able to first delete the PR, and then set the FDQ flag in the SD order/item to get the schedule dates you require.
It is possible to have the fixed date quantity flag to be defaulted to 'set' if it meets with your business requirements. OVZJ > Select Sales Org/Dist channel/division. Set or unset as the default setting. You can always change this flag manually within the sales doc, regardless of the default setting, so there is little danger here.
Rgds,
DB49

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

Data from Info Records

Due to a vendor number change I need to extract data from an existing Info Record and load it again as a new Info Record. I have been looking for programs or BAPIs for doing this, but I don´t seem to find the way. Any ideas?

There are standard LSMW routines which all you do upload. You can extract the data from tables EINE and EINA. You can do this via se16 or you can write a custom program to do so. Format the data for your LSMW and upload. You also might want to try doing mass changes via transaction MEMASSIN.
Regards,
Rich Heilman

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

Expired validity price of Consignment Info record

For the consignment process we created the consignment info record with the pricing condition validity from 1.1.2008 to 31.7.2008. the consignment contract validity is from 1.1.2008 to 31.12.2008.
After 31 July the price was agreed to be changed, but the user forgot to change the price validity period of the consignment info record.
But still we are able to create the Consignment Po referencing the consignment contract with the old price validity period ending 31.7.2008.
Even the system has not given any warning message or stopped the user to make the Po though the price validity has expired.
In future how can we prevent this case?
Is there any message that can be populated at the time of Po creation if this case happens.
What shall we do with the goods that have come for the PO from 1.8.2008 to 10.8.2008, they are still lying in consignment Godown, he have not made any withdrawal against these POs.
Regards

Hi
i have tried this scenario in the test environment. i just happened with me. i have a consignment info record with the validity period which expired. even with that i could make PO and do GR. it didnt allowed me to do GI to my own stock. at that time it gave me the error that the consignment price is not maintained.
if you see by logic PO and GR could be possible for consignment stock or order. the liabilities are only created when we issue goods from consignment stock to own stock. at that time we need the price of the stock since we are not going to receive any invoice from the vendor about the price of the stock. its taken from info records.
please correct me if i am wrong.

Restriction of Validity start date in Info record ME11/12

Similar Messages

Maybe you are looking for