Validating Date Parameter

Dear friends,
I want to validate a user parameter (named ENDDATE) in my runtime parameter form (Report 6) with format 'YYYYMMDD', I am wondering if someone would give me some hint about how to write the condition:
function ENDDATEValidTrigger return boolean is
begin
if ( the condition ENDDATE is not format 'YYYYMMDD') then
return (FALSE);
end if;
return (TRUE);
end;
Any help is greatly appreciated!
Judy

In addition to provided list of format masks - you may just type your own in the Input Mask field.
From Reports help:
"If you enter a new format mask and accept the property sheet, the new value will appear in the list. However, these format masks are only valid during the current Report Builder session. If you quit Report Builder and then invoke it again, the list of values will not contain the format masks you created in the previous Report Builder session (unless you open the report(s) that used these masks). To add new format masks to the list that will be saved between sessions, use the Edit Masks button in the Preferences dialog."
Slava.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Judy:
Dear Oracle Reports Team jls,
Thanks for your reply, I tried what you told before, but I couldn't set the input mask as YYYYMMDD, since YYYYMMDD is not on the list (Oracle Developer 6.0). Any other ideas? I'd really appreciate it.
Best regards.
Judy
<HR></BLOCKQUOTE>
null

Similar Messages

Validating Date parameter in discoverer

Hi
In the discoverer is it possible to validate or restrict the users to enter the wrong format of the date e.g. if the date format to be entered is dd-mm-yyyy, the system should not allow the users to enter mm-dd-yy,
Is it possible to put any validation?
As of now what is happening is discoverer is not telling me any thing after running for few minutes i am not getting any result, after that if i check i found that the date is in the wrong format
Regards
Ramesh Kumar S

Hi
If I may throw an aside in here. If your users are using 10.1.2 Plus there should be no need for users to key anything into any date parameter because Discoverer now has a calendar for this use. I find it much easier to teach my users to use a calendar than to try and teach them how to key dates in correctly.
One other thing you might want to consider if you have not already done so is to standardize a date format across your entire Discoverer installation. Then the date format will be obvious because its the same one they see all of the time.
Nevertheless, if you still want a mechanism to trap what users are keying it is possible to create functions that trap formats displaying appropriate error messages.
Best wishes
Michael

How to pass a date parameter(from a procedure IN) to a API

