Enterprise Structure Configuration.

The purpose of this session, we're going to define the purpose of using the
Enterprise Structure Configurator.
We're going to describe the guided process within the ESC. And we'll explain how
job and
position descriptive flexfield segments can be defined by using the ESC.

What we're really talking about here is something called the Enterprise Structure
Configurator (ESC).
That's what our focus will be in this lesson.
And using the ESC can be utilized to populate the enterprise, the legal entity,
the division, the business unit, and
business unit set assignment.
Enterprise Structure Configurator is one of many tools or tasks that you can
utilize to populate some of these tables.

So when we say tables or objects, do you want to populate the name of your
enterprise?
That's the highest level umbrella. Enterprise basically equals client. Oracle would
be the enterprise.
Even though we know Oracle has multiple legal entities, we operate in many, many
countries.
We have, let's say, 100 different legal entities, but it all falls under the
umbrella of Oracle.

You can populate the name of your enterprise. You can populate your legal
entities-- only the required fields.
What's the legal entity name? What is the identifier provided by the country in
which you registered the entity?
What are the business unit names? What are your reference data sets? Are you using
divisions? They're optional.

When we talk about loading these high-level enterprise structures,

the task that you can use within Functional Setup Manager is called the Enterprise
Structure Configurator.
Some clients will use that.
Other clients will use HCM Data Loader to load any objects that HCM Data Loader
supports and/or Spreadsheet Loader.
And you also might go and create some of these values manually.

So let's say you're going to use Data Loader to populate all of your business units
and all of your divisions.
Well, we don't have a Data Loader or object for Manage Enterprise HCM Information.
You might go to that and define that and then use Data Loader for other things. You
have many different ways.

We're just taking a look at one of those ways here.

It's very common to load most of your objects through Data Loader when you're
talking about Core HR, Enterprise,
and Workforce Structures, as well as people data during your implementation.
We have training on Oracle HCM Cloud import data. So please take a look at that if
you need to understand that tool.

So let's give us some time here to talk a little bit about the Enterprise Structure
Configurator.
So the Enterprise Structure Configurator is an interview-based tool that guides you
through the process of
setting up basic enterprise structures. You're going to use the ESC to define the
org structure.
When it says job and position structure, all you're really doing with the ESC and
the job position is saying,
are you going to configure and deploy flexfields.

If you don't know the concept of flexfields, we do cover flexfields in detail in

the training called
Oracle HCM Cloud Extensibility.
You're not actually creating the job or job codes-- human resource specialist,
benefits analyst.
You're just indicating I know that I need these five flexfield segments, so I'm
going to maybe start configuring those.

Create organizations quickly through a guided process, which requires only some
mandatory fields.
For example, when we see the enterprise object, we might see five fields.
When we actually navigate to Manage Enterprise HCM Information and look at the
individual object,
there's probably 50 fields. So it's a quick way to get these enterprise structures
in.
But you still have to look at each of the individual objects to complete any of the
optional fields,
override any of the defaults.

So that's what I have right here. You update any optional fields in each task that
are not displayed in the ESC
by accessing each individual organizational task.
And we will do that. In this session, we're looking at using the ESC. In the
subsequent sessions,
I will go to each of the objects in the ESC and say these are all the fields. This
is what each field means.

So how do you get to this? If I go into the system, and I'm going to go to Settings
and Actions.
I'm going to go to Setup and Maintenance. And this is going to bring us into
Functional Setup Manager.
And then under our setup, I want to choose Workforce Deployment.
And then here, I'm going to search for establish enterprise.

And then it's going to highlight it. We could see that it's under Enterprise
Profile.
So if you look at the suggested order, in a previous session, we already talked
about geographies.
Well, when you use the ESC, one of the things that you do is define an address.
So you want the geographies loaded so, when you're defining that address,
you can select the city, the state, the county, the province, the postal code from
that list.
So you want to think about that order here.

So I'm going to go ahead and choose Establish Enterprise Structure. And while
that's loading, as I said before,
the ESC is one of several options that can be used to create your high-level org
structures.
So you've got HCM Data Loader. HCM Spreadsheet Loader can also be used.
So if we take a look here, this is an example of one that's already been created.

