Setting Expiration period for Maintenance Plan Backups fails to work in sql server 2008

I have created a Maintenance Plan to do a nightly full backup and set the backup
set to expire after 4 days in sql server 2008 R2.
Weeks later, old backups are sitting on the hard drive.Please do the needful.
Can any one please explain what is the use of BACKUP Expiration ???
I created a backup with expiration date but still am using the same backup file to restore databases?? Then what is the use of Expiration date?

Similar Messages

Login fails when connecting to SQL Server 2008

There were 3 databases and a report server database on sql server 2008 r2. All were renamed. Now, when trying to connect to sql server I am getting a login failed error for default database. I'm guessing because the default db name was changed. How
can I fix this so that I can connect to the db server\instance?
Thanks

Hi ,
According to your description, I do a test in SQL Server 2008R2. If you use windows system admin account to log in the instance via Windows authentication, even if you change all use database name, you can still log in successfully. However, if you create
a SQL Server login name to connect to instance via SQL Server authentication, when you change the default database name, it will
occur the error which just like at follows .
//Cannot open user default database. Login failed.
Login failed for user '***'. (.Net SqlClient Data Provider), Error Number: 4064//
I recommend you change the default database any existing database on your server like master via clicking on Option , or you can run following statement for username
to replace your original database name with master.
ALTER LOGIN [login name] WITH DEFAULT_DATABASE = master
GO
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Java for PI 7.1 EHP1 in Windows and SQL Server 2008

Hi Gurus
I try to install PI 7.1 EHP1 in Windows and SQL Server 2008. The questions is :
What version of java is the correct for this installation???
And where i can download it??
Thanks and advance!!!

Hi Aaron,
The version for PI 7.1 is 1.5, instead of the 1.4.2 of 7.0/3.0.
Anyway, for VM settings, you should refer to SAP JVM, which
is used for the PI 7.11.
Hope it helps!
Regards,
Caio Cagnani

I Am Getting Failed Notifications When Installing SQL SERVER 2008 can any one suggest me Wt can i do

Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-07 08:24:10
End time: 2014-03-07 09:07:13
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xC71AA851%400x73BA6908
Machine Properties:
Machine name: HOME
Machine processor count: 1
OS version: Windows XP
OS service pack: Service Pack 3
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: E:\Projects\Sqlserver2008\x86\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: HOME\Administrator
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: E:\Projects\Sqlserver2008\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: HOME\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\SystemConfigurationCheck_Report.htm

Hello,
Please check below link
http://support.microsoft.com/kb/955403/en-gb
SQL Server enterprise edition is not supported on Windows XP.You can install but its not supported by Microsoft.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server 2008 R2 Backup jobs are failing

I have a problem with SQL Server 2008 R2. First the management studio package is failing to load. backup jobs on that server are failing to run. The server won't accept any installation. The Installation of .Net Framework failed, the Installation of SQL
server 2008 R2 SP2 also failed, Trying to repair SQL Server through the CD also failed. Actually the server cannot install anything on it. When you try to initiate the installation it comes back and say check online for solution or close the program.
I am desperate here as I cannot backup

When you try to initiate the installation it comes back and say check online for solution or close the program.
Are you sure this is the error, I updated SP2 last week and I got the same message but if I remember correctly there was a continue button as well. Could you post the errors.
SP2 not installing, .net framework not installing, ssms not loading up and backups not running all could be due to different issues. Consider these as different and post error message that you are receiving for the issue which is most important for you.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Backup Restore With SQL Server 2008 R2 although it succeeded with SQL Server 2008

