QM_Control on Required start date in quality notifications

Dear QM experts,
Requirement is,
For Q2 notification type the entries in required start date filed (QMEL-STRMN) to be restricted in such a way so that user can not do entry for last month.
Foe example,
1.     Today is June 12, 2009. If a user is creating Q2 notification today he/she may change the required start date in the past but not before 1st June 2009.
2.     User should be in a position to enter back date in required filed only for the current month
3.     The concept is just similar to period closing activities.
I tried through SPRO-Quality Management-Quality notifications-Notification creation u2013Notification types-Define screen templates-Field Selection: General Screens. Here there is facility to make the field grey, hide or required. One of the limitations is that this is client level setting.
Can the requirement be mapped for particular plant and for perticular notification type?
Thanks is advance
Best Regards,
Anand Rao

Dear Anand
Here are some of the thoughts. Please check and then come back with your feedback
1) Make Priority button mandatory for Q2 notification .VIQMEL-PRIOK. You can do only for Notification type Q2 by using the influencing fields
2) Make required date in grey so that no changes can be done . do this notification Q2
2) Maintain QM priorities SPRO >Quality Notifications > Notification Processing>Response Control> Define Priorities
3) Maintain Priorities in the QM priority in the same config
When you set the priority in the notification required from and end date is updated in the system automatically
4) Use this exit QQMA0018 Deadline setting based on entered priority to make sure that always the date doesnt fall on past date
Hope this gives some idea
Regards
gajesh

Similar Messages

Required Start date in Notification

Hi All,
Maint order is assigned as a call object for a maint plan. After scheduling the maint order is generated with the basic date as per the planned date in maint plan. But the notification generated along with the order has the required start date same as that of the notification generated date (due to call horizon) instead of the planned date in maint plan. Kindly give me the config steps to set the notification reqd start date as per the planned date in maint plan.

Hi Pushpa,
Thx.,
I had done that.
But i'm getting it right only when the priority in maint plan is not selected.
If priority is selected then i'm getting it wrong...
Kindly revert back !
Prabhu

Malfunction start date in preventive notification

Hi all
I have created one notification type of preventive to capture weekly preventive maintenance & scheduled the maintenance plan.When notification is generated on due date & I am opening the notification by t-code IW22 or IW28, system is taking malfunction start date field as system date.I have activated the "scheduling overview" tab of this notification type to know required start date(planned date) of the notification.How can I avoid the malfunction start date to be populated ? as my users get confusion due to this date?Why this date is coming by default as system date?
rgds
rajib

Hi,
This malfunction date/time will always be set as default to current date when the notification is created. Even if you were to set it empty via a exit, it will get populated when notification is loaded via IW22. An option would be to hide these fields for your preventative notification type. Make settings via OIAL with influence on notification type.
-Paul

Required start date in a services purchase requisition. How?

When hiring equipment (eg. a tower wagon), it is required to specify in the purchase requisition on what date the equipment needs to be available and on what date the equipment needs to be picked up again. So basically, the required start and end date of a service need to be captured in the purchase requisition (and copied to the PO and subsequently sent to the vendor).
The end date of the service is already recorded in the delivery date field. The start date can be entered in the item text. But since it is required to report on the start date of services, it is desirable to record the start date in a separate field in the purchase requisition. This way a list could be created with all the equipment that should have been made available by the vendor on a certain date.
Does anybody have any good suggestions on how to make such a 'required start date' field available? N.B. To make things more complex, the requisitions are raised in Plant Maintenance, so ideally the start date would be filled from the PM-order too.

The validity dates in the PO are maintained at header level. The required start and end date for an equipment should be maintained on item level, as there can be multiple items in one PO each with different start and end dates.
Also, the validity end date in the PO has the functionality that "No further service entry sheets can be created after this date." It is very common that a Service entry sheet is raised after the hire period is ended.
So using the validity dates in the PO is not a good option.

How to display absence start date and end date in workflow notification?

