Alpha Conforming Values Error 5323,1461....

Hi All,
I am facing the problem with info object of vendor alpha conforming values error..
I got 53 record errors in PSA level.
Please tell me how to solve this issue.
It's very urgent . plz help to me.
I was checked the Transfer rule alphs Conv check box for vendor.But showing same errors.
Thanks & Regards,
Guna.

Hi,
i am extracting the datafrom R/3 using data source 2lis_05_q0task.
I am getting the error is:-
InfoObject VENDOR does not contain alpa-conforming value 5323.
like that i got few more values like 1461,1561,1643....
Please give me solution how to solve this issue.
Thnaks,
guna
Edited by: gunasekhar raya on Jan 23, 2008 2:25 PM

Similar Messages

Error: InfoObject does not contain alpha-conforming value 20030729

Hi everyone,
I got this problem, that i tried to fix yesterday, but all i did was that i got realy frustrated...
I created an infoobject which is copy of 0DOC_NUMBER and has alpha coversion routine.
Mapping field in DataSource is also type character 10(VBELN) as my infoobject.
But there are some values in this field that i am trying to load, less then 10 characters long (20030729,20051116...) and shouldn't be there, because the values are dates and not document numbers.
But anyway on R/3 side this values are in field which is defined as character 10 (VBELN), and when I am trying to load Infopackage(17500 records) I get 52 errors: InfoObject does not contain alpha-conforming value 20030729.
I don't get it, since both fields are type character 10 and the values are only digits, why do I get this error message and how can I fix it?
PS:One solution is to remove alpha conversion routine from infoobject, but i don't want that.
Regards,
Uro

hi,
sorry... correction, it's 'Exclusive attributes' that cannot be used for navigational attribute, you can set lower case to differentiate ... check the impact of lower case setting here ...
http://help.sap.com/saphelp_bw33/helpdata/en/b7/f470375fbf307ee10000009b38f8cf/frameset.htm
Lowercase letters allowed / not allowed
If this indicator is set, the system differentiates between lowercase letters and capital letters when you use a screen template to input values. If this indicator is not set, the system converts all the letters into capital letters when you use a screen template to input values.
If you choose to allow the use of lowercase letters, you must be aware of what happens when you input variables:
If you want to use the characteristic in variables, the system is only able to find the values for the characteristic if the lowercase letters and the capital letters are typed in accurately on the input screen for variables. If, on the other hand, you do not allow the use of lowercase letters, any characters that you type onto the input screen, are converted automatically into capital letters.
Exclusive attributes:
If you select Exclusively Attributes, the created characteristic can be used only as a display attribute for another characteristic, and not as a dedicated characteristic in the InfoCube. Furthermore, you then cannot transfer the characteristic into InfoCubes. However, you can use it in ODS objects or InfoSets.

Infopack Error ( does not contain alpha conforming value 10)

When I try to run my infopack which pulla data from BW into APO, the data load fails with the error below:
"InfoObject /BIC/XXXX does not contain alpa-conforming value 10" when I click on the details icon, I get the following description.
Can somebody please throw some light on this as I am new to DP/BW. Appreciate your help if someone can help me with fixing this problem.
                                                                                Diagnosis
The system checked whether the loaded InfoObject value conforms to the
     conversion exit.The check failed.
For example:
The value '1' was loaded into an InfoObject with alpha exit, even though
     the value '0000000001' was expected.
System response
The load process has failed or the erroneous records are displayed in
     the monitor. This does not depend on how error handling is set up.
Procedure
Find out why the data does not conform to the conversion exit, and, if
     possible, correct the cause. Possible causes are errors in Business
     Content or an error in a customer exit in the source system.
If you cannot correct the problem, you have the option of removing the
     conversion exit on the InfoObject. However, since the system has already
     been converted, duplicates appear in the system again.
Thanks
Varun

Hello Varun,
BW expects your Key Figures to be stored in "alpha conforming format". This is can be roughly described as having 0s in front. For example, if your key figure value is 10, then the alpha conforming value of that is 000000000000000010 (assuming the number of chars in your KF is 18).
To correct the error do the following:
In your transfer rule in BW for InfoObject /BIC/XXXX, implement an ABAP routine that calls function module CONVERSION_EXIT_ALPHA_INPUT. Here an example of the ABAP code you should put in your transfer rule for /BIC/XXXX:
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    input         = TRAN_STRUCTURE-/bic/xxxx
IMPORTING
   OUTPUT        = RESULT.
Hope this helps. Please post again if you have questions.

Alpha non conforming value

