Applies to:
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-2540254671.
Symptoms
SBL-EAI-04184
Hello,
We are running into an issue while using ADM to migrate product data using the Product Data Type method. When trying to migrate a product that does not already exist in the target environment, we obtain an error stating that no inserts are allowed (Please see the attached screenshot). Note that migrating updates to a product that already has an older version in the target environment works fine.
Here are the steps to reproduce the error:
1. Create Product A in Source environment (can be simple or customizable product). Ensure that this product does not exist in the Target environment.
2. Go to ADM->Deployment Projects. Create a new project using the data type 'ProductData'.
3. Go to Deployment Session. Create a new session based on the deployment project just created. Set the deployment filter to [Name]='Product A', click Deploy.
4. In the Target environment, go to ADM->Deployment Sessions->Menu->Deploy from File. The attached error is obtained.
Thanks for your help in advance.
Cheers
Solution
Message 1
[1 / 2]
For the benefits of other readers,
When customer migrate a product using Application Deployment Manager (ADM) in Siebel 7.8.2 [19213], the following error occurred:
No inserts are allowed in Integration Component 'Internal Product - ISS Admin'.
(SBL-EAI-04184)
In the ADM process, they used 'ProductData' as data type (content object: Product (ADM)) and underlying integration object 'UDA Admin Product Definition'.
From the research, it was found that the integration component 'Internal Product - ISS Admin' within the integration object ‘'UDA Admin Product Definition' has the user properties:
- NoDelete: Y
- NoInsert: Y
It indicated that it is not allow user to insert or delete the product data using the integration component. That is, the reported error was expected one based on the configuration of the integration component. In fact, it is not possible to use ADM to create new simple products, but updates are possible in Siebel 7.8.x. To get this working, products must be part of a joint workspace project and ADM can migrate these well.
(Cont) ...
Message 2
[2 / 2]
Siebel Bookshelf, Product Administration Guide > Releasing Products and Other Versioned Objects > Migrating Products Among Environments reads that
Migrating Products Using Application Deployment Manager (ADM). This method allows you to move both versioned and unversioned data.
It would mislead that ADM can be used to migrate new product data from source to target environment including creating and deleting products. As result, Change Request 12-16BAJM7 has been logged to address this documentation defect.
Please also refer service request 38-2040903971 (ADM error “No inserts are allowed in Integration Component ‘Internal Product – ISS Admin'") in SupportWeb.
Kind Regards,
Siebel Technical Support
Applies to:
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-2540254671.
Symptoms
SBL-EAI-04184
Hello,
We are running into an issue while using ADM to migrate product data using the Product Data Type method. When trying to migrate a product that does not already exist in the target environment, we obtain an error stating that no inserts are allowed (Please see the attached screenshot). Note that migrating updates to a product that already has an older version in the target environment works fine.
Here are the steps to reproduce the error:
1. Create Product A in Source environment (can be simple or customizable product). Ensure that this product does not exist in the Target environment.
2. Go to ADM->Deployment Projects. Create a new project using the data type 'ProductData'.
3. Go to Deployment Session. Create a new session based on the deployment project just created. Set the deployment filter to [Name]='Product A', click Deploy.
4. In the Target environment, go to ADM->Deployment Sessions->Menu->Deploy from File. The attached error is obtained.
Thanks for your help in advance.
Cheers
Solution
Message 1
[1 / 2]
For the benefits of other readers,
When customer migrate a product using Application Deployment Manager (ADM) in Siebel 7.8.2 [19213], the following error occurred:
No inserts are allowed in Integration Component 'Internal Product - ISS Admin'.
(SBL-EAI-04184)
In the ADM process, they used 'ProductData' as data type (content object: Product (ADM)) and underlying integration object 'UDA Admin Product Definition'.
From the research, it was found that the integration component 'Internal Product - ISS Admin' within the integration object ‘'UDA Admin Product Definition' has the user properties:
- NoDelete: Y
- NoInsert: Y
It indicated that it is not allow user to insert or delete the product data using the integration component. That is, the reported error was expected one based on the configuration of the integration component. In fact, it is not possible to use ADM to create new simple products, but updates are possible in Siebel 7.8.x. To get this working, products must be part of a joint workspace project and ADM can migrate these well.
(Cont) ...
Message 2
[2 / 2]
Siebel Bookshelf, Product Administration Guide > Releasing Products and Other Versioned Objects > Migrating Products Among Environments reads that
Migrating Products Using Application Deployment Manager (ADM). This method allows you to move both versioned and unversioned data.
It would mislead that ADM can be used to migrate new product data from source to target environment including creating and deleting products. As result, Change Request 12-16BAJM7 has been logged to address this documentation defect.
Please also refer service request 38-2040903971 (ADM error “No inserts are allowed in Integration Component ‘Internal Product – ISS Admin'") in SupportWeb.
Kind Regards,
Siebel Technical Support
No comments:
Post a Comment