Date format for call transaction

Hi,
What is the best solution for passing a date field to a call transaction in the date format that the user has in his settings?.
Rgds

The best solution is to define a character field of length 10. Then WRITE the date to the BDC_DATE and then use this variable when passing to BDC.
data: bdc_date(10) type c.
write sy-datum to bdc_Date.
Regards,
Rich Heilman

Similar Messages

How look the flat file for CALL Transaction

Hi ABAPERS
i am new for BDC i want to know how the flat file format for call transaction execution.
if any one have sample flat file data for any transaction please send me.

Hi,
The file format differ for different transaction. Basically you can have the field in any order. It matters how you upload into SAP. Use the function module GUI_UPLOAD to upload the flat file.
Please see this sites for more info.
http://www.sap-img.com/abap/learning-bdc-programming.htm
Help with BDCs and flat files.....
Cheers
Vinod
Message was edited by: Vinod C

When we have to go for session method, when we have to go for call transact

when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

Data Transfer
During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
Direct Input:
In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
Call Transaction:
In this method you can check the data consistency with the help of screen logic.
Batch Input Session:
In this method data consistency is checked with the help of screen logic.
Direct Input Method
Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
Call Transaction Method
Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
Batch Input Session Method
This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
System à Services à Batch input. Moreover, you can have the session run in the background processing.
Writing a Data Transfer Program
If you want to write a data transfer program, you have to follow the steps mentioned below.
Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
Thirdly, you will have to initialize the SAP data structure.
Fourthly, fill the structure with data, performing any conversions and error checking that are required.
Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
Batch Input Method
Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
The process flows for a batch input are discussed below.
Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
Error Handling in Batch Input Method
It is found that most problems usually fall into one of the following two categories discussed below.
In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
Conclusion
I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
Thanks,
Shankar

Hi guys please give me sample code for call transaction that handles error

hi guys, please give me sample code for call transaction that handles error,
please send me the sample code in which there should be all decleration part and everything, based on the sample code i will develop my code.
please do help me as it is urgent.
thanks and regards.
prasadnn.

Hi Prasad,
Check this code.
Source Code for BDC using Call Transaction
*Code used to create BDC
*& Report ZBDC_EXAMPLE                                                *
*& Example BDC program, which updates net price of item 00010 of a     *
*& particular Purchase order(EBELN).                                   *
REPORT ZBDC_EXAMPLE NO STANDARD PAGE HEADING
                      LINE-SIZE 132.
Data declaration
TABLES: ekko, ekpo.
TYPES: BEGIN OF t_ekko,
    ebeln TYPE ekko-ebeln,
    waers TYPE ekko-waers,
    netpr TYPE ekpo-netpr,
    err_msg(73) TYPE c,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko,
      it_error TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_error TYPE t_ekko,
      it_success TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_success TYPE t_ekko.
DATA: w_textout            LIKE t100-text.
DATA: gd_update TYPE i,
      gd_lines TYPE i.
*Used to store BDC data
DATA: BEGIN OF bdc_tab OCCURS 0.
        INCLUDE STRUCTURE bdcdata.
DATA: END OF bdc_tab.
*Used to stores error information from CALL TRANSACTION Function Module
DATA: BEGIN OF messtab OCCURS 0.
        INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF messtab.
*Screen declaration
SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME
                                    TITLE text-001. "Purchase order Num
SELECT-OPTIONS: so_ebeln FOR ekko-ebeln OBLIGATORY.
SELECTION-SCREEN END OF BLOCK block1.
SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME
                                    TITLE text-002. "New NETPR value
PARAMETERS: p_newpr(14)   TYPE c obligatory. "LIKE ekpo-netpr.
SELECTION-SCREEN END OF BLOCK block2.
*START-OF-SELECTION
START-OF-SELECTION.
Retrieve data from Purchase order table(EKKO)
SELECT ekkoebeln ekkowaers ekpo~netpr
    INTO TABLE it_ekko
    FROM ekko AS ekko INNER JOIN ekpo AS ekpo
      ON ekpoebeln EQ ekkoebeln
   WHERE ekko~ebeln IN so_ebeln AND
         ekpo~ebelp EQ '10'.
