Delta error in production

Hi,,,
we are updating one cube through DSO during last delta its showing reuest to be red n wen we see the monitor screen its showing yellow.... plz let me know what steps shud be taken to repeat delta at DSO itself .
urgent
help wud b appreciated

Chk for any jobs in SM37 or any background process related to the load in SM66 or SM50. In datatarget if the load is running for long time it might change to red..that doesnt mean the laod has failed. Chk for any hanged IDOCS in sm58.
Regards,
B

Similar Messages

Most common BW data load errors in production and how to solve them ..

Hi All,
Most common BW data load errors in production and how to solve them ..
Any doc on it ,if so plz send it across to this id [email protected]
Thanks in advance.
Rgrds
shoba

hi
1) RFC connection lost.
2) Invalid characters while loading.
3) ALEREMOTE user is locked.
4) Lower case letters not allowed.
5) While loading the data i am getting messeage that 'Record
the field mentioned in the errror message is not mapped to any infoboject in the transfer rule.
6) object locked.
7) "Non-updated Idocs found in Source System".
8) While loading master data, one of the datapackage has a red light error message:
Master data/text of characteristic 'so and so' already deleted .
9) extraction job aborted in r3
10) request couldnt be activated because theres another request in the psa with a smaller sid
11) repeat of last delta not possible
12) datasource not replicated
13) datasource/transfer structure not active ´
14) Idoc Or Trfc Error
15. ODS Activation Error

Errors in Production

Hi Friends,
Pls any one send me Errors in production with solutions.
Regards
Ramana