Dears;
I have a Full backup of some DB of around 417 GB within SQL Server 2008 R2 , and when I tried to restore it , i get stuck several times with the error below :
Restore failed for Server (Microsoft.SqlServer.SmoExtended)
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider
running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical
Although I have restored
successfully other several Full+ Deferential backups for the same DB while it was in SQL Server 2008 not 2008 R2.
And so I have rounded all different possible assumptions for such common know error by Microsoft for SQL Server 2000, 2005, 2008 but
no way as next:
1-
I have attempted to restore it within 2 environments clustered and non-clustered of SQL Server 2008 R2.
2-
I have attempted to restore verify it and it was so fine .
3-
I have attempted to restore it using Continue_after_error ,no_checksum but no way.
4-
I have attempted to move Backup file to another Storage but no way.
5-
I have scheduled jobs to DBCC
Checkdb the live DB and it wasn’t any errors since long time right now
6-
I have also DBCC check all master +msdb+model+Tempdb ,and they are so fine
7-
I have also checked all I/O subsystem of SAN and Network controllers , but they are fine evidenced much more by my trial on 2 different environments.
8-
I have also checked Memory and it is so fine all the time since I have 128 GB memory and I control it also so well.
For DB Design +Structure :
It has 20 Files containing tables partitioned horizontal +Vertically
(Schema Partitioning +File Stream partitioning ) through these 20 files.
I have Data compression of the required tables only.
I have one table of more than 300 GB alone which is partitioned as mentioned above.
I have implemented Read Committed Snapshot isolation level using row versioning integrated so well with File stream technology since it is a new feature of SQL 2008 R2.
DB is in simple recovery model for garbage collection of all file stream data as a result of much Delete /update in images themselves.
So any one has any idea about such case..How to solve it…?

Hi Ashwin,
When i searched with no answers these are listed out. So i thought this is still existing. Now on wards let me check the data and time of latest reply. Thanks for guidance.
It was happening by oversight. Thanks for guidance.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/

Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

Shouldn't I be able to upgrade to 2008 R2?
Current version:
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

I've the same problem as described above.
My Version is: 10.0.2531.0 SP1
Standard Edition (64-bit), on Windows Server 2003
Additionally, I have SQL Server 2005 Developer installed on the same machine.
I choosed SQL Server 2008 to upgrade to R2.
In the log I found:
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' found no upgrade features.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_engine_core_inst_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package 'sql_engine_core_inst_ctp6_Cpu64' with SkuValue=STANDARD ProductVersion=10.0.1600.22
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition STANDARD for feature package 'sql_engine_core_inst_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=STANDARD sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix found match in sku matrix.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_engine_core_inst_Cpu64' permits upgrade.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_is_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Found feature package 'IS2005_Cpu64' with SkuValue=DEVELOPER ProductVersion=9.3.4035.00
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 9.0 and edition DEVELOPER for feature package 'sql_is_Cpu64'.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=9.0 sourceEdition=DEVELOPER sourceArchitecture=X64 targetEdition=STANDARD targetArchitecture=X64
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
2010-10-01 17:54:31 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_is_Cpu64' is blocking upgrade.
2010-10-01 17:54:31 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
2010-10-01 17:54:31 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
2010-10-01 17:54:31 Slp: Rule running on machine: <skipped>
2010-10-01 17:54:31 Slp: Rule evaluation done   : Failed
2010-10-01 17:54:31 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2008 R2 version and edition upgrade matrix in Books Online.
Thanks,
Patrik

Incompatible SQL backup on SQL Server 2008 R2

I installed SQL Server 2008 R2 from MSDN download for testing on a development server. I copied a backup from a live SQL Server 2008 R2 server and when I tried to restore the database on the MSDN downloaded copy of SQL the following error was generated...
"The database was backed up on server version 10.50.4033. That version is incompatible with this server, which is running version 10.00.2531....."
Any suggestions on a solution?

NO possibilities of backing up from higher to lower version.
only lower to higher is possible.
you can do this
upgrade this instance to SQL Server 2008 R2 or
restore the backup you have on a SQL Server 2008 R2 instance, export all the data and import it on a SQL Server 2008 database.
Mark as answer if it is useful

Status "Inactive" set for maintenance plan.

Dear all,
while doing
Maintenance plan-->functions-->Activate<-->Inactive-->Deactive for maintenance plan
which field and Table we can able to get the details,Status "Inactive" set for maintenance plan.
Required
Changed by, Changed on , Deactivated field
Regards,
U.Linganathan

Please refer MPLA table to OBJNR value.
Refer JCDS & JEST tables to get the Inactive Maintenance plans.
If Status I0320 is active in JEST table, then that Maintenance plan is Inactive.
Pass INACT is not equal to "X" & OBJNR = "WO*" to get all Inactive Maintenance Plans OBJNR values. Pass that in MPLA table & get WARPL value.

