Does length of CBO table's field is shorter than structure field?

HI
length of CBO tables's field name is 16 and structure field name 30.
how this happen?
I was trying to make CBO table include some structure.
and that says field name is too long.
is this not possible all structucture can include CBO table?
or should I change table properties like tech. settings?
does anyone can solve this problem?
thanks.
Regards.
Kim

Hi!
Unfortunately there is no way to enter more than 16 chars long names into tables. Nor with an included a structure.
As the sap help sais:
"There are some restrictions for certain objects. These objects are included in the following list together with the maximum length allowed:
Transparent tables and their fields: 16"
Correct the names within your structure (use less than 16 characters for the field names).
Best regards
Tamá

Similar Messages

Table name and field name of the structure field

Hi Gurus
I am having a screen where i enter a value in a field and that field is a structure field, I would like to know in which table and what field is this value storing?
Can anyone help me out in finding the field name? and what is the procedure to find?
Thanks in advance

Hi Satya,
In the field data section (technical information), you can double click on the field name then the system will take you to SE11 (Data Dictionary). From here, you can check whether the field is available in tranparent table or structure.
In general, as naren mentioned sales order header data stored in table VBAK and line item in table VBAP, VBEP, etc.
For request delivery date, it stores in table VBAK-VDATU.
Regards,
Ferry Lianto
Please close this thread if your problem solved and mark for all helpful answer.

Summarization of field on more than one field

Hi All,
I have a internal table in which I have 6 field and I have to summarize the 6th field on basis of first five field.
can I summarize one field in internal table on more than one field.
Please help me out.
Regards,
Sandeep

Hi sandeep,
1. u want to summarize (total)
the sixth field,
on the basis of different combinations of first 5 fields.
2. simple
3. Create another table,
 with the same structure, say STAB.
4. just use this logic.
5. LOOP AT ITAB.
 CLEAR STAB.
 MOVE-CORRESPONDING ITAB TO STAB.
 COLLECT STAB.
ENDLOOP.
regards,
amit m.

Alias tables do not show more than 9 fields of the same type in a Command

Hi there, In Crystal Reports I have a Command to query a database, this works fine and returns what I need,
but in when you add more than 9 alias's and and then Select more thatn 9 fields of the same type it does not show any more them in the Field Exporler window.
i.e. I want to add another alias and select casdet_text(10) but it does not show any more than 9.
Any help woud be apprecitated.
Thanks
casdet_text(1)
casdet_text(2)
casdet_text(3)
casdet_text(4)
casdet_text(5)
casdet_text(6)
casdet_text(7)
casdet_text(8)
casdet_text(8)
casdet_text(9)