Hi,
CREATE OR REPLACE package body xxal_basic_sal_increment_pkg1 as
procedure emp_pro_inc1(ERRBUF VARCHAR2,RETCODE OUT NUMBER,
p_business_group_id_enter in number,p_change_date in varchar2) is
CURSOR STAFF IS
SELECT pp.ASSIGNMENT_ID
,peo.EMPLOYEE_NUMBER employee_no
,pp.OBJECT_VERSION_NUMBER
,pp.PAY_PROPOSAL_ID
,pp.PROPOSED_SALARY_N basic_salary
,pp.PROPOSAL_REASON
,pp.change_date
,pp.BUSINESS_GROUP_ID
,pg.name
,pr.PERFORMANCE_RATING,
'' v_effective_start_date,
'' v_effective_end_date
FROM per_all_people_f peo,
per_all_assignments_f pa,
per_pay_proposals pp,
per_grades_tl pg,
per_performance_reviews_v pr
where pa.person_id = peo.PERSON_ID
and pa.ASSIGNMENT_ID = pp.ASSIGNMENT_ID
and peo.PERSON_ID=pr.PERSON_ID
and pg.GRADE_ID=pa.GRADE_ID
--and peo.EMPLOYEE_NUMBER=STAFF_VAR.employee_no
and sysdate between peo.EFFECTIVE_START_DATE and peo.EFFECTIVE_END_DATE
and sysdate between pa.EFFECTIVE_START_DATE and pa.EFFECTIVE_END_DATE
and peo.BUSINESS_GROUP_ID = p_business_group_id_enter
and pp.change_DATE = (select max(change_DATE) from per_pay_proposals temp
where ASSIGNMENT_ID =pp.ASSIGNMENT_ID);
--L_BUSINESS_GROUP_ID NUMBER:=5128;
L_ASSIGNMENT_ID NUMBER;
L_PAY_PROPOSAL_ID NUMBER;
L_OBJECT_VERSION_NUMBER NUMBER;
L_pyp_proposed_sal_warning BOOLEAN;
L_additional_comp_warning boolean;
l_person_id number;
L_COMMON boolean;
L_ELEMENT_ENTRY_ID NUMBER;
TEMP NUMBER;
L_EFFECTIVE_START_DATE DATE;
L_MULTI VARCHAR2(30):='N';
L_APPROVED VARCHAR2(30):='Y';
L_CHANGE_DATE DATE:=TO_DATE('31-JAN-2008','DD-MON-YYYY');
BEGIN
v_disp_output:='EMPLOYEE_NUMBER'||','||
'BASIC'||','||
'EFF START DATE'||','||
'EFF END DATE';
fnd_file.put_line(FND_FILE.output,v_disp_output);
FOR STAFF_VAR IN STAFF LOOP
L_ELEMENT_ENTRY_ID:=null;
begin
select assign.assignment_id,assign.effective_start_date into
l_assignment_id,l_change_date_new
from per_people_f peo,per_assignments_f assign
where peo.person_id=assign.person_id
and sysdate between peo.effective_start_date and peo.effective_end_date
and sysdate between assign.effective_start_date and assign.effective_end_date
and current_employee_flag='Y'
and primary_flag='Y'
and peo.business_group_id=l_business_group_id
and peo.employee_number=staff_var.employee_no;
L_CHANGE_DATE_new:=L_CHANGE_DATE;
--L_CHANGE_DATE_new:=STAFF_VAR.v_effective_start_date;
begin
HR_MAINTAIN_PROPOSAL_API.INSERT_SALARY_PROPOSAL
P_PAY_PROPOSAL_ID=>L_PAY_PROPOSAL_ID
,P_ASSIGNMENT_ID=>staff_var.ASSIGNMENT_ID
,P_BUSINESS_GROUP_ID=>staff_var.BUSINESS_GROUP_ID
,P_CHANGE_DATE=>L_CHANGE_DATE_new
,P_PROPOSED_SALARY_N=>STAFF_VAR.basic_salary
,P_OBJECT_VERSION_NUMBER=>STAFF_VAR.OBJECT_VERSION_NUMBER
,p_multiple_components=>L_MULTI
,p_approved=>L_APPROVED
,P_VALIDATE=>false
,p_element_entry_id =>L_ELEMENT_ENTRY_ID
,P_INV_NEXT_SAL_DATE_WARNING=>l_common
,P_PROPOSED_SALARY_WARNING=>L_COMMON
,P_APPROVED_WARNING=>L_COMMON
,P_PAYROLL_WARNING=>L_COMMON
in the above code the variable L_CHANGE_DATE DATE is hard coded .
but we need to supply this variable value as dynamic, means (p_change date--procedure IN Parameter )
i tried like below ,
CREATE OR REPLACE package body xxal_basic_sal_increment_pkg1 as
procedure emp_pro_inc1(ERRBUF VARCHAR2,RETCODE OUT NUMBER,
p_business_group_id_enter in number,p_change_date in varchar2) is
CURSOR STAFF IS
SELECT pp.ASSIGNMENT_ID
,peo.EMPLOYEE_NUMBER employee_no
,pp.OBJECT_VERSION_NUMBER
,pp.PAY_PROPOSAL_ID
,pp.PROPOSED_SALARY_N basic_salary
,pp.PROPOSAL_REASON
,pp.change_date
,pp.BUSINESS_GROUP_ID
,pg.name
,pr.PERFORMANCE_RATING,
'' v_effective_start_date,
'' v_effective_end_date
FROM per_all_people_f peo,
per_all_assignments_f pa,
per_pay_proposals pp,
per_grades_tl pg,
per_performance_reviews_v pr
where pa.person_id = peo.PERSON_ID
and pa.ASSIGNMENT_ID = pp.ASSIGNMENT_ID
and peo.PERSON_ID=pr.PERSON_ID
and pg.GRADE_ID=pa.GRADE_ID
--and peo.EMPLOYEE_NUMBER=STAFF_VAR.employee_no
and sysdate between peo.EFFECTIVE_START_DATE and peo.EFFECTIVE_END_DATE
and sysdate between pa.EFFECTIVE_START_DATE and pa.EFFECTIVE_END_DATE
and peo.BUSINESS_GROUP_ID = p_business_group_id_enter
and pp.change_DATE = (select max(change_DATE) from per_pay_proposals temp
where ASSIGNMENT_ID =pp.ASSIGNMENT_ID);
--L_BUSINESS_GROUP_ID NUMBER:=5128;
L_ASSIGNMENT_ID NUMBER;
L_PAY_PROPOSAL_ID NUMBER;
L_OBJECT_VERSION_NUMBER NUMBER;
L_pyp_proposed_sal_warning BOOLEAN;
L_additional_comp_warning boolean;
l_person_id number;
L_COMMON boolean;
L_ELEMENT_ENTRY_ID NUMBER;
TEMP NUMBER;
L_EFFECTIVE_START_DATE DATE;
L_MULTI VARCHAR2(30):='N';
L_APPROVED VARCHAR2(30):='Y';
L_CHANGE_DATE DATE:=TO_DATE(p_change_date,'DD-MON-YYYY');
BEGIN
v_disp_output:='EMPLOYEE_NUMBER'||','||
'BASIC'||','||
'EFF START DATE'||','||
'EFF END DATE';
fnd_file.put_line(FND_FILE.output,v_disp_output);
FOR STAFF_VAR IN STAFF LOOP
L_ELEMENT_ENTRY_ID:=null;
begin
select assign.assignment_id,assign.effective_start_date into
l_assignment_id,l_change_date_new
from per_people_f peo,per_assignments_f assign
where peo.person_id=assign.person_id
and sysdate between peo.effective_start_date and peo.effective_end_date
and sysdate between assign.effective_start_date and assign.effective_end_date
and current_employee_flag='Y'
and primary_flag='Y'
and peo.business_group_id=l_business_group_id
and peo.employee_number=staff_var.employee_no;
L_CHANGE_DATE_new:=L_CHANGE_DATE;
--L_CHANGE_DATE_new:=STAFF_VAR.v_effective_start_date;
begin
HR_MAINTAIN_PROPOSAL_API.INSERT_SALARY_PROPOSAL
P_PAY_PROPOSAL_ID=>L_PAY_PROPOSAL_ID
,P_ASSIGNMENT_ID=>staff_var.ASSIGNMENT_ID
,P_BUSINESS_GROUP_ID=>staff_var.BUSINESS_GROUP_ID
,P_CHANGE_DATE=>L_CHANGE_DATE_new
,P_PROPOSED_SALARY_N=>STAFF_VAR.basic_salary
,P_OBJECT_VERSION_NUMBER=>STAFF_VAR.OBJECT_VERSION_NUMBER
,p_multiple_components=>L_MULTI
,p_approved=>L_APPROVED
,P_VALIDATE=>false
,p_element_entry_id =>L_ELEMENT_ENTRY_ID
,P_INV_NEXT_SAL_DATE_WARNING=>l_common
,P_PROPOSED_SALARY_WARNING=>L_COMMON
,P_APPROVED_WARNING=>L_COMMON
,P_PAYROLL_WARNING=>L_COMMON
but we are getting the error Cause: FDPSTP failed due to ORA-01839: date not valid for month specified
ORA-06512: at "APPS.XXAL_BASIC_SAL_INCREMENT_PKG1", line 45
ORA-06512: at line 1
we tried the solution available in the metalink still its giving error ..
pl help us to solve this issue ...
how should we pass the date parameter while we run the concurrent program(we used date value set).
also we tried with some other value set also ..
Regards,
kumar