hi ramana
HI,
"Job Termination in the R/3 Source System
u2022 The Exact Error message is ""Job termination in source system"". The exact error message may also differ, it may be u201CThe background job for data selection in the source system has been terminatedu201D. Both the error messages mean the same. Some times it may also give u201CJob Termination due to System Shutdownu201D.
u2022 The message appears in the Job Overview in RSMO, or in u201CDisplay Messageu201D option of the Process in the PC.
" "u2022 If the job in R/3 system cancels due to some reasons, then this error is encountered. This may be due to some problem in the system. Some times it may also be due to some other jobs running in parallel which takes up all the Processors and the jobs gets cancelled on R/3 side.
u2022 The error may or may not be resulted due to Time Out. It may happen that there would be some system issues like locks/DB Issues in the source system
" "u2022 First check the job status in the Source System. It can be checked through Environment -> Job Overview -> In the Source System. This may ask you to login to the source system R/3. Once logged in it will have some pre-entered selections, check if they are relevant, and then Execute. This will show you the exact status of the job. It should show u201CXu201D under Canceled.
u2022 The job name generally starts with u201CBIREQU_u201D followed by system generated number.
u2022 Once we are confirm that this error has occurred due to job cancellation, we then check the status of the ODS, Cube under the manage tab. The latest request would be showing the QM status as Red.
u2022 We need to re-trigger the load again in such cases as the job is no longer active and it is cancelled. We re-trigger the load from BW.
u2022 We first delete the Red request from the manage tab of the InfoProvider and then re-trigger the InfoPackage.
u2022 Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
"Transact RFC Error u2013 Non Updated IDOCs in the Source System.
u2022 Message appears in the bottom of the u201CStatusu201D tab in RSMO. The error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted.
u2022 Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them.
" u2022 tRFC u2013 Transact Remote Function Call Error, occurs whenever LUWu2019s (Logical Unit of Worku2019s) are not transferred from the source system to the destination system. "u2022 Once this error is encountered, we could try to Click a complete Refresh u201CF6u201D in RSMO, and check if the LUWu2019s get cleared manually by the system.
u2022 If after u201Ccoupleu201D of Refresh, the error is as it is, then follow the below steps quickly as it may happen that the load may fail with a short dump.
u2022 Go to the menu Environment -> Transact. RFC -> In the Source System, from RSMO. It asks to login into the source system.
u2022 Once logged in, it will give a selection screen with u201CDateu201D, u201CUser Nameu201D, TRFC options.
u2022 On execution with u201CF8u201D it will give the list of all Stuck LUWu2019s. The u201CStatus Textu201D will appear Red for the Stuck LUWu2019s which are not getting processed. And the u201CTarget Systemu201D for those LUWs should be the BW Production system. Do not execute any other IDOC which is not related have the u201CTarget Systemu201D.
u2022 Right Click and u201CExecuteu201D or u201CF6u201D after selection, those LUWu2019s which are identified properly. So that they get cleared, and the load on BW side gets completed successfully.
u2022 When IDocs are stuck go to R/3, use Tcode BD87 and expand u2018IDOC in inbound Processingu2019 tab for IDOC Status type as 64 (IDoc ready to be transferred to application). Keep the cursor on the error message (pertaining to IDOC type RSRQST only) and click Process tab (F8) . Ths will push any stuck Idoc on R/3.
u2022 Monitor the load for successful completion,
and complete the further loads if any in the Process Chain.
"No SID found for a characteristics
For example consider a Transactional Data load has failed due to no SID found for the characteristic 0Customer." It might happen that the Master Data 0Customer was loaded much before the transactional data load and by the time the transactional data load was started some transactions has taken place in the OLAP sytem and a new Customer has got created. As a result the Transactional Data load which would try to get the SID for the master data would not find it would fail. Check for the Master data in the R3 system if the data is available in the R3 system load the Master data in BW and then manually load the transactional Data. If the master data is not present in the R3 system also then itu2019s a data issue and needs to be reported to OSC or the Client.
"Attribute Change Run failed - ALEREMOTEBW was locked.
u2022 The message appears in the Job Overview in RSMO, or in u201CDisplay Messageu201D option of the Process in the PC.
u2022 The exact error message would be like, u201CUser ALEREMOTE locked the load of master datas for characteristic 0CUSTOMERu201D. Here it is specifically for the 0CUSTOMER load. It may be different related to Master Data InfoObject which is getting loaded. " During the Master data Loads, sometimes a lock is set by the system user ALEREMOTE. This happens because the HACR is runnning for some other MD load at the same time when the system tries to carry out the HACr for this new MD. This is scheduling problem as due to the time clashing the error has occured. "
u2022 Check the error message completely and also check the long text of the error message, as it will tell you the exact Master Data which is locked by user ALEREMOTE.
u2022 The lock which is set is because of load and HACR timing which clashed. We first need to check RSA1 -> Tools -> HACR, where in we would get the list of InfoObjects on which HACR is currently running. Once that is finished only then, go to the Tx Code SM12. This will give you few options and couple of default entries. When we list the locks, it will display all the locks set. Delete the lock for the specific entry only else it may happen that some load which was running may fail, due to the lock released.
u2022 Now we choose the appropriate lock which has caused the failure, and click on Delete. So that the existing lock is released.
Care should be taken that we do not delete an active running job. Preferable avoid this solution
u2022 When HACR finishes for the other Master Data, trigger Attribute change run fot this Master Data.
No Data found in the soucre system It may happen that there is transaction which has taken place for particular load. Or incase of delat loads there is no changes. This would result in giving anerror message as "No data available in the source system". As a result the load would remaing hanging ie the QM status would be yellow and if not changed then the load would fail due to processing overdue. Extract the data in the source sytem and check whether the data is actually present or not. If the load is getting the data from a flat file go to the Application server i.e transaction AL11 and go to the relevant path and check whether if data is present. If data is not present then change the QM status to manually green. If the data is available check for the extractor job failure.
srinivas reddy
Posts: 40
Registered: 7/11/07
Forum Points: 0
   Re: errors
Posted: Jun 13, 2008 3:41 PM    in response to: Shashank Dighe       E-mail this message      Reply
can u tell me the solutions for above lock issues, no app found data , idoc/trfc errors
Bala Murugan A.J
Posts: 462
Registered: 9/27/07
Forum Points: 864
   Re: errors
