Non updated Idocs in BW

Hi Experts,
Error message i get is:
{IDocs were found in the ALE inbox for Business Information Warehouse that are not updated.
Processing is overdue. Process Idocs manually.}
Please suggest what can be the solution for this issue.
Thank you very much,
Neel

Hi Shu Moh / Pradip,
I am not able to see the radio button section for assigning points now, is there any problem?
I will not forget to reward points once it is ok.
Thanks a lot for your response
Neel
I was able to reward points.
Basis team is working on this issue, will post once the problem is figured.
Message was edited by: Neel

Similar Messages

Problem with non-updated idocs

Hi,
we have a problem after upgrading from 3.5 to 7.0. Lots of extractors end
in an error-message concerning non-updated idocs. Every day several
extractors have this problem. This are not always the same extractors. As
a result we must repair many extractions manually.
I know the procedure of how to repair, but I want te know how I can prevent
extractors from running into this problem in the first place.
Any suggestions?
This is the problem-message that we get...
Non-updated Idocs found in Source System
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.

It has been happening on our env as well (BI 7.0 SP 12), time to time one load or the other gets into this problem and it waits yellow for few hrs before turning red.
I can correct the IDOC and move on or run the load again it works fine.. but the process chain gets held up not going to the next stage for hrs..
any resolution on your problem..
thanks
Mayil

Non-updated Idocs found in Source System

Hi Experts,
I am getting an error Non-updated Idocs found in Source System
Plz help me to resolve this issue.

Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Hope it helps

R3 to BW Extraction fails: Non-updated Idocs found in Source System

We load data from R3 to BW and this process has been successful for the past few days except last night. The error msg is listed below in between two dashed lines:
Non-updated Idocs found in Source System
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.
I checked the system connection by right click the source system in the Source System page on BW and selecting "Check" and "Customizing for Extractors" from the context menu and find everything works fine.
Any idea about the IDOC thing?
Thanks

hi Subray/Bhanu,
With WE05, find some records with yellow status. How to find some missing data here?
With BD87, under BW system folder, there are two folders:
1. IDocs in outbound processing
2. IDoc in inbound processing
Under 1st folder, there is one yellow status folder called "IDoc ready for dispatch (ALE service)", continue to expand another folder called CREMAS under it, there is a blue information line which is "Receiver found , Data filtered , No conversion , No version change".
Under 2nd folder, there is one yellow status folder called "IDoc ready to be transferred to application", continue to expand other two folder under it called "BBPIV" and "RSRQST", find there is a red flash status line which is "No resources, immed. processing not possible: Too few free dialog work" under these two folders.
I need to go ahead to select these two red flash status lines and then press the Process button at the top bar?
Thanks
Message was edited by: Kevin Smith

Non-updated Idocs found in Business Information Warehouse

Hi,
I got the following error while trying to load data:
"Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse 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. "
Please help me solve this issue.

Hi,
Actually i tried all these options. I updated the idoc manually, and now the following message comes :
"Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
Data packets were found that have not yet been rea "
And the process is on for the past 5hours. Can i do something regarding this?

Idocs error: Non-updated Idocs found in Business Inormation Warehouse

Hi
I have found this error for delta load.
"Non-updated Idocs found in Business Information Warehouse"
I know that if the non-updated idocs found in source system, we can use
BD87 to manual update.
But it is with in the BI.
Can someone please help with steps involved.
Thanks

I will suggest you to set the delta load request to red and then reset the delta flag. Reload the last repested delta will include all missing idocs. That way it is much cleaner.
Good Luck,
CL

Key flexfield - protecting one of the segment as NON-UPDATABLE/ READ-ONLY

Key Flexfield setup for "People Group Flexfield" consists of seeg1,seg2,seg3,seg4.
We would like to make Seg1 of this flexfield "READ ONLY" / "DISPLAY ONLY" / "Non-Updatable".
Please advise possible way of making this functionality.
I have tried, following but no luck :
1) Limitations of Forms Personalization [ID 420518.1]
Forms Personalization is not possible for any key flexfield structure or segments.
This is a limitation of Forms Personalization on Flexfield. There was an enhancement request Bug 5506506 - "PERSONALIZE FLEXFIELDS BY USING FORMS PERSONALIZATION" but it was rejected the enhancement request as this is not feasible. A Flexfield is a single field in a form but then when you click into it and it opens up the flexfields window, the multiple fields you see is actually a user exit with multi segment values, not form fields. No Form Personalization events are passed to flexfield windows (user exits). No Form Personalization events are passed to segments inside the flexfield window (user exit).
2) Key Flexfield Security Rules Enabled
Defining security rules on any segment in key flexfield makes all segments as read only. Per Oracle Document:"Defining security rule on key flexfield combination on one or more segments allows all segments to be not updatable"

