Purchase Options-problem defining
From: fariha afreen [mailto:fafreen@ora-tech.com]
Sent: Tuesday, October 26, 1999 5:55 AM
To: Multiple recipients of list
Subject: Problemin defining Purchasing Options
Hi,
We am facing a problem that we are implementing Oracle
Payables,
Inventory and Purchasing, while defing Purchasing Options ,
in Internal
Requisition Window, it ask for Order Type and when we ask
for List of
value, its empty. We are not using Order Entry Module.....
What to do.
And without defining Order Type , it won't save the
Purchasing
Options......
Your help will be highly appreciated.....
Thanks
Fariha
Date: Tue, 26 Oct 1999 08:09:07 -0500
From: "Severtson, Anne" amsevertson@sbec.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Problemin defining Purchasing Options
Try not going to that screen. If you go to that screen, it expects it to be
completed. Therefore, do not select that group.
Anne
Date: Tue, 26 Oct 1999 05:55:37 -0700
From: "Sadhwani, Suneel" SSadhwani@ea.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Problemin defining Purchasing Options
Hi Fariha
Are you using 10.7 version , if yes then this is a bug . Simply empty the
field and save it .
It gives this message 'Field must be entered' . But you can save this
without any value in it .
Rgds
Suneel
Date: Tue, 26 Oct 1999 15:02:53 +0200
From: Gorre Richard GorreR@fnherstal.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Problemin defining Purchasing Options
Hi
I suppose the system is requiring Internal order type ?
I define it from OE, but an oracle consulting people told me, it was
possible to define this internal order type from INV
br
Richard
Date: Tue, 26 Oct 1999 15:10:45 +0200
From: Mike Bennet MikeB@langeberg.co.za
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Problemin defining Purchasing Options
Try defining the purchasing options from the Inventory module setup. I think
I recall that was possible without having to complete the internal order
fields. Another option is to use character mode to update the purchasing
options fields.
Regards
Mike
Date: Tue, 26 Oct 1999 06:30:22 -0700 (PDT)
From: "Jay P." jpmrp@yahoo.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Problemin defining Purchasing Options
Make sure you have added a default price list to your internal order
type in OE. If you haven't it will not give you the order type in
the LOV.
Hope this helps
Jay Patel
Gaylord Entertainment
Date: Tue, 26 Oct 1999 23:48:53 +0700
From: "Nagamohan U." umohan@irs.co.id
To: oraapps-l@cpa.qc.ca
Subject: RE: Problemin defining Purchasing Options
Hi Fariha
Trt this.
Go the Sysadmin responsibility and go to \Install\Information. Query up the
Order Entry Application and save it as Installed or shared. And then try to
save the Purchasing Options set up in the PO.
Regards/Nagamohan
Tuesday, October 26, 1999
Workflow for PO/PR notification
Date: Fri, 29 Oct 1999 18:50:06 +0800
From: "220 Hsieh, Patrick" patrickh@ctxopto.com.tw
To: OraApps-L@cpa.qc.ca
Subject: PO: Using Workflow for PO/PR notification upon upgrading to R11
We just upgrade to R11 from 10.7SC.
Before upgrade, we learned from many scattered documents that the approval
flow for PR/PO
(and flows in other Modules) is replaced by the Embedded Workflow engine.
Could any guru please advise where to start setting the right approval flow?
Are there any related documents
from Oracle?
Thanks,
Patrick
Date: Sun, 31 Oct 1999 01:11:19 -0700 (PDT)
From: kartik iyer mukul061292@yahoo.com
To: oraapps-l@cpa.qc.ca
Subject: Re: PO: Using Workflow for PO/PR notification upon upgrading to R11
DearPatrick,
Hi! I am Kartik . I have implemented the
Purchase module The version is 11.0.3The procedure for
the set up for approval of documents is as follows:
1.Define 2 employees
2.Define 2 positions.
3.Attach a position to the employees (for boss and
subordinate both )
4.Define a position hierarchy
5.In the position hierarchy screen mention the
person's position whom you want to be reporting to
higher authority as the subordinate position
6.DEfine the approval documents(Approval assignments
)for both these positions
7.Define approval groups.
8.The approval groups and the positions must be the
same.
9.Set the document types in the Purchasing options in
the setup
please try and if any doubts contact me.
Thanks,
Kartik,
Relicon Dubai
Date: Mon, 1 Nov 1999 08:16:13 +0800
From: "220 Hsieh, Patrick" patrickh@ctxopto.com.tw
To: oraapps-l@cpa.qc.ca
Subject: RE: PO: Using Workflow for PO/PR notification upon upgrading to R
Thanks. I also read documents - don't remember where - that the Syst Adm
has to
turn on the "Workflow Background Process" including a couple "item types"
like "PO Approval",
"PO Requisition Approval", etc. Do you have experience with that?
Regards,
Patrick
Date: Tue, 02 Nov 1999 17:12:01 GMT
From: "Ananth Swaminath" ananth999@hotmail.com
To: oraapps-l@cpa.qc.ca
Subject: Reply: PO: Using Workflow for PO/PR notification upon upgrading to
R11
Hi Patrick
In addition to what Kartik has mentioned below:
You need to define Jobs and associate each employee to a job. Jobs are a
required setup in PO. You can decide to use Approval Hierarchies or not. In
case you do, Positions have to be defined to and you can create Position
Hierarchies depending upon the business rules that your organisation has
over procurement.
PO is probably the most active user of the Workflow Engine. You need to
schedule the Worflow Background Process (From Sysadmin). Each Workflow
process is identified as an Item Type. PO uses 3 workflow processes:
- PO Approval
- PO Requisition Approval
- PO Send Notifications
Each of these processes must be scheduled to run as per the periodicity of
raising and approving documents (This can be determined from the Purchase
Department and key users). The first 2 processes relate to document
approval. The 3rd one relates to notifying users on the actions that have
been perfomed/to be performed on the document.
The other parameters are:
- Minimum Threshold, Maximum Threshold. This relates to the minimum and
maximum cost an activity can possess in order to spawn to workflow
background process.
- Process Deferred and Process Timeout. Atleast ONE Workflow Background
process must be set to Yes. Timing out tell the system that it must wait for
"x" days prior to forwarding the document to the next person in the
hieararchy. Evidently, if this is set to No, the process will NOT time out
and will wait endlessly for the current owner of the document to perform
his/her action. To defer the process means that you specify whether this
background engine checks for deferred activities or not.
Be sure to set the profile option PO: Workflow Background Processing Mode to
"Background".
Find below the step wise procedure to start up the Approval Process in PO.
(Also note that the approval form in the document has a bug depending upon
the Form Version being used. This is a known bug).
1. Define Jobs
2. Define Posistions
3. Define Employees
4. Associate Users to Employees
5. Define Employees as Buyers
6. Decide whether or not you need to use Approval Hierarchies.
7. DEfine one or more Position Hiearchies.
8. Associate any one of the above as the Security Hierarchy in Global
Options.
9. Associate the Business Group at the Responsibility level for the profile
option HR: Security Level.
10. Define Approval Groups. Make sure that you have atleast Document Total
and Account Range defined.
11. Assign Approval Groups to each Job/Position for required Document Types.
12. Determine business rules for each Document Type. Select the Position
Hiearchy here. Also determine other rules you may need.
13. Run Fill Employee Hiearchy process from PO.
14. Set the PO: Workflow Background Process to Background.
15. Startup the Workflow Background processes from Sysadmin.
16. In case you encounter the bug in the Approval form - apply patch P758079
(check with Support based upon platform).
Your approval process should be up and running. However, if you do need any
further clarifications, do get in touch.
Cheers
Ananth
Associate Principal Consultant
Oracle Applications