Field length issue

Hello,
i have WAD report and a chart in it.In this chart we have dates being displayed on the X axis.i date format is 01/01/2008.
Our requirement is to have the date being displayed as
01-jan-2008.
For that i have written a customer exit variable .we have used a funfction module which passes the input as date and converts it in the required format.
FM input:01012008
FM output:01-jan-2008
i concatenated it to format 01jan2008.
But now whn i run the report it gives me the message that the length of field (ZVDAPRD-my variable name) is short
ZVDAPRD(customer exit) is made on the info obj Z_period which is of 8 length(date type). info object output length 10. reference characteristic 0date.
just to try i did format 01jan2008 to 01jan08,but still it gave me some wrong value like '1ja08" is invalid.
please help me to solve this!
also let me know if any other method to achive this.
thanks,
Pallavi

Hi Pallavi,
try to use text variables.
Processing by: Replacement Path
Replace Variable With: Name (Text)
regards Sven

Similar Messages

Custom infotype - field length issue

Hi experts,
We have a requirement of keeping so much free text fields in the custom infotype. However, the system doesnu2019t allow having these many fields in the PS structure. We got the information from the error description as- The maximum length of PS structures for infotypes is 1000; this is the length of the general infotype header in bytes. Could you please suggest some way to solve this issue?
Thanks,
Rahul

Give a field and try to enter some decription for large text in that field .
Create a table for that field and give F4 for that .
Maintain the text in SO10 and call that text using read_text fn module .
Try this way

Field Length issue in ALV Report

Hi,
I am using FM REUSE_ALV_GRID_DISPLAY to display few fields. Among them I have a field with length 200 characters text.
During ALV report display I am able to see only 128 characters, But when I download it and see the field, the it is showing complete text.
Can anybody help me out?
Thanks,
Ramakrishna

Check out the last answer of this post.
Re: ALV Grid Display - 255 characters
<i>I found a SAP document called "Using ALV for list display.pdf" that says the following:
"Size of data fields: While the list-based ALVList can display only tables of up to 90 columns, the control-based ALVGrid and ALVFullscreen have the limitation of 128 characters per data cell."</i>
Please make sure to award point for helpful answers and mark the post as solved. Thanks.
Regards,
Rich HEilman

Output field length issue in OO ALV

Hello Experts,
I have an requirement to download ALV grid output into Excel but some of columns having more than 128 characters, as per standard SAP will not support so I have included one more button and I have written the below code.
field-symbols: <fs_table> type standard table,
                 <fs_wa>.
* Get the current fields of the layout
CALL METHOD ALV_GRID->GET_FRONTEND_FIELDCATALOG
    IMPORTING
      ET_FIELDCATALOG = it_fcat.
* Generate dynamic internal table
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
    EXPORTING
      IT_FIELDCATALOG           = it_fcatn
    IMPORTING
      EP_TABLE                  = dyn_table
assign dyn_table->* to <fs_table>.
create data dyn_line like line of <fs_table>.
assign dyn_line->* to <fs_wa>.
loop at lt_final into ls_final.
    if ls_final-EBELP is not INITIAL.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
        EXPORTING
          INPUT = ls_final-EBELP
        IMPORTING
          OUTPUT = ls_final-EBELP.
    endif.
    MOVE-CORRESPONDING ls_final to <fs_wa>.
    append <fs_wa> to <fs_table>.
endloop.
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME                = FULLPATH
      FILETYPE                = 'DAT'
      WRITE_FIELD_SEPARATOR   = 'X'
      CONFIRM_OVERWRITE       = 'X'
    TABLES
      DATA_TAB                = <fs_table>
      FIELDNAMES              = LT_HEADING
Now my problem is some of field output value getting truncated(in excel) but it displayed in Grid output.
eg.
lt_final having one text field(Doc. Type description) and the length is 20, actually printing 17 characters but we are not defining the output length.
Can you please anyone faced the problem earlier? Basically the SAP version is R/3 4.7.
Regards,
Vadamalai A

Hello All,
Before calling CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
we can define the length
WHEN 'BATXT'.       wa_fcatn-OUTPUTLEN =
20.
Regards,
Vadamalai A.
We can close this thread.

