Question - are we not able to create indexed items in custom folders?

Just a question here. I would like to use the index/Value option for parameters in a workbook. This is where the List of Values drop down box for the parameter would show both the index number and the value and let you choose to select based on the index or on the value. An obvious example of this would be with months, where you would have January (1), February (2), March (3), and so forth. To do this, you have to set up indexed items in Discoverer Administrator.
That is where I am running into a problem/issue. I am not being able to pick an item and click to look at its properties, scroll down to the Indexed Item property, click on that property, and get a list of items to pick from. On the indexed item property I see a value of <None>, and when I click on that property, no list of items pops up.
I have defined indexed items before, but that was always done on regular folders (imported from the database). In this case, I am working with a custom folder.
The SQL that I have keyed in for this custom folder is this -
SELECT flex_value, description, flex_value_set_id, flex_value_id
FROM fnd_flex_values_vl
WHERE flex_value_set_id = 1011187
ORDER BY flex_value;
FND_FLEX_VALUES_VL is an Oracle view, that combines Oracle tables FND_FLEX_VALUES and FND_FLEX_VALUES_TL.
My goal would be to show both the FLEX_VALUE and the DESCRIPTION in the parameter to the users, so they can better decide what value(s) they want to pick. This is a general ledger application that I am working with, with the General Ledger account number segments and the Flexfield value set for each segment (we are using 7 segments to define our general ledger account number).
Am I not able to define indexed items when working with a custom folder? The documentation is not real clear. It talks about simple folders and complex folders, but does not mention custom folders, at least that I can find. Or perhaps I need to do something different with how I code the SQL for the custom folder to enable me to define indexed items in the custom folder?
Hope this makes some sense. Always a challenge to explain the situation in a clear manner. Thanks for any insight/assistance anyone can give me on this.
John Dickey

Ahh, those picky little details. Once I created an Item Class LOV on my item, then I could click on the Indexed Item property and get the list of fields in the folder to show up and pick my item (to be the indexed item) from that list. I went back to the user guides and the documentation sure does not indicate this requirement. For example, in the Discoverer Administrator guide, you have the section (page 9-30 in the version I have) titled "How to assign an indexed item to an item". Nowhere in that section does it say that you have to create an Item Class LOV first to be able to do this. Though it does show how if you do not have an LOV on the item you pick to be the indexed item, you will be prompted to create an LOV for that item. In the past I had my LOVs created first. This time I was trying to do the indexed item first before creating my LOVs. So lesson learned - you have to create an Item Class LOV first before you can assign an indexed item to an item.
Thanks for the assistance.
John Dickey