Hi,
I would like to display the absence start date and end date at
1) Subject of workflow email notification/worklist notification OR/AND
2) Content of workflow email notification/worklist notification.
Appreciate if anyone can advise on this as this information is very crucial to our client.
Thank you.
Regards,
Shiau Chin, Teo

1) Subject of workflow email notification/worklist notification OR/ANDyou have to customize the subject of notification message. You can find the message using following query.
SELECT message_type, message_name
FROM wf_notifications notif
where notification_id = <your notification>;> 2) Content of workflow email notification/worklist notification.
its already there I think.

Quality Notifications - Setting Required Fields

Is there a way to set certain fields as required for only a subset of Quality Notification Types?? The specific field I want to set is "Required End". I can see where this change would be made and applied on a global level, but do not see a way to only apply this to certain QN types.
Thanks in Advance,
Nic

In SPRO
QM>Quality notifications>Notification Types-->Define Screen Templates
Select "Field Selection: General Screens"
Click on menu bar button "Influencing"
Double click on notification type
Enter Q3 (or whatever notification type your working with)
From drop down menus select Field Selection > Change<>Display.
Screen should change from display to change mode. Fields should now be available to make changes
Scroll down until you find VIQMEL-LTRMN - Required End
Click on radio button in colum labelled "Req.".
Save.
Craig

WO basic start date - requirement date

Good morning folks,
Would anyone be able to shed some light on any config that would be suitable for the following:
The materials are assigned to a task list that is then assigned to a plan. That plan is then scheduled and the work orders are generated.
When the materials are added to the work order their requirement date is automatically assigned as the work order basic start date - can this requirement date be pulled from the scheduled dates instead?
The problem is that the material may not be required at the beginning of the WO, so the defaulted basic start date of the WO would not be the way forward.
Thanks
Mantas

hi Mantas
you can set in scheduling parameters with following possibilities
<b>Path Plant maintenance and customer service->Maintenance and service order->scheduling->set scheduling parameter</b>
1)The basic dates are adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
2)The basic dates are not adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
3)The basic dates are adjusted and the dependent requirements are scheduled for the order basic start date.
4)The basic dates are not adjusted and the dependent requirements are scheduled for the order basic start date.
so when you add the components you have to assign the operations,after selecting the operation you can change the operation date, after you change the operation dates,the material scheduled dates will be changed to the operation date
(using the option <b>1</b>)
regards
thyagarajan

Set the dependant requirement dates to be scheduled to order start date

Dear Experts,
The components have been assigned to the relative operations in the routing.
During the lead time scheduling, is it possible to set all the required date of the components to the order start date instead of the operation start date? How to configure?
Thanks,
Dawson

Hi,
In lead time scheduling, the precise production times, that is, the target start date and the target finish date, are specified for materials that are produced in-house. Capacity Requirements are also created during lead time scheduling and the date that the components must be provided is also determined.
You have maintained the following parameters for lead time scheduling in Customizing for MRP by choosing Define scheduling parameters for planned orders:
Parameters for determining the routing
Parameters that determine if and how scheduling is carried out
Parameters that indicate if and how basic dates are to be adjusted
Then
You have assigned a scheduling margin key in the material master record.
You can define the scheduling margin key in Customizing for MRP by choosing Define floats (scheduling margin key).
If You Assign BOM components to the first Operation then all the components are provided on the Basic start date of the production considering all the floats
OR
In a situation where different operations are assigned with different BOM components then we define Lead time off set(+ve on u2013ve value) to have material provision on the basic start date of production order
pavan

Error: "Depreciation start date required in old assets data (please enter)"

When , I use transaction AS91 , for an asset , with book depreciation key = 0000, the system shows this error:"Depreciation start date required in old assets data (please enter)",
somebody could help me with this please?

Check if the depreciation start date has got populated in the tab for depreciation areas in AS91.
Usually this gets populated based on capitalization/creation date.If not then try to enter this manually.
Thanks and regards
Kedar

