BC4J Custom API: Batch Validation with Sequence-based primary key

Hi people,
I am trying to create a BC4J Custom API using the Batch Validation feature of iSetup Framework. However, my entity object has a sequence-based primary key, and this key is carried to the View Object. This way, i have three attributes marked as key attributes in the VO: InvoiceTypeId (the sequence), OrganizationId and InvoiceTypeCode (The alternate, developer key). the primary key is marked AZ_EXPORTABLE=FALSE, because it must be rebuilt in the target using the alternate key.
I was able to successfully extract a single row to XML using this API (i am testing locally). When i try to import this XML file containing a single row, i get the following exception. Is this feature supported in Batch Validation mode?
Regards
Thiago Souza
** Exception starts **
Started import...
An exception occurred in API 'CLL Invoice Types'.
oracle.apps.fnd.framework.OAException: An exception occurred in API 'CLL Invoice Types'.
     at oracle.apps.az.fwk.BEUtil.wrapperException(BEUtil.java:395)
     at oracle.apps.az.fwk.server.BEImport.populateTempTableForBatchValidation(BEImport.java:1927)
     at oracle.apps.az.fwk.server.BEImport.importXML(BEImport.java:371)
     at oracle.apps.az.fwk.server.BEApplicationModuleImpl.importFromXML(BEApplicationModuleImpl.java:404)
     at R12APITester.importFile(R12APITester.java:205)
     at R12APITester.importFile(R12APITester.java:180)
     at R12APITester.main(R12APITester.java:65)
## Detail 0 ##
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-06550: line 32, column 29:
PL/SQL: ORA-00904: "KEY31": invalid identifier
ORA-06550: linha 32, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 33, coluna 29:
PL/SQL: ORA-00904: "KEY32": invalid identifier
ORA-06550: linha 33, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 34, coluna 29:
PL/SQL: ORA-00904: "KEY33": invalid identifier
ORA-06550: linha 34, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 35, coluna 29:
PL/SQL: ORA-00904: "KEY34": invalid identifier
ORA-06550: linha 35, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 36, coluna 29:
PL/SQL: ORA-00904: "KEY35": invalid identifier
ORA-06550: linha 36, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 37, coluna 29:
PL/SQL: ORA-00904: "KEY36": invalid identifier
ORA-06550: linha 37, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 38, coluna 29:
PL/SQL: ORA-00904: "KEY37": invalid identifier
ORA-06550: linha 38, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 39, coluna 29:
PL/SQL: ORA-00904: "KEY38": invalid identifier
ORA-06550: linha 39, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 40, coluna 29:
PL/SQL: ORA-00904: "KEY39": invalid identifier
ORA-06550: linha 40, coluna 1:
PL/SQL: SQL Statement ignored
ORA-06550: linha 41, coluna 29:
PL/SQL: ORA-00904: "KEY40": invalid identifier
ORA-06550: linha 41, coluna 1:
PL/SQL: SQL Statement ignored
     at oracle.apps.fnd.framework.OAException.wrapperException(Unknown Source)
     at oracle.apps.az.fwk.server.BEValidationXMLParser.executeSql(BEValidationXMLParser.java:288)
     at oracle.apps.az.fwk.server.BEValidationXMLParser.collectUKFKValues(BEValidationXMLParser.java:254)
     at oracle.apps.az.fwk.server.BEImport.populateTempTableForBatchValidation(BEImport.java:1897)
     at oracle.apps.az.fwk.server.BEImport.importXML(BEImport.java:371)
     at oracle.apps.az.fwk.server.BEApplicationModuleImpl.importFromXML(BEApplicationModuleImpl.java:404)
     at R12APITester.importFile(R12APITester.java:205)
     at R12APITester.importFile(R12APITester.java:180)
     at R12APITester.main(R12APITester.java:65)

Hi Thiago,
I would suggest to test your API first with row by row validation mode where you would be resolving the foreign and primary keys as specified in the framework. This would help you to understand the framework better and once it starts working for you and then you can try with batch validation mode.
Thanks
Mugunthan.

Similar Messages

Best practices with sequences and primary keys

We have a table of system logs that has a column called created_date. We also have a UI that displays these logs ordered by created_date. Sometimes, two rows have the exact same created_date down to the millisecond and are displayed in the UI in the wrong order. The suggestion was to order by primary key instead since the application uses an oracle sequence to insert records so the order of the primary key will be chronological. I felt this may be a bad idea as a best practice since the primary key should not be used to guarantee chronological order although in this particular application's case, since it is not a multi-threaded environment, it will work so we are proceeding with it.
The value for the created_date is NOT set at the database level (as sysdate) but rather by the application when it creates the object which is persisted by Hibernate. In a multi-threaded environment, thread A could create the object and then get blocked by thread B which is able to create the object and persist it with key N after which control returns to thread A it persists it with key N+1. In this scenario thread A has an earlier timestamp but a larger key so will be ordered before thread B which is in error.
I like to think of primary keys as solely something to be used for referential purposes at the database level rather than inferring application level meaning (like the larger the key the more recent the record etc.). What do you guys think? Am I being too rigorous in my views here? Or perhaps I am even mistaken in how I interpret this?

