BBPIV03: Field name invalid GS_SCREEN_MAINDATA-CURRENCY

Hi everybody
In BBPIV03, in the search help of the currency I get the next message
Field name invalid GS_SCREEN_MAINDATA-CURRENCY .
I have only seen SAP NOTE 438430, but this note don't apply to my system.
SRM SERVER 550 SAPKIBKT06
does anybody know how I can solve this?
The log shows me:
M    ***LOG W01=>  [itsplxx.c    1552]
W    *** ERROR => ipl_ConvertOut returns -9(ITSPE FAILURE) [itsplxx.c    1554]
W    *** ERROR => Raise Last error:[41 from: w3xxsemg.cpp:3436] [itsplxx.c    1230]
W    *** ERROR => RaiseError(sapdext) ITS_P:41 [w3xxsemg.cpp 3436]
W    *** ERROR =>            MSGV0(GS_SCREEN_MAINDATA-CURRENCY) [w3xxsemg.cpp 3436]
M  ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   13205]
Thanks
Regards

Hi Atul,
When I am creating an invoice and I use the search help for the currency.
<b>- The ITS Dump says</b>
Field name invalid GS_SCREEN_MAINDATA-CURRENCY .
<b>- The log system says</b>
Further details for this message type
Module nam Loc T100................    Parameters
                ITS_P               041
Documentation for system log message D0 1 :
The transaction has been terminated.  This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction.  The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message &aGS_SCREEN_MAINDATA-CU
Not found
No documentation exists for message &a-CU
Log
<b>The trace file content is</b>
W Wed May 02 12:43:46 2007
W      *** WARNING => diag: SemgSyncTransaction: Resync required [w3xxsemg.cpp 3141]
W        *** WARNING => diag: SemgSyncTransaction: SyncFrames returned rc=0xffffffcf [w3xxsemg.cpp 3276]
W        *** WARNING => diag: SemgSyncTransaction: Trying to recover state [w3xxsemg.cpp 3344]
W        *** ERROR => diag: SemgHandleSearchhelpRequest: SetCursor returned rc=0xffffffd9 [w3xxsemg.cpp 3435]
W        *** WARNING => diag: SemgXGHandleRequest: Can't submit after request [w3xxsemg.cpp 1126]
W      *** ERROR => plugin: XKrnHandleRequest failed. 000007FF44D283B0 rc: -9 [itspxkrn.cpp 405]
W    *** ERROR => ipl_ConvertOut failed rc = -9, send icf error page [itsplxx.c    1551]
M    ***LOG W01=>  [itsplxx.c    1552]
W    *** ERROR => ipl_ConvertOut returns -9(ITSPE FAILURE) [itsplxx.c    1554]
W    *** ERROR => Raise Last error:[41 from: w3xxsemg.cpp:3436] [itsplxx.c    1230]
W    *** ERROR => RaiseError(sapdext) ITS_P:41 [w3xxsemg.cpp 3436]
W    *** ERROR =>            MSGV0(GS_SCREEN_MAINDATA-CURRENCY) [w3xxsemg.cpp 3436]
M  ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   13205]
A
Thanks and regards
Pd. I think I'm going to open a SAP message

