AXCABMR: initialize procedure raised

Hello all.
I installed EBS 12 and while browsing forms on Cash Management, Vision Operations -> Bank Statements -> Banks Statements and Reconciliation, I encountered the following error:
AXCABMR: initialize procedure raised unhandled exception ORA-01403: NO DATA found FRM-40735: WHEN-NEW--FORM-INSTANCE trigger raised unhandled exception ORA-06508.
I got the following workaround on EBS 11 from Metalink:
https://metalink.oracle.com/metalink/plsql/f?p=130:14:6133937266938631561::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,557752.1,1,1,1,helvetica
On querying my DB, I noticed the table doesn't exist
SQL> SELECT TABLE_NAME FROM DBA_TABLES where table_name like 'CE_SYSTEM_PARAMETERS%';
TABLE_NAME
CE_SYSTEM_PARAMETERS
CE_SYSTEM_PARAMETERS_ALL_A
SQL> DESC CE_SYSTEM_PARAMETERS;
ERROR:
ORA-04043: object CE_SYSTEM_PARAMETERS does not exist
SQL> DESC CE_SYSTEM_PARAMETERS_ALL_A;
ERROR:
ORA-04043: object CE_SYSTEM_PARAMETERS_ALL_A does not exist
Please, what can I do for this?
Regards

Hello Hussein,
After doing this I ran AutoConfig
This is what am getting after. I also recreated a password for the sys and system, now
AutoConfig completed successfully.
The log file for this session is located at: /d01/oracle/VIS/db/tech_st/10.2.0/appsutil/log/VIS_ebs/09291707/adconfig.log
Please, waht can I do Hussein to get over this? Thanks
500 Internal Server Error
java.lang.NoClassDefFoundError at oracle.apps.fnd.sso.AppsLoginRedirect.AppsSetting(AppsLoginRedirect.java:120) at oracle.apps.fnd.sso.AppsLoginRedirect.init(AppsLoginRedirect.java:161) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.loadServlet(HttpApplication.java:2231) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4617) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4541) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2821) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:740) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:299) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:187) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:595
Regards,
Nadine

Similar Messages

0FC_BP_ITEMS DataSource Initialization procedure

Hi Experts,
Could someone provide me step by step procedure on the above mentioned DataSource implementation by considering my input here.
SAP ECC - Clinet 100 is for configuration
Client 200 is for data extraction (as soon as you finish with configuration in Client 100, automatically reflect in 200).
I have followed all steps described in all forum notes, SAP help.
After I ran FPOP, all 3 tables are get filled with decent data.
I am able to Initialize without data transfer option without fail. But follow up Delta run fetching 0 records.
I am unable to initialized with data transfer. Its keep failing and complaining, "Delta Extraction for Business Parter Items is not active".
I also need to work on 0FC_PAY and 0FC_RET. If someone have any procedure on these datasources, I will really appreciate your help in sharing/guiding.
Thank you,
Anil

Hi Amit
If you have done the enhancement and are able to see the fields in RSA3 then you need not do any other settings in SBIW. The settings which you refered from the link are specifically for Open Item and Cleared Items.
So go ahead, replicate the enhanced DS in BI and extract the data through the Info package till PSA. You could even check in PSA if the enhanced fields are appearing or not.
Cheers
Umesh

SRM Initialization procedure

Can anyone tell me the procedure for init load(for both customized and std datasource).. Is there any need to fill the setup table for that..

any updates?

Dbms_scheduler job finihed succesfull when underlying procedure fails

I have a job created with dbms_scheduler which finishes succesfully even when the underlying plsql procedure raises a oracle error.
Is there any way to stop the running job with a failure when the plsql procedure fails and show the oracle error in the all_scheduler_job_run_details.error# column?
Example:
procedure test is
begin raise no_data_found;
end;
dbms_scheduler.create_job(job_name =>'MY_JOB', 'test');
dbms_scheduler.run_job;
when querying all_scheduler_job_run_details I want to see the no_data_found error which occurs in procedure.