>
I think the chronological order of records should be using a timestamp (i.e. "order by created_date desc" etc.)
>
Not that old MYTH again! That has been busted so many times it's hard to believe anyone still wants to try to do that.
Times are in chronological order: t1 is earlier (SYSDATE-wise) than t2 which is earlier than t3, etc.
1. at time t1 session 1 does an insert of ONE record and provides SYSDATE in the INSERT statement (or using a trigger).
2. at time t3 session 2 does an insert of ONE record and provides SYSDATE
(which now has a value LATER than the value used by session 1) in the INSERT statement.
3. at time t5 session 2 COMMITs.
4. at time t7 session 1 COMMITs.
Tell us: which row was added FIRST?
If you extract data at time t4 you won't see ANY of those rows above since none were committed.
If you extract data at time t6 you will only see session 2 rows that were committed at time t5.
For example if you extract data at 2:01pm for the period 1pm thru 1:59pm and session 1 does an INSERT at 1:55pm but does not COMMIT until 2:05pm your extract will NOT include that data.
Even worse - your next extract wll pull data for 2pm thru 2:59pm and that extract will NOT include that data either since the SYSDATE value in the rows are 1:55pm.
The crux of the problem is that the SYSDATE value stored in the row is determined BEFORE the row is committed but the only values that can be queried are the ones that exist AFTER the row is committed.
About the best you, the user (i.e. not ORACLE the superuser), can do is to
1. create the table with ROWDEPENDENCIES
2. force delayed-block cleanout prior to selecting data
3. use ORA_ROWSCN to determine the order that rows were inserted or modified
As luck would have it there is a thread discussing just that in the Database - General forum here:
ORA_ROWSCN keeps increasing without any DML

Error While Deploying A CMP Entity Bean With A Composite Primary Key

Hello all,
I have a problem deploying CMP Entity beans with composite primary keys. I have a CMP Entity Bean, which contains a composite primary key composed of two local stubs. If you know more about this please respond to my post on the EJB forum (subject: CMP Bean Local Stub as a Field of a Primary Key Class).
In the mean time, can you please tell me what following error message means and how to resolve it? From what I understand it might be a problem with Sun ONE AS 7, but I would like to make sure it's not me doing something wrong.
[05/Jan/2005:12:49:03] WARNING ( 1896):      Validation error in bean CustomerSubscription: The type of non-static field customer of the key class
test.subscription.CustomerSubscriptionCMP_1530383317_JDOState$Oid must be primitive or must implement java.io.Serializable.
     Update the type of the key class field.
     Warning: All primary key columns in primary table CustomerSubscription of the bean corresponding to the generated class test.subscription.CustomerSubscriptionCMP_1530383317_JDOState must be mapped to key fields.
     Map the following primary key columns to key fields: CustomerSubscription.CustomerEmail,CustomerSubscription.SubscriptionType. If you already have fields mapped to these columns, verify that they are key fields.Is it enough that a primary key class be serializable or all fields have to implement Serializable or be a primitive?
Please let me know if you need more information to answer my question.
Thanks.
Nikola

Hi Nikola,
There are several problems with your CMP bean.
1. Fields of a Primary Key Class must be a subset of CMP fields, so yes, they must be either a primitive or a Serializable type.
2. Sun Application Server does not support Primary Key fields of an arbitrary Serializable type (i.e. those that will be stored
as BLOB in the database), but only primitives, Java wrappers, String, and Date/Time types.
Do you try to use stubs instead of relationships or for some other reason?
If it's the former - look at the CMR fields.
If it's the latter, I suggest to store these fields as regular CMP fields and use some other value as the PK. If you prefer that
the CMP container generates the PK values, use the Unknown
PrimaryKey feature.
Regards,
-marina

Sql*loader and sequence() for primary keys

