Forecast for new fields on Nakisa

[Former Member]

Hello all,

I need to see this fields on Nakisa.

Birth date

As known as

Civil status and descriptive

Number of children

Social Security scheme and descriptive

Professional category and descriptive

District

County

Postal Code

Gender (male or female) and descriptive

Country birth and descriptive

Number of hours per week

Qualifications

Email

Area and descriptive

Formation and descriptive

Upward feedback

End date of contract

End date of experimental period

In resume its 20 news fields. Could you tell me how many time i will spend to implement that?

Note: It's my first time on Nakisa.

Best Regards

João Regalado

[lukemarson · Accepted solution]

HI João,

For an experienced consultant this could take about 1 day, but if you are inexperienced then I would give yourself 3 to 5 days to do it.

Best regards,

Luke

[Former Member]

Hi Luke and Stephen,

Thanks for your quick responses and relevant questions.

This estimate was important for me to have an idea how many time I will spend to implement.

Now I have an ideia

Many thanks for everything

João Regalado

[StephenMillard]

João.

Whilst I think Luke probably has a much better appreciation of the timings than me, I'd suggest it might take a bit longer depending upon how these fields are being used.

Where are the changes to be made?

There are a number of places in which these fields could be added.  Are they all being added in the same place?  Are any of them being added to multiple places (I'm taking a baseline here of assuming at least for both standard and basic modes) - e.g. employee/position details panel and manager business card and one or more views?

Are there any additional formatting requirements?

What format should the dates take?  Are there any fields you need to set to a specific number of decimal places or need to remove leading zeroes?

Lookups 'and' vs. 'or'

Some of the fields you mention are being retrieved along with a description.  Are you going to display both of these in all cases or just the description for all or some?

Documentation

Presumably you are documenting the configuration changes you make.  Does this need to be factored in or have you already accounted for documentation?

Testing

In terms of implementation do you include testing time in that?  If so do you already have suitable data directly to hand that will allow you to quickly test each piece of data in each place ... or do you need to factor in time getting that as well?

Learning Curve

I consider myself quite bright and technologically capable.  I've been working on OrgChart since my first day on the job about seven months ago.  I still run into problems at least a couple of times a week in configuring things.  Whilst I'm at the point where I can figure a lot of them out on my own  I still have to fall back on the support of other more experienced implementers.  Consider the channels you might use (e.g. this discussion space) and how much delay you might incur on your first time through.  Do you need to consider the elapsed time or time spent working on an issue in your estimates?  I'm guessing a bit of both.

You suggest that you have got 20 new fields to add.  I make it that you've got between 19 and 26 new items of data to be added to one or more locations (views, panels, listings) in OrgChart.  So assuming you have test data readily to hand, encounter no issues, have a good understanding about where in SAP the data will be pulled from and the format you will display it in; assuming an 8 hour day and hitting the 5 day mark, that's about 1.5 - 2.0 hours per field.

Remember that this would be the allotted time to include the extraction of the data from SAP into the one or more areas in OrgChart with the correct formatting, documentation of the change and test of the change.

So I can't say for certain what your supporting knowledge (e.g. SAP, XML, XSL, databases) is, what training you've had (if any), how much background reading you've done (if any), how clear the requirements are in terms of precise detail, etc. ... but my instinct is that even five days might be optimistic if you really are starting from a blank slate with less than crystal clear requirements.

Stephen.

[lukemarson]

It is worth noting that project-related items, such as documentation, are not included in the "forecast" that I provided. My forecast is also based on an SAP consultant being involved in the project who knows OM/PA to a reasonable level. However, requirements should always be gathered before works begins and this requirements gathering is also not part of the "forecast". I also assume that the Live architecture is being used as this is the SAP and Nakisa best practice approach.

Some of the fields come from the same infotype tables or related infotype table, meaning many of them can be grouped together in a single NakisaRFC function so that few functions are required (depending on the use). For example, many of the address fields are from the same infotype table and a number of the fields are contract fields, which are also from related tables.

Dates need to be defined in the NakisaRFC functions, so this would also be done at the same time.

Once you have an understanding of the SAP infotype structure and the application architecture (such as defining dates) then the data work becomes much more of a managable task. The more difficult part for this is the work for displaying the fields, rather than creating the NakisaRFC or SAP Extractor functions.