cancel
Showing results for 
Search instead for 
Did you mean: 

How can I should the position number in sequence via ppom_old or ppome

Former Member
0 Kudos
633

Our user creates the position number via ppom_old and get the position number from this screen. The position number has been shown on sequence. However, something seems collapse. Do you guys know how I can show insequence again?

View Entire Topic
Former Member
0 Kudos

Hi,

As Shobana said, position numbers, Org unit number and job number are in sequence.

for example: once you create position and then org unit the sequence will be like 1 for position and 2for org unit. This way the number range will work.

thanks,

Vasu.

Former Member
0 Kudos

I found the system behavior is not what mentioned. For example:

Org Unit object ID: 60001218

Position ID: 70003982

70005728

20101084

70001205

What shown on via ppom_old is as below:

Org Unit 60001218

Position 70003982

Position 70005728

Position 20101084

Position 70001205

Seems the position can't be shown in sequence. Is that I can do something in order to sort in ascending order?

Former Member
0 Kudos

It is based on Priority (Edit-> Priorirty)

Use

Sequence Priority of Objects

The Priority field is optional. It is used to determine the sequence in

which objects are presented in Simple Maintenance and Structural

Graphics.

When multiple objects are located on the same hierarchical level of a

structure, these must be ordered in a specific sequence from left to

right (or from top to bottom).

This is done by assigning alphanumeric priority values, where the value

1 is the highest (far left or top) and 99 the lowest priority (far right

or bottom).

If you specify no priority, the system places objects according to their

object IDs.

Priority When Defining Evaluation Paths

It is only necessary to prioritize evaluation paths as an exception.

Generally, you should use '*', so that all relationships are read.

Use the Priority field to define evaluation paths if you want only

objects which are assigned a certain priority (see above) to be

considered in an evaluation path.

Note

You can find more information on the meaning of the priority field with

reference to evaluation paths in the online IMG documentation for

'Maintain evaluation paths'.

Priority for Responsibilities

If you are using responsibilities for role resolution in Workflow, you

Example: There are various responsibilities for a standard role for

processing orders, grouped, for example according to order value (one

responsibility for orders up to a certain value, another for orders with

a greater order value).

Assuming that orders for a particular customer are always to be

processed with the same responsibility (and therefore by the same

agent), you can access it via another responsibility with a higher

priority that contains the customer name as the only criterion. The

responsibility (-ies) with lower priority, and therefore the order

value, is then no longer taken into account during agent determination.

Use only numeric values here, and note that, logically, the

responsibility with the highest numberic value in this field has the

highest priority.

Procedure

1. Sequence Priority of Objects

In Create mode, assign a priority to the objects you wish to rank.

To do so, assign an alphanumeric value (1, 2, 3... or A, B, C...) to

each object.

2. Priority When Defining Evaluation Paths

In the Priority field, enter the priority or priorities for objects

that should be considered in evaluation paths. Enter "*" if you want

to have no restriction.

3. Priority for Responsibilities

Maintain the priority directly in the detail screen for the

responsibility or in the overview screen for the responsibilities

for the rule. Note that you must use numeric values here. On the

overview screen, the system sorts the responsibilities in descending

order of priority.