dear,
I have the following code to create proposal, but the API create salary proposal for all record s and does not create entry for all records it just creates for the first record
any advice
the code ....
/* Formatted on 2007/08/29 16:20 (Formatter Plus v4.8.8) */
----------------------- P R O P O S A L -------------------------
DECLARE
l_rows_processed NUMBER := 0;
l_commit_point NUMBER := 500;
l_business_group_id NUMBER
:= fnd_profile.VALUE ('PER_BUSINESS_GROUP_ID');
l_proposal_salry NUMBER;
l_approved CHAR (1);
l_rowid VARCHAR2 (30);
l_errmessage VARCHAR2 (400);
l_entry_indecator NUMBER;
l_assignment_id NUMBER;
p_ctr_object_version_number NUMBER;
-- Out Parameters --
l_element_entry_id NUMBER;
p_element_entry_id NUMBER;
l_ctr_object_version_number NUMBER;
l_pay_proposal_id NUMBER;
l_inv_next_sal_date_warning BOOLEAN;
l_proposed_salary_warning BOOLEAN;
l_approved_warning BOOLEAN;
l_payroll_warning BOOLEAN;
CURSOR crs_dc_mn
IS
SELECT xdp.ROWID, xdp.assignment_id, xdp.change_date,
xdp.proposal_reason, xdp.proposed_salary,
xdp.assignment_number, xdp.employee_number, xdp.person_id,
xdp.new_asg_id
FROM apps.xx_dc_proposal xdp
WHERE xdp.assignment_id <> -1
AND xdp.processed = 'N'
AND xdp.change_date =
(SELECT MIN (xdc.change_date)
FROM xx_dc_proposal xdc
WHERE xdc.assignment_id = xdp.assignment_id
AND xdc.processed = 'N')
ORDER BY assignment_id, change_date ASC;
pro_rcrd crs_dc_mn%ROWTYPE;
CURSOR crs_dc_proposal1 (p_asg_id IN NUMBER)
IS
SELECT xdp.ROWID, xdp.assignment_id, xdp.change_date,
xdp.proposal_reason, xdp.proposed_salary,
xdp.assignment_number, xdp.employee_number, xdp.person_id,
xdp.new_asg_id
FROM apps.xx_dc_proposal xdp
WHERE xdp.assignment_id <> -1
AND xdp.processed = 'N'
AND xdp.assignment_id = p_asg_id
ORDER BY assignment_id, change_date ASC;
BEGIN
OPEN crs_dc_mn;
FETCH crs_dc_mn
INTO pro_rcrd;
LOOP
BEGIN
hr_maintain_proposal_api.insert_salary_proposal
(p_pay_proposal_id => l_pay_proposal_id,
p_assignment_id => pro_rcrd.assignment_id,
p_business_group_id => l_business_group_id,
p_change_date => pro_rcrd.change_date,
p_comments => NULL,
p_next_sal_review_date => NULL,
p_proposal_reason => NULL,
p_proposed_salary_n => pro_rcrd.proposed_salary,
p_forced_ranking => NULL,
p_performance_review_id => NULL,
p_attribute_category => NULL,
p_attribute1 => NULL,
p_attribute2 => NULL,
p_attribute3 => NULL,
p_attribute4 => NULL,
p_attribute5 => NULL,
p_attribute6 => NULL,
p_attribute7 => NULL,
p_attribute8 => NULL,
p_attribute9 => NULL,
p_attribute10 => NULL,
p_attribute11 => NULL,
p_attribute12 => NULL,
p_attribute13 => NULL,
p_attribute14 => NULL,
p_attribute15 => NULL,
p_attribute16 => NULL,
p_attribute17 => NULL,
p_attribute18 => NULL,
p_attribute19 => NULL,
p_attribute20 => NULL,
p_object_version_number => l_ctr_object_version_number,
p_multiple_components => 'N', -- 918219
p_approved => 'Y',
p_validate => FALSE,
p_element_entry_id => l_element_entry_id,
p_inv_next_sal_date_warning => l_inv_next_sal_date_warning,
p_proposed_salary_warning => l_proposed_salary_warning,
p_approved_warning => l_approved_warning,
p_payroll_warning => l_payroll_warning
UPDATE xx_dc_proposal
SET processed = 'Y'
WHERE ROWID = pro_rcrd.ROWID;
l_rows_processed := l_rows_processed + 1;
IF l_rows_processed = l_commit_point
THEN
COMMIT;
l_rows_processed := 0;
END IF;
EXCEPTION
WHEN OTHERS
THEN
l_errmessage := SQLERRM;
UPDATE xx_dc_proposal
SET err_message = l_errmessage
WHERE ROWID = pro_rcrd.ROWID;
END;
END LOOP;
CLOSE crs_dc_mn;
COMMIT;
END;
..............................

Web template :Error Valid Data provider not assigned

Hello Friends we have the web template that was working before , we did the upgrade to SP13 from SP11.
It gives the error Valid Data provider not assigned and
Bad integer Parameter value of Parameter BLOCK_COLUMNS_SIZE of Object item:ANALYSIS_ITEM:ANALYSIS;
Please help where do i need to assign the Data provider beacuse the Values are same for Dataprovider as before
Portal Runtime Error
An exception occurred while processing your request
Exception id:
See the details for the exception ID in the log file.
Thanks
Soniya
Message was edited by:
soniya kapoor

Open the template in WAD and do a validation against the server and make sure the template is well formed.
Also make sure you apply BI JAVA Patch 1 for SPS 13.

Date Parameter in BIP

Hi
I have compiled a report in BI publisher. As part of reports i have also configured LoVs and Parameter (Date). Whenever i open the report from Excel Analyzer and going to define date parameter for filtering. I get the following error:
Runtime error '1004' : The name that you entered is not valid
I have set the Date string as: yyyy-mm-date and i am entring the string as: 2009-08-26
Even the calendar attached with Date field in BI publisher does not work properly, if i select 1 jan, 2009 from calendar then what i get in the field is 2009-14-01
Thanks in advance for your prompt response
Regards
Perhiya

Try using date format as yyyy-MM-dd and resave your report . It should work.

Crystal Reports Date Parameter Problem

Hello Experts,
I have this query in crystal, I need it to be suming the Quantity and Totals but because of the date optional its not doing that, How I put the date parameter and remove it from her so that I can achieve my results.
SELECT T0.[DocDate],T1.[Dscription] as 'BRANDS /SKU', Sum(T1.[Quantity]) as 'QTY', Sum(T1.[LineTotal]) as 'VALUE' FROM OINV T0 INNER JOIN INV1 T1 ON T0.DocEntry = T1.DocEntry INNER JOIN OCRD T2 ON T0.CardCode = T2.CardCode WHERE T2.[GroupCode] = '100' GROUP BY T1.[Dscription],T0.[DocDate]
Thanks,
Titi

Hi Titi,
I don't really get what your question is but I can suggest to add the date parameter on WHERE clause. In case it's optional, you can put validation checking before entering query. When it's null you set a period of time which is relevant to current date. And as replied by GordonDu, the parameter is compare to T0.DocDate
Hope it helps.

FM for validating date coming from a file

HI All,
I have to validate date that needs to be validated before passing it to DB.
Is der any FM for same
I tried CONVERT_DATE_TO_INTERNAL.
But it accepts date only in one specified format.

hi,
try this
Use Function module DATE_CHECK_PLAUSIBILITY to validate a date.
1)If you given a invalidate date then it will ask you to enter a valid date.
2)After changing it to correct value, you can click on SAVE button or if you want to continue with the invalid date then click on USE INVALID VALUE button.
Try with this code.
PARAMETER P_DATE TYPE SYDATUM.
CALL FUNCTION 'DATE_CHECK_PLAUSIBILITY'
EXPORTING
date = P_DATE
EXCEPTIONS
PLAUSIBILITY_CHECK_FAILED = 1
OTHERS = 2.
IF sy-subrc 0.
MESSAGE E000(ZI) WITH 'INPUT DATE IS INVALID DATE'.
ENDIF.
Regards,
RItesh J

