Question on normal maintenance cycle in 4.0

Hi
We have a maintenance cycle for normal corrections. Due to missed authorizations, when our testers changed the status of the change request after successful testing, the status is changed to 'consolidated', but the transport requests were not released. When we manually released the transports from SCMA task list, system released all the open transport requests, whose tasks are released. This has caused the issue of these transports being added to the production buffer. So now we have the released transport requests for requests that are at the consolidated status and for requests whose status in less than the consolidated status, i,e. to be tested, in development. If the status of the MC is changed to 'Go-Live' and when the production import job is scheduled, is it going to move all the transports in the production buffer or only those transports that have the corresponding change request status is 'Consolidated'? Thanks in advance.

I believe that in later Service Packs of SolMan 4.0 the "Export transport request" and "Return to development" actions described in note 910506 are not part of the standard workflows so some of these problems should not exist. SolMan uses Transport of Copies functionality when the developer performs the Complete Development action. These "copy" transports only get imported into the QA system and not into production. When the tester performs "Confirm Successful Test", the transport is actually released.
Now if for some reason the tester made a mistake when "Confirming", the correct action would likely be to do an Urgent correction to repair the problem or undo the change.

Similar Messages

Maintenance Cycle Questions

Hi,
We have in the process of exploring CHARM feature. I have few questions:
1) Is there any possibility to have more than maintenance cycle. The reason is if i have a procedure like requests in the cycle goes into production every 2 weeks and i know that a new development in a particular case going to take 4 weeks to complete then what is the purpose of putting in the cycle which is scheduled to go for production every 2 weeks.
2) Also i found that when i try to close cycle it is showing what are all still left over in the status of Created, In Development, Successfully Tested to move out of this cycle and gets automatically attached when next cycle is created. By doing this what is the actual purpose of having a cycle when something can be taken out , why can't we have more than 1 cycle and have long process one in second one and possible short ones in cycle 1 ?
3) Is there any way of removing a request from a cycle whenever we want ? The reason for this question is say if have a X request which went till quality and found an error which needs a new one to be created and if the new one goes to production as urgent corr, and if remaining all from the cycle goes to production then the bad one goes and invalidate the urgent correction one, then i have to put the urgent also again into PRD, why to do like this twice ?
Thanks
Murali.

Hi Avinash,
Thanks for your reply. I checked the IMG proj created for this maintenance pro. in the satellite system (both Maintenance project and IMG proj in satellite system is ZMAINT_12 and it isshowing in satellite system SPRO_ADMIN, how to make sure it is active ? Another working project ZMAINT also looks same like thisnew one ZMAINT_12 in terms of all columns values, so the new one should be active. Let me know any specific place i can see it is active or not apart from seeing in SPRO_ADMIN with status as In Process.
Regarding shipment route it looks ok.
Regarding checking system landscape check, it looks ok except this message:
Logical component ZECC is not used in project ZMAINT_12 but it is GREEN color status. (ofcourse same thing is there in another working project ZMAINT also).
One more thing to mention is Under the Change Request tab where we activate the change request management for that project, next to the button cProjects Project Assigned there is nothing in the working project ZMAINT, but in this new one ZMAINT_12 it is showing a value called NONE. (Basically ZMAINT_12 is copied from ZMAINT).
Thanks,
Murali.

Photosmart 8250 constant maintenance cycles while printing & excessive ink usage

I'm having a problem with my trusty 4-year-old HP Photosmart 8250: Whenever I print a document, whether in color or black ink only mode, it constantly enters maintenance cycles and excessively uses ink.
Two examples: When I printed a color document (color, HP Bright White Inkjet Paper, 17 pages), the printer behaved erratically, with constant maintenance cycles. It also said I had to change yellow ink, but when I re-turned on the printer to install a fresh yellow ink cartridge (I only use original HP ink), it still showed remaining yellow ink. Then yesterday, when I printed a 32 page graphics document (black ink only, plain paper, normal), the ink meter for black dropped from full to 25% full (I had changed the black cartridge only one week earlier), and the printer went through four maintenance cycles. Neither had happened before in my four years of owning this printer, and the black ink consumption for similar documents in the past was barely a quarter of what it was for this document.
Are these issues most likely related to the printhead? I know that the Photosmart 8250, like all printers with HP 02 cartridges, uses a fixed non-replaceable printhead, so does the printhead need cleaning or alignment? Or should I just get a new HP printer, as I have used this printer extremely frequently over the past 4 years?
Thanks for all your help!

Hi johnpd,
There have been some significant upgrades to photo printing and the inks since the MP610 was introduced. With the MG7120, and the XL ink tanks (which are comparably priced to the standard ink tanks used in the MP610), you should receive similar or greater page yields. One major reason for this boost is the addition of the gray CLI-251 ink. When gray appears in your printout, instead of using a mixture of all the other colors, the gray ink is used, reducing your overall ink consumption.
At the risk of sounding like a typical salesman, "I want to get you in the model that is right for you"! If you are looking for a photo printer, the MG7120 is one of my top suggestions for a quality Photo All-in-One. If however, you do not plan to make heavy use of the printer and only occasionally print photos, you might get more value from an Office All-in-One.
Please feel free to Contact Us if you have any additional questions.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

Error "No maintenance cycle is open for the current system"

Hi,
I'm setting up the ChaRM for test purposes.
I have done everything according to SAP Expert Guided session requirements (like Basic configuration, Landscape and TSMS set-up) and also was reading and checking the following Blog " Change Request Management scenario: Working examples"
/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
Everything seems to be ok:
1) Landscape ok, IBase created and active, Partners assigned to each component
2) Maintenance project created and Maintenance cycle set to "Development with release"
3) I can easily create Change request (I tried Normal correction), approve it.
4) When I open Change Document for approved change reques - it gives error "No maintenance cycle is open for the current system" and I can't proceed with setting Change document status to "In development".
In Change Request I indicate the only IBase (1) and as Component - SolMan clent 803, whish is set-up like PRD.
What could be wrong?
I tried reading all threads but did not get solution - there were suggestions to activate maintenance cycle (in my case it active), to check if business partners are assigned to IBase components (in my case done),
What else?
Thanks in advance,
Ausra Gustainiene

