Hiding Field in Maint Plan

Hi All,
I have to hide the business area field in Maint plan screen.
Kindly suggest.
Thanks,
Prabhu

Hi,
Thanks.........
I have to hide the field while creating a maint plan (IP01) with call object as maint order.
While creating a maint plan with Notification as a call object, business area field doesn't appear in the screen.
Kindly suggest.
Prabhu

Similar Messages

Sort field in maint.plan&in ip30

hi
does some one implementd sort field use in img of maint plan
and does dead line monitoring in ip3o
whar are the benifits or scope
ponts will be rewarded

Hi,
The sort field is used to 'sort' plans according to different criteria that you need to configure.
For e.g. If a company has 200 Maintenance plans and you want to know all the plans valid for a certain division of the company. You can have these plans sorted as per company division.
You will need to configure the sort fields in IMG. If company name is COMP, then sort fields may be
COMPDIV1, COMPDIV2 etc (just an example).
For scheduling maintenance plans indvidually IP10 may be used. However in real scenarios. the transaction IP30 is used to do a scheduling of all the maintenance plans together.
Thanks,
KF

How to display field SZAEH (Start Counter Reading) in IP01 for Maint Plan

Please let me know how i can configure field SZAEH (Start Counter Reading) to be displayed for data entry in IP01 for Maint Plan creation. I tried Tcode OIW0 but cou;dn't succeed.
ALl the help will be appreciated

Jain,
The start counter reading will automatically comeup in the scheduling parameter screen , if the maintenance plan is tied to a counter. Isnt this not coming up?
Regards
Narasimhan

Sort field in maintenace plan

hi
does some one implementd sort field use in img of maint plan
and does dead line monitoring in ip3o
whar are the benifits or scope

Hi,
The sort field is used to 'sort' plans according to different criteria that you need to configure.
For e.g. If a company has 200 Maintenance plans and you want to know all the plans valid for a certain division of the company. You can have these plans sorted as per company division.
You will need to configure the sort fields in IMG. If company name is COMP, then sort fields may be
COMPDIV1, COMPDIV2 etc (just an example).
For scheduling maintenance plans indvidually IP10 may be used. However in real scenarios. the transaction IP30 is used to do a scheduling of all the maintenance plans together.
Thanks,
KF

Maint plan generating call before cycle.

Hi
I created single strategy plan for a fleet equipment
the cycle maintained is 250 mi (At 250 miles i need a notification)
The last counter reading is 200 mi only.
But when i run IP30 by giving the maint plan only it creating a notification.
If i execute IP30 again also it is generating notification.
Why it is creating notification before 250 mile is reached ?

Hi,
Annual Estimate should be maintained in case of even Measurement document is not created, but based on experience, if Maintenance Call object needs to be generated.
Also Annual Estimate is optional field, you can leave blank. While creating Maintenance Plan by assigning that Measuring Point, it will you Information message as Annual Estimate has not been maintained. You can skip that message & go with scheduling based on Measurement Document.
As you maintain 10000 in Annual Estimare, notification has been created immediately. Calculation would be 10000 for 365 days. So for example cycle value is 500, then 20 call objects would be created once in 18.25 days.
Annual estimate should be realistic. Also for your requirement, it is not required.
I hope its clear now.
Regards,
Maheswaran.
Edited by: Maheswaran.K on Apr 28, 2011 12:38 PM

Maint plan

Hi All,
In IP41 maint. plan description is made as mandatory i/p field. Where i could find setings in SPRO.

this field is mandatory because the same text will be copied to maintenance order description once generated through maintenance plan
Regards,
E-Jad

Scheduling for certain Equipment only from a maint. plan

Hello,
I have maintained many Equipment as separate line item in a Main. Plan. While scheduling, I donèt see option to select certain Equipment only.
I would like to maintain one or few main. plan, one each for a set of equipment. And then call a few from that one set of equipment. E.g. Total Equipment 120,000. 10 types each 120,000. Thus 10 maint. plans. Call Type I/Maint. Plan 1 and Schedule 1-10,000 on Jun 1. Call Type 2/Main Plan 2 and Schedule 10,001-20,000 on Jul 1 and so on.
Any suggestion please!

There is no way to do equipment wise scheduling in IP30. you have to create separate maintenance plans equipment wise and try using sort field in additional so that you can schedule maintenance plan bit easily.

Hiding fields in HCM forms

Hi Experts,
I have following requirement for hiding fields in my form.
I have two screens MANAGER and HR screen.
now i have some input fields which has to be visible in MANAGER screen and
and should be hidden in HR screen.
please let me know how can i achieve this using form calc or java script.
any code will be helpful.
Thanks,
Santosh