User validity date is not refelcting in Childsystem

Hi Experts,
I have changed the validity of a user in CuA system . But the validity is not reflecting in child system. on checking SCUL I found the error as " User type 75 is not actiive". I didnot find any issues in distributing roles and profiles for this user in CUA.only for user valdity I am reciving this error. Please advice how this error can be rectified. In SCUM the distribution parameter is global for user valdity. I need to know the root cause for this error.
Thanks,
Sanjeev.S

Hi Sanjeev,
Why dont you identify user master data that has not been changed from the central system and distribute it again where necessary.
You can do all this from SCUL
Look at the following SAP notes :
632486
First of all check if that user is existing in the child system and is active or expired:
Some times the user might have been deleted in the backend system and you are tyring to change the validity date of the user only on the CUA system because he exists only in the CUA box.
I strongly think that the user record is manually deleted in the child system
Please try to perform this action for another user who exists and see if its happening the same way.
if it does not.
Go to the child system and delete the user completely and recreate the user one more time in CUA and see what happens.
Edited by: Franklin Jayasim on Jun 29, 2010 7:04 PM

BPEL stored procesure call error about date parameter.

When we call stored procedure including date parameter from dbadapter servive inside Oracle BPEL (10.1.3.3) engine
we have taken folowing exception. (\opmn\log\default_group~oc4j_soa~default_group~1.log)
08/11/17 13:25:36 oracle.xml.parser.v2.XMLElement@15e52e5
08/11/17 13:25:36 ORA-00921: unexpected end of SQL command
is there anywhere (log files) we can see SQL statement coused error.
How can we correct this error.
Thanks.

