Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to transport Number Range object ?

Former Member
0 Kudos

Hii

I need to transport an Number range object,the system asks for a request when saving the number range in transaction 'SNOR' but the request after being transported does not show the intended object,that is i am unable to get the number range object in the target systam.

Is there any way of transporting the Number range object ? or importing it explicitly in the target system.

Regards

Ajitabh

2 REPLIES 2

anversha_s
Active Contributor
0 Kudos

hi,

chk this.

General - Number Range Generation

  • In the 4.6x environment, SAP have included a number range generation

  • program just like those used for Purchase Order, Sales Order etc.

*

  • This SAP number range generation is an include program.

*

  • INCLUDE ZRANGENO.

*

  • Always have to be included in the main program data declaration

*

  • data: wnorange like INRI-NRRANGENR, "number range,

  • wsubobj like inri-SUBOBJECT, "sub object

  • wdocno(12).

*

  • Steps :-

  • 1. Number range Sub Object must be maintain in table ZSGRP

  • You can used transaction SE16 to create a table entries.

  • 2. Maintain number range and intervals in transaction code SNUM

*

*

call function 'NUMBER_RANGE_ENQUEUE'

exporting

object = 'ZOWNNO' "Create with SNUM

exceptions

foreign_lock = 1

object_not_found = 2

system_failure = 3

others = 4.

if sy-subrc ne 0.

  • message e086 with 'Lock error' sy-subrc.

endif.

call function 'NUMBER_GET_NEXT'

exporting

nr_range_nr = wnorange

object = 'ZOWNNO'

subobject = wsubobj

importing

number = wdocno "Number generated by SAP

exceptions

interval_not_found = 1

number_range_not_intern = 2

object_not_found = 3

quantity_is_0 = 4

quantity_is_not_1 = 5

internal_overflow = 6

others = 7.

if sy-subrc ne 0.

  • message e086 with 'Number Range' sy-subrc.

endif.

call function 'NUMBER_RANGE_DEQUEUE'

exporting

object = 'ZOWNNO'.

if sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

endif.

pls go thru this links.

refer the links

http://www.sap-img.com/ge003.htm

http://www.sap-basis-abap.com/sapmm009.htm

http://www.erpgenie.com/abap/code/abap33.htm

http://www.kabai.com/abaps/z26.htm

rgrds

anver

if hlped mark points

Former Member
0 Kudos

Hi,

this is described in the Note <b>52390:</b>

<b>Symptom</b>

Number ranges and allocation to a group cannot be transported.

...

<b>Cause and prerequisites</b>

For reasons of data consistency (this is the main reason why number ranges must not be transported automatically!!), <u>you should generally avoid transporting number ranges and recreate these in the target system</u>.

If the transport is absolutely necessary, in order to save maintenance time, you must first note the following:

You must always transport the "Assignment Process -> Number range" together, as well as the 'Ranges and Group texts'. No number range groupsmaybe created inthe target system/client for this process. ONLY THEN may the transport be carried out exactly ONE TIME (/Z1)!!

The only option for a danger-free transport of the processes is if no number ranges are created for this process in the target and source systems.

For transporting 'Ranges and Groups': In the target system, first ALL ranges are DELETED so that after the import, (Z1) ONLY the EXPORTED ones (/Z1) exist (otherwise you cannot ensure that no overlapping will occur!

If errors occur during the number range maintenance after a transport, start report RSSNR0T1 and enter the affected number range object as the parameter. The listed inconsistencies are cleared with 'Save'.

As these requirements cannot current be checked technically, a foolproof 'adhoc correction' is not possible.

<b>Solution</b>

A possible transport connection of the group table cannot currently be made to a central location, but must be made available by the respective application.

Regards,

Stefan