Stephen's SAP Blog

I've recently started working on SAP HR (ECC 6). This blog is just somewhere for me to keep notes of things I've found like lists of transaction codes, infotypes &c. If it's useful to anyone else then great, if not then no worries.

My Photo
Name:

  • Aging
  • Dyspraxic
  • Former Oracle DBA
  • Former techie
  • Single

Friday, 23 October 2009

Some info on authorisation levels from a colleague

The authorization level field specifies the access mode. The following
authorization levels exist:
. R (.read.) for read access
. M (.matchcode.) for read access using input help (F4)
. W (.write.) for write access
. E and D (.enqueue. and .dequeue.) for write access using the
asymmetrical double verification principle. E allows the user to create
and change locked data records and D allows the user to change lock
indicators.
. S(.symmetrical.) for write access using the Symmetric Double
Verification Principle
. * always includes all other authorization levels simultaneously

Labels: , , ,

Tuesday, 20 October 2009

Table T777F

Been running into a lot of errors that complain about not having things in table T777F. the question on everyone's lips is, "What the frak is table T777F"

Only thing I could find that seemed to give any real information at all is an item on CaptainSAP. The downside is it's in French and no-one here speaks French. It's not that we're ignorant xenophobes, out of the 60 odd people in the room we probably have over 150 languages spoken to a decent degree of fluency, just none of them are French.

The definition the page gives for the table is:"Opérations d'infotypes autorisées selon statut de planification (ISTAT)"

I thinkl that translates very roughly to "Authorisations of/for Infotype operations in/for planning stages." which, allowing for grammar corrections, is what freetranslation.com thinks it means as well.

Worklist going astray

Just been told (thanks Noel)about a really useful transaction. We're testing Employee Self Service (ESS) and Manager Self Service (MSS) right now. A lot of the stuff relies on workflows and items going to people's worklists to be actioned.

A recurring problem I've been seeing is that an employee will complete, say, a car use authorisation request form (so they can claim mileage) and from their side it seems to work fine. The thing is, the form doesn't show up in their manager's worklist for authorisation. No error messages, no warnings.

The transaction I've been told of is SWI1. This basically lets you see all the worklist items, including ones that failed. I've discovered what's going wrong (as in what the errors are, not necessarily what the cause is but it's a step towards finding the cause) on several defects. It's not a particularly user friendly transaction but compared with dissecting core dumps and some Oracle trace files it's not too bad.

Labels: , , ,