Is the DATE parameter IN or IN/OUT? If so then the first thing you should check is to see if your XML is valid. Date is represented by java.sql.Timestamp and should adhere to the XML Schema definition for dateTime, which is YYYY-MM-DDTHH:mm:ss. The error seems to be coming from the XML parser which could mean that you instance value for your DATE parameter is the wrong syntax.

Can we pass data-parameter in host

Can we pass a data-parameter to a report using host command in the form.
urgent please
vishal

Your answer is quite correct, but it is stupid behavior - how do you build backwards compatibility into a function if you have to specify the keyword 'default'?
For example, I have an existing function that takes one parameter, but I need to alter it to take two parameters. I work for a large bank that has a rigorous change management process, and this function resides in the data warehouse, so many
people can use this function in their code, and I need to ensure that any changes I make are backwards compatible, and don't break any existing code that I don't know about.
If this was a stored proc, I could call it without the optional parameter, and the default value would be applied, but a function needs me to specify the keyword 'default' or to provide a value.
My only option seems to be to create a wrapper function that calls either the old function (if only one parameter is provided) or the new function (if both parameters are provided). Sort of defeats the purpose of having default or optional values.

Unit Testing: Supplying SYSDATE on a DATE parameter

hi all,
I have a procedure that I'm unit testing and one of the parameter is date, I want to supply a dynamic value to it relative to sysdate but SQL Developer only accepts hard coded date values. Does anyone know how I can supply SYSDATE or SYSDATE-50 to a date parameter directly. I can already solve this by using a wrapper procedure, just wondering if there's a solution to directly supply the value.
Thanks,
Alfredo

