Inbasket approval data and RD30 access flag

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Roger French
Veteran Member
Posts: 549
Veteran Member
    I want a second opinion. For inbasket approvals for processflow, the Access Flag must = Y to see the actual data for an approval (such as a personnel action for ESS/MSS). If the Access Flag = N, then the data will be blank as the flag restricts you to your own employee information.

    Just an FYI, it does not appear any of the pflow documentation says the access flag must = Y to see approval data.

    Can anyone else confirm this about the access flag and the inbasket?

    Thanks in advance,
    Roger
    John Henley
    Posts: 3353
      Hi Roger, the Access Flag means "ignore extra IOS security" which is applied based on company, employee, vendor, customer, etc. What happens if access=N is that you can see your own info as well as any of your direct reports as defined in the HRSUPER table--without needing to open access=Y. Where access=Y is needed is when you're in multiple roles. This is particularly true in RQ: if you have requester = XXX and you are also an approver..you can't see the requisitions where requester <> XXX.
      Thanks for using the LawsonGuru.com forums!
      John
      Roger French
      Veteran Member
      Posts: 549
      Veteran Member
        John said:
        "Hi Roger, the Access Flag means "ignore extra IOS security" which is applied based on company, employee, vendor, customer, etc. What happens if access=N is that you can see your own info as well as any of your direct reports as defined in the HRSUPER table--without needing to open access=Y. Where access=Y is needed is when you're in multiple roles. This is particularly true in RQ: if you have requester = XXX and you are also an approver..you can't see the requisitions where requester <> XXX. "

        Yup I know the Access Flag, My Data Security..and also the HRSUPER situation. We had a situation where some managers apparently were outside their normal span of control for direct reports and we're trying to approve actions for employees not in their span. We corrected it and all is fine now.

        Thanks John
        Roger French
        Veteran Member
        Posts: 549
        Veteran Member
          It turns out that a browser patch was needed for some PC's out in the field to correct the problem with the workunit data not appearing.

          My, how those browser patches rear their ugly heads in mysterious ways.

          -R