Posted: Jun 13, 2008 4:10 PM    in response to: srinivas reddy       E-mail this message      Reply
1) IDOC or TRFC Error
We can see the following error at u201CStatusu201D Screen;
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.
Analysis:
If we see at the error message we find that the failure is due to Non-arrival of IDOCs from Source System to BW.
Action to be taken:
Reload the Master Data manually again from Info-package at RSA1.
2) PROCESSING IS OVERDUE FOR PROCESSED IDOCs
Diagnosis
IDocs were found in the ALE inbox for Source System that are not
Updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.
Analysis:
After looking at all the above error messages we find that the IDocs are found in the ALE inbox for Source System that are not Updated.
Action to be taken:
We can process the IDocs manually as shown below:
3) ERROR AT SOURCE SYSTEM ASKING FOR REPLICATION OF DATASOURCES
Analysis:
If we see at the error message we find that the System is asking us to Replicate the Data Source System.
Action to be taken:
Go to RSA1 initial Screen & press Source System tab at LHS.
Once Replication is done we have to activate the Transfer Structures in Production System. For this we have to execute a program SE38 in BW On executing we will get the following screen:-
Once you have Replicated the Data-Sources & Activated the Transfer Structure you can reload the data manually by Executing the Info-package at RSA1.
4) LOCK NOT SET FOR LOADING MASTER DATA ( TEXT / ATTRIBUE / HIERARCHY )
Reason for Failure:
Diagnosis
User ALEREMOTE is preventing you from loading texts to characteristic
0COSTCENTER . The lock was set by a master data loading process with the
request number (DataPcakage number)
REQU_3VB1GNF0FGRRV84IUWGFOIIG7(000001) on 20041001,071055(985111) .
System response
For reasons of consistency, the system cannot allow the update to continue, and it has terminated the process.
Procedure
Wait until the process that is causing the lock is complete. You can call transaction SM12 to display a list of the locks.
If a process terminates, the locks that have been set by this process are reset automatically.
Analysis:
After looking at all the above error messages we find that the user is u201CLockedu201D.
Action to be taken:
Wait for sometime & try reloading the Master Data manually again from Info-package at RSA1.
5) DATA ERROR
Analysis:
After looking at all the above error messages we find
1st u2013 That it is a PC File Source System.
2nd - That there are Duplicate Data Records leading to error.
Action to be taken:
We have to delete this Request & then rectify the Data in the Data source at the Source System Level. After this we have to manually load the data.
6) OTHER TYPE OF DATA ISSUE
l Error Message
Diagnosis
1 data records were marked as incorrect in the PSA. The additional checking and processing of the 2 data package was terminated in a customer routine. This was done intentionally or was due to a short dump being intercepted.
System response
The data package was not updated.
Procedure
Correct the incorrect data records in the data package (for example by manually editing them in PSA maintenance). You can find the error message for each record in the PSA by double-clicking on the record status.
Analysis:
After looking at all the above error messages we find that the PSA contains incorrect record.
Action to be taken:
To resolve this issue there are two methods:-
i) We can rectify the data at the source system & then load the data.
ii) We can correct the incorrect record in the PSA & then upload the data into the data target from here.
Resolution: - We will see how to do the go for the 2nd method: -
7) ERROR WHILE LOADING PC FILE FROM DESKTOP / APPLICATION SERVER
Analysis:
After looking at all the above error messages we find
1st u2013 That it is a PC File Source System.
2nd u2013 For uploading data from the PC File it seems that the file was not kept at the application server & the job was scheduled in Background.
Action to be taken:
For running the job in Background Transfer file to Application server & then load it from there.
OR Else if you want to load file from your desktop then donu2019t schedule the job in background instead select u201CSchedule Immediatelyu201D option in the Info-Package.
8) JOB FAILURE AT SOURCE SYSTEM
Analysis:
Diagnosis
The background processing was not finished in the source system.
It is possible that the background processing in the source system was terminated.
System response
There are incomplete data packets present.
Further analysis:
Go to the background processing overview in the source system. You can get to this with the Wizard or the menu path Environment -> Job Overview -> In the source system (This is the alternate path to see the u201CJob Overviewu201D at the Source System.
Once there, check whether the background job really was terminated.
Note
Please make sure that the correct date of request has been selected in the selection screen of the overview.
Action to be taken:
At source system you can see the reason for the Job Failure. Thus we need to take the action accordingly.
9) ERROR ASKING FOR INITIALIZATION
Analysis:
After looking at all the above error messages we find that if we want to load data with the delta update you must first initialize the delta process.
Action to be taken:
If you want to load data with the delta update you must first initialize the delta process.
Afterwards the selection conditions that were used in the initialization can no longer be changed.
But Initialization is a typical process that should not be carried out without confirming with the onsite person in any case.
10) ERROR RELATED TO ACTIVATION
Analysis:
Here we can see that the Activation of ODS has failed as the Request Status in the ODS may not be green.
Action To be Taken:
Go to RSA1 Select your ODS Object  Right Click on it & Select u2018Manageu2019.
Select the Red Request & see the reason for its failure.
Rectify the error & then go for its activation.
Error message when processing in the Business Warehouse
Diagnosis
An error occurred in the SAP BW when processing the data. The error is documented in an error message.
System response
The error message(s) was/were sent by:
Second step in the update
Second step in the update
Second step in the update
Second step in the update
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box and select the long text for further information.
Follow the instructions in the message.
11) TRANSACTION JOB FAILES GIVING MESSAGE : u201CNO SID FOUND FOR CERTAIN DATA RECORDu201D
Action to be taken:
Load Master data KU. To load it, select its Infopackage & at schedule tab select u201CImmediateu201D & start loading.
After this come to RSMO & select this failed job.
Click on Detail tab.
Since in this case we see that the data is only getting loaded in ODS & not in PSA thus we have to reload data manually through Infopackage.
If we have PSA here then we need to take the following action:
1) Expand nodes under Detail tab.
2) Expand node u201CProcessing (data packet): Everything OKu201D
3) Right click on u201CData Package 1 : Everything OKu201D under it.
4) Select Manual update option in the dropdown menu.
Hope it helps

