Validity date

Dear Experts
My problem is i need to change the Validity to date in inspection task list which is defaulted as 31.12.9999 and which cannot be edited.
Surender

Dear,
Go to t.code "CC02 or CC01". Just beside effectivity date field , you will see a icon. Click to that icon , you will see a date-lower limit and date-upper limit. Enter the dates you want and do not click the check box "date indicator" then assig it to task list.
You create a change request ( change no.) For this change number you need to define effective date (10.11.2008) and validity date(10.12.2010). Now if you make changes to task lsit using this change no. should be valid for 10.11.2008 to 10.21.2010.
Create a Change note number using CC01 define your dates as per your requriment. Then use this no in task list, system will act according to date of change no.
Pl go throught the link
http://help.sap.com/saphelp_47x200/helpdata/en/d8/7329d14b7511d1894b0000e8323c4f/frameset.htm
Regards,
R..Brahmankar

Similar Messages

Error messege- Please enter a valid date in Background Job

Hi all,
background job which is scheduled in sm37 is giving error for dated 01.01.2009 to 30.01.2009.
But before 31.12.2008 it was working fine
error messege-
This is happening in Production and developement client.
While running the report it showing the error messege- Please enter a valid date
One function module is used in the report for geting fiscal year from date.
it is showing the following error messege for perticular date range- 01.01.2009 to 30.01.2009.
GM_GET_FISCAL_YEAR
Error
Fiscal year variant V3 not defined or maintained for date 01.01.2009
Thanks
Susanta

Hi,
Did you put the date fields to be dynamic in your variant? i.e if in your variant you specified date range of last year, this will not work for this year and eventually give you an error message that the date is not valid...
Dev.

Error messege in Background Job(SM37) - Please enter a valid date

Hi all,
background job which is scheduled in sm37 is giving error for dated 01.01.2009 to 30.01.2009.
But before 31.12.2008 it was working fine
error messege-
This is happening in Production and developement client.
While running the report it showing the error messege- Please enter a valid date
One function module is used in the report for geting fiscal year from date.
it is showing the following error messege for perticular date range- 01.01.2009 to 30.01.2009.
GM_GET_FISCAL_YEAR
Error
Fiscal year variant V3 not defined or maintained for date 01.01.2009
Thanks
Susanta

Hi,Because this datein the past

BOM Valid Date

Hi,
While creating BOM due to some human error we took wrong valid date.Now i want to change it.
Please suggest me the T-code or any customization to change the same.
"I am online"

Dear Pawar
This are the basic IMG settings in order to used the engineering change management
features.
x refers to a tick.
First setup the control data in OS54.
Revision sections
Fields :-
Revision level active            x
Ext. revision level              x
Higher revision level            x
Object Management Record sections
Fields :-
Object maintenance               x
Assign alternative date          x
Overide value/assignment date sections
Fields :-
Only with leading change mst.    x
Setting the Revision level active is to activate the engineering change management for
material master. If you do not want the engineering change management for materials,
remove the tick.
With a tick in "Higher revision level", the new revision level has to be always higher
than the old revision.
Secondly, setup the external number range in OS53.
If you use the internal number range, then remove the external number range.
Third, define the status for the change master records in transaction SM30 - V_T419S.
Change No.     Chg        Date Chg     Dist. Lock      Description
Status         Poss
1             x            x             ' '         Active
2            ' '          ' '            ' '         Inactive
3            ' '          ' '             x          Locked
Fourth, define modification parameters for the BOM in OS27.
Fields :-
BOM Validty Maint.               x
EC Management Active             x
History Requirement             ' '
Unit Piece                      PC
The rest of the fields are blank.
If the History Requirement is tick, every time during creation of the BOM, SAP will
prompt your for an ECN number as is compulsory.
Lastly, define fields selection for routing in OP5A.
PP task lists: initial screen -> Change number -> Transaction code -> Tick Req.
Setting the Transaction code fields Required indicate that you have make the ECN number ........
Hope this will help you one of our friends gave me this
Pavan

Regd : How to find Validity date for a user in central user system

Hi Experts;
I want to get the list of users with profile SAP_ALL with following details like validity ,user type ,user name ,user id..
I can get through SUIM for each individual systems.Its very difficult to login to each system ,generate the report.So I prefered to go for Central system
But if I use central user system I have no option to find validity and user type for the system ( SUIM - > Cross system application )
I have also tried to the table USRO2 ( which gives only the list of users in the central system )
So is there any possible ways to find the Users with profile SAP _ALL with validity date in the central user system. So that I can easily generate it as one report instead of logging to each and every system
Regards
Sanjeev.S

Hi Ruchit
Thanks for your reply. I want to find the validity date of all users having SAP_ALL
profile of all child system connected through central user system .So it is possible
to do that in Centrals System by executing the report?
If I execute that report in Central user system will it give the details of all child
system connected to central system
I think it will give only the result of Central system and not the child system connected to Central system.Please clarify me.
I can execute the report by logging to each child system ,but it takes very long hours for me since there are many system in my landscape.
Awaiting for your reply.'
Thanks
Sanjeev.S

