Number ranges query

dear gurus,
               i am having some queries regarding number ranges,.
        in number ranges of production orders i am finding..
number range group with check box under that i find the order types.Say(1234 -to9999)
pp01
pp04
zx01
.My requirement is I want to (detach) remove order type pp04.and I want to assign order type pp04 to different number range group.
please guide me>it is very urgent in client side.
                please help me
                                  guna         -

In co82,
Group -->maintain
inside the screen
keep coursor on PP04 and follow the menu path
Edit -->select element
Select the check box of group to which you want to assign and follow the menu path
Edit --> assign element group
then save.
come back if required

Similar Messages

Material Document Number Range query

Hi all,
How can I create Materila Doc Number Range Groups and elements . Pls note I want to create it new one and DO NOT WANT TO USE STANDARD .
Also how can I assign or relate or link this groups to Company code or Plant
Regards
Bhushan

1. go to MMNR Transaction
2. click GROUP - change mode
3. go to menu: GROUP -> INSERT (F6)
4. maintain new group data and material number intervals
5. save
6. assign proper material types to new group.
If you want to control material number you can use enhacement:
Source: IMG help:
"enhacement MGA00002 (for industry) or enhancement MGW00002 (for retail) for this.
For more information, see the documentation for the following components assigned to these enhancements:
Industry
EXIT_SAPLMG02_001
EXIT_SAPLMG02_002
Retail
EXIT_SAPLMG72_001
With the exception of the transfer structure, this function is identical to customer enhancement MGA00002 for material number assignment for the material master for industry. Please see customer enhancement MGA00002 for more information and for sample coding.
EXIT_SAPLMG72_002
With the exception of the transfer structure, this function is identical to customer enhancement MGA00002 for material number assignment for the material master for industry. Please see customer enhancement MGA00002 for more information and for sample coding.
EXIT_SAPLMGNK_003"
Hope it helps.
Regards,
wojciech

Number Range Query

Hi,
I have a requirement that number range for sales order and delivery to be same but it is not possible in SAP. Request if anyone can guide for solution like maybe prefix etc.
The requirement is that when we look at delivery number we should know the sales order number but without any document flow or report but by just viewing the delivery number the sales order number to be guessed correctly.
kindly help.

Firstly the idea of suffix like "S" for Sales Order, "D" for Delivery seems good...
But practically speaking it would be very hard, infact impossible to continue with same numbers for Sales Orders & Deliveries.
The main reason behind this Sales Orders may be blocked, cancelled, deleted. Similarly, Deliveries may be reversed or blocked & so on...
So over a period of time Sales Order & Delivery number ranges may not run in same sequence, no matter how hard you try... This is my practical experience.
The client can anytime see the Document flow & know the preceeding / suceeding number document numbers.
Hope this helps...
Thanks,
Jignesh Mehta

Number range query causes repeated scan by index