Sql*loader field length issue

so I'm loading a file and it's rejected a record where "field in data file exceeds maximum length" the record it's failing on has data length of 625 characters. I'm loading it into a table with a field type of varchar2(1024).
for the life of me, I can't figure out why it's failing. I've even gone and manually copy and pasted the rogue record into the table (via Toad) and it works fine, but I need it to load via SQL*loader.
there is no white space that i'm not counting. Can anyone suggest where to look next?

Hi,
Just change the problematic field in the control file as
load
field char(1000),
If you give the length in the control file, ur problem ll be solved.
- karthik

TCURR field TCURR_UKURS - field length is too short

Has ECC6 addressed the field length issue of 9 characters (5 decimals) in table TCURR field UKURS to cater for weak currencies, to avoid using ratios of 1000:1

Hi,
I don't see any issue. UKURS field has 9 characters, that's right; but, as you rightly mentioned, it should not pose any problem considering the ratio. Why ratio of 1000:1 is posing a problem for you?
Regards,
Eli

Field length change in Web Dynpro Components iView

Hi,
We are using SAP MDM Web Dynpro Components - Configuration Manager (NW7.3) to develop the UI. One of the issue while disply field is, Though field maintained in MDM has only 2 charaters UI that displays a full-screen-width field.
I would like to display actual field length maintained in reposiroy for each field. Is it possible??
Cheers,
Rc

This is closed.
By mistake Raised Twice....I guess I need break

Field alignment issue on a page

Hi -
I am trying to align the fields on an apex page but not able to find a way.
Basically I have 2 rows of columns shown on an apex page.
First row has 4 fields (Text box items):
And second row has 2 fields (Text box items)
1st row > Name|---------------------------| Address|-----------| Ph1|-------------------| Ph2|-------------------|
2nd row> Indicator|----| Active|------|
So I want the second row fields to be under the first row's first field. I am trying to do that using START_TBL and STOP_TBL but the second field (Active field) from the 2nd row is always showing after the end of the 1st row's first field's (Name field) length on the 2nd row.
Desired:
1st row > Name*|---------------------------|* Address*|-----------|* Ph1*|-------------------|* Ph2*|-------------------|*
2nd row> Indicator*|---|* Active*|----|*
But getting:
1st row > Name*|---------------------------|* Address*|-----------|* Ph1*|-------------------|* Ph2*|-------------------|*
2nd row> Indicator*|---|* Active*|----|*
Please share your expertise.
Thanks.

Thanks so much osgood... a really strange one as those parts of the page are locked out (i.e. controlled by the template only), so to resolve the issue I've created a new page altogether, copied and pasted the index code in, and resaved as the index.html file. It's now working again as desired. Thanks again!

Control an Integer field Length without using Validation ??

Hi,
I have Couple of fields where I need to configure them as Integers.
Now each one has a fixed length that i need to limit to.
But when i create a field of type: integer, i cannot select teh length!!!
To achive this the idea i have is to write a validation which checks length..
But can i achive it without going for a validation on each field???
PS: I am aware that TEXT field can limit the length But it also allows me to enter text values, my requirement clearly says that to allow users to only enter Numeric values..
Did anyone face a similar Case?
Kind Regards
Eva

Hi Eva,
I didn't try in the system, but I feel there are two solutions to achieve your requirement (*of course in both cases you will need to write a simple validation)
Solution 1 : When field is defined as "Integer" in Console.
lets take an example, you want to restrict an integer field with a limit of max 4 characters.
Maximum value of a 4 character integer can be "9999". So, you can put a simple validation to compare the field value with 9999. if the value is less then this means fields values is less than 4 characters, else more than 5 characters.
In this case Your validation expression in expression editor will be:
FIELD NAME<= "9999"
Solution 2 : When field is defined as "Text" in Console.
In this case you can restrict the maximum field length through Console. But you will also need to write a validation to ensure that user is not entering any alphabets or special characters in this field.
In this Case you can use below validation:
HAS_ALL_CHARS(FIELD NAME, "0","9")
This will ensure that field has all characters between 0 and 9 and doesn't hold any special character or alphabets.
In Both cases you will need to set "Automatic Execution" property as "Error". Also please do not manually type any function or value in expression editor. use drop down for fields, operators, functions etc. and enter numeric values using the first blank box before dimension list.
Kindly revert if you face any issues.
-Shiv