In SSHR, I believe it is possible although I have not done it before, I have spoken to people who have.
You need to have access to jDeveloper and be able to open up the SSHR page in question. Find the internal ID of the flex item within the SSHR page in question.
Then you create a new item in personalization and set that new item to have the same ID as you retrieved from jDeveloper. Make that item read only and configured the 'default' flex to not show the segment in question.
That is basically the way this can be achieved but it is not straightforward and requires a cursory understanding of OAF.
I do not know if it is possible to do this in the PUI. Would be interested to know requirement behind essentially showing a static read only field in a professional form - can the admins not be trusted to leave it alone? One workaround would be coding a user hook or custom library to error if that field is updated. Not read only but would stop those pesky Administrators meddling with it!

Error Loading Hierarchy Error when updating Idocs in Source System

Hello Friends,
I am loading hierarchy data using Info pac into 0FUNDS_CTR . I have selected a hierarchy under hierarchy selections tab in the Info pac .
All Partner profiles in WE20 seems OK . But When I loaded data , throwing errrr message as below
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
When I checked in TC WE05 says that IDoc: 0000000000355113 Status: Error during syntax check of IDoc (outbound) with status 26 .
Please advice .
Many thanks

Hi Krishna4bi,
Actually we will monitor idoc status in BD87 in SAP BI As well ECC , while extracting the data from source sytem if any idoc struck we will manually process in BD87 , But you are telling that while loading the datasource the error occurred , so please check once in ECC side . Otherwise see how many packets are still process, make it red that infopackage and do manually update.
Hope it helps,
By,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://bluemarlinsys.com/bi.

Error when updating Idocs in Source System - Urgent

Hi Team,
When i was loading the data from SAP R/3 to BW, i was facing the error "Error when updating Idocs in Source System" (0 From 0 Records).
When i check in the Environment>Transaction RFC->In the Source System, it was displaying the error--
<b>" Import container contains errors (are any obligato) in the Function Module: IDOC_ERROR_WORKFLOW_START_R".</b>
Can any one please help me to solve this error.
This is am Urgent requirement for me to deliver.
Thanks & Best Regards,
Venkata.

Hello VenkaTa,
How r u ?
The workflow settings are not proper it seems. Ask the BASIS people to correct the Work Flow Settings. Then try Updating the IDOCs manually.
Also check the Inbound and outbound IDOCs in the Source system. The outbound should contain some warnings or errors.
Best Regards....
Sankar Kumar
+91 98403 47141

Error when updating Idocs in Source System

Hi All,
We did a recent copy from QAS to DEV,after which am unable to run my process chains ,the load status still showin yellow signal,whereas job is getting finished but am unable to load datas to the targets. Am getting the following error message when i see the display message in process chain.
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
Error when updating Idocs in Source System
Could anyone please let me know what can be done ?
Thanks
con

Hello All,
I have same problem but its RESOLVED by the following process.
Step - 1
execute the Function module "SCP_LANGUAGES_IN_INSTANCE". It may or maynot give some output. Just note if it give the output
Step - 2
in Transaction SE38 execute the program "RSCPINST".
Just Click on the Activate button (dont select anything).
Step - 3
Again do the same thing specified in Step - 1. Now it will give the output saying that Language is DE.
So by the above procedure my issue is been resolved.
Regards
Sankar

Any FM/methods to update idoc segments without changing idoc status

Hi All,
My requirement is a reprocessor program which fills up some fields in the idoc segment before posting. So, after updating the segments, the idoc status should remain as before.
Is there any function modules or methods to update idoc fields in segments without changing the idoc status?
I have tried the FMs EDI_DOCUMENT_OPEN_FOR_EDIT, EDI_CHANGE_DATA_SEGMENT and EDI_DOCUMENT_CLOSE_EDIT, but it changes the idoc status.
Thanks,
Arun Mohan

As for FM to do this, i don't know if there are any, but i think you can go directly to the tables with the IDOC data and change them without triggering the changes in status like FM do. Still, i am not sure this is completely true, but you could give it a try. Also, i don't know if this is the best way to do it, because of those legal/audit questions mentioned by Thomas.
Here is a sample code of a program we have to change a field in a segment of WPUUMS.
*& Report YRE00021INTPG
REPORT yre00021reppg.
TABLES: edid4 ,
        edidc ,
        mean .
