Error In SNP PPM Creation . . .
Hi All,
I am getting following error message while converting PPDS PPM to SNP PPM. . .
" SNP-relevant and non-snp relevant modes exist in operation "
Please can someone let me know the solution on this. .
Thanks in advance.
Regards,
PP.
Hi,
Please check if any single or multi-mixed resource has "Not SNP Rel. indicator" has been set on the Planning Parameters tab page is in the PPDS ppm.
Regards
Datta
Similar Messages
-
Getting error while trying to generate SNP PPM
Hi Experts,
I am getting error, while trying to generate SNP PPM fron PP/DS PPM. It says Set up matrix for resource in planning version is not define. But I checked that i havea set up matrix as well as setup group.
Any help will be appreciated. Thanks In advance.
SaniHi Sani,
Try running resource & ppds ppm consistency check against
their respective transactions (/sapapo/res01 & /sapapo/scc_03)
and check any inconsistencies found.
Regards
R. Senthil Mareeswaran. -
Hi ,
I am facing an issue in SNP PPM generation from PPDS PPM and getting an error as /SAPAPO/PPM_GENERATE124-u2018Start date of the generation period is in the pastu2019.
I tried changing dates in field u2018Start of Gen. Periodu2019 to future in /SAPAPO/PPM_CONV_310 std TCode but still this error remains.
Please let me know the missing part here u2026
Regards,
DigambarHi Digambar,
Please check SAP notes 737991, 524601 and 1036685.
Whichever is relevant for you, implement it
Regards
R. Senthil Mareeswaran. -
PPDS to SNP PPM conversion error log
Dear all,
Iu2019m facing an issue in PPM conversion from PPDS to SNP.
I have deleted the both PPDS & SNP PPM for a product/location combination & the corresponding PV has been made invalid.
I have created a new PV for the product/location combination.
When I execute CIF & conversion for the newly created PV, though system is generating both new PPDS & SNP PPMu2019s but at the same time it issuing error messages referring the deleted PPMu2019s in transaction /SAPAPO/PPM_CONV_LOG - SNP PPM Generation: Display Log.
Please suggest how to resolve this issue. More over I would like to know is there any table where the deleted PPMu2019s data is stored which system is referring while generating new PPMu2019s?
Thanks in advance.Hi Shaiz,
I am surprised at the behavior of system. PV is invalid and still it is giving error message.
Please try to CIF new PPM for newly created PV after making earlier PPM inactive.
If the above said option does not work.
I could suggest you to try this. Let's hope it works.
1) Delete all SNP and PPDS PPM for this product location combination.
Make sure PPMs are inactive and deleted.
2) Delete the PV which is invalid and maintain only one valid PV.
Now try to CIF it afresh.
As far as your last question is concerned.
all the plans can be accessed by table /SAPAPO/PLAN
You will get all the details about all PPMs in this table along with the status if PPM (Active/Inactive)
Hope this helps. Let us know if it works.
Regards,
Abhay Kapase -
ERROR ODI-40837: An error occurred during the creation of the schema
Hi I am trying to test an xml file server and keep getting the following error.
ERROR ODI-40837: An error occurred during the creation of the schema: ODI-40738: A SAXException was caught while reading the model saying: Expected 'DOCTYPE'.
JDBC URL jdbc:snps:xml?f=C:/Projects/prd.xml&ro=true&DOD=YES
anybody could help as i dont find any blog or documentation about this error?.
Thanks
Edited by: user626688 on May 31, 2013 1:26 PMThere seems to be some problem with your xml file. Please work with support channel to investigate this issue.
You can also check the xml driver parameters details at http://docs.oracle.com/cd/E28280_01/integrate.1111/e12644/appendix_xml_driver.htm#CHDECBHH -
Hello Experts,
I am CIFfing production versions to create PPDS PPMs in APO. From there I am creating SNP PPMs.
The question is, when I do initial CIF of all the production versions(some production versions are old and some are new), how do I find a list of the PPDS PPMs that are still not converted to SNP PPMs.
Also is there a list which shows PPDS PPM plan along with the respective SNP PPM plan?
I tried referring the table /sapapo/plan, but it just gives the plan number, date of creation etc etc. Not even the Input/ouput products and the location.
Regards
ManotoshHi,
Use the BAPI : BAPI_PPMSRVAPS_GETLIST to get the PPM details.
/SAPAPO/PLAN_GEN to get the details of SNP PPM generated from PPDS PPM in the coloumn Plan generated.
Thanks,
nandha -
SNP PPM Generation from PPDS PPM - Time less than 1 sec. in snp bucket con
Dear All,
Request immediate help .
(a) My PPDS PPM have time elements less than 1 seconds towards processing time and there are operations without a set up time .
(b) While converting such a PPM PPM into an SNP PPM I get an error of bucket consumption as SNP cannot convert less than 1 second into a daily bucket .
(c) I have to maintain the base qty in BOM and Routing as 1 unit hence cannot increase the same .
(d) Is there a way in which SNP PPM can be generated from a PPDS PPM wherein the PPDS PPM has only a processing time of 1 second and no set up time .
(e) Infact I have tried to convert the PPDS PPM with a time of 1.5 seconds but now I have lot of products where the routing suggests a processing of less than 1second and no set up . This is leading to a PPDS PPM of time less than 1 second and SNP PPM is not getting generated as guess it cannot convert a PPDS PPM with less than 1.5 seconds in a day .
Would appreciate a quick response .
Thanks and Best Regards ,
Prashant KumarHi
Firstly, can I ask why the base unit has to be 1, this seems a strange restriction?
If it has to be, then two possible solutions:
1) In the CIF enhancement CIFPPM01 you could multiply all values by, for example, 100 to give you larger values in the PP/DS PPM in APO and hence of a size that SNP conversion can cope with.
2) In one of the BADI's /sapapo/ppm_calc or /sapapo/ppm_gen you can do the same conversion factor if the PP/DS PPM has to also be 1 unit.
Hope this helps
Ian -
Hello All,
Our design is to have one SNP PPM with more than one output products. Howeverm when there is demand for one product, the receipt for only that product should be generated. For example:
Product A - Demand = 100
Product B - Demand = 0
Product C - Demand = 0
When I run heuristic, I get a planned order of 100 for Product A which is good. But what i am also seeing that manufacture of products for Product B and Product C.
Is there a way to prevent the creation of the manufacture of co-products eventhough the SNP PPM has more than one output components.
Any ideas?
Thanks in advance.Hi Virendar,
Thanks for the input. But the flag you were suggesting wouldn't really help because all the products that are in PPM are output products and not components. As per my requirement,
If
Product A - Demand = 100
Product B - Demand = 0
Product C - Demand = 0
I need a planned order for only product A and nothing for the other 2 products
If
Product A - Demand = 0
Product B - Demand = 100
Product C - Demand = 0
I need a planned order for only product Band nothing for the other 2 products
And so on and so forth.
Thx -
Hi ,
I am working in SCM 5.1 , I wanted to test the dependent demand flow in SNP heuristic run and for the same I have tried to create PPM. I have created resource bucket & single mixed both. But when I am trying to activate the SNP PPM it gives me error "No linked PP/DS plan exists for SNP plan". IS it necessary to have PP/DS plan for SNP ppm ? Is anybody else faced the same problem in SCM 5.1 ?
Thanks for your support.
Best Regards,
MHi,
are you getting some more error? like 'bucket consumption is not defined'. then you have to define the 'bucket consumption' in the resource. go to 'mode' of the 'ppm' and check resource consumption is properly defined or not.
thanks,
Satyajit -
Hi Guys,
I have PPDS PPM have 3 operation , in first operation there are 6 modes ,all are SNP relevant and second operation there are one mode and third operation there are 2 modes. second and third operation resources are not SNP relevant, While generating SNP PPM system gives error maximum no of mode combination exceeds.
The requirement is only 6 SNP PPM should be generated as there are 6 SNP relevant modes are there.
Thanks and regards
Thamizhchelvan GHello,
With my experience SNP PPM generation can be a tricky business. Try this out...give the max number of PPMs possible as '99' and generate the PPMs. Then have a look at the number of PPMs generated and see what its doing. It should give you a fair amnt of idea wats going on.
Let me know how it goes
Abhi -
Error in : Purchase order Creation using BAPI_PO_CREATE1
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
i_create_order,
i_cycle TYPE cycle,
i_qty_acpt TYPE dzmeng,
i_dly_date TYPE vbak-vdatu,
i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
i_vbap TYPE vbap,
i_ekko TYPE ekko,
i_ekpo TYPE ekpo,
i_bsoh TYPE bapisdhd1,
i_bsohx TYPE bapisdhd1x,
i_bpoh TYPE bapimepoheader,
i_bpohx TYPE bapimepoheaderx,
i_vbeln TYPE vbeln_va,
i_posnr TYPE posnr_va,
i_contr TYPE vbeln_va,
i_conit TYPE posnr_va,
i_ebeln TYPE ebeln,
i_ebelp TYPE ebelp,
i_pargr TYPE pargr,
i_thead TYPE thead,
i_line TYPE tline,
i_note TYPE txw_note,
i_new_vbeln TYPE vbeln_va,
i_new_ebeln TYPE ebeln,
i_wa_bsoi TYPE bapisditm,
i_wa_bsoix TYPE bapisditmx,
i_wa_bsop TYPE bapiparnr,
i_wa_bsos TYPE bapischdl,
i_wa_bsosx TYPE bapischdlx,
i_wa_vbpa TYPE vbpa,
i_wa_vbkd TYPE vbkd,
i_wa_bpoi TYPE bapimepoitem,
i_wa_bpoix TYPE bapimepoitemx,
i_wa_bpos TYPE bapimeposchedule,
i_wa_bposx TYPE bapimeposchedulx,
i_wa_bpop TYPE bapiekkop,
i_wa_ekpa TYPE ekpa,
i_message TYPE char72,
i_bapiretn TYPE bapiret2,
i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
c_char_e VALUE 'E',
c_char_p VALUE 'P',
c_char_g VALUE 'G',
c_char_i VALUE 'I',
c_char_s VALUE 'S',
c_char_x VALUE 'X',
c_zsw(3) VALUE 'ZSW',
c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
IF NOT i_create_order IS INITIAL .
CLEAR: i_create_order .
MOVE: wa_order_split_create-docnr TO i_ebeln,
wa_order_split_create-docitm TO i_ebelp .
CALL FUNCTION 'ME_EKKO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
IMPORTING
po_ekko = i_ekko
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
ENDIF .
* Fill PO Header
i_bpoh-comp_code = i_ekko-bukrs .
i_bpoh-doc_type = i_ekko-bsart .
i_bpoh-vendor = i_ekko-lifnr .
i_bpoh-langu = i_ekko-spras .
i_bpoh-pmnttrms = i_ekko-zterm .
i_bpoh-purch_org = i_ekko-ekorg .
i_bpoh-pur_group = i_ekko-ekgrp .
i_bpoh-currency = i_ekko-waers .
i_bpoh-agreement = i_ekko-konnr .
i_bpoh-incoterms1 = i_ekko-inco1 .
i_bpoh-incoterms2 = i_ekko-inco2 .
* Fill PO update indicator 'X'
i_bpohx-comp_code = c_char_x .
i_bpohx-doc_type = c_char_x .
i_bpohx-vendor = c_char_x .
i_bpohx-langu = c_char_x .
i_bpohx-pmnttrms = c_char_x .
i_bpohx-purch_org = c_char_x .
i_bpohx-pur_group = c_char_x .
i_bpohx-currency = c_char_x .
i_bpohx-agreement = c_char_x .
i_bpohx-incoterms1 = c_char_x .
i_bpohx-incoterms2 = c_char_x .
CALL FUNCTION 'ME_EKPO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
pi_ebelp = i_ebelp
IMPORTING
po_ekpo = i_ekpo
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF .
* Fill PO Item
i_wa_bpoi-po_item = i_ekpo-ebelp .
i_wa_bpoi-material = i_ekpo-matnr .
i_wa_bpoi-plant = i_ekpo-werks .
i_wa_bpoi-stge_loc = i_ekpo-lgort .
i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
i_wa_bpoi-po_unit = i_ekpo-meins .
i_wa_bpoi-tax_code = i_ekpo-mwskz .
i_wa_bpoi-val_type = i_ekpo-bwtar .
i_wa_bpoi-item_cat = i_ekpo-pstyp .
i_wa_bpoi-acctasscat = i_ekpo-knttp .
i_wa_bpoi-agreement = i_ekpo-konnr .
i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
APPEND i_wa_bpoi TO i_bpoi .
* Fill PO Item update indicator 'X'
i_wa_bpoix-po_item = i_ekpo-ebelp .
i_wa_bpoix-po_itemx = c_char_x .
i_wa_bpoix-material = c_char_x .
i_wa_bpoix-plant = c_char_x .
i_wa_bpoix-stge_loc = c_char_x .
i_wa_bpoix-quantity = c_char_x .
i_wa_bpoix-po_unit = c_char_x .
i_wa_bpoix-tax_code = c_char_x .
i_wa_bpoix-val_type = c_char_x .
i_wa_bpoix-item_cat = c_char_x .
i_wa_bpoix-acctasscat = c_char_x .
i_wa_bpoix-agreement = c_char_x .
i_wa_bpoix-agmt_item = c_char_x .
APPEND i_wa_bpoix TO i_bpoix .
* Fill PO Item Schedule
i_wa_bpos-po_item = i_ekpo-ebelp .
i_wa_bpos-sched_line = '0001' .
i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
APPEND i_wa_bpos TO i_bpos .
* Fill PO Item schedule update indicator 'X'
i_wa_bposx-po_item = i_ekpo-ebelp .
i_wa_bposx-sched_line = '0001' .
i_wa_bposx-delivery_date = c_char_x .
i_wa_bposx-quantity = c_char_x .
APPEND i_wa_bposx TO i_bposx .
CLEAR: i_pargr .
SELECT SINGLE pargr
INTO i_pargr
FROM t161
WHERE bstyp = i_ekko-bstyp
AND bsart = i_ekko-bsart .
CLEAR i_ekpa[].
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = i_ekpa[].
LOOP AT i_ekpa INTO i_wa_ekpa .
i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
i_wa_bpop-langu = sy-langu .
IF NOT i_wa_ekpa-lifn2 IS INITIAL .
i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
ELSE .
i_wa_bpop-buspartno = i_wa_ekpa-parnr .
ENDIF .
APPEND i_wa_bpop TO i_bpop .
CLEAR: i_wa_ekpa, i_wa_bpop .
ENDLOOP .
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = i_bpoh
poheaderx = i_bpohx
IMPORTING
exppurchaseorder = i_new_ebeln
TABLES
return = i_bapiret2
poitem = i_bpoi[]
poitemx = i_bpoix[]
poschedule = i_bpos[]
poschedulex = i_bposx[].
i_order = i_new_ebeln .
SHIFT i_order LEFT DELETING LEADING '0' .
i_return-errortype = c_char_i .
i_return-workarea = c_zsw .
i_return-message = '064' .
i_return-variable1 = i_order .
loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
append i_bapiretn to t_bapi_return .
endloop .
if t_bapi_return[] is initial .
i_create_order = c_char_x .
CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
EXPORTING
act_return = i_return. "Popup with new PO no.
ENDCASE . " Docind
ENDIF .
ENDLOOP.Hi Shareen,
I think in the following parts of the code,
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = i_ekpa[].
Error in : Purchase order Creation using BAPI_PO_CREATE1
Posted: Mar 20, 2006 7:39 PM Reply E-mail this post
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
i_create_order,
i_cycle TYPE cycle,
i_qty_acpt TYPE dzmeng,
i_dly_date TYPE vbak-vdatu,
i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
i_vbap TYPE vbap,
i_ekko TYPE ekko,
i_ekpo TYPE ekpo,
i_bsoh TYPE bapisdhd1,
i_bsohx TYPE bapisdhd1x,
i_bpoh TYPE bapimepoheader,
i_bpohx TYPE bapimepoheaderx,
i_vbeln TYPE vbeln_va,
i_posnr TYPE posnr_va,
i_contr TYPE vbeln_va,
i_conit TYPE posnr_va,
i_ebeln TYPE ebeln,
i_ebelp TYPE ebelp,
i_pargr TYPE pargr,
i_thead TYPE thead,
i_line TYPE tline,
i_note TYPE txw_note,
i_new_vbeln TYPE vbeln_va,
i_new_ebeln TYPE ebeln,
i_wa_bsoi TYPE bapisditm,
i_wa_bsoix TYPE bapisditmx,
i_wa_bsop TYPE bapiparnr,
i_wa_bsos TYPE bapischdl,
i_wa_bsosx TYPE bapischdlx,
i_wa_vbpa TYPE vbpa,
i_wa_vbkd TYPE vbkd,
i_wa_bpoi TYPE bapimepoitem,
i_wa_bpoix TYPE bapimepoitemx,
i_wa_bpos TYPE bapimeposchedule,
i_wa_bposx TYPE bapimeposchedulx,
i_wa_bpop TYPE bapiekkop,
i_wa_ekpa TYPE ekpa,
i_message TYPE char72,
i_bapiretn TYPE bapiret2,
i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
c_char_e VALUE 'E',
c_char_p VALUE 'P',
c_char_g VALUE 'G',
c_char_i VALUE 'I',
c_char_s VALUE 'S',
c_char_x VALUE 'X',
c_zsw(3) VALUE 'ZSW',
c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
IF NOT i_create_order IS INITIAL .
CLEAR: i_create_order .
MOVE: wa_order_split_create-docnr TO i_ebeln,
wa_order_split_create-docitm TO i_ebelp .
CALL FUNCTION 'ME_EKKO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
IMPORTING
po_ekko = i_ekko
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
ENDIF .
Fill PO Header
i_bpoh-comp_code = i_ekko-bukrs .
i_bpoh-doc_type = i_ekko-bsart .
i_bpoh-vendor = i_ekko-lifnr .
i_bpoh-langu = i_ekko-spras .
i_bpoh-pmnttrms = i_ekko-zterm .
i_bpoh-purch_org = i_ekko-ekorg .
i_bpoh-pur_group = i_ekko-ekgrp .
i_bpoh-currency = i_ekko-waers .
i_bpoh-agreement = i_ekko-konnr .
i_bpoh-incoterms1 = i_ekko-inco1 .
i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
i_bpohx-comp_code = c_char_x .
i_bpohx-doc_type = c_char_x .
i_bpohx-vendor = c_char_x .
i_bpohx-langu = c_char_x .
i_bpohx-pmnttrms = c_char_x .
i_bpohx-purch_org = c_char_x .
i_bpohx-pur_group = c_char_x .
i_bpohx-currency = c_char_x .
i_bpohx-agreement = c_char_x .
i_bpohx-incoterms1 = c_char_x .
i_bpohx-incoterms2 = c_char_x .
CALL FUNCTION 'ME_EKPO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
pi_ebelp = i_ebelp
IMPORTING
po_ekpo = i_ekpo
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF .
Fill PO Item
i_wa_bpoi-po_item = i_ekpo-ebelp .
i_wa_bpoi-material = i_ekpo-matnr .
i_wa_bpoi-plant = i_ekpo-werks .
i_wa_bpoi-stge_loc = i_ekpo-lgort .
i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
i_wa_bpoi-po_unit = i_ekpo-meins .
i_wa_bpoi-tax_code = i_ekpo-mwskz .
i_wa_bpoi-val_type = i_ekpo-bwtar .
i_wa_bpoi-item_cat = i_ekpo-pstyp .
i_wa_bpoi-acctasscat = i_ekpo-knttp .
i_wa_bpoi-agreement = i_ekpo-konnr .
i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
i_wa_bpoix-po_item = i_ekpo-ebelp .
i_wa_bpoix-po_itemx = c_char_x .
i_wa_bpoix-material = c_char_x .
i_wa_bpoix-plant = c_char_x .
i_wa_bpoix-stge_loc = c_char_x .
i_wa_bpoix-quantity = c_char_x .
i_wa_bpoix-po_unit = c_char_x .
i_wa_bpoix-tax_code = c_char_x .
i_wa_bpoix-val_type = c_char_x .
i_wa_bpoix-item_cat = c_char_x .
i_wa_bpoix-acctasscat = c_char_x .
i_wa_bpoix-agreement = c_char_x .
i_wa_bpoix-agmt_item = c_char_x .
APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
i_wa_bpos-po_item = i_ekpo-ebelp .
i_wa_bpos-sched_line = '0001' .
i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
i_wa_bposx-po_item = i_ekpo-ebelp .
i_wa_bposx-sched_line = '0001' .
i_wa_bposx-delivery_date = c_char_x .
i_wa_bposx-quantity = c_char_x .
APPEND i_wa_bposx TO i_bposx .
CLEAR: i_pargr .
SELECT SINGLE pargr
INTO i_pargr
FROM t161
WHERE bstyp = i_ekko-bstyp
AND bsart = i_ekko-bsart .
CLEAR i_ekpa[].
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = <b>i_ekpa[].</b>
LOOP AT i_ekpa INTO i_wa_ekpa .
i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
i_wa_bpop-langu = sy-langu .
IF NOT i_wa_ekpa-lifn2 IS INITIAL .
i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
ELSE .
i_wa_bpop-buspartno = i_wa_ekpa-parnr .
ENDIF .
APPEND i_wa_bpop TO i_bpop .
CLEAR: i_wa_ekpa, i_wa_bpop .
ENDLOOP .
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = i_bpoh
poheaderx = i_bpohx
IMPORTING
exppurchaseorder = i_new_ebeln
TABLES
return = i_bapiret2
<b> poitem = i_bpoi[]
poitemx = i_bpoix[]
poschedule = i_bpos[]
poschedulex = i_bposx[].</b>
it should be only i_bpoi, i_bpoix, i_bpos, i_bposx but not i_bpoi[], i_bpoix[], i_bpos[], i_bposx[].
CHange the code as follows:
DATA: i_insert,
i_create_order,
i_cycle TYPE cycle,
i_qty_acpt TYPE dzmeng,
i_dly_date TYPE vbak-vdatu,
i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
i_vbap TYPE vbap,
i_ekko TYPE ekko,
i_ekpo TYPE ekpo,
i_bsoh TYPE bapisdhd1,
i_bsohx TYPE bapisdhd1x,
i_bpoh TYPE bapimepoheader,
i_bpohx TYPE bapimepoheaderx,
i_vbeln TYPE vbeln_va,
i_posnr TYPE posnr_va,
i_contr TYPE vbeln_va,
i_conit TYPE posnr_va,
i_ebeln TYPE ebeln,
i_ebelp TYPE ebelp,
i_pargr TYPE pargr,
i_thead TYPE thead,
i_line TYPE tline,
i_note TYPE txw_note,
i_new_vbeln TYPE vbeln_va,
i_new_ebeln TYPE ebeln,
i_wa_bsoi TYPE bapisditm,
i_wa_bsoix TYPE bapisditmx,
i_wa_bsop TYPE bapiparnr,
i_wa_bsos TYPE bapischdl,
i_wa_bsosx TYPE bapischdlx,
i_wa_vbpa TYPE vbpa,
i_wa_vbkd TYPE vbkd,
i_wa_bpoi TYPE bapimepoitem,
i_wa_bpoix TYPE bapimepoitemx,
i_wa_bpos TYPE bapimeposchedule,
i_wa_bposx TYPE bapimeposchedulx,
i_wa_bpop TYPE bapiekkop,
i_wa_ekpa TYPE ekpa,
i_message TYPE char72,
i_bapiretn TYPE bapiret2,
i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
c_char_e VALUE 'E',
c_char_p VALUE 'P',
c_char_g VALUE 'G',
c_char_i VALUE 'I',
c_char_s VALUE 'S',
c_char_x VALUE 'X',
c_zsw(3) VALUE 'ZSW',
c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
IF NOT i_create_order IS INITIAL .
CLEAR: i_create_order .
MOVE: wa_order_split_create-docnr TO i_ebeln,
wa_order_split_create-docitm TO i_ebelp .
CALL FUNCTION 'ME_EKKO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
IMPORTING
po_ekko = i_ekko
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
ENDIF .
Fill PO Header
i_bpoh-comp_code = i_ekko-bukrs .
i_bpoh-doc_type = i_ekko-bsart .
i_bpoh-vendor = i_ekko-lifnr .
i_bpoh-langu = i_ekko-spras .
i_bpoh-pmnttrms = i_ekko-zterm .
i_bpoh-purch_org = i_ekko-ekorg .
i_bpoh-pur_group = i_ekko-ekgrp .
i_bpoh-currency = i_ekko-waers .
i_bpoh-agreement = i_ekko-konnr .
i_bpoh-incoterms1 = i_ekko-inco1 .
i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
i_bpohx-comp_code = c_char_x .
i_bpohx-doc_type = c_char_x .
i_bpohx-vendor = c_char_x .
i_bpohx-langu = c_char_x .
i_bpohx-pmnttrms = c_char_x .
i_bpohx-purch_org = c_char_x .
i_bpohx-pur_group = c_char_x .
i_bpohx-currency = c_char_x .
i_bpohx-agreement = c_char_x .
i_bpohx-incoterms1 = c_char_x .
i_bpohx-incoterms2 = c_char_x .
CALL FUNCTION 'ME_EKPO_SINGLE_READ'
EXPORTING
pi_ebeln = i_ebeln
pi_ebelp = i_ebelp
IMPORTING
po_ekpo = i_ekpo
EXCEPTIONS
no_records_found = 1
OTHERS = 2.
IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF .
Fill PO Item
i_wa_bpoi-po_item = i_ekpo-ebelp .
i_wa_bpoi-material = i_ekpo-matnr .
i_wa_bpoi-plant = i_ekpo-werks .
i_wa_bpoi-stge_loc = i_ekpo-lgort .
i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
i_wa_bpoi-po_unit = i_ekpo-meins .
i_wa_bpoi-tax_code = i_ekpo-mwskz .
i_wa_bpoi-val_type = i_ekpo-bwtar .
i_wa_bpoi-item_cat = i_ekpo-pstyp .
i_wa_bpoi-acctasscat = i_ekpo-knttp .
i_wa_bpoi-agreement = i_ekpo-konnr .
i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
i_wa_bpoix-po_item = i_ekpo-ebelp .
i_wa_bpoix-po_itemx = c_char_x .
i_wa_bpoix-material = c_char_x .
i_wa_bpoix-plant = c_char_x .
i_wa_bpoix-stge_loc = c_char_x .
i_wa_bpoix-quantity = c_char_x .
i_wa_bpoix-po_unit = c_char_x .
i_wa_bpoix-tax_code = c_char_x .
i_wa_bpoix-val_type = c_char_x .
i_wa_bpoix-item_cat = c_char_x .
i_wa_bpoix-acctasscat = c_char_x .
i_wa_bpoix-agreement = c_char_x .
i_wa_bpoix-agmt_item = c_char_x .
APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
i_wa_bpos-po_item = i_ekpo-ebelp .
i_wa_bpos-sched_line = '0001' .
i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
i_wa_bposx-po_item = i_ekpo-ebelp .
i_wa_bposx-sched_line = '0001' .
i_wa_bposx-delivery_date = c_char_x .
i_wa_bposx-quantity = c_char_x .
APPEND i_wa_bposx TO i_bposx .
CLEAR: i_pargr .
SELECT SINGLE pargr
INTO i_pargr
FROM t161
WHERE bstyp = i_ekko-bstyp
AND bsart = i_ekko-bsart .
CLEAR i_ekpa[].
CALL FUNCTION 'MM_READ_PARTNERS'
EXPORTING
application = c_char_p
ebeln = i_ebeln
bstyp = i_ekko-bstyp
pargr = i_pargr
TABLES
x_ekpa = i_ekpa.
LOOP AT i_ekpa INTO i_wa_ekpa .
i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
i_wa_bpop-langu = sy-langu .
IF NOT i_wa_ekpa-lifn2 IS INITIAL .
i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
ELSE .
i_wa_bpop-buspartno = i_wa_ekpa-parnr .
ENDIF .
APPEND i_wa_bpop TO i_bpop .
CLEAR: i_wa_ekpa, i_wa_bpop .
ENDLOOP .
CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = i_bpoh
poheaderx = i_bpohx
IMPORTING
exppurchaseorder = i_new_ebeln
TABLES
return = i_bapiret2
poitem = i_bpoi
poitemx = i_bpoix
poschedule = i_bpos
poschedulex = i_bposx.
i_order = i_new_ebeln .
SHIFT i_order LEFT DELETING LEADING '0' .
i_return-errortype = c_char_i .
i_return-workarea = c_zsw .
i_return-message = '064' .
i_return-variable1 = i_order .
loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
append i_bapiretn to t_bapi_return .
endloop .
if t_bapi_return[] is initial .
i_create_order = c_char_x .
CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
EXPORTING
act_return = i_return. "Popup with new PO no.
ENDCASE . " Docind
ENDIF .
ENDLOOP. -
Error message during cube creation
Hi expert,
System show the following error message during cube creation, please info how to solve this problem. Thanks.
Define the characteristics of the validity table for non-cumulatives
Message no. R7846
Diagnosis
The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
Examples of such characteristics are:
A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
Procedure
Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
In the example above, the characteristics "plan/actual" and "plant" must be selected.
The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.Hi,
Go to the Extras Tab in the definition of the Cube and there select " Maintain Non-Cumulatives" and there select the Plant check box. You can also check Material but it is not recommended. Now try to activate the cube. I think it will work for you. -
Getting Error while installing Repository Creation Utility (RCU)!!!!!
Hi,
While installing RCU, I was getting the Invalid Username/Password error on Database Connection Details Screen when i give sys userid. on Database Connection Details Screen I was trying to connect with sys user but failed then I used system user and it got connect.
Then on Component screen, I was getting the below error.
RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
Trying to connect as a non SYSDBA user. User should have SYSDBA privileges to successfully load the ESS schema.
RCU-6092:Component Selection validation failed. Please refer to log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
I do not know why i am unable to connect with sys user as i am giving the correct password. Now i have changed the sys password but still unable to connect.
Please check the below link.
http://download.oracle.com/docs/cd/E12839_01/doc.1111/e14259/rcu_screens.htm
Please suggest something.
--- Log File Error ------------------------
2009-12-22 16:46:06.904 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: HOSTNAME: cicl-11g
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: OSINFO: i386 2.6.18-164.6.1.el5 Linux
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: JREINFO: 1.6.0_14 /u01/app/oracle/rcuHome/jdk/jre
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERNAME: oracle
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERDIR: /u01/app/oracle/rcuHome/bin
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: User country: US
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: User language: en
2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java class path: /u01/app/oracle/rcuHome/jlib/rcu.jar:/u01/app/oracle/rcuHome/jlib/share.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/orai18n-mapping.jar:/u01/app/oracle/rcuHome/lib/xmlparserv2.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc5.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc14.jar:/u01/app/oracle/rcuHome/jlib/jewt4.jar:/u01/app/oracle/rcuHome/jlib/ojdl.jar:/u01/app/oracle/rcuHome/modules/oracle.odl_11.1.1/ojdl.jar:/u01/app/oracle/rcuHome/jlib/SchemaVersion.jar:/u01/app/oracle/rcuHome/jlib/wlsqlserver.jar:/u01/app/oracle/rcuHome/jlib/wlbase.jar:/u01/app/oracle/rcuHome/jlib/wlutil.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.6.0.0.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.7.0.0.jar:/u01/app/oracle/rcuHome/jlib/wldb2.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/oracle_ice.jar:/u01/app/oracle/rcuHome/jlib/rcuhelp.jar:/u01/app/oracle/rcuHome/jlib/rcuhelppages.jar:/u01/app/oracle/rcuHome/assistants/opca/jlib/opca.jar:/u01/app/oracle/rcuHome/portal/jlib/ptlshare.jar:/u01/app/oracle/rcuHome/jlib/ldapjclnt11.jar:/u01/app/oracle/rcuHome/jlib/commons-collections-3.1.jar:/u01/app/oracle/rcuHome/jlib/commons-dbcp-1.2.1.jar:/u01/app/oracle/rcuHome/jlib/commons-logging.jar:/u01/app/oracle/rcuHome/jlib/commons-pool-1.2.jar:/u01/app/oracle/rcuHome/jlib/quartz-1.6.0.jar:/u01/app/oracle/rcuHome/jlib/jta.jar:/u01/app/oracle/rcuHome/jlib/xml.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-utils.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-authz-service.jar:/u01/app/oracle/rcuHome/jlib/iam-features-identity.zip:/u01/app/oracle/rcuHome/jlib/iam-features-configservice.zip:/u01/app/oracle/rcuHome/jlib/jps-api.jar:/u01/app/oracle/rcuHome/jlib/jps-common.jar:/u01/app/oracle/rcuHome/jlib/jps-ee.jar:/u01/app/oracle/rcuHome/jlib/jps-internal.jar:/u01/app/oracle/rcuHome/jlib/jps-manifest.jar:/u01/app/oracle/rcuHome/jlib/MicroSM.jar:/u01/app/oracle/rcuHome/jlib/javax.persistence_1.0.0.0_1-0-2.jar:/u01/app/oracle/rcuHome/jlib/org.eclipse.persistence_1.0.0.0_1-1-0.jar:/u01/app/oracle/rcuHome/jlib/identitystore.jar:/u01/app/oracle/rcuHome/jlib/jps-unsupported-api.jar:/u01/app/oracle/rcuHome/jlib/pd-internal.jar
2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java library path: /u01/app/oracle/rcuHome/jdk/jre/lib/i386/client:/u01/app/oracle/rcuHome/jdk/jre/lib/i386:/u01/app/oracle/rcuHome/jdk/jre/../lib/i386:/u01/app/oracle/rcuHome/lib32:/u01/app/oracle/rcuHome/network/lib32:/u01/app/oracle/rcuHome/lib:/u01/app/oracle/rcuHome/network/lib:/u01/app/oracle/product/11.2.0/network/lib:/u01/app/oracle/product/11.2.0/jdbc/lib:/u01/app/oracle/product/11.2.0/lib:/usr/lib:/usr/local/lib:/usr/java/packages/lib/i386:/lib:/usr/lib
2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: Launching RCU.
2009-12-22 16:46:06.916 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: Creating InteractiveRCUModel
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: Base URL : file:///u01/app/oracle/rcuHome/rcu/config/
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: ComponentInfo xml location : /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: Storage xml location : /u01/app/oracle/rcuHome/rcu/config/Storage.xml
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: DTD Validation : true
2009-12-22 16:46:07.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.RCUCommandLineParser::process: Processing command line ....
2009-12-22 16:46:39.363 NOTIFICATION rcu: oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine::connect: Connecting to database: user:system, role:Normal, connectString:(description=(address=(host=cicl-11g)(protocol=tcp)(port=1521))(connect_data=(service_name=DEV11G)(server=dedicated)))
2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Initializing repository configuration metadata
2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = INIT_META_DATA
2009-12-22 16:46:40.704 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : AS_COMMON
2009-12-22 16:46:40.707 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
2009-12-22 16:46:40.713 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
2009-12-22 16:46:40.714 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
2009-12-22 16:46:40.716 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : IAU
2009-12-22 16:46:40.720 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORAESS
2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : IDM
2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OID
2009-12-22 16:46:40.723 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OIF
2009-12-22 16:46:40.732 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OWLCS
2009-12-22 16:46:40.733 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPXDMS
2009-12-22 16:46:40.735 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPSDS
2009-12-22 16:46:40.759 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPLS
2009-12-22 16:46:40.760 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOA
2009-12-22 16:46:40.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
2009-12-22 16:46:40.763 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : BAM
2009-12-22 16:46:40.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
2009-12-22 16:46:40.768 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
2009-12-22 16:46:40.769 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
2009-12-22 16:46:40.770 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER_SUITE
2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
2009-12-22 16:46:40.772 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
2009-12-22 16:46:40.774 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
2009-12-22 16:46:40.776 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
2009-12-22 16:46:40.777 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
2009-12-22 16:46:40.779 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
2009-12-22 16:46:40.783 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
2009-12-22 16:46:40.784 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
2009-12-22 16:46:40.785 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
2009-12-22 16:46:40.786 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS_CRAWLER
2009-12-22 16:46:40.791 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS_CRAWLER
2009-12-22 16:46:40.794 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
2009-12-22 16:46:40.796 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTAL_BI
2009-12-22 16:46:40.797 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTAL
2009-12-22 16:46:40.800 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCOVERER
2009-12-22 16:46:40.821 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseXmlData: XML Document: /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml is valid
2009-12-22 16:46:40.835 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : MDS
2009-12-22 16:46:40.843 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//mds/mds.xml is valid
2009-12-22 16:46:40.852 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : IAU
2009-12-22 16:46:40.857 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/iau/iau.xml is valid
2009-12-22 16:46:40.864 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORAESS
2009-12-22 16:46:40.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//ess/ess.xml is valid
2009-12-22 16:46:40.883 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : OID
2009-12-22 16:46:40.886 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oid/oid.xml is valid
2009-12-22 16:46:40.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : OIF
2009-12-22 16:46:40.898 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oif/oif.xml is valid
2009-12-22 16:46:40.904 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPXDMS
2009-12-22 16:46:40.907 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commspresence/commspresence.xml is valid
2009-12-22 16:46:40.915 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPSDS
2009-12-22 16:46:40.932 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commssds/commssds.xml is valid
2009-12-22 16:46:40.938 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPLS
2009-12-22 16:46:40.939 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commsls/commsls.xml is valid
2009-12-22 16:46:40.945 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : SOAINFRA
2009-12-22 16:46:40.950 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//soainfra/soainfra.xml is valid
2009-12-22 16:46:40.955 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : BAM
2009-12-22 16:46:40.958 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//bam/bam.xml is valid
2009-12-22 16:46:40.963 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPM
2009-12-22 16:46:40.975 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//sdpm/sdpm.xml is valid
2009-12-22 16:46:40.981 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : WEBCENTER
2009-12-22 16:46:40.991 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//webcenter/webcenter.xml is valid
2009-12-22 16:46:40.998 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : PORTLET
2009-12-22 16:46:41.006 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//portlet/portlet.xml is valid
2009-12-22 16:46:41.011 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : CONTENTSERVER
2009-12-22 16:46:41.021 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/contentserver/contentserver.xml is valid
2009-12-22 16:46:41.024 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCUSSIONS
2009-12-22 16:46:41.030 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive/jive.xml is valid
2009-12-22 16:46:41.040 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCUSSIONS_CRAWLER
2009-12-22 16:46:41.048 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive-crawler/jive-crawler.xml is valid
2009-12-22 16:46:41.052 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : WIKI
2009-12-22 16:46:41.056 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//wiki/wiki.xml is valid
2009-12-22 16:46:41.063 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : PORTAL
2009-12-22 16:46:41.065 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/portal/portal.xml is valid
2009-12-22 16:46:41.070 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCOVERER
2009-12-22 16:46:41.073 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/dc/discoverer.xml is valid
2009-12-22 16:46:41.108 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseStorageData: XML Document: /u01/app/oracle/rcuHome/rcu/config/Storage.xml is valid
2009-12-22 16:46:41.452 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Initializing repository configuration metadata : 937 milliseconds
2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Obtain properties of the specified database
2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_QUERY_DATABASE
2009-12-22 16:46:41.498 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Obtain properties of the specified database : 34 milliseconds
2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Check requirement for specified database
2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_GLOBAL_CHECK
2009-12-22 16:46:41.557 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Check requirement for specified database : 43 milliseconds
2009-12-22 16:46:41.572 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Execute pre create operations
2009-12-22 16:46:41.573 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.CustomCompManager::getActionList: CustomCompManager.getActionList: CUSTOM_COMP_PRELOAD_SETUP
2009-12-22 16:46:41.579 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData
2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Execute pre create operations : 9 milliseconds
2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Metadata Services
2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = MDS
2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
2009-12-22 16:46:55.722 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Metadata Services : 35 milliseconds
2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Audit Services
2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = IAU
2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
2009-12-22 16:46:55.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Audit Services : 34 milliseconds
2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Enterprise Scheduler Service
2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = ORAESS
2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
2009-12-22 16:46:55.773 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.PrereqTask::execute: Prereq Evaluation Failed
oracle.sysman.assistants.rcu.backend.validation.PrereqException: RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
at oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator.executePrereqTask(PrereqEvaluator.java:642)
at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:68)
at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
at java.lang.Thread.run(Thread.java:619)
2009-12-22 16:46:55.773 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
oracle.sysman.assistants.common.task.TaskExecutionException: RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
Trying to connect as a non SYSDBA user. User should have SYSDBA privileges to successfully load the ESS schema.
at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:76)
at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
at java.lang.Thread.run(Thread.java:619)
Edited by: yousufpaya on Dec 22, 2009 7:31 PMHi yousuf;
Please follow below and see its helpful for your issue:
http://soadev.blogspot.com/2009_07_01_archive.html ( part:Error in Running Repository Creation Utility (RCU) While Using Oracle XE database )
Also check:
http://forums.tangosol.com/forums/thread.jspa?threadID=930952&tstart=60 (Joaanas post)
Regard
Helios -
Error as Enter while creation of PO due to this PO is not created in ME21N
Hi All,
I have an issue where one of my user cannot able to create a PO with refernce to Network and he is getting error as ENTER while creation of PO in ME21N and there is no long text for this error.Also user cannot able to create a PO whenever he clicked on save button the only option he got is Hold or Edit or cancel.
I have asked user to provide the same information (inputs while creation of PO in ME21N) to his colleague and check whether he can able to create a PO successfully or not. User confirmed that his colleague can able to create a PO successfully.
Please let me know what was the root cause behind this.
Awaiting for your valauble inputs & quicker reply.
Note: I have crossverified with technical team and they confim all the required roles are in place for my user.
BR // Kumar.SHi Jurgen,
Question from you
Just message ENTER is pretty unusual. Even if there is no long text, the message should at least have a message number, can you tell this number? In general there should be the field name next to the message.
Answer from me
As you have said i have cliked on the error ie ENTERand got the message number as below,
Enter
Message no. ME083
Question from you
Is there any userexit which may cause this error?
Answer from me
According to me know because only one user is having a problem other users can able to create a PO sucuessuflly.
Question from you
What happens if a different user enters the PO under the user ID of the user who can only hold the PO?
What happens if the effected user creates the PO under the user ID of a different user (who is usually able to save POs)?
Answer from me
not tried will let u know on this later
Question from you
Have you customized a new process, and this user is testing it?
Answer from me
No
Please let me know whether the above my inputs help you to identify the issue where exactly it was.
BR // Kumar.S -
Hello All,
Posting this problem here and hoping for a solution from the experts in this forum.
When i have restarted the Analysis Services , i see that it has been stopped but never started back. It fails with an error
"The SQL Server Analysis Services (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
When Checked the Event Viewer i see the following error -
The service cannot be started: The following system error occurred: The filename, directory name, or volume label syntax is incorrect. File system error: Error occurred during the creation of directory: '\\?\E:\OLAP\MSSOLAPFactory\OlapData;M:\Test
Backup'.
I remember changing the BackupDir value of Analysis Services few days back, and i think it could have impacted. Can you please help me how can i change back the BackupDir value and have the server back?
Let me know if you need any more details
SGIs this still an issue? If so, I would find msmdsrv.ini and make sure you don't have two folders listed in the BackupDir (or DataDir or TempDir). You'll have to runas Administrator to edit the msmdsrv.ini file and save changes. Once you fix that, it should
succeed.
http://artisconsulting.com/Blogs/GregGalloway
Maybe you are looking for
-
HT1766 how do i save my old photos and put it on the new device?
how do i save my old photos and put it on the new device?
-
Help, i have a question abou serialization
i am a newbie here. i use wsad to generate a web service from a simple java bean. And i can choose to generate a client proxy and the serialization related classes. But if i don't want to use this proxy in my client. What should i do? Say i use axis
-
Why I can't find my photo stream? I have 1000 photos in it but when I open it I only have 700?
I Have an iPhone6 and last night I mistaken log off my icloud id so when I log in again in my phone my some of my photos in photo stream are gone I used to have 1000 photos now I only have 700. And why everytime I delete a picture in camera roll it a
-
Imovie 11 hangs on start up - /Users
iMovie 11, Mountain Lion 10.8.1 on iMac Intel i7 8Gb RAM. Project and Events on 2Tb USB3.0 disk independent of MichintoshHD. Hanging on start up. Does not start to load the Project or Event Libraries. I have read various threads after Googling the is
-
Working web gallery file locations?
LR3's ftp is timing out so I need to upload the gallery files with an ftp client. However, I can't find where it's putting the files to be uploaded. Where does it put them in windows 7?