Comments

  • Neil Peacock

    Hi,

    Thanks for your reply, I can confirm the primary assignments have not changed for these employees for the last 3-4 months, however they do have old working relationships in this entity they are now linked to. However these relationships were terminated 3-4 months ago, with the new relationships being made primary.

    I am just worried that they seem to be pulling through the first dated work relationship even if it is terminated, I am currently trying to see if it is only these colleagues or if it is wider spread on other business units where the employees have old working relationships too.

    Neil

  • Neil Peacock

    We agree that we would like the lines to be auto expanded when you go in to edit an invoice. I can understand the status summary being moved to give more space, however I am not sure why the lines area would be minimized as default.

     

  • Neil Peacock

    Hi Evan,

    I would suggest this could be a OTBI report that the procurement team run then distribute. This way the role security won't be affected and you could get all the information you need. We currently have a report that is sent out to procurement once a week through an Agent that they then distribute to all the HoFs etc in the organisation showing all open POs and Reqs.

    I believe something like this, running on a daily basis could work for you.

    Kindest regards

    Neil

  • Neil Peacock

    Hi Evan,

    Would it be worth pulling the information from a report which can then be distributed to your AP Team? This would allow the team to view PO and PO details without burning your licenses?

    Neil

  • Neil Peacock

    Hi Thanks for that Brendon.

    I have found the answer to get users names through Doc ID 1983485.1 using Manage Data Role and Security Profiles to see Names. however we are also unable to view tax from the subject area, so this gave me a couple of extra roles and a duty to try out, but we are still unable to see tax unless the user has BI Admin access. Therefore i believe it will be a role issue as the reporting users can see distributions, locations etc.

    I ripped apart the SQL in the background to ensure that there was no permission issues relating to procurement agents themselves, and there is no added security check, so then i built queries checking each join using the subject area and they could see everything up to the tax which is stored on PO_DISTRIBUTIONS_ALL. The users can see distribution numbers etc so there must be an added something to give them tax access relating to procurement and the Purchase Order Transaction Analysis Duty unfortunately did not make any difference.

    Regards

    Neil

     

  • Neil Peacock

    Hi Mizuru,

    Do you mean the latest patch bundle or the latest version of the document?

    Neil

  • Neil Peacock

    Hi Arun,

    The limitation is not with Excel itself, it is with the export from Oracle being configured to have a maximum row count. These could be changed in the config, however I have been advised on an SR that this is very rare due to the fact that it will get overwritten with patches/updates etc

    Thanks

    Neil

  • Neil Peacock

    Your welcome, glad I could help. We had this issue in another Oracle system when exporting and thankfully it holds true here too.

  • Neil Peacock

    Hi Aaron,

    Our analysis works with is null for this report, however it has been created through a data model. Can I ask what item you are performing the is null on? We have it on  "IBY_EXT_BANK_ACCOUNTS"."BANK_ACCOUNT_NUM_ELECTRONIC"

    However without the SQL it is hard to know exactly and the best avenue might be to make a ticket.

    Neil

  • Neil Peacock

    Hi Robin,

    If you export the report as a Data - CSV file, you will have a higher limit of rows. I believe this is 65,000. However this method can lose some formatting and will be exported in the order you have the data in the criteria tab, rather than in the results tab. So you might have to make your criteria match your results order and import into excel from text to continue to use any vlookups to older documents.

    This method will allow you to analsyse up to 65,000 rows on your preexisting report.

    Neil

     

     

  • Neil Peacock

    Hi Chris,

    Thanks for this reply, I had been told by Oracle support that the settings can't be changed but the export of CSV through an agent should use the CSV limit and not be cut off at a lower limit. However I believe your answer is correct.

    Do you know if there is any plans to match agent limits to the data type they are exporting or is this not in the pipeline?

    Neil

  • Neil Peacock

    Hi,

    If anybody is struggling to get the cross subject analysis example 1: Invoice, Payment, Hold, and Installment to work, add in Hold Count as a value from Invoice Hold Details in the Payables Invoices - Holds Real Time. This was covered in the referenced document :Fusion Applications OTBI: Guidelines for creating cross subject area analyses in Oracle Transactional BI (OTBI) (Doc ID 1567672.1). However I assumed that the white paper would have followed the guidance from the supporting document in its examples.

    Thanks

    Neil

     

     

  • Neil Peacock

    Hi Andy,

    This works great once you remove the ledger filter.

  • Neil Peacock

    This is quite useful, I wish we had this when we started out reporting.

    The cross subject areas analysis does not work for the first example but it is a good starting point, thanks for sharing it.

  • Neil Peacock

    I go between Oracles SQL Developer and Notepad++ however I have not managed to get the developer to link to the system. The format option works well on SQL Developer to restructure the text. This uses colours for key words and highlights a companion bracket when you select it.