This content has been marked as final. Show 4 replies
How is DB side application view set up? Was it imported as a table definition table in your database?
The DB application view was setup using the XML DTD.
Goel (got your name right this time!)
I always try to base my DB Application view on a DB table, usually a staging table, rather than a DTD.
e.g. Have your staging table look something like this....
iStudio will then only create the following sql script containing a "Publish" Package. (A second script _TYPES.sql, will be empty).
a. A crMsg_[your_event]_OAI_V1 procedure.
b. A cr-[Line_object_name] function, and
c. A pub_[your_event]_OAI_V1 procedure
1. Call the crMsg_[your_event]_OAI_V1 procedure first. There will be ONE IN paramter, and two OUT parameters....
- STUDY_NAMEOUT Parameters
- messageObjectID and2. Pass the messageObjectID and aoID into the cr_[Line_object_name], together with your Line data.
3. For every Line record, loop and pass your data to the A cr-[Line_object_name] function, including the messageObjectID and aoID created in step 1. When your cursor loop exits then...
4. Call the pub_[your_event]_OAI_V1 procedure.
If you have based your DB View on an XML DTD, then probably iStudio has created 2 sql scripts that you need to compile.
The first script will be similar to one described above. The other script (*_TYPES.sql) should contain the ItemRef Type your DB Adapter was complaining about.
Have a look at both scripts generated by iStudio when you Exported the PL/SQL from iStudio.
Thanks for your reply.
I solved this by declaring a DTD with the attributes as XML tags on the Database adapter side and transformed them while mapping on the FTP adapter side.