Processchain errors in Production and how to solve those issues

Dear All,
Please share some process chain errors in production and how to solve those errors as well,
Please send me if any one have the list of errors and how you are solved those..
I am very new to BW,am also preparing my list of errors and solutions to fix them..Please share me if any one have ?
Thanks

Hi
Table of Contents
1.     Time stamp error     2
2.      PSA error records     4
3.      SID not found for characteristic     7
4.      Error calling number range object     8
5.      Trfc error     10
6.      ALE REMOTE lock     13
7.      Delta fails     14
8.      Deleting setup table     18
9.      How to run statistical setup for different Application components     19
10. How to do selective deletion     22
11. Roll up     24
11. Compression or collapse     25
12. How to do Attribute change run     27
1.Time stamp error
Resolution procedure
Go to RSA1Source system
Run program RS_TRANSTRU_ACTIVATE_ALL
Mention source system and Info source and then execute.
Now the transfer structure will be automatically activated.
Then proceed with the reload, it will get success now.
2. PSA error records
Go to details tab, we will find its packet no. and its record no.
Resolution procedure
Click on PSA icon in monitor and select the error data packet
Double click on error record and edit it to the correct value,
select save.
Now update from PSA to target by selecting the option Start update immediately.
3. SID not found for characteristic
Resolution procedure
a. Remove the failed request from data target by making its QM status into red.
b. Load Master data for characteristic using full update.
c. Then reload the transactional data.
4. Error calling number range object
Resolution procedure
Note down the assigned dimension into the cube for 0VAL_TYPE
copy the dimension name
Go to RSRV transaction
Tests in Transaction RSRV -> All Elementary Tests ->Transactional Data then double click on Comparison of Number Range of a Dimension and Maximum DIMID- then click on the right pane in same->Mention the cube name and dimension name, click on enter.
Then click on correct error. It will correct the error.
5. Trfc error
Resolution procedure
Go to SM58
Go to edit->Execute LUW.
Then do refresh in monitor.
Now it will pick the records and the load will get success.
Some times we found that some packets will not get updated even if the extraction is showing as complete.
Do manual update of each packet
6. ALE REMOTE lock
Resolution procedure
This can happen when user or ALEREMOTE is accessing the same table
a.     Remove failed request from data target by making its QM status into red.
b.     Check into sm12 and delete the lock, usually the BASIS deletes them
c.     Reload the package
7. Delta fails
Resolution procedure
R/3->BW
Data is coming from R/3 then make the request technical status red in monitor and remove the request from manage.
go to info package restart the load, then you will get a pop up saying that repeat of last delta click on request again.
Go back to manage and look for the delta type, it will show as Repeat of last delta.
BW->BW(Data mart)
Delta load failed from ODS to cube/any data mart.
Make its technical status as red
Go to manage and remove the failed request by making its QM status as red.
It is updating from ODS, so we have to remove the data mart status in ODS manage, before restarting delta
If you click on data mart status it will pop up a window
Click on delete icon, select YES and then ok.
Now refresh manage the data mart status will get deleted.
If you load now the failed delta will get success.

Error reading product file driver files