ANSI X12 EDI 850 V4010 - REF Field length Increase

Hi,
The standarad EDI V4010 definiation contains Segment:REF, Field:127, MaxLength:30 (ISA.GS.ST.REF:127), partner sending a EDI data with more than 30 characters for this field. As per their EDI guide lines the MaxLength allows upto 50 chars for this field.
Have changed the field length from 30 to 50 chars in ANSI X12 850 V4010 message structure and re-generated EDI To XML mapping.When test the mapping in BIC tool, the EDI file is getting converted to EDI XML when the field value is more than 30 chars i.e upto 50 chars. Also Tested by giving more than 50 chars value for this field and it's failed to convert in BIC mapping tool saying 'The length of the field value is too big'.
As the change working in BIC tool, generated sda file and deployed on PI QA system. While test the change after .sda file deployment the change of Field Length is not reflecting and it's only allowing upto 30 chars only., and more than 30 chars data for this field EDI files are failing.
As the change working alone in BIC tool fine and not reflecting thefield length after sds file deployment. Any ideas about this issue and how to handle this requirement.
Thanks
Veera

Hi John,
If you see the documentation what you have given :
Parameters:
on: delimiters at the end do not appear
off: delimiters at the end appear
it clearly says the parameter is used for the delimiters, but not for truncating length of the fields in Seeburger.
I'm not sure if you've ever used the BIC Mapping tool and what I'm really looking for is someone with experience in this area to give a solution that works for this question:
By the way I have used the seeburger and this requirement we have done within XI because we have done all the rules within XI not in seeburger. But I will give a try with this requirement and will try to update you. Until unless I work with any of the issue I will not suggest. Even If I didnt I will try and then will suggest. Dont get me wrong.
Cheers,
John.

Incoming Email Subject Field length increase

Hi,
In CRM 7.0,I need to increase the incoming email Subject Field length ,When i try to modify UI configuration,Subject fields are not enabled for configuration (Other fields in the same screen are enabled for modifications)..
Please give your inputs whether incoming email Subject Field length can be increased? if so,this should be done at UI level or mail form?
Regards
Shan

Hi Prasenjit,
Thanks for your interaction and response.
Actually I can to find out views and class details in CRM 7.0 by using F2 key..
The UI component is CRMCMP_CCS_EML and view is CRMCMP_CCS_EML/MailBody. The implementation class is ZL_CRMCMP_C_MAILBODY_IMPL. Since all the page attributes are string, There is a context class ZCL_CRMCMP_C_MAILBODY_CTXT, But no context node (Like you mentioned type CN as in *CN00, *CN01) within page attribute.
The main issue am facing here is that couldnu2019t figure out where to start the debugging for inbound mails where the subject field is truncated. I usually process inbound mails from SOIN transaction.
Moreover subject field can have more than 40 characters in outgoing mail, but the inbound mail subject field limited to 40 character and rest of them truncated.
Hope you understand my area of concern and provide me your input.
Regards,
Shan

How to restrict field length upon Export - OFR

Hi,
I am working with the standard AP solution. We are experiencing an issue with the Invoice Number and PO Number exporting lengths that are longer than we have allowed in IPM. Therefore, we are having multiple documents fail with input agent in IPM because the number of characters are over the limit in the .txt file for those fields.
Thanks,
Natalie