*END-OF-SELECTION
END-OF-SELECTION.
Check data has been retrieved ready for processing
DESCRIBE TABLE it_ekko LINES gd_lines.
IF gd_lines LE 0.
Display message if no data has been retrieved
    MESSAGE i003(zp) WITH 'No Records Found'(001).
    LEAVE TO SCREEN 0.
ELSE.
Update Customer master data (instalment text)
    LOOP AT it_ekko INTO wa_ekko.
      PERFORM bdc_update.
    ENDLOOP.
Display message confirming number of records updated
    IF gd_update GT 1.
      MESSAGE i003(zp) WITH gd_update 'Records updated'(002).
    ELSE.
      MESSAGE i003(zp) WITH gd_update 'Record updated'(003).
    ENDIF.
Display Success Report
Check Success table
    DESCRIBE TABLE it_success LINES gd_lines.
    IF gd_lines GT 0.
    Display result report column headings
      PERFORM display_column_headings.
    Display result report
      PERFORM display_report.
    ENDIF.
Display Error Report
Check errors table
    DESCRIBE TABLE it_error LINES gd_lines.
If errors exist then display errors report
    IF gd_lines GT 0.
    Display errors report
      PERFORM display_error_headings.
      PERFORM display_error_report.
    ENDIF.
ENDIF.
*&      Form DISPLAY_COLUMN_HEADINGS
      Display column headings
FORM display_column_headings.
WRITE:2 ' Success Report '(014) COLOR COL_POSITIVE.
SKIP.
WRITE:2 'The following records updated successfully:'(013).
WRITE:/ sy-uline(42).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'Purchase Order'(004), sy-vline,
          (11) 'Old Netpr'(005), sy-vline,
          (11) 'New Netpr'(006), sy-vline.
WRITE:/ sy-uline(42).
ENDFORM.                    " DISPLAY_COLUMN_HEADINGS
*&      Form BDC_UPDATE
      Populate BDC table and call transaction ME22
FORM bdc_update.
PERFORM dynpro USING:
      'X'   'SAPMM06E'        '0105',
      ' '   'BDC_CURSOR'      'RM06E-BSTNR',
      ' '   'RM06E-BSTNR'     wa_ekko-ebeln,
      ' '   'BDC_OKCODE'      '/00',                      "OK code
      'X'   'SAPMM06E'        '0120',
      ' '   'BDC_CURSOR'      'EKPO-NETPR(01)',
      ' '   'EKPO-NETPR(01)' p_newpr,
      ' '   'BDC_OKCODE'      '=BU'.                      "OK code
Call transaction to update customer instalment text
CALL TRANSACTION 'ME22' USING bdc_tab MODE 'N' UPDATE 'S'
         MESSAGES INTO messtab.
Check if update was succesful
IF sy-subrc EQ 0.
    ADD 1 TO gd_update.
    APPEND wa_ekko TO it_success.
ELSE.
Retrieve error messages displayed during BDC update
    LOOP AT messtab WHERE msgtyp = 'E'.
    Builds actual message based on info returned from Call transaction
      CALL FUNCTION 'MESSAGE_TEXT_BUILD'
           EXPORTING
                msgid               = messtab-msgid
                msgnr               = messtab-msgnr
                msgv1               = messtab-msgv1
                msgv2               = messtab-msgv2
                msgv3               = messtab-msgv3
                msgv4               = messtab-msgv4
           IMPORTING
                message_text_output = w_textout.
    ENDLOOP.
Build error table ready for output
    wa_error = wa_ekko.
    wa_error-err_msg = w_textout.
    APPEND wa_error TO it_error.
    CLEAR: wa_error.
ENDIF.
Clear bdc date table
CLEAR: bdc_tab.
REFRESH: bdc_tab.
ENDFORM.                    " BDC_UPDATE
      FORM DYNPRO                                                   *
      stores values to bdc table                                    *
--> DYNBEGIN                                                      *
--> NAME                                                          *
--> VALUE                                                         *
FORM dynpro USING    dynbegin name value.
IF dynbegin = 'X'.
    CLEAR bdc_tab.
    MOVE: name TO bdc_tab-program,
           value TO bdc_tab-dynpro,
           'X' TO bdc_tab-dynbegin.
    APPEND bdc_tab.
ELSE.
    CLEAR bdc_tab.
    MOVE: name TO bdc_tab-fnam,
           value TO bdc_tab-fval.
    APPEND bdc_tab.