I have a query that seems to repeatedly call an index scan on a table for reasons I'm not sure about. Anyone know why it would be doing the index scan on totaldwellingarea in the dimensions table (DIMEN_PID_TDWELLAREA) repeatedly? This only seems to happen when I put on the range clause d.totaldwellingarea between scr.lowvalue and scr.highvalue.
I am using Oracle version 9.2.0.3.
select d.propertyid,d.totaldwellingarea, e.size_, scr.size_
from eqid e, dimensions d, brt_eval.size_code_ranges scr
where e.style not in ('1','A','G','L') and e.size_ = '0'
and d.propertyid = e.propertyid and e.style = scr.style and d.totaldwellingarea between scr.lowvalue and scr.highvalue;
CREATE
TABLE "BRT_ADMIN"."EQID"
 "PROPERTYID" VARCHAR2(20 BYTE) NOT NULL ENABLE,
 "EQID" CHAR(10 BYTE),
 "ZONE_" CHAR(1 BYTE),
 "AREA" CHAR(1 BYTE),
 "GROUP_" CHAR(1 BYTE),
 "GMA" CHAR(1 BYTE),
 "STYLE" CHAR(1 BYTE),
 "FLOORPLAN" CHAR(1 BYTE),
 "BLDGCODEABBR" CHAR(1 BYTE),
 "SIZE_" CHAR(1 BYTE),
 "CONDITION" CHAR(1 BYTE),
 "SUBGROUP" CHAR(1 BYTE),
 "UPDATED_BY" VARCHAR2(10 BYTE),
 CONSTRAINT "EQID_PK" PRIMARY KEY ("PROPERTYID") USING INDEX
 CONSTRAINT "EQID_PROPERTIES_FK1" FOREIGN KEY ("PROPERTYID") REFERENCES
 "BRT_ADMIN"."PROPERTIES" ("PROPERTYID") DISABLE
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('3734003158','E241RJR440','E','2','4','1','R','J','R','4','4','0','274892');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('5428001913','H113TMH330','H','1','1','3','T','M','H','3','3','0','263579');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('8798001037','J423DX0440','J','4','2','3','D','X','0','4','4','0','SYSTEM');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('6924000909','L423LR0000','L','4','2','3','L','R','0','0','0','0','275251');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('81640006040000304','P142223240','P','1','4','2','2','2','3','2','4','0','SYSTEM');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('6828004705','M812IW3340','M','8','1','2','I','W','3','3','4','0','275281');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('3622002125','K212RJO340','K','2','1','2','R','J','O','3','4','0','TEMP001');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('7492002946','H513RJO250','H','5','1','3','R','J','O','2','5','0','276022');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('2561002635','A221MOW340','A','2','2','1','M','O','W','3','4','0','275464');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('7380002035','P612MRU530','P','6','1','2','M','R','U','5','3','0','TEMP002');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('8396000929','J211RJO340','J','2','1','1','R','J','O','3','4','0','SYSTEM');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('8902001921','B123RJO340','B','1','2','3','R','J','O','3','4','0','272144');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('5094000612','L142RJR340','L','1','4','2','R','J','R','3','4','0','225293');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('8803005315','L312TMH440','L','3','1','2','T','M','H','4','4','0','225293');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('5378004026','D121MNU140','D','1','2','1','M','N','U','1','4','0','134965');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('5414005625','L311RJR340','L','3','1','1','R','J','R','3','4','0','275251');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('6286005917','E323RJR240','E','3','2','3','R','J','R','2','4','0','274951');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('7824000540','E314SE0140','E','3','1','4','S','E','0','1','4','0','274951');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('3200001829','H525LR0000','H','5','2','5','L','R','0','0','0','0','248930');
Insert into EXPORT_TABLE (PROPERTYID,EQID,ZONE_,AREA,GROUP_,GMA,STYLE,FLOORPLAN,BLDGCODEABBR,SIZE_,CONDITION,SUBGROUP,UPDATED_BY) values ('1102002714','G314MPW240','G','3','1','4','M','P','W','2','4','0','250794');
CREATE
TABLE "BRT_ADMIN"."DIMENSIONS"
 "PROPERTYID" VARCHAR2(20 BYTE),
 "DIMENSIONID" NUMBER(38,0),
 "LANDDATE" DATE,
 "BLDGDATE" DATE,
 "PROCESSDATE" DATE,
 "INPUTUSER" VARCHAR2(100 BYTE),
 "PLOTFRONT" NUMBER(38,3),
 "PLOTDEPTH" NUMBER(38,3),
 "PLOTSQFT" NUMBER(38,3),
 "TOTALDWELLINGAREA" NUMBER(38,3),
 "TOTALFLOOR" NUMBER(38,3),
 "SHAPE" CHAR(1 BYTE),
 "GARAGE" VARCHAR2(2 BYTE),
 CONSTRAINT "DIMENSIONS_PK" PRIMARY KEY ("DIMENSIONID") USING INDEX
