Leading Space in Number Range

hi,
My requirement is to allow the user to enter a leading space in the material number creation in MM01. The number range for external number is from 000000000000000003 to ZZZZZZZZZZZZZ. So when i enter the material number with leading space I am getting an error message as number out of scope. What should be the FROM Number for the number range to accept a leading blank?
Please provide suggestions
Thanks!
Janani

hi u can pass like this ,
data: test(30) value '00000000000000000000000000003',
test1(10) .
test1 = test+20(10).
then it is possible,
reward points if useful,
venkat.
Edited by: venkat appikonda on Mar 6, 2008 2:53 PM

Similar Messages

Number Range object skipping numbers SAP

Hi All,
Number Range object skipping numbers SAP "EINKBELEG" . While creating Purchase order with transaction code me21n, the purchase order is skipping odd numbers. I have checked the transaction code "SNRO" there is no buferring set on the object.
Please help

Are multiple users creating Purchase Orders at the same time?
If yes then this is possible. Because Number Range (unique Number) is assigned to Purchase Order at the start of the Transaction (ME21N).
Thus if multiple users are creating Purchase Orders at the same time & some of these users may have not saved the Purchase Order after partially creating it... This may lead to particular Number Range to be skipped as the following number is already assigned to some other Purchase Order.
Hope this helps,
Thanks,
Jignesh Mehta

Incremental number range in non leading ledger

Hello Experts,
I have a serious problem with regard to number ranges in non leading ledger.
I have defined number range from 8000 to 8999 for document type SA. When I do a posting in FB50L, document number for non leading ledger is created as 8001. I am OK with this. But system is showing current number in use as 8099 instead of 8001. I have changed manually the current number as 8100 and posted one more document. Now document number is 8002, but number in use showing as 8199. If I post now document number will show as 8003, but number in use will show as same 8199.
Please advise me how to resolve this issue.
Thanks in advance.
Regds
Joy

Check in SNRO for numbe range object RKE_BELEG if any buffering has been set.
If yes, then go to Edit-Set up buffering and set to No buffering.
Also check in FAGLFLEXA on the last document number posted and maintain that number as the current number in number range in FBN1.
Thanks and regards
Kedar

Number range in Lead Transaction

Hi ,
In my Sandbox we have created one lead transaction and assigned one number range to that transaction.Now suddenly we figured out that one number of that range is assigned to more than one transactions of the same T type. eg 116 number is assigned to two different lead transactions created at two different times from the same transaction type. Is it usual scenario pls let me know how to debug the problem.
Thanks,
Ambrish

Hi
Run the archiving program which is by SARA transaction.
Put the archicing object CRM_LEAD.Its shall pick up all the transactions which are to be archived and put them in a flat file.
For further information refer to the link:
http://help.sap.com/saphelp_crm50/helpdata/en/e6/c66f3b6c980c3be10000000a11402f/frameset.htm
Regards
Rekha Dadwal

Removing leading spaces in a decimal number

I have a decimal number field of length 28 with 9 spaces.I have to print it right justified and remove the leading spaces.I appreciate if anyone can let me the statement for this

Hi,
Try this..
DATA: V_P TYPE P DECIMALS 2.
V_P = '112.00'.
WRITE: / V_P.
DATA: STR TYPE STRING.
STR = V_P.
SHIFT STR LEFT DELETING LEADING SPACE.
WRITE: / STR.
Thanks,
Naren

External number Range with leading zeros for Handling Units

Hi Experts
    My requirement is to use the External number for the Handling Units provided by vendor.That number starts with 2digits"00"+18 for Example:00123456789123456789
I am Using HU_VEKP Object for no range and maintaining
External No Range From 00000000000900000000 to 00000000000999999999.
But When i am giving Number 00000000000900000001 its only taking
900000001.
Kindly suggest me the right way to take leading zeros.
Rewards for answer sure if it works.
rajesh

Hi Laksmipathi
                      I am maintaining the number range for External number range coz its vendor supplied HU.
           But the prefix zeros has meaning for identifying the Handling unit Functionality.In realtime IF prefix contains Say "0000" it refers to carton
If prefix contains say "0010" it refers to pallet.
           So i need to satisfy there requirement.For example If it is for material number we can maintain In OMSL by check box of leading zeros.
            But i am not able to find any setting for this Handling units.U can check this object HU_VEKP in SNRO tcode where i am maintaining Number range.
Thanks give suggestion
RajeshS

Vendor Master External Number range