ENDIF.
ENDFORM.                               " DYNPRO
*&      Form DISPLAY_REPORT
      Display Report
FORM display_report.
FORMAT COLOR COL_NORMAL.
Loop at data table
LOOP AT it_success INTO wa_success.
    WRITE:/      sy-vline,
            (10) wa_success-ebeln, sy-vline,
            (11) wa_success-netpr CURRENCY wa_success-waers, sy-vline,
            (11) p_newpr, sy-vline.
    CLEAR: wa_success.
ENDLOOP.
WRITE:/ sy-uline(42).
REFRESH: it_success.
FORMAT COLOR COL_BACKGROUND.
ENDFORM.                    " DISPLAY_REPORT
*&      Form DISPLAY_ERROR_REPORT
      Display error report data
FORM display_error_report.
LOOP AT it_error INTO wa_error.
    WRITE:/      sy-vline,
            (10) wa_error-ebeln, sy-vline,
            (11) wa_error-netpr CURRENCY wa_error-waers, sy-vline,
            (73) wa_error-err_msg, sy-vline.
ENDLOOP.
WRITE:/ sy-uline(104).
REFRESH: it_error.
ENDFORM.                    " DISPLAY_ERROR_REPORT
*&      Form DISPLAY_ERROR_HEADINGS
      Display error report headings
FORM display_error_headings.
SKIP.
WRITE:2 ' Error Report '(007) COLOR COL_NEGATIVE.
SKIP.
WRITE:2 'The following records failed during update:'(008).
WRITE:/ sy-uline(104).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'Purchase Order'(009), sy-vline,
          (11) 'Netpr'(010), sy-vline,
          (73) 'Error Message'(012), sy-vline.
WRITE:/ sy-uline(104).
FORMAT COLOR COL_NORMAL.
ENDFORM.                    " DISPLAY_ERROR_HEADINGS
Hope this resolves your query.
Reward all the helpful answers.
Regards

Date Format for the input Variable

Hi all,
I got an issue with Date format we enter in the input variable screen for the BEx Analyzer.
We have given a format of MM/DD/YYYY. But when the users accessed the report, it is not taking the format of the variable i.e MM/DD/YYYY but it is taking the format of the users system.
If the user's system format is DD/MM/YYYY, it is accepting the input inthe same format only.
Why this strange behaviour?
My questions are
Is the input for BEx system specific? or variable specific?
Rgrds
Kumar

Hi,
I think it is user specific... you can maintain the date format for user ....
Go to SU01 transaction or.. Go to SYSTEM -> User Profile -> Own data
Here in defaults tab you can see the date formet for user...
Hope this helps...
Thanks,
Vikrant Mahajan

Invalid date format for 'Created' field in the getVersions web service Response.

Hi all,
I am trying to get all versions for selected document by calling getVersions method Versions.asmxweb service, but getting ‘Created’ date attribute value is in the format "29-05-2012 12:01"
but I am expecting either one of the following date formats.
1.      yyyy-MM-dd HH:mm:ss or yyyy-MM-ddTHH:mm:ssz
2.      MM/dd/yyyy HH:mm a   (a means AM/PM)
3.      MM/dd/yyyy
4.      yyyyMMdd HH:mm:ss
where do I need to change?
what are all the formate will be support by SharePoint?
please find attached response xml of getVersions call.
<results xmlns="http://schemas.microsoft.com/sharepoint/soap/">
    <list id="{6A6F6CD1-2E9C-44CC-B1F5-56G7JB5C8778}"/>
    <versioning enabled="1"/>
    <settings url="http://hbngjfgj47s20/reg/_layouts/LstSetng.aspx?List={7S6F6CD1-2E9C-44CC-B1F5-KO9J8Y7Y6H78}"/>
    <result version="@0.3" url="http://vmesxsrv47s20/register/Shared Documents/Parent/child/my_doc" created="29-05-2012 12:01" createdRaw="2014-12-02T12:46:02Z" createdBy="my_dom\agi_sharepoint"
createdByName="AGI_Sharepoint" size="288" comments=""/>
    <result version="0.1" url="http://hbngjfgj47s20/register/_vti_history/1/Shared Documents/Parent/child/my_doc" created="29-05-2012 10:01" createdRaw="2014-12-02T10:55:18Z" createdBy="my_dom\my_sharepoint"