IPhoto says it cannot import my photos b/c they may be an unrecognized file or the file may not contain valid data. The operation could not be completed. Error code is: ImageCaptureCoreError-9905.

Unable to download photos from my camera. iPhoto returns an error message that states: The following files could not be imported (they may be an unrecognized file or the files may not contain valid data). FILE NAME: 100_0490.JPG REASON: com.apple.ImageCaptureCoreError- 9905. WHAT'S UP WITH THAT? Did not have a problem importing photos under the LEOPARD OS, however, now that I have upgraded to Yosemite 10.10.3 the iPHOTO app is not performing the imports.

Are you using Photos, or iPhoto? Maybe you've got a corrupt file on your camera. I would try using the image capture application to import the bad picture to my desktop. If it works and the picture looks ok, then delete that pic from the camera, then try to import into iphoto again. You can then import the pic it was saying was bad from your desktop.
Or, try downloading all the pics using image capture and then import from the download folder.

Validity date in RFQ

Hi all,
Can anyone explain me what is the correct definition of the Validity start date and end date in the RFQ.
The reason I am asking this question is , If you eneter the start date and end date in the RFQ and create the PO with reference to RFQ, these dates gets copied on to the PO. if the document type of PO is NB then these fields are not visible on PO screen bu in the background the table EKPO is updated with these two filed. And the if you try to eneter the SES after these dates sysetm is not allowing and giving the message as SES date is beyond the valididty date.
Has any one come across any such issue. Can any one suggest any solution to this.

Hi Don,
RFQ means...requesting quotation from a vendor. Validity date start and validity end means the quotation should be send before the validity end date from the vendor. Before getting the quotation and before knowing the rate, how could you make purchase order to that vendor. Before you rise PO, you should maintain the quotation in ME47. As per standard SAP, you should rise po w.r.to quotation.
Regards,
Prasath

Mass extention of service entry sheet condition record validity date

Hi all,
I have immediate requirement. i need to extend the validity date for condition record related to the Service entry sheet. This has to done mass sheet changes.
I am looking for Any bapi or Standard function module or any config changes.
I am looking forward for your valuable inputs.
Regards,
Sreenivasa Sarma K

Arun,
This doesn't suprise me...
I'm not sure if there is a standard solution, but you could do this via user-exit/BADI (see [here|http://www.sapfans.com/forums/viewtopic.php?p=648307] under maintenance plans )
PeteA
[www.pjas.com]

DMS Document Validity date issue.

Hello All,
I have an issue in DMS Valid from Date & Valid to date as below.
In our Document type when our document status is set to OB i.e. obsolete, in front of the status, system is showing two dates like 22.01.2014 to 31.12.9999.
We are not using change number functionality in this document type. But still system is showing two dates. When document is in RE i.e Release status system is showing 22.01.2104... date in front of the status.
Could you please let us know why it is showing two dates in front of document status.
Thanks

Hi,
from my point of view I can inform you that these dates are validity dates for the document. Normally these dates are filled when the document is released to show which version of the document is valid or was valid in a specific period.
By using menu "Extras" >> "Versions". Here a list of all versions should be displayed and the columns "Valid From" and "Valid to" should show the validity dates.
Normally these date values are only filled when the status has set the "release" flag in transaction DC10.
Best regards,
Christoph

Changing validity date using BAPI_PROFITCENTER_CHANGE for a profit center.

Hi Friends
I need your help to know if we can use BAPI_PROFITCENTER_CHANGE to change the validity period of a profit center.I am using this BAPI in a LSMW program.
The changes I want to make are something like changing the validity dates from
1) 01/01/2006 - 12/12/9999 to 01/01/2007 - 12/12/9999
2) 01/01/2006 - 12/12/9999 to 01/01/2005 - 12/12/9999
3) 01/01/2006 - 12/12/9999 to 01/01/2006 - 12/12/2010
or should I use BAPI_PROFITCENTER_CREATE?
-Thanks
Mitesh

change document in profit center change
Bapi - BAPI_ASSET_ACQUISITION_POST
need a function module for profit center
Please give me reward points...

How can I set an validity date for a given vendor?

Hello,
we are currently trying to set a "validity date" for vendors.
Basically, our vendors need to be audited, and are "accepted" for a period of time, beyond which we'd need to re-audit them.
What we'd like the system to do is block use of the vendor if this date was exceeded.
Anyone has an idea on the way to achieve this?
PS: We know that there is a way to do this at the material level, we instead wish to manage it centrally for the vendor
Tx