Have your tried to adjust the application fields' lengths?
(see http://docs.oracle.com/cd/E23943_01/admin.1111/e12782/c04_applications.htm#CIHCJFEF )
Note that if you exceed the type's limits (like mentioned 'Possible string length is specified in the Length element with a maximum of 200 characters supported.') you might have to go with a workaround, but for fields like Invoice Number it can be a challenge (this field is probably heavily used in searching).

CAT2 Time sheet additional field length

Hi All
I have added additional fields in include CI_CATSDB in that fields one fields is reference field in that I have taken field length 60 Char but in the input it is taking length only 35 Char.
So if any one has come across this issue please help me because I have to enter reference that have more length.
Thanks and regards
Balbir

hi
in the catsdb table it will accept the length as 60 , but in the screen fld in the structure , it does not allow more than 35 chars, it is a limitation.
Regards
Sameer

Changing field length of a standard field in standard table VBEP

Hi,
Please advice the possibility and the possible repercussions of changing field lengths in a standard table. Table in concern is VBEP.
Thanks & Rgds,
Pradeep

No you cannot change the field length
thanks
G. Lakshmipathi

Type conflict when calling a function module (field length)

Dear All,
            I am getting this following error while executing: Type conflict when calling a function module (field length)
This is piece of coding i have writern in my action button.
method SEARCH_MATERIAL .
data:
        node_mat_input TYPE REF TO if_wd_context_node,
        node_mat_output TYPE REF TO if_wd_context_node,
        material TYPE BAPIMATDET-MATERIAL,
        itab TYPE TABLE OF BAPIMATDOA.
node_mat_input = wd_context->get_child_node( 'NODE_MAT_INPUT' ).
node_mat_output = wd_context->get_child_node( 'NODE_MAT_OUTPUT' ).
node_mat_input->get_attribute( EXPORTING name = 'MATERIAL'
                                 IMPORTING value = material ).
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material                    = material
    PLANT                       = plant
    VALUATIONAREA               =
    VALUATIONTYPE               =
    MATERIAL_EVG                =
   IMPORTING
     MATERIAL_GENERAL_DATA       = itab
    RETURN                      =
    MATERIALPLANTDATA           =
    MATERIALVALUATIONDATA       =
node_mat_output->bind_table( itab ).
endmethod.
Attributes are:
Node name = INPUT its structure is BAPIMATDET
INPUT attributes = MATERIAL of type BAPIMATDET-MATERIAL
Thanks,
Gopi.

Hi Amit,
           I have used service call to fetch records from that bapi..
The following is the code generated by service call:-
METHOD execute_bapi_material_get_deta .
declarations for context navigation
DATA:
    node_bapi_material_get_de   TYPE REF TO if_wd_context_node,
     node_exporting   TYPE REF TO if_wd_context_node,
     node_material_general_dat   TYPE REF TO if_wd_context_node,
     node_importing   TYPE REF TO if_wd_context_node,
      lri_element    TYPE REF TO if_wd_context_element.
declarations for fuba parameters
data:
    stru_c_material_general_dat    TYPE if_componentcontroller=>element_material_general_dat.
DATA:
    attr_material    TYPE bapimatdet-material,
    attr_plant    TYPE bapimatall-plant.
get all involved child nodes
node_bapi_material_get_de = wd_context->get_child_node( `BAPI_MATERIAL_GET_DE` ).
node_exporting = node_bapi_material_get_de->get_child_node( `EXPORTING` ).
node_material_general_dat = node_exporting->get_child_node( `MATERIAL_GENERAL_DAT` ).
node_importing = node_bapi_material_get_de->get_child_node( `IMPORTING` ).
get input from context
node_importing->get_attribute(    EXPORTING      name = `MATERIAL`
                                                     IMPORTING      value = attr_material ).
node_importing->get_attribute( EXPORTING       name = `PLANT`
                                                          IMPORTING       value = attr_plant ).
the invocation - errors are always fatal !!!
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material =                        attr_material
      plant =                           attr_plant
"      valuationarea =                   wd_This->Valuationarea
"      valuationtype =                   wd_This->Valuationtype
"      material_Evg =                    wd_This->Material_Evg
    IMPORTING
      material_general_data =           stru_c_material_general_dat
"      return =                          wd_This->Return
"      materialplantdata =               wd_This->Materialplantdata
"      materialvaluationdata =           wd_This->Materialvaluationdat
node_material_general_dat->bind_structure( stru_c_material_general_dat[] ).
ENDMETHOD.
                             but the problem is I am getting the following error while compiling...
" stru_c_materialplantdata " is not an internal table - the " OCCOURS n" specification is missing.
Thanks,
Gopi.
Edited by: Yegalaivan on Nov 18, 2009 8:30 AM

Field length issue

Similar Messages

Maybe you are looking for