And one of the benefits of the ESC is your client might say we'd like to prototype
a couple of different structures.
We'd like to be enterprise as the high level but then underneath that some legal
employers, then divisions, then
business units.
Someone else might say, well, no, let's look at it where it's legal employer
business unit, then division
-- something like that. So you could prototype and look at each of the different
scenarios.

So when you're creating a structure, you're not
So if I brought up this example and then I just
defined three divisions.
If I go next to business units, they've created
units.
And here, we can see it might look like they've
populating the individual objects.
click on Next, so here they've
a bunch of different business
done business unit by country.

But if we go back to legal entities and we look at these legal entities, if I

navigated to manage legal entity or
manage divisions, I wouldn't see the divisions because someone hasn't loaded this
configuration.
So you're really just setting it up here. And after you've had discussions about
it, you're satisfied
with what you're going to use, then you could run a process to load the individual
objects.

So if I go back to the beginning, the first thing that would be defined would be
your enterprise.
So enterprise equals client. Then once you've get this information populated, you
click Next.
Now you're looking at your divisions. So divisions are optional.
And as you're looking at this structure here, I don't want you to look at this and
say this is the defined hierarchy,
that it has to be enterprise, then division, then more legal entities, then
business units.
You need to have discussions with your system integrator on what your structure
will be.

So, for example, at Oracle, I'm in the business unit of Oracle University.
That business unit spans many legal entities. I have colleagues who are in Oracle
India.
I have another colleague who's in Oracle UK, maybe another colleague in Oracle
France.
So that business unit is above or spans multiple legal entities.
In some organizations, you're not going to do that. You might have a business unit
or business units within a
legal entity. You define your divisions if you're going to use them.

So if we look at those legal entities, so it's the name of the legal entity.
The legal entity identifiers that you see are issued by the issuing country.
Then, you could create your additional business units.
And as I said, this example looks like they're doing a business unit for each legal
entity.

Then, we talk about something called reference data sets.

So as you work your way through these, you're filling out the required information.

If I go ahead and click on Save and Close, once that's been viewed, you've decided
this is going to
work, you could load this, and it would populate those individual tables.

So establish enterprise structures-- I kind of walked you really quickly through

the first part of the ESC.
The second part of the ESC is once you've created it, if I go back into the system,

and then I can click on this Configure Jobs and Positions.

Oh, it's telling me I had to highlight one, so let's go ahead and get rid of that.
And I have to highlight it first and then Configure Jobs and Positions.

Again, you're not setting up your individual job codes or your individual
positions.
Those are not enterprise structures. Those are work structures.
So they're created manually or through Data Loader, Spreadsheet Loader.
But this is just asking you, hey, based on the type of organization you are, we
think you should utilize jobs.
Or do you want to explore other options around positions?
So it's going to ask questions. So maybe I just want to explore other options.

And then it starts to go through. And it's kind of just like a question and answer.

And then at the end, it says use jobs. Yes, I want to use jobs. Or I could say, no,

I want to use positions and hierarchies for reporting.

So just because it makes a recommendation, you don't have to follow it.

Now once that's done and we click Next, then it's saying, well, now that you've
decided that
you're probably going to use positions and jobs, do you want to start to create
your flexfield segments?
So what is the name of the segment? Maybe travel required, and it's going to be a
character segment.
So you still have additional steps to do, but you're starting to create those
additional fields.

Oracle delivers 65 additional segments on most of our objects that are hidden in
the UI as delivered.
But you have the option of creating and then tracking additional information using
flexfields.
So maybe it's that you've tracked a field in your previous HCM system.
You need to track it in HCM Cloud. Where do you do that?
So what you're going to use flexfield segments for is entirely going to be up to
you.
You would have to define that information.

So if I did a really simple example here, maybe when we're looking at here,
we're saying enterprise level for position or enterprise level for job.
What that means is that every single position is going to have this flexfield
deployed,
or every single job is going to have that flexfield deployed.