Hi James,
It's likely an internal limitation. If you are going to alias all of your fields it's more efficient to use a View or Stored Procedure to handle the renaming server side rather than client side.
It may even be a connection limit, try using another tool and see if you can add more than 9 aliases.
Thank you
Don

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
 form like zscr_data_hdr-form,
 werks like zscr_data_hdr-werks,
 matnr like zscr_data_hdr-matnr,
 verid like zscr_data_hdr-verid,
 lot like zscr_data_hdr-lot,
 lot_qty like zscr_data_hdr-lot_qty,
 udate like zscr_data_hdr-udate,
 utime like zscr_data_hdr-utime,
 zuser like zscr_data_hdr-zuser,
 processed like zscr_data_hdr-processed,
 defect like zscr_defect_data-defect,
 vornr like zscr_route_data-vornr,
 fld1 like zscr_defect_data-defect_val,
 fld2 like zscr_defect_data-defect_val,
 fld3 like zscr_defect_data-defect_val,
 fld4 like zscr_defect_data-defect_val,
 fld5 like zscr_defect_data-defect_val,
 fld6 like zscr_defect_data-defect_val,
 fld7 like zscr_defect_data-defect_val,
 fld8 like zscr_defect_data-defect_val,
 fld9 like zscr_defect_data-defect_val,
 fld10 like zscr_defect_data-defect_val,
 fld11 like zscr_defect_data-defect_val,
 fld12 like zscr_defect_data-defect_val,
 fld13 like zscr_defect_data-defect_val,
 fld14 like zscr_defect_data-defect_val,
 fld15 like zscr_defect_data-defect_val,
 fld16 like zscr_defect_data-defect_val,
 fld17 like zscr_defect_data-defect_val,
 fld18 like zscr_defect_data-defect_val,
 fld19 like zscr_defect_data-defect_val,
 fld20 like zscr_defect_data-defect_val,
 fld21 like zscr_defect_data-defect_val,
 fld22 like zscr_defect_data-defect_val,
 fld23 like zscr_defect_data-defect_val,
 fld24 like zscr_defect_data-defect_val,
 fld25 like zscr_defect_data-defect_val,
 fld26 like zscr_defect_data-defect_val,
 fld27 like zscr_defect_data-defect_val,
 fld28 like zscr_defect_data-defect_val,
 fld29 like zscr_defect_data-defect_val,
 fld30 like zscr_defect_data-defect_val,
 fld31 like zscr_defect_data-defect_val,
 fld32 like zscr_defect_data-defect_val,
 fld33 like zscr_defect_data-defect_val,
 fld34 like zscr_defect_data-defect_val,
 fld35 like zscr_defect_data-defect_val,
 fld36 like zscr_defect_data-defect_val,
 fld37 like zscr_defect_data-defect_val,
 fld38 like zscr_defect_data-defect_val,
 fld39 like zscr_defect_data-defect_val,
 fld40 like zscr_defect_data-defect_val,
 fld41 like zscr_defect_data-defect_val,
 fld42 like zscr_defect_data-defect_val,
 fld43 like zscr_defect_data-defect_val,
 fld44 like zscr_defect_data-defect_val,
 fld45 like zscr_defect_data-defect_val,
 fld46 like zscr_defect_data-defect_val,
 fld47 like zscr_defect_data-defect_val,
 fld48 like zscr_defect_data-defect_val,
 fld49 like zscr_defect_data-defect_val,
 fld50 like zscr_defect_data-defect_val,
 fld51 like zscr_defect_data-defect_val,
 fld52 like zscr_defect_data-defect_val,
 fld53 like zscr_defect_data-defect_val,
 fld54 like zscr_defect_data-defect_val,
 fld55 like zscr_defect_data-defect_val,
 fld56 like zscr_defect_data-defect_val,
 fld57 like zscr_defect_data-defect_val,
 fld58 like zscr_defect_data-defect_val,
 fld59 like zscr_defect_data-defect_val,
 fld60 like zscr_defect_data-defect_val,
 fld61 like zscr_defect_data-defect_val,
 fld62 like zscr_defect_data-defect_val,
 fld63 like zscr_defect_data-defect_val,
 fld64 like zscr_defect_data-defect_val,
 fld65 like zscr_defect_data-defect_val,
 fld66 like zscr_defect_data-defect_val,
 fld67 like zscr_defect_data-defect_val,
 fld68 like zscr_defect_data-defect_val,
 fld69 like zscr_defect_data-defect_val,
 fld70 like zscr_defect_data-defect_val,
 fld71 like zscr_defect_data-defect_val,
 fld72 like zscr_defect_data-defect_val,
 fld73 like zscr_defect_data-defect_val,
 fld74 like zscr_defect_data-defect_val,
 fld75 like zscr_defect_data-defect_val,
 fld76 like zscr_defect_data-defect_val,
 fld77 like zscr_defect_data-defect_val,
 fld78 like zscr_defect_data-defect_val,
 fld79 like zscr_defect_data-defect_val,
 fld80 like zscr_defect_data-defect_val,
 fld81 like zscr_defect_data-defect_val,
 fld82 like zscr_defect_data-defect_val,
 fld83 like zscr_defect_data-defect_val,
 fld84 like zscr_defect_data-defect_val,
 fld85 like zscr_defect_data-defect_val,
 fld86 like zscr_defect_data-defect_val,
 fld87 like zscr_defect_data-defect_val,
 fld88 like zscr_defect_data-defect_val,
 fld89 like zscr_defect_data-defect_val,
 fld90 like zscr_defect_data-defect_val,
 fld91 like zscr_defect_data-defect_val,
 fld92 like zscr_defect_data-defect_val,
 fld93 like zscr_defect_data-defect_val,
 fld94 like zscr_defect_data-defect_val,
 fld95 like zscr_defect_data-defect_val,
 fld96 like zscr_defect_data-defect_val,
 fld97 like zscr_defect_data-defect_val,
 fld98 like zscr_defect_data-defect_val,
 fld99 like zscr_defect_data-defect_val,
 fld100 like zscr_defect_data-defect_val,
 fld101 like zscr_defect_data-defect_val,
 fld102 like zscr_defect_data-defect_val,
 fld103 like zscr_defect_data-defect_val,
 fld104 like zscr_defect_data-defect_val,
 fld105 like zscr_defect_data-defect_val,
 fld106 like zscr_defect_data-defect_val,
 fld107 like zscr_defect_data-defect_val,
 fld108 like zscr_defect_data-defect_val,
 fld109 like zscr_defect_data-defect_val,
 fld110 like zscr_defect_data-defect_val,
 fld111 like zscr_defect_data-defect_val,
 fld112 like zscr_defect_data-defect_val,
 fld113 like zscr_defect_data-defect_val,
 fld114 like zscr_defect_data-defect_val,
 fld115 like zscr_defect_data-defect_val,
 fld116 like zscr_defect_data-defect_val,
 fld117 like zscr_defect_data-defect_val,
 fld118 like zscr_defect_data-defect_val,
 fld119 like zscr_defect_data-defect_val,
 fld120 like zscr_defect_data-defect_val,
 fld121 like zscr_defect_data-defect_val,
 fld122 like zscr_defect_data-defect_val,
 fld123 like zscr_defect_data-defect_val,
 fld124 like zscr_defect_data-defect_val,
 fld125 like zscr_defect_data-defect_val,
 fld126 like zscr_defect_data-defect_val,
 fld127 like zscr_defect_data-defect_val,
 fld128 like zscr_defect_data-defect_val,
 fld129 like zscr_defect_data-defect_val,
 fld130 like zscr_defect_data-defect_val,
 fld131 like zscr_defect_data-defect_val,
 fld132 like zscr_defect_data-defect_val,
 fld133 like zscr_defect_data-defect_val,
 fld134 like zscr_defect_data-defect_val,
 fld135 like zscr_defect_data-defect_val,
 dayst like zscr_data_hdr-dayst,
 end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

