Work Manager 6.0 - Order & Notification assignment type Z

Hi Agentry experts,
for WM 6.0 we have the idea to get a more flexible assignment for notifications and work orders, as our business process requires more flexibility than the standard available assignment types e.g. Work Center
User A should only see certain equipment
User B should see certain activity types
User C should only see unscheduled
etc.
Our idea is to add custom assignment types (similar to described by Mark here) which will call the standard reports behind IW29 / IW39 with a user specific selection variant.
Does any of you have experience which you could share, or a better suggestion how this can be achieved?
Thanks in advance for suggesting!
Regards
Merten

Hi,
we are now working on this and have implemented some ABAP code for Notification and Work Order Assignment Type = Z which is available in the standard WM 6.0 config panel. This is also configured in the mobile application config and data object filters (as described in the Assignment Type documents.
However, on the client we get error: Invalid Wo.AssignmentType from the ini file or SAP Mobile Configuration. Please check the ini file or the mobile configuration for assignmenttype (Z) in section APPLICATION_CONFIG
So our Assignment config is OK, but not working. I see in Java that this error is thrown by class WorkOrderAssignmentTypeDelegateFactory, this class only tests on types 1-8 and A.
Any guidance on how to resolve this easy would be appreciated.
Thanks
Merten

Similar Messages

Notification Assignment Type Issue - SAP Work Manager 6.0

Hello Experts,
We are not able to download notifications on the device for header level work center that is assignment type = 5.
We have done the below configuration.
- added the user parameter for work center in user profile.
- changed assignment type to 5 in Notification MDO.
Same configuration is working properly in case of work orders only change is assignment type set to 8 and changed in client global value Wo.AssignmentType to 8.
There is no configuration guide available which explains notification assignment types in SAP Work Manager 6.0.
Any help would be appreciated.
Regards,
Abhishek
Tags edited by: Michael Appleby

Hi,
In the notification MDO data filter, you also need to add a filter to the WORK_CNTR field. It should be user parameter type, with value "VAP".
Also, from memory, I had to disable some other filters that were set out of the box. These were filtering out my data.
Hope that helps
Michael

Work Manager 6.0 Push Notification not working

Hi All,
I have configured Standard Work Manager 6.0 application and now I am trying to configure Work Manager 6.0 Push Notification.
I have completed all Post Installation(optional and required) which are mentioned in Standard product document.
I am getting new work order entries in /SYCLO/PSH01 and /SYCLO/PSH02. After that Agentry server is also calling /SYCLO/PM_DOPUSHWORKORDER_GET Function Module and /SMERP/CL_PM_PUSHWORKORDER_DO Class Handler.
I am getting result in final export table(ls_mdo_output_vals) of /SMERP/CL_PM_PUSHWORKORDER_DO.
My problem is still I am neither getting this work order into ATE nor push notification message.
When I went to Syclo Admin panel, status of the push notification is also NEW.
I have configured 8282 port in [HTTPXML-2] section of Agentry,ini and Syclo Config panel outbound trigger.
Kindly let me know what can be an issue?
Regards,
Mohit Verma.
Message was edited by: Michael Appleby

Mohit,
I noticed the following in your Backend-Java.log.
~~~~~~~~error 1~~~~~~~~
2014/06/27 17:37:36.947: Error in initializing the StepHandler from the ini file or SAP configurations (com.syclo.sap.component.serviceorder.stephandler.ServiceOrderRemovePushStepHandler). Please check the JavaBE.ini file. java.lang.ClassNotFoundException: com.syclo.sap.component.serviceorder.stephandler.ServiceOrderRemovePushStepHandler
~~~~~~~~end~~~~~~~~~
<-- Make sure this is corrected. For some reason your java code is not being detected during start up. Check your Java folder in the root directory of your Work Manager 6.0 to see if it can be seen.
Based on history of Support tickets the following SAP Note is mandatory to make Push work:
1. Do mandatory SAP Note: 1954444
2. Please review: 1828657 - Release strategy for the ABAP add-ons SMFND, SMERP, SMISU, and SMCRM (Make sure you installed the correct add-on - look at the spelling in detail)
3. SCN Push threads that may help: http://scn.sap.com/thread/3494003
See if any of the comment above will work for you.
4. After you tried the above and it didn't work for you to try the latest SMP 2.3 SP04 version and let us know. This is for what I can see on the logs.
~~~~~~~~Error 2: Backend-java log~~~~~~~~~
2014/06/27 17:40:35.471:             Getting Java results in the the 'WorkOrderPushForEventSteplet' step (java class com/syclo/sap/component/workorder/steplet/WorkOrderPushForEventSteplet)
2014/06/27 17:40:35.471:             : 1 lines, 0 non-printing characters, 20 total characters
The module is 'PM'
2014/06/27 17:40:35.471:             The root object is 'WorkOrder'
2014/06/27 17:40:35.471:             Trying to read results by calling getReturnData()
2014/06/27 17:40:35.471:             : 1 lines, 0 non-printing characters, 81 total characters
getReturnData() method returned null, falling back to reading _returnData field
2014/06/27 17:40:35.471:             Processing public field _returnData: Ljava/lang/Object;
2014/06/27 17:40:35.471:             _returnData is a single object: 'Ljava/lang/Object;'
2014/06/27 17:40:35.472:             Mapping public fields of Java Class 'java/lang/Object' to Agentry object 'WorkOrder'
2014/06/27 17:40:35.472:             No public field userid found in java/lang/Object for user ID, and not in per-user mode: cannot determine user for data.
~~~~~~~~~end~~~~~~~~~~~~~~~~~~
The log comment above is stating that the push is trying to be sent to the PDA/handheld but it does not know where to send it to. This is proven from your backend setup and when you have no errors in your push retry.
The last line above is still a mystery to me as there are lots of upgrades with patches and SMP 2.3 SP# and with the userid is not found (especially when it states it is not in per-user mode: cannot determine user for data) then the Agentry Server cannot determine where to send the push to.   Hopefully somebody in this thread knows this.
Regards,
Mark Pe
SAP Senior Support Engineer (Mobility)

SAP Work Manager 6.0 - Creating notification on mobile device (customizing the default Start and End date)

Dear all,
When I create a notification in SAP Work Manager 6.0, the notification gets created in the back-end with Start Date equal to Current Date + 1 day and End Date equal to Current Date + 3 days.
Can you advise where I can customize this behaviour, so that the Start Date is for example equal to the Current Date and End Date being 14 days in the future? Is this something that would need to be configured in Agentry Editor or within the ABAP stack?
Many thanks for your support.
Pavel
Tags edited by: Michael Appleby

Hi Jason,
We went this route and identified the initial values, and tried to modify those.
No impact though, as if those values are being overwritten elsewhere (whatever value we set, no change on the backend).
Please see the attachments with screenshots of Agentry Editor.
Many thanks.
Pavel

Orders/Notifications assigned to a personnel Number

I need to get all the orders and notifications assigned to a personnel in plant maintenance. Can anybody suggest me the tables where I can query and get the orders and notification assigned on personnel Number. This Personnel Number get populated against the order in TRANSACTION -IW37 .
Any Idea????

That transaction is using AFVC and the view VIAFKOS. u have personnel number in AFVC and the Order in VIAFKOS.
Join conditions are AFVC-AUFPL = VIAFKOS-AUFPL & AFVC-APLZL = VIAFKOS-APLZLT

Query on Service Order Assignment Type in CRM Service Manager

Hi All,
This query is regarding the Service Order Assignment type in CRM Service Manager.
While fetching the service orders from SAP, the ServiceOrderFetchBAPI calls the ServiceOrderAssignmentTypeDelegateFactory class
ServiceOrderAssignmentTypeDelegateFactory class contains {
1. public static String ASSIGNMENT_TYPE_GLOBAL = "ServiceOrder.AssignmentType";
      public static String SECTION = "APPLICATION_CONFIG";
Question 1: Please explain about both the String values, Are these two values being fetched from the sap config panel ? If yes then please elaborate where can I check their respective values in SAP.
2. The method getAssignmentTypeDelegate compares each values and returns the respective assignmentTypes
public static ServiceOrderAssignmentTypeDelegate getAssignmentTypeDelegate(User user, SAPObject sapObject, BAPI bapi)
    throws Exception
    String assigmentType = user.getPropertyValue(SECTION, ASSIGNMENT_TYPE_GLOBAL);
    if (assigmentType.equalsIgnoreCase("1"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByResourcePlanning(user, sapObject, bapi);
      return assignmentTypeBAPI;
    if (assigmentType.equalsIgnoreCase("2"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByPartnerResponsible(user, sapObject, bapi);
      return assignmentTypeBAPI;
    if (assigmentType.equalsIgnoreCase("3"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByMultiResourceScheduling(user, sapObject, bapi);
      return assignmentTypeBAPI;
    if (assigmentType.equalsIgnoreCase("4"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByAccount(user, sapObject, bapi);
      return assignmentTypeBAPI;
Based on the values a new class is instantiated and it mentions their filter range to be set in BAPI
For ServiceOrderByResourcePlanning -
public void setParameters(SAPObject obj)
    throws Exception
    String partnerGUID = this._serviceOrderComponentManager.getPartnerGUID();
    this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, "");
For ServiceOrderByPartnerResponsible -
public void setParameters(SAPObject obj)
    throws Exception
    String partnerGUID = this._serviceOrderComponentManager.getPartnerGUID();
    this._bapi.setFilterRange("IT_PARTNER_GUID_RA", "I", "EQ", partnerGUID, "");
For ServiceOrderByMultiResourceScheduling -
public void setParameters(SAPObject obj)
    throws Exception
    String partnerGUID = this._serviceOrderComponentManager.getPartnerGUID();
    this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, "");
For ServiceOrderByAccount -
public void setParameters(SAPObject obj)
    throws Exception
    for (GUID object : this._accounts)
      String guid = object.getGUID();
      this._bapi.setFilterRange("IT_ACCOUNT_GUID_RA", "I", "EQ", guid, "");
Question 2 : Why the filter range in ServiceOrderByMultiResourceScheduling (MRS Scheduling engine ) is set as - this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, ""); ? If we see the ServiceOrderByResourcePlanning also has the same filter range - this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, "");
If these are two different scheduling engines then the table names should be different both in case of MRS and LRP ? Please clarify and explain
Please Explain
Thanks and Regards
Neha Mahanty

Neha,
Got these answers back from the programmer:
Answer 1: Yes, this is being
fetched from the Mobile application configuration parameters as shown below.
The value is configured by a rule to look up to the Service Order MDO
Assignment type filter.
Answer 2: Yes, MRS and LRP are
different scheduling engines, but since the client does not have all the user
information regarding MRS (i.e the resource information), we set the partner
GUID for both. SAP backend ABAP code will determine resource based on the
partner GUID and will call the respective handler for MRS and LRP to retrieve
the service order assignments. Currently Service Manager 4.0 code does not
support MRS with the provided add on.
Jason Latko - Senior Product Developer at SAP

Agentry Work Manager 6.0: BADI to enhance assignment type

Hi,
I have the requirement to more or less combine the work order assignment types 1 and 2. I have to fetch the operations based on its assigned personal number, but at the same time I have to fetch a work order and all the operations if the Agentry user is the work order header responsible.
Unfortunately this is a single value parameter so I set the assignment type to 2. Now I thought it would be really easy to fetch the work orders based on the assignment type 1 since there is a BADI available after each assignment call method:
WHEN '2'.                                           "Operation level
           me->get_assignment2(
             EXPORTING
                iref_rfc_oo_data = iref_rfc_oo_data
             IMPORTING
                et_return        = lt_return
                et_wo_object     = lt_wo_object ).
           IF NOT gref_badi_wo IS INITIAL.
             CALL BADI gref_badi_wo->get_assignment_type2
               EXPORTING
                 iref_mdo_data = me->oref_mdo_data
               CHANGING
                 ct_wo_object = lt_wo_object.
           ENDIF.
So inside the BADI gref_badi_wo->get_assignment_type2, I wanted to call the me->get_assignment1 method, and then join the 2 internal tables values.
But the problem is once the BADI is called it is not possible to call this method since we only have the OREF_MDO_DATA object which has the original class as a inaccessible private attribute. I could try to copy and adapt the me->get_assignment1 code but there are some attributes that are not accessible inside the BADI. Do you see a simple and elegant solution to this requirement?
I would like to avoid creating a new Z handler class inheriting from the standard one...
Thank you.
Tags edited by: Michael Appleby

Hi,
I just wanted to close this old thread since what I did long ago to solve the issue is to replicate the me->get_assignment1 inside the me->get_assignment2 BADI method code. It is not just a copy paste since from the BADI you don't have access to some MDO handler private data.
But it is possible to replicate all the fetch process except when doing a delta with exchange since I couldn't easily get the necessary data from the main MDO. But even if you get all the work orders ID's, after the BADI the standard code checks the exchange table again and rules out the unnecessary WO ID's.

Work Order / Notification Transfer - SAP Work Manager 6.2

Hey Guys,
How do we transfer notification based on Work Center, Standard work manager does not updates main work center.
Requirement is to Transfer notification which are associated with work order when we transfer work order.
Please let us know how to transfer notification based on work center.
Thanks,
Madhur Kanungo

In Agentry you can trigger a Notification Change Transaction (Z_NotifTransfer) without a screen and update "WorkCenter" field on Notification Object. Please make sure you IsEdited = True and NeedsXmit = True along with the change to the Notification. This will update the notification object along with Work Order.
The other option is to extend the WO MDO Class and invoke BAPI_ALM_NOTIF_DATA_MODIFY in the Transfer method.
thanks,
Chandra

Order is assigned to a general notification - INCORRECT SAP BEHAVIOR

Has anyone encountered the issue where a work order is assigned to a general notification. This is an incorrect SAP behavior. Only maintenance and service notifications can be linked to a work order.
Here's the steps to replicate the issue:
1. Open a work order via transaction IW32.
2. Go to Objects tab.
3. In the next available line of the Object List table, go to the Notification column. Enter a GENERAL notification. (Here at work, we have a process where operator submit a work/change request. They come in initial as GENERAL notifications. It then goes to an approval process. That's when it gets converted to a Maintenance Notification).
4. After entering the general notification number, hit enter. You will get the error "Transaction not allowed
for notification type G1". G1 is our general notification type. This behavior is correct.
5. Take out the notification number since it is causing an error. Hit enter. This time no more errors show up. Everything is fine.
6. Save the work order.
7. Open table QMEL via transaction SE16.
8. Look for the general notification. You will see that field AUFNR was assigned the work order number. THIS IS NOT CORRECT.
I looked at SAP Notes but didn't find one that will fix the issue. I'm wondering if anyone has encountered this issue before. Thanks.
Giscard

Well Giscard,
You are definitely right about this. Such an incosistency in one of the tables refers to an incorrect behavior. But one amazing thing is that the Object List table OBJK is not updated with the notification number whereas the Notification table QMEL gets updated with the order number and even the status of the notification is changed to Order Assigned and whenever you would try to link the notification to another order, it would not allow you to do so.
In this case, I suppose you should raise an OSS to SAP regarding such behaviour. I was also searching the marketplace, did find some SAP notes about inconsistencies in the QMEL table like 1345087 but none actually addresses this issue.
Regards,
Muhammad Usman Kahoot

Work Manager 6.2 (CS) - Longtext not set for multiplie Notification Activities

Hi all,
I am trying to post multiple activities, each with its own long text from the work manager. The thing is that only the first activity will have the long text. While debugging /SYCLO/IF_CORE_DO_HANDLER~CREATE (/SMERP/CL_CS_NOTIFICATION_DO), I found a curious piece of code, that basically does the following:
Loop over activities (outer loop)
Get a fresh sort number
Loop over long texts (inner loop)if the long text sort number matches the activity sort number (the activity from the outer loop)
then replace the long text sort number by the fresh sort number and remove the long text from the list of long texts and copy its values to another list
else remove the long text from the list of long texts and copy its values to another list
replace the activity sort number (the activity from the outer loop) with the fresh sort number
What happens with multiple activities is that in the inner loop, all the long texts are removed from the list of long texts (even those that are matching the second, third, ... activity in the activity list). Therefore, only for the first activity, long texts are added. Did anyone else encounter this problem (if this is working for anyone, could you provide me with your BAPI parameters)? Any idea on what SAPWM-911 is about (would it be safe to get rid of that part)?
             LOOP AT me->tab_notif_activity ASSIGNING <notif_activity>.
               ADD 1 TO lv_sort_no.
               LOOP AT lt_notif_longtext INTO ls_notif_longtext WHERE objtype = lc_ltext_notif_activity.
                 lv_index = sy-tabix.
                 IF ls_notif_longtext-objkey+4(4) = <notif_activity>-act_sort_no.
                   ls_notif_longtext-objkey+4(4) = lv_sort_no.
                   APPEND INITIAL LINE TO me->tab_notif_longtext ASSIGNING <notif_longtext>.
                   MOVE-CORRESPONDING ls_notif_longtext TO <notif_longtext>.
                   DELETE lt_notif_longtext INDEX lv_index.
                   "<--Ins 332_700 SP1 - SAPWM-911 - Start
                 ELSE.
                   "Check for remaining longtext rows not matching with parent table
                   "is considered as update to the existing activity notes
                   APPEND INITIAL LINE TO me->tab_notif_longtext ASSIGNING <notif_longtext>.
                   MOVE-CORRESPONDING ls_notif_longtext TO <notif_longtext>.
                   DELETE lt_notif_longtext INDEX lv_index.
                   "<--Ins 332_700 SP1 - SAPWM-911 - End
                 ENDIF.
               ENDLOOP.
               <notif_activity>-act_sort_no = lv_sort_no.
             ENDLOOP.
Thanks in advance for any contribution to this problem.
Regards, Daniel

Hi Daniel,
I would suggest you raise an OSS message to get this fixed if you believe its bug.
With Regards
Murali

Re : sales order without assigning document type in OVAZ

Hi
How to create sales order without assigning document type in OVAZ.
Thanks
Mani

Hi Mani,
If all your order types can be used in all the sales orders, you dont need to maintain in OVAZ. If you think ur order type has to be used only in one of the sales area then you need to maintain in OVAZ.
Hope this helps.
Kind Regards
Chakradhar

Weblogic 10.3 : Work manager is not getting assigned to a application

Hi,
i have assigned a work manager to an application in weblogic-application.xml and able to see that under Deployments
-> Application name -> Configuration -> Workload tab of weblogic console.
But while starting server get a warning as
<Dec 17, 2008 9:45:16 AM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name RealWorkManager. Dispatch policy RealWorkManager will map to the default WorkManager for the application SmpMain>
Can some one help me out how to assign a work manager to a application.
Thanks,
Smita

Thanks for your help.
When i created a work manager from Deployments -> Configuration -> Workload -> New and the new Work Manager appears in the Application-Scoped Work Managers table. But was not able to see that in Monitering -> Workload Work managers table. Why is that so?
Regards,
Smita

Assign global work manager to Java archive

Using Weblogic 9.2
have created a global work manager (response time constraint) via the console. haven't found a way to assign that global manager to a deployed archive (ear/war). the [Work Managers Guide|http://e-docs.bea.com/wls/docs92/config_wls/self_tuned.html] just states:
"An application uses a globally defined Work Manager as a template"
assuming that to use a global manager the assignment has to be made in the deployment descriptors. or is there a work-around?

exactly. the connect to work managers exists only in the descriptors. looking for a confirmation for that statement.
odd all the same that via the console we can't directly update the descriptors. maybe a nice feature in the future.

Ticket Management Through PM Orders !!!

Hi,
We have a requirement in an upgrade project whereby Ticket Management should be done thru PM Notifications or Orders i.e. each object which need to be upgraded will be considered as a seperate ticket and a corresponding Notification/Order will generated for it. It will then be assigned to a business partner(developer,functional tester etc.) thru a workflow.
Pls respond if any of u have any idea or have implemented this kind of system thru PM module.A detailed explaination will be appreciated.
Saurabh.

Saurabh,
I could not understand what you or your client wants to achieve by this upgrade project.
Yes you can configure the notification and order for the same, but there will not be any equipment or Functional location.
You can configure the different type of notification only for the tracking purpose and then create notification for every Ticket.If it is billable OR if it is a CR, create PO to capture the efforts and cost and if there is no cost involved create only notification and also you can configure the work centre for the developers to assign the notification.
I have not configure the system for ticket management,but we configure the PM module to capture the customer complaint at client site.
I hope it may help.
Regards,
Manish

Inspection Rounds in Work Manager 6.0

Hi all,
We've setup Work Manager 6.0 running on SMP2.3. One of the functions that I'd like to get working is inspection rounds.
We have
Configued the standard order type PM01 to be an inspection rounds order in the work order MDO filter INSP_ORDER_TYPE.
Assigned a measurement point PRT to the order operation.
Added an Equipment number to the order operation.
In work manager I am able to access the PRT screen from the Work Order Detail PRT link. In that screen I can see the buttons for Tools, Inspection Types, Measuring Points, and Attachments. In all my testing I've never seen a Measurement Point under the Measurement Point selection.
When I've checked the data structure in the Agentry Test Environment the measurement point entries come up in the PRT section under the Operation section. They are missing any value in the RecordID field. Other PRT types have this information filled and I assume that it provides the link to the measurement point information downloaded for the functional location and equipment data structures under the operation structure.
Inspection Rounds are working fine in the back end using standard confirmation transaction iw42.
Any suggestions?
thank you
Steve.
Tags edited by: Michael Appleby

Thank you Syam,
We have activated 'LOG_EAM_LINEAR_1' and '/SMERP/EHP5_EAM_BUS_FUNC' and we now get inspection round measurement points coming through to Work Manager.
Separate switches for the functions in future releases is a solid idea. Any customer who is not running linear assets will have to debate with their account manager if the want to use inspection rounds. Linear generally attracts an additional license cost.
Back to Inspection Rounds. The measurement points come through only if the functional location or equipment record is explicitly specified on the operation. In the ECC functionality any measurement point can be specified as long as it is in the hierarchy beneath the functional location/equipment referenced on the operation. I assume that work manager limits this to minimise data sent to the device.
Does the parameter OBJECT_HIER_LEVEL'' on the 'WORKORDER_GENERIC' MDO have any impact on the collection of Functional Location and Equipment data at the operation level. We are debugging and initially find a section of code relating to BDS documents. Do you know the scope of the parameter? Changing it's value seems to have no impact on the inclusion/exclusion of measurement points. Debugging continues.....
Ideally the get work order routine would be able to identify the required Functional Location and Equipment records from the measurement point PRTs themselves, that way only push the required records to the device, rather than a full hierarchy (assuming that full hierarchy was an option). As it stands it looks like we'd need to implement a BADI to restrict the assignment of measurement point PRTs in ECC to only measurement points attached to the functional location and equipment record explicitly referenced on the operation. If that wasn't done then you could add measurement PRTs in ECC that you couldn't process in Work Manager.
Thank you again for your assistance.
Steve.

Work Manager 6.0 - Order & Notification assignment type Z

Similar Messages

Maybe you are looking for