Process overdue error asynchronus transmission of info idoc 2 error

Hi
For an r/3 job i am getting the below message and it is not progressing from last 2 days and failing in BW with Process overdue error. Can somebody advise me on this.
data soucrce :0CO_OM_OPA_6
The job stucked for last 10 hrs and showing 0 records in BW.
Thanks
Subbu

Hi,
What are you trying to do...
are you performing any loads from the above said DataSource from R/3 to BW or
are you replicating the DataSource from your source system to BW side...
in any of the above cases..please check whether you have connected well to your source system from your BW system...
for this right click on source system in source system section of RSA1..and check..if everything is fine...then it should take such long time to complete your activity.
if not check in Tcode:SM59 to make sure the connectivity..which your problem can be solved sucessfully...
hope this is clear for you...
Regards
Ramsunder

Similar Messages

Job termination in source system /Asynchronous transmission of info IDoc 2

Hi All,
We have certain loads that we do every 2 hours, which will run for 20 to 30 minutes to load current year BCS data into a Basic Cube. So, In total we schedule 12 times in a day. This is needed as we have users around the globe.
We have totally 10 BGD processes and 10 Dialog processes.
These loads are scheduled through a process chain and we submit three parallel jobs at a time based on the version and in total we have 15 loads, 5 per each parallel job.
We went live with this process yesterday and the jobs ran all well until today afternoon, when they started giving the following message and when I checked the log of the process chain, one of the InfoPackage did fail with job termination in the source system.
The job log is as follows:
Date       Time     Message text                                                                 Message class Message no. Message type
06/20/2007 13:55:47 Job started                                                                       00           516          S
06/20/2007 13:55:47 Step 001 started (program SBIE0001, variant &0000000014146, user ID RFCUSER)      00           550          S
06/20/2007 13:55:47 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)          R3           413          S
06/20/2007 13:55:47 DATASOURCE = 80BCS_VC10                                                           R3           299          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:55:47 *          Current Values for Selected Profile Parameters               *         R8           049          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:55:47 * abap/heap_area_nondia......... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 * abap/heap_area_total.......... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 * abap/heaplimit................ 40894464                                *        R8           050          S
06/20/2007 13:55:47 * zcsa/installed_languages...... EFD                                     *        R8           050          S
06/20/2007 13:55:47 * zcsa/system_language.......... E                                       *        R8           050          S
06/20/2007 13:55:47 * ztta/max_memreq_MB............ 2047                                    *        R8           050          S
06/20/2007 13:55:47 * ztta/roll_area................ 3000320                                 *        R8           050          S
06/20/2007 13:55:47 * ztta/roll_extension........... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:58:04 NONE                                                                             UGBW          001          E
06/20/2007 13:58:04 Job cancelled after system exception ERROR_MESSAGE                                00           564          A
I do not have acceess in BWP to get you the Data Transfer Parameters within BW system.
Any suggestions would be greatly appreciated.
Thanks & Best Regards,
- Shashi

Hi Shashi,
Check in st22 for any dumps, do you have any pointer there?
Also check sm21 to identify possible cause of errors.
Regards.

Loading Error from CRM datasource - Info Idoc recieved with status 8