Similar Messages

  • Cannot edit wiki pages-- Exception message: Invalid field name

    We have migrated from one Sharepoint 2010 environment to another Sharepoint 2010 environment and only wanted to preserve a few sites, mostly Enterprise Wiki Sites.
    We have imported 5 total Enterprise Wiki Sites, all of which point to particular Term Sets in Managed Metadata. 
    2 wikis are pointed to term set A, 2 wikis are pointed to term set B and one wiki is pointed to term set C.
    One of the wikis pointed to term set A is working, and one is not
    The malfunctioning wiki has the following symptom:
    Whenever you try to edit a page (new or existing) and save your changes, regardless of whether it is tagged, you cannot save your changes.  When you try, you get the error below.
    Error
    Failed to get value of the "Wiki Categories" column from the "Managed Metadata" field type control. See details in log. Exception message: Invalid field name. {f863c21f-5fdb-4a91-bb0c-5ae889190dd8}
    https://sharepoint.domain.com/wiki/adminwiki /wiki/adminwiki/Pages.
    Troubleshoot issues with Microsoft SharePoint Foundation.
    Correlation ID: 4188c150-de8f-4940-9dbd-54939f117bfe
    Date and Time: 3/12/2012 4:26:09 PM
    Go back to site
    To me, it looks like there is an invalid URL, since it gives the URL path, and then there is a space, and then it also has a relative URL to /wiki/adminwiki/pages ...is this normal?
    Any ideas on how to fix this is great.  I don't think it has anything to do with the Managed Metadata service or the Term Store since the other wiki site (pointing to the same exact Term Set) is working normally with no problems.

    To solve the problem make sure that the template you are using for the current page (with errors) has the same content type as the page. In example of the Enterprise Wiki page, I forgot to set the content type to an Enterprise Wiki page on a custom page
    template I just added to the Master pages.
    So what I had to do is:
    go to properties of the page with errors described above and set it to be
    Enterprise Wiki page
    go to master pages and set the custom template to be of the same type, Enterprise Wiki page
    That solved the problem

  • How to correct an invalid BDC Field Name in FEBEP table

    Hi,
    In FEBAN processing, I am unable to re-process a failed transaction because of an invalid value in "BDC Field Name" field.  This entry has not generated any document so far. Is there any way I can fix this error?
    Thanks.

    Hi,
    Goto FEBAN.
    1.     Highlight the item in error.
    2.     Click on u201CEdit->Posting Mode->In Foregroundu201D from the menu.
    3.     Click on u201CStatement Items -> Postu201D from the menu.
    Edit incorrect fields and post.

  • System.ArgumentException: Invalid field name. {c042a256-787d-4a6f-8a8a-cf6ab767f12d} while Activating Info path form Feature

    We are encountering an error while activating features for info-path form on site collection.Earlier It was working fine but when we deactivate info path feature on site collection and try to activate again with updated info path form its giving below error.
    Feature receiver assembly 'Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c', class 'Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver', method 'FeatureActivated' for feature '86e128c1-8d91-9809-ac8a-7b77e8a2159b'
    threw an exception: System.ArgumentException:Invalid field name. {c042a256-787d-4a6f-8a8a-cf6ab767f12d} at Site Collection url at Microsoft.SharePoint.SPFieldCollection.GetFieldById(Guid
    fieldId, Boolean bThrowException) at Microsoft.SharePoint.SPFieldCollection.get_Item(Guid id) at Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver.UpdateContentType(SPContentType contentType, String serverRelativeUrl, FormTemplate formTemplate)
    at Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver.CreateOrUpdateContentTypes(SPSite currentSite, String serverRelativeUrl, FormTemplate formTemplate) at Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties
    properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)

    Hi Prathap singh.
    Greetings . pls try to deactivate from powerhell and activate it again
    http://social.technet.microsoft.com/Forums/office/en-US/e79ebe96-2b48-46e3-8cce-6caed44f0418/invalid-field-name-error-while-trying-to-deactivate-administrator-approved-infopath-form-template?forum=sharepointcustomizationprevious
    http://social.technet.microsoft.com/Forums/office/en-US/ddb8b710-138a-4e26-bf46-65ebd0ac525f/i-get-the-invalid-field-name-when-trying-to-activate-feature-to-publish-infopath-form?forum=sharepointcustomizationlegacy
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • "Invalid Field Name" Error message on Client System

    Hi all,
    I have installed some addons  on server, and the same is installed on client systems as well. on server everything works well. But when it comes to client systems, one particular form shows an error message, "Invalid Field Name", on loading the form.
    I have the same .srf's as on server but still the problem persists. If anybody knows the cause of the problem, please let me know what could be the reason.
    Regards,
    Rohan S. Kamble.

    Hi Rohan,
    Are you sure you have the same version of DI (also addon) on your client and your server side?
    Reinstall the addon on your client, check if the problem still happens.
    Regards,
    Jay.

  • Failing to export with Export-SPWeb - Invalid Field Name error

    Hi,
    I am trying to export a site collection and restore the site collection to a sub site. In order to do that I have used Export-SPWeb command to export the site collection. The command I used 
    Export-SPWeb -Identity http://SitecollectionURL/ -Path "F:\filename.bak" -IncludeUserSecurity -Compression 1024 -IncludeVersions 4
    I got the below error,
    Progress: Starting to process objects of type ContentType.
    FatalError: Invalid field name. {c876558a-1cb9-4a87-bf55-ee69876f6b8b} http://sitecollectionURL/
    Debug:    at Microsoft.SharePoint.SPFieldCollection.GetFieldById(Guid fieldId, Boolean bThrowException)
       at Microsoft.SharePoint.SPFieldLinkCollection.Load(XmlReader xrdr)
       at Microsoft.SharePoint.SPFieldLinkCollection.EnsureLoaded()
       at Microsoft.SharePoint.SPFieldLinkCollection.Save(XmlTextWriter xwtr)
       at Microsoft.SharePoint.Deployment.ContentTypeSerializer.GetDataFromDataSet(Object obj, SerializationInfo info, StreamingContext context)
       at Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object obj, SerializationInfo info, StreamingContext context)
       at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object obj, ISerializationSurrogate surrogate, String elementName, Boolean bNeedEnvelope)
       at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream serializationStream, Object topLevelObject)
       at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
       at Microsoft.SharePoint.Deployment.SPExport.Run()
    I need assistance on this. 
    Thanks in advance
    -Sasi

    Hi Sasi,
    Export-SPWeb is used to export a site, list, or library rather than a site collection. The Identity of the command should be a site.
    Based on your description, my understanding is that you want to export a site and import it to aother site. Is it right?
    I run your command using the URL of my site instead of the
    http://SitecollectionURL/, everything worked well. Please re-run the command below:
    Export-SPWeb -Identity <URL of your site> -Path "F:\filename.bak" -IncludeUserSecurity -Compression 1024 -IncludeVersions 4
    In addition, please try to export the site via Central Administration->Backup and Restore->Export a site or list under Granular Backup, and select the site collection and the site, then  click ‘Start Export’. If you want to import the exported
    site to another site, you should use Import-SPWeb command.
    About Export-SPWeb command:
    http://technet.microsoft.com/en-us/library/ff607895(v=office.15).aspx
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Exception message, failed to get value, could not load managed metadata, invalid field name

    Hi, i have created some site collection columns with managed metdata and taxonomy term sets. I have then created some site content types of those site columns. Some of them function properly and some don't.
    When i have created or uploaded a document to the document library i start to "tag" the document by first choosing witch conent type i want too use, but when it comes to save the document it renders an error message(its not the full content
    of the message):
    "exception message, failed to get value, could not load managed metadata, invalid field name"
    I have created some other site content types before and with the same site columns and they do not generate a error message. Is there a solution for my dilemma?

    try these links:
    https://prashobjp.wordpress.com/2014/02/14/failed-to-get-value-of-the-column-name-column-from-the-managed-metadata-field-type-control-see-details-in-log-exception-message-invalid-field-name-guid-site-url/
    http://www.sharepointconfig.com/2011/03/issues-provisioning-sharepoint-2010-managed-metadata-fields/
    http://blog.goobol.com/category/sharepoint/sharepoint-issue-troubleshooting/
    http://www.instantquick.com/index.php/correctly-provisioning-managed-metadata-columns?c=elumenotion-blog-archive/random-whatnot
    https://pholpar.wordpress.com/2010/03/03/taxonomy-issues/
    Please mark answer as correct if it is correct else vote for it if you find it useful Happy SharePointing

  • Table name and field name

    hi frds
    Give me table name and field name of OPEN PO QUANTITY ..
    thanks
    Pari Vendhan.R

    See the sample code for the open PO's based on Vendor
    and do accordingly
    *& Report ZMM_PO_REPORT
    REPORT ZMM_PO_REPORT message-Id yb
    NO STANDARD PAGE HEADING
    LINE-COUNT 60(1)
    LINE-SIZE 230.
    D A T A B A S E T A B L E S D E C L A R A T I O N
    TABLES: lfa1, " Vendor Master
    t161, " PO Doc Types
    t024, " Purchase Groups
    ekko. " PO Header
    T Y P E S D E C L A R A T I O N S
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_po,
    ebeln TYPE ebeln, " PO No.
    ebelp TYPE ebelp, " PO Item
    bstyp TYPE bstyp, " PO Category
    bukrs TYPE bukrs, " Company Code
    bsart TYPE bbsrt, " PO Type
    lifnr TYPE lifnr, " Vendor No
    ekgrp TYPE bkgrp, " Purchase Group
    waers TYPE waers, " Currency
    bedat TYPE etbdt, " PO Date
    txz01 TYPE txz01, " Material Text
    werks TYPE ewerk, " Plant
    lgort TYPE lgort_d, " Storage Location
    matkl TYPE matkl, " Material Group
    menge TYPE bamng, " PR Quantity
    meins TYPE bamei, " UOM
    bprme TYPE bbprm, " Price Unit
    netpr TYPE netpr, " Net price
    peinh TYPE peinh, " Price Unit UOM
    pstyp TYPE pstyp, " Item Category
    knttp TYPE knttp, " Account Assignment Category
    END OF s_po.
    Purchase Orders History Structure
    TYPES: BEGIN OF s_account,
    ebeln TYPE ebeln, " PO No.
    ebelp TYPE ebelp, " PO Item
    gjahr TYPE mjahr, " Fiscal Year
    belnr TYPE mblnr, " PO Invoice No
    menge TYPE menge_d, " PR Quantity
    wrbtr TYPE wrbtr, " Price in Local Currency
    dmbtr TYPE dmbtr, " Price in Foreign Currency
    waers TYPE waers, " Currency
    shkzg TYPE shkzg, " Dr/Cr Indicator
    END OF s_account.
    Purchase Orders History Structure(Item Sum)
    TYPES: BEGIN OF s_inv_sum,
    ebeln TYPE ebeln, " PO No.
    ebelp TYPE ebelp, " PO Item
    menge TYPE menge_d, " PR Quantity
    wrbtr TYPE wrbtr, " Price in Foreign Currency
    waers TYPE waers, " Currency
    END OF s_inv_sum.
    Purchase Orders Main Structure
    TYPES: BEGIN OF s_rep,
    lifnr TYPE lifnr, " Vendor No
    ebeln TYPE ebeln, " PO No.
    ebelp TYPE ebelp, " PO Item
    bstyp TYPE bstyp, " PO Category
    bsart TYPE bbsrt, " PO Type
    ekgrp TYPE bkgrp, " Purchase Group
    waers TYPE waers, " Currency
    bedat TYPE etbdt, " PO Date
    txz01 TYPE txz01, " Material Text
    werks TYPE ewerk, " Plant
    lgort TYPE lgort_d, " Storage Location
    matkl TYPE matkl, " Material Group
    menge TYPE bamng, " PR Quantity
    meins TYPE bamei, " UOM
    bprme TYPE bbprm, " Price Unit
    netpr TYPE netpr, " Net price
    peinh TYPE peinh, " Price Unit UOM
    pstyp TYPE pstyp, " Item Category
    knttp TYPE knttp, " Account Assignment Category
    name1 TYPE name1, " Plant
    orewr TYPE netpr, " To be Invoiced Price
    curr TYPE waers, " Inv Doc Currency
    END OF s_rep.
    D A T A D E C L A R A T I O N S
    DATA: gv_title1 TYPE sylisel, " Report title
    gv_dial. " Color flag
    C O N S T A N T S D E C L A R A T I O N S
    CONSTANTS: c_x VALUE 'X', " Flag X
    c_h VALUE 'H', " Debit
    c_vgabe TYPE vgabe VALUE '2'. " Transaction Type
    I N T E R N A L T A B L E S D E C L A R A T I O N S
    DATA: i_po TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
    " Purchase Order
    i_inv TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
    " PO Invoice Values
    i_rep TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
    " PO Invoice Values
    i_ekbe TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
    " PO Invoice Values
    S E L E C T I O N S C R E E N *
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
    s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
    s_bsart FOR t161-bsart,
    s_ekgrp FOR t024-ekgrp,
    s_bedat FOR ekko-bedat.
    SELECTION-SCREEN END OF BLOCK b1.
    I N I T I A L I Z A T I O N *
    INITIALIZATION.
    A T S E L E C T I O N - S C R E E N *
    AT SELECTION-SCREEN.
    Validate the screen fields
    PERFORM validate_screen.
    S T A R T - O F - S E L E C T I O N *
    START-OF-SELECTION.
    Fetch main data
    PERFORM fetch_data.
    T O P - O F - P A G E *
    TOP-OF-PAGE.
    Header of the List
    PERFORM header.
    E N D - O F - P A G E *
    Footer
    END-OF-PAGE.
    ULINE.
    E N D - O F - S E L E C T I O N *
    END-OF-SELECTION.
    Display the Report Output data
    PERFORM display_data.
    At Line-Selection
    AT LINE-SELECTION.
    When double clicked on EBELN display the details of Purchase Doc
    PERFORM line_sel.
    *& Form validate_screen
    Validation of Selection Screen fields
    FORM validate_screen .
    Validation of Vendor Number
    CLEAR lfa1-lifnr.
    IF NOT s_lifnr[] IS INITIAL.
    SELECT lifnr UP TO 1 ROWS
    INTO lfa1-lifnr
    FROM lfa1
    WHERE lifnr IN s_lifnr.
    ENDSELECT.
    IF sy-subrc 0.
    MESSAGE e000 WITH 'Invalid Vendor'(002).
    ENDIF.
    ENDIF.
    Validation of PO Number
    CLEAR ekko-ebeln.
    IF NOT s_ebeln[] IS INITIAL.
    SELECT ebeln UP TO 1 ROWS
    INTO ekko-ebeln
    FROM ekko
    WHERE ebeln IN s_ebeln.
    ENDSELECT.
    IF sy-subrc 0.
    MESSAGE e000 WITH 'Invalid Document Number'(003).
    ENDIF.
    ENDIF.
    Validation of PO Document Type
    CLEAR t161-bsart.
    IF NOT s_bsart[] IS INITIAL.
    SELECT bsart UP TO 1 ROWS
    INTO t161-bsart
    FROM t161
    WHERE bsart IN s_bsart.
    ENDSELECT.
    IF sy-subrc 0.
    MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
    ENDIF.
    ENDIF.
    Validation of Purchasing Group
    CLEAR t024-ekgrp.
    IF NOT s_ekgrp[] IS INITIAL.
    SELECT ekgrp UP TO 1 ROWS
    INTO t024-ekgrp
    FROM t024
    WHERE ekgrp IN s_ekgrp.
    ENDSELECT.
    IF sy-subrc 0.
    MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
    ENDIF.
    ENDIF.
    ENDFORM. " validate_screen
    *& Form fetch_data
    Fetching the PO related data from Database Tables
    FORM fetch_data .
    CLEAR i_po.
    REFRESH i_po.
    SELECT a~ebeln " PO No.
    b~ebelp " PO Item
    a~bstyp " PO Category
    a~bukrs " Company Code
    a~bsart " PO Type
    a~lifnr " Vendor No
    a~ekgrp " Purchase Group
    a~waers " Currency
    a~bedat " PO Date
    b~txz01 " Material Text
    b~werks " Plant
    b~lgort " Storage Location
    b~matkl " Material Group
    b~menge " PR Quantity
    b~meins " UOM
    b~bprme " Price Unit
    b~netpr " Net price
    b~peinh " Price Unit UOM
    b~pstyp " Item Category
    b~knttp " Account Assignment Category
    INTO TABLE i_po
    FROM ekko AS a JOIN ekpo AS b
    ON a~ebeln = b~ebeln
    WHERE a~ebeln IN s_ebeln AND
    a~lifnr IN s_lifnr AND
    a~ekgrp IN s_ekgrp AND
    a~bsart IN s_bsart AND
    a~bedat IN s_bedat.
    SORT i_po BY ebeln ebelp.
    break-point.
    IF NOT i_po[] IS INITIAL.
    Fetch the PO History/Invoice Details from EKBE Table
    CLEAR i_ekbe.
    REFRESH i_ekbe.
    SELECT ebeln " PO No.
    ebelp " PO Item
    gjahr " Fiscal Year
    belnr " PO Invoice No
    menge " PR Quantity
    wrbtr " Price in Local Currency
    dmbtr " Price in Foreign Currency
    waers " Currency
    shkzg " Dr/Cr Indicator
    INTO TABLE i_ekbe
    FROM ekbe
    FOR ALL ENTRIES IN i_po
    WHERE ebeln = i_po-ebeln AND
    ebelp = i_po-ebelp AND
    vgabe = c_vgabe.
    IF sy-subrc = 0.
    SORT i_ekbe BY ebeln ebelp.
    LOOP AT i_ekbe.
    IF i_ekbe-shkzg = c_h.
    i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
    ENDIF.
    MODIFY i_ekbe.
    ENDLOOP.
    break-point.
    Sum up the Item wise Invoice totals
    LOOP AT i_ekbe.
    AT END OF ebelp.
    READ TABLE i_ekbe INDEX sy-tabix.
    SUM.
    MOVE-CORRESPONDING i_ekbe TO i_inv.
    APPEND i_inv.
    ENDAT.
    CLEAR i_inv.
    ENDLOOP.
    SORT i_inv BY ebeln ebelp.
    break-point.
    ENDIF.
    ENDIF.
    Move the Vendor Name and Invoice Values to I_rep Internal Table
    LOOP AT i_po.
    MOVE-CORRESPONDING i_po TO i_rep.
    CLEAR i_inv.
    READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
    ebelp = i_po-ebelp.
    IF sy-subrc = 0.
    i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
    i_rep-curr = i_inv-waers.
    ELSE.
    i_rep-orewr = i_po-menge * i_po-netpr.
    i_rep-curr = i_po-waers.
    ENDIF.
    break-point.
    Get the Vendor Name
    CLEAR lfa1-name1.
    SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
    WHERE lifnr = i_po-lifnr.
    IF sy-subrc = 0.
    i_rep-name1 = lfa1-name1.
    ENDIF.
    APPEND i_rep.
    CLEAR i_rep.
    break-point.
    ENDLOOP.
    SORT i_rep BY lifnr ebeln ebelp.
    DELETE i_rep WHERE orewr LE 0.
    break-point.
    ENDFORM. " fetch_data
    *& Form display_data
    Display the Report Output data
    FORM display_data .
    DATA: lv_flag, " New Flag
    lv_rec TYPE i. " No of Records
    CLEAR lv_rec.
    IF i_rep[] IS INITIAL.
    MESSAGE e000 WITH 'No Data found'(022).
    ELSE.
    LOOP AT i_rep.
    Toggle Color
    PERFORM toggle_color.
    IF lv_flag space.
    NEW-LINE.
    ENDIF.
    At New Purchase Document
    AT NEW ebeln.
    WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
    lv_flag = c_x.
    lv_rec = lv_rec + 1.
    ENDAT.
    WRITE: 1 sy-vline,
    12 sy-vline,13(4) i_rep-bsart,
    17 sy-vline,18(10) i_rep-lifnr,
    28 sy-vline,29(35) i_rep-name1,
    64 sy-vline,65(4) i_rep-ekgrp,
    69 sy-vline,70(10) i_rep-bedat,
    80 sy-vline,81(5) i_rep-ebelp,
    86 sy-vline,87(40) i_rep-txz01,
    127 sy-vline,128(9) i_rep-matkl,
    137 sy-vline,138(1) i_rep-pstyp,
    139 sy-vline,140(1) i_rep-knttp,
    141 sy-vline,142(4) i_rep-werks,
    146 sy-vline,147(4) i_rep-lgort,
    151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
    165 sy-vline,166(3) i_rep-meins,
    169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
    185 sy-vline,186(4) i_rep-waers,
    190 sy-vline,191(5) i_rep-peinh,
    196 sy-vline,197(4) i_rep-bprme,
    201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
    217 sy-vline,218(4) i_rep-curr,
    222 sy-vline,223(7) i_rep-bstyp centered,
    230 sy-vline.
    NEW-LINE.
    hide: i_rep-ebeln.
    ENDLOOP.
    ULINE.
    FORMAT COLOR OFF.
    WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
    lv_rec COLOR 3.
    ENDIF.
    ENDFORM. " display_data
    *& Form header
    Write the Report Header
    FORM header .
    FORMAT RESET.
    header
    WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
    SKIP.
    FORMAT COLOR COL_HEADING.
    ULINE.
    WRITE:/1 sy-vline,2(10) 'Pur.Doc.No'(006) CENTERED,
    12 sy-vline,13(4) 'Type'(007),
    17 sy-vline,18(10) 'Vendor'(008) CENTERED,
    28 sy-vline,29(35) 'Name'(009) CENTERED,
    64 sy-vline,65(4) 'PGrp'(010) CENTERED,
    69 sy-vline,70(10) 'Doc.Date'(012) CENTERED,
    80 sy-vline,81(5) 'Item'(011),
    86 sy-vline,87(40) 'Material Short Text'(024) CENTERED,
    127 sy-vline,128(9) 'Mat.Group'(013),
    137 sy-vline,138(1) 'I',
    139 sy-vline,140(1) 'A',
    141 sy-vline,142(4) 'Plnt'(014),
    146 sy-vline,147(4) 'SLoc'(015),
    151 sy-vline,152(13) 'Quantity'(016) CENTERED,
    165 sy-vline,166(3) 'UoM'(017),
    169 sy-vline,170(15) 'Net Value'(018) CENTERED,
    185 sy-vline,186(4) 'Curr'(019),
    190 sy-vline,191(5) 'Per'(020),
    196 sy-vline,197(4) 'Unit'(021),
    201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
    217 sy-vline,218(4) 'Curr'(019),
    222 sy-vline,223(7) 'Doc.Cat'(026),
    230 sy-vline.
    ULINE.
    ENDFORM. " header
    *& Form toggle_color
    This routine alters the color of the records in the list FORM toggle_color.
    IF gv_dial = space.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    gv_dial = c_x.
    ELSE.
    FORMAT COLOR 1 INTENSIFIED OFF.
    CLEAR gv_dial.
    ENDIF.
    ENDFORM. " toggle_color
    *& Form LINE_SEL
    *When double clicked on EBELN field display the details of Purchase Doc
    FORM line_sel.
    CASE sy-lsind.
    WHEN '1'.
    DATA: lv_field(20),
    lv_value(10),
    lv_bstyp like i_rep-bstyp.
    clear: lv_bstyp,lv_value, lv_field.
    GET CURSOR FIELD lv_field VALUE lv_value.
    IF lv_field = 'I_REP-EBELN'.
    IF NOT lv_value IS INITIAL.
    READ LINE sy-index FIELD VALUE i_rep-bstyp
    INTO lv_bstyp.
    READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
    if lv_bstyp = 'F'.
    SET PARAMETER ID 'BES' FIELD lv_value.
    CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
    elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
    SET PARAMETER ID 'VRT' FIELD lv_value.
    CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
    elseif lv_bstyp = 'A'.
    SET PARAMETER ID 'ANF' FIELD lv_value.
    CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
    endif.
    ENDIF.
    ENDIF.
    ENDCASE.
    ENDFORM. " line_sel{code]
    <REMOVED BY MODERATOR>
    kushagra
    Edited by: Alvaro Tejada Galindo on Feb 18, 2008 2:03 PM

  • XSLT for dynamic target field names

    Hello,
    I got a requiremt where I need to create target field names from input values.
    Input XML -
    <?xml version="1.0" encoding="UTF-8"?>
    <Createelement_MT>
    <Field Name="A">
    <Value>1</Value>
    </Field>
    <Field Name="B">
    <Value>1</Value>
    </Field>
    </Createelement_MT>
    Expected OutPut XML -
    <?xml version="1.0" encoding="UTF-8"?>
    <Createelement_MT>
    <Statement><TableName><table>XYZ</table>
    <access>
    <A> 1 </A>
    <B> 2 </B>
    </access>
    </Statement></TableName>
    </Createelement_MT>
    The value of the attribute 'Name' of field 'Field' should be the name of target field.
    XSLT:
    <?xml version="1.0"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml"/>
    <xsl:template match="@*|node()">
    <xsl:copy>
    <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
    </xsl:template>
    <xsl:template match="Createelement_MT">
    <xsl:element name="statement">
    <xsl:element name="TableName">
    <xsl:element name="table">ABC</xsl:element>
    <xsl:element name="access">
    <xsl:for-each select="Field">
    <xsl:element name="{@Name}">
    <xsl:value-of select="Value"></xsl:value-of></xsl:element></xsl:for-each>
    </xsl:element>
    </xsl:element>
    </xsl:element>
    </xsl:template>
    </xsl:stylesheet>
    Error:
    Error: at xsl:element on line 15 of file:///......: XTDE0820: Invalid element name. Invalid QName {}
    Please help me with the xslt code for this requirement.
    Thanks!

    Hi,
                Please try this code
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
         <xsl:output method="xml"/>
         <xsl:template match="/">
              <Createelement_MT>
                   <Statement>
                        <TableName>
                             <table>XYZ</table>
                        <access>
                             <xsl:for-each select="Createelement_MT/Field">
                                  <xsl:variable name="field" select="@Name"></xsl:variable>
                                  <xsl:element name="{$field}">
                                  <xsl:value-of select="Value"></xsl:value-of>
                                  </xsl:element>
                             </xsl:for-each>
                        </access>
                        </TableName>
                   </Statement>
              </Createelement_MT>
         </xsl:template>
    </xsl:stylesheet>
    input xml
    <?xml version="1.0" encoding="UTF-8" ?>
    - <Createelement_MT>
    - <Field Name="A">
      <Value>1</Value>
      </Field>
    - <Field Name="B">
      <Value>1</Value>
      </Field>
      </Createelement_MT>
    output xml
    <?xml version="1.0" encoding="UTF-8" ?>
    - <Createelement_MT>
    - <Statement>
    - <TableName>
      <table>XYZ</table>
    - <access>
      <A>1</A>
      <B>1</B>
      </access>
      </TableName>
      </Statement>
      </Createelement_MT>
    One small request, if you think your question has been answered,could you please kindly, if possible, close this thread.
    regards
    Anupam

  • Field name is not know error when trying to add a filter

    Hello all!
    I need to add a filter dinamically to display a report. I'm using Crystal Reports 10 w/ RAS server.
    There is an sql statement in Database Fields > Command. It uses a join and a correlation name for table name: TT.START_TIME.
    I am getting a "Field name is not known" error:
    "This field name is not known. Details: errorKind Error in File C:\WINDOWS\TEMP\{D375AB61-F7AE-4BCC-AF5E-6702C0EFDE10}.rpt: Error in formula . '{Command.TT.START_TIME} in DateTime (2007, 08, 01, 09, 00, 00) to DateTime (2007, 08, 24, 04, 45, 00)' This field name is not known. Details: errorKind"
    I tried to specify the field the following ways:
    Command.START_TIME
    TT.START_TIME
    START_TIME
    TIME_TRACKER.START_TIME (time_tracker being the table name)
    MAIN.TIME_TRACKER.START_TIME (main being the schema)
    All of the above is giving the same field name not known error.
    I am adding the filter the following way:
            String whereClause = "{Command.TT.START_TIME} in DateTime (2007, 08, 01, 09, 00, 00) to DateTime (2007, 08, 24, 04, 45, 00)";
            IFilter filter = rptClientDoc.getDataDefinition().getRecordFilter();
            filter.setFreeEditingText(whereClause);
            rptClientDoc.getDataDefController().getRecordFilterController().modify(filter);
    I also tried the following where clause:
    String whereClause = "{Command.TT.START_TIME} > DateTime (2006, 08, 01, 09, 00, 00) AND {Command.TT.START_TIME} < DateTime (2007, 08, 24, 04, 45, 00)";
    still doing the same thing.
    If anyone could please help me w/ this I'd really appreciate it!
    Thank you!
    Anastasia

    The first formula was created using the selection formula expert. I only added the TT part after it didn't work giving the same message. The name the expert gives it after I click on the field is {Command.START_TIME}. Still gives the invalid field name error. -_- Could the rest of the forumula be causing the problem?
    In regards to parameterizing the SQL Command, I spoke w/ the gentleman who creates these reports in Crystal, he says it's not possible, because sometimes we don't want a where clause and sometimes we do.
    Is there a way to directly edit the SQL string itself which is in the Command through java?
    Thank you very much for taking time to respond.
    Anastasia

  • Batch reading request doesn't prefix field names by table name

    A batch reading request doesn't prefix field names by table name and I've got a AmbigiousException which is normal because there is the same fields in the 2 tables.
    The following code :
    //call a ReadAllQuery and return a list of AffaireImpl
    List<Affaire> listeAffaire =  affaireDao.getAffaireCorrespondantes(lccJrd, lnaAnnee, lnaOrdre, lcNataffCode, lnaNoSuite);
    for (Affaire affaire : listeAffaire) {
       //there is a one to Many mapping on Affaire to Dossier, with Transparent Indirection, Read-Ony and Batch Reading
       //this metod generate the wrong batch reading method
       List<Dossier> listeDossiers = affaire.getDossier();
    generates the following requests:
    ReadAllQuery(eu.curia.litige.model.AffaireImpl) --
    SELECT * FROM LA_AFF WHERE ( ((LCC_JRD = 'C') AND (LNA_ANNEE = 8)) AND (LNA_ORDRE = 8))
    ReadAllQuery(eu.curia.litige.model.DossierImpl) --
    SELECT t0.*
    FROM LA_DOSSIER t0, LA_AFF t1
    WHERE
    (((t0.LNA_NO_SUITE = t1.LNA_NO_SUITE) AND ((t0.LCC_JRD = t1.LCC_JRD) AND ((t0.LC_NATAFF_CODE = t1.LC_NATAFF_CODE) AND ((t0.LNA_ANNEE = t1.LNA_ANNEE) AND (t0.LNA_ORDRE = t1.LNA_ORDRE)))))
    AND UPPER(LCC_JRD) = 'C' AND UPPER(LNA_ORDRE) = '8' AND UPPER(LNA_ANNEE) = '8')+
    but the request should be :
    SELECT t0.*
    FROM LA_DOSSIER t0, LA_AFF t1
    WHERE
    (((t0.LNA_NO_SUITE = t1.LNA_NO_SUITE) AND ((t0.LCC_JRD = t1.LCC_JRD) AND ((t0.LC_NATAFF_CODE = t1.LC_NATAFF_CODE) AND ((t0.LNA_ANNEE = t1.LNA_ANNEE) AND (t0.LNA_ORDRE = t1.LNA_ORDRE)))))
    AND t1.LCC_JRD = 'C' AND t1.LNA_ORDRE = '8' AND t1.LNA_ANNEE = '8')+
    It's strange because this is the only place the batch reading doesn't prefix and uses a UPPER.
    For now we have disabled the batch reading, but it decreases the performanes (the list of affaire can be hudge).
    Any Idea?
    We use TopLink 10.1.3 on a Oracle 10g Database.
    Edited by: krampstudio on 2 déc. 2011 07:40
    Edited by: krampstudio on Dec 7, 2011 11:57 AM

    Here the mapping (I've also remove the tags of some of the direct mapping fields to simplify the reading)
         <opm:class-mapping-descriptor xsi:type="toplink:relational-class-mapping-descriptor">
             <opm:class>eu.curia.litige.model.AffaireImpl</opm:class>
             <opm:alias>Affaire</opm:alias>
             <opm:primary-key>
                <opm:field table="LA_AFF" name="LC_NATAFF_CODE" xsi:type="opm:column"/>
                <opm:field table="LA_AFF" name="LCC_JRD" xsi:type="opm:column"/>
                <opm:field table="LA_AFF" name="LNA_ANNEE" xsi:type="opm:column"/>
                <opm:field table="LA_AFF" name="LNA_NO_SUITE" xsi:type="opm:column"/>
                <opm:field table="LA_AFF" name="LNA_ORDRE" xsi:type="opm:column"/>
             </opm:primary-key>
             <opm:events xsi:type="toplink:event-policy"/>
             <opm:querying xsi:type="toplink:query-policy">
                <toplink:does-exist-query xsi:type="toplink:does-exist-query">
                   <toplink:existence-check>check-database</toplink:existence-check>
                </toplink:does-exist-query>
             </opm:querying>
             <opm:attribute-mappings>
                <opm:attribute-mapping xsi:type="toplink:one-to-many-mapping">
                   <opm:attribute-name>dossier</opm:attribute-name>
                   <opm:read-only>true</opm:read-only>
                   <opm:get-method>getDossier</opm:get-method>
                   <opm:set-method>setDossier</opm:set-method>
                   <opm:reference-class>eu.curia.litige.model.DossierImpl</opm:reference-class>
                   <opm:target-foreign-key>
                      <opm:field-reference>
                         <opm:source-field table="LA_DOSSIER" name="LCC_JRD" xsi:type="opm:column"/>
                         <opm:target-field table="LA_AFF" name="LCC_JRD" xsi:type="opm:column"/>
                      </opm:field-reference>
                      <opm:field-reference>
                         <opm:source-field table="LA_DOSSIER" name="LNA_ANNEE" xsi:type="opm:column"/>
                         <opm:target-field table="LA_AFF" name="LNA_ANNEE" xsi:type="opm:column"/>
                      </opm:field-reference>
                      <opm:field-reference>
                         <opm:source-field table="LA_DOSSIER" name="LNA_ORDRE" xsi:type="opm:column"/>
                         <opm:target-field table="LA_AFF" name="LNA_ORDRE" xsi:type="opm:column"/>
                      </opm:field-reference>
                      <opm:field-reference>
                         <opm:source-field table="LA_DOSSIER" name="LC_NATAFF_CODE" xsi:type="opm:column"/>
                         <opm:target-field table="LA_AFF" name="LC_NATAFF_CODE" xsi:type="opm:column"/>
                      </opm:field-reference>
                      <opm:field-reference>
                         <opm:source-field table="LA_DOSSIER" name="LNA_NO_SUITE" xsi:type="opm:column"/>
                         <opm:target-field table="LA_AFF" name="LNA_NO_SUITE" xsi:type="opm:column"/>
                      </opm:field-reference>
                   </opm:target-foreign-key>
                   <toplink:batch-reading>true</toplink:batch-reading>
                   <toplink:container xsi:type="toplink:list-container-policy">
                      <toplink:collection-type>oracle.toplink.indirection.IndirectList</toplink:collection-type>
                   </toplink:container>
                   <toplink:indirection xsi:type="toplink:transparent-collection-indirection-policy"/>
                   <toplink:selection-query xsi:type="toplink:read-all-query">
                      <toplink:container xsi:type="toplink:list-container-policy">
                         <toplink:collection-type>oracle.toplink.indirection.IndirectList</toplink:collection-type>
                      </toplink:container>
                   </toplink:selection-query>
                </opm:attribute-mapping>
                <opm:attribute-mapping xsi:type="toplink:direct-mapping">
                   <opm:attribute-name>lccJrd</opm:attribute-name>
                   <opm:field table="LA_AFF" name="LCC_JRD" xsi:type="opm:column"/>
                </opm:attribute-mapping>
                <opm:attribute-mapping xsi:type="toplink:direct-mapping">
                   <opm:attribute-name>lcNataffCode</opm:attribute-name>
                   <opm:field table="LA_AFF" name="LC_NATAFF_CODE" xsi:type="opm:column"/>
                </opm:attribute-mapping>
                <opm:attribute-mapping xsi:type="toplink:direct-mapping">
                   <opm:attribute-name>lnaAnnee</opm:attribute-name>
                   <opm:field table="LA_AFF" name="LNA_ANNEE" xsi:type="opm:column"/>
                </opm:attribute-mapping>
                <opm:attribute-mapping xsi:type="toplink:direct-mapping">
                   <opm:attribute-name>lnaNoSuite</opm:attribute-name>
                   <opm:field table="LA_AFF" name="LNA_NO_SUITE" xsi:type="opm:column"/>
                </opm:attribute-mapping>
                <opm:attribute-mapping xsi:type="toplink:direct-mapping">
                   <opm:attribute-name>lnaOrdre</opm:attribute-name>
                   <opm:field table="LA_AFF" name="LNA_ORDRE" xsi:type="opm:column"/>
                </opm:attribute-mapping>
             </opm:attribute-mappings>
             <toplink:descriptor-type>independent</toplink:descriptor-type>
             <toplink:caching>
                <toplink:cache-invalidation-policy xsi:type="toplink:time-to-live-cache-invalidation-policy">
                   <toplink:time-to-live>30000</toplink:time-to-live>
                </toplink:cache-invalidation-policy>
             </toplink:caching>
             <toplink:instantiation/>
             <toplink:copying xsi:type="toplink:instantiation-copy-policy"/>
             <toplink:change-policy xsi:type="toplink:deferred-detection-change-policy"/>
             <toplink:tables>
                <toplink:table name="LA_AFF"/>
             </toplink:tables>
          </opm:class-mapping-descriptor>

  • Alias a field name in a join query

    I have a database with spaces in the field names (not my fault).
    I am having a problem with the query because one of the fileds I am joining on has a space in its name. See bolded text.
    SELECT *
    FROM employee_passwords
    INNER JOIN employee_general_info
    ON employee_passwords.Employee_ID=employees.[Employee ID]
    WHERE username = '#username#' AND password = '#password#'  
    So I get this error message
    Error Executing Database Query.
    [Macromedia][SQLServer JDBC Driver][SQLServer]Invalid object name 'employees.Employee ID'.
    Is there a way to alias the employees.[Employee ID] field?

    Should be
    ON employee_passwords.Employee_ID=employee_general_info.[Employee ID]

  • Table Names & Field Names in FS for ABAP

    What is the easiest option to find out Table & Field Names normally asked by ABAP Consultant through Functional Specs?
    Any specific tips to find specific table names & field names?

    T000 Clients
    T001 Company Codes
    T001E Company code-dependent address data
    T001P Personnel Areas/Subareas
    T500L Personnel Country Grouping
    T500P Personnel Areas
    T500T Personnel Country Groupings
    T501 Employee Group
    T501T Employee Group Names
    T502T Marital Status Designators
    T503 Employee Groups / Subgroups
    T503K Employee subgroup
    T503T Employee Subgroup Names
    T504A Benefits - Default Values (NA)
    T504B Benefit Option Texts (North America)
    T504C Benefit Type (NA)
    T504D Benefit Credit Group Amount
    T504E Benefit Amount
    T504F Benefit Costs
    T508A Work Schedule Rules
    T508T Texts for Employee Subgroup Groupings for Work Schedules
    T510 Pay Scale Groups
    T510A Pay Scale Types
    T510F Assign Pay Scale > Time Unit, Currency
    T510G Pay Scale Areas
    T510H Payroll Constants with Regard to Time Unit
    T510I Standard Working Hours
    T510J Constant Valuations
    T510L Levels
    T510M Valuation of pay scale groups acc. to hiring date
    T510N Pay Scales for Annual Salaries (NA)
    T510S Time Wage Type Selection Rule
    T510U Pay Scale Groups
    T510Y Special Rules for Wage Type Generation
    T511 Wage Types
    T512R Cumulation Wage Types in Forms
    T512S Texts for Cumulation Wage Types in Forms
    T512T Wage Type Texts
    T512W Wage Type Valuation
    T512Z Permissibility of Wage Types per Infotype
    T513 Jobs
    T514S Table Name Texts
    T514T Field Name Texts
    T51D2 Wage Type Classes
    T51D3 Reduction Rules
    T51D4 Cumulation Rules
    T527X Organizational Units
    T528B Positions - Work Centers
    T528C Wage Type Catalog
    T528T Position Texts
    T529A Personnel Event
    T529F Fast Data Entry for Events
    T529T Personnel Event Texts
    T52BT Texts For HR Objects
    T52C0 Payroll Schemas
    T52C1 Payroll Schemas
    T52C2 Texts for Personnel Calculation Schemas
    T52C3 Texts for Personnel Calculation Schemas
    T52C5 Personnel Calculation Rules
    T52CC Schema Directory
    T52CD Schema Directory
    T52CE Directory of Personnel Calculation Rules
    T52CT Text Elements
    T52CX Cross References via Generated Schemas
    T52D1 Valid Processing Classes
    T52D2 Valid Values for Processing Classes
    T52D3 Valid Evaluation Classes
    T52D4 Permitted Values for Evaluation Classes
    T52D5 Wage Type Groups
    T52D6 Wage Type Group Texts
    T52D7 Assign Wage Types to Wage Type Groups
    T52D8 Valid Processing Classes - Texts
    T52D9 Valid Values for Processing Classes - Texts
    T530 Reasons for Events
    T530E Reasons for Changes
    T530F Reasons for Changes
    T530L Wage Types for Special Payments
    T530T Event Reason Texts
    T531 Deadline Types
    T531S Deadline Type Texts
    T533 Leave Types
    T533T Leave Type Texts
    T539A Default Wage Types for Basic Pay
    T539J Base Wage Type Valuation
    T539R Events for Standard Wage Maintenance
    T539S Wage Types for Standard Wage Maintenance
    T548 Date Types
    T548S Date Conversion
    T548T Date Types
    T548Y Date Types
    T549A Payroll Areas
    T549B Company Features
    T549C Decision Trees for Features (Customers)
    T549D Feature Directory
    T549L Date modifiers
    T549M Monthly Assignment: Payroll Period
    T549N Period Modifiers
    T549O Text for date modifier
    T549P Valid Time Units for Payroll Accounting
    T549Q Payroll Periods
    T549R Period Parameters
    T549S Payroll date types
    T549T Payroll Areas
    T549M Monthly Assignment: Payroll Period
    T549N Period Modifiers
    T549O Text for date modifier
    T549P Valid Time Units for Payroll Accounting
    T549Q Payroll Periods
    T549R Period Parameters
    T549S Payroll date types
    T549T Payroll Areas
    T554S Absence and Attendance Types
    T554T Absence and Attendance Texts
    T554V Defaults for Absence Types
    T554Y Time Constraints in HR TIME
    T555A Time Types
    T555B Time Type Designations
    T559A Working Weeks
    T559B Name of Working Week
    T572F Event Texts
    T572G Allowed Values for Events
    T572H Event Value Texts
    T582A Infotypes
    T582B Infotypes Which Are Created Automatically
    T582S Infotype Texts
    T582V Assignment of Infotypes to Views
    T582W Assigns Infotype View to Primary Infotype
    T582Z Control Table for PA Time Management
    T584A Checking Procedures - Infotype Assignment
    T588A Transaction Codes
    T588B Infotype Menus
    T588C Infotype Menus/Info Groups
    T588D Infogroups for Events
    T588J Screen Header Definition
    T588M Infotype Screen Control
    T588N Screen Modification for Account Assignment Block
    T588O Screen Modification for Assignment Data
    T588Q Screen types for fast entry
    T588R Selection Reports for Fast Data Entry
    T588S Screen Types for Fast Entry
    T588T Menu and Infogroup Designations
    T588V Business object type
    T588W Event types for infotype operations
    T588X Cust. composite definition of event types for IT operations
    T588Z Dynamic Events
    T591A Subtype Characteristics
    T591B Time Constraints for Wage Types
    T591S Subtype Texts
    T596F HR Subroutines
    T596G Cumulation wage types
    T596H _Cumulation wage type texts
    T596I Calculation rule for cumulation wage types
    T596U Conversion Table
    T599B Report Classes
    T599C Report Classes
    T599D Report Categories
    T599F Report Classes - Select Options
    T777A Building Addresses
    T777T Infotypes
    T777Z Infotype Time Constraints
    T778T Infotypes
    T778U Subtypes
    CATSCO Cross-Application Time Sheet (CATS)- Transfer to CO
    CATSDB CATS- Database Table for Time Sheet
    CATSHR Cross-Application Time Sheet (CATS)- Transfer to HR
    CATSMM Cross-Application Time Sheet (CATS)- Transfer to MM
    CATSPM Cross-Application Time Sheet (CATS)- Transfer to PM/CS
    CATSPS Cross-Application Time Sheet (CATS)- Transfer to PS

  • CFUPDATE problem with field name beginning with a number

    I have a form (actually several) that is gathering data for a survey. I tried to use cfupdate to update the data elements and got a string index out of range error. I tested again without the form fields that began with numbers and it worked just fine. I then tried to enclose the offending field names in () and []. Both times I got same error. Does anyone have a work around for this? The code and error are below.
    Changing the field names is not really an option. This survey has almost 400 data points and most of the fields begin with the question number.
    Thanks
    DW
    <cfupdate datasource="#application.fdp_datasource#" tablename="arra_survey1" dbtype="ODBC" formfields = "entry_no, 2_a_fy09, '2_a_fy10', '2_a_fy11', '2_a_fy12', '2_b_fy09', '2_b_fy10', '2_b_fy11', '2_b_fy12', '2_c_fy09', '2_c_fy10', '2_c_fy11', '2_c_fy12', '2_d_fy09', '2_d_fy10', '2_d_fy11', '2_d_fy12', '2_e_fy09', '2_e_fy10', '2_e_fy11', '2_e_fy12', '2_f_fy09', '2_f_fy10', '2_f_fy11', '2_f_fy12', '2_g_fy09', '2_g_fy10', '2_g_fy11', '2_g_fy12', '2_h_fy09', '2_h_fy10', '2_h_fy11', '2_h_fy12', '2_i_fy09', '2_i_fy10', '2_i_fy11', '2_i_fy12', '2_j_fy09', '2_j_fy10', '2_j_fy11', '2_j_fy12', '2_k_fy09', '2_k_fy10', '2_k_fy11', '2_k_fy12', '2_l_fy09', '2_l_fy10', '2_l_fy11', '2_l_fy12', central_office, dept_office, incl_other, 3_a_fy09, 3_a_fy10, 3_a_fy11, 3_a_fy12, 3_b_fy09, 3_b_fy10, 3_b_fy11, 3_b_fy12, 3_c_fy09, 3_c_fy10, 3_c_fy11, 3_c_fy12, 3_d_fy09, 3_d_fy10 3_d_fy11, 3_d_fy12, 3_e_fy09, 3_e_fy10, 3_e_fy11, 3_e_fy12, 3_f_fy09, 3_f_fy10, 3_f_fy11, 3_f_fy12, 3_g_fy09, 3_g_fy10, 3_g_fy11, 3_g_fy12, 3_h_fy09, 3_h_fy10, 3_h_fy11, 3_h_fy12, 3_i_fy09, 3_i_fy10, 3_i_fy11, 3_i_fy12, 3_j_fy09, 3_j_fy10, 3_j_fy11, 3_j_fy12, 3_k_fy09, 3_k_fy10, 3_k_fy11, 3_k_fy12, 3_l_fy09, 3_l_fy10, 3_l_fy11, 3_l_fy12">
    String index out of range: -2
    The error occurred in C:\Inetpub\wwwroot\directory\process_arra_suvey_2.cfm: line 12
    12 : <cfupdate datasource="#application.fdp_datasource#" tablename="arra_survey1" dbtype="ODBC" formfields = "entry_no, 2_a_fy09, '2_a_fy10', '2_a_fy11', ...

    I think you have run one of CFUPDATE's limitations.  I am not 100% certain, but I do not think cfupdate provides a way to escape invalid column names like yours.  In which case you may need to do a regular UPDATE within a  cfquery instead... or rename your columns.
    fields that began with numbers
    Most databases discourage creating column names that start with a number (or other restricted characters).  While many databases will allow you to escape invalid names, it is simpler all around to avoid them altogether.  Otherwise, you may have to escape the names in every single query. The recommendations vary, but usually object names that begin with a  letter, and contain only letters, numbers and underscores are considered  safe.
    This survey has almost 400 data points and most of the fields begin with the question number.
    Four-hundred (400) is a lot of columns for a single table.  The fact that they all them seem to contain the same type of information (ie response to a question) is an indication that data should probably be stored in a separate table, as rows, not columns.  For example questions could be stored in one table, possible answers in another, and the results of an individual test/survey stored in a third table.  A structure like that is much easier to query, can easily accommodate changes (add/remove questions, responses, etcetera) without having modify the table every time.

  • This field name is not known. for newly added fields

    dear sir,
    i ma using VS 2008 with CR.NET. There are previously dsigned reports. when I add some new Fields to the report, it prompts the error message
    [COMException (0x80041019): This field name is not known.
    Error in File C:\DOCUME1\TERESA1\ASPNET\LOCALS~1\Temp\PolicyReceipt {F0958318-C3D3-493D-9140-4CEA08B27B98}.rpt:
    Error in formula  <Address>.
    '{GetTransactionsForPolicyReceipt;1.ClientAddress_zh}+{GetTransactionsForPolicyReceipt;1.Address_zh_2}'
    This field name is not known.]
       CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext) +0
       CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext) +240
    here is the stored procedure
    select Transactions.TransactionID
                 , Transactions.PolicyDate
                 , Transactions.PolicyNumber
                 , ClientBranch.BranchName as ClientBranchName
                 , c.last_name + ', ' + c.other_name as ClientName
                 , c.last_name_zh + c.other_name_zh as ClientName_zh
                 , c.last_name as ClientLastName
                 , c.address as ClientAddress
                 , c.Address_2
                 , c.Address_3
                 , c.Address_4
                 , c.address_zh as ClientAddress_zh
                 , c.Address_zh_2
                 , c.Address_zh_3
                 , c.Address_zh_4
                 , c.email as ClientEmail
                 , c.[language]
                 , Gender.ShowName as ClientGenderName
                 , Gender.ShowName_zh as ClientGenderName_zh
                 , Institution.InstitutionName
                 , Product.ProductName
                 , FormulaType.FormulaTypeName
                 , Frequency.FrequencyName
                 , Frequency.FrequencyName_zh
                 , Frequency.FrequencyPeriod
                 , Frequency.IsLumpsum
                 , Currency.CurrencyName
                 , Currency.CurrencyName_zh
                 , Transactions.FrequencyPayment
                 , Transactions.Years
                 , Transactions.Terms
                 , Transactions.Remarks
    , c.Address_2
                 , c.Address_3
                 , c.Address_4
                 , c.Address_zh_2
                 , c.Address_zh_3
                 , c.Address_zh_4
    are newly added
    the other fields can be shown properly
    Edited by: tomckw on Oct 24, 2011 10:04 AM

    Only the RAS ( Report Application Server ) SDK includes API's to retrieve the version information. As you do not have full build of CR, you do not have the RAS SDK.
    Just as an FYI. The APIs are:
    CrystalDecisions.ReportAppServer.ClientDoc.ISCDReportClientDocument.MajorVersion
    CrystalDecisions.ReportAppServer.ClientDoc.ISCDReportClientDocument.MinorVersion
    A C# example code looks like this:
    MessageBox.Show("Report Version: " + (rptClientDoc.MajorVersion.ToString() + "." + rptClientDoc.MinorVersion.ToString()), "RAS", MessageBoxButtons.OK, MessageBoxIcon.Information);
    I htink your only way to tell is to take the 10.2 report, add it to your VS2008 project and save. On save, if it says something like;
    "this report was crated ina precious version of CR"
    you know it is not 10.5.
    But I do not think that is your problem here...
    - Ludek

Maybe you are looking for

  • Problem with iTunes in iPhone 4S

    Hello! I have iPhone 4s in iOS 6. When i go to iTunes via iPhone.. it appears this "1" in red cyrcle. And then I cand ged rid of this.. I tap to retry but still nothing.. I cant delete it also.. Any ideas?

  • Deleting Templates from Numbers

    Is it possible to edit or delete templates from My Template Chooser in Numbers?

  • An error occured in the claim providers configured from this site collection

    Hi Team I have farm Environment.I have Couple of Question 1)I have enabled web application from classic to claims mode.     Since than i have been getting error in sites in that Particular Webapplication.     I have configured CA,Webapplications Alte

  • HP C309g - Unable to view saved files

    Hi all, I tired to scan a document recently using my HP C309g all-in-one and I can scan the document, I can see the output using HP Scan but when I save a try to view the document all I get is a bunch of thick black lines separated by thin grey lines

  • HELP! I can't transfer my purchased music to my ipod

    After purchasing a new pc and transfering my songs over via an external hard drive, I can't transfer new music that I purchased to my ipod. I purchased the new music with the new pc and a recently loaded version of iTunes via the website. When I try