ATG extending OOTB enumerated data type

Hi All,
If i have to add a extra payment group/option to an data-type="enumerated" in ATG repository, should we ,
1) Use the OOTB table in our extended orderRepository.xml???? Coz ATG recomends to use auxiliary when extending the OOTB properties.
2)Should we mention all the OOTB options along with my custom option????
3) Will there be any SQL change for adding a extra option in the enumarated data-type????
4)Can you please let me know more about data-type="enumerated" .
<item-descriptor name="paymentGroup" sub-type-property="type" version-property="version" expert="true" cache-mode="simple" display-name-resource="itemDescriptorPaymentGroup" item-cache-timeout="180000">
<table name="dcspp_pay_group" type="primary" id-column-name="payment_group_id">
      <attribute name="resourceBundle" value="atg.commerce.OrderRepositoryTemplateResources"/>
   <property name="type" data-type="enumerated" default="paymentGroup" expert="true" category-resource="categoryInfo" display-name-resource="type">
        <attribute name="useCodeForValue" value="false"/>
        <option value="paymentGroup" code="0"/>
        <option value="creditCard" code="1"/>
        <option value="giftCertificate" code="2"/>
        <option value="storeCredit" code="3"/>
         <option value="MyPaymentGroup" code="3"/>
        <option value="invoiceRequest" code="5000"/>
        <attribute name="resourceBundle" value="atg.commerce.OrderRepositoryTemplateResources"/>
        <attribute name="propertySortPriority" value="10"/>
      </property>
</table>
Regards

Hi,
You can use OOTB tables for this requirement as you are not changing the table definitions.
No SQL change is required.
You need to mention all the OOTB options when you say xml-combine as replace. Make sure that you are getting the correct repository xml file after combining by examining the template definition thro dyn admin.
One more good practice is use reasonably greater value to the code to your custom option (instead of giving the next number) as it would help during migration.
For Ex, in your example you have given code as 3 for your custom option. If ATG adds one more payment group they would use this code. If you use something like 100, it avoids the rework during migration.
Hope this helps.
Keep posting the updates / questions.
Thanks,
Gopinath Ramasamy

Similar Messages

Using enumerated data types?

I have an array of enumerated datatypes which is the output from a database. I have selected that the enumerated data be Strings. Why can't I loop through the array and store the string in a string array?

Hello,
Try to run the array of enumerated through a for loop,you can get the string for the current value of the control by wiring it to a Format Into String VI and specifying the format to be string (%s) and get the array of current value out of the for loop.
If you want all strings values contained in the enum, run the array trough a for loop,create an indicator for the enum element , create a property node for this enum with strings[] property and you will get a an array of strings out of the for loop.
Regards,
Cyril Bouton
Applications Engineer
National Instruments.
Cyril Bouton
Active LabVIEW Developper

Updating data types

Hi,
I have the following issue: I need to extend a complex data type with a new atomic field (a string) after I already used it within my process context and a business rule. Thus I changed the data type, deleted the context and reloaded the alias in the business process. In both cases the old data type without the new added string. What else do I have to do in order to make the changes visible to both the process and the business rule?
Thank you for your support