When attempting apply a large merge patch I receive the following error:
Screening out files not valid for this installation...
Determining valid on-site files...
AutoPatch error:
The following file is missing:
/oracle/prodappl/pa/11.5.0/admin/driver/pasb038.drv
AutoPatch error:
Error reading product file driver files [complete; make tapes]
AutoPatch error:
Error determining valid on-site files
Any ideas?
I've tried using options=noprereq option, but that didn't help.

- Try to restore the file from a backup you have Or just copy it from any other environment.
- Make sure that you have included all pre-req patches in the merged file.
I've tried using options=noprereq optionBy this you tell adpatch not to check for pre-req, use 'options=prereq' instead.

Sales Order Error Message 'Product does not exist in system'

Hi Gurus,
we recently upgraded from CRM 4 to 7.0. There is a ECC attached (which was also upgraded from 4.7 to 6.0 before).
Scenario: materials are replicatd from ECC to CRM. All mandatory customizing objects were initially loaded succesfully.
Because of the upgrade we already have "old" products in CRM. We requested a single product from ECC, the bdoc went through with green. The product can be found via commpr01 and also on database in comm_product. But when try to add the product to an sales order e.g. quotation, it gives the error message "product does not exist in the system.
We then tried to delete that product using the report com_product_delete_single. When entered the selection criteria for that report, we used the f4-valuehelp to enter the product. We found the product and then executed the report. But gives the message 'product not found'.
We also created a product for testing purposes directly in crm, but it shows the same behaviour in sales orders and for the deletion report.
Please help me with that issue. Your help will be highly appreciated!!!
Kind regards
Hannes

Solved with the help of SAP.
Keywords: COM_PRODUCT
COM_PRODUCT_GUID_GET_INTERNAL
CONVERSION_EXIT_PRID1_INPUT
CRM_ORDERADM_I 501
Relevant notes:
Note 1449146 - Dump While Creation IP via WebUI
Note 1445079 - Unable to add products to contract
The notes do not exactly described our issue but the code corrections were still relevent for us.

Error - Update Product Data in Solution Manager

Hello,
We are currently downloading the Enhancement Package 4 in SOLMAN via Maintenance Optimizer, however, after choosing the Technical Usages in step 2.1, it shows an error in step 2.2 (Select OS/DB Dependent Files):
Error : Update Product Data in Solution Manager
Has anyone encountered the same problem? Would it be fine to continue on the next step after selecting the files which you need for your operating system-database combination.
Any information is highly appreciated. Thank you.

Hi Jaypee,
Check guide How-To Install EHP4- A practical guide. Solution of this problem is documented there. you can download it from http://service.sap.com/erp-ehp
Extract from this guide for this problem:
Make sure that you update the product data in SAP Solution Manager. This is described in SAP Note 1277035 which is referenced from the collective SAP Note 1122966. If you do not update the product data, you might get an error message after the stack calculation. The message text explains the problem in more detail.
Thanks
Sunny

Valuation with material cost estimate: error with product

Hi Experts,
Message no. KE350, Valuation with material cost estimate: error with product "2286940000". Please suggest me to resolve this issue.
Points will be provided for good solution.
Regards,
Jay

Hi Jaya
This means that your customization is wrong then...
In KE4J or KEPC you have assigned costing keys to your material types or some other combination... You should have done this config in a way that costing key is not called for in the case of non valuated materials...
In Ke40 you have defined costing key where in you have specified "Issue error msg if no cost estimate found".. This costing key is assigned in KE4J or KEPC in a way that it is getting called even in case of non valuated materials...
Do you have a separate mat type for non valuated material? If yes, remove this mat type from KE4J/KEPC..
If you dont have separate mat type i.e. in the same mat type if you have both valuated and non valuated, then you have a problem.. You would get stuck in that case
Regards
Ajay M

Valuation with material cost estimate: error with product "117122"

Hi people,
We have the error:
=====================
Valuation with material cost estimate: error with product "117122"
Diagnosis
In Profitability Analysis (CO-PA), the system tried to valuate a line item using the current standard cost estimate.
In order to determine the current plan period, the system needs to read the valuation segment of the material master.
The system has found that the current plan period is not filled forproduct "117122" in plant "UBE1".
We have the follow configuration in trans.: KE40:
. Determine material cost estimate
   . Transf. Standard Cost Estimate