Problem with full backup with copy only in maintenance plan sql server 2008

Hello
I am starter DBA for sql server in general
I have problem related to backup with maintenance plan in sql server 2008 and 2008 r2
I created maintenance plan to take full back up with copy only option checked, but when I check the back up in backupset table is_copy_only column it shows 0 for databases that I run job for.
I did the same steps on sql server 2012 and I checked backupset table is_copy_only column it shows 1 for databases that I run job for .so it works as it should be
Note: all the servers I mention here are production servers

Copy-only Backup by using GUI ( SSMS) in SQL Server 2008 but it was not available in Maintenance Plan "Back
Up Database Task". Now in SQL Server 2012 It is included in "Back Up Database
Task".
http://sqlage.blogspot.in/2013/06/dba-maintenance-plan-back-up-database.html

No. range not found for maintenance plan

Hi Team,
I have maintained no. range for maintenance plan in SPRO. However I am getting this error while creating maintenace plan.
Thanks

Hi,
Check the number range customizing again via IP20. Use the groups option to ensure your number range interval is assigned to the maintenance plan category. Also check that maintenance item number range is maintained correctly via IP21.
-Paul
Moving to [Enterprise Asset Management (EAM)|Enterprise Asset Management (SAP EAM); forum

Iv just bought Ipad 2 for back home in UK in usa. I'm trying to set it up for the plane ride home on my sisters pc which already has itunes installed. Will I be able to sync it with my own PC back home.

Iv just bought Ipad 2 for back home in UK in usa. I'm trying to set it up for the plane ride home on my sisters pc which already has itunes installed. Will I be able to sync it with my own PC back home.

Yes, but all the data from your sisters PC will be erased and replaced with yours, which is probably what you want anyhow.

Table for maintenance plan and maintenance cycle and Unit

Hello,
I need to know the table where the values are stored for maintenance plan, maintenance cycle and Unit.
I know that we can get the maintenance cycle and unit from MMPT table.
Question 1
If the maintenance plan has only a single cycle then the data is stored in above table MMPT, but if a maintenance plan has mutiple cycles like 1 maintenance plan has maintenance cycle as 364 Days and 1092 days then the data is not stored in MMPt table.
Question 2
Requirement is I need to develop a report where in I need maintenance order, maintenance plan and the relevant maintenance cycle and unit. Supose an maintenance order is created for the above maintenance plan which has 2 maintenance cycle how can I identify for which maintenance cycle the order is created.
Regards,
Narendra

Hi,
Please review PM tables
PM/SM/SD Tables
MPOS                       Maintenance Items
AFAB     Network - Relationships
PLKO     Task list
PLAS
AFFH     Operations
PRT assignment data for the work order
AFFL     Work order sequence
AFFT     Order process instructions
AFFV     Order process instruction values
AFFW     Goods movements with errors from confirmations
AFIH     Maintenance order header
AFKO     Order header data PP orders
AFPO     Order item
AFRC     Table of planned changes to conf.: Automatic goods receipt
AFRD     Default values for collective confirmation
AFRH     Header information for confirmation pool
AFRU     Order completion confirmations
AFRV     Pool of confirmations
AFVC     Operation within an order
AFVU     DB structure of the user fields of the operation
AFVV     DB structure of the quantities/dates/values in the operation
MPOS     Maintenance ITEM
AFWI     Subsequently posted goods movements for confirmations
AUFK     Order master data
AUFM     Goods movement for order
MPLA     Maintenance Plans
BGMK     Master warranty header
BGMP     Master warranty item
BGMS     Text item master warranty
BGMT     Master warranty text
BGMZ     Warranty counter information
CRHD     Work Center Header
CRTX     Text for the Work Center or Production Resource/Tool
EQKT     Equipment short texts
EQST     Equipment link to BOM
EQUI     Equipment master data
EQUZ     Equipment time segment
HIKO     Order master data history
IFLO     Functional Location (View)
IFLOT     Functional location (TABLE)
IFLOTX     Functional location: Short texts
IHGNS     Plant maintenance permit segment
IHPA     Plant Maintenance: Partners
IHSG     Object-related permits in Plant Maintenance
ILOA     PM object location and account assignment
IMPTT     Measuring point (table)
IMRG     Measurement document
KAKO     Capacity Header Segment
KONP     Conditions (Item)
KONV     Conditions (Procedure Data)
OBJK     Plant Maintenance Object List
QMEL     Quality notification
QMFE     Quality notification - items
QMIH     Quality message - maintenance data excerpt
QMMA     Quality notification - activities
QMSM     Notification - Tasks
QMUR     Quality notification - causes
STPOA     Name is does not have an A at the end; BOM items
T001     Company Codes
T001L     Storage Locations
T001W     Plants
T077D     Customer account groups
T003O     Order Types
T352R     Maintenance revisions
T353I_T     Maintenance activity type description
T356     Priorities
T357G     Permits
T357G_T     Table 357G texts
T370A     Activity category for PM lists
TINCT     Customers: Incoterms: Texts
TVKO     Organizational Unit: Sales Organizations
TVKOS     Organizational Unit: Divisions per Sales Organization
TVKOV     Org. Unit: Distribution Channels per Sales Organization
TVTA     Organizational Unit: Sales Area(s)
VIAUFKST     Order selection view
MMPT Cycle detail
Regards
Carlos

Service products for Maintenance Plan

Hi All,
Is it possible to Create maintenance plan from a a Service product - Contract Line item(VA41)? I have come across the Tcode OISF but do not know how to make use of it?
Would appreciate if you could throw some light on this?
Pranav

Hello
You have maintained the following data for the service product that you subsequently entered in the outline agreement under Logistics --> Customer Service >Service Agreements>Environment -->Sales and Distribution -->Service Products:
·        Plant for maintenance planning
·        Work center
·        Order type
·        Plant of maintenance work center
·        Business area
·        General maintenance task list (you cannot assign equipment task lists or functional location task lists)
·        Task list type
Then-you have created an outline agreement that fulfils the following conditions:
1)The contract category is Contract.
2)The contract type is Service and Maintenance.
3) On the tabstrip Sales, you have specified
              I)the start and end dates of the contract
              II)service product as outline agreement item
