Maintenance Cycle Order deleted

Hi all,
Due to bad authorizations somebody deleted the maintenancecycle order. The order with transaction type SDMN. Now, when we change de status from "Created" to "In development" an error message is raied: No document found. That's because the relation to the maintenance order has been deleted by deleting the maintenance order.
Is there a way to retreive the maintenance order and it's relations ????
If not, what's the best thing to do in these situations ??
Kind regards,
Gert-Jan

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

Similar Messages

Import of maintenance cycle with deleted transport requests in queue

We use Solution manager 7.0 with one maintenance cycle per satelite system landscape.
In this maintenance cycle Regular corrections and Urg. corrections are used.
When a transport request (connected to a correction) is re-imported into the quality assurance system.
The transport request triggers a deletion and "add to buffer" of the same request into the import queue of the production system.
The sequence of the transport in the production queue is correct before the "import all" into production is triggered via the tasklist of the maintenance cycle.
During the "import all" of the maintenance cycle into production the re-imported requests are pushed to the end of the importqueue.
The re-imported transports are imported last in the sequence and left in the importqueue.
The deletion of the request in the import queue causes this problem.
Re-importing a request is sometimes unavoidable (E.g. after a client copy to QAS).
All our satelite systems have a 3-tier landscape with a simple transport routes configuration.
We are looking for a solution to problem, this can be either technical or adjusting procedures.
Kind regards
Gert-jan Meijer

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

IW21 Retrieving the maintenance cycle text while creation of work order

Hi Experts,
My requirement is to display the maintenance cycle text on the print preview while creating a work order via transaction IW21.
Since the print preview is clicked before saving the work order, the data from the work order has not been updated in the database tables (AFVC, PLWP).
Hence, the maintenance cycle text will have to be accessed through a runtime structure.
The text has to be fetched in a subroutine program which is called from the SAPscript.
I tried accessing the global data while debugging. However, the maintenance cycle text does not seem to be present.
Please help.
Regards,
Anusha

It is inappropriate to produce a SAPScript prior to save, IMHO. What prevents the user from changing something after the print preview was done in this case?
At any rate, you'll find that some data values, like document numbers, etc., are not set until the user has saved the document. The document needs to be saved, and SAPScript generated at the end of that process.

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

No maintenance cycle is open for the current system

Hello!
I have problems to use CharM functionality due to following error:
<b>No maintenance cycle is open for the current system</b>
The error arises when I try to set a urgent correction in status "In Development" I get the following error, menwhile I have an valid maintenance cycle active.
I use CharM functionality for the solution consisting of an single system with two clients:
SRM:000 (as DEV-system) (system role: source system)
SRM:100 (as PRD-system) (system role: target system)
- No maintenance cycle is open for the current system (meanwhile I have a valid maintenance cycle created and activated).
Futhermore I get the additional warning:
IBase component is not a productive system in system lanscape
Can some help me with this issue?
Thank you very much!
regards
Thom

Hello Kriti,
thank you very much for your response.
Unfortunately I also thought about it.
Basically my CharM procedure looks as follows.
I send the message from productive client (I have only one system with client 000 and 100) to Service Desk in SOLMAN.
There I can see the IBase of the productive client.
Then I create a urgent correction by assigning IBase to this IBase of productive client. It is also possible to change the IBase in change mode, so I have tried all the possible values of IBase and get the same error.
My problem also is that I have multiple values of IBase assigmenets, it means one system has multiple assigments to IBase components.
I do not know how to delete/cut these settings....
Thank you for your further help!
regards
Thom

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

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

ChaRM - Multiple Maintenance Cycles

We now have a Quarterly release cycle; however, we'd also like to have a Weekly release cycle for the smaller break / fix changes that are not true Urgents. We don't want to use UCs for these since we'd like to move them together on Saturday morning. How can we prevent leapfrog issues? For example, if an object is on the Quarterly and Successful Testing is recorded, the object is released. If the the same object is now changed and included on the Weekly Maint Cycle and moved to production, it will be overlaid when the Quarterly Maint Cycle is moved to production. I don't think this is possible, but I was asked to confirm..... Is it possible to re-import all of the Transports from previous weeks at the time the Quarterly ones are moved to ensure all Transports are moved in the order they were actually released? Is there a way to detect / prevent leapfrog issues? What do other companies do?

If you use normal correction for your quarterly release and SDHF corrections for your weekly releases, the normal correction will move ALL transports for the maintenance project including those which are for the SDHF corrections and even those for which the SDHF correction has not been approved for production import.
If you are only using SDHF variants for your process - then there is a possibility to handle this manually through the maintenance cycle directly. There are mass transport move tasks in the task list of the maintenance projects. However, this will require a manual element to your process for the production import.
But as you may already be aware, either of these options are tricky to implement and you need to have someone with a good understanding of development and transports.
Hope this helps...
Cheers
Pranav

Payment order Deleted

