Case type Default data

Hello Team,
In the case type default data in GTS for the Procedure CMCD - Customs document, system asks below fields
Foreign trade Organization
Document Type
Goods Direction
for SPL and Embargo check in customs document, i wanted to determine seperate case type. But the above input fields will be unique and system not allows me to assign seperate case type.
Can you help me on how to determine different case type based on the Area?
Note:
I wanted to determine the case type as below
In SPL Check for customs document e.g. EXPORD - Case type SPLE
In Embargo check for customs document e.g. EXPORD - Case type EMBE
Thanks & Regards
Rahul

Some ideas:
One method would be to place a before insert trigger on the data and upper it.
You could add another column, populate via a trigger as upper(), then build a unique index on this column.
See the following Oracle documentation on case insensitive searchs and comparisons
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch5lingsort.htm#i1008800
Oracle support documents:
Develop Global Application: Case-insensitive searches #342960.1
How to use Contains As Case-Sensitive And -Insensitive On The Same Column #739868.1
How To Implement Case Insensitive Query in BC4J ? #337163.1
HTH -- Mark D Powell --

Similar Messages

  • Defaulting Date Types in IT0041

    Hi All,
    I have a issue in defaulting Date Types in IT0041,
    There is a feature DATAR for defaulting Date Types in IT0041. When I create new IT0041 by PA30, values from feature DATAR is getting defaulted.
    But, when i run Hiring Action and at that time vaules from feature DATAR is not being called, its defaulting some other date types.
    Is there any other place where Date Types are defaulted?
    Please let me know if you want any more information
    With Regards
    Shyam

    Hi All,
    Current problem is rectified,
    Solution : I have used INSS instead of INS. In this case values from DATAR is getting defaulted
    New issue is there,
    Some dynamic action is automatically updating with Date Types those which are not there in DATAR. I dont know from where these values are being picked....
    I will continued my research and let you guys know the status.
    I request others to share their thoughts..
    Regards
    Shyam V

  • Error while saving default data type

    When I try to save system wide Default Data Format of any of the columns, an error pops out. Seems like an XML error:
    The current xml is invalid with the following errors:
    Bad xml instance!
    <?xml version="1.0"?> <sawsavedformat:metadata xmlns:sawsavedformat="com.siebel.analytics.web/savedformat/v1.1"><sawsavedformat:columnSavedFormats><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Division Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Group Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Dept Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Class Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Subclass Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Chain Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Area Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Region Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;District Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Store Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Business Calendar&quot;.&quot;Fiscal Week&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="left" vAlign="top"><saw:dataFormat xsi:type="saw:text" textFormat="plain"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Unit Inventory&quot;.&quot;U BOP&quot;"><saw:displayFormat><saw:formatSpec suppress="repeat" wrapText="true" visibility="visible" hAlign="right" vAlign="top" imagePlacement="right"><saw:dataFormat xsi:type="saw:number" whistlerFormat="#,##0" commas="true" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat></sawsavedformat:columnSavedFormats></sawsavedformat:metadata>
    Line:2, Col:8982, Attribute 'whistlerFormat' is not declared for element 'dataFormat'
    Any suggestions?
    Thanks

    HI,
    Its known bug in obiee11.1.1.5. version try to apply obiee11.1.5.5.BP bug fixes version.
    fyi,
    bug 13370386 - 'THE CURRENT XML IS INVALID WITH THE FOLLOWING ERRORS: BAD XMLINSTANCE!' OCCURS
    bug 13249783 - OBIEE 11G THROWS BAD XML INSTANCE
    Thanks
    Deva

  • Default date type for IT0041 in action

    Hi,
    I configure feature DATAR to set 01 as default date type for IT0041, but when I do hiring action, default date type will be 01,02,12.
    Don't know where to change the default.

    Hi,
    Please verify if there is any dynamic action in table V_T588Z set-up for same which may cause override over default.
    Also, verify if your DATAR feature is set up correctly for relevant country grouping and activated.
    Thanks,
    Ameet

  • How to set a default date for a custom field of Date type in project server 2010.

    hi,
    can somebody help  me.
    How Can i set the default date for a custom field of date type in project server 2010 ?

    Dear Rohan,
    You can set default value to custom field thru Lookup table. Assign lookup table to custom field and set default value to some lookup value (Note: check the “Choose a value to use as a default when adding new item” checkbox).
    Regards,
    Avinash kumar | Blog:http://avigr8.wordpress.com | If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

  • JPA - How can I use the table's default Date types? e.g. CURRENT_TIME

    Once again, can't find an answer anwhere.
    I would like to know if/how one can use the default date/time/datetime types as declared for the target table when attempting to persist an entity having these fields set as null.
    create table item
         item_id INTEGER NOT NULL PRIMARY KEY DEFAULT AUTOINCREMENT,
         date_created DATETIME NOT NULL DEFAULT NOW(*),
         date_updated DATETIME NOT NULL DEFAULT NOW(*),
    );Now how can I get the above table to work when attempting to em.persist(myItem) whereby dateCreated and dateUpdated are both null?

    I should also mention that TopLink has always supported the ability to retrieve the current time from the database for use in optimistic locking. The TimestampLockingPolicy offers the ability to configure the next value being retrieved from the database instead of using the local time from the JVM. Our extended optimistic locking configuration does not currently support setting this option but it could be done using a descriptor customizer which can be configured in your persistence unit properties.
    Using optimistic locking may be a good solution for the last modified date since it will also ensure that you do not corrupt the database if someone else has incremented this value since your last read.
    Doug

  • Copying default case types into Dev

    I am working on a system that only have the demo case type delivered in client 100 (golden)
    In client 000 - the default case types are there F_DM, F_PP, F_CR.
    Normally I have seen the default case types in the golden client - is there a program, setting or BASIS process that needs to be performed to move these?

    Hi Mark, to copy the missing entries go to configuration point for the case types, the go to
    Utilities> Adjustments
    Select the R/3 connection to the client 000
    Then select the entries that you need to copy, click on adjust, then all, go back and save the new entries.
    Best regards,
    Cristobal.

  • Multiple dispute case types for one company code

    Hi Experts
    I am trying to design a solution for external system interfacing with SAP FSCM. Requirement is to create dispute cases for short pays automatically using program FDM_AUTO_CREATE (which is normal standard SAP process). We are also creating complaints in third party system based out of our data from SAP. When these are getting created in third party, we need to interface back into SAP and create Dispute (against compalint created in third party). I am thinking of using program FDM_AUTO_CREATE to create disputes based on company code/document number/fiscal year/line item etc.
    To differentiate between disputes and complaints i am proposing to create new case type (other than dispute case type) and have its own number range assigned to it, so that it can be easily recognised in SAP. But as per standard SAP setting one company code can have only one default case type assigned to it and whenever i create cases using FDM_AUTO_CREATE, system always picks up only one case type.
    Is there any standard setting so that system can create complaint cases in SAP with different case type (other than default dispute case type) while using auto create program?
    Thanks in advance
    Aleem

    This is an common question when implementing SAP TCM for trade promotions where claims/ disputes go to CRM for approval.
    We have overcome this by leaving the standard dispute case type in the default settings. We then activate a BAdI - FDM_AR_DEF_CASE_TYPE. We create a Z table that we linked to in the BAdI - that had company code and reason code - and put the additional case type in the table linked to a reason code. By adding a reason code (FI-AR) to the specific items, when you create the dispute it will call the BAdI and table and use the extra dispute case type as opposed to the standard one.

  • Convert the date into user default date formate

    I am wrinting a bdc and i want to convert the date into user default date farmate ..please suggust the functiom module should i use...

    actually by using dats or d type you can get the user specific date itself.
    but if u have different dates format that need to be converted to the user specific date then you can follow below procedure
    1. retrieve the user format from usr01
        SELECT SINGLE datfm
          INTO w_datfm
          FROM usr01
         WHERE bname EQ sy-uname.
    pass w_datfm to the below FM (4th import parameter)
    2. create Z - FM and retrieve the user secific date
    FUNCTION ZFXX_USER_SPECIFIC_DATE.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(IW_DAY) TYPE  CHAR2
    *"     VALUE(IW_MONTH) TYPE  CHAR2
    *"     VALUE(IW_YEAR) TYPE  CHAR4
    *"     VALUE(IW_DATFM) TYPE  USR01-DATFM
    *"  EXPORTING
    *"     VALUE(EW_USER_DATE) TYPE  CHAR0008
    *1  DD.MM.YYYY
    *2  MM/DD/YYYY
    *3  MM-DD-YYYY
    *4  YYYY.MM.DD
    *5  YYYY/MM/DD
    *6  YYYY-MM-DD
    CASE iw_datfm.
      when '1'.
        concatenate iw_day iw_month iw_year
               into ew_user_date.
      when '2'.
        concatenate iw_month iw_day iw_year
               into ew_user_date.
      when '3'.
        concatenate iw_month iw_day iw_year
               into ew_user_date.
      when '4'.
        concatenate iw_year iw_month iw_day
               into ew_user_date.
      when '5'.
        concatenate iw_year iw_month iw_day
               into ew_user_date.
      when '6'.
        concatenate iw_year iw_month iw_day
               into ew_user_date.
      when others.
        clear ew_user_date.
    endcase.
    ENDFUNCTION.

  • Why ServletRequest and ServletResponse default data encoding is ISO8859-1?

    why ServletRequest and ServletResponse default data encoding is ISO8859-1 not System default file.encoding?
    So if my servlet contents Chinese charactors it can't write once runs any system with different encoding types.
    for example:
    import java.io.*;
    import java.util.*;
    import javax.servlet.http.*;
    import javax.servlet.*;
    public class HelloServlet extends HttpServlet {
      public void doGet (
         HttpServletRequest     req,
         HttpServletResponse     res
        ) throws ServletException, IOException
        res.setContentType("text/html");
        String hello = "Hello world &#19990;&#30028;&#20320;&#22909;";
        PrintWriter pw = res.getWriter();
        pw.println("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 Transitional//EN\">");
        pw.println("<head>");
        pw.println("<title>" + hello + "</title>");   
        pw.println("</head>");   
        pw.println();
        pw.println("<body>");
        pw.println();
        pw.println("<h1>" + hello +"</h1>");
        pw.println("</body>");
        pw.close();
      public HelloServlet() {}

    A server parses parameters using the common ISO 8859-1 charset. When a browser uses another charset, it is supposed to send the encoding information in the Content-Type header of the request, but almost no browsers do.
    In the Servlet 2.2 API (e.g Tomcat 3.x), the methods that parse parameter input always assume that it's sent as ISO 8859-1. So they create a String containing the correct bytes but incorrect charset.
    In that case, you can use the com.oreilly.servlet.ParameterParser class and its setCharacterEncoding method :
    http://www.servlets.com/cos/index.html
    However,in Servlet 2.3 (e.g Tomcat 4), a new method on the HttpServletRequest object was added in order to be able to specify the request's parameters charset encoding:
      // Set the charset as Shift_JIS
      req.setCharacterEncoding("Shift_JIS");
      // Read a parameter using that charset
      String name = req.getParameter("name");The setCharacterEncoding call may throw java.io.UnsupportedEncodingException if the encoding is not supported.

  • Doubt on diff types of data plz clarify

    1) we know that there r 3 types of data like i)customizing data/control data ii)master data iii)transactional data.will these  three types of data reside in the same database table are some set of database tables form each categeory?
    2)how to define customizing data/control data,master data,transactional data with examples?
    3)is there any difference between customizing data/control data,master data and transactional data?
    4)what is buffering?can u plz explain single record buffering,generic buffering,full buffering with examples?
    5)is there any site where we can test our abap knowledge?

    hi
    chk this
    Buffering
    The major difference between the context buffer and the normal database and table buffers is that it is only refreshed at given intervals. There is no attempt to update it synchronously, or even nearly synchronously. This means that it is not appropriate to use it for every context or context module.
    Buffering Types
    Permanent (P): This is the default setting. In this case, the data is kept on each application server beyond the end of the transaction in which it is used. The buffer is reset every hour on the hour (8:00, 9:00...). You can reset the buffer manually in the Context Builder.
    Temporary (T): Data is only buffered for the duration of the current transaction.
    No buffering (N)
    Buffer Size
    You can set the maximum number of entries to be buffered. The default is 128. This number only applies to the permanent buffer for a single module. Within a transaction, all of the data that occurs is stored in the buffer unless you have switched off buffering for the module. It is usually best to leave the maximum buffer size set to 128. It is not often that a large number of key combinations occur within one hour on a single application server. Even if this does occur, you can expect combiniations from the first 128 entries to be repeated. The system resets the buffer after one hour, which should ensure that no one module monpolizes it.
    Buffering Types
    An I buffer is a table that assigns derived values to the input fields of the module. It
    Only contains one entry with key values.
    An E buffer is a table that assigns the derived values of the module tot he key fields of the context, It
    contains more than one entry with key values.
    can be a join of all I buffers for the modules buffered
    Performance
    The E buffer gives the fastest access, since it can find the values requested in the DEMAND statement in a single step. Under certain circumstances, it can return a smaller number of hits than the I buffer.

  • How to change default Date format in BO 6.5 SP4

    A problem with date display has been reported to me by one of our users -  in BO 6.5 - since installing SP4.
    The default date format is now MM/DD/YYYY
    I have tried to recreate this on my PC and have been able to confirm that this is the case.
    Most of our PC's will have two versions of Business Objects on them - for 5.1.6 and for 6.5 - that is the case for my PC.
    If I create a new BO document based on a spreadsheet with three entries in the spreadsheet as follows:-
    20/01/2009    20-Jan-2009  20th January 2009
    This displays in BO 6.5 as
    1/20/2009   1/20/2009    20th January 2009
    My PC regional setting is UK and the time displays DD/MM/YYYY
    Can you advise how to correct this problem please.

    Hi Sebastien
    Thank you for your response.
    I haven't checked Dimension in universe because this is happening even when datasource is an Excel spreadheet - as per details in previous post.
    I have looked for *.sbo files and found one for ODBC.sbo in the Version 5 folders on PC - with date format details in it which I've changed - that doesn't make any difference.
    Any other ideas?
    Regards
    Linda

  • Default data adaptor error when deploying a war file in weblogic

    Hi All,
    Newbie here with a few questions regarding the deployment of OPA 10.1. Really hoping you guys can help...
    1) I'm attempting to deploy an unexploded web-determinations.war file on WebLogic. Thanks to this forum I've got past the issues of "rulebase directory not found" etc. However, i'm now faced with an issue which I can't find any info on. Please see below.
    3672074 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN com.or
    acle.determinations.web.platform.controller.actions.StartSessionAction - Could not instansate defau
    lt data adaptor
    java.lang.NullPointerException
    at java.io.File.<init>(File.java:194)
    at com.oracle.determinations.web.platform.plugins.data.XDSDataAdaptor.<init>(XDSDataAdaptor.
    java:55)
    at com.oracle.determinations.web.platform.controller.actions.StartSessionAction.createInterv
    iewSession(StartSessionAction.java:173)
    at com.oracle.determinations.web.platform.controller.actions.StartSessionAction.getResource(
    StartSessionAction.java:66)
    at com.oracle.determinations.web.platform.servlet.WebDeterminationsServlet.doGet(WebDetermin
    ationsServlet.java:67)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.
    java:226)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.oracle.determinations.web.platform.util.CharsetFilter.doFilter(CharsetFilter.java:46)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
    ontext.java:3393)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2
    140)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    I've got the following entry in the application.properties file too...
    # Default XDS data adaptor file path
    #xds.file.path =data
    From what we can see we believe the code is getting a null pointer because of the following method in the WebDeterminationsServletContext class.
    public String resolveFullPath(String path)
    File f = new File(path);
    return f.isAbsolute() ? f.getAbsolutePath() : this.servletContext.getRealPath(path);
    We believe the getRealPath(path), highlighted in red, is returning null. Any ideas how we can resolve this?
    2) The second issue I'm facing is with regards the plugins.libraries property in the application.properties file. I've got the entry as
    plugin.libraries =DataAdaptor.DA;
    which should point to our customised data adaptor. However I'm getting the following error.
    4242994 [[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN com.or
    acle.determinations.web.platform.servlet.WebDeterminationsServletContext - Can not find class: Data
    Adaptor.DA
    4243025 [[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN com.or
    acle.determinations.interview.engine.local.LocalInterviewEngine - Can not find class: DataAdaptor.D
    A
    3) Also, does anyone know if it's possible to deploy a web-determinations.war file containing additional internal application code? What we're attempting to do is deliver a single war file which not only holds the web determination code but also all the code for an application which wraps the OWD within it. At present this just isn't working. I'm not sure what the conflict is exactly. The only way i seem to be able to get this working is by deploying the code in two seperate war files.
    Any help on these issues would be greaty appreciated.
    Thanks,
    Taj

    (2) is being caused because your data adaptor plugin is not installed properly. The jar that contains your plugin needs to go in the WEB-INF/lib directory and you must specify the fully qualified class name in the plugin.libraries property of the application.properties file.
    If you haven't provided a custom data adaptor, Web Determinations will configure and attach the default one for use instead, which is file based. If you are deploying to WebLogic as an unxeploded war, you must configure the directory the default data directory the plugin will uses by specifying an absolute path that your instance of Web Determinations has read/write permissions to in the xds.file.path property of the application.properties file. In your case (1) is basically being caused by (2) since if the your data adaptor was loaded correctly the default one wouldn't load at all.
    As for (3) yes it's likely possible, provided you don't have library conflicts. How it's done really depends on what these additional customisations consist of.

  • How to update the default date format in OBIEE 11G.

    Hi All,
    How to change the default date format in OBIEE 11g from the MM/DD to DD/MM. Could anyone please help me out ASAP?
    Thanks,
    Arpan

    Hi Arpan
    OBIEE 11g is having " localedefinitions.xml " file at this Location C:\Oracle\Middleware\Oracle_BI1\bifoundation\web\display
    in my case i installed at C:\Oracle\MIddleware.
    so
    1- Stop BI Server from EM
    2- Navigate to this Location C:\Oracle\Middleware\Oracle_BI1\bifoundation\web\display. in your case oracle home will be different
    3- take a backup of this file localedefinitions.xml "
    4- modify it and save
    5- bring BI Server up.
    Regards
    sher

  • Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed

    SharePoint 2010 -
    I have created a console utility that further calls the stsadm.exe to Export sites from one site collection in a DB to another site collection in another DB of the same web application.
    Export works fine. But during Import, I get the following errors
    [ListItem] [Admin] Progress: Importing
    [ListItem] [Admin]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Hol plans.xls] Progress: Importing
    [ListItem] [Hol plans.xls]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Time.doc] Progress: Importing
    [ListItem] [Time.doc]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [AP Docs] Progress: Importing
    [ListItem] [AP Docs]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Update - June 27th.pdf] Progress: Importing
    [ListItem] [Update - June 27th.pdf]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Update - June 27th.pdf]   Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    [ListItem] [Update - June 27th.pdf]   Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    [ListItem] [Update - June 27th.pdf]   Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    FatalError: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    Progress: Import did not complete.
    1. Does the console application treated as a Sandbox Solution?
    2. Do I need to configure CAS policy in wss_usercode.config? and what?
    3. What else could be configured to make this work?
    I have tried adding the following in wss_custom_minimaltrust.config but no avail.
    <SecurityClass Name="SqlClientPermission" Description="System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>           
    and
    <PermissionSet
                        class="NamedPermissionSet"
                        version="1"
                        Name="SPRestricted">
    <IPermission
                          class="SqlClientPermission"
                          version="1"
                          Unrestricted="true"
                                />   
    <!-- Other IPermission -->
    </PermissionSet>
    UPDATE: It has been observed that the issue is intermittent. That is, sometimes the import works fine (event without any configuration of SqlClientPermission in any config file) but sometimes it gives the above error. I'm stuck!
    Regards, Amit Gupta

    Hi,
    According to your post, my understanding is that you get Error “Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed
    Simple solution is to change the trust the trust level to FULL: <trust   level="[Full]"    originUrl="URL" />
    In addition, you can modify the wss_mediumtrust.config and wss_minimaltrust.config file under the path “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG”.
    For more information, you can refer to:
    http://blogs.msdn.com/b/navdeepm/archive/2010/02/19/system-security-securityexception-request-for-the-permission-of-type-system-data-sqlclient-sqlclientpermission-system-data-version-2-0-0-0-culture-neutral-publickeytoken-b77a5c561934e089-failed.aspx
    http://www.fewlines4biju.com/2011/01/request-for-permission-of-type_18.html
    http://techsolutions-at-desk.blogspot.com/2011/08/request-for-permission-of-type.html
    Thanks,
    Linda Li                
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Linda Li
    TechNet Community Support

Maybe you are looking for