Hi,
There is a single number range object for vendor account groups
you have suppose five different account groups
suppose
for LIEF i am using internal number range starting with 10..up to 10 digit
for Vedor i am using external say A to ZZZZ up to 10digit
Now i have a account group for which i want to use P1000 to P9999 (External)
when i do this system allows me to create vendor even if i put P100000 bcoz it also considers
the balance 5 blank spaces
I can not customize the object to use it up to only 5 places since other number ranges are using
10 digit i also tried to use P-1000 to P-9999 but no use
Anybody has solution on this,please advise
Best Regards
Diwakar

Hi Charlie,
Thanks for your reply but client does not want to use it with
leading zeros
they want it like P1000 to P9999 Only
Please advise
BR
Diwakar

Lexicographic flag setup and material number range change

Hi gurus,
got the following situation:
AS IS:
Tcode MMNR: Number range for material master part number: AAAAAAAAAAAAAAAAAA to ZZZZZZZZZZZZZZZZZZ (lenght 18, external assignment)
Tcode OMSL: Lexicographic flag IS NOT setup
Tcode OMS2: For all material types flag "External no. assignment w/o check" IS SETUP
Basically we can't create numeric only part numbers.
The new requirement is to be able to create numeric part numbers like:
1234
12345
0123
01234 (where the leading zero is a significant character for the part number)
By doing the following changes:
MMNR: change number range 000000000000000000 to ZZZZZZZZZZZZZZZZZZ
OMSL: setup lexicographic AND leading zeros flag
OMS2: clear flag for External no. assignment w/o check
I see I do achieve the result: numeric part numbers can be created, leading zeros are managed in the correct way and all numeric part numbers are LEFT-aligned, so looking to MARA you would see part numbers like this:
00012345
012345
012345V
09CATALIST1
0AFVAU0001
12345
23225V
23243V
2SIMBACK3210
I did already tried all the above changes in the quality system, then created a numeric part number and an alfanumeric part number, for both of them did create a PO, Inbound delivery, posted MIGO, created a sales order, outbound delivery, PGIed without any issue, stock was displayed and managed correctly by the system, same for material docs.
We already thought about BW, so in case we do the changes BW would be ok.
Apparently everything is fine so I should go for the production system BUT........ in my mind I'm thinking that OMSL Tcode is usually setup day 1 of an Sap project and then usually you forget it... I have the fear that even if everything looks fine (and Sap allows me to change the customizing), I'm going to muck up the system...
Have you ever had the same to do ? I already saw posts similar to this one but already existing conditions were different so to me this case looks like unique so far..
Any help, suggestion, whatever will be highly appreciated, especially cause I have to take a decision by tomorrow morning
Many thanks in advance !!
Enrico
Edited by: Matt on Aug 13, 2011 7:39 AM - profanity removed

As you never had numeric numbers, it should not create a big problem.
I am working in a system with lexicographical setting in use.
But you have to keep in mind that your sort sequence is quite different to numeric numbers, like this:
1
10
11
12
2
3
31
311123
32
32012
4
And you may get the one or other issue if you download material numbers to Excel, with wrong settings you will loose your leading zeros.
A similar effect happens most of the time if user not very familiar with Excel give you a file for an upload, as this often is prepared without leading zeros, which could cause a load to the wrong material if the remaining number would be a duplicate:
0123 and 123
Of course is a selection by number range not that easy as it is with numeric numbers. Usingthe first example a range from 1 to 3 includes materials 10, 11 and 12 as well

How to change number range for document type ?

Dear All
Experts
How to change the number range for document types for entry view? I am trying to change the number range for all document type as per defined ranges in FBN1, but at the time of saving document type and number range the system is throwing error message as
Doc. type C1: Number range 07 is used for ledger L6 with doc. type AE
Message no. FAGL_LEDGER_CUST093
I have defined a leading ledger in system too with these settings
1)     Define ledger for accounting.
2)     Defining currencies for it.
3)     Defining ledger group for the same.
4)     Defining accounting principles
5)     Assignment of principles to leading ledger.
Are there any extra settings required for leading ledger settings?
I have some doubts those are :-
How document types defined at ledger level?
How to define them at leading ledger level? (Like my case)
Focus on this will be appreciable.
Regards,
Sharvari Joshi.

