0% found this document useful (0 votes)
31 views

How Does Requisition Import Process Generate Accounts?

The document discusses importing items into Oracle Inventory using the Item Interface. It provides an overview of the item import process, describes the tables and fields used, and answers common questions about resolving errors. The Item Interface reads data from interface tables and imports new items, revisions, and categories while assigning defaults and validating data. Errors are tracked in the MTL_INTERFACE_ERRORS table.

Uploaded by

kumar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views

How Does Requisition Import Process Generate Accounts?

The document discusses importing items into Oracle Inventory using the Item Interface. It provides an overview of the item import process, describes the tables and fields used, and answers common questions about resolving errors. The Item Interface reads data from interface tables and imports new items, revisions, and categories while assigning defaults and validating data. Errors are tracked in the MTL_INTERFACE_ERRORS table.

Uploaded by

kumar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 16

How

does
requisition
import
process
generate
accounts?
It
can
be
either
one
of
two
methods
for
accounts
to
be
generated:
1.
By
a
valid
CCID
or
2.
By
a
valid
combination
of
account
segments.
Requisition
import
does
not
use
the
account
generator
process.
The
process
validates
the
charge_account_id
or
the
combination
of
account
segments
which
are
populated
in
the
interface
table.
This
is
the
existing
functionality.
An
enhancement
request
Bug
2245333
is
logged
to
request
the
ability
for
the
requisition
import
to
use
the
same
logic
used
in
the
requisition
form.
When
I
load
the
Requisition
Interface
and
create
Requisitions
it
always
does
sourcing.
How
can
I
stop
sourcing
from
happening?
You
have
to
set
the
autosource_flag
in
the
Requisition
interface
to
'N'
to
avoid
vendor
Sourcing
How
can
I
avoid
sourcing
from
overriding
my
vendor
information?
You
have
to
set
the
autosource_flag
to
'P'
for
partial
sourcing.
Does
the
requisition
import
allow
note
to
vendor
to
be
imported
on
requisitions?
The
requisition
import
does
not
support
the
note
to
vendor
field
at
this
time.
How
to
Import
the
Requisition
ordered
by
Line
Number?
Per
standard
functionality
the
line
number
is
a
sequence
number
starting
from
1
for
records
having
the
same
requisition
header
id
order
by
item_description
and
quantity.
In
other
words,
the
po_requisition_lines
table
is
ordered
by
item_description
and
quantity
for
the
same
header_id
and
then
the
line_num
is
updated
with
a
counter
that
increments
by
1.
It
is
not
possible
to
populate
line
number
in
the
interface
table.
The
following
enhancement
requests
are
logged
requesting
the
ability
to
sort
the
lines:
Enhancement
Request
<
Bug
3906591>
and
Enhancement
Request
Bug
4205941.
Item
Import
:
Import
Overview:
§ Use
the
item
import
process
to
import
items
from
your
legacy
system
or
PDM
system.
You
can
import
items
from
any
source
into
Oracle
Inventory
and
Oracle
Engineering.
§ When
you
import
items
through
the
Item
Interface,
you
create
new
items
in
your
Item
Master
organization
or
assign
existing
items
to
additional
organizations.
You
can
specify
values
for
all
the
item
attributes,
or
you
can
specify
just
a
few
attributes
and
let
the
remainder
default
or
remain
Null.
§ You
can
also
specify
an
item
template
for
each
item
and
inherit
attribute
values
from
the
template.
§ The
Item
Interface
also
lets
you
import
revision
details,
including
past
and
future
revisions
and
effective
dates.
Program
Name:
Import
Items
Short
Name:
INCOIN
Application:
Inventory
Executable:
INCOIN
Executable
Method:
Spawned
Tables:
Table
Name
Mandatory
Columns
MTL_SYSTEM_ITEM_INTERFACE
§ SET_PROCESS_ID
MTL_ITEM_REVISIONS_INTERFACE
§ SET_PROCESS_ID
MTL_ITEM_CATEGORIES_INTERFACE
§ SET_PROCESS_ID
MTL_INTERFACE_ERRORS
§ LAST_UPDATE_DATE
§ LAST_UPDATED_BY
§ CREATION_DATE
§ CREATED_BY
§ The
Item
Interface
reads
data
from
two
tables
for
importing
items
and
item
details.
You
use
the
MTL_SYSTEMS_ITEM_INTERFACE
table
for
new
item
numbers
and
all
item
attributes.
This
is
the
main
item
interface
table,
and
can
be
the
only
table
you
choose
to
use.
§ If
you
are
importing
revision
details
for
new
items,
you
can
use
the
MTL_ITEM_REVISIONS_INTERFACE
table.
A
third
table,
MTL_INTERFACE_ERRORS,
is
used
for
error
tracking
of
all
items
that
the
Item
Interface
fails.
You
can
import
item
categories
using
interface
table
called
as
MTL_ITEM_CATEGORIES_INTERFACE.
§ Before
you
use
the
Item
Interface,
you
must
write
and
run
a
custom
program
that
extracts
item
information
from
your
source
system
and
inserts
it
into
the
MTL_SYSTEM_ITEM_INTERFACE
table,
and
(if
revision
detail
is
included)
the
MTL_ITEMS_REVISIONS_INTERFACE
table.
§ After
you
load
the
items
into
these
interface
tables,
you
run
the
Item
Interface
to
import
the
data.
§ The
Item
Interface
assigns
defaults,
validates
data
you
include,
and
then
imports
the
new
items.
You
may
also
specify
an
item
template
for
each
item
being
imported.
§ You
must
import
items
into
the
Item
Master
organization
before
you
import
items
into
additional
organizations.
You
can
accomplish
this
by
specifying
only
your
Item
Master
organization
on
first
run
of
the
Item
Interface.
Once
this
has
completed,
you
can
run
the
Item
Interface
again,
this
time
specifying
an
additional
or
all
organizations.
You
can
also
use
the
Item
Interface
to
import
a
single
item
material
cost
and
material
overhead,
and
revision
details.
FAQ
--‐
Item
Import:
How
do
I
know
what
error
has
occurred?
§ The
process_flag
in
mtl_system_items_interface
will
be
3.
Now
the
error
message
will
be
in
mtl_interface_errors
table.
§ The
record
in
mtl_system_items_interface
will
have
a
transaction_id.
There
will
be
corresponding
record
with
error
code
and
explanation
in
mtl_interface_errors.
select
transaction_id
from
mtl_system_items_interface
where
process_flag
=
3;
§ Now
substitue
the
&transaction_id
value
in
the
following
sql
by
the
value
that
you
get
in
the
ablove
sql.
You
should
be
able
to
see
the
error.
select
message_name,column_name,error_message
from
mtl_interface_errors
where
transaction_id
=
&transaction_id;
What
things
should
I
check
if
I
getting
errors?
§ First
check
if
you
are
populating
the
correct
values
in
all
the
fields.
§ Then
check
if
there
are
any
mandatory
descriptive
flexfield
columns.
§ You
can
go
to
application
setup
>
flexfields
>

You might also like