SQL.Fetch: object isn't open on a select

Usually, you come across this error when there are erroneous rows while loading data through Component Interface (CI).

You might be using any of the sql class functions to loop through the data and then inserting each row.  When an error occurs the CI closes the SQL object which is open. Thus subsequent rows will not get processed.

This is a problem as the subsequent rows which are valid are not getting inserted.
Now that we identified the cause for the issue, lets try to fix this issue.

Below is one such approach which helps in resolving the issue.

Resolution:
1. Create a standalone rowset and fill it with all the rows which needs to be inserted.

2. Now loop through the rowset and load the data through CI.

3. For error row, CI fails while saving. At this point , call the Cancel function as the current transaction is invalid.

4. After Successful cancellation of erroneous row , CI will move on to next row in the loop.

This way , we can avoid/skip error rows and proceed with insertion of other valid rows.
Hope this post is useful..

Component Interface Part1

You might have already heard about Component Interface (CI) as a medium through which we can insert data into component.

Agenda: Creating CI.

 Lets discuss some basic steps which are required to develop CI.

1. Assign component to CI through App Designer.
2. Check the validity of CI.
3. If no errors great!! If some errors , it will show 'X' marks in the CI structure.
    Below are some possible reasons for these errors.
    a) Key structure mismatch between CI and Component.
    b) Some property is missing which needs to be added to CI.
   Note: Even though if you donot get errors, later point in time if underlying component is changed     make sure to make CI to be in Sync with the component.
4. Cross check the Mode in which you want to use the CI like Add mode etc.
5. Testing the CI from App Designer by passing some data to the key values of component.
6. And lastly , add the permission list to CI.

Generally for many of the Delivered components PeopleSoft comesup with Component Interfaces.
So if any of these delivered components are customized then we have to make sure the CI is in sync with the new structure.

Component Interaces also called as CI in short, are also known as Enterprise Integration Points (EIP).

Before going further, we shall see one example of how to insert data through CI.