Referencing Tables - "Invalid Reference"

I'm trying to reference a cell between two tables on a single sheet. While this works with several tables, it doesn't work with one of them--even when I click on the cell I want to reference.
It will, however, work if I duplicate the table, delete the original, rename the duplicate to the original, and then reference the cell. This carries over until I close Numbers.
Previous references to that table will continue to work as intended, but new references return the error *This formula contains an invalid reference.* I receive this error when referencing the cell by clicking on it, typing the reference in, or copying an existing (and working) reference from the Function field.
Any assistance will be much appreciated.
Thanks!

Here is the formula being used.
=Amarr :: Additional Ships Gem1ni
The table is Amarr, the column is N, header +Additional Ships+, and the row is 3, header Gem1ni.
The original formula was created by pressing = and selecting cell N3.
Message was edited by: EchoD
Message was edited by: EchoD

Similar Messages

Best practice: self referencing table

Hallo,
I want to load a self referencing table to my enterprise area in the dwh. I am not sure how to do this. What if a record references to another record which is inserted later in the same etl process? There is now way to sort, because it is possible that record a references to record b and record b references to record a. Disabling the fk constraint is not a good idea, because this doesn't prevent that invalid references will be loaded? I am thinking of building two mappings, one without the self referencing column and the other only with it, but that would cause approx. twice as much running time. Any other solutions?
Regards,
Torsten

Mind sharing the solution? Would be interested to hear your solution (high level).
Jean-Pierre

Ms sql - {"The referenced table must have a primary or candidate key. [ FK Name = ForeignKeyB_Details ]"}

