Best Of
Re: We have a requirement to record supplier quotations in the system and generate corresponding reports
Purchasing has the traditional quotes (also called RFQs) that you can load via an APIs and use as a pricing tool. Requisitions referencing these Quotes will be converted into Standard POs. Purchasing does offer a quote analysis tool/form that you can use or develop custom reports for your requirements.
Purchasing also has another module called Sourcing that offers extensive features in terms of creating RFQs and converting them into BPAs after negotiations with suppliers. The external suppliers can participate in the negotiation process be sending in their responses (i.e., Quotes) via iSupplier portal interface.
Re: We have a requirement to record supplier quotations in the system and generate corresponding reports
Hi -
Thanks for using Oracle community !
On Supplier quotations, refer
https://docs.oracle.com/cd/E18727_01/doc.121/e13410/T446883T443954.htm
Vision Demo - How To Demonstrate Requisition To Sourcing RFQ To Purchase Order (Doc ID 1612667.1)
regards,.
Ananth
Re: Price List Functionality in Oracle Purchasing.
Hi -
Thanks for using Oracle community !
Yes, on price list functionality please review
regards,
Ananth
Re: Price List Functionality in Oracle Purchasing.
Hi,
You can use "Advanced Pricing" in Purchasing
Check the following document for more information
What Are The Steps Required To Setup And Use Advanced Pricing in Purchasing Technical Brief (Doc ID 455778.1)
Vision Demo - How To Utilize Advanced Pricing in Purchasing (Doc ID 1101067.1)
Regards,
Sirisha
Re: Price List Functionality in Oracle Purchasing.
While you can use Adv. pricing capabilities in conjunction with contract purchasing agreements in Purchasing to keep track of the price of items, this is not an easy solution to manage from a buyer's perspective. I would suggest you to use Blanket Purchase Agreements (BPAs) or Quotations instead as your pricing instruments. Just sharing 2 cents from experience.
Re: Xml Publisher - That was a bad request!
Working OK again in test after apply October's CPU.
Re: Guidance on what program to use to upload payroll journal entries from an external program.
Thank you for posting your thread question.
the most common enterprise approach is to use the General Ledger (GL) Batch Journal Import functionality.
Here’s how it typically works:
1. Standard Import Programs
1.1. Standard Batch Journal Import (P09110Z1 / R09110Z)
- Table: F0911Z1 (Batch Journal Entry - External table)
- Upload: Load your journal entries from the external program into the F0911Z1 table, usually with a flat file or an integration tool (such as Oracle Integration Cloud, or via SQL scripting if permitted).
- Process: Run the Journal Entry Batch Processor (R09110Z) to process entries from F0911Z1 into the main GL tables (F0911) and create the corresponding journal entry batches.
- Access: Application P09110Z is used for managing and reviewing imported entries.
1.2. Payroll-Specific Integration
- If your external payroll system can output files in the format expected by the F0911Z1 table, or you can map your payroll data accordingly, this is the preferred method.
2. Payroll Close - Create Journal Entries (R072902)
- If payroll journal entries are generated within JDE (i.e., you are running payroll inside JDE), the standard process is to run the Payroll Close process (R072902), which moves the payroll entries into the GL.
- Note: This is not designed for importing external payroll entries, but only for payrolls run in JDE.
3. Custom Integrations
- Some organizations develop custom UBE (Universal Batch Engine) or Orchestration routines to import payroll journal entries if the source system does not match JDE’s import format.
- E1: Can 3rd Party Payroll Journal Entries (JEs's), T1-T7, be brought into JDE Summarized in Same Manner as Final Update? (Doc ID 3091612.1) is another option as well.
In summary:
The standard approach is to load data into F0911Z1 and use R09110Z (Batch Journal Import) to create GL batches, regardless of the external source.
Important:
- Always validate the data structure and mapping in F0911Z1.
- Test thoroughly in a non-production environment.
- Ensure compliance with your organization’s security and data governance protocols when moving data into JDE.
Regards,
TanyaM - Oracle
