Payables & Cash Management

Get Involved. Join the Conversation.

Topic

    Beth Bleijie
    Payables aging - backdated
    Topic posted April 8, 2018 by Beth BleijieBronze Trophy: 5,000+ Points, last edited January 30, 2019, tagged Financials, General Ledger, Payables, Period Close / Reconciliation 
    883 Views, 18 Comments
    Title:
    Payables aging - backdated
    Summary:
    Can't figure out how to reconcile Payables Aging to Balance Sheet
    Content:

    Through Oracle MOS I submitted an SR and was informed that it is not possible to produce an AP Aging report "as of" a past date.

    I still can't get over the idea that this fundamental reconciliation is not supported by Oracle. . .certainly we can't be the first Oracle user to come across this issue!  (I have been informed that it will be available on R13, but that doesn't help me now.) 

    But incredulity aside, I still need to have a reconciliation for AP monthly, and my Auditors are also asking for it for end Dec 2017. 

    I have spent hours (probably close to 20 hours now) trying to complete a roll-forward from implementation on Nov 1 2017 through year-end Dec 31 2017, but I'm not having much success.

    So, how do I come up with a detailed list of what makes up my Balance Sheet balance from the end of December 2017?

    Beth

     

    Comment

     

    • Balakrishna Chaturvedula

      Hi Beth,

      Hope you are on R12. We have two reports available in Oracle.

      1. Payables Trial Balance – This provides unpaid invoices balance by supplier and invoice. This can be run by parameter “Liability Account As of Date”.
      1. Payables Invoice Aging Report – This provides list all unpaid invoices with aging periods. This cannot be run for a given date. If you run it today, you would miss invoices, created in 2017 but paid in 2018.

      So, I would advise to run Trial balance and then play with excel to generate aging column. The report format is also not that great to play with. If you have huge volume of data, then I would suggest creating an OTBI report.

      Thanks, Bala.

    • Beth Bleijie

      Thank you for your response, Bala.

      The Payables Trial Balance report only gives me a total, please see attached.

      I would expect/prefer to see a listing of payables by Supplier (by invoice as well, ideally, but by Supplier at a minimum).

      Beth

      • Alexey Shtrakhov

        Hi Beth,

        There are 4 different seeded templates on "Payables Trial Balance" available. There is also available by supplier.

        You can select those templates either during report submission or when you do republishing.
        Please see some screenshots attached..

        Also it looks like in R13 there is coming following report: Supplier Balance Aging Report
        -------------------------------------------------------------------------------------------------------------------------------
        You can now generate an aging report on a suppliers balance based on a specific date. The Supplier Balance Aging report only considers the invoices that are accounted in Payables and transferred to the General Ledger. These balances will reconcile with the trial balance report.
        --------------------------------------------------------------------------------------------------------------------------------

         

        Alexey

    • Sameh Rady Soliman

      As of aging for AP is available in R13

      if you on lower releases you can create a BI report using the below query

      let me know if that helps

       
      select 
      PV.VENDOR_NAME,PVS.VENDOR_SITE_CODE 
      ,API.INVOICE_NUM 
      ,DUE_DAYS 
      ,case when INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) <=DUE_DAYS then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end in_terms 
      ,case when INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) >DUE_DAYS then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end out_terms 
      ,case when (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) <=:P_bucket_day 
      and (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date)>due_days))then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end bucket1 
      ,case when (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) between 
      1*:P_bucket_day+1 and 2*:P_bucket_day 
      and (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date)>due_days)) then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end bucket2 
      ,case when (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) between 
      2*:P_bucket_day+1 and 3*:P_bucket_day 
      and (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date)>due_days))then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end bucket3 
      ,case when (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) between 
      3*:P_bucket_day+1 and 4*:P_bucket_day 
      and (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date)>due_days))then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end bucket4 
      ,case when (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date) >4*:P_bucket_day 
      and (INVOICE_TYPE_LOOKUP_CODE!='PREPAYMENT' and 
      to_date(:P_ason,'dd-mon-yy')-to_date(api.invoice_date)>due_days))then 
      (decode(api.INVOICE_CURRENCY_CODE,'INR',nvl(api.exchange_rate,1),api.exchange_rate)*ps.AMOUNT_REMAINING) 
      else 0 end bucket5 
      ,round(decode(api.INVOICE_TYPE_LOOKUP_CODE,'PREPAYMENT',AP_PREPAY_UTILS_PKG.get_prepay_amount_remaining(api.invoice_id),0)*nvl(api.exchange_rate,1),2) 
      unapp 
      ,(select trunc(c.RECEIPT_DATE) from RCV_VRC_TXS_V a,AP_INVOICE_LINES_all b 
      ,RCV_VRC_HDS_V c where 
      a.SHIPMENT_LINE_ID=b.RCV_SHIPMENT_LINE_ID 
      and a.SHIPMENT_HEADER_ID=c.SHIPMENT_HEADER_ID 
      and b.INVOICE_ID=api.invoice_id 
      and rownum=1) recptdt 
      FROM 
      ap_payment_schedules_all ps 
      ,ap_invoices_V api 
      ,po_vendors pv 
      ,po_vendor_sites_all pvs 
      --,AP_TERMS_LINES ATL 
      ,(select distinct TERM_ID,max(DUE_DAYS) DUE_DAYS from AP_TERMS_LINES group 
      by TERM_ID ) ATL 
      where ps.invoice_id=api.invoice_id 
      --and trunc(api.invoice_date)<=to_date(:P_ASON) 
      and trunc(api.gl_date)<=to_date(:P_ASON) 
      AND api.cancelled_date IS NULL 
      and api.ORG_ID=:P_ORGID 
      and 
      decode(api.INVOICE_TYPE_LOOKUP_CODE,'PREPAYMENT',AP_PREPAY_UTILS_PKG.get_prepay_amount_remaining(api.invoice_id),(NVL(api.invoice_amount,0) 
      - NVL(api.amount_paid,0)))*nvl(api.exchange_rate,1) <> 0 
      --AND nvl(api.payment_status_flag,'N') in ('N','P') 
      --AND ps.amount_remaining!= 0 
      and api.VENDOR_ID=pv.VENDOR_ID 
      and api.VENDOR_ID=nvl(:P_vendorid,api.VENDOR_ID) 
      and api.VENDOR_SITE_ID=pvs.VENDOR_SITE_ID 
      AND API.TERMS_ID=ATL.TERM_ID 
      and api.APPROVAL_STATUS_LOOKUP_CODE<>'NEVER APPROVED' 
      order by VENDOR_NAME

       

      • Jo Bates

        Hi Sameh,

        Thanks for sharing this query - we have tried to use it and my technical colleague has told me that the views RCV_VRC_TXS_V, RCV_VRC_HDS_V & AP_INVOICES_V do not exist, nor are they found in the Oracle Enterprise Repository. 

        What do you suggest?  It would be really useful for us to be able to get this information.

        Many thanks,

        Jo

    • Becky Alvarez

      Have you looked at the Shared Reports section on Customer Connect to see if you could find something.  If not, please share what you do find as we are always looking for good reports to share.

      https://cloudcustomerconnect.oracle.com/pages/17668b0b6c

    • Srikanth Kura

      Hi,

      Please try below.

      SELECT

      DISTINCT AIA.INVOICE_NUM,
      TO_CHAR(APSA.DUE_DATE, 'MM-DD-YYYY') AS DUE_DATE,
      --TO_CHAR(AIA.INVOICE_DATE, 'MM-DD-YYYY') AS DUE_DATE2,

      AU.PAYMENT_AMOUNT AS INVOICE_PAYMENT_TOTAL,
      AU.INVOICE_AMOUNT AS FULL_INVOICE_AMOUNT,
       
      TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) AS DUE_DAYS,
      AIA.PARTY_ID,
      AU.INVOICE_VARIANCE AS REMAINING_AMOUNT,
      (AU.INVOICE_VARIANCE/(CASE AU.INVOICE_AMOUNT WHEN 0 THEN 1 ELSE AU.INVOICE_AMOUNT END))*100 AS PERCENTAGE_UPAID,

      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) <= 0 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_0,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) BETWEEN 1 and 30 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_1,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) BETWEEN 31 and 60 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_2,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) BETWEEN 61 and 90 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_3,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) > 90 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_4,
      AIA.VENDOR_SITE_ID,

      CASE AP_INVOICES_PKG.GET_POSTING_STATUS(AIA.INVOICE_ID) WHEN 'Y' THEN 'Posted' WHEN 'P' THEN 'Posted' ELSE 'Not Posted' END AS POSTED_FLAG,
      CASE WHEN (CASE AP_INVOICES_PKG.GET_POSTING_STATUS(AIA.INVOICE_ID) WHEN 'Y' THEN 'Posted' WHEN 'P' THEN 'Posted' ELSE 'Not Posted' END = 'Posted') THEN to_char(AIA.GL_DATE, 'MM-DD-YYYY') ELSE NULL END AS POSTED_DATE,


      TO_CHAR(AIA.INVOICE_DATE, 'MM-DD-YYYY') AS INVOICE_DATE,
      TO_CHAR(AIA.CREATION_DATE, 'MM-DD-YYYY') AS CREATION_DATE,

      --HZ.PARTY_ID,
      HZ.PARTY_NAME AS SUPPLIER_NAME,
      HZ.PARTY_NUMBER AS SUPPLIER_NUMBER,
      POZ.VENDOR_TYPE_LOOKUP_CODE AS SUPPLIER_TYPE


      FROM


      (SELECT
      AP_VARIANCE.INVOICE_ID,
      SUM(AP_VARIANCE.PAYMENT_AMOUNT) PAYMENT_AMOUNT,
      SUM(AP_VARIANCE.INVOICE_AMOUNT) INVOICE_AMOUNT,
      (SUM(AP_VARIANCE.INVOICE_AMOUNT)-SUM(AP_VARIANCE.PAYMENT_AMOUNT)) INVOICE_VARIANCE
      FROM
      (SELECT

      AIPA.INVOICE_ID,
      SUM(NVL(AIPA.AMOUNT,0)) PAYMENT_AMOUNT,
      0.00 INVOICE_AMOUNT

      FROM

      AP_INVOICE_PAYMENTS_ALL AIPA
      WHERE

      AIPA.POSTED_FLAG = 'Y'
      AND AIPA.ACCOUNTING_DATE <= TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY'))

      GROUP BY
      AIPA.INVOICE_ID

      UNION ALL

      SELECT

      AIDA.INVOICE_ID,
      0.00 PAYMENT_AMOUNT,
      SUM(NVL(AIDA.AMOUNT,0)) INVOICE_AMOUNT

      FROM

      AP_INVOICE_DISTRIBUTIONS_ALL AIDA
      WHERE

      AIDA.POSTED_FLAG = 'Y'
      AND AIDA.ACCOUNTING_DATE <= TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY'))

      GROUP BY
      AIDA.INVOICE_ID
      ) AP_VARIANCE

      GROUP BY
      AP_VARIANCE.INVOICE_ID

      HAVING (SUM(AP_VARIANCE.INVOICE_AMOUNT)-SUM(AP_VARIANCE.PAYMENT_AMOUNT)) <>0.00

      ) AU,
      AP_INVOICES_ALL AIA,
      AP_PAYMENT_SCHEDULES_ALL APSA,
      AP_INVOICE_DISTRIBUTIONS_ALL AIDA,
      HZ_PARTIES HZ,
      POZ_SUPPLIERS POZ,

      GL_LEDGERS gll,
      GL_JE_HEADERS glhdr,
      GL_PERIODS glper

      WHERE AU.INVOICE_ID = AIA.INVOICE_ID
      AND AU.INVOICE_ID = APSA.INVOICE_ID
      AND AU.INVOICE_ID = AIDA.INVOICE_ID
      AND AIA.PARTY_ID = HZ.PARTY_ID
      AND HZ.PARTY_ID = POZ.PARTY_ID

      AND AIA.SET_OF_BOOKS_ID = GLL.LEDGER_ID
      AND GLL.LEDGER_ID = GLHDR.LEDGER_ID
      AND GLHDR.PERIOD_NAME = GLPER.PERIOD_NAME
      AND GLL.PERIOD_SET_NAME = GLPER.PERIOD_SET_NAME

      AND HZ.PARTY_NAME IN (:P_PARTY_NAME)
      AND POZ.VENDOR_TYPE_LOOKUP_CODE IN (:P_VENDOR_TYPE_LOOKUP_CODE)

      ORDER BY PARTY_NAME ASC

       

       

      thanks,

      Srikanth

    • Srikanth Kura

      Hi

      Sorry, I have copied the wrong one. please use the below one.

      SELECT

      DISTINCT AIA.INVOICE_NUM,
      TO_CHAR(APSA.DUE_DATE, 'MM-DD-YYYY') AS DUE_DATE,
      --TO_CHAR(AIA.INVOICE_DATE, 'MM-DD-YYYY') AS DUE_DATE2,

      AU.PAYMENT_AMOUNT AS INVOICE_PAYMENT_TOTAL,
      AU.INVOICE_AMOUNT AS FULL_INVOICE_AMOUNT,
       
      TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) AS DUE_DAYS,
      AIA.PARTY_ID,
      AU.INVOICE_VARIANCE AS REMAINING_AMOUNT,
      (AU.INVOICE_VARIANCE/(CASE AU.INVOICE_AMOUNT WHEN 0 THEN 1 ELSE AU.INVOICE_AMOUNT END))*100 AS PERCENTAGE_UPAID,

      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) <= 0 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_0,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) BETWEEN 1 and 30 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_1,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) BETWEEN 31 and 60 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_2,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) BETWEEN 61 and 90 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_3,
      CASE WHEN TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY')) - TRUNC(TO_DATE(INVOICE_DATE)) > 90 THEN AU.INVOICE_VARIANCE ELSE 0 END AS MONTH_4,
      AIA.VENDOR_SITE_ID,

      CASE AP_INVOICES_PKG.GET_POSTING_STATUS(AIA.INVOICE_ID) WHEN 'Y' THEN 'Posted' WHEN 'P' THEN 'Posted' ELSE 'Not Posted' END AS POSTED_FLAG,
      CASE WHEN (CASE AP_INVOICES_PKG.GET_POSTING_STATUS(AIA.INVOICE_ID) WHEN 'Y' THEN 'Posted' WHEN 'P' THEN 'Posted' ELSE 'Not Posted' END = 'Posted') THEN to_char(AIA.GL_DATE, 'MM-DD-YYYY') ELSE NULL END AS POSTED_DATE,


      TO_CHAR(AIA.INVOICE_DATE, 'MM-DD-YYYY') AS INVOICE_DATE,
      TO_CHAR(AIA.CREATION_DATE, 'MM-DD-YYYY') AS CREATION_DATE,

      --HZ.PARTY_ID,
      HZ.PARTY_NAME AS SUPPLIER_NAME,
      HZ.PARTY_NUMBER AS SUPPLIER_NUMBER,
      POZ.VENDOR_TYPE_LOOKUP_CODE AS SUPPLIER_TYPE


      FROM


      (SELECT
      AP_VARIANCE.INVOICE_ID,
      SUM(AP_VARIANCE.PAYMENT_AMOUNT) PAYMENT_AMOUNT,
      SUM(AP_VARIANCE.INVOICE_AMOUNT) INVOICE_AMOUNT,
      (SUM(AP_VARIANCE.INVOICE_AMOUNT)-SUM(AP_VARIANCE.PAYMENT_AMOUNT)) INVOICE_VARIANCE
      FROM
      (SELECT

      AIPA.INVOICE_ID,
      SUM(NVL(AIPA.AMOUNT,0)) PAYMENT_AMOUNT,
      0.00 INVOICE_AMOUNT

      FROM

      AP_INVOICE_PAYMENTS_ALL AIPA
      WHERE

      AIPA.POSTED_FLAG = 'Y'
      AND AIPA.ACCOUNTING_DATE <= TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY'))

      GROUP BY
      AIPA.INVOICE_ID

      UNION ALL

      SELECT

      AIDA.INVOICE_ID,
      0.00 PAYMENT_AMOUNT,
      SUM(NVL(AIDA.AMOUNT,0)) INVOICE_AMOUNT

      FROM

      AP_INVOICE_DISTRIBUTIONS_ALL AIDA
      WHERE

      AIDA.POSTED_FLAG = 'Y'
      AND AIDA.ACCOUNTING_DATE <= TRUNC(TO_DATE(TO_CHAR(:P_AS_OF_DATE, 'MM-DD-YYYY'), 'MM-DD-YYYY'))

      GROUP BY
      AIDA.INVOICE_ID
      ) AP_VARIANCE

      GROUP BY
      AP_VARIANCE.INVOICE_ID

      HAVING (SUM(AP_VARIANCE.INVOICE_AMOUNT)-SUM(AP_VARIANCE.PAYMENT_AMOUNT)) <>0.00

      ) AU,
      AP_INVOICES_ALL AIA,
      AP_PAYMENT_SCHEDULES_ALL APSA,
      AP_INVOICE_DISTRIBUTIONS_ALL AIDA,
      HZ_PARTIES HZ,
      POZ_SUPPLIERS POZ,

      GL_LEDGERS gll,
      GL_JE_HEADERS glhdr,
      GL_PERIODS glper

      WHERE AU.INVOICE_ID = AIA.INVOICE_ID
      AND AU.INVOICE_ID = APSA.INVOICE_ID
      AND AU.INVOICE_ID = AIDA.INVOICE_ID
      AND AIA.PARTY_ID = HZ.PARTY_ID
      AND HZ.PARTY_ID = POZ.PARTY_ID

      AND AIA.SET_OF_BOOKS_ID = GLL.LEDGER_ID
      AND GLL.LEDGER_ID = GLHDR.LEDGER_ID
      AND GLHDR.PERIOD_NAME = GLPER.PERIOD_NAME
      AND GLL.PERIOD_SET_NAME = GLPER.PERIOD_SET_NAME

      AND HZ.PARTY_NAME IN (:P_PARTY_NAME)
      AND POZ.VENDOR_TYPE_LOOKUP_CODE IN (:P_VENDOR_TYPE_LOOKUP_CODE)

      ORDER BY PARTY_NAME ASC

       

      Thanks,

      Srikanth

    • Marybeth Snodgrass

      @ Beth:

      I find myself muttering to myself, "We certainly can't be the first Oracle user to come across this issue!" on a daily basis. 

      • Beth Bleijie

        Marybeth, I say that ALL the time.  We've been on Oracle for about 15 months, and we just can't believe what a fiasco it is.

        I'm interested in going to an Oracle conference, but worry that it'll be more of an Oracle-love-fest, or wow-look-at-new-stuff-Oracle-is-doing, when I really need seminars where I can learn, even some basics, and where I can be involved in Q&A and grill successful users for information.

        (And I have to ask, Marybeth, any chance you're related to a Mayrlou Snodgrass who would be in her mid-50's, grew up in the SF Bay Area?  If so, we were in Girl Scouts together, and if not it's amazing that I have met a Marylou AND a Marybeth Snodgrass in my life . . .great names)

         

    • Becky Alvarez

      If you want to go to a conference where you can learn and talk the real talk with real users and hear their good and bad experiences, Collaborate is the place for you as well as nay local/regional OAUG (Oracle Applications User Group) events.  I don't know how Cloud Focused it is but if I were you I would look into it.  It is run by users for users and they have sessions run by users and partners discussing the how to's and real experiences and Oracle is not allowed to participate unless specifically invited so not anything like OpenWorld which is completely sponsored and run by Oracle.  It is by not means an Oracle-love-fest and it not a wow-look-at new-stuff-Oracle-is-doing although there is some of that because you do want to be informed of what new features are available and how they work but since it is user driven it is more informative than an advertisement. 

      But in I do have to say in Oracle's defense, it is not all bad and there is a lot of good features and functionality in Cloud Financials.  If you have a good implementation and an understanding of what reports you need and someone who understands how to write them you can get what you need out of the system.  We are always trying to improve based on your input.  For example we just released the ability to drill into invoices and if you have the security you can edit the invoice right then and there including releasing holds, updating installments, etc.  We also included the ability to drill down into payment information as well and if you have security you can void the payment, etc.

      I hope that helps and I do understand your point as well.

      • Marybeth Snodgrass

        Very helpful info, especially about the regional Oracle Apps User Groups! I had no idea! Thanks!!

      • Beth Bleijie

        Thanks, Becky.

        I'll look into Collaborate, I didn't realize it was not Oracle-run.  That might be a great place to start for us.

        We have discovered that one of our biggest issues is reporting, and we have only one person who can pull data because he has programming experience, but I feel like it shouldn't be that hard. 

        We're working through our problems internally, and with Oracle, but at this point we have yet to see the joy in Oracle. 

        But we're working on it, and your recommendation to attend Collaborate might be a good next step.

        I appreciate all your posts, it is nice to be heard, and be helped.  And we need help.  smiley

        • Glen Ryen

          Hi Becky,

          I know this is a late reply, but have you looked into OTBI and/or Smart View?  Those tools are available for end user ad hoc reporting (against transactions and GL balances, respectively) without the need for programming experience.  That may not be something your implementation partner trained your users on, but getting up to speed on those will address a lot of reporting challenges (from what I've seen).

          Hope that helps,

          Glen

    • Becky Alvarez

      My pleasure.  Just make sure that Collaborate has something for Cloud.  In the past (5 years ago)  they were more EBS, PeopleSoft and JD Edwards focused which is on-premise and I am hoping that with more Cloud users they have more Cloud Focused tracks today than they did then.  If not, let me know and I will see what I can find out for you what else might be available to you for user groups as that will be the best place for you to interact with other users and find out how others are using the system.

    • Wendy Ware

      Interesting discussion.  Of course, THIS forum has been a sanity-saver for me more than once!  Wendy