Hello All,
NEED YOUR HELP
We have a CRM datasource 0CRM_SALES_ACT_1 which works well from source in RSA3. The dataload is a full and fetches 19,000 records from CRM
However when we load it from an infopackage from BW it gives us the following "No data in source sysetm" Info Idoc with status 8. We have tried the following to eleminate some doubts
1) Checked the connection in SM59 using aleremote .Connection and authorization successful. Also loaded data in the BW system for other datasources from same CRM system it works well, so no authorization/ connections issues.
2) In the source system CRM tried transaction RSA3--> extract data get 19000 records
3) In the source system CRM Triied transaction RSA3--> Import Request from BW --> successful.
4) Checked the TRFC queue in SM58 the TRFC queue is empty
5) When we check the logs in CRM for ALEREMOTE we get the following message
synchronous transmission of info IDoc 2 in task 0001 (0 parallel tas
DATASOURCE = 0CRM_SALES_ACT_1
Current Values for Selected Profile Parameters
abap/heap_area_nondia......... 0
abap/heap_area_total.......... 9437184000
abap/heaplimit................ 40000000
zcsa/installed_languages...... ED
zcsa/system_language.......... E
ztta/max_memreq_MB............ 256
ztta/roll_area................ 3000000
ztta/roll_extension........... 2000000000
Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records
Result of customer enhancement: 0 records
IDOC: Info IDoc 2, IDoc No. 266228, Duration 00:00:00
IDoc: Start = 2008.10.22 14:18:38, End = 2008.10.22 14:18:38
Synchronized transmission of info IDoc 3 (0 parallel tasks)
IDOC: Info IDoc 3, IDoc No. 266229, Duration 00:00:00
IDoc: Start = 2008.10.22 14:18:39, End = 2008.10.22 14:18:39
Job finished
*What is the issue ? Data is present and confirmed available in source system , yet we get 0 records in BW system ? WE NEED YOUR HELP *

Hi
May be you need to provide full authorizations to the user 'ALEREMOTE'.Ask your basis team to check the authorizations.
Regards,
Chandu.

STATUS 51 error not directed to inbox (Idoc error)

Hi all,
When the single step Task is triggering for Idoc error ie,Status 51 the workitem is not going to the Users inbox.
The task has been assigned to User in PPOMW.
Note: The workitem is going for other Status.
Kindly guide with your points.
Thanks and Regards,
Sridhar

Hello,
Can you check the task attributes?
Also, can you please maintain the user assignment in the Task itself, through the path Extras>Agent Assignment>Maintain.
I think when you maintain the agent assignment in the task itself that would do the job correctly.
Cheers.
Abhijit

Error in transmission

Hi All,
One shopping cart was created with status as approved but in the Follow on Documents tab nothing was mentioned regarding the follow on documents created or not?
Then I checked the BBP_PD, and found that PO No has been assigned to the particular shopping cart wherein the status of each item was showing as Item in transfer process.
In order to get the status of shopping cart than I ran both the programs CLAEN_REQREQ_UP and BBP_GET_STATUS_2, but all in vain ,since the status of the shopping cart was still showing without any Follow on Documents.
Then i execute the BBP_PD_SC_RESUBMIT Function module,since the items were showing as Items in transfer process but after executing the same now the
shopping cart has started giving Error as "Error in transmission" and with an Error message as "Shopping Cart 0010128502 (Purchase order 3000061718): ME218 External document number 3000061718 already assigned "
Could you please provide any feedback regarding how to get back the status of the shopping cart with Follow On Documents No mentioned in the check status
option of the EBP Web version. We are working in SRM 4.0 /EBP V5.0.
An immediate respone in this regard is highly appreciated please.
Regards,
Pranab

Hi
Please go through the following SAP OSS Notes, which will defninitely help ->
Re: ECS describe requirement not transferred to backend
Re: Transfer PO from SRM to R/3 - Error in Process
Note 841021 - Manual price entered disappears - error 06 218
Note 932236 - BAPI_PO_CREATE1: Purchase order price unit not transferred
Note 580225 - Purchasing BAPIs: Conditions and pricing
Note 853970 - BAPI_PO_CREATE1: Net price is not transferred
Note 571860 - BAPI_PO_CREATE1: Price is not transferred
Note 487605 - ME21N: 06 218 'Net price must be greater than 0'.
Refer to these link as well for details.
Problem with BAPI_PO_CREATE1
PO created with status : Transfer Failed (E.Sys.)
Problem with BAPI_PO_CREATE1
Re: Error in pricing when doing sourcing in EBP 4.0
Re: STO classic scenario SRM 4.0
Re: Incorrect status in pricing - Short dump - IPC
Hope this will help.
Regards
- Atul

Error in transmission but No Error

Hi,
We are trying to create PO with SC having catalog items. After status approved it shows status as error in transmission but shows no error.
Also there is no entry found in application monitorRZ20.
Even debugging FM BBP_REQEQ_TRANSFER also did not helped.
Please help.
~Vipin

PO may not be created so far.
you must get an error in rz20 . it takes 3 minutes to see error in rz20 or sc application monitor.
even if you dont have error. go to monitor shopping cart -> click follow on document icon- now error message will be thrown in rz20 after 2-3 minutes for quick analysis.
i am pretty sure there is some data problem in that shopping cart. check vendor / account assignment details available and valid.
however check slg1 log.
Muthu

IDOC error in production server

Hi everyone,
I'm getting this error, when users trigger an Idoc:
Error while writing IDoc to file
Message no. EA084
Diagnosis
The IDoc was to be written to file
cocca3301\interface\output_idocs\1120549.txt
That was not possible because no authorization for writing to this file.
Procedure
Please inform your system administration.
Anyone has seen this before? in development and quality servers didn't happen this...
Thanks in advance. Helpful answers will be rewarded.

Not at all, I was talking with basis administrators about this problem for a long time. I'm pretty sure that it's all about folder permission. I think it's a matter of system, not SAP. But they said that's not the problem... I'm not 100% confident with that answer.
But, in order to keep idocs running, i found program RBDAGAIN, that reprocess the failed idocs. I put it into a job every 30 minutes. That solves my problem "temporary", until i solve the real problem.
I advice you to talk with your system administrator and/or basis, and check the group permission for the folder you are trying to put your files. If it works, please let me know.

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
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.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

IDOCS Error - Not getting processed automatically

Hi All,
We are loading hierarchy for a Product from R/3 system using the standard datasource.
When we execute the info package, IDOCs are not getting processed automatically.
We are facing the below error message.
Error when updating Idocs in Business Information Warehouse
Diagnosis
Errors have been reported in Business Information Warehouse during IDoc update:
No status record was passed to ALE by the applicat
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
Thanks in Advance
Regards,
Sachin

Hi,
This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, 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. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
Hope it helps a lot.
Thanks and Regards,
Kamesham

BBPIV IDoc Error Processing

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Use Transaction WE42 to identify the process code that is linked to your idoc type.
After you identify the process code, go to the detail screen and next to the "Identification" field you will see a button (ALE table). Click this button and it will take you to another detailed screen.
I assume that your Idoc Processing Type is via Function Module.
There will be a separate tab or block called "IDoc"
Choose the correct Object Type and in the fields Start event and end event configure the following values
INPUTERROROCCURRED INPUTFINISHED respectively.
You also need to create a agent (intended users to receive the errored Idocs via SAP Inbox) and map this info back in WE20 transaction.

IDOC Error V1 042 - Sales document X is currently being processed by user X

Hello Experts,
I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
I added a couple of minutes of wait time between the file processing but that did not help.
Please let me know if you have faces same situation and what solution did you apply.
Regards,
PS

Hopefully you have fixed this by now, but for anyone else who might be looking at this problem. We had this problem and we had the 2 programs check to see if the other was already runing. If so the program would submit itself for a number of minutes, different for both programs, and then exit. We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit. This was necessary because re-scheduling could put a program in conflict with itself. I hope that this may help someone. We used the join V_OP and searched for the program name, not the job name.
Kevin

Error message : Info Idoc missing ;database system

I am trying to load the data from database system oracle ,the data was successfully loaded into psa , but cant able to load the data into ods from psa .
Data in psa is all green without any errors , as info idocs are missing its not letting to load data manually from psa to ods ,
I try to reload but coming up with same error
Next day problem was fixed automatically, I want to know what is the exact reason for this problem and how can next day it fixed automatically

Error message : Info Idoc missing ;database system
I need the solution urgently, please help

Info IDoc : sent, not arrived ; Error passing data to port

Hi Folks,
While I am loading the data from R/3 I am facing the following error in Production..
Info IDoc 2 : sent, not arrived ; Error passing data to port
when I checked in SM59 every thing seems fine like RFC test connection and authorization check
In BW is check the Source system saying it is Ok.
Only the thing I found here is in TRFC, it is error when opening RFC Connection.
but it is different in SM59 saying every thing is ok, as said above..
Please help me in this regard
thanks masters
DJ

Srinivas,
Thanks for your prompt reply..
user : ALEREMOTE and password are fine..
As told I check st22 and sm21 in both sytems, no sort dumps I found..
Please help me its an urgent..
thanks
DJ
Message was edited by:
Jangareddy dasari

Error: process overdue

hi gurus,
what might be reasons for the error: process over due.
how can we try to solve it?
regards,
Rajesh

Rajesh,
Processing overdue can occur due to several reasons
1. Less number of background processes in BW. Increase the number.
2. Multiple infosources are trying to update one infoprovider.
3. Loading the cube without dropping the Index. Delete index first before loading cube.
4. Tablespace / table extend problem. Check w/Basis person.
5. All source system records have not come into BW and the BW process has time out. Check the timeout settings.
Thanks,
Bharath

Process overdue error asynchronus transmission of info idoc 2 error

Similar Messages

Maybe you are looking for