If Quality notification as follow up action fails

Dear all
I have a situation where Quality notification is configured as a Follow up action once the UD is made.
So I am getting Create notification screen once UD is filled and SAVE button is clicked.
In Case some wrong data is entered in the Create notification screen and I am coming out of Notification without saving the notification.
The status of the inspection lot is getting flipped to UDed as expected.
But is there any setting where i can define if the Followup action is not successful( Notification not created), then wont make the UD of Inspection lot also. (OR some user status will get updated saying Notif not created etc..)

Hi Navdeep,
Thanks to Anand for his correct feedback.
Please note that as per standard SAP, unless and otherwise there is a defect created, there can't be a 1:1 link with inspection lot with the notification, though in the notification header table there is a placeholder available (QMEL-PRUEFLOS) to capture this inspection lot field. You are trying to use a follow-up action wherein, after UD you are always creating a notification based on business case. I believe, the FM you are using in follow-up action, is not presently populating QMEL-PRUEFLOS. So there can't be a link to find out when there is failures in notification creation, but UD happening successfully.
You can try out the below approach -
Approach - 1
During the UD save process, there should be additional checks happening. Ask the follow-up FM to update QMEL-PRUEFLOS or TEXT field with inspection lot for all successful notification creation and UD update, and send a confirmation email to approver or task processing partners, or the UD processing user ID (This email part can be skipped in case if this is not required). In case of any failures in notification creation at save, it should truncate the UD save process too and send a message to UD processing user for this failure.
Approach - 2
You can create a batch job running at the background to validate for which inspection lot there is no notification created, even though UD is done. Send a mail to the UD processing user to create a notification, as that is not created. User can then create it manually it by updating TEXT field in notification in foreground.
Thanks,
Arijit

Basic start date & Basic finish date based on Priority

Dear Experts,
When I am creating Notification & selecting Priority, System gives pop-up “do you want to specify new dates?” If I select yes system automatically change required start & required end based on Priority.
Now my question is do we have same functionality for Maintenance order as priority field is available there (If we are directly creating a MO)?
Even if we are creating WO from notification, required start & end dates copies to Basic start & Basic finish but if we change priority then no change in basic start & finish dates. Why?

Greetings Parag,
You may select the Priority in the initial screen of IW31 and the dates will shift accordingly, if you maintained the Relative Start &/or Relative End in
SPRO > Plant Maintenance > Maintenance Processing > Maintenance & Service Orders > General Data > Define Priorities > Define Priorities for Each Priority Type
If you want to change date based on Priority on the Order header screen, it's not possible in the standard to my knowledge, but you may easily develop an enhancement utilizing the user exit
IWO10012 Maintenance order: Priority handling on central header
or
IWO10009 PM Order: Customer Check for 'Save' Event

Change of quality notification document type

Hello guys,
the SAP enables change of notificaiton type, but only if original notification has origin "General notification". Has somebody succeeded to change also notification with origin "Q1 Customer complaint", meaning Quality notification.
Thanks
Br, Jan

In config, you have to explicitly define what changes you allow.
Most of my clients have defined their own not. Types. So we have to define for each one, what other not. type it is allowed to be changed to.
In config, under the Quality Notifications area, select Notification Creation --> Notification Type --> Allowed Change of Notification Type.
It should be pretty clear once you are in there.
You must test the conversion however. Read the config help and it will talk about inconsistencies. The data from the source QN must map ok to the target QN. If you special requirements in the target QN like certain mandatory fields, it might nit be possible to make the conversion. Each possible conversion should be carefully tested.
FF

Function Module to create Tasks in a Quality Notification