Hi sushmita,
Thanks for ur reply.
The solution which you have given i have already tried but not working.
my requirement is like MGR or HR can initiate the process.
if only MGR intiates the process the solution which u have given will work.
but here i have a diff scenario.i have created separate process for HR also but im not able
to see that process on the process list.
so i have to use only one process and resolve this.whatever im writing validation is working
only when MGR initiates the process but fails when HR initiates.
Hope u got my point.any suggestions will be helpful.
Thanks,
santosh

Hiding fields in phtmlb:formLayout (new thread)

Original Thread:
hiding fields in a bsp...
What Kevin is talking about, is some special development we did for HR eRecruitement. Well, let us turn it around. They helped us, and we returned the favour. And yes, this is actually some of the more interesting bits and pieces of BSP. (Fresh meat to discuss:).
Effectively, the <phtmlb:formLayout> has two functionalities. The first is a very easy way to layout a form. The second is a way via customization to dynamically have customers overwrite the visibility/required property of each field. So the SAP puts the maximum number of fields into the formlayout, and the customer can then via customization remove some, flag some as required, etc.
(If anybody should feel like writing a long weblog on this, I will provide technical detail, plus examples offline.)
The interesting database tables are these PHTMLB_FLI* ones. Part of the agreement was that the application itself provides for a UI to update the table. Also, the application itself controls which fields are changable.
If you really want to play, look at SBSPEXT_PHTMLB, the formLayout example. In the top part, there are also a serious of dropdown listboxes. What these do, is that they update the customization tables first, before the formlayout is rendered. So what you are seeing is actually the formlayout as it has been programmed, plus then the effects of a (customer) customization on it.
Also the example shows the effect of using an XML bee to dynamically add entries into the fieldLayout (if the application added these hooks).
brian

Hallo Thomas,
No, unfortunately we never build something to also customize the labels. They HR colleagues did not ask for this :).
I first started to write you here a loong text with answers. But then I got lazy, and searched my archive mailbox. Here below is the draft input that I wrote initially for the documentation. It describes everything pretty good. (But it is draft document, never proofread again, so read it lightly!)
bye, brian
Why?
Typically when an application is developed at SAP, the developer must make provision for all possible fields of information that must be displayed and/or queried from the user. However, in specific business cases, or depending on specific country laws, all fields might not be required. Also in some cases, fields in one scenario can be flagged required, versus in another they are only optional.
The typical starting point will be a complete formlayout done during the development. On top of this a customization layer is placed. The automatic reading and applying of the customization layer is automatically done by the phtmlb fL.
What?
For each field, a default behaviour is assumed. This is the behaviour that is defined by the developer during development time. For example, it could be specified that email address must be required. During the runtime it is now possible to overwrite the default behaviour with a customization entry for the field.
The following options are supported:
As Defined: The formLayoutItem in displayed as it has been defined during development.
Invisible: The formLayoutItem is not placed on the formLayout. It is immediately removed. All following items below it, will be moved up to fill its position.
Hidden: In this case, the formLayoutItem is placed on the formLayout, but not displayed. The item reserves its slot, and an empty slot will be displayed. However, after all items have been placed on the formLayout, a row "compression" is done, whereby all rows that contain only hidden elements are removed. Hidden is important for cases where columns next to one another must align. A typical example would be name & surname horizontally aligned. If now one item is invisible before this row, the two items will not be aligned anymore. With hidden, this alignment will be kept, and we still have the benefit of empty rows been removed.
Required: Sets the required flag for the item. Label of item will be rendered an indication that it is required (usually little red asterix after the label).
Optional: Can be used to customize a required field to be not required.
Read Only: Field value is only displayed.
What is index?
Customization is stored for a formLayout under the key that is build from the BSP application namespace, BSP application name, plus the page/view on which the formLayout is placed. It is assumed that there will only be one formLayout per view. A typical example would be:
SAP/SBSPEXT_PHTMLB/FORMLAYOUTSAMPLE.HTM
In addition, a customization key must be specified. Typical examples would be to say this is the default customization for USA, or for the specific branchen Losuegn. The customization key must be supplied with the <phtmlb:fL> tag, and only then will the customization data be read from the database.
Tables
For customization there are three interesting tables.
The first table PHTMLB_FLI is completed by the developer, and defines a list of all the formLayout items that can be customized. Only for those flItems which customization is possible, will entries be made in this table. The table contains three components:
NS_APPL_PAGE This is the unique key that identies the formLayout, consisting of namespace, application and page/view.
FLI_ID Id string of the specific formLayoutItem.
COMPONENT This is software component to which development applies, for example SAP_BASIS for all BSP development work done by us.
The second table PHTMLB_FLI_TEXT is just a language dependant text table that describes each item in the formLayout.
The tables PHTMLB_FLI and PHTMLB_FLI_TEXT are not using during the runtime. They are only of interest for design time. Note that NO tools are provided to make any entries in these tables. This is considered to be in the application domain, and will usually be part of the customization process of the application.
The third table PHTMLB_FLI_CUST is the only table that is read during the runtime. It is assumed that a customization tool has made the relevant entries for this table.
NS_APPL_PAGE see above
VARIANT_KEY This is the specific customization layer that is currently active. This string is equavalent to <pthmlb:fL customizationKey>. It is used to pull a specific customization.
FLI_ID see above
MODIFIER This is the new value to apply. For the possible values, see DDIC domain PHTMLB_FLI_MODIFIER.
For an example of customization, see BSP application SBSPEXT_PHTMLB, pages formLayout.htm. In this example, the customization can quickly be set via dropdown listboxes. On each request the PHTMLB_FLI_CUST is quickly updated and then the formLayout will find the set of new customization data to use.