Maximum length of the table

Hi,
I created one table, in that table i have 101 field, total length of the table is 430, but i could not able to create 102nd field because it's saying total length of the table is exceed. How i can increase table length?

The total length of the fields is limited to 1962 in case of Transparent tables.
Please check if one of the following constraints is causing the problem
Constraints
All the key fields of a table must be stored together at the beginning of the table. A non-key field may not occur between two key fields.
A maximum of 16 key fields per table is permitted. The maximum length of the table key is 255.
If the key length is greater than 120, there are restrictions when transporting table entries. The key can only be specified up to a maximum of 120 places in a transport. If the key is larger than 120, table entries must be transported generically.
A table may not have more than 249 fields. The sum of all field lengths is limited to 1962 (whereby fields with data type LRAW and LCHR are not counted).
Fields of types LRAW or LCHR must be at the end of the table. Only one such field is allowed per table. There must also be a field of type INT2 directly in front of such a field. The actual length of the field can be entered there by the database interface.

LSMW - Problem while assigning the quantity field to the target structure

Hi,
Here I am getting the warning while I am maintaing the field mapping and conversion rules . Here I am doing this through the Batch input Recording.
That is , while I am assigning the source field to the target structre field .
" WARNING : Source field is longer than target field "
plz help me to remove that warning.
Thank you

in lsmw use char field instead quantity of same length(in stucture defined in lsmw).

How to display the table components that make up a structure?

Hi,
How does one display the table components that make up a structure?
I want to see the table fields that make up the structure EKBEZ.
Thx.
Andy

Hi
GOTO SE11 , type the structure name in DataType optional feild , you will get the feilds that make the structure
Kindly rewards the points accordignly
Regards,
Pranshu

Field length in internal table

hi,
how to selt field length in internal table?.
i have created on report the report out puts down load to using download function .
the out format is:
op1 op2   op3      op4
1     3       4
i want
op1   op2   op3       op4
1                3          4
how to set this please give sample code.

HI,
Give internal table like this.
DATA: BEGIN OF itab OCCURS 100,
            op1(04),
            op2(04),
op3(04),
op4(04),
      END OF itab.
So it will allocate space between 1, 3 and 4.
Reward if it useful.
Thanks.

Error in formula field: Column 'TASK_BCWP' does not belong to table Task