createdByName="my_sharepoint" size="288" comments=""/>
    <result version="0.2" url="http://hbngjfgj47s20/register/_vti_history/2/Shared Documents/Parent/child/my_doc.txt" created="29-05-2012 11:01" createdRaw="2014-12-02T10:59:25Z" createdBy="my_dom\my_sharepoint"
createdByName="my_sharepoint" size="288" comments=""/>
</results>
Kindly help me on this.

Hi,
According to your post, my understanding is that you want to change date format for ‘Created’ field in the getVersions web service.
Per my knowledge, you can get the date format for ‘Created’ field as “MM/dd/yyyy HH:mm a”.
For more information, you can refer to:
Versions.GetVersions Method (Versions)
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Program for call transaction method

can any body help me , how to write a call transaction method . how to create error logs for call transaction method

hi
REPORT ZCALL.
TYPES : BEGIN OF itab,
lifnr TYPE rf02k-lifnr,
ktokk TYPE rf02k-ktokk,
END OF itab.
DATA : i_tab TYPE TABLE OF itab INITIAL SIZE 0,
wa_tab TYPE itab.
DATA : i_bdc TYPE TABLE OF bdcdata INITIAL SIZE 0,
wa_bdc TYPE bdcdata.
DATA : i_message LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE,
wa_message TYPE bdcmsgcoll.
DATA : fname TYPE string VALUE 'd:\manish.txt'.
DATA: p_text(100) TYPE c.
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = fname
filetype = 'ASC'
has_field_separator = 'X'
TABLES
data_tab = i_tab.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT i_tab INTO wa_tab.
PERFORM bdc_dynpro USING 'SAPMF02K' '0100'.
PERFORM bdc_field USING 'RF02K-LIFNR' wa_tab-lifnr.
PERFORM bdc_field USING 'RF02K-KTOKK' wa_tab-ktokk.
PERFORM bdc_field USING 'BDC_OKCODE' '= AUSW'.
CALL TRANSACTION 'XK01' USING i_bdc MODE 'N'. " UPDATE 'S' MESSAGES
"INTO i_message.
REFRESH i_bdc.
ENDLOOP.
IF sy-subrc NE 0.
READ TABLE i_message WITH KEY msgtyp = 'E'.
IF sy-subrc = 0.
LOOP AT i_message INTO wa_message.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
id = i_message-msgid
lang = 'EN'
no = i_message-msgnr
v1 = i_message-msgv1
v2 = i_message-msgv2
v3 = i_message-msgv3
v4 = i_message-msgv4
IMPORTING
msg = p_text
EXCEPTIONS
not_found = 1
OTHERS = 2.
WRITE:/ p_text.
ENDLOOP.
ENDIF.
ENDIF.
*& Form bdc_dynpro
text
-->PROGRAM text
-->DYNPRO text
FORM bdc_dynpro USING program dynpro.
CLEAR wa_bdc.
wa_bdc-program = program.
wa_bdc-dynpro = dynpro.
wa_bdc-dynbegin = 'X'.
APPEND wa_bdc TO i_bdc.
ENDFORM. "bdc_dynpro
*& Form bdc_field
text
-->FNAM text
-->FVAL text
reward if u find useful
regards
Nagesh.Paruchuri

Date formats for SQL statements used by recordset object

Hi,
Date formatting appears to be quite problematic for Business One. I did a forum search for date issues and I don't think I saw any of them with an "answered" status. I have an issue with formatting a date for the creation of an SQL statement that the DI sends to SQL Server 2005. I need to format a date so that the localization parameters don't matter for either the client machine or SQL Server's machine. We don't have a problem as long as our machines are localized as USA.
I have PL 22 and I have a form - ours - where I use the Today() function to fill a date field. So this is a date that is not entered by the user. The result of this function is consistent with the localization parameters on my machine. We have two other date fields on the form where the user must type in the date.
As a test, I changed my machine to the UK parameters. I then set up the language parameters of Business One for English(United Kingdom). I changed the date format specifications in Business One so that its format is dd/mm/yy. I then brought up the form and the field that is formatted by the above function arrived in the form's field as dd/mm/yy. I then typed in the two other dates in the same format and added the record to the database. The form's table is user-defined.
I dismissed the form then brought it back up loaded with the new record. The date that was entered by the function appeared in USA format (mm/dd/yy). The dates that were typed in appeared in the Business One format (dd/mm/yy). This of course is not consistent.
When I looked at what got into the database, the formats were the opposite. Weird! To make matters really confusing, I run an SQL statement within SQL Server Mgt Studio, and use the WHERE clause to filter on the date that was based on the function. It didnt matter what format I used for the WHERE clause, the record came up. Does anyone have any idea about how I can ensure that I always use the correct date format for SQL statements passed by Business One to SQL Server regardless of where in the world the application is being run?
Thanks,
Mike

