| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Open Item Interface problems (Oracle Mfg)
Looking at the list of default column values 'supplied' by the interface, a number of these are defaulted by refering to values in other tables, i.e. default category set.
Firstly, I presume that when you refer to 'Global Org' you are refering
to your 'item master organization' and that this is an inventory
organization_id?
This must be populated by all items, *before* the interface will import
them into another organization_id. You seem to have gotten that far.
The next thing to check is that the the list of parameter tables that
are used for deriving default values are populated with the correct/any
data. It sometimes happens that there is an attempt to import items
using this interface, before enough of the set-up parameters have been
put in place.
Look in the Open Interface Manual- Open Item Interface (which I'm sure
you know well by now) and look at the 'Column Defaults in the Items
Interface Table' table. Run some adhoc queries against these tables to
make sure the interface can find the system defaults it needs.
As mentioned above, make sure you have a default category defined.
Your Financials set-up will need to be fairly advanced/complete before the interface will work.
I must say that given the relatively limited flexability of this
interface (at version 10.6) like;
cannot update/disable items, only create new,
cannot assign a category and sub-category,
requires all items in the master inventory org first,
my client chose to (have me) write a bespoke interface, to allow continuous maintenance by the legacy systems, until the are fully phased out. This did then allow the flexability of assigning categories at creation, disables, updates, not populate the master inventory org, make full use of the item templates where possible and default templates where not, custom create the CCID's and know *why* they aren't right when they don't work, user (programmer) defined exceptions and stored messages (that make sense) when individual item imports fail.....
Some of these features are invaluable when you are creating and then maintaining several thousand items, in a multiplicity of organizations, where this would have to be done on a item by item basis through the forms.
I don't recomend this lightly however, (and Oracle recomends it not at
all, so take heed -:)), as it is a large amount of programming to get
this just right.
To give you an idea, the current interface package amounts to just short
of 5800 lines of pl/sql code.
I hope the suggestions above are some help, if not, and no better/further ones come through, post again, with more detail of messages (mtl_interface_errors), etc. Happy to have another go!
Good luck.
In article <32FA9C4E.2376_at_qtm.net>, Bergs <berg_at_qtm.net> writes
>I'm trying to ensure the item interface works by importing a test item
>into the global DB, Global Org.
>
>According to the interface manual I should be able to accomplish this by
>setting item_number/segment1, description
>organization_id/organization_code, process_flag=1,
>and transaction_type='CREATE'
>
>I've also been playing with the COPY_xxxx of each but have had no luck.
>
>Does anyone have any suggestions?
>
>Thanks,
>
>Brant Berg
>
--
Mike Proctor Database Consultants International (UK)
Mike_Proctor_at_realworld.com Oracle vision.
Only Oracle.
All the time.
Received on Mon Feb 24 1997 - 00:00:00 CST
![]() |
![]() |