I have a question regarding SQL*Loader with the sequence() function and using it for a primary key to load records in multiple tables from one input record. I am pulling data from a delimited file and populating several tables from each row. For the primary key, I am using the sequence function.
For the first table (the parent), I use sequence(40000,1) for the key. Since the remaining inserts are based on the same logical record, I use sequence(40000,1) for those too (one record for each month). The problem comes in when a child record does not pass a WHEN clause (the amount is zero). Then it almost seems as if the parent record is not loaded and the child (or children) that does pass the WHEN clause are assigned to the next parent! Obviously, the sequence is getting out of sync between the children and the parent.
I've looked in the documentation and tried several different ways to attack this problem. Is there a bug in SQLLDR (8.1.7) or is it just my coding.
I will try to include the files below but they are very large.
Thanks for your help.
Dan
***CONTROL FILE***
LOAD DATA
INFILE 'rent.csv'
INTO TABLE BUDGET_LINE
append
WHEN TOT_AMT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER CHAR,
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
JUL_AMT          FILLER CHAR,
JUL_CNT          FILLER CHAR,
AUG_AMT          FILLER CHAR,
AUG_CNT          FILLER CHAR,
SEP_AMT          FILLER CHAR,
SEP_CNT          FILLER CHAR,
OCT_AMT          FILLER CHAR,
OCT_CNT          FILLER CHAR,
NOV_AMT          FILLER CHAR,
NOV_CNT          FILLER CHAR,
DEC_AMT          FILLER CHAR,
DEC_CNT          FILLER CHAR,
CUT               FILLER CHAR,
NETMANGEN          FILLER CHAR,
NETMAN_item          BOUNDFILLER CHAR,
NETMAN_item_seq     BOUNDFILLER CHAR,
NETMAN_location     BOUNDFILLER CHAR,
UPDATED_ON          DATE "MM/DD/YYYY",
NETMAN_com_desc     BOUNDFILLER CHAR,
NETMAN_vendor          BOUNDFILLER CHAR,
NETMAN_generation     BOUNDFILLER CHAR,
CREATED_ON          SYSDATE,
CREATED_BY          CONSTANT '0',
UPDATED_BY          CONSTANT '0',
ACTIVE          CONSTANT 'T',
GL_CODE_COMBO_ID     CONSTANT '0',
BUDGET_TYPE          CONSTANT 'B',
AMOUNT_TYPE          CONSTANT 'D',
source          constant 'N',
BUDGET_LINE_ID     SEQUENCE(40000,1),
DESCRIPTION          "(:NETMAN_item)||'-'||(:NETMAN_item_seq)||'; '||:NETMAN_com_desc||'; '||:NETMAN_vendor||' ('||:NETMAN_generation||')'"
INTO TABLE GL_CODE_TEMP
append
WHEN TOT_AMT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
SPENDER          CHAR ,
ACCT               CHAR ,
TOT_AMT          FILLER CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '1',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '2',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '3',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '4',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '5',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '6',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '7',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '8',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
JUL_AMT          FILLER CHAR,
JUL_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '9',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
JUL_AMT          FILLER CHAR,
JUL_CNT          FILLER CHAR,
AUG_AMT          FILLER CHAR,
AUG_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '10',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
JUL_AMT          FILLER CHAR,
JUL_CNT          FILLER CHAR,
AUG_AMT          FILLER CHAR,
AUG_CNT          FILLER CHAR,
SEP_AMT          FILLER CHAR,
SEP_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '11',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
JUL_AMT          FILLER CHAR,
JUL_CNT          FILLER CHAR,
AUG_AMT          FILLER CHAR,
AUG_CNT          FILLER CHAR,
SEP_AMT          FILLER CHAR,
SEP_CNT          FILLER CHAR,
OCT_AMT          FILLER CHAR,
OCT_CNT          FILLER CHAR,
AMOUNT          CHAR
INTO TABLE BUDGET_COST
append
WHEN AMOUNT != '0'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
NETMAN_ITEM_NO      FILLER POSITION(1) CHAR TERMINATED BY ',',
BUDGET_LINE_ID     SEQUENCE(40000,1),
PERIOD_ID          CONSTANT '12',
SPEND               FILLER CHAR,
ACCOUNT          FILLER CHAR,
TOT_AMT          FILLER CHAR,
JAN_AMT          FILLER CHAR,
JAN_CNT          FILLER CHAR,
FEB_AMT          FILLER CHAR,
FEB_CNT          FILLER CHAR,
MAR_AMT          FILLER CHAR,
MAR_CNT          FILLER CHAR,
APR_AMT          FILLER CHAR,
APR_CNT          FILLER CHAR,
MAY_AMT          FILLER CHAR,
MAY_CNT          FILLER CHAR,
JUN_AMT          FILLER CHAR,
JUN_CNT          FILLER CHAR,
JUL_AMT          FILLER CHAR,
JUL_CNT          FILLER CHAR,
AUG_AMT          FILLER CHAR,
AUG_CNT          FILLER CHAR,
SEP_AMT          FILLER CHAR,
SEP_CNT          FILLER CHAR,
OCT_AMT          FILLER CHAR,
OCT_CNT          FILLER CHAR,
NOV_AMT          FILLER CHAR,
NOV_CNT          FILLER CHAR,
AMOUNT          CHAR
*** PIECE OF DATA FILE ***
Item,Spender,Account,Total Amt,Jan Amt,Jan Count,Feb Amt,Feb Count,Mar Amt,Mar Count,Apr Amt,Apr Count,May Amt,May Count,Jun Amt,Jun Count,Jul Amt,Jul Count,Aug Amt,Aug Count,Sep Amt,Sep Count,Oct Amt,Oct Count,Nov Amt,Nov Count,Dec Amt,Dec Count,Status,Netman Gen,Netman Item,Netman Unit,Location,Last Update Date,Component Description,Vendor Description,Generation Process
10110993,10993,8301-01,90134,7480,0,7480,0,7480,0,7480,0,7480,0,7480,0,7480,0,7480,0,7480,0,7480,0,7667,0,7667,0,0,+,LEASE PYMT,207,WIMOS,5/22/2002,LEASE PAYMENTS,"VIKING HOLDING, INC.",ACTUAL BUDGET
10410993,10993,8301-04,15240,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,1270,0,0,+,JANITORIAL,58,WIMOS,5/22/2002,JANITORIAL,BUILDING ONE SVC SOLUTION,ACTUAL BUDGET
10810993,10993,8301-08,2232,186,0,186,0,186,0,186,0,186,0,186,0,186,0,186,0,186,0,186,0,186,0,186,0,0,+,ELECTRIC,77,WIMOS,5/22/2002,"UTILITIES (GAS,ELEC.,ETC)",WISCONSIN PUBLIC SERVICE,AVGD 01 04 07 10 NOT WEIGHTED
10910993,10993,8301-09,4220,26,0,348,0,609,0,383,0,348,0,371,0,348,0,371,0,360,0,348,0,360,0,348,0,0,+,FIRE EQUIP,51,WIMOS,5/22/2002,RENT CONTRACT SERVICES,"CENTRALCOM, INC.",ACTUAL EXPERIENCE
11610993,10993,8301-16,1272,106,0,106,0,106,0,106,0,106,0,106,0,106,0,106,0,106,0,106,0,106,0,106,0,0,+,L/H MOSINE,1,WIMOS,5/22/2002,LEASEHOLD IMPROVEMENTS,ELLIS STONE,ACTUAL BUDGET
10110994,10994,8301-01,69960,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,5830,0,0,+,LEASE PYMT,228,WISTEWEL,5/22/2002,LEASE PAYMENTS,BJ INVESTMENTS LLC,ACTUAL BUDGET
10410994,10994,8301-04,840,70,0,70,0,70,0,70,0,70,0,70,0,70,0,70,0,70,0,70,0,70,0,70,0,0,+,JANITORIAL,69,WISTEWEL,5/22/2002,JANITORIAL,MARSDEN,ACTUAL BUDGET
10710994,10994,8301-07,6067,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,6067,0,0,+,LEASE PYMT,228,WISTEWEL,5/22/2002,LEASE PAYMENTS,BJ INVESTMENTS LLC,ASSUME 5% INCREASE OVER ACTUAL 2000 EXPENSES
10810994,10994,8301-08,2460,205,0,205,0,205,0,205,0,205,0,205,0,205,0,205,0,205,0,205,0,205,0,205,0,0,+,ELECTRIC,84,WISTEWEL,5/22/2002,"UTILITIES (GAS,ELEC.,ETC)",BJ INVESTMENTS LLC,AVGD 03 06 09 NOT WEIGHTED
10910994,10994,8301-09,1050,70,0,70,0,105,0,105,0,70,0,105,0,35,0,140,0,35,0,70,0,210,0,35,0,0,+,SANITATION,12,WISTEWEL,5/22/2002,RENT CONTRACT SERVICES,WASTE MANAGEMENT OF WIS,ACTUAL EXPERIENCE
11910994,10994,8301-19,1099,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1099,0,0,0,0,0,0,0,0,0,0,+,INSURANCE,6,WISTEWEL,5/22/2002,INSURANCE,BJ INVESTMENTS LLC,ACTUAL EXPERIENCE
10110998,10998,8301-01,2440,2440,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,+,LEASE PYMT,47,ILELG,5/22/2002,LEASE PAYMENTS,ELGIN AIRPORT BUSINESS PK,ACTUAL BUDGET
10410998,10998,8301-04,146,146,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,+,LEASE PYMT,47,ILELG,5/22/2002,LEASE PAYMENTS,ELGIN AIRPORT BUSINESS PK,ACTUAL BUDGET
10610998,10998,8301-06,336,28,0,28,0,28,0,28,0,28,0,28,0,28,0,28,0,28,0,28,0,28,0,28,0,0,+,DRINK H2O,46,ILELG,5/22/2002,COOLER AND BOTTLED WATER,"HINCKLEY & SCHMITT, INC.",AVGD 01 02 03 04 05 06 07 08 09 10
10710998,10998,8301-07,276,276,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,+,LEASE PYMT,47,ILELG,5/22/2002,LEASE PAYMENTS,ELGIN AIRPORT BUSINESS PK,ASSUME 5% INCREASE OVER ACTUAL 2000 EXPENSES
10810998,10998,8301-08,3108,433,0,315,0,234,0,173,0,181,0,292,0,320,0,337,0,316,0,153,0,183,0,171,0,0,+,ELECTRIC,20,ILELG,5/22/2002,"UTILITIES (GAS,ELEC.,ETC)",COMMONWEALTH EDISON,AVGD 01 02 03 04 05 06 07 08 09 10 WEIGHTED
*** SCRIPT FOR TABLES LOADED ***
CREATE TABLE BUDGET_LINE (
BUDGET_LINE_ID NUMBER NOT NULL,
BUDGET_TYPE CHAR (1) NOT NULL,
GL_CODE_COMBO_ID NUMBER NOT NULL,
AMOUNT_TYPE CHAR (1) NOT NULL,
ACTIVE CHAR (1) DEFAULT 'T' NOT NULL,
SOURCE CHAR (1),
CUT CHAR (1),
DESCRIPTION VARCHAR2 (180),
CAP_ITEM_ID NUMBER,
PBT_ID NUMBER,
BILL_ID NUMBER,
CREATED_ON DATE DEFAULT SYSDATE NOT NULL,
CREATED_BY NUMBER NOT NULL,
UPDATED_ON DATE DEFAULT SYSDATE NOT NULL,
UPDATED_BY NUMBER NOT NULL,
CHECK (ACTIVE IN ('T','F') ) ,
CHECK (CUT IN ('C',NULL) ),
CONSTRAINT BUDGET_LINE_PRI
PRIMARY KEY ( BUDGET_LINE_ID ) ) ;
CREATE TABLE BUDGET_COST (
BUDGET_LINE_ID NUMBER NOT NULL,
PERIOD_ID NUMBER NOT NULL,
AMOUNT NUMBER (13,2),
CONSTRAINT BUDGET_COST_PRI
PRIMARY KEY ( BUDGET_LINE_ID, PERIOD_ID ) ) ;
CREATE TABLE GL_CODE_TEMP (
BUDGET_LINE_ID NUMBER NOT NULL,
SPENDER CHAR (5),
ACCT CHAR (7),
GL_CODE_COMBO_ID NUMBER,
CONSTRAINT GL_CODE_TEMP_BDGT_ID
PRIMARY KEY ( BUDGET_LINE_ID ) ) ;