hi ,
The document numbers in the leading ledger and the non leading ledgers should be in sync, they should not have any differences, so incase you are trying to change the number range for C1, the number range 07 is already been assigned to doc type AE. i guess you have cant use 07 for C1. may be you can try out with an other number range. check this and let me know if you are able to do this.
coming to
1.How document types defined at ledger level?
2.How to define them at leading ledger level? (Like my case)
Ans 1. please try defining document types for entry view in a ledger.
path : SPRO- financial accounting new -financial accounting global settings new - document -document types -define document types for entry view in ledger.
upon prompt enter the ledger and go ahead creating the number ranges for the document types.
Hope this helps.
Regards
amrutha

Best practice for Number range buffering in SAP BI for FI Cubes

Hello Experts,
I have a question regarding Number range buffering. What i have observed is if we use more number of background processes while loading data, it for sure creaets locks with NRIV table bcoz of more calls for bufffered numbers with multiple processes.
But there is a clause in SNRO while we buffer 'Main Memory' that it should not be used for Financial documents. I understand that this is for serial assignment of numbers for Documents and acoounts on the backend ECC, but does this even stand true for DIM ID's which we are buffering while loading data into a FI Cube?
I have looked up a SAP note 1398444, which talks about NRIVSHADOW and parallel buffering and different use case scenarios.
Which one of those should be used if I need to buffer my Dimension while loading a FI Cube in BI with maximun background processes?
Please help me understand the difference?

hi,
well the message is just like a warning to signify that incase you load more number of new records then your existing limit of buffer then you will have to increase accordingly if no then you can ignore
if you want to understand the reason it like this....
if there is not sufficent buffers space available and then process would be rollback and the existing numbers will get lost resulting gaps between the document numbers and for applications like finance this is not desirable .
see doc more details
http://help.sap.com/saphelp_nw04/helpdata/en/95/3d5540b8cdcd01e10000000a155106/frameset.htm
Also if you are not sure you ask your basis team for Early watch alert report in their you can easily see whether number range buffering is really required or not, if yes then for which object/dimensions
Also check below SAP Note:449030 and 62077
hope it helps
regards
laksh

How to achieve Number Ranges in third party CRM tool and in SAP CRM

Hello Guru's,
My business requirement is I have to create LEAD from third party CRM tool to SAP CRM and vice versa i want to maintain number ranges for created lead in both side.
How can I achieve this please provide me your valuable suggestions and document.
Thank's In Advance

Hi,
In SAP IMG screen maintain the external number range in CRM through the below path.
CRM-Transactions-basic setting-Define Number range.
Also maintain the same number range for lead in the third party crm.
Regards,
Ashish

Leading spaces in excel file from ALV

Hi Guys,
once I export a record from ALV to excel. Some values I think all values that are TYPE I. How can I remove this leading spaces.
Ex: '                                                      100'
something like that.. so if you dont expand the column with you wont see the value 100. I checked the internal table being passed to ALV. It doesnt have leading spaces also in the ALV display. there is no leading spaces. Is there something to to with column width optimization? I need this to optimize the column headers. Thanks in Advance!
Regards,
Michael Nacionales

