cancel
Showing results for 
Search instead for 
Did you mean: 

Required steps to add standard SAP field to Work Manager 6.0

Former Member
0 Kudos

Dear Agentry experts,

I need some help on how to add standard SAP backend fields to the Work Manager 6.0 application. The application is freshly setup and not yet customized apart from filters, so we are also new to develop it.

Specifically we want to add fields QMTXT and QMCOD from Notification Header. We have checked and the fields are activated in the backend configuration, so I hope there are no changes required to the backend. However, when checking the data in the ATE, the fields are currently not added / available in the Notification Collection.

I have searched this forum and found several pointers, but they deal with adding a full new field, and I want to keep changes limited. Can you please advise what specific steps I need to do on the Agentry / Eclipse side to close the gap between SAP backend and the Notification Collection. (I know how to add the fields to the UI if they are in the collection). Do we need to create custom Java Classes? Can I solve this by just Agentry configuration?

Thank you very much for your kind advice!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I got this working end-to-end now. As a reference:

To get standard fields down on the device, only extending the related Object Class and change of SAPOBJECT parameter in the backend is required.

To send values back, it is needed to extend several steps:

- Extend the Object class further

- Build extensions to Steplet, StepHandler and BAPI classes

- Maintain the changed Steplet in the Agentry application

- Change STEPHANDLER parameter in the backend

- Add new parameters for the BAPI_WRAPPER

- Enhance the related Transactions & Ccreens

The actual code is simple, the Enhancements Guide provides good samples.

0 Kudos

Thank you for posting the details of your solution!

Regards, Mike

SAP Customer Experience Group - CEG

Former Member
0 Kudos

Hi Merten,

Can you please check this thread

I'm also working on Notification create customization but facing some issues.

Regards,

Abhishek Wajge

Answers (1)

Answers (1)

i834235
Product and Topic Expert
Product and Topic Expert
0 Kudos

Look at the attachment, diagram depicts a data flow across the systems. You have to extend Java code for  the object  your trying to enhance and plus you have to make  necessary changes on  Agentry side as well.

if you have access to Service Market place , check out  SAP-WM-6.0-EnhancementsGuide.pdf document under Work Manager 6.0 documentation which describes the steps involved in enhancing application.

Alternatively you can also check this blog .

Thanks

Manju.

Former Member
0 Kudos

Thanks Manju, I was missing the Enhancements Guide, good document.

But looking at my specific requirement of adding a standard SAP field, would I still need to go the full custom route? The fields are available and active in standard SWM60_NOTIFICATION_GENERIC:

Will I need to

- Create custom BAPI )

- Create custom Stephandler

- Create custom Steplet

- Create custom Object (this is of course needed)

Or can I achieve this with only a part of nonstandard code, like Object / Steplet?

Thanks again.

i834235
Product and Topic Expert
Product and Topic Expert
0 Kudos

Since your doing enhancement to existing Agentry object, it is always recommended to extending  existing object rather than creating from the scratch.  In your  case since these fields are already exposed on SAP end there is no end to create  or extended BAPI  but you  have to extend java code to include additional fields along with corresponding  Agentry object  to accommodate additional fields.   Key thing to note here is that your not creating any objects  from  the scratch instead your existing  Java code/Agentry object and by adding new entries in syclo panel to map your  newly extended java objects to SAP objects.

Thanks

Manju.

Former Member
0 Kudos

Hi Schueler,

You don't need to go the full custom route if the fields are available and active in standard Data Object.

You need to

- Activate these fields in standard Data Object(SWM60_NOTIFICATION_GENERIC) if they are inactive.

- Create a new java class which extends an existing notification object java class to include new fields(Check WM60 enhancement guide)  

- Change application parameter settings for notification object to point to the new java notification object class.

- Enhance your existing Agentry object to add new fields. 

Hope it will help.

Regards,

Abhishek Wajge

Former Member
0 Kudos

Hi Abhishek Wajge,

great, when doing this I got it working immediately and I can now see and edit my fields on the device, after addition to transaction and screen objects.

Also when I change the field value on the client, the NotificationPostCurrentSteplet gets triggered, but the changes are not reflected in the backend. I assume also here I will need to add some code, can you advise which classes need to be enhanced to properly trigger the standard update BAPI?

Thanks a lot,

Merten

Former Member
0 Kudos

When you change the field value on the client, is that value getting saved in agentry notification object?

Check that first, Also you can try debugging java class to make sure that values are coming to the java layer.

Regards,

Abhishek Wajge