Hi Ausra,
Please, take a look at this topic:
Change Request Management scenario: Usual questions and known errors
/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
17. Error: "No maintenance cycle is opened for the current system"
Best Regards,
Fernando Rocha

SDMJ assignment to Maintenance Cycle is done in wrong phase

Hello,
Since Solution Manager SP15 we have the following problem.
If you Approve the Normal Correction (SDMJ) the system does not ask you to which Maintenance Cycle you want to assign this NC (SDMJ). Before SP15 this used to work !
Now ... after SP15 the question is asked only at the phase of setting the Normal Correction "Into Development. so one stage too late !
Now, instead of the Change Manager, the Developer has to decide to which Maintenance Cycle a Normal Correction belongs to. This is unwanted behaviour.
Are there other customers, having the same problem ?
With kind regards,
Rik Vriens
+31.6.51937336

Hi
Please go to your project and PRESS REFRESH button in System landscape-Change Requests Tab
this update the entries in database then now
goto this table /TMWFLOW/PROJMAP
Check if the Project is still locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table.
The refresh button will help you to get out of this problem and check also if there any other errors.
Regards
Prakhar

ChaRM: Several maintenance cycles in one maintenance project?

Hi!
We are working with urgent correction within ChaRM and thinking about to implement the normal corrections as well.
Our ChaRM workflow for normal corrections is characterized by:
a)corrections with different Life cycle (those who will be processed within 1 week, other with 2 week, etc.)
Questions:
1) Is it possible to have several maintenance cycles for one maintenance project to handle condition u201Ca)u201D?
2) What will happen with all the normal corrections and urgent corrections that have a long life cycle (status: in development, test, etc.) when the charm manager set the status of maintenance cycle in u201CGo liveu201D?
Thank you very much!
H. Thomasson

Hi Holger,
Maintenance cycle and SMI project is a 1:1 relationship.
In status GoLive you will be able to continue developement/work on normal corrections but you will not be able to release any transport requests/create transport of copies so your testings in QA will be limited.
In phase GoLive you are able to import requests into production.
Normal Corrections which have not been released yet are not lost. Depending on your scenario you may switch phases back to "in dev with rel." after you imported into production. It is not necessary to close and recreate maintenance cycles if you use one project for daily/weekly maintenance.
/cheers

Multiple system maintenance cycles are not shown in pop up for selection

Hi,
In change manager, when we create a change document from a change request, we dont get a pop up for selection of maintenance cycles with multiple systems in it.
The change document is getting created by taking the only available maintenance cycle with only that system.
Is there any configuration for this?
Regards,
Dipti Sawarkar.