hi gurus,
This ramesh. Please telme anybody HOW DO WE GET ALPHA NON CONFORMING VALUE (ERROR)? WHAT IT MEANS?

HI
You may not have alpha routine exists in transfer rules,please check your transfer rules for your data source,where you getting this error...in transfer rules you will get it in reght side of the left pane..please check against your info object..
and also,Please check alpha conversion has been done or not for this object..you can run it in transaction 'RSMDCNVEXIT'
Hope it helps
Thanks
Teja

Plz urgent alpha non confirmation error

I am getting this errror alpha non confirmation error
solution

Hi naresh kumar ch
Some times it happens because of Preceding Zeros
Just have a look @ the following links..
Re: Alpha non conforming value
Hope itz clear a little atleast...!
Thanks & Regards
R M K
***Assigning pointz is the only way of saying thanx in SDN ***
**Learning the thingz is never end process if u stop it will Be a devil if u continue it will be a divine***
> I am getting this errror alpha non confirmation
> error
>
> solution

Load ODS - InfoObject: InfoObject does not contain alpa-conforming value

Hello everybody,
I get following error while uploading from ODS to InfoObject.
InfoObject /BIC/ZHOUSENUM does not contain alpa-conforming value 0000000000000000004.
The data flow is as follows: Transactional InfoSource -> ODS -> InfoObject.
In the Transfer Rules before ODS I have marked the Conversion check box. The data is populated into ODS without any problems.
I can even activate the ODS, which reporting enabled.
When I browse the ODS table with the option check conversion exits unmarked, I can see the value '0000000000000000004'.
But the upload into InfoObject master data failes
Any help appreciated.
TIA
pawel

sap_all onboard.
I assume, this infosource is locked, due to the fact it was system generated.
On the other hand, there is a s-note 559763 which says:
If an InfoObject is filled with ALPHA exits from an R/3 System, the BW assumes that the data is to arrive in the internal ALPHA format and therefore does not convert the data.
I know, it is about R/3 as source system, but I assume the same would be for BW.
p.

InfoObject REQUESTER does not contain alpa-conforming value 1006152

Hello All,
I am trying to load data into ODS.
The load is failing at "Data Package 6" Record # 11140. I am getting following message at the failed record. -
"InfoObject REQUESTER does not contain alpa-conforming value 1006152".
I went ahead and checked this record # 11140, in PSA, in Package # 6. There the requester field is populated with "1006152" where it is expecting "Some description".
I went ahead and changed the START_ROUTINE. with
LOOP AT DATA_PACKAGE.
IF NOT DATA_PACKAGE-REQUESTER cs 'S'.
DELETE DATA_PACKAGE.
ENDIF.
ENDLOOP.
Expecting that these erroneous records will be removed and will get a successful load.
I am getting the same error message at the same record # and data-package number.
Any help is highly appreciated.
Thanks,
PK.

Hi
when u r having such a problem of Alpha numerical error in a particular for a particular record.Then u just write a Fomula into that Particular formula USE {TOUPPERCASE(REQUESTER)} & thenn reload to the Target...this will solve the problem...to my knowledge..
try this..
HOPE THIS HELPS
THNX
BI Learner.

InfoObject FORWAGENT does not contain alpa-conforming value 100.........

HI ALL,
Can someone through some light on resolving the issue
"InfoObject FORWAGENT does not contain alpa-conforming value 100............"
In "Details Tab" of the monitor screen
Requests (messages): Everything OK
Extraction (messages): Errors occurred --> data selection ended succesfully
T ransfer (IDocs and TRFC): Errors occurred -->some of the data packets not yet processed
Processing (data packet): Errors occurred --> while processing transaction data
InfoObject FORWAGENT does not contain alpa-conforming value 100............"
error occured
Please advice how to solve
Thanking you in advance,
Rase

Hi,
Use ALPHA conversion in the general tab of the infoobject FORWAGENT.
then load the data again.
also in the transfer strcture in the right most side tick the option " alpha....."
Thanks

SQL Error Code: 1461

