Purchasing

Get Involved. Join the Conversation.

Posts

  • NIRANJAN KRISHNA VARADHARAJAN
    BU AND ledger creation for procurement15.0
    Topic posted July 23, 2019 by NIRANJAN KRISHNA VARADHARAJANBlue Ribbon: 750+ Points, tagged Create Requisition, Financials, Fusion, General Ledger, Payables, Requisition Processing 
    Title:
    BU AND ledger creation for procurement
    Summary:
    doubt regarding enterprise structure
    Content:

    My client has 4 LE registered in 4 different countries and also does operations in various other countries now when an pr is raised from the countries they are not registered they do sourcing and after that they want to create po from any one of the L.E that they are registered can any body provide me with solution regarding enterprise structure that we can follow and req proc setups.

  • Harshith E S
    Need the concept/logic behind why Retroactive pricing is...1
    Topic posted March 29, 2019 by Harshith E SRed Ribbon: 250+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, BI Publisher Reports, Business Intelligence, Create Requisition, FAQ, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, Payables, Public Sector, Requisition Processing, Security, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Tip, Web Services, White Paper 
    Title:
    Need the concept/logic behind why Retroactive pricing is viable only with Non-Cumulative Price Break and not with Cumulative Price Break in BPA on Procurement Cloud ?
    Summary:
    We have a request from our client to have Retroactive pricing under Cumulative Price break in Blanket Purchase Agreement.
    Content:

    Hi all,

    Based on my research,

    For a retroactive pricing to reflect, it is suggested to choose price break type as Non-Cumulative.

    Need to understand the relation between Price Break and Retroactive Pricing, an explanation with a Business example would help.

    Please refer this document ID in My Oracle Support - (Doc ID 2259539.1) 

    Thank you,

    Harshith E S

     

     

    Version:
    19A (11.13.19.01.0)
  • Atul Kumar
    Manage Purchasing Document Lifecycle - Validate15.0
    Topic posted December 20, 2018 by Atul KumarBronze Medal: 1,250+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, BI Publisher Reports, Business Intelligence, Create Requisition, FAQ, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, Payables, Requisition Processing, Security, Setup, Supplier Communication, Tip, Web Services, White Paper 
    Title:
    Manage Purchasing Document Lifecycle - Validate
    Summary:
    Diagnostic is failing for Test name Manage Purchasing Document Lifecycle - Validate
    Content:

    Hi

    Getting below error while running diagonostics test on Test name Manage Purchasing Document Lifecycle - Validate even after running it from procurement page. Please let me know if you faced the same issue?

     

    Critical: Thread 15027: An error occurred while executing test: oracle.apps.prc.po.diagnostic.internal.PoDocumentActivity: Could not invoke test. Reasons could be because (a) The associated application ProcurementApp is not running (b) Credential Store and Permissions have not been set up correctly (c) The test is being invoked from outside the J2EE context.
    oracle.apps.fnd.appltest.diagfwk.common.DiagfwkException: Could not invoke test. Reasons could be because (a) The associated application ProcurementApp is not running (b) Credential Store and Permissions have not been set up correctly (c) The test is being invoked from outside the J2EE context. at oracle.apps.fnd.appltest.diagfwk.engine.impl.TestRunner.runTestViaMBean(TestRunner.java:324) at oracle.apps.fnd.appltest.diagfwk.engine.impl.TestRunner.run(TestRunner.java:224) at oracle.apps.fnd.appltest.diagfwk.engine.impl.TestRunner.doRun(TestRunner.java:152) at oracle.apps.fnd.appltest.diagfwk.engine.DiagRunnable.run(DiagRunnable.java:68) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622) at java.lang.Thread.run(Thread.java:745)
    Fix Information: An unexpected error was encountered. Please contact your system administrator.

  • Zakaria Soomro
    POs in Review Receipt Interface1
    Topic posted February 14, 2018 by Zakaria SoomroRed Ribbon: 250+ Points, tagged Financials, Fusion, General Ledger, Payables 
    Title:
    POs in Review Receipt Interface
    Content:

    Hello Everyone,

     

    I have query regarding the Purchase Orders appearing in review receipt interface. We have integrated Oracle Logfire (WMS) with Oracle Fusion and perform the following steps;

     

    1- Create PO in Fusion against Purchase Requisition

    2- Integrate/push that PO to Logfire.

    3- Receive the items in Logfire.

    4- Verify the receiving of items in Logfire (that push the receiving to Fusion)

    5- Run Manage Receiving Transactions to receive the same items in Fusion.

    6- Run Send Pay on Receipt in Fusion to create invoices in Payables.

     

    Some of items are not received in Fusion due to various reasons and same are appearing in Review Receipt Interface, then we have to manually them.

     

    Now I have the following questions;

     

    1- Can we receive all of the pending POs simultaneously, rather than one by one?

    2- After receiving one particular PO manually, why same is appearing again in Receipt Interface?

    3- What is financial impact of these pending POs on AP and GL?

     

    Thanks in advance for you kind response.

     

    Regards,

    Zakaria Soomro

  • Raju Ch
    Fusion P2P – Oracle Fusion Procure to Pay (P2P) L...5.0
    Topic posted July 22, 2019 by Raju ChGreen Ribbon: 100+ Points, tagged Approvals, Approvals/Notification, BI Publisher Reports, Create Requisition, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, OTBI, Payables, Requisition Processing, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Tip, White Paper 
    Title:
    Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow
    Content:
    The P2P cycle comprises of the following steps,
    01. Create Requisitions
    02. Approve Requisitions
    03. Create Purchase Orders
    04. Approve Purchase Orders
    05. Receive Goods
    06. Create Payables invoice with Match PO Lines
    07. Approve Invoice
    08. Invoice Payment to Supplier with Electronic Method
    09. Approve Payments
    10. Verify the Transaction Life Cycle
    11. Transfer Payables data to General Ledger
    12. Transfer Payments data to General Ledger
    13. Verify the Journal Batches
    14. Verify the Notifications in Mail
     

    Please click on the below link for more details:

    Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow
    https://oracleapps88.blogspot.com/2019/07/fusion-p2p-oracle-fusion-procure-to-pay.html

     

    Thanks,
    Raju Chinthapatla
    http://OracleApps88.Blogspot.com/
    OracleApps88@Yahoo.com
    (+91) 905 957 4321

    Version:
    R12
    Image:
  • Ivan Pena
    How to allows users to populate a segment of the PO charge...4.7
    Topic posted July 16, 2018 by Ivan PenaBronze Crown: 15,000+ Points, tagged Fusion, General Ledger, Setup, Tip 
    Title:
    How to allows users to populate a segment of the PO charge account
    Summary:
    How to allows users to populate a segment of the PO charge account
    Content:

    Business case

    You want users to be able to provide values for one or more segments of the chart of accounts, while allowing the application to derive the remaining segments using TAB (Transaction Account Builder.),

    Solution

    You can enable a DFF to capture the segment values entered by the user, and then configure Transaction Account Builder to override the respective COA segments with the DFF attribute values.

    Example

    Assume your COA has a segment called 'Department" and you want your PO users to be able to provide the value for this segment, while allowing TAB to derive the remaining COA segments.  The following steps outline the required setup:

    1. Enable a PO header DFF and use an attribute (say ATTRIBUTE1) to capture the Department. Make sure the DFF attribute uses the same value set as the COA segment you want to populate. (Let's say the value set name is COA_Department.) 
    2. Define an account rule in TAB of type "Value set" for the value set used by the COA segment you want to override (COA_Department in this example),) and select the corresponding DFF source (PO Header Attribute1 in this example) as input.
    3. Use the account rule created in (2) to override the corresponding segment In the Transaction Account Definition. Note the transaction account definition needs to have a chart of accounts assigned, so that you are able to assign account rules to named segments (Department in this example.)

    Ivan