Order Entry Interface table error handling through Form after Orderimport

Hi Gurus,
We are on Oracle Apps 11.0.3.
I'm just curious to know that is there any form available to correct error records in SO_HEADERS_INTERFACE, SO_LINES_INTERFACE, SO_LINE_DETAILS_INTERFACE, SO_PRICE_ADJUSTMENTS_INTERFACE, SO_SALES_CREDITS_INTERFACE, SO_SERVICE_DETAILS_INTERFACE, SO_LINE_ATTRIBUTES_INTERFACE, SO_HEADER_ATTRIBUTES_INTERFACE tables after running orderimport.
Most thread says that set REQUEST_ID, ERROR_FLAG and INTERFACE_STATUS columns to NULL in each interface tables. Is there any oracle standard form available to accomplish this in Oracle Apps 11.0.3 or 11i?
Thanks
-Manish

Hi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus

Similar Messages

OWB Error handling through error tables

I have a mapping, which i want to implement error handling through error table, the table is created (error) and i have supplied it in the error table propertis in the target table. But i have tried testing if this is working by changing the data type of one column in my target database, but the whole mapping is failing to run with no error rerded in the error table. And i tried testing the this through sql and suprisingly the errors are being captured. How do i get the whole mapping to run and record the errors if any in the error table without it failing.

When you say 'the whole mapping is failing to run' what do you mean? Can you deploy the mapping? If not what is the error? When you run the mapping what happens?
If you look at the DML statement (the INSERT, MERGE or whatever) generated by OWB does it include the LOG ERRORS INTO statement in it?
There is a blog post below for OWB 11gR2;
http://blogs.oracle.com/warehousebuilder/entry/owb_11gr2_dml_error_logging
And an older one here which was based on OWB 10gR2
http://blogs.oracle.com/warehousebuilder/entry/set_based_errors_dml_error_log
Cheers
David

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

Error Handling in Forms