Ian,
Here's what I'm concerned about: Im using the date in a WHERE clause.
Assume the date is Aug 3, 2007.
"SELECT * FROM Table WHERE StartDate > 8/3/2007"
OR
"SELECT * FROM Table WHERE StartDate > 3/8/2007"
If the client machine is set up as USA, the today function will provide the date as formatted in the first query. If the database server is setup as lets say the UK, I believe that SQL Server query parser will interpret the date as Mar 8, 2007.
If the client machine is set up as UK, the today function will provide the date as formatted in the second query. If the database server is setup as lets say USA, I believe that SQL Server query parser will also interpret the date as Mar 8, 2007.
In both cases it would be wrong.
I know I could use the DATEPART function to get the three parts and this will make the code indifferent to the localization specs of the client machine. I need to then be able to concatenate those date parts for the WHERE clause so that the localization specifications of the database server dont matter.
Thanks,
Mike

To accept all date formats for variables

Hi,
I am getting a vadidation message on refresh of a query on entering European date format in the selection criteria "Please enter value in permitted format for variable XXXX"
I need date to accept all date formats for variables to execute query.
Currently US date format has been accomodated, On entering European date format i get the above validation message.
Please suggest how do i supress this validation message or any other thoughts on the same.
If anyone experienced the same before or applied any notes plz send the SAP Note number for the same. I am currently on BW 3.5.
Message was edited by:
tyson m

tyson,
why dont you control the date display through the user creation / user details option - then your date entries should sort themselves out.
Arun

How to change date format for prentation variable in Formula

Hi experts.._
I need to change date format for presentation variable in formula..
my dashbord date prompt format: mm/dd/yyyy(i have created one presentation variable for this prompt: pv_date)
now i need to show it as : month-dd-yyyy
Thanks in advance
Regards
Frnds

Hi Kishor...Thanks for reply...
But i need to change my precentation variable date formt...
i need to write one text like: 'Year to dd/month/yy' in one column formula..
So how can i achieve it..

How to change date format for prentation variable

Hi experts
In my prompt the date format is MM/DD/YYYY . I have created one presentation variable for that but i want to use this in Formula as well in Title as: DD-MON-YY
So how can i achieve it..
Thanks in advance
Regards
Frnds

Hi
i think this can't be done through any code like oracle uses to_char, to_date function.
Just follow this
http://oraclebizint.wordpress.com/2007/12/19/oracle-bi-ee-101332-dates-dates-and-dates/
With this, wherever you have this column, you will be getting this format dates..
if you don't want in reports you can change it by mentioning the data format for that paricular column in report, but for the same column, if you want different format at different places (for prompts), you can't do that..

Where does one manage date formats for display and input

the user specification is that dates be displayed as YYYY-MON-DD. Is there a config or properties file which contains the date format for display? Is there a calendar drop-down that can be positioned next to a date input field for a question on a screen?
Thanks,
Allan