Thanks for the reply .. user do have their user credentials but only for the application ... but all users use a common loader and control file once they log into the application. So irrespective of which user is logged in he selects the same control file and loads to the same table mentioned in the control file .. i instead want user to be able to load to the table in control file but into his schema like username.tablename instead of just the tablename mentioned in .ctl file.

Creating entity beans with auto numbered primary key

I have two entity bean with a CMR between them. I am successfully creating the first one but when I try and create the child entity bean I get a NullPointerException.
Now I think this is because the gernerated code tries to get the primary key of the created entity bean and this is not set as it is set using a auto number in the database (An oracle sequence and trigger).
Is there anyway i can get round this problem?
Thanks in advance,
Adrian

This is the auto generated code:
     public dmd.sync.ejbs.entity.AppliancePackInfoLocal create_Local(dmd.sync.dataobjects.dto.AppliancePackInfoDTO appliancePackInfoDTO, dmd.sync.ejbs.entity.AmppLocal amppLocal) throws javax.ejb.CreateException, java.rmi.RemoteException {
          BeanO beanO = null;
          dmd.sync.ejbs.entity.AppliancePackInfoLocal result = null;
          boolean createFailed = false;
          boolean preCreateFlag = false;
          try {
               beanO = super.createBeanO();
               dmd.sync.ejbs.entity.AppliancePackInfoBean bean = (dmd.sync.ejbs.entity.AppliancePackInfoBean) beanO.getEnterpriseBean();
               preCreateFlag = super.preEjbCreate(beanO);
               bean.ejbCreate(appliancePackInfoDTO, amppLocal);
               Object ejsKey = keyFromBean(bean);
               result = (dmd.sync.ejbs.entity.AppliancePackInfoLocal) super.postCreate_Local(beanO, ejsKey, true);
               bean.ejbPostCreate(appliancePackInfoDTO, amppLocal);
               super.afterPostCreate(beanO, ejsKey);
It must be falling over on the last line as it calls the ejbPostCreate fine.

Switch the sequence of Primary Key Columns

Hi MaxDB experts,
As part of our product upgrade we've made a schema change to 10 of our database tables. Typically these tables contain about 5 million rows in them. The change involves switching the order of columns in the primary key (original order SampleTime, Id; new order would be Id, SampleTime). What's the quickest way to achieve this?
So far I've tried the following approaches without much luck:
1. Use the "alter table alter primary key (new seuqence of columns)". Takes an average of 1 hour per table.
2. Copy original table content into another table with "insert into newTable (select * from existingTable)" command. Takes the same amount of time as #1
3. Tried using "Export Table" option presented by the "loadercli". Unfortunately, exported data can not be imported to a table with a different schema (in our case changed primary key column sequence).
What else can we try? Any advise / direction would be greatly appreciated. Thanks for your time.
Sincerely,
Sameer Apte

Hi there,
ok, I assume that you figured out that you like to have data entries belonging to a specific ID stored rather nearby than scattered around in the table by TIMESTAMP or that you have more queries that specify the ID but not the TIMESTAMP.
Both would be good reasons to perform such a change.
Concerning the speed: basically things won't get any faster than ALTER TABLE or INSERT (SELECT * FROM)...
The ALTER TABLE approach would have the advantage to be transactional atomic and simple to use.
The INSERT approach would enable the use of the PREFETCHING feature for the read-I/O on the source table.
So if you're just focussing on speed, then I'd recommend to:
setup a data cache that can hold both source and target tables im memory
enable prefetching by setting the parameter READAHEAD_TABLE_THRESHOLD to say 128 (be aware that you've to use MaxDB 7.6.05 or higher, but not 7.7.x for that!)
After you've copied each table, make sure to create the secondary indexes one by one since otherwise the internal parallelism won't be used.
regards,
Lars
p.s.
it is possible to export/import into different schemas - it's even supported via DB Studio.
Anyhow, it wouldn't make anything quicker for this case.

Master-detail with auto-generated primary key(master)

Hello,
I have the following master-detail setup:
Master - block A primary key is: codeA
Detail - block B
codeA is genrated only at commit time and is obtained from a sequence.
User needs to add detail records. This is easy to do since he has to click on the insert icon on the toolbar. At commit time, use commit_form.
Prob: the requirements as asked by the client is to add a button (which we will label INSERT DETAIL). When the user click on the button, it opens a window where he can enter the detail info then click on save. This should bring him back to the master-detail form and the record in the detail block is inserted.
What is the problem here ? since the detail block has the foreign key tied to the master primary key, the window-form (with the call_form) that we opened for the detail entry won't be able to save since at this point we still have not assigned a value for the primary key (and hence a value for the foreign key).
Possible Suggestions:
-Use a temp database table to hold the detail record from the second form and use it to transfer values to the detail record in the master-detail
-Use a global record group
-We can't use parameter list to pass back these values.
So my question is:
What would be the most efficient way to have an insert button on the detail block that would allow the user to have a pop up where he can insert his values and then be brought back to the master-detail.
Thanks.

Hello again,
May be I was not clear enough.
Scenario 1: We use the master-detail form as is with the default oolbar. In this case, the user can insert the detail records one by one without needing the primary-foreign key value since this is handled by default.
Once we save the form (commit_form), I use the pre-insert trigger to get the master block primary key generated from the sequence and since the detail block key is copied from this value, both are saved correctly and it is the end of the story.
Scenario 2: As explained in the initial post, the user will populate the detail records one by one by clicking on the -INSERT DETAIL- button and hence has a window where he can insert the detail info and then be brought back to the master-detail form every time he enters a new detail record.
The problem here is that I can't generate the primary key for the master block since the client has the following requirement:
The user can always change his mind and not complete, meaning save the form, his process
As such, the key should be generated in the last step before Commit.

Batch processing problem: Seeing the primary key (id) in the test cases...

Another problem we seem to be having is how to read the primary key into a base attribute of an entity.
In batch processing, we may define the "id" as the primary key on the table. We need to get that id and the foreign key ids into the base attributes in the rule set...
How do we go about doing that?

Perhaps better, if you could give me a sample xml config with global and one entity. The only attribute in the entity should be the id... The id should be the primary key in both OPA and Oracle...
The global table in oracle would contain a single column with the global id.
The child table in oracle would contain 2 columns -> one for the global ref id and one for the child key...
I think you will find problems.
As a note we have duct-tape solved this by creating views and making column copies in the views of the child id and then mapping the id in oracle to the duplicate column in the view.
So our child view contains the child table with the child id repeated twice so that we can map...

Does ADF Business Components work well with tables without primary Key?

We have tables using unique index without primary key. Can ADF Business Components relate business objects based on the unique index columns of the tables?

Hi,
Regarding my question about the XML syntax for custom properties:
It turned out to be another problem in the Entity object definition that caused the JDeveloper error. Other entities let me add the custom property without problems. However should anybody ever need that XML syntax, here's how you add a custom property to an entity definition in the XML code:
<Attribute
    Name="Id"
    IsNotNull="true"
    Precision="10"
    Scale="0"
    ColumnName="ID"
    Type="oracle.jbo.domain.Number"
    ColumnType="NUMBER"
    SQLType="NUMERIC"
    TableName="TABLE"
    PrimaryKey="true">
    <DesignTime>
      <Attr Name="_DisplaySize" Value="22"/>
    </DesignTime>
    <Properties>
      <CustomProperties>
        <Property
          Name="SequenceName"
          Value="SEQ1"/>
      </CustomProperties>
    </Properties>
</Attribute>Best regards,
Bart Kummel
Edited by: Bart Kummel on Sep 8, 2009 1:14 PM

Problem with foreign and primary keys migration from SQL Server to Oracle

Hi folks, i'm using SQL Developer to migrate from a SQL Server database to Oracle and i'm stuck with a couple issues:
The worst of them so far is the fact that i can't migrate any of the PKs and FKs. After successfully capturing the SQL Server DB model and converting it to Oracle, when the tool generates the scripts, all ALTER TABLE queries that add the PKs and FKs have their target columns duplicated.
for example: when i'm trying to migrate a simple table that contains an Id (PK) and Name columns, the tool generates the following scripts:
PROMPT Creating Table TestTable...
CREATE TABLE TestTable (
Id NUMBER(10,0) NOT NULL,
Name VARCHAR2 NOT NULL
PROMPT Creating Primary Key Constraint PK_TestTable on table TestTable ...
ALTER TABLE TestTable
ADD CONSTRAINT PK_TestTable PRIMARY KEY
Id,
Id
ENABLE
As for the FKs, the tool duplicates the columns as well:
ALTER TABLE SomeTable
ADD CONSTRAINT FK_SomeTable_SomeTable2 FOREIGN KEY
SomeTable2Id,
SomeTable2Id
REFERENCES SomeTable2
Id,
Id
ENABLE
Does anyone have a clue on how to solve these issues? I'd be greatly thankful for any answers!

Hi Fernando,
I was unable to replicate this issue. My primary / foreign keys where defined using unique columns.
PROMPT Creating Primary Key Constraint PK_Suppliers on table Suppliers ...
ALTER TABLE Suppliers
ADD CONSTRAINT PK_Suppliers PRIMARY KEY
SupplierID
ENABLE
I tried a few things like
capturing twice and renaming both models the same
renaming the converted models
but with no luck.
I think this issue is occuring either at the capture or convert phase.
1) Are you performing the capture online or offline?
2) Can you provide a the entire DDL for one of these tables and its indexes to see if I can replicate?
3) Did the capture or convert fail or have to be redone at any stage ?
I all else fails I would attempt a capture and convert again using a brand new repository (create a new schema in Oracle and associate the migration repository with it).
Regards,
Dermot
SQL Developer Team
Edited by: Dermot ONeill on Oct 22, 2009 12:18 PM

Master Detail Forms with 2 composite primary keys - Is there a workaround?

Hello All,
I have been searching for a workaround to the maximum 2 part primary key restriction on the multi-row updates, and master-detail forms, and am hoping that someone can help me. I am using HTMLDB v2.0.0.00.49 with IE 6 against a 9.2 DB.
I successfully implemented the workaround of Fred Stoopendaal's (see Updata PK on HTML DB ) and it works fine for single page multi-record updateable forms, but alas I haven't been able to extend it to master detail forms (I think it is something to do with Oracle not allowing the "returning" clause on views).
Here is what I tried:
two tables, one with a 2 part composite primary key, which is the master table, and a detail table with 3 part composite primary key -
--------- BEGIN SQL ---------
create table master_table
( master_col1 number
, master_col2 number
, master_col3 varchar2(30)
, constraint master_pk primary key (master_col1,master_col2));
create table detail_table
(detail_col1 number
,detail_col2 number
,detail_col3 number
,detail_col4 varchar2(30)
, constraint detail_pk primary key(detail_col1,detail_col2,detail_col3)
, constraint master_detail_fk foreign key (detail_col1,detail_col2) references master_table(master_col1,master_col2));
create or replace view v_master_table as
select rowid mata_rowid,mata.*
from master_table mata;
create or replace view v_detail_table as
select rowid deta_rowid,
(select rowid from master_table mata where mata.master_col1 = deta.detail_col1 and mata.master_col2 = deta.detail_col2) deta_mata_rowid
, deta.*
from detail_table deta;
create or replace trigger mata_ins_upd_trg
instead of insert or update on v_master_table
referencing new as new old as old
for each row
begin
if inserting then
insert into master_table (master_col1, master_col2, master_col3)
values (:new.master_col1, :new.master_col2, :new.master_col3);
end if;
if updating then
update master_table
set master_col1 = :new.master_col1,
master_col2 = :new.master_col2,
master_col3 = :new.master_col3
where rowid = :old.mata_rowid;
end if;
end;
create or replace trigger deta_ins_upd_trg
instead of insert or update on v_detail_table
referencing new as new old as old
for each row
begin
if inserting then
insert into detail_table ( detail_col1, detail_col2, detail_col3, detail_col4)
values (:new.detail_col1, :new.detail_col2, :new.detail_col3, :new.detail_col4);
end if;
if updating then
update detail_table
set detail_col1 = :new.detail_col1,
detail_col2 = :new.detail_col2,
detail_col3 = :new.detail_col3,
detail_col4 = :new.detail_col4
where rowid = :old.deta_rowid;
end if;
end;
--------- END SQL ---------
Then I created a master-detail form in Apex on the two views, using the mata_rowid and deta_rowid as primary keys, and mata_rowid=deta_mata_rowid as the link. I realise that using a function to fetch the master rowid within the detail view query is costly, but it was my intention to modify the record fetch queries to use the real FK columns once things were up and running.
It seems to generate the pages ok, and I can insert/update master table records, but as soon as I modify records in the detail table things go a bit haywire. I can't find any documentation on how the inbuilt MRU/MRD logic works, so can't figure out the issue.
Can anyone out there tell me what the problem is with the logic above, or if they have come up with a neat solution to this annoying limitation. I know that many will say that I should modify the data model to use surrogate primary keys, but many of the uses for HTMLDB are new interfaces for old schemas, so a workaround that doesn't involve wholesale data model changes would be preferable.
Thanks in advance,
Mike Cretan

Hi, this is likely not the most elegant way...but perhaps the simplest -- and I didn't have much time to play.
I used Wizard to create two separate Master Detail forms, each with a separate detail table. Thus I ended up with four pages:
Page "A" - "Selector" page for Master (Report), with Edit link driving to Detail-1
Page "B" - Editable Master/Detail-1 page (HTML / Report)
Page "C" - "Selector" page for Master (Report), with Edit link driving to Detail-2
Page "D" - Editable Master/Detail-2 page (HTML / Report)
Then I selected the primary key column TWICE on the Report on Page A. Modified the second instance of this column to navigate to Page D (passing primary key) exactly the way the original instance of this column navigates to Page B. Then I deleted Page C.
Since you can have only one Tabular Entry form per page, this seemed the best way to drive two separate detail tables from a common interface.

CMP with Auto-increment Primary Key problem

I'm trying to set a column as IDENTITY in PointBase and have the app server utilize this in the CMP beans. I followed the instructions from the tutorial:
- In the deployment descriptor, the primary key class is defined as a java.lang.Object. The primary key field is not specified.
- In the home interface, the argument of the findByPrimaryKey method must be java.lang.Object.
- In the entity bean class, the return type of the ejbCreate method must be a java.lang.Object.
Below is (a fragment of) my deployment descriptor:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<display-name>CMPModule</display-name>
<enterprise-beans>
<entity>
<display-name>DocState</display-name>
<ejb-name>DocState</ejb-name>
<home>com.sun.itstar.j2ee.projectdocmgt.ejb.DocStateHome</home>
<remote>com.sun.itstar.j2ee.projectdocmgt.ejb.DocState</remote>
<local-home>com.sun.itstar.j2ee.projectdocmgt.ejb.LocalDocStateHome</local-home>
<local>com.sun.itstar.j2ee.projectdocmgt.ejb.LocalDocState</local>
<ejb-class>com.sun.itstar.j2ee.projectdocmgt.ejb.DocStateBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Object</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>DocState</abstract-schema-name>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>description</field-name>
</cmp-field>
<cmp-field>
<field-name>color</field-name>
</cmp-field>
</entity>
In the admin-serv/logs directory I get the follow message (bad place for the logs, took me a while to find where it was putting it!):
[24/Sep/2002:16:33:57] WARNING ( 4165): Validation error in bean DocumentType: Warning: All primary key columns in primary table DOCUMENT_TYPE of the bean corresponding to the generated class com.sun.itstar.j2ee.projectdocmgt.ejb.DocumentTypeBean_387898907_JDOState must be mapped to key fields.
Map the following primary key columns to key fields: DOCUMENT_TYPE.ID. If you already have fields mapped to these columns, verify that they are key fields.

Great! This worked. Here are some clear steps:
1. delete the field from the CMP
2. delete any business methods that you might have for the field
3. go to the properties of the bean, find the primary key property. Set the property to Unkown Primey Key Class (java.lang.Object)
Now there is a bigger problem. CMR fields. In ejbPostCreate() the bean gets its own pk and looks up other related beans. Now that I have removed the accessor to the pk field (and the pk field from the bean), how do I lookup the relationships?
I need some method that I can call from within ejbPostCreate() that will return the primary key...
I tried adding the field back in but not as the primary key. That generated an exception that said you cannot do that. If the field is the pk it must be marked as the pk.
Any ideas?

CMP with auto-increment primary key.Please help

Hi all,
I new with EJB technology so please bear with me.
Env: 2k Server, SQL 2k Server
Sun One(Forte EE) to develop and deploy CMP
I got the servlet to load the data from CMP's business mehods
is fine. Calling the findPrimaryKey is OK too. Even when I try to insert the row into DB is OK. At this time I make key PK is int AND NOT
AUTO INCREMENT everything is OK. In the ejbCreate method
I called setPK, setName ...It's fine.
The problem comes when I try to make the PK(still int) to be auto-increment field.In ejbCreate not call setPK because of in SunOne IDE, under the J2EE RI tab of EJB Module property, the Auto generate SQL I set to false so that I can
modify the SQL statement under SQL Deployment.createRow not taking the PK. I thought that will do it but it doesnot like it at all (I got Exception with transaction rollback)I just want to insert a single row with ID and name that's all.
Then I changed the SQL statment take PK and changed the Auto Generate SQL to True and in ejbCreate the PK as one of the args and called setPK this time with null object. It doesn't like neither.(Exception Cannot set the primary key with null. That is reasonable.)
I thought using EJB fast and clean technique would help developer to develop application with easiness.
So I realy stuck with this, I wonder ejb 2.0 support for auto increment at all because I would like to take advantage of the auto increment feature of the DB without writing the PrimaryKeySequence generator at all.
Am I missing something with this? May be just config thing to tell
that my PK is auto-increment field so that when the ejbCreate called it knows not taking the PK or even not asking to call setPK in ejbCreate.
Any help would appreciated.

Check out this thread, there's a bunch of good info:
http://www.theserverside.com/patterns/thread.jsp?thread_id=4976

Database Adapter Merge with char/varchar primary key

Hi guys,
It seems as though merge statements in BPEL database adapters do not work if the primary key of the table contains a char/varchar. This is in Jdeveloper 10.1.3.4.0
If I create the table below:
create table test_merge (
id        number primary key,
text      varchar2(255)
);Then the merge operation will update and insert as expected. However, if I create the same table but with id as a char/varchar, then the merge statement will never update.
It seems like it never finds a record with the same id (if it is a char/varchar), and always attempts to insert, which results in unique key constraint errors for the primary key column.
Has anyone else encountered this issue and found a way to get the merge statement to work correctly? I can obviously perform the select myself, and then conditionally update/insert, but I would prefer the merge to work as expected.
Thanks

After investigating further, it seems that even a database adapter select is not working correctly. Consider the following table:
create table test_merge (
id        varchar2(255) primary key,
text      varchar2(255)
);And I have inserted a record with id = "1" and text="abc"
If I create a BPEL process and add a database adapter (with only the select checkbox ticked) with the following SQL:
SELECT ID, TEXT FROM TEST_MERGE WHERE (ID = #id)If I invoke this adapter, passing in "1" as the id, then a record is returned, with the correct text (i.e. "abc") BUT the id returned is "-9900000000000000000000000000"
Can anyone explain why this is happening?

About sequences substituting primary key values

I've created trigger:
TRIGGER EMPLOYEES_TRG BEFORE INSERT ON EMPLOYESS
FOR EACH ROW
BEGIN
SELECT employees_seq.nextval
INTO :new.nr
FROM dual;
END;
following statement works just fine in SQL Worksheet:
insert into employees(Name, Surname) values ('M','C')
but when I try to make a swing client from application module using fields from entityView it seems that trigger doesn't fire as I commit. maybe the adequate statement
generated using ADF Business components doesn't generate "employees(Name, Surname)"?
The question is how to make my tables primary key get increased using trigger when I make a client form from two fields: Name, Surname and create and commit buttons.. ?

HI Mario,
your primary key in the entity object needs to be of DBSequence type.
It will show as a negative number in the form but when doing a commit the Trigger will catch it and change the value to sequence number.
Carl

BC4J Custom API: Batch Validation with Sequence-based primary key

Similar Messages

Maybe you are looking for