Packed Data type

Hi Experts
I have declared the data type as follows
Data : amt type p decimals 3. * But its decimal places = 3
But in the result am getting only 2 decimal places.
what could be the reason.
Pls suggest me on this.
Regards
Rajaram

Hi,
just copy this code and activate this, execute this code.
Data : amt type p decimals 3.
amt = 50 / 7.
write:/ amt.
now amt = 7.143.Here, as you have declared amt as
Data : amt type p decimals 3 you are getting output as 7.143
hope this works.

Similar Messages

Problem with packed data type variable?

Hi all,
I have a problem while doing calculations with packed data type variables . As they are saving in the format '0,00'. so unable to do calulations because of ',' .
To convert these fields into str and replacing ',' with '.' is very time consuming because i have many packed data type variables.
Can you please provide any other alternative for over coming this problem? Is there any option while defining these variables?
Thanks,
Vamshi.

Hi VAMSHI KRISHNA,
First check out SU01 Tcode (if u don't have permission then u can ask BASIS to do it)
Enter User Name
Execute
Goto Defaults Tab
Check Out Decimal Notation here... set it 1,234,567.89
SAVE it
Log Off once and again login with the same user id and check the result...
Hope it will solve your problem..
Thanks & Regards
ilesh 24x7

Packed Data Type from DB2

Hi everyone.
I am working with a DB2 Data Base connected to PI 7.1, there is a standard Packed Data Type and I have to take it to PI to make some conversions on PI.
Do someone know if there is a way to handle DB2 Packed Data Type on PI 7.1??
Thanks in advanced

Have a look here : http://jrecord.cvs.sourceforge.net/viewvc/jrecord/jrecord/src/net/sf/JRecord/Common/Conversion.java?revision=1.2&view=markup
It contains a lot of conversion routines, this one : "getMainframePackedDecimal(...)" may suits you !
Chris

Dynamic Internal Table - data type changed automatically

Dear All,
I have a requirement of craetion of dynamic inetrnal table which I have created referring to a custom table .
In that custom table there is field ZDC002 of type DEC(16,7) which is converted to data type P(9,7) .
Now it works fine if 2 digit and 7 decimals value passed like 12.1234567 but it gives overflow error when passing more than 2 digit value .
Please help me as I have no control to SAP standard functinality while creation of data-type . My piece of code :
ref_table_des ?=
cl_abap_typedescr=>describe_by_name( 'ZBW_EE_DCONTR' ).
idetails[] = ref_table_des->components[].
In this idetails[] table filedname data type changed from DEC16,7 to data type P(9,7). => Total Length of Packed Data Type is 9 which allows to contain only 2 numericdigits and 7 decimals => puts overflow error if more than 2 numeric data passed.
Any suggestions will be appreciated.
Thanks,
Sachin

Did you try to view the code on the Data Source view and cube that it is reflecting the correct data type on both places? if not you can change there and save it.
prajwal kumar potula

Pack and Floating Point Data Type in ABAP

Dear All,
I am new to ABAP. Started with data types. Came across pack and floating point.
Please let me know what PACK and Floating Point stands for with few examples and the main difference between them.
Regards
Arun V

Hi,
You'd better ask this question in ABAP forum http://forums.sdn.sap.com/forum.jspa?forumID=50 .
Best Regards,
Ada

Data type conversion from packed to numeric

Hi Experts,
i have a question on data type conversion. My requirement is:
i have fields of type packed decimal in my internal table itab. I need to convert the values of packed decimal fields in itab to numeric type.
Example:
Data: begin of itab occurs 0,
            ebeln like ekko-ebeln,
            ebelp like ekpo-ebelp,
            menge(15) type p decimals 2,
            netpr(15) type p decimals 2,
          end of itab.
if itab-menge has a value of 2.00, i need to convert that value to '         200'. Right justified.
if itab-netpr has a value of 1,234.56, i need to convert that to '         123456'.
The above internal table itab is passed to the Function module GUI_DOWNLOAD and the itab data is downloaded to a text file.
Please let me know how to acheive this objective.

Hi ,
You can use
SPLIT at '.' into v1 v2
concatenate v1 v2 into vv1.
REPORT ZDN_TEST_001 .
data: lv_var1(15) type p decimals 2 value '123.00'.
data: lv_var2(15) type p decimals 5 value '123.12121'.
data: lv_varc1(15) type c.
data: lv_varc2(15) type c.
data: lv_varc1d(2) type c.
data: lv_varc2d(5) type c.
data: lv_varc11(15) type c.
data: lv_varc21(15) type c.
write:/ lv_var1.
write:/ lv_var2.
*1)write & REPLACE.
write lv_var1 to lv_varc1.
write lv_var2 to lv_varc2.
REPLACE '.' WITH SPACE INTO lv_varc1.
             CONDENSE lv_varc1 NO-GAPS.
