Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to demonstrate two different approaches that can be used to include number ranges in a transport for PR and PO.

Overview 

For the transportation of number ranges, a different procedure needs to be followed. Reason is that the settings for number ranges are not covered by the normal transport functionality.

(Table to use: NRIV with object name EINKBELEG for purchase orders and object name BANF for purchase requisitions.)

All intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.

There are two approaches for including number ranges in a transport.

Approach 1: Transport via Number Range Transactions.

 

For the maintenance of number ranges you can use the following customizing transactions:

OMH6 for the maintenance of number ranges for Purchasing Documents.

OMH7 for the maintenance of number ranges for Purchase Requisitions.

Via these transactions you can maintain the relevant number ranges as normal. Once created you select ‘Interval – Transport’ in the initial Number Range screen.

A pop up appears asking you whether you want to transport the intervals. Press Yes.

You are asked to create a customizing request. When you display the content of the created request, a * entry is visible for the relevant object name (EINKBELEG/BANF). This * entry assures that the complete table for this object name is deleted so this should NEVER be done.

If you do transport such a request, all number ranges within this object will be set to zero. So during purchase order creation the first number will be generated again which is already available in the production environment. As a result lots of short dumps will appear in your production environment.

 

To assure that only the relevant number range is transported, the following action needs to be performed:

 

  1. Enter the created customizing request via transaction SE03.
  2. Double click on the ‘Customizing Task’. In the example above this is DV1K954561.
  3. Go to change mode of this request.

  4. Double click on the object name or press ‘Function’



  5. Double click on the entry that is displayed

  6. Change the * entry into the new created number range and enter 0000 in the filed ‘To year’.
  7. Save the change.

 

Now the change request can be transported to production via the normal transportation cyclus.

Approach 2: Via the creation of a separate transport

Starting point for this scenario is that the number range that must be transported is created.

  1. Create a transport via transaction SE01 (Transport Organizer)
  2. Select ‘Customizing Request’ in the Create Request pop-up screen.
  3. Enter a short description and save the request. At this moment an empty customizing request is created in which you have to add the relevant configuration settings.
  4. Double click on the ‘Customizing Task’. In the example above this is DV1K954561.
  5. Go to the change mode of this request and perform the following actions:
      1. In the field ‘Program ID’ add:           R3TR
      2. In the field ‘Object” add:                  TABU
      3. In the field ‘Object Name’ add:         NRIV
  6. Double click on the ‘Object Name’ or press ‘Function



  7. Double click on the first empty line shown in the overview.

  8. Enter the following data in the pop-up screen:

Med. Field label

Field Name

Key Value

Client

CLIENT

Client you are working in (020, 310, …)

Object name

OBJECT

EINKBELEG for Purchase Order number ranges

BANF for Purchase Requisition number ranges

No. range no.

NRRANGENR

Enter the number range you created

To year

TOYEAR

0000