SIL_GLCOGSFact Failed with Unique Constraint

Hi,
A Task SIL_GLCOGSFact failed with ORA-00001: unique constraint (DW.W_GL_COGS_F_U1) violated
while insert into table W_GL_COGS_F.
There is not any record existing in the fact table. There is no way for such error. So weird.
Please help me out.
Roger
Error in Session log as following:
Database driver error...
Function Name : Execute
SQL Stmt : INSERT INTO W_GL_COGS_F(GL_ACCOUNT_WID,BUDGT_ORG_WID,CUSTOMER_WID,CUSTOMER_FIN_PROFL_WID,TERRITORY_WID,SALES_GROUP_ORG_WID,CUSTOMER_CONTACT_WID,CUSTOMER_SOLD_TO_LOC_WID,CUSTOMER_SHIP_TO_LOC_WID,CUSTOMER_BILL_TO_LOC_WID,CUSTOMER_PAYER_LOC_WID,SUPPLIER_WID,SUPPLIER_ACCOUNT_WID,SALES_REP_WID,SERVICE_REP_WID,ACCOUNT_REP_WID,PRODUCT_WID,SALES_PRODUCT_WID,INVENTORY_PRODUCT_WID,SUPPLIER_PRODUCT_WID,COMPANY_LOC_WID,PLANT_LOC_WID,SALES_OFC_LOC_WID,LEDGER_WID,COMPANY_ORG_WID,BUSN_AREA_ORG_WID,CTRL_AREA_ORG_WID,FIN_AREA_ORG_WID,SALES_ORG_WID,PURCH_ORG_WID,ISSUE_ORG_WID,DOC_TYPE_WID,CLRNG_DOC_TYPE_WID,POSTING_TYPE_WID,CLR_POST_TYPE_WID,COST_CENTER_WID,PROFIT_CENTER_WID,BANK_WID,PAY_TERMS_WID,TRANSACTION_DT_WID,TRANSACTION_TM_WID,CONVERSION_DT_WID,ORDERED_ON_DT_WID,INVOICED_ON_DT_WID,DELIVERED_ON_DT_WID,CUSTOMER_REQUEST_DT_WID,GOODS_ISSUE_DT_WID,STOCK_XFER_DT_WID,CLEARING_DOC_DT_WID,BASELINE_DT_WID,PLANNING_DT_WID,ACCOUNT_DOC_ID,COGS_DOC_AMT,COGS_LOC_AMT,XACT_QTY,UOM_CODE,DB_CR_IND,ACCT_DOC_NUM,ACCT_DOC_ITEM,ACCT_DOC_SUB_ITEM,CLEARING_DOC_NUM,CLEARING_DOC_ITEM,SALES_ORDER_NUM,SALES_ORDER_ITEM,SALES_SCH_LINE,INVOICE_NUM,INVOICE_ITEM,DELIVERY_DOC_NUM,DELIVERY_DOC_ITEM,GI_DOC_NUM,GI_DOC_ITEM,STO_DOC_NUM,STO_DOC_ITEM,DOC_HEADER_TEXT,LINE_ITEM_TEXT,ALLOCATION_NUM,FED_BALANCE_ID,BALANCE_ID,DOC_STATUS_WID,POSTED_ON_DT_WID,POSTED_ON_TM_WID,CLEARED_ON_DT_WID,GL_RECONCILED_ON_DT,DOC_CURR_CODE,LOC_CURR_CODE,LOC_EXCHANGE_RATE,GLOBAL1_EXCHANGE_RATE,GLOBAL2_EXCHANGE_RATE,GLOBAL3_EXCHANGE_RATE,CREATED_BY_WID,CHANGED_BY_WID,CREATED_ON_DT,CHANGED_ON_DT,AUX1_CHANGED_ON_DT,AUX2_CHANGED_ON_DT,AUX3_CHANGED_ON_DT,AUX4_CHANGED_ON_DT,DELETE_FLG,W_INSERT_DT,W_UPDATE_DT,DATASOURCE_NUM_ID,ETL_PROC_WID,INTEGRATION_ID,TENANT_ID,X_CUSTOM,GL_RECONCILED_ON_PROC_WID) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
Database driver error...
Function Name : Execute Multiple
SQL Stmt : INSERT INTO W_GL_COGS_F(GL_ACCOUNT_WID,BUDGT_ORG_WID,CUSTOMER_WID,CUSTOMER_FIN_PROFL_WID,TERRITORY_WID,SALES_GROUP_ORG_WID,CUSTOMER_CONTACT_WID,CUSTOMER_SOLD_TO_LOC_WID,CUSTOMER_SHIP_TO_LOC_WID,CUSTOMER_BILL_TO_LOC_WID,CUSTOMER_PAYER_LOC_WID,SUPPLIER_WID,SUPPLIER_ACCOUNT_WID,SALES_REP_WID,SERVICE_REP_WID,ACCOUNT_REP_WID,PRODUCT_WID,SALES_PRODUCT_WID,INVENTORY_PRODUCT_WID,SUPPLIER_PRODUCT_WID,COMPANY_LOC_WID,PLANT_LOC_WID,SALES_OFC_LOC_WID,LEDGER_WID,COMPANY_ORG_WID,BUSN_AREA_ORG_WID,CTRL_AREA_ORG_WID,FIN_AREA_ORG_WID,SALES_ORG_WID,PURCH_ORG_WID,ISSUE_ORG_WID,DOC_TYPE_WID,CLRNG_DOC_TYPE_WID,POSTING_TYPE_WID,CLR_POST_TYPE_WID,COST_CENTER_WID,PROFIT_CENTER_WID,BANK_WID,PAY_TERMS_WID,TRANSACTION_DT_WID,TRANSACTION_TM_WID,CONVERSION_DT_WID,ORDERED_ON_DT_WID,INVOICED_ON_DT_WID,DELIVERED_ON_DT_WID,CUSTOMER_REQUEST_DT_WID,GOODS_ISSUE_DT_WID,STOCK_XFER_DT_WID,CLEARING_DOC_DT_WID,BASELINE_DT_WID,PLANNING_DT_WID,ACCOUNT_DOC_ID,COGS_DOC_AMT,COGS_LOC_AMT,XACT_QTY,UOM_CODE,DB_CR_IND,ACCT_DOC_NUM,ACCT_DOC_ITEM,ACCT_DOC_SUB_ITEM,CLEARING_DOC_NUM,CLEARING_DOC_ITEM,SALES_ORDER_NUM,SALES_ORDER_ITEM,SALES_SCH_LINE,INVOICE_NUM,INVOICE_ITEM,DELIVERY_DOC_NUM,DELIVERY_DOC_ITEM,GI_DOC_NUM,GI_DOC_ITEM,STO_DOC_NUM,STO_DOC_ITEM,DOC_HEADER_TEXT,LINE_ITEM_TEXT,ALLOCATION_NUM,FED_BALANCE_ID,BALANCE_ID,DOC_STATUS_WID,POSTED_ON_DT_WID,POSTED_ON_TM_WID,CLEARED_ON_DT_WID,GL_RECONCILED_ON_DT,DOC_CURR_CODE,LOC_CURR_CODE,LOC_EXCHANGE_RATE,GLOBAL1_EXCHANGE_RATE,GLOBAL2_EXCHANGE_RATE,GLOBAL3_EXCHANGE_RATE,CREATED_BY_WID,CHANGED_BY_WID,CREATED_ON_DT,CHANGED_ON_DT,AUX1_CHANGED_ON_DT,AUX2_CHANGED_ON_DT,AUX3_CHANGED_ON_DT,AUX4_CHANGED_ON_DT,DELETE_FLG,W_INSERT_DT,W_UPDATE_DT,DATASOURCE_NUM_ID,ETL_PROC_WID,INTEGRATION_ID,TENANT_ID,X_CUSTOM,GL_RECONCILED_ON_PROC_WID) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
WRITER_1_*_1> CMN_1761 Timestamp Event: [Tue Nov 17 18:50:31 2009]
WRITER_1_*_1> WRT_8425 ERROR: Writer execution failed.
WRITER_1_*_1> CMN_1761 Timestamp Event: [Tue Nov 17 18:50:31 2009]
WRITER_1_*_1> WRT_8114
Row # [1] in bad file
WRITER_1_*_1> CMN_1053 : Rowdata: ( RowType=0(insert) Src Rowid=42 Targ Rowid=42
GL_ACCOUNT_WID (GL_ACCOUNT_WID:Double:): "271134.0000000000"
BUDGT_ORG_WID (BUDGT_ORG_WID:Double:): "0.00000000000000"
CUSTOMER_WID (CUSTOMER_WID:Double:): "0.00000000000000"
CUSTOMER_FIN_PROFL_WID (CUSTOMER_FIN_PROFL_WID:Double:): "0.00000000000000"
TERRITORY_WID (TERRITORY_WID:Double:): "0.00000000000000"
SALES_GROUP_ORG_WID (SALES_GROUP_ORG_WID:Double:): "0.00000000000000"
CUSTOMER_CONTACT_WID (CUSTOMER_CONTACT_WID:Double:): "0.00000000000000"
CUSTOMER_SOLD_TO_LOC_WID (CUSTOMER_SOLD_TO_LOC_WID:Double:): "0.00000000000000"
CUSTOMER_SHIP_TO_LOC_WID (CUSTOMER_SHIP_TO_LOC_WID:Double:): "0.00000000000000"
CUSTOMER_BILL_TO_LOC_WID (CUSTOMER_BILL_TO_LOC_WID:Double:): "0.00000000000000"
CUSTOMER_PAYER_LOC_WID (CUSTOMER_PAYER_LOC_WID:Double:): "0.00000000000000"
SUPPLIER_WID (SUPPLIER_WID:Double:): "0.00000000000000"
SUPPLIER_ACCOUNT_WID (SUPPLIER_ACCOUNT_WID:Double:): "0.00000000000000"
SALES_REP_WID (SALES_REP_WID:Double:): "0.00000000000000"
SERVICE_REP_WID (SERVICE_REP_WID:Double:): "0.00000000000000"
ACCOUNT_REP_WID (ACCOUNT_REP_WID:Double:): "0.00000000000000"
PRODUCT_WID (PRODUCT_WID:Double:): "107667.0000000000"
SALES_PRODUCT_WID (SALES_PRODUCT_WID:Double:): "5093039.000000000"
INVENTORY_PRODUCT_WID (INVENTORY_PRODUCT_WID:Double:): "4376743.000000000"
SUPPLIER_PRODUCT_WID (SUPPLIER_PRODUCT_WID:Double:): "0.00000000000000"
COMPANY_LOC_WID (COMPANY_LOC_WID:Double:): "0.00000000000000"
PLANT_LOC_WID (PLANT_LOC_WID:Double:): "2147.000000000000"
SALES_OFC_LOC_WID (SALES_OFC_LOC_WID:Double:): "0.00000000000000"
LEDGER_WID (LEDGER_WID:Double:): "2030.000000000000"
COMPANY_ORG_WID (COMPANY_ORG_WID:Double:): "0.00000000000000"
BUSN_AREA_ORG_WID (BUSN_AREA_ORG_WID:Double:): "0.00000000000000"
CTRL_AREA_ORG_WID (CTRL_AREA_ORG_WID:Double:): "0.00000000000000"
FIN_AREA_ORG_WID (FIN_AREA_ORG_WID:Double:): "0.00000000000000"
SALES_ORG_WID (SALES_ORG_WID:Double:): "0.00000000000000"
PURCH_ORG_WID (PURCH_ORG_WID:Double:): "0.00000000000000"
ISSUE_ORG_WID (ISSUE_ORG_WID:Double:): "0.00000000000000"
DOC_TYPE_WID (DOC_TYPE_WID:Double:): "6111.000000000000"
CLRNG_DOC_TYPE_WID (CLRNG_DOC_TYPE_WID:Double:): "0.00000000000000"
POSTING_TYPE_WID (POSTING_TYPE_WID:Double:): "0.00000000000000"
CLR_POST_TYPE_WID (CLR_POST_TYPE_WID:Double:): "0.00000000000000"
COST_CENTER_WID (COST_CENTER_WID:Double:): "3317.000000000000"
PROFIT_CENTER_WID (PROFIT_CENTER_WID:Double:): "2025.000000000000"
BANK_WID (BANK_WID:Double:): "0.00000000000000"
PAY_TERMS_WID (PAY_TERMS_WID:Double:): "0.00000000000000"
TRANSACTION_DT_WID (TRANSACTION_DT_WID:Double:): "20090211.00000000"
TRANSACTION_TM_WID (TRANSACTION_TM_WID:Double:): "0.00000000000000"
CONVERSION_DT_WID (CONVERSION_DT_WID:Double:): "0.00000000000000"
ORDERED_ON_DT_WID (ORDERED_ON_DT_WID:Double:): "0.00000000000000"
INVOICED_ON_DT_WID (INVOICED_ON_DT_WID:Double:): "0.00000000000000"
DELIVERED_ON_DT_WID (DELIVERED_ON_DT_WID:Double:): "0.00000000000000"
CUSTOMER_REQUEST_DT_WID (CUSTOMER_REQUEST_DT_WID:Double:): "0.00000000000000"
GOODS_ISSUE_DT_WID (GOODS_ISSUE_DT_WID:Double:): "0.00000000000000"
STOCK_XFER_DT_WID (STOCK_XFER_DT_WID:Double:): "0.00000000000000"
CLEARING_DOC_DT_WID (CLEARING_DOC_DT_WID:Double:): "0.00000000000000"
BASELINE_DT_WID (BASELINE_DT_WID:Double:): "0.00000000000000"
PLANNING_DT_WID (PLANNING_DT_WID:Double:): "0.00000000000000"
ACCOUNT_DOC_ID (ACCOUNT_DOC_ID:UniChar.80:): "2899322~12389~Feb-09~230"
COGS_DOC_AMT (COGS_DOC_AMT:Double:): "30.00000000000000"
COGS_LOC_AMT (COGS_LOC_AMT:Double:): "30.00000000000000"
XACT_QTY (XACT_QTY:Double:): "1.000000000000000"
UOM_CODE (UOM_CODE:UniChar.50:): ""
DB_CR_IND (DB_CR_IND:UniChar.30:): "DEBIT"
ACCT_DOC_NUM (ACCT_DOC_NUM:UniChar.30:): "(NULL)"
ACCT_DOC_ITEM (ACCT_DOC_ITEM:Double:): "(NULL)"
ACCT_DOC_SUB_ITEM (ACCT_DOC_SUB_ITEM:Double:): "(NULL)"
CLEARING_DOC_NUM (CLEARING_DOC_NUM:UniChar.30:): "(NULL)"
CLEARING_DOC_ITEM (CLEARING_DOC_ITEM:Double:): "(NULL)"
SALES_ORDER_NUM (SALES_ORDER_NUM:UniChar.30:): "(NULL)"
SALES_ORDER_ITEM (SALES_ORDER_ITEM:Double:): "(NULL)"
SALES_SCH_LINE (SALES_SCH_LINE:Double:): "(NULL)"
INVOICE_NUM (INVOICE_NUM:UniChar.30:): "(NULL)"
INVOICE_ITEM (INVOICE_ITEM:Double:): "(NULL)"
DELIVERY_DOC_NUM (DELIVERY_DOC_NUM:UniChar.30:): "(NULL)"
DELIVERY_DOC_ITEM (DELIVERY_DOC_ITEM:Double:): "(NULL)"
GI_DOC_NUM (GI_DOC_NUM:UniChar.30:): "(NULL)"
GI_DOC_ITEM (GI_DOC_ITEM:Double:): "(NULL)"
STO_DOC_NUM (STO_DOC_NUM:UniChar.30:): "(NULL)"
STO_DOC_ITEM (STO_DOC_ITEM:Double:): "(NULL)"
DOC_HEADER_TEXT (DOC_HEADER_TEXT:UniChar.255:): "(NULL)"
LINE_ITEM_TEXT (LINE_ITEM_TEXT:UniChar.255:): "(NULL)"
ALLOCATION_NUM (ALLOCATION_NUM:UniChar.30:): "(NULL)"
FED_BALANCE_ID (FED_BALANCE_ID:UniChar.320:): "12389~10004~BUDGET~~10004~~"
BALANCE_ID (BALANCE_ID:UniChar.320:): "10004~12389~"
DOC_STATUS_WID (DOC_STATUS_WID:Double:): "102006.0000000000"
POSTED_ON_DT_WID (POSTED_ON_DT_WID:Double:): "20090211.00000000"
POSTED_ON_TM_WID (POSTED_ON_TM_WID:Double:): "20090211.00000000"
CLEARED_ON_DT_WID (CLEARED_ON_DT_WID:Double:): "0.00000000000000"
GL_RECONCILED_ON_DT (GL_RECONCILED_ON_DT:Date:): "(NULL)"
DOC_CURR_CODE (DOC_CURR_CODE:UniChar.30:): "USD"
LOC_CURR_CODE (LOC_CURR_CODE:UniChar.30:): "USD"
LOC_EXCHANGE_RATE (LOC_EXCHANGE_RATE:Double:): "1.000000000000000"
GLOBAL1_EXCHANGE_RATE (GLOBAL1_EXCHANGE_RATE:Double:): "1.000000000000000"
GLOBAL2_EXCHANGE_RATE (GLOBAL2_EXCHANGE_RATE:Double:): "33.96700000000000"
GLOBAL3_EXCHANGE_RATE (GLOBAL3_EXCHANGE_RATE:Double:): "1.000000000000000"
CREATED_BY_WID (CREATED_BY_WID:Double:): "11254.00000000000"
CHANGED_BY_WID (CHANGED_BY_WID:Double:): "11254.00000000000"
CREATED_ON_DT (CREATED_ON_DT:Date:): "02/11/2009 14:56:23"
CHANGED_ON_DT (CHANGED_ON_DT:Date:): "(NULL)"
AUX1_CHANGED_ON_DT (AUX1_CHANGED_ON_DT:Date:): "02/11/2009 14:56:23"
AUX2_CHANGED_ON_DT (AUX2_CHANGED_ON_DT:Date:): "(NULL)"
AUX3_CHANGED_ON_DT (AUX3_CHANGED_ON_DT:Date:): "(NULL)"
AUX4_CHANGED_ON_DT (AUX4_CHANGED_ON_DT:Date:): "(NULL)"
DELETE_FLG (DELETE_FLG:UniChar.1:): "N"
W_INSERT_DT (W_INSERT_DT:Date:): "11/17/2009 18:39:40"
W_UPDATE_DT (W_UPDATE_DT:Date:): "11/17/2009 18:39:40"
DATASOURCE_NUM_ID (DATASOURCE_NUM_ID:Double:): "41.00000000000000"
ETL_PROC_WID (ETL_PROC_WID:Double:): "16.00000000000000"
INTEGRATION_ID (INTEGRATION_ID:UniChar.80:): "46214900~12389~2899322~Feb-09~230"
TENANT_ID (TENANT_ID:UniChar.80:): "DEFAULT"
X_CUSTOM (X_CUSTOM:UniChar.10:): "(NULL)"
GL_RECONCILED_ON_PROC_WID (GL_RECONCILED_ON_PROC_WID:Double:): "(NULL)"
)