REPLACE '.' WITH SPACE INTO lv_varc2.
             CONDENSE lv_varc2 NO-GAPS.
write:/ lv_varc1.
write:/ lv_varc2.
*2)split & concatinate
write lv_var1 to lv_varc1.
write lv_var2 to lv_varc2.
split lv_varc1 at '.' into lv_varc1 lv_varc1d.
concatenate lv_varc1 lv_varc1d into lv_varc11.
split lv_varc2 at '.' into lv_varc2 lv_varc2d.
concatenate lv_varc2 lv_varc2d into lv_varc21.
write:/ lv_varc11.
write:/ lv_varc21.

Conversion of Packed Decimal Numbers to Java Data Types

Hi all,
I'm working with a mainframe file which contains datas in Packed Decimal Numbers.My requirement is to convert these datas to Java datatypes and also to convert the Java datatypes to Packed Decimal Numbers before storing them in the mainframe.
Can anyone help me out with any code for converting Java data types to/from other data formats such as: EBCDIC, IBM370 COMP (binary numbers up to 9 digits), and COMP-16 (packed decimal numbers)?
I would hugely appreciate any response to my query.
Thanking you all,
Kaushik.

Rather than go that route, I'd instead look into providing a "service" on your mainframe to:
1) provide a textual representation of the numbers (from native to text)
2) read text, converting to native numeric storage
And use that service to retrieve that information by your Java app (1)Similarly, instead of trying to write natively-formatted numbers from your Java app, I'd write it as text and make that same "service" read the text (2)
This is the kind of thing XML is for.

No-rounding while converting data type F to Packed

Hi All,
I want to pass value of a variable of data type F to another variable of dtata type P with decimals 3.
While converting values decimals are getting rounded to next higher value.
Can any one tell me how to retain the actual values,without rounding off.
Ex. variable 1 = 25.1238567890000 (type F).
when variable 2 is assigned the value of variable 1,then it should consist of the value 25.123(instead of 25.124).
Thanks & Regards
Seshagiri.

Hi seshagiri,
it seems that the value you want to pass to (type F) is smaller than the value that you are using in your code.
Can I ask what is the actual use of the value type P? if there is processing to be done then I suggest to try to process the needed code using a common data type then until the later parts of the logic to pass it to data type P.
If the value is only to be used for display then just pass it to a variable of data type C or string to retain the decimals.

Unicode - "DMBTR" must be a character-type field (data type C,N,D or T)

Greetings Experts!
I am trying to convert legacy code to Unicode for a current ERP6.0 reinstallation and have encountered the syntax error "DMBTR" must be a character-type field (data type C,N,D or T)
The field is part of a structure and the fields attributes are as follows:
COMPONENT = DMBTR
COMPONENT TYPE = DMBTR
DATA TYPE = CURR
LENGTH = 13
DECIMALS = 2
DESCRIPTION = Amount in Local Currency
The code in question is as follows:-
macro Move_Zoned.
Converts a numeric variable to zoned format and moves it to a
target variable.
DEFINE move_zoned.
     &1 - source variable
     &2 - Number of Decimal Places
     &3 - 'To'
     &4 - Target Variable.
write &1 to w_zoned no-grouping decimals &2.
condense w_zoned.
     Remove the Decimal Points.
search w_zoned for '...'.
while sy-subrc = 0.
    move sy-fdpos to w_to_point.
    if w_to_point = 0.
      w_to_point = 1.
    endif.
    compute w_from_point = sy-fdpos + 1.
    concatenate w_zoned+0(w_to_point)
                w_zoned+w_from_point
           into w_zoned.
    search w_zoned for '...'.