Similar Messages

  • Not able to create index for organization

    in transaction ses_admin, i created an index for business object BAS_BUPA of type 1,ie individual account.
    However, i am not able to create index for BAS_BUPA of type 2
    It says "No entry in table SIC_INDEX_MAIN for index object BAS_BUPA and index 2"

    hi,
    The index is for Business Partner, so it includes both Persons and Organizations. So, only one index needs to be created for both.
    The functioning is correct, just that i missed it.

  • Not able to create new item

    Hi ,
    I am trying to create a new item at the master level and getting the following message :
    You are only authorized to access company 'ABC1000' .
    Value secured: You Are Only Authorised To Access Company 'ABC1000' .
    I am not able to change the accounts to ABC1000 in the cost of goods sold accounts and other accounts in the item creation screen.
    Is there any profile options that I am missing?
    Regards,

    Just keep in mind there might be other security rules that you may have to change as well.
    Sandeep Gandhi

  • Safari Bookmarks are disabled (not able to create a bookmark)

    When I go to create or save a bookmark, nothing at all happens. This started out of no where. I tried clearing the history option, and the problem is still at large.

    Go to the home folder/ home ~Library/ Safari folder/ Bookmarks. plist "Get
    info" : Ownership & permissions are they Read and Write
    If not go ahead and put it on read & write. if you can not change it or it
    changes back you should run perm. repair.
    Eme~;~

  • Not able to create a java class included in custom jar from script

    Hi,
    We need to call a third-party web service from within SAP Sourcing and so we have created and deployed a custom JAR. However I am not able to create any of the custom classes included in this object. I have created a simple JAR file having just a "Hello World" message and got our BASIS team to deploy this (they deployed using the steps mentioned in Installation Guide Section 4.2.4 - we are using Sourcing Wave 9). I have added the required import statement in my test script and included this line:
    HelloWorld test = new HelloWorld();
    When this script executes, it gives the error:
    Class:HelloWorld not found in namespace.
    Can you please give your suggestions on how to fix this error?
    Thanks,
    Gayathri

    The issue was fixed after including the custom jar in esourcing90/lib folder and redeploying

  • We are not able to create CUP Requests

    HI all
    I am also gettting same error like this..We created CUP Requests one hour before ..But we are not able to create CUP Requests now.. I got below error message in system log.
    Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://c700u121.com:50000/SAPGRC_CCRiskAnalysis_V01/Config1?wsdl&style=document"
    2012-03-08 13:05:25,558 [SAPEngine_Application_Threadimpl:3]_23 ERROR com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested exception is:
    com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://c700u121.com:50000/SAPGRC_CCRiskAnalysis_V01/Config1?wsdl&style=document"
    com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested exception is:
    com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://c700u121.com:50000/SAPGRC_CCRiskAnalysis_V01/Config1?wsdl&style=document"
    at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
    at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:4087)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:408)
    at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:381)

    Hello Naga!!
    Has your problem been solved??? Error Creating Request - Risk Analysis in CUP
    If yes, I'd be nice if you close this thread and document your solution
    If not, please let us know.
    Be aware that the user should set the Security Policy to "technical user" to avoid problems with password expiration as per note 1296696.
    Cheers!!
    Diego.

  • Users are not able to create POs from PRs having Production Order (F)

    Hi Gurus
    Users are not able to create POs from PRs having Production Order (F) as creation indicator.
    Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type F.
    Would you please investigate and advise what OSS notes are required to be able to use item category L (subcontracting) on a PO for a requisition generated from a network activity via Procurement Type = "Preliminary requisition for WBS element".
    Thanks,
    Sada.

    Hi Ajay & Andra
    Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type  Production order (F).
    Our Business requirement as shown below.
    1).The problem - we currently have no way to "direct requisition" an item to be procured via      subcontracting - only itu2019s possible via MRP.
    2).These behaviors are inconsistent as the requisition process should not impact the procurement process.  Can we find a way to influence the creation indicator on the requisition so that it does not appear as a production order?
    Please suggest any alternate method for achieving this.
    Thanks & Regards
    Sada

  • Not able to create new e-mail on N8 using Mail for...

    Not able to create new e-mail on N8 using Mail for Exchange.
    Currently using google for my domain, but settings are the same as explained on the google Sync webpage: http://www.google.com/support/mobile/bin/answer.py?hl=en&answer=147951
    When creating reply on mail the application crashes.  When creating new mail it says "Kan bewerking niet uitvoeren" in english: "Unable to execute action".
    Any idea why creating mail is not possible?
    Regards,
    Joris

    problem is known
    more info there:
    /t5/Nseries-and-S60-Smartphones/N8-syncing-with-Google-contacts-amp-calendar/td-p/772020
    there is little workaround aslo.

  • Not able to create sales order  using BAPI - BAPI_SALESORDER_CREATEFROMDAT2

    Hi Experts,
    I am not able to create sales order . I am using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
    to create sales order .I am passing external sales order number to the parameter
    SALESDOCUMENTIN.
    I am getting following error.
    "524   |Only quantity 1 EA is allowed (Item 00001"
    Here EA is UOM(Unit of measurement).
    Below is the sample program through which i am trying to create the sales order.
    *& Report  ZSDC_SALES_TEST
    report  zsdc_sales_test.
    *DATA: wa_bapi_header    TYPE bapisdhd1.
    Include Name    - ZSDC_SALES_ORD_UPLOAD_TOP
    Program Name    - ZSDC_SALES_ORD_UPLOAD_1393
    Program Title   - Include for Data Declaration  and selection screen
    Created by      - Lalitha W
    Created on      - 18-Nov-2008
    Object ID       - SD_C_1393_SALES_ORDER_UPLOAD
    Request Id      - SD3K905579
    Description - This is a common INCLUDE for data declarations and
    *selection screen details.
                            HISTORY
    Date    |Developer |Req by    | Description              |Reference ID
            |          |          |                          |
            |          |          |                          |
                               TYPE-POOLS
    *TYPE-POOLS: truxs, abap, slis.
                              TABLES
    *TABLES: t100.
                               TYPES
    types:begin of   ty_header,
            auart(4)    type c,    " Sales Order Type
            vkorg(4)    type c,    " Sales Organization
            vtweg(2)    type c,    " Distrubution Channel
            spart(2)    type c,    " Division
            kunnr_1(10) type c,    " Sold to Party
            kunnr_2(10) type c,    " Ship to Party
            augru(3)    type c,    " Order Reason
            bstkd(35)   type c,    " PO Number
            bstdk(10)   type c,    " PO Date
            ketdat(10)  type c,    " Required Delivery Date
            zterm(4)    type c,    " Payment Terms
            inco1(3)    type c,    " Inco Terms -1
            inco2(28)   type c,    " Inco Terms -2
            prsdt(10)   type c,    " pricing date
            waerk(5)    type c,    " Document Currency
            vkbur(4)    type c,    " Sales Office
            vkgrp(3)    type c,    " Sales group
            pltyp(2)    type c,    " Price List type
            kdgrp(2)    type c,    " Customer Group
            bstkd_e(35) type c,    " Ship-to-party PO number
            submi(10)   type c,    " Collective Number
            bname(35)   type c,    " Name
            ihrez(12)   type c,    " Your Reference
            kschl_1(4)   type c,    " Condition Type
            kbetr_1(11)  type c,    " Amount
            kschl_2(4)   type c,    " Condition Type
            kbetr_2(11)  type c,    " Amount
            kschl_3(4)   type c,    " Condition Type
            kbetr_3(11)  type c,    " Amount
           partner_1(25) TYPE c,    "  Partner(Bill To Party Number)
           partner_2(25) TYPE c,    "  Partner(Payer Number)
           partner_3(25) TYPE c,    "  Partner(Sales Responsible Number)
           partner_4(25) TYPE c,    "  Partner(Order admin)
           partner_5(25) TYPE c,    "  Partner(Contact person)
            partner_1(10) type c,    "  Partner(Bill To Party Number)
            partner_2(10) type c,    "  Partner(Payer Number)
            partner_3(10) type c,    "  Partner(Sales Responsible Number)
            partner_4(10) type c,    "  Partner(Order admin)
            partner_5(10) type c,    "  Partner(Contact person)
            tdspras_1(2)  type c,
            text_1(500)   type c,    " Text Before Items Z012
            tdspras_2(2)  type c,
            text_2(500)   type c,    " Invocie Up Z034
            tdspras_3(2)  type c,
            text_3(500)   type c,    " Invocie Down Z035
            tdspras_4(2)  type c,
            text_4(500)   type c,    " Customer Reference Continue Z018
            tdspras_5(2)  type c,
            text_5(500)   type c,    " Dispatch Marks/ Order Z019
            tdspras_6(2)  type c,
            text_6(500)   type c,    " Ordered By  Z003
            tdspras_7(2)  type c,
            text_7(500)   type c,    " Sales Parameters Z002
            kvgr1(3)      type c,    " Industry
            kvgr2(3)      type c,    " customer BU
    end of ty_header.
    types: begin of ty_item,
              bstkd(35)     type c,    " PO Number
              bstdk(10)     type c,    " PO Date
              bstkd_e(35)   type c,    " Ship-to-party PO number
              posnr(6)      type c,    " POSTION NUMBER
              matnr(18)     type c,    " Material Number
              kwmeng(18)    type c,    " Order Quantity
              pstyv(4)      type c,    " Sales doc. item categ
              kursk(18)     type c,    " EXCHANGE RATE****
              ffprf(8)      type c,    " DIP PROFILE
              werks(4)      type c,    " Delivering Plant
              vstel(4)      type c,    " SHIPPING POINT
              lgort(4)      type c,    " STORAGE LOCATION
              route(6)      type c,    " Route
              kurrf(18)     type c,    " EXCHANGE RATE-FI
              ntgew(18)     type c,    " Net Weight
              brgew(18)     type c,    " Gross Weight
              gewei(3)      type c,    " Weight Unit
              prctr(10)     type c,    " profit center
              abgrs(6)      type c,    " RESULT ANALYSIS KEY
              kalsm_k(4)    type c,    " COSTING SHEET
              kschl_1(4)    type c,    " Condition Type
              kbetr_1(11)   type c,    " Amount
              kschl_2(4)    type c,    " Condition Type
              kbetr_2(11)   type c,    " Amount
              kschl_3(4)    type c,    " Condition Type
              kbetr_3(11)   type c,    " Amount
              text_1(500)    type c,    " material Text 0001
              tdspras_1(1)   type c,
              text_2(500)    type c,    " Pr Text 9001
              tdspras_2(1)   type c,
           end of ty_item.
    types:  begin of ty_schedule_line,
             bstkd(35)       type c, "PO number
             bstdk(10)       type c, "PO date
             bstkd_e(35)     type c, "Ship-to-party PO number
             posnr(6)        type c, "sales doc.Item
             etdat(10)       type c, "Schedule line date
             wmeng(2)        type c, "Order Quantity
            end of ty_schedule_line.
    types: begin of ty_err  ,
            auart(4)    type c,    " Sales Order Type
            vkorg(4)    type c,    " Sales Organization
            vtweg(2)    type c,    " Distrubution Channel
            spart(2)    type c,    " Division
            kunnr_1(10) type c,    " Sold to Party
            kunnr_2(10) type c,    " Ship to Party
            augru(3)    type c,    " Order Reason
            bstkd(35)   type c,    " PO Number
            bstdk(10)   type c,    " PO Date
            ketdat(10)  type c,    " Required Delivery Date
            zterm(4)    type c,    " Payment Terms
            inco1(3)    type c,    " Inco Terms -1
            inco2(28)   type c,    " Inco Terms -2
            prsdt(10)   type c,    " pricing date
            waerk(5)    type c,    " Document Currency
            vkbur(2)    type c,    " Sales Office
            vkgrp(3)    type c,    " Sales group
            pltyp(2)    type c,    " Price List type
            kdgrp(2)    type c,    " Customer Group
            bstkd_e(35) type c,    " Ship-to-party PO number
            submi(10)   type c,    " Collective Number
            bname(35)   type c,    " Name
            ihrez(12)   type c,    " Your Reference
            kschl_1(4)   type c,    " Condition Type
            kbetr_1(11)  type c,    " Amount
            kschl_2(4)   type c,    " Condition Type
            kbetr_2(11)  type c,    " Amount
            kschl_3(4)   type c,    " Condition Type
            kbetr_3(11)  type c,    " Amount
            partner_1(25) type c,    "  Partner(Bill To Party Number)
            partner_2(25) type c,    "  Partner(Payer Number)
            partner_3(25) type c,    "  Partner(Sales Responsible Number)
            partner_4(25) type c,    "  Partner(Order admin)
            partner_5(25) type c,    "  Partner(Contact person)
            tdspras_1(2)  type c,
            text_1(500)   type c,    " Text Before Items Z012
            tdspras_2(2)  type c,
            text_2(500)   type c,    " Invocie Up Z034
            tdspras_3(2)  type c,
            text_3(500)   type c,    " Invocie Down Z035
            tdspras_4(2)  type c,
            text_4(500)   type c,    " Customer Reference Continue Z018
            tdspras_5(2)  type c,
            text_5(500)   type c,    " Dispatch Marks/ Order Z019
            tdspras_6(2)  type c,
            text_6(500)   type c,    " Ordered By  Z003
            tdspras_7(2)  type c,
            text_7(500)   type c,    " Sales Parameters Z002
            kvgr1(3)      type c,    " Industry
            kvgr2(3)      type c,    " customer BU
            message(600) type c,
      end of ty_err.
    types: begin of ty_t685a,
            kschl type kschl,
            krech type krech,
          end of ty_t685a.
                       INTERNAL TABLES
    ***header
    data:  g_krech_1(4)    type c,    " Calculation type for condition
           g_krech_2(4)    type c,    " Calculation type for condition
           g_krech_3(4)    type c.    " Calculation type for condition
          g_krech_4(4)    TYPE c,    " Calculation type for condition
          g_krech_5(4)    TYPE c,    " Calculation type for condition
          g_krech_6(4)    TYPE c,    " Calculation type for condition
          g_krech_7(4)    TYPE c,    " Calculation type for condition
          g_krech_8(4)    TYPE c,    " Calculation type for condition
          g_krech_9(4)    TYPE c,    " Calculation type for condition
          g_krech_10(4)   TYPE c,    " Calculation type for condition
          g_krech_11(4)   TYPE c,    " Calculation type for condition
          g_krech_12(4)   TYPE c,    " Calculation type for condition
          g_krech_13(4)   TYPE c,    " Calculation type for condition
          g_krech_14(4)   TYPE c,    " Calculation type for condition
          g_krech_15(4)   TYPE c,    " Calculation type for condition
          g_krech_16(4)   TYPE c,    " Calculation type for condition
          g_krech_17(4)   TYPE c,    " Calculation type for condition
          g_krech_18(4)   TYPE c,    " Calculation type for condition
          g_krech_19(4)   TYPE c,    " Calculation type for condition
          g_krech_20(4)   TYPE c.    " Calculation type for condition
    Items
    data:   g_krech_item_1(4)   type c,    " Calculation type for condition
            g_krech_item_2(4)   type c,    " Calculation type for condition
            g_krech_item_3(4)   type c.    " Calculation type for condition
           g_krech_item_4(4)   TYPE c,    " Calculation type for condition
           g_krech_item_5(4)   TYPE c,    " Calculation type for condition
           g_krech_item_6(4)   TYPE c,    " Calculation type for condition
           g_krech_item_7(4)   TYPE c,    " Calculation type for condition
           g_krech_item_8(4)   TYPE c,    " Calculation type for condition
           g_krech_item_9(4)   TYPE c,    " Calculation type for condition
           g_krech_item_10(4)  TYPE c,    " Calculation type for condition
           g_krech_item_11(4)  TYPE c,    " Calculation type for condition
           g_krech_item_12(4)  TYPE c,    " Calculation type for condition
           g_krech_item_13(4)  TYPE c,    " Calculation type for condition
           g_krech_item_14(4)  TYPE c,    " Calculation type for condition
           g_krech_item_15(4)  TYPE c,    " Calculation type for condition
           g_krech_item_16(4)  TYPE c.    " Calculation type for condition
    data: it_t685a  type standard table of ty_t685a.
    data: wa_bapi_header    type bapisdhd1,
         wa_bapi_headerx   TYPE bapisdhd1x,
          it_bapi_item      type table of bapisditm,
         it_bapi_itemx     TYPE TABLE OF bapisditmx,
          it_bapi_cond      type table of bapicond,
         it_bapi_condx     TYPE TABLE OF bapicondx,
          it_bapi_partner   type table of bapiparnr,
          it_bapi_shdl      type table of bapischdl,
         it_bapi_shdlx     TYPE TABLE OF bapischdlx,
         it_bapi_order_text type TABLE OF BAPISDTEXT,
          it_bapireturn     type table of bapiret2.
    data:  wa_bapi_item       like line of it_bapi_item,
          wa_bapi_itemx      LIKE LINE OF it_bapi_itemx,
           wa_bapi_cond       like line of it_bapi_cond,
          wa_bapi_condx      LIKE LINE OF it_bapi_condx,
           wa_bapi_partner    like line of it_bapi_partner,
           wa_bapi_shdl       like line of it_bapi_shdl,
          wa_bapi_shdlx      LIKE LINE OF it_bapi_shdlx,
          wa_bapi_order_text like LINE OF it_bapi_order_text,
           wa_bapireturn      like line of it_bapireturn.
    *DATA: zmode(1) VALUE 'N'.
    data: it_header      type standard table of ty_header.
    *DATA: it_temp_header TYPE STANDARD TABLE OF ty_header.
    data: it_item        type standard table of ty_item.
    *DATA: it_temp_item   TYPE STANDARD TABLE OF ty_item.
    data: it_err         type standard table of ty_err.
    data: it_fline1 type standard table of tline,
          wa_fline1 type tline.
    data: it_thead1 type thead.
    data: it_fline2 type standard table of tline,
          wa_fline2 type tline.
    data: it_thead2 type thead.
    data: it_fline3 type standard table of tline,
          wa_fline3 type tline.
    data: it_thead3 type thead.
    data: it_fline4 type standard table of tline,
          wa_fline4 type tline.
    data: it_thead4 type thead.
    data: it_fline5 type standard table of tline,
          wa_fline5 type tline.
    data: it_thead5 type thead.
    data: wa_header         like line of it_header,
          wa_item           like line of it_item,
          wa_err            type ty_err,
         wa_bill           LIKE LINE OF it_bill,
         wa_bill1          LIKE LINE OF it_bill,
          wa_iterr          like line of it_err,
          wa_t685a          like line of it_t685a.
         wa_bill_item TYPE ty_bill_item.
    data: it_schedule_line  type standard table of ty_schedule_line,
          wa_schedule_line type ty_schedule_line.
    data: sales_order_no     type bapivbeln-vbeln.
    data: ext_sales_order_no type bapivbeln-vbeln.
    Variable to be used to separate the fields which are concatenated by a
    runtime character
    *DATA: g_tabchar(1) TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
    *DATA: wa_truxs_t_text_data TYPE truxs_t_text_data.
    *DATA: g_filename      TYPE string,
         g_path          TYPE string,
         g_fullpath      TYPE string,
         g_user_action   TYPE i,
         g_file_encoding TYPE abap_encoding.
    *DATA : g_text(8192),
    data : g_mstring1(100) type c,
          g_mstring2(100) type c,
          g_mstring3(100) type c,
          g_mstring4(100) type c,
          g_mstring5(100) type c.
    data: g_count1 type ebelp,
          g_str_count1(6) type c.
    data: g_count type ebelp,
          g_str_count(6) type c.
    *DATA: f_subrc      LIKE sy-subrc,
         f_subrc1     LIKE sy-subrc,
         f_error(500) TYPE c,
         item1(27)    TYPE c,
         item2(27)    TYPE c,
         item3(27)    TYPE c,
         item4(27)    TYPE c,
         i            TYPE ekpo-ebelp.
    *DATA: g_billplan_header TYPE c,
         g_billplan_item TYPE c.
    data : g_external_so type vbak-vbeln. "SO
                          SELECTION-SCREEN
    selection-screen begin of block frame1 with frame title text-001 .
    parameters:p_file1 type rlgrap-filename, "OBLIGATORY, "Header data.
               p_file2 type rlgrap-filename, "OBLIGATORY, "Item Data.
               p_file3 type rlgrap-filename,            "Schedule line.
               p_file4 type rlgrap-filename ."OBLIGATORY. "Error file.
    selection-screen end of block frame1.
    start-of-selection.
      wa_bapi_header-doc_type     =  'Z0MX'. "order type
      wa_bapi_header-sales_org    =  '0130'."sales org
      wa_bapi_header-distr_chan   =  '13'.  "distr channel
      wa_bapi_header-division     =  '13'.  "division
    Old code from copied program
    wa_bapi_header-purch_no_s   =  wa_header-kunnr_2.  " Ship to party
    New code as required in Finland project
    We are using to Header ->Order Tab -> Ship to Party -> Purchase order no (BSTKD_E) to store Old legacy SO number
      wa_bapi_header-purch_no_s   =  'MX100443'.  "External SO i.e Old legacey SO number
      wa_bapi_header-ref_1_s      = '0000666666'. "Sold to party
    wa_bapi_header-ord_reason   =  wa_header-augru.
      wa_bapi_header-purch_no_c   =  'ddr1234'.    " PO number
      wa_bapi_header-purch_date   =  sy-datum.    " PO date
      wa_bapi_header-req_date_h   =  sy-datum.   " Required Delivery Date
      wa_bapi_header-pmnttrms     =  '01'.    " Payment Terms
    wa_bapi_header-incoterms1   =  wa_header-inco1.
    wa_bapi_header-incoterms2   =  wa_header-inco2.
    wa_bapi_header-price_date   =  wa_header-prsdt.    " Pricing date
    wa_bapi_header-currency     =  wa_header-waerk.    " Document Currency
    wa_bapi_header-sales_grp  =  wa_header-vkgrp. " Sales group
    wa_bapi_header-price_list   =  wa_header-pltyp. " Price list type
    wa_bapi_header-cust_group   =  wa_header-kdgrp.   " Cust Group
    wa_bapi_header-ship_type    =  wa_header-vsart.   " Shipping Type
    wa_bapi_header-purch_no_s   =  wa_header-bstkd_e. " Ship-to-party po number
    wa_bapi_header-collect_no   =  wa_header-submi.   " Collective No.
    wa_bapi_header-name         =  wa_header-bname.   " Name
    wa_bapi_header-ref_1        =  wa_header-ihrez.   " Your Reference
    wa_bapi_header-cust_grp1    =  wa_header-kvgr1.   " Industry
    wa_bapi_header-cust_grp2    =  wa_header-kvgr2.   " Customer BU
    *ENDFORM.                    " f_header
    IF wa_header-partner_1 IS NOT INITIAL.
        wa_bapi_partner-partn_role = 'AG'.
        wa_bapi_partner-partn_numb = '0000666666'.
        wa_bapi_partner-itm_number = '000000'.
        append wa_bapi_partner to it_bapi_partner.
        clear wa_bapi_partner.
    ENDIF.
      call function 'CONVERSION_EXIT_ALPHA_INPUT'
        exporting
          input  = wa_header-partner_2
        importing
          output = wa_header-partner_2.
    IF wa_header-partner_2 IS NOT INITIAL.
        wa_bapi_partner-partn_role = 'WE'.
        wa_bapi_partner-partn_numb = '0000666666'.
        wa_bapi_partner-itm_number = '000000'.
        append wa_bapi_partner to it_bapi_partner.
        clear wa_bapi_partner.
    ENDIF.
      perform f_item.
    data : order_items_inx type table of bapisditmx with header line.
      order_items_inx-material          = 'X'.  "
      order_items_inx-target_qty        = 'X'.  "
      order_items_inx-comp_quant        = 'X'.  "
      order_items_inx-trgqty_den        = 'X'.
      order_items_inx-rnddlv_qty        = 'X'.
    order_items_inx-updateflag = 'I'.
    order_items_inx-target_qu = 'X'.
      order_items_inx-plant             = 'X'.  "
      append order_items_inx.
      call function 'BAPI_SALESORDER_CREATEFROMDAT2'
        exporting
          salesdocumentin = 'MX11111152'
      order_header_in      = wa_bapi_header
             order_header_inx     = wa_bapi_headerx
      importing
      salesdocument        = sales_order_no
      tables
      return               = it_bapireturn
      order_items_in       = it_bapi_item
      order_items_inx      =  order_items_inx
      order_partners       = it_bapi_partner
       order_conditions_in  = it_bapi_cond.
      if sy-subrc is initial.
      commit work.
      endif.
    *&      Form  f_item
          text
    form f_item .
      call function 'CONVERSION_EXIT_ALPHA_INPUT'
        exporting
          input  = wa_item-posnr
        importing
          output = wa_item-posnr.
      wa_item-posnr = '000010'.
    IF sy-subrc EQ 0. "IS INITIAL.
      move wa_item-posnr to g_str_count."commented out by shakti
    ENDIF.
      wa_bapi_item-itm_number        =  wa_item-posnr.  " Line item
    WA_BAPI_ITEM-PO_ITM_NO         =  WA_ITEM-EBELP.
    wa_bapi_item-division          = wa_item-spart.
      wa_bapi_item-purch_no_c        = 'ddr1234'.   " po number
      wa_bapi_item-purch_date        = sy-datum.   " po date
      wa_bapi_item-purch_no_s        = 'MX11111112'. " Ship-to-party po number
      wa_item-matnr = 'MAXIMO_SERVICE'.
      call function 'CONVERSION_EXIT_MATN1_INPUT'
        exporting
          input        = wa_item-matnr
        importing
          output       = wa_item-matnr
        exceptions
          length_error = 1
          others       = 2.
      if sy-subrc is initial.
        wa_bapi_item-material        = wa_item-matnr.  "material
      endif.
      wa_bapi_item-target_qty        = '1'. " Order qty
      wa_bapi_item-comp_quant = '1'.
      wa_bapi_item-target_qu = 'EA'.
        wa_bapi_item-fixed_quan = '1'.
    wa_bapi_item-comp_quant        = wa_item-kwmeng.
    wa_bapi_item-trgqty_den        = '1'.
    wa_bapi_item-rnddlv_qty        = wa_item-kwmeng.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
       EXPORTING
         input  = wa_item-ps_psp_pnr
       IMPORTING
         output = wa_item-ps_psp_pnr.
    IF sy-subrc = 0.
       wa_bapi_item-wbs_elem          = wa_item-ps_psp_pnr.
    ENDIF.
      wa_bapi_item-item_categ        = 'ZMAX'.
    wa_bapi_item-ex_rate_fi        = wa_item-kurrf.
    wa_bapi_item-dli_profil        = wa_item-ffprf.   " Dynamic item processor profile
    wa_bapi_item-route             = wa_item-route.   " route
    wa_bapi_item-exchg_rate        = wa_item-kursk.
      wa_bapi_item-plant             = '2090'.   " Plant
      wa_bapi_item-ship_point        = 'FN11'.   " Shipping point
    wa_bapi_item-store_loc         = wa_item-lgort.   " stg loc
    REPLACE ALL OCCURRENCES OF  ',' IN wa_item-ntgew WITH '.'.
    REPLACE ALL OCCURRENCES OF  ',' IN wa_item-brgew WITH '.'.
    wa_bapi_item-net_weight        = wa_item-ntgew.  "
    wa_bapi_item-gross_wght        = wa_item-brgew.  "
      call function 'CONVERSION_EXIT_CUNIT_INPUT'
        exporting
          input    = wa_item-gewei
          language = sy-langu
        importing
          output   = wa_item-gewei.
       EXCEPTIONS
         unit_not_found = 1
         OTHERS         = 2.
    IF sy-subrc <> 0.
    ENDIF.
      wa_bapi_item-untof_wght        =  'KG'.  " weight unit
      replace all occurrences of  ',' in wa_item-kursk with '.'.
      replace all occurrences of  ',' in wa_item-kurrf with '.'.
    wa_bapi_item-profit_ctr        = wa_item-prctr.   " Profit center
    wa_bapi_item-resanalkey        = wa_item-abgrs.   " RESULT ANALYSIS KEY
    wa_bapi_item-cstg_sheet        = wa_item-kalsm_k. " COSTING SHEET
      append wa_bapi_item to it_bapi_item.
    endform.                    " f_item
    Thanks & regards,
    Chetan

    see the following to create sales order:-
    *& Report  ZSALESORDER
    *&DEVELOPED BY JANI KRUPA 4.10.2008
    REPORT  ZSALESORDER.
    Parameters
    Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d .
    SELECTION-SCREEN END OF LINE.
    Complete Deliver
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
    PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    v_text10 = 'Complete delivery'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    *Complete delivery
        header-COMPL_DLV = p_autlf.
        header-COMPL_DLV = 'X'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
    item category
      itemx-ITEM_CATEG = 'X'.
      APPEND item.
      APPEND itemx.
      ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000020'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000020'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000020'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.

  • I've just updated my iphone to the version 5.0 (9A334), I'm not able to create a new event in the calender, it shows "no calender"

    I've just updated my iphone to the version 5.0 (9A334), I'm not able to create a new event in the calender, it shows "no calender"

    Here you are "the strange draft logos"...

  • Not able to create EAR file for WAR file extracted project

    Hi Experts,
    I am trying to import a WAR file, make changes to the project and create an EAR file for the same. I am not able to remove import
    errors despite of adding required jar files to it.
    Also, I am not able to create an EAR file for the same.
    I have copied the steps here with screen shots. Below are the steps :
    Import WAR file in NWDS 7.3 – Enterprise Portal perspective
    Select WAR file to create WAR and EAR project for it.
      Project created with import errors.     e.g – com.sapportals.portal.prt*
    Found jar file from Class – target jar file table. 
    e.g – for Class com.sapportals.portal.prt.resource.IResource needed jar file is tc~epbc~prt~api.jar
    Copied required jar files in WEB-INF -> lib folder.
    Configure Build path and Add External jars.
    Portalapp file screen shot
    I think errors should go now, but they still exist.
    Next I right click on WAR project and tried updating related EAR project.
      Next, Export EAR file from EAR project.
       I have tried both EAR types.
    But EAR file is not created.
    Please help me in removing the errors.
    Thanks in advance :-)
    Anubha Pandey

    Hi Anubha,
    I feel that you're missing JAR dependencies and hence not able to resolve the above import errors.
    Please go through the below thread for the AFP Masthead customization and follow the same:
    How to download and change AFP Masthead on SAP Portal 7.3
    Hope, this will help!!!
    BR,
    Anurag

  • Not able to create interactive pdf

    Hello everyone,
    I'm not able to create an offline pdf using exclusively ABAP. I tried using the tutorial "Offline Interactive Forms Using ABAP" but i'm missing something. I allready created the form using transaction SFP, and my ABAP program is like this:
    REPORT ztest_interactive_forms.
    DATA: wa_lfa1 LIKE lfa1.
    DATA: fm_name TYPE funcname.
    DATA: fp_outputparams TYPE sfpoutputparams.
    DATA: fp_docparams TYPE sfpdocparams.
    DATA: fp_formoutput TYPE fpformoutput.
    PARAMETERS: p_lifnr LIKE lfa1-lifnr.
    START-OF-SELECTION.
    SELECT SINGLE lifnr name1 name2 ort01 FROM lfa1 INTO CORRESPONDING FIELDS OF wa_lfa1 WHERE lifnr = p_lifnr.
    first get name of the generated function module
    CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
    EXPORTING
    i_name = 'ZTEST_NCS'
    IMPORTING
    e_funcname = fm_name.
    Set output parameters and open spool job
    fp_outputparams-nodialog = 'X'. " suppress printer dialog popup
    fp_outputparams-getpdf = 'X'. " launch print preview
    CALL FUNCTION 'FP_JOB_OPEN'
    CHANGING
    ie_outputparams = fp_outputparams
    EXCEPTIONS
    cancel = 1
    usage_error = 2
    system_error = 3
    internal_error = 4
    OTHERS = 5.
    Set form language and country (->form locale)
    fp_docparams-langu = 'E'.
    fp_docparams-country = 'US'.
    fp_docparams-fillable = 'X'.
    Now call the generated function module
    CALL FUNCTION fm_name
    EXPORTING
    /1bcdwb/docparams = fp_docparams
    vendor_data = wa_lfa1
    IMPORTING
    /1bcdwb/formoutput = fp_formoutput
    EXCEPTIONS
    usage_error = 1
    system_error = 2
    internal_error = 3
    OTHERS = 4.
    Close spool job
    CALL FUNCTION 'FP_JOB_CLOSE'
    EXCEPTIONS
    usage_error = 1
    system_error = 2
    internal_error = 3
    OTHERS = 4.
    When function module "fm_name" is called, variable fp_formoutput is returned blank (0 pages).
    Can anyone help or suggest something ?
    Thank you in advance,
    Nuno Santos

    Hi,
    The default export parameter is /1bcdwb/formoutput of type
    fpformoutput. This parameter has to be evaluated in the calling program if the
    resulting document needs to be handled by the program itself. Export parameters
    can be added only for those interfaces that are compatible with Smart Forms.
    There is also only one standard exporting parameter of the form's generated
    function module: /1bcdwb/formoutput of type fpformoutput. It contains three
    fields:
    . pdf: Contains the PDF data in hexadecimal form if parameter getpdf of
    function module FP_JOB_OPEN is set to 'X'. This is required if your
    program has a download functionality or if you want to pass on your PDF to
    Business Communication Service to fax or e-mail it.
    Detail information on Business Communication Service can be found in the
    SAP Library, Topic .Generic Business Tools for Application Developers
    (BC-SRV-GBT).. See also standard demo reports BCS_EXAMPLE_...
    . pdl: contains the PDL data in hexadecimal form if parameter getpdl of
    function module FP_JOB_OPEN is set to 'X'.
    . pages: returns the number of pages that have been printed.
    There is also only one standard exporting parameter of the form's generated
    function module: /1bcdwb/formoutput of type fpformoutput. It contains three
    fields:
    . pdf: Contains the PDF data in hexadecimal form if parameter getpdf of
    function module FP_JOB_OPEN is set to 'X'. This is required if your
    program has a download functionality or if you want to pass on your PDF to
    Business Communication Service to fax or e-mail it.
    Detail information on Business Communication Service can be found in the
    SAP Library, Topic .Generic Business Tools for Application Developers
    (BC-SRV-GBT).. See also standard demo reports BCS_EXAMPLE_...
    . pdl: contains the PDL data in hexadecimal form if parameter getpdl of
    function module FP_JOB_OPEN is set to 'X'.
    . pages: returns the number of pages that have been printed.
    Note:
    . getpdf: If set to 'X', the /1bcdwb/formoutput-pdf field of the form's generated
    function module will contain the PDF data in hexadecimal form. This is
    helpful for further processing the PDF file. A preview will not be possible if
    getpdf = 'X'
    Hope this will be helpfull.
    Regards
    Adil
    Edited by: Syed  Abdul Adil on Jun 17, 2008 4:23 PM
    Edited by: Syed  Abdul Adil on Jun 17, 2008 4:24 PM

  • Not able to create a universe when using nav. att. 0MATL_TYPE in the query

    Dear experts,
    A few days ago I posted a message in the BO General Category due to this error and I was adviced to install SP19 in BW (3.5). We've allready installed it but the issue is still arising. I am posting this thread now in this category since maybe the other category was too general and this one a little bit more specified.
    The error we are having is the following:
    We are having an issue when trying to create a universe over a BEx query which uses navigational attribute 0MATL_TYPE of 0MATERIAL (0MATERIAL__0MATL_TYPE).
    No matter where do we insert this nav. attribute in the query (lines, columns, free characteristics...) that we are not able to create the universe. We receive a message when trying to create it such as "error without message"
    We have other navigational attributes from several characteristics which are not giving us any problems in universes, just nav attributes 0MATL_TYPE and a Z characteristic (ZMATPR) which is the same as 0MATL_TYPE (it is defined the same way, not related).
    We are working with:
    BW 3.5 - SP19, BEx 3.x
    BOBJ XI 3.0 (without service pack or fix pack)
    Does any one have any clue on what could be the reason for this issue??
    Thanks in advance for your interest!
    Best regards!!!!
    Cecilia

    Hello Ingo,
    First of all thanks for your help, since we are really concerned about this issue.
    We have been analysing the file you have talked us about. The thing is that a week and a half ago we had to write an OSS message to SAP concerning another issue, and we were recommended to install note 1260004 which involves editing the registry in order to show SOFA logs, and if we have understood correcty, the file you have given us modifies as well the server registry in order to show sofa logs.
    Does the file you have given us includes new information in the SOFA logs, what is the difference between what we have changed with the SAP note and what you have given us?
    Nevertheless, we have retrieved two logs from two executions (having navigational attribute 0MATL_TYPE in the query from which we want to create the universe) in case you could help us to interpret the informations given since we are not able to understand it. (You can seen them below my signature.....haven't find a way to attach files....sorry....)
    Thank's very much in advance for your help!!!! This is so disconcerting.......
    Best regards!
    No way , I cannot copy the logs since the message format is destroyed when I copy it..... If you need it please inform me and we will send it to you!
    Thanks again for the help!!!
    Cecilia
    Edited by: Cecilia Guerra on May 11, 2009 1:56 PM
    Edited by: Cecilia Guerra on May 11, 2009 2:09 PM

  • Not able to create J2EE user DDIC in portal

    Hi All,
    I am trying to configure the BI 7.0  system in EP 7.0. My systems are running on Windows 2003 32 bit edition. SP level is SPS11 & SP10
    I have configured the UME where datasource is ABAP system. After using the supportdesk tool I am getting the below three erros in the system.
    Import of Web Templates in active version will fail because the J2EE user DDIC is not properly mapped to an ABAP user other than DDIC Maintain a user mapping for J2EE user DDIC - see note 945055 for details
    Check could not be executed because retrieval of WebAS ABAP settings failed Check connectivity to WebAS ABAP and make sure the ABAP coding correction from note 937697 is applied in the latest version available
    Check could not be executed because retrieval of WebAS ABAP settings failed Check connectivity to WebAS ABAP and make sure the ABAP coding correction from note 937697 is applied in the latest version available
    To resolve these issues i tried to create user id DDIC in portal but I am not able to create it. It is giving below error
    A user with the specified logon ID already exists; choose a different, unique logon ID
    As it is trying to create this user id in ABAP datasource. Please let me know how to create DDIC in J2EE engine where ABAP is the datasource.
    Please help me resolve this issue.
    Thanks,
    Shambo

    Hi,
    In defaulttrace.trc I am getting the below errors
    #1.5#00055D4A98DC0061000004BC00001610000460FCEAE15F00#1232539295495#com.sap.ip.bi.preexecutionservices.PreexecutionservicesRfcService#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.preexecutionservices.PreexecutionservicesRfcService#Administrator#9873####403302b0e7b311ddbd4500055d4a98dc#SAPEngine_Application_Thread[impl:3]_27##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: com.sap.ip.bi.base.exception.BIBaseRuntimeException: SAX Exception
    com.sap.ip.bi.base.exception.BIBaseRuntimeException: SAX Exception
         at com.sap.ip.bi.webapplications.runtime.preexecution.impl.PreexecutionDispatcher$DocumentAnalysis.createMutableDocument(PreexecutionDispatcher.java:93)
         at com.sap.ip.bi.webapplications.runtime.preexecution.impl.PreexecutionDispatcher.validateDocument(PreexecutionDispatcher.java:571)
         at com.sap.ip.bi.preexecutionservices.PreexecutionservicesRfcService.handleRequestForRSWR_PREEXECUTION_PROXY(PreexecutionservicesRfcService.java:109)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.handleServiceRequestGeneric(BIServicesRfcDispatcherService.java:283)
         at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:177)
         at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:235)
         at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
         at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
         at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0_0.processFunction(PRTRFCRemoteObjectImpl0_0.java:118)
         at sun.reflect.GeneratedMethodAccessor299.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy119.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
         at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:59)(:main:, row=1, col=59) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:59)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at com.sap.ip.bi.webapplications.runtime.preexecution.impl.PreexecutionDispatcher$DocumentAnalysis.createMutableDocument(PreexecutionDispatcher.java:85)
         ... 28 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:59)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1590)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1710)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
         ... 30 more
    #1.5#00055D4A98DC0061000004BF00001610000460FCEAE18738#1232539295511#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.application.message.impl.MessageBase#Administrator#9873####403302b0e7b311ddbd4500055d4a98dc#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#/Applications/BI#Plain###A message was generated:
    ERROR
    Transformer exception while transforming BEx Web templates
    com.sap.ip.bi.deploytime.BISP2Jsp SAPXMLTransformer
    SAX Exception
    Transformer exception while transforming BEx Web templates
    com.sap.ip.bi.deploytime.BISP2Jsp SAPXMLTransformer
    SAX Exception#

  • Not Able to create 0008 in QA

    Hi seniors,
    While doing testing in QA i am not able to creat the infotype 0008 .
    I have schecked the table T510A,there i could find the Pay Roll Types & PayrollScale Area ,
    Even system automatically picks up the data but when i am tring to select the wage types its not accepting any and throughing an error of 01 not available in T510A.
    What could be the possible reason.please help.

    Hi Lata & Nasim,
    Thanks for the updates,I have gone through all the system settings in QA which i had transported from DEV .
    I have checked all the possible settings and features,everything is in place.
    Do i need to Reactivate all the features in QA again.
    Now out of my 23 Infotypes configured in actions following are also not working.
    0077,0094,0009,0185-no subtye avilable,i am even not able to maintain them in PA30.
    what could be the possible reasons for thiese errors in QA.
    Please guide.
    Edited by: srssaphr09 on Mar 25, 2011 1:59 PM
    Edited by: srssaphr09 on Mar 25, 2011 2:26 PM