* Variaveis Auxiliares
DATA: t_edidc TYPE edidc OCCURS 0 WITH HEADER LINE.
DATA: t_edid4 LIKE edid4 OCCURS 0 WITH HEADER LINE .
DATA: BEGIN OF t_docs OCCURS 0,
        docnum LIKE edidc-docnum ,
      END OF t_docs.
DATA: wa_e1wpu02 LIKE e1wpu02 .
DATA: wa_e1wpu03 LIKE e1wpu03 .
DATA: t_itedidd LIKE edi_dd40 OCCURS 0 WITH HEADER LINE ,
      t_itedidc LIKE edi_dc40 OCCURS 0 WITH HEADER LINE ,
      fw_itedidc LIKE edi_dc40 ,
      fw_itedidd LIKE edi_dc40 .
DATA: l_matnr TYPE mara-matnr,
      l_tam TYPE i.
DATA: l_idoc_number TYPE edidc-docnum.
* Ecran de selecção
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_docnum FOR edid4-docnum ,
                s_credat FOR edidc-credat DEFAULT sy-datum ,
                s_cretim FOR edidc-cretim .
PARAMETER:      p_mestyp LIKE edidc-mestyp DEFAULT 'WPUUMS' ,
                p_status LIKE edidc-status DEFAULT '51' .
*SELECTION-SCREEN SKIP.
*PARAMETER:      p_ean11 TYPE mean-ean11.
SELECTION-SCREEN : END OF BLOCK b1.
AT SELECTION-SCREEN.
IF p_status <> '51'.
    MESSAGE e001(yre) WITH 'Apenas pode modificar IDOCS com erro'.
ENDIF.
IF p_mestyp <> 'WPUUMS'.
    MESSAGE e001(yre) WITH 'Apenas pode lançar WPUUMS'.
ENDIF.
*AT SELECTION-SCREEN ON p_ean11.
* SELECT SINGLE * FROM mean WHERE
*    ean11 = p_ean11.
* IF sy-subrc <> 0.
*    MESSAGE e001(yre) WITH 'Ean não existente'.
* ENDIF.
START-OF-SELECTION.
SELECT docnum INTO TABLE t_docs FROM edidc
                     WHERE status = p_status
                     AND   mestyp = p_mestyp
                     AND   docnum IN s_docnum
                     AND   credat IN s_credat
                     AND   cretim IN s_cretim .
CHECK sy-subrc = 0 .
LOOP AT t_docs.
    CLEAR : wa_e1wpu02.
    SELECT * FROM edidc INTO TABLE t_edidc
      WHERE docnum = t_docs-docnum.
    CHECK sy-subrc = 0.
    SELECT * FROM edid4 INTO TABLE t_edid4
                  WHERE docnum = t_docs-docnum AND
                        segnam = 'E1WPU02'.
    CHECK sy-subrc = 0.
    SORT t_edid4 BY segnum.
    LOOP AT t_edid4 .
      wa_e1wpu02 = t_edid4-sdata.
      WRITE wa_e1wpu02-artnr TO l_matnr NO-ZERO.
      CONDENSE l_matnr.
*      l_tam = STRLEN( l_matnr ).
*      IF l_tam <= 6.
        SELECT SINGLE ean11 INTO wa_e1wpu02-artnr FROM ytre00004 WHERE
          codcurto = l_matnr.
        IF sy-subrc = 0.
          WRITE : /1 'Código ', l_matnr, ' alterado para ', wa_e1wpu02-artnr.
        ELSE.
          WRITE : /1 'Código ', l_matnr, ' não encontrado na tabela de conversão'.
          CONTINUE.
        ENDIF.
*        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
*          EXPORTING
*            input = p_ean11
*          IMPORTING
*            output = wa_e1wpu02-artnr.
*      ENDIF.
      UPDATE edid4 SET   sdata   = wa_e1wpu02
                   WHERE docnum = t_edid4-docnum
                   AND   counter = t_edid4-counter
                   AND   segnum = t_edid4-segnum .
      IF sy-subrc <> 0 .
        ROLLBACK WORK .
        WRITE: / t_edid4-docnum .
      ELSE.
        COMMIT WORK.
      ENDIF.
    ENDLOOP.
ENDLOOP.
END-OF-SELECTION.

Setting check box (in detail block) as (non) updatable...