We are currently facing a problem in which we are getting “SQL Error Code: 1461
java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column” . This issue is not happening always and only happens in the PROD environment. We tried to replicate this scenario in our QA and Local and where not able to reproduce it.
The scenario is we have a web application screen in which the user enters multiple data which includes textarea which supports upto 2000 characters and it is stored in database as varchar2 the other fields are stored as Number and clob datatype. Whenever we perform some changes in a textarea which is varchar2 (2000) in the database we are getting this ORA – 01461. However this scenario is only happening in PROD. In QA whenever the user enters more than 2000 characters the strut level validation handles it.
We are using Spring framework for DAO operations and the Spring Version is : 1.2.8 , oracle version 9i.
Oracle NLS setting
(SELECT * from NLS_SESSION_PARAMETERS)
PARAMETER,VALUE
NLS_LANGUAGE,AMERICAN
NLS_TERRITORY,AMERICA
NLS_CURRENCY,$
NLS_ISO_CURRENCY,AMERICA
NLS_NUMERIC_CHARACTERS,.,
NLS_CALENDAR,GREGORIAN
NLS_DATE_FORMAT,DD-MON-RR
NLS_DATE_LANGUAGE,AMERICAN
NLS_SORT,BINARY
NLS_TIME_FORMAT,HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT,DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT,HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT,DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY,$
NLS_COMP,BINARY
NLS_LENGTH_SEMANTICS,BYTE
NLS_NCHAR_CONV_EXCP,FALSE
Ojdbc.jar version Specification-Version: Oracle JDBC Driver version - "10.2.0.1.0"
Edited by: Sanu Sasidharan on Apr 6, 2010 11:20 PM

We further debugged this issue today and checked the ojdbc14.jar which is used in the QA and PROD environment.
The issues is happening with the jar, Specification-Version: Oracle JDBC Driver version - "10.2.0.1.0"
But in our QA we are using ojdbc14.jar Specification-Version: "Oracle JDBC Driver version - 9.0.2.0.0" in this version the issues is not happening. We replaced the 9.0 with 10.2 jar in our QA and we were able to reproduce this issue.
Hence we have localized the issue to be related to version.

ORA-0605: PL/SQL: numeric or value error: character string buffer too small

I get this error on two function activities in a workflow of mine. I don't even get into the pl/sql procedure call.
The exact error is:
Error Name -6502
Error Message: ORA-0605: PL/SQL: numeric or value error: character string buffer too small
Error Stack: @#@Wf_Engine_Util.Function_Call(MY_PACKAGE.MY_PROC, ITEM_TYPE, ITEM_KEY, 6519, RUN)
If I retry the step (expedite -> retry) it runs until it hits the second function which does the same thing (there is a function in between the two functions that do not have any issues). I then have to retry that step as well. Any ideas?
This seems similar to the following issue that does not have a resolution posted:
ORA-06502 PL/SQL numeric or value error in wf process
I've tried commenting out the bodies of the procedures called but that does not help (again -- im not getting into the bodies but im not sure what else it could be).
Any ideas or suggestions?

Hi,
Does this happen on every instance of the process, or just a few?
Are these activities in the middle, or right at the start of the flow?
Are any other activities being performed correctly first? If so, are these standard or bespoke?
My inclination would be that there is some kind of variable that is being populated (or concatenated onto), which is growing too big. When the process errors, it gets cleared, which is why an expedite would move the activity on.
Matt
WorkflowFAQ.com - the ONLY independent resource for Oracle Workflow development
Alpha review chapters from my book "Developing With Oracle Workflow" are available via my website http://www.workflowfaq.com
Have you read the blog at http://thoughts.workflowfaq.com ?
WorkflowFAQ support forum: http://forum.workflowfaq.com

How to display 'Alpha numeric values' in lower character?

Hi,
We have 'Alpha numeric value' in one column and i need to display alphabets in lower character.
I tried but throwing error.
SQL> select * from a439487.ora_dev_inventory;
HOST_NM HA INV_DT
SMMK94 - 21-AUG-08
SQL> select to_lower(HOST_NM) from a439487.ora_dev_inventory;
select to_lower(HOST_NM) from a439487.ora_dev_inventory
ERROR at line 1:
ORA-00904: "TO_LOWER": invalid identifier
I want 'HOST_NM' to be displayed in lower value.
I need o/p like 'smmk94'.
Any idea?

Where did you find the TO_LOWER function? Can you
show us?I would guess it was just an assumption based on the fact we have to_char, to_date, to_number...
;)

Alpha confirming value

while I am doing a load i am getting a Alpha-confirming value 6019999 RSAR 196 error message in Master data. But i have seen the info object setting it has got the alpha setting in it.
But what is the real problem does any can help.Pease...

Hi ,
Said error occurs due to the insufficient length of the data.
Use following function module in the transfer routine of the characteristic.
FM : CONVERSION_EXIT_ALPHA_INPUT.
Pass the characteristic object as input and collect the output in the resulting variable.
It will add required zeros before the 6019999 .
It will solve the problem.
Regards,
Aditya

InfoObject does not contain alpha confirming values