Hi Christian,
Thanks for your reply.
I know the pop up will come only when there is more than one maintenance cycles for that production system.
I have done configuration for Normal correction.( SDMJ) and customized it (ZDMJ).
When I try to create a CD* from CR* for a particular production system ( CCP) , it just takes up a maintenance cycle for CCP system and doesnt show up any pop for selection of maint cycles whereas I have created 5 maintenance cycles for this system CCP.
The other 4 maintenance cycles have multiple landscapes (CCP and EAP )in it whereas this one (which gets selected by default) just has CCP landscape in it.
The strange part is that when I try to create a stand alone CD ( without CR ) , it will give that pop up showing all 5 maint cycles. But this is not happening when I create a CD from a CR.
I have never done/ seen configuration for the pop up of selecting maint cycles in ChaRM.
Looking forward to ur help,
( *CD - Change Document and * CR - Change Request)
Regards,
Dipti Sawarkar.

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

Inconsistency with maintenance cycle and task list phases in ChaRM

Hi Experts,
I'm deploying ChaRM with SolMan 4.0 SP09.
I was testing a scenario where there are more than one maintenance project open for same landscape (different logical components but values are the same). I have been using maintenance cycle document (in crmd_order) to control phase changes both in task list and in maintenance cycle.
I received an error message stating that the system has reset the status of the maintenance cycle and the end result was that task list phase is one step ahead of the maintenance cycle. This of course causes the situation where certain actions are no longer possible (maintenance cycle in Dev with release but task list already in test => release and import are not possible and reseting phase with task list is prevented by ChaRM).
My question is how do I restore the inconsistency. I have looked for notes (but of course this is not a notes issue) and the internet for solution.
I am very greatful for any hints you may give me!
Kind regards,
Auli

Thank you!
Exactly what I'm trying to do. I'll give it a go and get back to you asap.
BR
Auli

Solution Manager - Import buffer and duplicate imports in maintenance cycle

Hello,
I am trying to understand how Normal and Urgent Correction work in a maintenance cycles.
I am using SOLMAN 4.0 and I would like to know how the import buffers are managed.
When I have completed a maintenance cycle and all my transport request have been imported in the production system, I want to switch the status of the maintenance cycle back to development in order to complete my previous open normal corrections. I have read in many places that if I act in this way, not only my new corrections but all the old correction will be imported in the quality and production systems because the import buffers do not get empty.
For example, If I decide to have 10 normal corrections but eventually only 9 corrections are imported in quality and production systems, when I switch back to development and I complete the 10th correction, this correction will be imported together with the other 9 corrections or this will be imported alone since the other nine correction have been imported before?
How it works?
I appreciate suggestions.
Thanks
Antonello

Hi Gert-Jan,
We do the same and we don't face this issue. There is thus a solution.
I never had this case, this might be a parameter in your QAS refresh procedure.
1/ If you empty your production import buffer (meaning you import it all to production) before tacking the production copy you will never have this issue.
2/ If you have some transportd left in the import buffer of production , you have this issue ? I guess this is our case
I will try to reformulate the case.
The refresh of QAS is causing the lost of some customizing that were not yet imported in production but was imported in QAS prior to the refresh of QAS.
When you reimport the "overwritten" transports in QAS after the refresh, this transport is removed from the QAS import buffer and going too the import buffer of production.
A/The same transport is now twice in the import buffer of production ? we don't have this in our landscape (I even think this was not possible)
B/Or in between this transport has been imported in production and thus you are right it falls in the import buffer of production again with another sequence.
Thank you to confirm your case A or B ?.

Assigment maintenance cycle -- system (IBASE) in CharM

Hello!
I have the problem to establish CharM functionality.
When I try to set a urgent correction in status "In Development" I get the following error:
No maintenance cycle is open for the current system
My question are:
- How do this assignment maintenance cycle <--> system (IBASE) work?
- Is it perhaps possible to execute this assignment manually?
- Is there some log files that can be analysed for this problem?
Thanks & regards
Thom

Hi,
About this issue, there is a detail information about this in blog point 6 u201CChanges in the logical components of a project where Charm is already activatedu201D.
This is the link: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15116
So, you have to change the transport route accordingly and then close current maintenance cycle and generate a new one.
Following is the steps.
1: please import all the transport requests which were associated in the current maintenance cycle task list by STMS manually import.
1: change transport route from DEV > PREPROD >PROD to DEV > USER > PROD on the domain controller system.
2: close current maintenance cycle.
3: change the system landscape to DEV > USER > PROD in solar_project_admin.
4: generate a new maintenance cycle.
Thanks
Regards,
Vikram