There is one table CRVS_B with field SFHNR, while creating PRTS I need this field, so I do like this:
select max( SFHNR ) into l_sfhnr
from CRVS_B.
add var to l_sfhnr.
So for example l_sfhnr is equal to 000000000000000010, then after add, it gives me 11, and surprisingly in database 11 is placing position in such a way that last char is empty so it is not 11 but 00000000000000011 ( 17 chars ) as after 11 one empty space, and when it comes next time:
select max( SFHNR ) into l_sfhnr
from CRVS_B.
add var to l_sfhnr.
the value of l_sfhnr is still 000000000000000010......
else try this
Hi
Field_catalog:
Field catalog with field descriptions
2.7.1. Description
Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
all fields in this structure are to be output
the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
Positioning
row_pos (row position)
value set: 0, 1 - 3
Only relevant if the list output is to be multi-line (two or three lines) by default.
A multi-line list can also be defined by the user interactively if the default list is one-line.
The parameter specifies the relative output line of the column in a multi-line list.
col_pos (column position)
value set: 0, 1 - 60
only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
Identification
fieldname (field name)
value set: internal output table field name (required parameter)
Name of the internal output table field which is described by this field catalog entry
tabname (internal output table)
value set: SPACE, internal output table name
This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
Data Dictionary reference
ref_fieldname (reference field name)
value set: SPACE, Data Dictionary field name
Name of the Data Dictionary field referred to.
This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
ref_tabname (reference table/structure field name)
value set: SPACE, name of a Data Dictionary structure or table
Structure or table name of the referred Data Dictionary field.
This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Reference to fields with currency/measurement unit
Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
There is a field in the internal output table which contains the associated unit.
There is also an entry in the field catalog for the unit field.
(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
The association of a value field to a unit affects the output as follows:
appropriate decimal places display for the unit
an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
Link to currency unit
cfieldname (currency unit field name)
value set: SPACE, output table field name
Only relevant for amount columns with associated unit.
Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
ctabname (internal currency unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Link to measurement unit
qfieldname (measurement unit field name)
value set: SPACE, output table field name
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Column output options
outputlen (column width)
value set: 0 (initial), n
For fields with a Data Dictionary link this parameter can be left initial.
For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
initial = column width is the output length of the referred Data Dictionary field (domain).
n = column width is n characters
key (key column)
value set: SPACE, 'X' 'X' = kex field (key field output in color)
Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
key_sel (hideable key column)
value set: SPACE, 'X'
only relevant when FIELDCAT-KEY = 'X'
Key field which can be hidden interactively.
The key column sequence cannot be changed interactively by the user.
The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
no_out (field in field list)
value set: SPACE, 'X' 'X' = field is not displayed in the current list.
The user can interactively choose the field for output from the field list.
The user can display the contents of these fields at line level using the 'Detail' function.
See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
tech (technical field)
value set: SPACE, 'X' 'X' = technical field
Field cannot be output in the list and cannot be displayed interactively.
Field can only be used in the field catalog (not in IT_SORT, ...).
emphasize (highlight columns in color)
value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
C: Color (coding must begin with C)
x: color number
y: bold
z: inverse
hotspot (column as hotspot)
value set: SPACE, 'X'
'X' = column cells are output as hotspots
fix_column (fix column)
value set: SPACE, 'X'
Not relevant for block lists (output of several lists consecutively)
'X' = column fixed (does not scroll horizontally)
All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
do_sum (sum over column)
value set: SPACE, 'X' 'X' = a sum is to be calculated over this internal output table field.
This function can also be called by the user interactively.
no_sum (sums forbidden)
value set: SPACE, 'X' 'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
input (column ready for input)
Function not available
Format column contents
icon
value set: SPACE, 'X' 'X' = column contents to be output as an icon.
The caller must consider the printability of icons.
symbol
value set: SPACE, 'X' 'X' = column contents are to be output as a symbol.
The internal output table column must be a valid symbol character.
The caller must consider the printability of symbols.
Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
just (justification)
value set: SPACE, 'R', 'L', 'C'
Only relevant for fields of data type CHAR or NUMC
' ' = default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output
The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
lzero (leading zeros)
value set: SPACE, 'X'
Only relevant for fields of data type NUMC
ALV outputs NUMC fields right-justified without leading zeros by default.
'X' = output with leading zeros
Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
no_sign (no +/- sign) Only relevant for value fields
value set: SPACE, 'X' 'X' = value output without +/ sign
no_zero (suppress zeros) Only relevant for value fields
value set: SPACE, 'X' 'X' = suppress zeros
edit_mask (field formatting)
value set: SPACE, template
template = see documentation of WRITE formatting option USING EDIT MASK template
The output conversion conv can be made by template = '== conv'.
Texts
The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
The 'long field label' is also used in display variant definition, sort, etc. popups.
seltext_l (long field label)
seltext_m (medium field label)
seltext_s (short field label)
reptext_ddic (header)
analogous to the Data element maintenance 'Header'
The specified text is not necessarily output in the list, an optimum among all texts is sought.
ddictxt (specify text)
value set: SPACE, 'L', 'M', 'S'
You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Parameters for program fields without Data Dictionary reference
see also 'Text' parameters
datatype (data type)
value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
Only relevant for fields without Data Dictionary reference
Program field data type
ddic_outputlen (external output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
FIELDCAT-INTLEN = n
see also the documentation of the parameter FIELDCAT-INTLEN
n = external format field output length
The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
intlen (internal output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
FIELDCAT-DDIC_OUTPUTLEN = n
see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
n = internal format field output length
rollname (data element)
value set: SPACE, Data Dictionary data element name
F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
When F1 help is called for this field, the documentation of the specified data element is displayed.
If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
Others
sp_group (field group key)
value set: SPACE, CHAR(1)
Field group key.
Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
reprep (Report/Report interface selection criterion)
value set: SPACE, 'X'
Prerequisites:
The system contains the Report/Report interface (function group RSTI, table TRSTI)
Parameter LAYOUT-REPREP = 'X'
(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
2.7.2. Default
The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
fieldname
ref_tabname
Notes:
ALV gets the remaining information from the Data Dictionary.
If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
Priority rule:
Entries in the field catalog have priority over differing entries in the Data Dictionary.
The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
fieldname
outputlen
datatype
seltext_s
seltext_m
seltext_l
Notes:
F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
The Important Parameters are :
I. Export :
i. I_program_name : report id
ii. I_internal_tabname : the internal output table
iii. I_inclname : include or the report name where all the dynamic forms are handled.
II Changing
ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is
declared in the type pool SLIS.
Reward points if useful
Regards
Anji
Vijayendra Rao
Posts: 1,699
Questions: 28
Registered: 9/14/04
Forum points: 3,018
Re: ALV
Posted: May 14, 2007 8:29 PM    in response to: kotireddy       Reply
Hi,
Field catalog defines the attributes and specifies the technical details of the columns displayed in an ALV output.
You can check the following thread to see how to build a field catalog and how to work with ALV.
Message was edited by:
        Karthikeyan Pandurangan

Document number ranges in entry view and in General Ledger view

What is the difference between Document number ranges in entry view and in General Ledger view ?
We have new GL activated in our system , and found that the GL Document types ( SA) are assigned to document number ranges in entry view . What is the need to define document number ranges in General Ledger view ?

Hi,
Document Number Range in entry view is the document numbers which are posting in your leading ledger. You cant achieve the same document number range to the general ledger view. A General ledger view can have both Leading ledger view and non leading ledger view therefore document number range should not be kept same for both ledgers as your running document number gets skipped.
That to some times you can only post documents to only Non Leading ledgers. Therefore a separate number ranges needs to be created for general ledger view
Hope u understood.
regards
srikanth
Edited by: boddupalli srikanth on May 21, 2009 9:28 PM

In search of a 'special' number range of validator

Hi,
I am developing a JSF based web page with a text field that can hold numbers.
I want to add number range to this text field so that user does not enter more than a allowed range of numbers.
I am aware of multiple options JSF and its various flavors provide and below is the option I am considering -
Add a validator which will be called upon typing the numbers and the validators returns with an error message shown on the UI.
However, I was wondering if there was any validation any of the JSF flavors provide that can validate number range on typing and automatically truncate the number to the range provided.
As an example, if the range is 0.0 to 99.00, as soon as the user types 100, the validation truncates the value to 10 by removing the leading 0. A error message would be even great but not mandatory. Similarly,upon typing 99.999, the leading 9 would be truncated making the value 99.99.
The reason I am looking for such a feature is because I have a editable datatable with the date split into multiple pages with a richfaces scroller in between.
I am using a doublerangevalidator facelet which does validation and shows error message alright. But I want the error message to persist even after going to the next page in the scroller, which is not happening right now.
The idea is to have the user see all text fields that violate the number range as a comprehensive list of errors on the page.
Since I am not able to achieve this using any of the validators provided by JSF RI or Richfaces, I am looking to atleast prevent the user from typing invalid data.
Thanks for the help.

anand_sridhar wrote:
As an example, if the range is 0.0 to 99.00, as soon as the user types 100, the validation truncates the value to 10 by removing the leading 0. A error message would be even great but not mandatory. Similarly,upon typing 99.999, the leading 9 would be truncated making the value 99.99. Sounds like you need a converter instead of a validator. A validator is meant to validate the data, not to change the data.
Have you looked in the converters corner anyway? Implementing one yourself isn't that hard.

Vendor Master Record number ranges

Hi,
We have one requirement . At present my client is maintaining the vendor master record number ranges with 4 digits. Ex. 0001 to 9999
His present requirement is that to maintain the number ranges with 4 digits .ex. 00001 to 99999. They want this should apply even to existing records. Ex: Old number 2345 , they want the present number should be 02345.
Request you to please help in resolving the issue. Thanks in advance for the help. Matter is urgent
Thanks
D.K.Lakshmi narayana

Hello Lakshmi,
It seems to me these are your alternatives.
1) For each old vendor in the 4-digit scheme, create a new vendor master record in the 5-digit scheme with the leading zero. Then, transfer all open documents/master records (invoices, purchase orders, info records, etc.) from the old vendor to the new vendor. Then, block the old vendor.
2) Same as previous except instead of changing all open documents, only change the master data (e.g., info records or long term contracts or agreements) to the new vendor master record and continue to use the old vendor master record until the open documents are closed. Then, block the old vendor master record.
I think option 2 will be the "safer" choice. Plus, for reporting, you will probably need to continue using both vendor numbers for a while.
Maybe someone else has an easier way...
Cheers,
Larry

Leading Space in Number Range

Similar Messages

Maybe you are looking for