Hi ,
I am trying to load data into the object called ZAML_CODE, the type is CHAR and Length is 3.
The characteristic is enabled with ALPHA - Conversion exit.
we are loading data to this object since 3 years successfully.
But now only it is saying that InfoObject ZAML_CODE does not contain alpha confirming values.
Especially we are getting error for numeric values like 1, 2,3 etc only.
Previously numeric values were also loaded successfully.
Now the source system is ECC6.0, previously it was 4.6C. This is the only difference.
Please respond with your suggesions.
Regards
Srinivas

Hello,
Just check if there is space in the front of these numeric values or some garbage value...if there is... then it may not be able to pad it up with zero and hence the issue...check in R/3 about how these values are stored...you can remove the space from the front and change it in PSA...and then load but first do the analysis of the source system and see why its coming up wrong.
Regards
Ajeeet

Problem with error ORA-06502: PL/SQL: numeric or value error string

Hi,
I am running a loop to just spool output data using 'dbms_output.put_line' and I keep getting this error after a few records. I resorted it and it happen at a different interval. Could it have to do with the length of the item I am trying to spool? Thanks.
ORA-06502: PL/SQL: numeric or value error string

SD wrote:
Hi,
I am running a loop to just spool output data using 'dbms_output.put_line' and I keep getting this error after a few records. I resorted it and it happen at a different interval. Could it have to do with the length of the item I am trying to spool? Thanks.
ORA-06502: PL/SQL: numeric or value error stringyes, it is a data dependent error.
Handle:     SD
Status Level:     Newbie
Registered:     Nov 21, 2001
Total Posts:     289
Total Questions:     189 (183 unresolved)
why do you waste time here when you rarely get your questions answered?

ORA-06502: PL/SQL: numeric or value error: character string buffer too smal

Hi Guys I am getting error ORA-06502: PL/SQL: numeric or value error: character string buffer too small as it said i thought it would be issue with length of feild but i tried to change is nothihg work i am posing code here if any one can please help me on this
PROCEDURE REPORT
p_rpt_from_dt in varchar2,
p_rpt_to_dt in varchar2,
p_apvr_id in tc_wkr.tc_row_id%type default NULL,
p_rpt_type in varchar2 default NULL,
p_backto_pg in varchar2 default NULL
IS
v_rpt_from_dt date := var_to_date(p_rpt_from_dt);
v_rpt_to_dt date := var_to_date(p_rpt_to_dt);
v_time_str varchar2(15);
cursor period_cur
cp_from_dt date,
cp_to_dt date
is
select beg_dt, end_dt
from jmcs_wk_tprd
where beg_dt <= cp_to_dt -- report end date
and end_dt >= cp_from_dt -- report start date
BEGIN
if sys_security('tcsys', 'tc_reports') != 'GRANTED' then
apps_main.access_denied;
return;
end if;
if lg_debug_fl then
v_time_str := to_char(lg_sysdate, 'hh:mi:ss a.m.');
else
v_time_str := tc_time(lg_sysdate);
end if;
/* get the time card time periods applicable to the report */
lga_tc_strt_dt := lga_null_date;
for recs in period_cur(v_rpt_from_dt, v_rpt_to_dt) loop
lga_tc_strt_dt(lga_tc_strt_dt.count+1) := recs.beg_dt;
lga_tc_end_dt(lga_tc_end_dt.count+1) := recs.end_dt;
end loop;
--if p_apvr_id is NULL then
if p_rpt_type != 'D' then
tc_reporting.reports_header
1,
'Time Card Status Report',
'for '||dd_mon_yyyy(v_rpt_from_dt)||' through '||dd_mon_yyyy(v_rpt_to_dt)||' '||
'Report Date: '||dd_mon_yyyy(lg_sysdate)||' Time: '||v_time_str,
NULL,
NULL,
NULL,
'javascript:window.close()', /* Backto */
'alert(''Reminder! Click on logo when you are ready to return to previous page'')'
end if;
if p_apvr_id is NULL then
sub_STATUS_BD_ALPHA (v_rpt_from_dt, v_rpt_to_dt, TRUE, p_rpt_type, p_apvr_id);
else
htp.p('');
sub_STATUS_BD_APVR (v_rpt_from_dt, v_rpt_to_dt, p_rpt_type, p_apvr_id);
end if;
htp.p('</body></html>');
EXCEPTION
WHEN OTHERS THEN
error_proc(SQLERRM, SQLCODE, owa_util.get_cgi_env('PATH_INFO'));
htp.p('Error Code is :'||SQLERRM);
END REPORT;
This package in trun call other procedure like below
PROCEDURE sub_STATUS_BD_ALPHA
p_rpt_from_dt in date,
p_rpt_to_dt in date,
p_display_hdr in boolean,
p_rpt_type in varchar2 default 'B',
p_apvr_id in tc_wkr.tc_row_id%type default NULL,
p_tcs_user_id in tc_wkr.tc_row_id%type default NULL
IS
v_time_str varchar2(15);
v_apvr_id tc_wkr.tc_row_id%type := 0;
v_a_user_id tc_wkr.tc_row_id%type; -- approver tcs_user_id
v_cnt integer := 0;
v_people_cnt integer := 0;
v_stat_cd varchar2(2000);
v_display_fl boolean := FALSE;
/*===========================================================================*/
cursor people_cur
cp_from_dt in date,
cp_to_dt in date
is
select
d_full_nm_lfm as name,
tc_row_id as tcs_user_id,
tcw_typ as pay_typ,
tcw_id as pay_id,
sys_strt_date as sys_strt_dt,
sys_end_dt
from tc_wkr
where sys_strt_date <= cp_to_dt
and nvl(sys_end_dt, cp_to_dt) >= cp_from_dt
order by upper(d_full_nm_lfm);
/* find the current or the most recent (if no current) approver */
cursor apvr_cur
cp_tcs_user_id in tc_wkr.tc_row_id%type
is
select
a.f_tc_apvr_id as fk_tcs_apvr_id,
w.d_full_nm_lfm as apvr_name,
w.tcw_typ as apvr_pay_typ,
w.tcw_id as apvr_pay_id,
a.strt_dt,
a.end_dt
from tc_wkr w, tc_ap_asmt a
where a.f_tc_wkr_id = cp_tcs_user_id
and w.tc_row_id = a.f_tc_apvr_id
order by a.strt_dt desc;
/* list of existing time cards UNION required time cards */
cursor tc_cur
cp_tcs_user_id in tc_wkr.tc_row_id%type, /* who's time cards */
cp_from_dt in date, /* report period from date */
cp_to_dt in date /* report period to date */
is
select
stat_cd,
strt_dt,
end_dt
from tc
where strt_dt <= cp_to_dt
and end_dt >= cp_from_dt
and fk_tc_wkrtcw_id = cp_tcs_user_id
UNION
select
'Required' as stat_cd,
beg_dt as strt_dt,
end_dt
from jmcs_wk_tprd
where beg_dt <= cp_to_dt
and end_dt >= cp_from_dt
and beg_dt not in (
select strt_dt
from tc
where strt_dt <= cp_to_dt
and end_dt >= cp_from_dt
and fk_tc_wkrtcw_id = cp_tcs_user_id
order by strt_dt;
BEGIN
if lg_debug_fl then
v_time_str := to_char(lg_sysdate, 'hh:mi:ss a.m.');
else
v_time_str := tc_time(lg_sysdate);
end if;
if p_apvr_id > 0 then
lga_report_out := lga_report_out_null;
v_apvr_id := p_apvr_id;
lga_apvr := lga_apvr_null;
select
d_full_nm_lfm,
tc_row_id,
tcw_id,
tcw_typ
into
lga_apvr(1).apvr_name,
lga_apvr(1).apvr_tcs_id,
lga_apvr(1).apvr_pay_id,
lga_apvr(1).apvr_pay_typ
from tc_wkr
where tc_row_id = v_apvr_id;
if lga_apvr(1).apvr_pay_typ != 'S' then
select decode(bend_empl_fl, 'Y', 'E', 'W')
into lga_apvr(1).apvr_pay_typ
from empl
where empl_id = lga_apvr(1).apvr_pay_id;
end if;
end if;
if p_display_hdr then
if lga_tc_strt_dt.count > 6 then /* more than 6 time periods (1 month) */
lga_width(1) := to_char(.15 * lg_page_width_standard);
lga_width(2) := to_char(.08 * lg_page_width_standard);
for i in 1..lga_tc_strt_dt.count loop
lga_width(lga_width.count+1) := to_char(.09 * lg_page_width_standard);
end loop;
lg_page_width_standard := to_number(lga_width(1)) + to_number(lga_width(2));
if nvl(p_apvr_id, 0) = 0 then
lg_page_width_standard := lg_page_width_standard * 2;
end if;
htp.p('');
for i in 3..lga_width.count loop
lg_page_width_standard := lg_page_width_standard + to_number(lga_width(i));
htp.p('');
end loop;
lg_page_width := to_char(lg_page_width_standard);
else
lga_width(1) := '15%';
lga_width(2) := '8%';
lga_width(3) := '9%';
lga_width(4) := '9%';
lga_width(5) := '9%';
lga_width(6) := '9%';
lga_width(7) := '9%';
lga_width(8) := '9%';
end if;
sub_DETAIL_PAGE_HD(p_apvr_id);
end if;
/* cursor loop */
for p in people_cur(p_rpt_from_dt, p_rpt_to_dt) loop
/* is/was this person assigned to the selected approver for the report period */
v_display_fl := FALSE;
if nvl(p_tcs_user_id, 0) > 0 then
if p_tcs_user_id = p.tcs_user_id then
htp.p(' Selected User');
v_display_fl := TRUE;
end if;
elsif nvl(p_apvr_id, 0) = 0 then
if nvl(p_apvr_id, 0) = 0 then
v_display_fl := TRUE;
elsif p_apvr_id > 0 or p_apvr_id = -1 then
v_display_fl := fct_ASSIGNED_APVR(p.tcs_user_id, p_apvr_id, p_rpt_from_dt, p_rpt_to_dt);
end if;
if v_display_fl then
v_people_cnt := v_people_cnt + 1;
lg_tcs_owner_info.USER_ID := p.tcs_user_id;
lg_tcs_owner_info.PAY_ID := p.pay_id;
lg_tcs_owner_info.PAY_TYPE := p.pay_typ;
lg_tcs_owner_info.SYS_STRT_DT := p.sys_strt_dt;
lg_tcs_owner_info.TERM_DT := p.sys_end_dt;
if p.pay_typ = 'S' then
begin
select wrk_hire_dt
into lg_tcs_owner_info.hire_dt
from subcntr
where sub_id = p.pay_id;
exception
when no_data_found then
tc_debug.html_message('subcntr.pay_id('||p.pay_id||')');
end;
else
select
wrk_hire_dt,
decode(bend_empl_fl, 'Y', 'E', 'W')
into
lg_tcs_owner_info.hire_dt,
lg_tcs_owner_info.pay_type
from empl
where empl_id = lg_tcs_owner_info.PAY_ID;
end if;
if lga_report_out.count = 0 then
lga_report_out(lga_report_out.count+1) := '<table border="1" cellpadding="3" width="'||lg_page_width||'">';
end if;
if mod(v_people_cnt,2) = 1 then
lga_report_out(lga_report_out.count+1) := ('<tr bgcolor="'||lg_odd_bgcolor||'">');
else
lga_report_out(lga_report_out.count+1) := ('<tr bgcolor="'||lg_even_bgcolor||'">');
end if;
lga_report_out(lga_report_out.count+1) := ('<td valign="top">'||p.name||'</td >');
lga_report_out(lga_report_out.count+1) := ('<td valign="top">'||p.pay_typ||'-'||lpad(p.pay_id,4,'0')||'</td >');
if nvl(p_apvr_id, 0) > 0 then /* Single Approver */
/* need approver ID for time card "status" */
lga_apvr := lga_apvr_null; /* clear the approver id array */
lga_apvr(1).apvr_tcs_id := p_apvr_id;
elsif nvl(p_apvr_id, 0) = 0 then /* ALL Approvers */
lga_apvr := lga_apvr_null; /* clear the approver id array */
v_cnt := 0;
for ap in apvr_cur (p.tcs_user_id) loop
if v_cnt = 0 then
/* most recent approver may not be the applicable approver */
v_cnt := 1;
lga_apvr(v_cnt).apvr_name := ap.apvr_name; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_tcs_id := ap.fk_tcs_apvr_id; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_pay_id := ap.apvr_pay_id; -- identify multiple approvers for the "status"
v_apvr_id := ap.fk_tcs_apvr_id;
if ap.apvr_pay_typ = 'S' then
lga_apvr(v_cnt).apvr_pay_typ := ap.apvr_pay_typ; -- identify multiple approvers for the "status"
else
select decode(bend_empl_fl, 'Y', 'E', 'W')
into lga_apvr(1).apvr_pay_typ
from empl
where empl_id = lga_apvr(1).apvr_pay_id;
end if;
end if;
if ap.strt_dt <= p_rpt_to_dt and nvl(ap.end_dt, p_rpt_to_dt) >= p_rpt_from_dt then
/* approver record */
lg_tcs_owner_info.APVR_ID := ap.fk_tcs_apvr_id;
lg_tcs_owner_info.APVR_STRT_DT := ap.strt_dt;
lg_tcs_owner_info.APVR_END_DT := ap.end_dt;
don't enter same approver name multiple times
when same approver has been assigned more than once
Example: approver1, approver_2, approver_1 (change back to approver 1)
for i in 1..lga_apvr.count loop
v_apvr_id := ap.fk_tcs_apvr_id;
if lga_apvr(i).apvr_tcs_id = ap.fk_tcs_apvr_id then
/* don't add again */
v_apvr_id := NULL;
exit;
end if;
end loop;
if v_apvr_id is not NULL then
v_cnt := v_cnt + 1;
lga_apvr(v_cnt).apvr_name := ap.apvr_name; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_tcs_id := ap.fk_tcs_apvr_id; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_pay_id := ap.apvr_pay_id; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_pay_typ := ap.apvr_pay_typ; -- identify multiple approvers for the "status"
end if;
end if;
end loop;
/* list approver pay IDs */
lga_report_out(lga_report_out.count+1) := ('<td valign="top">');
if lga_apvr.count = 0 then
lga_report_out(lga_report_out.count+1) := 'Approver Unassigned';
else
for i in 1..lga_apvr.count loop
if i > 1 then
lga_report_out(lga_report_out.count+1) := ' ';
end if;
lga_report_out(lga_report_out.count+1) := (lga_apvr(i).apvr_name);
end loop;
end if;
lga_report_out(lga_report_out.count+1) := ('<td valign="top">');
if lga_apvr.count = 0 then
lga_report_out(lga_report_out.count+1) := 'N/A';
else
for i in 1..lga_apvr.count loop
if i > 1 then
lga_report_out(lga_report_out.count+1) := ' ';
end if;
lga_report_out(lga_report_out.count+1) := (lga_apvr(i).apvr_pay_typ)||'-'||lpad(lga_apvr(i).apvr_pay_id,4,'0');
end loop;
end if;
lga_report_out(lga_report_out.count+1) := ('</td >');
end if;
for t in tc_cur(p.tcs_user_id, p_rpt_from_dt, p_rpt_to_dt) loop
htp.p('<! '||t.strt_dt||', '||t.end_dt||', '||t.stat_cd||' -->');
--lga_report_out(lga_report_out.count+1) := ('<td valign="top">');
--lga_report_out(lga_report_out.count+1) := (t.stat_cd);
--lga_report_out(lga_report_out.count+1) := ('</td >');
/* has the selected approver has completed processing */
if p_apvr_id > 0
and v_apvr_id = p_apvr_id
and v_a_user_id != p_apvr_id
then
exit;
end if;
for ap in apvr_cur (p.tcs_user_id) loop
if apvr_cur%rowcount = 1 then
/* most recent approver assigned */
lg_tcs_owner_info.apvr_id := ap.fk_tcs_apvr_id;
end if;
if ap.strt_dt <= t.end_dt and nvl(ap.end_dt, t.end_dt) >= t.strt_dt then
/* approver assigned during time card period */
lg_tcs_owner_info.apvr_id := ap.fk_tcs_apvr_id;
exit;
end if;
end loop;
lg_tc_status.strt_dt := t.strt_dt;
lg_tc_status.end_dt := t.end_dt;
lg_tc_status.stat_cd := t.stat_cd;
v_stat_cd := fct_TC_STATUS(nvl(p_apvr_id, 0));
lga_report_out(lga_report_out.count+1) := ('<td align="center" valign="top" bgcolor="'||lg_tc_status.bg_color||'">');
lga_report_out(lga_report_out.count+1) := ('');
lga_report_out(lga_report_out.count+1) := v_stat_cd;
lga_report_out(lga_report_out.count+1) := ('</td >');
end loop;
lga_report_out(lga_report_out.count+1) := '</tr>';
end if; /* v_display_fl */
end loop;
if p_rpt_type in ('B', 'S') then
lg_page_cnt := lg_page_cnt + 1;
sub_DISPLAY_STATUS_SUMMARY;
end if;
if lga_report_out.count > 0 then
lga_report_out(lga_report_out.count+1) := '</table>';
end if;
if lga_report_out.count > 0 then
if p_rpt_type = 'B' or p_apvr_id > 0 then
if p_display_hdr then
if lg_page_cnt > 0 then
if p_apvr_id > 0 then /* selected individual approver */
htp.p('</table>');
end if;
htp.p(' ');
 htp.p('');
 htp.p('');
end if;
lg_page_cnt := lg_page_cnt + 1;
tc_reporting.reports_header
1,
'Time Card Status Report',
'for '||dd_mon_yyyy(p_rpt_from_dt)||' through '||dd_mon_yyyy(p_rpt_to_dt)||' '||
'Report Date: '||dd_mon_yyyy(lg_sysdate)||' Time: '||v_time_str,
NULL,
NULL,
NULL,
NULL, -- p_backto_pg, /* Backto */
'focus()',
lg_page_cnt
end if;
end if;
if p_rpt_type in ('B', 'D') then
for i in 1..lga_report_out.count loop
htp.p(lga_report_out(i));
end loop;
end if;
end if;
END sub_STATUS_BD_ALPHA;
Some veriable
type report_tc_rec is record
tc_owner_name tc_wkr.d_full_nm_lfm%type,
o_user_id tc_wkr.tc_row_id%type,
o_pay_id varchar2(10),
o_sys_strt_dt date,
o_sys_end_dt date,
tc_apvr_name tc_wkr.d_full_nm_lfm%type,
a_pay_id varchar2(10),
a_user_id tc_wkr.tc_row_id%type,
tc_strt_dt date,
tc_end_dt date,
tc_stat_cd varchar2(50),
ap_strt_dt date,
ap_end_dt date
/* time card owner information */
TYPE tcs_owner_info_rec IS RECORD
USER_ID tc_wkr.tc_row_id%type,
PAY_ID tc_wkr.tcw_id%type,
PAY_TYPE tc_wkr.tcw_typ%type,
HIRE_DT date,
SYS_STRT_DT date,
TERM_DT date,
APVR_ID tc_wkr.tc_row_id%type,
APVR_STRT_DT date,
APVR_END_DT date
/* status code determines report cell font and background colors */
TYPE tc_status_rec IS RECORD
STRT_DT date,
END_DT date,
STAT_CD tc.stat_cd%type,
FONT_COLOR varchar2(16),
BG_COLOR varchar2(16)
/* count of all time card status for report summary */
TYPE tc_status_summary_rec IS RECORD
APPROVED_CNT integer := 0,
REJECTED_CNT integer := 0,
SUBMITTED_CNT integer := 0,
POSTED_CNT integer := 0,
VERIFIED_CNT integer := 0,
OPEN_CNT integer := 0,
NEW_CNT integer := 0,
REQUIRED_CNT integer := 0,
TOTAL_CNT integer := 0
/* determine multiple approvers for individual for selected report period */
TYPE apvr_rec IS RECORD
apvr_name tc_wkr.d_full_nm_lfm%type,
apvr_tcs_id tc_wkr.tc_row_id%type,
apvr_pay_id tc_wkr.tcw_id%type,
apvr_pay_typ tc_wkr.tcw_typ%type
TYPE apvr_id_array_table IS TABLE OF apvr_rec
index by binary_integer;
type output_array is table of varchar2(1000)
index by binary_integer;
type date_array is table of date
index by binary_integer;
type status_array is table of varchar2(1000)
index by binary_integer;
type apvr_array is table of number(8)
index by binary_integer;
lga_report_out output_array; /* array of HTML code to be output to browser */
lga_report_out_null output_array; /* null array of HTML code */
lga_tc_status status_array;
lga_null_status status_array;
lga_tc_strt_dt date_array;
lga_tc_end_dt date_array;
lga_tc_disp date_array; /* start dates of displayed TC for selected user */
lga_null_date date_array; /* null array used to clear other date arrays */
/* LOCAL GLOBAL VARIABLES */
lg_tcs_owner_info tcs_owner_info_rec; /* time card owner information */
lg_tc_status tc_status_rec; /* time card status information */
lg_tc_status_summary tc_status_summary_rec; /* time card count by status */
lg_tc_rec report_tc_rec; /* time card */
lga_apvr apvr_id_array_table; /* array of approver Names and Payroll IDs */
lga_apvr_null apvr_id_array_table; /* clear the lga_apvr array for each user */
lg_sysdate date := sysdate;
lg_debug_fl boolean := FALSE;
lg_debug_owner_id tc_wkr.tc_row_id%type := 9905;
lg_debug_apvr_id tc_wkr.tc_row_id%type := 1000;
The chnages i have done its in bold
Please Advice
Thanks
Edited by: Purvik on Aug 25, 2009 11:59 AM

There is not a chance in the world, especially not knowing column definitions that I, and I suspect most anyone else, is going to wade through this much unformated code looking for an error you couldn't bother to copy in full.
Either tell us, specifically, the line on which the error is occurring or, better yet, start whacking stuff out of your code until you find the offending definition. That is certainly what I would do. Commenting out sections is a marvelous way to quickly find an issue.
Before you post again please read the FAQ. It will explain to you how to properly post and use the tags.

Alpha Conforming Values Error 5323,1461....

Similar Messages

Maybe you are looking for