4)You have specified the start and end dates for billing in the billing plan under Goto> Item>Billing plan.
When Creating the Maintenance Plan for Above Contracts
1)When creating a maintenance plan, you choose an appropriate maintenance plan category.
   Maintenance plan category with reference to an outline agreement, maintenance call object u201Cservice orderu201D
Enter the following data:
1)Valid outline agreement
Regards,
Rakesh

Table name with feild Duration of Task/Frequency , Change in Duration/Frequency for maintenance plan

hi experts,
i need a table for maintenance plan which has field
1) Duration of Task/Frequency
2) Change in Duration/Frequency
below i have elaborated my requirements.
among those fields i have got the table name mpos,mpla,plpo except the above listed two feilds.
i have to create a report with these requirements.
anyone tell me in which table can i get that 6 and 7th fields.
Requirement1:
Maintenance Plan Number
Operation Code
Standard Teode(assigned to Plan)
Standard Text Key description
Cost Center
Duration of Task/Frequency
Change in Duration/Frequency
Created Date
Created By
Changed On
Changed By
Requirement 2: layout of the report should be modifiable with the existing fields.
Requirement 3: A transaction will be created to access the report.
Requirement 4: In the report, Maintenance Plan number will be hyperlinked which will divert to AMP screen (display view of maintenance Plan) once clicked on it.
Requirement 4: Report should contain all created and changed Maintenance Plan details.
Requirement 5: Initial selection parameter for the report will be only Date. Based on the entered date, records created or changed during the duration should be picked up in the report.
Requirement 6: Change in frequency will only be picked for single cycle plan. Strategic Plan will not be considered in case frequency change made in it.
Requirement 7: Change By and Created By should be the complete name instead of User ID.
regards,
priya

can anyone answer for my above question?
regards,
priya

Setting Expiration period for Maintenance Plan Backups fails to work in sql server 2008

Similar Messages

Maybe you are looking for