CREATE
 INDEX "BRT_ADMIN"."DIMEN_PID_TDWELLAREA" ON "BRT_ADMIN"."DIMENSIONS"
 "PROPERTYID",
 "TOTALDWELLINGAREA"
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8318000324',506808,null,to_date('01-JUN-2001 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('19-JUN-2001 12:00 AM','DD-MON-YYYY HH:MI AM'),'DOMENIC J. DEMURO',15.5,56,868,1200,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8814000708',336134,null,to_date('01-JUL-1999 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('30-JUL-1999 12:00 AM','DD-MON-YYYY HH:MI AM'),'margaret jimenez',16,69.29,1108.64,2265,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8791002638',231697,null,null,to_date('29-OCT-2004 12:00 AM','DD-
MON-YYYY HH:MI AM'),'DMEB020',15,65.38,980.7,0,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('6138000961',409453,to_date('01-AUG-2004 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('01-AUG-2002 12:00 AM','DD-MON-YYYY HH:MI AM'),to_date('18-AUG-2004 12:00 AM','DD-MON-YYYY HH:MI AM'),'DMEB017',14.75,78.5,1157.87,1357,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8576002721',154908,null,null,to_date('29-OCT-2004 12:00 AM','DD-
MON-YYYY HH:MI AM'),'DMEB020',12,72.99,875.88,0,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('3851000509',441426,to_date('01-AUG-2004 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('01-NOV-2003 12:00 AM','DD-MON-YYYY HH:MI AM'),to_date('18-AUG-2004 12:00 AM','DD-MON-YYYY HH:MI AM'),'DMEB017',63.94,97.96,6264,2358,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('2889011105',498582,null,to_date('01-AUG-2000 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('14-AUG-2000 12:00 AM','DD-MON-YYYY HH:MI AM'),'ANTHONY CELLO',19.92,102.16,2035.02,1400,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('6960000520',535448,to_date('30-DEC-2011 12:00 AM','DD-MON-YYYY
HH:MI AM'),null,to_date('30-DEC-2011 12:00 AM','DD-MON-YYYY HH:MI AM'),'Donna Dirscherl',50,209.33,10342,0,0,'A','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8902000005',398306,null,to_date('01-JUL-2001 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('11-JUL-2001 12:00 AM','DD-MON-YYYY HH:MI AM'),'BERNICE murphy',40,98,3920,7040,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('4624001130',341318,null,to_date('01-FEB-2001 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('27-FEB-2001 12:00 AM','DD-MON-YYYY HH:MI AM'),'JANINE TRAVALINA',15.96,66,1053.36,960,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('2798005812',459363,null,to_date('01-JAN-2001 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('19-JAN-2001 12:00 AM','DD-MON-YYYY HH:MI AM'),'ANTHONY D ELETTO',15.5,60,930,1112,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('1940000212000008A',500949,null,to_date('01-NOV-2010 12:00 AM','DD-
MON-YYYY HH:MI AM'),to_date('02-NOV-2010 12:00 AM','DD-MON-YYYY HH:MI AM'),'GERALDINE WHITE',0,0,0,1068,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('1132006225',544051,to_date('01-AUG-2004 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('01-MAY-2002 12:00 AM','DD-MON-YYYY HH:MI AM'),to_date('18-AUG-2004 12:00 AM','DD-MON-YYYY HH:MI AM'),'DMEB017',16,63.5,1016,1088,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('6588004904',258106,to_date('01-NOV-2007 12:00 AM','DD-MON-YYYY
HH:MI AM'),null,to_date('08-NOV-2007 12:00 AM','DD-MON-YYYY HH:MI AM'),'DMEB025',15.5,109.88,1703.14,1660,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('3504001628',166760,null,to_date('01-JAN-2001 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('10-JAN-2001 12:00 AM','DD-MON-YYYY HH:MI AM'),'BERNICE murphy',14.83,63.5,941.7,938,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8817006645',285652,null,to_date('01-JUN-1999 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('22-JUN-1999 12:00 AM','DD-MON-YYYY HH:MI AM'),'ANTONETTE M. LAFAUCI',15.8,72.5,1145.5,1210,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('6450003427',115405,null,null,to_date('29-OCT-2004 12:00 AM','DD-
MON-YYYY HH:MI AM'),'DMEB020',14,50,700,0,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('5284002600',416035,null,to_date('01-JAN-1999 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('11-JAN-1999 12:00 AM','DD-MON-YYYY HH:MI AM'),'rose cappo',15,40,600,750,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8801003637',415464,null,to_date('01-OCT-2000 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('30-OCT-2000 12:00 AM','DD-MON-YYYY HH:MI AM'),'CARLA DOWNS',15.5,80,1240,1632,0,'E','0');
Insert into EXPORT_TABLE (PROPERTYID,DIMENSIONID,LANDDATE,BLDGDATE,PROCESSDATE,INPUTUSER,PLOTFRONT,PLOTDEPTH,PLOTSQFT,TOTALDWELLINGAREA,TOTALFLOOR,SHAPE,GARAGE) values ('8878000860',163537,null,to_date('01-MAR-1999 12:00 AM','DD-MON-YYYY
HH:MI AM'),to_date('30-MAR-1999 12:00 AM','DD-MON-YYYY HH:MI AM'),'VIVIAN REESE',15,60.5,907.5,1140,0,'E','0');
CREATE
TABLE "BRT_EVAL"."SIZE_CODE_RANGES"
 "STYLE" CHAR(1 BYTE),
 "SIZE_" CHAR(1 BYTE),
 "LOWVALUE" NUMBER(38,0),
 "HIGHVALUE" NUMBER(38,0),
 "DESCRIPTION" VARCHAR2(25 BYTE),
 CONSTRAINT "SIZE_CODE_RANGES_PK" PRIMARY KEY ("STYLE", "SIZE_") USING INDEX
Insert into BRT_EVAL.SIZE_CODE_RANGES (STYLE,SIZE_,LOWVALUE,HIGHVALUE,DESCRIPTION) values ('2','2',400,1399,'400 sqft - 1399 sqft');
Insert into BRT_EVAL.SIZE_CODE_RANGES (STYLE,SIZE_,LOWVALUE,HIGHVALUE,DESCRIPTION) values ('2','4',2600,3599,'2600 sqft - 3599 sqft');
Insert into BRT_EVAL.SIZE_CODE_RANGES (STYLE,SIZE_,LOWVALUE,HIGHVALUE,DESCRIPTION) values ('P','3',1300,1601,'1300 sqft - 1601 sqft');
Explain Plan:
OPERATION OPTIONS OBJECT_NODE OBJECT_OWNER OBJECT_NAME OBJECT_INSTANCE OBJECT_TYPE OPTIMIZER SEARCH_COLUMNS ID PARENT_ID POSITION COST CARDINALITY BYTES OTHER_TAG
PARTITION_START PARTITION_STOP PARTITION_ID OTHER DISTRIBUTION CPU_COST IO_COST TEMP_SPACE
SELECT STATEMENT CHOOSE 0 14 14 1 63 14
TABLE ACCESS BY INDEX ROWID BRT_ADMIN EQID 1 ANALYZED 1 0 1 2 1 16 2
NESTED LOOPS 2 1 1 14 1 63 14
NESTED LOOPS 3 2 1 6 4 188 6
TABLE ACCESS FULL BRT_EVAL SIZE_CODE_RANGES 3 4 3 1 2 1 32 2
INDEX FAST FULL SCAN BRT_ADMIN DIMEN_PID_TDWELLAREA NON-UNIQUE 5 3 2 4 1427 21405 4
INDEX RANGE SCAN BRT_ADMIN EQID_PROPERTYID_IDX NON-UNIQUE ANALYZED 1 6 2 2 1 10 1 Edited by: ReubenC on Oct 16, 2012 9:50 AM

I tried removing the index to see if that would have any effect. That appears to work OK. I would like to leave the index in place, however.
Looks like NO_INDEX Hint works. First time using hints... I don't suppose there's anyway to tell it to use the index for one part of the where clause but not a different part?
select /*+ NO_INDEX(d DIMEN_PID_TDWELLAREA) */ d.propertyid,d.totaldwellingarea, e.size_, scr.size_
from eqid e, dimensions d, brt_eval.size_code_ranges scr
where e.style not in ('1','A','G','L') and e.size_ = '0' and totaldwellingarea <> 0
and d.propertyid = e.propertyid and e.style = scr.style and totaldwellingarea >= scr.lowvalue and totaldwellingarea <= scr.highvalue;
select /*+ NO_INDEX(d DIMEN_PID_TDWELLAREA) */ count(*)
from eqid e, dimensions d, brt_eval.size_code_ranges scr
where e.style not in ('1','A','G','L') and e.size_ = '0' and totaldwellingarea <> 0
and d.propertyid = e.propertyid and e.style = scr.style and totaldwellingarea >= scr.lowvalue and totaldwellingarea <= scr.highvalue;Edited by: ReubenC on Oct 16, 2012 3:15 PM
Edited by: ReubenC on Oct 16, 2012 3:22 PM
OK figured all that out.

SD Revenue recognition-Query on Number range for Rev Rec

Hi Experts ,
I see that in VF45-Rev Rec overview transaction, the deferred value are captured as required.But when I try posting them into Revenue G/L account, Iam facing the below errors.
Error Log
1)Accounting document for collective processing 1000002092 was not created
2)For object RF_BELEG 0417, number range interval 88 does not exist FBN1
3)0148000018 000010 Non-processed revenue line: 0003010501 2009003 000 - successor: 000000 - bal. sheet accts: 0002035000
4)0148000018 000010 Non-processed revenue line: VPRS 2009003 000 - successor: 000000 - bal. sheet accts:
Can you suggest me the right config i need to do to over come this issue??
Also can any one explain the significance of this new number range in the FI config??
Appreciate your earliest support
Thanks in Advance
Banu

Hi Banu
For your First query , as the accounting document is not generated that is the reason it has given error also of maintaining number range in FBN1
For your second query , Maintain number range interval 88 in FBN1 with the from and To number range.
Just configure then your third problem should also get solved. If it is not solved let us know or else close the thread if your problem is solved
Regards
Srinath

Query of batch number range

Hi experts
I found that I can assign a external batch number to a material manually,but in background I have not assigned an external number range for batch, who can tell me that's why?
thank you!

Hi,
It is not relevant with No. Range of Batch
Go to SPRO > Logistics - General > Batch Management > Creation of New Batches > Define Initial Creation of Data for Batch Master Transactions > Here for Material Type select option as "C" (Automatic / No Manual)
Also check in SPRO > Logistics - General > Batch Management > Creation of New Batches > Define Batch Creation for Goods Movements > Here for Movement Type select option as "C" (Automatic / No Manual)

Query on number ranges?

hi friends
if PR is created automatically using MD01 i.e through MRP do we need to manually maintain number ranges and document type for PR or if any purchasing document is created automatically then do we need to manually maintain number ranges and document type
Thanks
regards
krishna

IF PR is created via MRP than system will pick up the number range and document type as per config.
In the PO creation system defualt NB doc type and number range automatically from config.
For number rabnge config you can use tcode SNRO
enter your object and maintain or go through SPRO

CRM ISA R/3 Edition on AP 7.0 Pricing Routine Number range error

Hi Experts,
For our R/3 ISA Secenerio I have developed a Pricing Prepare Routine (PRP). I have uploaded this routine into AP 7.0 ( which runs my IPC 5.0). Now when I try to register my PRP routine I'm not able to do so because of Number range not defined for Application V Scenerio A and Routine Type PRP.
My question are:
1) For a PRP type Routine( Multiple Implementation) is it important to assign a
routine number? ***( according to pricinguserexit manual dummy routine no
has to be assigned)******
2) If yes then how can i assign Number range for this combination.
NOTE: AP 7.0 has SP 7 ( So it fullfills requirment for Special scenerio)
I have never recieved a reply for my query from this forum... hope someone helps this time. :)
Regards,
Dipender Singh

go to http://www.configuration-workgroup.com/ and find technical doc about IPC 5.0 that i presented at Marco Island in 2006.

Reg: Vendor Account Group Number Range

Hi Guru's,
I have created 3 Account groups for vendor -
MV- Material Vendor , SV - Service Vendor , Ov - One Time Vendor
And i need to number range (external) like this for MV- MV10000 to MV19999 and SV - SV10000 to SV19999
i tried by XKN1 but the system says Enter the intervals without overlap .
Guide me to achieve this.
Thanks in advance
Regards
Anand

Hi
Thanks for your solution.. It means my intervals falls under a to zzzz.
i have a query A to ZZZZZ is alphanumeric or alphabetic?
Can we set the range only as alphabetic .. that is no numeric is allowed .
Regards
Anand

Subsequent credit Number ranges

Hi Guys,
We are running the t.code MIR6 for posting the invoice documents. Now the requirement is they need a different document types for Invoices and credit memos. In MM we can assign a document type to transaction in Logistics Invoice verification. Can we assign different number ranges for different transactions say invoice, credit memo, subsequent debit, subsequent credit etc... for the same transaction MIR6?
How we can differentiate the transaction because we can able to assign only one document type to the transaction and so that only one number range gets assigned to the financial document type?
Srinivasan.K

Hi dear
This is MM issue. Pls raise this query in MM forum for getting a good answer
Thanks
Chandra

How to transport number range group Configuration in Material Master

Hi,
I have this query regarding how to transport number range group in material master from one server to another.
Problem: There was no number range assignment done for a particular material type. So, i assigned the particular mat. type to a group which had some number range intervals with the help of T-Code MMNR.
But when i want to transport this config. to other sever, it is only transporting the interval but not the assignment done to that group. In the menu bar only Interval transport option is there.
Can anybody help me with this I hope the query is clear.
Regards
Vivek

Hi,
Number range objects can be transported using Workbench requests.
Thanks
Kishore

Number Ranges for Purchasing Info Record

Dear Guru's
Number range interval for Purchase info record can be created and assign to group and there are two group for Stock and Non Stock materials.
Now my query is how the system pick the number range ??? Since we don't have any assignment like PR,PO
My requirement is we have 3 company code - I need to have different number ranges for purchase Info record for each company . Guide me to achieve ...
Thanks in advance
Regards
Anand

SAP has provided only Two standard document Types for Pur. Info Records.
IL for Stock Material ( with matl No.)
IN For material Group (w/o MMR).
By default, if you enter Matl No. in the initial screen, system automatically picks the doc. type IL and the no. range assigned to it.
If you're not entered matl. no. in the initial screen, and proceed the Transaction further, system picks the doc. type IN and prompts you to enter Matl Group.
In the second case, the system picks up the no. range as per assignment.
Here in your case, you want create a new no. range and assign to your IL/ IN.
For this, you go to the transaction Define No. Ranges in Inforecord, from menu bar, choose Group-> maintain. Here you maintain your new no. range with a name. Now your new group is created with your required no. range.
Then select your new group ( Check box), select, IL, and click assign button and save.. Your IL is assigned to your new group and system picks the new No. Range when you are creating a Inforecord with Mat No. Similarly, you can change No. range for IN also.
or one more option you have.
In the first screen of No. Ranges Transaction, select change intervals tab button, you'll be goto intervals screen. There, from Menu bar, choose Interval-> change current No. Then you reset your current no. to Zero, save it. The again choose Change Interval, then in that screen, change the Interval with your new no. range.
Here in the second case, u need not maintain new groups. Just changing the Interval for the existing group.
You can adopt any one of these options.

Number Ranges - Best Practise

Can anyone advise what's the best approach if a particular number range is being used up for a sales order type? Do we assign another number range? What if we really run of number ranges, is there anyway to reuse the number range by archiving documents out?
Thanks
Peter

There are many ways by which you can acheive your desired result.
You can have number range based on Fiscal year. eg. in 2008 for Sales doc you are using no range 10, 1000000000 - 199999999 and say you exhaust that. this u can treat in two ways:
either Reassign new number range to the sales doc say 49, 2000000000 - 2999999999.
or reset the counter for the number range 10 to 0 (Zero) and use it. There will be no conflict in numder series use in the same fiscal year. As doc number does not total depend on number range only, it also take date into consideration.
Hope it clears you query. If not kindly revert or esle reward.
Take care. JP

Document types - number range

Hi Experts,
I have following query.
I am doing project which has three company codes and each company code has a manufacturing plant.
I have created document types for P.R., P.O.,Contract,Scheduling agreement and assigned the number ranges for the same.
Client requires that for each plant whenever any document is created in the system, it should start with the initial number and it shouls appear in sequential manner. Ex. if a P.R. is made for three plant the in each plant the P.R. number should be 1000000.
It should not be 1000001,1000002,1000003.
Please guide me how the same can be achieved for document types of P.R., P.O.,Contract,Scheduling Agreement etc.
I there any customization for the same.
Thanks & Regards,
Aditya.

A . Aaditya wrote:
Hi Experts,
>
> I have following query.
> I am doing project which has three company codes and each company code has a manufacturing plant.
> I have created document types for P.R., P.O.,Contract,Scheduling agreement and assigned the number ranges for the same.
>
> Client requires that for each plant whenever any document is created in the system, it should start with the initial number and it shouls appear in sequential manner. Ex. if a P.R. is made for three plant the in each plant the P.R. number should be 1000000.
> It should not be 1000001,1000002,1000003.
>
> Please guide me how the same can be achieved for document types of P.R., P.O.,Contract,Scheduling Agreement etc.
> I there any customization for the same.
>
> Thanks & Regards,
>
> Aditya.
Hi,
Do you mean, for each plant the starting no range should be 100000? pls clarify
Shiva

Number Ranges in Q.M

Dear Gurus,
We have two plants in our company code and we are implementing QM for both the plants.I have regarding number ranges--> Inspection Number Ranges for Inspection Characteristics,Number Ranges for Inspection Methods,Number Ranges for Inspection Plans,Number ranges for inspection lot..etc
My query is -->Are these number ranges maintained at client or plant level.I think its client,but no sure.How can define number for different plants for the all above mentioned .
Regards Ram

Ram,
As per SAP standard Inspection lot number range we can not maintain plant wise.
Please follow following path to get idea:
SPRO --> Quality Management --> Quality Inspection --> Inspection lot creation --> Maintain Number ranges.
Here you would see this number range are stored in inspection lot origin, they apply to the entire client. So it would be applicable to client wise not plant wise.
So if you maintain number range for "01" like From 010000000000 to 019999999999, then this number range would be applicable to all plant of client for 01 origin.
If you still want to assign number range plant wise then you can maintain custom table for number range inspection type and plant wise, but to define number range externally plant wise is not advisable.
Hope this helps.
Thanks!!!

Number ranges query

Similar Messages

Maybe you are looking for