Maybe you are looking for

  • Creating Recovery Discs for Win 7 - When Win7 Pro 64 is Preloaded from Win 8.1 Dowgrade Rights ?

    Novice questions: 1. What is the proper procedure for: Creating Recovery Discs for Win 7 Pro 64 - When Win 7 Pro 64 is "Preloaded by Lenovo from Win 8.1 Dowgrade Rights" ??? 2.  Will I then be able to use these Win 7 pro 64 - Recovery discs in the fu

  • Need info regarding static file cache in weblogic

    Hi, I want to cache the static files at weblogic side I am using Apache plugin provided by weblogic I have gone through the e-docs about FileCache ON which is needs to be set in httpd.conf I want to know is there any settings which is set at weblogic

  • Adobe Audition audio won't sync

    Hi there, We've been editing with FCPX for a while now and it's gone smoothly for the most part. Typically we've been recording video with a T3i and our audio via Logic or a Zoom portable recorder. I've never had a problem dropping the alternate audi

  • Migration key error

    I have a R/3 4.71 system, on AIX 5.1, oracle 9.2.0.3.    I bought a new IBM SERVER pP 550. I need to migrate R/3 to this new server.    I used system copy to export all data.  but when I import it , Migration key always error,   why ? I got key from

  • ANY IDEAS? can't read Leopard HDV QT on Tiger system

    I'm trying to play a QT made in Leopard on a different computer with a Tiger OS (G5, dual 2.0 processors, ver.10.4.9), and it won't open or play. It shows up as a blank page rather than the QT icon on the Tiger system, but shows as a QT on the Leopar