Hello Experts,
I have a query as below,
Vendor master created with Payment method C(Cheque) -No payment order configured in FBZP
Customer has been assigned in Vendor master and Customer has been created with Payment method Q(Payment method configured(FBZP)_
MIRO posted for Vendor and System included for payment proposal and Payment order has been posted for Vendor line item
Not sure how user has deleted the payment order,Upon checking table PYORDP, System resulted No entry exists.
Now after payment order deleted i can still see payment order exist in line item i.e. in document
If we try to execute payment now system doesnt considering this line item for payment.
Please tell me the way forward on this
Note:-Sorry with my presentaion as i am new to SCN
Regards
Kiran

Hello Jayj,
Thanks for the reply,
But as i already mentioned above user has already deleted payment order, and it doesnt exist in PYORDH and PYORDP respectively.Meanwhile even after deletion i still can see Payment order in line item of the docment and because of this system doesnt considering this for F110.
Please tell me how can make this entry considerble inF110
Regards
Kiran

Payment Order deletion

Dear gurus,
I need a help in APP.
In Autometic payment program our client is using payment orders. While clearing from the bank due to some techinal issue open item has not been cleared but clearing document has been created against the vendor.
This transaction is happend in 2001 fisical year. That payment orders deleted from the data base. Due to that i am not able to clear the payment order in the vendor invoice.
In this senario, is there any way to delete the payment order in the vedor invoice.
While testing in DEV,i deleted the entris from REGUP & REGUH. Even it is not working.
Please suggest me how to slove this issue.
Regards,
Ramana
Edited by:

This issue solved.

Change Maintenance Work Order Detail Report in Print WO page

Hello,
I would like to ask you for your help. We would like to have different report in Print WO function than Maintenance Work Order Detail Report. I mean SSM responsibility > Search for WOs > click Print WO icon. We applied patch #9871500 (I found it there: Templates associated to datadefinitions other than 'EAMWRREP' are not shown in the Work Order Detail report in EAM [ID 1209703.1]). I did personalizations steps - I defined new data definition (for example TEST) and report with data definition TEST is shown in the option on Print WO page now... But how should I it define to have correct result? What should be defined in Executable, Concurrent Program, Data Definition and Data Template? I have RDF and RTF files for this report. We are using different SQL than it is used in the original report. How could be used our SQL defined in RDF?
Thanks, Regards,
Jitka

Hi,
1) You can choose to select and Print shop paper when you need.No enhancement is required.
2) There is not an option in standard to say Print/Not print Long text . You will have to replace the standard form with a custom form and build the logic to print /Not Print long text based on your rules.
Regards
Narasimhan

EAM Maintenance Work Order Detail Report

Hello All,
I have a requirement to add new fields to the Maintenance Work Order Detail Report which is run from the web page. This report's RTF template works based on the fields which are defined in the seeded data definition. This seeded data defintion has an seeded XSD file with the fields in it. By the RTF template I got the standarad concurrent program name as Maintenance Work Order Detail Report.
I assumed the following process to happen when the Run button on the EAM work order page is clicked.
1. Concurrent program Maintenance Work Order Detail Report is submitted
Executable: PL/SQL Package EAM_WOREP_PUB.Work_Order_CP
Seeded Data Definition: Work Order Details -- This DD has a seeded XSD file EAMWOREPORT.xsd
2. So the RTF template based on the pl/sql package and the XSD file generates the report and displays.
Please correct if my assumptions are wrong.
I want to add new fields to this report. So I have customized the pl/sql package, modified the code with new fields and created a custom data defintion with a new XSD file with the new fields added in it. Also created a new template linked to new data defintion. After doing all this I am not able to see the new fields on the report generated they come as NULL.
My question is Is it feasible to add new fields to this Maintenance Work Order Detail Report or we can use only the fields which the seeded one gives?
Version: R12.1.2
I tried and tried but couldn't find a solution to it. If anyone has faced the same issue please let me know.
Thank You!!

IW47 should give you the required information.
Regards
Narasimhan

How to Change Maintenance Work Order Report in EAM Maintenance Super User

Hi,
We like to change or create new costom report in place of Standrd EAM Maintenance work order details report in Maintenance super User Responsibility.
When we go Maintenance Super User > Work Order > Print work order >Layout , In Template layout we find only one LOV called Maintenance report.
We like to where this this Template LOV storing and Run button code where it's storing
THANKS,
Gana

Hi,
You could temporarly adjust the CUNI definition for TST so that it can be converted to seconds. Adjust the notifications to set a valid unit of measure.
The alternative would be to update the field MAUEH in table QMIH with a valid breakdown unit of measure.
-Paul

Removing a corection from a maintenance cycle

Good Day;
I am trying to figure out how to remove a "correction" from a maintenance cycle. There is a transport assigned to the correction.
We are currently on support stack 17
Thanks all
Regards
Don Newton

Thanks Sanjai;
This part works well except that that any transports have remained in the maintenance cycle.
Not a big problem as I can use SE10 to remove the transport from the maintenance cycle as long as it is in u201Cmodifiableu201D status.
Thanks again Sanjai
Regards
Don Newton

SNP planned order deleted in APO, but not in R/3.

OK Guru's,
We have a situation where during the weekend SNP planning runs, SNP Planned orders are deleted in APO, but the order is never deleted in R/3. The change pointer is not in CPP and there are no failed queues. Also, when you run CCR on planned orders, we will get an error on some orders saying "Not in APO" and the only option to reconcile that order is to "Send to APO". The option that should exist is "delete in R/3" becuase the deletion never occured in R/3.
If you send the order back to APO, the order will show in the "Production Confirmed" line of the Planning Book. This is because APO is thinking that this order is an order that was created in R/3 when in fact is it really is a SNP planned order.
Any clues to why this would happen?
thanks,
Brian

How are you getting the SNP Planned Orders to R/3 in the first place.
If you are transferring them using /SAPAPO/RRP7 then I guesss its a manual transfer and system does not consider SNP Planned Order deletion flag relevant for transfer to R/3.
You will need to look into CIF enhancement to send the deletions to R/3.
Normally SNP Planned Orders are not relevant for transfer to R/3 unless its replaced or converted to a PPDS planned order.
Somnath

Maintenance Cycle Order deleted

Similar Messages

Maybe you are looking for