Custom development in SAP Agentry

[Former Member]

Dear SCN,

We are busy developing an Agentry app for what’s known at the customer as QM Inspections. Basically very similar to PM Work Orders, hence we copied SAP WM 6.0 as a starting point. However, due to the nature of the business they have 2 specific requirements that are not met with standard WM 6.0. I have tried explaining the requirements below, and for both the same question applies:

a. Is this possible within the Agentry framework?

b. If so, how can this be achieved?

We have had a look at various options, and have tried a few things already, but we’re not getting what we really want.

1. We have our own custom version of "Crew Management", not to be confused with Crew Management in WM 6.1. Within the app we want 1 full screen that lists all people assigned to certain work centers, derived from the person logged in. Next to that list of names we want buttons to select the crew members for the day. We need to keep that crew composition until such time they change the crew members. (Just fyi, this will also be recorded for time confirmations on the PM orders.) Following is a screen mockup as an example.

2. We make use of the standard PM-QM integration in ERP where they capture and store characteristics of the inspection tasks in the QM component. This QM integration is not supported with standard WM hence we are looking at a custom development here as well. To give you an idea, they will have a list of inspection orders, each will have one or more inspections points. Then they select an inspection point, again each inspection point will have one or more inspection tasks (characteristics) that need to be maintained. We already have the screens and navigation up to the inspection tasks, and when they select one it will open an edit screen. However, there's a huge concerns that there’s too many steps/taps involved to get to the inspection tasks. Can these characteristics be maintained at the point where the inspection tasks are listed, see below screen mockup.

Looking forward to some valuable input.

Regards,

Edwin

[jason_latko · Accepted solution]

Edwin,
You would need to populate a complex table or data table with the current user’s work center to compare against.  With so few people, I would fetch them all down into an object collection People.  Bring down the work center also in that object.  Then display the list on a Tile List.  Filter the list using an include rule that compares the work center on the Person object to the work center for the current user you placed in the complex table or data table.  Display a Boolean value on the list next to each person to indicate whether they are included in the crew or not, checked means yes, unchecked means no.  Add a single-click action on the tile list that runs an edit transaction against the current Person object and toggles the flag: Set it to true if currently false, and false if currently true.  You would do this with a rule before data entry on the transaction property.  Then as the user clicks Person objects on the list, the check box will toggle back and forth to add/remove them from the crew.

For the second part, yes you can add the inspections and then add a child collection under them with inspection characteristics.  You cannot really interact with a tile though on Android, and the inline edit capabilities of the Windows implementation are buggy at best.  I would stick with traditional edit transactions.  Set the screen up as I indicated above.  Have two tile list controls on the screen.  The left side shows the inspections and the right side dynamically adjusts to display the inspection characteristics for the selected inspection row on the left.  On the inspection rows, modify the screen for tile display to show only the fields that are appropriate for the current characteristic type and hides the others, using hidden rules on the fields.  It is not possible unfortunately to use multiple screens on a tile.  You need to use one screen and modify it dynamically at run-time with hidden rules to make it look different.  Add a single-click action on the characteristic tile that runs an edit transaction against the current characteristic row.  Now you can use multiple screens depending on type in the characteristic edit screen to only capture the data you need for a particular type.  Create two screens in the screenset and show the correct one with an enable rule on each screen that checks to see what type of characteristic this is.  Only one screen will be shown depending on the type.  After the data is entered and saved, the main tile will update itself to reflect the data change.

Jason Latko - Senior Product Developer at SAP

[Former Member · Accepted solution]

Hi Jason,

Thanks for your reply. The first part we got working based on your input, see below screenshot. The second part we are working on right now.

Regards,

Edwin