Hello Nisha,
before doing business with a new vendor for services, our QA group needs to go thru a serie of verifications. We check various things such as insurance, certification,...
Once "approved", the vendor can be utilised by the plant for a certain period of time, after which a "re-audit" is necessary.
What I'd like to implement is a field where the QA group would enter this date, after which the vendor would be automatically blocked for usage.
This would then trigger the "re-audit" followed by the release from QA (who'd re-modify the date with the new one), and so on.
The vendor is not necessarily used for supply chain. Sometimes, it could be for services , maintenance, or other.
Tx for the ideas.

ALE BOM. Updates ALL! items with validity date & change no.

Hi All,
We are having problems where ALE-BOM sent with change in validity date (with change no) to a particular item. What happens is that ALE-BOM will instead update ALL! items with the same validity date and change number.
Next,when we process ALE again for the same BOM with a different validity date(with change no), then only that
particular item is updated with validity date and change no.
Would anyone know what could be the problem that when changes are sent for the first time all items are updated?
[Version: SAP 4.6C/ SAPKH46C48]
Regards,
Neeth

Dear:
The error itself telling you the correction. You profit center which is assigned to your cost center has a validity date less than the one you are now assigning.You can check in KE52 against the profit center assigned to your cost center master data. However the best thing is to go to KS01 and create this cost center with desired validity date.
This will resolve your issue.
Regards

Validating Date

Hi, I'm trying to validate a Date. I want my code to only get dates in the "dd/MM/yyyy" format, but it's validating dates that only have 2 years digit. What should I do to force the user to set dates with 4 years digit??
Here's the code:
try {
SimpleDateFormat lDateFormat = new SimpleDateFormat("dd/MM/yyyy");
lDateFormat.setLenient(false);
Date fecha = lDateFormat.parse(strDate);
} catch (Exception ex) {
Note: for example I pass "01/01/69" and it returns to me "01/01/0069" ....

What you want to do is use yyyy as the year. As the documentation says, Java will interpret 2 digit dates to be in the range you want. If you use yyyy, you force it to assume a valid 4 digit date. So 63 is assumed to be 0063, not 1963. yy forces it to assume the century as you wish. Here is the documentation for SimpleDateFormat:
When parsing a date string using the abbreviated year pattern ("y" or "yy"), SimpleDateFormat must interpret the abbreviated year relative to some century. It does this by adjusting dates to be within 80 years before and 20 years after the time the SimpleDateFormat instance is created. For example, using a pattern of "MM/dd/yy" and a SimpleDateFormat instance created on Jan 1, 1997, the string "01/11/12" would be interpreted as Jan 11, 2012 while the string "05/04/64" would be interpreted as May 4, 1964. During parsing, only strings consisting of exactly two digits, as defined by Character.isDigit(char), will be parsed into the default century. Any other numeric string, such as a one digit string, a three or more digit string, or a two digit string that isn't all digits (for example, "-1"), is interpreted literally. So "01/02/3" or "01/02/003" are parsed, using the same pattern, as Jan 2, 3 AD. Likewise, "01/02/-3" is parsed as Jan 2, 4 BC.

Maintain Validity Date for Documents

Hi
Any Idea how can we put and maintain Validity Dates for any Document uploaded in DMS Server.
Validity Dates here means (Documents cannot be used if validty is over)
I could not find any option in CV01* T-Codes.
Regards

Dear Prasant,
You can also do this solution also if you find it OK.
1. Create a Class with "Validaty Date" as characteristics. Assign this Charac to class. Assign this class to doc Type. This charac should not be editable to any one except creator.
2. Create a program with BAPI " Set Status" ( Check the name). which will run in background to check the validity date of Document. If the validity date is reached the BAPI will change the status to "S" as stated by Chritoph.
This will help user to manually tracked which documents have exceded the validity date. You can also genegrate report and mail it to particular user that what documents have been set to Status "S".
Hope I have provided a valid solution as I have tried similar kind of functionality with changing a characteristics with Date.
With warm Regards
Mangesh Pande

IVL License and validity date

Hello Experts,
How do you apply an IVL license to a sales order that was placed before the validity date of the license?
The business scenario that I have is a sales order was placed in September, and it required a license. We applied for the license and recieved it recently and the validatity date is December 2010 thru December 2011. The license was maintained in the system as such, but the license will not apply to the order since it was placed prior to the stated validity of the license because the document reference date that is being used is the date the order was placed. Is there a way to account for this without having the sales rep replace the order so the document reference date is inside the validity date of the license recieved from the government?
Regards,
annm

hi
In your GTS system go to Transaction- /n/SAPSLL/LCD_CHANGE and delete the existing license from the existing order.
Then go to transaction- /n/SAPSLL/CUHD_MR_EXP and check boxes of "Display Log" and Save Log" and execute it with order number. New license will be assigned to it but make sure you have maintained the correct license determination strategy for it.
Thanks
DG

User lock / Validity date?

Hello IDM Gurus,
I needed your insight on an issue we're facing; Using standard tasks from the SAP provisioning framework, we have a task that locks a user in a connected SAP system; and we have another task that sets a person's validity date to today's date (basically invalidating their account by the following day); After locking a user using the task we then go ahead and set the same user's validity date as today's date; as a result of this, the administrator lock set previously ends up disappearing. I don't believe this is normal behavior; shouldn't a validity date and an admin lock exist independent of each other? Is this happening because of the way the SAP Provisioning framework sets a validity date?
Would greatly appreciate any advice and insight on the issue!
Thanks a lot in advance!
Best regards,
Sandeep

closed.

Validity date

Similar Messages

Maybe you are looking for