I'm handling a case for a customer regarding the window 'Connectivity Outbox' in Apps 08Load a Shipment from the 'Shipment' Window. RMB and 'send dispatch advice' Open the latest message from 'Connectivity Outbox' Get Lines in the bottom from the 'Grid'There are numerous columns named C00, C01,… C99, N00,….N99, D00… etc. My question is that, how do I get some information regarding these columns? What are they, how the information is fetched? What information is shown by each column? I'm interested in column C91 to be precise. PS: The Page Help was not clear about this.
Can someone explain why there are black dots in the navigator items?
I faced this issue during a technical investigation. There was an error message prompting in the application. "Invoice.ACCERROR1: Error (The Voucher Row object already exists.) occurred while booking Invoice CN xxxxxx" After copying the PLSQL Details, pasted it in the Test Window and ran it. The error message came as same as shown in the app. While debugging there was a requirement of inserting traces using Dbms_output. The packages that I inserted were Voucher_Row_API, INVOICE_API and Voucher_Util_Pub_API. The traces were inserted and compiled without any issues. They worked fine for a while. But in the middle of the investigation, the error message changed to "Invoice.ACCERROR1: Error (could not find program unit being called) occurred while booking Invoice CN xxxxxx." As you can see the text inside the bracket changed from ' The Voucher Row object already exists' to 'could not find program unit being called'. This also changes the error stack. Why is this happening and is there a wa
Anyone know what this code segment does? :: If no file name is provided, start TestARest in interactive mode.IF "%~1" == "" ( SET FILE_TO_READ=) ELSE ( SET FILE_TO_READ=FileToRead="%~1")
I came across a case where a simple search in Supplier Schedule Line takes around 1 hour to return results.We’ve investigated and narrowed down that the condition that gives the biggest performance hit is the between condition applied on ‘Created’ field.However, further investigation showed that the supp_sched_line_tab had more than 40 million records. So, the performance hit is self-explanatory.40 million is a way too big of a number to exist in a single table. My question is, is there a procedure to clean up older / completed Supplier Schedule Lines in apps 8? If there is, where can I find more information on that?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