Hi ,
thank you for you answer. I can't realy follow your explaination as it mentions Webdynpro.
Maybe I should precise my problem a bit more (if you solution will help me please explain it once more to me
I am working with a complex data dype in the Process Development perspective. When I add another field (lets say a string) to the complex datatype usually the dialog to reimport the xsd should appear
(I am talking about the one which can bet put on and off under Preferences > Enterprise Service Modeling > Import and Reimport)
However, although it is put on this dialog appear in one of my projects. It event appears if I do the changes to other projects but not in this particualar one. And as the reimport does not work the added field does not appear in the process context where I use the complex type.
Is there a manual way to start the reimport manually?

Java Data Types?

Hi,
shall we say
The data types in Java 1.5 can be divided into 4 categories. They are:
i.     Primitive Data Types
ii.     Abstract Data Types
iii.     Arrays
iv.     Enumerated Data Types
...............?

Raijinsetsu wrote:
I have to agree with jverd...
Abstract is not a data type. Abstract declares a specific type of class which cannot be instantiated. Enumerations are just specialized objects. Arrays are also specialized objects.One could choose to consider arrays, enums, and abstract classes as separate categories.
>
If you wanted, the full list would be:
Object (reference is another term you could apply to objects)
int
long
short
byte
charEven if you include the primitives you forgot, this list is just as arbitrary as the original one, and does not correspond to the JLS.
In particular, Object is not a type. There are primitives, references, and the null type.
Edited by: jverd on May 6, 2009 7:56 AM

Optional operations on extended data type

Hello everyone,
I am currently working on a project where I have to read data from either a database or a file and depending on how much information is available different statistics will be computed.
Currently I have two data types MyRecord and ExtendedMyRecord which are both interfaces and provide getter methods to retrieve the data. ExtendedMyRecord extends MyRecord. For both interfaces there is a default implementation.
The first thing the application does is it loads records from the database - whcih in most cases are MyRecord objects. Afterwards statistics are calculated for the whole set of records.
In case all records are of type ExtendedMyRecord additional operations may be performed.
However what got me thinking is that MyRecord currently has three fields and ExtendedMyRecord has 6 fields. In the current architecture I have to create new classes and interfaces in case I ever have to extend the number of fields in the database (or I would have to change one of the interfaces and put the additional fields there and change all code using them).
Does it make more sense to provide a boolean operation isAvailable() which can be used to determine whether a particular field was available for a certain record or is the design I currently use - where I check using instanceof - the better approach?
Any ideas?
Kind Regards,
snowbird

The first thing the application does is it loads
records from the database - whcih in most cases are
MyRecord objects. Afterwards statistics are
calculated for the whole set of records.
In case all records are of type ExtendedMyRecord
additional operations may be performed.That description doesn't sound good to me.
Database operations require three things
1. Functionality to access the database.
2. Data specific to the database (like a connection)
3. Data specific to the application (like a customer name which might be stored in a record in the database.)
Your description sounds like you are mixing 1 and 3 (and perhaps throwing 2 in as well.)
That is always wrong. Because only the database layer should have 1 and 2. 3 is entirely seperate from 1 and 2 and should be kept that way.
Keeping it seperate leads to the following type of structures....
- Customer, has the name, account, etc.
- CustomerCollection, contains a list of Customer.
- CustomerDao, this takes a Customer and stores it, updates it, etc. It also has queries that creates CustomerCollection.
There are variations on the above where there might be more classes for each of the above. But in all cases Customer is never a "record".
In Java Blueprints, the Customer record about would be a Transfer Object (or Data Transfer Object) and CustomerDao would be a Data Access Object.

I need help in "HOW TO EXTEND THE DATA TYPE SYSTEM"......

Hi All,
I need to add new data type like SDO_GEOMETRY in spatial Oracle.
I don't mean the User-Defined Datatype but new datatype embed in the database.
I read the Data Cartridge Developer's Guide but it has info how to use more efficiently UDT through indexes.
Anybody used the “Type System” under Databases and Extensibility Services?
It might be written in C++ or Java but I do not know how.
Any hints and help will be appreciated.
Thanks,

> In Figure 1-1 Oracle Services, there is a "Type System" as Oracle Services.
The "Type System" is merely a compartmentalising the data type handling and implementation code/modules in Oracle.
This covers all types. Oracle native types, user defined types (UDTs), etc.
Saying that you want to create a new type in the "Type System" is basically saying you want to use the CREATE TYPE SQL command in Oracle.
> So, I want new_type1 and new_type2 behave like other built-in types, just the way
SDO_GEOMETRY works in Oracle Spatial Cartridge.
Not familiar with the SDO_GEOMETRY. Why do you mention this type specifically? What do you want to do similar?
> I have already done it with user-defined types. Now I need to do this way so that I can
compare and contrast in terms of speed, space...etc for part of my research.
Hmm.. I'm not sure what you are trying to compare ito of a UDT and Data Cartridge extensions. It is not one or the other. What research is this if I may ask?
Simplistically you extend the Type System with a new UDT/ADT. And there you have a new type data can be used in the SQL Engine and the PL/SQL engine. The OCI (Oracle Call Interface) supports such types via the OCI object API calls - which means this new type can also be used from Oracle clients written in Delphi, C++, Java, etc.
That new type can be a complex type. This type may need specific management code (memory management, context management, internationalisation, etc). To support this you can extend the UDT/ADT further by developing Cartridge Basic Service interfaces for the type - designing and writing management code to, for example, support specific internationalisation requirements when dealing with multibyte character sets.
You can also extend the UDT/ADT to be custom managed ito indexing, determining query optimisation, computing costs of custom methods/functions/operators on this custom data type. These extensions are done by developing Data Cartridge interfaces for the type.
Thus I cannot see what you are trying to compare. It is not one layer/interface versus another. These layers exist for all Oracle types (in the Type System). Oracle not only allows you to add to the top layer by adding/defining a new data type. It also allows you to customise (if needed) the layers below it.

TestStand Data Type Enumeration Explained for Array of column_information

I'm sure it's in the documentation somewhere but I can't find TestStand Data Type Enumeration Explained for Array of column_information.
data_type 1, 2, 3 ect.
What do they represent?
Thnaks,
-SS
Attachments:
TestStand.PNG ‏20 KB

If you are referring to the Database Connectivity Toolkit, then the definitions for the data types are as follows:
Item
Value
String
0
Long (I32)
1
Single (SGL)
2
Double (DBL)
3
Date/Time
4
Binary
5
Jared A.
Applications Engineer
National Instruments

Problem with central build of Simple Date Type with Enumeration

Dear gurus,
I hope I'm posting this in the correct forum. Please advise if I'm in the wrong forum.
I have a Web Dynpro DC in which I've created a simple data type with enumeration. It is used for binding to a radio box. The data type is called DownloadType; the enumeration contains two vales: current and archive. To allow me to access the enumeration values, I turn on the "Generate a class representation of the enumeration" in the data type builder.
I then reference the enumeration values with code like:
if (downloadType.equals (DownloadType._CURRENT))
    yada yada yada
This works fine when building locally and deploying directly. But when the DC is built by CBS (or doing a "Development Component->Build..." in NW Dev Studio), the build fails, stating that the DownloadType._CURRENT symbol cannot be resolved.
For example:
C:yadayadayada.java:227: cannot resolve symbol
symbol : variable _CURRENT
location: class yadayadayada.DownloadType
                equals(DownloadType._CURRENT)) {
Apparently the central builder is not smart enough to handle the "Generate a class representation" flag.
Is this a known problem? Are there any workarounds?
Thanks in advance for any help you can provide.
-Kelly
P.S. Environment: 2004s

Hi Kelly,
works for me using SP10, what SP are you on?
There's a line in the DC log that says:
     [ddgen] [Info]    Generating datatypes/com/x/x/x/MyEnum.java
and the java compiler includes the matching path for compilation:
      [echo]   source paths:
      [echo]     ...\_comp\src\packages
      [echo]     ..\t\ABF37B5AFB3B2E8A76FFD29E7862EA48\gen_ddic\datatypes
Regards,
Marc

Using Long Data type in the Page

Hi ,
I have a page (in multiple page creation form ) which is suppose to contain only the NOTES field of the entity being created . The Notes field is defined as LONG data type in the table.
Two Doubts.
1. As of now in Jdev , u only have Varchar2 data type when assigning to any messageText layout item. What should be the max value set for Max Lenght of this field on the form . I suppose its 32k+ ,since its Long Field .
Anybody has used Long notes field before ??
2. This page has only one item on it , ie Notes ,which i have defined as messageRichText as style. I have been trying to resize this item ,so that it stretches out on entire page . But it just doesnt resizes .. any idea ..below is my PG.xml code
<?xml version = '1.0' encoding = 'UTF-8'?>

<page xmlns:jrad="http://xmlns.oracle.com/jrad" xmlns:oa="http://xmlns.oracle.com/oa" xmlns:ui="http://xmlns.oracle.com/uix/ui" version="9.0.3.8.13_1426" xml:lang="en-US" xmlns:user="http://xmlns.oracle.com/jrad/user" xmlns="http://xmlns.oracle.com/jrad" file-version="$Header$">
<content>
<oa:pageLayout id="NotesMainR" amDefName="oracle.apps.xxi.pro.server.ProAM" windowTitle="Pro Notes" controllerClass="oracle.apps.xxi.pro.webui.ProNotesCO">
<ui:corporateBranding>
<oa:image id="corporateBrandingImage" source="/OA_MEDIA/FNDSSCORP.gif"/>
</ui:corporateBranding>
<ui:contents>
<oa:messageComponentLayout id="ProInfoR" extends="/oracle/apps/xxi/pro/webui/ProInfoRN"/>
<oa:pageButtonBar id="PgButton">
<ui:contents>
<oa:submitButton id="Back" use="/oracle/apps/fnd/attributesets/Buttons/Back" unvalidated="true" serverUnvalidated="false"/>
<oa:submitButton id="Save" use="/oracle/apps/fnd/attributesets/Buttons/Save"/>
<oa:submitButton id="Continue" use="/oracle/apps/fnd/attributesets/Buttons/Continue"/>
</ui:contents>
</oa:pageButtonBar>
<oa:tableLayout id="region3" hAlign="center">
<ui:contents>
<oa:rowLayout id="region4" hAlign="left" vAlign="top" width="100%">
<ui:contents>
<oa:cellFormat id="region5" height="100%" width="100%" hAlign="left" columnSpan="1" vAlign="top">
<ui:contents>
<oa:header id="region6" text="Notes In Table Layout">
<ui:contents>
<oa:messageRichTextEditor id="ProNotesI" maximumLength="20000" viewName="CustomerPOVO" viewAttr="ProNotes" fontBar="true" alignmentGroup="true" tipType="shortTip" prompt="Pro Notes" richTextModeDisplayHeight="100%" richTextModeDisplayLength="100%"/>
</ui:contents>
</oa:header>
</ui:contents>
</oa:cellFormat>
</ui:contents>
</oa:rowLayout>
</ui:contents>
</oa:tableLayout>
</ui:contents>
</oa:pageLayout>
</content>
</page>
any idea??
thanks

Hi Padma,
Thanks for reply !!
The width is still pain point for me ,as i am unable to increase its width .
I tried increasing the width of the table to 100%, however ,it still doesn work .
Any pointers ??
If you have used this widget before , could you assist me with any sample code u hv ??
I would really appreciate it
thanks

Performance and data types: which to use?

Hi All,
I am wondering what data type to use and the effect of them on memory/speed.
1. What is the difference (if any) of using sgl, dbl, int etc. Looking at the LabVIEW help there seems to be a range of 8-256 bits of storage according to the data type. Is it basically choose the one with the smallest storage that can fit the data?
2. I currently have a cluster flowing through subVI's. The cluster contains the start time (or freq), the delta t (or f) and the array of data (about 500-5000 elements). I tried to use the waveform datatype but it couldn't handle a delta t of 2 nanoseconds (500 MHz signal). Am i ok using the cluster, or should i seperate the components and pass them along? What data type should i use for each of the components?
Thanks

There are three main issue to consider.
Range and accuracy. If you need a very high level of accuracy, then you will need to use the extended data type or even create your own, although that's unlikely.
Memory. Yes, SGL takes less than DBL, but unless you're dealing with really huge amounts of data this won't matter.
Coercion. Most built in functions work on DBL. If you wire a SGL into them, they will coerce it, possibly creating a copy of the data and increasing your memory usage.
To sum it up, most of the times it would be best to use the default DBL. It's highly unlikely you'll need one of the others.
As for your second question, it sounds to me like the data is a single organism, so I would say you should leave it in the cluster, but that really depends on whether the functions need it or not and whether you're constantly bundling and unbundling the cluster. Note that 5000 elements is far from being a large array and you shouldn't have any problems handling it.
As for the timing unit, if you really only have 5000 elements (that's 10 microseconds of data?) then you should not have a problem with using a U32 with a nanosecond as the base unit. That should give you the ability to measure more than 4 seconds.
Try to take over the world!

Can I use Non-standard XSD Data Types in my XSD; if so how?

Please help if you can, this is a complex question, so bear with me.
Also note that I am in Livecycle 8.2 ES (not ES2 or higher).
I am working on creating XSD schemas to map to form objects.
I have created one master schema document that is wired into multiple forms, and I have one separate schema for reusable form objects, that I refer to as a "common node".
All of my individual form schemas are brought together in this one Master Schema via the use of include statements.
EXAMPLE: This is like my Master Schema
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" >
<xs:include schemaLocation="./commonElementsNode.xsd" />
<xs:include schemaLocation="./form1111.xsd" />
<xs:include schemaLocation="./form2222.xsd" />
<xs:include schemaLocation="./form3333.xsd" />
<xs:element name="form">
<xs:complexType>
<xs:sequence>
   <xs:element ref="commonElementsNode" />
   <xs:element ref="form1111" />
   <xs:element ref="form2222" />
   <xs:element ref="form3333" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
This works fine.
I can load this up in Designer in the Data View and everything appears in the Data View hierarchy correctly, with "form" as the top node.
And as long as I use standard "xs:" data types - everything works great. So if I go into LiveCycle Designer and I go to File --> Form Properties --> Preview --> Generate Preview Data and generate dummy XML data - it respects my XSD conventions.
Now here is where the problem arises:
In these schemas, I need to define the data types.
The client I am working for needs me to use their data types.
These data types are not standard xs: data types, like "xs:string" or "xs:date".
Rather, the data types are ones that have been defined in other schemas and reserved to a namespace.
For instance, rather than use xs:date I need to use something like: "myns:DateType"
This "myns:DateType" is defined as:
<xs:complexType name="DateType">
<xs:simpleContent>
   <xs:extension base="xs:date">
    <xs:attribute name="format" type="xs:string" use="optional">
     <xs:annotation>
      <xs:documentation xml:lang="en">
       <mydoc:Name>Date Format Text</mydoc:Name>
       <mydoc:Definition>The format of the date content</mydoc:Definition>
       <mydoc:PrimitiveType>string</mydoc:PrimitiveType>
      </xs:documentation>
     </xs:annotation>
    </xs:attribute>
   </xs:extension>
</xs:simpleContent>
</xs:complexType>
Note that I have redacted this data type slightly and changed the namespace to protect the anonymity of my client, but we can assume that their data type is valid and currently in use with other systems.
It conforms to W3 standards.
Note also how this type is an enumeration of the base type "xs:date".
This is defined in a schema called something like "MyCoreTypes.xsd"
There is a namespace reservation in this file that looks something like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"
xmlns:myns="http://clinetname.com/schemas/mycoretypes" >
So there is a name space reservation there.
In my aforementioned "Master Schema" file, I have an include statement that looks like this:
<xs:include namespace="http://clinetname.com/schemas/mycoretypes" schemaLocation="./MyCoreTypes.xsd" />
(let's assume that the schema is in the same folder, as the Master Schema, so we can use the "./" relative path.)
Now the problems is that in all my forms, where I have a myns:DateType (e.g.: in form1111, a "Date of Birth" element that looks like this: <xs:element name="OwnerBirthDt" type="myns:DateType"/> ) the XSD is not respected when the XML dummy data is generated in LiveCycle Designer implying that the XSD's data types are not being recognized properly.
Has anyone had this problem before?
Is there a solution?
Is it even possible to use these kind of include or import references in LiveCycle to define a data type other that the standard "xs:" data types?
Please let me know - it would be greatly appreciated.
I am more than willing to clarify the question further if others are willing to help.
Thanks -
Ben Lyons

prf.kishorekumar wrote:
i came here with a hope that I would definitely get some help.
pls.. some one reply1) You got some help. No where do I see thanks or acknowledgment for the information given.
2) Please remember that people on the forum help others voluntarily, it's not their job.
3) Google can often help you here if the forum can't. Using Google I found this interesting link:
http://today.java.net/pub/a/today/2004/05/24/html-pt1.html
It discusses the Swing HTML EditorKit as well as some other free HTML renderers.
Edited by: petes1234 on Oct 24, 2007 7:29 PM