ETL will do a commit for every 10k records i believe. Might be when it is trying to insert the first 10k records it is having the duplicates. So check in the staging table whether that unique column combination is having any duplicates.

Similar Messages

Insert called before delete in a collection with unique constraint

Hi all,
I have a simple @OneToMany private mapping:
private Collection<Item> items;
@OneToMany(mappedBy = "parent", cascade = CascadeType.ALL)
public Collection<Item> getItems() {
return items;
public void setItems(Collection<Item> items) {
this.items = items;
public void customize(ClassDescriptor classDescriptor) throws Exception {
OneToManyMapping mapping = (OneToManyMapping)
classDescriptor.getMappingForAttributeName("items");
mapping.privateOwnedRelationship();
I have a unique constraint on my Items table that a certain value cannot be duplicated.
My problem appears when I remove a previously saved item from the collection and add a new item containing the same data, at the same time.
After I save the parent and do a flush, I receive SQLIntegrityConstraintViolationException because TopLink performs first an insert query instead of deleting the existing item.
I tested the application and everything went fine with: remove item / save parent / insert item / save parent
I checked on the Internet and the documentation but didn't find anything similar to my problem. I tried debugging TopLink's internal calls but I'm missing some general ideas about all the inner workings and don't know what to look for. I use TopLink version: Oracle TopLink Essentials - 2.1 (Build b60e-fcs (12/23/2008))
Does anyone have a hint of what to look for?
Edited by: wise_guybg on Sep 25, 2009 4:01 PM
Edited by: wise_guybg on Oct 5, 2009 11:22 AM

Thank you for the suggestions James
As I mentioned briefly I have done some debugging but couldn't understand how collections are updated. What I did find out is that setShouldPerformDeletesFirst() doesn't come into play in this case because this is not a consecutive change on entities.
What I have in my case is a collection inside an entity that the user has tampered with and now TopLink has to do a merge. I cannot call flush() in the middle since the user has not approved that the changes made to the entity should be saved.
I see that for TopLink it's not easy to figure out the order in which changes were made to a collection. Here is pseudo-code of when the constraint is touched:
entity.items.remove(a)
entity.items.add(b)
merge(entity)
And here is code that executes without a problem:
entity.items.remove(a)
merge(entity)
entity.items.add(b)
merge(entity)
So once again, I think that collection changes are managed differently but I don't find a way to tell TopLink how to handle them. Any ideas?

Insert result of query into a table with unique constraint

Hi,
I have a query result that I would like to store in a table. The target table has a unique constraint. In MySQL you can do
insert IGNORE into myResultTable <...select statement...>
The IGNORE clause means if inserting a row would violate a unique or primary key constraint, do not insert the row, but continue inserting the rest of the query. Leaving the IGNORE clause out would cause the insert to fail and an error to return.
I would like to do this in oracle... that is insert the results of a query that are not already in the target table. What is the best way to do this? One way is use a procedural language and loop through the first query, checking to see if each row is a duplicate before inserting it. I would think this would be slow if there are lots of records. Other options...
insert into myTargetTable
select value from mySourceTable where ... and not exists (select 'x' from myTargetTable where value = mySourceTable.value)
insert into myTargetTable
select mySourceTable.value
from myTargetTable RIGHT JOIN mySourceTable
ON myTargetTable.value = mySourceTable.value
where ...
and myTargetTable.value IS NULL
any other suggestions?
Thanks,
Simon

Try doing a MINUS instead of not exists., ie Source MINUS Target.
Disabling the constraint will not help you since this will allow the duplicate rows to be inserted into the table. I don't think you want this.
--kalpana

Table with unique Constraint

Dear All
i have a a project ADF-BC / JSF - JDeveloper 11.1.2.3.0 latest, and i have EO contains PK constrain in db in 2 fields (userid & Roleid) and i implemented bundle to handle error message with jbo error code and it works fine in AM test
and i have VO contains LOV in one attribute of this unique constrain columns (Roleid), now i dropped VO in jsf page as a af:table as below with input text with list of values for roleid and auto submit = true , and i face unexpected behavior from lov attribute in case of entering repeated value ..
when i enter another repeated value , it give me error message i created in the bundle and everything ok until now
but when i tab out of input text with list of values , it go back to old value as may be validation fired in back ground , it is not a problem until now
when i try to make anything else, he still gives me error message of duplicated key
i change the value again to correct value to avoid duplication error message , i am surprised , still i get the error message and shows me the repeated value again !!
simply it still save the old repeated value however i corrected , please any one help me to know what is happening and how to solve ?
Attribute in EO :
<Attribute
Name="RoleId"
Precision="10"
ColumnName="ROLE_ID"
SQLType="VARCHAR"
Type="java.lang.String"
ColumnType="VARCHAR2"
TableName="USER_ROLES"
PrimaryKey="true">
<DesignTime>
<Attr Name="_DisplaySize" Value="10"/>
</DesignTime>
<validation:ExistsValidationBean
Name="RoleId_Rule_1"
ResId="CS.model.BC.EO.UserRolesEO.RoleId_Rule_1"
OperandType="EO"
AssocName="CS.model.BC.ASS.UsersRolesFk2ASS"/>
</Attribute>
Interface af : table
<af:table value="#{bindings.UserRoles2.collectionModel}" var="row"
rows="#{bindings.UserRoles2.rangeSize}"
emptyText="#{bindings.UserRoles2.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.UserRoles2.rangeSize}"
rowBandingInterval="0"
filterModel="#{bindings.UserRoles2Query.queryDescriptor}"
queryListener="#{bindings.UserRoles2Query.processQuery}"
filterVisible="true" varStatus="vs"
selectedRowKeys="#{bindings.UserRoles2.collectionModel.selectedRow}"
selectionListener="#{bindings.UserRoles2.collectionModel.makeCurrent}"
rowSelection="single" id="t1" columnSelection="none"
columnStretching="column:c3">
<af:column sortProperty="#{bindings.UserRoles2.hints.RoleId.name}"
filterable="true" sortable="true"
headerText="#{bindings.UserRoles2.hints.RoleId.label}"
id="c2">
<af:inputListOfValues id="roleIdId"
popupTitle="Search and Select: #{bindings.UserRoles2.hints.RoleId.label}"
value="#{row.bindings.RoleId.inputValue}"
model="#{row.bindings.RoleId.listOfValuesModel}"
required="#{bindings.UserRoles2.hints.RoleId.mandatory}"
columns="#{bindings.UserRoles2.hints.RoleId.displayWidth}"
shortDesc="#{bindings.UserRoles2.hints.RoleId.tooltip}"
autoSubmit="true" editMode="select">
<f:validator binding="#{row.bindings.RoleId.validator}"/>
</af:inputListOfValues>
</af:column>
<af:column sortProperty="#{bindings.UserRoles2.hints.RoleName.name}"
sortable="true"
headerText="#{bindings.UserRoles2.hints.RoleName.label}"
id="c3">
<af:outputFormatted value="#{row.bindings.RoleName.inputValue}"
id="of7" partialTriggers="roleIdId"/>
</af:column>
<af:column sortProperty="#{bindings.UserRoles2.hints.Active.name}"
filterable="true" sortable="true"
headerText="#{bindings.UserRoles2.hints.Active.label}"
id="c4">
<af:outputFormatted value="#{row.bindings.Active.inputValue}"
id="of8" partialTriggers="roleIdId"/>
</af:column>
</af:table>
Edited by: user8854969 on Oct 7, 2012 1:34 PM
Edited by: user8854969 on Oct 7, 2012 2:16 PM

I believe there is a little confusion here. The error I am encountering has to do with a unique constraint violation and not a foreign key constraint. If I have the data:
PK FK sequence
1 5 1
2 5 2
3 5 3
with a unique constraint on (FK, sequence) and want to change it to:
PK FK sequence
1 5 1
4 5 2 --insert
2 5 3 --update on sequence
3 5 4 --update on sequence
I am currently getting a unique constraint violation because the insert is issued before the updates, and the updates alone cause problems because they are issued out of order (i.e. if I do the shifting operation without the insertion of a new record).

Insert / delete fails on unique constraint (order problem)

Hi dear Kodo team,
within a transaction, we are deleting a certain jdo object. The deletion is
undone later (within the same tx), resulting in creating a new object with
the same contents as the deleted one (gets another oid, of course). In our
database, there is a unique constraint on two mapped fields of this object.
Unfortunately, kodo issues the INSERT statement before the DELETE
statement, thus producing a unique constraint violation.
Is there a way to influence the statement order? Is there any solution other
than disabling / deferring this constraint?
Thanks in advance,
Contus

Beside Oracle, we are using our db schema on db platforms that do not
support deferred constraints. That's why we would like to know if there is
a way to influence statement order without removing those constraints.
Thanks,
Contus
Alex Roytman wrote:
In general the best option is to use deferred constraints on all your FK
and unique constraints. You still get complete referential integrity but
do not need Kodo to order your statements for you. If you are already
doing it but still get this error message and you are using Oracle 9.2 it
seems to be a bug in oracle JDBC. I submitted it to oracle - they accepted
it and supposedly working on resolution
"contus" <[email protected]> wrote in message
news:bulku6$qad$[email protected]..
Hi dear Kodo team,
within a transaction, we are deleting a certain jdo object. The deletionis
undone later (within the same tx), resulting in creating a new object
with the same contents as the deleted one (gets another oid, of course).
In our database, there is a unique constraint on two mapped fields of
thisobject.
Unfortunately, kodo issues the INSERT statement before the DELETE
statement, thus producing a unique constraint violation.
Is there a way to influence the statement order? Is there any solutionother
than disabling / deferring this constraint?
Thanks in advance,
Contus

Help with unique constraint ERROR!!!

This error occurs after invoking a Stored Procedure program. When it tries to insert, the PK table goes beserk:
ORA-00001: unique constraint (HASUNI.THA_OTHER_ACTIVITY_PK) violated
ORA-06512: at "HASUNI.POPULATE_GDW_ACTIVITY", line 203
ORA-06512: at "HASUNI.GDW_MASTER", line 21
ORA-06512: at line 9
I tried to clear the PK table to get past the unique constraint error, but I can't seem to delete contents.
PLEASE HELP!!!!

The other queries are erroring out. It doesn't like the HASUNI.THA_OTHER_ACTIVITY_PK. It says this is an undefined table.
Insert Statement:
INSERT INTO HASUNI.THA_OTHER_ACTIVITY <-- line 203
SELECT
viewActivity.GROUPID,
SUBSTR(viewActivity.MEMBERID,11,9)||SUBSTR(viewActivity.MEMBERID,21,9),
viewActivity.ACTIVITYSEQUENCE,
val_first_day,
TO_DATE('31DEC9999'),
viewActivity.PRODUCTID,
viewActivity.PRODPLANTYPE,
SUBSTR(viewActivity.MEMBERID,11,9),
SUBSTR(viewActivity.MEMBERID,21,9),
viewActivity.CLASSVAL,
viewActivity.PCC,
viewActivity.BRANCH,
viewActivity.ARC,
viewActivity.LOCATION,
viewActivity.MEMBERID,
viewActivity.DOB,
viewActivity.GENDER,
viewActivity.MEMBERSTATUS,
viewActivity.CHPNID,
viewActivity.SSN,
NULL,
NULL,
SUBSTR(viewActivity.ZIPCODE,1,5),
SUBSTR(viewActivity.ZIPCODE,7,4),
viewActivity.ST,
viewActivity.SOURCESYSTEMID,
viewActivity.SOURCE,
viewActivity.INITIATEDBY,
viewActivity.OUTCOMES,
viewActivity.OUTCOMESDATE,
viewActivity.INITACTDATE,
viewActivity.INITACTTAKEN,
viewActivity.INITACTTAKENDATE,
viewActivity.INITUSERID,
viewActivity.LASTMODUSRID,
viewActivity.LASTMODDATE,
'HAS',
val_last_day,
NULL
FROM
HASUNI.VW_GDW_ACTIVITY viewActivity,
HASUNI.HA_OUTREACH outreach
WHERE
viewActivity.MEMBERID IN (SELECT viewActivity.MEMBERID FROM HASUNI.VW_GDW_ACTIVITY viewActivity)
AND outreach.MMBR_ID = viewActivity.MEMBERID
AND viewActivity.INITACTTAKEN = 'OTHER'
AND (TRUNC(viewActivity.INITACTDATE) BETWEEN val_first_day AND val_last_day
OR (TRUNC(viewActivity.INITACTDATE) < val_first_day
AND TRUNC(viewActivity.LASTMODDATE) BETWEEN val_first_day AND val_last_day));

EjbRemove fails with deferred constraints in 8.1.6

I get a constraint violation under certain conditions from Oracle.
IBM ejb container hides the exception, and raises a CSI_ROLLBACK exception. The only workaround I can think of, is disabling all constraints in Oracle, and trusting IBMs Application server to guarantee the
referential integrity of the database.
Does anyone else notice these problems and found a resolution?
Oracle introduced deferred constraints to allow the constraint violation checking at the end of an transaction.
For the IBM implementation of entity EJBs this is essential,
because any the "DELETE FROM WHERE id=" which result from an ejbRemove() happens >>>before<<< an ejbStore() which results in "UPDATE SET foreignkey = NULL ".
I am using the jdbc driver from classes12.zip, and noticed that
you get an constraint violation on a commit, when the record has been created in a transaction, is updated in a transaction, and then is deleted in a transaction. The transactions are isolated.
A rollback, and deleting again resolves the problem.
But the problem is that an Websphere Application server is in between the
delete from a user, and the jdbc driver accessed through a datasource.
null

Does anyone know where to configure and find required settings (e.g. the number of open_cursors) for Oracle 8.1.6 server when using the jdbc thin driver ?
null

Unique constraint violation on version enabled table

hi!
we're facing a strange problem with a version enabled table that has an unique constraint on one column. if we rename an object stored in the table (the name-attribute of the object is the one that has a unique constraint on the respective column) and rename it back to the old name again, we get an ORA-00001 unique constraint violation on the execution of an update trigger.
if the constraint is simply applied as before to the now version enabled table, I understand that this happens, but shouldn't workspace manager take care of something like that when a table with unique constraints is version enabled? (the documentation also says that) because taking versioning into account it's not that we try to insert another object with the same name, it's the same object at another point in time now getting back it's old name.
we somewhat assume that to be a pretty standard scenario when using versioned data.
is this some kind of bug or do we just miss something important here?
more information:
- versioning is enabled on all tables with VIEW_WO_OVERWRITE and no valid time support
- database version is 10.2.0.1.0
- wm installation output:
ALLOW_CAPTURE_EVENTS OFF
ALLOW_MULTI_PARENT_WORKSPACES OFF
ALLOW_NESTED_TABLE_COLUMNS OFF
CR_WORKSPACE_MODE OPTIMISTIC_LOCKING
FIRE_TRIGGERS_FOR_NONDML_EVENTS ON
NONCR_WORKSPACE_MODE OPTIMISTIC_LOCKING
NUMBER_OF_COMPRESS_BATCHES 50
OWM_VERSION 10.2.0.1.0
UNDO_SPACE UNLIMITED
USE_TIMESTAMP_TYPE_FOR_HISTORY ON
- all operations are done on LIVE workspace
any help is appreciated.
EDIT: we found out the following: the table we are talking about is the only table where the unique constraint is left. so there must have been a problem during version enabling. on another oracle installation we did everything the same way and the unique constraint wasn't left there, so everything works fine.
regards,
Andreas Schilling
Message was edited by:
aschilling

hi!
we're facing a strange problem with a version enabled table that has an unique constraint on one column. if we rename an object stored in the table (the name-attribute of the object is the one that has a unique constraint on the respective column) and rename it back to the old name again, we get an ORA-00001 unique constraint violation on the execution of an update trigger.
if the constraint is simply applied as before to the now version enabled table, I understand that this happens, but shouldn't workspace manager take care of something like that when a table with unique constraints is version enabled? (the documentation also says that) because taking versioning into account it's not that we try to insert another object with the same name, it's the same object at another point in time now getting back it's old name.
we somewhat assume that to be a pretty standard scenario when using versioned data.
is this some kind of bug or do we just miss something important here?
more information:
- versioning is enabled on all tables with VIEW_WO_OVERWRITE and no valid time support
- database version is 10.2.0.1.0
- wm installation output:
ALLOW_CAPTURE_EVENTS OFF
ALLOW_MULTI_PARENT_WORKSPACES OFF
ALLOW_NESTED_TABLE_COLUMNS OFF
CR_WORKSPACE_MODE OPTIMISTIC_LOCKING
FIRE_TRIGGERS_FOR_NONDML_EVENTS ON
NONCR_WORKSPACE_MODE OPTIMISTIC_LOCKING
NUMBER_OF_COMPRESS_BATCHES 50
OWM_VERSION 10.2.0.1.0
UNDO_SPACE UNLIMITED
USE_TIMESTAMP_TYPE_FOR_HISTORY ON
- all operations are done on LIVE workspace
any help is appreciated.
EDIT: we found out the following: the table we are talking about is the only table where the unique constraint is left. so there must have been a problem during version enabling. on another oracle installation we did everything the same way and the unique constraint wasn't left there, so everything works fine.
regards,
Andreas Schilling
Message was edited by:
aschilling

Unique Constraint on a Table

I want to have a unique constraint on deptno and emp_name in emp table.
What I want is:
Any Dept can have 100 Steves OR 100 Johns but only 1 Robert
Dept No               Emp Name
10               Steve
10               Steve
10               Robert
20               Steve
20               Robert
20                John
20               John
How can we achieve this with unique constraint??
Cheers
Prasad.

You are talking about unique constraint and you want to have duplicate records in a column with unique constraint. No, what you want is not possible with unique constraint. When you have a unique constraint on emp_name, how can you have 100 johns or 100 steves. Forget about 100, you can't have the second john/steve.

Import fails with error unique constraint

Hello,
I try to import an APEX Application from Version 2.2 to APEX Version 2.0.
I get the following error message:
ORA-20001: GET_BLOCK-Fehler. ORA-20001: GET_STMT-Fehler. ORA-20001: Die Ausführung der Anweisung war nicht erfolgreich. ORA-00001: unique constraint (FLOWS_020000.WWV_FLOW_REGION_UPD_RPT_CI1) violated<pre>
 begin --------------------------------------- -- ...updatable report columns for page 60 -- begin<b
For the Import I chose the option "Auto Assign New Application ID".
Has anyone an Idea, why the import fails?
(Export from Version 2.2 and Import to a different Workspace in Version 2.2 is successful)
Thank you for your responses,
Carola

Carola,
I have no idea why this is happening. You may send the application export file (or the export file for page 60 only) to [email protected] and I will check it.
Scott

ORA-00001: unique constraint @ impdp with table_exists_action=truncate

Hi everybody
I can't understand why my data pump import execution with parameter TABLE_EXISTS_ACTION=TRUNCATE returned ORA-00001 (unique constraint violation), while importing schema tables from a remote database where the source tables have the same unique constraints as the corresponding ones on the target database.
Now my question is "If the table would be truncated, why I get unique constraint violation when inserting records from a table where the same unique constraint is validated?
Here are the used parameter file content and the impdp logfile.
parfile
{code}
DIRECTORY=IMPEXP_LOG_COLL2
CONTENT=DATA_ONLY
NETWORK_LINK=PRODUCTION
PARALLEL=1
TABLE_EXISTS_ACTION=TRUNCATE
EXCLUDE=STATISTICS
{code}
logfile
{code}
Import: Release 10.2.0.1.0 - Production on Gioved� 22 Ottobre, 2009 15:33:44
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connesso a: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
FLASHBACK automatically enabled to preserve database integrity.
Starting "IMPEXP"."PROVA_REFRESH_DBCOLL": impexp/********@dbcoll SCHEMAS=test_pump LOGFILE=test_pump.log parfile=refresh_dbcoll.par JOB_NAME=prova_refresh_dbcoll
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 523 MB
ORA-31693: Table data object "TEST_PUMP"."X10000000_TRIGGER" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (TEST_PUMP.SYS_C00726627) violated
ORA-31693: Table data object "TEST_PUMP"."X10000000_BASIC" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (TEST_PUMP.SYS_C00726625) violated
Job "IMPEXP"."PROVA_REFRESH_DBCOLL" completed with 2 error(s) at 15:34:04
{code}
Thank you
Bye Alessandro

I forgot to read the last two lines of the documentation about TABLE_EXISTS_ACTION where it says:
"TRUNCATE cannot be used on clustered tables or over network links."
So it seems that it ignored the clause for the use of NETWORK_LINK and unreasonably opted for an APPEND action instead of throwing an error to highlight the conflicting parameters in the used configuration.
Bye Alessandro

UNIQUE constraint but with a condition?

Hi!
Is it possible to define a unique constraint in a table which would apply only under a condition (depending on row content only) ?
For example:
CREATE TABLE example
pk number,
a number,
b number,
c VARCHAR2(10),
x number
The constraint would be UNIQUIE (a,b), but only when x is > 10.
So if x is not above 10, then same values for a nd b should be allowed.
Maybe with a view ?
Like this?
create view example_view ( unique (a,b)) AS
select a,b from example where x > 10
with read only; -- ??? needed? Regards,
David

Hello David,
not on the table directly, but you can define a Materialized View with your condition
CREATE MATERIALIZED VIEW check_example
   BUILD IMMEDIATE
   REFRESH FAST ON COMMIT
   AS SELECT a,b
   FROM example
   WHERE x > 10On this MV you can define your unique constraint. The refresh will fail if the condition is not met and you will get an error for your changes in the example table..
Regards
Marcus

Mapping failed due to Unique Constraint

Hi,
We are using Oracle Financial Analytics and noticed that one of the mapping SIL_PositionDimenstionHierarchy failed due to Unique Constraint.
Mapping was inserting data into W_POSITION_DH table.
Is there a way to find the source table from where it is inserting the record?
I don't have much Informatica experience.
Thanks,
Poojak

Hi,
Our servers are hosted to Oracle On Demand. I have opened a ticket with Oracle. They have asked us to aply a patch to increase the version of the Mapping.
Please see update from Analyst.
"Development team is requesting to apply patch number 9782718, which solves this issue as well.
You need to go to Patches and Updates tab on Support Portal, click on Oracle, Siebel and Hyperion products link and do a simple search with patch number 9782718. The patch files contain detailed instructions.
Please test on your Test environment first before applying to Production. Let us know if you have any issues.
Thanks,
Poojak

Creating a view on KONA & KONH - Failed with 'Field name DATAB not unique'

Hi all,
    I am creating a view on KONA (Rebate Agreement) & KONH (Conditions Header) tables. The link is KONA-KNUMA = KONH-KNUMA_AG.
   The field 'DATAB' exists in both tables and I have included those two fields under 'View Fields' . When I tried to activate the View, it fails with 'Field name DATAB not unique'.
   The following is the complete error message:
Message no. MC060
Diagnosis
When you define aggregates (views, lock objects or matchcode objects), you can assign the aggregate fields your own names (the system assigns names to the basic fields automatically). These names must be unique.
System response
The system has established that the names assigned to the aggregate fields in an aggregate definition are not unique and issues an error message.
Procedure
Assign unique names to the aggregate fields in question.
   Why I am not able to create the view after including a field that EXISTS in two tables, PLEASE ?
Thanks,
Venkat.

Hi,
you can include both fields (but what for??); most likely KNUMH will also complain after fixing DATAB (just a guess...).
You can include both fields if you name them differently (different aliases):
In the view fields tab, enter two different names in the column "view field".
this will work.
hope this helps...
Olivier.
Message was edited by:
        Olivier Cora

ASCP erroring out with ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITI

Here is log
=====================================================
18-AUG 11:06:25 : ======================================== 18-AUG
11:06:25 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG 11:06:27 : COLUMN=ORGANIZATION_CODE,
VALUE=TST:M1 18-AUG 11:06:27 : COLUMN=RESOURCE_ID, VALUE=14 18-AUG
11:06:27 : COLUMN=FROM_SETUP_ID, VALUE=1 18-AUG 11:06:27 :
COLUMN=TO_SETUP_ID, VALUE=2 18-AUG 11:06:27 : ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:27 :
======================================== 18-AUG 11:06:27 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG
11:06:27 : COLUMN=ORGANIZATION_CODE, VALUE=TST:M1 18-AUG 11:06:27 :
COLUMN=RESOURCE_ID, VALUE=14 18-AUG 11:06:27 : COLUMN=FROM_SETUP_ID,
VALUE=2 18-AUG 11:06:28 : COLUMN=TO_SETUP_ID, VALUE=1 18-AUG 11:06:28 :
ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:28 : ======================================== 18-AUG
11:06:28 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG 11:06:28 : COLUMN=ORGANIZATION_CODE,
VALUE=TST:M1 18-AUG 11:06:28 : COLUMN=RESOURCE_ID, VALUE=16 18-AUG
11:06:28 : COLUMN=FROM_SETUP_ID, VALUE=1 18-AUG 11:06:28 :
COLUMN=TO_SETUP_ID, VALUE=2 18-AUG 11:06:28 : ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:28 :
======================================== 18-AUG 11:06:28 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG
11:06:28 : COLUMN=ORGANIZATION_CODE, VALUE=TST:M1 18-AUG 11:06:28 :
COLUMN=RESOURCE_ID, VALUE=16 18-AUG 11:06:28 : COLUMN=FROM_SETUP_ID,
VALUE=2 18-AUG 11:06:28 : COLUMN=TO_SETUP_ID, VALUE=1 18-AUG 11:06:28 :
ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:28 : Total resource transition = 167 18-AUG 11:06:28 : .1 minutes elapsed.
18-AUG 11:06:30 : Procedure MSC_CL_RPO_ODS_LOAD.LOAD_IRO_DEMAND;
started. 18-AUG 11:06:31 : <<LOAD_IRO_DEMAND>> 18-AUG 11:06:31 :
<<CURSOR>>INSERT /*+ APPEND */ INTO DEMANDS_TST( PLAN_ID, DEMAND_ID, DISPOSITION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, USING_ASSEMBLY_ITEM_ID, USING_ASSEMBLY_DEMAND_DATE, USING_REQUIREMENT_QUANTITY, QUANTITY_PER_ASSEMBLY, ISSUED_QUANTITY, ASSEMBLY_DEMAND_COMP_DATE, DEMAND_TYPE, ORIGINATION_TYPE, SOURCE_ORGANIZATION_ID, RESERVATION_ID, OP_SEQ_NUM, DEMAND_CLASS, REPETITIVE_SCHEDULE_ID, SR_INSTANCE_ID, PROJECT_ID, TASK_ID, PLANNING_GROUP, UNIT_NUMBER, ORDER_NUMBER, REPAIR_LINE_ID, WIP_ENTITY_ID, WIP_ENTITY_NAME, WIP_STATUS_CODE, WIP_SUPPLY_TYPE, ASSET_ITEM_ID, ASSET_SERIAL_NUMBER, COMPONENT_SCALING_TYPE, COMPONENT_YIELD_FACTOR,null,null, REFRESH_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY)SELECT -1, MSC_DEMANDS_S.nextval, NVL(ms.TRANSACTION_ID,-1) DISPOSITION_ID, t1.INVENTORY_ITEM_ID, msd.ORGANIZATION_ID, t2.INVENTORY_ITEM_ID USING_ASSEMBLY_ITEM_ID, nvl(msd.USING_ASSEMBLY_DEMAND_DATE,ms.new_schedule_date),
msd.USING_REQUIREMENT_QUANTITY, msd.QUANTITY_PER_ASSEMBLY, msd.QUANTITY_ISSUED, msd.ASSEMBLY_DEMAND_COMP_DATE, msd.DEMAND_TYPE, msd.ORIGINATION_TYPE, msd.SOURCE_ORGANIZATION_ID, msd.RESERVATION_ID, msd.OPERATION_SEQ_NUM, msd.DEMAND_CLASS, msd.REPETITIVE_SCHEDULE_ID, msd.SR_INSTANCE_ID, msd.PROJECT_ID, msd.TASK_ID, msd.PLANNING_GROUP, msd.END_ITEM_UNIT_NUMBER,
REPLACE(REPLACE(substr(msd.ORDER_NUMBER,1,62),:v_chr10),:v_chr13)
ORDER_NUMBER, REPAIR_LINE_ID , msd.WIP_ENTITY_ID, msd.WIP_ENTITY_NAME, msd.WIP_STATUS_CODE, msd.WIP_SUPPLY_TYPE, t3.inventory_item_id ASSET_ITEM_ID, msd.ASSET_SERIAL_NUMBER, msd.COMPONENT_SCALING_TYPE, msd.COMPONENT_YIELD_FACTOR,null,null, :v_last_collection_id, :v_current_date, :v_current_user, :v_current_date, :v_current_user FROM MSC_ITEM_ID_LID t1, MSC_ITEM_ID_LID t2, MSC_ITEM_ID_LID t3,SUPPLIES_TST ms, MSC_ST_DEMANDS msd WHERE msd.SR_INSTANCE_ID= 21 AND msd.ORIGINATION_TYPE = 77 AND msd.DELETED_FLAG= 2 AND t1.SR_INVENTORY_ITEM_ID= msd.inventory_item_id AND t1.sr_instance_id= msd.SR_INSTANCE_ID AND t2.SR_INVENTORY_ITEM_ID= msd.using_assembly_item_id AND t2.sr_instance_id= msd.SR_INSTANCE_ID AND t3.SR_INVENTORY_ITEM_ID (+)= msd.ASSET_ITEM_ID AND t3.sr_instance_id (+) = msd.SR_INSTANCE_ID AND ms.sr_instance_id= msd.SR_INSTANCE_ID AND ms.ORGANIZATION_ID= msd.ORGANIZATION_ID AND ms.DISPOSITION_ID= msd.repair_line_id AND ms.plan_id=-1 AND ms.ORDER_TYPE= 75 18-AUG
11:06:31 : ORA-01747: invalid user.table.column, table.column, or column specification 18-AUG 11:06:31 : .1 minutes elapsed.
===================================================
any help is appreciated. Just got this Bug 8661320, ref with no help. Its on R12 12.1.1

Sundeep,
No similar errors are reported in Metalink, so I would suggest you log a SR.
Regards,
Hussein

SIL_GLCOGSFact Failed with Unique Constraint

Similar Messages

Maybe you are looking for