Hi,
We have a formula field to calculate the a cost KPI and that field throws an error in the ULS logs. The error is: PWA:PWA, ServiceApp:Project Server Service Application, User:GDFN\IPL_Content, PSI: SSP: Formula Evaluation Failed! - trying to continue - (System.ArgumentException:
Column 'TASK_BCWP' does not belong to table Task.
We are running EPM 2010. Recreating of the custom field did not work. We are not running with the latest CU yet.
The formula that we use is:
IIf([BCWP] > 0; [ACWP] / [BCWP]; 1)
The stack trace from the ULS log is:
PWA:http://gdfn-ipl-14/PWA, ServiceApp:Project Server Service Application, User:GDFN\IPL_Content, PSI: SSP: Formula Evaluation Failed! - trying to continue - (System.ArgumentException: Column 'TASK_BCWP' does not belong to table Task.
at System.Data.DataRow.GetDataColumn(String columnName)
at System.Data.DataRow.get_Item(String columnName)
at Microsoft.Office.Project.Server.BusinessLayer.FormulaDataProvider.HaveColumn(DataRow row, String columnName)
at Microsoft.Office.Project.Server.BusinessLayer.FormulaDataProvider.GetTaskData(Guid nodeId, Int32 fieldId)
at Microsoft.Office.Project.Server.BusinessLayer.FormulaDataProvider.GetDataInternal(Int32 entityId, Guid nodeId, Int32 fieldId, Boolean canChangeEntity)
at Microsoft.Office.Project.Server.BusinessLayer.FormulaDataProvider.GetData(Int32 entityId, Guid nodeId, Int32 fieldId)
at Microsoft.Office.Project.Server.BusinessLayer.Formula.FieldExpression.Evaluate(IFieldEvaluator context, Guid nodeId)
at Microsoft.Office.Project.Server.BusinessLayer.Formula.GreaterExpression.Evaluate(IFieldEvaluator context, Guid nodeId)
at Microsoft.Office.Project.Server.BusinessLayer.Formula.ConditionalExpression.Evaluate(IFieldEvaluator context, Guid nodeId)
at Microsoft.Office.Project.Server.BusinessLayer.Formula.FormulaEvaluator.Evaluate(PlatformContext context, Expression formula, Int32 entityId, Int32 fieldId, Guid nodeId, Dictionary`2 entityFormulaFields)) + -- FieldId = 188776525 -- NodeId = 1b1149c1-52c2-4f7f-ba60-6d65effdb6b3
-- Formula = IIf(Greater([MSPJ188743691], 0), Divide([MSPJ188743800], [MSPJ188743691]), 1)
I have no clue where to start looking for the cause of this error. Any help would be appreciated.
Thanks,
Quint Mouthaan

Hi Quint,
This can because of database fragmentation. I would recommend you to re-index the databases and perform a de-fragmentation and can check the behavior.
On the other hand when you receive this message, you can try an IISRESET and check. Additionally you can use refer to following link for de-fragmenting queries.
http://support.microsoft.com/kb/943345
Happy troubleshooting.
Vikram Daruru - MSFT

Maximum record length in internal table?

Is there a maximum record length in an internal table? Please note: My question is NOT related to table space. I'm referring only to the length of an individual record (A.K.A. row length).
I am using a work area to insert data into an internal table. Both the work area and internal table are defined by the same structure.
The structure has a total length of 672 bytes. For the sake of this discussion I'll point out that at the end of the structure, bytes 669, 670, 671, and 672 are four separate fields of 1 character each.
When viewing the work area record in the debugger I'm seeing all the fields and all the values. When viewing the internal table in the debugger after a record is inserted, the internal table ends with the field defined at Byte 670. The internal table does not include the two fields defined at Bytes 671 and 672.
Am I to assume from the above explanation that the length of a record ( A.K.A. row) in an internal table cannot exceed 670 bytes?
Thank you.

Manish,
False alarm! While, technically, you didn't answer my question, your request for code ended up helping me answer my own question.
To provide you with some code I wrote a simple test program using the record layout referred to above, with a DO loop to put some records into the internal table, followed by a LOOP AT, with accompanying WRITE statements to display the contents of the internal table and demonstrate that the last two fields weren't being stored.
However, when I ran the test program, the last two fields were being displayed.
It was at that point, when stepping through the debugger that I noticed the scroll arrows above the last column of my internal table that allowed me to scroll to the right and see my final two fields.
Apparently, because of the large number of fields in my internal table I had reached the default display length of the debugger. While I was obviously aware of the scroll bar found at the bottom of the display, I had never worked with an internal table of that width in the past and hadn't even noticed the scroll arrows above the last column before.
Thanks for taking the time to respond helping me get to the solution.

Cost Component structure field and table names

Hey all,
i need to code a BADI to push value of one column in cost component structure to another column in ccs for only order settlements..
any idea how to do this??
i am very new to abap please take it easy on ur answer..
i coulndt even find in which table and fields these values are stored...
thank you

I have an OSS note, it tells you step by step how to config the badi u need.. but does not mention about the logic u ll use.. it is up to you....
so i need to find the field names and tell take these and post them to these columns...
i dont know if i make any sence, but this is all i need to do...
so i have the body i have the logic but i dunno the import and export fields...
i believe the table is ckmlkeph.... and field that populate the columns are kst0XX, but i cannot see the field name and table name if i select a line in the column and F1 ????

Questions on: 1) Last Update; 2) Max String Length; 3) dynamic table keys

Hi:
- I am currently prototyping a plug-in but I have some questions:
- 1) At the 'All Metrics' table, what is the intent of the 'Last Upload' field,
and how is this field updated?
- I have created some metrics but for some metrics the 'Last Upload' field
has a timestamp but for other metrics there is no data.
As far as I know, the metrics are similar but I do not know why the behaviour is different.
- 2) Is there a maximum string length that the Oracle agent can accept?
- I have a script which just returns all the environment variables into one cell.
In emagent.trc, the Oracle agent issues the following warning:
2009-08-27 12:38:47 Thread-76336 WARN upload: Truncating value of "STRING_VALUE" from "AGENT_HOME=
- Is the truncation an issue?
- 3) I have created some dynamic tables from performing an snmp walk, but the key that I use
is the index of the SNMP table. The data is collected correctly, but I am not sure that using
the table index as the key for OEM is a good idea because the metrics are stored according to the SNMP table index.
Should the OEM key be the something like 'object name' instead of the index number from performing an SNMP walk ?
For example, when I click a metric, the metric name is: Sensor Index 1.
But should it not be something like 'Fan #1' ?
Thanks John

Metrics are collected at certain intervals, the Last Upload field indicates the date and time of the last time a metric collection was uploaded. The quicker the interval, the more recent that date should be. If you don't specify a CollectionItem in your default collection file for your metrics, they won't be collected or uploaded.
If your metric column is a STRING type, it is stored in a VARCHAR2(4000)
I'm not sure I understand your last problem... You have a table metric with a set of columns. The column you use as the key is just some tracking index which doesn't really mean anything. As long as your key column(s) make the row unique, the agent will be satisfied. If you want something more meaningful as your key, then it's something you will have to inject into your dataset if it isn't already there.

Need to find table/field behind "Item long text" field in Notes tab in FB70

Hello,
To print a custom FI invoice, I need to access the data entered in the "Item long text" field of the Notes tab in FB70. To test, I used 5000 characters in that field to make sure it stood out from the rest of the data. F1 help does nothing on that field, and even running an SQL trace (ST05) doesn't show the text in that field being entered into any table. I tried F1 on a nearby field and got a structure instead of a table, so I investigated the structure through SE11 but found no character field with such a large capacity. How else can I find where that field is stored?

Thanks! It took a while, but with your help and a few other pages I managed to piece together an answer.
Vinod helpfully explained that the text name is a concatenation of various fields, but didn't specify how to find the line item ID. If you go to table STXH (as hinted by Brad and confirmed [here|http://fuller.mit.edu/SAPWebDocs/LongComment.html]) and search for texts created today (or whenever you were testing), you'll see the text name ends in '001' after GJAHR, so the line item ID is '001' regardless of how many line items you enter in the invoice.
Armed with that info, you can call READ_TEXT and loop through the results to concatenate the contents of each TDLINE field. (FB70 automatically breaks the user-entered text into different lines even if the user didn't press Enter, and each line gets its own record in the results.)
Thanks again,
Pedro

FB03 - Increase length of the field "Account Short Text" in FB03

Dear Expert!
I understand that Tcode: FB03 is SAP standard tcode. However, i just want to ask, is it possible to increase length of the field "Account Short Text" to 42 characters in FB03? Because my vendor/customer name is quite long, and when i view via FB03, the field "Account Short Text" only displays 20 characters, not full vendor/customer name. Unless, i double click on the line item, then i can see full vendor/customer name. But i want the "Account Short Text" field can display full vendor/customer name.
Is that possible?
Thank you very much.
LeLinh

Hi,
there's a matadata table behind it RFPSD and for Account short text field KTEXT is used, which in fact has a length of 35 chars.
But on the other hand there's also a filed KTEXT_GL (G/L Account Short text) which is maybe applied here. It has a length of 20.
You can do some more checks on program to clear it finally
Regards

Does length of CBO table's field is shorter than structure field?

Similar Messages

Maybe you are looking for