How to set the Data types of the Excel sheet while exporting details to it.

Hi All,
We are trying to export some order details to the excel sheet from a jsp. It is working fine when the local system language is set to English.
But when i change it to Russian. the details like Line Numbers(e.g: 1.1, 1.2, 1.3 and so on... ) are getting changed into some other data type(e.g: 01.янв, 02.янв, 03.янв and so on....).
i guess this is mainly due to some data type mismatch, so i tried setting all the possible charset for response in the jsp, but could not succeeded.
This is only for the details which or of decimal format, working fine for the details which are in String type. like Description, Item name etc...
As it is high preference issue for our client, Please help me in this regard ASAP.
Thanks & Regards,
Praveen Reddy B

hi Shiv..
Its not an OAF page but it is from Apps only (i.e.Oracle iStore).
we tried writing this:
<%response.setContentType("application/vnd.ms-excel; charset=UTF-8");%>
<%response.setHeader("Content-Disposition", "attachment; filename=downloadOrders.xls" );%>
<head>
          <title>Logitech_iStore</title>
<style>
table {
border-style: solid;
table th.mainHeader {
                                        border-style: solid;
background-color:#000099;
border-color:#000000;
color:#FFFFFF;
font-family:Arial, Helvetica, sans-serif;
font-weight:bold;
font-size:13pt;
table th {
                                        border-style: solid;
background-color:#6687C4;
border-color:#000000;
color:#FFFFFF;
font-family:Arial, Helvetica, sans-serif;
font-weight:bold;
font-size:12pt;
table td.color1 {
                                        border-style: solid;
background-color:#FFFFFF;
border-color:#000000;
color:#000000;
font-family:"Times New Roman", Times, serif;
font-weight:normal;
font-size:12pt;
table td.color2 {
                                        border-style: solid;
background-color:#C0C0C0;
border-color:#000000;
color:#000000;
font-family:"Times New Roman", Times, serif;
font-weight:normal;
font-size:12pt;
                              table td {
                                        border-style: solid;
background-color:#FFFFFF;
border-color:#000000;
color:#000000;
font-family:"Times New Roman", Times, serif;
font-weight:normal;
font-size:12pt;
</style>
</head>
          <body>
          <%
                    /*BigDecimal resp_id=RequestCtx.getResponsibilityId();
                    String respIdParam="";
                    String respkey="";
                    if(resp_id!=null)
                    respIdParam=resp_id.toString();
                    out.println("respIdParam"+respIdParam);
                    logi.oracle.apps.ibe.util.LogiDAOImpl dao=new logi.oracle.apps.ibe.util.LogiDAOImpl();
                    respkey=dao.getRespKey(respIdParam);
                    out.println("respkey"+respkey);
          logi.oracle.apps.ibe.util.LogiOrderDetailsBean orderDetailsBean = new logi.oracle.apps.ibe.util.LogiOrderDetailsBean();
                    java.util.ArrayList ls = new java.util.ArrayList();
                    String resp_key=request.getParameter("respkey");
                    System.out.println(resp_key);
                    String noofDays=request.getParameter("noOfDays");
                    String qCustAcctId=request.getParameter("qCustAcctId");
                    logi.oracle.apps.ibe.util.LogiDAOImpl daoimpl=new logi.oracle.apps.ibe.util.LogiDAOImpl();
                    String decideTab=request.getParameter("decideTab");
                    String startDate=request.getParameter("startDate");
                    String endDate=request.getParameter("endDate");
                    String queryCondition=request.getParameter("queryCondition");
                    String queryOperator=request.getParameter("queryOperator");
                    String queryValue=request.getParameter("queryValue");
                    String queryDateValue=request.getParameter("queryDate");
                    System.out.println("queryDateValue"+queryDateValue);
%>
                    <table cellspacing="1" cellpadding="1" width="100%" border="0" class="OraBGAccentDark">
<tr>
<th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_NUM")%></th>
                                   <th>Customer Name</th>
                                   <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_DATE")%></th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_BOOKED_DATE")%></th>
                              <th>Request Date</th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_STATUS")%></th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ORD_PO")%></th>
                              <th>Currency</th>
                                        <th>Payment Terms</th>                                                                      <th>Freight Terms</th>
                                   <th>FOB</th>
                                        <th>Sales Channel</th>
                                        <th>Ship to Location</th>
                                        <th>Bill to Location</th>
                                        <th>SalesTerritory Country</th>
                                        <th>Order Type</th>
                                        <th>Order Total</th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_LINE_NUM")%></th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_ITEM")%></th>
                                        <th>Customer SKU</th>
                                        <th>Description</th>
                                        <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_QTY")%></th>
                                        <th>Shipped Quantity</th>
                                        <th>ScheduleShip Date</th>
                                        <th>Unit Price</th>
                                        <th>Extented Amount</th>
                                        <th>Taxes Total</th>
                                        <th>Freight Charges</th>
                                        <th>Case pack charge</th>
                                        <th>Charges Total</th>
                                   <th><%=AOLMessageManager.getMessageSt("IBE","IBE_LGT_LINE_STATUS")%></th>
                                        <th>Ship Date</th>
                                        <th>Warehouse</th>
                                        <th>Tracking Number</th>
                                        <th>Waybill Number</th>
                                        <th>Delivery Number</th>
                                        <th>Pro Number</th>
                                        <th>Hold Applied</th>
                                        <th>Pallet Qty</th>
                                        <th>Pallet#</th>
                                        <th>Invoice Number</th>
                                        <th>Promo Number</th>
                                        <th>Ship Method</th>
</tr>
<%
                         int pSiteid=0;
                         java.math.BigDecimal mSiteId=oracle.apps.ibe.util.RequestCtx.getMinisiteId();
                         if(mSiteId!=null)
                         pSiteid=mSiteId.intValue();
                         out.println("pSiteid"+pSiteid);
               if(decideTab!=null && decideTab.trim().equalsIgnoreCase("days"))
                         if(qCustAcctId!=null)
                                   ls=daoimpl.downOrderDetails(qCustAcctId,noofDays,pSiteid);
                    else if(decideTab!=null && decideTab.trim().equalsIgnoreCase("dates"))
                         if(qCustAcctId!=null)
                                   ls=daoimpl.downOrderDateDetails(qCustAcctId,queryDateValue,startDate,endDate);
                    else if(decideTab!=null && decideTab.trim().equalsIgnoreCase("condition"))
                         if(qCustAcctId!=null)
                                   ls=daoimpl.downOrderConditionDetails(qCustAcctId,queryCondition,queryOperator,queryValue);
                    for(int i=0;i<ls.size();i++)
                         orderDetailsBean=(logi.oracle.apps.ibe.util.LogiOrderDetailsBean)ls.get(i);
                         String orderNumber= orderDetailsBean.getOrderNumber();          //Order Number
                         if(orderNumber==null)orderNumber="";
                         String customerName=orderDetailsBean.getCustomerName();          //Customer Name
                         if(customerName==null)customerName="";
                    String orderedDate=orderDetailsBean.getOrderDate();               //Order Date
                         if(orderedDate==null)orderedDate="";
                         String bookeddate= orderDetailsBean.getBookedDate();          //Booked Date
                         if(bookeddate==null)bookeddate="";
                         String requestdate= orderDetailsBean.getRequestDate();          //Requested Date
                         if(requestdate==null)requestdate="";
                         String orderstatus= orderDetailsBean.getOrderStatus();          //Order Status
                         if(orderstatus==null)orderstatus="";
                         String ponumber= orderDetailsBean.getPoNumber();               //PO Number
                         if(ponumber==null)ponumber="";
                         String currency=orderDetailsBean.getCurrencyCode();               //Currency
                         if(currency==null)currency="";
                         String paymentterms= orderDetailsBean.getPaymentTerms();     //Payment Terms
                         if(paymentterms==null)paymentterms="";
                         String frieghtterms=orderDetailsBean.getFreightTerms();          //Freight Terms
                         if(frieghtterms==null)frieghtterms="";
                         String fobterms=orderDetailsBean.getFobTerms();                    //Fob Terms
                         if(fobterms==null)fobterms="";
                         String saleschannel=orderDetailsBean.getSalesTerms();          //Sales Channel
                         if(saleschannel==null)saleschannel="";
                         String billtoloc=orderDetailsBean.getBillToLocation();          // Bill to Location
                         if(billtoloc==null)billtoloc="";
                         String shiptoloc=orderDetailsBean.getShipToLocation();          //Ship To Location
                         if(shiptoloc==null)shiptoloc="";
                         String salesterr=orderDetailsBean.getSalesCountry();          // Sales Territory
                         if(salesterr==null)salesterr="";
                         String ordertype=orderDetailsBean.getOrderType();               // Order Type
                         if(ordertype==null)ordertype="";
                         String ordertotal=orderDetailsBean.getOrderTotal();               //Order Total
                         if(ordertotal==null)ordertotal="";
                         String linenumber=orderDetailsBean.getLinenumber();               //Line Number
                         if(linenumber==null)linenumber="";
                         String item= orderDetailsBean.getItem();                         //Item Name
                         if(item==null)item="";
                         String sku= orderDetailsBean.getCustomerSKU();               // Customer SKU
                         if(sku==null)sku="";
                         String desc= orderDetailsBean.getDescription();               //Item Description
                         if(desc==null)desc="";
                         desc = URLEncoder.encode(desc);                                        // Added by Sunil
                         desc = URLDecoder.decode(desc);
                         String qty=orderDetailsBean.getQty();                              //Ordered Quantity
                         if(qty==null)qty="";
                         String shippedqty=orderDetailsBean.getShippedQty();               //Shipped Quantity
                         if(shippedqty==null)shippedqty="";
                         String scheduleqty=orderDetailsBean.getScheduleDate();          //Schedule Date
                         if(scheduleqty==null)scheduleqty="";
                         String unitprice=orderDetailsBean.getUnitPrice();               //Unit Price
                         if(unitprice==null)unitprice="";
                         String xamount=orderDetailsBean.getXAmount();                    //Extended Amount
                         if(xamount==null)xamount="";
                         String taxestotal=orderDetailsBean.getTaxesTotal();               //Taxes Total
                         if(taxestotal==null)taxestotal="";
                         String freightcharges=orderDetailsBean.getFreightCharges();//Freight Charges
                         if(freightcharges==null)freightcharges="";
                         String palletcharges=orderDetailsBean.getPalletSurcharge();     //Pallet Charges
                         if(palletcharges==null)palletcharges="";
                         String chargestotal=orderDetailsBean.getChargesTotal();          //Charges Total
                         if(chargestotal==null)chargestotal="";
                         String linestatus=orderDetailsBean.getLinestatus();               //Line Status
                         if(linestatus==null)linestatus="";
                         String shipdate=orderDetailsBean.getShipDate();                    //Ship Date
                         if(shipdate==null)shipdate="";
                         String warehouse=orderDetailsBean.getWareHouse();               //Ware House
                         if(warehouse==null)warehouse="";
                         String trackingnumber=orderDetailsBean.getTrackingNumber();//Tracking Number
                         if(trackingnumber==null)trackingnumber="";
                         String waybill=orderDetailsBean.getWayBillnumber();               //Waybill Number
                         if(waybill==null)waybill="";
                         String deliverynumber=orderDetailsBean.getDeliveryNumber();     //Delivery Number
                         if(deliverynumber==null)deliverynumber="";
                         String pronumber=orderDetailsBean.getProNumber();               //Pro Number
                         if(pronumber==null)pronumber="";
                         String holdapplied=orderDetailsBean.getHoldApplied();          //Hold Applied
                         if(holdapplied==null)holdapplied="";
                         String palletqty=orderDetailsBean.getPalletQty();               //Pallet Qty
                         if(palletqty==null)palletqty="";
                         String pallethash=orderDetailsBean.getPalletHash();               //Pallet Hash
                         if(pallethash==null)pallethash="";
                         String invoicenumber=orderDetailsBean.getInvoiceNumber();               //invoice Number
                         if(invoicenumber==null)invoicenumber="";
                         String promonumber=orderDetailsBean.getPromoNumber();               //Promonumber
                         if(promonumber==null)promonumber="";
                         String shipmethod=orderDetailsBean.getShipMethod();               //Promonumber
                    if(shipmethod==null)shipmethod="";
               %>
               <tr>
               <td><%=orderNumber%></td>
               <td><%=customerName%></td>
               <td><%=orderedDate%></td>
               <td><%=bookeddate%></td>
               <td><%=requestdate%></td>
               <td><%=orderstatus%></td>
               <td><%=ponumber%></td>
               <td><%=currency%></td>
               <td><%=paymentterms%></td>
               <td><%=frieghtterms%></td>
               <td><%=fobterms%></td>
               <td><%=saleschannel%></td>
               <td><%=billtoloc%></td>
               <td><%=shiptoloc%></td>
               <td><%=salesterr%></td>
               <td><%=ordertype%></td>
               <td><%=ordertotal%></td>
               <td><%=linenumber%></td>
               <td><%=item%></td>
               <td><%=sku%></td>
               <td><%= desc %></td>
               <td><%=qty%></td>
               <td><%=shippedqty%></td>
               <td><%=scheduleqty%></td>
               <td><%=unitprice%></td>
               <td><%=xamount%></td>
               <td><%=taxestotal%></td>
               <td><%=freightcharges%></td>
               <td><%=palletcharges%></td>
               <td><%=chargestotal%></td>
               <td><%=linestatus%></td>
               <td><%=shipdate%></td>
          <td><%=warehouse%></td>
               <td><%=trackingnumber%></td>
               <td><%=waybill%></td>
               <td><%=deliverynumber%></td>
               <td><%=pronumber%></td>
               <td><%=holdapplied%></td>
               <td><%=palletqty%></td>
               <td><%=pallethash%></td>
               <td><%=invoicenumber%></td>
               <td><%=promonumber%></td>
               <td><%=shipmethod%></td>
               </tr>
               <%     }
          %>
          </table>
          </body>
          </html>
Please suggest the needful...
Praveen Reddy

Length in creation of data type

Hi Experts,
I have one doubt regarding field length.i will get data from proxy(ECC) through status field and it would be a 25 character.
i have created a status field as data type in my proxy source structure .
could you please suggest do i need to create a status field with length 25 if yes where is the option length to be extended in datatype creation
it would be appreciate if u people give me the answer
thanks,
Bhaskar

>
bhaskar yenneti wrote:
> Hi Experts,
>
> I have one doubt regarding field length.i will get data from proxy(ECC) through status field and it would be a 25 character.
>
> i have created a status field as data type in my proxy source structure .
>
> could you please suggest do i need to create a status field with length 25 if yes where is the option length to be extended in datatype creation
>
> it would be appreciate if u people give me the answer
>
> thanks,
> Bhaskar
Are you on XI3.0/Pi 7.0 or PI 7.1?
if its XI3.0/Pi 7.0, then note that XI doesn't validate the length of the data/field even though the option is there.
http://help.sap.com/saphelp_nw04/helpdata/en/b2/439347ce019848bf3ad9c000d414c3/content.htm
Else if you are on PI 7.1, you can expect validation.

Dynamic Drop Down creation using simple data types

Hi all,
I have got a requirement in which i have to create an iView which is going to have 6 drop down values and with in that 1 value is going to have sub values which needs to get displayed in the similar drop down fashion.
I have created a simple data type having enumeration of the 6 values and linked the same to iView with drop down by key which is working successfully. And for the purpose of sub values i have created a similar simple data type with two values and linked the same with a value attribute.
Well, can any one tell me the further process to proceed ?
Thanks in advance ...
Vipin

Vipin,
There are quite some steps to achieve what you need. Since you have both your DropDownByKey elements defined and bound to context elements, it may make sense to keep the Second DropDownByKey element invisible and make it visible only when user selects a specified key from first DropDownByKey. To achieve this, follow these steps.
1. Create an action with a parameter "key" of type string.
2. Bind this action with onSelect event of your First DropDownByKey UI Element.
3. Do mapping of parameter "key" in your wdDoModifyView with following code.
if (firstTime)
         final IWDDropDownByKey dk = (IWDDropDownByKey)view.getElement("DropDownByKey1");
           // Replace DropDownByKey1 with id of your DropDownByKey Element.
         dk.mappingOfOnSelect().addSourceMapping("key", "key");
4. Create a context attribute of type WDVisibility say "DDVisible" and bind to "visible" property of your second DropDownByKey.
5. Set DDVisible to NONE in wdInit().
wdContext.currentContextElement().setDDVisible(WDVisibility.NONE);
6. In onSelect action write this code to make second visible
if(key.equalsIgnoreCase("Two")){
     //Replace "Two" with your required value.
         wdContext.currentContextElement().setDDVisible(WDVisibility.VISIBLE);
       else{
            wdContext.currentContextElement().setDDVisible(WDVisibility.NONE);
This should give the desired results.
Hope this helps.
Vishwas.

Change function to work for date data type

I have found the below function form the AstTom page. This function works perfectly when i pass varchar datatype and I am wondering what do i need to change here of course the datatype inoder
for this function to accept date value. example I want to pass (05/21/2010, 04/23/2010) as a date data type and
--create your type
create or replace type varcharTableType as table   of varchar2 (255);
CREATE OR REPLACE FUNCTION tplcp.in_varchar (p_string IN VARCHAR2)
   RETURN varchartabletype
AS
   l_string   LONG             DEFAULT p_string || ',';
   l_data     varchartabletype := varchartabletype ();
   n          NUMBER;
BEGIN
   LOOP
      EXIT WHEN l_string IS NULL;
      n := INSTR (l_string, ',');
      l_data.EXTEND;
      l_data (l_data.COUNT) := LTRIM (RTRIM (SUBSTR (l_string, 1, n - 1)));
      l_string := SUBSTR (l_string, n + 1);
   END LOOP;
   RETURN l_data;
END in_varchar;
CREATE OR REPLACE PROCEDURE planholderslist (
   p_letting_date   IN       VARCHAR2,
   p_results        OUT      sys_refcursor
AS
BEGIN
   OPEN p_results FOR
      SELECT DISTINCT DECODE (TRIM (MIN (j.route)),
                              NULL, 'N/A',
                              TRIM (MIN (j.route))
                             ) routenumber,
                      l.lcontid contractid, (q.cdescr) jobdescription,
                      INITCAP (q.clocat1 || q.clocat2) LOCATION,
                      SUBSTR (q.cprojnum, 1, 10) projectnumber,
                         SUBSTR (l.letting, 3, 2)
                      || '-'
                      || SUBSTR (l.letting, 5, 2)
                      || '-'
                      || SUBSTR (l.letting, 1, 2) lettingdate
                 FROM vendor v,
                      vendaddr r,
                      letprop l,
                      planhold p,
                      proposal q,
                      project j,
                      propproj k,
                      bidlet bd
                WHERE v.vendor = r.vendor
                  AND k.contid = q.contid
                  AND k.pcn = j.pcn
                  AND l.lcontid = k.contid
                  AND p.vendor = v.vendor
                  AND l.letting = p.letting
                  AND (TO_CHAR (bd.datelet, 'MM/DD/YY') IN (
                                      SELECT COLUMN_VALUE
                                        FROM TABLE (in_varchar (p_letting_date)
                  AND l.CALL = p.CALL
                  AND r.addrnum = p.billto
                  AND bd.letting = l.letting
             GROUP BY q.cdescr,
                      q.clocat1,
                      q.clocat2,
                      bd.letting,
                      l.letting,
                      l.lcontid,
                      q.cprojnum
             ORDER BY lettingdate;
END planholderslist;
/

three or even four dates passed to the parameter.4 date parameters are still easy to code for. Use an IN clause.
Just do something like this:
SQL> select * from t;
D
05-JAN-2010 00:00:00
15-MAR-2010 00:00:00
09-SEP-2010 00:00:00
07-DEC-2010 00:00:00
SQL> create or replace
2 procedure find_date (rc out sys_refcursor
3                      ,p1 in date
4                      ,p2 in date default null
5                      ,p3 in date default null
6                      ,p4 in date default null
7                      ) as
8 begin
9    open rc for
10       select d
11       from   t
12       where d in (p1,p2,p3,p4);   -----<<< notice this line
13 end;
14 /
SQL> var results refcursor
SQL> exec find_date(:results, to_date('05-JAN-2010'));
PL/SQL procedure successfully completed.
SQL> print results
D
05-JAN-2010 00:00:00
SQL> exec find_date(:results, to_date('05-JAN-2010'),to_date('09-SEP-2010'));
PL/SQL procedure successfully completed.
SQL> print results
D
05-JAN-2010 00:00:00
09-SEP-2010 00:00:00
SQL> exec find_date(:results, to_date('05-JAN-2010'),to_date('09-SEP-2010'), sysdate);
PL/SQL procedure successfully completed.
SQL> print results
D
05-JAN-2010 00:00:00
09-SEP-2010 00:00:00
SQL> exec find_date(:results, to_date('05-JAN-2010'),to_date('09-SEP-2010'), to_date('15-MAR-2010'), to_date('07-DEC-2010'));
PL/SQL procedure successfully completed.
SQL> print results
D
05-JAN-2010 00:00:00
15-MAR-2010 00:00:00
09-SEP-2010 00:00:00
07-DEC-2010 00:00:00

ATG extending OOTB enumerated data type

Similar Messages

Maybe you are looking for