I have a txt file which has all the sqltext in it separated by semi colon .Then I try to run a query one by one like this-
var conn = new SqlCeConnection(ConnectionString);
conn.Open();
var cmdArray = Regex.Split(sqlText, ";");
var cmd = new SqlCeCommand(null, conn);
foreach (var text in cmdArray)
cmd.CommandText = text;
if (!text.Equals(string.Empty))
cmd.ExecuteNonQuery();
else
break;
conn.Close();
I get the error {"The referenced table must have a primary or candidate key. [ FK Name = ForeignKeyB_Details ]"}
here is part of my txt file-
CREATE TABLE A
PrimaryId nvarchar(10) NOT NULL REFERENCES C(PrimaryId),
UserId nvarchar(20) NOT NULL,
FirstName nvarchar(30) NOT NULL,
MiddleInitial nvarchar(1) NULL,
LastName nvarchar(30) NOT NULL,
MobileNumber nvarchar(20) NULL,
PhoneNumber nvarchar(10) NOT NULL,
PhoneExtension nvarchar(6) NULL,
FaxNumber nvarchar(20) NULL,
EmailAddress nvarchar(50) NOT NULL,
CONSTRAINT PrimaryKeyA PRIMARY KEY(PrimaryId, UserId)
CREATE TABLE B(
MarketId int NOT NULL references E(MarketId),
UserId nvarchar(20) NOT NULL,
UserFirstName nvarchar(30) NOT NULL,
UserMiddleInitial nvarchar(1) NOT NULL,
UserLastName nvarchar(30) NOT NULL,
PhoneNbr nvarchar(10) NOT NULL,
Extension nvarchar(6) NOT NULL,
FaxNbr nvarchar(20) NOT NULL,
Email nvarchar(50) NOT NULL,
ShortName nvarchar(10) NOT NULL,
PublicIdFlag nvarchar(6) NOT NULL references D(publicId),
CONSTRAINT PrimaryKeyB PRIMARY KEY( MarketId, UserId)
ALTER TABLE B ADD CONSTRAINT ForeignKeyB_Details FOREIGN KEY(UserId, UserFirstName, UserMiddleInitial, UserLastName, PhoneNbr, Extension, FaxNbr, Email) REFERENCES A(UserId, FirstName, MiddleInitial, LastName, PhoneNumber, PhoneExtension, FaxNumber, EmailAddress);

Hi,
Foreign key columns are frequently used in join criteria when the data from related tables is combined in queries by matching the column or columns in the FOREIGN KEY constraint of one table with the primary or unique key column or columns in the other table.
For more information about the foreign key constraint, please refer to this link:
http://msdn.microsoft.com/en-us/library/ms175464.aspx
Here is a similar thread for your reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/5a71948b-dfb1-46a5-8688-ccab9317e959/error-message-the-referenced-table-must-have-a-primary-or-candidate-key-fk-name-fktblatblb-?forum=sqlce
Thanks.
Tracy Cai
TechNet Community Support

Self Referencing Tables...

I have a self-referencing table (a Topic can be a response to another Topic) and read one of Frank Nimphius' blogs on this subject, posted on the ADF board for advise. As a result I created the read-only ViewObject to set up this tree relationship and set it to be exposed to the App Module.
Do I need to do more to it than that for JHeadstart to generate the right page defs? Any advise on setting this up cleanly? My user interface must present a page in which users can post new Topics, view topics in a heirarchy (response thread, like in this forum) and respond to Topics or responses. A response is a Topic that references another (parent) Topic. I have to believe this has been done before a million times but am not sure myself how to do it.
Thanks!

Steve,
I've read the section and am getting this error:
(oracle.jbo.SQLStmtException) JBO-27122: SQL error during statement preparation. Statement: SELECT Topic.SUBJECT, Topic.ROW_ID, Status.STATUS_CHOICE, Status.ROW_ID AS ROW_ID11, Topic.CREATED_BY, Topic.CREATION_DATE, Response.SUBJECT AS SUBJECT1, Response.CREATION_DATE AS CREATION_DATE1, Response.ROW_ID AS ROW_ID12, Response.CREATED_BY AS CREATED_BY1 FROM TOPIC Topic, RESPONSE Response, STATUS Status WHERE (Topic.ROW_ID = Response.MASTER_ID (+)) AND (Topic.TOPIC_STATUS_ID = Status.ROW_ID) CONNECT BY PRIOR Topic.ROW_ID = Response.MASTER_ID (+) OR Response.ROW_ID = Response.MASTER_ID (+) ORDER BY SUBJECT,CREATION_DATE1
----- LEVEL 1: DETAIL 0 -----
(java.sql.SQLException) ORA-01436: CONNECT BY loop in user data
I have a table called Topic with a Pk called ROW_ID and another table called Response with a Pk called ROW_ID and an Fk called MASTER_ID. A Topic can have many Responses and a Response can also have many Responses. The parent ID could point to either a Topic or a Response. There's no limit on how many levels this can continue. There's a Status table also from which I want to show the text value of the Status for the Topic row (not the Status ROW_ID)
I have a View Object including entities: Topic, Response & Status
I tried the SQL query as:
(Topic.ROW_ID = Response.MASTER_ID (+)) AND (Topic.TOPIC_STATUS_ID = Status.ROW_ID) CONNECT BY PRIOR Topic.ROW_ID = Response.MASTER_ID (+) OR Response.ROW_ID = Response.MASTER_ID (+)
Hoping to have this result:
Topic A
-Response A (to Topic A)
--Response B (to A)
---Response C (to B)
-Response D (to Topic A)
Topic B
Topic C
What am I doing wrong?
Is there a guide that explains better using JHeadstart with JDeveloper (rather than Oracle Designer, which we don't use)? The developer's guide for JHeadstart is hard to translate for use with JDeveloper...
Thanks!!

JPA: How to initialise an entity for a self-referencing table?

I am working on a project that requires a self-referencing table:
mysql> show create table attributes\G
*************************** 1. row ***************************
       Table: attributes
Create Table: CREATE TABLE `attributes` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`parent` int(11) DEFAULT NULL,
`type` int(11) DEFAULT NULL,
`name` varchar(128) DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `parent` (`parent`),
KEY `type` (`type`),
CONSTRAINT `attributes_ibfk_1` FOREIGN KEY (`parent`) REFERENCES `attributes` (`id`),
CONSTRAINT `attributes_ibfk_2` FOREIGN KEY (`type`) REFERENCES `attributes` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=26 DEFAULT CHARSET=latin1
I used NetBeans to generate an entity class from the table:
@Entity
@Table(name = "attributes")
@XmlRootElement
@NamedQueries({
    @NamedQuery(name = "Attributes.findAll", query = "SELECT a FROM Attributes a"),
    @NamedQuery(name = "Attributes.findById", query = "SELECT a FROM Attributes a WHERE a.id = :id"),
    @NamedQuery(name = "Attributes.findByName", query = "SELECT a FROM Attributes a WHERE a.name = :name")})
public class Attributes implements Serializable {
    private static final long serialVersionUID = 1L;
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Basic(optional = false)
    @Column(name = "id")
    private Integer id;
    @Size(max = 128)
    @Column(name = "name")
    private String name;
    @OneToMany(mappedBy = "parent")
    private Collection<Attributes> attributesCollection;
    @JoinColumn(name = "parent", referencedColumnName = "id")
    @ManyToOne
    private Attributes parent;
    @OneToMany(mappedBy = "type")
    private Collection<Attributes> attributesCollection1;
    @JoinColumn(name = "type", referencedColumnName = "id")
    @ManyToOne
    private Attributes type;
    @OneToMany(cascade = CascadeType.ALL, mappedBy = "attributes")
    private Collection<ItemAttributes> itemAttributesCollection;
    @OneToMany(mappedBy = "ivalue")
    private Collection<ItemAttributes> itemAttributesCollection1;
But how can I write a constructor for this entity? The auto-generated code gets around the issue by doing nothing; the constructor is empty. I can't help thinking that if I set the parent and type references to anything with new Attributes(), then it will recurse out of control. What else can/shall I do? I know how to rewrite it to not use the entity relations, but I'd prefer to make it work.

Cymae wrote:
I don't want to call the hash table creation method because from what i understand about interfaces the idea is that your main method doesnt know the table is actually a hash table...is that right?That's not exactly the idea. The idea to use the interface as the type instead of the implementation, is that your class probably doesn't need to know the full type. This makes it easy to change the implementation of the interface if needed. However, somebody at some point has to create the concrete object, a HashTable.
Basically, an interface describes a behavior, and a class that implements an interface decides how to actually perform this behavior. It is obviously impossible to perform the behavior if you are not told how to perform it.
Table table = new HashTable() is the correct way to do it. This means that if you ever need you Table implementation to change, the only thing you need to change in your whole class is this line. For example you might want Table table = new FileTable().

Self referencing table and contraint

Hi,
I have a self referencing table, used to store information on projects in an organization. There is a pimary key (modifier) and a foreign key to the modifier field (parentModifier)
Note: (modifier = project in the organization)
Basically, the parentModifier cannot be equal to the modifier in the same table, or equal to any of its children, otehrwise you get wierd recursive relationships. Its like saying you cannot be your own father, or one of your children cannot be your father. To get a list of the modifiers the parentModifier cannot be, the following statement can be used:
select
modifier
from
modifier
where
modifier = 'A'
and
level >= 1
connect by prior
modifier = parentModifier
start with
modifier = 'A'
order by
level;
So, now, I guess the way to do this is perform that query in a trigger before each row is being updated, so the pseudo code would be something like:
BEFORE UPDATE ON modifier
FOR EACH ROW
DECLARE
modifierToChange varchar2(255);
modifierList ???;
BEGIN
select
modifier
into
modifierList
from
modifier
where
modifier = 'A'
and
level >= 1
connect by prior
modifier = parentModifier
start with
modifier = 'A'
order by
level;
if modifierToChange in modifierList
return error
else
execute query
end if
END
As you can see my PL/SQL is limitied. At the moment I can handle this at the application layer (in php), but if the admin going to SQL Plus and starts to fiddle, they can easy break the system, by setting an invalid relationship.
I was wondeirng, if anyone could give me some help or advice, it would be fantastic,
Thanks!

Having a unique key on mod_id would be enough to make sure the same element is not in the structure more than once. By allowing it to happed you will have all the descendants of the dup element following it when you walk the tree.
Let's say this is the intended behavior.
Consider the following test scenario:
create table modifier (
mod_id varchar2(10),
parent_mod_id varchar2(10)
insert into modifier (mod_id, parent_mod_id) values ('a', null);
insert into modifier (mod_id, parent_mod_id) values ('aa', 'a');
insert into modifier (mod_id, parent_mod_id) values ('ab', 'a');
insert into modifier (mod_id, parent_mod_id) values ('ac', 'a');
insert into modifier (mod_id, parent_mod_id) values ('aaa', 'aa');
insert into modifier (mod_id, parent_mod_id) values ('aab', 'aa');
insert into modifier (mod_id, parent_mod_id) values ('aac', 'aa');
insert into modifier (mod_id, parent_mod_id) values ('aba', 'ab');
insert into modifier (mod_id, parent_mod_id) values ('abb', 'ab');
insert into modifier (mod_id, parent_mod_id) values ('abc', 'ab');
insert into modifier (mod_id, parent_mod_id) values ('aca', 'ac');
insert into modifier (mod_id, parent_mod_id) values ('acb', 'ac');
insert into modifier (mod_id, parent_mod_id) values ('acc', 'ac');
insert into modifier (mod_id, parent_mod_id) values ('b', null);
insert into modifier (mod_id, parent_mod_id) values ('ba', 'b');
insert into modifier (mod_id, parent_mod_id) values ('bb', 'b');
insert into modifier (mod_id, parent_mod_id) values ('bc', 'b');
insert into modifier (mod_id, parent_mod_id) values ('baa', 'ba');
insert into modifier (mod_id, parent_mod_id) values ('bab', 'ba');
insert into modifier (mod_id, parent_mod_id) values ('bac', 'ba');
insert into modifier (mod_id, parent_mod_id) values ('bba', 'bb');
insert into modifier (mod_id, parent_mod_id) values ('bbb', 'bb');
insert into modifier (mod_id, parent_mod_id) values ('bbc', 'bb');
insert into modifier (mod_id, parent_mod_id) values ('bca', 'bc');
insert into modifier (mod_id, parent_mod_id) values ('bcb', 'bc');
insert into modifier (mod_id, parent_mod_id) values ('bcc', 'bc');
commit;
SQL> select lpad(' ', 2 * (level - 1)) || mod_id item
2    from modifier
3   start with parent_mod_id is null
4 connect by prior mod_id = parent_mod_id;
ITEM
a
aa
    aaa
    aab
    aac
ab
    aba
    abb
    abc
ac
    aca
    acb
    acc
b
ba
    baa
    bab
    bac
bb
    bba
    bbb
    bbc
bc
    bca
    bcb
    bcc
26 rows selected
Create a function to verify if a mod_id already is parent_mod_id's ascendant or descendant:
create or replace function exists_in_parents_branch
i_mod_id in varchar2
,i_parent_mod_id in varchar2
) return boolean is
pragma autonomous_transaction;
v_dummy varchar2(10);
begin
select mod_id
    into v_dummy
    from (select mod_id
            from modifier
           where mod_id = i_mod_id
          connect by prior mod_id = parent_mod_id
           start with mod_id = i_parent_mod_id
          union
          select mod_id
            from modifier
           where mod_id = i_mod_id
          connect by prior parent_mod_id = mod_id
           start with mod_id = i_parent_mod_id);
return true;
exception
when no_data_found then
    return false;
end exists_in_parents_branch;
Create a trigger that calls the function above for every insert and update
create or replace trigger biu_modifier
before insert or update on modifier
for each row
begin
if exists_in_parents_branch(:new.mod_id, :new.parent_mod_id) then
    raise_application_error(-20000, 'Cannot insert or update because of recursive relationship.');
end if;
end biu_modifier;
You are all set.
Here is a statement that should fail:
SQL> insert into modifier (mod_id, parent_mod_id) values ('bcc', 'b');
insert into modifier (mod_id, parent_mod_id) values ('bcc', 'b')
ERROR at line 1:
ORA-20000: Cannot insert or update because of recursive relationship.
ORA-06512: at "RC.BIU_MODIFIER", line 3
ORA-04088: error during execution of trigger 'RC.BIU_MODIFIER'
Here is a statement that should succeed:
SQL> insert into modifier (mod_id, parent_mod_id) values ('aaaa','aaa');
1 row created.

PLS-00487: Invalid reference to variable ' expression '

oracle database 10G
OS unix
One of procedure is giving error PLS-00487: Invalid reference to variable '<expression>' while compilation in above database while it is compiling
successfully in other database.
Is there any database error?

PLS-00487: Invalid reference to variable "string"
Cause: A variable was referenced in a way that is inconsistent with its datatype. For example, a scalar variable might have been mistakenly referenced as a record, as follows: DECLARE CURSOR emp_cur IS SELECT empno, ename, sal FROM emp; emp_rec emp_cur%ROWTYPE; my_sal NUMBER(7,2); BEGIN ... total_sal := total_sal + my_sal.sal; -- invalid ...
Action: Check the spelling of the variable name. Make sure the variable was declared properly and that the declaration and reference are consistent regarding datatype.
Most probably the compiler "sees" some other type variable with the same name first which in the other database doesn't exist or is out of scope.
Regards
Etbin

Error:Invalid reference to variable 'PARTS1.PNUM%TYPE' - how to resolve

error:
ERROR at line 29:
ORA-06550: line 29, column 39:
PLS-00487: Invalid reference to variable 'PARTS1.PNUM%TYPE'
ORA-06550: line 29, column 4:
PL/SQL: SQL Statement ignored
DECLARE
cursor c1 is select pnum from parts1;
TYPE NumTab IS TABLE OF parts1.pnum%TYPE INDEX BY PLS_INTEGER;
TYPE NumTab1 IS TABLE OF parts1.pnum%TYPE INDEX BY PLS_INTEGER;
--TYPE NameTab IS TABLE OF parts1.pname%TYPE INDEX BY PLS_INTEGER;
pnums NumTab;
pnums1 NumTab1;
-- pnames NameTab;
--iterations CONSTANT PLS_INTEGER := 500;
t1 INTEGER;
t2 INTEGER;
t3 INTEGER;
l_num_index integer := 0;
BEGIN
FOR j IN 1..50000 LOOP -- load index-by tables
insert into parts1 values(j);
END LOOP;
commit;
t1 := DBMS_UTILITY.get_time;
/* FOR i IN 1..iterations LOOP -- use FOR loop
INSERT INTO parts1 VALUES (pnums(i));
END LOOP;
select pnum bulk collect into pnums from parts1;
t2 := DBMS_UTILITY.get_time;
open c1;
loop
l_num_index := l_num_index + 1;
fetch c1 into pnums1(l_num_index).pnum;
EXIT WHEN c1%notfound;
end loop;
close c1;
t3 := DBMS_UTILITY.get_time;
DBMS_OUTPUT.PUT_LINE('Execution Time (secs)');
DBMS_OUTPUT.PUT_LINE('---------------------');
DBMS_OUTPUT.PUT_LINE('FOR loop: ' || TO_CHAR((t2 - t1)/100));
DBMS_OUTPUT.PUT_LINE('FORALL: ' || TO_CHAR((t3 - t2)/100));
COMMIT;
END;
thanks,
vinodh

The line number in the error message is nearly always a good clue.
fetch c1 into pnums1(l_num_index).pnum;should be
fetch c1 into pnums1(l_num_index);

APP-FND-00798 invalid reference

hi all
while ctreating sales order i am getting this error
APP-FND-00798 invalid reference
AR_SRS_LOC_STRUCT_ID_BYSYSPAR in value set attached to segment gk.
please check the where clause of your table validetedvalue sets.
does anybody has an idea of this ...
pls help ,
naveen

I research and can't find an exact match on the metalink for the issue you are experiencing regarding AR_SRS_LOC_STRUCT_ID_BYSYSPAR with APP-FND-00798. I think you need to log a TAR for this issue.

XMLTRANSORM - LPX-00607: Invalid reference - xsl:variable

Hi,
I'm working on Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit.
I have a problem using XMLTRANSFORM method with variable (ie. SenderDN).
There is a table "ma_table" with three columns : "id", "data_xml" and "data_xsl".
Here is the query used :
SELECT XMLTRANSFORM (data_xml, data_xsl) FROM ma_table WHERE id = 64;Here is the data to transform :
<?xml version="1.0" encoding="ISO-8859-1"?>
<SOSTA xmlns="http://www.xxxxxx.com/yyyy/pipo">
     <infos>
          <generated>2009-08-19T16:23:56</generated>
          <reference_tech>ABCD123456789</reference_tech>
     </infos>
     <RECEDEP>AAAAAAAA</RECEDEP>
     <SENDERM>BBB</SENDERM>
     <REFSEND>5100161753</REFSEND>
     <QUALIFI>N</QUALIFI>
     <REFINTE>0010000934487</REFINTE>
     <TYPSTAT>IPRC</TYPSTAT>
     <STAREMT>REJT</STAREMT>
     <RAISON>DSEC</RAISON>
     <NARRA>blablabla</NARRA>
     <NARRA1>blablabla</NARRA1>
     <NARRA2/>
     <CENTRDT>20090819</CENTRDT>
     <STTLMDT>00000000</STTLMDT>
     <TYPSORA>SOU</TYPSORA>
     <INDMONT>O</INDMONT>
     <QUANTFI/>
     <SEAMMNT>10941,19</SEAMMNT>
     <CLIEDEV>EUR</CLIEDEV>
     <IFICODI>EEEEEEEEEE</IFICODI>
     <IFILIBE/>
     <IDCPTIT>123456789456132</IDCPTIT>
     <routage>
          <feuille name="tagada">
               <Destinataire>dest</Destinataire>
               <Priority>Normal</Priority>
               <IsNotificationRequested>false</IsNotificationRequested>
               <Service>dervice</Service>
          </feuille>
     </routage>
</SOSTA>And here is the stylesheet :
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
     xmlns:yyyy="http://www.xxxxxx.com/yyyy/pipo">
     <xsl:output method="xml" encoding="UTF-8" indent="yes"/>
     <xsl:variable name="SenderDN">sender dn</xsl:variable>
     <xsl:variable name="SenderBIC8">bic height</xsl:variable>
     <xsl:template match="/*">
          <DataPDU xmlns="urn:swift:saa:xsd:saa.2.0">
               <Header>
                    <Message>
                         <SenderReference>
                              <xsl:value-of select="./yyyy:infos/yyyy:reference_tech"/>
                         </SenderReference>
                         <MessageIdentifier>
                              <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:MessageIdentifier"/>
                         </MessageIdentifier>
                         <Format>MX</Format>
                         <Sender>
                              <DN>
                                   <xsl:value-of select="$SenderDN"/>
                              </DN>
                              <FullName>
                                   <X1>
                                        <xsl:value-of select="$SenderBIC8"/>
                                        <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:SenderBranchCode"/>
                                   </X1>
                              </FullName>
                         </Sender>
                         <Receiver>
                              <DN>
                                   <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:ReceiverDN"/>
                              </DN>
                              <FullName>
                                   <X1>
                                        <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:ReceiverBIC11"/>
                                   </X1>
                              </FullName>
                         </Receiver>
                         <InterfaceInfo>
                              <UserReference>
                                   <xsl:value-of select="./yyyy:infos/yyyy:reference_tech"/>
                              </UserReference>
                         </InterfaceInfo>
                         <NetworkInfo>
                              <Service>
                                   <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:Service"/>
                              </Service>
                         </NetworkInfo>
                    </Message>
               </Header>
               <Body>
                    <AppHdr>
                         <MsgRef>
                              <xsl:value-of select="./yyyy:infos/yyyy:reference_tech"/>
                         </MsgRef>
                         <CrDate>
                              <xsl:value-of select="./yyyy:infos/yyyy:generated"/>
                         </CrDate>
                    </AppHdr>
                    <Document> </Document>
               </Body>
          </DataPDU>
     </xsl:template>
</xsl:stylesheet>And I get this error message :
ORA-31011: XML parsing failed
ORA-19202: Erroroccured in XML processing
LPX-00607: Invalid reference: 'SenderDN'Why this error?
How to use this variable?
Thanks,
-Dominique

Hi,
I'va found the solution by modifying the <xsl:stylesheet> like this :
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
     xmlns:yyyy="http://www.xxxxxx.com/yyyy/pipo"
     xmlns="urn:swift:saa:xsd:saa.2.0">(adding xmlns="urn:swift:saa:xsd:saa.2.0")
But I don't understand why it work fine now ???
If anyone have an explanation?
Thanks,
-Dominique

Hiearchy Node [Alias] - unable to assign in the referencing table!

Hi All,
I really understand the definition and usage of Alias created in the Hierarchy & Taxonomy.
But is there any reason that am unable to assign or use these Alias Nodes in the referencing tables.
for example: Sales representative hierarchy by Region:
USA
- TX
     Agent1
- WI
     Agent2
- MI
     Agent3
- CA
     Agent1 [Alias]
Product table am using the above hierarchy and unable to assign/use the Alias node.
thanks
Alexander

Hi Alexander,
Hope you must have seen the below explanation about Alias
Sometimes, you may want a group of products to appear in more than one location in the hierarchy tree, so that they can be found in various ways using drilldown search. A node alias provides just this ability, and allows products assigned to a single node to appear in two or more locations in the tree. For example, in a repository of gifts, you may have a hierarchy that lists all of the holidays, and you may want u201CChristmasu201D to be found in the tree under the node u201CChristianu201D (if navigating by religion) and the node u201CDecemberu201D (if navigating by month).
Add Internal Leaf cannot be used for Children because you can directly use child nodes in the reference table and for parents you have Add Internal Leaf option if you want to assign parent node to the reference table record.
Regards,
Jitesh Talreja

Invalid reference in persistent store

Scenario: an object in the persistent store holds an invalid reference
(either an object with the referenced id does not exist or it can't be
instantiated for some other reason). When the object is loaded in
memory, an attempt to navigate the invalid reference does not generate
an exception, but instead returns a null. This doesn't seem correct.
I've attached a simple test case that demonstrates the problem.
Alex Albu
Commerce Technologies, Inc.
21 Corporate Drive
Clifton Park, NY 12065

I might be subjective here, but I don't agree, Abe. I don't think that
checking the return value of each method call is the norm in Java. It
is in C, but Java's exceptions are meant to relieve you from this
burden. After all, inconsistent data really is an exceptional
circumstance. Obviously, the granularity of your try/catch blocks,
won't be at the line level. To me, navigating a reference is very
similar with PersistenceManger.getObjectById(). It won't return a null
if the object isn't present in the data store.
Nulls are many times legal values and substituting them for invalid
references takes away the possibility to distinguish between good and
bad data. Code handling invalid references just like it handles nulls
is most likely going to produce wrong results whose cause is going to be
hard to determine.
We have gone to great lengths to ensure that our object model stays
consistent. For example, if A's bField is required by business rules to
be non-null, then our object model offers no way to construct an A
object with a null bField. So if there ise no circumstance under which
bField's getter would return null, why check? If the model has become
inconsistent, that's a serious issue (at least for us) and it is
critical for the application to signal that right away in a clear
fashion (NPE's don't mean anything to production support).
Anyway, as I said, this is just my opinion and I can see how other users
might find your decision suited for their applications. Offering an
option that allows users to control this behavior seems appropriate.
Abe White wrote:
And I'm not sure this behavior is helpful anyway. If you're
trying to dereference an invalid reference, you'll get a NPE,At least it's possible to check for nulls and avoid NPEs. If we threw
an execption on any attempt to load an invalid reference, it would be
impossible for users to avoid the exception.
Consider the following extremely common case:
* Object A has a field bField with a reference to object B.
* Object B is deleted, but the user does not null object A's bField reference.
* Later, the user finds object A and calls A.getBField () to do some operation
on the related B if it exists.
The vast majority of users just want a null to be returned if no related object
exists. Users almost always check for null when dealing with returned objects
in Java; it doesn't get in the way of their programming. Having the
possibility of any getter method for a relation throw an exception, though --
that would force users to build in a lot of exception handling code that
they wouldn't normally include. It breaks the transparency of JDO.
anyway. I guess the only way you can take advantage of this
feature (?) is to test references for null before accessing
them, which doesn't seem reasonable.As stated above, code like this:
B b = a.getBField ();
if (b != null)
is the norm in Java. Code like this:
B b;
try
b = a.getBField ();
catch (JDOUserException jue)
... what could I possibly do to recover here? ...
is not. Additionally, you would still need to do the null check in most
situations, because bField could simply have been set to null.
You can avoid either situation by keeping your object model consistent. This
feature is for careless users. If they're so careless that they also don't
check for null objects, then yes, they'll get a NPE. But with your solution,
they'd get an exception anyway, just a different kind... and an unavoidable
one at that.
I'm interested, though: how would throwing a JDOUserException immediately
help your code? If you can make a compelling enough case, we could offer
this as an option...

"Not using a pattern recognized by the GSA table invalidation mechanism" warning (many-to-many items relationships)

Hello.
I'm getting such warnings on server startup:
12:57:33,241 WARN [StoreRepository] Warning - table: store_user appears in item descriptors: store and user but not using a pattern recognized by the GSA table invalidation mechanism. Cached values from this table will not be updated when user's properties are modified. These properties for this table are: [storeUsers]
12:57:33,241 WARN [StoreRepository] Missing a src id property in item-descriptor user's table named store_user whose column-names are store_id
12:57:33,242 WARN [StoreRepository] Missing a dst id property in item-descriptor store's table named store_user whose column-names are user_id
12:57:33,242 WARN [StoreRepository] Missing a dst multi property in item-descriptor store's table named store_user whose column-name is store_id
12:57:33,242 WARN [StoreRepository] Warning - table: store_user appears in item descriptors: user and store but not using a pattern recognized by the GSA table invalidation mechanism. Cached values from this table will not be updated when store's properties are modified. These properties for this table are: [userStores]
12:57:33,243 WARN [StoreRepository] Missing a src id property in item-descriptor store's table named store_user whose column-names are user_id
12:57:33,243 WARN [StoreRepository] Missing a dst id property in item-descriptor user's table named store_user whose column-names are store_id
12:57:33,243 WARN [StoreRepository] Missing a dst multi property in item-descriptor user's table named store_user whose column-name is user_id
Here's repository definition file:
<item-descriptor name="user" id-space-name="user" display-name="User" display-property="name">
<table name="user_tbl" type="primary" id-column-name="user_id">
       <property name="id" column-name="user_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="user_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="user_id" multi-column-name="store_id">
       <property name="userStores" display-name="User Stores" data-type="map" column-names="email" component-data-type="string">
            <attribute name="propertySortPriority" value="-1" />
            <attribute name="uiwritable" value="false" />
       </property>
</table>
</item-descriptor>
<item-descriptor name="store" id-space-name="store" display-name="Store" display-property="name">
<table name="store_tbl" type="primary" id-column-name="store_id">
       <property name="id" column-name="store_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="store_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="store_id" multi-column-name="user_id">
       <property name="userStores" display-name="User Stores" data-type="map" column-names="email" component-data-type="string">
            <attribute name="propertySortPriority" value="-1" />
            <attribute name="uiwritable" value="false" />
       </property>
</table>
</item-descriptor>
I'll appreciate it, if someone tell me what's wrong with my definition.
Thank you in advance,
Jurii.

Hi Jurii,
You are right about ATG docs do not have info about M-M that can fit into your requirement. So we have to give it a try :-)
Please try with the below definition to see it it works.
user_tbl and store_tbl - no changes
store_user table has three columns - user_id, store_id and email
<item-descriptor name="user" id-space-name="user" display-name="User" display-property="name">
<table name="user_tbl" type="primary" id-column-name="user_id">
       <property name="id" column-name="user_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="user_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="user_id">
       <property name="store" display-name="Stores" data-type="set" column-names="store_id" component-item-type="store"/>
    <property name="email" display-name="User Store Email" data-type="set" column-names="email" component-data-type="string"/>
</table>
</item-descriptor>
<item-descriptor name="store" id-space-name="store" display-name="Store" display-property="name">
<table name="store_tbl" type="primary" id-column-name="store_id">
       <property name="id" column-name="store_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="store_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="store_id">
       <property name="user" display-name="Users" data-type="set" column-names="user_id" component-item-type="user"/>
    <property name="email" display-name="User Store Email" data-type="set" column-names="email" component-data-type="string"/>
</table>
</item-descriptor>
Thanks,
Gopinath Ramasamy

Problem creating Allocation Table with Reference to a PO

Dear Folks,
I am having problems creating an allocation table with reference to a PO in T-code WA01.
I read the SAP help that some prerequisites need to exist:
==> You can only reference order items flagged as being relevant to a stock split (the Allocation table relevant indicator in the additional item data).
Can anyone advice me where to find this stock split indicator?
Also, can anyone advice me how to reuse an allocation table? For example, I had previously created an allocation table with many articles and various allocation rules. I already generated follow on documents for this table.
Say after 2 weeks, I have the similar requirements that I can make use of the same table, only with minor adjustments to the quantity. How do I create a new allocation table using the existing allocation table data?
Thanks and Regards
Junwen

Any idea please?
thanks

PLS-S-00487, Invalid reference to variable while compiling PRO*C program

Hi,
I am writing a PRO*C code and get an error in compilation.
Code is as below:
+#include <stdio.h>+
+#include <string.h>+
EXEC SQL INCLUDE sqlca.h;
int main(int argc , char **argv)
+{+
int i;
EXEC SQL BEGIN DECLARE SECTION;
VARCHAR connString[100];
struct emp_record
+{+
char name[25];
char dept[10];
int id;
int salary;
int comm;
int tot_sal;
+}e1;+
EXEC SQL END DECLARE SECTION;
strcpy (connString.arr, "abcd/efgh@ijkl");
connString.len = strlen ( connString.arr);
+printf("\n Connection is [%d][%s]",connString.len,connString.arr);+
+EXEC SQL CONNECT :connString;+
+if(sqlca.sqlcode!=0)+
+{+
+printf("\nFailed to Connect, sqlcode is %d\n",sqlca.sqlcode);+
+printf("\nOracle Message = %s", sqlca.sqlerrm.sqlerrmc);+
+exit(-1);+
+}+
+else+
+{+
+printf("\nConnected\n");+
+}+
+EXEC SQL EXECUTE+
+BEGIN+
+emp_calc ( :e1.name,+
+:e1.id,+
+:e1.salary,+
+:e1.tot_sal+
+);+
+END;+
+END-EXEC;+
+if(sqlca.sqlcode!=0)+
+{+
+printf("Oracle Error:[%d][%s]",sqlca.sqlcode,sqlca.sqlerrm.sqlerrmc);+
+}+
+}+
Procedure code is:
+CREATE OR REPLACE PROCEDURE "EMP_CALC" (+
+pi_empname in emp.ename%type,+
+pi_empno in emp.empno%type,+
+pi_sal in emp.sal%type,+
+po_totsal out NUMBER)+
+is+
+begin+
+po_totsal := 1.1 * pi_sal;+
+dbms_output.put_line('Total Salary is:' || po_totsal);+
+end;+
*My main aim is to use elements of a structure in procedure call as parameters*
*But when I compile I get error on such usage as follows:*
Pro*C/C++: Release 11.2.0.3.0 - Production on Tue Apr 30 16:59:22 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
System default option values taken from: /mtsapp1/ora11g/product/11.2.0.3/dbhome_1/precomp/admin/pcscfg.cfg
Error at line 52, column 20 in file singleStructOra.pc
emp_calc ( :e1.name,
...................1
PLS-S-00487, Invalid reference to variable 'E1'
Error at line 52, column 1 in file singleStructOra.pc
emp_calc ( :e1.name,
1
PLS-S-00000, Statement ignored
Semantic error at line 50, column 1, file singleStructOra.pc:
BEGIN
1
PCC-S-02346, PL/SQL found semantic errors
*I would like to know how to resolve this compilation error and how do I use members of structures in such a procedure call.*
Thanks....

Sadly PL/SQL blocks do not understand structs (or arrays). DML statements do understand them.
This is not very clearly stated in the manual, but it does say:
http://docs.oracle.com/cd/E11882_01/appdev.112/e10825/pc_08arr.htm#autoId33
Restrictions on Arrays of Structs
The following restrictions apply to the use of arrays of structs in Pro*C/C++:
Arrays of structs (just as with ordinary structs) are not permitted inside an embedded PL/SQL block.
http://docs.oracle.com/cd/E11882_01/appdev.112/e10825/pc_07pls.htm#autoId13
Do not use C pointer or array syntax in PL/SQL blocks. The PL/SQL compiler does not understand C host-variable expressions and is, therefore, unable to parse them.
Although the example uses an array of structs, simple structs also fail. I have always had to copy the fields to and from simple variables when calling stored procedures.
regards,
David

Referencing Tables - "Invalid Reference"

Similar Messages

Maybe you are looking for