New workflow organization added to FSS in production [FSS05] Upgrade. See web:
rolesweb.mit.edu -> Hierarchy of qualifiers
Fund (Fund centers and funds)
FC_FSS
This brings up the following list:
+--FC_FSS FINANCIAL SYSTEMS SERVICES
+--FC_FSS01 TERMINATED
| +--FC101102 GO-FSS TERMINATED P421200
+--FC_FSS02 OPERATING
| +--FC101103 GO-FSS OPERATIONS P421200
+--FC_FSS03 W92 BUILDING SHARED COSTS
| +--FC101532 GO-W92 BUILDING SHARED COSTS
+--FC_FSS04 HR/PAYROLL
| +--FC101536 GO-HR/PAYROLL P421200
| +--FC400284 DH-HR/PAYROLL PROJECT
+--FC_FSS05 UPGRADE
+--FC400289 DH-FSS UPGRADE P421200
The characters beyond the FC_ and before the space correspond to the code in brackets at the beginning of the organization name in PPOM, in this example [FSS05].
Settings -> Maintenance interface... (this is a toggle between new JOY interface and old style faster interface)
Select high order [FSS] and click on the "Create" soft button
"Abbr" should be UPGRADE and "Name" should be [FSS05] UPGRADE.
Click on "Staff Assignments" soft button
Select on the new organization, [FSS05] UPGRADE
Click on "Positions" soft button
Enter X1 and enter, save
Repeat for X2 (All the other release strategies have the model in the name, but this one does not. It would be nice if we could change this. What impact would it have?)
S, V, W ,X, Y are using Workflow Role resolution via user exit
Z1 - Z3 = Workflow Role resolution with group, code, and plant (T16FW) - I think this has been model has been dropped. No fund centers are associated with it. On the other hand it might be driven by material group instead of funds center. 1C is the only release strategy that references the model. It is associated with job (C), 50002729, not position (S). It certainly looks like it was developed to be a final approval above and beyond the DLC approval process. There are 3 Z positions but they are not referenced because Model 1 has no fund centers.
There are only 155 Model 2 positions at the institute, compared to over 1000 Model 4 and over 2000 Model 3 positions
PFOM in production to view staff assignments:
All Org Object types radio button on initial screen (or when assigning Funds Center the Org. Object Type is ZBUS0028. When turning auto approve on and off, the Org Object Type is WF_TASK.)
Click on pencil
Click [FSS05]
Create soft button (funny hierarchy icon next to pencil on left)
Organization object type is ZBUS0028
FM area is MIT
Funds center 400289 (see snapshot above)
Remember that funds centers are assigned to the organization (blue) not the position (yellow). Always select the organization before pressing the create button.
If we want to toggle Auto Approve on and off, we can choose any org level and follow the same steps as those for ZBUS0028 but instead of entering ZBUS0028, enter WF_TASK. Instead of Funds Center enter the workflow of interest, either WS91000010 for auto approve or WS91000008 for vanilla. In production, the only workflow that is entered is WS91000010 because vanilla is the default if nothing is found in the org heirarchy. But, for testing purposes, we could make one of our organizations vanilla and another auto approve. In the snapshot above you can see that only our main organization has a WF_TASK assigned
When trying to find a cost collector that belongs to a particular funds center, the table of interest is FMZUOB. It does not have an index on Funds Center! But it is a mid size table (60,000) and the queries don't seem to take too long.
PFOM -> PRES
Notice that Auto Approve listed at multiple levels. It is thought that auto approve must appear at all levels in order for it to work for model 2. This isn't true for any other model.
Where is the 101101 Funds center? It seems like it should be in the level between 100281 and 101102. So it seems that not all Funds centers are assigned to an Organizational unit. Why?
From Chuck King e-mail:
On RolesWeb, when you click on "Hierarchy of qualifiers" then select the default "FUND (funds centers and funds), you see this: +--FCMIT ALL INSTITUTE FUNDS +--FC_CUSTOM Custom Fund Groups +--FC100000 PRESIDENT +--FC900000 DEFAULT FUND CENTER FOR FM AREA +--FC999999 INACTIVE / TO BE REUSED "FC_CUSTOM Custom Fund Groups" mirrors the PdOrg structures. This is NOT the MIT funds center hierarchy, it is simply the DLC's custom hierarchy or authorizations hierarchy. "FC100000 PRESIDENT" is the DLC's funds center hierarchy that is fed by SAP on a nightly basis. This structures mirrors FM2G.
See how to assign funds center and auto approve. And see how this assignment relates to the Funds Center Hierarchy.
So this Web Hierarchy of qualifiers for FC_FSS corresponds to the first (100281 - not explicitly shown but FC_FSS) and third level of Funds Center heirarchy (101102, 101103, etc). The items below the 3rd level Funds Center represent cost objects that are assigned to the particular Funds Center.
So what are the other Funds Centers, the 2nd and 4th level Funds Centers? Can cost objects be assigned to these Funds Centers via FRC3 (cost centers) FRC5 (internal orders) FRC7 (WBS)?
Table FMZU0B is the table that maps cost objects to Funds Centers. I searched this table on Funds Center, 101101 and found nothing.
*FSS*
Select top one
Enter
"Staff assginments" soft button
Release Strategies
Workflow (table T16FW)
C indicates JOB
The position (S) 50001376 belongs to the organization (O) 50003253 and is described by the job (C) 50002737, which is assigned to the Release Code X2 (see table T16FW). More on this in pd_org directory.
From PPOM, there is not a view of the Funds Center, so you first have to go to PFOM and decide which Fund Center you wish to manipulate. The Fund Centers are associated with organizations, so remember the organization. Then back to PPOM and add or substract people from the organization of choice.
Select the Position beneath the Organization of interest and press "Assign holder"
Type is US (user in order to use Kerberos principal)
Name is Keberos principal
Time period is the time period of interest. If you want the user to pick up pre-existing workflow items, then back date the period.
Save.
Since the 4.6c upgrade a dialog box appears, Replace in period xx/xx/xxxx, User xxxxxxx with Person yyyyyyy. In production, the person is the same as the user. In SF2 the person does not seem to ever be the same as the user:
What's going on here... Research In the meantime, always click No. Workflow is tied to users not persons.