Hi Kranthi.
1. Assuming you are with Plus you can make the parameters optional in the parameters screen (tools -> parameters)
so that if they get NULL as value they will return all data.
2. the second way is if you like to keep it mandatory is to define a default value for the parameter and then take care of the situation in the condition.
for example you'll define the 1-Jan-1900 as your default date for the from_date.
Then in the condition change if you'll define it just as from_date > :P_from_date then you got what you wanted.
BTW In similar situations when you are dealing with varchar you can do a manipulation such as:
from_date > :P_from_date
Or
:P_from_date = '1-Jan-1900'
Tamir

How to pass a date parameter from report builder query designer to oracle database

i'm using report builder 3.0 connected to oracle database. i'm trying to pass a date parameter in the query with no success, i don't
know the exact syntax. I've tried :
SELECT * FROM igeneral.GCL_CLAIMS where CREATED_BY IN (:CREATED_BY) AND CLAIM_YEAR IN(:UW_YEAR) AND (LOSS_DATE) >To_Date('01/01/2014','mm/dd/yyyy')
it worked perfectly.
However if i try to put a date parameter "From" instead of 01/01/2014 it will not work, a Define Query Parameter popup window appear and error occurred after i fill
the values (usually i shouldnt get this popup i should enter the value when i run the report)
SELECT * FROM igeneral.GCL_CLAIMS where CREATED_BY IN (:CREATED_BY) AND CLAIM_YEAR IN(:UW_YEAR) AND (LOSS_DATE) >To_Date(:From,'mm/dd/yyyy')
appreciate your assistance

