cancel
Showing results for 
Search instead for 
Did you mean: 

Find next open number

Former Member
0 Kudos

In SAP R/3 you can, when creating an object, let the system "find the next open number" or "find number after last assigned".

Is it possible to make this function in MDM?

When creating a record I suspect an suggestion for the value of one of the fields. Auto ID is not an option because the user must be able to overrule the suggested value.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

You can try this workaround

1. Create the field of type Auto ID

2. Create one more field say RecordID and make it unique

3. Create one Assignment on the field RecordID and select the Auto ID field name in assignment expression i.e. assign the value of Auto ID field to this field.

4. Create one workflow with only one Assign step and pass the assignment created in step 3. Launch this workflow on Record Add.

By this, you will get one unique field which gets automatically populated on addition of record and is still editable for the user.

Regards,

Jitesh Talreja

Former Member
0 Kudos

Dear Jitesh Talreja,

Thank you. This was indeed the only sub-solution I could think of. The only trouble is that we are close to the end of the number sequence we use and we want to use the unused numbers because we can't use higher numbers as the other applications can't process those.

Kind Regards, Job Jansen

Former Member
0 Kudos

JJ,

Lets get tagged an STATUS field to your wide range of number sequence; like ( assigned, not assigned, avaialble, not available , Active and Inactive...and so)

and look for something Available status, to make use of them.

  • This might works when you do UPC assignment scenario.

thanks,

Alexander.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Job

1.Is it possible to make this function in MDM? - no, but you can set field as unique -MDM automatically control values unique for that field and if you filled dublicate inform us about it.

2. in MDM record ID isnt visable value, therefore usally used autoID. My point of view -havn't make sense create field special for user, otherwise user can fill wrong value and you need check it and inform user about it

Regards

Kanstantsin

Former Member
0 Kudos

Dear Kanstantsin,

Thank you. I did alrady make the field Unique but this is not sufficient.

We are migrating an other application and we have to use the same numbers and number sequence because the underlying application architecture does not change.

Kind regards, Job Jansen