user4260036 wrote:
I have a job created with dbms_scheduler which finishes succesfully even when the underlying plsql procedure raises a oracle error.
Is there any way to stop the running job with a failure when the plsql procedure fails and show the oracle error in the all_scheduler_job_run_details.error# column?
what exactly does "stop the running job" mean?
when querying all_scheduler_job_run_details I want to see the no_data_found error which occurs in procedure.in which column do you expect/desire this information to reside?
SQL> desc all_scheduler_job_run_details
Name                            Null?    Type
LOG_ID                              NUMBER
LOG_DATE                             TIMESTAMP(6) WITH TIME ZONE
OWNER                                  VARCHAR2(30)
JOB_NAME                             VARCHAR2(65)
JOB_SUBNAME                             VARCHAR2(65)
STATUS                              VARCHAR2(30)
ERROR#                              NUMBER
REQ_START_DATE                         TIMESTAMP(6) WITH TIME ZONE
ACTUAL_START_DATE                        TIMESTAMP(6) WITH TIME ZONE
RUN_DURATION                             INTERVAL DAY(3) TO SECOND(0)
INSTANCE_ID                             NUMBER
SESSION_ID                             VARCHAR2(30)
SLAVE_PID                             VARCHAR2(30)
CPU_USED                             INTERVAL DAY(3) TO SECOND(2)
CREDENTIAL_OWNER                        VARCHAR2(65)
CREDENTIAL_NAME                        VARCHAR2(65)
DESTINATION_OWNER                        VARCHAR2(128)
DESTINATION                             VARCHAR2(128)
ADDITIONAL_INFO                        VARCHAR2(4000)

Early Delta Initialization option in Production system

Hi Experts,
I have seen some threads related to Early Delta initialization in this forum. I have a question regarding this option.
To minimize the downtime/block users in the R/3 production system during set up tables fillup I would like to use the Early delta option. Please give your suggestions on the following procedure:
For Sales Orders, billing and Deliveries
1. Initialize Early delta in the BI system.
2. Go and fill setup tables
3. Do a full load to BI
4. Run delta job in R/3 (LBWE)
5. Run delta job in BI Info package
Do we miss any documents in this process for e.g. during set up tables fill up changes to existing documents or newly created sales orders.
I feel we won't miss. All changes will be reflected in Delta queue. And even newly created orders also will be coming to delta queue.
Please let me know if I am wrong.
Thank you.

Need Clarification on this thread,
According to my understanding, during the filling of set up table if a user does any posting, then the data available in BW will be incorrect.
am i right?
In your sequence the 4th step
4. Run delta job in R/3 (LBWE), this means you are using queued or unseriallized v3 update.
Early delta iniliazation essentially of no advantage because, as conventional initialization procedures, you can readmit document
postings after successfully filling the setup tables.
can anybody clear my doubt. is it possible during setup table filling user can post a document.
I know the documents will be collected in the queue. But the data loaded to bw will be incorrect right?
Regards,
Anand.
Edited by: araj123 on May 26, 2010 11:41 AM

Using WWSBR_API.ADD_ITEM raises exception ITEM_CREATION_ERROR

