As always HR team is now asked to maintain data required for Finance but it is reluctant to maintain it as it adds workload..

Anyways I need to find a solution to somehow default the PO information segments using employee's organisation--> org definition --> others --> costing info --> cost centre.

Has any one done it before??
Any ideas?

We have lots of defaulting taking place, especially on the assignments screen, including Asg DFF attributes, costing and budget values.

We do it all via Custom Library.

Yep - we did just that at BAA. Worked fine. Had to assume that there would be no split costing in HR or course, as Finance don't cope with that. A concurrent process was run overnight to line up the PO costing field on the Assignment based on the costing for the employee.

You need to configure a Form Personalization in the Assignment to default the PO Information.

Hmmm - or write a concurrent process to run overnight - that'd be my preference (I don't like Forms Personalisations!)

Geoff, having had (limited) exposure to Forms Personalisations here at Fort Apache, I am interested to know what you don't like about them? Just interested is all, honest!

Forms personalizations are neat for doing simple things. But the functionality is limited/restricted. If you require more complex interaction and processing then its custom library.

There are also a few oversights in the Personalization functionality which i consider to be sloppy or lazy implementation. For instance...
... you can change field boiler-plate text, and alter LOV functionality, but you cannot rename the LOV title. So you could "modify" a form to rename certain fields to suit the client requirements (and replace the LOV code) but the moment they then click on the LOV you get the original field name/LOV name in the window. Sloppy. You cant get around this using personalizations, you can only do this using custom library.

... you want to disable the DFF block. Fine and dandy, but you are still left with the little [ ] graphic on the form where the DFF was!

However, if you also need the same processing to happen in the Self service pages then custom library obviously does not fully fit the bill, and you need to consider a more custom route...

Hey ho....I wonder if it gets any better in Fusion Apps