Hi,
I am trying to create Tasks in an existing Quality Notification through a program.
I have used 'BAPI_QUALNOT_MODIFY_DATA', 'BAPI_QUALNOT_SAVE' and 'BAPI_TRANSACTION_COMMIT', but it create any tasks in the given quality notification.
I am passing values to the following parameters in ''BAPI_QUALNOT_MODIFY_DATA" FM:
- NUMBER (Quality Notification Number)
- NOTIFTASK (Notification Task for Creation)
- NOTIFTASK_X (Change Indicator for Notification Task)
I am getting this error message in BAPI's RETURN internal table - "No changes made" (Message ID: IM and Message No: 407).
Can anybody suggest me where am I going wrong? Is there any alternate way to create Tasks for a QN doc?
Thanks in advance for your help/thoughts!

Hi Krishna,
You can use "RH_STRUC_GET ". In import parameters pass the following values,
ACT_OTYPE = 'O'
ACT_OBJID = <Org Unit Object Id>
ACT_WEGID = O-S-P
ACT_PLVAR = 01
ACT_BEGDA = <Start Date>
ACT_ENDDA = <End Date>
ACT_TDEPTH = 0
ACT_TFLAG = 'X'
ACT_VFLAG = 'X'
AUTHORITY_CHECK = 'X'
You will get all the positions and persons under that org unit in the RESULT_TAB table. You can read this table to read the positions alone.
Thanks,
Prasath N

Quality Notifications - Items / tasks / activities / overview / causes / ..

Hi PLM specialists,
I do have a question concerning quality notification, type F2 - vendor error. I do get the following tabs: reference objects, subject, processing: that's clear.
But there are also these tabs: items, tasks, activities. The tab items has the following subtabs: overview, causes, tasks and activities.
Does anyone has an idea concerning their use and what is the difference between the subtabs tasks, activities and the tabs tasks and activities?
Thanks!

Dear Peter,
The use of Item level Tasks and Header level task have been mentioned in SAP help.
Basicaly Header level tasks are referred as "Immediate Tasks", These tasks provide a quick fix for a problem requiring immediate attentione and header level activities are referred as activities done immediately attend the same.
Item level tasks are " Corrective Tasks". These tasks usually provide final solutions that wil prevent the problem for reccuring.
For eg if you get a vendor rejection in your shop the immediate action will to intimate to the concerned person quickly and remove it to block location. So your immedite task can be of like 1) Communicate the production personnel 2) block the material 3) block the vendor 4) inform vendor and activities can be of like 1) email send to vendor 2) material moved to block 3)deliveries return back to vendor etc
But as you know notification refers to a particular defect. So we need to take necessary corrective and preventive actions. SAP notification helps in doing this also. The item level entries are basicaly meant for this. In Item overview we can enter the defects that was noted on the material, you can maintain relevant causes for the same. Corrective tasks can be of like 1) Audit at vendors place 2) activation of source inspection 3) tighten the inspection standards and relevant activities done to achieve the tasks can also be maintained. This also helps in creating the 8D reports
So a detailed analysis of the problem is dealt in the item level Cause, tasks & activities while immediate action get covered in the header datas.
Hope this helps in clarifying your doubt
Regards
Gajesh

Creating Quality Notification via BAPI

I am attempting to create a quality notification using BAPI_QUALNOT_CREATE but am running into an issue. I need the ability to link the inspection lot number to the quality notification but I do not see a field for inspection lot in any of the BAPI segments. When i record results using defect codes in SAP, the quality notification that is created has the inspection lot linked to it (in the reference object tab). As there another field within the BAPI that i can use to pass the inspection lot number??
Thanks in advance...

Brock,
Thanks for the response. I have attempted to use the FM you suggested but still am not having much luck. After I feed the required data to the FM, I am prompted with the error message u201CNo quality notification type maintained for inspection lot type.u201D However in SPRO, under Quality Management -> Quality Inspection -> Inspection Lot Creation -> Maintain Inspection Types, the notification type is defined for each of the inspection types I am using. Is there any additional configuration I may be missing? Thanks againu2026
Harm

QM_Control on Required start date in quality notifications

Similar Messages

Maybe you are looking for