Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT

Gold Client: Executing the Number Range Utility

cancel
Showing results for 
Search instead for 
Did you mean: 
Troy_Raney
Digital Support
Digital Support

Gold Client: Executing the Number Range Utility

Last Update:

Jan 31, 2023 7:17:59 AM

Updated By:

Troy_Raney

Created date:

Jan 31, 2023 7:17:59 AM

Troy_Raney_0-1675167407304.gif

Environment

  • Qlik Gold Client

 

Transcript

Greetings! My name is Steve George and I'm a Senior Solution Engineer of SAP with a focus on Gold Client. In this video, I provide insight and how-to content for the Gold Client Number Range Utility. I feel obliged to mention that this content is an advanced topic, but if you have prior experience in working with number ranges, that could prove helpful here.

This video will focus on these key topics: use cases and the intended user audience, notable topics related to this program, and how-to execute this program. I will conclude with several useful topics, a summary of best practices, and where to locate additional resources.

The typical use case is to execute the Number Ranges program after having performed a client refresh by following one of these two processes:
Gold Client was used to copy master data from the source into an empty client.
A database copy was performed so that all data in the source was replicated to the target.

Because the organization's Basis team typically executes client refreshes, it makes the most sense for this team to own the execution of this program. It may be best to think of having to execute this program as a client refresh post-processing step.

Let's now spend time focused on a few notable topics related to this program.
It is important to manage number ranges in the target client because data is being copied from some other client - typically Production - into this target, and because users are likely creating new data in the target as well. Gold Client's solution is to increase or inflate the last assigned number to some higher number within each range. And just to be clear, this program is executed is within the target client.

You may wonder, what are the ramifications if this program is not executed? What could occur is that users will be transacting in the target client thus generating new data, and when the SAP program attempts to save the new data to the database, it realizes the data already exists and so generates a short dump because it does not know how to reconcile a situation where duplicate records exist. There are some visuals within the user guide to help explain how this situation may occur so reference this content if helpful.


Allow me to narrate the steps while walking through the process using the Gold Client user interface.

Go to t-code ZGOLD (Z-G-O-L-D).
From the Gold Client dashboard, select either of the Post Process buttons as the program is contained within both
On the next screen, select the Number Range Utility executable; notice the selection screen requires only minimal inputs
The processing options allow the user to execute the program in summary or update mode; I'm going to use the summary mode for this execution because I want to check the results before performing the actual update
The middle section is probably the most critical input as this is where the user dictates how large a buffer to create
I'm going to input a value of 10 and in a few moments, I will explain the impact of this value
The final section allows the user to apply the program's execution across all number range objects or to only a selection; I am going to use the default selection of all objects
Select the Execute button to run the program; its runtime is typically 5-15 seconds

This screen shows the program's output; the first eight columns of data are read just as they appear in the Number Ranges table whereas the 'Updated Number' column (in red) shows the values that will be applied if this program was executed in update mode. The output also includes the 'Remaining %' and 'Warning %' columns which may be useful to confirm that the inflated numbers will not cause issues. The 'Remaining %' is calculated based on the Updated Number value, and the 'Warning %' is simply being read from table TNRO which is where number ranges are defined.

So, how is the 'Updated Number' determined? Let's use this number range as an example. We can see the starting number is 45 with all zeros and the ending number is 45 with all nines, so the total range is 100 million. We can see the Status value is 4500022391 which means that more than 22,000 POs in this range have been consumed. The program first calculates how many numbers are still available in the range. It then takes this number and applies the user’s input, in this case 10%, to determine the increased value. Finally, the program takes this value and adds it to the Number Status which we can see is 4510020152 -- an increase of about 10 million. So, from a user's perspective, this means that when creating a new purchase order, the number will be created using this value and not this value.

I will now return to the input screen, select the 'Update Database' option, and execute the program again. At this point, the Number Ranges table has been updated accordingly.

Let me now share with you some useful content.

This program only updates internal number ranges; as such, external number ranges will not be impacted.

This program cannot be executed in production systems.

This program is not designed to prevent existing data in the target client from being overwritten.

The input screen provides an option of excluding number range objects from being included in the program's execution. Qlik provides a few known exceptions by default and others can be added, if needed.

The input screen contains an 'Execution Log' option that shows who ran this program and when.

If for some reason the Number Ranges program will not achieve your team's desired outcome, it may be necessary to use standard SAP processing instead.


This slide contains a summary of best practices.

With respect to the 'Increase by %' field, Qlik advises using a value between 5 and 20. Values lower than this may create only a short-term solution where the program must then be executed again, and values higher than this have been known to cause other various issues within SAP.

With respect to the selection criteria, use the 'All Number Range objects' unless the team has known exceptions.

Be sure and limit the access to this program to just Basis and/or Administrator roles.

For all details regarding this program, please reference the Gold Client Number Range User Guide located on the Qlik Help website. It includes content about the calculations performed by this program, additional details about number range exceptions, and charts to help explain why it is important to execute this program.

There was a lot of content shared in this video, but I hope that you found it to be of value. If this video and our related user guide still leaves you with questions or in need of support, please submit a support case and our team will respond accordingly. Have a great day!

Labels (2)
Contributors
Version history
Last update:
‎2023-01-31 07:17 AM
Updated by: