Frame only for columns having values in smartforms

hi friends,
im in the process of developing a smartform in which i have a table and i need to have give frames only to the columns which are having values...is it possible..pls help

I think if its in table it wont happen like this
try it once unless try like this
in your text elements output options check the boxes with shading & in its adjacent print priview
the box frame is completly checked when you click the box with frame then remove the horizontal lines by clicking upper frame & lower frame icons & about vertical line try once with left frame & once with right frame
It definately works because it wont dispaly this without data.
Thanks,
Phani.
Edited by: phani kumar on May 15, 2008 2:37 PM

Similar Messages

Quality Operation confirmation only for specific grid Values

Hello,
When I am doing in process inspection for a specific routing for say the 0040th operation, upon confirmation I would like to confirm only part quatities for a specific grid value alone. But there are certain issues as follows:
1. When I am specifying the grid values, the same is not automatically copied to the yield quantitites field for confirmation. Moreover the system does not even propose what is the quantity to be confirmed. so the user has to remember and feed in the quantities.
2. When I am trying to save the partial quantites as per the grid system is automatically raising a partial lot. Why is system doing so? I am not able to figure out why?
Any suggestions on this is greatly appreciated.
Sincerely,
Aji Kurian Mani

Hi Aji Kurian Mani,
I am not so sure which transaction code you are using for confirmation. If at all you are willing to perform this through QA32 its feasible.
1.     All you need to do is maintain inspection point at header level in routing
2.     At operation level double click on control key. Scroll down up to quality management view.
3.     There in confirmation menu choose valuation and confirmation.
4.     You may try using different combinations there as a result of which when you valuate the results for inspection point, system throws a window to input yield and scrap.
Regards,
Anand Rao
Edited by: Anand Rao on Aug 31, 2011 11:49 PM

Display Columns having sum/total not zero

We have a report that hav total twenty columns.
Each time we run te report (dynamic query) random columns have sum=zero
we want to display eachtime only the columns having sum greater than zero.
regards
jazib

Hi Jazib,
Ok - I've been testing this here [http://htmldb.oracle.com/pls/otn/f?p=267:43]. The report on the left shows/hides the SAL and COMM columns according to the totals. The report on the right shows the full data. Change the Dept to see this in effect.
There are other methods available, but this is what I have done:
The dept select list (item name is P43_DEPTNO) is just a list of departments and a NULL option that returns 0 (zero).
The report's source is a SQL statement of:
SELECT EMPNO, ENAME, SAL, COMM
FROM EMP
WHERE :P43_DEPTNO = 0 OR :P43_DEPTNO = DEPTNO
ORDER BY ENAMEI have a region in the After Header position that uses "No Template" and contains two Hidden items - P43_SAL and P43_COMM.
I have an Item Computation, running "Before Header", that sets P43_DEPTNO to 0 if it is NULL.
I have an unconditional PL/SQL Process, running "On Load - Before Header", that has the following process code:
DECLARE
vSAL NUMBER;
vCOMM NUMBER;
BEGIN
SELECT NVL(SUM(SAL),0), NVL(SUM(COMM),0)
INTO vSAL, vCOMM
FROM EMP
WHERE :P43_DEPTNO = 0 OR :P43_DEPTNO = DEPTNO;
:P43_SAL := vSAL;
:P43_COMM := vCOMM;
END;And, finally, on the SAL column in the report, I have set the Condition Type to "Value of Item in Expression 1 != Zero" and Expression 1 is: P43_SAL. And the same on the COMM column, but Expression 1 is: P43_COMM
When the page is loaded, the process is run and the totals for SAL and COMM are calculated and inserted into P43_SAL and P43_COMM. The report is then run and the conditions check the values of these two hidden items - if either is non-zero, then the column is displayed.
Andy

In fusion BI Publisher Enterprise only the data having US as language in tl table are geting displayed.

Hi,
I am using Oracle Business Intelligence 11.1.1.7.10.
In my Dataset sql have condition as "tl_table.language = USERENV('LANG')".So it should fetch the data as per the userenv language.
But it fetching only the column having the US as language in tl table.I tested the select USERENV('LANG') from dual by creating a demo datamodel ,it getting only US even after I have logged in using other language than US en .Just for testing I removed the "tl_table.language = USERENV('LANG')" condition than it fetched all the column.The web pages are ok the text are displaying in logged in language.
My requirement is that if I have logged in to BIP using Korean language than it should fetch all the column having Korean(KO) as language in tl table.

Hi,
I am using Oracle Business Intelligence 11.1.1.7.10.
In my Dataset sql have condition as "tl_table.language = USERENV('LANG')".So it should fetch the data as per the userenv language.
But it fetching only the column having the US as language in tl table.I tested the select USERENV('LANG') from dual by creating a demo datamodel ,it getting only US even after I have logged in using other language than US en .Just for testing I removed the "tl_table.language = USERENV('LANG')" condition than it fetched all the column.The web pages are ok the text are displaying in logged in language.
My requirement is that if I have logged in to BIP using Korean language than it should fetch all the column having Korean(KO) as language in tl table.

ORA-01461: can bind a LONG value only for insert into a LONG column error

Oracle 11g R1 RHEL 5 64bit (Apex 3.1)
Hi all,
I am having a tough time with this error:
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-06512: at "FPRCHR.PKG_TRIGGER_EMAIL", line 39
ORA-06512: at "ISWRNEW.PKG_NOTIFICATION", line 310
ORA-06512: at "ISWRNEW.PKG_NOTIFICATION", line 1745
ORA-06512: at line 1
The FPRCHR.PKG_TRIGGER_EMAIL looks like follows:
INSERT INTO fprchr.trigger_email
(trigger_email_rid,
email_to,
email_from,
email_body,
email_subject,
email_cc,
email_bcc,
mime_type,
email_priority
VALUES (l_job,
p_recipients,
p_sender,
p_message,
p_subject,
p_cc,
p_bcc,
p_mime_type,
p_priority
execute immediate 'alter session set events ''10046 trace name context off''';
END submit;
It seems like the characters have exceeded the limit that VARCHAR2 can handle? What other data type could I change the fprchr.trigger_email table to? Is that all that is needed?
Thanks.

It seems like the characters have exceeded the limit that VARCHAR2 can handle? What other data type could I change the fprchr.trigger_email table to? Is that all that is needed?
Did you try with clob data type?
Regards.
Satyaki De

ORA-01461: can bind a LONG value only for insert into a LONG column in 11.2

Hello,
We have been getting the following exception when we try to save an XML (>5k).
SQL state [72000]; error code [1461]; ORA-01461: can bind a LONG value only for insert into a LONG column
This is occurring only for Oracle 11g (11.2.0.1.0)
Our column is CLOB type, not LONG type.
Could anyone please suggest what could be the reason and fix?
Thanks in advance
--Cheers
paruvid

Thanks for quick response!!
Inserting throw JDBC (Spring jdbcTemplate)
using the ojdbc6.jar as driver
here is the stask strace
Caused by: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO tabl1(c1, c2, c3, c4, c5, c6, c7, c8, c9, c10, c11, c12, c13, c14, c15,c16(CLOBCOL),c17, c18, c19) SELECT c1,c2, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? FROM table2 S JOIN table1 D ON S.c1 = D.c1 WHERE S.c2 = ? AND D.c5 = ? GROUP BY S.c1];
SQL state [72000]; error code [1461]; ORA-01461: can bind a LONG value only for insert into a LONG column
; nested exception is java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:83)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:602)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:786)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:842)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:846)
at com.smartstream.cms.message.dao.SSIMessageDao.editSSIInstance(SSIMessageDao.java:522)
... 52 more
Caused by: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
Edited by: paruvid on Aug 9, 2011 5:07 AM
Edited by: paruvid on Aug 9, 2011 5:17 AM
Edited by: paruvid on Aug 9, 2011 5:23 AM

Weird exception in 12c (ORA-01461: can bind a LONG value only for insert into a LONG column)

I have a Windows app that accesses an Oracle 12c database via ODBC (the driver version is 12.01.00.01).
I have a table that has a key column named REGION_ID (NVARCHAR2(9)), and about a dozen other columns, three of which are named REGION1, REGION2, and REGION3, all of type NVARCHAR2(40).
When I try to insert a string into the REGION1 field that's greater than 9 characters (the length of REGION_ID), I get an ORA-01461 error ('Can bind a LONG value only for insert into a LONG column). If I define the length of REGION_ID to be NVARCHAR2(15), then I can add strings to the REGION1 field with a length up to 15 before I get the ORA-01461 exception again. Oddly, if I change the REGION1 column name to REGIONONE, I do not get any errors, and everything works fine. It's almost as if the column name REGION1 is being confused with REGION_ID behind the scenes.
Any ideas? I’m using SQLBindParameter to bind the columns, and all of the calls succeed. I get the exception when I execute the insert statement. This same code worked for previous versions of Oracle (11g, 10g, and 9i). And if I use an 11g client driver against the 12c server, I do not get the exception.
Thanks!

Sorry, I was just now able to install the patch for bug 18232462, and it did indeed solve the issue I described above. Thanks!

ORA-01461: can bind a LONG value only for insert into a LONG column ORA-020

Getting error --
ORA-01461: can bind a LONG value only for insert into a LONG column ORA-02063: preceding line from APPS
A page has 3 fields and a Add button
(1) first field is a LOV "select with submit"
(2) second field is getting its value from select statement with where clause = ID selected from field1
(3) field 3 is the value of field1
In After submit Process , I write simple insert as follows in the
BEGIn
INSERT INTO TABLE_NAME (ELEMENT_NAME,ELEMENT_TYPE_ID )
VALUES (:P3_NAME ,to_number(:P3_ELEMENT_TYPE_ID));
COMMIT;
END;
when i click on Add i get the error above

try doing the bind locally before executing the remote dml...
declare
l_long long := :P3_NAME;
begin
insert into table_name (ELEMENT_NAME,ELEMENT_TYPE_ID )
values (l_long ,to_number(:P3_ELEMENT_TYPE_ID));
end;
...and if that doesn't work, please let us know the definition of you TABLE_NAME table.
thanks,
raj

ORA-01461: can bind a LONG value only for insert into a LONG column - Issue

We are getting an error from Oracle DB --- Cause: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
The application was working fine with Oracle 10.2.0.4 and ojbc14 driver 10.2.0.1 Error occurs only after an upgrade to Oracle 10g 10.2.0.5. So after some googling, we found that a driver upgrade would eliminate this error. So the 10.2.0.5 version of the driver was used. But the ORA error still occurs. The readme of ojdb14.jar specified this - BUG 8847022 - ORA-01461: CAN BIND A LONG VALUE ONLY FOR INSERT INTO A LONG COLUMN
The problem is that we are not able to reproduce this using a sample program however it is happening consistently in the client environment.
we get the error ORA-01461, when the oracle version is upgraded to 10.2.0.5. This error occurs when we try to insert a file(BLOB) data with the file length greater than 4KB to a table.
Exception trace
uncategorized SQLException for SQL []; SQL state [72000]; error code [1461];
--- The error occurred in nl/sss/gict/mcb/data/dao/config/StateQueries.xml.
--- The error occurred while applying a parameter map.
--- Check the setReceivedFile-InlineParameterMap.
--- Check the statement (update failed).
--- Cause: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
; nested exception is com.ibatis.common.jdbc.exception.NestedSQLException:
--- The error occurred in nl/sss/gict/mcb/data/dao/config/StateQueries.xml.
--- The error occurred while applying a parameter map.
--- Check the setReceivedFile-InlineParameterMap.
--- Check the statement (update failed).
--- Cause: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
Oracle version installed in acceptance:
1 Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
2 PL/SQL Release 10.2.0.5.0 - Production
3 CORE 10.2.0.5.0 Production
4 TNS for Linux: Version 10.2.0.5.0 - Production
5 NLSRTL Version 10.2.0.5.0 - Production

Is the server running Java 1.4? If it is Java 5 or higher there is no need to keep using OJDBC14, you can upgrade to OJDBC5.
If you cannot do that, then I ask you: why make this post? What are you expecting someone to do? Your problem is with the OJDBC driver, you are not going to get tech support for it in this Java programming forum.

ORA-01461: can bind a LONG value only for insert into a LONG column-Update

Hi,
I'm using Oracle 9.2 with Weblogic 8 server. There are two columns OBJ_EVIDENCE_COMP - varchar2(4000 bytes), Descriptiion - varchar2(4000 bytes) in a table.I'm getting the Data from that table and again I'm updating into the same table with same data after updating the Data object in java.
I am getting the following error
"Java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column"
Can some one let me know why this error occurs ? Please do let me know if you want any other information. Below is my SQL Query:
* @jc:sql statement::
* UPDATE CORRECTIVE_ACTION SET
* CA_ID = {dt.caId},
* CA_NBR = {dt.caNbr},
* CAPA_PLAN_ID = {dt.capaPlanId},
* OBJ_EVIDENCE_COMP = {dt.objEvidenceComp},
* APPLICABLE_ELSE_WHERE = {dt.applicableElseWhere},
* JUSTIFICATION = {dt.justification},
* MOE = {dt.moe},
* COMPLETION_DATE = {dt.completionDate},
* EXTENSION_DUE_DATE = {dt.extensionDueDate},
* STATUS_CD = {dt.statusCd},
* SYSTEM_STATUS_CD = {dt.systemStatusCd},
* ROOT_CAUSE_CD = {dt.rootCauseCd},
* DESCRIPTION = {dt.description},
* CA_TYPE = {dt.caType},
* CREATED_BY = {dt.createdBy},
* CREATED_DATE = {dt.createdDate},
* MODIFIED_BY = {dt.modifiedBy},
* MODIFIED_DATE = {dt.modifiedDate},
* COMPLETION_DUE_DATE = {dt.completionDueDate}
* WHERE CA_ID = {dt.caId}
In the above update statement if i remove one among the 2 columns mentioned then it is getting updated properly......
Regards,
Bharat
Edited by: 908508 on Jan 17, 2012 2:18 AM

I am occasionally getting this error in an Oracle 11g database
I use Rogue Wave to insert:
connection.beginTransaction ("bulkInsertEvents");
RWDBTBuffer <RWCString> symbols (symbol, rowCount);
RWDBTBuffer <RWDateTime> timeStamps (timeStamp, rowCount);
RWDBTBuffer <int> eventCounts (eventCount, rowCount);
RWDBTBuffer <RWCString> events (event, rowCount);
RWDBBulkInserter ins = table.bulkInserter (connection);
ins << symbols << timeStamps << eventCounts << events;
ins.execute ();
connection.commitTransaction ("bulkInsertEvents");
catch (RWxmsg & exception)
cout << Logging::getProgramName () << " " << exception.why () << endl;
throw "Failed to do bulk insert events to DBTools.";
Some of the inserts give me
"[SERVERERROR] ORA-01461: can bind a LONG value only for insert into a LONG column"
the table structure is
SYMBOL     VARCHAR2(33 BYTE)
DATEANDTIME     TIMESTAMP(6)
NUMOFEVENTS     NUMBER
EVENTS     VARCHAR2(4000 BYTE)

Can bind a LONG value only for insert into a LONG column

I got an exception when I was using sesame adapter to dump a turtle file which contains long texts as objects into oracle semantic database. The exception information is:
org.openrdf.repository.RepositoryException: org.openrdf.sail.SailException: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-06512: in "SF.ORACLE_ORARDF_ADDHELPER", line 1
ORA-06512: in line 1
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:202)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1005)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3530)
     at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:4735)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
     at oracle.spatial.rdf.client.sesame.OracleSailConnection.addStatement(OracleSailConnection.java:1976)
     at org.openrdf.repository.sail.SailRepositoryConnection.addWithoutCommit(SailRepositoryConnection.java:249)
     at org.openrdf.repository.base.RepositoryConnectionBase.add(RepositoryConnectionBase.java:510)
     at org.openrdf.repository.util.RDFInserter.handleStatement(RDFInserter.java:193)
     at org.openrdf.rio.turtle.TurtleParser.reportStatement(TurtleParser.java:963)
     at org.openrdf.rio.turtle.TurtleParser.parseObject(TurtleParser.java:416)
     at org.openrdf.rio.turtle.TurtleParser.parseObjectList(TurtleParser.java:339)
     at org.openrdf.rio.turtle.TurtleParser.parsePredicateObjectList(TurtleParser.java:315)
     at org.openrdf.rio.turtle.TurtleParser.parseTriples(TurtleParser.java:301)
     at org.openrdf.rio.turtle.TurtleParser.parseStatement(TurtleParser.java:208)
     at org.openrdf.rio.turtle.TurtleParser.parse(TurtleParser.java:186)
     at org.openrdf.rio.turtle.TurtleParser.parse(TurtleParser.java:131)
     at org.openrdf.repository.base.RepositoryConnectionBase.addInputStreamOrReader(RepositoryConnectionBase.java:404)
     at org.openrdf.repository.base.RepositoryConnectionBase.add(RepositoryConnectionBase.java:295)
     at org.openrdf.repository.base.RepositoryConnectionBase.add(RepositoryConnectionBase.java:226)
     at sforcl.dao.support.OracleSailDaoTemplate.addTTLFile(OracleSailDaoTemplate.java:114)
     at sforcl.test.OracleSailDaoTemplateTest.testAddTTLFile(OracleSailDaoTemplateTest.java:33)
     at sforcl.test.OracleSailDaoTemplateTest.main(OracleSailDaoTemplateTest.java:122)
How can I solve this problem?

Hi,
Can you please try loading the same file following Example 5 in Section 8.10.5 of
http://docs.oracle.com/cd/E11882_01/appdev.112/e25609/sem_sesame.htm
Thanks,
Zhe

ORA- 01461 : Can Bind a long value only for insert into a column error

I was trying to create a new job using dbms_job.isubmit
begin
sys.dbms_job.isubmit(job => 1111,
what => '',
next_date => to_date('21-10-2011 03:00:00', 'dd-mm-yyyy hh24:mi:ss'),
interval => 'TRUNC(SYSDATE+1)+3/24');
commit;
end;
However, I am getting the error 'ORA- 01461 : Can Bind a long value only for insert into a column error'.
I tried a lot but cant get rid of.
Any help gurus ?

You have an error in the code:
1. you don't provide a value for 'what' - you have to tell Oracle what it should execute when it submits the job.
And remember - with ISUBMIT the next_date parameter has datatype VARCHAR2 - SUBMIT uses datatype DATE. So make sure you provide a VARCHAR2 value and do not rely on implicit conversion.
>
PROCEDURE DBMS_JOB.ISUBMIT
(job IN BINARY_INTEGER
,what IN VARCHAR2
,next_date IN VARCHAR2
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);
PROCEDURE DBMS_JOB.SUBMIT
(job OUT BINARY_INTEGER
,what IN VARCHAR2
,next_date IN DATE DEFAULT SYSDATE
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);

Error ORA-01461: can bind a LONG value only for insert into a LONG column

Within an existing application , i need to create a new report , i created a new page in it and then tried to create classic report , during wizard when i enter the same query which i have used for previous page , it gives me following error during the creation of report.
The following bind variable i have already used for previous page. I want to reuse the same bind variables. There is no any long dataype within column predicates.
Error ORA-01461: can bind a LONG value only for insert into a LONG column
OK
Following is the query
SELECT
   "VWSR_ALL_MERGED_DATA_MV"."SR_AREA" "SR_AREA",
   "VWSR_ALL_MERGED_DATA_MV"."SR_STATUS" "SR_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_SUB_STATUS" "SR_SUB_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_CREATED" "SR_DATE_CREATED",
   "VWSR_ALL_MERGED_DATA_MV"."SR_OPEN_DATE" "SR_OPEN_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CLOSED_DATE" "SR_CLOSED_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT1" "SR_PRODUCT1",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT2" "SR_PRODUCT2",
   "VWSR_ALL_MERGED_DATA_MV"."SR_TIO_PRIORITY" "SR_TIO_PRIORITY",
   "VWSR_ALL_MERGED_DATA_MV"."SR_REF_NUMBER" "SR_REF_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_RECD" "SR_DATE_RECD",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CIDN" "SR_CIDN",
   "VWSR_ALL_MERGED_DATA_MV"."SR_BUS_UNIT" "SR_BUS_UNIT",
   "VWSR_ALL_MERGED_DATA_MV"."SR_NUMBER" "SR_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
   "VWSR_ALL_MERGED_DATA_MV"."BATCH_ID" "BATCH_ID"
FROM VWSR_ALL_MERGED_DATA_MV
WHERE trunc(VWSR_ALL_MERGED_DATA_MV.SR_DATE_RECD)=trunc(sysdate-1)
AND VWSR_ALL_MERGED_DATA_MV.SR_TIO_PRIORITY IN
                                                :P2_SR_TIO_PRIORITY
                                               ,'CEO'
                                               ,'TER'
                                               ,'Priority Assistance'
                                               ,'Enquiry'
AND   (
        (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                                     'Business Support and Improvement'
                                   , 'Finance and Administration'
                                   , 'Cust Sat Simplification and Productivity'
                                   , 'Project New and Customer Experience'
                                   , 'Corp Strategy and Customer Experience'
                                   , 'Other'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('BS&I'))
   OR   (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                                     'Consumer'
                                   , 'Consumer Telstra Country Wide'
                                   , 'Customer Service and Sales'
                                   , 'Offshore Sales and Service'
                                   , 'TC and TCW Operations'
                                   , 'Telstra Country Wide'
                                   , 'Other'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TC&C'))
   OR   (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                         'Telstra Customer Sales and Service'
                        ,'Telstra Program Office'
                        ,'Human Resources'
                        ,'IT'
                        ,'Unallocated'
                        ,'Other'
            AND :P2_SR_BUSINESS_UNIT= 'OTHER')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                    'Telstra Operations'
                   ,'Telstra Networks and Services'
                   ,'Other'
            AND :P2_SR_BUSINESS_UNIT= 'TO')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Business'
            AND :P2_SR_BUSINESS_UNIT= 'TB')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Wholesale'
            AND :P2_SR_BUSINESS_UNIT= 'TW')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Enterprise and Government'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TE&G'))
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Sensis'
                 ,'Sensis Pty Ltd'
            AND :P2_SR_BUSINESS_UNIT= 'SENSIS')
AND :P2_SR_TIO_PRIORITY = 'Level 0'
UNION
SELECT
   "VWSR_ALL_MERGED_DATA_MV"."SR_AREA" "SR_AREA",
   "VWSR_ALL_MERGED_DATA_MV"."SR_STATUS" "SR_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_SUB_STATUS" "SR_SUB_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_CREATED" "SR_DATE_CREATED",
   "VWSR_ALL_MERGED_DATA_MV"."SR_OPEN_DATE" "SR_OPEN_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CLOSED_DATE" "SR_CLOSED_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT1" "SR_PRODUCT1",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT2" "SR_PRODUCT2",
   "VWSR_ALL_MERGED_DATA_MV"."SR_TIO_PRIORITY" "SR_TIO_PRIORITY",
   "VWSR_ALL_MERGED_DATA_MV"."SR_REF_NUMBER" "SR_REF_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_RECD" "SR_DATE_RECD",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CIDN" "SR_CIDN",
   "VWSR_ALL_MERGED_DATA_MV"."SR_BUS_UNIT" "SR_BUS_UNIT",
   "VWSR_ALL_MERGED_DATA_MV"."SR_NUMBER" "SR_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
   "VWSR_ALL_MERGED_DATA_MV"."BATCH_ID" "BATCH_ID"
FROM
   VWSR_ALL_MERGED_DATA_MV
WHERE trunc(VWSR_ALL_MERGED_DATA_MV.SR_DATE_RECD)=trunc(sysdate-1)
   and VWSR_ALL_MERGED_DATA_MV.SR_TIO_PRIORITY IN (:P2_SR_TIO_PRIORITY)
AND (
     (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN (
                     'Business Support and Improvement'
                   , 'Finance and Administration'
                   , 'Cust Sat Simplification and Productivity'
                   , 'Project New and Customer Experience'
                   , 'Corp Strategy and Customer Experience'
                   , 'Other'
AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('BS&I'))
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN (
                     'Consumer'
                   , 'Consumer Telstra Country Wide'
                   , 'Customer Service and Sales'
                   , 'Offshore Sales and Service'
                   , 'TC and TCW Operations'
                   , 'Telstra Country Wide'
                   , 'Other')
AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TC&C'))
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                         'Telstra Customer Sales and Service'
                        ,'Telstra Program Office'
                        ,'Human Resources'
                        ,'IT'
                        ,'Unallocated'
                        ,'Other'
        AND :P2_SR_BUSINESS_UNIT= 'OTHER')
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                      'Telstra Operations'
                      ,'Telstra Networks and Services'
                      ,'Other'
        AND :P2_SR_BUSINESS_UNIT= 'TO')
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                     'Telstra Business'
        AND :P2_SR_BUSINESS_UNIT= 'TB')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Wholesale'
        AND :P2_SR_BUSINESS_UNIT= 'TW')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Enterprise and Government'
        AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TE&G'))
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Sensis'
                 ,'Sensis Pty Ltd'
        AND :P2_SR_BUSINESS_UNIT= 'SENSIS')
AND :P2_SR_TIO_PRIORITY = 'Level 1'Edited by: user13653962 on 30/01/2013 15:11
Edited by: user13653962 on 30/01/2013 15:14

You have an error in the code:
1. you don't provide a value for 'what' - you have to tell Oracle what it should execute when it submits the job.
And remember - with ISUBMIT the next_date parameter has datatype VARCHAR2 - SUBMIT uses datatype DATE. So make sure you provide a VARCHAR2 value and do not rely on implicit conversion.
>
PROCEDURE DBMS_JOB.ISUBMIT
(job IN BINARY_INTEGER
,what IN VARCHAR2
,next_date IN VARCHAR2
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);
PROCEDURE DBMS_JOB.SUBMIT
(job OUT BINARY_INTEGER
,what IN VARCHAR2
,next_date IN DATE DEFAULT SYSDATE
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);

SRM 4.0- How to set the default values for product type (01) only for SC

The radio button Service should not be visible.
Also for search help (e.g. search for internal products) where a search should only be possible for product type 01 (goods). The system should not display the product type and internally always search for goods only.
How to set the default values for product type (01) only for SC
We needs to use Search help BBPH_PRODUCT which having parameter PRODUCT_TYPE
Here we can set defalut value 01 but it is not correct one since same search help is using several places.
We need to limit the search help results only for SC.
Kindly help out me ASAP.

The easiest way to set defautl values is to edit the batch class.
Goto the characteiristic and go to update values.
In here you probably have something like 0 - 100 as a spec range.
On the next line enter the default value within this range. At the end of the line, click in the box in the column labelled "D". This indicates the defautl value for the characteristic.
If you need to you can do this in the material classification view as well.
Just to be clear, these values will only show up in the batch record. You can not have defautl values in resutls recording screens.
FF

Adding virtual column: ORA-12899: value too large for column

I'm using Oracle 11g, Win7 OS, SQL Developer
I'm trying to add virtual column to my test table, but getting ORA-12899: value too large for column error. Below are the details.
Can someone help me in this?
CREATE TABLE test_reg_exp
(col1 VARCHAR2(100));
INSERT INTO test_reg_exp (col1) VALUES ('ABCD_EFGH');
INSERT INTO test_reg_exp (col1) VALUES ('ABCDE_ABC');
INSERT INTO test_reg_exp (col1) VALUES ('WXYZ_ABCD');
INSERT INTO test_reg_exp (col1) VALUES ('ABCDE_PQRS');
INSERT INTO test_reg_exp (col1) VALUES ('ABCD_WXYZ');
ALTER TABLE test_reg_exp
ADD (col2 VARCHAR2(100) GENERATED ALWAYS AS (REGEXP_REPLACE (col1, '^ABCD[A-Z]*_')));
SQL Error: ORA-12899: value too large for column "COL2" (actual: 100, maximum: 400)
12899. 00000 - "value too large for column %s (actual: %s, maximum: %s)"
*Cause:    An attempt was made to insert or update a column with a value
           which is too wide for the width of the destination column.
           The name of the column is given, along with the actual width
           of the value, and the maximum allowed width of the column.
           Note that widths are reported in characters if character length
           semantics are in effect for the column, otherwise widths are
           reported in bytes.
*Action:   Examine the SQL statement for correctness. Check source
           and destination column data types.
           Either make the destination column wider, or use a subset
           of the source column (i.e. use substring).When I try to select, I'm getting correct results:
SELECT col1, (REGEXP_REPLACE (col1, '^ABCD[A-Z]*_'))
FROM test_reg_exp;Thanks.

Yes RP, it working if you give col2 size >=400.
@Northwest - Could you please test the same w/o having a regex clause in col2?
I doubt on the usage of a REGEX in this dynamic col case.
Refer this (might help) -- http://www.oracle-base.com/articles/11g/virtual-columns-11gr1.php
Below snippet from above link.... see if this helps...
>
Notes and restrictions on virtual columns include:
Indexes defined against virtual columns are equivalent to function-based indexes.
Virtual columns can be referenced in the WHERE clause of updates and deletes, but they cannot be manipulated by DML.
Tables containing virtual columns can still be eligible for result caching.
Functions in expressions must be deterministic at the time of table creation, but can subsequently be recompiled and made non-deterministic without invalidating the virtual column. In such cases the following steps must be taken after the function is recompiled:
Constraint on the virtual column must be disabled and re-enabled.
Indexes on the virtual column must be rebuilt.
Materialized views that access the virtual column must be fully refreshed.
The result cache must be flushed if cached queries have accessed the virtual column.
Table statistics must be regathered.
Virtual columns are not supported for index-organized, external, object, cluster, or temporary tables.
The expression used in the virtual column definition has the following restrictions:
It cannot refer to another virtual column by name.
It can only refer to columns defined in the same table.
If it refers to a deterministic user-defined function, it cannot be used as a partitioning key column.
The output of the expression must be a scalar value. It cannot return an Oracle supplied datatype, a user-defined type, or LOB or LONG RAW.
>
Edited by: ranit B on Oct 16, 2012 11:48 PM
Edited by: ranit B on Oct 16, 2012 11:54 PM

Frame only for columns having values in smartforms

Similar Messages

Maybe you are looking for