cancel
Showing results for 
Search instead for 
Did you mean: 

BI Idoc error

Former Member
0 Kudos

Hi all,

When I started the SD transactional process chain, most of the info package errored up. The error message states:

Transfer (IDocs and TRFC): Errors occurred

Request IDoc : IDoc with errors added

also I checked the RFC source system connection, everything its working fine.

Please share your ideas and suggestions......... thanks very much for your time.......

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Ram,

check youe selection criteria in SM58..you should maintain correct user id (generally ALEREMOTE) and date to see the idocs.

Thanks..

Shambhu

Former Member
0 Kudos

Hi Shumbhu,

I tried giving ALEREMOTE, BWREMOTE......... with different dates (also witn no dates )....... *BUT NO LUCK in SM58

Former Member
0 Kudos

I could'nt see any entry in SM58

Former Member
0 Kudos

Check the trfc queue on R3 - have you got a calendar problem?

Former Member
0 Kudos

Hi Simon,

I have no authorization for SM58 in ECC (Quality)........ I have asked my TL to try......

In BW - SM58 the last errored LUW is listed as last month..... my yesterday's failed idoc is not listed.......

Please let me know if I am doing any mistakes or any other suggestions .....

Thanks for ur time

Former Member
0 Kudos

whilst that is happening

Have you checked the jobs in R3 and BW (use the menus in the infopackge to go straight to them)

Sm21 have any errors?

etc

Former Member
0 Kudos

Hi All,

This is the error message displayed in the Process Chain:

****************************************************************************************************

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.

Error when updating Idocs in Source System

Former Member
0 Kudos

Can any body help how to check the extraction monitor in Source System

Former Member
0 Kudos

All explained above

Ignore the process chain (that tells me nothing)

Go into the infopackage - go to the menu options

display jobs in OLTP and BW

then check the sm21 records

Former Member
0 Kudos

Hi all,

thanks for all your help........... I reported the issue to Basis. They are working on this issue.......as no Idoc is been send to BW from ECC......

Let u all know .. why this problem occured once its finished..........

Thanks

Former Member
0 Kudos

Problem solved..........

Its actually the Basis issue...... They copied the Production system to Quality for some security purpose.........Hence some of the parameters like Partner profile etc... are pointing to Production system......

They resolved and gave the system back......... Thanks once again for all ur inputs to this issue...

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello all......... Thanks for your suggestions.

Chandrasekar : I tried replicating the datasource and ran the process chain. It again failed at the same step

Aanand: According to ur suggestion I executed the report RBDAGAIN and the Idoc number ( BW Idoc - got from the monitor screen). But it saus No data is selected.

Can you please let me know whether I gave the right Idoc number? Is the OSS note which you refered is related to this problem ?

Shambhu Kumar: I went to the SM58 in BW , there is no entry listed there ? Is there any problem which should be solved by the Basis.

Thanks again for all ur inputs...... Hope to solve this thread soon...

Former Member
0 Kudos

Go to SM58..in source and target system.....select the Idoc and process them manually...by pressing F6.

Thanks...

Shambhu

former_member204514
Contributor
0 Kudos

Hi Ram,

Try to reprocess the errored IDocs,

Run the report 'RBDAGAIN' which will reprocess the IDocs.

Ref : note 784381

Regards,

aanand

Former Member
0 Kudos

HI

Replicate the all data sources once and try to run the process chain.

Regards,

chandra.