Preview field length in DIAdem ascii import assistant too small

I am evaluating the DIAdem 8.0 software, and cannot seem to get around the field length of the preview in the ascii import assistant. The default field is 10240 bytes, my file header is much larger than this (I don't make the files, I just use them . If I can't see the headers, I cannot properly import the file. Is there a variable available to increase the default size on the preview field? Adjusting the memory options doesn't seem to affect the field size at all...

Could you ZIP your ASCII file and upload it here, I would like to try to find a solution to your problem and need a file for testing.
You might want to provide a file with 'uncritical' i.e. non-confidential data, as everybody will be able to download your file once you make it available here.
I look forward to receiving your file.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Similar Messages

Input ascii file to diadem with ascii-import filter

Hello,
i want to import an ascii-file to diadem7.02 and want to save it as an .DAT-File.
i do this with Fileload and with the ascii-import filter. My problem is, when i want to record a autosequence, and i open the ascii-import filter und push the Ctrl-A key, it doesn´t record this window in the autosequence.
Is this unpossible in DIAdem or have anyone a solution for it.

Thank you Brad for your help,
but this solution is only for Diadem 8 and i have version 7.02.
I have hardly experience in Diadem 8 and nothing in vbs-programming so i had to solve this problem in Diadem 7.
Attachments:
BZE_fb2_001_3.zip ‏1 KB
asciidef.stp ‏1 KB

Length error occured in IMPORT statement

Hello everyone,
i hv one requirment in PO print(ME23N). in po print asset no nt display without changing other format.
so that i first copy both smartform and driver program, in that i made certain changes such that i declare the patameter p_ebeln and i comment to data statement of p_ebeln & p_ebeln = nest-objky.
then i join asset no (anek-anln1) with the help of inner join. then in smartform i gave condition that if bsart = 'ZCAP'
wa_final-anln1 = gv_anln1.
endif.
i import gv_anln1 in smartform and exported in deriver program.
both are synthetically currect but when i gave print preview dump is occured.
length error occured in IMPORT statement
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
     not caught in
    procedure "%GLOBAL_INIT" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    During import the system discovered that the target object has
    a different length than the object to be imported.
what i do?

Hello,
can u send me coding for that?
program line is already created for that
and their first coding is like that,
if gv_bsart = 'ZCAP'.
wa_final-matnr = space.
endif.
and in text they fetch matnr no.
but as per requirement they want asset no when bsart = 'ZCAP'
how that asset no will come.
matnr comes there is bsart is other that ZCAP, but bsart = ZCAP they want asset no instead of matnr.

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

I am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

i am trying to generate purchase order and i create a BAPI also which is active.
But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Hi,
Yeah i tried my Z_BAPI in R3 and then giving some ERROR.
This is my CODE-
FUNCTION ZBAPIPOTV2.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(POHD) TYPE ZPOHD OPTIONAL
*"     VALUE(POITEM) TYPE ZPOITEM OPTIONAL
*" TABLES
*"      RETURN STRUCTURE BAPIRET1 OPTIONAL
data: ls_pohd type bapimepoheader,
         ls_pohdx TYPE bapimepoheaderx,
         lt_poit TYPE TABLE OF bapimepoitem,
         lt_poitx TYPE TABLE OF bapimepoitemx,
         ls_poit TYPE bapimepoitem,
         ls_poitx TYPE bapimepoitemx.
   MOVE-CORRESPONDING pohd to ls_pohd.
   MOVE-CORRESPONDING poitem to ls_poit.
   ls_pohdx-comp_code = 'x'.
   ls_pohdx-doc_type = 'x'.
   ls_pohdx-vendor = 'x'.
   ls_pohdx-purch_org = 'x'.
   ls_pohdx-pur_group = 'x'.
   ls_poit-po_item = '00010'.
   APPEND ls_poit to lt_poit.
   ls_poitx-po_item = '00010'.
   ls_poitx-po_itemx = 'x'.
   ls_poitx-material = 'x'.
   ls_poitx-plant = 'x'.
   ls_poitx-quantity = 'x'.
   APPEND ls_poitx to lt_poitx.
CALL FUNCTION 'BAPI_PO_CREATE1'
   EXPORTING
     POHEADER                     = ls_pohd
    POHEADERX                    = ls_pohdx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
* IMPORTING
*   EXPPURCHASEORDER             =
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
    RETURN                       = return
    POITEM                       = lt_poit
    POITEMX                      = lt_poitx
*   POADDRDELIVERY               =
*   POSCHEDULE                   =
*   POSCHEDULEX                  =
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
ENDFUNCTION.
i am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

How to set field length in Dynamic IT tab

Hi All,
 I am creating 1 dynamic internal table with refrence of field catalog, but in the dynamic IT tab and work area i am gettinf field length is 10 char.
But i want to change this into 15 or 20 char like this.... how can i change this
Please help me .
DATA: ep_tab TYPE REF TO data,
 new_line TYPE REF TO data.
FIELD-SYMBOLS: <l_table> TYPE table,
 <l_line> TYPE ANY.
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 I_STYLE_TABLE = c_char
 it_fieldcatalog = it_fieldcatalog
 I_LENGTH_IN_BYTE = ' '
 IMPORTING
 ep_table = ep_tab.
ASSIGN ep_tab->* TO <l_table>.
CREATE DATA new_line LIKE LINE OF <l_table>.
ASSIGN new_line->* TO <l_line>.
This is my code.
Regards,
Arjun.

Hi,
try this
** ALV DECALRATION
DATA : wa_lvc_cat TYPE lvc_s_fcat,
 gt_lvc_cat TYPE lvc_t_fcat.
DATA : wa_fieldcat TYPE slis_fieldcat_alv,
 gt_fieldcat TYPE slis_t_fieldcat_alv.
DATA : wa_slis_layout TYPE slis_layout_alv.
PERFORM create_dynamic_itab. " Fill fieldcatlog and create dynamic itab
*& Form CREATE_DYNAMIC_ITAB
* text
* --> p1 text
* <-- p2 text
FORM create_dynamic_itab .
CLEAR g_pos .
PERFORM fill_gt_lvc_cat_fld USING 'MATNR' 18 . "fieldname outputlen.
PERFORM fill_gt_fieldcat_field USING c_x 'MATNR' 'CHAR' 18 text-006.
PERFORM fill_gt_lvc_cat_fld USING 'CODE' 40 .
PERFORM fill_gt_fieldcat_field USING ' ' 'CODE' 'CHAR' 40 text-024.
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = gt_lvc_cat
 IMPORTING
 ep_table = new_table.
ENDFORM. " CREATE_DYNAMIC_ITAB
*& Form FILL_gt_lvc_cat_FLD
* text
* -->P_0006 text
* -->P_18 text
FORM fill_gt_lvc_cat_fld USING p_fieldname TYPE any
 p_outputlen TYPE any.
wa_lvc_cat-fieldname = p_fieldname . " 'MATNR'
wa_lvc_cat-outputlen = p_outputlen. " 18
APPEND wa_lvc_cat TO gt_lvc_cat.
CLEAR wa_lvc_cat.
ENDFORM. " FILL_gt_lvc_cat_FLD
*& Form FILL_GT_FIELDCAT_FIELD
* text
* -->P_C_X text
* -->P_0012 text
* -->P_0013 text
* -->P_18 text
* -->P_TEXT_006 text
FORM fill_gt_fieldcat_field USING p_key TYPE any
 p_fieldname TYPE any
 p_datatype TYPE any
 p_outputlen TYPE any
 p_seletext_m TYPE any.
g_pos = g_pos + 1.
wa_fieldcat-col_pos = g_pos. " 1.
wa_fieldcat-key = p_key . " c_x.
wa_fieldcat-fieldname = p_fieldname. " 'MATNR'.
wa_fieldcat-datatype = p_datatype. " 'CHAR'.
wa_fieldcat-outputlen = p_outputlen. " 18.
wa_fieldcat-seltext_m = p_seletext_m. " text-006. "'Material'.
APPEND wa_fieldcat TO gt_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. " FILL_GT_FIELDCAT_FIELD
PERFORM fill_output_layout. " Fill the output data into field symbol
*& Form FILL_OUTPUT_LAYOUT
* text
* --> p1 text
* <-- p2 text
FORM fill_output_layout .
ASSIGN new_table->* TO <fs_table>.
CREATE DATA new_line LIKE LINE OF <fs_table>.
ASSIGN new_line->* TO <fs_line>.
LOOP AT gt_mseg INTO wa_mseg.
 ASSIGN COMPONENT 'MATNR' OF STRUCTURE <fs_line> TO <fs_field>.
 <fs_field> = wa_mseg-matnr.
 READ TABLE gt_grdtrans INTO wa_grdtrans WITH KEY mawerk = wa_mseg-WERKS
 matnr = wa_mseg-matnr
 mat_doc = wa_mseg-mblnr binary search.
 IF sy-subrc = 0.
 LOOP AT gt_qmfe INTO wa_qmfe WHERE qmnum = wa_grdtrans-qmnum.
 READ TABLE gt_qpct2 INTO wa_qpct2 WITH KEY codegruppe = wa_qmfe-fegrp
 code = wa_qmfe-fecod
 BINARY SEARCH .
 IF sy-subrc = 0.
 ASSIGN COMPONENT 'CODE' OF STRUCTURE <fs_line> TO <fs_field>.
 <fs_field> = wa_qpct2-kurztext.
 ENDIF.
 endloop.
 clear wa_qmfe.
 ENDIF.
ENDLOOP.
 CLEAR wa_mseg.
PERFORM fill_layout. " Filling the layout of REUSE_ALV_GRID_DISPALY
*& Form FILL_LAYOUT
* text
* --> p1 text
* <-- p2 text
FORM fill_layout .
wa_slis_layout-zebra = c_x.
wa_slis_layout-colwidth_optimize = c_x.
ENDFORM. " FILL_LAYOUT
Edited by: ShaliniSinha on Mar 30, 2009 1:49 PM
Edited by: ShaliniSinha on Mar 30, 2009 1:55 PM

Custom IDOC type Segment-field length change

Hello,
We have a custom segment developed for triggering Outbouds. I'm tring to change the Field length of a deta element used for one of the fields in the segment.
But after chaning the data element and activating it also, the changes are not effecting in WE31/ in the structure of the segment.
Process I'm following:
we31 <segment>
......cancel release
Change data element and activate
....set release.
Please suggest if something else can be done
Thanks,
Lucky.

> @Sarvesh: The IDOC segment has been released. I also re-imported the IDOC into XI - is that what you mean by 'reloaded'?
No, re-importing in XI is different from reloading the metadata into ABAP stack of XI using IDX2 transaction. So if you have not done this, then this could be the main reason of truncating the length.
Regards,
Sarvesh

How to add field length constraints when using an existing JavaBean model

Within our current project we used a O/R mapping tool to generate our JavaBean model. For e.g.
public class Person{
private String name; ...getName() ...setName(...)
}
The whole model is used within our Web Dynpro project. Now it's a requirement to implement field length constraints. Normally this is no problem using ISimpleType like the following:
attributeInfo = wdContext.nodePerson().getNodeInfo().getAttribute
(IPrivate...IPersonElement.NAME);
ISimpleTypeModifiable type = attributeInfo.getModifiableSimpleType();
type.setLength(60);
But we've got an runtime exception that it is not allowed to modify the models datatype:
com.sap.tc.webdynpro.progmodel.context.ContextException: AttributeInfo
(Basics.Person.name): must not modify the datatype of a mapped attribute
at
com.sap.tc.webdynpro.progmodel.context.AttributeInfo.getModifiableSimpleType
(AttributeInfo.java:337)
The question is how could a workaround look like. Or is there nothing like that and we have to build a dictionary type tier upon our JavaBean model. Any ideas ?
thx,
s.w.

Sabine,
You may:
1. Import JavaBeans model
2. Create DDIC type with necessary constarints (string-based, max. length 60)
3. Open editor for target model class and change type of property.
See my blog /people/valery.silaev/blog/2005/06/29/apojo--almostplain-old-java-objects-as-model (section "Tweaking model classes") for details.
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

Forms not updating field lengths

All,
I've been changing field lengths in forms all day in OIM 9.1, and it never updates the actual column lengths when the form is activated. I've reverted to directly updating the column sizes in the database to get things working. Am I missing something here, or are field length changes in OIM completely useless?
S

We faced recently a similiar problem, but regarding export/import operations.
We changed the forms in our dev environment, and sizes updated correctly in the database. But when exporting and importing the forms into the QA environment, although field size in the form definition was updated, the field size in the database table didn't.
The workaround we found was to manually change field sizes in the form definition.
Hope this help!

CL_ABAP_TYPEDESCR - DESCRIBE_BY_DATA field length is doubled

I have a custom program developed on Non Unicode system, that is using CL_ABAP_TYPEDESCR -> DESCRIBE_BY_DATA to get field lengths of the fields in a structure. The code works perfectly file on Non Unicode system where it is developed, However when the same code is imported on a UNICODE system the field lengths of the fields in the same structure are exactly doubled. Anybody has any idea, why this may be happening?

> However when the same code is imported on a UNICODE system the field lengths of the fields in the same structure are exactly doubled. Anybody has any idea, why this may be happening?
Yes - because Unicode uses two bytes to represent ONE character.
Markus

Length error occurred in IMPORT statement.

Hi All,
           while exexuting a program i got dump saying that Length error occurred in IMPORT statement. through ST22 i came to know that both import and export structres are not same. Import structure is longer than the export structure.
         I tried in SDN but i coudnt find any solution. can you please suggest how to solve this.
Thanks in advance,
Sreekala.

Hi,
Maybe what you can do si....
Program X
data: v_var(20) type c.
export v_var.
Program Y
data: v_var(20) type c,
         v_var2(50) type c.
import v_var.
v_var2 = v_var.
Create a variable that is exactly the same with the exporting parameter, then just assign it to a local variable declared in the 2nd program.
Hope this helps.
Benedict

How to add more fields at level task for importing to MsProject

Hi everyone,
We would like to have the same number of fields either for importing as exporting; or at least, the fields that we need.
The problem is when we are configurating the fields for exporting from cProjects to MsProject, we found 81 available fields and then we don't find the same amount for importing (34). So, in some cases we don't find fields which were configurated for exporting and it is no posible to upload the information back because the field is no available for importing.
Does anyone knows how to add more fields for importing at the cProjects side?
Thanks a lot,
CAMILO URIBE

Some fields can not be migrated because of MsProject designe. The above is the reason why cProjects' customizing does not offer the
mapping of the same nuember of fields.

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

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

I am not able to import photos into Lightroom 5.7. When I select a folder, it doesn't show a preview of the images and the import button is greyed out. ??

I am not able to import photos into Lightroom 5.7. When I select a folder, it doesn't show a preview of the images and the import button is greyed out. ??
I have been using Lightroom 5 for 2-3 months now and all worked well, up until today's effort to import a new set of photos. I am working on a Mac with Yosemite 10.10.1.

Go to the bibliothec module, select the folder, right click on the folder and hit synchronize
Sorry I have only a german version , so don't know what your menu will show.

Preview field length in DIAdem ascii import assistant too small

Similar Messages

Maybe you are looking for