All,
i create a very simple procedure in the schema of the portal owner:
create or replace procedure test_insert_item is
l_item_nr number;
l_site_id number;
l_corner_id number;
l_type_id number;
l_type_caid number;
l_region_id number;
begin
l_site_id := 154;
l_corner_id := 6989;
l_type_id := 2;
l_type_caid := 0;
l_region_id := 5;
l_item_nr := wwsbr_api.add_item (
p_caid => l_site_id
, p_folder_id => l_corner_id
, p_display_name => 'my test item'
, p_type_id => l_type_id
, p_type_caid => l_type_caid
, p_region_id => l_region_id
, p_text => 'my own text'
commit;
end;
If i run this procedure in SQL*Plus as the Portal-owner, then the first time during a session the procedure raises the exception
WWSBR_API.ITEM_CREATION_ERROR. Each following time that i run the procedure it inserts the text item as expected.
How come? I checked for invalid object etc., but there are none.
Any ideas?
Thanks in advance!
Regards,
Bindert Glazema

I experimented a little bit further. If i change the procedure to:
create or replace procedure test_insert_item is
l_item_nr number;
l_site_id number;
l_corner_id number;
l_type_id number;
l_type_caid number;
l_region_id number;
begin
l_site_id := 154;
l_corner_id := 6989;
l_type_id := 2;
l_type_caid := 0;
l_region_id := 5;
l_item_nr := wwsbr_api.add_item (
p_caid => l_site_id
, p_folder_id => l_corner_id
, p_display_name => 'my test item'
, p_type_id => l_type_id
, p_type_caid => l_type_caid
, p_region_id => l_region_id
, p_text => 'my own text'
commit;
exception
when WWSBR_API.ITEM_CREATION_ERROR then
l_item_nr := wwsbr_api.add_item (
p_caid => l_site_id
, p_folder_id => l_corner_id
, p_display_name => 'my test item'
, p_type_id => l_type_id
, p_type_caid => l_type_caid
, p_region_id => l_region_id
, p_text => 'my own text'
commit;
end;
then no exception will be raised when i run the procedure the first time during a SQL*Plus session and still the item is inserted. The weird thing is, that when i call this procedure from a dynamic page:
<HTML>
<BODY>
<ORACLE>
begin
portal30.test_insert_item;
exception
when portal30.wwsbr_api.ITEM_CREATION_ERROR
then
htp.p('Item creation error');
end;
</ORACLE>
</BODY>
</HTML>
then the item is not inserted when the page is run, but the page shows 'Item creation error' instead. Does anyone have an idea why this doesn't work?
null

Using FOR .. LOOP counter in handling of PL/SQL procedures with nest. table

Hi all!
I'm learning PL/SQL on Steve Bobrovsky's book (specified below sample is from it) and I've a question.
In the procedure of specified below program used an integer variable currentElement to get reference to the row of nested table of %ROWTYPE datatype.
Meanwhile, the program itself uses a common FOR .. LOOP counter i.
DECLARE
TYPE partsTable IS TABLE OF parts%ROWTYPE;
tempParts partsTable := partsTable();
CURSOR selectedParts IS
SELECT * FROM parts ORDER BY id;
currentPart selectedParts%ROWTYPE;
currentElement INTEGER;
PROCEDURE printParts(p_title IN VARCHAR2, p_collection IN partsTable) IS
BEGIN
   DBMS_OUTPUT.PUT_LINE(' ');
   DBMS_OUTPUT.PUT_LINE(p_title || ' elements: ' || p_collection.COUNT);
   currentElement := p_collection.FIRST;
   FOR i IN 1 .. p_collection.COUNT
   LOOP
    DBMS_OUTPUT.PUT('Element #' || currentElement || ' is ');
     IF tempParts(currentElement).id IS NULL THEN DBMS_OUTPUT.PUT_LINE('an empty element.');
     ELSE DBMS_OUTPUT.PUT_LINE('ID: ' || tempParts(currentElement).id || ' DESCRIPTION: ' || tempParts(currentElement).description);
     END IF;
    currentElement := p_collection.NEXT(currentElement);
   END LOOP;
END printParts;
BEGIN
FOR currentPart IN selectedParts
LOOP
tempParts.EXTEND(2);
tempParts(tempParts.LAST) := currentPart;
END LOOP;
printParts('Densely populated', tempParts);
FOR i IN 1 .. tempParts.COUNT
LOOP
IF tempParts(i).id is NULL THEN tempParts.DELETE(i);
END IF;
END LOOP;
FOR i IN 1 .. 50
LOOP
DBMS_OUTPUT.PUT('-');
END LOOP;
printParts('Sparsely populated', tempParts);
END;
/When I've substituted an INTEGER global variable with such FOR .. LOOP counter, an APEX have returned an error "ORA-01403: no data found".
DECLARE
TYPE partsTable IS TABLE OF parts%ROWTYPE;
tempParts partsTable := partsTable();
CURSOR selectedParts IS
SELECT * FROM parts ORDER BY id;
currentPart selectedParts%ROWTYPE;
PROCEDURE printParts(p_title IN VARCHAR2, p_collection IN partsTable) IS
BEGIN
   DBMS_OUTPUT.PUT_LINE(' ');
   DBMS_OUTPUT.PUT_LINE(p_title || ' elements: ' || p_collection.COUNT);
   FOR i IN 1 .. p_collection.COUNT
   LOOP
    DBMS_OUTPUT.PUT('Element is ');
     IF tempParts(i).id IS NULL THEN DBMS_OUTPUT.PUT_LINE('an empty element.');
     ELSE DBMS_OUTPUT.PUT_LINE('ID: ' || tempParts(i).id || ' DESCRIPTION: ' || tempParts(i).description);
     END IF;
   END LOOP;
END printParts;
BEGIN
FOR currentPart IN selectedParts
LOOP
tempParts.EXTEND(2);
tempParts(tempParts.LAST) := currentPart;
END LOOP;
printParts('Densely populated', tempParts);
FOR i IN 1 .. tempParts.COUNT
LOOP
IF tempParts(i).id is NULL THEN tempParts.DELETE(i);
END IF;
END LOOP;
FOR i IN 1 .. 50
LOOP
DBMS_OUTPUT.PUT('-');
END LOOP;
printParts('Sparsely populated', tempParts);
END;
/When I've tried to handle this code in SQL*Plus, the following picture have appeared:
Densely populated elements: 10
Element is an empty element.
Element is ID: 1 DESCRIPTION: Fax Machine
Element is an empty element.
Element is ID: 2 DESCRIPTION: Copy Machine
Element is an empty element.
Element is ID: 3 DESCRIPTION: Laptop PC
Element is an empty element.
Element is ID: 4 DESCRIPTION: Desktop PC
Element is an empty element.
Element is ID: 5 DESCRIPTION: Scanner
Sparsely populated elements: 5
DECLARE
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at line 14
ORA-06512: at line 35What's wrong in code(or what I have not understood)? Help please!

942736 wrote:
What's wrong in code(or what I have not understood)? Help please!First code. You have collection of 10 elements:
1 - null
2 - populated
3 - null
4 - populated
5 - null
6 - populated
7 - null
8 - populated
9 - null
10 - populated
Then you delete null elements and have 5 element collection
2 - populated
4 - populated
6 - populated
8 - populated
10 - populated
Now you execute:
printParts('Sparsely populated', tempParts);Inside procedure you execute:
currentElement := p_collection.FIRST;
This assingns currentElement value 2. Then procedure loops 5 times (collection element count is 5). Element 2 exists. Inside loop procedure executes:
currentElement := p_collection.NEXT(currentElement);
which assigns currentElement values 4,6,8,10 - all existing elements.
Now second code. Everything is OK until you delete null elements. Again we have:
2 - populated
4 - populated
6 - populated
8 - populated
10 - populated
Again you execute:
printParts('Sparsely populated', tempParts);Now procedure loops 5 times (i values are 1,2,3,4,5):
FOR i IN 1 .. p_collection.COUNT
Very first iteration assingns i value 1. And since collection has no element with substript 1 procedure raises no data found.
SY.

Commits in Stored Procedures or ADO

I'm working on a .Net project and the Developers want to put the commit/rollback control in the ADO. This makes for extra trips and extra logic in the ADO that I think should be in stored procedures.
What arguements can I make to convince the developers that the best place to control commits and rollback is in pl/sql?

I am used to doing somthing like this:
begin
  --dml code
  commit;
exception
  when others then
  rollback;
    --call error logging procedure
    raise;
end;
This process of handling errors still must happen. If I put it in the middle tier, then more traffic happens between the middle tier and the database.
1. run proc
2. inspect outcome
3. commit or rollback
4. inspect outcome
or
1. run proc
2. inspect outcome
Secondly, if this breaks on step 2 because of a network problem or the middle tier server dies, then I will have a problem. Or maybe the middle tier wasn't coded perfectly (that does happen you know) and the wrong session issues the commit or rollback. Or the midle tier can't handle a particular exception and crashes.
Any other arguements for putting commit control in pl/sql?

Calling PL/SQL Procedures from Java

Hello,
I want to know, if it is possible to call PL/SQL Procedures from
SQLJ(which uses htp.print from the Package web toolkit ).
Though, it is possible to call normal procedures but if I want
to call PL/SQL procedures with htp.print then I get I error.
For example:
#sql{Call html_test()};
Can you give me a advice?
Your help is much appreciated!
M|ller

Oracle's htp packages are develop to be work with
mod_plsql/OAS/OWS webserver.
If you are trying to use htp packages first need to instanciate
some enviroment vars for htp packages, for example first you has
to call to owa.initialize procedure, populate owa.cgi array and
so on.
If you need more information about how this toolkit works you
could get the source of DB Prism at
http://www.plenix.com/dbprism/ this open source framework
includes backward compatibility with mod_plsql application and
then includes settings of this values from Java code.
Best regards, Marcelo.

How to Use Early Delta Initialization

Hi BW Experts,
We are in BI 7.0 Version. Only for Reporting we are using BI 7.0. For modeling, still we are using BW 3.1C only.
We want to use Early Delta Initialization. But this is in Disable Mode in our system
I am getting the following Messages:
<b>"Extractors supporting early delta initialization are not available before plug-in (-A) 2002.1"</b>
<b>"You cannot execute an initialization simulation together with an early delta"</b>
Please can anyone give me the suggestion.
Regards
Anjali

Hi,
you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system. You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this..Use the Early Delta Initialization indicator in the InfoPackage if you want to avoid a period when no updates can be made (no document processing and update) in the source system while the delta process is being initialized. In some applications (such as LO Cockpit), an update-free period is nevertheless needed to fill the setup tables. In such cases, the update-free time is merely reduced. If you want to carry out early delta initialization, the update in the source system can continue and the data can be written to the delta queue while the initialization requests are being processed. Note: DataSources that support early delta initialization are available as of the release Plug-In 2002.1. The field ZDD_ABLE (characteristic value = X) for table RSOLTPSOURCE (in BW) or ROOSOURCE (in the source system) indicates whether a DataSource can support early delta initialization.Not always on our systems an important downtime is possible in the initialization process during the reconstruction and the delta init request (just thinking when you need to ask a billing stop period...a real nightmare in some company !)
For this reason, as of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the initialization for selected datasources (just checking in infopackage update mode tab if this function is available): in this way you can readmit document postings in the OLTP system as early as possible during the initialization procedure..In fact, if an early delta initialization infopackage was started in BW, data may be written immediately to the delta queue.
But, if you are working with the queued delta method, using early delta initialization function doesnt make sense: as described before, its the same method definition that permits to reduce downtime phase.
But leaving aside that, dont forget that, regardless of the update method selected, its ALWAYS necessary to stop any document postings (for the relevant application) during setup tables recompilation run

Early delta initialization

Hello Gurus,
What are the scenarios we use Early Delta Init.
Is it available for Logistics datasources.
Full points to right answers.
Thanks in advance.

hi BW,
check this
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system. You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this.
Extractors that support early delta initialization were delivered with Plug-Ins as of Plug-In (-A) 2002.1.
You cannot run an initialization simulation together with an early delta initialization.
yes, it's available for logistics - oss note 505700, you can cross check the infopackage.
hope this helps.
505700-LBWE: New update methods as of PI 2002.1
g) Early delta initialization in the logistics extraction:
As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
Early Delta Initialization

Object instance initialization code - constructor equivalent?

Hi,
Is there an alternative in new javafx to using:
trigger on new MyClass{
//run several initialization statements
}Or simply put: how do I create a constructor (that will be invoked automatically after each instance has been created)? And no, using static factory method isn't an option, since there are no private constructors, meaning I can't force a programmer to invoke the static factory method, which might leave an object in illegal state (since the initialization procedure hasn't been invoked)...
Edited by: alextk on Nov 4, 2008 10:31 AM

Finally found it by digging through jdk code:
Old version JavaFx syntax:
trigger on new MyClass{
//run several initialization statements
}New version JavaFx (preview sdk) syntax:
postinit {
//run several initialization statements
}

Each procedure have commit statement

I call five procedure individually, and each procedure have commit statement from .net environment i.e. click event of submitt button call five procedure
but now i want only one commit statement for all five proceduce if all procedure successfully
executed.
suppose first two procedure successfully execute then third procedure raise some exception, in that case previously execute procedure data successfully comitted, but i want them rollback because all five procedure does not successfully execute.

What does this have to do with OCI? Sounds like a transaction control question...
The answer is to commit at the end of the transaction from the client code, and not at the end of each procedure call.

Difference between initialization with data transfer?

Dear Ones,
What is the Difference between initialization with data transfer,initialization without data transfer and early delta initialization?
Please explain me in senario basis..
Thanks
Shiva

Hello Shivananda,
See oss note 505700 :
The early delta initialization is used to admit document postings
in the OLTP system as early as possible during the initialization
procedure.
Regards,
Fred

JDK class initialization...

Hi,
I believe that class level member variables are not guarenteed to be initialized anymore by the JDK starting from jdk1.4 due an optimization that tries to reuse the instances.
So for example, if I defined a class level String variable, and was creating a number of instances of this class, it could be that some of the valus of this variable would be "dirty", i.e they would contain the previous values leftover from the last instance. So it was the developer's responsibility to make sure to explicitly initalize all class level variables.
Can anyone confirm this behaviour? Is this still the case?
Thanks

Hi,
I believe that class level member variables are not
guarenteed to be initialized anymore by the JDK
starting from jdk1.4 due an optimization that tries to
reuse the instances.Initialization is very closely described in the spec.
Refer to these sections to get started:
12.4 Initialization of Classes and Interfaces
12.4.1 When Initialization Occurs
12.4.2 Detailed Initialization Procedure
http://java.sun.com/docs/books/jls/second_edition/html/execution.doc.html#44411
So for example, if I defined a class level String
variable, and was creating a number of instances of
this class, it could be that some of the valus of this
variable would be "dirty", i.e they would contain the
previous values leftover from the last instance. So
it was the developer's responsibility to make sure to
explicitly initalize all class level variables.That would sound like a bug to me. Can you post
a code example that demonstrates this?

AXCABMR: initialize procedure raised

Similar Messages

Maybe you are looking for