Professional Documents
Culture Documents
Croovg
Croovg
supported?
ORIGINAL
-‐
create
new
document
ADD
-‐
add
new
lines
onto
an
existing
document
UPDATE
-‐
update
existing
line
information
for
document
REPLACE
-‐
Replace
the
existing
document
Which
interface
tables
are
involved?
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE(Used
for
Standard
PO
only)
Which
document
types
can
be
updated
by
using
Purchasing
Document
Open
interface?
Blankets
and
quotations
created
by
Purchasing
Document
Open
Interface.
Blankets
and
quotations
created
manually
via
Oracle
Applications
standard
forms
can
not
be
updated
by
using
Purchasing
Document
Open
Interface
since
there
is
no
value
for
vendor_order_num
for
blanket
or
quote_vendor_quote_number
for
quotation.
In
release
11.5.10,
new
lines
and
associated
shipments
can
be
added
to
an
existing
standard
purchase
order
created
by
PDOI.
Existing
lines
in
the
Standard
PO
can
not
be
updated
using
this
process.
P2P
Interview
Preparation
-‐
by
Dinesh
Kumar
REQ
Import:
Program
Name:
Requisition
Import
Short
Name:
REQIMPORT
Application:
Purchasing
Executable:
POCIRM
Executable
Method:
Spawned
Tables:
Table
Name
Mandatory
Columns
PO_REQUISITIONS_INTERFACE_ALL
§ INTERFACE_SOURCE_CODE
§ DESTINATION_TYPE_CODE
§ AUTHORIZATION_STATUS
PO_REQ_DIST_INTERFACE_ALL
§ INTERFACE_SOURCE_CODE
PO_INTERFACE_ERRORS
§ INTERFACE_TYPE
§ INTERFACE_TRANSACTION_ID
§ CREATION_DATE
§ CREATED_BY
§ LAST_UPDATE_DATE
§ LAST_UPDATED_BY
FAQ
-‐
REQ
Import:
What
methods
are
available
in
the
application
to
resolve
errored
records
in
the
PO_INTERFACE_ERRORS
table?
Oracle
Purchasing
provides
the
Requisition
Import
Exceptions
Report,
which
can
be
used
to
diagnose
problems
with
the
records,
which
have
currently
errored
out
in
the
PO_REQUISITIONS_INTERFACE_ALL
table.
To
run
the
report,
follow
these
steps:
1.
Using
Purchasing
responsibility,
navigate
to
Reports-‐>Run
2.
Select
the
Requisition
Import
Exceptions
Report
There
is
parameter
titled
'Delete
Exceptions'.
If
this
is
populated
with
'Yes',
then
all
records
in
the
PO_REQUISITIONS_INTERFACE_ALL
table
with
status
of
'ERROR'
and
the
corresponding
records
in
the
PO_INTERFACE_ERRORS
will
be
deleted
when
the
report
is
executed.
You
can
also
restrict
the
deleted
records
by
selecting
the
Batch_id
and
the
Interface
Source
code.
If
the
parameter
is
set
to
No,
then
you
will
see
the
errors
from
the
report
and
be
able
to
manually
fix
the
data
in
the
table,
if
so
desired;
then,
upon
completion
of
the
data
correction,
run
Requisition
Import
again
to
process
the
modified
rows
in
the
interface
table.
What
are
the
grouping
options
for
imported
requisitions?
The
requisition
import
process
has
group
by
parameter.
Use
this
feature
to
determine
how
requisition
lines
are
grouped
on
the
requisitions
you
create.
The
default
in
this
field
is
set
in
the
Purchasing
Options
window.
Choose
one
of
the
following
options:
All:
Group
all
requisition
lines
on
one
requisition
P2P
Interview
Preparation
-‐
by
Dinesh
Kumar
Buyer:
Group
requisition
lines
for
each
buyer
name
on
separate
requisition
Category:
Group
requisition
lines
for
each
purchasing
category
on
separate
requisition
Item:
Group
requisition
lines
for
each
item
on
separate
requisition
Location:
Group
requisition
lines
for
each
location
on
separate
requisition
Supplier:
Group
requisition
lines
for
each
supplier
name
on
separate
Requisition
To
define
default
in
the
Purchasing
Options
form,
follow
these
steps:
1.
Using
Purchasing
responsibility,
navigate
to
Setup-‐>
Organizations-‐>
Purchasing
Options
2.
Enter
default
value
for
the
'Requisition
Import
Group-‐By'
field
(under
Document
Defaults)
3.
Save
changes
The
Requisition
Import
process
will
first
look
at
the
group
by
parameter
selected
when
the
process
is
submitted;
should
this
parameter
be
left
blank,
the
system
will
then
look
to
the
group
by
field
residing
in
the
Purchasing
Options
form.
How
does
Requisition
Import
determine
the
grouping
method
for
incoming
pieces
of
data?
The
process
groups
requisitions
following
this
order:
1. Assign
values
to
REQUISITION_LINE_ID
and
REQ_DISTRIBUTION_ID
2. Group
requisitions
based
on
the
REQ_NUMBER_SEGMENT1
column.
All
requisitions
with
the
same
NOT
NULL
REQ_NUMBER_SEGMENT1
are
assigned
the
same
REQUISITION_HEADER_ID.
3. Group
requisitions
based
on
the
GROUP_CODE
column.
All
requisitions
with
the
same
value
in
the
GROUP_CODE
column
are
assigned
the
same
REQUISITION_HEADER_ID.
4. Group
requisitions
based
on
the
GROUP_BY
parameter,
which
takes
on
the
value
of
DEFAULT_GROUP_BY
if
not
provided.
GROUP_BY
could
be
one
of
the
following:
BUYER,
CATEGORY,
ITEM,
VENDOR,
LOCATION
or
ALL.
How
can
automatically
approve
the
requisitions
am
creating?
There
are
two
ways
of
doing
this:
1. You
can
populate
records
in
the
Interface
table
with
status
as
Approved.
In
this
case
the
Approval
process
is
not
called
after
creating
the
requisition.
2. If
you
want
the
requisitions
created
to
go
through
the
approval
process
then
you
have
to
set
Requisition
Import
Parameter
'Initiate
Approval
after
Reqimport'
to
'Yes'
when
Launching
the
Requisition
Import
Concurrent
Program.
3. Yes:
The
PO
Requisition
Approval
workflow
is
launched
automatically
for
requisitions
imported
with
status
of
Pre-‐Approved
or
Incomplete.
No:
The
PO
Requisition
Approval
workflow
is
not
automatically
launched
for
Pre-‐Approved
or
Incomplete
requisitions.
You
can
submit
these
to
the
approval
process
later,
when
you
select
the
Approve
button
on
the
requisition.
For
the
Requisition
to
be
automatically
Approved,
the
APPROVER_ID
value
from
PO_REQUISITIONS_INTERFACE_ALL
must
have
authority
to
approve
the
requisition.
If
that
user
does
not
have
approval
authority,
then
the
requisition
will
be
in
status
In
Process
and
forwarded
up
that
user's
Approval
Hierarchy.
Can
requisition
import
handle
multiple
currencies?
Requisition
Import
is
capable
of
handling
multiple
currencies,
provided
that
all
rate
types
and
currency
conversions
have
been
defined.
Can
requisition
import
handle
multiple
distributions?
P2P
Interview
Preparation
-‐
by
Dinesh
Kumar
Requisition
Import
can
handle
multiple
distributions.
Is
requisition
import
organization-‐specific?
Requisition
Import
is
operating
unit-‐specific.
Within
the
PO_REQUISITIONS_INTERFACE_ALL
table
lies
the
column
ORG_ID.Upon
Initiating
the
Requisition
Import
program,
the
profile
'MO:
Operating
Unit'
is
queried
to
derive
the
value
of
ORG_ID
tied
to
the
login
running
the
program.
Then
the
Requisition
Import
program
executes,
all
records
in
the
interface
table
which
are
the
same
as
the
organization
listed
in
the
'MO:
Operating
Unit'
profile
will
be
processed.
If
you
don't
see
any
valid
Import
source
when
you
launch
Reqimport
but
if
you
had
already
populated
the
Interface
table
then
you
have
to
check
the
org_id
Column
you
populated.
this
org_id
will
be
your
operating
unit
tied
to
your
Applications
log-‐
in
responsibility.
If
the
org_id
is
NULL
then
you
can
see
you
record
in
the
Import
Source.
Here
is
script
to
assist:
select
hr.name
from
hr_all_organization_units
hr,
po_requisitions_interface_all
pri
where
hr.organization_id
pri.org_id
and
pri.interface_source_code
'&source'
order
by
pri.creation_date
desc;