Hi Allan,
Curious why the rule project wasn't created with "English (Canada)" initially? If your project is English (UK) with the default configurations for that locale, then I assume your currency values are appearing in OWD with the GBP symbol (£) instead of a dollar sign ($)?
As for the impact of switching… I highly recommend getting confirmation from the OPA Dev team before doing it, but in the meantime, if you wanted to experiment on your own with a separate test rulebase (as opposed to whatever formal rulebase you're working on), here are my observations from an initial look… (FYI, I'm an experienced OPA rulie, but I'm non-technical and not in the Dev team, so best to check with them!)
I poked around the language parser files and saw that English (UK) has an English (UK) verb list, whereas English (Canada) uses the English (US) verb list. The vast majority of verbs are identical in all the variations of English, however, there are a couple which differ. So if you've used any verbs which have a different spelling between the 2 lists, there may be some attribute text to tweak, e.g.
- English (UK): the person travelled to Australia
- English (US): the person traveled to Australia
- English (UK): the person cancelled the reservation
- English (US): the person canceled the reservation
I saw some other different files between English (Canada) vs English (UK), but didn't notice anything in them which I'd expect to impact the rulebase.
As for how it might impact other components:
* screens file and the properties file – May be some tweaking depending on how you addressed the verb spelling issue above.
* regression test files – May be some tweaking depending on how you addressed the verb spelling issue above.
* messages.(locale).properties – The default messages.(locale).properties file appears to be based on the Language setting of the Project. I just tested this and OWD used a different messages.(locale).properties file when I changed the Project Language (OPM | File menu | Project Properties | Common Properties | General | Language).
* Siebel Connector – don't know what the impact would be.
OPA Dev team – Can you review what I've said here? And add any relevant further detail?
Cheers,
Jasmine

Supported date formats for sorting

Can someone point me to a document describing the supported
date formats for sorting? I mean, how should I format a date column
in an XML dataset in order to have this column correctly sorted
using the Spry framework?
Thank you and sorry if the question is trivial.

Thanks, what I have done for the moment as a temporary
solution is to use the two date formats and have them both inside
the one cell in the table (the column for the sortable date
yyyy-mm-dd). In my CSS I have created a style for the first date
that has it's visibility as hidden. That way it's sorting the Date1
but only Date2 is being shown to the users as the other cells have
more than one line of text it doesn't look too off centre.
<div spry:region="ds2">
<table width="662">
<tr>
<th width="127" class="eventhead"
spry:sort="Date1">Date</th>
<th width="151" class="eventhead"
spry:sort="Type">Type</th>
<th width="146" class="eventhead"
spry:sort="Title">Title</th>
<th width="189" class="eventhead"
spry:sort="Venue">Venue</th>
</tr>
<tr spry:repeat="ds2" spry:setrow="ds2">
<td height="53" class="event">{Date2}<span
class="eventhide">{Date1}</span></td>
<td class="event">{Type}</td>
<td class="event">{Title}</td>
<td class="event">{Venue}</td>
</tr>
</table>
</div>
</div>
It seems to be working for the moment...

Date Format for Language

Hi all,
is there any possibility to customize the default date format for the portal for the languages?
When I set the user language to EN, date format for EN is default MM/dd/yyyy. I would like to have dd MMM yyyy (like 12 Aug 2005).
Thanks in advance
balop

Hi peter,
         I thought you wanted to change the date format in the webdynpo implementation(coding).Now I got what you wanted ie date in ur reqd format from the picker UI itself.
         I really dont see much support in Webdynpro Date picker UI as of now for ur requirement.
        Anyway thanks for giving me a good question to think )
Rdgs,
G

CalendarUI element showing different date format for different locations

Hi,
I have an input field with date calendar in my webdynpro Java form . User can select date from this calendar and fill the input field. For this I have used input field in my layout and have binded this with one context attribute of type date. Say name of this field is requiredByDate
Now when I build and deploy my code, I can see the the required By date field and user is able to select date values from the calendar button next to the input field. The format of the date selected is mm/dd/yyyy.
However , when a user tests this application from other location say Malaysia, for him the format is coming as dd/mm/yyyy after selecting the date from the calendar.
Just want to know ,is there is difference in date format for differnt locations ? For India, when you select the date its showing mm/dd/yyyy and for Malayisa its showing dd/mm/yyyy.
Is there anything we can do by changing our system settings like timezone or dateformat in system settings.
I am using standard UI element and binding it with context element of type date.
Need your advice or help on this..
Thanks and regards,
Sai

Hi,
go to
[http://help.sap.com/saphelp_nw04/helpdata/en/f4/d95664da179b4db731e21c2e470b72/frameset.htm|http://help.sap.com/saphelp_nw04/helpdata/en/f4/d95664da179b4db731e21c2e470b72/frameset.htm]
It describes the fallback sequence followed by the Web Dynpro for Java Runtime in order to determine the current session locale.
Regards
Matteo

Date format for call transaction

Similar Messages

Maybe you are looking for