Hi,
I have a master-detail form. The form does execute a query when it opens. Now, according to a condition i want to do the check box(in detail block) as non- updatable.
I have tried to write the appropriate code in:
WHEN-NEW-RECORD-INSTANCE(in the master block level)
WHEN-NEW-ITEM-INSTANCE (in the detail block level)
POST-QUERY(in the detail block level)
but it does not work 'perfectly'. I mean that in most cases even one of the above triggers does not execute (for example the 'WHEN-NEW-RECORD-INSTANCE' but only after i click on this new record instance. I mean that after this on this new record the condition is estimated....)
or
it does execute but after i click on the checkbox (for example the 'WHEN-NEW-ITEM-INSTANCE').
The code i tried looks like the following:
if :block.item=<condition>
then
set_item_property ('detail_block.chk_box',updatable,property_false);
else
set_item_property ('detail_block.chk_box',updatable,property_true);
end if;I consider to use the WHEN-CHECKBOX-CHANGED trigger and code which looks like:
if <condition>=true
then
    /*i set the value of the checkbox as the opposite of what it is just after the click on it...*/
if :detail_block.chk_box=0
   then
     :detail_block.chk_box=1;
else
    :detail_block.chk_box=0;
end if;
set_record_property(currect_record,status,query_status);
set_item_property ('detail_block.chk_box',updatable,property_false);
end if;The truth is that i do not like very much this code, but is there any alternative...???
Note: I use Dev6i with patch 12
Thank you,
Sim

I build a little testform based on HR-schema-table DEMO_USERS and switch each second record to be not updateable, works without problems (code from POST-QUERY-trigger):
DEFAULT_VALUE('1', 'GLOBAL.SWITCH');
:GLOBAL.SWITCH:=3-:GLOBAL.SWITCH;
IF :GLOBAL.SWITCH=2 THEN
SET_ITEM_INSTANCE_PROPERTY('DEMO_USERS.ADMIN_USER', TO_NUMBER(:SYSTEM.TRIGGER_RECORD), UPDATE_ALLOWED, PROPERTY_TRUE);
ELSE
SET_ITEM_INSTANCE_PROPERTY('DEMO_USERS.ADMIN_USER', TO_NUMBER(:SYSTEM.TRIGGER_RECORD), UPDATE_ALLOWED, PROPERTY_FALSE);
END IF;     Edited by: Andreas Weiden on 31.03.2009 21:24

How to make a record as Non Updatable

Hi all
I want to make the whole record(multi record block) as non updatable. My condition is, I have one status field in the base table block, when I query the form if the "status" field containing value 'Y', the user should not be able to update any item in the record. How to acheive the functionality?
Thanks in advance
ram.

Hi,
Have you tried using the set_item_instance_property('',update_alowed,..) built_in in the when_new_record_instance trigger on the block level?
You can check there the :block.status field,and set the item instances in that record to non updatable.

How to create editable form with non-updatable vo

Hi,
i need to create a new form on non-updatable VO.
My requirement is: i have Data base View, based on that view i have created VO, based on this VO i need to create new form, when ever i submit a request, web service will invoke and that validate the data and sends to the data base.
when ever i drag drop the vo i couldn't able to enter any data bcoz all the data are coming in the form of output boxes.
can any one help how can i create this.

Check the setting of your viewobject attributes settings, most probably they are 'updatable never', set them to "updatable always".
This way you can drag the view as an editable form.
About sendind data to the database, i guess you have an idea how to do it afterwards :)

Display description, but non-updatable data block

To display my Item_Description, I've created a post-query trigger to lookup Item_Description based on Item_Num, which works fine, except if the user does not have update priveledge. By default the data block is non-updatable. If the user has update, then the block is set updatable at run-time.
Problem is, for a non-update priveledge user, the form errors when the trigger attempts to set the description field. [Even though the field is set updatable by default.]
What am I missing? Thanks.

I'm confused. You say:
"By default the data block is non-updatable."
but then you say:
"...the field is set updatable by default."
If the data block is not updateable, then you can't make the item updateable.
Assuming the default is non-updateable, and a user does not have update privilege, then the error message you are getting is correct because the trigger is trying to do an update when the item is non-updateable.
If you need the trigger to do an update, then you need to make the item updateable. If you don't want the trigger to do an update for this user, then first check if the item is updateable (use the get_item_property), and if it is updateable, then let the trigger do the update.
Message was edited by:
Mark Roberts

Non updated Idocs in BW

Similar Messages

Maybe you are looking for