. Costing Variant
. Control Data for Standard Cost Estimate
   . Period Indicator = "Current Standard Cost Estimate acc. to entry in mat master
. Addiitonal data CO-PC
    . Transfer cost estimate in controlling area currency "activated"
We think the reason about our error is because the field above is activated and some configuration more is necessary for this case. For examplo: Trans.: OKYW and this one was not configurated yet.
Do you know what happend?
If we need to configure some transation, or sonly process the cost estimate?
Thanks,
Rosana.

Hello Guido
Thank you very much for your return.
It is happenning in a Client that some people are doing the configuration.
Before we didin't have in KE40, the fiel "Transfer cost estimate in controlling area currency" activated.
And now, the people activate that in this new Client and I don't know the impact about that.
I think we have to make the configuration in OKYW.
The other transation you told me, we don't have any information.
Could you tell me some other idea what happend?
Message error is just "Message no. KE350"
Abou claculate the cost:
It was calculated by trans.: CK11N for future planning and the real wasn't not possible to release because this material already have moviments.
Could you tell us is there is some thing more to do?
Thanks,
Rosana.

Valuation with material cost estimate: error with product " 200038 "

Hi,
I am getting an error:
Valuation with material cost estimate: error with product " 200038 " (Message KE350).
Kindly assist on the same?

If this material is mto material go to t.code KE40 and maintain define access to standard cost estimate define cost key with
"Transfer sales orde cost estimatex".
If it is mts material define costing key with Transfer std cost estimate and in costing data
costing variant : ppc1
costing verstion: 1
period indicator: Release std cost estimate matching with goods issue or material costing matching posting date.
This will resolve ur problem.

Error in Production Load: Error passing data to port

Hello All,
I got this unexpected error in production. The Jobs are still processing for a long time(in Yellow status) with the error message :
Extraction (messages): Missing messages      (Status:Yellow)
     Missing message: Request received      (Status:Yellow)
     Missing message: Number of records sent     (Status:Yellow)
     Missing message: Selection Completed     (Status:Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings           (Status:Yellow)
     Request IDoc : Application document posted                (Status:Green)
     Info IDoc 2 : sent, not arrived ; Error passing data to port      (Status:Yellow)
     Info IDoc 3 : sent, not arrived ; Error passing data to port      (Status:Yellow)
     Info IDoc 1 : sent, not arrived ; Error passing data to port      (Status:Yellow)
I went through the below forumn, and asked the basis to look in to it. In the meantime can any one please suggest me any solutions.
Some problem with IDoc's Settings while loading data

Hi Ram,
The problem may be with the connection to the source system you are loading the data from. You can check the connection using the note 140276.
Best Regards,
Des.

Error in production environment

Hi,
We are getting Error in production following environment. Anyone knows the reason of error ?
(internal)     06.25 06:43:40.779     IdcServerThread-751869     !csPageMergerUnableToGenerateHtmlPage!csSystemError,\!syServiceRuntime\,java.lang.IndexOutOfBoundsException: Index: 7\\\, Size: 7
     at java.util.ArrayList.RangeCheck(ArrayList.java:546)
     at java.util.ArrayList.get(ArrayList.java:321)
     at intradoc.data.DataResultSet.getStringValue(DataResultSet.java:1902)
     at intradoc.data.ResultSetUtils.getValue(ResultSetUtils.java:371)
     at intradoc.server.PageMerger.getValueFromDataClassEx(PageMerger.java:879)
     at intradoc.server.PageMerger.getValueFromDataClass(PageMerger.java:768)
     at intradoc.server.PageMerger.appGetValue(PageMerger.java:546)
     at intradoc.common.DynamicHtmlMerger.computeValue(DynamicHtmlMerger.java:1308)
     at intradoc.common.DynamicHtmlMerger.evaluateGrammarElement(DynamicHtmlMerger.java:800)
     at intradoc.common.DynamicHtmlMerger.substituteVariable(DynamicHtmlMerger.java:597)
     at intradoc.common.DynamicHtml.substituteVariable(DynamicHtml.java:1244)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:986)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1006)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1050)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1086)
     at intradoc.common.DynamicHtml.outputHtmlEx(DynamicHtml.java:1019)
     at intradoc.common.DynamicHtml.outputHtml(DynamicHtml.java:906)
     at intradoc.server.Service.outputHtml(Service.java:1500)
     at intradoc.server.Service.merge(Service.java:1480)
     at intradoc.server.Service.buildResponsePage(Service.java:1249)
     at intradoc.server.Service.doResponse(Service.java:1868)
     at intradoc.server.FileService.doResponse(FileService.java:1408)
     at intradoc.server.Service.sendErrorEx(Service.java:1755)
     at intradoc.server.ServiceRequestImplementor.handleErrorResponse(ServiceRequestImplementor.java:1499)
     at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:674)
     at intradoc.server.Service.doRequest(Service.java:1707)
     at intradoc.server.ServiceManager.processCommand(ServiceManager.java:359)
     at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)