endwhile.
shift w_zoned right deleting trailing space.
translate w_zoned using ' 0'.
call function 'Z_TRANSLATE_ZONED_DECIMALS'
    exporting
      i_input              = w_zoned
    importing
      i_output             = w_zoned
    exceptions
      x_invalid_zoned_char = c_invalid_zoned_char
      x_numeric_info_lost = c_numeric_info_lost
      others               = c_other_zoned_error.
     Get the length of the recipient field so we don't truncate the
     numbers....
describe field &4      length w_flength in character mode.
describe field &4      type   w_type.
describe field w_zoned length w_zoned_len in character mode.
if w_zoned_len <= w_flength.
    move w_zoned to &4.
    shift &4 right deleting trailing space.
    translate &4 using ' 0'.
else.
        Get the start position....
        If it's a packed field allow for values up to 6 figures
    compute w_zoned_len = w_zoned_len - w_flength.
    if w_type = 'P'.
      subtract 2 from w_zoned_len.
      clear w_type.
    endif.
    move w_zoned+w_zoned_len &3 &4.
endif.
END-OF-DEFINITION. "Move_zoned
LOOP AT t_single_kunnr.
    move_zoned t_single_kunnr-postamt 2
            to t_single_kunnr-dmbtr.
    DIVIDE t_single_kunnr-dmbtr BY 100.
    MODIFY t_single_kunnr.
ENDLOOP.
Is there a solution to get past this syntax error as I would rather not change the datatype of the field in the structure.
Much Obliged
Elphick.

Type X is not allowed in Unicode. When a field is declared as Type X with Value u201809u2019 or any other value, it can be resolved by using classes.
Before Unicode
                  CONSTANTS: c_hex TYPE x VALUE '09'.
Resolution:
Itu2019s work for any value of x.
First a temporary field of Type c should declare. Following class will convert Type x variable into type c.
Example:
CONSTANTS: c_hex TYPE x VALUE '09'.
DATA: LV_TEMP TYPE STRING.
DATA: LV_TMP TYPE C.
TRY.
CALL METHOD CL_ABAP_CONV_IN_CE=>UCCP
EXPORTING
UCCP   = c_hex
RECEIVING
CHAR   = LV_TMP   .
CATCH CX_SY_CONVERSION_CODEPAGE.
CATCH CX_PARAMETER_INVALID_TYPE.
CATCH CX_SY_CODEPAGE_CONVERTER_INIT.
ENDTRY.
CONCATENATE I_OUTPUT-BKTXT I_OUTPUT-BVORG
I_OUTPUT-BUDAT I_OUTPUT-MESSAGE INTO
SEPARATED BY LV_TMP.
I_BUFFER = LV_TEMP.
CLEAR LV_TEMP.
CLEAR LV_TMP.
OR
Note: It works only for type x value 09.
CLASS cl_abap_char_utilities DEFINITION LOAD.
CONSTANTS: c_hex TYPE c VALUE
                         abap_char_utilities=>HORIZONTAL_TAB.

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

Microsoft OLE DB Provider for Oracle: Data type is not supported.

I got the error:
Microsoft OLE DB Provider for Oracle: Data type is not supported.
Shortly after upgrading from Oracle 8 to Oracle 9. I was advised to download more up to date oracle drivers, but I was wondering if there was a way to tell what version of the 'OLE DB Provider for Oracle' is already at. Is there a command I can use via SQL Plus or something?

I have found Microsoft ODBC for Oracle to be more stable than the Microsoft OLEDB for Oracle driver. I have also found both Microsoft ODBC and OLEDB drivers to be more stable than the drivers from Oracle.
You could always get the latest MDAC (Microsoft Data Access Components) from Microsoft's MSDN Download site and then get the ODAC (Oracle Data Access Components) from Oracle's OTN Download site. ODAC requires MDAC. And ODAC has the latest drivers.
I suppose it would help to have the latest patches for your Oracle client software too. Maybe Oracle MetaLink would have these?
It may even help to have the latest service pack for Visual Studio 6 (Visual C++ 6 and Visual Basic 6) too.