If I click Next and go to Contextual Attributes, then, when you're adding things
here, you can add it based on business unit.
So for the positions in this business unit, I want to deploy a flexfield.
But for other business units, I don't. Or maybe for each set of jobs that I'm
creating
I want to deploy thelexfield and, in other cases, I don't. So I'm going to go ahead
and cancel out of here.

And then another thing you could do here is Review Results. And this is just going
to simply show me what I filled out
in each of those steps of the guided process once it decides to load,
so your divisions, your legal entities, business units, reference data sets.
You've also got this reporting structure. Now this is created in the ESC as a
default org tree,
but you can certainly modify it, override it-- whatever you need to do.

We could also download our technical summary report. I'll go ahead and download
that to my desktop.
And then I'll go ahead and open it up. And then you can see it's got your different
contents.
You can flip to different sections, take a look at what's been defined.
And when you're filling out the enterprise, you didn't see anything about worker,
so no generation or employment model.

This is giving you an example of some of the default fields that you might see as
an organization
that you might need to override.
So, again, it gives you some examples of location information. It gives you your
legal entities that you defined.
I'm going to go all the way to the end of the report. And then you can see this
management reporting structure.
So this is the org tree that was defaulted in the ESC. Obviously, you could use it
as defaulted, but you'll likely
want to do some modifications.

Then here you see an example, your ultimate holding company.

You see some divisions. You see some additional legal entities.
You don't see any business units in this example, which you have to have at least
one.
And again, just because you see divisions above legal entities doesn't mean that's
how you have to have
your structure defined.
You decide the hierarchy when you're having your discussions with your system
integrator.

And this takes us through the job and position structure.

So I said, this is where you start to create your flexfield at the very beginning
of the ESC
asks which type of industry you are.
And one of the reasons it uses that is to suggest using jobs or positions.
If you look in the student guide and the notes below this slide, it does give you
an example of where it might
recommend position versus jobs.

And then here's an example of coming up with potential flexfields, so define

segments in the position and job flexfields
for further identifying job and positions in the enterprise.
Set enterprise level attributes to identify separate components of the position.
Use descriptive flexfields to capture additional information when you're creating
jobs and positions.

So I already did the demonstration when I was in the Enterprise Structure

Configurator.
I showed you how to walk through that just very high level.
And now I do want to go back into the system, and I want to go to Home.
And what I said to you when you're ESC is that it's one of many tools that you can
utilize to load your structure.
Well, from here, I'm going to go to My Client Groups. And then I want to go to Data
Exchange.

So Data Exchange is where, if you have the security permissions,

you can access information about which objects can be loaded through Data Loader.
So again, we have that import data training, so please take a look at that.
But if I come here into Data Loader, then I come into View Business Objects,
this is going to give me a list of all objects we support.
And we often support additional as we move from one release to another.

So just to provide you an example-- I'm just going to move this over a bit here.
And I'm going to put in, let's say, Global HR. And what it's gone and done for me
is it's kind of filtered my list. So if you start looking at the different things
that you've got here-- location records, grades-- if you're scrolling down, you
can see departments and org hierarchies and positions and person data. So you
could use this process in order to load your positions and your jobs.

But there's no place in this list to load the enterprise. That really doesn't
exist in other applications. We don't load your legal entities through here
either. So those can be done manually. There's also a link directly on legal
entity to create it. If we looked at organizations, that could load divisions.
That could load departments. They both fall into a category of org. So you want
to take a look at this and see if it's supporting the different objects through
Data Loader, Spreadsheet Loader or not.

That's going to take us to the end of this discussion. So we talked about using
the Enterprise Structure Configurator. It's one way to start creating your
high-level enterprise structures. You can create multiple scenarios, have
discussions about which scenario works best, and then load those to the
individual objects.

And then once you've done that, you still need to bring up the Manage Enterprise
HCM Information or Legal Entity HCM Information or business units or divisions
and complete any of the fields that weren't required, maybe any of the fields
that defaulted and you want to override them. But this is a nice, quick way to
get those enterprise structures created. We also took a look at the tasks within
the ESC and talked about how you could start to create flexfield segments as part
of using the Enterprise Structure Configurator.