(internal)     06.25 06:44:13.575     Archive lock     Thread maintaining archive lock is not receiving enough CPU cycles.

Hi,
Looks like you are doing Archiving documents/content at your server. By looking at the message "Archive lock Thread maintaining archive lock is not receiving enough CPU cycles." CPU utilization is very high.
Make sure when you are running any Archive at the production server is idle. You can also do this activity during non-business hours.
Thanks,
Ravinder

I am using Mac OS X 10.7.5 as of now and when I am trying to upgrade to Mavericks, it is throwing error "The product distribution file could not be verified. It may be damaged or not signed".

I am using Mac OS X 10.7.5 as of now and when I am trying to upgrade to Mavericks, the App Store is throwing error "The product distribution file could not be verified. It may be damaged or not signed".
Is there anything I should do differently? Is anyone else facing the same issue?
Kindly help.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Step 1
Triple-click anywhere in the line of text below on this page to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -ef
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting. A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
Step 2
Repeat with this line:
{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo; sudo defaults read com.apple.loginwindow LoginHook; echo; sudo crontab -l; } 2> /dev/null | open -ef
This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.
Step 3
{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; echo; crontab -l 2> /dev/null; } | open -ef
Step 4
ls -A /e*/{cr,la,mach}* {,/}Lib*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -ef
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.
Step 5
osascript -e 'tell application "System Events" to get name of login items' | open -ef
Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.
You can then quit Terminal.

XML errors message (Product key not found/Invalid) in SNC5.1

Hi,
I am working on SNC project which includes POC scenario.I have completed all the required configuration in R/3 4.6c and SNC5.1 system. The master data (mat, plant,vendor and Info records) are CIFed from R/3 to SNC, BP and MoT created in SNC. All the MD BAdIs are implemented in SNC. I am trying to post a PO from R/3 to SNC, IDOCS are successfully generated, PI has converted the IDOCS into XML messages, but i am getting XML error in SNC system (sxmb_moni) which states-
1) Product key 000000000123456 (category ID) not found
2) Item 00001: Product is missing or invalid
3) Order, item 00001: Product 000000000123456 does not exist
4) BOL processing failed. XML-message inbound processing has been terminated.
I am able to post the PO successfully in SNC Web UI which has alpha numeric product number (eg- 1120-110), but products with numerical value leading zeroes (eg- 000000012345) do not get posted. These product IDs give error in SNC sxmb_moni.
I have set up the output format of product number with 40.
Appreciate your help.
Is there any kind of configuration required for leading zeroes in any of the systems (R/3,PI or SNC)
Appreciate your help.
Regards,
Edited by: Dmohite on Jun 11, 2009 11:09 PM

Hi Bharath,
Were you able to over come the error for products in the XML message? I have same issue, can you please briefly point me in right direction?
I am facing the error message " Product key 0000000000xxxxxxx (category ID) not found". can you please briefly mention how did you resolve?
In my case, the XML message had product number '000000000070000598' and I tried to implement BAdI to make the product number appear as '70000598' and still it failed.
Thank you in advance
Best regards
Vivek
Thank you in advance.
Best regards
Vivek

Error :Check product hierarchy for uniqueness

Dear all ,
load is failing with below message
Error:Check product hierarchy for uniqueness.
please suggest
Regards,
Puru

Hi Purshottam,
Check the technical names of the hierarchy nodes. They should not be same.
This issue is faced when technical names of the hierarchy nodes are same.
To solve this issue, modify the technical names of your hierarchy nodes and then try loading the hierarchy.
Thank you,
Ketan Z

Delta error in production

Similar Messages

Maybe you are looking for