Dear all,
we are using oracle developer suite 10g r2 with oracle database 10g r2 against windows server 2003.
Error handling is a very big issue.
i try to do the following, just correct me, or make the trigger more efficient.
i face unexpected messages, like a message two time displayed, sometime important message never displayed.
i just set the :system.message_level =20 in the when-new-form-instance trigger.
and create on-error trigger like below
declare
errcode number:=error_code;dbmserrcode number;dbmserrtext varchar2(200);
formtxt varchar2(200);
errtype varchar2(3);
begin
--------- user defined database exceptions errors raised by --RAISE_APPLICATION_ERROR
IF DBMS_ERROR_CODE in (-20738,.......) then
raise form_trigger_failure;
end if;
if error_code=50017 then
message('duration must be between 0 and 23');message(' ',no_acknowledge);
raise form_trigger_fialure;
elsif
error_code=40202 then
clear_message;
message('please provide the required fields.');message(' ',no_acknowledge);
raise form_trigger_fialure;
elsif error_code=50022 then
clear_message;
message('time must be in the correct format.');message(' ',no_acknowledge);
raise form_trigger_fialure;
end if;
if error_code in (40509,40508) then
dbmserrcode:=dbms_error_code; dbmserrtext:=dbms_error_text;
if dbmserrcode=-1438 then
clear_message;
message('your number is too large.try again.');message(' ',no_acknowledge);
raise form_trigger_fialure;
elsif dbmserrcode=-1400 then
clear_message;
message('your forgot to provide a value.try again.');message(' ',no_acknowledge);
raise form_trigger_fialure;
elsif dbmserrcode=-2291 then
clear_message;
message('header is not found for this insertion.');message(' ',no_acknowledge);
raise form_trigger_fialure;
elsif dbmserrcode=-1 then
clear_message;
message('record already exists');message(' ',no_acknowledge);
raise form_trigger_fialure;
else
clear_message;
message(error_code||' : '||error_text);message(' ',no_acknowledge);
raise form_trigger_fialure;
end if;
else
clear_message;
message(error_code||' : '||error_text);message(' ',no_acknowledge);
raise form_trigger_fialure;
end if;
exception
when others then
if dbms_error_code=-20738 then
clear_message;
message('Error: absent or later record errror from the database trigger.);
raise form_trigger_failure;
elsif .....
esle
clear_message;
message(error_code||' : '||error_text);message(' ',no_acknowledge);
raise form_trigger_fialure;
end if;
end;any suggession?
Regards

i must come with a plsql code which handle every error and suppress unnecessary messages.Good luck with that. No matter how well thought out or planned, you're not going to be able to take all scenarios into account. The design of an exception handler takes time to address all possible scenarios you want handled and even then, you're not likely to handle every situation in the beginning.
could we implement the oracle ebusiness error handling procedures here in our application?if yes, then where could we find that procedure?>
I've dug through that code and it is not a thorough as you think it is. It handles specific situations and then defaults the rest. It is a good model for your own exception handler, however. That is what I used it for. :) I don't recall which library it is in, but I'll look around and if I find it, I'll post it.
I agree with Andreas's comment...
Simply remove your ON-ERROR-trigger, then you have a default. That's nothing better or worse than what apex has.I'm not too familiar with Apex; I've worked with it, but it's been a little while. Even with Apex, you're going to have to develop a customized Exception Handler so more intuitive or application specific messages are displayed in response to an exception.
As to Andreas's comment...
For your own error-handling... The "simplest" way in my eyes is create your own error-table where you have appropiate columns for the error-code and the error-type (FRM,ORA,Whatever), then in your ON-ERROR-trigger read the appropiate record from that table and show the error. You could also have a flag in your table which decides what to do with a specific error (Show as Message, Show as Alert, Don't show at all) and react accordingly.This is exactly what we implemented in our application. We created a set of tables that contain all of the Oracle Runtime errors and their attributes (Error Type, Severity Level, etc). Then we wrote a standard On-Error trigger that is subclassed to all of our forms that calls a Library "On_Error" package. This package evaluates the exception raised, compares it to the database entry for the error and then displays an appropriate message depending on the Severity Level, Error Type (ORA or FRM) and Message Type (Informational, Error, Caution) and we display the message in either the Status Bar, Note Alert, Caution Alert or Stop Alert or it is supressed. If an error is not found in the table, then it is displayed in a Stop Alert as an "Unhandled Exception." The second table I mentioned contains all of the messages used by our application and is cross referenced with the table that contains the Oracle messages. By simply assigned one of our messages to an Oracle message - our package will display our message instead of the default Oracle Message. Yes, this took sometime to build and test and once implemented, we spent another couple of months perfecting it, but now it is pretty solid and we haven't had to modify it in over a year.
While this level of complexity may be overkill for your application, it does offer the greatest flexibility in the long-run. Also, if your application must support multiple languages, having all of your messages in a table make internationalization extremely easy. :)
The point of all this, is that no matter which system you use (Forms, Apex, or Java) you will still need to invest some time into designing an Excpeiton Handling method for your application and then implement it accross the application. This is not something you can develop in a short period of time and it will not be perfect in the beginning. However, in the long-run, you will be happy you spent the time up-front to build a flexible and robust Exception Handling system.
Craig...

How to import order from Interface table using Api Order Import

Hi All
I am using oracle EBus R12.
I was working in Data migration in Order management.
I have manually entered data in Interface table ie (oe_header_iface_all) and (oe_lines_iface_all)
And i have given the order_source_id as 2 and order_source as COPY.
And after that i ran the concurrent program with parameter as COPY but the concurrent program does'nt picks the order in the interface.
Can any one please tell the steps in OM.
Thanks & Regards
Srikkanth.M

Hi;
please check:
http://sureshvaishya.blogspot.com/2009/04/order-import-using-api.html
Also i suggest see:
http://irep.oracle.com/index.html
API User Notes - HTML Format [ID 236937.1]
R12.0.[3-4] : Oracle Install Base Api / Open Interface Setup Test [ID 427566.1]
Oracle Trading Community Architecture API User Notes, June 2003 [ID 241320.1]
Technical Uses of Customer Interface and TCA-API [ID 269121.1]
http://www.google.com.tr/#hl=tr&source=hp&q=Api+Order+Import+&oq=Api+Order+Import+&aq=f&aqi=&aql=&gs_sm=e&gs_upl=469l469l0l1l1l0l0l0l0l0l0ll0&fp=87c57485fd170fd2&biw=1259&bih=793
Regard
Helios

Export pending sale orders to Interface table

Hi,
I need to export all pending sale order lines to interface table and should be import from interface table as a new orders. Is there is any possibility ?
regards
Ravi

so you want all SO lines which are in pending status as new SO line in Entered or Booked status? Why?
Have you tried using Copy Feature?

Interface for error handling.

Hi experts,
i have to design an interface for exception handling .there is a client system ( mainframe) linked to
sap system through webspher (ibm) .whenever ERN from the client system comes to sap system .
there will be 2 types .
1. the ERN is valid one.
2. the ERN is invalid one .
for the invalid ERN we have to inform the client system about the exception. this is through IDOC only ..
can any one sugesst the good techincal design.
regards
SV

please explain ERN , also what EDI transaction comes in and what idoc message/ idoc type is used?
Also look at EDI 864 which is a text message.
But give me more details.
BTW Welcome to SDN.
Message was edited by:
Sandeep Bhavsar

Booking Order with Interface Tables

Hello, I am trying to book an order using the interface tables. RIght now, I load the header into the OE_HEADERS_IFACE_ALL table, then load the operation "BOOK_ORDER" into the OE_ACTIONS_IFACE_ALL table. I see that the action is tied to the header, b/c it shows under the actions button for that header. Nothing is happening, though. I have looked at the Oracle documentation, and notes, that have told me to use this method instead of the "booked_flag" on the header (I tried that, too :P ). Please tell me if there are some configuration issues, or if there is anything that I may be doing wrong when importing it.
Thanks in advance,
Joe

What is your method of loading the Interface Tables ??? Can you please elaborate? I have made use of ODI to build dimension into Planning and using ODI we can control the sequence in whatever way we want.
--XAT

Error-handling in form routines to be called from maintenance view

hello,
i have created a table maint. dialog. Under 'enviroment->modification->events' you can create form-routines for your own coding.
I have the maint.event '01 - Before saving the data in the database'. Here i do some checks if entered values in some fields are okay or not etc.....
When the users enters 'wrong' data i do a "message e000 with 'text' " So i got a error-message and the user is not able to save the data before changing it.
BUT: i get the right error-message in the status-line, but i got an EMPTY screen, all the fields disapear. I have to go back with enter or the red cancel button. But then i 'fall back' to the selection screen of the maint. view. Thats not very user-friendly.
Any ideas ?

hi,
think you have place your module not correct:
try that: (without event)
PROCESS AFTER INPUT.
LOOP AT EXTRACT.
    FIELD VIM_MARKED MODULE LISTE_MARK_CHECKBOX.
    CHAIN.
      FIELD Y789.
      FIELD Y012.
      MODULE LISTE_UPDATE_LISTE.
    ENDCHAIN.
*begin of insertation
    CHAIN.
      FIELD Y123.
      FIELD Y456.
      module check_field ON CHAIN-input.
    ENDCHAIN.
*end of insertation
ENDLOOP.
Andreas

Customer Coversion Using Interface Table - Error during update

I need to import customers from legacy applicatiion and is planning to use standard customer interface for that. For testing, I am able to create customers with hardcoded values. But while I try to update the same customer record (again using hard coded values), it gives me error and is not generating the error report as well. I am getting the following error during update:
racudc: ORA-20212: Enter valid Billing Fields.
ORA-06512: at "APPS.ADVOAR_CUST
racudc: Error updating customers.
or
racudc: updated 1 partiesracudc: Partyrel 1 parties
racudc: ORA-20210: You have edited one of the following fields, Extended Billi
racudc: Error updating customers.
Also it seems we can not update an address, site_use_code, or PRIMARY_SITE_USE_FLAG using customer interface.
The following is the test record I inserted for updating the customer I created and ran the customer interface:
insert into ra_customers_interface
(ORIG_SYSTEM_CUSTOMER_REF
,INSERT_UPDATE_FLAG
,CUSTOMER_NAME
,CUSTOMER_STATUS
,LAST_UPDATED_BY
,LAST_UPDATE_DATE
,CREATED_BY
,CREATION_DATE
,ORIG_SYSTEM_ADDRESS_REF
,ADDRESS1
,CITY
,COUNTY
,STATE
,POSTAL_CODE
,COUNTRY
,customer_attribute13
values
('APP1-492503' --ORIG_SYSTEM_CUSTOMER_REF
,'U' --INSERT_UPDATE_FLAG
,'Pizza Hut - CDH TEST4' --CUSTOMER_NAME
,'A' --CUSTOMER_STATUS
,-1 --LAST_UPDATED_BY
,sysdate --LAST_UPDATE_DATE
,-1 --CREATED_BY
,sysdate --CREATION_DATE
--,'Y' --PRIMARY_SITE_USE_FLAG
--,'BILL_TO' --SITE_USE_CODE
,'APP1-492503-ADDR1' --ORIG_SYSTEM_ADDRESS_REF
,'1 River Road, Bldg 1' --ADDRESS1
,'SCHENECTADY' --CITY
,'SCHENECTADY' --COUNTY
,'NY' --STATE
,12305 --POSTAL_CODE
,'US' --COUNTRY
,'55'
I am testing this in 11.5.10 env. Any help on this is appreciated.
Thanks,
MK

Convert only the data you need. And the data you need is probably less than you think. For example, other than open invoices (invoices for which money is still owed), you probably don’t need to convert ANY old invoices. You may want to convert data on what was purchased (e.g., event registration, membership, product, etc.) but the actual details (e.g., payment type, payment date) are probably no longer significant.
http://www.e-datapro.net/data_conversion.htm

Idoc Error Handling through workflow

Hi all,
I want to send the Error Notification for a particular person for whom the task orders is assigned in the organization chart.
What all the things I need to do.
I have created the org chart and I have assigned the task to a user under a position.
I have linked the Idoc error event in Tcode SWETYPV .
What all the things I am supposed to do.
Regards
Kumar

Please go to transction WE20, pick the Partner / Idoc that you would like to assign the Org. chart to.
Then you should configure "post processing :permitted agent" Tab with the Organizational unit.
Then double click the process code associated with the Idoc Type and click the button next to the Function Module associated with this process code.
Check IDoc Tab and see if Stanard Event INPUTERROROCCURRED is present in the field called start event.

WSRP Error Handling through Consumer Entitlement

Hi
Is there are way to do entitlements in the Consumer side based on the Availablity of the Producer. Say If the producer is down then a particular book or page in consumer portal needs to be hidden. We can use interceptor for catching the error and displaying a error message on the screen, but how we can hide the page itself through entitlement.
Thanks
Rajesh A.r

Hello Rajesh and Emmanuel,
Emmanuel is correct that you can't usually do what you want in an interceptor- at least not a GetMarkupInterceptor. The problem is the way the portal lifecycle is run in WLP-- a tree of controls is built up, then pruned by entitlements, then the remaining controls are asked to render onto a page. The WSRP getMarkup operation is performed during the last stage of this lifecycle-- during render, when it is already too late to not have a portlet show up. Indeed, when the getMarkup operations are run, it is already too late to issue a redirect, so you wouldn't even be able to set entitlements and then redirect back to the same page.
So the first page view that recognizes that the producer is down is too late to simply not have the portlets appear on the page, but you can make the interceptor take steps so that the next person that tries to view any page with remote portlets on it from that producer just won't see them. In addition, you can make the interceptor provide the markup for the portlet that failed to be retrieved from the remote producer, or some sort of message in its place.
You may want to take a look at the producer disabling functionality built in to WLP:
http://edocs.bea.com/wlp/docs102/javadoc/com/bea/wsrp/consumer/management/producer/ProducerManager.html#disableProducer(java.lang.String,%20java.lang.String,%20javax.servlet.http.HttpServletRequest)
If you used the disableProducer() method in your interceptor when you notice that the producer is not responding, you can tell all portlets coming from a remote producer to not be rendered-- but only for future page renders; again, it is already "too late" for the page that notices the producer is down, at least if the producer being down gets noticed during getMarkup.
If you detect the producer being down during the InitCookie, BlockingInteraction or HandleEvents WSRP operations, these all occur before render, so you would be able to disable the producer, or set entitlements, or even do a page redirect at that point in time. But during the GetMarkup operation, the page is already "committed" and there is no way around the problem at that time.
Kevin

ALE: Error handling through workflow

Hi All,
My requirement is to trigger a workflow to send a mail when ever there is an error in posting an IDOC.
I have created a FM, Business object, Process code and assigned FM & BO to it. created a workflow object and assigned BO object to it. I am getting mails too.
But the problem here is I am getting mails to SAP inbox even the IDOC is posted successfully.
I am setting the value WORKFLOW_RESULT = 99999 when IDOC posting fails.
My requirement is to trigger workflow only when there is an error in posting IDOC.
Please suggest.
Thanks in advance,
Prathap

I think there are standard workflow for your requirement. Please check WE46 transaction code for the task.
Thanks
Arghadip

Error while saving forms after migration to apex 4.0

Hi,
When I am saving a form, I have an error.
I am under tomcat with apex listener.
Etat HTTP 500 - System Unavailable. Please try again later.
type Rapport d'état
message System Unavailable. Please try again later.
description Le serveur a rencontré une erreur interne (System Unavailable. Please try again later.) qui l'a empêché de satisfaire la requête.
Apache Tomcat/6.0.24
Here is the error into the stdout file.
p_instance:4258835777415386
f05: {7a 1a 1a 3a Da Dm 5a 8a 9a Dm 9a 4a (09) Da 10a 5a 10a 4a 9a Da 6a 4a 3a Da Da 1a 8a 1a 2a (09) 1a 3a 0a 5a 2a Da Da 4a Da 4a 6m 7a 3a Dm Da 2a 8a 7a (09) 10a Da 0a Da Da 9a 9a 2a Da 1a 9a 10a (09) Da 7a 0a 5a 3a 4a (09) 3a 0a 4a 3a 6a 6a 0a 2a 1a 1a Da 8a 0a 0a Da 10a }
f04: {7a1a1a3aDa1a5a1a2aDaDm5a8a9aDm8a1a2a2a2a9a4a(09)Da0a5a0a6aDm7a6a0a4a9aDa6aDa0a3a(09)3aDa4a3a0aDa1a6a(09)Da2a1a0a8a1a2a(09)1a3a2aDa1a1a1a0a5a2aDaDa5a1a1a5a2a4aDa4a6m7a0a3m4m(09)6aDa3aDmDa2a8a4aDaDa(09)8aDa7a(09)0aDa0aDaDaDa3a2a5aDa0a9a2aDaDaDaDmDa2a1a0a0a(09)Da7a2a6a1a1aDa0a5a3a4a(09)3a0a4a8a8aDa0a4a3a6a6a1a1aDa(09)6a9a0a2a1a1aDa0a9a(09)8a0a4a8a0a0aDa0a(09)0mDaDaDa6a}
p_page_submission_id:3209856541065050
fhdr:Idc
f03: {0000000000000000}
f02: {12345678910111213141516}
f01: {1000002100000210000021000002100000210000021000002100000210000021000002100000210000021000002100000210000021000002}
fmap:IDC
p_md5_checksum:
p_flow_step_id:27
fcs: {42E10286DF66A3D6FCBA2A011876B96E5C62425BAE66E8D720EA20029CB9C052DC6F492B4B7DF2693EF88FEC14198D865CB7F313AB41E3C3285C05EBE76B3A24F1215443C1321AA29ACD8E11D161B04F6282D72471E8E5773B1DA99405EF7AABEABAC89D0E3AC23DF6CE48D2D5345A8515C222A801C97F5CFAA78B1587497189929920604FB4C2E0892B0776597F2994F96806255CB71F48DB1D0798438AD2621BF2DC831EB5FD9B514672486B5455063BF3F5BE96E14998F81803A50DFCBB944C2293DF9CAAE8E1AD8BE33C01CE98FD19501BF13786AF27FE2734B6C46AD780B48D4EB1AA388701A510D7A101C000C7F1804950FBB1674296FD940BCFFC242C}
p_request:SUBMIT
fcud:U
p_t01:1000002
p_arg_names: {9716035995860003}
p_flow_id:102
p_instance:4258835777415386
f05: {7a 1a 1a 3a Da Dm 5a 8a 9a Dm 9a 4a (09) Da 10a 5a 10a 4a 9a Da 6a 4a 3a Da Da 1a 8a 1a 2a (09) 1a 3a 0a 5a 2a Da Da 4a Da 4a 6m 7a 3a Dm Da 2a 8a 7a (09) 10a Da 0a Da Da 9a 9a 2a Da 1a 9a 10a (09) Da 7a 0a 5a 3a 4a (09) 3a 0a 4a 3a 6a 6a 0a 2a 1a 1a Da 8a 0a 0a Da 10a }
f04: {7a1a1a3aDa1a5a1a2aDaDm5a8a9aDm8a1a2a2a2a9a4a(09)Da0a5a0a6aDm7a6a0a4a9aDa6aDa0a3a(09)3aDa4a3a0aDa1a6a(09)Da2a1a0a8a1a2a(09)1a3a2aDa1a1a1a0a5a2aDaDa5a1a1a5a2a4aDa4a6m7a0a3m4m(09)6aDa3aDmDa2a8a4aDaDa(09)8aDa7a(09)0aDa0aDaDaDa3a2a5aDa0a9a2aDaDaDaDmDa2a1a0a0a(09)Da7a2a6a1a1aDa0a5a3a4a(09)3a0a4a8a8aDa0a4a3a6a6a1a1aDa(09)6a9a0a2a1a1aDa0a9a(09)8a0a4a8a0a0aDa0a(09)0mDaDaDa6a}
p_page_submission_id:3209856541065050
fhdr:Idc
f03: {0000000000000000}
f02: {12345678910111213141516}
f01: {1000002100000210000021000002100000210000021000002100000210000021000002100000210000021000002100000210000021000002}
fmap:IDC
p_md5_checksum:
p_flow_step_id:27
fcs: {42E10286DF66A3D6FCBA2A011876B96E5C62425BAE66E8D720EA20029CB9C052DC6F492B4B7DF2693EF88FEC14198D865CB7F313AB41E3C3285C05EBE76B3A24F1215443C1321AA29ACD8E11D161B04F6282D72471E8E5773B1DA99405EF7AABEABAC89D0E3AC23DF6CE48D2D5345A8515C222A801C97F5CFAA78B1587497189929920604FB4C2E0892B0776597F2994F96806255CB71F48DB1D0798438AD2621BF2DC831EB5FD9B514672486B5455063BF3F5BE96E14998F81803A50DFCBB944C2293DF9CAAE8E1AD8BE33C01CE98FD19501BF13786AF27FE2734B6C46AD780B48D4EB1AA388701A510D7A101C000C7F1804950FBB1674296FD940BCFFC242C}
p_request:SUBMIT
fcud:U
p_t01:1000002
p_arg_names: {9716035995860003}
p_flow_id:102
EXEC FAILED:ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
ORA-06550: line 2, column 2:
PL/SQL: Statement ignored
ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'ACCEPT'
ORA-06550: line 2, column 2:
PL/SQL: Statement ignored
Any Idea?
Many thanks jko

Problem solved.
Better Remove apex 3.2 (export your applications first)
Then do fresh install of apex 4.
And it works
Jko

No Fact table error on every report after upgrading frm11.1.1.5 to 11.1.1.6

All,
All the dashboard reports were working fine on version 11.1.1.5. After upgrading to 11.1.1.6 i am getting below error
I have followed all the In-place upgrade steps and all were finished without any errors.
[2013-03-17T21:44:08.000+00:00] [OracleBIServerComponent] [TRACE:3] [USER-34] [] [ecid: 62a0baeaae7f41bf:-31b079a9:13d6cea7626:-8000-0000000000004616] [tid: 12d8] [requestid: 68fd0001] [sessionid: 68fd0000] [username: Administrator] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
Any help is appreciated
Thanks,

After applying patch to make it 11.1.1.6.6 everything worked. All reports working without any issues.

Order Entry Interface table error handling through Form after Orderimport

Similar Messages

Maybe you are looking for