Hi Gorgo,
According to your description, you have problem when in passing a parameter for running a Oracle Query. Right?
Based on my knowledge, it use "&" as synax for parameter in Oracle, like we use "@" in SQL Server. In this scenario, maybe you can try '01/01/2014' when inputing in "From". We are not sure if there's any limitation for To_Date()
function. For your self-testing, you can try the query in sqlplus/sql delveloper. Since your issue is related to Oracle query, we suggest you post this thread onto Oracle forum.
Best Regards,
Simon Hou

How to pass date parameter from one page to other in BSP application

Hello gurus,
In my BSP application i have taken an input field and made its type "date" and its value also of type date and have set showhelp .
Now once a particular date is given as an input i want to pass its value to next page. And in next page i have to fire a query based on the date entered in previous page...
Now my prb is that my date value is not getting passed to the next page.
I have used
navigation->set_parameter( name = 'BEGDA' value = BEGDA ).
to pass date parameter.....still parameter is not getting passed.
plz help me with this.....
thankx.....

Hi Eddy,
By truncation i mean the entire date becomes 10 char including the ' . ' eg(06.12.2006).
so with begda being 8chars it takes my date as 06.12.200
as a result my query is not getting executed.
now i have tried to use a FM 'CONVERT_DATE_TO_INTERN_FORMAT'.
in my 1st page but still in 2nd page its giving me following error.
<b>The data that was read could not be written to the specified target field during a SELECT access. Either the conversion is not supported for the type of the target field, or the target field is too short to accept the value, or the data is not in the appropriateformat for the target field.
</b>
Regards
Swati

Sending Date parameter from the form to Report

Dear Friend
Hi everybody, I am sending the date parameter to my report through a form ,and my date format in the form and in the report as follow : DD/MM/YYYY but when I enter the date as 18/1/2004 the system pass this value as follow : 18-JAN-04 but I want the system to pass my date format as 18/1/2004 not as 18-JAN-04 ,how can I do that
Best regards
Jamil

Ino,
thanks for your answer.
You're all rigth abouth the index issue. So I've written my SQL like you say in your post. But i get an error : "ORA-... Non-character found where character expected... " or something like that. I've checked nls_date_format in my client machine and the server (DB 8.1.7.4), and also the regional settings in both machines, and all are set to 'DD-MON-YY'. What can be wrong?
Thanks again for your time.
Jaime.

Passing date parameter from forms to report

Hi,
I'm using forms and reports 6i.
I want to pass one date parameter from forms to reports.
Using
Add_Parameter(pl_id,'P_FROM_DATE',TEXT_PARAMETER,:FROM_DT);
giving me error REP-0091- Invalid value for parameter 'P_FROM_DATE'
This i think is because report expects date and here it is converted as varchar.
Please help

Hi Divya,
Even I use this kind of statement
Add_Parameter(pl_id,'P_FROM_DATE',TEXT_PARAMETER,:FROM_DT);and works fine for me.
This i think is because report expects date and here it is converted as varchar
Correct.
Open the report in the builder and under Data Model -> User Parameters, Go to the Property Inspector of P_FROM_DATE. Under Parameter, set Datatype as Character instead of Date.
Hope this should work. and tell me if it works(coz it wokred for me).

Validating Date Parameter

Similar Messages

Maybe you are looking for