Hiding fields in a form

hiding fields in a Form is called what? How do I go about hiding fields in a form than having a button the user can click on to make the fields visible to fill out? Thanks Nick

The "presence" property controls the visibility of form elements.
This eseminar explains the details:
http://adobechats.adobe.acrobat.com/p87746471/
Thom Parker
The source for PDF Scripting Info
pdfscripting.com
The Acrobat JavaScript Reference, Use it Early and Often
http://www.adobe.com/devnet/acrobat/javascript.html
Then most important JavaScript Development tool in Acrobat
The Console Window (Video tutorial)
The Console Window(article)

Change of Maint. Item in Maint Plan

Hi Experts,
is it possible to change of call object in Maintenance Plan,
as initially i've created maint plan with call object as order,
now instead of order ,i want Notification as call object,
please guide me if this is possible,
or i've to delete maint plan and create new maint plan
thanks in advance

Hi Pravin,
it is not possible to change call object in a maintenance plan. Even u create a new maintenance plan with same category u cant assign notification as call object. U hv to create Maintenance Plan category which has call object notification, then u can proceed.
narendra

Table & Field Name for Plan Data in CO

Hi All,
Can anyone tell me the table & field name where we can get the planned data in Cost Center Accounting and Profit Center Accounting.
I checked out the COSP(which is Totals) and COEP tables for CCA but i could find the fields only for actual data and not planned data.
Same for PCA...i checked out the GLPCT & GLPCA tables but in vain.
Regards & Thanks
Piyush Kothari.

Hi,
Thanks for the reply but COKL is only for Activity Type which contains Allocation Cost Elements.
I would like to have the Table & Field name for Plan data of Primary Cost Element.
Piyush

Copy Planning Plant to Sort field in Maintenance Plan

Hi All,
Is there any User Exit User exit is available to Copy Planning Plant to Sort field in Maintenance Plan.
Regds
Vinit

I think it is not possibe as the sort field in maintenance plan is a customizing field. you can not enter any value in the sort field but you in SPRO first you have to maintain the values for sort field.
The sort field in order and notification, there you can copy the planning plant or anything else as they are manual input fields

How to design maint plans

Hi friends ,
I have one equipment for which different maint tasks i have to perform
Sr no      Check point description                    frequency
1     Replace Hyd pp RL filter                              4 weeks
2     Replace GB oil for X axis mechanism     3 months
3      Chk flywheel motor current                      15 days
4      Clean heat exchanger if outlet water temp is more than 70 degrees
5     Lubricate flywheel brg after every        200 running hours
Is it possible with one maint plan or i have to apply diff plans
Can i include all tasks in same task list
plz Suggest.

A maintainance plan has maitainance items.
Attach this equipment to each maitainance items & attach task list pertaining to each equipment.
But when you want to schedule them differently I think you need different maintainance plans with different cycle duration.
Edited by: Sujit Gujar on Nov 17, 2011 5:25 PM

Completion requirement tick in maint plan

hi
requirement: when maint.pan is scheduled by ip10 then if in maint.plan header the completetion requirement tick is made.then irrespecive of that tick ip10 should generate orders but if earlier order is delayed by "x" days then next order should shift accordingly by "x" days
pls guide how to map the scenario
Please check you inbox for information from me
-Paul (Moderator)
Edited by: Paul Meehan on Feb 22, 2012 2:12 PM

Hello,
You have to remove completion required check box as it prevents the generation of work order until unless last work order have status TECO.I will suggest to use the FIXED call option in IP10 to delay the call as per your requirement if you dont want
to remove the check box for completion required.
Regards,
Rakesh

Hiding Field in Maint Plan

Similar Messages

Maybe you are looking for