Dates in BEx query coming into designer as a dimension with Char data type

This must be an old issue with a well documented work around ... but alas i can find it !
When i build a universe over a BEx query with dates the universe designer builds them as Dimensions of CHAR type not DATE. Therefore all WebI date functionality fails .. eg sorting, automatic time hierarchies etc.
What is the workaround ?
Andrew Fox

Is the data source an InfoSet or an InfoCube? It appears the date type object has not been implemented yet for Infosets. Here's SAP Note 1370410:
Symptom
Infoset date type objects (DATS type) are mapped as Character types in a universe based on a SAP BEX Query.
Prompts related to the Date field variables are coming as List of values instead of Calendar in WebIntelligence.
Reproducing the Issue
Create a BusinessOjects universe on a Super Query which is based on a multiprovider containing an Infoset or
Create a BEx superquery directly on Infoset.
BusinessObjects Enterprise XI 3.1
SAP Integrated Solutions Kit XI 3.1
Cause
This behaviour has been considered as an enhancement request and tracked under ADAPT01229917.
Resolution
This enhancement request is scheduled to be addressed in Service Pack 3 (SP3) for BusinessObjects Enterprise XI 3.1 due approximately April 2010.
I did try a BEx query that uses an InfoCUBE as a source and the objects are coming into the universe correctly as dates.

Packed date format conversion

I am getting the date from a third party interface in the packed form of size 4 char of bit data type. Can this be converted into the SAP format?

HI
When converting decimal figures with numbers following the decimal point into binary floating-point numbers, unavoidable rounding errors occur. This is because many decimals (for example, 0.1) correspond to periodic fractions, and are therefore unable to be displayed exactly.
If you choose Calculate with Packed Numbers in the query monitor, packed numbers (ABAP data type P, with nine decimal places) are used as the internal number format for all query key figures instead of binary decimals. Rounding errors are avoided with commercial calculations with this fixed-point number, because in doing so no conversion of numbers into the dual system takes place.
Choose this option for those application areas in which a high accuracy is required (for example, for queries in the accounting and cost accounting areas).
Because calculating with packed numbers causes a high processing status overall, we recommend not using this number format for all query key figures, but rather only for those key figures for which a very high degree of accuracy is required.
You have to make this setting in the InfoObject maintenance for the respective key figure:
1)From the SAP Easy Access Menu, choose Modeling ® Object Maintenance ® InfoObject.
2)Enter the name of the key figure and choose Maintain.
3)To calculate with packed numbers, choose from the Additional Properties tab page under Diverse with the option Key Figure with Maximum Accuracy.
with regards
vinayaka

What should be the data type for a field in ztable?

i am desing a ztable , wht should be the datatype for a field if i want to enter values like -1.5 and -2.5 , negative values with decimals what should be the data type???

declare as P type. TYPE P DECIMALS 1
Type P data allows digits after the decimal point. The number of decimal places is generic, and is determined in the program. The value range of type P data depends on its size and the number of digits after the decimal point. The valid size can be any value from 1 to 16 bytes. Two decimal digits are packed into one byte, while the last byte contains one digit and the sign. Up to 14 digits are allowed after the decimal point. The initial value is zero. When working with type P data, it is a good idea to set the program attribute Fixed point arithmetic.Otherwise, type P numbers are treated as integers.
You can use type P data for such values as distances, weights, amounts of money, and so on.
Also check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb2fd9358411d1829f0000e829fbfe/content.htm
Regards,
Maha

Multi language description of data types - xsd export

Hi,
with PI 7.1 there is a new feature for multi language field description (http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/fdd13fa69a4921e10000000a1550b0/content.htm) in the repository.
If you change the display language, the description language is also changed.
If you want to export the XSD of the data type, the description in XSD depends on the display language.
Does anybody knows a way to export a XSD with both language description.
I remember seen a XSD with the xml:lang tag.
regard,
Torsten

If assuming if a Element is only present in 1 Language pack, that SCSM defaults to that?
yes. Hence you should be able to get away with manually removing the secondary language packs. There is however a slight chance that some Ids have no displaystring in the primary language pack.
http://codebeaver.blogspot.dk/

Packed Data type

Similar Messages

Maybe you are looking for