Hi all,
I have search through the forum but no concrete answer. I encounter this problem everytime the idoc jobs are export to a new server. My IDOC load stage would be stuck and no records updated into it. It would hang and be unable to stop. Have anyone encounter this problem before? Need to resolve this as this is production server. Thanks.
Regards
Joe
IDOC stage keep running(stuck)
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 232
- Joined: Sat May 07, 2005 2:49 pm
- Location: USA
Hi Ketfos,
Here is some Info regarding an IDOC
Here is some Info regarding an IDOC
Code: Select all
An IDoc (intermediate document) is a report, that is, a hierarchal package of related records, generated by SAP R/3 in an SAP proprietary format. An IDoc, whose transmission is initiated by the source database, exchanges data between applications. It provides a standard format for exchanging data with SAP R/3.
Thanks,
Naveen
Naveen
Hi netland,
The log file shows the usual stuff of '...NLS map ISO8859-1'. After that it is suppose to show sending rows to IDOC but didn't.
Connection to R/3 is ok and when validating the link, it shows all link connected.
I can choose different idoc type from the stage, so i think there should be no problem with authorization.
We had this problem once last time when we migrate our dev server to a new one. Manage to resolve the problem by renaming the job and compiling it again. However, this time it doesn't work.
Regards
Joe
The log file shows the usual stuff of '...NLS map ISO8859-1'. After that it is suppose to show sending rows to IDOC but didn't.
Connection to R/3 is ok and when validating the link, it shows all link connected.
I can choose different idoc type from the stage, so i think there should be no problem with authorization.
We had this problem once last time when we migrate our dev server to a new one. Manage to resolve the problem by renaming the job and compiling it again. However, this time it doesn't work.
Regards
Joe
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
Re: IDOC stage keep running(stuck)
Is the memory usage going up when it is hanging?joetan wrote:Hi all,
I have search through the forum but no concrete answer. I encounter this problem everytime the idoc jobs are export to a new server. My IDOC load stage would be stuck and no records updated into it. It would hang and be unable to stop. Have anyone encounter this problem before? Need to resolve this as this is production server. Thanks.
Regards
Joe
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
IDOC stage keep running(stuck)
I have faced this problem recently while trying to load a huge volume of records into SAP. The Idoc in use was MATMAS_BAPI.
On execution of the load job nothing really was getting loaded into SAP system immediately and the Job log did not throw up any warnings.
It was only after 2 to 3 hours did the data get into the SAP System.
I beieve if there is huge volume of data and if the Idoc has many segments and sub segments then the entire process can be time taking.
On execution of the load job nothing really was getting loaded into SAP system immediately and the Job log did not throw up any warnings.
It was only after 2 to 3 hours did the data get into the SAP System.
I beieve if there is huge volume of data and if the Idoc has many segments and sub segments then the entire process can be time taking.
IDOC stage keep running(stuck)
I have faced this problem recently while trying to load a huge volume of records into SAP. The Idoc in use was MATMAS_BAPI.
On execution of the load job nothing really was getting loaded into SAP system immediately and the Job log did not throw up any warnings.
It was only after 2 to 3 hours did the data get into the SAP System.
I beieve if there is huge volume of data and if the Idoc has many segments and sub segments then the entire process can be time taking.
Rachana Singh,
SAP-DataStage Consultant,
Capgemini India.
On execution of the load job nothing really was getting loaded into SAP system immediately and the Job log did not throw up any warnings.
It was only after 2 to 3 hours did the data get into the SAP System.
I beieve if there is huge volume of data and if the Idoc has many segments and sub segments then the entire process can be time taking.
Rachana Singh,
SAP-DataStage Consultant,
Capgemini India.