ChaRM Error - "No maintenance cycle is open for the current system"

Hello All,
I am setting up ChaRM in development system after EGI session with SAP support. I have copied standard transactions to custom ones and created Maintenance and Implementation project to run test of all scenarios.
I now come across error of "No maintenance cycle is open for the current system" after I create a change request and in the change document, I cannot see it link with task list and the error message is displayed. I tried it with custom transaction as well as standard SAP transaction (SDCR) and get the same error.
What links a document to a maintenance cycle? Where can I see the config of this setup? I am trying to see where it is broken. I am using the correct IBASE number (production client in logical component), I tried to create a new logical component, new projects with correct settings but it still gives this error message. Please advice.
Thanks and regards,
Nischal

Hi
did you also unlock the maintenance cycle and open for changes in solar_project_admin by right click
do check this blog
/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples-final-points-and-appendix
Question no 17
/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
Hope it solves
Regards
Prakhar

Error "no link to maintenance cycle" happens after reset to previous phase

Experts:
I have a CHaRM project which has successfully transported a few changes into production.
Then I use action "set to previous phase" several times to set this project to "development without release".
Then I create another change request by selecting the maintenance cycle of above project.
After authorizing and saving above change request, a normal correction is created. However this normal correction
has an error "no link to maintenance cycle" even its document flow shows the maintenance cycle mentioned above.
The IBase is the same as previous selected and is verified to be right.
Could you help decide what else is wrong?
Thanks!

Hi
Please go to your project and PRESS REFRESH button in System landscape-Change Requests Tab
this update the entries in database then now
goto this table /TMWFLOW/PROJMAP
Check if the Project is still locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table.
The refresh button will help you to get out of this problem and check also if there any other errors.
Regards
Prakhar

Maintenance cycle - Charm

Dear All,
I am in process of implementing CHARM and i am facing issue in the process flow for maintenance cycle.
In normal changes - we create change request and a maintenance cycle (MC) is attached to it. Once we change the status to Dev with release then changes are moved to Test system (transport of copies) and after successful testing (actual transport request is released) we change MC status to Test then changes moves to Test system. Then MC moves to Go live and then changes are imported to production. Now when status of MC is go live then we need to change the status back to dev with release which is not working instead it gets insync with the project phase. Kindly let me know if anyone has faced the similar situation.
Can you someone please clarify how mc status should work in case of normal changes.
Regards
Sushant

Hi Sushant,
1. try to change the phase of the project cycle without assigning any Change Document to it .
2. Number Ranges
"Before you can begin using Change Request Management transaction types, you must ensure that a number range is defined for these transaction types. The number range interval determines the sequential numbers assigned to newly created transactions. "
To do so you can use transaction SNUM and enter CRM_SERVIC as the number range object.
The number range interval which the system uses is defined in the transaction customizing in the Transaction Numbering section.
Please check the below link for more details in 3.2.7
https://websmp208.sap-ag.de/~sapidb/011000358700001056012011E.PDF (3.2.7)
Rg,
Karthik

One maintenance cycle?

Some consultants are stating that it's better to have 1 maintenance cycle per system in solution manager and keep moving the phases back and forward (thus: after go-live the phase is being moved back to "development without release" and from there a new normal correction can start). But can somebody explain to me <b>why</b> this is better than closing a maintenance cycle at the end of a normal correction?
Thanks in advance!

Hi!
I personally wouldn't recommend that but it sounds like an alternative method of handling parallel development for multiple release. At least in the project I'm in, there is a need to handle two or more simultaneous business releases with different go live dates.
Idealistically there should be only one maintenance project and subsequently one maintenance cycle per system. A release (=maintenance cycle) is planned, executed and delivered. End of story. But in reality this is not the case. Planning and executing next cycle is usually started while the previous has not yet gone live and this is something that is hard to handle when you can have only one maintenance cycle at the time.
I'm guessing that the idea of going back and forth with cycle phases is to use certain functionality of one phase but still keep the previous phase functionalities and enable parallel development.
Having two or more maintenance projects and subsequently many maintenance cycles in order to enable parallel development is risky and it doesn't work well. Trust me I've tried. With more project than one in the same system you easily end up with inconsistencies etc.
Hope this helps even a bit!
BR
Auli

Question on normal maintenance cycle in 4.0

Similar Messages

Maybe you are looking for